Switching to an UMTS-Stick with less powerusage the errors goes away. Is there any place we can track the status of bugs and unimplemented features in the current firmware? Logged glimmer (OP) g Posts: 119 Re: USB support is still seriously bugged. « Reply #2 on: January 10, 2014, 10:03:21 PM » Quote from: zear on January 10, 2014, 08:23:46 Thanks, Bernd Reply With Quote 04-03-2005,19:50 #2 tatnat View Profile View Forum Posts View Blog Entries View Articles Registered User Join Date Mar 2005 Posts 3 Problem fixed by using a have a peek here
Unloading the OHCI-Driver doesn´t help. I am trying to remove the module ehci-hcd by writing command in the start up file but getting error , cannot unload module is not available. One fix vom NBD was a backbort on the 3.10 kernel for while, but this don´t solve the problems on the older v1.1 Version. The module compiled fine and its also loaded without complains.
Changed by anonymous Author Your email or username: E-mail address and user name can be saved in the Preferences. Mostly simple reboots doesn´t solve anything, only hard resstarts. You may use WikiFormatting here. So my conclusion is: There is NO Power-Problem on the v1.1 Model, because with an extra hub in the middle, this combination consumes more power as without - but it works
Changed by anonymous Author Your email or username: E-mail address and user name can be saved in the Preferences. When the stick is detected, normaly i can plug it in and out, and it is every time detected without problems. Using TP-link firmware does not have this bug The Entire Situation on actual trunk is absolutely sporadic and it looks like that some registers left in a tri-state or are not With the older v1.1 model, there is a timing issue, as this results from the "different" d+/d- coupling/pulldown/pullup, or something else.
My connections are failing and I am seeing errors in the kernel log. If there's any testing I can do to help, I'm willing to do so. The 1.2 Version mostly works WITHOUT a hub, the 1.1 Version mostly NEVER works with this stick (without a extra HUB!) I compared the Hardware inside, and figured out, that on Gee, maybe I should give some money to the development effort - maybe that will get their attention. - Randy Adv Reply Page 1 of 2 12 Last Jump to
By hugo in forum WL-500g Q&A Replies: 8 Last Post: 03-01-2005, 12:01 video device By cardoso99 in forum WL-500g Q&A Replies: 0 Last Post: 08-06-2004, 10:43 Tags for this Thread ftdi, great hint tnx a lot! Today I can't reproduce the issue at all. Is it a flash drive, an external hard disk, a printer?
But the error seems to be even before the module is needed. Product=USB2.0_Hub Serial=? 05e3 0608 Sun Jun 8 18:17:06 2014 user.notice usb-modeswitch: Ignoring Unnamed Hub Sun Jun 8 18:17:16 2014 kern.info kernel: usb 1-1.3: new high-speed USB device number 6 using ehci-platform Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks !
Last edited 22 months ago by john410 (previous) (diff) comment:15 Changed 22 months ago by anonymous On WR710N-Models there is a big difference between H/W-Version 1.1(blue LED) and 1.2(green LED)! navigate here Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [ubuntu] [SOLVED] USB: device not accepting I opened up booth devices and check for different hardware, the flash/ram/cpu is exactly the same: AR9331-AL3A (Taiwan) - so the cpu is 100% the same! But i figured out, that the usb-connectors "feeding" is a little bit changed with extra condensors and a few SMD parts are replaced/changed?
if this happens again, i'll try shutting the power to the screen off as well. comment:2 Changed 2 years ago by jmomo I am having very similar problems with at least two different TP-Link TL-WR710N. Errno 145 I found only for asm-mips and it says something like timeout. http://cloudindet.com/usb-device/usb-device-not-recognized-windows-8-device-descriptor-request-failed.html hub.c: new USB device 00:03.0-1, assigned address 2 usb.c: USB device not accepting new address=2 (error=-145) hub.c: new USB device 00:03.0-1, assigned address 3 usb.c: USB device not accepting new address=3
tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky
i was trying BB latest revision because of some driver tweaks and found out i'll have to try it with CC to be able to test everything i intended (ath9k_htc) while
Please note: The HUAWEI E3276 has an internal USB-Switch included for his NDIS and COM-Ports - all USB 2.0! - Why an extra passive HUB fix all this USB2.0 issues i This fix worked great with MR34xx-Series and WDR3600 comment:16 Changed 20 months ago by john410 Any news about this? Here is my dmesg-log after cold boot: usbcore: registered new interface driver usb-storage usb 1-1: new high-speed USB device number 2 using ehci-platform jffs2: notice: (333) jffs2_build_xattr_subsystem: complete building xattr subsystem, Visit the Trac open source project athttp://trac.edgewall.com/ Search: LoginPreferencesHelp/GuideAbout TracRegister WikiTimelineRoadmapBrowse SourceView TicketsNew TicketSearch Context Navigation ← Previous TicketNext Ticket → Modify ↓ Opened 2 years ago Last modified 13 months
Getting errors when connecting a mice or keypad: [ 21.410000] usb 1-1: device descriptor read/64, error -145 [ 36.700000] usb 1-1: device descriptor read/64, error -145 [ 36.930000] usb 1-1: new So the Asus communicates with the hub and the hub with my device. THis is a over current event which is triggered when dongle tries to consume more power . this contact form I was having problem with a mp3 player and with your line its fixed now, really awesome!!
So this time it is no "pll-loop/reset" problem, comming from wifi-devices, etc.! According to the dmesg attached the usb device is managed by the ehci driver: [ 6.230000] usb 1-1: new low-speed USB device number 2 using ehci-platform The ohci driver doesn't found Logged zear Moderator Posts: 2377 Re: USB support is still seriously bugged. « Reply #3 on: January 10, 2014, 11:20:30 PM » Quote from: glimmer on January 10, 2014, 10:03:21 PMQuote Board index The team • Delete all board cookies • All times are UTC - 8 hours Powered by phpBB Forum Software © phpBB Group
I can't wait to go back to my MR3020 with OpenWrt awesomeness, but so far this USB issue makes it unreliable for using when on the go. Update your scripts to load br_netfilter if you need this. [ 2.160000] 8021q: 802.1Q VLAN Support v1.8 [ 2.180000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2. [ 2.180000] Freeing Sun Jun 8 18:17:46 2014 daemon.notice netifd: wan (1888): Lease of 10.35.249.93 obtained, lease time 518400 Sun Jun 8 18:17:46 2014 daemon.notice netifd: Interface 'wan' is now up Sun Jun 8 comment:10 Changed 2 years ago by nbd please test if current trunk with linux 3.14 handles it better.
DistroUbuntu Re: USB: device not accepting address, new high speed USB device using ehci_hcd... This made me laugh (a little bit hysterically) I have been pulling late nights, having rows with my missus turning up late for work etc trying to get this #[email protected] hard Eventually there is a timing problem with initialisation/detection of the external devices. So it seems this is probably an issue with the archer chipset, I wonder if this is the only solution to this annoying problem?
Results 1 to 2 of 2 Thread: USB device not accepting new address=2 (errno=145) Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Rate This Thread Current Rating lo between messages i determined it was the 4 port hub on my dell screen. Total pages: 8128 Kernel command line: board=TL-WR710N console=ttyATH0,115200 rootfstype=squashfs,jffs2 noinitrd PID hash table entries: 128 (order: -3, 512 bytes) Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash I have no idea where to start.
Again: Only a passive hub finaly fix the usb 2.0 issues. The v1.8 and one of the v1.9s present errors with the Huawei E3276 modem: The other v1.9 works flawlessly with the same modem, always. I had the same problem, your ehci_hcd line has solved my usb woes.