Hyperion Entertainment Message Boards

I can't answer your question, but I have pointed it out to others more skilled in the art.

@Skateman

At this moment everyone using an X5000 with the onboard nic and using OS4.1 FE is having the same MAC address!

True, but that's the fault of the driver, not the hardware or firmware. The Hyperion driver does not have that problem.

Short answer: No, there is only the one V53.x version. V53.3 was released in 2011 and no newer version has been released. No bug reports have been filed since 2006, the two from that year were both closed at the time. So your problem has not been reported before. Have you checked it with a clean sys...

@Spectre660: Firstly, I don't remember an "issue" with MAC addresses in the past. Gregor's complaint is the only one I've heard and I haven't seen it confirmed by anyone else (Is Skateman confirming the problem?). Until this thread, I didn't even know that U-Boot regenerated the MAC addresses on boo...

I don't pretend to be an Intuition or a Graphics expert, but as far as I can see, you can't change the width x height values of a screen. In order to change the aspect ratio of a display, you would have to close the screen and reopen it in the new width x height. Of course, you don't have to do that...

If what Skateman says is true (that all later boards act this way), then I would prefer to fix the bug in U-Boot.

Unfortunately we don't yet have access to the U-Boot sources.

No, forget that. You only need the RX, TX and ground. Nothing else is connected at the X5k end. RX from one end becomes TX at the other, so pins 2 & 3 are swapped in the cable. Pin 5 (ground) goes straight through. I would suggest that you use Term on the MicroA1, rather than on a Classic. U-Boot ha...

I'm afraid that I'm out of ideas. Except for that old standby, the CR2032 coin cell. If it's not a hardware issue (and you've shown that you can both read and write to the SD Card), then it must be a software issue. I do suggest you make or buy a null-modem cable. Then you could capture on the Micro...

So, once again, the facts: If you change the stored values of "ethaddr" and "eth1addr" in the SD-RAM variables (listed by "printenv"), they will appear "changed" in the list when you type "printenv" again. If you then type "saveenv" while the SD-RAM variables are "wrong", they will be saved wrong (...

OK, having proved that the SD-RAM variables are correctly regenerated and visible when you type "printenv" in U-Boot, I booted back into AmigaOS but I didn't check (at the time) the value of "ethaddr" as read by AmigaOS. Turns out that what AmigaOS reads is not what U-Boot reads. Looking into it now...