Arch Linux

wpjsolo

Member

Registered: 2013-08-27

Posts: 5

Still Can't Use Super Top M6116 SATA Bridge

Early Discussion refer to :

https://bbs.archlinux.org/viewtopic.php?id=152011

I have an Hard Disk ,lsusb :
Bus 001 Device 004: ID 14cd:6116 Super Top M6116 SATA Bridge

I can't mount it in newest Arch .   After pacman -Syu

uname -ar
Linux WPJSOLO 3.10.9-1-ARCH #1 SMP PREEMPT Wed Aug 21 13:49:35 CEST 2013 x86_64 GNU/Linux

What I can do to mount my Hard Disk without recompile kernel?

gmoraesalvarez

Member

Registered: 2013-10-22

Posts: 5

Re: Still Can't Use Super Top M6116 SATA Bridge

I can confirm the bug still affects me with 3.11.6-1-ARCH x86_64. I have additional machines and the latest working kernel I can confirm with my device (bcdDevice 1.50) is 3.2 from a Lubuntu netbook I have.

I'm pretty sure there is no workaround for this. So you'll have to recompile. I still don't understand why this hasn't been corrected upstream yet.

linux-git 3.12.rc6.3.g0df651a-1 seems to have applied a correction, though. Compiling it now.

wpjsolo

Member

Registered: 2013-08-27

Posts: 5

Re: Still Can't Use Super Top M6116 SATA Bridge

Thanks for you attention!
I'm glad to see the news that it will be fixed in future kernel(3.12).
I also notice a strange thing :
If you plug in the device before boot the system, it sometimes can be mount correctly.

gmoraesalvarez

Member

Registered: 2013-10-22

Posts: 5

Re: Still Can't Use Super Top M6116 SATA Bridge

Well, It happens that what I thought was a correction is not. So no luck coming to 3.12.
I'm testing kernels down to 3.1.9-2 to see when it started going downhill and hopefully find what patch started this mess. As I said my old lubuntu kernel 3.2.0 works just fine.
I noticed that on 3.6.9-1, for example, it mounts fine and I can copy files from tty2 mounting from commandline, the drive plugged in from boot. As soon as I enter xfce the drive starts spitting errors. On newer kernels I can't mount even like that.
I'm still testing kernels and now gvfs as well. I'll come back to post results as soon as I have something solid.

gmoraesalvarez

Member

Registered: 2013-10-22

Posts: 5

Re: Still Can't Use Super Top M6116 SATA Bridge

Ok. The issue, at the very least in my case, is entirely with gvfs. Unninstalling it and mounting from terminal works fine on any kernel.

edit: going back to gvfs 1.12 (which works fine on my lubuntu netbook) with kernel 3.11 does not solve the issue. So it seems to be a kernel/gvsf relationship issue. Gonna test older kernel+older gvfs next.

Last edited by gmoraesalvarez (2013-10-23 23:44:55)

wpjsolo

Member

Registered: 2013-08-27

Posts: 5

Re: Still Can't Use Super Top M6116 SATA Bridge

https://github.com/raspberrypi/linux/issues/230
I find this page, and some bug links in it .
It seems that it's a bug of ums_cypress module.
I'm not sure why the developer add this line:
UNUSUAL_DEV( 0x14cd, 0x6116, 0x0000, 0x9999,
    "Super Top",
    "USB 2.0  SATA BRIDGE",  /* why this?*/
    USB_SC_CYP_ATACB, USB_PR_DEVICE, NULL, 0),

gmoraesalvarez

Member

Registered: 2013-10-22

Posts: 5

Re: Still Can't Use Super Top M6116 SATA Bridge

I have checked this particular piece source code. The last change to it is very old. unusual_cypress.h is inaltered at least since kernel 3.0.101. cypress_atacb.c though has plenty of changes, but it is never quoted around. I will try removing the whole line from unusual_cypress.h added in 2010 to see if it solves the issue. Compiling shall take some time. I'll return with results.

gmoraesalvarez

Member

Registered: 2013-10-22

Posts: 5

Re: Still Can't Use Super Top M6116 SATA Bridge

It works.

Same solution as in the original thread basically.

Simply comment out this and recompile.

UNUSUAL_DEV( 0x14cd, 0x6116, 0x0000, 0x0219,
        "Super Top",
        "USB 2.0  SATA BRIDGE",
        USB_SC_CYP_ATACB, USB_PR_DEVICE, NULL, 0),

I downloaded the linux-git PKGBUILD, issued 'makepkg -o PKGBUILD' to download sources, made the change in unusual_cypress.h and issued 'makepkg -e PKGBUILD' to build the package with my modified source. Then installed with 'pacman -U' (had to install linux-firmware-git first) both linux-git-headers and linux-git.

Before rebooting I created a new line on my bootloader to boot vmlinuz-linux-git instead of vmlinuz-linux and the appropriate initramfs-linux-git. The package does not remove the stable kernel.

Had amazing number of problems then recompiling nvidia modules since nvidia-hook doesn't work on my old card which uses legacy drivers (nvidia-304xx). On my other machines using open source drivers (radeon) all was fine and I didn't have to do anything besides installing the packages and adjusting the bootloader.

I still can't use the drive in any other linux machine, but it's a start. This should be taken care of upstream, I suppose. Any advice on getting them to do something is welcome.

Hope it helps.

Last edited by gmoraesalvarez (2013-10-24 15:41:57)