DC-DeepComputing / DC-ROMA_Pad_II_RV-P1B

2 stars 2 forks source link

Reimaging #10

Open ppenzin opened 3 weeks ago

ppenzin commented 3 weeks ago

I've tested images found in the repository as well as live Debian included with the Pad. Burnt with Balena (did some with dd as well, same results), I have 16GB/128GB (RAM/EMMC) version. All images are taken from provided artifact repository, I just went to its parent directory. Result:

The fact that neither of the install images boot is a bit underwhelming. There must be a way to flash emmc from a live image, right?

ppenzin commented 3 weeks ago

@Haui1112, to answer your question in https://github.com/DC-DeepComputing/DC-ROMA_Pad_II_RV-P1B/issues/1#issuecomment-2453311697, dd with default settings takes a very long time to finish (FreeBSD version does on my machine, anyway), but I'll take another at that.

Also for unminimize (https://github.com/DC-DeepComputing/DC-ROMA_Pad_II_RV-P1B/issues/1#issuecomment-2453345706), it might be possible to try it out on one of the live images, as you can just eject the card and re-burn it.

DoktorCranium commented 3 weeks ago

Weird - I reflashed a couple of times my Pad with ubuntu-24.04-desktop-k1-pad-9985-upgradecard.zip. image, and all is ok. You need to write the ubuntu-24.04-desktop-k1-pad-9985-upgradecard.zip to a MMC card, boot it off and wait for the process to finish, once you will see (after a few minutes) an ASCII message DONE - you can eject the MMC and boot to the stock image.

ppenzin commented 3 weeks ago

@DoktorCranium, that is really weird, I left it for a few hours and the screen was just blank. What configuration of the Pad do you have (memory, storage)? Not sure there are any significant differences between them though

DoktorCranium commented 2 weeks ago

maybe you have a bad MMC card, or the image wast not transferred properly to the MMC, I have the 16GB RAM model with 128 GB storage. The screen should definitely not be black, as you will see the flashing progress on the display.

On Mon, Nov 4, 2024 at 8:58 PM Petr Penzin @.***> wrote:

@DoktorCranium https://github.com/DoktorCranium, that is really weird, I left it for a few hours and the screen was just blank. What configuration of the Pad do you have (memory, storage)? Not sure there are any significant differences between them though

— Reply to this email directly, view it on GitHub https://github.com/DC-DeepComputing/DC-ROMA_Pad_II_RV-P1B/issues/10#issuecomment-2455586722, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFYTCKBRQZS73K24RIA2R6LZ667VRAVCNFSM6AAAAABRDM7VVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJVGU4DMNZSGI . You are receiving this because you were mentioned.Message ID: @.***>

ppenzin commented 2 weeks ago

Hm, I have the same model. Balena did verify that the image got written correctly, though maybe yes, I should try another one to be safe.

Haui1112 commented 2 weeks ago

@Haui1112, to answer your question in #1 (comment), dd with default settings takes a very long time to finish (FreeBSD version does on my machine, anyway), but I'll take another at that.

Also for unminimize (#1 (comment)), it might be possible to try it out on one of the live images, as you can just eject the card and re-burn it.

I have in fact tried using balena for making the card and it crashed with the upgradecard image. not sure if related. have you tried doing dd with stock arguments?

ppenzin commented 1 week ago

Stock arguments make dd very slow, at least on FreeBSD. pv is a pretty good alternative, but it needs to run from a root shell.