who tells you that serial ?Serial on the Patched Firmware shows20201228which is nowhere to be seen in the File from HxD.
who tells you that serial ?Serial on the Patched Firmware shows20201228which is nowhere to be seen in the File from HxD.
i found a checksumlsusb -d 534d:2130 -vvv | grep -i serial
But I still don't understand why the VendorID changes after changing ANYTHING. Do they have some kind of CRC/Checksum and if that fails, they load a Fallback Image or something ?


I received this with my 12-board package, so I was hoping someone from you guys will knowA Picture where we could see:
- The FULL Part Number (is that a2or8or what between33and00?)
- The Part in Question (Picture from the opposite Side)
I would have thought one small Solar Busbar if I were to throw a wild Guess but hey that's the Info I can gather from this Picture![]()
Ah, makes sense
written in nice letters on the left of the checksum (screenshot results)What Checksum algorithm is that they used ?
Eh ? What do you mean "vents that fit into plastic holders" ? I didn't mount the Fan with the Fan Clips just yet ...What type are those vents that fit into plastic holders that came with the board? Isn't it option?
checksum-16, not a CRC.So that would explain why it's falling back to some sort of stock Firmware, the CRC mismatches.
if not selected, not included in checksum-16IAlright. Is the25 F7(just before the Checksum itself) to be included in the Checksum Calculation ? Or what is it otherwise ? You did NOT have it as selected in your Screenshot.
They said that LATEST (and I think ONLY L2.12, although possibly also L2.11 is affected ?) BIOS only supported AMD Series 3000/5000 CPUs: https://forums.servethehome.com/ind...ack-b450d4u-v1lq5-matx-am4.47305/#post-461607Thought I'd share an interesting observation.
Ordered another 2 boards, a week or so ago, just before the stock dried up.
I received 2 boards, and this time, there was a USB3 cable included.
my existing boards are all Ryzen 3000 series cpu now.
I still had a Ryzen 2600x left for testing etc. gave one of the boards a spin up.
This reminded me of LuckyLinux adventures.
- No video, but boards seems to be posting looking at the debug led activity.
- keyboard and mouse on the built-in USB3 port : not working
- used the provided usb3 cable, that worked.
- had to add a PCIE gpu (old MSI passive cooled thing), to get video posting on screen
was thinking, let's update to bios 2.12 on the Ryzen 2600x, flashed ok, but after rebooting, board gets stuck on b0 (reseat cpu or ram), tried 3 differents dimms. nothing, was convinced i bricked one board. I tried the second last board, left the bios as is (2.09), same story gpu and usb3 cable required in order to do anything, but more or less functional board.
this evening tried a ryzen 3100 cpu on the board i thought i bricked, and connected the vga monitor to the onboard adapter, removed the gpu, left out the usb3 cable and connected keyboard to the onboard usb3 port, and guess what: it boots fine, video posts, keyboard words and easily installed proxmox from a netboot.xyz environment.
lessons learned: ryzen 3000 series are the sweet spot for these boards
take a look at the header, 3C C3 FB A0IAlright. Is the25 F7(just before the Checksum itself) to be included in the Checksum Calculation ? Or what is it otherwise ? You did NOT have it as selected in your Screenshot.
By the Way, it's NOT dried up. There are still at least 2x12 + 30 on eBay for sale if you want moreThought I'd share an interesting observation.
Ordered another 2 boards, a week or so ago, just before the stock dried up.
I received 2 boards, and this time, there was a USB3 cable included.
my existing boards are all Ryzen 3000 series cpu now.
I still had a Ryzen 2600x left for testing etc. gave one of the boards a spin up.
This reminded me of LuckyLinux adventures.
- No video, but boards seems to be posting looking at the debug led activity.
- keyboard and mouse on the built-in USB3 port : not working
- used the provided usb3 cable, that worked.
- had to add a PCIE gpu (old MSI passive cooled thing), to get video posting on screen
was thinking, let's update to bios 2.12 on the Ryzen 2600x, flashed ok, but after rebooting, board gets stuck on b0 (reseat cpu or ram), tried 3 differents dimms. nothing, was convinced i bricked one board. I tried the second last board, left the bios as is (2.09), same story gpu and usb3 cable required in order to do anything, but more or less functional board.
this evening tried a ryzen 3100 cpu on the board i thought i bricked, and connected the vga monitor to the onboard adapter, removed the gpu, left out the usb3 cable and connected keyboard to the onboard usb3 port, and guess what: it boots fine, video posts, keyboard words and easily installed proxmox from a netboot.xyz environment.
lessons learned: ryzen 3000 series are the sweet spot for these boards
# enable OC
printf '%0*x' 48 0 | fold -w 2 | tac | tr -d '\n' | xxd -r -p | sudo tee /sys/kernel/ryzen_smu_drv/smu_args && printf '\x5A' | sudo tee /sys/kernel/ryzen_smu_drv/rsmu_cmd
# vcore 1,2v (VID 56)
printf '%0*x' 48 56 | fold -w 2 | tac | tr -d '\n' | xxd -r -p | sudo tee /sys/kernel/ryzen_smu_drv/smu_args && printf '\x61' | sudo tee /sys/kernel/ryzen_smu_drv/rsmu_cmd
#overclock freq 4000
printf '%0*x' 48 4000 | fold -w 2 | tac | tr -d '\n' | xxd -r -p | sudo tee /sys/kernel/ryzen_smu_drv/smu_args && printf '\x5C' | sudo tee /sys/kernel/ryzen_smu_drv/rsmu_cmd
I know images is a PITA on this Forum, you might need to reduce by 50% Resolution or something. I cannot read your Mind [un]fortunatelyI meant this one. Can't insert image here.
How easy was it to solder the PCIe Slots and M.2 Connectors ?It is a B450D4U-V1LQ5, same as everyone else in this thread bought. The image is of my own board. I don't make the sticker on the board, that's just what ASRock labelled it.
As I said in my previous reply, I would like access to the PCIe configuration in BIOS to test my hardware modifications (addition of PCIe x1, x8, and M2 socket).
you should not overclock a server motherboard, to much RMAs if available.WTF? WHY?
Does that Samsung 970 EVO NVMe SSD support ASPM in any of your other systems? I’ve had problems with Samsung NVMes in the past but that was a long time ago.Weird is that the Samsung SSD claims to NOT support ASPM (Latency is unlimited), yet it claims it within its Capabilities
Aaah you want to put an AMD Stock Cooler with those Plastic Holders that sit on the Motherboard ?This one:
amd am4 bracket (check in more Detail):test results with a 5600G: no GPU (ASPEED), no OC Settings on bios > 2.0, no rear USB.Did you also try that with a 5000 Series CPUs such as e.g. AMD Ryzen 7 5700X ?
Oh Damn I shouldn't have said itSimpson quote:


I didn't check to see if I had any cable at all. For sure NOT in the 2 Motherboards I pulled out of the Box. But knowing how I'm "lucky", they will come out with the last Motherboard I pull out, I'm sure of itThing is, I have these black plastics, they came with boards. There must be cheap compatible cooler that will definitely fit I believe. Had something similar on older sockets.
I also got USB and audio cables, but only 5 for 12 board unfortunately :-(
amd stock cooler, but probably amd am4 cooler would also work):
Don't tempt me too I think I'll also go for another set of 12 and I'll need 22 more CPUs too if I do thatand he'll go after any amd 3xxx or 5xxxx cpu deals too![]()
it's not a real v0.1 if there are no jumper wires soldered on well, the idea is to attach it to the ioshield. Will add some mounting pad/hole on that. A small support structure, so the ethernet jack is somewhere to the right of the onboard NIC and USB3 ports.Did you already figured out where you are going to install it ? Inside the Chassis or out hanging somewhere in a 3D printed Enclosure or something ?
basic 2 layer pcb, bottom ground plane fill and top layer 3.3V fill. The 3.3V from the esp32-s3 should be connected to oled display and W5500 board. I somehow created an island for the esp32-s3 3.3V pin, missed the warning in KiCad, or I didn't upload the very latest version. My latest current kicad files are not having this issue. I noticed it by not working, and measuring some traces. and a nice WTF moment later I saw the mistake.Do you mean you were using a separated Ground ?