In my ongoing attemps to figure out why after the last dist-upgrade nothing from inside goes out unless the firewall is disabled, I have set up another SD card with debian 12, while it was still in testing. Not an upgrade from 11 which is what stopped working in the main FreedomBox.
The apu1d4 is, per lshw, capable of 1600MHz (2 cores). Qemu runs on a 2.3GHz computer, 2 cpus, 4 x 2 cores. To simulate the apu1d4, qemu was started like this: sudo qemu-system-x86_64 -drive file=/dev/sdf,media=disk -m 4G -smp 2 -nic user,hostfwd=tcp::10080-:443 I can access the web interface by pointing the browser to https://127.0.0.1:10080 I would have thought that this would be a pretty similar set up, with the additional cpu power compensating for the emulator overhead, but the FreedomBox image, that was at 22.12, has been "updating" for 10 days now. I can also not login at the "Freedombox login:". Not only does it claim incorrect user name or password, the qemu window steals the cursor rendering the whole computer inaccessible via mouse until I type CTRL + ALT + G (lower case ok), as I found here: https://unix.stackexchange.com/questions/107633/how-do-i-get-my-mouse-back-from-qemu-kvm I know the ueer name and password are correct. I have tried to "change" it using the same one and it succeeded, but it gave some LDAP error. This is a brand new FreedomBox image, downloaded while it was still in testing and the only configuration done to it is the admin user, as required by the first boot setup. Then it was upgraded a few times, until version 22.12. I might stop it or let it run a little longer, but for how long? Would another day or two let it finish the upgrade? or will it require another 10? 20? Very strange... When I finally pulled the plug on the original FreedomBox/apu1d4, the rest of the upgrade completed in minutes via aptitude. _______________________________________________ Freedombox-discuss mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss
