IRC log of #maemo for Saturday, 2020-10-10

dos1I'm pretty late to the party, but Allegro 5 and SDL2 can work fine even on Fremantle, so I would expect them to work on Leste as well as long as they're compiled with GLES2 support and the GPU driver is there and operational00:10
*** Kilroo has joined #maemo01:42
*** florian has quit IRC03:00
*** drathir_tor has quit IRC03:02
*** sunshavi has quit IRC03:04
*** drathir_tor has joined #maemo03:09
*** Pali has quit IRC03:19
*** sunshavi has joined #maemo03:29
*** tm has quit IRC04:40
*** tm has joined #maemo04:43
*** sunshavi has quit IRC05:26
*** sunshavi has joined #maemo05:29
*** drathir_tor has quit IRC05:52
*** drathir_tor has joined #maemo05:54
*** DocScrutinizer05 has quit IRC07:31
*** DocScrutinizer05 has joined #maemo07:31
brolin_empeyLong story short, I have a 512-GB mSATA SSD with Debian GNU+Linux 10 (buster) with KDE 5 for x86-64 using MBR that boots and works on a Core 2 tower computer with this motherboard:07:40
brolin_empeyThis motherboard uses literal BIOS, not EFI.07:40
brolin_empeyI used HDClone 9 for Windows to clone the mSATA SSD onto a USB 3 SSD and allowed HDClone to change the disk signature and maybe something else that makes the cloned drive different from the original drive but that I thought should not matter for booting GNU+Linux.  When I try to boot the Core 2 tower computer from the USB SSD with the mSATA SSD disconnected, the boot process initially looks the same as when booting from the SATA drive but is much slower07:40
brolin_empeybecause the computer only has USB 2 connectivity so the USB SSD only uses High-speed, not SuperSpeed but then Debian stops booting with this ACPI error:07:40
brolin_empeyApparently the result is the same after I power-cycled the computer and tried booting again so it does not seem to be a problem only on the first boot of the cloned drive.  I have not yet searched the Internet about this message because I am still at work at 21:30 on Friday and I realise that this channel is not focused on Debian but does anyone have a suggestion of how to fix this problem?  Does it matter that the disk signature and maybe something else was07:40
brolin_empey changed when the drive was cloned?  The partitions and the volumes within them have been resized too because the USB drive is only 240 GB instead of 512 GB but I do not think that matters in this case considering how far the boot process gets before it stops.07:40
*** infobot has joined #maemo07:43
*** ChanServ sets mode: +v infobot07:43
Maxdamantusbrolin_empey: my guess would be that the ACPI error is probably not relevant to the problem.07:52
Maxdamantusbrolin_empey: it's booted to a busybox shell, so Debian simply isn't able to find the root filesystem.07:53
Maxdamantusbrolin_empey: probably because it's missing the relevant drivers (since you said you're trying to boot it from USB whereas it used to just boot from SATA)07:54
Maxdamantusbrolin_empey: I suspect Debian probably creates an initramfs containing the particular drivers needed to boot your system, so if you change the installation media, you'd probably need to regenerate the initramfs.07:55
brolin_empeyMaxdamantus: Thank you for the quick reply but how do I regenerate the initramfs?08:05
*** pagurus has joined #maemo09:37
*** Kilroo has quit IRC09:42
*** sunshavi has quit IRC10:22
*** luke-jr has quit IRC10:22
*** luke-jr has joined #maemo10:23
*** xmn has quit IRC11:05
*** dreamer has quit IRC11:07
*** infobot has quit IRC11:24
*** Pali has joined #maemo11:33
*** florian has joined #maemo11:36
*** florian has quit IRC11:46
*** dingen has joined #maemo11:46
*** dingen is now known as dreamer11:46
Maxdamantusbrolin_empey: I've tended to just maintain my own kernel when using debian, but from Googling, I think it should work if you're able to get it to boot manually from the USB and then run `update-initramfs` from the running system.12:06
Maxdamantusbrolin_empey: I would probably try getting into the initramfs of a live USB system, then instead of letting it continue to boot into the live USB, mount your own root filesystem instead (eg, something like `mount -o ro /dev/sdb1 /mnt`), then boot into it using `exec chroot /mnt /sbin/init`12:08
MaxdamantusSince the live USB initramfs will very likely have all the relevant drivers (particularly: usb, usb-storage and a module for whatever filesystem you're using)12:10
Maxdamantusbrolin_empey: seems that to boot to initramfs from the livecd, you go to "Help" at the boot menu, then use a boot command like `install init=/bin/sh`12:23
Maxdamantusbrolin_empey: then you should be able to run the commands I wrote above (you'll need to figure out what your actual root device is; my command assumes it's "/dev/sdb1")12:24
*** dogdjgift has joined #maemo12:30
*** dogdjgift has quit IRC13:13
*** niceplace has quit IRC15:54
*** florian has joined #maemo16:05
*** florian has quit IRC16:50
*** sunshavi has joined #maemo16:54
*** luke-jr has quit IRC17:06
*** luke-jr has joined #maemo17:06
*** ahjolinna has quit IRC17:49
*** ahjolinna has joined #maemo17:50
*** luke-jr has quit IRC18:00
*** luke-jr has joined #maemo18:01
*** florian has joined #maemo18:33
*** florian has quit IRC18:41
*** luke-jr has quit IRC19:18
*** luke-jr has joined #maemo19:19
*** Kilroo has joined #maemo19:24
*** florian has joined #maemo19:53
*** florian has quit IRC19:59
*** florian has joined #maemo20:45
*** florian has quit IRC20:52
*** florian has joined #maemo20:56
*** xmn has joined #maemo21:10
*** drathir_tor has quit IRC22:44
*** drathir_tor has joined #maemo22:47

Generated by 2.15.1 by Marius Gedminas - find it at!