On Friday 27 August 2004 11:12, Joey Hess wrote: > Alban Crequy wrote: > > So I tested the network pxe installation but the keyboard still not > > work. > > > > So I tried to modify the initrd in order to load the usb-uhci > > kernel module: I mount -o loop the initrd file, and add these ugly > > lines on /sbin/debian-installer-startup: > > > > depmod -a > > modprobe usb-uhci > > > > With these 2 lines, the keyboard works. > > > > dmesg, cpuinfo, etc. can be found at: > > http://linux.ensimag.fr/~acrequy/bazard/Debian-IA64-usbkeybord-bugr > >eport/ > > > > I suggest: > > - either detecting correctly the USB keyboard > > As far as I can tell the current installer should detect your usb > controller anbd load usb-uhci for it. Both of the PCI ids (808624c2, > 808624c4) of your usb controller are in the discover database. > usb-discover also has these values, and it is included on the initrd. > It's possible that this was not the case in rc1, you could try a > current daily build to be sure. The problem is in the way the initrd was built. If you look carefully, you will find that there is no modules.dep which crashes modprobe. This *should* have been done by the initrd builder but it failed because the kernel version and the udeb versions did not match. Check the ..../config/ia64.cfg for the correct KERNEL*VERSION values. Once the makefile can find the correct version, it does depmod before cramfs'ing the initrd. With the rollup to a new kernel version, this needs to be checked (again). btw, usb isn't the only one. Other modules that are needed prior to loading of some of the various kernel udeb's which do a (new) depmod in their postinst also break. Usb is critical (and noticed) simply because that forces the choice of serial or kb/video console at the very beginning. -- ************* Jim Lieb Wild Open Source Inc. [EMAIL PROTECTED] Cell: 831.295.9317 Office: 831.421.0883 Fax: 831.421.0885
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
