NSLU2-Linux
view · edit · print · history

Peripherals.EthernetAdapter History

Hide minor edits - Show changes to markup

April 10, 2011, at 10:41 PM by player61784 --
Changed line 26 from:
  1. Go to /opt/lib/modules (Unslung) or /lib/modules (other OSes) or /lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o (newer Unslung)
to:
  1. Go to /opt/lib/modules (Unslung) or /lib/modules (other OSes) (exact: /lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o)
April 10, 2011, at 10:36 PM by player61784 --
Changed line 26 from:
  1. Go to /opt/lib/modules (Unslung) or /lib/modules (other OSes)
to:
  1. Go to /opt/lib/modules (Unslung) or /lib/modules (other OSes) or /lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o (newer Unslung)
January 18, 2010, at 04:39 PM by Ernst J Oud --
Changed line 15 from:
  • RTL8150 based (e.g. Sitecom LN-013) (kernel-module-rtl8150)
to:
  • RTL8150 based (e.g. Sitecom LN-013, Linksys USB100M?) (kernel-module-rtl8150)
January 10, 2010, at 01:19 PM by Ernst J Oud --
Changed lines 6-7 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)
to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS USB200M-DE (Version 1 only)) (kernel-module-usbnet)
January 07, 2010, at 07:02 PM by Ernst J Oud --
January 07, 2010, at 07:01 PM by Ernst J Oud --
Changed lines 8-9 from:
 ** (July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
to:
  • (July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
January 07, 2010, at 07:00 PM by Ernst J Oud --
Changed lines 8-9 from:
  • (July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
to:
 ** (July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
January 07, 2010, at 06:59 PM by Ernst J Oud --
Changed line 7 from:

to:
Added line 9:
Added line 11:
Added line 13:
January 07, 2010, at 06:59 PM by Ernst J Oud --
Added line 7:

January 07, 2010, at 06:56 PM by Ernst J Oud --
Deleted line 6:
January 07, 2010, at 06:55 PM by Ernst J Oud --
Added line 7:
January 07, 2010, at 06:54 PM by Ernst J Oud --
Changed lines 7-14 from:
(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine.)

to:
  • (July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
  • (February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)
  • (January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine.)
January 07, 2010, at 06:53 PM by Ernst J Oud --
Added line 8:
January 07, 2010, at 06:53 PM by Ernst J Oud --
Changed lines 6-7 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)
(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

January 07, 2010, at 06:52 PM by Ernst J Oud --
Changed lines 8-9 from:

>-(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

to:
(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

January 07, 2010, at 06:51 PM by Ernst J Oud --
Changed lines 8-10 from:
(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

to:

>-(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

January 07, 2010, at 06:51 PM by Ernst J Oud --
Changed lines 7-8 from:



to:
January 07, 2010, at 06:51 PM by Ernst J Oud --
Changed lines 6-7 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)



January 07, 2010, at 06:50 PM by Ernst J Oud --
Changed lines 6-7 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

January 07, 2010, at 06:50 PM by Ernst J Oud --
Changed lines 10-11 from:
(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

to:
(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine.)

January 07, 2010, at 06:48 PM by Ernst J Oud --
Changed lines 6-7 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

January 07, 2010, at 06:48 PM by Ernst J Oud --
January 07, 2010, at 06:47 PM by Ernst J Oud --
Changed lines 6-11 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS USB200M-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)\\\ (February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on [=AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS USB200M-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html) ->(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on [=AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

January 07, 2010, at 06:46 PM by Ernst J Oud --
Changed lines 6-11 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS USB200M-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html) (February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on [=AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS USB200M-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)\\\ (February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on [=AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

January 07, 2010, at 06:45 PM by Ernst J Oud --
Changed line 7 from:

//

to:
Changed line 9 from:

//

to:
Changed line 11 from:

//

to:
January 07, 2010, at 06:44 PM by Ernst J Oud --
Changed lines 6-9 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)

(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

//

Changed line 9 from:
to:

//

Changed line 11 from:
to:

//

January 07, 2010, at 06:41 PM by Ernst J Oud --
Changed lines 6-7 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)\\
to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)
Added line 9:
Added line 11:
January 07, 2010, at 06:40 PM by Ernst J Oud --
Changed line 6 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)
to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)\\
January 07, 2010, at 06:40 PM by Ernst J Oud --
Changed lines 6-7 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)
    (July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)\\
to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)

(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

Changed lines 9-10 from:

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

to:

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

January 07, 2010, at 06:39 PM by Ernst J Oud --
January 07, 2010, at 06:39 PM by Ernst J Oud --
Changed lines 9-10 from:

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

to:

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

January 07, 2010, at 06:38 PM by Ernst J Oud -- Added info on rev 2.0 of Linksys USB200M
Changed line 6 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS USB200M-DE) (kernel-module-usbnet)\\
to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS [=USB200M?-DE= (Version 1 only)]) (kernel-module-usbnet)\\
Changed lines 9-10 from:
to:

(January 2010 - Linksys USB200M? has been revised, version 2.0 and 2.1 (version number appears on the back of the device) use the AX88772? chipset, for which no Linux 2.4 drivers are available (a backport from 2.6 exists for the TiVo? but doesn't compile for Unslung on my setup). Got myself an old Sitecom LN-013 using RTL8150? instead, works fine. Anyone in need of a brand new USB200M??)

September 10, 2009, at 08:48 PM by G Amanakis --
Changed lines 8-9 from:

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. I built them natively on the NSLU2. e-mail: gamanakis_at_hotmail.com)

to:

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. (manually build module, see below). E-mail: gamanakis_at_hotmail.com)

September 10, 2009, at 08:47 PM by G Amanakis --
Added lines 43-44:

AX8877X

September 10, 2009, at 08:46 PM by G Amanakis --
Changed lines 33-34 from:
  • for debianslug and AX8817X based devices you might also need the "asix" module.
to:

Debianslug

for debianslug and AX8817X based devices you might also need the "asix" module.

September 10, 2009, at 08:45 PM by G Amanakis --
Changed lines 42-43 from:
  • On a Debian system do the following as root on the nslu2 (be patient it has a slow processor):
to:

Debian

On a Debian system do the following as root on the nslu2 (be patient, it has a slow processor):

September 10, 2009, at 08:43 PM by G Amanakis --
Changed lines 31-34 from:

debianslug and AX8817X

for debianslug and AX8817X based devices you might also need the "asix" module.

to:

AX8817X

  • for debianslug and AX8817X based devices you might also need the "asix" module.
Changed line 42 from:

On a Debian system do the following as root on the nslu2 (be patient it has a slow processor):

to:
  • On a Debian system do the following as root on the nslu2 (be patient it has a slow processor):
September 10, 2009, at 08:42 PM by G Amanakis --
Changed lines 46-48 from:

apt-get install linux-source tar xjvf /usr/src/linux-source

to:
  1. apt-get install linux-source
  2. tar xjvf /usr/src/linux-source
Changed lines 50-57 from:

cp /boot/config-$(uname -r) .config cp /lib/modules/$(uname -r)/build/Module.symvers /usr/src/linux cd /usr/src/linux make clean make oldconfig make modules_prepare make scripts

to:
  1. cp /boot/config-$(uname -r) .config
  2. cp /lib/modules/$(uname -r)/build/Module.symvers /usr/src/linux
  3. cd /usr/src/linux
  4. make clean
  5. make oldconfig
  6. make modules_prepare
  7. make scripts
Changed lines 59-61 from:

cd /usr/src/linux/drivers/net/usb/ make -C /usr/src/linux SUBDIRS=$PWD modules

to:
  1. cd /usr/src/linux/drivers/net/usb/
  2. make -C /usr/src/linux SUBDIRS=$PWD modules
Changed lines 63-66 from:

cp asix.ko /lib/modules/$(uname -r)/kernel/drivers/net/usb/asix.ko modprobe asix

to:
  1. cp asix.ko /lib/modules/$(uname -r)/kernel/drivers/net/usb/asix.ko
  2. modprobe asix
September 10, 2009, at 08:40 PM by G Amanakis --
Changed lines 42-66 from:
to:

On a Debian system do the following as root on the nslu2 (be patient it has a slow processor): The "linux-source" has to be in accordance with "uname -r".

Getting the linux kernel source: apt-get install linux-source tar xjvf /usr/src/linux-source

Configuring the kernel to match the one currently installed: cp /boot/config-$(uname -r) .config cp /lib/modules/$(uname -r)/build/Module.symvers /usr/src/linux cd /usr/src/linux make clean make oldconfig make modules_prepare make scripts

Compiling the asix.ko and usbnet.ko modules: cd /usr/src/linux/drivers/net/usb/ make -C /usr/src/linux SUBDIRS=$PWD modules

Installing the modules and loading them: cp asix.ko /lib/modules/$(uname -r)/kernel/drivers/net/usb/asix.ko modprobe asix

February 09, 2008, at 01:51 AM by G Amanakis --
Changed lines 8-9 from:

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X? chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. I built them natively on the NSLU2. e-mail: gamanakis_at_hotmail.com)

to:

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. I built them natively on the NSLU2. e-mail: gamanakis_at_hotmail.com)

February 09, 2008, at 01:50 AM by G Amanakis --
February 09, 2008, at 01:50 AM by G Amanakis --
Changed lines 8-9 from:

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. I built them natively on the NSLU2. e-mail: gamanakis_at_hotmail.com)

to:

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. Rev B1 is based on AX8877X? chipset. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. I built them natively on the NSLU2. e-mail: gamanakis_at_hotmail.com)

February 09, 2008, at 01:48 AM by G Amanakis --
Deleted line 7:
February 09, 2008, at 01:48 AM by G Amanakis --
Changed lines 7-8 from:

(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

to:

(July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)

February 09, 2008, at 01:47 AM by G Amanakis -- D-Link DUB-E100 rev B1
Changed lines 8-10 from:

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3)

to:

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3. The modules "asix.ko" and "usbnet.ko" have to be built from the kernel-source. I built them natively on the NSLU2. e-mail: gamanakis_at_hotmail.com)

February 09, 2008, at 01:46 AM by G Amanakis -- D-Link DUB-E100 rev B1 working
Added line 8:

(February 2008 - D-Link DUB-E100 rev B1 confirmed working in Debian/lenny with kernel version: 2.6.22-3)

June 23, 2007, at 08:52 AM by ssb22 -- DM9601 added
Added lines 55-56:

Davcom DM9601? USB to Ethernet bridge

This chipset is used in some Chinese "USB LAN" adapters. On Debian etch, I did apt-get install linux-headers-2.6.18-4-ixp4xx and then downloaded www.silencio.ro/DM9601?.GZ (which is actually a .tar.gz file), typed make, and then typed insmod dm9601.ko (while the dm9601.ko file was in the current directory) and it worked.

June 07, 2007, at 05:14 PM by ssb22 -- deleted my previous addition about not being necessary; I thought it was a nice idea but it doesn\'t work...
Deleted lines 3-4:

Note: If you just want the Slug to act as a router connecting several home PCs to a cable modem, then you might not need a second Ethernet port at all. Just use a cheap "ethernet splitter", make sure the Slug is the first machine to be switched on, and get everything else to route through the Slug. This usually works, because a cable modem is a network bridge, and most nowadays are programmed to do bridging for the first MAC address they see on your side and to ignore all other MAC addresses on your side. So if the Slug is the first to boot then the cable modem will see it and ignore everything else, so it doesn't matter if the other machines are sharing an unswitched, unrouted network with the slug and modem. (However, because the modem will be ignoring your other machines, you still need the Slug to do routing. But it can do it all on the one interface.)

June 04, 2007, at 04:46 PM by fcarolo -- formatting
Changed lines 4-5 from:

Note: If you just want the Slug to act as a router connecting several home PCs? to a cable modem, then you might not need a second Ethernet port at all. Just use a cheap "ethernet splitter", make sure the Slug is the first machine to be switched on, and get everything else to route through the Slug. This usually works, because a cable modem is a network bridge, and most nowadays are programmed to do bridging for the first MAC address they see on your side and to ignore all other MAC addresses on your side. So if the Slug is the first to boot then the cable modem will see it and ignore everything else, so it doesn't matter if the other machines are sharing an unswitched, unrouted network with the slug and modem. (However, because the modem will be ignoring your other machines, you still need the Slug to do routing. But it can do it all on the one interface.)

to:

Note: If you just want the Slug to act as a router connecting several home PCs to a cable modem, then you might not need a second Ethernet port at all. Just use a cheap "ethernet splitter", make sure the Slug is the first machine to be switched on, and get everything else to route through the Slug. This usually works, because a cable modem is a network bridge, and most nowadays are programmed to do bridging for the first MAC address they see on your side and to ignore all other MAC addresses on your side. So if the Slug is the first to boot then the cable modem will see it and ignore everything else, so it doesn't matter if the other machines are sharing an unswitched, unrouted network with the slug and modem. (However, because the modem will be ignoring your other machines, you still need the Slug to do routing. But it can do it all on the one interface.)

Changed lines 8-11 from:
  • AX8817X based (e.g. Netgear FA120, LINKSYS USB200M-DE) (kernel-module-usbnet)
   (July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset
 the newer Rev B1 is not working due to chipset changes - see details here
 http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
to:
  • AX8817X based (e.g. Netgear FA120, LINKSYS USB200M-DE) (kernel-module-usbnet)
    (July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset the newer Rev B1 is not working due to chipset changes - see details here http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
Changed line 22 from:
  1. Go to /opt/lib/modules (Unslung) or /lib/modules (other OSes?)
to:
  1. Go to /opt/lib/modules (Unslung) or /lib/modules (other OSes)
June 03, 2007, at 09:23 AM by ssb22 -- \"use a cheap ethernet splitter\" is better wording than \"connect everything to an unswitched hub\" because the former is easier to find by searching eBay etc
Changed lines 4-5 from:

Note: If you just want the Slug to act as a router connecting several home PCs? to a cable modem, then you might not need a second Ethernet port at all. Just connect everything to an unswitched hub, make sure the Slug is the first machine to be switched on, and get everything else to route through the Slug. This usually works, because a cable modem is a network bridge, and most nowadays are programmed to do bridging for the first MAC address they see on your side and to ignore all other MAC addresses on your side. So if the Slug is the first to boot then the cable modem will see it and ignore everything else, so it doesn't matter if the other machines are sharing an unswitched, unrouted network with the slug and modem. (However, because the modem will be ignoring your other machines, you still need the Slug to do routing. But it can do it all on the one interface.)

to:

Note: If you just want the Slug to act as a router connecting several home PCs? to a cable modem, then you might not need a second Ethernet port at all. Just use a cheap "ethernet splitter", make sure the Slug is the first machine to be switched on, and get everything else to route through the Slug. This usually works, because a cable modem is a network bridge, and most nowadays are programmed to do bridging for the first MAC address they see on your side and to ignore all other MAC addresses on your side. So if the Slug is the first to boot then the cable modem will see it and ignore everything else, so it doesn't matter if the other machines are sharing an unswitched, unrouted network with the slug and modem. (However, because the modem will be ignoring your other machines, you still need the Slug to do routing. But it can do it all on the one interface.)

May 31, 2007, at 05:03 PM by ssb22 -- added you might not have to do this
Changed lines 4-6 from:

There are various chipsets available:

to:

Note: If you just want the Slug to act as a router connecting several home PCs? to a cable modem, then you might not need a second Ethernet port at all. Just connect everything to an unswitched hub, make sure the Slug is the first machine to be switched on, and get everything else to route through the Slug. This usually works, because a cable modem is a network bridge, and most nowadays are programmed to do bridging for the first MAC address they see on your side and to ignore all other MAC addresses on your side. So if the Slug is the first to boot then the cable modem will see it and ignore everything else, so it doesn't matter if the other machines are sharing an unswitched, unrouted network with the slug and modem. (However, because the modem will be ignoring your other machines, you still need the Slug to do routing. But it can do it all on the one interface.)

If you do want to connect a USB ethernet adapter, there are various chipsets available:

February 03, 2007, at 09:57 AM by W -- final cosmetics, for real now, i hope
Changed line 20 from:
  1. Getting the software: run ipkg install kernel-module-pegasus
to:
  1. Getting the software: ipkg install kernel-module-pegasus
Changed lines 23-25 from:
  1. find pegasus.o or pegasus.ko in this directory; Do insmod pegasus.o or insmod pegasus.ko (as appropriate)
  2. Now the device eth1 should be created. Do ifconfig -a to verify the presence of an inactive network adapter. (eth0 is the built-in network controller)
  3. Now you can do things like ifconfig eth1 up 10.0.1.114 and so on - it is an active Ethernet device.
to:
  1. find pegasus.o or pegasus.ko in this directory; Do "insmod pegasus.o" or "insmod pegasus.ko" (as appropriate)
  2. Now the device eth1 should be created. Do "ifconfig -a" to verify the presence of an inactive network adapter. (eth0 is the built-in network controller)
  3. Now you can do things like "ifconfig eth1 up 10.0.1.114" and so on - it is an active Ethernet device.
Changed line 47 from:

lsusb shows ID 9710:7830 MosChip Semiconductor.

to:

lsusb shows "ID 9710:7830 MosChip Semiconductor".

Changed line 53 from:
  1. Edit the Makefile that comes with it: change KDIR := /lib/modules/$(shell uname -r)/build to KDIR := /usr/src/<your kernel tree>
to:
  1. Edit the Makefile that comes with it: change "KDIR := /lib/modules/$(shell uname -r)/build" to "KDIR := /usr/src/<your kernel tree>"
Changed line 56 from:
  1. ifconfig -a should show your device appears as "usb0"
to:
  1. "ifconfig -a" should show your device appears as "usb0"
February 03, 2007, at 09:54 AM by W -- last tweaks (if only preview worked)
Changed lines 12-13 from:
  • MCS7830? based (e.g. delock) (manually build module, see below)
to:
  • MCS7830 based (e.g. delock) (manually build module, see below)
Changed line 43 from:

delock usb 2.0 ethernet adapter

to:

delock usb 2.0 ethernet adapter: MCS7830

Changed lines 47-48 from:

lsusb shows ID 9710:7830 MosChip? Semiconductor The chip is a mcs7830 (http://www.moschip.com/html/MCS7830.html).

to:

lsusb shows ID 9710:7830 MosChip Semiconductor. The chip is a mcs7830 (see http://www.moschip.com/html/MCS7830.html).

Changed line 51 from:
  1. You need to have "gcc" and "glibc6-dev" installed on debianslug, as well as the kernel source.
to:
  1. You need to have "gcc" and "glibc6-dev" installed on debianslug, as well as the kernel source.
Changed lines 54-55 from:
  1. Compile the driver: make
  2. Load it: insmod mcs7830.ko
to:
  1. Compile the driver: make
  2. Load it: insmod mcs7830.ko
February 03, 2007, at 09:49 AM by W -- Some more, major cosmetics
Deleted line 9:
Changed lines 13-20 from:

The example below assumes you are using a device with the pegasus chipset. Instructions for the other ones are similar.

1 Getting the software

  1. run ipkg install kernel-module-pegasus.

2 Hooking it all up

to:

Instructions for most chipsets are similar to the pegasus example below.

specific chipset instructions

Basic example: Pegasus chipset

  1. Getting the software: run ipkg install kernel-module-pegasus
Changed lines 23-25 from:
  1. find pegasus.o or pegasus.ko in this directory; Do "insmod pegasus.o" or "insmod pegasus.ko" (as appropriate)
  2. Now the device eth1 should be created. Do "ifconfig -a" to verify the presence of an inactive network adapter. (eth0 is the built-in network controller)
  3. Now you can do things like "ifconfig eth1 up 10.0.1.114" and so on - it is an active Ethernet device.
to:
  1. find pegasus.o or pegasus.ko in this directory; Do insmod pegasus.o or insmod pegasus.ko (as appropriate)
  2. Now the device eth1 should be created. Do ifconfig -a to verify the presence of an inactive network adapter. (eth0 is the built-in network controller)
  3. Now you can do things like ifconfig eth1 up 10.0.1.114 and so on - it is an active Ethernet device.
Changed lines 30-31 from:

specific chipset details

to:
Changed lines 35-36 from:

ipkg install kernel-module-ax8817x

to:

ipkg install kernel-module-ax8817x

Changed lines 47-48 from:

lsusb shows "ID 9710:7830 MosChip? Semiconductor".

to:

lsusb shows ID 9710:7830 MosChip? Semiconductor

Changed lines 51-56 from:

You need to have "gcc" and "glibc6-dev" installed on debianslug + the kernel source to do this. Just edit the Makefile that comes with the driver, and change "KDIR := /lib/modules/$(shell uname -r)/build" to "KDIR := /usr/src/<your kernel tree>" then "make" and you'll have a shiny new driver. "insmod mcs7830.ko" to load it, your device appears as "usb0".

to:
  1. You need to have "gcc" and "glibc6-dev" installed on debianslug, as well as the kernel source.
  2. Extract the driver downloaded from the moschip site
  3. Edit the Makefile that comes with it: change KDIR := /lib/modules/$(shell uname -r)/build to KDIR := /usr/src/<your kernel tree>
  4. Compile the driver: make
  5. Load it: insmod mcs7830.ko
  6. ifconfig -a should show your device appears as "usb0"
February 03, 2007, at 09:38 AM by W -- more cosmetics
Changed line 13 from:
  • MCS7830? based (e.g. delock) (manually build module, see Note2)
to:
  • MCS7830? based (e.g. delock) (manually build module, see below)
Changed lines 31-32 from:

Note: for debianslug and AX8817X based devices you might also need the "asix" module.

to:

specific chipset details

debianslug and AX8817X

for debianslug and AX8817X based devices you might also need the "asix" module.

Changed lines 45-46 from:

Note2: I got a "delock usb 2.0 ethernet adapter" working on debianslug (http://delock.de/produkte/gruppen/USB+Adapter/USB_20_Ethernet_Adapter_61147.html)

to:

delock usb 2.0 ethernet adapter

I got a "delock usb 2.0 ethernet adapter" working on debianslug (http://delock.de/produkte/gruppen/USB+Adapter/USB_20_Ethernet_Adapter_61147.html)

February 03, 2007, at 09:35 AM by W -- minor cosmetic changes
Changed lines 42-44 from:

I thought it used the asix chipset when I bought it. But it turn out it doesn't.

to:

I thought it used the asix chipset when I bought it. But it turns out it doesn't.

Changed lines 48-49 from:

You need to have "gcc" and "glibc6-dev" installed on debianslug + the kernel source to do this. Just edit the Makefile that comes with the driver, and change "KDIR := /lib/modules/$(shell uname -r)/build" to "KDIR := /usr/src/<your kernel tree>" then "make" and you'll have a shiny new driver. insmod "mcs7830.ko" to load it, your device appears as "usb0".

to:

You need to have "gcc" and "glibc6-dev" installed on debianslug + the kernel source to do this. Just edit the Makefile that comes with the driver, and change "KDIR := /lib/modules/$(shell uname -r)/build" to "KDIR := /usr/src/<your kernel tree>" then "make" and you'll have a shiny new driver. "insmod mcs7830.ko" to load it, your device appears as "usb0".

February 03, 2007, at 09:33 AM by W -- Added MCS7830 explanation
Added line 13:
  • MCS7830? based (e.g. delock) (manually build module, see Note2)
Added lines 39-46:

Note2: I got a "delock usb 2.0 ethernet adapter" working on debianslug (http://delock.de/produkte/gruppen/USB+Adapter/USB_20_Ethernet_Adapter_61147.html) I thought it used the asix chipset when I bought it. But it turn out it doesn't. lsusb shows "ID 9710:7830 MosChip? Semiconductor". The chip is a mcs7830 (http://www.moschip.com/html/MCS7830.html). The moschip site has linux drivers. You need to compile or crosscompile them yourself. You need to have "gcc" and "glibc6-dev" installed on debianslug + the kernel source to do this. Just edit the Makefile that comes with the driver, and change "KDIR := /lib/modules/$(shell uname -r)/build" to "KDIR := /usr/src/<your kernel tree>" then "make" and you'll have a shiny new driver. insmod "mcs7830.ko" to load it, your device appears as "usb0".

October 17, 2006, at 01:28 AM by fred -- added small edit
Changed lines 17-18 from:

run ipkg install kernel-module-pegasus.

to:
  1. run ipkg install kernel-module-pegasus.
September 02, 2006, at 03:42 PM by Bullfrog --
Added lines 7-10:
   (July 2006 - D-Link DUB-E100 upto rev A4 also use this chipset
 the newer Rev B1 is not working due to chipset changes - see details here
 http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.0/0738.html)
Added lines 31-37:

ipkg install kernel-module-ax8817x

Also some of the above modules may complain re mii errors on loading. So type

ipkg install kernel-module-mii

July 10, 2006, at 01:30 PM by eFfeM --
Changed lines 20-21 from:
  1. Now the device eth0 should be created. Do "ifconfig eth0" to verify the presence of an inactive network adapter.
  2. Now you can do things like "ifconfig eth0 up 10.0.1.114" and so on - it is an active Ethernet device.
to:
  1. Now the device eth1 should be created. Do "ifconfig -a" to verify the presence of an inactive network adapter. (eth0 is the built-in network controller)
  2. Now you can do things like "ifconfig eth1 up 10.0.1.114" and so on - it is an active Ethernet device.
Changed lines 23-25 from:
  1. Add in /etc/modules : pegasus alias eth0
to:
  1. Unslung: add a line in /opt/etc/modules : pegasus alias eth1
  2. SlugOS: add a line in /etc/modutils/modules (creating the file if needed: pegasus alias eth1; then run update-modules
June 26, 2006, at 02:37 PM by eFfeM -- major cleanup
Deleted lines 0-1:

This page needs updating, as the kernel modules required are now in the feeds for both Unslung and OpenSlug.

Changed lines 4-23 from:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but most USB-Ethernet adapters that uses the ADMtek Pegasus AN986 and Pegasus II chipsets should work (the approach should be the same for all Ethernet adapters supported by Linux, though the actual modules needed will differ):

  • ADMtek AN986 Pegasus
  • ADMtek ADM8511 Pegasus II
  • Accton 10/100
  • Billington USB-100
  • Corega FEter USB-TX
  • Genius (KYE) GF3000U
  • MELCO/BUFFALO LUA-TX
  • D-Link DSB-650TX, DSB-650TX-PNA, DSB-650, DU-E10, DU-E100
  • Netgear FA120
  • Linksys USB100TX, USB10TX
  • LANEED Ethernet LD-USB/TX
  • SMC 202
  • SOHOware NUB Ethernet
  • Dynamode USB 10/100
  • (update 2-25-06) Belkin F5D5050? USB Ethernet

It is also possible to use a Philips CPWUE01?/00 adapter, but that requires a little bit more work. See the last chapter. The recipe given over there might also be useful for other adapters

to:

There are various chipsets available:

  • Pegasus based (e.g. Philips CPWUE01/00) (kernel-module-pegasus)
  • AX8817X based (e.g. Netgear FA120, LINKSYS USB200M-DE) (kernel-module-usbnet)
  • kaweth based (e.g. 3Com 3C19250 USB) (kernel-module-kaweth)
  • RTL8150 based (e.g. Sitecom LN-013) (kernel-module-rtl8150)

The example below assumes you are using a device with the pegasus chipset. Instructions for the other ones are similar.

Changed lines 13-16 from:

(this section has been updated to match Unslung 4.x and 5.x)

The kernel Ethernet modules are now in the feed. Search the web for the module matching your adapter and run ipkg install kernel-myethermodule.

to:

run ipkg install kernel-module-pegasus.

Changed lines 18-19 from:
  1. Go to /opt/lib/modules
  2. Do "insmod pegasus.o"
to:
  1. Go to /opt/lib/modules (Unslung) or /lib/modules (other OSes?)
  2. find pegasus.o or pegasus.ko in this directory; Do "insmod pegasus.o" or "insmod pegasus.ko" (as appropriate)
Changed lines 22-83 from:
  1. UPD: Add in /etc/modules : pegasus alias eth0

Note on the Pegasus chip set

This is a 10/100 Mb/s Ethernet adapter with USB 1.1 interface which means that it tries to do 100 Mb/s over a maximum 12 Mb/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidered.

If I had a USB 2.0 adapter I would be much happier, though (*hint* :-) )

Bob_tm

Another Success

I have managed to get this method to work with the Netgear FA120 which is a USB 2.0 ethernet adapter (it uses the same chipset as the D-link DUB-E100). I needed to compile the AX8817X module instead of the pegasus module. Other than that, everything was the same. One thing to note is that you need to update your routing table before much can be done with the device.

Christopher

The LINKSYS USB200M-DE (USB 2.0) is supported as well. It also uses the AX8817X module. On OpenSlug (kernel 2.6.11-2) the driver is included in the usbnet module per default.. If you are using DebianSlug you will also need the "asix" module. The asix module provides 100 Mb support.

bofh_omega

The 3Com 3C19250 USB 1.1 is supported. It uses the kaweth module. On Unslung the driver is included in the unslung feed (kernel-module-kaweth)

supergerg79

Sitecom LN-013 (RTL8150 chipset) works great!. be sure to:

  • get kernel-module-rtl8150 with ipkg (see above)
  • install the .o file to /lib/modules/2.4.22-xfs/kernel/drivers/usb/ (if not already there).
  • use insmod to load the kernel module with DiversionScripts

strike-2

All the network devices below should also work:

  • ASIX 88172
  • ATEN UC210T
  • D-Link DUB-E100
  • Hawking UF200
  • Linksys USB200M
  • Netgear FA120
  • Intellinet
  • ST Lab USB Ethernet
  • TrendNet TU2-ET100

eddyp

Can anybody confirm or infirm that Repotec's RP-USB102C? USB ethernet card works?

eddyp

Using the Philips CPWUE01?/00 adapter

The approach mentioned in this section might also be applicable for other adapters.

The adapter uses the Pegasus II chipset. However it is not mentioned in pegasus.h. What I did was add the following two lines in the .h file:
PEGASUS_DEV( "Philips CPWUE01?/00 USB 10/100 Ethernet", VENDOR_ACCTON, 0xb004,
DEFAULT_GPIO_RESET | PEGASUS_II )
I hacked this in tmp/work/*kernel/linux*/drivers/usb/net/pegasus.h, followed by a remove of tmp/stamps/*kernel*compile* and a bb openslug-kernel (I'm on openslug, but unslung is similar). This will give you a pegasus.ko file which you can use for the steps above.

If it does not work check that pegasus.ko is indeed rebuilt (remove it before building) and if pegasus.h is not overwritten with the original.

As of kernel 2.6.15, the Philips adapter is natively supported and the patch above is not needed. This will be in OpenSlug 3.3.

to:
  1. update your routing tables as you see fit
  2. Add in /etc/modules : pegasus alias eth0

Note: for debianslug and AX8817X based devices you might also need the "asix" module.

May 09, 2006, at 02:03 PM by Jim Drash --
Changed lines 54-55 from:

The LINKSYS USB200M-DE (USB 2.0) is supported as well. It also uses the AX8817X module. On OpenSlug (kernel 2.6.11-2) the driver is included in the usbnet module per default..

to:

The LINKSYS USB200M-DE (USB 2.0) is supported as well. It also uses the AX8817X module. On OpenSlug (kernel 2.6.11-2) the driver is included in the usbnet module per default.. If you are using DebianSlug you will also need the "asix" module. The asix module provides 100 Mb support.

February 24, 2006, at 09:47 PM by Martijn Ebben -- Added Belkin F5D5050 on Pegasus
Changed lines 22-23 from:
to:
  • (update 2-25-06) Belkin F5D5050? USB Ethernet
February 08, 2006, at 08:16 AM by eFfeM --
Changed lines 97-99 from:

If it does not work check that pegasus.ko is indeed rebuilt (remove it before building) and if pegasus.h is not overwritten with the original. I'll try to make a patch for this later.

to:

If it does not work check that pegasus.ko is indeed rebuilt (remove it before building) and if pegasus.h is not overwritten with the original.

As of kernel 2.6.15, the Philips adapter is natively supported and the patch above is not needed. This will be in OpenSlug 3.3.

January 22, 2006, at 02:06 PM by jonh --
Changed lines 21-22 from:
to:
  • Dynamode USB 10/100
October 06, 2005, at 04:52 PM by EddyP -- corrected id
Changed lines 79-80 from:
to:

eddyp

Changed lines 83-85 from:
to:

eddyp

October 06, 2005, at 04:48 PM by EddyP -- Adding a list of supported devices on USB 2.0 / 10/100
Added lines 68-85:

All the network devices below should also work:

  • ASIX 88172
  • ATEN UC210T
  • D-Link DUB-E100
  • Hawking UF200
  • Linksys USB200M
  • Netgear FA120
  • Intellinet
  • ST Lab USB Ethernet
  • TrendNet TU2-ET100

EddyP?

Can anybody confirm or infirm that Repotec's RP-USB102C? USB ethernet card works?

EddyP?

October 01, 2005, at 07:07 PM by eFfeM -- added text for Philips CPWUE01/00 adapter
Changed lines 6-7 from:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but any USB-Ethernet adapters that uses the ADMtek Pegasus AN986 and Pegasus II chipsets should work (the approach should be the same for all Ethernet adapters supported by Linux, though the actual modules needed will differ):

to:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but most USB-Ethernet adapters that uses the ADMtek Pegasus AN986 and Pegasus II chipsets should work (the approach should be the same for all Ethernet adapters supported by Linux, though the actual modules needed will differ):

Added lines 22-23:

It is also possible to use a Philips CPWUE01?/00 adapter, but that requires a little bit more work. See the last chapter. The recipe given over there might also be useful for other adapters

Changed lines 66-79 from:

strike-2

to:

strike-2

Using the Philips CPWUE01?/00 adapter

The approach mentioned in this section might also be applicable for other adapters.

The adapter uses the Pegasus II chipset. However it is not mentioned in pegasus.h. What I did was add the following two lines in the .h file:
PEGASUS_DEV( "Philips CPWUE01?/00 USB 10/100 Ethernet", VENDOR_ACCTON, 0xb004,
DEFAULT_GPIO_RESET | PEGASUS_II )
I hacked this in tmp/work/*kernel/linux*/drivers/usb/net/pegasus.h, followed by a remove of tmp/stamps/*kernel*compile* and a bb openslug-kernel (I'm on openslug, but unslung is similar). This will give you a pegasus.ko file which you can use for the steps above.

If it does not work check that pegasus.ko is indeed rebuilt (remove it before building) and if pegasus.h is not overwritten with the original. I'll try to make a patch for this later.

August 30, 2005, at 11:18 AM by ingeba -- Replaced info for 3.x with 4.x/5.x info
Changed lines 23-37 from:

1.1 The easy way - getting it from me

  1. Fetch http://folk.uio.no/ingeba/pegasus.o and move it to /opt/lib/modules on your slug (the directory has to be created if not present).

1.2 The hard way - Building it yourself

  1. Follow the OpenEmbedded GettingStarted guide to get the make environment going.
  2. Follow the EnableTrafficShaping HowTo point 1.2, but instead of the list of modules to enabled mentioned there, make sure that the following line is in the defconfig:
    • CONFIG_USB_PEGASUS=m
  3. Make the kernel again as described in the EnableTrafficShaping HowTo and make sure you delete the proper files for remake so the modules are rebuilt.
  4. Transfer the module from your cross development host location
    ${OEMBUILD}/tmp/work/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o
    to your slug's directory /opt/lib/modules
to:

(this section has been updated to match Unslung 4.x and 5.x)

The kernel Ethernet modules are now in the feed. Search the web for the module matching your adapter and run ipkg install kernel-myethermodule.

August 14, 2005, at 08:04 PM by tman --
Changed lines 72-73 from:
  • use insmod to load the kernel module with DiversionScripts
to:
August 14, 2005, at 08:03 PM by tman --
Changed line 68 from:

Sitecom LN-013 (RTL8150? chipset) works great!.

to:

Sitecom LN-013 (RTL8150 chipset) works great!.

August 14, 2005, at 07:07 PM by strike-2 -- Added Sitecom LN-013 (rtl8150)
Changed lines 66-74 from:

supergerg79

to:

supergerg79

Sitecom LN-013 (RTL8150? chipset) works great!. be sure to:

  • get kernel-module-rtl8150 with ipkg (see above)
  • install the .o file to /lib/modules/2.4.22-xfs/kernel/drivers/usb/ (if not already there).
  • use insmod to load the kernel module with DiversionScripts

strike-2

August 10, 2005, at 01:19 PM by rwhitby --
Added lines 1-2:

This page needs updating, as the kernel modules required are now in the feeds for both Unslung and OpenSlug.

July 23, 2005, at 05:50 PM by supergerg79 -- Added 3Com 3C19250 USB Ethernet
Changed lines 60-64 from:

bofh_omega

to:

bofh_omega

The 3Com 3C19250 USB 1.1 is supported. It uses the kaweth module. On Unslung the driver is included in the unslung feed (kernel-module-kaweth)

supergerg79

July 19, 2005, at 11:29 AM by alecv --
Changed lines 4-5 from:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but any USB-Ethernet adapters that uses the ADMtek? Pegasus AN986? and Pegasus II chipsets should work (the approach should be the same for all Ethernet adapters supported by Linux, though the actual modules needed will differ):

to:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but any USB-Ethernet adapters that uses the ADMtek Pegasus AN986 and Pegasus II chipsets should work (the approach should be the same for all Ethernet adapters supported by Linux, though the actual modules needed will differ):

July 19, 2005, at 11:29 AM by alecv --
Changed lines 4-5 from:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but this should work on the following adapters (the approach should be the same for all Ethernet adapters supported by Linux, though the actual modules needed will differ):

to:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but any USB-Ethernet adapters that uses the ADMtek? Pegasus AN986? and Pegasus II chipsets should work (the approach should be the same for all Ethernet adapters supported by Linux, though the actual modules needed will differ):

Changed lines 32-34 from:

${OEMBUILD}/tmp/work/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o to your slug's directory /opt/lib/modules

to:

${OEMBUILD}/tmp/work/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o
to your slug's directory /opt/lib/modules

July 19, 2005, at 10:20 AM by alecv --
Changed lines 31-33 from:
  1. Transfer the module from your cross development host location ${OEMBUILD}/tmp/work/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o to your slug's directory /opt/lib/modules
to:
  1. Transfer the module from your cross development host location
    ${OEMBUILD}/tmp/work/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o to your slug's directory /opt/lib/modules
Changed lines 42-43 from:
to:
  1. UPD: Add in /etc/modules : pegasus alias eth0
Changed lines 46-47 from:

This is a 10/100 Mb/s USB 1.1 adapter which means that it tries to do 100 Mb/s over a maximum 12 Mb/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidered.

to:

This is a 10/100 Mb/s Ethernet adapter with USB 1.1 interface which means that it tries to do 100 Mb/s over a maximum 12 Mb/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidered.

Changed lines 57-58 from:

The LINKSYS USB200M?-DE (USB 2.0) is supported as well. It also uses the AX8817X module. On OpenSlug (kernel 2.6.11-2) the driver is included in the usbnet module per default..

to:

The LINKSYS USB200M-DE (USB 2.0) is supported as well. It also uses the AX8817X module. On OpenSlug (kernel 2.6.11-2) the driver is included in the usbnet module per default..

July 19, 2005, at 10:05 AM by alecv --
Changed line 11 from:
to:
  • Genius (KYE) GF3000U
July 19, 2005, at 10:05 AM by alecv -- Genius (KYE) GF3000U
Added line 11:
June 11, 2005, at 05:56 PM by bofh_omega --
Changed lines 54-55 from:

The LINKSYS USB200M?-DE (USB 2.0) is supported as well. It also uses the AX8817X module.

to:

The LINKSYS USB200M?-DE (USB 2.0) is supported as well. It also uses the AX8817X module. On OpenSlug (kernel 2.6.11-2) the driver is included in the usbnet module per default..

May 13, 2005, at 07:14 AM by bofh_omega -- LINKSYS USB200M-DE
Added lines 53-56:

The LINKSYS USB200M?-DE (USB 2.0) is supported as well. It also uses the AX8817X module.

bofh_omega

January 24, 2005, at 05:10 PM by bob_tm --
Changed line 13 from:
to:
  • Netgear FA120
January 19, 2005, at 10:37 AM by bobtm --
Changed line 4 from:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but this should work on the following adapters (the approach should be the same for all, though the actual modules needed will differ):

to:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but this should work on the following adapters (the approach should be the same for all Ethernet adapters supported by Linux, though the actual modules needed will differ):

Changed line 50 from:

I have managed to get this method to work with the Netgear FA120? which is a USB 2.0 ethernet adapter (it uses the same chipset as the D-link DUB-E100). I needed to compile the AX8817X? module instead of the pegasus module. Other than that, everything was the same. One thing to note is that you need to update your routing table before much can be done with the device.

to:

I have managed to get this method to work with the Netgear FA120 which is a USB 2.0 ethernet adapter (it uses the same chipset as the D-link DUB-E100). I needed to compile the AX8817X module instead of the pegasus module. Other than that, everything was the same. One thing to note is that you need to update your routing table before much can be done with the device.

January 19, 2005, at 01:56 AM by ChrisE --
Added line 13:
Changed line 50 from:

I have managed to get this method to work with the Netgear FA120? which is a USB 2.0 ethernet adapter. I needed to compile the AX8817X? module instead of the pegasus module. Other than that, everything was the same. One thing to note is that you need to update your routing table before much can be done with the device.

to:

I have managed to get this method to work with the Netgear FA120? which is a USB 2.0 ethernet adapter (it uses the same chipset as the D-link DUB-E100). I needed to compile the AX8817X? module instead of the pegasus module. Other than that, everything was the same. One thing to note is that you need to update your routing table before much can be done with the device.

January 19, 2005, at 01:55 AM by ChrisE --
Added lines 47-51:

Another Success

I have managed to get this method to work with the Netgear FA120? which is a USB 2.0 ethernet adapter. I needed to compile the AX8817X? module instead of the pegasus module. Other than that, everything was the same. One thing to note is that you need to update your routing table before much can be done with the device.

Christopher

January 13, 2005, at 01:31 AM by tman --
Changed line 2 from:

It is possible to add a number of external USB Ethernet adapters to the slug and make it act like a router. This is a brief HowTo on connecting one directly to the slug, but via a hub one can connect many.

to:

It is possible to add a number of external USB Ethernet adapters to the slug and make it act like a router. This is a brief HowTo on connecting one directly to the slug, but via a hub one can connect many.

Changed lines 6-7 from:
to:
  • ADMtek AN986 Pegasus
  • ADMtek ADM8511 Pegasus II
Changed lines 13-14 from:
to:
  • Linksys USB100TX, USB10TX
  • LANEED Ethernet LD-USB/TX
Changed line 16 from:
to:
  • SOHOware NUB Ethernet
Changed line 42 from:

This is a 10/100 MB/s USB 1.1 adapter which means that it tries to do 100 MB/s over a maximum 12 MB/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidered.

to:

This is a 10/100 Mb/s USB 1.1 adapter which means that it tries to do 100 Mb/s over a maximum 12 Mb/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidered.

January 12, 2005, at 07:28 PM by bobtm --
Changed line 28 from:
  1. Make the kernel again as described in the Howto.EnableTrafficShaping EnableTrafficShaping HowTo? and make sure you delete the proper files for remake so the modules are rebuilt.
to:
  1. Make the kernel again as described in the HowTo.EnableTrafficShaping EnableTrafficShaping HowTo? and make sure you delete the proper files for remake so the modules are rebuilt.
January 12, 2005, at 06:11 PM by tman --
Changed lines 6-7 from:
to:
Changed line 10 from:
to:
  • Corega FEter USB-TX
Changed lines 25-26 from:
  1. Follow http://www.nslu2-linux.org/wiki/OpenEmbedded/GettingStarted to get the make environment going.
  2. Follow http://www.nslu2-linux.org/wiki/HowTo/EnableTrafficShaping point 1.2, but instead of the list of modules to enabled mentioned there, make sure that the following line is in the defconfig:
to:
  1. Follow the OpenEmbedded.GettingStarted OpenEmbedded GettingStarted? guide to get the make environment going.
  2. Follow the HowTo.EnableTrafficShaping EnableTrafficShaping HowTo? point 1.2, but instead of the list of modules to enabled mentioned there, make sure that the following line is in the defconfig:
Changed line 28 from:
  1. Make the kernel again as described in Howto.EnableTrafficShaping? and make sure you delete the proper files for remake so the modules are rebuilt.
to:
  1. Make the kernel again as described in the Howto.EnableTrafficShaping EnableTrafficShaping HowTo? and make sure you delete the proper files for remake so the modules are rebuilt.
Changed lines 36-38 from:
  1. Do "insmod pegasus.o"
  2. Now the device eth0 should be created. Do "ifconfig eth0" to verify the presence of an inactive network adapter.
  3. Now you can do things like "ifconfig eth0 up 10.0.1.114" and so on - it is an active Ethernet device.
to:
  1. Do "insmod pegasus.o"
  2. Now the device eth0 should be created. Do "ifconfig eth0" to verify the presence of an inactive network adapter.
  3. Now you can do things like "ifconfig eth0 up 10.0.1.114" and so on - it is an active Ethernet device.
Changed line 42 from:

This is a 10/100 mb/s USB 1.1 adapter which means that it tries to do 100 mb/s over a maximum 12 mb/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidered.

to:

This is a 10/100 MB/s USB 1.1 adapter which means that it tries to do 100 MB/s over a maximum 12 MB/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidered.

Deleted lines 46-48:
January 12, 2005, at 04:17 PM by bobtm --
Added line 1:

Introduction

Changed lines 18-19 from:

The easy way - getting it from me

to:

1 Getting the software

1.1 The easy way - getting it from me

Changed line 23 from:

The hard way - Building it yourself

to:

1.2 The hard way - Building it yourself

Changed line 32 from:

Hooking it all up

to:

2 Hooking it all up

January 12, 2005, at 04:09 PM by bobtm --
Changed line 35 from:
  1. Now the device eth0 should be created. Do "ifconfig eth0" to verify the presence of a inactive network adapter.
to:
  1. Now the device eth0 should be created. Do "ifconfig eth0" to verify the presence of an inactive network adapter.
January 12, 2005, at 03:34 PM by bobtm --
Changed line 40 from:

This is a 10/100 mb/s USB 1.1 adapter which means that it tries to do 100 mb/s over a maximum 12 mb/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidering.

to:

This is a 10/100 mb/s USB 1.1 adapter which means that it tries to do 100 mb/s over a maximum 12 mb/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidered.

January 12, 2005, at 03:33 PM by bobtm --
Changed line 3 from:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but this should work on the following adapters (the approach should be the same for all, though the actual modules will differ):

to:

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but this should work on the following adapters (the approach should be the same for all, though the actual modules needed will differ):

Changed line 42 from:

If I had a 2.0 adapter I would be much happier, though (*hint* :-) )

to:

If I had a USB 2.0 adapter I would be much happier, though (*hint* :-) )

January 12, 2005, at 03:23 PM by bobtm --
Changed line 27 from:
  1. Transfer the module from your cross development host location ${OEMBUILD}/tmp/work/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o to your slugs directory /opt/lib/modules
to:
  1. Transfer the module from your cross development host location ${OEMBUILD}/tmp/work/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o to your slug's directory /opt/lib/modules
January 12, 2005, at 03:23 PM by bobtm --
Changed line 27 from:
  1. Transfer the module from your cross development host location ${OEMBUILD}/tmp/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o to your slugs directory /opt/lib/modules
to:
  1. Transfer the module from your cross development host location ${OEMBUILD}/tmp/work/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o to your slugs directory /opt/lib/modules
January 12, 2005, at 03:22 PM by bobtm --
Changed lines 1-47 from:

Describe AddEthernetAdapter? here.

to:

It is possible to add a number of external USB Ethernet adapters to the slug and make it act like a router. This is a brief HowTo on connecting one directly to the slug, but via a hub one can connect many.

The adapter I'm using is an old USB 1.1 adapter from D-Link, the D-Link DSB-650TX, but this should work on the following adapters (the approach should be the same for all, though the actual modules will differ):

The easy way - getting it from me

  1. Fetch http://folk.uio.no/ingeba/pegasus.o and move it to /opt/lib/modules on your slug (the directory has to be created if not present).

The hard way - Building it yourself

  1. Follow http://www.nslu2-linux.org/wiki/OpenEmbedded/GettingStarted to get the make environment going.
  2. Follow http://www.nslu2-linux.org/wiki/HowTo/EnableTrafficShaping point 1.2, but instead of the list of modules to enabled mentioned there, make sure that the following line is in the defconfig:
    • CONFIG_USB_PEGASUS=m
  3. Make the kernel again as described in Howto.EnableTrafficShaping? and make sure you delete the proper files for remake so the modules are rebuilt.
  4. Transfer the module from your cross development host location ${OEMBUILD}/tmp/unslung-able-kernel-2.3r25-r7/install/kernel-module-pegasus/lib/modules/2.4.22-xfs/kernel/drivers/usb/pegasus.o to your slugs directory /opt/lib/modules

Hooking it all up

  1. Hook up you USB Ethernet adapter to your slug
  2. Go to /opt/lib/modules
  3. Do "insmod pegasus.o"
  4. Now the device eth0 should be created. Do "ifconfig eth0" to verify the presence of a inactive network adapter.
  5. Now you can do things like "ifconfig eth0 up 10.0.1.114" and so on - it is an active Ethernet device.

Note on the Pegasus chip set

This is a 10/100 mb/s USB 1.1 adapter which means that it tries to do 100 mb/s over a maximum 12 mb/s USB connection. This doesn't work too well and you are likely to get lots of receive errors on it. Still it is pretty good on a switch all things concidering.

If I had a 2.0 adapter I would be much happier, though (*hint* :-) )

Bob_tm

Page last modified on April 10, 2011, at 10:41 PM