From: Olaf <mai...@ba...> - 2009-09-24 17:03:48
|
Gilles Espinasse wrote: > Not yet send what I discover with udev. > On 16 attempts I register udevadm settle duration: > - it take 5 s in 12 attempt > - it take 112 s in 4 attempt I have seen udevadm settle taking more than 15 minutes after which I gave up waiting. > I have added an easy way on init script to register on an usb key whatever log > you want. You just need to add on the kernel line DEBUGDEV=sda to have a log > created on init script saved to sda key. > If DEBUGDEV does not exist, nothing is made. > I think that could be helpfull. Yes. Early in the boot process can be fairly difficult, as there are no other consoles available. > Should we not have all our installer specific variables in capital? You mean nousb, nombr and such variables? > I have now another issue wich I think is udev related, not sure it is in all > attempt yet : > first card with e100 driver that I pxe-boot from, is renamed to eth1_rename > second card with 8139too appear as eth0 > third card with n2kpci appear as eth1 > Then everything went wrong, because boot interface is not detected and installer > try to 'ifconfig 192.168.... up (the boot ip) without an interface name. > And installer think eth2 exist but it does not appear in /sys/class/net, only > eth1_rename. > I don't know why the rename happen I saw an error message on 1 attempt, something like failed to rename to eth0_rename. > Concerning udev upgrade, I noticed that a newer libblkid from util-linux-ng is > required in udev-142. So we should upgrade first util-linux-ng (and e2fsprogs) > to have the newer libblkid. Not tested at all. I have managed to upgrade e2fsprogs to 1.41.9 and util-linux-ng to 2.16.1. Required some configure modifications for e2fsprogs and reordering in make.sh. Still fighting with the modifications for the toolchain. Olaf |