On 12/03/2021 10.27, Carlos E. R. wrote:
On 12/03/2021 08.04, Takashi Iwai wrote:
On Fri, 12 Mar 2021 02:39:51 +0100, Linux Kamarada wrote:
On Thu, Mar 11, 2021 at 4:54 AM Takashi Iwai <tiwai@suse.de> wrote:
On Thu, 11 Mar 2021 03:54:46 +0100, Linux Kamarada wrote:
This message caught my attention:
DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000009d800000-0x000000009fffffff], contact BIOS vendor for fixes
I believe the problem is with the 15.3 kernel, because I'm able to boot with the 15.2 kernel.
Is this a known bug? Or should I report it as a new bug?
Not really, it's a harmless firmware bug that is seen commonly on many machines.
How did you update to Leap 15.3? On Leap 15.3, the kernel package was split to three sub-packages, kernel-default, kernel-default-extra and kernel-default-optional. (Ditto for kernel-preempt: kernel-preempt, kernel-preempt-extra and kernel-preempt-optional.) Some drivers are put in *-extra or *-optional, and one of them is nouveau driver. So, make sure that you have installed kernel-*-extra driver at least.
Actually, kernel-default-extra, kernel-default-optional, kernel-preempt-extra and kernel-preempt-optional were all already installed.
OK, then my first guess was wrong.
I thought about installing kernel-firmware, but then YaST told me that would uninstall kernel-firmware-all, so I canceled.
Right, kernel-firmware is the old style package containing the all files in uncompressed format in a single package, while Leap 15.3 follows the package split that is already done in Tumbleweed.
So it's a different problem. As suggested in the thread, please try to login there; even without graphics, the system might be able to boot further and we can get logs.
He posted an error message that indicates the filesystem is read only, but after "startx" runs :-?
Ah, in his first message he said:
And later, when I boot the 15.2 kernel, I realize nothing was written to /var/log/messages regarding the previous trial with the 15.3 kernel.
which would indicate it is read only since boot. Maybe "dmesg" might have something in RAM, and might be dumped to another partition or external disk. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)