Even backing your important files up to a 20 dollar pile of DVD's is better than nothing. If for any reason you lose your files, you will have nobody to blame but yourself. Having all your important data in only one place when additional drives or free cloud storage for backups is either cheap or free is just begging to lose all your files. All the time, everyday thousands and thousands of them just quit working. You're first problem is that you're not very smart for not having your important files backed up. The only workaround people in bug reports seem to have is amdgpu.dc=0 (and fortunately I don't do much graphics-heavy work in linux, so I can just about live with that, irritating though it may be).Is there more than one internal drive on this build, if so, disconnect all secondary drives and see if it will boot.
Sadly, I don't have a displayport or DVI monitor to check whether linux has a problem detecting those as well. I'm totally baffled as to why this has come up now, given that everything was perfectly content before and I didn't change anything substantial. It's correctly identifying the monitor as well. my CPU continues to bottleneck the GPU as ever!). Windows is behaving itself fine I tried some panorama stitching, a spot of rendering and a bit of gaming to see if I could perceive or record any quality degradation and everything seems much as before speed/temp/framerate-wise (i.e. It is a bizarre bug, I grant you, although one that seems to occur frequently enough with the RX 470/480/570/580 cards to have several reports online. Last edited by ConfusedInConsett ( 12:12:06)Īmdgpu.dc=0 severely limits the functionality of your videocard, for a well supported card like RX 580 it should never be needed. I am unfortunately too stupid to understand what this means (beyond the basic "Der Computer ist kaputt") and my cursory googling so far has drawn something of a blank. īooting via the bootloader installed on the live USB gives a perfectly functional startup with no error messages, until it all goes blank part way through as described in the initial message. Last edited by ConfusedInConsett ( 16:43:50)Ġ.076952 : TSC_DEADLINE disabled due to Errata please update microcode to version: 0x22 (or later)ġ.028250 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)ġ.028351 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.6.8-arch1-1 #1ġ.028426 Hardware name: Gigabyte Technology Co., Ltd. I've not got a great deal to go on, sadly, so diagnosis isn't straightforward.
I know it's not exactly Arch related, but if anyone has any idea what is going on here, it'd be very gratefully received. Sorry I can't post the relevant log files, but since I can boot into exactly no linux right now, they're tricky to get at. After trying live CDs from various other linux distros with the same result, reflashing the bios, disconnecting all drives (and with my Windows boot still mocking me by working perfectly normally all the while), I admitted defeat and came here. Bafflingly, the same problem arose when I tried to boot from an Arch live USB intending to chroot in: boot hangs on a blank screen with no warning once again (and again, with a tiny puff of protest from the CPU cooler). "Display manager problems! Must have been an upgrade." But I couldn't change tty to get into the system, just that blank screen. went blank, with a little pulse of the CPU fan. I tried again in verbose, and it showed that everything was going fine, got as far as loading GDM and Network Manager (), then. Everything was happily coexisting (all booting in EFI mode, the civil war over system time resolved, hardware all happy in Arch, etc.) until today, when my attempt to boot into Arch was met with a blank screen. I'm currently dual-booting with Windows (distasteful, I know, but I need Excel and Adobe). I've been using Arch for a few years but this is my first foray into forums. Firstly, sorry if this is in the wrong place/wrong format/wrong plane of reality.