> Trouble could be if ripit picks up from stat(2) before
> it opens the device, we don't know the underlying blocksize
> until after open, floppy drives for instance support many
> different sectorsizes.
Sorry for the confusion - I'm not even using ripit to test now,
I'm simply putting an audio CD in the drive and trying:
# dd if=/dev/rcd0c of=/dev/null
dd: /dev/rcd0c: Invalid argument
[console log: dscheck: b_bcount 512 is not on a sector boundary (ssize 2048)]
I figured ripit was too "high level" a test and I should just try and
get some data off the thing again before moving on. :) I've tried
/dev/rcd0a and /dev/cd0c too, just for grins, no luck. Though trying
the block device does yield a different message on the console:
(cd0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0
(cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0
(cd0:ahc0:0:4:0): Illegal mode for this track
(cd0:ahc0:0:4:0): cddone: got error 0x16 back
- Jordan
>
> What is the name of the port you're using ?
>
> In message <409.935917817@localhost>, "Jordan K. Hubbard" writes:
> >>
> >> This could be another si_bsize casualty.
> >>
> >> Try this patch
> >
> >Nope, it still occurs. You're definitely in the right ballpark
> >though since I added some printfs and it's this check:
> >
> > } else if (ssp->dss_secshift != -1) {
> > if (bp->b_bcount & (ssp->dss_secsize - 1))
> > goto bad_bcount;
> >
> >Which is now failing.
> >
> >- Jordan
> >
>
> --
> Poul-Henning Kamp FreeBSD coreteam member
> [EMAIL PROTECTED] "Real hackers run -current on their laptop."
> FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
