> If you now apply the remedy to the stick
> dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462
>then i expect it to be permanently booting in reasonable time.
> .. Please confirm.
Inserted thumb-drive(2) [Ubuntu-MATE jammy] into box and
-- start paste
guiverc@d960-ubu2:/de2900/ubuntu_mate_64$ sudo dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462
[sudo] password for guiverc:
16+0 records in
16+0 records out
16 bytes copied, 0.0107609 s, 1.5 kB/s
-- end paste
booted it on j3400
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
on boot (noting when at grub) it had reached maybe-ubiquity in ~3 mins using room clock (no seconds as digital). I made an error in typing SysRq-REO (intended REISUB) so as no sync.. ignoring this bot.
turned box back on & booted again; again at maybe-ubiquity in ~3 mins by room clock. Correctly used SysRq-REISUB to restart
another boot & again ~3 mins by room clock. SysRq-REISUO now
NOTE: I didn't wait for clock to change minute & press enter this time, thus the extra seconds (making 2+ mins ~3 mins) is just ME not starting hitting the timing at ~:01 secs or hitting ENTER just after minute changes.. Either way ~3 mins is NOT TEN minutes as the slow boot takes to reach maybe-ubiquity.
> If you now apply the remedy to the stick
> dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462
>then i expect it to be permanently booting in reasonable time.
> .. Please confirm.
Inserted thumb-drive(2) [Ubuntu-MATE jammy] into box and
-- start paste d960-ubu2: /de2900/ ubuntu_ mate_64$ sudo dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462
guiverc@
[sudo] password for guiverc:
16+0 records in
16+0 records out
16 bytes copied, 0.0107609 s, 1.5 kB/s
-- end paste
booted it on j3400
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
on boot (noting when at grub) it had reached maybe-ubiquity in ~3 mins using room clock (no seconds as digital). I made an error in typing SysRq-REO (intended REISUB) so as no sync.. ignoring this bot.
turned box back on & booted again; again at maybe-ubiquity in ~3 mins by room clock. Correctly used SysRq-REISUB to restart
another boot & again ~3 mins by room clock. SysRq-REISUO now
NOTE: I didn't wait for clock to change minute & press enter this time, thus the extra seconds (making 2+ mins ~3 mins) is just ME not starting hitting the timing at ~:01 secs or hitting ENTER just after minute changes.. Either way ~3 mins is NOT TEN minutes as the slow boot takes to reach maybe-ubiquity.
This confirms what I believe you wanted.