Upgraded Endeavour OS

[Hedon James]

10 hours ago, raymac46 said:

Updated my Windows virtual machine where I installed Google Chrome from the AUR. After a reboot, I got a segfault when I tried to launch Chrome. Removed Chrome completely then reinstalled it from AUR. It works now. Nevertheless there is something funky about VBox and Windows and EndeavourOS. Lots of room for interactions, I would say.

since it didn't work, but then it did, I think you have to chalk that up to a "quirk".  That's "normal" behavior for most computers and OS, IMO.  With all that said, I'd suspect that something in the "AUR stack" was the likely culprit in that one:  the build script, or yay/pacaur or whatever you use to build AUR packages.  still interesting though, because it gives you a hard target to consider.

[raymac46]

(Moan) updated my Windows VBox copy of EndeavourOS and after a reboot got to "Reached Target Graphical Interface" and everything came to a halt - no GUI. 

So, another nuke and repave. This time, I am not using yay for anything or installing any packages from the AUR.

In the meantime, my copy of MX in VBox just chugs along.

[raymac46]

I updated my Linux version of EndeavourOS in VBox and got the same result. "Reached Target Graphical Interface" and then everything came to a halt.

In the meantime, I updated my on-the-rails installation of EndeavourOS on my junker Lenovo laptop - including rebuilding Google Chrome - and everything works just fine.

There is something toxic about EndeavourOS in VirtualBox and figuring out what's wrong is above my pay grade. I am just going to remove EndeavourOS from my suitable list of VBox guest candidates.

 

[Hedon James]

4 hours ago, raymac46 said:

I updated my Linux version of EndeavourOS in VBox and got the same result. "Reached Target Graphical Interface" and then everything came to a halt.

In the meantime, I updated my on-the-rails installation of EndeavourOS on my junker Lenovo laptop - including rebuilding Google Chrome - and everything works just fine.

There is something toxic about EndeavourOS in VirtualBox and figuring out what's wrong is above my pay grade. I am just going to remove EndeavourOS from my suitable list of VBox guest candidates.

 

Good news....you proved it's not a host issue.  And given that MX chugs along, I think it's safe to say it isn't a VBox issue, but an Arch issue in VBox.  I'd be looking at SBs post about the additional steps for an Arch VM and see if any of them apply to you.

 

That error message is helpful.  I was thinking the desktop manager (LightDM vs SDDM vs ???), but a quick google suggests this is likely a driver issue.  Nvidia issues come up a LOT.  Not sure that applies to a VM though.  Can you boot with a PRIOR kernel, rather than updated kernel?  All indications are that your system isn't hosed, just that GUI won't boot.

 

https://forum.endeavouros.com/t/system-wont-boot-stuck-at-reached-target-graphical-interface/30620/7

 

And here's a resolved issue...they reference VMWare, but I can't tell if they were running a VM or bare metal?  Driver issue:

https://forum.endeavouros.com/t/booting-reached-target-graphical-interface-then-continue-blinking/45438/46

 

Here's a resolution with Arch Linux...outdated mirror installed older package.  This dovetails nicely with your observation/theory of corrupted packages.  Boot to terminal, sync your mirrors, and run the update again, see if it resolves itself:

https://bbs.archlinux.org/viewtopic.php?id=287617

[raymac46]

Useful links but I don't think I see an exact parallel here. The video driver issue is the likely cause but I am using the VBox drivers, not Nvidia or AMD as the case may be. I was unable even to get a TTY with the system. I could boot to >grub but that didn't do much for me. Using the fallback image gave me the same error.

This has to be an EndeavourOS-VBox issue because the normal installed Endeavour works great and has for months.

If you have some spare time, I'd be interested to see how you get on with VMM and EndeavourOS.

[Hedon James]

I can do that.  Bumping up on some hard deadlines right now, but I'll try to get an Endeavour VM setup in VMM.  I've been curious to check it out anyhow.  And if it corrupts as quickly as yours does, it will be a short courtship.  LOL!

 

[Hedon James]

12 hours ago, raymac46 said:

Useful links but I don't think I see an exact parallel here. The video driver issue is the likely cause but I am using the VBox drivers, not Nvidia or AMD as the case may be. I was unable even to get a TTY with the system. I could boot to >grub but that didn't do much for me. Using the fallback image gave me the same error.

This has to be an EndeavourOS-VBox issue because the normal installed Endeavour works great and has for months.

If you have some spare time, I'd be interested to see how you get on with VMM and EndeavourOS.

I agree...no exact parallel.  But generalized parallel is a video driver issue, caused by outdated mirror that corrupts pacman package installations...partial installs, or breaking installations because certain dependencies aren't updated with package.

 

I've got Endeavour downloaded and note recommended install on EFI, despite legacy support.  How did you install?  If I'm testing VMM vs VBox, I'd like my install to mirror yours. 

 

And you installed Chrome from AUR correct?  Been awhile since I messed with AUR on my VMs and I've never used yay.  What's the command line for an AUR install?  I'm guessing "sudo yay -S chrome".  Please confirm or correct me, and I'll get VMM setup like yours.  TIA!

[securitybreach]

3 minutes ago, Hedon James said:

And you installed Chrome from AUR correct?  Been awhile since I messed with AUR on my VMs and I've never used yay.  What's the command line for an AUR install?  I'm guessing "sudo yay -S chrome".  Please confirm or correct me, and I'll get VMM setup like yours.  TIA!

 

Same syntax as pacman but you never want to use sudo to build a package. Just yay -S packagename, it will prompt for creds when it's done building.

[securitybreach]

Personally, I prefer paru but I do keep the aur packages to a minimum as these are not official packages.

[Hedon James]

1 minute ago, securitybreach said:

Personally, I prefer paru but I do keep the aur packages to a minimum as these are not official packages.

yay is preinstalled on Endeavour, and that's what Ray used, so I'll mirror what he did.  Last time I used an AUR package, I think i used pacaur; or maybe the one before pacaur...can't remember the name.

[raymac46]

I just followed the defaults in VBox to install the VM. I don't think I specifically mentioned EFI so maybe I got a legacy install. Not sure.

You use yay as user, not root

$ yay -S google-chrome

you'll get a request for your sudo password as needed.

You can also just type yay as user for a system update; no need for yay -Syu or pacman -Syu although those work too.

I have not tried using reflector or the Reflector GUI in Endeavour after an install lately. Just used the default mirrorlist. The only time I tried changing the mirrorlist was when pacman / yay got subsequently broken.

[raymac46]

Now that I am thinking about it, I don't recall the installer setting up a boot/EFI partition so I likely had a legacy install.

[Hedon James]

Okay....Endeavour with LXQT DE installed in VMM with legacy/MBR configuration.

 

Before I do anything that potentially corrupts the system, here is my Mirror list for pacman:
 

################################################################################
################# Arch Linux mirrorlist generated by Reflector #################
################################################################################
# With:       reflector --verbose -c US --protocol https --sort age --latest 20 --download-timeout 5
# When:       2024-11-15 20:37:50 UTC
# From:       https://archlinux.org/mirrors/status/json/
# Retrieved:  2024-11-15 20:37:36 UTC
# Last Check: 2024-11-15 20:18:32 UTC

## United States
Server = https://america.mirror.pkgbuild.com/$repo/os/$arch

## United States
Server = https://us.arch.niranjan.co/$repo/os/$arch

## United States
Server = https://arch.mirror.constant.com/$repo/os/$arch

## United States
Server = https://arlm.tyzoid.com/$repo/os/$arch

## United States
Server = https://mirrors.lug.mtu.edu/archlinux/$repo/os/$arch

## United States
Server = https://plug-mirror.rcac.purdue.edu/archlinux/$repo/os/$arch

## United States
Server = https://mirrors.vectair.net/archlinux/$repo/os/$arch

## United States
Server = https://m.lqy.me/arch/$repo/os/$arch

## United States
Server = https://us-mnz.soulharsh007.dev/archlinux/$repo/os/$arch

## United States
Server = https://iad.mirrors.misaka.one/archlinux/$repo/os/$arch

## United States
Server = https://mirror.hasphetica.win/archlinux/$repo/os/$arch

## United States
Server = https://archmirror1.octyl.net/$repo/os/$arch

## United States
Server = https://repo.ialab.dsu.edu/archlinux/$repo/os/$arch

## United States
Server = https://arch.goober.cloud/$repo/os/$arch

## United States
Server = https://mirror.arizona.edu/archlinux/$repo/os/$arch

## United States
Server = https://mirror.zackmyers.io/archlinux/$repo/os/$arch

## United States
Server = https://archlinux.doridian.net/$repo/os/$arch

## United States
Server = https://arch.mirror.k0.ae/$repo/os/$arch

## United States
Server = https://mirrors.ocf.berkeley.edu/archlinux/$repo/os/$arch

## United States
Server = https://codingflyboy.mm.fcix.net/archlinux/$repo/os/$arch

 

Updating the Endeavour mirrors indicated some potential issues, but updated.  For future reference:
 

==> eos-rankmirrors: info: fetching https://gitlab.com/endeavouros-filemirror/PKGBUILDS/-/raw/master/endeavouros-mirrorlist/endeavouros-mirrorlist ...
==> eos-rankmirrors: info: ranking EndeavourOS mirrors, please wait ...
==> Warning about https://endeavouros.ip-connect.info/repo/$repo/$arch:
    Update level is 2244/2262, problem with the mirror?
    Continuing.
==> Warning about https://mirror.albony.xyz/endeavouros/repo/$repo/$arch:
    Connection to this mirror failed (code 60).
    Continuing.
==> Warning about https://mirrors.urbanwave.co.za/endeavouros/repo/$repo/$arch:
    Update level is 2258/2262, some [endeavouros] packages may be outdated if this mirror is in use.                
    Continuing.
==> Info: Results of ranking EndeavourOS mirrors:
                                                          
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# EndeavourOS mirrorlist, ranked by eos-rankmirrors at 11/15/2024 03:41:16 PM.
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Server = https://mirrors.gigenet.com/endeavouros/repo/$repo/$arch
Server = https://mirror.rznet.fr/endeavouros/repo/$repo/$arch
Server = https://ftp.rz.tu-bs.de/pub/mirror/endeavouros/repo/$repo/$arch
Server = https://repo.c48.uk/endeavouros/repo/$repo/$arch
Server = https://mirror.moson.org/endeavouros/repo/$repo/$arch
Server = https://mirrors.c0urier.net/linux/endeavouros/repo/$repo/$arch
Server = https://fastmirror.pp.ua/endeavouros/repo/$repo/$arch
Server = https://ftp.belnet.be/mirror/endeavouros/repo/$repo/$arch
Server = https://md.mirrors.hacktegic.com/endeavouros/repo/$repo/$arch
Server = https://mirror.alpix.eu/endeavouros/repo/$repo/$arch
Server = https://www.miraa.jp/endeavouros/repo/$repo/$arch
Server = https://fosszone.csd.auth.gr/endeavouros/repo/$repo/$arch
Server = https://mirror.accum.se/mirror/endeavouros/repo/$repo/$arch
Server = https://mirror.funami.tech/endeavouros/repo/$repo/$arch
Server = https://mirror.archlinux.tw/EndeavourOS/repo/$repo/$arch
Server = https://mirror.jingk.ai/endeavouros/repo/$repo/$arch
Server = https://mirrors.nxtgen.com/endeavouros-mirror/repo/$repo/$arch
Server = https://mirror.freedif.org/EndeavourOS/repo/$repo/$arch
Server = https://mirrors.tuna.tsinghua.edu.cn/endeavouros/repo/$repo/$arch
Server = https://mirror.sjtu.edu.cn/endeavouros/repo/$repo/$arch
Server = https://mirrors.jlu.edu.cn/endeavouros/repo/$repo/$arch
Server = https://mirrors.urbanwave.co.za/endeavouros/repo/$repo/$arch

#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Mirror ranking info at (UTC) 11/15/2024 08:41:16 PM:
# The following fields are shown for each mirror:
#   mirror:          The mirror address
#   update-level:    Ordinal number of the latest update (larger is newer)
#   fetch-time:      Measures the speed of the mirror (smaller is faster)
#
# mirror                                                             update-level  fetch-time
# ~~~~~~                                                             ~~~~~~~~~~~~  ~~~~~~~~~~
# https://mirrors.gigenet.com/endeavouros/repo/$repo/$arch           2262          0.218039
# https://mirror.rznet.fr/endeavouros/repo/$repo/$arch               2262          0.360150
# https://ftp.rz.tu-bs.de/pub/mirror/endeavouros/repo/$repo/$arch    2262          0.393205
# https://repo.c48.uk/endeavouros/repo/$repo/$arch                   2262          0.394227
# https://mirror.moson.org/endeavouros/repo/$repo/$arch              2262          0.397792
# https://mirrors.c0urier.net/linux/endeavouros/repo/$repo/$arch     2262          0.424712
# https://fastmirror.pp.ua/endeavouros/repo/$repo/$arch              2262          0.469356
# https://ftp.belnet.be/mirror/endeavouros/repo/$repo/$arch          2262          0.471443
# https://md.mirrors.hacktegic.com/endeavouros/repo/$repo/$arch      2262          0.492163
# https://mirror.alpix.eu/endeavouros/repo/$repo/$arch               2262          0.546549
# https://www.miraa.jp/endeavouros/repo/$repo/$arch                  2262          0.619345
# https://fosszone.csd.auth.gr/endeavouros/repo/$repo/$arch          2262          0.625912
# https://mirror.accum.se/mirror/endeavouros/repo/$repo/$arch        2262          0.715977
# https://mirror.funami.tech/endeavouros/repo/$repo/$arch            2262          0.769213
# https://mirror.archlinux.tw/EndeavourOS/repo/$repo/$arch           2262          0.818110
# https://mirror.jingk.ai/endeavouros/repo/$repo/$arch               2262          0.911733
# https://mirrors.nxtgen.com/endeavouros-mirror/repo/$repo/$arch     2262          0.956845
# https://mirror.freedif.org/EndeavourOS/repo/$repo/$arch            2262          1.180108
# https://mirrors.tuna.tsinghua.edu.cn/endeavouros/repo/$repo/$arch  2262          1.347543
# https://mirror.sjtu.edu.cn/endeavouros/repo/$repo/$arch            2262          3.246184
# https://mirrors.jlu.edu.cn/endeavouros/repo/$repo/$arch            2262          4.330499
# https://mirrors.urbanwave.co.za/endeavouros/repo/$repo/$arch       2258          1.077839
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

==> Moving old EndeavourOS mirrorlist to /etc/pacman.d/endeavouros-mirrorlist.bak.
==> Writing new ranked EndeavourOS mirrorlist to /etc/pacman.d/endeavouros-mirrorlist.

 

With the base system installed and mirrors setup, I'll update the system and see what happens.  My installation media was 9.24.2004, but I chose the "online installation" for the LXQt desktop, so may already be up to date.  I want to go through ONE update cycle without any issues, then I'll install Chrome from AUR...introduce 1 variable at a time.  Assume all is good until you see me report that it is not, LOL!

 

When/if that happens, we'll compare notes and look for a common cause.  I REALLY, REALLY think you have mirror/repo issue with pacman, and a partial/failed upgrade.  I'd be look at your mirrors for your VBox VM and compare with your metal installation.  I'm sure my mirrors are different than yours, being in USA, but that's part of the trial process, IMO.  Here we go now...

[Hedon James]

As expected, sudo pacman -Syyu indicates all packages are up to date, with nothing to do.  I'll try again in a work or so, just to catch SOMETHING to update, and then I'll reboot and see if the GUI failed.

 

If it does NOT, I'll install Google Chrome from AUR and wait a little to update system, and reboot system again....same as before...and look for GUI failure.  After that, I'll just keep trying to update and keep you informed.

 

Side note:  I chose the LXQt desktop, but I'm seeing a LOT of Gnome elements/theme in the DE.  Seems "dis-jointed" to me.  But it's a VM, and looks don't matter.  As long as it works, we're good right?  Ray chose LXQt, so I did the same.  Stay tuned...

[raymac46]

So far you have done everything that I did almost word for word.

[securitybreach]

All of the times that I had Endeavor on a machine. I only used arch repos and never endeavor's repos except for one for the themes.

[Hedon James]

36 minutes ago, securitybreach said:

All of the times that I had Endeavor on a machine. I only used arch repos and never endeavor's repos except for one for the themes.

I have installed NOTHING.  Endeavour repos are part of default installation.

[securitybreach]

19 minutes ago, Hedon James said:

I have installed NOTHING.  Endeavour repos are part of default installation.

 

That must be something new then as that wasn't the case in previous versions.

 

[raymac46]

The Endeavour repos are themes and wallpaper stuff. Nothing too fancy. I did install an LXQt wallpaper. Have not installed Chrome as yet. I'm using Firefox in the VM to post this.

[raymac46]

I have followed HJ in ranking the mirrors with reflector and also performed eos-rankmirrors. I was able to reboot without problems. Can't update because nothing to do. So far so good. This is on a Windows host.

[securitybreach]

I doubt it has anything to do with this but I did just read that EndeavorOS uses "dracut instead of mkinitcpio" when building the kernel/modules.

[raymac46]

Dracut seems to work OK in the on-the-rails installation of EndeavourOS and has been stable enough. The glitches I have had in VBox don't seem to be initramfs related. But never say never....

[Hedon James]

had some updates this morning....nothing major, just some lib* packages, but I took 'em and re-booted, with no issues.  Back in Endeavour, I installed google-chrome from AUR with 'yay -S google-chrome' and verified it was working as expected....it was.  Re-booted again and successfully logged back into Endeavour.  Google Chrome still working as expected, and 'sudo pacman -Syyu' indicates there's nothing to do.  Google Chrome was version 131.

[jim@EndeavourVM ~]$ sudo pacman -Q google-chrome
[sudo] password for jim:
google-chrome 131.0.6778.69-1

 

I think a baseline has been established for a working system, with updates and AUR packages.  Here's the baseline OS and kernel info:

[jim@EndeavourVM ~]$ lsb_release -a
LSB Version:    n/a
Distributor ID: EndeavourOS
Description:    EndeavourOS Linux
Release:        rolling
Codename:       rolling
[jim@EndeavourVM ~]$ uname -a
Linux EndeavourVM 6.6.61-1-lts #1 SMP PREEMPT_DYNAMIC Thu, 14 Nov 2024 14:13:22 +0000 x86_64 GNU/Linux

 

Nothing to do now, except sit and wait, and periodically check on updates and maybe even force some reboots when/if a new kernel shows up.  That seems to be when Ray experiences issues....a new kernel, with a corrupted driver/build of the vbox graphics driver (explaining difference between bare metal and VM installs), due to faulty/out-of-sync repo.  That's my working theory until dis-proven.

 

We'll know more when/if one of us diverges and starts experiencing issues.  I note that my kernel is a LTS kernel (selected at time of installation), so I might have to manually select a newer kernel at some point.  For now, that's okay, perhaps even informative if one of us is LTS kernel and the other is not.  Now we exercise patience, right?  LOL!

Edited November 16 by Hedon James

[raymac46]

I performed a minor upgrade and everything worked after a reboot. Then installed Google Chrome from AUR and it worked. Rebooted and everything was fine. Google Chrome worked. I do not have an LTS kernel. I did switch my video to SBoxSVGA as suggested.

Now we have two repair techs onsite and the faulty appliance is working perfectly. 

[Hedon James]

39 minutes ago, raymac46 said:

I performed a minor upgrade and everything worked after a reboot. Then installed Google Chrome from AUR and it worked. Rebooted and everything was fine. Google Chrome worked. I do not have an LTS kernel. I did switch my video to SBoxSVGA as suggested.

Now we have two repair techs onsite and the faulty appliance is working perfectly. 

 

LOL, that tracks!  Reminds me of my youth....junior high age.  I used to get a lot of sore throats.  Not "take a lozenge" to lubricate, but REALLY severe sore throats...where it hurt to swallow.  And frequently.  Doctor said "next time this happens, I think we should probably consider removing his tonsils."  My body heard that, and I didn't have a sore throat for YEARS after!  Never found out, definitively, what the cause was; but apparently, just the threat of removing the offending body part was enough to cure it?! 

 

And here we are...

 

EDIT:  let's not forget that VBox Guest Additions is proprietary, while VBox itself is open-source.  That is why video drivers in VBox used to require dkms for new kernels, while newer kernels in curated distros (Ubuntu, Debian, etc...) ship with virtual graphics drivers, which is why Live distros display correct.  Arch VMs tend to not scale to full resolution, in my observation, so maybe Arch kernels are still vanilla, and require dkms for VM graphics?  We keep dancing around that video driver as an issue in Arch VM, but waiting to pin down a "cause" to develop a solution.

Edited November 16 by Hedon James

[raymac46]

I remember when I studied total quality management there was something called the "spotlight effect" where a perceived problem got better just because everybody was paying attention to it.

When I was playing around with SDesk earlier on it would not scale in VBox. I assumed that was because virtualbox-guest-utils were not present.
Guest Additions are a very nice feature when they work, and there are fewer and fewer distros that require you to build the additions. However, you can't discount the fact that VBox introduces a layer of complexity that VMM does not. I still think I'll get screwed up before you do.

[crp]

if it is the GUI interface that is the only problem, maybe the issue is with the system graphics card?

[raymac46]

GUI problem is one of the issues. There is also an issue of pacman getting broken in the guest system.

The video issue has to be in the VM as I've had it on two different host systems. One system has a middle-aged Nvidia card and the other an antediluvian AMD card.

[Hedon James]

Here we go Ray....got some minor updates to be performed today, including updated packages for linux-lts-6.6.62-1 & linux-lts-headers-6.6.62-1, which look to me like incremental upgrades for the kernel.  gonna take the upgrades, reboot, and see what happens! 

 

interesting sidenote...Endeavour notification popup recommends a reboot due to upgrade of core packages...i don't ever remember seeing that in an Arch distro before, at least not in my Arch nor Manjaro VMs.

 

2nd interesting sidenote, I watched pacman build the kernel images for boot, including "backup" and I remembered selecting the "install LTS kernel, in addition to current kernel" checkbox at time of install.  I was curious what the "current" kernel installation was and wanted to manually select that in GRUB menu, but the ONLY kernel entries available for boot was the recently upgraded kernel and the "fallback" kernel, with no other identifying information.  Is this an Arch convention, or an Endeavour convention?  In Ubuntu & Debian worlds, I'm used to seeing a list of installed kernel options to choose from, in reverse chronological/numerical order, with newest at top and older at bottom; with numeric identifiers and ability to choose a specifically numbered/identified kernel.  I'm not a fan of the "generic" choices being the current or "fallback" with no identifying information as to WHICH kernel(s) they are.  Is it possible that I only have 2 kernels installed, the initial at time of installation and the updated kernel today?  And the list will grow as more kernels are added?  Will the identifying kernel information also expand as more kernels are added?

 

Rebooted Endeavour, using the freshly updated kernel and everything is fine.  Current Endeavour info as follows:

[jim@EndeavourVM ~]$ lsb_release -a
LSB Version:    n/a
Distributor ID: EndeavourOS
Description:    EndeavourOS Linux
Release:        rolling
Codename:       rolling
[jim@EndeavourVM ~]$ uname -a
Linux EndeavourVM 6.6.62-1-lts #1 SMP PREEMPT_DYNAMIC Sun, 17 Nov 2024 16:35:16 +0000 x86_64 GNU/Linux

 

3rd sidenote....I REALLY like that display manager for the LXQT desktop, with it's glass/crystal appearance.  Very modern looking.  I'm wondering if that's LightDM, or SDDM that LXQt recommends...I've used both with LXQT, and I can't tell.  Cool default theme, and it matches the default Endeavour desktop wallpaper perfectly....it's like someone MEANT to do that!  LOL!

 

[raymac46]

My turn.. I had only some libs from the extra repo to upgrade. Rebooted and all is well.

 

[ray@ray-virtualbox ~]$ inxi -Fxz
System:
  Kernel: 6.11.8-arch1-2 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: LXQt v: 2.1.1 Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2
    serial: <superuser required>
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required>
    UEFI: innotek GmbH v: VirtualBox date: 12/01/2006
CPU:
  Info: dual core model: 11th Gen Intel Core i7-11700 bits: 64 type: MCP
    arch: Rocket Lake rev: 1 cache: L1: 160 KiB L2: 1024 KiB L3: 32 MiB
  Speed (MHz): avg: 2496 min/max: N/A cores: 1: 2496 2: 2496 bogomips: 9987
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter
    vendor: VMware driver: vboxvideo v: kernel bus-ID: 00:02.0
  Display: x11 server: X.Org v: 21.1.14 driver: X: loaded: modesetting
    gpu: vboxvideo resolution: 1920x974~60Hz
  API: EGL v: 1.5 drivers: swrast platforms: active: x11,surfaceless,device
    inactive: gbm,wayland
  API: OpenGL v: 4.5 vendor: mesa v: 24.2.7-arch1.1 glx-v: 1.4
    direct-render: yes renderer: llvmpipe (LLVM 18.1.8 256 bits)
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0
    v: kernel bus-ID: 00:05.0
  API: ALSA v: k6.11.8-arch1-2 status: kernel-api
  Server-1: PipeWire v: 1.2.6 status: active
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: c1a0
    bus-ID: 00:03.0
  IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge
    driver: piix4_smbus v: N/A port: N/A bus-ID: 00:07.0
Drives:
  Local Storage: total: 20.15 GiB used: 8.41 GiB (41.7%)
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 20.15 GiB
Partition:
  ID-1: / size: 18.68 GiB used: 8.32 GiB (44.5%) fs: ext4 dev: /dev/sda2
Swap:
  Alert: No swap data was found.
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon
    or lm-sensors.
Info:
  Memory: total: 6 GiB available: 5.67 GiB used: 1003.2 MiB (17.3%)
  Processes: 168 Uptime: 4m Init: systemd
  Packages: 870 Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.37 inxi: 3.3.36
[ray@ray-virtualbox ~]$ 

I'll have to wait until a kernel update I think.