|00:44||sep has joined IRC (firstname.lastname@example.org)|
|00:53||bakytn has joined IRC (email@example.com)|
|01:39||Yet_another_Bill has left IRC (Yet_another_Bill!billy@nat/redhat/x-ryyhipnxsztkujsa, Remote host closed the connection)|
|02:04||Yet_another_Bill has joined IRC (Yet_another_Bill!billy@nat/redhat/x-jzjmnpbkfouryqfw)|
|03:26||bakytn has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|03:28||LoveStorm has left IRC (LoveStorm!Storm@gateway/shell/trekweb.org/x-utitzqlsrvuihnjs)|
|03:28||LoveStorm has joined IRC (LoveStorm!Storm@gateway/shell/trekweb.org/x-utitzqlsrvuihnjs)|
|03:49||adrianorg_ has left IRC (email@example.com, Read error: Operation timed out)|
|03:49||monteslu_ is now known as monteslu|
|04:07||zamba has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|05:31||leio_ has left IRC (leio_!~leio@gentoo/developer/leio, Ping timeout: 240 seconds)|
|06:24||leio has joined IRC (leio!~leio@gentoo/developer/leio)|
|06:34||vagrantc has left IRC (email@example.com, Quit: leaving)|
|09:30||monteslu_ has joined IRC (firstname.lastname@example.org)|
|09:33||monteslu has left IRC (email@example.com, Ping timeout: 240 seconds)|
|10:34||Trixboxer has joined IRC (Trixboxer!~Trixboxer@office.supportdepartment.net)|
|10:41||Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@CPE-121-218-39-117.lnse4.ken.bigpond.net.au)|
|10:49||Gremble has joined IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com)|
|11:02||adrianorg_ has joined IRC (firstname.lastname@example.org)|
|11:05||leio_ has joined IRC (leio_!~leio@gentoo/developer/leio)|
|11:07||leio has left IRC (leio!~leio@gentoo/developer/leio, Ping timeout: 252 seconds)|
|11:18||artista-frustrad has joined IRC (email@example.com)|
|11:27||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)|
|11:35||leio_ is now known as leio|
|11:52||andygraybeal has joined IRC (firstname.lastname@example.org)|
|11:59||zamba has joined IRC (email@example.com)|
|12:07||Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@CPE-121-218-39-117.lnse4.ken.bigpond.net.au, Quit: Leaving)|
|12:18||cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)|
|12:21||[GuS] has joined IRC ([GuS]!~MysT@unaffiliated/gus/x-663402)|
|12:27||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)|
|12:28||cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)|
what is the minimum required hardware for a fluent experience?
i feel i have lots of screen lag
especially when using a browser
and switching windows in the x session is sluggish
|12:38||bengoa has joined IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9)|
do you guys have a ton of 'console-kit-daemon's running? i'm using ubuntu 10.04 using htop to look at resources
and i'm trying to find memory leaks as i slowly run out of memory ;) i found one 'gnome-power-manager'
|12:50||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Read error: Connection reset by peer)|
i relinquished nearly 3GB with that
my system lasts about a month then needs rebooted
it's got 8GB of memory, but i run some kvm's too
oh and i run in 'thin client' mode.. which i meant to switch over to fat client this holiday, but i got terribly sick
|12:51||brunolambert has joined IRC (brunolambert!~bruno@nat/revolutionlinux/x-hwhrruduzsxauzhy)|
yea, and bonobo-activation-server ? that sounds pretty stupid
|13:04||cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)|
no words of help? i gotta run into town .. for a report and finish my work hours log.
aight, lata :)
|13:36||andygraybeal has left IRC (firstname.lastname@example.org, Quit: Ex-Chat)|
|13:41||khildin has joined IRC (email@example.com)|
|14:44||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
zamba: do you have LDM_DIRECTX=True in lts.conf?
|15:05||cliebow has joined IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us)|
zamba: and what are your client specs? ram and network speed?
100 mbps network
should be 128 MB ram
It's a bit underpowered for a fluent experience
With a gigabit network and 256 RAM it would go better
Currently, can you watch a fullscreen divx video without dropped frames?
hm, ok.. i'll check that the next time i'm on site
Btw, with 128 RAM, you might want to disable compcache and enable NBD_SWAP
|15:14||Mava has left IRC (Mava!~Mava@ip-45-224.dhcp.opintanner.fi, Ping timeout: 276 seconds)|
|15:14||bobby_C has joined IRC (bobby_Cfirstname.lastname@example.org)|
sup dude. Merry post-Xmas
Same to you too :)
I have a question pertaining to a kernel patch I am hoping to have implemented: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/907055
The maintainers are asking that I "submit upstream"
is that something that I can do by just tagging this patch, or is there some other process I am not aware of?
"upstream" means submitting the bug to the kernel itself, instead of ubuntu/launchpad etc
Your patch disables LVDS?
JUST for a certain model
a certain model by a certain manufacturer
And what if someone has this model and wants to use LVDS?
This specific model does not have an LVDS output. It's not a laptop, so when you boot the client for the first time, there is an "invisible" second monitor attached to the output
That card isn't available on *any* laptop?
The main crux of the problem is: this is not a laptop.
I mean, your code may fix your specific model + use case, but could it break someone else's laptop?
Which uses the same graphics card as you?
Mind if I PM you pertaining to this?
So, "upstream" in this case means that you should get in contact with the intel_lvds.c maintainers
Find the mailing list they use, and submit a bug report there, and the patch
_UsUrPeR_: did you say that it works ok with fedora?
Indeed it does!
Why? Do they have a fedora specific patch for that?
I am not sure, tbh. I have been told that Fedora is using a different driver.
lspci -nn -k | grep -A 2 VGA tells you the driver in use
In Fedora, I assume :)
In both, to compare the difference
|15:35||dead_inside has joined IRC (email@example.com)|
If Ubuntu should be using another driver, then that's another bug report you should file
Out of curiosity, if there is a difference, how does that help me?
Would ubuntu just switch drivers based on the difference?
Now you're trying to push a kernel change for something that happens on one distro and not on another
Applying a fix from one distro to another sounds easier to me
(easier to get it accepted upstream)
Yeah, I see what you're saying. This was suggested by one of the canonical team based on feedback at the bottom of that bug report
You didn't mention at the bug report that it works on Fedora though
This is true. I had thought this was independent. Ok, I see what you are saying. I will get the version numbers now, and report them in the bug.
If you did, I imagine that they would ask "why does it work in fedora? where's their patch"?
This will add some credibility to the report, stating that Fedora already fixed it, etc etc etc
|15:41||xsl has joined IRC (firstname.lastname@example.org)|
E.g. you may find that Fedora has already proposed your patch for inclusion, and you only need to wait for it to be available in Ubuntu
Or, you may find that Ubuntu is using the wrong driver for that model, and that needs to be changed, instead of blacklisting the model
This is almost the equivalent that stgraber implemented for another model with the same problem. I was just following along with how he implemented the patch: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/544671
The link I sent you was a bug entry for 10.04
same problem, different model
Yes, it says there that stgraber contacted upstream, to get his patch included
But, if it works in Fedora, that means that maybe there's a better fix somewhere else
Generally, blacklisting isn't a good fix, it's a workaround
So e.g. there may be other models with the same problem, and maybe all of them work in Fedora, because they solved the problem elsewhere
fedora probably has a different hack
the proper fix for that kind of hardware is the kernel patch
the non-workaround fix would be to have the manufacturer ship a fixed video BIOS and recall all existing devices, but that's pretty unlikely
|16:05||bobby_C has left IRC (bobby_Cemail@example.com, Quit: Goin' down hard)|
_UsUrPeR_: updated and commented in the bug
_UsUrPeR_: looking at my e-mail history, you probably want to send that patch by e-mail to firstname.lastname@example.org
stgraber: Thanks. I was looking for the proper upstream link to add this to myself, and am not sure where I would go for that.
_UsUrPeR_: here's the e-mail I sent them for mine: http://paste.ubuntu.com/784682/
_UsUrPeR_: last time I got feedback from them pretty quickly and it got pushed into the kernel a few days later. Adding a link to the mailing list discussion in the Launchpad bug may help the kernel team to include your fix once it's been reviewed upstream
as they said, they don't like distro patches, but as soon as something has been acked by an upstream kernel developer and pushed to the branch for the next linux kernel, they're usually fine cherrypicking it then
stgraber: mind if I ask the date you sent that email you pasted to me?
_UsUrPeR_: 03/23/2010 12:48 AM
stgraber: maybe Fedora has a method that better detects if an LVDS is available or not, and that would work on other models too. Why not have a look at their patch?
alkisg: there's such a method yes, but it's not better. They probably use the form factor from the DMI but that's wrong as we've been reported hundred of false positives
in general, I never look at fedora for their X stack as it's known to be pretty unstable and fails to work with a lot of hardware. Which is fine for a bleeding edge distro that doesn't care about binary drivers but doesn't quite match what ubuntu does
If the specific method with the form factor is worse, then sure, one shouldn't use it. But in general I don't mind looking at unstable code for better solutions, e.g. they do have a better solution for the acpi problems with the laptops
|16:18||staffencasa has joined IRC (email@example.com)|
|16:39||Trixboxer has left IRC (Trixboxer!~Trixboxer@office.supportdepartment.net, Ping timeout: 252 seconds)|
|16:39||Trixboxer has joined IRC (Trixboxer!~Trixboxer@220.127.116.11)|
|16:42||rishi__ has joined IRC (rishi__!~Trixboxer@office.supportdepartment.net)|
|16:42||Trixboxer has left IRC (Trixboxer!~Trixboxer@18.104.22.168, Read error: Connection reset by peer)|
|16:47||rishi__ has left IRC (rishi__!~Trixboxer@office.supportdepartment.net, Ping timeout: 240 seconds)|
|16:59||andygraybeal has joined IRC (firstname.lastname@example.org)|
|17:00||rishi__ has joined IRC (rishi__!~Trixboxer@22.214.171.124)|
stgraber: for the record, I guess dri-devel is using lists.freedesktop.org now for their mailing list
instead of sourceforge
|17:07||xsl has left IRC (email@example.com, Read error: Connection reset by peer)|
|17:08||xsl has joined IRC (firstname.lastname@example.org)|
_UsUrPeR_: good to know
|17:25||andy__ has joined IRC (email@example.com)|
|17:25||andy__ has left IRC (firstname.lastname@example.org, Quit: Ex-Chat)|
|17:29||Gremble has left IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com, Quit: I Leave)|
|18:20||rishi__ has left IRC (rishi__!~Trixboxer@126.96.36.199, Ping timeout: 240 seconds)|
|18:22||xsl has left IRC (email@example.com, Quit: Connection reset by fear)|
|18:26||matrix3000 has left IRC (matrix3000!~Eric@rrcs-70-61-255-227.central.biz.rr.com)|
|18:37||loather has joined IRC (firstname.lastname@example.org)|
|19:00||dead_inside has left IRC (email@example.com, Quit: Leaving...)|
|19:24||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)|
|19:26||andygraybeal has left IRC (firstname.lastname@example.org, Quit: Ex-Chat)|
|19:37||cliebow has left IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us, Quit: Leaving)|
|19:39||vagrantc has joined IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net)|
|19:44||cliebow has joined IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us)|
|19:54||[GuS] has left IRC ([GuS]!~MysT@unaffiliated/gus/x-663402, Remote host closed the connection)|
|20:00||cliebow has left IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us, Remote host closed the connection)|
|20:48||bengoa has left IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9, Quit: Leaving.)|
|20:56||brunolambert has left IRC (brunolambert!~bruno@nat/revolutionlinux/x-hwhrruduzsxauzhy, Quit: brunolambert)|
|20:56||andygraybeal has joined IRC (email@example.com)|
|21:01||vagrantc has left IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net, Ping timeout: 240 seconds)|
|21:30||monteslu__ has joined IRC (firstname.lastname@example.org)|
|21:33||monteslu_ has left IRC (email@example.com, Ping timeout: 240 seconds)|
|21:56||artista-frustrad has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|22:52||monteslu__ is now known as monteslu|
|23:19||khildin has left IRC (email@example.com, Quit: I'm gone, bye bye)|