meino.cra...@gmx.de wrote:
Hi John,
if sysreq does not work after inserting the usbstick then the kernel
stops working completly (the sysreq-code of the kernel is not
entered), which seems to be that something happening on very low
level (the problem not the sysreq-code of course... ;)
Just another shot into the dark:
Do you have modularized all usb-related stuff? This also may help to
let the usb-sticks work correctly.
Ah! Another thing: Insert the related modules into
/etc/conf.d/modules so that they get loaded in a very early
phase of the bootprocess.
With modules loaded and with no usb-sticks as root inspect the
according modules with modinfo -p<modulename> to see, whether
there a additional parameters you may pass to the modules to get
an extra of informations or - better - to fix the issue.
Modify under "Kernel hacking" in the kernel config the
"Default message log level" to see more.
Furthermore there is a switch "Kernel debugging" with sub-options.
May be turning on these may also help to get closer to all evil ;)
Last thing:
If there is nothing valueable stored on the usbsticks:
Try to reformat the usbsticks. Instead of putting a FAT32-fs on the
bare device, create a regular partition and create a Linux-fs
(reiserfs, ext2/3/4 or like that) on that partition.
This may not be good idea in general, but - if it works - this would
give a hint, where to search next.
Good luck!
Best regards,
mcc
Have you looked to see if that mobo has a USB problem and a BIOS update
to fix it?
Just curious.
Dale
:-) :-)
