I have a Seagate Backup Plus 1TB external hard disk. The is a SATA disk, but it comes with a SCSI adapter plugged in it that plugs into the USB port. Kind of strange if you ask me, but the price was great, so I am trying to make this work. The only Puppy I have that supports this setup out of the box is Lighthouse Pup 64 6.02b Mariner. There are likely others, but out of the ones I have that is the only one that supports it. Since it is 64bit I didn't bother trying the drivers that come with that puppy.
Does anybody know what drivers are required to make this work with Carolina? I am NOT looking to boot from this device I just want to store my media library on it and connect it to my media server, So the media files can be served over DLNA and SAMBA to other computers and devices throughout the house.
Here is the dmesg output:

Will the drive work with Linux?
Seagate Expansion Desktop and/or Seagate Extended Portable drives should function like any other USB drive connected to a Linux-based computer. However, this practice is not supported by Seagate.

I don't think the interface is SCSI. I think those references to "SCSI" in dmesg are due to standard SATA communication regimes - remember, both IDE and SATA are related to SCSI technology.
It's a very new interface device, and I think you just need a recent USB driver to handle it ... or maybe an older USB driver?
Your dmesg results show that the ehci_hcd driver (USB 2.0) is being used ... but the specifications of your Seagate Backup Plus indicate it should be USB 3.0 ?

I suspect your computer is only capable of USB 2.0, so this forces the Seagate to operate at the older standard, and maybe this is what is failing?
Try connecting the Seagate to a computer with USB 3.0 ports (modern Puppies fully support USB 3.0) - you might have more success.

Will the drive work with Linux?
Seagate Expansion Desktop and/or Seagate Extended Portable drives should function like any other USB drive connected to a Linux-based computer. However, this practice is not supported by Seagate.

I don't think the interface is SCSI. I think those references to "SCSI" in dmesg are due to standard SATA communication regimes - remember, both IDE and SATA are related to SCSI technology.
It's a very new interface device, and I think you just need a recent USB driver to handle it ... or maybe an older USB driver?
Your dmesg results show that the ehci_hcd driver (USB 2.0) is being used ... but the specifications of your Seagate Backup Plus indicate it should be USB 3.0 ?

I suspect your computer is only capable of USB 2.0, so this forces the Seagate to operate at the older standard, and maybe this is what is failing?
Try connecting the Seagate to a computer with USB 3.0 ports (modern Puppies fully support USB 3.0) - you might have more success.

I saw that bit on the Seagate website, but it is for the "Desktop Expansion" series drives and I have the "Backup Plus" series drive. I am quite certain that you are correct that my computer only supports USB 2.0. Unfortunately none of my machines have any USB 3.0 ports. On the bright side I know without doubt that this drive will work with a USB 2.0 port, as it works connected to a USB 2.0 port on this very computer, while running the Lighthouse Pup 64 6.02b Mariner (LHP64) puplet. I will reboot in LHP64 take a few screenshots to show you why I thought it was a SCSI drive, then if you could please cast a little more light on this I would greatly appreciate it. Thanks for looking into this so quickly.

I noticed that despite the dmesg output showing that ehci_hcd was used, the lsmod output doesn't show ehci_hcd or even uhci_hcd. Thanks for looking into this.Last edited by can8v on Sun 09 Feb 2014, 17:49; edited 1 time in total

You will see with Carolina that there are no USB-related modules listed ...
I just did some checking and I see that somewhere between Slacko 5.3 and Slacko 5.4 these modules were integrated into the core kernel. Thus, they are no longer external. This is new to me.
What Puppy version/kernel version is Carolina based upon? I don't know, and don't care. As you probably know, I hate unofficial Puppies. But clearly Carolina has one of these kernels with USB support built-in. There's no guarantee that all of the external modules listed as being loaded with LHP64 are contained within the Carolina kernel - the one I think is most important is ums_realtek.

There's one (external) module listed with LHP64 which is not listed with Carolina - sg. This is the SCSI generic driver.
So the only suggestion I can make is to manually load this module, prior to plugging in the Seagate drive, as such -

You will see with Carolina that there are no USB-related modules listed ...
I just did some checking and I see that somewhere between Slacko 5.3 and Slacko 5.4 these modules were integrated into the core kernel. Thus, they are no longer external. This is new to me.
What Puppy version/kernel version is Carolina based upon? I don't know, and don't care. As you probably know, I hate unofficial Puppies. But clearly Carolina has one of these kernels with USB support built-in. There's no guarantee that all of the external modules listed as being loaded with LHP64 are contained within the Carolina kernel - the one I think is most important is ums_realtek.

There's one (external) module listed with LHP64 which is not listed with Carolina - sg. This is the SCSI generic driver.
So the only suggestion I can make is to manually load this module, prior to plugging in the Seagate drive, as such -

Code:

modprobe sg

I have tried modprobe sg, then plugging in the hard drive to no avail. I don't get any error messages upon loading the module, but I do not get a working hard drive upon plugging it in either. I appreciate your looking into this for me. I understand it can be frustrating to support the myriad of puplets that have filled the landscape.

I've packkaged Master PDF Editor 1.9.22, this the Linux-based version is free for non-commercial use.

It is a qt app that requires glibc 2.11, so I have used the hack as used in slimboat and other apps to get this working, I symlinked the needed qt files to to keep the size down, so it is a Carolina only app at the moment, but if the qt lib files are includes it should run in other pups.

You will see with Carolina that there are no USB-related modules listed ...
I just did some checking and I see that somewhere between Slacko 5.3 and Slacko 5.4 these modules were integrated into the core kernel. Thus, they are no longer external. This is new to me.
What Puppy version/kernel version is Carolina based upon? I don't know, and don't care. As you probably know, I hate unofficial Puppies. But clearly Carolina has one of these kernels with USB support built-in. There's no guarantee that all of the external modules listed as being loaded with LHP64 are contained within the Carolina kernel - the one I think is most important is ums_realtek.

There's one (external) module listed with LHP64 which is not listed with Carolina - sg. This is the SCSI generic driver.
So the only suggestion I can make is to manually load this module, prior to plugging in the Seagate drive, as such -

Code:

modprobe sg

I have tried modprobe sg, then plugging in the hard drive to no avail. I don't get any error messages upon loading the module, but I do not get a working hard drive upon plugging it in either. I appreciate your looking into this for me. I understand it can be frustrating to support the myriad of puplets that have filled the landscape.

I've had similar problems with a 4TB Seagate external drive (see earlier in this thread). These drives don't seem to work too well with Linux, although I have it running perfectly with Fluppy. Earlier kernels seem to support it better than newer ones, though that's only a personal observation.

You will see with Carolina that there are no USB-related modules listed ...
I just did some checking and I see that somewhere between Slacko 5.3 and Slacko 5.4 these modules were integrated into the core kernel. Thus, they are no longer external. This is new to me.
What Puppy version/kernel version is Carolina based upon? I don't know, and don't care. As you probably know, I hate unofficial Puppies. But clearly Carolina has one of these kernels with USB support built-in. There's no guarantee that all of the external modules listed as being loaded with LHP64 are contained within the Carolina kernel - the one I think is most important is ums_realtek.

There's one (external) module listed with LHP64 which is not listed with Carolina - sg. This is the SCSI generic driver.
So the only suggestion I can make is to manually load this module, prior to plugging in the Seagate drive, as such -

Code:

modprobe sg

I have tried modprobe sg, then plugging in the hard drive to no avail. I don't get any error messages upon loading the module, but I do not get a working hard drive upon plugging it in either. I appreciate your looking into this for me. I understand it can be frustrating to support the myriad of puplets that have filled the landscape.

I've had similar problems with a 4TB Seagate external drive (see earlier in this thread). These drives don't seem to work too well with Linux, although I have it running perfectly with Fluppy. Earlier kernels seem to support it better than newer ones, though that's only a personal observation.

Funny you should say that. Since this is a core hardware component of my media server. I gave up this morning and changed the Distro from Carolina to Precise 5.7.1 and it works perfectly. I have tried this drive in many differrent puppies and here are the results.
Working in these puppies:
LHP 64, Precise 5.7.1, Racy 5.5
Not working in these puppies:
Saluki 021, Saluki 023, Carolina 1.1, Carolina 1.2, Carolite 1.1, Racy 5.2, Racy 5.3.
My understanding is that the Kernels for Saluki and Carolina both came from Racy 5.2. My guess is that whatever is causing this issue was not corrected in the Racy line until Racy 5.5. All puplets based on 5.2 and 5.3 will likely suffer from the same issues. Nice to know that fluppy works with this hardware. I might consider giving it a try at some point. I have a working setup now and it is a media server, so I will rarely access the server directly. Though if I have to get on this server directly more than a few times a year JWM and ROX will likely drive me crazy and I will end up finding something else that works Fluppy could be the answer. It is kind of dated now, but like I said this is just a media server. It needs to have this Seagate drive working, Samba and minidlna, not much else. Then again I may just get XFCE and Thunar or XFE working on Precise 5.7.1 I do like how it is binary compatible with Ubuntu packages. At any rate I still really like Carolina and will keep it on my laptop.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum