Topic: Install to NetServer E800 - Need NOUSB

[RobD]

I have two HP NetServer E800 servers.  One has a single processor and installs and runs the 6.0.1-01 just fine.  The second one is a dual processor and gives me problems (has since v5.x).

In order to install, I need to do the ACCEPT NOUSB trick at startup, similiar to what the ProLiant 1600 machines need.  Otherwise it locks up at the install point where it activates the USB drivers.

But once it is installed, it still locks up starting up.  How do I add the NOUSB option to the running configuration?  Right now I edited the boot floppy to have NOUSB, but that kernel is only a single CPU version and I'd hate to have to rely on my server to boot from a floppy.

Any help?  I need to get this answered within the week because I'm travelling to the server's very remote location for maintenance.

[smeghead]

hit ctrl-x at boot logo to get a boot prompt and press tab for kernel listing, type name of required kernel with nousb option.  If this works you need to edit the grub conf file in /boot/grub: see http://robots.activmedia.com/archives/pioneer-users/msg02426.html for the required syntax.

HTH

[RobD]

Thanks, that is exactly what I was looking for!  On the floppy, it was easy to find the syslinux.cfg file and make the change.  But I couldn't figure out how to handle the boot loader on the drive.

I see where I can specify the SMP kernel to be the default as well in the grub.conf file.  That will help as well.

[RobD]

Bummer.  I'm at the server location and have about 12 hours left for my stay.  I went into a console and changed directory to /boot/grub and added the "nousb" right after the ro entry for both the up and smp kernel entries.

Upon reboot, the server still hangs at this line:

Code: [Select]

Initializing USB controller (usb-ohci):

Any clues on what to do now?  I really don't want to leave this thing dependent on a boot floppy!

[RobD]

Can anybody help with this?  This HP uses a motherboard based on the Serverworks chipset, if this helps.  It has to be something with the dual processors, because the single CPU units work fine.

Can I just turn off the loading of the USB driver?  How would I safely do that so that it doesn't get turned on again?  (I see modules.conf has an alias for it).