-
USB DVD writer eludes my detection
Complete Newbie using Ubuntu 6.06 here. I have read every tutorial and resource that I can google up, but can find nothing directly in point, nor anything that leads me to a solution.
I have plugged in and am trying to use a Sony i.link/USB DVD+/-RW ,+/-r portable drive, but cannot locate it. I have run the following commands:
sudo cat /etc/fstab, which yields the following:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda2 / ext3 defaults,errors=remount-ro 0 1
/dev/hda3 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
There is an internal CD in the computer which appears to me to be hdc and there are 2 hdd's which I take to be hda2 and hda3. Do I have this right?
lsusb yields:
Bus 004 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Device manager identifies 3 USB UHCI controllers and one USB2 controller, but none identify the writer or give any helpful clues.
I only have one USB device plugged in and that is the DVD writer. How can I locate it? TIA
-
have you checked, dmesg and /var/log/messages
if the kernel even supports that device, you may have to write some udev rules for it to get it to work
-
dkeav, thank you most kindly for your post. Unfortunately, I am very much a noob and am not sure how to proceed.
dmesg yields screenfuls of information and I have copied the last one and posted it below, but I simply do not know what to look for. Here is:
[17336437.248000] printk: 39 messages suppressed.
[17336437.248000] hub 2-0:1.0: over-current change on port 1
[17336442.184000] printk: 36 messages suppressed.
[17336442.184000] hub 4-0:1.0: over-current change on port 3
[17336447.224000] printk: 37 messages suppressed.
[17336447.224000] hub 4-0:1.0: over-current change on port 3
[17336452.264000] printk: 36 messages suppressed.
[17336452.264000] hub 4-0:1.0: over-current change on port 3
[17336457.156000] printk: 29 messages suppressed.
[17336457.156000] hub 2-0:1.0: over-current change on port 1
[17336462.196000] printk: 39 messages suppressed.
[17336462.196000] hub 2-0:1.0: over-current change on port 1
[17336467.236000] printk: 39 messages suppressed.
[17336467.236000] hub 2-0:1.0: over-current change on port 1
[17336472.172000] printk: 38 messages suppressed.
[17336472.172000] hub 4-0:1.0: over-current change on port 3
[17336477.212000] printk: 30 messages suppressed.
[17336477.212000] hub 4-0:1.0: over-current change on port 3
[17336482.252000] printk: 28 messages suppressed.
[17336482.252000] hub 4-0:1.0: over-current change on port 3
[17336487.292000] printk: 28 messages suppressed.
[17336487.292000] hub 4-0:1.0: over-current change on port 3
[17336492.184000] printk: 37 messages suppressed.
[17336492.184000] hub 2-0:1.0: over-current change on port 1
[17336497.224000] printk: 33 messages suppressed.
[17336497.224000] hub 2-0:1.0: over-current change on port 1
[17336502.160000] printk: 34 messages suppressed.
[17336502.160000] hub 4-0:1.0: over-current change on port 3
[17336507.200000] printk: 36 messages suppressed.
[17336507.200000] hub 4-0:1.0: over-current change on port 3
[17336512.240000] printk: 37 messages suppressed.
[17336512.240000] hub 4-0:1.0: over-current change on port 3
[17336517.280000] printk: 36 messages suppressed.
[17336517.280000] hub 4-0:1.0: over-current change on port 3
[17336522.172000] printk: 28 messages suppressed.
[17336522.172000] hub 2-0:1.0: over-current change on port 1
[17336527.212000] printk: 32 messages suppressed.
[17336527.212000] hub 2-0:1.0: over-current change on port 1
[17336532.252000] printk: 30 messages suppressed.
[17336532.252000] hub 2-0:1.0: over-current change on port 1
[17336537.224000] printk: 26 messages suppressed.
[17336537.224000] hub 2-0:1.0: over-current change on port 1
[17336542.228000] printk: 24 messages suppressed.
[17336542.228000] hub 4-0:1.0: over-current change on port 3
as to /var/log, there are lots of folders and files there, but again I do not know what to look for.
Any guidance you can give me will be greatly appreciated.
-
Odyssey
Do another dmesg only pipe it through less ie. dmesg | less then to advance a page, press your space bar, to move back press B (pipe key is just under the backspace key if you didn't know). Now you can look at the output to see if it lists the hardware your looking for.
-
Also, as root:
Code:
tail -f /var/log/messages
Then plug in the drive.
What output do you get?
-
mrrangerman43, have done that and it listed hundreds of lines of output. Should I be looking for the letters "DVD" or perhaps Sony, or something less obvious? Is there a way to quickly search throught the massive output?
EnigmaOne, have done as you suggested, but it is writing a line, waiting a few seconds, then writing another, and this has been going on for several minutes now. Should it be this slow, and if not, do I need to reboot and run again, or ?
Many thanks to you both.
-
OK...let me show you what I get when I plug something into the USB:
Code:
dipsy-doodle@example.host[dipsy-doodle]$ su
Password:
root@example.host[dipsy-doodle]# tail -f /var/log/messages
Nov 3 10:36:12 localhost -- MARK --
Nov 3 10:56:12 localhost -- MARK --
Nov 3 11:15:32 localhost kernel: [17189176.752000] usb 4-1: new full speed USB device using uhci_hcd and address 2
Nov 3 11:15:32 localhost kernel: [17189176.984000] drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 1 proto 2 vid 0x03F0 pid 0x3C02
Nov 3 11:15:32 localhost kernel: [17189176.984000] usbcore: registered new driver usblp
Nov 3 11:15:32 localhost kernel: [17189176.984000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Control-C to get out of that.
You can see that, by plugging-in a printer that I'm writing a HOWTO4NOOBS about, I get some sort of immediate recognition by the machine that something has just been plugged-into the USB port. A plus would be that the OS recognizes what the device is, and registers a driver for it.
Doing an lsusb on it, while still logged-in as root:
Code:
root@example.host[dipsy-doodle]# lsusb -v
Bus 004 Device 002: ID 03f0:3c02 Hewlett-Packard PhotoSmart 7350
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x03f0 Hewlett-Packard
idProduct 0x3c02 PhotoSmart 7350
bcdDevice 1.00
iManufacturer 1 hp
iProduct 2 photosmart 7350
iSerial 3 { MASKED }
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 55
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 7 Printer
bInterfaceSubClass 1 Printer
bInterfaceProtocol 3 IEEE 1284.4 compatible bidirectional
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 7 Printer
bInterfaceSubClass 1 Printer
bInterfaceProtocol 2 Bidirectional
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
root@example.host[dipsy-doodle]#
tells me that the OS can read the device attributes, hopefully making it possible for me to use it with the appropriate driver.
Last edited by EnigmaOne; 11-03-2006 at 03:38 PM.
-
something is very wrong at my end because the output did not change when I plugged in the USB DVD writer. I stopped it and copied the last few lines which are:
Nov 3 13:35:09 Ubuntu606 kernel: [17346554.980000] printk: 4 messages suppressed.
Nov 3 13:35:15 Ubuntu606 kernel: [17346560.992000] printk: 3 messages suppressed.
Nov 3 13:35:20 Ubuntu606 kernel: [17346565.780000] printk: 3 messages suppressed.
Nov 3 13:35:37 Ubuntu606 kernel: [17346582.664000] printk: 1 messages suppressed.
Nov 3 13:35:55 Ubuntu606 kernel: [17346600.808000] printk: 1 messages suppressed.
Nov 3 13:35:59 Ubuntu606 kernel: [17346605.092000] printk: 1 messages suppressed.
Nov 3 13:36:05 Ubuntu606 kernel: [17346610.888000] printk: 1 messages suppressed.
Nov 3 13:36:11 Ubuntu606 kernel: [17346616.684000] printk: 3 messages suppressed.
Nov 3 13:36:43 Ubuntu606 kernel: [17346649.192000] printk: 1 messages suppressed.
Nov 3 13:37:08 Ubuntu606 kernel: [17346673.888000] printk: 2 messages suppressed.
Nov 3 13:37:14 Ubuntu606 kernel: [17346680.440000] printk: 5 messages suppressed.
Nov 3 13:37:19 Ubuntu606 kernel: [17346684.724000] printk: 4 messages suppressed.
Also lsusb yields:
Bus 004 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Same as posted above and same whether before or after DVD is plugged in.
It looks to me that I'm not the only one that can't find it. Neither can my computer?
-
OH. Ubuntu.
If I'm correct about this, you need to use sudo to run each of the commands I listed.
-
Got same result as without the sudo.
Also tried plugging in a known good USB flash drive. Again nothing showed up after doing this.
This computer previously ran WXP and the USB ports worked fine, so I do not expect that it is a hardware issue.
I note the "xy messages suppressed" in each line. can I "un-suppress" it so that we can see what the messages are?
-
you are running lsusb with the -v option right?
-
Am now ;<) (maybe a misadventure to assume that noobs know these things, but we're learning)
Apology for the length of this but I didn't know what I could eliminate
Bus 004 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 12
can't get hub descriptor: Operation not permitted
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 001 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 003 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 002 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
-
next time wrap in "code" tags provided by the forum
just because it works in windows doesnt mean that its functioning properly, if you have say a pci usb card laying around you might plug it in and make sure its not the usb hub itself that is the problem
-
OK, thanks for the tags guidance. Got it figured out now.
I think I can borrow a PCI USB card and will install it as a check. Will update.
-
Originally Posted by Odyssey
[17336437.248000] hub 2-0:1.0: over-current change on port 1
Something's asking for more power than your hub can provide. I would suspect this drive that you're trying to use is the culprit, since anything with an electrical motor in it is going to be a HUGE power-sucker.
If this writer has its own power cord, make sure that's plugged in. Otherwise, plug it into a USB root hub that has no other devices on it. If you still get these over-current messages, the device isn't working correctly.
(A USB hub can provide up to 500 mA to connected devices. AFAIK it's illegal according to the USB spec for a device to request more current than that. Since you'll be plugging it into a root hub, you should have the full 500 mA free, and since it'll be the only device on that hub, you should be able to allocate the entire power budget to it. If both of those is true, and it's still asking for too much power, then the problem is probably the device.)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|