I didn't know how to manage the dbug stuff, I didn't find anything saying exclude debug or something similar. But apparently I was capturing the debug data under /var/log/debug any ways (read that from /etc/logsys.conf as suggested).
So you were right. I'm attaching several logs, but specially debug one contains lines that confirms that although in other logs the HP8200e was detected, for some reason it's getting treated as a flash. Weird thing... Here I copy some lines, but the logs are attached also: Jun 26 17:59:44 fvv kernel: usb-storage: Status code 0; transferred 1/1 Jun 26 17:59:44 fvv kernel: usb-storage: -- transfer complete Jun 26 17:59:44 fvv kernel: usb-storage: usbat_read_user_io: UIO register reads F8 Jun 26 17:59:44 fvv kernel: usb-storage: usbat_flash_check_media_changed: media change detected ... Jun 26 17:59:44 fvv kernel: usb-storage: usbat_flash_transport: REQUEST_SENSE. Jun 26 17:59:44 fvv kernel: usb-storage: -- Result from auto-sense is 0 Jun 26 17:59:44 fvv kernel: usb-storage: -- code: 0xf0, key: 0x6, ASC: 0x28, ASCQ: 0x0 Jun 26 17:59:44 fvv kernel: usb-storage: Unit Attention: Not ready to ready change, medium may have changed ... Jun 26 17:59:44 fvv kernel: usb-storage: usbat_flash_transport: Gah! Unknown command: 26 (0x1a) Jun 26 17:59:44 fvv kernel: usb-storage: -- transport indicates command failure Jun 26 17:59:44 fvv kernel: usb-storage: Issuing auto-REQUEST_SENSE Jun 26 17:59:44 fvv kernel: usb-storage: usbat_flash_transport: REQUEST_SENSE. Jun 26 17:59:44 fvv kernel: usb-storage: -- Result from auto-sense is 0 Jun 26 17:59:44 fvv kernel: usb-storage: -- code: 0xf0, key: 0x5, ASC: 0x20, ASCQ: 0x0 Jun 26 17:59:44 fvv kernel: usb-storage: Illegal Request: Invalid command operation code Jun 26 17:59:44 fvv kernel: usb-storage: scsi cmd done, result=0x2 Jun 26 17:59:44 fvv kernel: usb-storage: *** thread sleeping. Jun 26 17:59:44 fvv kernel: usb-storage: queuecommand called Jun 26 17:59:44 fvv kernel: usb-storage: *** thread awakened. Jun 26 17:59:44 fvv kernel: usb-storage: Command ALLOW_MEDIUM_REMOVAL (6 bytes) ... Jun 26 17:59:44 fvv kernel: usb-storage: usbat_flash_transport: TEST_UNIT_READY. Jun 26 17:59:44 fvv kernel: usb-storage: usb_stor_ctrl_transfer: rq=82 rqtype=c0 value=0000 index=00 len=1 Jun 26 17:59:44 fvv kernel: usb-storage: Status code 0; transferred 1/1 Jun 26 17:59:44 fvv kernel: usb-storage: -- transfer complete Jun 26 17:59:44 fvv kernel: usb-storage: usbat_read_user_io: UIO register reads F8 Jun 26 17:59:44 fvv kernel: usb-storage: usbat_flash_check_media_changed: media change detected Jun 26 17:59:44 fvv kernel: usb-storage: usb_stor_ctrl_transfer: rq=82 rqtype=40 value=a0b0 index=00 len=0 Jun 26 17:59:44 fvv kernel: usb-storage: Status code 0; transferred 0/0 Jun 26 17:59:44 fvv kernel: usb-storage: -- transfer complete Sorry for my lack of knowledge and experience, but, what's next? Should I do something else, some trials? I'm also attaching syslog.conf in case there's something to be changed there also... Thx, Javier. On 6/26/05, Alan Stern <[EMAIL PROTECTED]> wrote: > On Sun, 26 Jun 2005, Javier-Elias Vasquez-Vivas wrote: > > > OK, > > > > So I enabled usb-storage debug under kernel, and when I perform dmesg, > > most of the output is lost, and most is consumed by the cyclic > > usb-storage failure. > > > > So instead of posting the dmesg output I redirected the output to a > > file, and I'm attaching it... > > > > Although /var/log/messages is less complete (includes less output) > > then dmesg, I'm also attaching it just in case... > > > > +++++++++++++++++++++++++++++++++++++ > > > > To recap, in case some one is not able to see the thread, under kernel > > 2.6.10 I had my hp8200e+ cd-writer working, and for it to work I had > > the kernel option: > > > > CONFIG_USB_STORAGE_HP8200 > > > > However under kernel 2.6.12.1, this option is no longer available and > > instead the following one must be used: > > > > CONFIG_USB_STORAGE_USBAT > > > > Problem is that just replacing one driver by the other doesn't seem to > > work, the linux device to use for the cd-writer seems to be different > > (previous scd0, now sda), and besides although the cd-writer is > > recognized, several errors are dumped, and mounting cds doesn't > > work... > > There is at least one big problem showing up in the log. The INQUIRY > response indicates a Direct Access type of device (i.e., a disk drive) > instead of a CD-ROM type. This may be the result of something going wrong > during the initial stages of probing, which were left out of the dmesg > log. Apparently the driver thought you had a flash device, not an > HP-8200e. > > Even though dmesg is getting overloaded, you can capture all the debugging > messages in the regular system log if you edit /etc/syslog.conf. Tell it > to store all levels of kernel messages instead of ignoring DEBUG level > messages. > > Alan Stern
syslog.conf
Description: Binary data
debug
Description: Binary data
kern.log
Description: Binary data
messages
Description: Binary data
syslog
Description: Binary data
