bernard

Hi ! As already stated in my former thread, my cdwriter is now being reckognised and I can mount it for reading on scd0. However, I can't write anything. cdrecord -scanbus says : [root@localhost bin]# cdrecord -scanbus Cdrecord 1.9 (i686-pc-linux-gnu) Copyright © 1995-2000 Jörg Schilling Linux sg driver version: 3.1.19 Using libscg version 'schily-0.1' scsibus0: 0,0,0 0) 'HP ' 'CD-Writer+ 8200 ' '1.0f' Removable CD-ROM 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * /proc/scsi/scsi says the same. I have madeup an image file, using mkisofs as shown in the man file. No errors doing so ; the file is about 45 mB , it contains a whole directory, I made it using the arguments -r -J. After introducing a new recordable disc in the cdwriter drawer, I typed: cdrecord -v -dummy speed=2 dev=0,0,0 -data tempo.raw and the process started nicely up to the end. Then I got the following messages: Cdrecord 1.9 (i686-pc-linux-gnu) Copyright © 1995-2000 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.19 Using libscg version 'schily-0.1' atapi: 1 Device type : Removable CD-ROM Version : 2 Response Format: 1 Vendor_info : 'HP ' Identifikation : 'CD-Writer+ 8200 ' Revision : '1.0f' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO Drive buf size : 2086656 = 2037 KB FIFO size : 4194304 = 4096 KB Track 01: data 43 MB Total size: 50 MB (04:57.93) = 22345 sectors Lout start: 50 MB (04:59/70) = 22345 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type B, low Beta category (B-) (4) ATIP start of lead in: -11834 (97:24/16) ATIP start of lead out: 359849 (79:59/74) Disk type: Short strategy type (Phthalocyanine or similar) Manuf. index: 24 Manufacturer: SONY Corporation Blocks total: 359849 Blocks current: 359849 Blocks remaining: 337504 Starting to write CD/DVD at speed 2 in dummy mode for single session. Last chance to quit, starting dummy write in 1 seconds. Waiting for reader process to fill input buffer ... input buffer ready. Starting new track at sector: 0 Track 01: 43 of 43 MB written (fifo 100%). Track 01: Total bytes read/written: 45758464/45758464 (22343 sectors). Writing time: 153.766s Fixating... WARNING: Some drives don't like fixation in dummy mode. Fixating time: 0.151s cdrecord: Input/output error. mode select g1: scsi sendcmd: retryable error CDB: 55 10 00 00 00 00 00 00 10 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 26 00 00 80 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x26 Qual 0x00 (invalid field in parameter list) Fru 0x0 Sense flags: Blk 0 (not valid) error refers to data part, bit ptr 0 (not valid) field ptr 0 cmd finished after 0.022s timeout 40s cdrecord: fifo had 721 puts and 721 gets. cdrecord: fifo was 0 times empty and 655 times full, min fill was 96%. [root@localhost bin]# ********* I have made another trial without the -dummy ; error result was the same, except that the writing process did quit right at the beginning or just about so. As one can imagine, I have retried this several times. I think I have seen once something about problem in power calibrating, but it may be one of those lines that have erased and that I therefore cannot copy here. Here is the content of my dmesg file, for the part that concerns my cdwriter:: usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.259 $ time 17:36:49 Sep 6 2001 usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 11 for device 00:07.2 usb-uhci.c: USB UHCI at I/O 0x8400, IRQ 11 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected usb-uhci.c: v1.251:USB Universal Host Controller Interface driver hub.c: USB new device connect on bus1/1, assigned device number 2 usb.c: USB device 2 (vend/prod 0x3f0/0x107) is not claimed by any active driver. SCSI subsystem driver Revision: 1.00 Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage scsi0 : SCSI emulation for USB Mass Storage devices Vendor: HP Model: CD-Writer+ 8200 Rev: 1.0f Type: CD-ROM ANSI SCSI revision: 02 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 USB Mass Storage support registered. EXT3 FS 2.4-0.9.8, 25 Aug 2001 on ide0(3,3), internal journal **************** and the last messages in /var/log/messages: May 28 18:47:15 localhost kernel: hub.c: USB new device connect on bus1/1, assigned device number 3 May 28 18:47:27 localhost su(pam_unix)[1532]: session opened for user root by bd(uid=500) May 28 18:47:39 localhost modprobe: modprobe: Can't locate module char-major-97 May 28 18:47:39 localhost last message repeated 3 times May 28 18:59:14 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 888 May 28 18:59:14 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 890 May 28 19:01:48 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1094 May 28 19:01:48 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1096 ********************** Thanks in advance for any hint about what to do next... Bernard

Hi Mel, Danleff and everyone else who took part in this thread ! I didn't say that there was anything wrong with HP cdwriter 8200 as far as comptatibility with Linux... I only said that it was most likely something wrong with MY HP cdwriter. As previously said, it was a used unit, and the power module was added on, the original one having likely given up. I found that it was fed on 12V DC only, while the scheme said that it should have been fed in 12V and 5V DC. I had gotten a positive test with that writer in MSWIN on my office PC, not on my laptop. In Linux, it was not even being reckognized. I therefore suspected that, on my office PC, part of the power was fed from the PC unit, through the usb cable, and that, using my laptop, there was not enough power. So, I got an old PC-AT power module, and adapted it to feed the missing 5V for my burner. Then, the writer got to be recognized under Linux. I could mount it, read CD... and even write CDs, except that I always got errors, so the discs were unusable. Furthermore, I noticed that CDs got to turn at variable speeds, increasing and decreasing back and forth. That is when I got the idea to test another apparatus, the ASUS I spoke of, and everything got allright, I got constant speed for cd spinning, and no errors in writing. I have no doubt that, had I tested a brand new HP cdwriter, or an used one in a good shape, I would have most likely worked... May I ask one more Out of Topic question ? I have played around a bit with cdrecord and mkisofs, but I did not find any possibility for checking a burnt CD against an iso file, as I used to do with xcdroast on an older PC, equiped with RH 6.0 and an SCSI TEAC burner. Since I don't intend to install xcdroast on my Thinkpad (I try to save as much disk space as possible), I'd like to know how to do without. Originally posted by Mel: Quote: All the recent kernals will support HP hardware but although all the distros claim to support HP hardware,Mandrake10 is the only distro I found that will properly set up HP stuff with system configuration GUI.The other distros require manual configuration of dependancies and kernal entries. At the risk of revealing my age,I will say,the last time I actually did any programming was way back when,to get anything really useful,I had to use a combination of CPM,Basic and ML with a lot of gosubs and calls.(That's a few years.)I think c was just coming out. I assume there are a lot of good programmers around now who never heard of CPM or gosub. My last post is the impression I got from replies from HP while trying to get this hardware to work. BTW,last time I tried, kernal 2.4 ,which I use now, seems stable, 2.6 tends to take side trips into never-never land.Also 2.4 handles 3rd party stuff OK while 2.6 has problems.

Originally posted by danleff: Quote: I'll take a stab in the dark. It looks like cdrecord does not like the media. What exact media and size (72 min vs. 80 min.) are you using? It looks like cdr media, but rated at 2X for this writer? It also looks like the media write has been writing to the cdr with an error. The media is fixated and can't be written to again... So, you run the risk of wasting cdr media? If the dummy write does not work, then don't remove this option, until cdrecord finishes without errors. Make sure that you use a fresh cdr media that has not been used before and that it is rated for this writer. ***************************************** There it is ! It now WORKS OK... but not with the HP cdwriter 8200. Must have been faulty. After many more trials, I jumped to my car and went buying a ASUS CRW 5224A external usb cdwriter. I made arrangements with the shop keeper so that I could return it in case it was not linux compatible. The test lasted no more than five minutes, using whatever command lines I had used with the used HP device ; it went the same way, except that there were no error messages ! I wrote a cd that I was able to read afterward... I hope I can get my money back for the used out of order HP 8200 that I will return. I am going to fill information in the linuxcompatible database so that the ASUS CRW 5224A usb is known as compatible. Thanks for you help. As I do more many trials and cdwriting, I will tell if I encounter any problem in doing more complicate tasks. Bernard

Hi there ! This cd burner is listed as linux compatible. As for details, it just says: "Just plug it in and it works without further configuration under RedHat 7.1, usually as SCSI device 0,0,0" I am trying to operate this roaster on my IBM Thinkpad 600 with RedHat 7.2, but I don't know how. After I had plugged this cdwriter on the USB port, the /var/log/messages file got incremented with the lines below: localhost kernel: usb.c: USB new device connect on bus 1/1, assigned device number 2 localhost kernel: usb.c USB device 2 (vend/prod/ 0x3f0/0x107) is not claimed by any active driver localhost kernel: SCSI subsystem druver Revision: 1.00 localhost kernel: Initializing USB Mass Storage Driver localhost kernel: usb.c: registered new driver usb-storage localhost kernel: scsi0: SCSI emulation for USB Mass Storage Devices localhost kernel: USB Mass Storage support registered ********* Now, where do I go from there ? I have, by just guessing, tried to mount a device, doing like this: mount /dev/sda1 /mnt/cdwriter... up to sda5, and none of the sda devices were reckognized. In any case, how am I to use this cdwriter ? Shall I have to use Xcdroast as I do on my old desk machine (RedHat 6.0 and an old SCSI burner) ? Or shall I be able to directly write files to the device filesystem ? Thanks for any help

Originally posted by bernard: Quote: Originally posted by danleff: *********************************** There we are: I have stuffed my HP 8200 cdwriter with a second power module. It now gets fed with both 12v and 5v as it should. So, as said before, the apparatus is now being reckognized by Linux. After a few trials, I found that it mounted on scd0, not on sr0 or anything else like sda1 or else. In /proc/scsi/scsi, I get: [root@localhost bd]# more /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: HP Model: CD-Writer+ 8200 Rev: 1.0f Type: CD-ROM ANSI SCSI revision: 02 [root@localhost bd]# cdrecord -scanbus gives: [root@localhost bin]# cdrecord -scanbus Cdrecord 1.9 (i686-pc-linux-gnu) Copyright © 1995-2000 Jörg Schilling Linux sg driver version: 3.1.19 Using libscg version 'schily-0.1' scsibus0: 0,0,0 0) 'HP ' 'CD-Writer+ 8200 ' '1.0f' Removable CD-ROM 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * [root@localhost bin]# Mounting tests gives this: [root@localhost bd]# mount -r -t iso9660 /dev/scd0 /mnt/cdwriter [root@localhost bd]# which means that it succeeded in mounting. a dir on the mounted directory gives: [root@localhost bd]# ls -l /mnt/cdwriter total 11947 -r-xr-xr-x 1 root root 5653836 Sep 13 1999 ar40fra.exe -r-xr-xr-x 1 root root 4310227 Nov 15 1999 data1.cab -r-xr-xr-x 1 root root 8327 Nov 15 1999 data1.hdr -r-xr-xr-x 1 root root 96 Nov 15 1999 DATA.TAG dr-xr-xr-x 1 root root 2048 Nov 30 1999 enc -r-xr-xr-x 1 root root 1299494 Oct 22 1999 ency.bmp -r-xr-xr-x 1 root root 296674 Feb 23 1999 _inst32i.ex_ -r-xr-xr-x 1 root root 27648 Oct 27 1998 _ISDel.exe -r-xr-xr-x 1 root root 23541 Jan 12 1999 lang.dat -r-xr-xr-x 1 root root 628 Nov 15 1999 layout.bin -r-xr-xr-x 1 root root 450 Jul 27 1998 os.dat dr-xr-xr-x 1 root root 165888 Nov 30 1999 PlanchesJpg dr-xr-xr-x 1 root root 24576 Nov 30 1999 plancheszip0 -r-xr-xr-x 1 root root 1127 Nov 15 1999 Readme.txt -r-xr-xr-x 1 root root 34816 Oct 8 1998 _Setup.dll -r-xr-xr-x 1 root root 73728 Jan 12 1999 Setup.exe -r-xr-xr-x 1 root root 100 Nov 15 1999 SETUP.INI -r-xr-xr-x 1 root root 59860 Nov 15 1999 setup.ins -r-xr-xr-x 1 root root 49 Nov 15 1999 setup.lid -r-xr-xr-x 1 root root 177755 Nov 15 1999 _sys1.cab -r-xr-xr-x 1 root root 4106 Nov 15 1999 _sys1.hdr -r-xr-xr-x 1 root root 14655 Nov 15 1999 _user1.cab -r-xr-xr-x 1 root root 4684 Nov 15 1999 _user1.hdr [root@localhost bd]# which is OK. However, if I try to go into the directory called PlanchesJpg, which directory contains hundreds of large images files, and then if I try to list those files, it takes an awful lot of time, maybe one minute or more, before anything appears on display. In the meantime, while I wait, I can hear the cdrom spinning at increasing and decreasing speeds... I therefore wonder if there is still a power problem... or else, maybe something needs a cleansing job inside the cdrom driver... I will bother with that later on. Now, let us try with a virgin recordable disc in the drawer: [root@localhost bd]# mount -r -t iso9660 /dev/scd0 /mnt/cdwriter mount: wrong fs type, bad option, bad superblock on /dev/scd0, or too many mounted file systems [root@localhost bd]# This is what I get. Nothing to be surprised about, since, indeed, a virgin disc is not supposed to be read. A write instruction instead of -r, does not work either: [root@localhost bd]# mount -w -t iso9660 /dev/scd0 /mnt/cdwriter mount: block device /dev/scd0 is write-protected but explicit `-w' flag given [root@localhost bd]# So, where do I go from there ? How am I to record anything on this disc ? Must I make use of cdrecord ? The person who wrote something on "Linuxcompatible" about HP usb cdwriter 8200, seems to mean that no software is required ; I therefore imagine that it must be possible to do direct file copying, something like: cp -R mydirectory /mnt/cdwriter/. By the way, I remember what you mentioned about disc media that would be suitable for record with such an old cdwriter. The cdrom media that I am making use of for writing, are those which I use on my other desk computer which operates a yet older cdwriter (this is a Traxdata C550 or something like that, working with a SCSI module, driven with Xcdroast on Linux 2.2.5-15 (RedHat 6.0). So, if these discs work fine on this very old system, I suppose that they are fit for the newer one. On these recordable discs, not much is written, and no more in the box : "SONY CD-R 700 MB recordable supremas". Nothing is being mentioned as far as recording speed or anything else. As a matter of fact, when purchasing recordable discs, it never happened that I found any that were unsuitable for writing on the very old system I just spoke of. However, I almost always buy something different, since the stores do not carry the same models for long. Thanks in advance for any more hints, Bernard

Originally posted by danleff: Quote: I think that you are correct, you need the power from both sources, USB and the AC input. Also, these are older drives and only work with specific cdrw and cdr media. If I remember correctly, they have to be 2X cdrw and cdr media. This may be the issue. I bet that it will not write to anything else! From the HP support page for the 8200 writer; "High speed media is a special type of CD-RW media designed to allow recording from 4X to 10X speeds in a CD-writer that supports higher writing speeds. The term, high speed, is confusing. For CD-RW media, high speed is not a subjective marketing or advertising term, but an official term representing a different low-level format on the media. The high speed media format prevents 1X – 4X CD-writers from being able to record to it. Trying to write to high speed media in one of these drives can produce a variety of errors depending on the recording application used. The errors produced may be strange or seemingly unrelated to the media. Because the media’s format is sufficiently different from existing CD-RW media, new CD-writer hardware with the ability to write to CD-RW media faster than 4X speed is required to be able to use this media. A firmware upgrade is not sufficient to make early 1X - 4X CD-writer drives able to write to the high speed media. The new high speed format only prevents 1X - 4X CD-writers from writing to the media but does not prevent them from reading information from the new media. Once recorded in a certified high speed drive, high speed media is fully readback compatible with 1X – 4X CD-writers and other MultiRead drives." ************************************* My later post doesn't seem to have reached here... I can't remember what exactly was in it... I wrote it from another address, my business address, nevertheless it should be there... In any case, I discovered something else. My newly purchased used cdwriter had been modified by its former owner. Most likely, the mains power module had given up, as it is often the case (it happens to me with the power module of a HP scanner). Here in France, these parts are sold at unbelievable prices: while a scanner or a cdwriter are being sold at a no more than 20% higher price than in the US, spare parts, in the other hand, run about ten times higher. So, the former owner of my cdwriter has modified the external power supply. The cdwriter should be fed with both 5v DC and 12vDC ; the power slot had three pins, one for the 5 DC, the other one for 12 DV, and the midlle one for common (minus, ground). This original slot was made useless, and a two wires cable did replace it, with only 12V DC. I have tried to feed the system as it should have been fed, using two regulated power modules, and clamps for the connexion. And then, I had a surprise ! Under Linux, the system is now being reckognised as scd0 device. That means that the command # mount /dev/scd0 /mnt/cdwriter said OK (I mean, it returned the shell script), except that it says that scd0 was being mounted as read only. In /var/log/messages, the cdwriter is being reckognized for what it is, that is, HP 8200 plus usb cdwriter. I have been able to read the cdrom content, which was not the case before. However, upon trying to mount a recordable disc, the system said that it had still been mounted as R/O, but this need to be investigated a bit further, using stable power supply instead of clamps that are not very stable. In any case, I am going to try finding an appropriate power module and test it in better conditions. Then I will tell you more. Thanks a lot for all the already provided help.

Originally posted by danleff: Quote: Oh ohh! No scsi drivers. Let's try one thing. I was not sure if this was needed. At a command prompt, as root, type in modprobe ide-scsi. Then try the cdrecord -scanbus command. See if you get no errors from the ide-scsi command (the screen just returns back to the command prompt with no errors) and if so, if the cdrecord -scanbus shows the drive. Well, I did type modprobe ide-scsi. Once this was done, I made a new test with cdrecord -scanbus, and, indeed, I got a positive reply... but not the one that I expected: see the copy/paste below: the SANYO CRD device that has been reckognized on scsibus 1 is not my HP USB cdwriter, it is my R/O internal ide cdrom drive ! And, as you can see, nothing else is being reckognized, despites the fact that I did not forget to connect the cdwriter. There may be another module that I should launch in order to have my cdwriter reckognized, and that could possibly be a module that has not been compiled in my system. However, there is another possibility, since I just discovered that my HP 8200 cdwriter may not work properly. I have just purchased it as a bargain through e-bay, since it is no longer available as new, at least, not to my knowledge. So, the used cdwriter I received has a funny behaviour, which may be due to a hardware problem, or else, it may be due to a power problem. This cdwriter is being powered by an external power source (12v DC), but, upon plugging, nothing seems to work: no lights on, and the drawer does not open. In order to get it working, I have to connect it to my PC, via the usb cable... and then, the light goes on and it becomes possible to open the drawer in pressing the button. Does this mean that part of the feeding power comes from my PC ? I need to know that for sure, since, if this is so, my PC being a laptop (Thinkpad 600), the power may then not be sufficient as a matter of amps. I used to think that only internal devices were powered through the PC, but I may be wrong... Besides, I have tested the cdwriter in MSWIN environment (Win 98), and it DOES NOT WORK PROPERLY ! Upon installing the driver that I downloaded on the web for W98, the cdwriter is being reckognized in the Windows Explorer, and you can read a cd in the slot, but any trial for writing a cd, have failed. Upon introducing a blank disk in the drawer, a new window should open on the screen according to the manual... and nothing opens... instead, I can hear the cd turning and getting speed, then slowing down and getting speed again, and so on and so forth forever ; in the meantime, I can see, on the PC screen, the "wait" icon getting on and off back and forth all the time. To morrow, I am going to bring this cdwriter at work and test it with a desk computer, to see if it makes any difference. I really want to know whether the usb port is supposed to provide DC power to feed such a device on top of the power module that is to be plugged to mains. Should this be the case, I would probably have to give up any hope of using this cdwriter on my laptop, unless the power that must provide the laptop is really no more than a few milliamps. The dowloaded manual says nothing about this. In the back of the cdwriter, I can read this: INPUT +5v DC 1.2 amp ......+12v DC 1 amp Why are there two figures for input ? Does this mean that the cdwriter may be fed either with 5v or 12v, a system being supposed to detect and adapt afterwards ? Or else, could this mean that there are two power feeding that are both necessary, one coming from a DC converter plugged on mains, the other coming from the PC through usb port ? Thanks in advance for more info [root@localhost bin]# /sbin/modprobe ide-scsi [root@localhost bin]# cdrecord -scanbus Cdrecord 1.9 (i686-pc-linux-gnu) Copyright © 1995-2000 Jörg Schilling Linux sg driver version: 3.1.19 Using libscg version 'schily-0.1' scsibus1: 1,0,0 100) 'SANYO ' 'CRD-S372B ' '1.24' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * [root@localhost bin]# I actually have one of these HP drives and can try it and see. The issue is that my dstro's will have ide-scsi already loaded, so it may not mimic your problems.

Originally posted by bernard: Quote: Originally posted by danleff: Quote: So much for a simple solution. Where did you see an article or directions that the driver would work on hotplug? It was on the 'linuxcompatible' data, for the HP cdwriter 8200 usb. Besides, upon plugging the usb cable, new lines get written in /var/log/messages as stated in my first post Look at the following page for a troubleshooting list; http://www.dragoninc.on.ca/mail-archives/linux-usb/2001-04/0198.html Now we will dig further. At a console prompt, type in, as per the article cdrecord -scanbus To see if the scsi device is recognized. If it is, note the location as 0,0,0 or whatever it is. It is NOT ! a call on cdrecord -scanbus gives the following reply: "Cannot open SCSI drivers" below, are the relevant lines that are in my /var/log/dmesg file: usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.259 $ time 17:36:49 Sep 6 2001 usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 11 for device 00:07.2 usb-uhci.c: USB UHCI at I/O 0x8400, IRQ 11 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected usb-uhci.c: v1.251:USB Universal Host Controller Interface driver and now, the relevant lines in the tail of /var/log/messages: May 22 18:39:37 localhost kernel: hub.c: USB new device connect on bus1/1, assigned device number 2 May 22 18:39:37 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x107) is not claimed by any active driver. May 22 18:39:41 localhost kernel: Initializing USB Mass Storage driver... May 22 18:39:41 localhost kernel: usb.c: registered new driver usb-storage May 22 18:39:41 localhost kernel: scsi0 : SCSI emulation for USB Mass Storage devices May 22 18:39:41 localhost kernel: USB Mass Storage support registered. Then (if it is); tail /var/log/messages and see if you see the expected messages in the run (example - yours may be slightly different); Apr 23 22:25:56 localhost kernel: Product: HP USB CD-Writer Plus Apr 23 22:25:59 localhost kernel: scsi0 : SCSI emulation for USB Mass Storage devices Apr 23 22:25:59 localhost kernel: Vendor: HP Model: CD-Writer+ 8200f Rev: 1.0A Apr 23 22:25:59 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Apr 23 22:25:59 localhost kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 Apr 23 22:25:59 localhost kernel: usb-storage: Command will be truncated to fit in SENSE6 buffer. Apr 23 22:25:59 localhost kernel: usb-storage: Command will be truncated to fit in SENSE6 buffer. Apr 23 22:25:59 localhost kernel: sr0: scsi3-mmc drive: 168x/0x writer dvd-ram cdda caddy Note the scsi device sr0 in this case. In my case, scsi0 : "SCSI emulation for USB Mass Storage devices" without any mention of the device sr0 or anything else. If not try the more /proc/bus/usb/drivers command and see what drivers are loading. Let us know what you find. Then we will go from there. I will just add this to my late posting (posted only a few minutes ago: more /proc/usb/drivers give this: usbdevfs hub and, if I do the same check when the cdwriter is plugged to the usb port : usbdevfs hub usb-storage the test: more /proc/scsi/scsi gives, in both cases: Attached Devices: NONE and : cdrecord -scanbus also gives same replies whether the crwriter is plugged or not: cannot open SCSI drivers. I tried these on both hotplugs and coldplugs, that is that I restarted my computer while the cdwriter was plugged.

Originally posted by danleff: Quote: So much for a simple solution. Where did you see an article or directions that the driver would work on hotplug? It was on the 'linuxcompatible' data, for the HP cdwriter 8200 usb. Besides, upon plugging the usb cable, new lines get written in /var/log/messages as stated in my first post Look at the following page for a troubleshooting list; http://www.dragoninc.on.ca/mail-archives/linux-usb/2001-04/0198.html Now we will dig further. At a console prompt, type in, as per the article cdrecord -scanbus To see if the scsi device is recognized. If it is, note the location as 0,0,0 or whatever it is. It is NOT ! a call on cdrecord -scanbus gives the following reply: "Cannot open SCSI drivers" below, are the relevant lines that are in my /var/log/dmesg file: usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.259 $ time 17:36:49 Sep 6 2001 usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 11 for device 00:07.2 usb-uhci.c: USB UHCI at I/O 0x8400, IRQ 11 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected usb-uhci.c: v1.251:USB Universal Host Controller Interface driver and now, the relevant lines in the tail of /var/log/messages: May 22 18:39:37 localhost kernel: hub.c: USB new device connect on bus1/1, assigned device number 2 May 22 18:39:37 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x107) is not claimed by any active driver. May 22 18:39:41 localhost kernel: Initializing USB Mass Storage driver... May 22 18:39:41 localhost kernel: usb.c: registered new driver usb-storage May 22 18:39:41 localhost kernel: scsi0 : SCSI emulation for USB Mass Storage devices May 22 18:39:41 localhost kernel: USB Mass Storage support registered. Then (if it is); tail /var/log/messages and see if you see the expected messages in the run (example - yours may be slightly different); Apr 23 22:25:56 localhost kernel: Product: HP USB CD-Writer Plus Apr 23 22:25:59 localhost kernel: scsi0 : SCSI emulation for USB Mass Storage devices Apr 23 22:25:59 localhost kernel: Vendor: HP Model: CD-Writer+ 8200f Rev: 1.0A Apr 23 22:25:59 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Apr 23 22:25:59 localhost kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 Apr 23 22:25:59 localhost kernel: usb-storage: Command will be truncated to fit in SENSE6 buffer. Apr 23 22:25:59 localhost kernel: usb-storage: Command will be truncated to fit in SENSE6 buffer. Apr 23 22:25:59 localhost kernel: sr0: scsi3-mmc drive: 168x/0x writer dvd-ram cdda caddy Note the scsi device sr0 in this case. In my case, scsi0 : "SCSI emulation for USB Mass Storage devices" without any mention of the device sr0 or anything else. If not try the more /proc/bus/usb/drivers command and see what drivers are loading. Let us know what you find. Then we will go from there.

Originally posted by danleff: Quote: Try the following, with a cdrom in the drive; mount -r -t iso9660 /dev/sr0 /mnt/cdwriter assuming that you have a directory in /mnt called cdwriter. Here is the reply I got: [root@localhost bd]# mount -r -t iso9660 /dev/sr0 /mnt/cdwriter mount: special device /dev/sr0 does not exist If you get no errors, see if it can read the inserted cd; ls -l /mnt/cdwriter