User1: hi, some things about your current kernel
User1: a) ndiswrapper is too old, remove or update - with 1.30 and installed usb wlan drivers you get a system lock
User1: b) pata-sis is borken in git, -8- kernel worked
User1: if you want to fix some little things like hostap + via intel southbridge bugfix take a look here
User1: http://kanotix.com/files/kernel/kernel-update-pack-noide/source/
User1: ndiswrapper 1.37 is not fully stable with 2.6.20 for me, will try to find a stable svn snapshot
User1: bye
User2: User3 any idea if/when the patch mentioned in #
User2: https://launchpad.net/bugs/87253 will make it into feisty?
User3: User2 it's already in feisty's ubuntu-2.6.git; expect it in the next kernel upload (you'd have to ask Ben for an ETA)
User2: User3 ok cool, thanks, as long as it make it's way in eventually I am happy :)
User2: User3 i asked earlier and got an "i think so" but... do you know for sure if these are in or getting in... http://svn.sourceforge.net/viewvc/mactel-linux/trunk/kernel/mactel-patches-2.6.20/
User2: i only ask again because if they are not I am interested in looking into it, it just don't want to waste time if they are already in or planned to be in
User3: I can only speak for audio [which I've addressed]
User3: I'm afraid I don't have any additional time atm to check
User2: ok, np, thanks
User2: i can dig in myself and check
User3: be aware that some of that code is already outdated
User3: certainly the sigmatel diff is incomplete
User2: User3 thanks for the heads up
User4: User7 Hi, will tp_smapi added to ubuntu kernel 2.6.20?
User5: hi
User5: I have a Dell Latitude D820 laptop and have been trying to get feisty fawn running on it. works fine so far but teh wireless drivers don't work.. found the driver (ipw3945) and followed the build instructions (involving replacing a module from the kernel source)
User5: but now I get some "no rule for target ubuntu/net/d80211/ieee80211.o" error.. (translated back from German)
User5: any ideas?
User5: the module is ieeee80211, a prerequisite for ipw3945
User6: er
User5: yes?
User6: ubuntu ships ipw3945 in l-r-m; why did you build it manually?
User5: because it did not work..
User6: you'll have to be a bit more specific.
User5: looked around and found instructions to install a newer version of it including the new ieee80211
User5: lspci showed the device, the module was loaded but no activity.. everything seemed fine, it just can't find anything or connect to anything
User6: strange. well, as long as you have the kernel headers and general build tools installed, compiling the new driver should simply work.
User5: the ieee80211 build process complains about a conflicting kernel version and wants to disable/outcomment it and add its own version
User5: conflicting module version
User5: in the kernel
User5: bbl
User7: which boot issue?
User7: bug number would be helpful
User8: i think my crestline reproduces that.
User8: [g2] , can you try booting with acpi=off or whatever and tell me if that helps? (it's what i did)
User8: (booting with irqpoll didn't fix things for me, which is why i ask)
User8: i just tried without the piix ide driver built into the kernel at all, and it's still an issue, so i'm kind of confused.
User8: livecd boots are fine, after install boots are boned, which confuses the hell out of me. :\
User8: [g2] , what is the symptom you see? i get "link down" on all sata links from ahci.
User8: hmm, i should try with i386.
User8: and edgy works flawlessly for you?
User8: ok.
User8: can you cat /proc/interrupts from your working system and /msg it to me?
User8: i think i just found something in common between working and non-working on my system.
User8: absolutely.
User8: i figured my acpi bios was just broken, but if other people are seeing this, something more insidious might be happening (the box i'm seeing it on isn't production so.. :/)
User8: ah, no sata?
User8: hrm
User8: ahci uses msi for me, so even with pci=nomsi irqpoll i am still getting no luck.
User8: hrm. ok.
User8: /proc/interrupts and dmesg on pastebin would be fantastic.
User8: yeah.
User8: i'm adding some crap to my kernel to see if i actually get any interrupts from libata (it shares the irq with uhci, so it's hard to tell.)
User8: for a while i thought maybe uhci was stealing the interrupts but it seems not.
User8: thanks
User8: yeah, definitely looks like there's no interrupt.
User7: so is piix conflicting with ata_piix?
User7: if that's the issue, I can fix it real quick
User8: no.
User8: not for paul92@example.com.
User7: the last comment is a different bug then?
User8: it's entirely possible intel managed to fuck the acpi bios completely on this sdv.
User7: I thought I had commented out the entries in piix that matched in ata_piix
User8: but it's pretty similar, edgy/feisty cds work, first boot into installed system fails miserably and no disks get see.
User8: n
User7: a conflict between piix and ata_piix seems impossible
User7: oh wait
User7: CONFIG_ATA_PIIX isn't defined, CONFIG_ATA_PIIX_MODULE is
User7: retarded
User8: [g2] , oh?
User8: interesting.
User8: i don't think i see that. can you try booting, wait for the initramfs, cat /proc/kmsg and take a picture of the oops?
User8: ok.
User7: User8 This *_MODULE thing could be the cause of a lot of problems, so keep it in mind when you check bug reports
User7: I fixed all the ones I had
User8: _MODULE?
User7: User8 The idea was that some of the pata drivers only had some of the matching PCI id's for the same IDE driver, so I had to keep the IDE driver enabled, but make it disable the matching PCI id's (so it would use pata)
User8: i see. hmm.
User7: but I used "#ifndef CONFIG_ATA_PIIX", and it wasn't matching
User7: it could account for this sort of thing (CD working, but normal boot isn't)
User7: piix, generic and siimage were the three drivers affected
User8: hmm.
User7: piix should only be used on a hand full of devices
User7: g2: Can you pastebin "lspci -vv"?
User7: and /proc/interrupts
User9: heylo
User7: either way should be fine
User7: looks like your ICH5 and UHCI are sharing IRQ's, just wondering if anything else is on it
User7: wtf
User7: is this on edgy?
User7: ok, irq's are routed to different numbers...
User7: I wish libata would use the driver name instead of just libata for request_irq() :/
User7: weird, on this one ide, sata and uhci show same irq in lspci, but it's not showing that in proc/interrupts
User7: ah, 201 is the audio
User7: so libata is taking taking 169 twice, and uhci_hcd is taking it once
User7: Can you do /proc/interrupts on feisty?
User7: try without
User7: be better to see what it's doing with acpi irq routing
User7: yeah
User7: ah, ide2
User7: ok, are you in busybox?
User7: rmmod piix
User7: modprobe ata_piix
User7: see if that does anything
User7: hmm
User7: ide modules are prone to being load-only
User7: ok, boot with whatever options you need to get to 2.6.20 being up
User7: rm -f /lib/modules/`uname -r`/kernel/drivers/ide/piix.ko
User7: update-initramfs -u
User7: then reboot without any options
User7: Ah, it's drivers/ide/pci/piix.ko
User7: But you can't do this from a livecd
User7: [g2] : Ok, can you pastebin lsmod output?
User7: piix is definitely loaded, and shouldn't be
User7: do you have feisty installed or are you doing this from livecd alone?
User7: You should be ok if you just rm the piix.ko driver
User7: next kernel upload will have that fixed
User7: I think piix and ata_piix don't play well together
User7: getting rid of piix fixed it up?
User7: or still using irqpoll?
User7: sounds good, thanks for testing
User7: [g2]  next kernel update should be fixed without needing any special hacks
User7: np
User7: [g2] : Lab, no, just the machines I have, and other developers have
User7: we have a support center that does testing for certain machines
User7: [g2] : Contact paul92@example.com
ubuntu-kernel
Ubuntu IRC