Success - Neoware e100 - only 1 network card



  • Ill share my experience with you boys n girls.

    The item is more or less exactly as this one http://www.ciao.co.uk/Neoware_E100__6478206 but it seems they have sub models within the e100, mine only came with 2 usb ports.

    my specs:

    VIA C3 @ 800mhz
    128MB RAM
    Intergrated Realtek 8139 network card

    The system board hosts a 44 pin ide male connector, so you can attach a cf card adapter or a laptop hdd

    I bought this Neoware about 8 months ago on ebay, inspired by a post I saw over at m0n0's forums, although the guy there used a Neoware 3000 (300mhz cpu)?…. I had it gathering dust since it wasnt shipped with a power supply (funny 4 pin looking thing), I know the 3000's and some similar models use just a plain kettle lead, anyway, i recently got hold of the required power supply that was shipped from the USA.

    The only downside of my purchase was that it didnt come included with the required isa2pci expansion card for me to stick in an additional network card, no problem, I have tons of vlan capable switches laying around  ;D

    Im not using a cf card adapter at the moment, so instead I am using a plain 124mb usb stick.

    I initially tried to copy the full install on to the usb stick and boot off it, that didnt succeed for some reason, I thought perhaps the usb stick was too small, so I tried my (fake) 8gb usb stick, again no joy, so I used physdiskwrite.exe to write an embedded pfs image on to the 124mb usb stick.

    I've never used the embedded system before, so I was puzzled when it booted and just stopped after "loading /boot/defaults/loader.conf", then I realised I needed a serial cable, after hunting through several boxes, I later found one and hooked it up between my laptop and the Neoware, lauched putty and connected to the Neoware console, proceeded with setting up my vlans, browsed to 192.168.1.1 and followed through the setup wizard.

    So far so good, its working fine, in actual fact I prefer just the one lan card using vlans but I wouldnt mind getting hold of the isa2pci expansion card so that I can throw in either a wireless card or even a pci adsl card, so if anyone has one of these and it has the expansion card included, could you read any references off it as I have searched high and low but couldnt find one.

    Lastly here is the output from my putty session, you will notice complaints about the usb stick, I dont have a clue what thats all about ::) and "unknown: <pnp0xxx" but="" as="" i="" said,="" it="" seems="" to="" be="" working="" fine,="" infact="" im="" writing="" up="" this="" post="" from="" the="" neoware.<br="">```
    Hit [Enter] to boot immediately, or any other key for command prompt.
    Booting [/boot/kernel/kernel]...
    Copyright (c) 1992-2007 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
            The Regents of the University of California. All rights reserved.
    FreeBSD is a registered trademark of The FreeBSD Foundation.
    FreeBSD 6.2-RELEASE-p11 #0: Sun Feb 24 17:36:53 EST 2008
        sullrich@builder6.pfsense.com:/usr/obj.pfSense/usr/src/sys/pfSense_wrap.6
    Timecounter "i8254" frequency 1193182 Hz quality 0
    CPU: VIA C3 Nehemiah+RNG+AES (797.97-MHz 686-class CPU)
      Origin = "CentaurHauls"  Id = 0x698  Stepping = 8
      Features=0x381b93f <fpu,vme,de,pse,tsc,msr,cx8,sep,mtrr,pge,cmov,pat,mmx,fxsr,sse>real memory  = 125763584 (119 MB)
    avail memory = 113541120 (108 MB)
    wlan: mac acl policy registered
    ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
    cpu0 on motherboard
    pcib0: <host to="" pci="" bridge="">pcibus 0 on motherboard
    pir0: <pci 6="" interrupt="" routing="" table:="" entries="">on motherboard
    pci0: <pci bus="">on pcib0
    pcib1: <pci-pci bridge="">at device 1.0 on pci0
    pci1: <pci bus="">on pcib1
    pci1: <display, vga="">at device 0.0 (no driver attached)
    isab0: <pci-isa bridge="">at device 7.0 on pci0
    isa0: <isa bus="">on isab0
    atapci0: <via 82c686b="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xd000-0xd00f at device 7.1 on pci0
    ata0: <ata 0="" channel="">on atapci0
    ata1: <ata 1="" channel="">on atapci0
    uhci0: <via 83c572="" usb="" controller="">port 0xd400-0xd41f irq 10 at device 7.2 on pci0
    uhci0: [GIANT-LOCKED]
    usb0: <via 83c572="" usb="" controller="">on uhci0
    usb0: USB revision 1.0
    uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
    uhub0: 2 ports with 2 removable, self powered
    pci0: <bridge>at device 7.4 (no driver attached)
    pci0: <multimedia, audio="">at device 7.5 (no driver attached)
    rl0: <realtek 10="" 8139="" 100basetx="">port 0xe800-0xe8ff mem 0xee000000-0xee0000ff irq 15 at device 9.0 on pci0
    miibus0: <mii bus="">on rl0
    rlphy0: <realtek internal="" media="" interface="">on miibus0
    rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    rl0: Ethernet address: 00:e0:c5:6c:1b:3b
    orm0: <isa option="" roms="">at iomem 0xc0000-0xcbfff,0xcc000-0xcffff,0xd0000-0xd1fff,0xd2000-0xd3fff on isa0
    ppc0: <parallel port="">at port 0x378-0x37f irq 7 on isa0
    ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
    ppbus0: <parallel port="" bus="">on ppc0
    ppi0: <parallel i="" o="">on ppbus0
    sio0 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0
    sio0: type 16550A, console
    sio1 at port 0x2f8-0x2ff irq 3 on isa0
    sio1: type 16550A
    speaker0: <pc speaker="">at port 0x61 on isa0
    unknown: <pnp0c01>can't assign resources (memory)
    unknown: <pnp0501>can't assign resources (port)
    unknown: <pnp0501>can't assign resources (port)
    unknown: <pnp0400>can't assign resources (port)
    umass0: vendor 0x0204 Flash Disk, rev 2.00/1.00, addr 2
    Timecounter "TSC" frequency 797969077 Hz quality 800
    Timecounters tick every 10.000 msec
    Fast IPsec: Initialized Security Association Processing.
    da0 at umass-sim0 bus 0 target 0 lun 0
    da0: < Flash Disk 4.00> Removable Direct Access SCSI-2 device
    da0: 1.000MB/s transfers
    da0: 124MB (255231 512 byte sectors: 64H 32S/T 124C)
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    GEOM_LABEL: Label for provider da0a is ufs/pfSense.
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    GEOM_LABEL: Label for provider da0d is ufs/pfSenseCfg.
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
    (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
    (da0:umass-sim0:0:0:0): Medium not present
    Trying to mount root from ufs:/dev/ufs/pfSense

    ___
    / f
    / p _
    / Sense
    _

        _
    _/

    Welcome to pfSense 1.2-RELEASE on the 'embedded' platform...

    Setting up embedded specific environment... done.
    Mounting filesystems... done.
    Creating symlinks......done.
    Launching PHP init system... done.
    Initializing.................. done.
    Starting device manager (devd)...done.
    Loading configuration......done.
    Updating configuration...done.
    Cleaning backup cache...done.
    Setting up extended sysctls...done.
    Syncing user passwords...done.
    Starting Secure Shell Services...done.
    Setting timezone...done.
    Starting syslog...done.
    Configuring LAN interface...done.
    Configuring WAN interface...done.
    Configuring OPT interfaces...done.
    Configuring CARP interfaces...done.
    Syncing system time before startup...done.
    Configuring firewall......done.
    Starting webConfigurator...done.
    Starting DHCP service...done.
    Starting DNS forwarder...done.
    Setting up microcode and tx/rx offloading...done.
    Starting FTP helpers...done.
    Generating RRD graphs...done.
    Starting DHCP service...done.
    Starting OpenNTP time client...done.
    Starting CRON... done.
    Executing rc.d items...
    Starting /usr/local/etc/rc.d/*.sh...done.
    appending output to nohup.out
    Bootup complete

    FreeBSD/i386 (pfsense.local) (console)

    *** Welcome to pfSense 1.2-RELEASE-embedded on pfsense ***

    LAN                      ->  vlan2  ->      192.168.1.1
      WAN                      ->  vlan3  ->      82.xxx.xxx.xx

    pfSense console setup


    0)  Logout (SSH only)
    1)  Assign Interfaces
    2)  Set LAN IP address
    3)  Reset webConfigurator password
    4)  Reset to factory defaults
    5)  Reboot system
    6)  Halt system
    7)  Ping host
    8)  Shell
    9)  PFtop
    10)  Filter Logs
    11)  Restart webConfigurator
    12)  pfSense PHP shell
    13)  Upgrade from console

    Enter an option:</pnp0400></pnp0501></pnp0501></pnp0c01></pc></parallel></parallel></parallel></isa></realtek></mii></realtek></multimedia,></bridge></via></via></ata></ata></via></isa></pci-isa></display,></pci></pci-pci></pci></pci></host></fpu,vme,de,pse,tsc,msr,cx8,sep,mtrr,pge,cmov,pat,mmx,fxsr,sse>



  • Some pics



  • Can you share you were able to configure the device with only 1 NIC ?

    If I recall Pfsense will halt the system if it doesn't detect at least 2 NICs?

    I would love to do the same thing as you with a micro atx pc.



  • VLANS effectively provide multiple "virtual" interfaces over a single physical interface.

    pfSense needs at least two interfaces (either physical or virtual). To use VLANs you will need a VLAN capable switch. Most of the low end switches are not VLAN capable.

    Another option for systems with limited expansion capability is to use a USB ethernet adapter. These are readily available on ebay. I bought a few, all of which turned out to be based on the Davicom DM9601 which is supported by the udav driver in FreeBSD 6.3. This device is a USB 1.1 device so capable of a maximum speed of 12Mbps which I figure should be ample to deal with my ADSL connection which runs up to about 6Mbps download and 1Mbps upload.

    The udav driver wasn't included in the pfSense I downloaded a few months ago but I built the driver myself and tweaked the pfSense startup to load the driver on startup.

    There are USB Ethernet adapters which interface to USB 2.0 devices at 480Mpbs. I've seen them available online for about US$30 and up. They are probably available on Ebay for much less but the challenge is to find out what chip is inside the adapter so you can have some confidence there is a driver for it.

    FreeBSD 6.3 also has the ural driver for a range of USB to wireless lan adapters which are alleged to be capable of acting as a wireless access point. I've tried for a while to locate one but supplies seem to have dried up. There is a driver (rum) for FreeBSD 7.0 which supports USB to wireless lan adapters which are much more readily available.



  • The recently announced pfSense 1.2.1 snapshot builds are based on FreeBSD 7.0 which includes the rum driver for a range of USB wireless LAN adapters which are capable of acting as access points.

    I have no experience with USB wireless LAN adapters but have ordered a couple and hope to report in a few weeks.



  • I tried the pfsense 1.2.1 and was surprised to see that during boot time it reported finding the Motorola WU830G USB wireless device.
    I though do not find that in my assign interface.
    Is there something to do. Because it will be nice to have the wireless directly from the pfsense PC.
    I don't use traffic shaping as it is just a home PC router.
    Any suggestions?
    Anil

    @wallabybob:

    The recently announced pfSense 1.2.1 snapshot builds are based on FreeBSD 7.0 which includes the rum driver for a range of USB wireless LAN adapters which are capable of acting as access points.

    I have no experience with USB wireless LAN adapters but have ordered a couple and hope to report in a few weeks.



  • I don't know if the Motorola USB WLAN device is supported in FreeBSD.

    How about posting (in a reply) a few lines from the startup output before and after the Motorola was reported? Then someone can tell you if it was a real WLAN driver that attached to the Motorola (in which case you can probably do something useful with it) or it was the generic USB driver (in which case you probably can't do anything useful with it in the near future).

    From the shell prompt the "dmesg" command will display the startup output.



  • @Slam:

    … but I wouldnt mind getting hold of the isa2pci expansion card so that I can throw in either a wireless card or even a pci adsl card, …

    AFAIK there is no support for ADSL cards in pfSense so better use a wireless card instead ;-)



  • @wallabybob:

    I don't know if the Motorola USB WLAN device is supported in FreeBSD.

    How about posting (in a reply) a few lines from the startup output before and after the Motorola was reported?

    Bob
    Thanks for the tip on dmesg as I would not know how else to get this output. I usually used log under menu…

    Here is the few (sorry if too many) around the Motorola USB for a home machine running 1.2.1-RC1

    
    kbd0 at atkbd0
    atkbd0: [GIANT-LOCKED]
    atkbd0: [ITHREAD]
    fdc0: <floppy drive="" controller="">port 0x3f4-0x3f7 irq 6 drq 2 on acpi0
    fdc0: No FDOUT register!
    device_attach: fdc0 attach returned 6
    sio0: configured irq 4 not in bitmap of probed irqs 0
    sio0: port may not be enabled
    sio0: configured irq 4 not in bitmap of probed irqs 0
    sio0: port may not be enabled
    sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
    sio0: type 8250 or not responding
    sio0: [FILTER]
    sio1: configured irq 3 not in bitmap of probed irqs 0
    sio1: port may not be enabled
    fdc0: <floppy drive="" controller="">port 0x3f4-0x3f7 irq 6 drq 2 on acpi0
    fdc0: No FDOUT register!
    device_attach: fdc0 attach returned 6
    sio1: configured irq 3 not in bitmap of probed irqs 0
    sio1: port may not be enabled
    pmtimer0 on isa0
    orm0: <isa option="" roms="">at iomem 0xc0000-0xc7fff,0xc8000-0xc87ff pnpid ORM0000 on isa0
    ppc0: parallel port not found.
    sc0: <system console="">at flags 0x100 on isa0
    sc0: VGA <16 virtual consoles, flags=0x300>
    sio1: configured irq 3 not in bitmap of probed irqs 0
    sio1: port may not be enabled
    vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    ugen0: <cybertan 0="" 2="" motorola="" wireless="" usb="" adapter,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on uhub0
    Timecounters tick every 1.000 msec
    Fast IPsec: Initialized Security Association Processing.
    hptrr: no controller detected.
    Waiting 5 seconds for SCSI devices to settle
    ad0: 38166MB <wdc wd400eb-75cpf0="" 06.04g06="">at ata0-master UDMA33
    acd0: CDROM <toshiba 1017="" cd-rom="" xm-6602b="">at ata1-master UDMA33
    SMP: AP CPU #1 Launched!</toshiba></wdc></cybertan></generic></system></isa></floppy></floppy> 
    

    I don't need much fancy on my home machine like traffic shaper etc…
    Much thanks again.



  • You're not in luck with the Motorola WLAN adapter. None of the standard WLAN drivers recognised it. The clue is the ugen0 in

    vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    ugen0: <cybertan 0="" 2="" motorola="" wireless="" usb="" adapter,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on uhub0
    Timecounters tick every 1.000 msec</cybertan></generic>

    ugen is a "generic" USB device driver, not a network device driver.

    None of my usual sources list the chipset used in the Motorola WU830G USB WLAN adapter so its pretty likely there is no opensource driver for it. You may be stuck with using it on Windows.

    This illustrates one of the problems with opensource/free software: lots of chipset manufacturers don't provide drivers or the necessary information to write drivers.

    A further problem is that its often not easy to determine the chipset used in a particular model device. For example the Belkin F5D7050 could have one out of at least 3 different chipsets from 3 different suppliers, each chipset needs a completely different driver and (as best I can tell) there are drivers for only 2 of those chipsets in FreeBSD.

    A few weeks ago I bought a couple of D-Link DWL-G122 USB WLAN adapters on ebay for only a few dollars each. This model could also have one of 3 different chipsets. The two most recent variants (revision B.1 and C.1) are supported in FreeBSD 7.0 and hence pfSense 1.2.1. I haven't yet tried them out for their WLAN capability so can't comment on how well they work. I chose this model out of a fairly limited range of options because both the recent variants are reported in the FreeBSD man pages as supporting "Host Access Point" mode (ural and rum drivers) as well as "infrastructure" (connects to an access point) and "ad hoc" mode (two stations only without an access point)



  • Many thanks for your clarifications.

    @wallabybob:

    You're not in luck with the Motorola WLAN adapter. None of the standard WLAN drivers recognised it. The clue is the ugen0 in

    vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    ugen0: <cybertan 0="" 2="" motorola="" wireless="" usb="" adapter,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on uhub0
    Timecounters tick every 1.000 msec</cybertan></generic>

    ugen is a "generic" USB device driver, not a network device driver.


Log in to reply