DId you try starting k3b from a console as root? #k3b
On Monday 28 March 2005 09:41 am, Kevin Toppenberg wrote: > Ismet, > > Thanks for your help. Comments below: > > --- "Ismet Kursunoglu, MD" <[EMAIL PROTECTED]> > > wrote: > > So I am guessing that you have some automounter > > running or that the cd > > (data I presume) was mounted as root either > > seperately or by k3b? I have > > never tried to copy a cd or dvd using it. > > Yes, there was an automounter that worked when I first > hooked up the hardware. When I put in RedHat9 > documentation disk, it would automatically launch a > dialog to install the documentation. It no longer > does that. > > > Is the device seen in the usb bus? i.e. > > /proc/bus/usb/devices ... > > This is all new to me, so I'll just post the file you > mention. Note that I have 2 USB devices on the bus. > The first is v1.0, the second is 2.0 or 2.1 I think. > Note also that my mother board has 5 ISA slots and 1 > PCI slot. I put the new USB 2.0 into the PCI slot. > But because of the number of ISA slots, I wonder if it > is an older version of the PCI slot--perhaps the new > USB card can't work with it. Anyway, here is that > devices file: > > [EMAIL PROTECTED] usb]$ ls > 001 002 003 004 devices drivers > [EMAIL PROTECTED] usb]$ cat devices > T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 > Spd=480 MxCh= 3 > B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 > D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 > #Cfgs= 1 > P: Vendor=0000 ProdID=0000 Rev= 2.04 > S: Manufacturer=Linux 2.4.20-8smp ehci-hcd > S: Product=NEC Corporation USB 2.0 > S: SerialNumber=0b:00.2 > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 > Driver=hub > E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms > T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 > Spd=12 MxCh= 1 > B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 > #Cfgs= 1 > P: Vendor=0000 ProdID=0000 Rev= 0.00 > S: Product=USB OHCI Root Hub > S: SerialNumber=f8882000 > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 > Driver=hub > E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms > T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 > Spd=12 MxCh= 2 > B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 > #Cfgs= 1 > P: Vendor=0000 ProdID=0000 Rev= 0.00 > S: Product=USB OHCI Root Hub > S: SerialNumber=f8880000 > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 > Driver=hub > E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms > T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 > Spd=12 MxCh= 2 > B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 > D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 > #Cfgs= 1 > P: Vendor=0000 ProdID=0000 Rev= 0.00 > S: Product=USB UHCI Root Hub > S: SerialNumber=cce0 > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 > Driver=hub > E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms > [EMAIL PROTECTED] usb]$ > > > ...and is there any special driver module that was > > being > > > loaded that somehow is > > now lacking? i.e. sometimes things like event device > > drivers or other > > rare things need to be loaded prior to scanning the > > bus on boot or with > > things like cdrecord > > I don't know how to go about checking this. I didn't > make any changes between the time it worked, and when > it stopped working (that I know of) > > > There are some graphical utilities to look at the > > usb devices in the > > usbutils Debian package. > > Well, it turns out it is standard with RH9 as well. I > did some research and found the lsusb command. Here > is it's output: > > [EMAIL PROTECTED] root]# usbutils > -bash: usbutils: command not found > [EMAIL PROTECTED] root]# lsusb > Unknown line at line 58 > Unknown line at line 2296 > Unknown line at line 2297 > Unknown line at line 2298 > Unknown line at line 2299 > Unknown line at line 2300 > Unknown line at line 2301 > Unknown line at line 2302 > Unknown line at line 2303 > Unknown line at line 2304 > Unknown line at line 2305 > Unknown line at line 2306 > Unknown line at line 2307 > Unknown line at line 2308 > Unknown line at line 2309 > Unknown line at line 2310 > Unknown line at line 2311 > Unknown line at line 2312 > Unknown line at line 2313 > Unknown line at line 2314 > Unknown line at line 2315 > Unknown line at line 2316 > Unknown line at line 2317 > Unknown line at line 2318 > Unknown line at line 2319 > Unknown line at line 2320 > Unknown line at line 2321 > Unknown line at line 2322 > Unknown line at line 2323 > Unknown line at line 2324 > Unknown line at line 2325 > Unknown line at line 2326 > Unknown line at line 2327 > Unknown line at line 2328 > Unknown line at line 2329 > Unknown line at line 2330 > Unknown line at line 2331 > Unknown line at line 2332 > Unknown line at line 2333 > Unknown line at line 2334 > Unknown line at line 2335 > > Bus 004 Device 001: ID 0000:0000 > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 9 Hub > bDeviceSubClass 0 > bDeviceProtocol 1 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 2.04 > iManufacturer 3 Linux 2.4.20-8smp ehci-hcd > iProduct 2 NEC Corporation USB 2.0 > iSerial 1 0b:00.2 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x40 > Self Powered > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type none > wMaxPacketSize 2 > bInterval 12 > Language IDs: (length=4) > 0000 (null)((null)) > > Bus 003 Device 001: ID 0000:0000 > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 9 Hub > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 0.00 > iManufacturer 0 > iProduct 2 USB OHCI Root Hub > iSerial 1 f8882000 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x40 > Self Powered > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type none > wMaxPacketSize 2 > bInterval 255 > Language IDs: (length=4) > 0000 (null)((null)) > > Bus 002 Device 001: ID 0000:0000 > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 9 Hub > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 0.00 > iManufacturer 0 > iProduct 2 USB OHCI Root Hub > iSerial 1 f8880000 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x40 > Self Powered > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type none > wMaxPacketSize 2 > bInterval 255 > Language IDs: (length=4) > 0000 (null)((null)) > > Bus 001 Device 001: ID 0000:0000 > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.00 > bDeviceClass 9 Hub > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 0.00 > iManufacturer 0 > iProduct 2 USB UHCI Root Hub > iSerial 1 cce0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x40 > Self Powered > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type none > wMaxPacketSize 8 > bInterval 255 > Language IDs: (length=4) > 0000 (null)((null)) > [EMAIL PROTECTED] root]# > > > Is the DVD device on when you boot or do you also > > hot-plug the device? I > > am sorry if I missed that part - but is the DVD > > burner powered from > > additional AC or from the bus itself? > > This is an external drive. It has its own > powersupply, and it's turned on. When I press the > eject button, the disk slides out. > > > Is there something else - some other application / > > process that is > > trying to use/access the device on bootup ? i.e. > > thinking that is is > > going to play/view some multimedia file or the like? > > How would I tell? > > > And lastly is sg and scsi_mod modules loaded, or > > could it be that you > > are only able to use it's cdrom reader capacity and > > not the dvd burning > > ability due to some permissions/access problem. > > I don't know how to tell. > > > What does the devices section from the k3b > > configuration show i.e. are > > you running it with group permissions set for > > something like the dvd or > > cdrom group? > > When I go to the devices in k3b, it shows only my old > cd-rom. When I first ran k3b, it showed the DVD > player, but not now. > > > You might also take a look at /var/log in syslog to > > see how and what is > > being loaded when you plug the device in 'tail -f > > /var/log/syslog' > > In my RH9, there is no /var/log/syslog file (??) > There is a boot.log.x (in fact several of them). When > I look at that, it lists the services being started > up, one of which is syslogd. Not sure what to do next > here. > > > Once you get the device loaded you might try running > > k3b from the > > command line and take a look at the output - you can > > see the options > > with 'k3b --help-all' > > Yeah, but I need to get the device loaded first! > > > I hope this gets you at least some more leads in > > getting it to work. > > > > Ismet > > I VERY MUCH appreciate your help. Thanks! > > Kevin > > > > > __________________________________ > Do you Yahoo!? > Make Yahoo! your home page > http://www.yahoo.com/r/hs > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Hardhats-members mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
