Bernd Walter wrote: > Are you shure you need to change the #if 0? > Especialy the first should only have an effect on different devices. > Can you please try with both to default and if that failed with > the first on default.
Sure! With both = 0, I get: umass0: Unsupported command protocol 5 ugen0: ASAHI PENTAX OPTIO 430, rev 1.00/10.00, addr 2 With the first = 0 and the second = 1, everything works as before, so I agree that the first block probably doesn't matter. (I simply enabled everything that said "ATAPI" when I made the change.) However: I found that I sometimes get kernel crashes when attaching the camera, after these messages (copied by hand, may have typos): umass0: ASAHI PENTAX PENTAX OPTIO 430, rev. 1.00/10.00, addr 2, 8070i (ATAPI) over CBI umass-sim:0:-1:-1:XPT_PATH_INQ:. umass0:0:0:-1: Attached to scbus0 as device 0 scbus0: scanning for umass0:0:0:-1 umass-sim:0:-1:-1:XPT_PATH_INQ:. umass0:0:0:0::XPT_PATH_INQ:. umass0:0:0:0::XPT_PATH_INQ:. umass0:0:0:0::XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense umass-sim:0:1:0:func_code 0x0004: Invalid target (no wildcard) umass0: Handling CBI state 10 (CBI Command), xfer=0xc3eb6800, NORMAL_COMPLETION These crashes happen only one the first attach (subsequent ones are fine *if* the first one succeeded), and not always on the first one. The strange thing is that they *only* seem to happen when I attach right after bootup *before* anyone logs in. After someone logs in, it never crashed (yet). It also doesn't crash if the camera was attached *during* boot. Any clues? (Can't produce a crashdump, kernel doesn't enter DDB when crashing). Lars -- Lars Eggert <[EMAIL PROTECTED]> Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
