I was just trying to boot it up on bare metal yesterday, on an AMD Phenom II machine but Kernel Panic’d on not finding a device to boot from, which was a bit puzzling. Unfortunately had no time to investigate, but I won’t give up, I make it boot somehow on that PC.
There’s nothing like that is enabled AFAIK, I"m not even sure this board has UEFI (only Legacy BIOS). It’s an Acer Veriton M421G brand PC, with a Phenom II X4 945 CPU.
Not even sure it’s compatible with the OS, but this boot device issue was strange, tho. (had the same problem booting up a partition manager software from floppy that is based on Visopsys)
But will double check everything. Thanks for the tip!
I dd-ed the image straight to the HDD. grub started and booted off from it. lots of messages of PCI devices, I guess some kind of scan. after a while the screen went white, and a bit later the logs of the kernel panic appeared at the top, with the message it could’t find a device to boot from.
so, it seems that the kernel itself didn’t see the hdd it just booted from - standard IDE PATA disk, 120GB. Used dd from a gparted live disc.
First, I resized the partition on the disk to the full, at the next try I left it, as-is.
Both times the same result; the BIOS boots into Serenity, white screen, then kernel panic, couldn’t find a device to boot from.
Thing is, there are 2 DVD drives (IDE and SATA) and a floppy drive attached to the PC, dunno if they can cause any problem. And 1GB memory.
this was yesterday, and since then I haven’t got tieme to fiddle with it, but will. :)
At the weekend I’ll have some time to fiddle with it.
I think I’ll try to boot Serenity first from USB, check if it wants to boot at all. Maybe I’ll got an Arduino to use as serial monitor to check the log.
Then move on to flashing the grub image to the HDD, again, with a different IDE drive. if thst doesn’t work, I’ll find a SATA HDD and flash that.
I really wanna see this OS boot on real hardware. Then take a good lookaround and develop or port something for it :)
you might want to maybe try a different distro image to verify, maybe a simple kernel with a net image or something.
This part actually makes me wonder… Do you think SerenityOS uses the Linux kernel? Because it does not, it’s its own completely separate thing. And the hardware support for anything other than the standard emulated machine is very iffy, so it doesn’t seem too surprising that it would get tripped up by something on an old computer.
If anything went wrong with its USB stack for example, the kernel would have no way to find the root filesystem that’s stored on a USB drive.
It would need to be edited a bit, but overall it should. The main issue I think are the selectors for the login fields on kbin. Might try to implement it when I get some more time
Not normal. Haven’t seen that one, yet either. Do you know how to redirect the output to a file and send that to me? (make sure to delete your login data before you do). If you don’t know, let me know and also tell me what operating system you’re using
I think it’s just a larger undertaking. Like mentioned in the last comments. People either need to address that as the main focus for some new major release and work on it. Or subdivide it and find people to work on the individual components to make it happen (gradually).
Also there is always the thing with hobby / free software projects. Sometimes people focus on functionality and features and not so much on asthetics and the first impression. I agree the welcome screen is somewhat important as it’s the first thing a new player sees. But I also like the developers to work on features which enhance the actual gameplay because I just see that screen for 10 seconds and it’s kind of a waste of time to improve it for someone like me. The current screen works alright. There are several dynamics affecting projects: “Perfect is the enemy of good” (don’t make it too complicated) but also sometimes a makeshift solution or something that works “okay” stays inplace indefinitely because “it works” and people concentrate on other stuff. That’s just how things work. It takes deliberate effort to work against those dynamics.
So I’d say the cause is, their focus is somewhere else.
Kakao (or whatever they’re called) were going after everyone involved, so Tachiyomi has been deprecated, one of the devs forked it and will continue development.
A long time Tachiyomi developer made the commits making branding changes to Mihon, so they might work together. But as they didn’t fork TachiyomiSY, its dev might continue work on it too.
I have read that the SY devs will now fork from mihon, and that they will develop both I think. No idea about the tachi dev. If that’s the case then I guess that that dev also worked on SY, or they talked or whatever. I’ll keep an eye on the commits and repo.
The devs just said fuckit afterwards, as you do when you get a lawsuit saying your about to be so far in debt because of your side project that your whole life will be turned up side down.
The big advantage for me is that lact runs as a (systemd) daemon. This is more convenient for me than having to autostart CoreCtrl.
A disadvantage of the daemon is that it can’t be packaged on flathub.
Enable and start the service (otherwise you won’t be able to change any settings): sudo systemctl enable --now lactd
You can now use the GUI to change settings and view information.
github.com
Top