1 |
meino.cramer@×××.de wrote: |
2 |
> Hi John, |
3 |
> |
4 |
> if sysreq does not work after inserting the usbstick then the kernel |
5 |
> stops working completly (the sysreq-code of the kernel is not |
6 |
> entered), which seems to be that something happening on very low |
7 |
> level (the problem not the sysreq-code of course... ;) |
8 |
> |
9 |
> Just another shot into the dark: |
10 |
> Do you have modularized all usb-related stuff? This also may help to |
11 |
> let the usb-sticks work correctly. |
12 |
> |
13 |
> Ah! Another thing: Insert the related modules into |
14 |
> /etc/conf.d/modules so that they get loaded in a very early |
15 |
> phase of the bootprocess. |
16 |
> |
17 |
> With modules loaded and with no usb-sticks as root inspect the |
18 |
> according modules with modinfo -p<modulename> to see, whether |
19 |
> there a additional parameters you may pass to the modules to get |
20 |
> an extra of informations or - better - to fix the issue. |
21 |
> |
22 |
> Modify under "Kernel hacking" in the kernel config the |
23 |
> "Default message log level" to see more. |
24 |
> |
25 |
> Furthermore there is a switch "Kernel debugging" with sub-options. |
26 |
> May be turning on these may also help to get closer to all evil ;) |
27 |
> |
28 |
> Last thing: |
29 |
> If there is nothing valueable stored on the usbsticks: |
30 |
> Try to reformat the usbsticks. Instead of putting a FAT32-fs on the |
31 |
> bare device, create a regular partition and create a Linux-fs |
32 |
> (reiserfs, ext2/3/4 or like that) on that partition. |
33 |
> |
34 |
> This may not be good idea in general, but - if it works - this would |
35 |
> give a hint, where to search next. |
36 |
> |
37 |
> Good luck! |
38 |
> |
39 |
> Best regards, |
40 |
> mcc |
41 |
> |
42 |
> |
43 |
|
44 |
Have you looked to see if that mobo has a USB problem and a BIOS update |
45 |
to fix it? |
46 |
|
47 |
Just curious. |
48 |
|
49 |
Dale |
50 |
|
51 |
:-) :-) |