I have any -pae kernel version since 4.20 cause kernel panic at boot. Now I use 4.1.6-towo.1-siduction-686-pae, it works. My hardware: motherboard Asus M4A88TD-V Evo/USB3, CPU AMD Phenom II x4 955, GPU Radeon HD 7850 (driver radeon), RAM 8 MB
Please help :'(
ASUS M4A88T-V EVO/USB3 AM3 AMD 880G USB 3.0 HDMI ATX AMD Motherboard with a Phenom II - clearly a strict 32bit CPU. I guess you are doomed.
But wait, what about a OS that uses the capabilities of the hardware like the amd64 architecture?
Hello Cheluskin,
you use some oldfashioned kernel parameters:
[ 0.000000] Kernel command line: root=UUID=b908c0f2-aa2d-4810-91c7-8204f49e981c noagp vga=0x324 init=/lib/systemd/systemd rd.md=0 rd.dm=0 rd.luks=0 rd.lvm=0 rootflags=noatime splash
Why did you put "noagp vga=0x324" in your kernel commandline?
The vga=0x324 interferes with kernel mode setting (KMS) which is essential since kernel 2.6.30 from 2009.
But how should your kernel even communicate with your graphics card without its AGPGART?
In your screenshot you can see the result of the "noagp" parameter:
[ 1.929874] Linux agpgart interface v0.103
[ 1.929969] Failed to find cpu0 device node
greetings
musca
It could be (or related to) the following bug which has been fixed in kernel 4.3, though it seems strange that 4.1.x kernel worked for you:
https://bugzilla.kernel.org/show_bug.cgi?id=101971 (https://bugzilla.kernel.org/show_bug.cgi?id=101971)
Quote from: melmarkerBut wait, what about a OS that uses the capabilities of the hardware like the amd64 architecture?
What about it? Yes, amd64 would be optimal/ideal, but some users have their reasons for using 32-bit, and it should work.
Quote from: musca on 2015/10/07, 02:11:02
you use some oldfashioned kernel parameters
Hello, musca, thank for your replay.
Commandline parameters and 32 bit - this is a historic :)
Boot with only "root=UUID=b908c0f2-aa2d-4810-91c7-8204f49e981c init=/lib/systemd/systemd" leads to the same result.
Quote from: seasons on 2015/10/07, 07:02:30
It could be (or related to) the following bug which has been fixed in kernel 4.3, though it seems strange that 4.1.x kernel worked for you:
https://bugzilla.kernel.org/show_bug.cgi?id=101971 (https://bugzilla.kernel.org/show_bug.cgi?id=101971)
Thank you, seasons!
It's very similar. I will tolerate 8)
The problem was solved after upgrading to kernel 4.2.4-towo.2-siduction-686-pae.
Thank you.
Yes, the fix for the bug I linked to was pushed to Linux 4.2.4:
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.2.4