[02:55] <zul> xen-2.6.20 building now :)
[03:40] <lifeless> cool
[03:40] <lifeless> zul: zen for fisty would be so nice.
[07:05] <dfgas> are there any precompiled kernels for dapper that is 2.6.19 or better?
[07:05] <dfgas> or a repo i could use for it
[11:19] <Ninjai> if i installed for example ubuntu + slax dual boot....and i am right now in ubuntu and doing: chroot /mnt/sda2 for example which stands for slax partition... what things will work and which wont work ??
[11:20] <crimsun> that's really difficult to know offhand, as very few of us run slax
[11:20] <xNinja> ok i have slax installed and now installing ubuntu 6.10
[11:21] <Nafallo> this is not really a supportchannel either :-). maybe you want to try #ubuntu or #ubuntu-CC? :-)
[11:21] <crimsun> I think xNinja wants #ubuntu
[11:21] <xNinja> i am there but no one answering me!
[11:21] <crimsun> I'll address this question there
[11:22] <xNinja> thanks
[12:18] <Tm_T> Hi kids.
[12:19] <Tm_T> This might go slightly OT but:
[12:19] <Tm_T> "Note: You need to have CONFIG_USB_NET_CDCETHER compiled either into the kernel, or as a module, in your kernel config."
[12:19] <Tm_T> And with Ubuntu kernels, situation is?
[12:19] <Tm_T> I'm totally out with kernel things.
[12:20] <thom> Tm_T: grep CONFIG_USB_NET_CDCETHER /boot/config-`uname -r`
[12:20] <Tm_T> Aah thanks.
[12:20] <thom> np
[02:08] <trueg> Hi guys
[02:08] <trueg> Does the ubunto kernel by default enable CD/DVD drive auto-closing?
[02:17] <maelcum> hi! i have an nforce 2 chipset and the system becomes very unresponsive during heavy disk i/o. this can be fixed by giving the kernel the "noapic" boot option. can this be added to some part of ubuntu so that it sets the option for this chipset?
[02:18] <maelcum> i don't think that people realize that this is a fixable problem, so a bug on launchpad will probably not get very much attention.
[02:19] <maelcum> iirc, i found the fix in some dark corner of the internet, nothing you'd expect the average user to find...
[02:21] <zul> maelcum: submit a bug request and it will get looked at
[02:27] <maelcum> zul: ok, i did that.
[02:28] <zul> thanks
[02:29] <maelcum> launchpad is the least annying bug tracker i have used so far, by two orders of magnitude.
[02:29] <maelcum> *annoying
[02:30] <Nafallo> :-)
[04:10] <lifeless> kylem: around ?
[04:10] <kylem> yes.
[04:11] <lifeless> I've updated bug 88899
[04:11] <lifeless> its buggered right this instant, is there anything more you want from me about it at this point ?
[04:12] <kylem> not really, i have no idea what the problem is.
[04:12] <kylem> can you attach your /proc/acpi/dsdt?
[04:12] <lifeless> sure
[04:12] <kylem> thanks.
[04:14] <lifeless> done
[04:14] <kylem> thanks. 
[04:33] <seb128> hi
[04:35] <seb128> pkl_: have you looked at bug https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/87078 ?
[04:36] <seb128> do you think it'll be fixed for feisty?
[04:37] <pkl_> seb128: have not looked at it yet.  It may be fixed for feisty, very much depends on whether I can identify the problem :-)
[04:37] <seb128> k
[04:38] <seb128> I think I'll just get a new network card then
[04:38] <seb128> network crashing is really unproductive, I've not close all the things I'm working on, etc every time
[04:38] <pkl_> seb128: there's a number of similar bug reports for different cards.  May be a related problem, in which case similar fixes may work etc.
[04:40] <seb128> pkl_: k, let me know if you need extra details
[04:40] <seb128> if that's not fixed for feisty I'll get a new card ;)
[04:41] <pkl_> seb128: looking at bug 76489, a similar issue is reported.  This appears to be fixed by turning off TSO ("TCP Segmentation Offload") with "sudo ethtool -K eth0 tso off".  You could give that a go, and report back.  Thanks
[04:42] <seb128> pkl_: ok, will
[04:42] <seb128> $ sudo ethtool -K eth1 tso off
[04:42] <seb128> Cannot set device tcp segmentation offload settings: Operation not supported
[04:45] <mjg59> pkl_: 8029 is a ne2k-pci
[04:45] <mjg59> The fact that it manages packets at all is sort of amazing
[04:46] <pkl_> mjg59: yeah, I used to have some ISA based ne2k boards...
[04:47] <pkl_> mjg59: a long time ago...
[04:47] <seb128> the card was working fine with 2.6.17 :p
[04:48] <mjg59> seb128: Diff the driver for the two cases?
[04:49] <pkl_> seb128: a number of  the drivers used to work OK in 2.6.17, and so it's not as straight forward as a diff.  Kernel changes in other parts of the kernel maybe causing problems.... 
[04:50] <mjg59> Actually, it doesn't seem to use workqueues, so there's a chance that just building the 2.6.17 driver would work
[04:51] <pkl_> seb128: it is probably worth diff-ing the drivers in case just in case.
[04:51] <seb128> mjg59, pkl_: ok, will do that
[04:51] <mjg59> seb128: You'll need to check ne2k-pci and 8390.c
[04:58] <pkl_> seb128: kyle has put a note on the comment asking you to try adding "irqpoll" to the kernel command line. 
[05:17] <lifeless> kylem: I think my laptops power-on power-state affects it
[05:18] <kylem> it's possible
[05:18] <lifeless> kylem: I had booted off battery; I've just hibernated and powered on again with the power on
[05:18] <lifeless> and once it came up removed and inserted the power lead and its happy now
[05:18] <kylem> whacko.
[05:19] <lifeless> yahuh
[07:53] <leroutier> hello
[07:53] <leroutier> got a systematic kernel panic when my webcam is plugged/ uvc driver is loaded
[07:53] <leroutier> on feisty with latest kernel
[07:54] <mjg59> leroutier: Got a bug number?
[07:54] <leroutier> nope, not reported to launchpad yet
[07:54] <leroutier> let me check if not a known prob
[08:01] <leroutier> hum, no luck, I can't access to launchpad
[08:01] <leroutier> I'll retry later, and come back here once the bug report is done
[08:02] <leroutier> dmesg with kernel traces saved
[08:03] <mjg59> Thanks
[08:03] <leroutier> looks like the crash is in alsa "snd_pcm" (when webcam is plugged), so perhaps interaction with "snd_usb_*"
[08:03] <leroutier> I'll come back once I have a proper bug report. ++
[08:30] <leroutier> mjg59, still around ?
[08:30] <leroutier> Bug #90922
[08:31] <mjg59> leroutier: Just heading out - someone ought to take a look shortly
[08:31] <mjg59> (19:30 here, food time!)
[08:31] <leroutier> oh, sorry yes, you're in UK
[08:31] <leroutier> have a good lunch
[08:31] <leroutier> and no hurry for this crash. it's just a webcam after all
[08:37] <JanC> 19:30 = food time ?
[08:37] <JanC> for me that's more around 21-22h   :)
[08:37] <JanC> (people tell me I should migrate to Spain ;-) )
[08:41] <leroutier> yep, I was told in spain it's more around 21h
[08:41] <leroutier> hard to find a place to eat around 10PM in UK (last time I was there)
[08:44] <bdmurray> BenC: Could you explain bug 57502 to me?
[08:47] <bdmurray> Or rather how could I find out if another one is similar to it.
[08:53] <BenC> bdmurray: Can you give me that bug# again?
[08:55] <leroutier> it was 57502
[08:55] <bdmurray> JMicron SATA controller
[08:56] <bdmurray> and I thought you mentioned an ICH8 controller too
[08:56] <bdmurray> in that bug report
[08:58] <BenC> bdmurray: What did you need explaining?
[08:58] <BenC> bdmurray: I just added a note about the status of dapper
[09:00] <bdmurray> BenC: I was trying to figure out if 58358 might be a duplicate
[09:02] <BenC> bdmurray: This sounds more like the Marvel IDE issue
[09:03] <BenC> bdmurray: Similar problem, but different driver
[09:03] <BenC> JMicron is fixed in stock edgy
[09:03] <BenC> fixed in dapper-proposed too
[09:03] <BenC> Marvell driver didn't make it into edgy, but is in edgy-proposed
[09:04] <bdmurray> BenC: and the JMicron is fixed on the Live CD too now?
[09:04] <BenC> and I think dapper-proposed as well
[09:04] <BenC> bdmurray: JMicron was fixed in edgy well before release, so all CD's
[09:04] <BenC> unless it's some new chipset, but I haven't heard of anything from my JMicron contact
[09:04] <bdmurray> Okay, cool.  Do you want to update 58358 or should I?
[09:05] <bdmurray> regarding testing proposed
[09:05] <BenC> bdmurray: Please do, but confirm it's a Marvell (lspci should show it)
[09:05] <BenC> kind of hard to test proposed if they don't have an existing install (No CD support means no install)
[09:05] <bdmurray> BenC: Okay, I asked for that.  "I ended up connecting my IDE CD ROM drive to SATA controller using a converter and that works now"
[09:06] <bdmurray> So he should be able to test, right?
[09:11] <BenC> yeah
[09:14] <bdmurray> I got a new HP laptop yesterday
[09:16] <kylem> working ok?
[09:19] <bdmurray> Yeah, everything seems to just work so far with Feisty.
[09:20] <bdmurray> It's all intel stuff - video and wireless.
[09:20] <kylem> cool.
[09:20] <kylem> suspend/resume? :)
[09:20] <bdmurray> Suspend yes, Hibernate had an X issue on resume
[09:20] <bdmurray> I could log into vt2 and had to restart kdm
[09:20] <kylem> bizarre. ok.
[09:21] <bdmurray> I got a CPU softlockup once and haven't been able to reproduce it
[09:22] <bdmurray> I think I might have booted with the killswitch off when I got the softlockup
[09:22] <zul>  /win 16
[09:23] <zul> gah...Im so ready to go home
[09:29] <bdmurray> bug 58358 seems to have an Intel IDE controller
[09:41] <lamont> BenC: you around?
[09:42] <lamont> probably works best if you request it,  rather than me... :-)
[09:42] <lamont> thoughts?
[09:43] <BenC> lamont: You can send an rt request and attach my blessing :)
[09:43] <lamont> ok
[09:43] <BenC> lamont: I prefer if you push to a branch of the tree, and send pull requests to me to make sure I don't get conflicting tree's during an upload preperation
[09:44] <lamont> np.  issue right now is EPERM trying to get to the tree at al
[09:44] <lamont> all
[09:44] <BenC> ah, total control :)
[09:46] <lamont> sigh.  forgot to cc  you
[10:08] <bdmurray> kylem: So I can get it to soft lockup 50% of the time by booting with killswitch off
[10:08] <kylem> killswitch off meaning?
[10:09] <bdmurray> The wireless switch on the laptop
[10:09] <bdmurray> It's a physical switch
[10:09] <kylem> so wireless on, in other words?
[10:09] <bdmurray> no off
[10:09] <bdmurray> I guess that is bad wording
[10:09] <bdmurray> killswitch on == wireless off
[10:09] <kylem> there's like quadruple negation here.
[10:09] <bdmurray> I know my bad
[10:09] <kylem> ipw3945?
[10:09] <bdmurray> yes
[10:10] <kylem> feisty kernel?
[10:10] <bdmurray> yep
[10:10] <kylem> bummer. i thought this was fixed.
[10:10] <bdmurray> got a call trace this time. I guess I'll submit a bug