Any known working usbadm8511-compatible devices?

@thread

i'm looking for someone who has actually run a USB-to-Ethernet adapter on their AOS4 system with usbadm8511.device. i've found threads where people talked about them, but i don't think anyone can point to a piece of hardware that they've actually used in conjunction with the usbadm8511.device driver? anyone?

-- eliyahu

Took a little more work but I figured it out. Turns out you don't need to set the vendor and device strings in the env vars. What was happening is RoadShow was onlining the interface but it was not detecting the Mac Address correctly. I plugged my F5D5050 to my Linux machine, got the MAC, then programmed that in to the interface file by hand. After that it worked!

I could tell you what system I am using to post this but... :)

Bill "tekmage" Borsari

@eliyahu

Following Belkin USB adapter

https://www.amazon.com/Belkin-F5D5050- ... net-Adaptor/dp/B000062R4P

has the adm8511 chipset but unfortunately usbadm8511.device does not work with this adapter. Probably the driver needs an update for latest AmigaOS4 releases.

@tekmage

AWESOME! would you mind taking a moment to send a note to a certain mailing list explaining in detail which adapter you used, where you bought it, and the steps you took in getting it to work with your system? many thanks in advance!

-- eliyahu

@tekmage

I am also interested. Usbamd8511.device .doc :

-----
usbadm8511.device is a driver for 10/100 MBit/s USB ethernet devices
which use the adm8511 chip.


Configuration
-------------
You can use environment variables to configure the behaviour of the
driver units. The variable is read every time the driver is launched
(ie. when an USB ethernet device is detected).

Currently the supported keywords are:

VENDORID/K/N -- Force device to use custom USB vendor ID.

DEVICEID/K/N -- Force device to use custom USB device ID.

10BASE-T=10BASET/S -- Force device to use 10 BaseT (10MBit/s).

100BASE-TX=100BASETX/S -- Force device to use 100 BaseTx (100MBit/s).

HALFDUPLEX/S -- Force device into half duplex mode.

FULLDUPLEX/S -- Force device into full duplex mode.


All this has to be put into "ENV:USB/usbadm8511.device/unitx" where x
is the unit number. An example, to be typed in a single line:

SetEnv SAVE USB/usbadm8511.device/unit0
"VendorID=1234 DeviceID=4321 100Base-TX FullDuplex"

When no USB vendor ID and USB device ID are specified, the driver tries
to find the first unused USB ethernet device which matches an internal
list of supported vendor/device pairs. You can use
SYS:Utilities/USBInspector to find out the vendor and device numbers of
your USB ethernet hardware.

Only one of the 10BASET and 100BASET keywords may be specified. When none
is specified, the driver uses auto negotiation for the speed configuration.

Only one of the HALFDUPLEX and FULLDUPLEX keywords may be specified. When
none is specified, the driver uses auto negotiation for the duplex
configuration.

@eliyahu

How I got the Belkin F5D5050 working in my Amiga OS4 system:


First, I was able to order a device off Amazon here:
https://www.amazon.com/Belkin-F5D5050- ... 1&keywords=belkin+f5d5050

When I connected this to my Amiga a few things happened:

The light on the device turned Amber

The USB Device detection window showed up

The USB Log looks like this (type t:usb.log)
I: [16:32:34] hub.usbfd | HUB | Device on hub port 4 successfully added.
I: [16:32:34] USB Fkt Init | Init Fkt | Fkt 0x6f99a470 is {Vendor: 0x07A6, Product: 0x8511, Class: 00.00}
I: [16:32:34] USB Fkt Init | Init Fkt | Fkt 0x6f99a470 ("ADMtek","USB To LAN Converter","0001") initialized
W: [16:32:34] USB FD fkt start | BindInterfaceDriver | No interface driver of fkt 0x6f99a470/ifc 0x63956f00 {Class 00.00} has been found
W: [16:32:34] USB FD fkt start | FD launcher | Could not bind any suitable interface driver for fit 0x6f99a470

This is ok, there is no USB ethernet device class so the USB stack does not have a class to bind. When the network device is launched it will bind to the device, assuming it’s setup right.

The next step is to configure a network interface using the usbadm8511.device.

Open the prefs/internet application. Select “new” then open the requester and pick "usbadm8511.device”. At this point one of two things will happen.

If the type show up as “ethernet”, then the driver was able to connect to the device and you can go to the next step.

If the the shows up as “Unknown”, you need to set an environment variable to help the driver find the device. To do that look at the USB log for the “Vendor” and “Product” numbers, like this: Vendor: 0x07A6, Product: 0x8511

Next convert those numbers from HEX to DEC, I used google. Then execute the following in a shell, but with your numbers:

>setenv save usb/usbadm8511.device/unit0 "VENDORID=1958 DEVICEID=34065”

In either case I would reboot at this point. Recommend that before you do make sure the device is plugged in to an active ethernet link is connected.

After the reboot, open a new shell (Amiga-E and “newcli” works). Then execute:
>shownetstatus interface <name of the usb interface>

The output will look like this:

4.System:> shownetstatus interface interface.1
Interface "interface.1"
Device name = usbadm8511.device
Device unit number = 0
Hardware address = 00:00:00:00:00:00
Maximum transmission unit = 1514 Bytes
Transmission speed = 10000000 Bits/Second
Hardware type = Ethernet
Packets sent = 2
Packets received = 20
<snip>

The problem is the MAC of the network interface is set to 00:00:00:00:00:00. This is why it will not work.

Next, connect the device to a linux system to obtain the proper mac address. Windows might work but you need to deal with drivers. Under the linux shell run “#ip link” to see the devices and their MAC address.

Once you have the MAC address we need to program that address in to the interface file. Simple opened the interface file in sys:devs/netinterfaces/ and added the the following line:

hardwareaddress=00:05:1b:70:d1:da

Besure to program your static address or set the device to use dynamic addressing and rebooted the system once more

Boom! Online.


I hope this works for others. I've tested on Amiga's big and small.

Cheers,
Bill "tekmage" Borsari

Thank you guys for this info. I managed to make an SMC SMC2206USB/ETH to work just fine.

I had the same problem with MAC address not recognised. I also had to add the following at the interface file
unit=0
configure=dhcp

Thanks again for that info

@tekmage
Quote:
My ethernet adapters & router have the MAC address on the underside of the devices below the serial number. It might be worthwhile for users to check on their devices before using Linux to get the MAC address.

@tekmage

Thanks. With your method, Belkin FD5050 works on 3 AmigaNGs that I have..

@tekmage

Thanks for the tip, worked like a charm. Now online with my usbadm8511.device.

I did not have to convert product/device information to decimal because the Vendor and product numbers were identical to your model. I was able to read the Macx address via a Windows machine without problem using ipconfig /all from a Dos CMD window,

Thanks again,

TrevorD