=== zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-kernel === sharms [n=sharms@ubuntu/member/sharms] has joined #ubuntu-kernel [02:34] is the ipw2200bg card currently supported in feisty? I just booted, restricted manager said it was using driver ipw3894abg but I didnt see a device, then when I rebooted the card stopped working, I think it may have flashed it with the wrong firmware? [02:34] err, what? [02:35] the ipw2200 certainly is supported via the ipw2200 driver [02:35] right but for some reason feisty identified it as ipw3894abg [02:35] I'm not sure what you mean by "it may have flashed it with the wrong firmware", though [02:35] if I do an ls pci it shows 2200bg [02:35] which module is loaded? [02:35] not sure, I didnt know if we flash it with firmware like my old wireless card (prism54) [02:36] well, if by "flash" you mean "upload", then yes [02:36] the first time it was ipw3945.ko, subsequent reboots (with bios error message) use ipw2200 [02:38] Its not a big deal for me hardware wise, but if it was somehow related that could be a big issue [02:38] that's a very odd issue (rather, I've not seen that happen before. PCI ID mismatch?) [02:38] It may have been a bad card from the git-go, I just got it an hour ago [02:39] I believe the first time it booted it identified itself was ipw3945 on the lspci [02:39] but since reboot it said ipw2200 [02:42] ipw3945: MAC is in deep sleep! [02:42] ipw3945: Unable to int nic [02:43] I suppose you could use /usr/bin/update-pciids [02:43] ipw2200 and ipw3945 are very different cards [02:43] well it no longer identifies as ipw3945 [02:43] it now identifies as ipw2200 [02:43] Given that one is PCI and one is PCIE [02:43] yeah, that error really makes no sense to me [02:43] but it is conflicting with other devices it says now [02:43] from the bios that is [02:43] lspci -n please [02:44] the card is out right now, back to prism54 let me reboot [02:44] Nothing the drivers do can alter the card in a non-volatile way [02:45] If it's going in the same slot as a prism54, it's not an ipw3945 === sharms_ [n=sharms@cpe-24-208-240-36.twmi.res.rr.com] has joined #ubuntu-kernel === sharms [n=sharms@ubuntu/member/sharms] has joined #ubuntu-kernel [02:49] mjg59: http://paste.ubuntu-nl.org/14502/ [02:55] That's certainly an ipw2200 [02:55] It's mini-pci, right? [02:56] ya [02:56] its in my laptop [02:56] So it can't possibly be ipw3945 [02:57] That's only available in mini-pcie form [02:57] right thats why I was worried maybe ipw3945 might have done something to it somehow [02:57] No [02:57] ok so then I will just write this one off on bad hardware, I just wanted to run it by you guys === jml [n=jml@59.167.203.115] has joined #ubuntu-kernel === sharms [n=sharms@ubuntu/member/sharms] has joined #ubuntu-kernel [03:21] mjg59: doing some addition research (looks like you may have been involved in some of this), could it be that my bios may have a whitelist of cards and that could be causing the issue? [03:29] mjg59: how dangerous would it be to use your whitelist bios modifier? [03:32] ha just went for it will let you know === lamont [i=lamont@nat/hp/x-530d4106aa5bafc1] has joined #ubuntu-kernel === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel === mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === rikai_ [n=rikai@unaffiliated/rikai] has joined #ubuntu-kernel === hyper_ch [n=hyper@84-75-60-32.dclient.hispeed.ch] has left #ubuntu-kernel ["Konversation] === Huahua [n=mvgh@122.0.231.112] has joined #ubuntu-kernel === m0rg0th [n=manugarg@219.64.120.181] has joined #ubuntu-kernel === ivoks [n=ivoks@3-75.dsl.iskon.hr] has joined #ubuntu-kernel === cassidy [n=cassidy@host-213-189-171-21.brutele.be] has joined #ubuntu-kernel === varka [n=varkatop@p54a5ed24.dip.t-dialin.net] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === pmjdebruijn [n=pmjdebru@pmjdebruijn.xs4all.nl] has joined #ubuntu-kernel === marcin_ant [n=marcin@194.114.146.126] has joined #ubuntu-kernel === marcin_ant_ [n=marcin@194.114.146.126] has joined #ubuntu-kernel === marcin_ant [n=marcin@194.114.146.126] has joined #ubuntu-kernel === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel === Eruantalon [n=hans@5634185c.rev.stofanet.dk] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === gicmo [n=gicmo@p5491d0e2.dip.t-dialin.net] has joined #ubuntu-kernel === jml [n=jml@59.167.203.115] has joined #ubuntu-kernel === Billism [i=Billism@cpe-66-69-130-39.houston.res.rr.com] has joined #ubuntu-kernel === Billism [i=Billism@cpe-66-69-130-39.houston.res.rr.com] has left #ubuntu-kernel [] === johanbr [n=j@blk-224-156-151.eastlink.ca] has joined #ubuntu-kernel === cassidy [n=cassidy@host-213-189-171-21.brutele.be] has joined #ubuntu-kernel [03:53] BenC: #96480 probably ought to be critical? [04:40] mjg59: marked and milestone'd [04:40] Ta === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel === BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel [05:32] Interesting, latest vmware w6 seems to use vmx extensions on linux [05:47] hey BenC, about that, I wondered why I can't activate the paravirtualisation stuff with the latest version of VM W6 and a Core2 Duo with the VT ? [05:47] paravirt only works on 32-bit [05:47] and I'm running it enabled right now, so I know it works [05:48] strange, I'm using 2.6.20-14 on 32-bit [05:48] You have to go to your virtual machine pref's, Other tab, Advanced, and check the box for paravirt [05:48] it's not enabled in ws6 by default [05:49] yep, but I simply can't because it's grayed with the latest version of ws6 [05:49] what build do you have? [05:49] 42757 [05:49] e.x.p build-42757 [05:50] you have to power off the vm first [05:50] it's powered off [05:50] talk to vmware [05:51] Just checked on mine, and it let's me check/uncheck it as long as the vm is powered off, and I've setup for a 32-bit OS [05:53] hmm, seems to work with an all new VM and the same settings. I'll maybe have to report this to vmware ... === rouzic [n=rouzic@212.145.63.25] has joined #ubuntu-kernel === johanbr [n=j@JBrannlund.MathStat.Dal.Ca] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel === finalbeta [n=finalbet@d54C689F7.access.telenet.be] has joined #ubuntu-kernel [07:22] I'm starting to fear Feisty could air with this bug https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/98782 , And that would render it unusable for me. Check out the latest attached dmesg. I hope I don't overstep any boundaries here, but the desperate... :p. It's 15 minutes now to boot, and the latest 2 kernels give errors about the CD drive also. Dapper and Feisty ran fine, and 2.6.20.9 and lower ran fine. [07:30] Does it boot at the normal speed if you disconnect the CD drive? [07:31] Will try. [07:34] No, doesn't seem to change anything [07:34] But you no longer get the ata1.01 errors? [07:34] Not yet, I'm waiting, it can take a while... [07:34] It's just sitting there. (figuratively) [07:35] Yep, no more errors, and after the initial stall, It boots much faster. [07:35] Already at the login screen. [07:36] Ok. So it's pretty clearly linked to the unhappiness with the CD drive. [07:36] definitely. [07:36] You're using an 80-wire cable, right? [07:37] Ehm, It's a dell laptop. I have no idea what so ever. [07:37] Ah, ok. Interesting. [07:37] I can't screw that part open also... [07:37] What model? [07:37] Tried before, couldn't do it. [07:37] Inspiron 8200 [07:37] Ok. [07:37] At least 5 years old. [07:38] Don't have anything with that chipset here [07:38] I'll have to leave that with Ben, then [07:38] I'll add that removing the cd drive fixes it, and add a dmesg to the report when booting without CD drive. [07:39] Thanks for helping me out. [07:44] <_ion> benc: bzr branch http://johan.kiviniemi.name/software/bzr/hardware_connected/ [07:45] <_ion> benc: Usage example: if modinfo -F alias nvidia-9755 | hardware_connected; then echo "nvidia-9755 compatible hardware is connected" ... [07:58] <_ion> benc: Assuming all nvidia drivers are moved to a single nvidia-glx package and alternatives are used instead of diverts, here are simplified preinst scripts that should remove *all* old diverts, without a need to list them manually. http://johan.kiviniemi.name/tmp/nvidia-glx-dev.preinst.in http://johan.kiviniemi.name/tmp/nvidia-glx.preinst.in [07:58] <_ion> s/diverts/divertions/g [07:59] _ion: you can't just remove diversions. diverts can be done by sysadmins too. you need to be careful there [08:00] <_ion> fabbione: It only removes diversions made specifically by nvidia-glx packages. [08:00] and what happens if you hit a custom one? how would you switch to use alternatives? [08:01] anyway.. it's S U N D A Y [08:01] and i should stop reading IRC [08:01] :) [08:02] <_ion> I haven't really given a lot of thought to special cases in this regard. I believe that when there are multiple nvidia modules installed and the system's supposed to automatically use the right one based on connected hardware, alternatives is the way to go. [08:03] ok an init script that sets the right links like /lib/modules../volatile [08:03] s/ok/or [08:04] given that you can actually change hw across reboot === mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-kernel [08:04] providing a set of alternatives will make it complicated for normal users to switch between driver versions [08:04] <_ion> nvidia.ko isn't going to be linked using alternatives, but IMO libGL and nvidia_drv.so should. [08:05] not my call.. but i don't believe alternatives is the right solution [08:06] <_ion> benc: Any comments to the discussion above? === ivoks [n=ivoks@20-147.dsl.iskon.hr] has joined #ubuntu-kernel === marcin_ant [n=marcin@194.114.146.126] has joined #ubuntu-kernel === cassidy [n=cassidy@host-213-189-171-21.brutele.be] has joined #ubuntu-kernel === zdzichuBG [i=matthew@ogrody.nsm.pl] has joined #ubuntu-kernel [09:03] hi === reitblatt [n=mark@resnet-50-24.dorm.utexas.edu] has joined #ubuntu-kernel === pkl_ [n=phillip@lougher.demon.co.uk] has joined #ubuntu-kernel === marcin_ant [n=marcin@194.114.146.126] has joined #ubuntu-kernel