[04:47] <elcasey> hey, what's the status on the JMicron fix? Mid-next week?
[04:48] <BenC> will be uploaded Sat
[04:48] <BenC> give 24-48 hours for turn around on builds and archive process
[04:49] <BenC> I'd say by Monday for sure
[04:49] <elcasey> oh nice
[04:50] <elcasey> my current edgy install has just gotten so weird it's time to kill it, and I'd like to go with feisty now if it'll boot
[04:50] <elcasey> it's supporting ralink wifi now, or still not worked out?
[04:50] <BenC> should be working
[04:50] <BenC> which chip?
[04:51] <elcasey> final question - i know it'll support compiz "out of the box" with supported drivers...will those also run beryl?
[04:51] <elcasey> rt61
[04:52] <BenC> rt61 should work
[04:53] <BenC> if you can run compiz, you should be able to run beryl
[04:53] <elcasey> excellent!
[04:53] <BenC> beryl can be a little more intensive on the gpu though
[04:53] <elcasey> seems the latest kernel will fix basically every linux issue i was having
[04:53] <BenC> so you may not be able to run it as well
[04:53] <BenC> glad to hear it
[04:53] <elcasey> well, i have a 7950GT, but I had serious driver issues in my latests install
[04:54] <elcasey> i'm actually running beryl on my intel 915 right now, which runs great, surprisingly. I've never tried compiz, i just may check it out.
[04:55] <elcasey> what version is monday's kernel going to be? 2.6.20-15?
[05:01] <BenC> -13
[05:01] <elcasey> guess I got ahead of myself :P
[05:02] <elcasey> thanks very much, BenC
[05:02] <BenC> np
[05:16] <tritium> BenC: atheros support wasn't touched in your latest fix for 2.6.20-12.20, right?  I can't even load ath_pci.  I get "Unknown symbol ath_hal_" errors.
[05:17] <tritium> I have an AR5212
[05:17] <BenC> are you sure you didn't disable it somehow with restricted-manager?
[05:17] <tritium> I'll double check, but I highly doubt that.
[05:19] <tritium> I run it, and it simply states my hardware doesn't need any restricted drivers.
[05:21] <tritium> And "sudo restricted-manager" returns "modinfo: could not find module ath_hal" (among others)
[05:22] <BenC> sudo /etc/init.d/linux-restricted-modules-common start
[05:22] <BenC> sudo depmod -a
[05:22] <BenC> sudo modprobe ath_pci
[05:22] <BenC> see if that does anything
[05:23] <tritium> BenC: that did it.
[05:23] <tritium> Thank you.
[05:23] <BenC> np
[05:25] <tritium> I should say the module now loads, but network-manager still doesn't work with it.
[06:03] <tritium> Is wireless with atheros AR5212 known not to work with 2.6.20?
[06:45] <BenC> tritium: -13 kernel upload has a new atheros driver, so probably wait for that
[06:46] <tritium> BenC: great info.  Thanks.
[06:48] <fabbione> ah cool
[06:48] <fabbione> abi change
[06:48] <fabbione> that's exactly what i was looking for :)
[06:48] <fabbione> because also gfs2/dlm will change api ;)
[06:48] <tritium> BenC: you already uploaded it?
[06:49] <BenC> tritium: No, should be available by Monday
[06:49] <tritium> Great.  Thanks!
[06:51] <fabbione> BenC: can it wait at least your morning for upload? i want to finish to test these fixes
[06:52] <BenC> fabbione: Not uploading till Saturday (post beta)
[06:52] <fabbione> BenC: ok perfect
[06:53] <fabbione> shouldn't take me more than kernel build time + userland local rebuild and a couple of reboots to test
[07:53] <Nafallo> hi! is there any way I can stop the race where I have two controllers, one SCSI and one using libata, and can never know which disks are sdb and which are sdf?
[07:53] <Nafallo> right now sdf and sdg are my RAID1 / :-P
[07:54] <fabbione> Nafallo: no you can't. that's why we mount by UUID
[07:55] <fabbione> and what kind of problem is that anyway?
[07:55] <fabbione> RAID doesn't need to know what devices are involved anyway
[07:55] <fabbione> not to build the array at least
[07:55] <fabbione> it uses the md superblock information to assemble it
[07:55] <fabbione> so it doesn't matter how the devices are named
[07:56] <fabbione> BenC, kylem:
[07:56] <fabbione> Checking module listings...
[07:56] <fabbione> Modules have gone missing:
[07:56] <fabbione> uvcvideo
[07:56] <fabbione> Will not continue!
[07:56] <fabbione> make: *** [build]  Error 1
[07:56] <fabbione> this is latest git
[07:56] <Nafallo> well, when I tried to restart newly upgraded feisty I got dropped into initramfs after it couldn't assemble /dev/md2 :-P
[07:57] <fabbione> Nafallo: that's not a kernel issue anyway.. talk to iwj and check mdadm bug list
[07:57] <Nafallo> so right now I've booted into one of the root-mirrors by plain luck :-P
[07:57] <Nafallo> oki
[07:58] <fabbione> the race is there rather than the kernel
[07:58] <Nafallo> ah, right :-)
[08:10] <moparisthebest> does anyone know anything about the TCP congestion control plugins?
[08:10] <moparisthebest> for example, how they work, and/or how one would go about writing a new one?
[08:11] <Nafallo> fabbione: wait a moment... are we supposed to mount RAID1 as UUID now aswell?
[08:12] <fabbione> Nafallo: the filesystem on top of the raid.. yes.. if it has a uuid
[08:12] <fabbione> but the problem is that mdadm is not assembling the raid
[08:12] <fabbione> that's slightly different
[08:12] <fabbione> a raid has also a raid UUID
[08:13] <fabbione> that's not the same as the filesystem UUID on top
[08:13] <fabbione> don't get confused because they are 2 different thigns
[08:13] <Nafallo> yea, most likely cause it haven't loaded anything to get harddrives at that point :-)
[08:13] <Nafallo> so what should I have for root= on the kernel cmdline?
[08:23] <ivoks> BenC: good news: rmmoding ata_piix during installation fixes issue with older Intel IDE controlers...
[09:08] <varka> hi
[09:09] <fabbione> BenC: you were partially right about the qla firmware.. the problem is that there is no firmware for qla24xx
[09:09] <fabbione> BenC: but the others seem to build from the kernel. tho i think it would be best to just update them 
[09:09] <fabbione> or at least add the qla24xx
[12:32] <fabbione> BenC: ok. i am all good with DLM and GFS2. i didn't push any update because one of them introduces a regression rather than helping 
[12:32] <fabbione> BenC: so upload at will
[05:15] <Nafallo> hi! does anyone know about a bug where /dev/sdb is created but not /dev/sdb? ? :-/
[05:15] <Nafallo> ehrm
[05:15] <Nafallo> -EWRONGCHAN
[06:28] <Nafallo> hmm
[06:29] <Nafallo> my 120GB PATA100 disks say they doesn't support smart anymore
[06:29] <Nafallo> should I hate libata now? :-)
[09:01] <mvo> hello! did the edgy->feisty kernel changes include a change in the device for cdroms? it looks like /dev/hdc (edgy) changed to /dev/scd0
[09:01] <mvo> (feisty)
[09:01] <Mithrandir> mvo: quite possibly.
[09:01] <Nafallo> yes :-)
[09:01] <Nafallo> for libata stuff it should have atleast
[09:02] <mvo> so we need a upgrade strategy
[09:03] <Nafallo> oh?
[09:04] <Nafallo> /dev/cdrom isn't the default in fstab?
[09:10] <mvo> on my test-install its /dev/hdc in /etc/fstab (fresh edgy install)
[09:11] <Nafallo> ouch :-)
[09:35] <mjg59> mvo: It should be /dev/cdrom
[09:35] <mjg59> Are you sure you haven't changed that by hand?
[09:36] <mvo> mjg59: yes. I did a fresh install for the upgrade testing
[09:36] <mvo> (fresh edgy install that is)
[09:37] <mjg59> Hm. Fun.
[09:38] <mvo> I also have a "/dev/          /media/floppy0" line 
[10:42] <bdmurray> my laptop has a sd/ms-pro/mmc/xd reader and when I insert an xD card in it the kernel doesn't report it
[10:42] <bdmurray> How could I track that down or get some more useful information?
[10:44] <mjg59> It's not supported
[10:45] <bdmurray> well, that makes it easy.  Is that true for all devices like that?
[10:49] <mjg59> The only xd readers we support are ones that connect via USB
[10:54] <bdmurray> Oh, so the one in my desktop is connected via USB.  So if future bugs come in about on board xd media readers they should be rejected?
[10:57] <mjg59> No, it's a valid bug
[10:57] <mjg59> It's just not one that's going to be fixed in the near future
[10:58] <bdmurray> Is there a "master" bug for those then?  One that all dupes should go to?
[11:03] <Nafallo> hmm
[11:04] <Nafallo> http://paste.ubuntu-nl.org/11752/
[11:04] <Nafallo> what does that mean? :-)
[11:05] <mjg59> Nafallo: Context?
[11:05] <Nafallo> ata7.01 (sde) failed in the RAID5-array :-/
[11:06] <Nafallo> and that paste is from dmesg
[11:06] <Nafallo> should I be worried? :-)
[11:06] <mjg59> What kernel?
[11:06] <mjg59> And does this always happen?
[11:07] <Nafallo> latest feisty
[11:07] <Nafallo> 2.6.20-12-server
[11:07] <Nafallo> no idea. the disk is new to me. plugged it in yesterday :-)
[11:08] <mjg59> See if the same happens with older kernels
[11:08] <mjg59> Then file a bug
[11:08] <Nafallo> I'm doing a cat /dev/zero > /dev/sde now and will try to add it to the array again. we'll see what happens :-)
[11:08] <Nafallo> okey, thanks :-)
[11:24] <Nafallo> mjg59: hehe. I get it numerous times while doing the lowlevel format... PIO0 _can't_ be a good sign ;-)
[11:25] <Nafallo> mjg59: might aswell be broken hardware though. SMART seems not ported for libata yet.
[11:28] <Nafallo> baah
[11:28] <Nafallo> [25195.000000]  Buffer I/O error on device sde, logical block 423072
[11:28] <Nafallo> [25195.010000]  lost page write due to I/O error on sde
[11:28] <Nafallo> broken hardware, right?
[11:29] <mjg59> Sounds like it
[11:30] <mjg59> But try it on a different port
[11:30] <Nafallo> the other ports have drives connected, but sure, I could swap some of them :-)
[11:54] <Nafallo> ehrm, launchpad doesn't have older kernels?
[11:56] <mjg59> Correct
[11:57] <Nafallo> how irritating :-P
[11:58] <Nafallo> then I can't test older kernels
[12:04] <Mithrandir> it does, it's just well-hidden
[12:05] <Mithrandir> find the previous version, find the build for the architecture you're interested in, and download the "resulting binaries"
[12:07] <Nafallo> ah, kewl :-)
[12:07] <Nafallo> thanks Mithrandir :-)