I installed Ubuntu 9.10 to my USB-HDD. After upadte, ubuntu can`t load with error:
usb 5-1: device description read/64: error -32
usb 5-1: device description read/8: error -71
hub 5-0:1.0: unable to enumerate USB device on port 1
The boot stopped after this strings.I reinstall the system, and I have this problem again.
Doing a dmesg I can see following lines
[ 130.876406] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 130.876453] usb 3-2: USB disconnect, address 6
[ 131.200399] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 131.396382] hub 1-0:1.0: unable to enumerate USB device on port 4
[code]....
That is what I have exactly pluged, the webcam on the top of my screen and an external mouse. Btw, I can plug USB devices with no problem, so I am skiping this error since long time ago, but I don't understand this message and I would love to do it.
i have this error in my log but i don't know why?
Quote:
Jun 19 20:34:08 localhost kernel: [352155.875643] hub 2-1:1.0: unable to enumerate USB device on port 2
Jun 19 20:34:08 localhost kernel: [352155.851515] usb 2-1.2: new low speed USB device using ehci_hcd and address 17
Jun 19 20:34:08 localhost kernel: [352155.677964] usb 2-1.2: device descriptor read/64, error -32
Jun 19 20:34:08 localhost kernel: [352155.503404] usb 2-1.2: device descriptor read/64, error -32
[code]....
The Motherboard is a Intel Desktop Board DH55TC, Sockel 1156, mATX, HDMI
After installation I boot a few times and used F15 on my Dell Inspiron 1564. But now I can't boot anymore. The screen just shows "unable to enumerate USB device on Port 4" and just hangs there with a blinking cursor below that line. I have no USB devices attached though.
View 2 Replies View RelatedI'm running Slackware 13.37 64 bit. I run it on an HP2945SE AMD Turion x2. I am getting an error during boot up unable to enumerate USB device on port 5. It filters throughout the rest of the boot up commands / results. It doesn't seem to matter if things are plugged up to the USB ports or not. Also it doesn't seem to affect anything on the computer. Its just irritating.
View 2 Replies View RelatedRecently my Ubuntu 10.04 was booting slow and to figure out what was going wrong, I booted Ubuntu in text mode. There I found it was hanging on for 5-6 sec showing "unable to enumerate usb device to Port 1". I know it has something to do with Port1 / usb device, but could not understand and solve it.
View 3 Replies View RelatedStartup script. I have a problem with an error on system boot:
hub 2-0:1.0:unable to enumerate usb device on port 5
This error is continuous, filling up my system logs. It is also a known kernel bug. I found a solution here: [URL] but it is only good after I boot. I have tried to make a startup script in /etc/init.d in the following manner.
sudo mkdir /opt/usb/
sudo gedit /opt/usb/usbproblem.sh
#!/bin/bash
# chkconfig: 345 91 19
# description: stop usb problem on startup
case $1 in
*)
echo "fixing usb problem"
cd /sys/bus/pci/drivers/ehci_hcd
sh -c 'find ./ -name "2-0:1.0" -print| sed "s/.///">unbind'
cd ~
esac
exit 0
#End of boot script
##
sudo cp /opt/usb/usbproblem.sh /etc/init.d
cd /etc/init.d
sudo chmod +x usbproblem.sh
sudo update-rc.d usbproblem.sh defaults 92 20
but it does not work.
Getting this constantly in messages:
Mar 13 18:33:26 cjbLT2 kernel: [ 7523.361079] hub 4-0:1.0: unable to enumerate USB device on port 5
Mar 13 18:33:26 cjbLT2 kernel: [ 7523.567075] hub 2-0:1.0: unable to enumerate USB device on port 5
Mar 13 18:33:26 cjbLT2 kernel: [ 7523.739110] hub 4-0:1.0: unable to enumerate USB device on port 5
Mar 13 18:33:26 cjbLT2 kernel: [ 7523.945101] hub 2-0:1.0: unable to enumerate USB device on port 5
[code]....
This is on my laptop. I have 3 external USB devices plugged in but this will happen when I boot without them plugged in too. Don't seem to be missing any device either. This wasn't happening on openSuSE 11.2 and just started when I upgraded it to 11.4.
I installed Centos 5.4 on my Pentium E5300 new comp, but I need IPX support in my work. It's simple - ipxutils and ncpfs from Fedora Core and new kernel with ipx support. I copied kernel config from /boot folder and activate ipx, ntfs support, and choose processor core 2 duo. New kernel (2.6.26) works OK, but I got one problem - when start it still shows message: "kernel: HUB 1.0:1.0 unable to enumerate USB device on port 1 (or 2, 3)" and stops after logging (text mode)
I got 2 USB devices connected - printer HP D5160 PhotoSmart and Scanner A3 USB Mustek, and I know scanner cause that messages but I don't understand why. Kernel config is the same like that from distro kernel (almost - ipx, ntfs and proc), but distro kernel doesn't do that. So I got 2 questions:
1. Why
2. What to do to stop that (disconnecting devices on boot time is not a solution)
I noticed this message "hub 1-0:1.0: unable to enumerate USB device on port 4" appear before the kernel says "no resume image found loading normal init" or something along these lines. Basically what I mean is, this message shows up whenever the kernel loads. So I checked if anything is logged in /var/log/messages (are messages like these logged???), did not find anything in the log.
I then used this command, which showed up the message I was looking for.
dmesg | grep -i enumerate [ 2.379748] hub 1-0:1.0: unable to enumerate USB device on port 4
My USB mouse and other USB hard drives are working fine, without any problem. I just wanted to know if this is some kind of bug. I did some search I found this link , [URL], where this kind of bug was discussed. Looks like they closed the bug.
here is my lspci output:
$ lspci
00:00.0 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP67 ISA Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP67 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
[Code].....
I installed ZTE MF 626 modem in my F10 with kernel 2.6.27.12-170, i run usb_modeswitch and so far things happened normally. Watching through /var/log/messages it says that F10 detects two port device for this modem: ttyUSB1 and ttyUSB2, and in the sequence it disable port ttyUSB1 BUT Network Manager still set this port.I mean, when i connect via wvdial appointing to ttyUSB2 i get connection, but Network Manager fails to do it appointing to ttyUSB1. How to change device port in Network Manager?
View 1 Replies View RelatedMy computer won,t boot up anymore, i keep getting the following mistake message: Unable to enumarate usb device on port 2. Don,t know how to skip that, and continue to desktop.
View 6 Replies View RelatedI need to know how GRUB is enumerating my drives. My disk layout as seen by the System Monitor is thulsy (??):
[Code]...
I'm not that great with mailservers, and just been thrown a curveball with a MS Exchange environment for which there is apparently no solution... yeah, right. But is there a workaround?
The problem is that the site mail (SMTP) needs to be sent via port 26 instead of the commonly used 25. Port 25 is mapped to a mailfilter, which apparently causes havoc with some of the mail, and the techs that have been on site trying to coax the Exchange server to co-operate have said that the only way would be to get rid of the filter.
The problem is that there are number of apps that are unable to have the outgoing port changed and so keep sending mail out on port 25.
I look after the Unix/Linux side of things at work, and I was wondering if there was an easy way to set up a Ubuntu box to receive mail on port 25 and just forward it to the MS box on port 26? So, in other words (and I hope this makes sense): monitor port 25, and forward whatever comes in on port 25 to the server on port 26. Simple portforwarding, or is it? What steps do I need to take?
All my music editing software programs say, "unable to open device /dev/dsp.Device or resource busy." How can I fix this?
View 3 Replies View RelatedI'm trying to move an existing FC10 install (created by someone else) from a 160GB WD1600AAJS SATA disk to a 160GB WD1600AAJB PATA disk (cursed trend of horizontally mounting SATA connectors at the end of the motherboard means the latest rev mobo doesn't fit in our enclosure!). I've used DD to copy the disk image from one to the other, but when attempting to boot, I get the following error:
Code:
Unable to access resume device (UUID=946f216f-0c24-4b02-a996-f42059970de7)
mount: error mounting /dev/root on /sysroot as ext3: no such file or directory
That particular UUID maps to sda2, which is the swap partition. Interestingly, both the SATA and PATA disk come up as /dev/sda on the motherboard. I kind of grok that the UUIDs are substitutes for directly naming the disks, and that they're referred to in fstab, initrd-2.6.27.12-170.2.5.fc10.i686.img, and in /dev/disk/by-* I'm guessing the problem is that the GUIDs (at least the one for swap) are no longer the same. How are they assigned to the partitions during boot?
I tried doing
Code:
swapoff -a
mkswap /dev/sda2
swapon -a
and put that new GUID in fstab and into initrd-* (using some steps I found elsewhere on how to gunzip/rezip it).At that point, I get a kernel panic on boot
Code:
Kernel panic - not syncing: CFS: Unable to mount root fs on unknown-block(0,0)
So I'm guessing that the other UUUDs have changed as well and I need to update them. How would I figure out what they are? I suppose I could change the references to /dev/sda*, but I didn't build this original image and I'm thinking whoever did had a good reason to go with UUIDs.
I have a host and a client both running linux. Host has internet through eth2. Client needs to share that connection. The computers are connected directly using a crossover. I can ping from both fine. I figured I needed to port forward eth2 to eth0 to gain internet access in the client. How?
Code:
eth0 Link encap:Ethernet HWaddr 00:26:18:a6:fd:a3
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::226:18ff:fea6:fda3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[code]...
been trying to use a rs232 device that uses the usb port. it calls for a virtual com port to be created. i am running on ubuntu 10 and get hella confused with the search results i have come across.some call for the usbdevfs which apparently doesn't exist under lucid. another had me do use some "magic" in getting it to work.they provided a script mountusbfs.sh
Code:
#
# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
[code]....
of course when i tried it the domount command doesn't exist so i modified the above script replacing the domount with mount and it seemed to do something things. usbview is specified as the determining factor whether or not you have the usbfs mounted properly. it wants to use proc bus and ubuntu doesn't use that anymore apparenlty. i have read that i need to enable a usbmon (flag?option?) in the kernel to be set. which it isn't when i followed the steps to check.
I am trying to use the printer port. But, I get this
Code:
Broadcom EJTAG Debrick Utility v1.6r-hugebird
Failed to lock /dev/parport0: No such device or address
johnh@tux:~/Ubuntu One/hh$
run from johnh I permission denied sudo-ing I get above.
tell me detection code of device when an external device is connected through USB port.
View 4 Replies View RelatedInstalled a TP-Link TG-3269 Gigabit card in a machine running OS 11.3 32 bit, when I go into Yast, Network Devices, Network to try configuring the card I get this errormsg: Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details. Couldn't find any mention of the card in dmesg's output, (though the 8139 onboard card is in there) there is some stuff about pci host bridge but I don't know whether they would be relevant or not
The chip on the card says it's rtl8169sc but lspci lists it as being 00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8369 (rev 10) Done some googling and there don't seem be any drivers for a Realtek 8639 and it returns no matches from a search on realtek's site, but there is a driver there for rtl8169sc chips, which I downloaded and installed, no errors when installing it Even after a reboot I still get the same error in Yast's Network Settings screen, lspci still lists it as 8369 and the device isn't listed at all if I run ifconfig
I am building a custom RedHat+<our-software> installer iso for our own appliance. I am using Red Hat 5.4. The appliances has two on-board eth interfaces. On the back panel of the appliance, these ports are marked 1 and 2. When I install RH, I find the device names assigned such as eth0/eth1 are arbitrary. I understand this is to be expected with kernels 2.6+. Most of our customers connect their eth cables to the port marked 1 on the back and assume they should configure eth0 to make the device reachable. However, sometimes port 1 gets assigned "eth1". This is not a blocking issue, but its going to confuse our customers and we wanted to make it easier on them.
From reading online discussion boards, I know HOW to switch the assignment of the eth names. However, what I am do not know is whether I need to switch them at all. So I have two questions
1) Is there anyway for me to tell which eth mac corresponds to which port on the back? Since they are soldered on the motherboard and not movable, I would think there would be some way to figure out that x mac address corresponds to the upper port (marked '1' etc).
2) Is there a way to tell this by running a linux command? We need to do this automatically so I need to be able to figure it out at install time from the kickstart post-install or similar.
i want to secure the USB port by any external device connection. so i need the code of detection of an external device when plugged in the USB port.
View 1 Replies View RelatedAfter new installation of slackware 13 when I plugin usb device in the usb port it's print error:
And I have not premission on the device and I must mount the device handle. I
I want to install Debian with USB. I'm using unebootin for this situations. I have installed,a lot of GNU/Linux with unebootin. But not Debian. When I boot with USB, Debian cannot mount the CD-ROM. The error is (in the black screen) : UNABLE TO ENUMARETE USB DEVCE N PORT 1
View 8 Replies View RelatedI just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:
[Code]....
I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
[Code]....
If I forward port 5764 to port 80 to my VOIP device, I can nmap and get a proper connection. If I forward port 5764 to port 22 to my server, it comes up filtered. It even happens if I try forwarding port 80 to my server. So I'm sure it has something to do with my server, but I'm not sure.Here's my Linksys iptables:
Code:
:wanin - [0:0]
-A FORWARD -i vlan1 -j wanin
[code]....
I want to install a TUSB3410 USb to serial port device on suse 10.3.
View 1 Replies View RelatedI have (at least 4) native USB ports that contain flash drives. I know that the /dev/sd[abcd] devices are created in the order they were inserted, but say you have all four plugged in at boot time, or further, they can be plugged and unplugged in real time. At times, /dev/sdf, /dev/sdg, etc. are created as well. I'm ignoring external hubs for now.
I need to know which drive is plugged into the "top port on the front panel", etc, by physical location. From dmesg I can check right after booting and get the physical assignment of a PCI device, say, PCI 0000:00:10.3, as being assigned to the EHCI usb bus. From /proc/bus/usb/devices, and the "T:" field, I have learned that the physical connectors I'm interested are known as USB Bus 1, Port=00, Port=01, Port=04, and Port=05.
From lsusb I can see all sorts of information from the USB point of view, but with no /dev/sd references.
From /proc/scsi/scsi, I can see what scsi devices have been created, with a count consistent with the number of flash drives plugged in, but no USB data.
So, I can get lots of information from the USB storage point of view, and lots of information from the SCSI point of view, but nowhere can I find how to correlate them. In other words, if I want to mount the drive plugged into a given physical slot, how can I find the /dev/sd device I need to mount? udev isn't really interesting here, because I'm just looking for the information that udev would use to answer the same question.
I've done some heaving exploring in the /sys and /proc filesystems and have not yet found where the USB and SCSI worlds intersect.
The closest I have found is (where "Port" is the physical port number from above):
This seems to have some mapping to the physical port and references a "/dev/sd[a-z]" value, but I don't know how reliable it might be, nor do I know if my having to increment that physical port by 1 is meaningful. Anyone have a simpler approach?
So, my goal becomes
mount /dev/<sd that was created for the top slot> /mnt/top
mount /dev/<sd that was created for the bottom slot> /mnt/bottom etc.
the message on the title only happens with Ubuntu. In Fedora, it just stops booting from LiveCD with "WARNING: Cannot find root file system!". The rest of the symptoms are the same.I'm trying to install Fedora LiveCD on an IBM i Series notebook (model 1161-21X). It's a Celeron powered unit with RAM expanded to 512MB. It has a 10GB HDD, and an internal CD-ROM drive. Although it has two USB ports (1.1), it cannot boot from a USB drive, so no pendrive nor external CD unit solution possible.When I boot from LiveCD, it stops booting with the message above. Looking atsg, there's no CD-ROM driver loaded. Also, there's a char device for sg0, but no block device for it, so no way to mount it. It seems that the driver module has been removed from the kernel. I'm currently running Fedora Core 5 in it. This very same problem happens with any Ubuntu newer that 6 or any Fedora post 7.
View 2 Replies View Related