[09:14] <apw> cluk what is broken about it?  was it mising the asm directory, that was an issue triggered by a bad find upload
[12:17] <apw> smb, you have a thinkpad with hardy, can you check if the thinkpad/thinkvantage key produces an X keysym.  using xev you should see that key produce XF86Launch1
[12:25] <apw> all, today is one of our regular kernel bug days ... come play with our fun bugs, free erm karma to those who help :)  https://wiki.ubuntu.com/KernelTeam/BugDay/20090512
[13:19] <smb> Just returned
[13:19] <smb> apw, the key does not produce events by default
[13:20] <smb> apw, The problem, iirc, is that the acpi events arrive but are mapped to a keyboard key that is normally not existent (with fakekey) So the keyboard driver ignores is
[13:20] <smb> it
[13:42] <apw> smb, ok so that is officially still broken in hardy
[13:43] <smb> apw, Yeah, and it actually was some deliberate change from upstream to ignore non-existent keys. This is where fakekey has its limit and the drivers in general should use input-events
[13:43] <smb> But thats probably a too big change for hardy
[13:43] <apw> yeah ... fair enough ... 
[15:07] <andresmujica> morning
[15:07] <andresmujica> we need a topic update..
[15:26] <apw> smb, on this thinkpad, does the command 'setkeycodes e073 148' sort out your thinkpad key thing?  so its seen in Xev ?
[15:27] <smb> apw, confirmed
[15:27] <apw> smb so we have a work around for hardy and intrepid
[15:28] <apw> no point in updating those two to fix something we have a simple work around for imo
[15:29] <smb> apw, Yeah, as it is long ago I am not sure I remember correctly, there had been some notes that this keycode you set might be in use by another key. But in general, yes
[15:29] <apw> when you say its visible, is it visible carrying the XF86Launch1 key symbol?
[15:30] <apw> smb, ^^
[15:32] <smb> Hm, don't see it:
[15:32] <smb> KeyPress event, serial 30, synthetic NO, window 0x4800001,
[15:32] <smb>     root 0x88, subw 0x0, time 25518768, (110,79), root:(1400,134),
[15:32] <smb>     state 0x0, keycode 159 (keysym 0x0, NoSymbol), same_screen YES,
[15:32] <smb>     XLookupString gives 0 bytes: 
[15:32] <smb>     XmbLookupString gives 0 bytes: 
[15:32] <smb>     XFilterEvent returns: False
[15:34] <apw> smb, what does 'xmodmap -pk | grep Launch1' say
[15:34] <smb> ""
[15:35] <apw> hrm
[15:48]  * apw notes that the current rate he will finish his 20 bug day bugs by about 2 am
[15:48] <apw> how are other people doing?
[15:50] <smb> apw, similar
[15:51]  * apw has reached 6 after 8 hours ... not good
[15:51] <apw> ok 7 hours
[17:44]  * apw actually gets to the bottom of his list of bugs
[17:44]  * apw pokes a couple of community ones for 'fun'
[17:57] <smb_tp> apw, Hrmpf, how did you do that?
[18:00] <apw> smb_tp, once you get to the Incompletes if they have been asked for feedback like a year ago by leann i felt happy closing them asking for a reopen if it stille xisted
[18:01] <apw> and most of my incompletes were like that
[18:01] <apw> the highs near killed me
[18:01] <smb_tp> maybe I should jump to the incompletes and get back to the highs later...
[18:59] <devel0> hi , i have a small problem related to initrd and I was hpoing someone could shed some light
[19:00] <devel0> Im looking to change the usplash theme but I cant exactly do an update initramfs -d becauyse I have separated ubuntu because im doing a pxe boot
[19:00] <devel0> when I say separated
[19:00] <devel0> I mean one part is vmlinuz and initrd , the other part is a squashfs file downloaded via http
[19:01] <devel0> when I simply replace the .so file , ubuntu moans at boot up that it cant find a usplash theme 
[19:01] <devel0> that will work with my resol
[19:01] <devel0> however with the default .so file , it doesnt complain
[19:01] <devel0> I changed the file , repacked initrd with cpio and gzip , but still im missing something to make it all work
[19:01] <devel0> any ideas someone ?
[19:02] <devel0> please ? :O
[19:03] <sladen> names
[19:04] <devel0> filenames you mean ?
[19:04] <sladen> devel0: the /etc/alternatives/usplash-artwork.so symlink is used to select which .so to pack into the initramfs cpoio
[19:04] <devel0> I was aware of that but why cant i just have the default usplash-artwork.so in /usr/lib/usplash/ ?
[19:06] <sladen> I'm stil not completely following the problem, can you try explaining it in a different way (what's "resol") ?
[19:07] <sladen> btw, for future reference, usplash doesn't have anything to do with the kernel.  It runs entirely in userspace
[19:07] <devel0> yeah i know , i just thought that maybe since this is a boot issue I could get a helping hand from you guys
[19:08] <devel0> basically I have initrd.gz outside the distro and i use pxe to boot it with vmlinuz (ubuntu's kernel), then I have a squashfs file which contains the root filesystem
[19:08] <devel0> I cant do an update-initramfs on my initrd.gz file , I can only pack it again with cpio and gzip
[19:08] <devel0> or maybe I can via the live boot
[19:08] <devel0> hmmm
[19:08] <devel0> brb
[19:08] <devel0> :D
[19:46] <layer8> hi there
[19:47] <layer8> can someone help me with a self compiled kernel? i have an error like "sata link down" during boot
[19:48] <devel0> sladen
[19:48] <devel0> I cant get round it
[19:48] <devel0> I was wondering if you could help
[19:48] <devel0> is there someone that can explain what integration the usplash .so file has with the initrd archive ?
[19:48] <devel0> beyond the fact that it sits inside it
[19:56] <layer8> hello?
[19:57] <layer8> noone here, who can help me?
[20:09] <sladen> devel0: no integration, other than getting copied in there by /usr/share/initramfs-tools/hooks/usplash
[20:09] <sladen> devel0: initramfs is flexible enough that the same initramfs should do you for PXE and non-PXE boot IIRC.
[20:10] <devel0> im boggled as to why it complains only by replacing the .so
[20:10] <sladen> devel0: best place to ask would be the LTSP / Edubuntu people
[20:10] <devel0> when i replace the .so file , i get a failed to init screen init thingy
[20:10] <devel0> oh
[20:10] <sladen> devel0: where did you get this new .so from?
[20:12] <devel0> i tried many
[20:12] <devel0> i tried kubuntus for example
[20:12] <devel0> edubuntus , and a few others
[20:12] <devel0> even custom ones from the net
[20:12] <devel0> i dont get it , seriously im puzzled , i just went through the script in the initramfs tools that is used to copy usplash
[20:12] <devel0> I do the same thing but manually
[20:12] <devel0> this is crazy :)
[20:16] <sladen> remember that the theme is a loadable executable file. Is it built to the same version as the usplash itself.
[20:16] <sladen> this is why my query about "where did you get it"
[20:16] <sladen> exactly how did you install this other usplash theme?
[20:16] <devel0> omg does the so file have to match the libusplash.so ver ?
[20:17] <sladen> did you compile it yourself.  Does it work with the test script
[20:17] <sladen> devel0: uh huh.
[20:17] <devel0> brb :)
[20:17] <devel0> is there a way to know what ver was used to build an so ?
[20:18] <sladen> dpkg -l | grep usplash
[20:19] <sladen> and  apt-cache show usplash-theme-ubuntu  says that it depends (it's compiled for)   usplash (>= 0.5.30)
[20:19] <devel0> im trying something i didnt before
[20:19] <devel0> the simplest of things
[20:19] <devel0> making the so executable
[20:19] <devel0> hoping it might work
[20:20] <devel0> im not too sure the usplash version makes much of a difference
[20:21] <devel0> ok making the file exec didnt work
[20:21] <devel0> leme sync the versions
[20:21] <sladen> *blinks*
[20:22] <sladen> devel0: put simply if usplash and the library (theme) it is dlopening are not speaking the same language (the same ABI) then it's not going to work
[20:23] <sladen> devel0: just  sudo apt-get install kubuntu-artwork-usplash   if you want something else
[20:27] <devel0> just recompiled an .so
[20:27] <devel0> worked like a charm
[20:27] <devel0> :)
[20:27] <devel0> How can I thank you ?
[20:28]  * devel0 dances 
[22:38] <vertix> anybody knows about boot sequence in a mixed IDE/SCSI situation at the point where root filesystem is loaded?
[22:38] <vertix> mounted that was
[22:39] <vertix> at least it is not insane as on #ubuntu
[22:39] <vertix> but looks quiet like in a grave
[22:39] <vertix> anybody alive here?
[22:39] <vertix> maaaaan, linux is a trip, i tellya
[22:40] <vertix> oki doki
[22:50] <devel0> yeah i know what you mean
[22:50] <devel0> when you say "linux is a trip"
[22:50] <devel0> :D
[22:50] <devel0> sorry I cant help