1
Blackbird / Re: SATA ports on the fritz?
« Last post by MPC7500 on February 05, 2023, 11:08:46 am »You're welcome
https://twitter.com/mpc7500v2/status/1622280764027985920
https://twitter.com/mpc7500v2/status/1622280764027985920
Recent Posts
2
Blackbird / Re: SATA ports on the fritz?
« Last post by Hasturtium on February 05, 2023, 10:36:21 am »You also could give me your ticket number. I could post it on Twitter.
Thank you - I deleted my account there recently. My ticket number is #493290.
3
Blackbird / Re: SATA ports on the fritz?
« Last post by MPC7500 on February 05, 2023, 08:50:15 am »You also could give me your ticket number. I could post it on Twitter.
4
Blackbird / Re: SATA ports on the fritz?
« Last post by Hasturtium on February 04, 2023, 08:45:58 pm »That definitely qualifies. Haven't gotten an update on the support ticket I placed a week ago, so I believe I'll give them a call on Monday.
5
Blackbird / Re: SATA ports on the fritz?
« Last post by ClassicHasClass on February 04, 2023, 04:04:21 pm »It eventually started showing a red background on everything and abnormal colours, when it showed video at all. I think that qualifies as "bananas." 
6
Blackbird / Re: Onboard nic not working
« Last post by meklort on February 04, 2023, 10:51:22 am »So, this is what the state as I see it:
- Linux appeases to be unable to acquire a lock in the hardware. (see https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/broadcom/tg3.c#L15439)
- The APE or RX firmware in the part has priority over Linux
- The APE or RX firmware likely has acquired the lock, and failed to release it due to an infinite loop / PHY hardware not responding how the firmware expected it to.
(Note: If you have an older version of the firmware, the RX firmware acquired the lock for the endpoint it was running on, however this failed to work in some cases, and is disabled in newer firmware. The APE firmware still grabs a lock as well, however this should be for one port only, not all of them, and so I don't expect this to be where the issue is)
All that said, when the lock failed to be acquired, Linux stopped initializing the device, and so you don't get the eth port showing up.
This is also why fwupd and ethtool failed to work - they depend on the tg3 driver being loaded.
To fix this, you'll need to do one of a two things:
- Try connecting to a different external device like a switch before going to the router and see if you get a different result. This is probably the simplest option if it works (unlikely due to all ports failing to initialize)
- If you're unable to get Linux to ever see the device, you'll need to install the development tools for the OSS firmware and at that point there are a couple of options.
(1) You can try loading the proprietary firmware image and see if that works. if it does *not* work, you'll need to RMA with Raptor as it's a hardware issue. If, on the other had, the proprietary firmware works, you can leave it as-is, or, we can flash the latest oss fw release and continue to (2)
(2) You/We can try debugging the issue. You'll need to provide dumps of the registers using the bcmregtool utility. That'll let me know if the firmware is spinning / locked up, the firmware version, etc and if there's an easy fix.
- Linux appeases to be unable to acquire a lock in the hardware. (see https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/broadcom/tg3.c#L15439)
- The APE or RX firmware in the part has priority over Linux
- The APE or RX firmware likely has acquired the lock, and failed to release it due to an infinite loop / PHY hardware not responding how the firmware expected it to.
(Note: If you have an older version of the firmware, the RX firmware acquired the lock for the endpoint it was running on, however this failed to work in some cases, and is disabled in newer firmware. The APE firmware still grabs a lock as well, however this should be for one port only, not all of them, and so I don't expect this to be where the issue is)
All that said, when the lock failed to be acquired, Linux stopped initializing the device, and so you don't get the eth port showing up.
This is also why fwupd and ethtool failed to work - they depend on the tg3 driver being loaded.
To fix this, you'll need to do one of a two things:
- Try connecting to a different external device like a switch before going to the router and see if you get a different result. This is probably the simplest option if it works (unlikely due to all ports failing to initialize)
- If you're unable to get Linux to ever see the device, you'll need to install the development tools for the OSS firmware and at that point there are a couple of options.
(1) You can try loading the proprietary firmware image and see if that works. if it does *not* work, you'll need to RMA with Raptor as it's a hardware issue. If, on the other had, the proprietary firmware works, you can leave it as-is, or, we can flash the latest oss fw release and continue to (2)
(2) You/We can try debugging the issue. You'll need to provide dumps of the registers using the bcmregtool utility. That'll let me know if the firmware is spinning / locked up, the firmware version, etc and if there's an easy fix.
7
Blackbird / Re: Onboard nic not working
« Last post by power9mm on February 02, 2023, 12:54:07 pm »Yeah.
it's just a blackbird with an 8 core cpu. Vega 64, 2.5 SSD and a pcie nic. Nothing special. its just hard wired into a librecmc router which is just wired to a modem. Cat6 cable i think.
I can try connecting to the BMC with an airgapped laptop I suppose. I don't want to connect that port to any internet connected devices.
it's just a blackbird with an 8 core cpu. Vega 64, 2.5 SSD and a pcie nic. Nothing special. its just hard wired into a librecmc router which is just wired to a modem. Cat6 cable i think.
I can try connecting to the BMC with an airgapped laptop I suppose. I don't want to connect that port to any internet connected devices.
8
Applications and Porting / Re: [GAMES] ET Legacy
« Last post by power9mm on February 02, 2023, 12:51:16 pm »https://github.com/etfdevs/ETe
you'll probably want to try this instead for playing ET online, it probably runs a lot better too.
you'll probably want to try this instead for playing ET online, it probably runs a lot better too.
9
Applications and Porting / Re: [GAMES] ET Legacy
« Last post by power9mm on February 01, 2023, 10:45:49 pm »As an update to this. Quake 3 plays on line just fine (with either ioquake3 or quake3e)
connects to sv_pure 1 servers no problem.
I imagine the same would be the case with ioRTCW
performance isn't as good vs x86 right now though.
connects to sv_pure 1 servers no problem.
I imagine the same would be the case with ioRTCW
performance isn't as good vs x86 right now though.
10
Blackbird / Re: Onboard nic not working
« Last post by meklort on February 01, 2023, 10:29:21 pm »Ah, that's very interesting. The tg3.c source code has ENODEV being reported in tg3_phy_probe. That routine has to cooperate with the APE firmware for everything to work right, so now I'm wondering what the APE firmware log is showing.
In any case, that's not expected, can you provide more details on your setup? What are you connecting to? What cables are you using? etc.
If you are willing to setup a dev environment, you can get a dump of the ape console and see what the firmware is trying to do. You'd need to compile the ape console utility in the firmware repo here: https://github.com/meklort/bcm5719-fw or use the prebuilt binary included in the release package, if you don't want to setup the environment yourself).
It'd also be worth connecting the BMC port to a switch / router / etc and seeing if you're able to talk to it before the OS starts up. My first guess is that the APE firmware is getting locked up somewhere (possibly also talking to the PHY), and not releasing the PHY resources for Linux.
In any case, the APE console output would be very useful to debug it.
In any case, that's not expected, can you provide more details on your setup? What are you connecting to? What cables are you using? etc.
If you are willing to setup a dev environment, you can get a dump of the ape console and see what the firmware is trying to do. You'd need to compile the ape console utility in the firmware repo here: https://github.com/meklort/bcm5719-fw or use the prebuilt binary included in the release package, if you don't want to setup the environment yourself).
It'd also be worth connecting the BMC port to a switch / router / etc and seeing if you're able to talk to it before the OS starts up. My first guess is that the APE firmware is getting locked up somewhere (possibly also talking to the PHY), and not releasing the PHY resources for Linux.
In any case, the APE console output would be very useful to debug it.
