This tells usb_modeswitch to send a sequence of two SCSI commands to the \"USB storage device\": the first command is \"allow media removal\", the second is \"eject media\". This is what some mode-switching USB devices use as an indication that the Windows driver installation kit is not needed any more, and the real functionality of the device can be revealed.
The next problem could be that the sr9700 driver module will not recognize the product ID 9702, as it expects only product ID 9700. When the device switches to the actual network interface mode, it might or might not change its ID. If the product ID changes to 9700, you'll only need the usb_modeswitch part.
If the chips with product ID 9702 will work identically to chips with product ID 9700, this might work. But if there are differences, the driver will most likely not work correctly. You might see errors in dmesg output.
The command lsusb -t reveals, if your personal combination of device, OpenWrt firmware and external USB drive supports the newer and slightly faster USB 3.0 UASP Extension (USB Attached SCSI Protocol) or the older USB 3.0 block driver:
**UPDATE 2: ASIX has provided a final release driver for use with macOS 10.15.3 (Catalina) only due to updated notarization requirements from Apple as of February 2, 2020. After thorough vetting and testing in coordination with ASIX, we have updated our download links to this 2.16.0 final release build from the previous 2.15.0 and 2.15.0-Beta 1 builds both on this blog post and our driver page for affected devices.
We are leaving the original post below as it is for posterity, and recommend using the final driver set below for our USB3-E1000, and USBC-E1000 adapters. Please feel free to reach out to us directly via our contact email below, or post in the comments section with any questions or concerns you may have.
(Please note, these drivers and instructions are intended only for our Plugable manufactured adapters. If your adapter is from another manufacturer, we would suggest to reach out to that company directly for support.)
**UPDATE 1: ASIX has provided a final release driver for use with macOS 10.15 (Catalina) only. After thorough vetting and testing in coordination with ASIX, we have updated our download links to this 2.15.0 final release build from the previous Beta 1 build both on this blog post and our driver page for affected devices.
The installation of macOS 10.15 Catalina will disable older drivers for some devices and devices which rely on these drivers will no longer function until a compatible driver is reinstalled. Most Plugable products are not affected by this, with the exception of our USB Ethernet adapters that use ASIX Gigabit Ethernet chips (models: USBC-E1000, USB3-E1000, USB2-E1000, and USB2-E100).
macOS 10.15 (Catalina), is nearly here, and with it come some new Application and driver requirements. For additional details about the new DriverKit model and the transition to 64-bit application requirements, check out our other Catalina blog posts here and here.While these are positive changes for the Mac ecosystem, the new driver requirements in Catalina will take time to get used to for some driver developers. In the short term some products will have a less user-friendly installation process as driver developers adapt to these changes. The vast majority of Plugable products that work in previous versions of macOS will continue to do so without incident in Catalina. However, USB Ethernet adapters (from Plugable and others) that use ASIX chips can pose the following challenges:
Because of challenges with the beta ASIX driver installation process in 10.15, we will no longer officially recommend our ASIX-based Gigabit Ethernet adapters on macOS Catalina until ASIX has developed an updated driver version with a less cumbersome installation process.
Click the button below to download the drivers, and see the step-by-step instructions in the next section that document the driver installation and macOS Gatekeeper approval process for our USB3-E1000 and USBC-E1000 adapters, which both use the ASIX AX88179 chipset.
Are adapters from other brands affected by the Catalina update as wellYes, the latest macOS Catalina update will affect any adapters with ASIX chipsets as drivers are not included in macOS and require installation by all customers upgrading to Catalina
I have an adapter from another manufacturer and it won't work. Can I use your steps and driversSorry for the trouble! No, unfortunately not. The troubleshooting steps and drivers we have are only for the USB3-E1000, and USBC-E1000 adapters that we manufacture. We would suggest to reach out to the manufacturer of your adapter directly for support.
Will users who upgrade to Catalina with the older ASIX drivers installed get an error messageUnfortunately, not, the drivers will silently fail to load and no error messages will be presented to any user of incompatible drivers.
I bought a usb 2.0 10/100M ethernet adapter (Kontron DM9601 fast ethernet adapter) and plugged the ethernet LAN cable into it. This adapter was then plugged into a USB port. After installing the right drivers and re-configuring the IP Addresses (the ones which were there before the port damage) in Windows 7, the internet seems to have returned and the Internet works well in Windows 7. However, when I restarted the machine and opened Xubuntu, there was disappointment ahead. Even when the adapter was plugged in, there was no internet connection in Xubuntu. I configured VPN > Created a new Ethernet Connection > Deleted the existing but unusable Ethernet Connection > Set the Mac Address > Set the IP Address, netmask, Gateway, DNS Server under IPv4 Settings> Saved and closed the Network Connections box.
How do I install the drivers for DM9601 ethernet adapter in Xubuntu I firmly think that this is most likely a driver problem. I received a mini-disk during purchase of the usb-to-ethernet adapter with driver files to be installed in linux. However, I can't figure out 'How to do it!!!'. Is there anyone who can offer an easy step-by-step procedure for installation of DM9601 driver in Xubuntu I have listed the output of important commands above. If someone needs any more info, I shall gladly provide it. It is really hopeless to work without internet in Xubuntu. Installation of some softwares are very difficult without net due to dependencies and stuff. Thanks.
If you have an eth0, it appears that the internal ethernet is (sort of) working. I suggest we find out its driver and blacklist it so the two interfaces don't potentially conflict. Please edit your question to add the full result of:
Another strange thing is that the interface the driver creates is called enx00e04c534458 (the number is also the MAC address of the adapter), which is different than any ethX for native ethernet ports.
udev should detect your network interface controller (NIC) and automatically load the necessary kernel module at startup. Check the \"Ethernet controller\" entry (or similar) from the lspci -v output. It should tell you which kernel module contains the driver for your network device. For example:
Search the internet for the right module/driver for your chipset. Some common modules are 8139too for cards with a Realtek chipset, or sis900 for cards with a SiS chipset. Once you know which module to use, try to load it manually. If you get an error saying that the module was not found, it is possible that the driver is not included in the Arch kernel. You may search the AUR for the module name.
Users with Realtek 8168 8169 8101 8111(C) 8156B based NICs (cards / and on-board) may notice a problem where the NIC seems to be disabled on boot and has no Link light. This can usually be found on a dual boot system where Windows is also installed. It seems that using the official Realtek drivers (dated anything after May 2007) under Windows is the cause. These newer drivers disable the Wake-On-LAN feature by disabling the NIC at Windows shutdown time, where it will remain disabled until the next time Windows boots. You will be able to notice if this problem is affecting you if the Link light remains off until Windows boots up; during Windows shutdown the Link light will switch off. Normal operation should be that the link light is always on as long as the system is on, even during POST. This problem will also affect other operating systems without newer drivers (eg. Live CDs). Here are a few fixes for this problem.
You can roll back your Windows NIC driver to the Microsoft provided one (if available), or roll back/install an official Realtek driver pre-dating May 2007 (may be on the CD that came with your hardware).
Probably the best and the fastest fix is to change this setting in the Windows driver. This way it should be fixed system-wide and not only under Arch (eg. live CDs, other operating systems). In Windows, under Device Manager, find your Realtek network adapter and double-click it. Under the \"Advanced\" tab, change \"Wake-on-LAN after shutdown\" to \"Enable\".
It appears that setting Integrated Peripherals > Onboard LAN Boot ROM > Enabled in BIOS/CMOS reactivates the Realtek LAN chip on system boot-up, despite the Windows driver disabling it on OS shutdown.
I've got a server running CentOS 5.3 (Final; kernel version 2.6.18) which I need to add a 2nd NIC to, initially temporarily, but eventually permanently. I'm not familiar with installing drivers under Linux and have only used system-config-network-tui and editing config files (we have no version of X installed) to configure the built-in ethernet adapter.
I found a few notes stating that the Apple USB Ethernet adapter works well under Linux. We're an Apple shop, so we have plenty and that'll do for the short term while we track down a better PCI-X ethernet adapter for this server. So, I downloaded & installed (make and make install) the appropriate version of the recommended AX88178 driver (Linux 2.6.38; for \"Android 1.x/2.x/3.0, Linux kernel 2.6.14 and later\"). After plugging in the Apple USB Ethernet adapter, it does show in the results of lsusb, but does not show in the options when I run system-config-network-tui. 153554b96e