Posted: Tue Feb 28, 2012 21:38 Post subject: WZR-HP-G300NH R18024 Konfiguration mit Huawei E398 LTE
Hallo
kann mir evtl. einer Helfen, ich habe den Buffalo WZR-HP-G300NH mit DD-WRT Firmware R18024 von BrainSlayer und bekomme keine Verbindung zustande mit dem Modem Huawei E398 (welcher auf der Kompatibilitäts liste ist)
so sehen meine WAN Einstellungen aus:
WAN Connection Type 3G/UMTS/4G/LTE
Connection Type
User Name leer
Password leer
Dial String *99***3# LTE/3.75/4G
APN internet
PIN ****
Connection type Auto 3G/2G
Force reconnectEnable Disable
beim verbinden ueber die GUI bekomme ich immer
Configuration Type
Connection Type Disabled
hier mein dmesg auszug:
<4>[ 4.490000] Realtek 8366SR switch ID 0x8366
<4>[ 8.510000] SP1000
<4>[ 8.520000] phyUnit=0 is lostlink
<4>[ 8.520000] phyUnit=1 is lostlink
<4>[ 8.530000] phyUnit=2 is lostlink
<4>[ 8.530000] phyUnit=3 is lostlink
<4>[ 8.540000] Writing 4
<4>[ 8.560000] rtl8366sr_phy_setup ethUnit=1
<4>[ 8.560000] phyUnit=4 is link
<4>[ 8.570000] Writing 6
<6>[ 8.750000] Compat-wireless backport release: compat-wireless-2011-12-01-r29460
<6>[ 8.760000] Backport based on wireless-testing.git master-2011-12-01
<6>[ 9.020000] cfg80211: Calling CRDA to update world regulatory domain
<6>[ 9.150000] cfg80211: World regulatory domain updated:
<6>[ 9.150000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
<6>[ 9.160000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 9.170000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
<6>[ 9.180000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
<6>[ 9.180000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 9.190000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<7>[ 9.960000] ath: EEPROM regdomain: 0x0
<7>[ 9.960000] ath: EEPROM indicates default country code should be used
<7>[ 9.960000] ath: doing EEPROM country->regdmn map search
<7>[ 9.960000] ath: country maps to regdmn code: 0x3a
<7>[ 9.960000] ath: Country alpha2 being used: US
<7>[ 9.960000] ath: Regpair used: 0x3a
<7>[ 9.980000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
<6>[ 9.980000] ieee80211 phy0: Atheros AR9100 MAC/BB Rev:7 AR2133 RF Rev:a2 mem=0xb80c0000, irq=2
<6>[ 9.990000] cfg80211: Calling CRDA for country: US
<6>[ 10.010000] cfg80211: Regulatory domain changed to country: US
<6>[ 10.020000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
<6>[ 10.030000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
<6>[ 10.040000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
<6>[ 10.040000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 10.050000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 10.060000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 10.070000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
<6>[ 10.740000] usbcore: registered new interface driver usblp
<6>[ 12.610000] device br0 entered promiscuous mode
<4>[ 12.640000] ag7100_ring_free Freeing at 0x838e5800
<4>[ 12.640000] ag7100_ring_free Freeing at 0x8397d000
<4>[ 12.660000] rtl8366sr_phy_setup ethUnit=0
<4>[ 12.670000] phyUnit=0 is lostlink
<4>[ 12.670000] phyUnit=1 is lostlink
<4>[ 12.670000] phyUnit=2 is lostlink
<4>[ 12.680000] phyUnit=3 is lostlink
<4>[ 12.690000] Writing 4
<4>[ 12.700000] ag7100_ring_free Freeing at 0x83000800
<4>[ 12.700000] ag7100_ring_free Freeing at 0x8397d000
<4>[ 12.720000] rtl8366sr_phy_setup ethUnit=0
<4>[ 12.730000] phyUnit=0 is lostlink
<4>[ 12.730000] phyUnit=1 is lostlink
<4>[ 12.740000] phyUnit=2 is lostlink
<4>[ 12.740000] phyUnit=3 is lostlink
<4>[ 12.750000] Writing 4
<6>[ 12.760000] device eth0 entered promiscuous mode
<4>[ 12.770000] ag7100_ring_free Freeing at 0x83000000
<4>[ 12.770000] ag7100_ring_free Freeing at 0x83bf5000
<4>[ 12.790000] rtl8366sr_phy_setup ethUnit=1
<4>[ 12.800000] phyUnit=4 is link
<4>[ 12.800000] Writing 6
<4>[ 12.820000] ag7100_ring_free Freeing at 0x83099000
<4>[ 12.820000] ag7100_ring_free Freeing at 0x83bf5000
<4>[ 12.840000] rtl8366sr_phy_setup ethUnit=1
<4>[ 12.840000] phyUnit=4 is link
<4>[ 12.850000] Writing 6
<6>[ 12.860000] device eth1 entered promiscuous mode
<6>[ 12.880000] br0: port 2(eth1) entering learning state
<6>[ 12.880000] device br0 left promiscuous mode
<6>[ 12.890000] device br0 entered promiscuous mode
<6>[ 12.900000] device br0 left promiscuous mode
<6>[ 12.910000] device br0 entered promiscuous mode
<6>[ 13.880000] br0: port 2(eth1) entering forwarding state
<7>[ 14.090000] ISO 9660 Extensions: Microsoft Joliet Level 3
<7>[ 14.110000] ISO 9660 Extensions: Microsoft Joliet Level 3
<7>[ 14.110000] ISOFS: changing to secondary root
<6>[ 22.470000] device ath0 entered promiscuous mode
<6>[ 22.470000] br0: port 3(ath0) entering learning state
<6>[ 22.680000] bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
<6>[ 22.690000] bonding: MII link monitoring set to 100 ms
<6>[ 23.480000] br0: port 3(ath0) entering forwarding state
<6>[ 24.260000] usbcore: registered new interface driver cdc_acm
<6>[ 24.270000] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
<6>[ 24.550000] usbcore: registered new interface driver usbserial
<6>[ 24.550000] USB Serial support registered for generic
<6>[ 24.560000] usbcore: registered new interface driver usbserial_generic
<6>[ 24.560000] usbserial: USB Serial Driver core
<6>[ 24.740000] USB Serial support registered for Sierra USB modem
<6>[ 24.750000] usbcore: registered new interface driver sierra
<6>[ 24.760000] sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems
<6>[ 24.850000] USB Serial support registered for GSM modem (1-port)
<6>[ 24.860000] usbcore: registered new interface driver option
<6>[ 24.860000] option: v0.7.2:USB Driver for GSM modems
<6>[ 26.690000] etherip: Ethernet over IPv4 tunneling driver
<6>[ 338.850000] br0: port 2(eth1) entering disabled state
<6>[ 363.280000] usb 1-1: USB disconnect, address 2
<6>[ 960.850000] br0: port 2(eth1) entering learning state
<6>[ 961.860000] br0: port 2(eth1) entering forwarding state
<6>[ 1286.540000] usb 1-1: new high speed USB device using ar71xx-ehci and address 3
<6>[ 1286.690000] usb 1-1: New USB device found, idVendor=12d1, idProduct=1505
<6>[ 1286.690000] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0
<6>[ 1286.700000] usb 1-1: Product: HUAWEI Mobile
<6>[ 1286.710000] usb 1-1: Manufacturer: Huawei Technologies
<6>[ 1286.720000] scsi1 : usb-storage 1-1:1.0
<5>[ 1287.730000] scsi 1:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0
<4>[ 1287.740000] sr0: scsi-1 drive
<7>[ 1287.740000] sr 1:0:0:0: Attached scsi CD-ROM sr0
<5>[ 1287.740000] sr 1:0:0:0: Attached scsi generic sg0 type 5
<4>[ 1291.340000] usb 1-1: usbfs: process 3469 (usb_modeswitch) did not claim interface 0 before use
<6>[ 1291.360000] usb 1-1: USB disconnect, address 3
<6>[ 1296.740000] usb 1-1: new high speed USB device using ar71xx-ehci and address 4
<6>[ 1296.890000] usb 1-1: New USB device found, idVendor=12d1, idProduct=1506
<6>[ 1296.890000] usb 1-1: New USB device strings: Mfr=4, Product=3, SerialNumber=0
<6>[ 1296.900000] usb 1-1: Product: HUAWEI Mobile
<6>[ 1296.910000] usb 1-1: Manufacturer: Huawei Technologies
<6>[ 1296.920000] option 1-1:1.0: GSM modem (1-port) converter detected
<6>[ 1296.920000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
<6>[ 1296.930000] option 1-1:1.1: GSM modem (1-port) converter detected
<6>[ 1296.940000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
<6>[ 1296.940000] option 1-1:1.2: GSM modem (1-port) converter detected
<6>[ 1296.950000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
<6>[ 1296.960000] option 1-1:1.3: GSM modem (1-port) converter detected
<6>[ 1296.970000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
<6>[ 1296.970000] option 1-1:1.4: GSM modem (1-port) converter detected
<6>[ 1296.980000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
<6>[ 1297.090000] scsi2 : usb-storage 1-1:1.5
<6>[ 1297.100000] scsi3 : usb-storage 1-1:1.6
<5>[ 1298.100000] scsi 2:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0
<5>[ 1298.110000] scsi 3:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2
<5>[ 1298.120000] sd 3:0:0:0: Attached scsi generic sg0 type 0
<4>[ 1298.130000] sr0: scsi-1 drive
<7>[ 1298.130000] sr 2:0:0:0: Attached scsi CD-ROM sr0
<5>[ 1298.140000] sr 2:0:0:0: Attached scsi generic sg1 type 5
<5>[ 1298.140000] sd 3:0:0:0: [sda] Attached SCSI removable disk
<7>[ 1299.630000] ISO 9660 Extensions: Microsoft Joliet Level 3
<7>[ 1299.660000] ISO 9660 Extensions: Microsoft Joliet Level 3
<7>[ 1299.660000] ISOFS: changing to secondary root
<6>[ 1425.260000] device eth0 left promiscuous mode
<6>[ 1425.270000] br0: port 1(eth0) entering disabled state
<6>[ 1425.280000] device eth1 left promiscuous mode
<6>[ 1425.280000] br0: port 2(eth1) entering disabled state
<6>[ 1425.300000] device ath0 left promiscuous mode
<6>[ 1425.300000] br0: port 3(ath0) entering disabled state
<4>[ 1430.580000] ag7100_ring_free Freeing at 0x83b12800
<4>[ 1430.580000] ag7100_ring_free Freeing at 0x8397d000
<4>[ 1430.600000] rtl8366sr_phy_setup ethUnit=0
<4>[ 1430.610000] phyUnit=0 is lostlink
<4>[ 1430.610000] phyUnit=1 is lostlink
<4>[ 1430.620000] phyUnit=2 is lostlink
<4>[ 1430.620000] phyUnit=3 is lostlink
<4>[ 1430.630000] Writing 4
<4>[ 1430.640000] ag7100_ring_free Freeing at 0x83acc800
<4>[ 1430.640000] ag7100_ring_free Freeing at 0x8397d000
<4>[ 1430.660000] rtl8366sr_phy_setup ethUnit=0
<4>[ 1430.670000] phyUnit=0 is lostlink
<4>[ 1430.670000] phyUnit=1 is lostlink
<4>[ 1430.680000] phyUnit=2 is lostlink
<4>[ 1430.680000] phyUnit=3 is lostlink
<4>[ 1430.690000] Writing 4
<6>[ 1430.700000] device eth0 entered promiscuous mode
<4>[ 1430.710000] ag7100_ring_free Freeing at 0x83b86000
<4>[ 1430.710000] ag7100_ring_free Freeing at 0x83bf5000
<4>[ 1430.730000] rtl8366sr_phy_setup ethUnit=1
<4>[ 1430.740000] phyUnit=4 is link
<4>[ 1430.740000] Writing 6
<4>[ 1430.760000] ag7100_ring_free Freeing at 0x83be8800
<4>[ 1430.760000] ag7100_ring_free Freeing at 0x83bf5000
<4>[ 1430.780000] rtl8366sr_phy_setup ethUnit=1
<4>[ 1430.780000] phyUnit=4 is link
<4>[ 1430.790000] Writing 6
<6>[ 1430.800000] device eth1 entered promiscuous mode
<6>[ 1430.800000] br0: port 2(eth1) entering learning state
<6>[ 1430.810000] device br0 left promiscuous mode
<6>[ 1430.820000] device br0 entered promiscuous mode
<6>[ 1430.830000] device br0 left promiscuous mode
<6>[ 1430.840000] device br0 entered promiscuous mode
<6>[ 1431.810000] br0: port 2(eth1) entering forwarding state
<6>[ 1442.260000] device ath0 entered promiscuous mode
<6>[ 1442.260000] br0: port 3(ath0) entering learning state
<6>[ 1442.460000] bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
<6>[ 1442.470000] bonding: MII link monitoring set to 100 ms
<6>[ 1443.270000] br0: port 3(ath0) entering forwarding state
<6>[ 1498.240000] device eth0 left promiscuous mode
<6>[ 1498.250000] br0: port 1(eth0) entering disabled state
<6>[ 1498.260000] device eth1 left promiscuous mode
<6>[ 1498.260000] br0: port 2(eth1) entering disabled state
<6>[ 1498.270000] device ath0 left promiscuous mode
<6>[ 1498.280000] br0: port 3(ath0) entering disabled state
<4>[ 1512.140000] ag7100_ring_free Freeing at 0x8317a000
<4>[ 1512.140000] ag7100_ring_free Freeing at 0x8397d000
<4>[ 1512.160000] rtl8366sr_phy_setup ethUnit=0
<4>[ 1512.160000] phyUnit=0 is lostlink
<4>[ 1512.170000] phyUnit=1 is lostlink
<4>[ 1512.170000] phyUnit=2 is lostlink
<4>[ 1512.180000] phyUnit=3 is lostlink
<4>[ 1512.190000] Writing 4
<4>[ 1512.200000] ag7100_ring_free Freeing at 0x832da000
<4>[ 1512.200000] ag7100_ring_free Freeing at 0x8397d000
<4>[ 1512.220000] rtl8366sr_phy_setup ethUnit=0
<4>[ 1512.230000] phyUnit=0 is lostlink
<4>[ 1512.230000] phyUnit=1 is lostlink
<4>[ 1512.240000] phyUnit=2 is lostlink
<4>[ 1512.240000] phyUnit=3 is lostlink
<4>[ 1512.250000] Writing 4
<6>[ 1512.260000] device eth0 entered promiscuous mode
<4>[ 1512.270000] ag7100_ring_free Freeing at 0x83a6c000
<4>[ 1512.270000] ag7100_ring_free Freeing at 0x83bf5000
<4>[ 1512.290000] rtl8366sr_phy_setup ethUnit=1
<4>[ 1512.290000] phyUnit=4 is link
<4>[ 1512.300000] Writing 6
<4>[ 1512.310000] ag7100_ring_free Freeing at 0x83042000
<4>[ 1512.310000] ag7100_ring_free Freeing at 0x83bf5000
<4>[ 1512.330000] rtl8366sr_phy_setup ethUnit=1
<4>[ 1512.340000] phyUnit=4 is link
<4>[ 1512.350000] Writing 6
<6>[ 1512.350000] device eth1 entered promiscuous mode
<6>[ 1512.360000] br0: port 2(eth1) entering learning state
<6>[ 1512.370000] device br0 left promiscuous mode
<6>[ 1512.380000] device br0 entered promiscuous mode
<6>[ 1512.390000] device br0 left promiscuous mode
<6>[ 1512.400000] device br0 entered promiscuous mode
<6>[ 1513.360000] br0: port 2(eth1) entering forwarding state
<6>[ 1523.520000] device ath0 entered promiscuous mode
<6>[ 1523.520000] br0: port 3(ath0) entering learning state
<6>[ 1523.640000] bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
<6>[ 1523.650000] bonding: MII link monitoring set to 100 ms
<6>[ 1524.530000] br0: port 3(ath0) entering forwarding state
<6>[ 1940.610000] usb 1-1: USB disconnect, address 4
<3>[ 1940.620000] option: option_instat_callback: error -143
<6>[ 1940.620000] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
<6>[ 1940.630000] option 1-1:1.0: device disconnected
<6>[ 1940.630000] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
<6>[ 1940.640000] option 1-1:1.1: device disconnected
<6>[ 1940.650000] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
<6>[ 1940.660000] option 1-1:1.2: device disconnected
<3>[ 1940.660000] option: option_instat_callback: error -143
<6>[ 1940.670000] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
<6>[ 1940.670000] option 1-1:1.3: device disconnected
<6>[ 1940.680000] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
<6>[ 1940.690000] option 1-1:1.4: device disconnected
<6>[ 2340.350000] br0: port 2(eth1) entering disabled state
<6>[ 3474.350000] br0: port 2(eth1) entering learning state
<6>[ 3475.360000] br0: port 2(eth1) entering forwarding state
root@DD-WRT:~#
Do you get a different usb id from 12d1:1505 when testing with and without TF card in the card reader? _________________ Kernel panic: Aiee, killing interrupt handler!
i have disabled the cd-rom and Cardreader with this AT command: at^setport="A1,A2;1,2,3,7"
so card will not more detected
Problem now is now more the connection, this i have solve with the startup script, but now when i connect i have only download 14 - 16 mbit when i put my modem into my PC, i get the speed of 35 - 65 mbit.
i have disabled the cd-rom and Cardreader with this AT command: at^setport="A1,A2;1,2,3,7"
so card will not more detected
Please tell me what pid's you get now with them disabled, 12d1:1505 is a previously unknown pid that
should be included for support.
Normally this modem has 12d1:1446 and will get 12d1:1506 after usb_modeswitch, is 1505 what you get before switching when the TF card is inserted?
iseek wrote:
Problem now is now more the connection, this i have solve with the startup script, but now when i connect i have only download 14 - 16 mbit when i put my modem into my PC, i get the speed of 35 - 65 mbit.
greets
IsEeK
Only 15 mbit, that is a pleasant problem
I believe this is caused by a slow serial driver and is a common problem with speedier modems connected to a router.
There is work being done elsewhere to make a new driver that is better suited for LTE and 4G speeds.
Do an lsmod and check if option.ko is loaded, if not then load it with insmod.
Then test if that gives you better speed. _________________ Kernel panic: Aiee, killing interrupt handler!
There is no need to insmod option.ko for test, your lsmod shows that the option module is already loaded and in use so you will not get any better speed.
Your first post in this thread had this as part of dmesg:
<6>[ 1286.690000] usb 1-1: New USB device found, idVendor=12d1, idProduct=1505
<6>[ 1286.690000] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0
<6>[ 1286.700000] usb 1-1: Product: HUAWEI Mobile
<6>[ 1286.710000] usb 1-1: Manufacturer: Huawei Technologies
<6>[ 1286.720000] scsi1 : usb-storage 1-1:1.0
<5>[ 1287.730000] scsi 1:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0
<4>[ 1287.740000] sr0: scsi-1 drive
<7>[ 1287.740000] sr 1:0:0:0: Attached scsi CD-ROM sr0
<5>[ 1287.740000] sr 1:0:0:0: Attached scsi generic sg0 type 5
<4>[ 1291.340000] usb 1-1: usbfs: process 3469 (usb_modeswitch) did not claim interface 0 before use
<6>[ 1291.360000] usb 1-1: USB disconnect, address 3
<6>[ 1296.740000] usb 1-1: new high speed USB device using ar71xx-ehci and address 4
<6>[ 1296.890000] usb 1-1: New USB device found, idVendor=12d1, idProduct=1506
<6>[ 1296.890000] usb 1-1: New USB device strings: Mfr=4, Product=3, SerialNumber=0
<6>[ 1296.900000] usb 1-1: Product: HUAWEI Mobile
<6>[ 1296.910000] usb 1-1: Manufacturer: Huawei Technologies
<6>[ 1296.920000] option 1-1:1.0: GSM modem (1-port) converter detected
<6>[ 1296.920000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
<6>[ 1296.930000] option 1-1:1.1: GSM modem (1-port) converter detected
<6>[ 1296.940000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
<6>[ 1296.940000] option 1-1:1.2: GSM modem (1-port) converter detected
<6>[ 1296.950000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
<6>[ 1296.960000] option 1-1:1.3: GSM modem (1-port) converter detected
<6>[ 1296.970000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
<6>[ 1296.970000] option 1-1:1.4: GSM modem (1-port) converter detected
<6>[ 1296.980000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
Where we can see an initial id of 12d1:1505, a modeswitch being done, and a resulting id of 12d1:1506.
This is done by your script, right?
Because 12d1:1505 is not in the dd-wrt 3G support library so the modeswitch can not have been done by dd-wrt.
If you disable this script and restart the router will that give you the same initial id (12d1:1505) with and without TF card inserted?
I am asking because this 12d1:1505 is reported as initial id for a couple of different sticks and they are so different that some of them are CDMA sticks and some of them are GSM sticks.
One thing all these sticks have in common is that they are also reported by other users to have initial id 12d1:1446.
So I wonder now what makes these sticks to sometimes have 12d1:1446 and sometimes 12d1:1505.
The 12d1:1505 id is anyway an id that has to be added to dd-wrt so that the modeswitch is made automatically. _________________ Kernel panic: Aiee, killing interrupt handler!
<6>[ 1.620000] usb 1-1: new high-speed USB device number 2 using ar71xx-ehci
<6>[ 1.960000] usb 1-1: New USB device found, idVendor=12d1, idProduct=1506
<6>[ 1.970000] usb 1-1: New USB device strings: Mfr=4, Product=3, SerialNumber=0
<6>[ 1.980000] usb 1-1: Product: HUAWEI Mobile
<6>[ 1.980000] usb 1-1: Manufacturer: Huawei Technologies
<6>[ 1.620000] usb 1-1: new high-speed USB device number 2 using ar71xx-ehci
<6>[ 1.960000] usb 1-1: New USB device found, idVendor=12d1, idProduct=1506
<6>[ 1.970000] usb 1-1: New USB device strings: Mfr=4, Product=3, SerialNumber=0
<6>[ 1.980000] usb 1-1: Product: HUAWEI Mobile
<6>[ 1.980000] usb 1-1: Manufacturer: Huawei Technologies
this dmesg is without any Startup Scripts.
so 12d1:1506 is supported??
greets
IsEeK
Yes 12d1:1506 is supported since long back, if it wasn't then you would not be able to communicate with the modem.
It is the id before switching, 12d1:1505, that was not supported but that is included now so the automatic modeswitch will work in the next released dd-wrt build.
Until that build is released you will have to keep your stick in the "cd-rom disabled" mode. _________________ Kernel panic: Aiee, killing interrupt handler!
Posted: Sat Jul 07, 2012 14:25 Post subject: Re: are there open Tickets for this issues ?
speedy1205 wrote:
I would like to know also if there are some changes planed and in which ticket they are working on. Any Info on this ?
There is still a lot of work remaining for the developers of new protocol modules for the linux kernel, it is not much use to do anything in dd-wrt before kernel support is finalised.
E398 can work, in future linux versions, in ethernet mode with the modules cdc_wdm and qmi_wwan.
Serial modem mode, via either cdc_acm or the option + usb-serial combo does not reach more than around 20-25 Mbps on a 680MHz Atheros cpu, mainly due to the simple USB controller and the cpu speed.
cpu usage is then around 80%.. _________________ Kernel panic: Aiee, killing interrupt handler!
Posted: Mon Jul 09, 2012 16:53 Post subject: now its clear....
OK now I see the problem of it. So I have to switsch probably my router as well and have some test with different Router Too Bad after I like the Features of DD-WRT but I hope there will be changes soon, so I can switch back