USB Modem - Internal stuff in Slackware ?
Hai all,
Am using a USB modem in Slackware and Fedora. In order to get it work, we need make the kernel to consider that modem as network device, not a block storage device. This can be done using "usb_modeswitch" command.
But, with Fedora laughlin this get done with out usb_modeswitch, and in Slackware too.
Before booting the machine, if I plug the modem then started the machine means, Fedora is switching the modem to [fff1] from [fff5] . But, Slackware is not doing this, it is considering the modem as a block device[ from lsusb command, the state of modem is not changed to fff1 ]. In Slackware , after I completed the login process , then I plug the modem means, it is switching to [fff1] and I can able to browse.
So, my question is, How this plugging modem before booting differs from plugging modem after login process ? How the stuffs are treated and carried out internally ?
Comments
-
linustorvalds wrote:Hai all,
Am using a USB modem in Slackware and Fedora. In order to get it work, we need make the kernel to consider that modem as network device, not a block storage device. This can be done using "usb_modeswitch" command.
But, with Fedora laughlin this get done with out usb_modeswitch, and in Slackware too.
Before booting the machine, if I plug the modem then started the machine means, Fedora is switching the modem to [fff1] from [fff5] . But, Slackware is not doing this, it is considering the modem as a block device[ from lsusb command, the state of modem is not changed to fff1 ]. In Slackware , after I completed the login process , then I plug the modem means, it is switching to [fff1] and I can able to browse.
So, my question is, How this plugging modem before booting differs from plugging modem after login process ? How the stuffs are treated and carried out internally ?
Have you attempted to create a new initrd file with the usbnet compiled into it or setting up a new udev rule to load the usbnet driver and start your configuration?0 -
Have you attempted to create a new initrd file with the usbnet compiled into it or setting up a new udev rule to load the usbnet driver and start your configuration?
No mathew. I did not tried with new "initrd" or "udev" for this.
Is that internally carried out ?
I did "pppsetup" only , for the USB modem in Slackware. Apart from that, I did not did anything manually. It is working fine if I plug-in after log-in.
thank you0 -
The intitrd is a basic image that contains the kernel modules that are necessary for bootup, and udev is what is used for new device recognition both when the system is running and when it is booting. By modifying the udev rules you can tell the system to automatically launch a set script or system event when certain hardware is detected.
But you will have to lookup the udev manual and build the proper udev even yourself.0 -
ok matt. I will gather information about udev and try to modify that accordingly, possibly this weekend and will report it.
Thank you:)0 -
In /etc/udev/rules.d/70-persistent-cd.rules files, I found the info related to the ZTE modem.
But, when the modem is in fff1,the contents are ,
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:22:04:3f:d7", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x4237 (iwlagn)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:65:26:d8:0e", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="wlan*", NAME="wlan0"
# USB_Storage_FFF1 (pci-0000:00:1d.0-usb-0:2:1.0-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="ZTE_USB_Storage_FFF1_000000000002-0:0", SYMLINK+="cdrom1", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="ZTE_USB_Storage_FFF1_000000000002-0:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
and when the modem is in ,"fff5" mode, [before switching to network device from block device]
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:22:04:3f:d7", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x4237 (iwlagn)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:65:26:d8:0e", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="wlan*", NAME="wlan0"0 -
I see that the automatic rules have set it correctly once the network device function is enabled.
You can take the lines from "fff5" mode and append them into a new file which we can call /etc/udev/rules.d/20-modem.rules which should make that state automatic.0
Categories
- 10.1K All Categories
- 35 LFX Mentorship
- 88 LFX Mentorship: Linux Kernel
- 501 Linux Foundation Boot Camps
- 278 Cloud Engineer Boot Camp
- 103 Advanced Cloud Engineer Boot Camp
- 47 DevOps Engineer Boot Camp
- 40 Cloud Native Developer Boot Camp
- 2 Express Training Courses
- 2 Express Courses - Discussion Forum
- 1.7K Training Courses
- 17 LFC110 Class Forum
- 4 LFC131 Class Forum
- 19 LFD102 Class Forum
- 148 LFD103 Class Forum
- 12 LFD121 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 566 LFD259 Class Forum
- 100 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 22 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 1 LFS203 Class Forum
- 43 LFS207 Class Forum
- 298 LFS211 Class Forum
- 53 LFS216 Class Forum
- 46 LFS241 Class Forum
- 40 LFS242 Class Forum
- 37 LFS243 Class Forum
- 10 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 131 LFS253 Class Forum
- 993 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 87 LFS260 Class Forum
- 126 LFS261 Class Forum
- 31 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 21 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 212 LFW211 Class Forum
- 153 LFW212 Class Forum
- 899 Hardware
- 217 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 208 Networking
- 101 Printers & Scanners
- 85 Storage
- 749 Linux Distributions
- 88 Debian
- 64 Fedora
- 14 Linux Mint
- 13 Mageia
- 24 openSUSE
- 133 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 355 Ubuntu
- 472 Linux System Administration
- 38 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 94 Linux Security
- 77 Network Management
- 107 System Management
- 49 Web Management
- 63 Mobile Computing
- 22 Android
- 27 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 527 Off Topic
- 127 Introductions
- 213 Small Talk
- 19 Study Material
- 794 Programming and Development
- 262 Kernel Development
- 498 Software Development
- 922 Software
- 257 Applications
- 182 Command Line
- 2 Compiling/Installing
- 76 Games
- 316 Installation
- 52 All In Program
- 52 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)