6.06.1 Install fails on HP ML 350G5 with kbdmode hanging

[Carsten Menke]

On a HP ML 350 G5 it is not possible to install Dapper 6.06.1 in a normal way.

As soon as you reach Configuration Step where you configure your keyboard
the screen just turns blue and nothing happens anymore.

A switch to the console shows that the process kbdmode is in state D, if you run ps aux.

However it is possible to install Ubuntu 6.06.1 in eypertmode, and do all the configuration stuff
when the installation is done after the installation Ubuntu runs stable.

The problem in expert mode is, that it horribly detects any hardware component wrong, so it suggest
the module "floppy" for the network card and all other hardware, despite the fact that the kernel *has* the correct
Module which is "bnx2" after manually adding it after the installation the network card works without problems

Bios Version on Installation was 09/2006
I used the ubuntu Server Image and also tried the Ubuntu Server AMD64 Image both with the same results

[Colin Watson (cjwatson)]

A process hanging in the D state suggests a kernel bug or a hardware problem, really. Have you tried Ubuntu 6.10 on this hardware?

You misunderstand expert mode - the prompts are just offering you basically every module available at that point. The hardware detection in expert mode is no different under the hood than that in normal mode; just hitting Enter to prompts in expert mode without changing the selection is basically equivalent to normal mode. Since expert mode is only for experts, I don't consider minor UI problems like this to be bugs.

[Carsten Menke (carsten-menke)]

No, because this system is in production. I just thought as 6.0.6 has Long Term Support that I mention this.

Would it help if I hook a IDE Drive into the server and try to install 6.10 or 7 to get the installer Problem solved?
I can get the system down for maintance on sundays

[Colin Watson (cjwatson)]

Sure, that sounds like it would help. Thanks.

[Josué Alcalde González (josuealcalde)]

I confirm this bug.
I am having same problems: I have tried alternate and desktop installation and both hangs.

[Josué Alcalde González (josuealcalde)]

This bug is caused by a known problem in USB port caused by iLO (a HP technology) and is solved in last dapper kernel.
Instalation has an old kernel but the problem can be solved removing the usb module: uhci_hcd

$ modprobe -r uhci_hcd

Then you can update to last kernel.

There is more information in the bug #55495 and I will mark this as a duplicate.

[Carsten Menke (carsten-menke)]

I do not think this is a duplicate, because USB was working for me, I do not have tried to use the Virtual Keyboard and the Install medium was not in a USB CDrom but was in a normal IDE CDROM drive build into the server.

2. This is not a duplicate because we need a new Install Version then, including the new kernel, as it is not possible to flawlessly install Dapper on a HP ML-350 G5, however I'm uncertain that this is related to the usb-uhci module and we would have to check if a new Installer Version would fix this issue or if the issue is still present.

[Josué Alcalde González (josuealcalde)]

Sorry, perhaps I haven't explain correct.

I also have and IDE CDROM, USB also works and I don't need HP VIrtual Keyboard or iLO or whatever it is. I have the same server, the same model.

It is better to tell you my sad history with this machine and its happy end :)

1. I had to install Ubuntu 6.06 in a HP ML-350 G5 (I usually install a complete ubuntu with gnome because people in my work doesn't know too much about linux and sometimes they must use it, and it is also easy for me).
2. I tried live CD and it hangs in "keyboard layout" step.
3. Dapper is the first Ubuntu with ubiquity and it was also the first time I install ubuntu for 64 bits, so I tried alternate CD. Of course, it also hangs in the same step.
4. I tried different keyboards usb/ps2 and of course, it did not work.
5. Then, I found the kbd-chooser process in a D state and found this bug.
6. Then, I install it using expert mode but something went wrong because any step asked me for the user name so I tried using "Rescue Mode"
7. Then, I found the problem in bug #55495 with a loop in a kernel module and a lot of messages in console. Using "Rescue Mode" shows you al the messages from the kernel in console (a problem when there is a loop). It could be solved removing the uhci_hcd module, but you lost usb. It was not a big problem because it was solved in a new kernel, but you can not update the kernel in your instalation cd. The best workaround, lost your usb removing the module until you install and update your kernel.
8. As my installation was a little broken, I did not have a user to login and rescue mode was unusable because messages were flooding my consoles, I started again with the live cd.
9. I had the idea to remove uhci_hcd and try ubiquity again and it worked perfectly (of course, i had not usb support during installation).
10. Once it was installed, I update my kernels and the problem was off.

So then, my conclusions were:
1. There is no problem with kbd-chooser, it is a loop in a kernel module which causes a hang in kbd-chooser.
2. This bug already exists as 55495
3. This bug is already solved but the state is triaged because of old kernel in instalation cds.
4. There is a workaround to install dapper, remove the uhci_hcd until you install and update your kernel