mail archive Technical discussion of FreeBSD on HP ProLiant server platforms.
freebsd-proliant.freebsd.org
(List home) (Recent threads) (174 other FreeBSD lists)
Subscription Options
- RSS or Atom: Read-only subscription using a browser or aggregator. This is the recommended way if you don't need to send messages to the list. You can learn more about feed syndication and clients here.
- Conventional: All messages are delivered to your mail address, and you can reply. To subscribe, send an email to the list's subscribe address with "subscribe" in the subject line, or visit the list's homepage here.
- Low traffic list: less than 3 messages per day
- This list contains about 657 messages, beginning Jul 2005
- 0 messages added yesterday
Report the Spam
This button sends a spam report to the moderator. Please use it sparingly. For other removal requests, read this.
Are you sure? yes no
Keyboard Curiosity
Ad
I have an HP ProLiant ML110 G6 Server on which I've installed and configured
FreeBSD v7.4-RELEASE.
Though the computer auto-boots uneventfully, I have never been able to
interact with the boot loader as no keyboard action is, while it's resident,
recognized.
I have tried a number of different keyboards (101-key, 102-key, 104-key;
PS/2, USB; with and without interface adapters) without result.
I find that if I attempt, continuously while booting, to toggle (for
example) the CapsLock key that there is a period during the boot process
where the associated CapsLock LED ceases toggling in response.
The period begins at the moment the boot manager's boot-slice selection is
satisfied (either via user action or timeout).
The period ends midway through the loading of the kernel; perhaps as early
as status message
... kernel: kbd2 at ukbd0
but, certainly, no later than status message
... kernel: sc09: <System console> at flags 0x100 on isa0
though it's difficult to discern as they go by quickly.
Any suggestions as to how this might be resolved would be appreciated.
Try to log into server via ILO port / web gui or via telnet/ then to use iLO to get on server when it is booting ... User guide for iLO 2 you can find on location: http://bizsupport1.austin.hp.com/bc/docs/supp... (Page 95 of 224) Text-based remote console overview iLO and its predecessors support a true text-based remote console. Video information is obtained from the server and the contents of the video memory are sent to the management processor, compressed, encrypted, and forwarded to the management client application. iLO uses a screen-frame buffer, which detects changes in text information, encrypts the changes, and sends the characters (including screen positioning information) to text-based client applications. This method provides compatibility with standard text-based clients, good performance, and simplicity. However, you cannot display non-ASCII or graphical information, and screen positioning information (displayed characters) might be sent out of order. The Remote Console uses Virtual KVM and does not provide a true text-based console. iLO 2 uses the video adapter DVO port to access video memory directly. This method significantly increases iLO 2 performance. However, the digital video stream does not contain useful text data. Data obtained from the DVO port represents graphical data (non-character-based), and is not comprehensible ASCII or text data. This video data cannot be rendered by a text-based client application such as Telnet or SSH. Text-based console during POST The standard iLO 2 text-based remote console remains available on iLO 2 until the operating system POST is complete. iLO 2 standard firmware continues to use the virtualized serial-port functionality of the management processor. On the iLO 2 firmware, the virtual serial port was renamed Remote Serial Console. iLO 2 uses the Remote Serial Console to access a pre-operating system, text-based iLO 2 Remote Console 95 remote console. The iLO 2 Remote Serial Console applet appears as a text-based console, but the information is rendered using graphical video data. iLO 2 displays this information through the remote console applet while in the server pre-operating system state, enabling a non-licensed iLO 2 to observe and interact with the server during POST activities. For an iLO 2 blade (and an iLO blade running Linux in a graphical format), enter getty() on the server's serial port, and then use iLO 2 Remote Serial Console or iLO Virtual Serial Port (CLP command start /system1/oemhp_vsp1) to view a login session to the Linux operating system through the serial port. A non-licensed iLO 2 cannot use Remote Console access after the server completes POST and begins to load the operating system. To use Remote Console and iLO Text Console after POST, you must have an iLO 2 Advanced or iLO 2 Advanced for BladeSystem. BR. Mladen ... -----Original Message----- From: On Behalf Of MCVenner Sent: 22. marec 2012 15:34 To: Subject: Keyboard Curiosity I have an HP ProLiant ML110 G6 Server on which I've installed and configured FreeBSD v7.4-RELEASE. Though the computer auto-boots uneventfully, I have never been able to interact with the boot loader as no keyboard action is, while it's resident, recognized. I have tried a number of different keyboards (101-key, 102-key, 104-key; PS/2, USB; with and without interface adapters) without result. I find that if I attempt, continuously while booting, to toggle (for example) the CapsLock key that there is a period during the boot process where the associated CapsLock LED ceases toggling in response. The period begins at the moment the boot manager's boot-slice selection is satisfied (either via user action or timeout). The period ends midway through the loading of the kernel; perhaps as early as status message ... kernel: kbd2 at ukbd0 but, certainly, no later than status message ... kernel: sc09: <System console> at flags 0x100 on isa0 though it's difficult to discern as they go by quickly. Any suggestions as to how this might be resolved would be appreciated. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Keyboard... Sent from the freebsd-proliant mailing list archive at Nabble.com.
While I was aware of the existence of the management port, I'd regarded it a
daunting distraction (ref. "IPMI", "BMC", "ILO", and a 224-page manual to
explain it all). Your suggestion inspired me to revisit the thing, if only
for a brief while.
At least the enabling and disabling of my keyboard (the original problem) is
repeatable. A constant background pinging of my computer's management port
showed it to go on and off network for no apparent reason. During the
periods it was active, an HTML client afforded nothing more than a
"settings" interface and a Telnet client never yielded anything more than a
"/./->" prompt (though for what I do not know). The only thing that seemed
remotely consistent was that the interface would go down a soon as the
kernel began loading.
If there is truly light at the end of this tunnel then, I'm afraid, I just
cannot see it right now.
Thanks, though, for replying.
----- Original Message ----- From: MCVenner [via FreeBSD] To: salster420 Sent: Thursday, March 22, 2012 3:33 PM Subject: Keyboard Curiosity I have an HP ProLiant ML110 G6 Server on which I've installed and configured FreeBSD v7.4-RELEASE. Though the computer auto-boots uneventfully, I have never been able to interact with the boot loader as no keyboard action is, while it's resident, recognized. I have tried a number of different keyboards (101-key, 102-key, 104-key; PS/2, USB; with and without interface adapters) without result. I find that if I attempt, continuously while booting, to toggle (for example) the CapsLock key that there is a period during the boot process where the associated CapsLock LED ceases toggling in response. The period begins at the moment the boot manager's boot-slice selection is satisfied (either via user action or timeout). The period ends midway through the loading of the kernel; perhaps as early as status message ... kernel: kbd2 at ukbd0 but, certainly, no later than status message ... kernel: sc09: <System console> at flags 0x100 on isa0 though it's difficult to discern as they go by quickly. Any suggestions as to how this might be resolved would be appreciated. If you reply to this email, your message will be added to the discussion below: http://freebsd.1045724.n5.nabble.com/Keyboard... To start a new topic under freebsd-proliant, email To unsubscribe from freebsd-proliant, click here. NAML Greetings, I had some issuses with this and found out that with this system is was a little buggy, Until,after making the RAID volume with the E200i controller, you needed for the system to finish with building the volume. After it seemed to install FreeBSD and Work correctly. You have to let this system stay on for about 4 hours and then reboot and check the status of the RAID controller, ADU Report 1. if the battery is charged 2. Most important the RAID is done building. or else it really makes this crazy stuff [DeviceStatusSmart Array E200 in slot 4 The cache is temporarily disabled Logical Drive 1 Background parity initialization is currently queued or in progress on this logical drive. If background parity initialization is queued, it will start when I/O is performed on the drive. When background parity initialization completes, the performance of the logical drive will improve.] WOuld boot with not keyboard at worse, not instal all the packages. 3. you need to update the SYSTEM BIOS / and BMC as well as the controller BIOS. Let me know more about the HW details from the HP Survey. then I can check it with the two Testing Proliant ML110's I have here in the Lab. ----- Salster420 Ticino FreeBSD Advocacy
Thanks for responding but my FreeBSD server has but a single hard drive (SATA) connected to a controller configured (via BIOS) in Compatible (not RAID) mode. It's hard for me to imagine that this is a hardware issue. The keyboard works until a very specific point in the FreeBSD boot sequence, at which point it ceases working. Then, at a very specific subsequent point in the boot sequence, it resumes working. Thereafter, it does not, again, fail to work. It's been going on -- invariably -- since I installed the O/S two months ago. Moreover; I have an identical platform on which I'm running Ubuntu (11.10) Linux with no inability to interact with its loader. Nonetheless; I am providing my 'HP Survey' as requested. http://freebsd.1045724.n5.nabble.com/file/n55... survey.html