FW: /dev/sg* for AMD64
Larry Rosenman
ler at lerctr.org
Fri Aug 15 16:00:13 UTC 2008
The device driver just doesn't work. There was mail traffic about it, and
ScottL said that he needed to redo some stuff in it.
I can give access to a relatively recent box with seagate drives in it if
you want...
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler at lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
-----Original Message-----
From: Roman Divacky [mailto:rdivacky at freebsd.org]
Sent: Friday, August 15, 2008 10:56 AM
To: Larry Rosenman
Cc: freebsd-current at freebsd.org
Subject: Re: FW: /dev/sg* for AMD64
On Fri, Aug 15, 2008 at 09:29:35AM -0500, Larry Rosenman wrote:
> Can I get a response from SOMEONE on getting /dev/sg* working for the
amd64
> platform so
> that tools such as Seagate's seatools linux32 binary will work on FreeBSD?
>
> (I was able to get a replacement drive without it this time, but sometimes
> seagate, and other manufacturers get pissy about running THEIR tool).
>
> Thanks!
>
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 512-248-2683 E-Mail: ler at lerctr.org
> US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
>
>
> -----Original Message-----
> From: owner-freebsd-current at freebsd.org
> [mailto:owner-freebsd-current at freebsd.org] On Behalf Of Larry Rosenman
> Sent: Friday, August 01, 2008 1:17 PM
> To: scottl at freebsd.org
> Cc: freebsd-current at freebsd.org
> Subject: /dev/sg* for AMD64
>
> Scott,
> Back before 7.0, you added /dev/sg* for linux compatibility, but the
> 64 bit stuff didn't work. Has there been any progress on getting it
> work with amd64?
> I have a seagate drive that's giving me flack, and they want me to
> run their linux tool, but it won't run on my box due to the above.
>
> If I need to file a PR, please let me know.
>
> I'm on 7-STABLE.
what exactly is the problem? please be a little more specific, can you
provide
a ktrace/linux_kdump of whats going on? does it crush? does it just dont use
the sg* device? what is the problem?
More information about the freebsd-current
mailing list