I tried the archlinux-gui-gnome-pure-2022.07-x86_64, going to try...
A Fast, Offline, Graphical Installer for Arch Linux
Brought to you by:
demonkiller
Menu
▾
▴
I had the following problems with this one and Carli 12
some reason it not liking my older 3D card is an Nvidia Geforce RTX 2080 that is the one having a black screen problem with some versions of or ports of ARch Linux like this one. Gigabyte G1.Assassin 2 (rev. 1.0) Intel® X79 Chipset motherboard hardware which runs manjaro & Garude fine. Carili 12 is running fine on Virtualbox on new pc. also note with this pc to my monitor I am using the displayport connect cable, and not the htmi 1 or htmi 2 on monitor, which is gigabyte M28U 4k monitor with HDR features. which works fine running manjaro builds and garuda builds and some acolinuxb desktop builds also seem to work fine, but I have not tried any of the older Carli yet, so I don't know if they have the display output problem where it seems to lose the connection to the monitor right when the desktop part loads again its not effecting all the linux arch ports just some of them from the iso I tried so far. . ok on bootup there a message that acolinuxb has about EDAC Sbridge Channel 0 memmory has DIMMs, but ECC is disabled is goes past this message is not in manjaro or garude I think only shows up on some ports of arch linux like this one I don't recall garuda or manjaro bootloaders from rufus to USB drive, I don't recall there versions of grub making a beeping sound. and archlinux-gui-gnome-pure had a bunch of messages errors about EDAC Sbridge in its arch linux kernal that are not in the working distro ports at all, so I think its a missing drivers for intel hardware which is my guess about it. I changed some settings in the bios which will allow it to boot MBR mode on older pc instead of UEFI and GPT mode, but I am not sure even if it boots mbr mode from the USB drive, I don't know if that will fix the display screen going black and losing the connection which only seems to happen with a few ports of arch linux. well that didn't work on bootup it still got a black screen on mbr mode instead of gpt mode during bootup of this linux version also it got CPU hcp handler not found type message during bootup of mbr mode which I didn't noticed when booting the UEFI GPT mode of grub 2. www.gigabyte.com/Motherboard/G1Assassin-2-rev-10/support#support-dl-driver this is what's in my older gigabyte system, on my newer pc which I have not tried to boot this I have an Z690 AORUS Master gigabyte motherboard , I have an Nvidia Geforce RTX 3070 card, gigabyte master brand, Intel Core i9 12900k, it runs fine on the new pc under Virtualbox, if I can't get this one to work yet on older hardware not under virtualbox but running it on the above older gigabyte system. I been able to run Calam-Arch-Installer-2023-04, garudaGNOME- 230319, manjaro-gnome-22.0.5-230316-linux61, and arcolinuxb-gnome-v23.03.01-x86_64 with no issues but for whatever reason carli-2023.04.05-x86_64, is getting a black screen when ran on the G1.Assassin 2 (rev. 1.0) Intel® X79 Chipset hardware, the nvidia 3D in that pc is Nvidia Geforce RTX 2080 that is the one having a black screen problem with some versions of or ports of ARch Linux during the bootup on the linux kernal into some of the desktops other than kde and gnome.
https://bbs.archlinux.org/viewtopic.php?id=272551 not sure if it helps but that new bing thing wrote this when I searched EDAC Sbridge Channel 0 memmory has DIMMs, but ECC is disabled arch linux on bing.com website.
Hello, this is Bing. I searched for your query and found some possible solutions.
According to one source1, the error message EDAC sbridge: ECC is disabled. Aborting is benign and can be ignored if it occurs only once. However, if it is being reported frequently on the same card, you may need to reboot the card or replace the module where the error is being reported.
Another source2 suggests that you can disable the EDAC module by creating a file /etc/modprobe.d/edac-blacklist.conf with this content:
blacklist i82975x_edac
blacklist amd64_edac_mod
blacklist skx_edac
blacklist e752x_edac
blacklist i5400_edac
blacklist i3200_edac
blacklist i5000_edac
blacklist ie31200_edac
blacklist edac_mce_amd
blacklist i3000_edac
blacklist sb_edac
blacklist pnd2_edac
blacklist i7core_edac
blacklist i7300_edac
blacklist x38_edac
blacklist i5100_edac
After rebooting, the message should not appear again.
A third source3 states that the symptom is benign but does not provide a solution.
A fourth source4 advises to check /sys/devices/system/edac/mc/mc* for more information about which row or DIMM might be faulty.
I hope this helps.😊
I was able to run and install archlinux-gui-gnome-2022.07-x86_64 with nvidia bootup from grub option but pure gnome version was not get into the desktop, so whatever in that version didn't work or the lack of stuff missing from it provented it from runnning on Gigabyte G1.Assassin 2 (rev. 1.0) Intel® X79 Chipset motherboard hardware with my Nvidia Geforce RTX 2080 3D card.
it gets some luks erros about Hibernation error text before it starts the gnome desktop using the installer I tried the encyption option from archlinux-gui-gnome-2022.07-x86_64 build, in any case if I don't use the encrption option under hard drive would fix this or a build 2023 build might help if and when this project gets updates I hope.
also had to look up how to unlock database error in arch linux on hard drive install packman -
I had to use sudo rm /var/lib/pacman/db.lck
then pacman -Syu
this happened on my install of archlinux-gui-gnome-2022.07-x86_64 from hard drive install of it which I had used its installer on iso image which I used rufus to install to drive, but when I had installed it with encyptioning the hard drive option with luks it seems to of cause problems or the problem exists in the iso images , I have not tried the plasma one yet so I don't own if it only exists in the gnome version, its a great idea but these have not been updated to the current builds of 2023 of arch linux files yet. so while I can use the 2022 builds isos they might have bugs in them that need updating. like this one.
https://laptrinhx.com/how-to-fix-unable-to-lock-database-error-in-arch-linux-1657946524/#:~:text=%24%20sudo%20rm%20%2Fvar%2Flib%2Fpacman%2Fdb.lck%20Voila%21%20It%20worked.%20I,and%20remove%20without%20any%20problems.%20%24%20pacman%20-Syu
can you come over to the discord server. would be able to help you there better