LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 08-25-2008, 04:11 PM   #1
landonmkelsey
Member
 
Registered: Jul 2001
Location: Texas
Distribution: Fedora 16
Posts: 323

Rep: Reputation: 37
1-0:1.0: unable to enumerate USB device on 4


On boot just after page 1
"Booting the kernel"

message:
1-0:1.0: unable to enumerate USB device on 4

I have kernel:
Linux localhost.localdomain 2.6.25.14-108.fc9.i686 #1 SMP Mon Aug 4 14:08:11 EDT 2008 i686 i686 i386 GNU/Linux

I did not have the problem with Fedora 8!

However all 4 ports work. I have something plugged into every port except for the internal!
(1) mouse
(2) flash memory
(3) flash memory
(4) flash memory

I just installed a new PCI card to give 5 USP 2.0 ports! On the old PCI port card I was getting several of the "unable to enumerate" messages above!

localhost (root) ~ [869]>lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 067b:2517 Prolific Technology, Inc. Flash Disk Mass Storage Device
Bus 001 Device 006: ID 0457:0151 Silicon Integrated Systems Corp. Super Flash 1GB / GXT 64MB Flash Drive
Bus 001 Device 005: ID 067b:2515 Prolific Technology, Inc. Flash Disk Embedded Hub
Bus 001 Device 003: ID 0781:5406 SanDisk Corp. Cruzer Micro 1/4GB Flash Drive
Bus 001 Device 002: ID 0409:0058 NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
localhost (root) ~ [870]>
 
Old 08-26-2008, 08:53 AM   #2
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,186

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
Typically, USB mice -- especially older ones -- fail to fully identify themselves to USB drivers according to current kernel standards. This is not a fatal error, and I just ignore it. I suspect that your F8 may have been using an older kernel. My F9 system pops that complaint when I boot it with my old Logitech Thumbwheel (wireless) mouse plugged in.
 
Old 08-26-2008, 01:32 PM   #3
landonmkelsey
Member
 
Registered: Jul 2001
Location: Texas
Distribution: Fedora 16
Posts: 323

Original Poster
Rep: Reputation: 37
not all

Thanks for the reply
(1) just bought the mouse Logitech last week

(2) I ALWAYS keep uptodate with yum update so I always have the latest kernel.

donno
 
Old 08-26-2008, 04:01 PM   #4
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,186

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
My "older kernel" comment was a reference to your "I did not have the problem with Fedora 8!" remark. And a recent purchase does not, necessarily, mean that what you paid for conforms to the most recent kernel standards. (The device may have been on the store's shelf for some time, and in the warehouse before that.)

On the other hand, I have noticed that kernel error messages tend to be written in "kernel developer" speak rather than "so, what should be done to fix the problem" speak. Or even, as I believe is your case, messages are displayed even when there is, in fact, no error and nothing that can be fixed.

In this case, as I said, you should probably ignore the message. But if you are really interested in why you're getting it, you could grab the USB kernel code and see what event is causing that message. As to why the message writer felt that the "failure to enumerate" warranted a boot-time error message, I don't really have a clue.
 
Old 08-26-2008, 04:38 PM   #5
landonmkelsey
Member
 
Registered: Jul 2001
Location: Texas
Distribution: Fedora 16
Posts: 323

Original Poster
Rep: Reputation: 37
kernel?

Thanks!

I was just report the facts!

Occasionally (too often) a tooltip pops up over a taskbar icon.

in coincidence with a desktop freeze!

Sometimes hitting Ctrl-Alt will break the freeze!

Usually unplugging/replugging the flash drive will break the freeze!

Sometimes the tooltip is flashing!

Never noticed this freeze with F8
 
Old 08-26-2008, 05:19 PM   #6
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,186

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
That sounds like a somewhat more serious problem. Over which taskbar icon is the tooltip being displayed? Or is it just a message pop-up placed above the task-bar? (One of the "new things" in F9 was "slid-up" messages.)

Anyhow, a drive error (even in a "flash" drive) can cause an (apparent) freeze. Usually, after the disk assess times out enough times -- usually 5 minutes or so -- the freeze resolves. In any case, a dmesg | tail in a console often displays the error.

I suspect that one of the memory chips in one of your flash drive may be "flaky," and that the problem you're having is unrelated to the "unable to enumerate" problem you initially asked about. (If the freeze was you initial concern, mentioning it might have resulted in advice and suggestions for a broader audience.)
 
Old 08-26-2008, 05:50 PM   #7
landonmkelsey
Member
 
Registered: Jul 2001
Location: Texas
Distribution: Fedora 16
Posts: 323

Original Poster
Rep: Reputation: 37
Thanks!..............again the problem appeared with F9

Not to suggest anything, but, I have the same flash drives I've had since 2006

and

I just replaced the PCI card that provides USB 2.0 service (as stated in the first post!

Of course something could have failed in the meantime!

It could be related to KDE 4.0.5 whose successor is due anytime!
_________________________________________________________________
Unplugging/replugging the flash memory (I think) unfreezes the desktop because it causes a little dialog concerning the flash memory to popup.
___________________________________________________________________
I will at your idea try unplugging the flash memory devices one at a time and rebooting!

If I want to use the flash drives ot NTFS, I have to access it through Dolphin first to "open" it! Once I had it down pat what to put in fstab!

I'll bet every problem disappears with F10!

Last edited by landonmkelsey; 08-26-2008 at 08:56 PM. Reason: new thought
 
Old 08-27-2008, 11:16 AM   #8
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,186

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
Re KDE: I installed KDE 4.1 from the [updates-testing] repository a few days ago. Testing of that version has been completed, and it's been submitted for inclusion in [updates], but the "dust up" over the loss of the PGP signing keys for the RHEL repositories seem to have delayed acceptance of 4.1 into [updates] for a while.

Anyhow, the KDE 4.1 does seem much more "user friendly" then the 4.0 release.

Now, re your flash drive(s), you say they're a couple of years old, so it's not impossible that a static discharge or a blow has "zapped" one of the chips in a flash drive. Did you look at the dmesg tail (or in /var/log/messages) to see if you could identify the specific offending flash drive?

<edit>
Somewhat off-topic, but you can do a ls -l /dev/disk/by-uuid to identify the UUIDs of your flash drives, and then add something like this
Code:
$ cat /etc/fstab | grep -i kingston
UUID=48A7-175E          /Kingston               vfat    defaults,noauto 0 0
to your /etc/fstab so you can mount your flash drives at a known location without needing to plug theminto a specific port.

You can, of course, set up udev rules to do that automatically, but my needs are easily satisfied by the fstab method.
</edit>

Last edited by PTrenholme; 08-27-2008 at 11:25 AM. Reason: Additional thought.
 
Old 08-27-2008, 09:07 PM   #9
landonmkelsey
Member
 
Registered: Jul 2001
Location: Texas
Distribution: Fedora 16
Posts: 323

Original Poster
Rep: Reputation: 37
removed all the flash drives

only my new APC UPS data UPS connection is connected to the new PCI USB 2.0 card I just installed!

same problem

For a while I used Gnome and (as in previous fedoras) the flash drives showed up as desktop icons

now I must open flash drives and NTFS via Dolphin

thanks for the admin facts
 
Old 08-27-2008, 10:54 PM   #10
landonmkelsey
Member
 
Registered: Jul 2001
Location: Texas
Distribution: Fedora 16
Posts: 323

Original Poster
Rep: Reputation: 37
I will look into using your comments about fstab

There was a time when I used fstab successfully!

The last time I tried, a strange code "___uid___" was necessary in column 1 for NTFS!

Talk about obfuscation!

NEW EVIDENCE:

unplugged EVERYTHING (even my brand new mouse) from the brand new USB

4 port PCI card.....no "unable to enumerate" messages!

Everything works great so I'll just think about those messages that arrived with F9

On XP Prof (I dual boot) there are no problems...everything works without a hitch
 
Old 08-28-2008, 08:55 AM   #11
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,186

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
Here's what I have in my fstab for NTFS on this laptop (which came with Vista):
Code:
$ cat /etc/fstab | grep -i ntfs
UUID=342D7D7923AC4107   /Vista                  ntfs-3g rw,defaults     0 0
UUID=2C88743C8874071C   /Vista/Recovery         ntfs-3g rw,defaults     0 0
The ntfs-3g driver gives you a way to use your NTFS partitions from Linux. Going the other direction there is a Windows driver available which you can use to to access ext2 and ext3 Linux file systems, so a dual-boot system can access some files on each other system. (Unfortunately, if your ext? fs is inside a logical volume -- which is the default for Fedora -- you can't access it from Windows.)

Re the "enumerate" message, I hope you're not surprised that removing the USB card eliminated the message.

When you say XP "works without a hitch," have you run a file system check on the USB drives from XP? (I.e, from the "properties" box, in the second tab IIRC, select the "check" option.)
 
Old 08-28-2008, 12:27 PM   #12
landonmkelsey
Member
 
Registered: Jul 2001
Location: Texas
Distribution: Fedora 16
Posts: 323

Original Poster
Rep: Reputation: 37
and I hope you are not surprised

that logically thinking, the problem could have come from

(1) the PCI card itself
(2) something on the motherboard
(3) something in one or more of the devices plugged in

more important:

I hope you are not surprised that the "enumerate" problem started the INSTANT I installed F9 (as did several other problems)

F8 was wonderful!

I presume that the numbers after the UUID are invariant between different installations of F9

UUID=342D7D7923AC4107 /Vista ntfs-3g rw,defaults 0 0
UUID=2C88743C8874071C /Vista/Recovery ntfs-3g rw,defaults 0 0
 
Old 08-29-2008, 07:50 AM   #13
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,186

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
Re UUID values: I have both Kubuntu and Fedora on this laptop, and the UUID (and fstab entries) are the same on both systems. There are commands you can use to change a device's UUID, but (unless you change your partition layout) the UUID does not change promiscuously.

Re the "enumerate problem," I'm still not convinced that it is a problem. What you've described is, I believe, more often referred to as an "informational message" rather than a "problem," although your later flash drive issue does sound like it might be a developing problem.

Remember that Fedora is, essentially, the Red Hat beta test system for their commercial RHEL offering, and that, as such, it contains much code that is very close to the "bleeding edge" of Linux development. So it's not too unexpected that error detection may be more sensitive in Fedora code than is code further from the edge.

For example, I recently added a Hitachi 320GB SATA drive to this laptop and every time I boot Fedora, I get these "error" messages:
Code:
ata2.00: ATA-8: Hitachi HTS543232L9A300, FB4OC40C, max UDMA/133     
ata2.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)        
ata2.00: configured for UDMA/133                                    
ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x2 frozen
ata2.00: irq_stat 0x08000000, interface fatal error                   
ata2: SError: { 10B8B Dispar }                                        
ata2.00: cmd 25/00:08:d9:d5:42/00:00:25:00:00/e0 tag 0 dma 4096 in    
ata2.00: status: { DRDY }                                             
ata2: hard resetting link                                             
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)                          
ata2.00: configured for UDMA/133                                                
ata2: EH complete
...
ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x780000 action 0x2 frozen
ata2.00: irq_stat 0x08000000, interface fatal error
ata2: SError: { 10B8B Dispar BadCRC Handshk }
ata2.00: cmd c8/00:08:91:22:06/00:00:00:00:00/e0 tag 0 dma 4096 in
ata2.00: status: { DRDY }
ata2: hard resetting link
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata2.00: configured for UDMA/133
ata2: EH complete
after which the system boots and rums with no problems I can find.

Neither Kubuntu 8.10 nor Vista (SP1) report any drive problems, nor does Fedora after the initial RAM disk image loads the system from the hard drive.

So I just ignore the messages.
 
Old 08-29-2008, 03:34 PM   #14
landonmkelsey
Member
 
Registered: Jul 2001
Location: Texas
Distribution: Fedora 16
Posts: 323

Original Poster
Rep: Reputation: 37
thanks! sounds reasonable

I learned something
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Unable to detect USB storage device in SLED10 xeroblast SUSE / openSUSE 1 11-22-2007 09:06 PM
unable to write on usb mass storage device just started linux Linux - Hardware 1 09-03-2006 01:33 AM
Unable to unmount USB device gsathya MEPIS 3 07-27-2006 12:07 AM
"Unable to open USB device "usb://hp/LaserJet%201000": No such device" lordshipmayhem Mandriva 2 08-08-2004 04:56 PM
HP Deskjet (USB) & CUPS & Slackware 9.1: Unable to open USB device "usb:/dev/usb/lp0&qu arnostienen Slackware 2 01-29-2004 03:22 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:29 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration