Hi Matt! On Thu, Mar 31, 2005 at 05:33:06PM -0500, Matt Price wrote: > > not on this list- - I mentioned it on debian-powerpc, but no one seems > to know what the problem is. There seeem to be two kinds of problems: > > 1) scsi: I boot from, and have my root filesystem on, a scsi disk. > THis means that scsi support has to be compiled into the main kernel, > and since most of the stock kernels have scsi disk support as a module, > I can't use them. With 2.4.x, I have working .config's that take care > of the problem. With 2.6.x, it's trickier. The kernel seems to load > properly, and scsi recognizes my scsi card and maybe the disks, but then > stops with an error "/dev/sda7 is not a valid ext3 filesystem" -- and > then dumps me into single-user mode to diagnose the problem with fsck. > However, I can't go any further from there because, > Could you give us/post a link to the kernel output (or those snippets relating to Scsi/Usb)? > > 2) usb: none of my usb peripherals are recognized by the kernel -- > despite the fact that I have the HID module enabled. Since I have a > mac, the usb connection is the only way for me to enter anything into > the computer, so I end up stalled, and have to do a hard reboot. There > are no error messages to this effect in /var/log/messages -- so I'm not > sure what's up. > > Any clues? can I provide you with more details? a (broken) .config file > is on the web at: > > http://www.derailleur.org/.configfiles/ > Hm, I've looked through it - looks fine. I guess you could even turn the whole IDE branch off if cdrom and all harddisks are connected via SCSI, but that's another thing. :) You're activating several controllers in the SCSI section... the AIC7xxx (got the right one? There's also AIC7XXX_OLD) and the QLA2xxx. During boot, the kernel should print a couple of lines when the controller driver loads, and maybe even wait a little, if the controller scans all of its LUNs first. Are all disks properly recognized? Concerning your no-input-via-USB problem: - Have you tried the USB boot protocol input drivers instead of the full HID? You have to deactivate USB_HID to make those options appear... - You could (temporarily) change /etc/inittab to call something else in single-user mode; edit the line ~~:S:wait:/sbin/sulogin to ~~:S:wait:/root/my_2.6_diag_script , write a short shell/perl script (or whatever suits you... you could for example put an fsck.ext3 /dev/sda7 in there), which redirects/copies its output somewhere safe, and put a reboot in the last line, so that the system reboots cleanly and you can investigate the logs from the old 2.4 system. If /dev/sda7 is not carrying any important data (i.e. / or /boot filesystem), and it's the only disk fsck is complaining about, remove the "auto" flag from it in /etc/fstab so it's skipped during bootup - and then boot directly into single-user (append S to the boot prompt). Hope this helps, Jan -- Jan C. Nordholz <jckn At gmx net>
Attachment:
signature.asc
Description: Digital signature