I hope it's the rigth forum for this question: there are 2 type of usb disk-on-keys.
1. Storage only, can have one or more partitions. Under Linux recognized as /dev/sd(something)1
2. Usually a mp3 player, has "no partition", under Linux seen as /dev/sd(something).
How do I mount the later under AOS4? Nothing interesting in t:usb.log
Thanks, Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
I had the impression that when the OS4 USB stack doesn't automatically mounts a device by startup you won't be able to use it (yet).
Using a "mounter" kind of programs afterwards doesn't work with USB ... or am i completely mistaken here?
People are dying. Entire ecosystems are collapsing. We are in the beginning of a mass extinction. And all you can talk about is money and fairytales of eternal economic growth. How dare you! – Greta Thunberg
I had the impression that when the OS4 USB stack doesn't automatically mounts a device by startup you won't be able to use it (yet).
Grrr... Means the Iriver and Swimp3 will be reloaded only via Linux...
Quote:
Using a "mounter" kind of programs afterwards doesn't work with USB ... or am i completely mistaken here?
Isn't mounter for scsi? usb-storage isn't wrapped by scsi like in linux afaik
Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
"automatically mounts a device by startup" grrr, scrap the "by startup" bit, i meant by plugging it in OR on startup (when already plugged in)
mounter
yes, bad example (as it is already covered in the now edited part of my first answer)
sorry bout that
People are dying. Entire ecosystems are collapsing. We are in the beginning of a mass extinction. And all you can talk about is money and fairytales of eternal economic growth. How dare you! – Greta Thunberg
The Mounter is for every removable partitioned storage medium (SCSI, IDE, SATA etc) except for USB. The mounter for partitioned and unpartitioned USB media is usbmassstorage.usbfd, when Utilities/USBInspector shows a massstorage medium with a loaded driver its very likely that typing Ctrl-Alt-M or using Commodities Exchange will bring up the MassStorage commodity which shows media, partitions and filesystem types and offers formatting. What does it display for the drive in question?
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
...but only if a MassStorageDevice is attached to USB.
Erm, the 'Final' edition doesn't work MSD very well. If the USB memory stick is installed in the hub before cold boot, I get a mounting error ; this never happened before. I've actually have gotten a 'babble' error message! OK, I think Detlef mentioned a stack size problem with USB. Who and what can I change??
Erm, the 'Final' edition doesn't work MSD very well.
You dont have 'July' installed???
Quote:
If the USB memory stick is installed in the hub before cold boot, I get a mounting error ; this never happened before. I've actually have gotten a 'babble' error message! OK, I think Detlef mentioned a stack size problem with USB. Who and what can I change??
How does your T:usb.log look?
Assumed that you use July: Sounds like you have July-Update or USB-HW problems. Try to copy the USB-Files from 'Final' over 'July' and see what happens.
when Utilities/USBInspector shows a massstorage medium with a loaded driver its very likely that typing Ctrl-Alt-M or using Commodities Exchange will bring up the MassStorage commodity
When USBInspector doesnt show a massstorage device have a look at T:USB.log. When this doesnt show the attempt to use a massstorage device, enable Info logging with Prefs/USB. When this crashes edit ENVRC:USB/System/LOGINFO by hand (set to 1). When your A1 has no USB fix, the behaviour when attching an USB device is undefined.
Yup. It is there when a recognizable media is present. I wrongly assumed the commodity is an external standalone app...
I enabled all the logging, and (probably independently) swimp3 appeared there but as "unitialized", regardless it's set to "auto" (usb1c:) or "fat" (usb2:) filesystem (it is initialized btw, and contains data). Size is correct.
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
2. Usually a mp3 player, has "no partition", under Linux seen as /dev/sd(something). How do I mount the later under AOS4? Nothing interesting in t:usb.log ... swimp3 appeared there but as "unitialized", regardless it's set to "auto" (usb1c:) or "fat" (usb2:) filesystem (it is initialized btw, and contains data). Size is correct.
Ok, now we know that neither Linux nor OS4 do believe that the medium contains a valid MBR, and we know that CrossDOSFileSystem also believes that the medium is not an unpartitioned FAT12/FAT16/FAT32 medium. Does Linux believe its using FAT? If yes, which blocksize? If no, why should OS4 be able to handle such a proprietary file system?
Ok, now we know that neither Linux nor OS4 do believe that the medium contains a valid MBR, and we know that
No MBR: correct. Linux can access it (the whole disk as a block device using FAT instead of accessing block device that represents a single partition).
Quote:
CrossDOSFileSystem also believes that the medium is not an unpartitioned FAT12/FAT16/FAT32 medium. Does Linux believe its using FAT? If yes, which blocksize?
I can query the parameters of the medium. Can I tell OS4 to mount the whole device? (like one can mount trackdisk.device, with propper block/whatever sizes/numbers, like telling Linux to mount /dev/sdb instead of /dev/sdb1). Will experiment with it when I'll have a chunk of time...
Imho MBR-less usb storage is common enough to be implemented "out of the box" in OS4 (as far as I know lot of flash-based mp3 players are MBR-less).
Jack
Edit: typos
Edited by Jack on 2007/10/7 21:29:39
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
Linux can access it (the whole disk as a block device using FAT instead of accessing block device that represents a single partition).
Thanks for the info. Then CrossDOSFileSystem _should_ be able to access it too...
Quote:
Can I tell OS4 to mount the whole device? (like one can mount trackdisk.device, with propper block/whatever sizes/numbers, like telling Linux to mount /dev/sdb instead of /dev/sdb1). Will experiment with it when I'll have a chunk of time...
Yes, when the filesystem selector in the massstorage commodity is set to "FAT" (or "Default"), the complete medium is mounted as-is, with LowCyl 0.
Quote:
Imho MBR-less usb storage is common enough to be implemented "out of the box" in OS4 (as far as I know lot of flash-based mp3 players are MBR-less).
AFAIK this works with at least some mediums...
You can experiment with mountlists, different filesystems etc. When e.g. the commodity shows "USB0" as device, "MountInfo USB0:" will create a mountlist for the complete medium, when its "USB1C" then "MountInfo USB1C" will create a mounlist for the first partition of a MBR-partitioned medium etc. Caution: CrossDOSFileSystem actively modifies the LowCyl, HighCyl and Interleave values, so those may _not_ match the real values which were used by massstorage.usbfd for mounting, to be sure to get better values, set the filesystem selector to FFS or SFS first (dont format of course) and change the DOSType.
When you have mountlists, you can try to use them with different versions of CrossDOSFileSystem, FAT95 or XFSD. You can also try to use MountDOS from Aminet when the medium is smaller than 2 or 4 GB (MountDOS doesnt support NSD...) to get mountlists.
Thanks for the extensive info. Will have to carve out a time for it (motivation --- exists, time --- doesn't)
Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
when its "USB1C" then "MountInfo USB1C" will create a mounlist for the first partition of a MBR-partitioned medium etc. Caution: CrossDOSFileSystem actively modifies the LowCyl, HighCyl and Interleave values, so those may _not_ match the real values which were used by massstorage.usbfd for mounting, to be sure to get better values, set the filesystem selector to FFS or SFS first (dont format of course) and change the DOSType.
Ok, the swimp3 is actually with MBR, fat16, linux reports: 16 heads 56 sectors/track, 571 cylinders first partition is fat16, there's also a warning about different physical/logical beginnings/endings: physical: 0,1,44, logical: 0,1,52 physical: 755,15,0 logical: 571,6,48
I assume that dostype should be 0x46415400. Or 16 instead of 00? Should I follow physical or logical mapping? Should the "Interleave" match the highest cylinder? Need an advice on the arithmetics...
Also tried to generate mountinfo for usb0c: in ffs mode, but when MBR is shown, can't switch the fs type.
Here's the mountinfo for the device as it appears in the commodity: Quote:
Edit: also tried the original mountlist with 00 and 16 at the end of Dostype, no avail. The other player (iriver t10) doesn't show up in the commodity, althought an attachment window pops up TIA, Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
Ok, the swimp3 is actually with MBR, fat16, linux reports: 16 heads 56 sectors/track, 571 cylinders first partition is fat16, there's also a warning about different physical/logical beginnings/endings: physical: 0,1,44, logical: 0,1,52 physical: 755,15,0 logical: 571,6,48
I assume that dostype should be 0x46415400. Or 16 instead of 00?
A "FAT" DosType is no standard AFAIK. CrossDOSFileSystem may work with it but the PC0 mountlist uses 0x4D534400 ("MSD") and massstorage.usbfd uses "FAT2" 0x46415432 which ensures that formatting is tried in FAT32 mode first.
Quote:
Should I follow physical or logical mapping?
massstorage.usbfd happily ignores physical track/head/sector values because those are outdated since many years. I dont know if CrossDOSFileSystem uses physical or logical values, eventually it even contains a check that both must match somehow and refuses to work with this broken MBR while Linux contains some magic code which selects the most reasonable alternative?
Quote:
Should the "Interleave" match the highest cylinder?
As already written CrossDOSFileSystem modifies it anyway. massstorage.usbfd does not specify Interleave at all and a standard AmigaOS filesystem ignores this.
Quote:
Need an advice on the arithmetics...
For a "normal" Amiga filesystem only LowCyl and HighCyl are important, and when LowCyl is 0 then HighCyl is ignored and the whole medium is used. For CrossDOSFileSystem AFAIK _both_ LowCyl and HighCyl are completely ignored, it always uses the complete medium when the device name doesnt end with a letter from C to Z, when it ends with "C" it uses the first MBR partition etc.
In your example with 56 sectors/track and "logical: 0,1,52" I'd calculate the start of the first partition to be at sector 0 head 1 track 52 = 1*56+52=108. The mountlist as modified by CrossDOS says LowCyl 107, not 108, strange...
When the player doesnt contain important data and has an option to format the medium in case he cant understand it, I'd simply try to partition and format the medium from some OS which knows how to create a valid MBR, e.g. Linux or Windows, and not the builtin player firmware...
Quote:
Also tried to generate mountinfo for usb0c: in ffs mode, but when MBR is shown, can't switch the fs type.
The massstorage commodity doesnt allow you to try to switch the filesystem of a partition on an MBR-partitioned medium to something which is not FAT. It would not work. FFS only works with RDB-partitioned media or with flat media. You are only allowed to switch to FFS after selecting the MBR entry, which implies that the MBR would be destroyed after formatting with FFS and that you are aware of that.
Quote:
The other player (iriver t10) doesn't show up in the commodity, althought an attachment window pops up
USBInspector and T:USB.log may help to find out whats wrong here.
When the player doesnt contain important data and has an option to format the medium in case he cant understand it, I'd simply try to partition and format the medium from some OS which knows how to create a valid MBR, e.g. Linux or Windows, and not the builtin player firmware...
I won't do it unless I find an indication that the firmware won't be lost while rewriting the mbr (the player is too expensive, it's waterproof). Luckily I have some linuces around to hook it up... Meanwhile I will experiment with mountlists, the letter at the end is very important piece of info (I wondered why there's always a "C" at the end of volume name when mr is used). Just tried the 108, and it didn't work.
BTW: mediatoolbox reports these physical values: 8000 cylinders, 16, sectors, 4 heads And logical size: 64 blocks per cylinder 8000 cylinders...
iriver info will follow later...
Thanks for helping Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
(used "find" - no avail. )
