Re: udev strangeness in Sid?
On 2/12/06, Magnus Therning [EMAIL PROTECTED] wrote: Ah, didn't even know there were alternatives to mkinitrd. I was pretty happy about the size reduction when swtiching from 'most' to 'dep' in initramfs.conf. That took it from 4.5MB to 2.7MB. Switching to yaird brought it down to 1.2MB as well as take away all the error messages. I compile kernel using make-kpkg and get initrd and headers. How to make it use yaird for compiling. What are the pros and cons of yaird and mkinitramfs? -- L.V.Gandhi http://lvgandhi.tripod.com/ linux user No.205042
Re: udev strangeness in Sid?
On Sat, Feb 11, 2006 at 03:28:26PM +0100, Florian Kulzer wrote: [..] I then found out that the problem is absent when I create my initrd with yaird instead of mkinitramfs. The yaird-generated initrd is also much smaller than the one from mkinitramfs (939 KB vs 2.1 MB). Ah, didn't even know there were alternatives to mkinitrd. I was pretty happy about the size reduction when swtiching from 'most' to 'dep' in initramfs.conf. That took it from 4.5MB to 2.7MB. Switching to yaird brought it down to 1.2MB as well as take away all the error messages. /M -- Magnus Therning(OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. Of course I laugh at my own jokes. You can't trust strangers. -- Phyllis Diller pgpgMRvysJ4B6.pgp Description: PGP signature
Re: udev strangeness in Sid?
Hi, I have been bitten by this bug now, too, after I recompiled my 2.6.15 kernel from the newest Debian sources today. The exact error messages are (ScrollLock + pen and paper): udevd-event[n-1]: run-program: exec of program '/lib/udev/udev_run_hotplugd' failed udevd-event[n]: run-program: exec of program '/lib/udev/udev_run_devd' failed The errors stop as soon as the root file system is mounted; in my case they reach a count of n1000 before that happens. I had no luck googling for these messages. I then found out that the problem is absent when I create my initrd with yaird instead of mkinitramfs. The yaird-generated initrd is also much smaller than the one from mkinitramfs (939 KB vs 2.1 MB). Older versions of package initramfs-tools appear to have the same problem with the current linux-source-2.6.15-6 (I tried 0.50c, 0.49 and 0.48), therefore I am not sure how to file a bug report properly (against initramfs-tools, against the kernel sources, or both?). Any suggestions? It would probably be a wishlist bug anyway, since the general consensus in this thread seems to be that there are no negative effects besides the annoying error messages. Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev strangeness in Sid?
On 2/11/06, Florian Kulzer [EMAIL PROTECTED] wrote: I then found out that the problem is absent when I create my initrd with yaird instead of mkinitramfs. The yaird-generated initrd is also much smaller than the one from mkinitramfs (939 KB vs 2.1 MB). Older versions of package initramfs-tools appear to have the same problem with the current linux-source-2.6.15-6 (I tried 0.50c, 0.49 and 0.48), therefore I am not sure how to file a bug report properly (against initramfs-tools, against the kernel sources, or both?). Any suggestions? It would probably be a wishlist bug anyway, since the general consensus in this thread seems to be that there are no negative effects besides the annoying error messages. I compile kernel using make-kpkg and get initrd and headers. How to make it use yaird for compiling. What are the pros and cons of yaird and mkinitramfs? -- L.V.Gandhi http://lvgandhi.tripod.com/ linux user No.205042
Re: udev strangeness in Sid?
On 2/11/06, Florian Kulzer [EMAIL PROTECTED] wrote: I then found out that the problem is absent when I create my initrd with yaird instead of mkinitramfs. The yaird-generated initrd is also much smaller than the one from mkinitramfs (939 KB vs 2.1 MB). Older versions of package initramfs-tools appear to have the same problem with the current linux-source-2.6.15-6 (I tried 0.50c, 0.49 and 0.48), therefore I am not sure how to file a bug report properly (against initramfs-tools, against the kernel sources, or both?). Any suggestions? It would probably be a wishlist bug anyway, since the general consensus in this thread seems to be that there are no negative effects besides the annoying error messages. I compile kernel using make-kpkg and get initrd and headers. How to make it use yaird for compiling. What are the pros and cons of yaird and mkinitramfs? -- L.V.Gandhi http://lvgandhi.tripod.com/ linux user No.205042
Re: udev strangeness in Sid?
Hi, I then found out that the problem is absent when I create my initrd with yaird instead of mkinitramfs. The yaird-generated initrd is also much smaller than the one from mkinitramfs (939 KB vs 2.1 MB). I had the same problem. I checked the generated initrd file and noticed that the programs udevd moans about here are missing in the initrd file. I put this at the end of /usr/share/initramfs-tools/hooks/udev: mkdir $DESTDIR/lib/udev/ cp /lib/udev/hotplug.functions $DESTDIR/lib/udev/ +copy_exec /lib/udev/ata_id /lib/udev +copy_exec /lib/udev/cdrom_id /lib/udev +copy_exec /lib/udev/edd_id /lib/udev +copy_exec /lib/udev/firmware.agent /lib/udev +copy_exec /lib/udev/ide-devfs.sh /lib/udev +copy_exec /lib/udev/ide.agent /lib/udev +copy_exec /lib/udev/logger.agent /lib/udev +copy_exec /lib/udev/modalias_ieee1394 /lib/udev +copy_exec /lib/udev/modalias_serio /lib/udev +copy_exec /lib/udev/net.agent /lib/udev +copy_exec /lib/udev/path_id /lib/udev +copy_exec /lib/udev/raid-devfs.sh /lib/udev +copy_exec /lib/udev/scsi-devfs.sh /lib/udev +copy_exec /lib/udev/scsi-re-add /lib/udev +copy_exec /lib/udev/scsi_id /lib/udev +copy_exec /lib/udev/udev_run_devd /lib/udev +copy_exec /lib/udev/udev_run_hotplugd /lib/udev copy_exec /lib/udev/udevsynthesize /lib/udev +copy_exec /lib/udev/usb_id /lib/udev copy_exec /lib/udev/vio.agent /lib/udev +copy_exec /lib/udev/vol_id /lib/udev Regenerated the initrd file, and the errors are gone. cheers, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev strangeness in Sid?
Peter Hirdina wrote: Hi, I then found out that the problem is absent when I create my initrd with yaird instead of mkinitramfs. The yaird-generated initrd is also much smaller than the one from mkinitramfs (939 KB vs 2.1 MB). I had the same problem. I checked the generated initrd file and noticed that the programs udevd moans about here are missing in the initrd file. I put this at the end of /usr/share/initramfs-tools/hooks/udev: mkdir $DESTDIR/lib/udev/ cp /lib/udev/hotplug.functions $DESTDIR/lib/udev/ +copy_exec /lib/udev/ata_id /lib/udev +copy_exec /lib/udev/cdrom_id /lib/udev +copy_exec /lib/udev/edd_id /lib/udev +copy_exec /lib/udev/firmware.agent /lib/udev +copy_exec /lib/udev/ide-devfs.sh /lib/udev +copy_exec /lib/udev/ide.agent /lib/udev +copy_exec /lib/udev/logger.agent /lib/udev +copy_exec /lib/udev/modalias_ieee1394 /lib/udev +copy_exec /lib/udev/modalias_serio /lib/udev +copy_exec /lib/udev/net.agent /lib/udev +copy_exec /lib/udev/path_id /lib/udev +copy_exec /lib/udev/raid-devfs.sh /lib/udev +copy_exec /lib/udev/scsi-devfs.sh /lib/udev +copy_exec /lib/udev/scsi-re-add /lib/udev +copy_exec /lib/udev/scsi_id /lib/udev +copy_exec /lib/udev/udev_run_devd /lib/udev +copy_exec /lib/udev/udev_run_hotplugd /lib/udev copy_exec /lib/udev/udevsynthesize /lib/udev +copy_exec /lib/udev/usb_id /lib/udev copy_exec /lib/udev/vio.agent /lib/udev +copy_exec /lib/udev/vol_id /lib/udev Regenerated the initrd file, and the errors are gone. Alright, so that's the proper way to solve it. I was in a hurry, therefore I just renamed both /usr/sbin/mkinitramfs and /usr/sbin/mkinitrd and then I did a dpkg-reconfigure on my linux-image package. This resulted in yaird being used, but it is of course an extremely ugly hack. I guess I should finally learn the correct usage of the various initrd generators. Thanks a lot for the information. Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev strangeness in Sid?
On Thu, Feb 09, 2006 at 02:03:29AM +, L.V.Gandhi wrote: On 2/8/06, Ken Wahl [EMAIL PROTECTED] wrote: On Tue, Feb 07, 2006 at 09:26:53AM +, Magnus Therning wrote: Yes, just verified it on my second machine. udev apparently tries to run stuff located in '/lib/udev/', and it doesn't find it. I have 3745 udevd_events written to the console during boot regarding this :( It seems the system isn't hurting from it though, everything's working fine AFAICT :) I wanted to know that How did you find it is 3745 lines? I also bootlogd enanled. But couldn't see in /var/log/boot. The lines are pre-pended with a string that contains a number, and that number increases by one for every line. I simply assumed it started from 1 and counted up :-) I haven't been able to find the lines in any log file either... I'm not sure what conclusions to draw from this, problem in the kernel? /M -- Magnus Therning(OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. The day after tomorrow is the third day of the rest of your life. pgptlSda6W301.pgp Description: PGP signature
Re: udev strangeness in Sid?
On Tue, Feb 07, 2006 at 09:26:53AM +, Magnus Therning wrote: Yes, just verified it on my second machine. udev apparently tries to run stuff located in '/lib/udev/', and it doesn't find it. I have 3745 udevd_events written to the console during boot regarding this :( It seems the system isn't hurting from it though, everything's working fine AFAICT :) ---end quoted text--- I see the same behavior on Sid using the latest 2.6.15-k7 kernel but not it's predecessor. Specifically linux-image-2.6.15-1-k7-2.6.15-4_i386.deb has the errors but linux-image-2.6.15-1-k7-2.6.15-3_i386.deb does not. This is with udev_0.084-3_i386.deb for both kernels. I do not seem to have lost any functionality that I can tell. -- Ken signature.asc Description: Digital signature
Re: udev strangeness in Sid?
On 2/8/06, Ken Wahl [EMAIL PROTECTED] wrote: On Tue, Feb 07, 2006 at 09:26:53AM +, Magnus Therning wrote: Yes, just verified it on my second machine. udev apparently tries to run stuff located in '/lib/udev/', and it doesn't find it. I have 3745 udevd_events written to the console during boot regarding this :( It seems the system isn't hurting from it though, everything's working fine AFAICT :) I wanted to know that How did you find it is 3745 lines? I also bootlogd enanled. But couldn't see in /var/log/boot. I see the same behavior on Sid using the latest 2.6.15-k7 kernel but not it's predecessor. Specifically linux-image-2.6.15-1-k7-2.6.15-4_i386.deb has the errors but linux-image-2.6.15-1-k7-2.6.15-3_i386.deb does not. This is with udev_0.084-3_i386.deb for both kernels. I do not seem to have lost any functionality that I can tell. I have compiled kernel 2.6.15 in the morming on 5/2/6. It is ok. I did apt-get update in AN on 5/2/6. It did upgrade udev. Using same config today I did kernel make today. I also got udev lines during boot similar to magnus. Any idea what it is what does it signify? -- L.V.Gandhi http://lvgandhi.tripod.com/ linux user No.205042
Re: udev strangeness in Sid?
2.6.15-1-686 me is sick of udev's error lines too :'(over hundred lines ;) couldnt even count how many.if anyone knows the solution, please let us learn too ;)
Re: udev strangeness in Sid?
On Tue, Feb 07, 2006 at 07:44:07AM +0100, Lubos Vrbka wrote: hi, Just did an `apt-get upgrade` on my Sid system and since it pulled in a new kernel I rebooted. During booting I was greated with _lots_ of message from udev about not being able to run hotplugd or udevd (I'm fairly sure those were the programs it was complaining about, I didn't find any trace of those messages in /var/log/* so I'm relying on my memory here). Anyone else seeing the same? Anyone who can offer a solution that'll make it go away ;-) i experience similar (same?) problem with the 2.6.15-something kernel that is in the sid right now. i also don't remember the message, but it is udevd that complains that it cannot run something (i recall seeing something like 'runscript' on the error line and then some path beginning with /lib/). the system however boots fine. this happens only with the distribution kernel. my self-compiled kernels work fine. Yes, just verified it on my second machine. udev apparently tries to run stuff located in '/lib/udev/', and it doesn't find it. I have 3745 udevd_events written to the console during boot regarding this :( It seems the system isn't hurting from it though, everything's working fine AFAICT :) /M -- Magnus Therning(OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. Sendmail and make are two well known programs that are pretty widely regarded as being debugged into existence. That's why their command languages are so poorly thought out and difficult to learn. It's not just you -- everyone finds them troublesome. -- Peter van der Linden, Expert C Programming, p. 220 pgp23ep27Wldi.pgp Description: PGP signature
udev strangeness in Sid?
Just did an `apt-get upgrade` on my Sid system and since it pulled in a new kernel I rebooted. During booting I was greated with _lots_ of message from udev about not being able to run hotplugd or udevd (I'm fairly sure those were the programs it was complaining about, I didn't find any trace of those messages in /var/log/* so I'm relying on my memory here). Anyone else seeing the same? Anyone who can offer a solution that'll make it go away ;-) Could it be related to the fact that udev _never_ is able to update the ramdisk? (update-initramfs -u always reports that /boot/initrd.img-2.6.15-1-686 was been altered. Cannot update.) /M -- Magnus Therning(OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. If you can explain how you do something, then you're very very bad at it. -- John Hopfield pgpqQr3hN8gaM.pgp Description: PGP signature
Re: udev strangeness in Sid?
Magnus Therning wrote: Just did an `apt-get upgrade` on my Sid system and since it pulled in a new kernel I rebooted. During booting I was greated with _lots_ of message from udev about not being able to run hotplugd or udevd (I'm fairly sure those were the programs it was complaining about, I didn't find any trace of those messages in /var/log/* so I'm relying on my memory here). Anyone else seeing the same? Anyone who can offer a solution that'll make it go away ;-) Could it be related to the fact that udev _never_ is able to update the ramdisk? (update-initramfs -u always reports that /boot/initrd.img-2.6.15-1-686 was been altered. Cannot update.) This will probably not be too helpful, but I can at least tell you that I get the same error message whenever udev is updated, but I do not have any problem with udev during boot. (I am using a custom 2.6.15 kernel compiled from the newest Debian sources on a Sid machine and udev 0.084-3.) Did you try to activate bootlogd? Maybe that will give you a chance to read the error message in detail. Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev strangeness in Sid?
hi, Just did an `apt-get upgrade` on my Sid system and since it pulled in a new kernel I rebooted. During booting I was greated with _lots_ of message from udev about not being able to run hotplugd or udevd (I'm fairly sure those were the programs it was complaining about, I didn't find any trace of those messages in /var/log/* so I'm relying on my memory here). Anyone else seeing the same? Anyone who can offer a solution that'll make it go away ;-) i experience similar (same?) problem with the 2.6.15-something kernel that is in the sid right now. i also don't remember the message, but it is udevd that complains that it cannot run something (i recall seeing something like 'runscript' on the error line and then some path beginning with /lib/). the system however boots fine. this happens only with the distribution kernel. my self-compiled kernels work fine. Could it be related to the fact that udev _never_ is able to update the ramdisk? (update-initramfs -u always reports that /boot/initrd.img-2.6.15-1-686 was been altered. Cannot update.) i recall also seeing similar message that was printed out for my kernel(s) that do not use initrd, that is somewhat strange. regards, -- Lubos [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
