massstorage.usbfd problem with 4.1FEU1

	Bottom Previous Topic Next Topic
Register To Post

Cass

Posted on: 2017/4/14 23:33 #1

Just popping in

massstorage.usbfd v53.37 (02/02/2014) mounts an 8GB Verbatim STORE N GO usb stick, but massstorage.usbfd v53.83 (27/11/2016) fails to do so :

Quote:

USB Fkt Init | Init Fkt | Fkt 0x38ad5700 is {Vendor: 0x18A5, Product: 0x0302, Class: 00.00}
USB Fkt Init | Init Fkt | Fkt 0x38ad5700 initialized
USB FD fkt start | BindInterfaceDriver | No interface driver of fkt 0x38ad5700/ifc 0x47d89180 {Class 08.06} has been found
USB FD fkt start | FD launcher | Could not bind any suitable interface driver for fkt 0x38ad5700

The official change log:
Quote:

massstorage.usbfd 53.83

FIXED
o A crash could occurr during warm reboot;

There seem to be many differences regarding the file size::
Quote:

massstorage.usbfd.v53.37 157812 ----arwe 02-Φεβ-14 22:19:00
massstorage.usbfd 55780 ----arwe 27-Νοε-16 20:09:30

H/W : Sam440F@800MHz, Verbatim StoreNGo 8GB

Has anybody else experienced such problems?

broadblues

Re: massstorage.usbfd problem with 4.1FEU1

Posted on: 2017/4/15 0:22 #2

Home away from home

@Cass

I have an 8gb Verbatim stick, it's never worked properly with any version of the usb mass storage driver. (that I remeber anyway)

At best it would mount and then eratically and unpredictable lose connection.

No other usb stick behased so, so I suspect a flexible attitude to the spec by the manufacturer.

The same stick also had issues on AROS on one of my rare ventures into that arena.

It does work well with linux, and my screen capture box will work with it, but is very fussy, sometimes require a reformat before it will write data again. But linux has a nore extensiv driver writing team.

Blender For OS4.x : Blues : Walker Broad

Cass

Re: massstorage.usbfd problem with 4.1FEU1

Posted on: 2017/5/15 23:56 #3

Just popping in

@Cass

I don't like leaving any loose ends, so here is the solution:

I have a dual boot configuration OS4.1FEU1 and OS4.1.6, in that exact order.

After the latest update, Kickstart/Kicklayout was modified by adding :
Quote:

; Update 1
MODULE Kickstart/mounter.library

at the end of the file, thus leaving the OS4.1FE config without FS automounter.
Strangely enough, massstorage.usbfd v53.37 seems not to be affected by the mounter.library module.

Rigo

Re: massstorage.usbfd problem with 4.1FEU1

Posted on: 2017/5/16 0:50 #4

Supreme Council

The later massstorage driver requires mounter.library. The older one did not, that's why.

Simon

Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such.
----
http://codebench.co.uk

sinisrus

Re: massstorage.usbfd problem with 4.1FEU1

Posted on: 2017/5/16 8:38 #5

Just popping in

@Rigo

I have this problem with sam460 and os4.1 FE

I have mounter.library in my drawer kickstart/ ?

Why put a library in kickstart/ ???
it does not make sense

Actualy i have 2 library in kickstart/

- mounter.library
- usbresource.library

In spite of this I had to put the old massstorage.usbfd to not have any more crash at the start of the system

nbache

Re: massstorage.usbfd problem with 4.1FEU1

Posted on: 2017/5/16 21:48 #6

Just can't stay away

@sinisrus

Quote:

Why put a library in kickstart/ ???
it does not make sense

Sure it does. The only difference is that it will be available already before the OS boot starts.

There have always been libraries in Kickstart, even when it was a ROM chip. Just think about exec.library (now part of the kernel file). And workbench.library was also in the Kickstart ROM on some early systems.

Best regards,

Niels

Register To Post
	Top Previous Topic Next Topic

Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )