On Wed, 2008-09-17 at 16:01 +0300, Pasi Kärkkäinen wrote: > Except that it's even worse with RHEL4.x. With RHEL5.x console keyboard > repeats every character twice, but with RHEL4.x console keyboard is totally > dead > after loading qla4xxx module. > > Obviously using RHEL installer (we're booting from iSCSI SAN, so we need to > have the > HBA plugged in straight from the beginning) is a pain with this problem.. > can't type any IP addresses, it's difficult to choose anything etc.. > > Basicly scripted kickstart installs are the only way to get RHEL installed > into > HS21 blades with QMC4052 HBA.. at least before this bug is fixed, where ever > the problem actually is..
We actually completed our two installs via a serial-over-LAN connection through the Bladecenter management module. It was a little difficult to set up the first time (not really that difficult, IBM has a nice SoL setup guide, but we had a few issues getting SOL to activate on our particular blade due to old firmware on the onboard ethernet). In the end, this provides the added benefit of out-of-band access to the console even after install. Just SSH (or telnet) to the management module and start a Serial-over-LAN session to the specific blade. This is certainly an annoying bug, and one that I haven't been able to get much attention to in my support case, but it's admittedly been "waiting on customer" because they don't feel like they have to do anything until after I test the "latest" kernel and I haven't been able to schedule downtime to get this latest kernel booted. It's nice to know I'm not the only one with the problem. Later, Tom _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
