[12:02] interesting [12:02] do you have a /proc/ide ? [12:02] yes, with "drivers ide0 hda ide1 hdc" in it [12:02] *blink* [12:03] agreed :-P [12:04] so you have /proc/ide/hda but not /sys/block/hda ? [12:04] how about /sys/block/hdc ? [12:04] /sys/block has only ram[0-15] [12:05] right [12:05] cd /sys/devices/*/*/ide0 [12:05] pwd [12:05] what does that say? [12:07] cd: 10: can't cd to /sys/devices/*/*/ide0 [12:07] sweet [12:07] uh [12:07] find /sys -name ide0 [12:07] I guess you don't have find though [12:08] indeed :-) [12:08] look for /sys/devices/*/ide0 */*/ide0 */*/*/ide0 etc. [12:08] (don't have it) [12:08] /sys/devices/ide0 [12:09] top-level like that?! [12:09] yepp :-) [12:09] cd into that [12:09] and do an ls for me [12:09] uevent power 0.0 [12:10] ok ls -l 0.0/bus [12:11] lrwxrwxrwx 1 0 0 0 0.0/bus -> ../../../bus/ide [12:11] ls 0.0 [12:11] uevent power bus [12:11] ok, try echo "" > /sys/devices/ide0/uevent [12:12] (why do you always echo "" rather than plain echo anyway? :-)) [12:12] (or udevplug /sys/devices/ide0/uevent) [12:12] Kamion: dunno [12:12] udevplug /sys/devices/ide0 I mean [12:12] but anyway [12:12] WRITE TO THAT FILE [12:12] [12:13] I think /dev/ttya[0-2] came out of that. [12:13] ksdgjs9gu8281 [12:13] or rather, they are the last ones ;-) [12:13] heh [12:14] you still don't have /sys/block/hda ? [12:14] nope [12:14] :-P [12:14] try udevplug /sys/bus/ide/0.0 [12:14] no change [12:15] meh [12:15] well, you haven't got an IDE controller [12:15] apparently [12:15] I can prove I have it by modprobe ide-disk ;-) [12:15] and so can ogra on his beauty ;-) [12:16] what kind of machine do you and ogra have in common? [12:16] ogra: amd64, no? [12:16] amd64 laptop here [12:16] SATA ? [12:16] http://www.magicalforest.se/darkelf [12:16] nope, PATA-100 [12:16] ok [12:17] try udevplug -Bpci [12:17] see if that makes /sys/block/hda [12:17] nope [12:17] udevplug [12:17] (without any arguments) ? [12:18] udevd-event[17175] : run_program: exec of program `/sbin/grepmap` failed [12:18] hence why I said that was missing :-P [12:19] yeah, that's just an annoying bitch I'm going to get rid of at some point [12:19] :-) [12:19] any /sys/block/hda though? [12:19] nope :-P [12:19] ok [12:19] well that means you have nothing on your system that claims to be an IDE controller [12:19] iz kernel bug [12:20] is ide-generic loaded? [12:20] where can I check? :-) [12:20] lsmod not found :-P [12:20] grep generic /proc/modules [12:21] ide-generic and ide-core is loaded, yes :-) [12:22] fwiw: ACPI registers the ide-bus in init-premount. [12:22] ide-disk then finds hda [12:23] ACPI? [12:23] yes [12:23] why is that "registering" the disk? [12:23] that just loads fan and thermal [12:23] ...] ACPI: bus type ide registered [12:24] you have nothing that says you need to load ide-disk [12:25] ie. the kernel hasn't found any ide devices [12:25] but it claims to have, as there's things in /proc/ide [12:25] which driver is it? [12:26] (it'll be one of the things hanging on to ide-core) [12:26] via82cxxx is memory provides [12:26] is that loaded? [12:27] nope [12:27] ah, interesting [12:27] modprobe -r ide-generic [12:27] then modprobe via82cxxx [12:27] then modprobe ide-generic again [12:28] yes? :-) [12:28] did that do anything? [12:29] said averything IDE was brought up (the usual kernelmessages) [12:29] did you get a /dev/hda ? [12:29] but no /dev/hda* or anything :-P [12:29] /sys/block/hda ? [12:29] nope [12:29] hmm [12:29] it could be buggered up by loading ide-generic first [12:30] that does evil things to the kernel [12:30] but you got a lot of the IDE things by loading the via82cxxx module? [12:31] not lots, that ACPI registered the bus.. [12:31] if I load ide-generic I get lots [12:31] right [12:31] ok [12:31] grep 1106 /sys/bus/pci/devices/*/vendor [12:32] 12 lines :-) [12:32] right [12:33] look at the /device files for each of them [12:33] they'll each have 4-digit numbers/letters [12:33] could you type them each here [12:34] shouldn't I be able to find out which one it is by grepping? :-) [12:35] no, clearly you have one that isn't registered [12:35] so I want the ids so I can google for them [12:35] hehe [12:37] 3177 [12:37] 0571 [12:38] 3059 [12:38] 3068 [12:38] any hit yet? :-) [12:38] carry on [12:39] 3065 [12:39] 3044 [12:40] b188 [12:40] 3188 [12:40] 3038 [12:42] same on all 00:10.*, so USB I guess [12:42] ok [12:42] could you note down the sysfs path to the one that's 0571 [12:42] then once done, reboot and put break=top onto the kernel command-line [12:42] so you're given a shell in the initramfs, rather than it failing [12:43] /sys/bus/pci/devices/0000:00:11.1/device [12:43] k [12:43] so reboot, with break=top, so we're in a fresh shell with no modules loaded [12:44] ey! you are reading my notes-to-self :-P [12:44] hmm? [12:44] oki, I'm there. [12:44] right [12:44] you told me to take a note ;-) [12:45] if you're on a laptop ... modprobe fan and modprobe thermal now [12:45] hehe, done [12:45] run UDEV_LOG=info /sbin/udevd --daemon [12:46] done [12:46] ok, now can you verify a few things for me, if not true, can you say what you see [12:46] /sys/bus/ide/devices is either empty or non-existant [12:46] grep via82cxxx /proc/modules shows nothing [12:47] /sys/bus/pci/devices/0000:00:11.1/vendor is 1106 [12:47] /sys/bus/pci/devices/0000:00:11.1/device is 0571 [12:48] all true [12:48] /sys/bus/pci/devices/0000:00:11.1/class is 0x010000 [12:48] not true [12:48] what is it? [12:48] 01018a [12:48] with or without an 0x on the front? [12:49] 0x01018a :-) [12:49] right, that's quite important :p [12:49] hehe, oki :-). all of them has that if not said otherwise ,-) [12:49] /sys/bus/pci/devices/0000:00:11.1/modalias should begin pci:v00001106d00000571sd... yes? [12:49] yeah, that's ok, just checking on that one in particular [12:50] also does it end bc01sc01i8a ? [12:50] not sd, sv [12:51] right, sorry, typo [12:51] sd00002032bc01sc01i8a [12:51] cool [12:51] now, /sys/block/hda should not exist [12:51] also /sys/devices/ide0 should not exist [12:51] and /proc/ide should not exist [12:51] are all those true? [12:52] yes indeed [12:52] right [12:52] udevplug -Bpci -Iclass=0x010[01] * [12:52] that should do a bunch of stuff on your screen, any of it interesting? [12:53] it didn't :-P [12:53] did nothing? [12:53] did nothing... [12:53] not even a grepmap bitch? [12:54] not even the bitch :-) [12:54] grep via82cxxx /proc/modules still shows nothing ? [12:54] cat /proc/modules: unix thermal processor fan [12:55] right [12:55] udevd is running? (ps ax) [12:55] yepp [12:55] udevplug /bus/pci/devices/0000:00:11.1 [12:55] does that do anything? [12:56] you forgot /sys, right? [12:56] doesn't matter, is optional [12:57] did nothing [12:57] how about just [12:57] echo > /sys/bus/pci/devices/0000:00:11.1/uevent [12:58] udevd-event output :-) [12:58] any of it interesting? [12:58] Keybuk ; Dude. You updated linux-meta while powerpc was still fucked? [12:59] infinity: yes, mdz said to :) [12:59] lol [12:59] /sbin/modprobe -Q pci:v.... [12:59] Nafallo: see, now that is interesting [12:59] do you now have any of /sys/block/hda, /sys/devices/ide0, /proc/ide/hda/media, /dev/hda ? [01:00] /sbin/modprobe (stderr) and the usage note :-P [01:00] huh why usage note? [01:00] is the line after that one... [01:00] so status 1 on modprobe... [01:00] uh [01:00] /sbin/modprobe -Q fan [01:00] ^ what does that do? [01:01] Keybuk : Ahh, yeah, just read backscroll. [01:01] usage message.. [01:01] -q maybe? [01:01] no, definitely -Q [01:01] so, could you do something for me [01:01] modprobe ide-disk [01:01] mount /dev/hda1 (or whatever your root/var is) /root [01:02] ls /dev still shows console and null only [01:03] *giggle* [01:03] OH I SEE THE PROBLEM [01:03] module-init-tools FTBFS [01:03] eeh? :-P [01:04] bloody patch systems === Nafallo breathes in [01:05] ...and out [01:06] ok [01:06] soooo, here's how to boot your machine [01:06] boot with break=premount [01:07] . conf/initramfs.conf [01:07] . scripts/functions [01:07] scripts/init-premount/acpid [01:07] udevd --daemon [01:07] udevplug /class/mem /class/misc /class/tty /class/vc /block [01:08] modprobe via82cxxx [01:08] modprobe ide-disk [01:08] modprobe ide-generic [01:08] (this should get you /dev/hda*) [01:08] udevplug -W [01:08] mountroot [01:08] run_scripts scripts/init-bottom [01:09] exec run-init /root $init "$@" /root/dev/console [01:09] -- [01:09] mountroot not found :-P [01:10] did you do the ". scripts/functions" bit? [01:10] Keybuk : Shall I fix module-init-tools while you're helping Nafallo get unfucked? [01:10] oh [01:10] sorry [01:11] . scripts/$BOOT [01:11] mountroot [01:11] infinity: already uploaded [01:11] Ahh, cool. [01:13] :-) [01:13] thanx :-) [01:13] booted? [01:13] yepp [01:13] and had more fun than ever on the way :-) [01:13] right [01:13] NOW BEFORE YOU GO [01:13] http://people.ubuntu.com/~scott/module-init-tools_3.2.1-0ubuntu3_i386.deb [01:13] actually [01:13] that's the wrong arch for you isn't it [01:13] uh [01:13] hehe, it is :-) [01:14] http://people.ubuntu.com/~scott/module-init-tools_3.2.1-0ubuntu3.diff.gz [01:14] http://people.ubuntu.com/~scott/module-init-tools_3.2.1-0ubuntu3.dsc [01:14] http://people.ubuntu.com/~scott/module-init-tools_3.2.1.orig.tar.gz [01:14] grab those three down, dpkg-source -x, dpkg-buildpackage -rfakeroot -b -uc -us, install module-init-tools [01:15] then check that "/sbin/modprobe -Q fan" does NOT give you a usage error :p [01:15] hmm, where is my network? ;-) [01:15] ifup [01:15] that's a known problem [01:15] it's in the release notes [01:17] I thought network-manager would take care of that ;-) [01:17] maybe [01:18] either way, it's on my list todo, just a few items down [01:18] just shout if you need testing :-) [01:18] let's first get you booting without error :p [01:19] got that built yet? [01:20] just wgeted and gave it to pbuilder :-) [01:28] oki, rebooting :-) [01:30] hmm, same error... [01:30] I don't have to run update-initramfs manually or something? [01:31] I actually just meant that you should run /sbin/modprobe before rebooting [01:31] but yes, you would need to run update-initramfs [01:35] I thought packages would do that these days ;-) [01:35] anyway, booted via the long command method again ;-) [01:36] no usage error :-) [01:37] sudo update-initramfs -u and then reboot again :-) [01:39] wow! "Mounting root file system ok" [01:39] :-) [01:39] thanx Keybuk! I'll post fresh bootcharts shortly :-) [01:40] even network works now ;-) [01:41] yay! my battery works :-) [01:44] http://www.magicalforest.se/~nafallo/bootchart/dapper-20051201-3.png === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-boot === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-boot === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-boot === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-boot === jbailey_ [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-boot === fabbione [n=fabbione@cerberus.fabbione.net] has joined #ubuntu-boot [07:36] guys can we have a FEW WORDS? [07:37] infinity: this upgrade is the disaster [07:37] RAID and network are gone [07:38] infinity: nvidia is broken on amd64 [07:38] + we load some fb modules that conflicts heavily with nvidia [07:38] removing the fb modules makes no good [07:38] nvidia either crashes or it manages to start X but it kills console [07:42] i think bootchart it's taking ages to release to console [07:43] but that's not a big deal [07:44] grepmap seems to be broken too === fabbione [n=fabbione@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-boot [08:09] fabbione : Hrm. nvidia works for me on amd64 (both legacy and current), but I tested it before the new udev and stuff when in. [08:10] yes, the problem seems to be either usplash or initramfs that are loading too many fb modules [08:10] fabbione : I'll have to test again after I upgrade evrything, but more concrete stuff than "it doesn't work" would be helpful, I think. [08:10] (And I'm using usplash with vga16fb on that machine, ie: a default setup) === pitti [n=pitti@ubuntu/member/pitti] has joined #ubuntu-boot [08:10] for what i can see other than the fb modules problems, nvidia kills switching to console [08:11] and it kills the machine if loading it directly without the fb modules [08:11] it's kind of a mess that will need more debugging [08:11] Fun. What kind of card do you have? [08:11] I've only been able to test on my 6800GT. [08:11] 0000:00:0e.0 VGA compatible controller: nVidia Corporation NV17GL [Quadro4 200/400 NVS] (rev a3) [08:11] 0000:01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4600] (rev a3) [08:11] it has 2 cards [08:12] So, if you boot with "nosplash", everything's okay?... [08:13] Or it dies in different ways? [08:13] (And have you tried with -legacy?... While your cards don't technically need it, they are older, so are more likely to run afoul of bugs in the new drivers, which are being aimed at 6/7 series stuff) [08:14] if i boot with nosplash the machine freezes [08:15] no, i didn't try -legacy yet [08:15] Er,, not sure if it's "nosplash", or just removing "splash" from the command line. Probably the latter, actually. [08:16] yeah i did try the recovery mode [08:16] and usplash was not loaded [08:16] it might as well be a problem with the sequence in which modules are loaded [08:16] because unloading fb stuff and loading nvidia works [08:16] so it's kind of weird [08:17] Very fun. I'll test again later tonight after a full upgrade. [08:17] ok [08:18] I fear it may be specific to your setup, though. So if I can't reproduce it at all, I'll whine at you to help. [08:20] yeah of course [08:20] i would like at least to get RAID/network back first [08:20] because they are truely annoying to start manually at each boot [08:20] You did upgrade everything, right? [08:21] yeps [08:21] Well, damn. :) [08:21] Blame keybuk. [08:22] heheh [08:22] infinity: do you plan a php5 upload soon? [08:23] there is the libsnmp5 -> 9 transition [08:23] it's the only pkg in main left [08:23] i just did hplip [08:31] Yeah, it's happening soon for other reasons. [08:32] ok === pitti [n=pitti@ubuntu/member/pitti] has joined #ubuntu-boot [09:36] ARGH. [09:36] fabbione : [09:42] ? [09:44] fabbione : Are you getting some nvidia-specific framebuffer module loaded? [09:44] fabbione : After upgrading everything and rebooting, I've noticed that something is now loading radeonfb magically for me, which is very clearly a bug. [09:44] If that's happening for you (but with the nv equivalent), that's the real problem. And I'm pretty sure it's the new udev's fault. [09:46] yes it is happening for me to [09:47] it loads radeon and nvidia fb [09:47] Both? [09:47] You have an ATI in there too? [09:47] Or is it doing something even more wrong than wrong? [09:47] nope [09:47] no ati on this box [09:47] sorry i meant riva [09:48] Oh, phew. [09:48] Kay. [09:48] Still very wrong, but at least that one makes sense. :) [09:48] [ 235.360791] NVRM: The NVIDIA probe routine was not called for 2 device(s). [09:48] [ 235.360796] NVRM: This can occur when a driver such as rivafb or rivatv was [09:48] [ 235.360798] NVRM: loaded and obtained ownership of the NVIDIA device(s). [09:48] [ 235.360802] NVRM: Try unloading the rivafb (and/or the rivatv) kernel module [09:48] [ 235.360804] NVRM: (or reconfigure your kernel without rivafb support), then [09:48] [ 235.360805] NVRM: try loading the NVIDIA kernel module again. [09:48] [ 235.362873] NVRM: No NVIDIA graphics adapter probed! [09:48] this one repeated several times [09:48] Yeahp. [09:48] it clearly goes away as soon as i rmmod riva [09:49] I'm getting the same here with conflicts between radeonfb and fglrx. Which, of course, shouldn't be happening, because radeonfb and rivafb shouldn't be autoloaded. [09:49] I'll be sure to yell at keybuk when he returns. [09:49] ehehehe [09:50] For now, you could blacklist rivafb, but having framebuffers hot/coldplugged at all is just sick and wrong, given that most of them are biuggy as hell. [09:51] i argee [09:51] agree [09:51] and i can wait for Keybuck to fix [09:51] i am not going to reboot this machine anytime soon anyway [09:54] Kamion: I'm going to waste a little time today trying to get our custom widget stuff upstream as well as our kbd-chooser changes. Ok? === jbailey__ [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-boot === pitti [n=pitti@195.227.105.180] has joined #ubuntu-boot [11:12] hmmm [11:13] Kamion: the pvremove -ffy solution doesn't solve all the problem :/ [11:13] i need to do a clean lvm removal [11:15] actually [11:15] no [11:15] i can be WAYYYY more evil :) [11:20] Mithrandir: cool, thanks [11:21] fabbione: ok ... [11:23] fabbione: I'm going to do a partman-auto-lvm upload to Debian in a moment; you'll need to merge that or your world will stop working [11:24] fabbione: oh, uh, you've been doing lots of stuff too, hmm [11:25] I guess it's not safe to upload at the moment [11:25] fabbione: if you want udev stuff to keep working with the new installer world order, merge r32609 from d-i svn; if you don't care, feel free to wait :) [11:26] Kamion: all the changes are the same we have in ubuntu [11:26] and all tested [11:26] if you want to upload pal you need to upload partman-auto too [11:27] Kamion: if you are talking about the udev bits, it's no problem... i can merge them easily [11:27] it's just 2 lines [11:28] my head is exploding === fabbione takes a break === Keybuk [n=scott@descent.netsplit.com] has joined #ubuntu-boot [11:33] Hi Keybuk [11:33] happy mailman day [11:33] Keybuk: I have some juicy udev bugs to talk about, when you have a minute? [11:34] sure, give me a few minutes to get my eyes open [11:34] and some coffee? :) [11:37] yes that too [11:38] fabbione: right, it's just to call update-dev [11:38] the old udevstart/udevsynthesize calls in p-a-l and elsewhere (apart from update-dev itself) will go away soon [11:55] is anyone doing new linux-meta for the new ABI? [11:55] udevsynthesize is nice for < 2.6.15 [11:56] makx: yes that's why they'll stay in update-dev [11:56] please, I know what I'm doing :-) [11:56] well, sometimes [11:56] np was just a remark, not looked in an updeate-dev yet- [11:57] Kamion: no, because we need new LRM for the new ABI [11:58] oh it's in.. [11:59] binaries aren't in yt [11:59] ah, new [12:00] ok, I'll process the new binaries [12:02] oh, god, no I won't, newing l-r-m gives me a vicious headache, I'll wait for elmo [12:05] whoa, rebooting just after installing new udev is indeed ultra-messy [12:05] d-i reboot, or ordinary reboot? [12:05] ordinary reboot [12:05] the bazillion udevsend errors scrolling down the console [12:05] Keybuk: check today's log for this chan [12:06] i also have several issues [12:06] hmm, no /dev/sda1 here ... [12:06] udevsend errors? [12:06] there's no such thing as udevsend [12:06] (it's not used) [12:06] raid/network and other stuff are clearly no go [12:06] my machine begs to differ [12:07] I probably have udevsend in /proc/sys/kernel/hotplug [12:07] s/have/had/ [12:07] hunger mentioned the same thing on #ubuntu-devel [12:07] that should get cleared in initramfs [12:08] unless something else is putting it back, of course [12:08] it's *before* reboot [12:09] as in, just upgraded from breezy-ish udev to current, then went to reboot [12:09] did that update your initramfs? [12:10] makx: yes, and it's totally irrelevant because the errors were BEFORE REBOOT so the new initramfs hadn't been started yet [12:10] oh [12:10] yeah [12:10] that'd go boom [12:10] ok, anyone fancy walking me through figuring out why I'm not getting /dev/sda1 in the new initramfs? SATA [12:11] could be that no modules are being loaded [12:11] udevplug puts it in [12:11] the easiest way to do it is to boot with break=mount [12:11] see if you have /dev/sda1 [12:11] if not, try udevplug -Bpci [12:11] then see if you have /dev/sda1 [12:12] btw nice "break=foo" patch Keybuk. :) [12:13] Keybuk: I don't even get a shell - I get "Spawning shell within the initramfs" and then a blinking cursor [12:13] huh? weird [12:15] maybe you have to wait for usplash to die or something [12:16] oh, the shell is in tty8 [12:16] that's helpful, not [12:17] no /dev/sda1 to start with, but udevplug -Bpci creates it [12:18] ok, excellent [12:18] is there a /sys/block/sda1/device symlink? [12:18] it might be /sys/block/sda/sda1/device [12:18] or /sys/block/sda/device [12:19] /sys/block/sda/device is there [12:19] ok [12:19] readlink/ls -l that and it should point to a pci device [12:19] cd into that (you can just cd /sys/block/sda/device) and pwd to make sure it's the right device [12:19] then cat vendor device class [12:20] and give me those three numbers :) [12:20] /sys/devices/pci0000:00/0000:00:0f.0/host0/target0:0:0/0:0:0:0 [12:20] vendor says ATA, device and class are missing [12:21] oh, interesting [12:21] try in ../../.. [12:21] 0x1106 [12:21] 0x3149 [12:21] 0x010400 [12:22] aha! [12:22] PCI_CLASS_STORAGE_RAID :) [12:22] le huh? [12:22] nobody told me it was RAID :) [12:22] not PCI_CLASS_STORAGE_SCSI [12:22] rightio [12:23] can you file a bug saying something like "load all storage controllers in initramfs, not just IDE/SCSI ones" [12:23] ok [12:23] you can boot that machine now with: [12:23] . conf/initramfs.conf [12:23] . scripts/functions [12:23] . scripts/$BOOT [12:23] mountroot [12:23] run_scripts scripts/init-bottom [12:24] exec run-init /root $init "$@" /root/dev/console [12:26] #20339 [12:26] boots fine now, thanks === pitti_ [n=pitti@195.227.105.180] has joined #ubuntu-boot [12:38] l [12:54] Kamion: new p-a-l uploaded [12:54] with the udev crack changed [12:56] ta [01:01] Keybuk : Hey, has anyone yelled at you about framebuffers, yet? === fabbione joins infinity on the crusade against fbs [01:02] Keybuk : I can only assume this is the new udev at fault, but it appears to be hot/cold-plugging framebuffers, based on installed hardware, so all ATI users get radeonfb loaded, nv users get rivafb, etc. THis is pretty horribly broken. [01:02] Keybuk : Since most of these framebuffers are buggy, break suspend/resume, and break their X driver counterparts. [01:04] it's in the release notes :) [01:04] (which I've yet to send, but still) [01:04] yes, I know framebuffer devices are loaded [01:04] I also have a bug assigned to me saying we should load framebuffer devices [01:04] I'm also aware that we might not want to [01:05] basically they need blacklisting [01:05] Keybuk: you are perfectly convinced you don't want to load them [01:05] and I'm not sure the elegant way to do that [01:05] it breaks MY workstation [01:05] badly === fabbione modprobes godfather.ko [01:05] Keybuk: or i will have to make you an offer you can't refuse === fabbione rmmods godfather [01:06] Keybuk : Was the bug filed by anyone with clue, or just someone who wants whizbang features? [01:07] Keybuk : Bottom line is that most framebuffers break just about everything else we do. [01:07] *nods* [01:07] soo... how do we blacklist them? [01:07] fabbione: hch needs a test for sbus sysfs debian -> #341522 [01:07] do we maintain a byhand list of framebuffer drivers? [01:07] Keybuk : why were they not being loaded before, but are now? That might be a good place to start. [01:07] there was a skip in the old hotplug shell code [01:08] And can we not replicate that behaviour on the new world order? [01:09] I'd like to do it with a blacklist file now [01:09] makx: i don't run debian on my sparc. [01:09] can't test [01:09] But we blacklist based on module name, not subsystem. Much more of a pain in the ass to maintain. [01:09] fabbione: he'll send you a kernel patch [01:09] Or can we blacklist in more clever ways? [01:10] Kamion : I realise you don't want to touch lrm NEW cause LRM is icky and makes your head hurt, but can you NEW the ia64 kernel binaries, so LRM can build there? :) [01:10] makx: still.. can't test.. my sparc is buildd.. not a test machine [01:11] rumout has it that we can do something like: [01:11] makx: plus he perfectly knows how to find me :) [01:11] fabbione: ok hehe trave11er will do [01:11] install pci:v*d*sv*sd*bc03*sc*i* /bin/true [01:11] infinity: (it's specifically icky because lisa can't handle l-r-m directly due to the d-i bits.) [01:11] that's pretty ugly though [01:12] we could also do that with SUBSYSTEM=="pci", SYSFS{class}=="0x03*", GOTO="modprobe_end" [01:12] Keybuk : I'd prefer to avoid line nois ein config files. [01:12] Keybuk : Though, something that ugly is unlikely to be touched by users, which may be a win.. [01:12] infinity: doing now [01:12] another option is to generate /etc/modprobe.d/display_class automatically in kernel postinst [01:12] UH UH [01:12] go udev! === fabbione sighs [01:13] no actually.. that would be initramfs too [01:14] Keybuk : Is there any reason to not just patch things to skip that particular class, other than the off chance that some user, somewhere, might really want to coldplug his framebuffers without using /etc/modules? [01:14] infinity: patch what? :) [01:15] Whatever enumerates incoming *plug events and decides to call modprobe? [01:15] I'm not the one who packaged this, I don't pretend to know the code. :) [01:15] well, the kernel generates uevents [01:15] we could patch the kernel to not generate events for display devices [01:15] Right, then? [01:15] What catches the events?... udev? [01:16] but it's slightly less intrusive to just not build the framebuffer devices in the first place [01:16] And then udev calls modprobe if it thinks it should? [01:16] yes, udev catches the events, looks them up in sysfs and processes it [01:16] we could add a udev rule to skip modprobe for display devices [01:16] Right, so udev should be the one skipping the events, if it knows the device class. [01:16] udev calls modprobe [01:16] with a device alias [01:16] modprobe can blacklist devices from matching a particular alias [01:17] (like we do for things like eepro100 and stuff) [01:17] infinity: Accepted 1 package set, 146 MB. [01:17] Yeah, but that percludes someone calling modprobe manually. [01:17] no, it doesn't [01:17] We just don't want udev automagically doing it, we don't want to stop users from doing it. [01:17] modprobe only applies it's blacklists to alias expansion [01:17] modprobe eepro100 still works [01:17] (unless you use -b, right?) [01:17] modprobe pci:blahblahforaneepro100 is what gets blacklisted [01:17] right [01:18] modprobe -b eepro100 is "load eepro100 only if it's not blacklisted" [01:18] ... [01:18] incidentally, please document -b in the man page, kthxbye :) [01:18] Well, I leave it in your hand to implement where/how you think works best. [01:18] I'd rather we did this at the modprobe level, because it's the least surprising way [01:18] and it's consistent with other things where we've decided not to load modules [01:18] I just want it to work, and I don't want anything that requires maintaining manual lists. [01:18] right [01:19] (Or something so user-obvious "Oh, look this blacklists framebuffers, I don't want that!" that users will delete it, not know how to get it back, and file tons of bugs cause X broke) [01:19] do you have anything against a list updated in a postinst? [01:19] Yes, I'm evil. [01:19] infinity: if users shoot themselves in the foot, they will shoot themselves [01:19] either way this will be in a conffile [01:19] I don't think hotplugging framebuffers is ever "right", so I'd really just not allow it. [01:20] Kamion : Thanks, BTW. [01:20] np [01:22] of course, it's impossible to accurately identify framebuffer drivers *shrug* [01:23] Then how did hotplug manage? [01:23] Rough guessing that was mostly true? [01:24] hotplug did it by device [01:24] All video devices? [01:25] That would work for us, since the only other things that vaguely relate to video devices are slave drivers to X drivers, which load (or are supposed to) when X loads. [01:25] right, that was always the drawback [01:25] there were various hotplug bugs where it didn't load some other driver [01:25] like capture cards, etc. [01:25] all-in-one cards didn't work at all without manual driver loading [01:25] Keybuk: udev-udeb being hard to type> I feel your pain [01:26] I can only type "udev" accurately one time in three [01:27] the udeb was missing lots of files because they were in debian/udeb-udev and debian/udev-udev and friends [01:29] heh === ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-boot [01:35] hi === crimsun [i=crimsun@pdpc/supporter/silver/crimsun] has joined #ubuntu-boot [01:36] ok [01:36] so let's first get your system to a useful point to play [01:36] your problem is that "your root filesystem is on a network device, and no network driver is loaded", is that correct? [01:36] i tried to replace the line that was there, as well as just ading your line [01:36] yup [01:36] ok, good [01:36] put that script back how it was, just the -Bpci -Iclass=0x01* line [01:36] update-initramfs [01:36] it loads the same set of modules in both cases === lbm [n=lbm@cpe.atm4-0-1301006.0x50a0824e.vgnxx6.customer.tele.dk] has joined #ubuntu-boot [01:37] then reboot, and add break=mount to the kernel command-line (remove splash for sanity) [01:37] Keybuk: Is this no-nic-at-startup troubleshooting, or a specific LTSP case? [01:38] ok, well, the installer boots with 2.6.15-6, sort of [01:38] I have to ifup at startup, but I think you said that's expected. [01:38] jbailey: we forgot about initramfs probing network modulesentirely when we wrote udev-roadmap [01:38] something's wrong with framebuffer bringup though [01:38] jbailey, it is ltsp... but might also affect others [01:38] Kamion: "wrong with" ? ... you mean that framebuffer drivers are brought up? [01:38] ogra: are we at a "Spawning shell in the initramfs" prompt yet? [01:39] Keybuk: er no, the installer relies on a framebuffer ... [01:39] Keybuk: Mmm, yeah. Althouhg it seems solvable in that the nfs initramfs class can have the nic probing and the klibc dhcp client call can be a udev rule at that point. [01:39] Kamion: oh, now that makes things more interesting wrt blacklists [01:39] Keybuk: So I don't think it's unsolvable. [01:39] Keybuk, wait, takes a second ... [01:39] Keybuk: nope, the installer already modprobes them itself [01:39] oh ok === Nafallo [n=nafallo@ubuntu/member/nafallo] has joined #ubuntu-boot [01:39] Keybuk: just leave it to do its job and it will be fine :) [01:39] (well, ish) [01:39] Keybuk: Then we just do the same event wait for the root filesystem to appear. [01:40] Kamion : Are you sure you're not getting fb conflicts? [01:40] Keybuk, ok, there [01:40] ogra: good [01:40] now what network driver are you looking for? [01:40] note that i have to regenrate the tftpboot stuff afterwards [01:40] infinity: pretty sure, yes. symptoms are funny squares in localechooser rather than UTF-8 characters; I'm investigating [01:40] Kamion : I get vga16fb/vesafb (whichever one usplash decides I wanted) loaded, then udev goes and loads a second later. [01:40] 8139too [01:40] infinity: no usplash in the installer [01:40] ok, grep 8139 /proc/modules and check it's not in there [01:40] but in fact all pci drivers [01:41] Kamion : Right, but similar idea, since the installer loads an FB, then you fire off udev... Right? [01:41] Kamion : (Or perhaps vice versa, but either way, you may end up with two loaded) [01:41] infinity: well there's only one entry in /proc/fb afterwards, so I don't think it's that [01:41] nope, not there [01:41] ogra: good [01:41] ogra: udevplug -Bpci -Iclass=0x02* [01:41] Kamion : Right, then I'll shut up. [01:42] ogra: then look to see whether the module was loaded [01:42] udev *might* not be helping here, but I can't say for sure yet [01:42] yup, loads [01:42] "yup, loads" ? loads of what? [01:42] the netcard module... 8139too [01:42] right [01:42] s/loads/it loads/ [01:43] :) [01:43] . conf/initramfs.conf [01:43] . scripts/modules [01:43] . scripts/$BOOT [01:43] mountroot [01:43] run_scripts scripts/init-bottom [01:43] exec run-init /root $init "$@" /root/dev/console [01:43] -- [01:43] oh [01:43] cant open scripts/modules [01:44] uh [01:44] sorry [01:44] scripts/functions [01:44] ah [01:44] also, just for my sanity, could you cat /sys/class/net/eth0/device/class [01:45] yup, booting [01:46] oh, err ... in busybox ? [01:46] nah, when the system is up is fine [01:47] 0x020000 [01:47] okies [01:47] thank you for your bug report. [01:47] so the udevplug needs to run in a later script, right ? [01:48] just needs udevplug running over network controllers somewhere [01:48] it was missed out [01:48] ah, fine [01:48] because neither jbailey or I remembered it when we wrote udev-roadmap [01:48] heh [01:48] ok [01:48] thanks for the prompt help :) [01:49] Keybuk: the installer-startup script is basically horribly broken - working on it now [01:49] Kamion: ok. I cargo-culted it from the main startup script, but wasn't sure how much of the "deal with initramfs" crap would be needed [01:50] Keybuk: can you please tell me when you have some minutes to discuss about my morning's udev failure? [01:50] can we just use cp -af or something rather than the find | cpio thing? [01:50] we don't have cpio in busybox-udeb at the moment [01:50] Kamion: heh, I tend to use cpio because I trust it ... I always assume that things like busybox don't have cp -a [01:50] but yes, if the result is the same, we can [01:51] seems to be [01:51] pitti: yup, give me three minutes, and you're up next [01:56] pitti: right, tell me about your problems [01:57] Keybuk: ok, so this morning I wanted to update an udev rule for testing [01:57] so, naive as I am, I tried sudo /etc/init.d/udev restart [01:57] which didn't seem to reload the conffiles [01:57] force-reload didn't either [01:57] then I did the more brutal way of calling stop, then start [01:58] after which I found my /dev empty, my conffiles in /etc/udev purged, and /etc/udev filled with devices [01:58] and /etc/udev did not seem to be a mount point (that was still /tmp) [01:59] ok [01:59] I suspect that "mount -n -o bind /dev /etc/udev [01:59] " in the init script (and the following commands) caused that [01:59] a) udevd keeps an inotify watch on /etc/udev/rules, so you don't need to reload it [01:59] I removed /etc/udev/* and purged/reinstalled the packages to get my conffiles back [01:59] 2) reload/force-reload should send it a HUP [01:59] 3) ooooooops :p [01:59] well, all I can say it that I changed /etc/udev/hal.rules, and it was not reloaded [01:59] yes [01:59] well [02:00] see also [02:00] DON'T PUT SYMLINKS IN /etc/udev/rules.d [02:00] I've been telling people this for a week now [02:00] including yourself about a dozen times [02:00] bbbut... that's the official Debian way [02:00] yes, that might be what Debian do [02:00] but it's wrong [02:00] we don't share any common code with the Debian udev packaging [02:00] put the file itself in /etc/udev/rules.d please [02:00] seriously [02:00] these symlinks come from various other packages: hal, alsa-utils, etc. [02:00] udevd cannot spot them changing [02:00] and won't reload them [02:00] yes [02:00] we will fix them all [02:00] ok [02:00] alsa-utils is on my list [02:01] TBH, I didn't notice/remember the no symlinks policy [02:01] I'll fix hal [02:01] yeah [02:01] Keybuk: do you know the cause of the lost conffiles? or do you need more info? [02:01] the symlinks stuff in the first place is Marco being very odd [02:01] bind-mount /dev to /etc/udev seems odd to me [02:01] we will just put the files themselves in /etc/udev/rules.d [02:02] Keybuk: Post that to u-d-a perhaps so that it's recorded? [02:02] jbailey: yeah, I should do [02:02] it applies to Kamion's pcmciautils packages too [02:03] ok [02:03] so #1 is understood (you didn't put the file in the right directory) [02:03] yep [02:03] #2 is also understood (it uses lstat, and the symlink itself didn't change) [02:03] that means force-reload/restart is not necessary [02:04] right, reload/force-reload just sends a HUP ... it should have zero effect [02:04] I just put them in because I was being complete [02:04] restart does a refresh of /lib/udev/devices and udevplug [02:04] useful for a "I changed something/installed new modules/etc." hit [02:05] stop does actually stop udevd and umount /dev [02:05] that even seemed to have worked [02:05] since then mountpoint -q /dev failed [02:05] right [02:05] and I got my old /dev mounted to /etc/udev [02:05] it's the start on a running system without a /dev that failed [02:06] right? [02:06] yes [02:06] thanks for testing that code-path :) I hadn't yet [02:06] (there's a /dev in the ordinary start, as initramfs makes it) [02:06] I was a little surprised that /etc/udev was no tmpfs mount [02:06] it seemed to be real files [02:06] or the kernel hides bind / -o move mounts really well [02:07] it uses it as a temporary place to put the static /de [02:07] the theory goes: [02:07] 1) move static /dev to /etc/udev [02:07] 2) mount tmpfs on /dev [02:07] 3) make /dev/.static/dev [02:07] 4) move /etc/udev mount back to /dev/.static/dev [02:07] yes, I see the code [02:07] I don't see any obvious flaws [02:07] oh, wait [02:08] I had to kill the start init script [02:08] because it ran indefinitely [02:08] aha! [02:08] there's a missing -p [02:08] mkdir -m 0700 /dev/.static/dev will fail [02:08] aah [02:09] so that means it probably hanged at the last mount -o move command [02:09] and the second move fails for some reason [02:09] but shouldn't it just fail? [02:09] no, it meant it failed at the mkdir -- it's a -e script [02:09] hmmm [02:09] it hanged, it didn't fail [02:10] ok, could you try it again with sh -x and see where it hangs? [02:10] Keybuk: maybe, just to be sure, you can temporarily mount it to /etc/udev/newdev/ or so? [02:10] sure, I'll try [02:10] stopped [02:10] whoops [02:11] that'd involve a mkdir on a read-only filesystem [02:11] $ ls /dev [02:11] alsa-utils.rules hal.rules initctl pcmcia.rules rules.d udev.conf [02:11] *ahem* [02:11] lol [02:11] you may wish to reboot to get to a sane system [02:12] follow-the-lady with your filesystem [02:12] Keybuk: /dev was perfectly sane before /etc/init.d/udev stop [02:12] (I already rebooted after the previous mess and restaurationof my conffiles) [02:14] so WTH did stopping udev scribble /etc/udev* over my /dev directory? (it's not mounted any more, btw) [02:14] dunno [02:16] fixing that -p, and changing -o move to --move fixes it for me [02:16] I can stop/start happily [02:16] ok, I did that, will try after reboot [02:17] last thing: pcspkr is not loaded automatically any more [02:17] oh, now that's kinda interesting [02:17] will that get fixed kernel-wise, or should we put it into /etc/modules? [02:17] I did not get any IRC beeps any more :) [02:17] modinfo pcspkr [02:18] vermagic: 2.6.15-5-amd64-generic gcc-4.0 [02:18] , if you need that [02:18] any alias lines? [02:19] no [02:19] grep pcspkr /lib/modules/$(uname -r)/* [02:19] /lib/modules/2.6.15-5-amd64-generic/modules.dep:/lib/modules/2.6.15-5-amd64-generic/kernel/drivers/input/misc/pcspkr.ko: [02:19] ok [02:19] check that you have a "alias pnp:dPNP0800 pcspkr" line in /etc/modprobe.d/isapnp [02:20] I have [02:20] grep PNP0800 /sys/bus/pnp/devices/*/id [02:20] /sys/bus/pnp/devices/00:05/id:PNP0800 [02:20] (I loaded it manually, btw) [02:20] /lib/udev/pnp_modules /bus/pnp/devices/00:05 [02:21] it will probably look different without the module loaded [02:21] pnp:dPNP0800* [02:21] *giggle* [02:21] RAH [02:21] what's that "*" doing there? [02:21] thankyou for your bug report :) [02:22] my pleasure :) [02:22] any more? [02:22] #20342 is everything we need, plus a few rootskel changes [02:22] (for the installer) [02:22] Keybuk: just a question [02:22] Keybuk: hunger got thousands of /usr/lib/hal/hal.hotplug not found errors during boot [02:22] Keybuk: because /usr was not mounted, so the udev rule failed [02:22] Keybuk: is it legitime to add a test -x check to the rule? [02:22] pitti: yeah, we need to fix the hal stuff ... I think hal listens on a socket that can be passed uevents, is that right? [02:23] I think so, yes [02:23] yeah, so we'll change that to do RUN+="socket:/org/freedesktop/hal/uevent" or whatever it calls the socket [02:23] unix 2 [ ] DGRAM 13585 6047/hald @/var/run/hal/hotplug_socket2 [02:23] test -x won't help you ... udev isn't a shell, so doesn't have a test buildin :p [02:23] that one maybe? [02:24] pitti: no, that's a filesystem socket, you want the unix namespace socket [02:24] Keybuk: oh, but with PROGRAM= / RESULT== it will ceratinly work? [02:24] it'll look like @/org/... I think [02:24] pitti: how do you mean? [02:24] Kamion: installer may have been bitten by same bug as pitti [02:25] Keybuk: the PROGRAM/RESULT check if /usr/lib/hal/hal.hotplug is available, and RUN is only called with RESULT==0 [02:25] what would you put in PROGRAM? [02:25] bah, why is test in /usr/bin? [02:25] ok, let's forget that [02:25] pitti: :D [02:25] test is also not in the initramfs at all [02:26] well, we could abuse /bin/bash .. :) [02:26] hrm [02:26] /bin/bash is not in the initramfs at all [02:26] anyway [02:26] this is more complicated than I thought... [02:26] the socket is the right way [02:26] ok, I'll read about this [02:26] Keybuk: hmm? [02:27] ok, let's restore my static /dev first [02:27] Kamion: you don't want /dev/.static/dev in the installer? [02:27] pitti: in any case you'd need to fail if hal.hotplug isn't there, so that the event can be replayed later [02:27] Keybuk: nope [02:27] Kamion: does nothing call MAKEDEV (package postinst?) [02:27] Keybuk: nope [02:27] ok [02:27] easy then [02:27] Keybuk: package postinst => chroot /target [02:28] ~ # type MAKEDEV [02:28] MAKEDEV: not found [02:28] pitti: the real bug is probably that udevd does an OMG THE SKY IS FALLING! when it can't find a binary [02:28] it should be a muted warning rather than an error [02:28] yes, you'll get thousands of error messages [02:28] cf. grepmap in the initramfs [02:29] Kamion: will /dev ever be a mountpoint when the udev startup script is run? ie. can I just assume it's not, and make it? [02:30] Keybuk: hm, is "sudo netstat -avpx|grep hal" really the right command to watch out for the unix socket? [02:30] Keybuk: there is just one listening socket [02:30] unix 2 [ ACC ] STREAM HRT 13584 6047/hald @/tmp/hald-local/dbus-7awadoPF2s [02:31] HRT == LISTENING [02:31] hmm, it might be a floating patch [02:31] and that DGRAM one [02:31] Keybuk: please leave that out, I've made init-udev-devices do it [02:31] assume that it's already a correct mountpoint [02:31] we need to create some minimal stuff in /dev in order to bring busybox init up *anyway*, so this is correct [02:32] right [02:32] Keybuk: the exact directions I gave in the bug work :-) [02:32] so what should I do? just copy over /lib/udev/devices and start udev/udeplug ? [02:32] replace lines 15-24 with 'cp -af /lib/udev/devices/* /dev/' [02:32] yep [02:32] that's all the startup script needs to do [02:33] I've fixed the few lines of d-i that needed to be tweaked; uploads are either in or on their way [02:35] oh, I remember why I used cpio [02:35] cp bitches when special files already exist [02:35] not a problem in the installer [02:35] cp -af doesn't [02:35] I ran into that, because /dev/console was already there [02:36] but if it doesn't work, force it :) [02:36] cp -af does too here [02:36] must be a busybox thing [02:36] 'cos it really didn't :) === pitti [n=pitti@ubuntu/member/pitti] has joined #ubuntu-boot [02:38] Keybuk: confirmed, with the two init script fixes (-p and --move) it works fine [02:48] whoah [02:48] isn't it great when you read code and find undocumented features that will rock [02:48] udev appears to have ifrename built in [02:49] AND correctly switches the name over for future events [02:49] \o/ [02:49] MAKE IT WORK NOW. [02:49] SUBSYSTEM=="net", SYSFS{address}=="....", NAME="eth1" [02:49] SUBSYSTEM=="net", RUN+="ifup %k" [02:49] the %k in the second call will be eth1, not eth [02:51] Keybuk: #20340> heh, oops, I thought I had upgraded already [02:52] Kamion: how insane am I if I want to run the installer in valgrind and fix the bugz? === ..[topic/#ubuntu-boot:Keybuk] : known: fb drivers loaded, oss drivers loaded, no network plugging, pcmcia/hal/alsa rules not reloaded, mtab not updated, /dev/pts not mounted || pending: nfs root fails, sata root fails, pnp devices not loaded, init stop/start === ..[topic/#ubuntu-boot:Keybuk] : known: fb drivers loaded, oss drivers loaded, no network plugging, pcmcia/hal/alsa rules not reloaded, mtab not updated, /dev/pts not mounted || pending: nfs root fails, sata root fails, pnp devices not loaded, init stop/start || fixed: notify-reboot, vio_type segfault, no modules loaded [02:57] Keybuk: ok, hal binds to the NETLINK_KOBJECT_UEVENT netlink socket [02:57] what socket is that? [02:57] Keybuk: but I don't have the slightest idea how they work [02:57] that sounds rather like hal is listening to uevents itself [02:57] if you give me a few minutes to get this release out of the door, I'll look with you [02:57] oh, sure [02:58] sorry to bother you with it [02:58] lol, bother away === ..[topic/#ubuntu-boot:Keybuk] : known: fb drivers loaded, oss drivers loaded, no network plugging, pcmcia/hal/alsa rules not reloaded, mtab not updated, /dev/pts not mounted || pending: nfs root fails, sata root fails, pnp devices not loaded, init stop/start, grepmap bitching || fixed: notify-reboot, vio_type segfault, no modules loaded [03:01] lol, bug tracking in /topic [03:01] yup [03:01] easier than my head/whiteboard [03:03] Keybuk: ok, I still know the old-fashioned way of hal: hotplug calls /usr/lib/hal/hal.hotplug, which grabs the environment, and forms a mesage out of it and sends it to a unix socket [03:04] Keybuk: so what you want to do is to send the udev messages directly to that socket, right? [03:04] fixing the pcmciautils issue now === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-boot [03:10] pitti: right, there's in theory no reason udev itself can't send that socket [03:10] except possibly for the hal magic thing [03:10] the udev release notes talk about this though: [03:10] RUN+="socket:/org/freedesktop/hal/udev_event" [03:11] that *might* be still in a patch that's not applied upstream [03:11] or in CVS HEAD or something [03:11] Keybuk: I just wonder why it listens to the KOBJECT socket itself [03:12] I think it didn't work without the rule, but I'll try again [03:13] ok, no, it doesn't work [03:15] Keybuk: ok, that socket: thing doesn't work, that would just be too easy :) [03:17] http://lists.freedesktop.org/archives/hal/2005-November/003943.html [03:17] Keybuk: ok, what hal.hotplug does, is: it opens the AF_LOCAL SOCK_DGRAM socket /var/run/hal/hotplug_socket2 [03:17] ^ you'll be wanting that patch [03:18] ah, great === ..[topic/#ubuntu-boot:Kamion] : known: fb drivers loaded, oss drivers loaded, no network plugging, hal/alsa rules not reloaded, mtab not updated, /dev/pts not mounted || pending: nfs root fails, sata root fails, pnp devices not loaded, init stop/start, grepmap bitching || fixed: notify-reboot, vio_type segfault, no modules loaded, pcmcia rules not reloaded [03:18] (diff: pcmciautils fixed) [03:18] Keybuk: ok, I'll pull it from the upstream cvs [03:19] Keybuk: I'll also fix the rules.d thing; is 85-hal ok, priority-wise? [03:19] what does the rule contain? just that? [03:19] Keybuk: that, and the automatic unmounting [03:19] of ripped out devices [03:19] (which should be in the kernel, but oh well..) [03:19] 85-hal.rules [03:20] ok, great [03:22] 005-11-15 Kay Sievers [03:22] * hald/linux2/osspec.c: (hald_udev_data), (hald_helper_data), [03:22] (osspec_init): Listen to socket: /org/freedesktop/hal/udev_event [03:22] Udev will pass all data over this socket to HAL, if the following [03:22] rule is given: [03:22] RUN+="socket:/org/freedesktop/hal/udev_event" [03:22] The HAL hotplug helper /usr/sbin/hal.hotplug is no longer needed [03:22] and should be replaced by the direct udev connection which will [03:22] no longer fork a process for every event. [03:22] This is the preparation to reuse the persistent data udev collects [03:22] from the hardware, instead of querying it a second time with HAL. [03:22] If we reach this, drive_id/* and the hotplug helper will be removed [03:22] from HAL. [03:22] (from hal CVS changelog) [03:26] any objection to me turning on command editing, history, and tab completion in the initramfs busybox shell? [03:26] it would make life so much less painful [03:26] Kamion: What the size cost? [03:26] I can find out === pitti_ [n=pitti@195.227.105.180] has joined #ubuntu-boot [03:44] Kamion: does newer pcmciautils add -Qb to its "modprobe pcmcia" call? [03:44] (in the udev rules) === HiddenWolf [n=HiddenWo@136.229.dynamic.phpg.net] has joined #ubuntu-boot [03:47] no; should it? [03:47] yeah [03:47] otherwise "users can't blacklist pcmcia" [03:47] and you want the -Q to suppress automated bitching [03:48] Keybuk: oh, right, that was another thing I wanted to ask you - is /etc/hotplug/blacklist.d still supported? [03:48] Keybuk: how about pcmcia_core? [03:48] that's currently -q [03:51] Kamion: change to -Qb ... I included all the behaviour of -q in -Q [03:52] pitti: nothing in Ubuntu should place a file in there, therefore it's currently disabled, however before beta we will enable it for anything the users might have in there [03:52] alright, I'll -Q the bridge module loads as well [03:52] fixed in my tree [03:52] Kamion: two or three packages drop stuff in it; most important is alsa [03:52] pitti: libsane should provide an /etc/modprobe.d/libsane-blacklist which has "blacklist hpusbscsi" and "blacklist scanner" in it [03:53] alsa is on my todo list [03:53] pitti: s/Kamion/Keybuk/ :) [03:53] ah, great [03:53] I can change my nick to Keybun if it would make things easier [03:53] Kamion: oops, sorry :) [03:53] Kamibuk [03:54] -rwxr-xr-x 1 cjwatson cjwatson 910672 2005-12-01 14:29 old/busybox [03:54] -rwxr-xr-x 1 cjwatson cjwatson 918352 2005-12-01 14:33 new/busybox [03:54] we get completion for 8 kB? [03:54] jbailey: ^-- size cost (unstripped) of turning on editing/history/tab-completion [03:55] sweet [03:55] Kamion: No brainer. =) [03:55] oh, no, I think that is stripped [03:55] ok, I'll enable it [03:56] infinity: linux-doc-2.6.15 conflict/overwrites linux-doc-2.6.12 [03:59] sweeet - conffiles were transitioned, hal responds to the socket events [04:00] thanks Keybuk [04:00] Keybuk: I'll fix the rules.d symlink story for libgphoto2, too [04:05] right, while the buildds are building new udev and m-u-t, I'm gonna grab lunch === crimsun [i=crimsun@pdpc/supporter/silver/crimsun] has left #ubuntu-boot [] === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-boot [04:51] inifinity: do you have latest ubuntu initramfs-tools in bzr archive? [04:52] jbailey's latest pushed is 0.31. [04:53] makx: I think he's asleep atm. [04:54] aah ok, will reask tomorrow, thanks jbailey. :) [05:02] Keybuk: libgphoto2 conffiles fixed === ..[topic/#ubuntu-boot:pitti] : known: fb drivers loaded, oss drivers loaded, no network plugging, alsa rules not reloaded, mtab not updated, /dev/pts not mounted || pending: nfs root fails, sata root fails, Kepnp devices not loaded, init stop/start, grepmap bitching || fixed: notify-reboot, vio_type segfault, no modules loaded, hal/pcmcia rules not reloaded [05:03] (diff: hal rules are reloaded now) === ..[topic/#ubuntu-boot:Keybuk] : known: fb drivers loaded, oss drivers loaded, no network plugging, alsa rules not reloaded, mtab not updated, /dev/pts not mounted || fixed: notify-reboot, vio_type segfault, no modules loaded, hal/pcmcia rules not reloaded, nfs root fails, sata root fails, pnp devices not loaded, init stop/start, grepmap bitching [05:12] (diff: pending -> fixed) [05:13] All of it? [05:14] Nice! [05:14] yeah, all the pending stuff went into 0ubuntu5 [05:26] Keybuk: in 0.40ubuntu1 you mention Copy across modprobe blacklist, as well aliases, is this the same file? [05:28] /etc/modprobe.d/aliases [05:28] /etc/modprobe.d/blacklist [05:28] different files [05:29] ohh overseen, yes thanks! [05:30] debian but #337318 wanted to have all /etc/modprobe.d [05:30] s/but/bug/ [05:30] i've asked him for clarification. === lbm [n=lbm@x1-6-00-13-10-7a-d1-e4.k233.webspeed.dk] has joined #ubuntu-boot [05:30] it makes some amount of sense to copy the entire directory === pitti_ [n=pitti@195.227.105.180] has joined #ubuntu-boot [06:00] Keybuk, just to report back, my thin clients boot fine again [06:00] thanks for the quick fix :) [06:09] Keybuk, if you have an uploade of initramfs-tools pending, could you pretty please finally remove the sleep 3 from /usr/share/initramfs-tools/scripts/nfs ? [06:10] I don't have an upload pending, it's infinity's job now :p [06:10] ok, i'll poke him.... [06:11] thin clients stilltake over a minute for booting :( [06:13] yeah, lots of changes yet to come [06:16] ogra: Still takes is fine. [06:16] oh, i thought this was it already [06:16] ogra: TAkes a minute longer would suck. =) [06:16] i target 45 seconds .... but i am at 1:03~1:09 [06:17] ogra: Just upload it with the NFS fix. There's no reason to wait on a BML. [06:17] what were you before? [06:17] at least i just could boot without usplash timing out [06:17] with all bootscripts it was ~1:45 [06:17] with eliminating the bootscripts ~1:20 [06:17] so it's taking 40s less? [06:18] ok, still 10-15s less then [06:18] so i won about 15sec [06:18] good [06:18] that's about my expected win [06:18] next we move several bits to udev rules [06:18] sort out networking [06:18] and reorder rcS to eliminate the bugs [06:18] that might give us up to 10-15s more [06:18] that'd be enough for me :) [06:19] then fix readahead, hopefully another 10-15s there [06:19] i just had the impression you were already done [06:19] hmm, no? this was the FIRST upload :p [06:19] forget about readahead ... i cant use it [06:19] (wont gain much with 32-64 MB) === jbailey_ [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-boot === pitti [n=pitti@ubuntu/member/pitti] has left #ubuntu-boot [] === crimsun [i=crimsun@pdpc/supporter/silver/crimsun] has joined #ubuntu-boot [09:40] likewise [09:40] UDEV_LOG=info /sbin/udevd --daemon [09:40] :p [09:41] ok, got that [09:41] right, did it output things? [09:42] indeed, 3 lines (I'll have to by-hand) [09:42] ok [09:42] just that it output things [09:42] now following stuff will output various gubbins, you'll need to read the screens (use shift-pgup/dn) and look for anything suspicious [09:42] has_driver returning 1 isn't suspicious, that just means there's no driver loaded yet [09:42] modprobe returning 1 is suspicious [09:42] etc. [09:42] k [09:43] now, first let's just sanity check that you don't have a /dev/sda* , /sys/class/block/sda* and /sys/bus/scsi* ? [09:43] none of those [09:43] good, it's nice to make sure we're not in la-la land [09:44] now we'll run a few udevplug commands, these will dump a lot of udevd debugging information to the screen -- read it all and summarise for me anything suspicious [09:44] k [09:45] we'll also write some output to a file, cat that file and say what you see (feel free to just replace long number strings with *) [09:45] udevplug -Bide -Bscsi -Bi2o -Busb -Bieee1394 > 1.txt [09:45] uh [09:45] stick -v in there too :p [09:45] udevplug -v -Bide -Bscsi -Bi2o -Busb -Bieee1394 > 1.txt [09:47] no output (1.txt is a 0-byte) [09:47] exxxxcellent [09:48] ok, this is an easy one, don't worry about this, it just makes a bunch of stuff you'll need [09:48] (ie ignore the output) [09:48] udevplug -Cmem -Cmisc -Ctty -Cvc [09:48] then you may as well press enter lots so you can find your place [09:48] this one we care about [09:48] udevplug -v -b > 2.txt [09:49] in 2.txt you should only have /sys/block/ram* ... and nothing suspicious in the udevd dump [09:52] doesn't appear to be anything suspicious, lots of /block/ram* and /dev/ram* with their associated has_driver returning 1, presumably innocuous according to above [09:52] yeah [09:52] has_driver is just a "can we skip modprobe" thing [09:53] right [09:53] so we still have no /dev/sda*, /sys/block/sd*, /sys/bus/scsi* ? [09:53] correct [09:54] right [09:54] so now, in theory, we're in a sane state to probe for scsi controllers [09:54] now, I'm assuming it's a real scsi controller that we're looking for, yes? [09:54] SATA (IBM TP X41-2527) [09:54] right, SATA controller [09:54] ok, that makes things more fun [09:55] so let's try this: [09:55] udevplug -v -Bpci -Iclass=0x0[12] * > 3.txt [09:55] you'll get a lot of output from that, read it all carefully [09:55] I'm interested in anything modprobe does (you'll see module/* events) [09:55] and also the 3.txt contents [10:04] ok, as far back as the buffer permits, SCSI device sda is attached, a lots of scsi_id output (ID_VENDOR, ID_MODEL, etc.), lots of use of kernel name because node name not being set, edd_id spits out "main: no kernel EDD support" (returns 2), has_driver /block/sda returns 1, /dev/sda is created, lots of symlinks set up, lots of vol_id output, /dev/sda4 created, more vol_id output, /dev/sda3 created, more vol_id output, /dev/sda1 created [10:05] right [10:05] ls $ROOT finds something? [10:05] 3.txt has /sys/devices/pci0000:00/0000:00:1[cef] * [10:06] yep, ''ls $ROOT'' returns "/dev/sda3" [10:06] ok... [10:06] can you do [10:06] grep udevplug scripts/init-premount/udev [10:07] check that the calls are exactly as you've done above [10:09] the output contains three lines: "/sbin/udevplug -Bide -Bscsi"[...] , "/sbin/udevplug -Bpci -Iclass=0x0[12] *", and "/sbin/udevplug -W" [10:10] ok [10:10] so what I think you have, is the "SCSI takes longer than udev" bug [10:10] it's not a udev version issue, it's just how fast your machine feels like [10:10] basically if it fails, it means your machine reached the "mount root filesystem" bit faster then your SCSI/SATA controller got around to finding the devices on its bus [10:10] time: 0.50 [10:10] nice [10:11] ah, so the change in 5 to probe the additional devices is probably the issue [10:11] not sure what it was before though [10:11] Kamion: 1:20ish [10:11] on *my* system, not yours [10:11] Kamion: they're surprisingly similar for broadly similar hardware [10:12] all those sleep statements [10:12] we pretty much walked through /etc/udev/rules.d/00*init (and maybe 20*names* ?), correct? [10:12] crimsun: actually, if anything, that makes it more likely to succeed [10:12] http://people.ubuntu.com/~cjwatson/bootchart/dapper-20051201-2.png, anyway [10:12] crimsun: it was probably the fact that udevplug is faster in ubuntu5 [10:12] we're taking heavily about adding a generic "spin until -e $ROOT" to initramfs [10:13] Keybuk: ah. In any case, thanks for taking time. [10:14] are you on i386? [10:14] yeah (2.6.15-6-686) [10:14] ok [10:14] to boot [10:14] ,pimtrppt [10:14] uh [10:14] mountroot [10:14] run_scripts scripts/init-bottom [10:15] exec run-init /root $init "$@" /root/dev/console [10:15] -- [10:15] that should get you booted [10:17] Keybuk: indeed, thanks again. It's kinda scary how much of the syntax is becoming familiar (spent a few hours this morning poring over /etc/udev/rules.d/ and the udev man page to get the firmware loading correctly again) [10:18] ok... one moment, I have a package for you [10:19] k [10:23] http://people.ubuntu.com/~scott/initramfs-tools_0.40ubuntu5_all.deb [10:23] ^ download and install that === ogra_ [n=ogra@p5089DE32.dip.t-dialin.net] has joined #ubuntu-boot [10:24] then update-initramfs -u [10:24] then reboot [10:24] see if that cures you [10:25] Kamion: neat ... should be able to take another 10s off you by the weekend too [10:27] Keybuk: yep, boots fine [10:27] could yo do a few reboots, just to make sure [10:27] one or two warm [10:27] and one or two cold [10:27] yup [10:27] (ie three-finger, reset button and power off/wait/power on) [10:30] crimsun: yeah, it's kinda kooky when you realise you can boot the system from kernel entirely from memory [10:41] hmm, now it hangs after "Done.\nBegin: Mounting root file system ...\nBegin: Running /scripts/local-top ...\nDone." [10:44] after ~25 seconds I'm dropped to a busybox shell [10:44] reproducible on both warm and cold boots === BenC_ [n=bcollins@dpc674797249.direcpc.com] has joined #ubuntu-boot === BenC [n=bcollins@dpc674797249.direcpc.com] has joined #ubuntu-boot [11:28] crimsun: hmm, we'll have to continue this in the morning [11:29] is getting too late here, will be back in ~8 hours === crimsun [i=crimsun@pdpc/supporter/silver/crimsun] has left #ubuntu-boot [] === JanC [n=janc@lugwv/member/JanC] has joined #ubuntu-boot