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.
Yes and they implement EVERYTHING in house. In case you haven’t heard they also started implementing a browser engine from scratch ladybird.dev just for fun. It kinda took off and they even got some nice donations, just to keep it going and see where it leads.
The “founders” youtube channel is quit interesting. Especially the monthly update videos if you want to keep up to date with the latest developments. inv.tux.pizza/channel/UC3ts8coMP645hZw9JSD3pqQ
The browser was at first only available in serentyOS itself but lately is available as a stand alone program running on other OSs as well. It’s still pretty early days, I am exited to see where all this leads tho!
It’s a work in progress. Most sites won’t work but some do. Check out this latest development update video: inv.tux.pizza/watch?v=giq5iXJntgQ&t=911 That link leads directly to the “demo segment” where he opens some sites.
The main difference between this project and the ones you listed is that this project includes a Plex installation out of the box. The other projects require you to connect to a separate Plex instance.
Looks like they have no idea how to get their software working using Nix. The following blurb is absurd to most GUIX or Nix users:
NOTE: In most cases, end users should never compile fwupd from scratch; it’s a complicated project with dozens of dependencies (and as many configuration options) and there’s just too many things that can go wrong.
Users should just have fwupd installed and updated by their distro, managed and tested by the package maintainer. The distribution will have also done some testing with how fwupd interacts with other software on your system, for instance using GNOME Software.
I’m not sure I see the problem here? It does say most cases and I’d definitely consider Nix/GUIX users to be in the minority for this (on top of users who would even compile software themselves in the first place).
Also from what I experienced during my (not so long) time with NixOS, usually things in Nixpkgs were contributed there by community members who ported applications over to be compatible with Nix. Sure, it’s a nice extra thing when the application developer does so out the gate, but given how special Nix and GUIX’s environment is, the onus has never really been on the app dev.
I’m not pointing to a problem per se. I’m just saying that this dev dismissed the act of building this from scratch as impossible when it is not actually impossible. Honestly, I’m just trying to spread the word about Nix and GUIX because they make things that were previously considered impossible (like this) possible.
I see, that’s plenty fair enough, although I don’t think they meant it quite so literally (but rather as a method of lightening their support requests - I don’t have any fwupd capable hardware AFAIK however I get the feeling fwupd is pretty popular).
I find it really cool what Nix/Guix are doing and I give major props to their communities for what they’ve pulled off, for what its worth.
Either it doesn’t support my mobo, or my mobo doesn’t support firmware updates from inside the OS. I had to update my mobo manually yesterday. At least I now get a clean boot without any irq handler warnings.
I used it at work recently to update my work-provided HP Thunderbolt dock, and it resolved an issue where the external monitors would fail to activate after resuming from standby. I never got an update notification when I was using my Windows laptop so I was oblivious to it; it was only thanks to connecting it to my Linux laptop and fwupd, that I found out there was an update, which subsequently resolved the issue.
I love it when stuff like this happens and Linux saves the day. =) (and I get to show off to my Windows heathens colleagues.)
The container connects to the VPN and only the VPN, now you can route whatever docker containers you want through that container as a network. Now that one VPN connection can serve any container you want.
Basically think of it as a SDK for defining data deletion on a platform. Omitme handles all the annoying stuff like account storage, building a CLI/GUI & sessions.
The core of Omitme is Seleniumwire used to grab login session tokens for platforms & HTTPX for making requests with those session tokens. Then you simply define you data deletion “targets” and the API calls to delete such data.
github.com
Active