I do not see any fixes for usb in the release notes.

Several nasty bugs occur after upgrading from 3.1 to 3.2 for the powerbook G4.
The powermac G5 on 3.2 has the same bugs.

Basically usb slows down to 1mb/sec.

It occurs when booting from the 3.2 cd also.

Did anyone look into it?

p.s.

I just got in (2) 1 TB 2.5" drives for my usb 2.0 jbod box and I really need to be able to backup as needed.

On my PowerBook, if I copy many files/a huge one, I often experience that the transfer stops with errors.
It exists at last until MOS 3.0. (I'm a MOS user since 3.0)
In 3.1 came a hack for this problem: In this case the device is reconnected...
The error existed further in 3.2. Probably it exists in the current release too.
It would be nice to see a correction one day for this problem too!

I just set up a Windows machine, partly for backup purpose. I think, the smbfs is also a good way to do this, but sometimes the USB transfer is also needed (e.g. copying pictures from a camera).

The problem with samba to backup is I need to backup the amiga attributes.
In an emergency recovery I just want to boot to cd, plug in the usb drive, and copy the OS back over from an amiga partition.

I have tried various backup tools but in the end they fail.
A straight up file copy never fails.
Admittedly I do not get any compression when using file copy but with 1TB drives nowadays who cares.

Quote:

Is it bus-powered? I have an el-cheapo external 2.5" sata enclosure (Fat32) whose power requirements are on the edge of what the Powerbook USB ports can deliver. When powered just using the USB cable, it will occasionally drop out whilst in use.
With a seperate power supply I have no such problems though.

@Bash64

I get a sustained ~15MB/s when copying from the internal drive/ram to my external SATA drive, I've never seen it drop to ~1MB/s let alone stay at that speed.

Does Poseidon give any error messages? Have you tried a different USB device, and/or removing any intermediate hub?

[ Edited by boot_wb 20.09.2013 - 00:42 ]

I do not use hubs because of the problems I have had with them over the years.
Most of them are junk.

I have used multiple devices , all have proven to work on a windows system with no issues, and were proven to work with at least 3.1 on a powerbook g4.

After upgrading to 3.2 all went to hell.

boot_wb,
Quote:
There are more devices:
- USB flash memory stick (bus powered)
- Camera (not bus powered)
- External drive (not bus powered, but it is suspicious to have some contact problems on it's data connector plug)

All of them have the descibed broblem.
I'll try it with my camera and phone too to check the problem again.

Quote:

Actual speed is around 13.4MB/s today using MorphOS3.2, PB 5.6, copying from USB to HDD (Fat32 > IceFS).

Copying HDD > USB (IceFS > Fat32) gives around the same.

Screenshot

It doesn't help to solve your problem, but at least shows that it's not 'normal' to expect such low speed.

[ Edited by boot_wb 20.09.2013 - 19:21 ]

I am going to do some tests today.
I will be upgrading to 3.3 and see if it fixes it.
I may just have some corrupted files somewhere.
The OS resides on SFS (I think thats the norm).
I do use IceFS a lot of several of the IceFS partitions went bad.
Not sure why, but definitely corrupt filesystems can wreck everything.

bash64,
Quote:

Oooh, that's scary, I've just started using IceFS.
Thanks for the warning, will make sure I keep everything backed up.

I am using MOS v3.7, and I keep trying to copy mp3 files from my HDD to a Kingston 64GB stick, this happens with other similar USB sticks, not just this one device, so after about 100MB is copied then there are error requesters stating the file has errors in it or it is incomplete, and that occurs with the next few files, to a point where the device becomes inactive and Ambient basically freezes - then I have to reboot as Ambinet is no longer functional. I reboot, and then can copy the files the system said there were errors with/were incomplete, so it's not the files - it's the filesystem or something software/system based.

Does anyone else suffer from this same issue, and more importantly is there a fix for it, or is it going to be fixed in the near future.

I use a couple of Belkin MacMini styled USB hubs, and a similar Firewire+USB hub with the relevant leads, and power supplies, but they work for copying a small amount of data then throw up these spurious errors.

I use the same hardware with Mac OS X 10.4 and have no issues with the stick or the hubs, or the Mac Mini - so something in the software is causing the problem, and needs to be fixed, as it is getting me really perplexed - well I keep turning purple and crosseyed.