On 07/06/2011 10:58 AM, Jimmy Cullen wrote:
> Before changing kernels, I would run an openSUSE liveCD to test if it
> sees the USB3 device. Its a quick and simple way to rule out a
> hardware problem.
>
> Jimmy
>
> On 6 July 2011 18:34, Yasha Karant<[log in to unmask]> wrote:
>> I have been attempting to get a USB 3 external disk to work under X86-64 SL
>> 6 . lsusb reports a USB 3 port. However, when the drive is inserted into
>> the USB 3 port, lsusb simply hangs and the drive does not appear nor mount.
>>
>> On hardware using the same motherboard and processor as my workstation, we
>> also have installed OpenSUSE current (not Enterprise SUSE that is the
>> competitor to RHEL, e.g., SL). The USB 3 external disk works and is seen as
>> USB 3.
>>
>> Here is a copy of the relevant typescript:
>>
>> Script started on Wed 06 Jul 2011 04:19:19 PM PDT
>> ^[]2;admin@ahprc1:~^G^[]1;ahprc1^Gadmin@ahprc1:~> lsusb
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 003 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
>> Bus 004 Device 002: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000
>> V1.0
>> Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 008 Device 002: ID 152d:0551 JMicron Technology Corp. / JMicron USA
>> Technology Corp.
>> ^[]2;admin@ahprc1:~^G^[]1;ahprc1^Gadmin@ahprc1:~> uname -a
>> Linux ahprc1 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100
>> x86_64 x86_64 x86_64 GNU/Linux
>> ^[]2;admin@ahprc1:~^G^[]1;ahprc1^Gadmin@ahprc1:~> mount
>> devtmpfs on /dev type devtmpfs
>> (rw,relatime,size=4056988k,nr_inodes=1014247,mode=755)
>> tmpfs on /dev/shm type tmpfs (rw,relatime)
>> devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
>> /dev/sda5 on / type ext2 (rw,relatime,errors=continue,user_xattr,acl)
>> proc on /proc type proc (rw,relatime)
>> sysfs on /sys type sysfs (rw,relatime)
>> debugfs on /sys/kernel/debug type debugfs (rw,relatime)
>> /dev/sda7 on /home type ext2 (rw,relatime,errors=continue,user_xattr,acl)
>> securityfs on /sys/kernel/security type securityfs (rw,relatime)
>> fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
>> gvfs-fuse-daemon on /home/admin/.gvfs type fuse.gvfs-fuse-daemon
>> (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
>> /dev/sdb7 on /media/_usr_local type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> /dev/sdb6 on /media/_vmware type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> /dev/sdb1 on /media/9aaab62a-50eb-4a36-a95c-02ed44d27881 type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> /dev/sdb8 on /media/_opt1 type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> /dev/sdb12 on /media/88b09855-c009-4cbd-b055-5bda1ec6d432 type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> /dev/sdb3 on /media/_home1 type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> /dev/sdb11 on /media/_usr11 type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> /dev/sdb9 on /media/68cc9e91-1115-4eeb-8e55-bf0f22f6ac26 type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> /dev/sdb5 on /media/167ee03e-960b-4c7e-8aba-b62f49d13834 type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> /dev/sdb2 on /media/848f55af-9e8c-4f46-bf62-5fd2eb577eb6 type ext2
>> (rw,nosuid,nodev,relatime,errors=continue,uhelper=udisks)
>> ^[]2;admin@ahprc1:~^G^[]1;ahprc1^Gadmin@ahprc1:~> exit
>> exit
>>
>> Script done on Wed 06 Jul 2011 04:20:20 PM PDT
>>
>> Although the account is called "admin", admin is just a regular user on the
>> machine upon which the output was generated; I did not need to use any root
>> privileges.
>>
>> A significant difference between the two machines is the kernel:
>>
>> 2.6.37.1-1.2-desktop x86_64 for OpenSUSE
>>
>> and
>>
>> 2.6.32-131.2.1.el6.x86_64 for SL 6
>>
>> 2.6.37 seems to work, 2.6.32 does not .
>>
>> Can I install a 2.6.37 x86_64 kernel on SL 6? If it does not boot, will
>> grub during boot give me the usual option of selecting the kernel to boot
>> and boot the existing 2.6.32 kernel?
>>
>> Yasha Karant
>>
I did a different test, and have isolated the problem to be a kernel bug.
Details:
We have a number of workstations that have identical motherboards, CPUs,
etc. All are running X86-64 implementations, including the kernel. On
one of these we are running OpenSUSE as I documented earlier, and this
works fine. On mine, I am running the most recent SL 6 production
kernel. On another, because we have not done an update, we are running
an earlier SL 6 production kernel, 2.6.32-71.29.1.el6.x86_64, and the
USB 3 device is at least recognized. To make this work with this kernel
and our configuration, I needed to do a
modprobe xhci_hcd
and then the devices were seen (the USB 3 hub and the external harddrive
unit).
I copied the necessary /lib/modules directory as well as the appropriate
files into /boot
from the working USB 3 system to my workstation. I then modified
grub.conf to allow these files to boot, and rebooted. As you can see
below, after the same modprobe command, USB 3 is seen. I still cannot
get the harddrive to mount -- no /dev/sde is autocreated -- but at least
the basic hardware is there. Thus, I conclude that the later kernel
2.6.32-131.2.1.el6.x86_64 has a bug compared to the earlier
2.6.32-71.29.1.el6.x86_64 . Should I simply change to the still later
OpenSUSE kernel or is there another solution?
Also, in RHEL 6, what is needed for the automatic creation of /dev/sdX
where X is appropriate for a USB drive (e.g., /dev/sde automatically
created on my particular workstation).
Output of lsusb verifying presence of USB 3 attached device.
[root@jb344 2.6.32-71.29.1.el6.x86_64]# lsusb
Bus 008 Device 002: ID 152d:0551 JMicron Technology Corp. / JMicron USA
Technology Corp.
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 03f0:0317 Hewlett-Packard LaserJet 1200
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Yasha Karant
Aside: technical netiquette threading question. In a non-threaded
environment, in this reply to email I am hereby posting, I would have
changed the subject to:
USB3 works under earlier SL6 kernel (was Re: USB 3 external disk works
under OpenSUSE current)
However, if I were to do this, would I not cause issues with the way
threaded readers work? The new subject is more informative, and is not
really a new thread.
|
