Hi folks,

I've just recently done a fresh install of 4.4 on a Sharp Zaurus
SL-C3200 according to
ftp://ftp.openbsd.org/pub/OpenBSD/4.4/zaurus/INSTALL.zaurus and the
install went fine from a CF card.

As far as I can tell, everything except the SD/MMC drive works as
expected.  When I plug in an SD card into the SD slot, I get this report
in dmesg:

scsibus0 at sdmmc0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed
sd0: 1920MB, 122 cyl, 255 head, 63 sec, 1024 bytes/sec, 1966080 sec
total

and then when I do a disklabel sd0, I get:

pxammc0: unhandled interrupt 1<DATADONE>
pxammc0: unhandled interrupt 1<DATADONE>

sent to dmesg and the following output to console:

# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: Drive #01
flags:
bytes/sector: 1024
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 122
total sectors: 1966080
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0          # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0

16 partitions:
#                size             offset    fstype [fsize bsize cpg]
  c:          1966080                  0    unused      0     0

and fdisk sd0 sends:

pxammc0: unhandled interrupt 1<DATADONE>
pxammc0: unhandled interrupt 1<DATADONE>
pxammc0: unhandled interrupt 1<DATADONE>
pxammc0: unhandled interrupt 1<DATADONE>

to dmesg and the following output to console:

Disk: sd0          geometry: 122/255/63 [1966080 1024-byte Sectors]
Offset: 0          Signature: 0x0
               Starting         Ending        LBA Info:
 #: id         C   H   S -      C   H   S [      start:       size ]
-----------------------------------------------------------------------
 0: 00         0   0   0 -      0   0   0 [          0:          0 ]
 unused
 1: 00         0   0   0 -      0   0   0 [          0:          0 ]
 unused
 2: 00         0   0   0 -      0   0   0 [          0:          0 ]
 unused
 3: 00         0   0   0 -      0   0   0 [          0:          0 ]
 unused

When I unplug this card from the SD slot, I get the following output to
dmesg:

sd0 detached
scsibus0 detached


This same SD card, when plugged into an SD slot on a USB multi-slot card
reader (handles CF/MD, SD/MMC, MS/PRO, SM), sends the following to dmesg
when the card reader is plugged into the USB port on the SL-C3200:

umass0 at uhub0wd0f: aborted command writing fsbn 378572 of
378572-378575 (wd0 bn 2378635; cn 2359 tn 12 sn 7), retrying
port 2 configuration 1 interface 0 "Generic Mass Storage Device" rev
2.00/1.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
wd0: soft error (corrected)
sd0 at scsibus0 targ 1 lun 0: <Generic, USB SD Reader, 1.00> SCSI0
0/direct removable
sd0: 1920MB, 244 cyl, 255 head, 63 sec, 512 bytes/sec, 3932160 sec total
sd1 at scsibus0 targ 1 lun 1: <Generic, USB CF Reader, 1.01> SCSI0
0/direct removable
sd1: drive offline
sd2 at scsibus0 targ 1 lun 2: <Generic, USB SM Reader, 1.02> SCSI0
0/direct removable
sd2: drive offline
sd3 at scsibus0 targ 1 lun 3: <Generic, USB MS Reader, 1.03> SCSI0
0/direct removable
sd3: drive offline

and disklabel sd0 sends no errors to dmesg and the following output to
console:

# Inside MBR partition 0: type A6 start 15 size 3932145
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: USB SD Reader
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 244
total sectors: 3932160
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0          # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0

16 partitions:
#                size            offset   fstype [fsize bsize  cpg]
  a:          3932145                15   4.2BSD   2048 16384    1
  c:          3932160                 0   unused      0     0

and fdisk sdo sends nothing to dmesg and the following to console:

Disk: sd0         geometry: 244/255/63 [3932160 Sectors]
Offset: 0         Signature: 0xAA55
              Starting         Ending         LBA Info:
 #: id        C   H   S -      C   H   S [       start:         size ]
 0: A6        0   0  16 -    244 195  15 [          15:      3932145 ]
 OpenBSD
 1: 00        0   0   0 -      0   0   0 [           0:            0 ]
 unused
 2: 00        0   0   0 -      0   0   0 [           0:            0 ]
 unused
 3: 00        0   0   0 -      0   0   0 [           0:            0 ]
 unused

And I can mount /dev/sd0a /mnt and do standard filesystem stuff like
mkdir /mnt/zusb and ls /mnt shows what one would expect.  When I plug
this same USB card reader and SD card into a PC running OBSD 4.4, I have
the same output as above (the second set of data) and I can do normal
filesystem stuff on the card in that manner also and see the changes
made by the Zaurus on that card via the card reader.

I suspect this is a bug and if so then I'll report it as such, but
thought I'd ask here first if anyone has any further troubleshooting
suggestions.

The difference in cylinders as perceived by the OS via the SD slot
versus the USB port and card reader seems significant, but either I
don't know how to force the SD slot to use 244 cylinders or perhaps it
just can't be done; not sure...

The SD card is labeled as follows:

PNY
Optima
SD
60X
2GB

I seem to recall reading elsewhere that somebody else had had success
with a 2GB SD card under OBSD in the Zaurus, but am not certain of that.
 Am I doing something wrong here or is this a bug?

Thanks for any suggestions.

Otis
PS. Please pardon any typos in the program output and dmesg reports
above.  These were hand-typed and possibly contain mistakes due to my
typing although I did proofread before sending.

PPS. I tried doing similar work earlier with this card formatted with a
filesystem from mfgr which showed up as an MS-DOS partition, but thought
that my problems might have been due to the absence of an OpenBSD
filesystem, so using the PC, I replaced the MBR and disklabel and slice
on the card with OpenBSD standard stuff.  The problems before (with
MS-DOS partition table) and after (as shown above) were the same if I
recall correctly.

Reply via email to