| Re: 3Ware 8006-2LP [message #15150 is a reply to message #15148] |
Fri, 20 July 2007 07:26   |
|
|
## LSPCI ##
[root@fa-0-1 ~]# lspci
00:00.0 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.5 PIC: VIA Technologies, Inc. P4M900 I/O APIC Interrupt Controller
00:00.6 Host bridge: VIA Technologies, Inc. P4M900 Security Device
00:00.7 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:02.0 PCI bridge: VIA Technologies, Inc. P4M900 PCI to PCI Bridge Controller (rev 80)
00:03.0 PCI bridge: VIA Technologies, Inc. P4M900 PCI to PCI Bridge Controller (rev 80)
00:0f.0 IDE interface: VIA Technologies, Inc.: Unknown device 5337 (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
00:13.0 Host bridge: VIA Technologies, Inc. VT8237A Host Bridge
00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge
01:00.0 VGA compatible controller: VIA Technologies, Inc. Chrome9 HC IGP (rev 01)
04:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
04:07.0 RAID bus controller: 3ware Inc 7xxx/8xxx-series PATA/SATA-RAID (rev 01)
## LSPCI -N ##
[root@fa-0-1 ~]# lspci -n
00:00.0 Class 0600: 1106:0364
00:00.1 Class 0600: 1106:1364
00:00.2 Class 0600: 1106:2364
00:00.3 Class 0600: 1106:3364
00:00.4 Class 0600: 1106:4364
00:00.5 Class 0800: 1106:5364
00:00.6 Class 0600: 1106:6364
00:00.7 Class 0600: 1106:7364
00:01.0 Class 0604: 1106:b198
00:02.0 Class 0604: 1106:a364 (rev 80)
00:03.0 Class 0604: 1106:c364 (rev 80)
00:0f.0 Class 0101: 1106:5337 (rev 07)
00:10.0 Class 0c03: 1106:3038 (rev a0)
00:10.1 Class 0c03: 1106:3038 (rev a0)
00:10.2 Class 0c03: 1106:3038 (rev a0)
00:10.3 Class 0c03: 1106:3038 (rev a0)
00:10.4 Class 0c03: 1106:3104 (rev 86)
00:11.0 Class 0601: 1106:3337
00:11.7 Class 0600: 1106:287e
00:13.0 Class 0600: 1106:337b
00:13.1 Class 0604: 1106:337a
01:00.0 Class 0300: 1106:3371 (rev 01)
04:04.0 Class 0200: 10ec:8139 (rev 10)
04:07.0 Class 0104: 13c1:1001 (rev 01)
It was working on the default CentOS 4.5 x64 kernel, 2.6.9-55.ELsmp.
I just wanted to see if there is a workaround, 3dm at the moment outputs.
[root@fa-0-1 ~]# 3dmd
Error: opendir() failed - No such file or directory. Check if the driver is loaded.
[root@fa-0-1 ~]# Error: opendir() failed - No such file or directory. Check if the driver is loaded.
Error: Could not initialize 3ware controller.
(error code 0) (e003/0)
However it worked before installing the 2.6.18-ovz028stab035.1-smp kernel.
Chris
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
