x1000 onboard network opensource driver in progress: new version

@All
While it's not related to driver , but this is related to onboard network. Find out that this "need to reset few times to make onboard network enables in hardware" , have pretty interesting pattern:

When you power on computer and watch over CFE output, you will noticed that:

Quote:

All fine. The light on the router up, onboard network up in hardware, so driver in os4 able to use it.

Now , simple hit "reset" , or type in CFE "reset" , and now, you will have in CFE output that:

Quote:

And then, light on router not up, there no link, onboard network simple didn't happens to be ON. Currently I don't know if it hardware issue (like wrong power signals or timing or whatever), or if it simple CFE acts again and simple didn't re-init it properly on the reset or so..

On my X1000, everytime I turn it on, the ethernet goes on.

I have never encountered any case where it doesn't start (I never use warm boot since I'm using an RX 560).

Hello,

I remember having a similar experience with the RTL card installed in my machine.
Ranger recognized the card as an RTL 8169 instead of an 8139, and internet did not worked until I turned off and on the computer.

@K-L
Quote:

But that full power off / power on, right ? Issue is exactly "reset". You can try for example to reproduce it like this : even with rx560, hit "reset" button one time , and see what happens with the "led" on the router where cable from x1000 connected to. Then another reset, and watch again : will it be the case that one of times it "up and green" , and another time stays without light ?

@Petrol
Can you also do the same ?

The point is to understand if it happens on every X1000, or on some revisions , or on some CFEs, etc.

@kas1e

I do make some hardware resets (sometimes two in a row) when I have a Grim Reaper or when pushing the button: every time the ethernet is on after the reboot.

@K-L
And you do have CFE update from 2012_june_08 as well or original one ? Also, how much memory you have installed (maybe that related somehow ..)

@All
I do not know if there were different revision of x1000 or all was one single batch ?

@kas1e
Quote:Single batch: No.
For all AmigaNG PPC systems first only a small number of early/beta systems were built, only available to kernel, hardware driver and Linux developers.
In case of the EyeTech AmigaOne it was the AmigaOne SE, never sold publicly and only available to developers and beta testers, only the XE and µ1 versions were available to normal users.
Same for the X1000, X5000 and A1222+, and probably the Sam440 and Sam460 as well.
It's possible that the final version available to end users is identical to the few early/beta systems in some cases, but rather unlikely as there probably was none on which no single hardware bug was found while developing AmigaOS 4.x and Linux for it.

@kas1e

Yes, I also have a driver problem. Every time I soft reset, I get the error "Pa6t_eth.device cannot be opened" and I have no network connection. Second soft reset helps 90% of the time (but not always). A hard reset always helps.

@Mufa
Not a driver problem as i say, but a hardware problem , or, CFE problem. Check plz what happens with your light on the router when you boot your x1000 after reset : when it works, you will see "light up" right after you reset , after 5 or so seconds. When you do another reset, "light up" on router didn't light up, and that while we even didn't reach amigaos at all : its all in the CFE.

Please check if that the case (i.e. check if when you reset, sometime light up on router connected to x1000 didn't up, and sometime did up).

I.e. you can even not load amigaos4 at all. You can do all tests in CFE : just reset, go to CFE, try to "ifconfig eth0 -auto" -> when hardware not enables, link will stay died, and ifconfig will not work. And another reset, check again light on router, and try "ifconfig eth0 -auto", if light was up, ifconfig will works too.

The only thing we need to understand why this happens on some motherboards, and didn't happens on another ones. Is it CFE different, or revision of motherboards different.

@kas1e

Ok, I'll check on Sunday, because I'm not at home at the moment and I don't have access to my X1000

@kas1e
Perhaps it depends on the device or how it behaves when connected?
If you can, could you try using a bridge (between the x1000 and the router/switch) to check whether any packets are being sent, if anything is happening, and what exactly?
Is there a setting on the device or router that allows you to disable auto-negotiation?
It might be a silly idea, but have a look.

My x1000 is from first contact batch and has this behavior with on/off network.

But hey, i just had a download speed of 5–6 MB/s...I never would have thought that was possible with the network stack.
But there it was:
https://youtu.be/kK83xXgN2nk?is=PXqbkJdPEdDMuwEn

Nice 👍

My x1000 has a 8169..
When I switched over to your driver, this is what I got

could not open "pa6t-eth.device "unit 0
(device/unit failed to open)

I read the on/off thread doesn't seen to be my issue?

any suggestions

Michael

BTW, my CFE version is PAS-2.0.30 from ranger

@sacc-dude
That mean you have hardware issues with your network. Remove dust from port, check if not corrozied and check if you have green light up on port when you power on machine: only then driver can find hardware. Until your both links on x1000 port and router port not green driver can do nothing about

@kas1e

ports cleaned, green lights turn on at motherboard and router.
at power up and reset..

same result

oh well, I've waited this long maybe we can think of something (sigh)
Michael

@sacc-dude
Strange.. You need to be double sure green lights are works. Try the if it works in CFE at all : reboot , go to CFE and type "ifconfig eht0 -auto" and then "ping <your_router_ip_or_any_ip_in_local_network>" to see if network works in CFE at all.

the CFE responds
eth0 1000BaseT FDX command status = 0

then it give a list of configs

I didnt do a ping as I have no knowledge address to use

light on motherboard ison and flashing
router is on and flashing

added!

serial cable to read output last lines said

[pa6t_eth} init pa6t_eth.device 1.1.(23.03.2026) (c)2026 kas1e
[pa6t_eth] init: failed to open expansion library

@sass-dude
Quote:

You have no expansion library in system ? Too old kernel ? Or deleted library ? init.c of driver have that code:



So your expansion library isn't found , or of older version or something of that sort happens. Without of course nothing will works.

I saw that (sigh)

I have several next gen amigas..
I will look for that
but I only remember expansion from classic?