somewhat OT: garmin oregon disklabel?
I just got a garmin oregon 450 (for hacking OSM/mkgmap). It attaches as two disks (internal flash and uSD slot): umass0 at uhub4 port 2 configuration 1 interface 0 umass0: vendor 0x091e product 0x2380, rev 2.00/5.09, addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, 2 luns per target sd0 at scsibus0 target 0 lun 0: <Garmin, GARMIN Flash, 1.00> disk removable sd0: fabricating a geometry sd0: 950 MB, 950 cyl, 64 head, 32 sec, 512 bytes/sect x 1945600 sectors sd0: fabricating a geometry sd1 at scsibus0 target 0 lun 1: <Garmin, GARMIN SD Card, 1.00> disk removable sd1: drive offline sd1(umass0:0:0:1): Check Condition on CDB: 0x00 00 00 00 00 00 SENSE KEY: Not Ready ASC/ASCQ: Medium Not Present But, there is apparently no MBR partition table:
fdisk sd0 fdisk: Cannot determine the number of heads Disk: /dev/rsd0d NetBSD disklabel disk geometry: cylinders: 950, heads: 64, sectors/track: 32 (2048 sectors/cylinder) total sectors: 1945600
BIOS disk geometry: cylinders: 950, heads: 64, sectors/track: 32 (2048 sectors/cylinder) total sectors: 1945600 Partition table: 0: <UNUSED> 1: <UNUSED> 2: <UNUSED> 3: <UNUSED> No active partition. A mac reads the filesystem just fine, but didn't obviously tell me what it was. I hear it works on Linux. Has anyone managed to read this with free software? Could they describe the type of filesystem and layout, and why there's no MBR partition table? I can report that the OSM img files I built with mkgmap work pretty well; you can just drop osm.img from mkgmap output on the flash in Garmin/. The map display is subdued (vs the harsh but easy to absord etrex), and that's making me more inclined to play with TYP files, although I lack the Copious Spare Time.
On Mon, Aug 30, 2010 at 4:53 PM, Greg Troxel <gdt@ir.bbn.com> wrote:
I just got a garmin oregon 450 (for hacking OSM/mkgmap). It attaches as two disks (internal flash and uSD slot): [...] But, there is apparently no MBR partition table: [...] A mac reads the filesystem just fine, but didn't obviously tell me what it was. I hear it works on Linux.
Has anyone managed to read this with free software? Could they describe the type of filesystem and layout, and why there's no MBR partition table?
The internal flash in my Oregon 300 is not partitioned but has a standard VFAT filesystem on the raw drive. It "just works" on my Linux systems (Fedora) and the few times that I've plugged it into a Windows system it has worked just fine there too.
I can report that the OSM img files I built with mkgmap work pretty well; you can just drop osm.img from mkgmap output on the flash in Garmin/. The map display is subdued (vs the harsh but easy to absord etrex), and that's making me more inclined to play with TYP files, although I lack the Copious Spare Time.
Without using a TYP file some things can be hard to tell apart, for example buildings from parking lots but it works. I haven't had the time to mess with TYP files either. -- Jeff Ollie
My Oregon 550T shows two FAT32 formatted disks in Windows 7 and XP, and from memory (lost the Mac and the Slackware laptop) I could read/write these in both OS X and linux. Maybe your OS lacks a driver for FAT32? J-----. -----[ Greg Troxel ]-----
I just got a garmin oregon 450 (for hacking OSM/mkgmap). It attaches as two disks (internal flash and uSD slot):
--- 8< --- snip --- 8< ---
A mac reads the filesystem just fine, but didn't obviously tell me what it was. I hear it works on Linux.
Has anyone managed to read this with free software? Could they describe the type of filesystem and layout, and why there's no MBR partition table?
"Jeroen Muris" <jeroen@tweejee.net> writes:
My Oregon 550T shows two FAT32 formatted disks in Windows 7 and XP, and from memory (lost the Mac and the Slackware laptop) I could read/write these in both OS X and linux.
thanks.
Maybe your OS lacks a driver for FAT32?
I can read a 16G CF from a dslr just fine, and also the 2G uSD in an etrex works ok. I think the problem is that there is no partition table. Is the windows-world assumption probably that the filesystem starts at sector 63? Normally NetBSD wants to use a partition table to find the filesytem and say what type it is. I'll have to try to fake that up.
participants (3)
-
Greg Troxel -
Jeffrey Ollie -
Jeroen Muris