On Sun, Sep 18, 2005 at 04:30:00AM +0200, Jonas Smedegaard wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 15 Sep 2005 21:54:27 +0200 > Sven Luther <[EMAIL PROTECTED]> wrote: > > > Well, i have to say that i am agreably surprised, by yaird, but i > > still have some small caveats : > > > > 1) The usb input modules are needed for usb keyboards. > > > > ./drivers/usb/core/usbcore.ko > > ./drivers/usb/host/ehci-hcd.ko > > ./drivers/usb/host/ohci-hcd.ko > > ./drivers/usb/host/uhci-hcd.ko > > ./drivers/usb/input/usbhid.ko > > > > Not sure if yaird would have made the right thing on a powermac > > without ps/2, or if i had a usb keyboard connected though. Also, in > > my experience ehci needs to be loaded before ohci or uhci, in order > > to not cause stability problems on pegasos with the old firmware, not > > sure if this is the case somewhere else or needed. > > - From the man page, section FILES, it seems the need for usb is probed > using /proc/bus/input/devices .
Neat, i will test it with a usb keyboard during install, still doesn't help in my case since i use to switch between both, but i guess configurability will help there. > > 2) i have a second disk on a sil sata drive (the sata modules come > > from /etc/mkinitrd/modules, not detected), and with initrd-tools, > > these where not included, and fsck had troubles with it each time. > > A brand new thing in 0.11 is configurability: Have a look > at /usr/lib/yaird/conf and post here what changes works for you. Cool, will have a look. > Hmm - Erik: Why did you not put this below /etc?!? > > > 3) my filesystem is actually ext3, not ext2, will the missing ext3 > > module cause problems ? > > How do your /etc/fstab look like? > > If / is mounted as ext3 then that module should have been picked > automatically. /dev/hda4 / ext2 defaults,errors=remount-ro 0 1 Huh, indeed, i wonder why it is noted as ext2, i always thought it was an ext3. > Erik: I actually found what seems to be a bug: Debian supports mount > type to be "auto" which then tries ext3 and falls back to ext2 on > failure. But yaird fails creating an initramfs, saying the module > "auto" does not exist. :) > > Anyway, yaird is great, and i look forward into making more tests > > with it :) > > Great to hear that. And again, all issues seem to be on my side, will confirm this later this week, so yaird is very great. > I believe that for debian-installer use a different template needs to > be written that probes less and instead statically includes a bunch of > modules. I have no experience in this, so if you want to play with > that, Sven, then you are more than welcome. you mean, how to detect the stuff during d-i run ? I guess a part of that is available, or can easily be made available, from the debconf templates, i will look at this next weekend. ... Eek, yaird is full of perl :/, i am not perl fluent, will see what i can do, my contribution may possibly be more on a higher level, testing out and proposing a method than implementation. The other issue is that we need a standard tool for creating an initrd for d-i, which i belive could be common to yaird, initramfs and d-i ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
