hello all ...first of all sorry for my english... Here is my problem with this server...with debian etch - Debian installer freezes, and the log console loops at detecting USB - It seems that it is the kernel who can not detect the USB. There is a infinite loop in USB detection - Even if USB is disabled in BIOS, the kernel does detect it and loops on the USB HUB - Even if I tell the installer not to detect USB it loops - Debian etch or sid installers does the same - Same for UBUNTU 6
With the console, while installing, it appears that the kernel USB module is continuously trying to detect USB but does not stop detecting it ( like it was discovering an infinity of USB Hubs and ports ) i tried to disable to the BIOS all the usb support and ports...but it didn't work at all i have still the same problem of usb loops....
WIth Debian 3.1 r2 stable it seems to be better but the installer doesn't recognise my ethernet card and the console doesn't have a lspci to see wich module do i have to choose from the manual menu...
- Debian installer freezes, and the log console loops at detecting USB
Could you paste some of that output? (or make a screen capture)
Quote
WIth Debian 3.1 r2 stable it seems to be better but the installer doesn't recognise my ethernet card and the console doesn't have a lspci to see wich module do i have to choose from the manual menu... Any ideas???
I assume there is 'nothing' connected to the USB ports? (if so, disconnect all and try again)
You could try booting from knoppix (http://www.knoppix.org) and use lspci to see what ethernet card is on board. Or you could install Debian 3.1r2 with kernel 2.4 and see if that works. (after that you could try to upgrade to kernel 2.6.15 or 16 in etch)
I'm curious on how you go along, please inform us. I hope to get a hand on a DL320 soon to try it out..
Ok tnks for the answer ...i'll try the knoppix... the kernel messages that are keeping printing on the screen in loop are exactly like the messages reporting in the link below... http://www.linuxquestions.org/questions/showthread.php?t=444111 THe model of the server isn't the same but the problem yes...same as described there... i tried to blacklist the usb modules with the ubuntu 6 live cd....( the only live that i been able to let boot because not even gentoo or fedoracore or rescuecd...starts...)
Notting is plugger in the usb ports...of course... It seems that Debian Sarge 3.1 is full supported and the netinstall cd boots quite good and i reported no problems with usb messages...by the way i need a newer kernel because my ethernet card on this machine is a Broadcom Trigon3 (tg3) wich is supported only oh kernels > 2.6.8...(etch...) i don't know how to manage this situation i really would like to install a debian on this server or at least a debian-like distro not a RedHat or SuSe...wich i don't like at all...
cheers
« Last Edit: July 26, 2006, 09:48:31 am by tommaso »
I successfully installed debian sarge on this HP DL320 using a kmuto debian sarge image which ships with all needed modules (tg3) to finalize the installation. Get it here: http://kmuto.jp/debian/d-i/2.6.15/sarge-custom-0206.iso
The only problem I have is "uhci_hcd" which seems to have troubles with the ilo2 virtual mouse/keyboard - these devices connect and disconnect in a neverending loop. The only option right now is rmmod this module.
I will blacklist this thing tomorrow and see what happens. Basically I do not need USB 1.0 (wich would be affected) and I hope blacklisting ends up in a well running system.
Question about the dl320g4 and ilo2: are you able to use remote console (not serial) of ilo2 without the ilo-advanced-license? This was possible for me so far using ilo (version 1), but is no longer with ilo2. Did HP remove the remote console feature from the standard license?
The only problem I have is "uhci_hcd" which seems to have troubles with the ilo2 virtual mouse/keyboard - these devices connect and disconnect in a neverending loop. The only option right now is rmmod this module.
This is a kernel issue, when you use a newer kernel (like 2.6.17 or .18) this problem should be gone. The latest etch installer uses 2.6.17 so they should work a expected.
Question about the dl320g4 and ilo2: are you able to use remote console (not serial) of ilo2 without the ilo-advanced-license? This was possible for me so far using ilo (version 1), but is no longer with ilo2. Did HP remove the remote console feature from the standard license?
Well, as far as I can tell, the iLO2 is not very different from 1. I don't have an HP with iLO 2 nearby for the moment (will test in the next few days), but according to the HP website the console access still exists:
Found on the HP website:
Quote from: HP website
The iLO2 Standard features include, simplified setup, text-based console for access to server boot sequences and text-mode operating system console, group configuration and server actions, remote power on/off, SSL security, detailed server status, logs, alert forwarding, virtual indicators, diagnostics, and automatic server recovery.
Actually I found the problem; here is what HP says, after the citation is how I dealt with:
Quote
<HP iLO2 User Guide> All iLO 2 Remote Console connection options are graphical and must be rendered using a client program that can process iLO 2 graphics commands. Two clients are provided to rendjer the iLO 2 graphics: a Java™-based Remote Console and a Windows® Active X-based Integrated Remote Console. For those clients that do not understand iLO 2 graphics (SSH and telnet), the iLO 2 Remote Serial Console must be used. iLO 2 blades ship with the iLO 2 Standard Blade Edition, which includes the Remote Console. However, the HP ProLiant ML and HP ProLiant DL models ship with the iLO Standard license, which does not include the Remote Console. Previous iLO Standard licenses on the HP ProLiant ML and ProLiant DL models included a text-based Remote Console. Because there is no true text protocol in the iLO 2 Remote Console, the iLO 2 Standard Remote Console on the HP ProLiant ML and ProLiant DL models is limited to pre-operating system only. As soon as the server starts to boot an operating system, the iLO 2 Standard on the HP ProLiant ML and ProLiant DL models displays a message that indicates the need for the iLO 2 Advanced license.</HP iLO2 User Guide>
So what I did is enabling serial console (S1) output for vt320 emulation (/etc/inittab), configured it to be standard console (/boot/grub/menu.lst) and accessed the server via remote serial console in iLO2. (Grub don't has to be modified because it's pre-os and therefore working with native iLO-serial-support - maybe it would be better to do so (faster, better usability...).
If somebody has done it more comfortably or is experiencing severe problems doing like this, please post your problems.
So what I did is enabling serial console (S1) output for vt320 emulation (/etc/inittab), configured it to be standard console (/boot/grub/menu.lst) and accessed the server via remote serial console in iLO2. (Grub don't has to be modified because it's pre-os and therefore working with native iLO-serial-support - maybe it would be better to do so (faster, better usability...).