Help setting up Roadshow with X-Surf 100

[Overmann]

Originally Posted by patrik

This is how it looks for me if I run with debug=yes and configure=dhcp in DEVS:NetInterfaces/X-Surf-100:
25-Okt-18 20:59:20 [Debug] Unknown Interface 'X-Surf-100' hardware address = 28:CD:4C:FF:FD:1E.
25-Okt-18 20:59:20 [Debug] Unknown Setting up BOOTP packet for 'X-Surf-100' with hardware address 28:CD:4C:FF:FD:1E.
25-Okt-18 20:59:20 [Debug] Unknown Sent initial DHCPDISCOVER request for 'X-Surf-100'; transaction ID=0x726FF515, retry timeout=0:00:04 hours, allocation timeout=0:01:00 hours.
25-Okt-18 20:59:24 [Debug] Unknown DHCP retry timeout for 'X-Surf-100' has elapsed.
25-Okt-18 20:59:24 [Debug] Unknown Setting up BOOTP packet for 'X-Surf-100' with hardware address 28:CD:4C:FF:FD:1E.
25-Okt-18 20:59:24 [Debug] Unknown Resent DHCPDISCOVER request for 'X-Surf-100'; transaction ID=0x3AF3361B, retry timeout=0:00:08 hours.
25-Okt-18 20:59:24 [Debug] Unknown Received BOOTP/DHCP server message for 'X-Surf-100'.
25-Okt-18 20:59:24 [Debug] Unknown Picking up BOOTP/DHCP server message for 'X-Surf-100'.
25-Okt-18 20:59:24 [Debug] Unknown Configuration information for 'X-Surf-100': Server identifier = 192.168.0.1.
25-Okt-18 20:59:24 [Debug] Unknown Setting up BOOTP packet for 'X-Surf-100' with hardware address 28:CD:4C:FF:FD:1E.
25-Okt-18 20:59:24 [Debug] Unknown Setting up DHCP packet for 'X-Surf-100' with transaction ID = 0x3AF3361B, server address = 192.168.0.1, client address = 192.168.0.30.
25-Okt-18 20:59:24 [Debug] Unknown Responding to DHCP offer; sent DHCPREQUEST request for 'X-Surf-100'; transaction ID=0x3AF3361B, retry timeout=0:00:03 hours.
25-Okt-18 20:59:24 [Debug] Unknown Received BOOTP/DHCP server message for 'X-Surf-100'.
25-Okt-18 20:59:24 [Debug] Unknown Picking up BOOTP/DHCP server message for 'X-Surf-100'.
25-Okt-18 20:59:24 [Debug] Unknown Server has responded to address allocation request for 'X-Surf-100'. Suggested IP address is 192.168.0.30.
25-Okt-18 20:59:24 [Debug] Unknown Checking if the IP address 192.168.0.30 proposed for 'X-Surf-100' is already in use.
25-Okt-18 20:59:24 [Debug] Unknown Configuration information for 'X-Surf-100': Server hardware address = 00:1B:21:81:1E:6C.
25-Okt-18 20:59:26 [Debug] Unknown IP address verification timeout for 'X-Surf-100' has elapsed.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Server identifier = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Address lease time = 0 day(s), 0:10:00 hour(s).
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Subnet mask = 255.255.255.0.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Router = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Domain name system server = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Domain name = "localnet".
25-Okt-18 20:59:26 [Debug] Unknown Binding address of 'X-Surf-100'.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Server identifier = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Server IP address = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Setting interface 'X-Surf-100' address to 192.168.0.30.
25-Okt-18 20:59:26 [Debug] Unknown Setting interface 'X-Surf-100' net mask to 255.255.255.0.
25-Okt-18 20:59:26 [Debug] Unknown Interface 'X-Surf-100' IP address is now set to 192.168.0.30/255.255.255.0.
25-Okt-18 20:59:27 [Debug] Unknown Interface 'X-Surf-100' address successfully changed to 192.168.0.30/255.255.255.0.


One thing that is very interesting is that your card reports the hardware address as 00:00:00:00:00:00, which is not correct, it should report an address starting with the Individual Computers OUI 28:cd:4c.

Have you tried xsurftest included in the driver archive? Should look like this:
7.Ram Disk:> xsurftest
X-Surf TestPrg V1.10 (Sep 12 2013)

Searching for X-Surf 10 (VEN_ID=4626, PROD_ID=23)
or X-Surf 100 (VEN_ID=4626, PROD_ID=100)....found X-Surf 100
found
Board address = 0x40000000
nic=40000c00
Searching for RTL8019 at 0x300...not found! (ID0=255, ID1=255)
Testing 16bit memory...ok!
Ethernet address = 28:cd:4c:ff:fd:1e
Chip is in jumper mode
Chip is using full-duplex mode
Chip is using IOBase something (0xf) and IRQ something (7)

IRQ / Loopback / cable connection test in progress:
IRQ received ok.
Packet send......via 100Mbit/s full duplex!


This should not be run when the interface is online.

On that note, which version of the driver are you using?

Thanks Patrik, for sticking with me here. I sent my busboard to finland for a recap and got it back this week. I had some time to test it yesterday and I've had more luck with my xSurf now.

Xsurftest gives me three different results. Some times it fails the memory test. Sometimes it fails the loopback test and sometimes it's just like your results above. Usually i find that if I turn off the amiga the first results after turning it on will be a failed memory test. Here Ethernet address = will always be 00:00:00:00:00:00 as well.
If I do a cold reboot I often find that it reports back a successfull test like yours, and when I execute network-startup I'm online in about 10 seconds. Sometimes though it fails the loopback, and when it does it won't go online. But usually it's just the first try after a hard reboot that results in failed test and no online. It's MUCH better then what I had before.

So a cold reboot seem to do something. The hardware address get assigned or something, as after a hard reboot it's often just 00:00:00:00:00:00.

EDIT:
After more testing I can say that every time the xsurf fails to get a proper hardware address it fails to get online. A reboot or four usually solves it. Does anyone know what could be causing XSurf to get a hardware address of 00:00:00..... , and how I might fix it permanently?