Speedy1205
Regular Contributor
Hi Guys,
I still try to figure out the issue with the LTE Modems and have a question to it.
This is how the kernel worked in version 374.42_2
and later
The newer kernel just loading all modules ????:
So the cdc_ncm is the fast driver which LTE user wants to use, even with workaround. In the new version its just loading all modules and uses the Option driver and ppp to connect the Modem to the ISP.
Is there a way I can force a device o use a specific kernel module ? I`m not so familiar with this OS, in my SUSE box I created some custom udev rules and that worked. How I can do this with this box RT-AC56U ?
Any suggestion are welcome.
PS> that's why in the new version the workaround with the services-start script doesn't work anymore because its loading the wrong modules.
I still try to figure out the issue with the LTE Modems and have a question to it.
This is how the kernel worked in version 374.42_2
Code:
Jan 1 01:00:15 kernel: scsi 0:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
Jan 1 01:00:15 kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 5
Jan 1 01:00:15 kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2
Jan 1 01:00:15 stop_nat_rules: apply the redirect_rules!
Jan 1 01:00:15 kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Jan 1 01:00:15 kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
Jan 1 01:00:15 kernel: usb 2-2: USB disconnect, address 2
Jan 1 01:00:15 rc_service: hotplug 570:notify_rc restart_nasapps
and later
Code:
Jan 1 01:00:15 kernel: usb 2-2: new high speed USB device using ehci_hcd and address 3
Jan 1 01:00:16 RT-AC56U: start httpd
Jan 1 01:00:16 kernel: usb 2-2: MAC-Address: 0c:5b:8f:27:9a:64
Jan 1 01:00:16 kernel: [B]cdc_ncm 2-2:1.2: usb0: register 'cdc_ncm' at usb-0000:00:0a.1-2[/B], Mobile Broadband Network Device, 0c:5b:8f:27:9a:64
Jan 1 01:00:16 kernel: scsi2 : usb-storage 2-2:1.3
Jan 1 01:00:16 hotplug: add net usb0.
Jan 1 01:00:16 hotplug: set net usb0.
Jan 1 01:00:16 kernel: scsi3 : usb-storage 2-2:1.4
Jan 1 01:00:16 crond[619]: crond: crond (busybox 1.20.2) started, log level 8
The newer kernel just loading all modules ????:
Code:
Jan 1 00:00:15 kernel: ohci_hcd 0000:00:0a.0: irq 111, io mem 0x18022000
Jan 1 00:00:15 kernel: hub 3-0:1.0: USB hub found
Jan 1 00:00:15 kernel: hub 3-0:1.0: 2 ports detected
Jan 1 00:00:15 kernel: usbcore: registered new interface driver usblp
Jan 1 00:00:15 kernel: usbcore: registered new interface driver asix
Jan 1 00:00:15 kernel: usbcore: registered new interface driver cdc_ether
Jan 1 00:00:15 kernel: usbcore: registered new interface driver rndis_host
Jan 1 00:00:15 kernel: cdc_ncm: 14-Mar-2012
Jan 1 00:00:15 kernel: usbcore: registered new interface driver cdc_ncm
Jan 1 00:00:15 kernel: usbcore: registered new interface driver cdc_wdm
Jan 1 00:00:15 kernel: usb 2-2: new high speed USB device using ehci_hcd and address 2
Jan 1 00:00:15 kernel: usbcore: registered new interface driver qmi_wwan
Jan 1 00:00:15 kernel: cdc_mbim: loaded
Jan 1 00:00:15 kernel: usbcore: registered new interface driver cdc_mbim
Jan 1 00:00:15 kernel: scsi0 : usb-storage 2-2:1.0
Jan 1 00:00:15 kernel: scsi1 : usb-storage 2-2:1.1
Jan 1 00:00:16 kernel: scsi 0:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
Jan 1 00:00:16 kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 5
Jan 1 00:00:16 kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2
Jan 1 00:00:16 kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Jan 1 00:00:16 kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
Jan 1 00:00:16 kernel: usb 2-2: USB disconnect, address 2
So the cdc_ncm is the fast driver which LTE user wants to use, even with workaround. In the new version its just loading all modules and uses the Option driver and ppp to connect the Modem to the ISP.
Is there a way I can force a device o use a specific kernel module ? I`m not so familiar with this OS, in my SUSE box I created some custom udev rules and that worked. How I can do this with this box RT-AC56U ?
Any suggestion are welcome.
PS> that's why in the new version the workaround with the services-start script doesn't work anymore because its loading the wrong modules.