Re: fwohci users, anyone ?

2020-11-12 Thread John D. Baker
On Thu, 22 Oct 2020, John D. Baker wrote:

> IBM ThinkCenter with a FireWire card installed.  In each case, the

> -current/i386 as they require less digging and scratching to set up

Dug out the ThinkCentre S51 to build packages for netbsd-9/i386 and
-current/i386 (9.99.75).  While the internal disk had enough space
for building most packages, "qemu" and "openjdk11" ran out of space.
I switched their ${WRKOBJDIR} to a FireWire-connected disk and it has
been working just fine.

-- 
|/"\ John D. Baker, KN5UKS   NetBSD Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSDFreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645


Re: fwohci users, anyone ?

2020-10-23 Thread Rhialto
On Thu 22 Oct 2020 at 14:05:26 +0200, Hauke Fath wrote:
> On 2020-10-21 15:29, Michael van Elst wrote:
> > Is anyone using firewire hardware ? In particular for mass storage ?
> 
> I would love to, but - has it ever been usable?

My first laptop, almost 20 years ago I guess, had very slow USB and
FireWire. Back then it worked fine, but I haven't tried it again once I
switched to a different laptop.

-Olaf.
-- 
Olaf 'Rhialto' Seibert -- rhialto at falu dot nl
___  Anyone who is capable of getting themselves made President should on
\X/  no account be allowed to do the job.   --Douglas Adams, "THGTTG"


signature.asc
Description: PGP signature


Re: fwohci users, anyone ?

2020-10-22 Thread John D. Baker
On Wed, 21 Oct 2020 13:29:22 - (UTC),  mlelstv%serpens.de@localhost
(Michael van Elst) wrote:

> Is anyone using firewire hardware ? In particular for mass storage ?

I use it on occasion and when I do it's with mass storage (hard disk,
CD/DVD-RW drive).  Mostly on i386, some amd64, and occasionally on macppc
(how ironic!).

I think the last time I needed to use this setup was under NetBSD-7.

In the i386 case, an IBM Thinkpad A31p which has fwohci built in and an
IBM ThinkCenter with a FireWire card installed.  In each case, the
machine's interal disk is just barely big enough for the OS and a few
select packages, so I used the firewire disk for source trees, build
space and the like.  Also had the DVD-RW drive daisy chained from the
hard disk on each (internal optical drive CD-RW only).  Never had a
problem with it.

I assume the sparc host is PCI based (an SBUS 1394 card would be neat).
I have some Ultra 5s I could put a FireWire card in but they are in
not-easily-accessible storage.  (Nevermind scratching out workspace to
set one up.)

I can dig out my firewire enclosures and try them on netbsd-9/amd64,
-current/amd64, and -current/macppc.  Possibly also netbsd-9/i386 and
-current/i386 as they require less digging and scratching to set up
and test.

I've heard of some 1394 peripheral interface ICs being finicky...

-- 
|/"\ John D. Baker, KN5UKS   NetBSD Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSDFreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645


Re: fwohci users, anyone ?

2020-10-22 Thread Hauke Fath

On 2020-10-21 15:29, Michael van Elst wrote:

Is anyone using firewire hardware ? In particular for mass storage ?


I would love to, but - has it ever been usable?

Attaching a firewire disk to

%  uname -a
NetBSD Gstoder 9.99.48 NetBSD 9.99.48 (GA-MA770-UD3-$Revision$) #0: Thu 
Oct 22 12:43:04 CEST 2020 
hf@Hochstuhl:/var/obj/netbsd-builds/developer/amd64/sys/arch/amd64/compile/GA-MA770-UD3 
amd64

%

results in

[  3628.304008] fwohci0: BUS reset
[  3628.304008] fwohci0: node_id=0x8800ffc0, gen=3, non CYCLEMASTER mode
[  3628.304008] ieee1394if0: 2 nodes, maxhop <= 1 cable IRM irm(0) (me)
[  3628.304008] ieee1394if0: root node is not cycle master capable
[  3628.304008] ieee1394if0: bus manager 0
[  3628.304008] fwohci0: autoconfiguration error: too many cycle lost, 
no cycle master present?

[  3628.554096] fwohci0: autoconfiguration error: txd err=14 ack busy_X
[  3628.554096] ieee1394if0: autoconfiguration error: node1: 
explore_read_quads failure

[  3628.554096] fwohci0: autoconfiguration error: txd err=14 ack busy_X
[  3628.554096] ieee1394if0: autoconfiguration error: node1: 
explore_read_quads failure

[  3628.554096] fwohci0: autoconfiguration error: txd err=14 ack busy_X
[  3628.554096] ieee1394if0: autoconfiguration error: node1: 
explore_read_quads failure

[  3655.923722] fwohci0: BUS reset
[  3655.923722] fwohci0: node_id=0xc800ffc0, gen=4, CYCLEMASTER mode
[  3655.923722] ieee1394if0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me)
[  3655.923722] ieee1394if0: bus manager 0
[  3657.204171] fwohci0: BUS reset
[  3657.204171] fwohci0: node_id=0x8800ffc0, gen=6, non CYCLEMASTER mode
[  3657.204171] ieee1394if0: 2 nodes, maxhop <= 1 cable IRM irm(0) (me)
[  3657.204171] ieee1394if0: root node is not cycle master capable
[  3657.204171] ieee1394if0: bus manager 0
[  3657.204171] fwohci0: autoconfiguration error: too many cycle lost, 
no cycle master present?

[  3657.454259] fwohci0: autoconfiguration error: txd err=14 ack busy_X
[  3657.454259] ieee1394if0: autoconfiguration error: node1: 
explore_read_quads failure

[  3657.454259] fwohci0: autoconfiguration error: txd err=14 ack busy_X
[  3657.454259] ieee1394if0: autoconfiguration error: node1: 
explore_read_quads failure

[  3657.454259] fwohci0: autoconfiguration error: txd err=14 ack busy_X
[  3657.454259] ieee1394if0: autoconfiguration error: node1: 
explore_read_quads failure

[  3700.549400] fwohci0: BUS reset
[  3700.549400] fwohci0: node_id=0xc800ffc0, gen=7, CYCLEMASTER mode
[  3700.549400] ieee1394if0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me)
[  3700.549400] ieee1394if0: bus manager 0
[  3701.819846] fwohci0: BUS reset
[  3701.819846] fwohci0: node_id=0x8800ffc0, gen=9, non CYCLEMASTER mode
[  3701.829849] ieee1394if0: 2 nodes, maxhop <= 1 cable IRM irm(0) (me)
[  3701.829849] ieee1394if0: root node is not cycle master capable
[  3701.829849] ieee1394if0: bus manager 0
[  3701.829849] fwohci0: autoconfiguration error: too many cycle lost, 
no cycle master present?


-- not anything that I would trust data with.

Cheerio,
Hauke

--
 The ASCII Ribbon CampaignHauke Fath
() No HTML/RTF in email Institut für Nachrichtentechnik
/\ No Word docs in email TU Darmstadt
 Respect for open standards  Ruf +49-6151-16-21344


Re: fwohci users, anyone ?

2020-10-21 Thread Mike Pumford

On 21/10/2020 16:47, Michael van Elst wrote:

mpumf...@mudcovered.org.uk (Mike Pumford) writes:

I'm trying it with a Sparc workstation running -current. It doesn't
look very stable there. It would be interesting to find a hardware
combination where it does work reliably.

Okay. I'll see if I can remember where I've got that disk enclosure 
tucked away and test it this weekend.


Mike



Re: fwohci users, anyone ?

2020-10-21 Thread Michael van Elst
mpumf...@mudcovered.org.uk (Mike Pumford) writes:

>On 21/10/2020 14:29, Michael van Elst wrote:
>> Is anyone using firewire hardware ? In particular for mass storage ?
>> 
>I'm not using it on a regular basis but I do have systems with hardware 
>and a mass storage enclosure I could attach to them. Currently the 
>firewire equipped systems are 8.2-STABLE amd64 and I think 9.0-STABLE 
>i386. I can easily try current on the i386 system but I'd be more 
>reluctant to do so on the amd64 one as its my primary file server.

I'm trying it with a Sparc workstation running -current. It doesn't
look very stable there. It would be interesting to find a hardware
combination where it does work reliably.


-- 
-- 
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."


Re: fwohci users, anyone ?

2020-10-21 Thread Mike Pumford

On 21/10/2020 14:29, Michael van Elst wrote:

Is anyone using firewire hardware ? In particular for mass storage ?

I'm not using it on a regular basis but I do have systems with hardware 
and a mass storage enclosure I could attach to them. Currently the 
firewire equipped systems are 8.2-STABLE amd64 and I think 9.0-STABLE 
i386. I can easily try current on the i386 system but I'd be more 
reluctant to do so on the amd64 one as its my primary file server.


Mike