topic Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series in Operating System - Linux

Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Tue, 02 Nov 2004 09:21:06 GMT

I recently attempted to install RH ES3 on a Compaq Evo D51s/P253 and encountered a strange situation. The install completed normally and the box now boots without trouble, but the PS2 keyboard and mouse do not respond. Since the NIC is already configured and sshd turned on I can reach the box via the network, but I cannot get it to respond to the console. I have replicated this situation on another Evo, this time a model D51s/P1.8. Both systems recognize the keyboard, but not the mouse, if they are booted in rescue mode.

This poses a more than modest operational risk in that if the NIC configuration becomes obsolete or corrupted the system will be unreachable, so I cannot put the device into service. Has anyone encountered anything similar and if so what was the resolution?

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

Steven E. Protter — Tue, 02 Nov 2004 10:18:54 GMT

This thread may provide some insights.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=721759

SEP

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Tue, 02 Nov 2004 12:14:07 GMT

I cannot see the relationship between the reference thread and my problem, but that may be a matter of ignorance on my part. What is common between running Fedora on a laptop with a wireless connection problem and a PS2 keyboard failure on a desktop running ES3? I ran lspci but I cannot for the life of me see anything that refers to either keyboard or mouse. What am I missing?

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Tue, 02 Nov 2004 12:37:17 GMT

However, here is the output of lspci. Is it possible that there is a resource conflict between say the USB devices and the PS2 interface?

# lspci
00:00.0 Host bridge: Intel Corp. 82845G/GL [Brookdale-G] Chipset Host Bridge (rev 01)
00:02.0 VGA compatible controller: Intel Corp. 82845G/GL [Brookdale-G] Chipset Integrated Graphics Device (rev 01)
00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 01)
00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 01)
00:1d.7 USB Controller: Intel Corp. 82801DB USB2 (rev 01)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corp. 82801DB LPC Interface Controller (rev 01)
00:1f.1 IDE interface: Intel Corp. 82801DB Ultra ATA Storage Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corp. 82801DB AC'97 Audio Controller (rev 01)
05:08.0 Ethernet controller: Intel Corp. 82801BD PRO/100 VM (LOM) Ethernet Controller (rev 81)

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Tue, 02 Nov 2004 12:49:34 GMT

I have also included the output of dmesg below:

Linux version 2.4.21-4.EL (bhcompile@daffy.perf.redhat.com) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-20)) #1 Fri Oct 3 18:13:58 EDT 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003f7f0000 (usable)
BIOS-e820: 000000003f7f0000 - 000000003f800000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
119MB HIGHMEM available.
896MB LOWMEM available.
On node 0 totalpages: 260080
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 30704 pages.
Kernel command line: ro root=/dev/vg00/LogVol00
Initializing CPU#0
Detected 2525.252 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 5033.16 BogoMIPS
Memory: 1018752k/1040320k available (1524k kernel code, 18048k reserved, 1086k data, 164k init, 122816k highmem)
zapping low mappings.
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: bfebfbff 00000000 00000000 00000000
CPU: Common caps: bfebfbff 00000000 00000000 00000000
CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz stepping 07
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
Process timing init...done.
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.20 entry at 0xeca9c, last bus=5
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
Transparent bridge - Intel Corp. 82801BA/CA/DB/EB PCI Bridge
PCI: Using IRQ router PIIX [8086/24c0] at 00:1f.0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS not found.
Total HugeTLB memory allocated, 0
Starting kswapd
allocated 32 pages and 32 bhs reserved for the highmem bounces
VFS: Disk quotas vdquot_6.5.1
aio_setup: num_physpages = 65020
aio_setup: sizeof(struct page) = 56
Hugetlbfs mounted.
pty: 2048 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS0 at 0x03f8 (irq = 4) is a 16550A
ttyS1 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
NET4: Frame Diverter 0.46
RAMDISK driver initialized: 256 RAM disks of 8192K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH4: IDE controller at PCI slot 00:1f.1
PCI: Enabling device 00:1f.1 (0005 -> 0007)
PCI: Assigned IRQ 10 for device 00:1f.1
ICH4: chipset revision 1
ICH4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x24a0-0x24a7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x24a8-0x24af, BIOS settings: hdc:DMA, hdd:pio
hda: Maxtor 6Y080L0, ATA DISK drive
blk: queue c0417e80, I/O limit 4095Mb (mask 0xffffffff)
hdc: HL-DT-STDVD-ROM GDR8162B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=10337/240/63, UDMA(100)
ide-floppy driver 0.99.newide
Partition check:
hda: hda1 hda2 hda3
ide-floppy driver 0.99.newide
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
Initializing IPsec netlink socket
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 427k freed
VFS: Mounted root (ext2 filesystem).
LVM version 1.0.5+(22/07/2002) module loaded
Journalled Block Device driver loaded
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 164k freed
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 18:21:59 Oct 3 2003
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 11 for device 00:1d.0
PCI: Sharing IRQ 11 with 00:02.0
PCI: Setting latency timer of device 00:1d.0 to 64
usb-uhci.c: USB UHCI at I/O 0x2440, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 5 for device 00:1d.1
PCI: Setting latency timer of device 00:1d.1 to 64
usb-uhci.c: USB UHCI at I/O 0x2460, IRQ 5
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
PCI: Found IRQ 10 for device 00:1d.7
PCI: Setting latency timer of device 00:1d.7 to 64
ehci-hcd 00:1d.7: Intel Corp. 82801DB USB2
ehci-hcd 00:1d.7: irq 10, pci mem f8884000
usb.c: new USB bus registered, assigned bus number 3
ehci-hcd 00:1d.7: enabled 64bit PCI DMA
PCI: 00:1d.7 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
PCI: 00:1d.7 PCI cache line size corrected to 128.
ehci-hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22
hub.c: USB hub found
hub.c: 6 ports detected
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
EXT3 FS 2.4-0.9.19, 19 August 2002 on lvm(58,0), internal journal
loop: loaded (max 8 devices)
Adding Swap: 1050832k swap-space (priority -1)
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
IA-32 Microcode Update Driver: v1.11
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
inserting floppy driver for 2.4.21-4.EL
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Intel(R) PRO/100 Network Driver - version 2.3.13-k1-1
Copyright (c) 2003 Intel Corporation

PCI: Found IRQ 5 for device 05:08.0
divert: allocating divert_blk for eth0
e100: selftest OK.
e100: eth0: Intel(R) PRO/100 Network Connection
Hardware receive checksums enabled

divert: freeing divert_blk for eth0
ip_tables: (C) 2000-2002 Netfilter core team
Intel(R) PRO/100 Network Driver - version 2.3.13-k1-1
Copyright (c) 2003 Intel Corporation

PCI: Found IRQ 5 for device 05:08.0
divert: allocating divert_blk for eth0
e100: selftest OK.
e100: eth0: Intel(R) PRO/100 Network Connection
Hardware receive checksums enabled

ip_tables: (C) 2000-2002 Netfilter core team
e100: eth0 NIC Link is Up 100 Mbps Full duplex
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
lp0: using parport0 (polling).
lp0: console ready

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

Johannes Krackowizer_1 — Wed, 03 Nov 2004 03:59:53 GMT

hi james,

did you talk to hp support is linux certified on this machines? you could try to update bios.
some older bioses abroad all manufactures have some problems with keyboards that needs 35mA to operate. did you get screen but keyboard does not respond or is the screen also blank?

another try is to disable usb-keyboard/mouse support in bios and very important is to disable usb emulate port60/64 support. on all machines i have tried to enable this emulation only usb keyboards and mice would work correctly.

best regards,

johannes

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Wed, 03 Nov 2004 09:00:40 GMT

The Compaq D510 series is not listed in the Linux HC guide so I presume this configuration is not HP "supported."

The keyboard and mouse (both PS/2) do not respond in normal boot mode but the monitor and NIC work fine. If the system is booted in linux rescue mode then the keyboard works but the mouse does not. In rescue mode I can chroot to the /mnt/sysimage but changes to the system nic configuration while in rescue mode do not seem to persist to the next normal boot.

The BIOS for this machine was updated to the latest available from HP immediately prior to installing Redhat Linux.

I have discoverd that an USB keyboard is recognized by this system but that an USB mouse is not, or at least the USB Logitech optical scroll mouse that I have is not. So, I now have keyboard access to the system but no mouse and thus no (useable) XWindows client or desktop. This is inconvenient but not fatal to my needs.

I would still like to know what is going on however since it seems strange that the keyboard is recognized in one boot mode and not in another and that a mouse is unavailable regardless of what configuration of OS and hardware is used.

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

Johannes Krackowizer_1 — Wed, 03 Nov 2004 09:07:43 GMT

hi,

try redhat-config-mouse, redhat-config-keyboard to reconfigure mouse and keyboard. perhaps this will bring your mouse up.

best regards,

johannes

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Wed, 03 Nov 2004 09:18:42 GMT

I tried these with the PS/2 configuration but I never throught to retry them with the USB mouse and keyboard. When I have physical access again I will run these with the new physical devices attached.

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

Johannes Krackowizer_1 — Wed, 03 Nov 2004 12:56:03 GMT

try them to run them remote in textmode.

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Wed, 03 Nov 2004 14:09:17 GMT

Ah. But they are not presently physically attached to the chassis. I have to do that first for them to be detected.

Thanks.

Jim

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Wed, 03 Nov 2004 14:19:14 GMT

I had a co-worker go in and attach the two USB devices and ran redhat-config-mouse. Both KB and mouse are now working in console (text) mode. I will test XWindows later but this is certainly good enough to get these things in production. Many thanks.

I will try disabling the USB port 60/64 option on the next box I set up and see if that works with respect to PS/2 devices.

Thank you very much.

Jim

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

Johannes Krackowizer_1 — Thu, 04 Nov 2004 04:27:20 GMT

hi,

normaly if textmode mouse/keyboard works keyboard should also work in X but the mouse has it's own driver in X you have to run a X configure util to switch the mouse type or edit manualy you XF86config but i don't know (now) how to do this because it's about five years ago since i did this last.

ps: it would be nice if you asign some points to answers that helps you. thanks.

best regards,

johannes

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Thu, 04 Nov 2004 23:22:43 GMT

Thanks Johannes,

I did assign points but they did not take.

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Thu, 04 Nov 2004 23:25:19 GMT

Because I pushed the wrong button! I think that my fumble fingers are now reattached to the brain stem.

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

Johannes Krackowizer_1 — Fri, 05 Nov 2004 03:18:04 GMT

hi james,

i hope this answers help. please tell me if it works under X.

best regards,

johannes

ps: thanks for the points. i'm also often don't see the right buttons also if they are as big as my screen. :-)

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

Johannes Krackowizer_1 — Fri, 05 Nov 2004 03:46:03 GMT

hi james,

i have seen an error in your dmsg output:
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }

do you see this error more often during work? if it only seen once during boot sequence it's ok. but if you get this error often during work: thats bad! to have a look at your kernel output i use the following:

vi /etc/syslog.conf
add two lines:
*.* /var/log/all
*.* /dev/tty12

restart syslogd
with this two lines you will write all messages from the kernel to /var/log/all and to tty12 press alt-f12 to see last kernel messages.

if this error means that the harddrive rejects a command. this could indicate that you have a harddrive with a buggy firmware or the drive is near death.

best regards,

johannes

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

Johannes Krackowizer_1 — Fri, 05 Nov 2004 03:46:55 GMT

ps: don't forget to make a rotate on /var/log/all if you don't than you will get a very huge logfile.

Re: Redhat Linux Enterprise 3 on Compaq Evo D51S series

JAMES B. BYRNE — Fri, 05 Nov 2004 16:03:29 GMT

Thanks for the heads up. I will take a look at this next Tuesday as I am travelling until then. The machine is not yet in production so there the risk of failure in the meantime is accepatable. This is a brand new drive so if it is going to fail it must be a manufacturing defect or damage caused by improper handling.