Moschip 7830 precompiled driver



  • Here is precompiled driver for pfsense 2.0 based on bsd 8.1
    http://www.upload.ee/files/1946687/if_mos.ko.html
    Im using it and it works fine :)


  • Netgate Administrator

    Is this 32bit or 64?

    Steve



  • sorry forgot its 32 bit driver



  • Would you provide the make and model of the specific hardware you're using?

    Also, what speed is your internet connection, and what speeds are you seeing through the adapter?



  • I'm a Windows user, so I'm just making a note of how I copied this precompiled driver onto the system and got it to load.

    First I formatted a USB stick to FAT16 and copied if_mos.ko to it.
    I plugged it into the pfsense system and ran:
    mkdir /mnt/stick
    mount_msdosfs /dev/da0s1 /mnt/stick
    cp /mnt/stick/if_mos.ko /boot/kernel
    kldload if_mos.ko
    vi /boot/loader.conf
    i

    Add in:
    if_mos_load="YES"
    to the end of the file.
    Hit Esc.  Type :w and hit enter, then type :q and hit enter.
    quit
    And then reboot the system.



  • This driver didn't have the traffic shaper enabled for it (as it wasn't included), but Bug #1850 specifically mentions that altq should work in this driver.

    Editing the "/etc/inc/interfaces.php" file, change line 3585 from:

    			"ste", "stge", "txp", "udav", "ural", "vge", "vr", "wi", "xl",
    

    to

    			"ste", "stge", "txp", "udav", "ue", "ural", "vge", "vr", "wi", "xl",
    


  • @atamido:

    vi /boot/loader.conf
    i

    It would be better to add the line to /boot/loader.conf.local since /boot/loader.conf is not guaranteed to survive a firmware upgrade but /boot/loader.conf.local is supposed to survive a firmware upgrade.



  • Thanks, I've made that change.  :)

    The ironic bit is that the USB NIC has been fine so far, while the onboard NIC using the "bge" driver has been unstable (appears to be a known issue starting with BSD 7.x).



  • I suppose I should mention that I picked up this adapter:

    http://www.bestofferbuy.com/eumark-usb-10100m-rj45-ethernet-network-adapter-dongle-moschip-mcs7830-p-26370.html

    It cost $8.60 and shipping from Hong Kong to the US was free (although it did take a couple of weeks).  I'm not really sure how they make a profit, possibly some poor fisherman loads up their boat and sails across the big pond?



  • i tried to install the moschip 7830,
    i copied the if_mos.ko to /boot/kernel
    and added the line to the loader.conf
    kldstat output:
    Id Refs Address    Size    Name
    1    8 0xc0400000 1178ad8  kernel
    2    1 0xc1579000 4d04    if_mos.ko

    after restart the driver is loaded , but the system don't recognise the usb adapter.
    can anyone help me?



  • What version of pfSense are you using?

    Please provide the output of pfSense shell command```
    usbconfig dump_device_desc



  • hi
    2.0.1-RELEASE pfSense

    usbconfig dump_device_desc

    ugen0.2: <usb 10="" 2.0="" 100m="" ethernet="" adaptor="" vendor="" 0x0fe6="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

    bLength = 0x0012
      bDescriptorType = 0x0001
      bcdUSB = 0x0110
      bDeviceClass = 0x0000
      bDeviceSubClass = 0x0000
      bDeviceProtocol = 0x0000
      bMaxPacketSize0 = 0x0040
      idVendor = 0x0fe6
      idProduct = 0x9700
      bcdDevice = 0x0101
      iManufacturer = 0x0000  <no string="">iProduct = 0x0002  <usb 10="" 2.0="" 100m="" ethernet="" adaptor="">iSerialNumber = 0x0000  <no string="">bNumConfigurations = 0x0001

    thx 4 help</no></usb></no></usb>



  • According to the USB ids file on Ubuntu 12.04 (idVendor = 0x0fe6, idProduct = 0x9700) indicates a Kontron DM9601. Based on the same file I would expect a MOSCHIP 7830 to have (idVendor = 0x9710, idProduct = 0x7830).

    I downloaded the MCS7830 datasheet from http://www.datasheetarchive.com/MCS7830-datasheet.html The datasheet suggests the MCS7830 is capable of USB high speed (480Mbps) operation but your device is connecting at USB full speed (12Mbps).

    Hence I expect you don't really have a MosChip 7830.

    Maybe you could plug this device into a Linux system and see what driver (if any) claims it.


Log in to reply