To review, here is what I'm doing: 1. Posts: 4 Joined: Mon Aug 21, 2017 5:57 pm Got my new chip and it works great in the board I built, so it was definitely a problem with the original controller chip I got! Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient. Approximately 4 four weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. Some other issues are also mentioned. Thanks for sending the correct flash along.
So peeps and devs, maybe this is not a real big problem-bug-thingie, is has a very big negative impact on the Fedora-distro image, or at least on the reputation of Linux-os. One quick reboot later, and here are the final results. It sounds like maybe some kind of additional information about which thing caused this error in this case is in order. I cannot get access to my external usb hard-drives. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. You could report the bug back to the kernel team though: I had this problem with a Ubuntu 12. This update is a significant rebase from the previous version.
May 17 23:01:06 arbol kernel: hub 1-0:1. . ? I guess there was a bad batch of chips. No obvious change, with the Pi still failing to enumerate Low-Speed devices on the High-Speed hub. If I only have one hard drive and no cdrom on the machine this message goes away. No obvious change, with the Pi still failing to enumerate Low-Speed devices on the High-Speed hub.
It's been useful for taming a number of non-compliant devices and such in the past. I have a mouse and keyboard that work perfectly when plugged into the Pi, but when I use a powered hub they fail to enumerate. If you do create a new bug not it here, and reference this one and the previous one in the new bug. I'm going to write it off as equipment failure. But I finally found a solution here:. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events.
Last time I booted Windows and it updated something related to that port which I am unable to rollback. Site Moderator Posts: 29044 Joined: 4. Please read the following thread: , all of the posts. Is it possible that my microconroller isn't pre-programmed? It's hard to get any more info out of it because I can't input via keyboard or connect via ssh. I am unable to use my usb mouse as it freezes after some time.
Any other suggestions for troubleshooting? Org Server Extension, version 10. Yes the development team need to give some serious thought to this one. You can , or from your own site. This can happen either at boot if the device is already plugged or when the device is plugged later. The card reader does not, with known-working cards. In this case all I have tried are flash drives. Great to know that there is a workaround.
I can not use my mouse. I end up having to put them in other machines and then cross mount them to use them. The key mounts without problems on Windows. I have also tried to disable both ehci and uhci moduels, but in that case I can not use lsusb command. Is this bug likely to be solved any time soon or is it too hard even for the most hard core kernel hackers? Which hints that you did not install the extension pack, despite what you say later. Yet here we go again! I've checked my assembly work fairly carefully and can't see any mistakes or bad solder joints. I would think if the developers maybe started a more descriptive message then maybe closing this one and starting over with each occurring more descriptive message might be good.
If anyone gets responses from upstream, we can help build test kernels and patches if needs be. I simply don't understand how this module is loaded. Sorry I don't have a solution. I tried lsusb -v and cannot find my hard-disk. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. Regarding the update, if all of the packages successfully downloaded at some point and properly installed that should be relatively irrelevant, but you might still run e.
A few days ago I ran -Syu and updated. This is both in this message occurring and in the resulting failures. I am including a part of messages file: hub 1-0:1. All devices regardless of speed enumerated fine on the low-speed hub, even if they complained about the speed and power. I had this problem on my old laptop and it resulted in very slow access to an external optical drive. .