Last time I did this, I used the block device, rather than the character device. Also, I think I used 2KB blocks, instead of 512B.
And then I found it was much faster to build a proper filesystem on the CF, mount it, populate it with tar/cpio/restore and then do the installboot. CF isn't noted for it's blazing speeds, but have a look at your dmesg to see what it says about the CF card. PIO ___, ___ sector transfers. Some of my faster CF cards can do 2 or 4 sector transfers. CK On 07/11/05, Didier Wiroth <[EMAIL PROTECTED]> wrote: > Hello, > > I've build an image file with opensoekris for 256 mb sandisk compactflash. > The writing of the image file takes very long (102188 bytes/sec), see the > output below (I interupted it after 20 minutes). > > How long should it normally take to write a 256mb to a compactflash card? > For me it takes about 42 minutes, is that normal? > > Thanks for helping! > Didier > > dd if=38c.2005-11-07-16.22.bin of=/dev/rsd1c bs=512 > 238985+0 records in > 238984+0 records out > 122359808 bytes transferred in 1197.395 secs (102188 bytes/sec) > 1197.55 real 0.27 user 4.53 sys > > > fdisk: sysctl(machdep.bios.diskinfo): Device not configured > Disk: sd1 geometry: 245/64/32 [501760 Sectors] > Offset: 0 Signature: 0xAA55 > 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: A6 0 1 1 - 244 63 32 [ 32: 501728 ] OpenBSD > > Here is disklabel output: > # Inside MBR partition 3: type A6 start 32 size 501728 > # /dev/rsd1c: > type: SCSI > disk: vnd device > label: fictitious > flags: > bytes/sector: 512 > sectors/track: 32 > tracks/cylinder: 64 > sectors/cylinder: 2048 > cylinders: 245 > total sectors: 501760 > 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: 501760 0 unused 0 0 # Cyl 0 - 244 > > -- GDB has a 'break' feature; why doesn't it have 'fix' too?
