Hello there, i got a rg40xx-h two weeks back and i have no light and no picture, not even the backlight. It boots fine with the stock OS, modified stock, knulli but not MuOs.
I tried with 3 different cards (The stock card and two brand new Lexar 128gb XC v30 U3 A2 Silver Plus) going with dd, rpi imager, usb-imager and even etcher from four different devices (My desktop, my steam deck, my cell phone and the rg40xx itself) all to no avail.
I also tried older versions, it does the same thing, no light, no screen event with pressing reset 3x while holding power.
Doing
gunzip -c < “MustardOS_RG40XX-H_2508.4_LOOSE_GOOSE-a55cdbe8.img.gz” | sudo dd of=/dev/sdd bs=4M conv=fsync status=progress
goes trough, but get stuck at the end for a few minutes with:
8739782656 bytes (8,7 GB, 8,1 GiB) copied, 144 s, 60,7 MB/s
gzip: stdin: invalid compressed data–crc error
8769240576 bytes (8,8 GB, 8,2 GiB) copied, 146 s, 60,1 MB/s
but then finishes and my computer then sees the partitions.
After that, lsblk gets me:
sdd 8:48 1 117G 0 disk
├─sdd1 8:49 1 8M 0 part
├─sdd2 8:50 1 32M 0 part
├─sdd3 8:51 1 16M 0 part
├─sdd4 8:52 1 64M 0 part
├─sdd5 8:53 1 8G 0 part
└─sdd6 8:54 1 8M 0 part
If i verify the disk with gdisk, i then get this:
GPT fdisk (gdisk) version 1.0.10
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): v
Problem: The secondary header’s self-pointer indicates that it doesn’t reside
at the end of the disk. If you’ve added a disk to a RAID array, use the ‘e’
option on the experts’ menu to adjust the secondary header’s and partition
table’s locations.
Warning: There is a gap between the secondary partition table (ending at sector
17127421) and the secondary metadata (sector 17127422).
This is helpful in some exotic configurations, but is generally ill-advised.
Using ‘k’ on the experts’ menu can adjust this gap.
Warning: The size of the partition table (1024 bytes) is less than the minimum
required by the GPT specification. Most OSes and tools seem to work fine on
such disks, but this is a violation of the GPT specification and so may cause
problems.
Identified 1 problems!
Even if i try to fix it it changes nothing.
Anyone got any idea what could work for this?