
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.