Follow the discussion below and jump in with a reply if the topic is open.
Latest iso, instalation went smooth, first boot ok, initial setup ok. After first upgrade under terminal, Raku fails to start, its doing sth but never goes to login screen. I waited 4 hours, no luck. Tried all three DE.
My config B650 r7 7700 rx9070.
I really like Raku from the beginning but there seems to be some kind of error preventing system to start properly.
amdyss15 said:
Latest iso, instalation went smooth, first boot ok, initial setup ok. After first upgrade under terminal, Raku fails to start, its doing sth but never goes to login screen. I waited 4 hours, no luck. Tried all three DE.
My config B650 r7 7700 rx9070.
I really like Raku from the beginning but there seems to be some kind of error preventing system to start properly.
Can you provide any errors from boot log you can see.. when the spinner is spinning hit the ESC key to see the live bootlog. tell me what the errors are if any. TBH the system-upgrade script is bit of a relic from when I first started work on RakuOS and at that time it was purely a flatpak based Atomic distro. Didn't even have the software center at that time ,which now its the primary way to check for and upgrade the system image. I will though fix that terminal command for folks that perfer to use the terminal for system updates
Last updated
It stops on Job rakuos-overlay-sync.service/start running and stays for hours.
Previous line was started NetworkManager-dispacher manager scriptdispacher service but it was after two hours.
Also - [Failed] to start rakuos-flatpack-wat_ice Rakuos flatpack event watcher also [failed] to start dkms.service bui..ll new kernel modules through DKNS
Would be more convinient if I could paste a photo.
amdyss15 said:
It stops on Job rakuos-overlay-sync.service/start running and stays for hours.
Previous line was started NetworkManager-dispacher manager scriptdispacher service but it was after two hours.
Also - [Failed] to start rakuos-flatpack-wat_ice Rakuos flatpack event watcher
also [failed] to start dkms.service bui..ll new kernel modules through DKNS
Would be more convinient if I could paste a photo.
ah so you are on a laptop.. known issue if eithernet isn't plugged in. fix coming with iso refreshes soon as I get the iso builds working on gitlab. I meant to make the live installer not required to be online but forgot to include the default applications in the sqush filesystem by default .. its trying to install the default applications from the overlay packages.list
tohur said:
amdyss15 said:
It stops on Job rakuos-overlay-sync.service/start running and stays for hours.
Previous line was started NetworkManager-dispacher manager scriptdispacher service but it was after two hours.
Also - [Failed] to start rakuos-flatpack-wat_ice Rakuos flatpack event watcher
also [failed] to start dkms.service bui..ll new kernel modules through DKNS
Would be more convinient if I could paste a photo.
ah so you are on a laptop.. known issue if eithernet isn't plugged in. fix coming with iso refreshes soon as I get the iso builds working on gitlab. I meant to make the live installer not required to be online but forgot to include the default applications in the sqush filesystem by default .. its trying to install the default applications from the overlay packages.list
No....I have desktop PC with Wifi network adapter and Ethernet and cable is plugged in. I disabled Wifi during initial setup.
Try to boot to emgercy mode and then run either of these commands
rakuos reset-overlay --confirm Wipes overlay
rakuos reset-overlay --soft Soft reset
From a universialblue forum post
Booting to Emergency Mode Emergency mode provides the most minimal environment possible and allows you to repair your system even in situations when the system is unable to enter rescue mode. In emergency mode, the system mounts the root file system only for reading, does not attempt to mount any other local file systems, does not activate network interfaces, and only starts few essential services.
Press Esc on the keyboard to reach the GRUB boot menu. a. If you press Esc too many times, you may end up at a grub> prompt. b. Return to the boot menu by typing exit and pressing Enter Select the desired deployment (the top entry is generally correct) and edit by pressing E on the keyboard. Arrow down to the line starting with linux and press Ctrl+E to reach the end of the line. Add the word emergency to the end of the line. a. Ensure there is a space between emergency and the pre-existing text. b. Equivalent parameters -b and systemd.unit=emergency.target may be added instead of emergency. Press Ctrl+X to boot the system.
Booting to Rescue Mode Rescue mode provides a convenient single-user environment and allows you to repair your system in situations when it is unable to complete a normal booting process. In rescue mode, the system attempts to mount all local file systems and start some important system services, but it does not activate network interfaces or allow more users to be logged into the system at the same time. In Fedora, rescue mode is equivalent to single user mode.
Press Esc on the keyboard to reach the GRUB boot menu. a. If you press Esc too many times, you may end up at a grub> prompt. b. Return to the boot menu by typing exit and pressing Enter Select the desired deployment (the top entry is generally correct) and edit by pressing E on the keyboard. Arrow down to the line starting with linux and press Ctrl+E to reach the end of the line. Add the word single to the end of the line. a. Ensure there is a space between single and the pre-existing text. b. Equivalent parameters 1, s, S, and systemd.unit=rescue.target may be added instead of single. Press Ctrl+X to boot the system.
Last updated
amdyss15 said: Latest iso, instalation went smooth, first boot ok, initial setup ok. After first upgrade under >terminal, Raku fails to start, its doing sth but never goes to login screen. I waited 4 hours, no >luck. Tried all three DE.
My config B650 r7 7700 rx9070.
I really like Raku from the beginning but there seems to be some kind of error preventing >system to start properly.
I have been able to reproduce the issue on my own system .. fix will be coming down the pipe soon.. was a timing issue on searching for enabled services in the overlay such as libvirt etc and was just an endless loop. so if you had the gaming packages and/or VM setup installed that was the source of the loops because the gaming setup comes with Lact which has a service and then theres libvirt, which I use myself thus was able to reproduce it
Last updated
Ok can confirm this is fixed. will let people know this a two part update, first there is one last update coming from GHCR (Github) then that will transition everyone to our Gitlab repos for future system updates. I still need to do some work on the overlay-services starting on boot but I sperated it from the overlay-sync so its not an blocker any longer from reaching the desktop
Last updated
tohur said:
Ok can confirm this is fixed. will let people know this a two part update, first there is one last update coming from GHCR (Github) then that will transition everyone to our Gitlab repos for future system updates. I still need to do some work on the overlay-services starting on boot but I sperated it from the overlay-sync so its not an blocker any longer from reaching the desktop
Glad to hear that.