Login
Username:

Password:

Remember me



Lost Password?

Register now!
Sections
Who's Online
66 user(s) are online (50 user(s) are browsing Forums)

Members: 0
Guests: 66

more...
Support us!
Recent OS4 Files
OS4Depot.net
Report message:*
 

Re: Any known working usbadm8511-compatible devices?

Subject: Re: Any known working usbadm8511-compatible devices?
by tekmage on 2017/9/30 4:29:56

@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
Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project