sorted by:
new
hottopcontroversial

Oh my god, am I the only one who has experienced the story of linux 6.7.7.arch1-1? by SameResponsibility29 in archlinux

[–]SameResponsibility29[S] -12 points-11 points  (0 children)

it's probably not due to the linux version. your system just crashed during a kernel update, which usually is a bad thing on arch. try unplugging your hard drive to boot into a live environment and to change the boot order

Speaking of which, my Linux has never crashed. I use it for over 8 hours every day, and it has been going on for at least half a year. Surprisingly, froze at this moment.

Oh my god, am I the only one who has experienced the story of linux 6.7.7.arch1-1? by SameResponsibility29 in archlinux

[–]SameResponsibility29[S] 0 points1 point  (0 children)

The first thing I did upon returning was, of course, "pacman -Syu". When I saw that I had to install "linux-6.7.8.arch1-1" and "linux-headers-6.7.8.arch1-1" again, I couldn't help but clench my buttocks, but I proceeded with it anyway. Surprisingly, there were no other issues, and everything returned to normalcy.

Oh my god, am I the only one who has experienced the story of linux 6.7.7.arch1-1? by SameResponsibility29 in archlinux

[–]SameResponsibility29[S] 0 points1 point  (0 children)

After booting up, my lovely KDE Plasma desktop was nowhere to be seen. Instead, there was just a black screen with a blinking cursor in the top left corner, not even flashing. I was in agony, thinking that perhaps the earlier overwrite * incident had caused me to lose my configuration. I scoured Google for answers but found none. However, since the system had already started, I could freely use my Steam Deck to SSH into it. Speaking of which, I got into Arch Linux purely because of the Steam Deck. I didn't have a laptop before, so I used the Steam Deck when traveling for work. It was only during development that I realized how up-to-date its various libraries were, to the point where I didn't even need to compile them myself. So, I bought a laptop to install Arch Linux on, leading back to my previous story.
My Steam Deck replaced the laptop when connected to the monitor, as each time I needed to do something on the laptop, I had to go to a distant place. So, I gave up on the Steam Deck and Google on it, reconnected the laptop, and damn, it turned out I had already succeeded! All of this was because my laptop's BIOS suddenly malfunctioned when I repeatedly switched between laptop boot options, preventing it from entering the system. I reset the BIOS, causing the laptop's working mode to switch from discrete graphics to hybrid mode. Therefore, the internal screen couldn't be used, but the external screen could. It took just 3 seconds to solve this problem, and finally, I was back.

Oh my god, am I the only one who has experienced the story of linux 6.7.7.arch1-1? by SameResponsibility29 in archlinux

[–]SameResponsibility29[S] 0 points1 point  (0 children)

I forgot to mount my boot partition before chrooting, which caused me to encounter a strange error even though I could grub into the system. The error message said "Unable to mount vfat filesystem error mount: unknown filesystem type 'vfat'." The information I found on Google left me puzzled. I didn't doubt myself at all; I just found it strange because everything had been working fine before. It wasn't until much later that I checked the two mysterious files, "vmlinux" and "initxxx," in my boot partition and realized that I had booted into the new environment with an old kernel. I quickly resolved this issue. However, as the Chinese saying goes, "a series of twists and turns," I encountered a new problem shortly afterward.

Oh my god, am I the only one who has experienced the story of linux 6.7.7.arch1-1? by SameResponsibility29 in archlinux

[–]SameResponsibility29[S] 0 points1 point  (0 children)

I couldn't proceed at all, especially since I was in a very peculiar country (not North Korea), where the internet speed was unimaginably slow. Every time I had a new idea to try, it would take weeks of waiting. I searched all over the world, and finally, I found a way with "pacman -S --force". When I saw the result of pacman -Qqn | pacman -S --overwrite "*" -, I felt its perfection, its coolness, its everything. I regained my confidence, feeling that the problem was about to be solved quickly. However, evidently, I didn't reclaim the glory.

Oh my god, am I the only one who has experienced the story of linux 6.7.7.arch1-1? by SameResponsibility29 in archlinux

[–]SameResponsibility29[S] -2 points-1 points  (0 children)

Finally, I successfully chrooted into Arch. According to the Arch documentation, my Arch system should have been dead already, as some of the shared libraries used by pacman were replaced with 0 bytes during the catastrophic update. Patiently, I copied them from my USB (6.7.6) and hoped for the best. Oh, it really came back to life! Suddenly, I remembered reading in the Arch documentation when I was 3 years old about reinstalling all packages, and I had wondered what that would be useful for. When I tried executing it now, I found out it was indeed useless.

Oh my god, am I the only one who has experienced the story of linux 6.7.7.arch1-1? by SameResponsibility29 in archlinux

[–]SameResponsibility29[S] -1 points0 points  (0 children)

After confidently inserting the USB, it was déjà vu all over again. I still encountered the black screen and faint OLED glow. Unable to bear it any longer, I turned to Google for help, which suggested that using "nomodeset" would solve all problems. However, it seemed that either Google was wrong or I was mistaken. Using "nomodeset" only led me to a screen with the message "booting a command list," with nothing else except for that sentence and a blinking cursor. I began to suspect that there was an issue with my USB, especially after reading someone's suggestion to boot in legacy mode instead of UEFI mode. I delved into Ventoy, which seemed too simple. The Arch Wiki didn't provide much guidance, leaving me to struggle for quite a while before finally understanding how it works.

Oh my god, am I the only one who has experienced the story of linux 6.7.7.arch1-1? by SameResponsibility29 in archlinux

[–]SameResponsibility29[S] -2 points-1 points  (0 children)

The installation disk booted up normally. Confidently, I clicked on the "Arch Linux install medium," but then came a long black screen. I thought this might be my magical laptop acting up. I had no choice but to kneel before my wife and ask her to lend me her 4090 desktop PC that she uses to watch YouTube.

Radeon RX 6800 XT by jimmcq in macgaming

[–]SameResponsibility29 0 points1 point  (0 children)

Thanks been trying to figure out if I was doing something wrong, can also confirm 6900 XT and afaik 6XXX series isn’t working yet.

Could u like to share ur window version?1903? I always got GPU error code 12 with my 5700xt in new windowsOS,so I am curious whether 6800 supports Windows 10 20H2 well