![]() Kernel panic: Aiee, killing interrupt handler! That is a problem in the last 2 builds, a kernel driver error which I believe Brainslayer has fixed now. ![]() Usb 1-1: usbfs: process 1236 (usb_modeswitch) did not claim interface 0 before useĮth1: link up (1000Mbps/Full duplex) Usb 1-1: usbfs: process 1003 (usb_modeswitch) did not claim interface 0 before use Usbcore: registered new interface driver optionīr0: port 2(ath0) entered forwarding state USB Serial support registered for GSM modem (1-port) Usbcore: registered new interface driver usbserial_generic USB Serial support registered for generic Usbcore: registered new interface driver usbserial Usb 1-1: new high-speed USB device number 2 using ar71xx-ehci Usbcore: registered new device driver usbĮhci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) DriverĪr71xx-ehci ar71xx-ehci.0: Atheros AR91xx built-in EHCI controllerĪr71xx-ehci ar71xx-ehci.0: new USB bus registered, assigned bus number 1Įhci_reset Intialize USB CONTROLLER in host mode: 3Īr71xx-ehci ar71xx-ehci.0: irq 3, io mem 0x1b000000Īr71xx-ehci ar71xx-ehci.0: USB 2.0 started, EHCI 1.00 ![]() Usbcore: registered new interface driver hub Usbcore: registered new interface driver usbfs S: Product=Atheros AR91xx built-in EHCI controller S: Manufacturer=Linux 3.3.8-svn19342 ehci_hcd ![]() Does anyone have any ideas on what I'm doing wrong?Īccording to this link it should work with OpenWRT so why doesnt it work also with DD-WRT? I have been trying for hours to get my new TP-Link WR703N with DD-WRT (SVN revision 19342) to work with my Huawei E353 modem (3.se branded)Īccording to the modem summary it should work but i cant get the modem to connect. Posted: Mon 18:14 Post subject: Problems with Huawei E353 modem on TP-LINK WR703N ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |