Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: dilligaf on November 30, 2005, 02:51:20 PM
-
I could really use some help if anyone can advise what to do to try and resolve this problem:
I have two exact machines hardware wise.
One of them is giving problem not seeing all the USB.
(I have a REV Drive on both, one sees it the other doesn't)
I show this :
[root@wrpserver root]# lspci -v|grep HCI
00:1d.0 USB Controller: Intel Corp.: Unknown device 24d2 (rev 02) (prog-if 00 [UHCI])
00:1d.1 USB Controller: Intel Corp.: Unknown device 24d4 (rev 02) (prog-if 00 [UHCI])
00:1d.2 USB Controller: Intel Corp.: Unknown device 24d7 (rev 02) (prog-if 00 [UHCI])
00:1d.7 USB Controller: Intel Corp.: Unknown device 24dd (rev 02) (prog-if 20 [EHCI])
On the machine that sees the REV drive, if I do this:
[root@specsmeserver root]# cdrecord --scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
scsibus0:
0,0,0 0) 'Iomega ' 'RRD ' '95.B' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
[root@specsmeserver root]#
On the server that does not work:
[root@wrpserver root]# cdrecord --scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
-
dilligaf,
(0) What "identical" hardware are you using...?
(1) Please show lspci -v result for both machines.
(2) I assume you are using SME 6.x ?
IF the machines are really "IDENTICAL"
My crystal ball offers two wild guesses:
(i) that you do not use "identical" ports/plugs...
Like many USB ports on front and back of PC-Boxes,
do connect to different chips and the back often
supports USB 2 while front still is USB 1
... most prominently on INTEL (server) mainboards!
(ii) you have disabled USB (or one of the usb chips) on one of the mainboards in the BIOS !
Regards
Reinhold
-
dilligaf,
Actually re-reading your post at:
[root@wrpserver root]# lspci -v|grep HCI
00:1d.0 USB Controller: Intel Corp.: Unknown device 24d2 (rev 02) (prog-if 00 [UHCI])
00:1d.1 USB Controller: Intel Corp.: Unknown device 24d4 (rev 02) (prog-if 00 [UHCI])
00:1d.2 USB Controller: Intel Corp.: Unknown device 24d7 (rev 02) (prog-if 00 [UHCI])
00:1d.7 USB Controller: Intel Corp.: Unknown device 24dd (rev 02) (prog-if 20 [EHCI])
... I feel quite sure that wild guess no. 2 is at least partially valid...
Why? USB controllers 3...6 are missing in that list... _and_ you have EHCI and UHCI chip(s) so my above 2 chip assumption is valid...
in addition USB chips (usually) give you packs of 4 sockets so the above remains strange indeed...
Enough guesswork 4 now :-D
Regards
Reinhold
-
dilligaf,
Actually re-reading your post at:
[root@wrpserver root]# lspci -v|grep HCI
00:1d.0 USB Controller: Intel Corp.: Unknown device 24d2 (rev 02) (prog-if 00 [UHCI])
00:1d.1 USB Controller: Intel Corp.: Unknown device 24d4 (rev 02) (prog-if 00 [UHCI])
00:1d.2 USB Controller: Intel Corp.: Unknown device 24d7 (rev 02) (prog-if 00 [UHCI])
00:1d.7 USB Controller: Intel Corp.: Unknown device 24dd (rev 02) (prog-if 20 [EHCI])
... I feel quite sure that wild guess no. 2 is at least partially valid...
Why? USB controllers 3...6 are missing in that list... _and_ you have EHCI and UHCI chip(s) so my above 2 chip assumption is valid...
in addition USB chips (usually) give you packs of 4 sockets so the above remains strange indeed...
Enough guesswork 4 now :-D
Regards
Reinhold
Hello, it is a very strange situation,
what I find now, is on the one server, if I unplug the power to the rev drive, and then plug it back in, and then do the cdrecord --scanbus, it shows the REV Drive.
-
dilligaf,
Actually re-reading your post at:
[root@wrpserver root]# lspci -v|grep HCI
00:1d.0 USB Controller: Intel Corp.: Unknown device 24d2 (rev 02) (prog-if 00 [UHCI])
00:1d.1 USB Controller: Intel Corp.: Unknown device 24d4 (rev 02) (prog-if 00 [UHCI])
00:1d.2 USB Controller: Intel Corp.: Unknown device 24d7 (rev 02) (prog-if 00 [UHCI])
00:1d.7 USB Controller: Intel Corp.: Unknown device 24dd (rev 02) (prog-if 20 [EHCI])
... I feel quite sure that wild guess no. 2 is at least partially valid...
Why? USB controllers 3...6 are missing in that list... _and_ you have EHCI and UHCI chip(s) so my above 2 chip assumption is valid...
in addition USB chips (usually) give you packs of 4 sockets so the above remains strange indeed...
Enough guesswork 4 now :-D
Regards
Reinhold
Reinhold, on an completely different server all together, I ran that, and it shows the same thing (the missing controllers)
[root@merlin root]# lspci -v|grep HCI
00:1d.0 USB Controller: Intel Corp.: Unknown device 24d2 (rev 02) (prog-if 00 [UHCI])
00:1d.1 USB Controller: Intel Corp.: Unknown device 24d4 (rev 02) (prog-if 00 [UHCI])
00:1d.2 USB Controller: Intel Corp.: Unknown device 24d7 (rev 02) (prog-if 00 [UHCI])
00:1d.3 USB Controller: Intel Corp.: Unknown device 24de (rev 02) (prog-if 00 [UHCI])
00:1d.7 USB Controller: Intel Corp.: Unknown device 24dd (rev 02) (prog-if 20 [EHCI])
-
dilligaf,
There is one complete chip with all it's 4 USBs (0,1,2,3) and one more at adr. 7... which is EHCI
Seems (a little nonmainstream but) OK!
Note: What you show is only a complaint by Linux that it doesn't know the devices and did not install
a driver - at that point.
- There is much more elsewhere and it could even be completely functional!
Also note that there are single USB ports in some chips. Mainly on INTEL mainboards...
Regards
Reinhold
-
dilligaf,
Not sure your case is solved now:
Please post the data we need to know!
What mainboard is this?!
Did you look into the BIOS for activation ?
Regards
Reinhold
-
dilligaf,
Not sure your case is solved now:
Please post the data we need to know!
What mainboard is this?!
Did you look into the BIOS for activation ?
Regards
Reinhold
Hi,
All three are the ASUS P4P800 SE boards
I have experimented and gone in the bios under USB and changed from all ports, to 8. to 4 etc to see the effect it has when you scan and it indeed is as you say, the ports are there.
I have it narrowed down to having to unplug power from the usb drive, and plug back in, then cdrecord --scanbus sees it.
Basically it looks like it does not see the device initially.