Fresh Install of Manjaro 20 Gnome Kernel Panic Solved



I really don't have experience in this area that you are trying to show me how to fix and I don't understand the instructions.

Thank you Wizard for trying to help me.:)

I plan to install Manjaro on my Sony Vaio.
That way the war on the bootloader is won because that machine only has one HDD.
 
I just performed a fresh installation of Manjaro 20 Gnome and I've got the dreeded:
Kernel panic - not syncing VFS: Unable to mount root fs.

I found a temporary fix by editing the kernel line by pressing 'e' at the grub menu and removing the intel-ucode.img and replacing it with /initrd /boot/initramfs-(manjaro's kernel image) -x86_64.img.

Anyone know how I can permanently fix this so I don't have to keep editing the kernel line?
A timely and very interesting thread whereas I am at this moment flashing Manjaro KDE 20.0 to an USB for installation on my 'test' box along side Linux Mint 19.3 and Ubuntu 20.04.
I think I recall @wizardfromoz mentioning before that Manjaro does not play nice with others boot loaders.
Glad I saw this before I started installing!

create a file called custom.cfg, in your /boot/grub beside grub.cfg on tricia GNOME

its only content is (substitute your own UUID from that screenshot, you can get it from gparted or blkid)

Code:
menuentry "Manjaro GNOME - configfile "  {
    insmod part_gpt
    part part_msdos
    insmod ext2
    search --no-floppy  --fs-uuid --set=root 58c5f278-e6b9-49cc-ab90-e100261da3c2
    configfile /boot/grub/grub.cfg
}

SAVE the file and reboot, you'll see the entry and it opens a new menu to manjaro

wiz
@wizardfromoz
When setting the UUID in that config file would that be the drive or partition UUID?
e.g. - sda or sda1 ?
 
It's really a shame that there's a boxing match over the bootlaoder.
Be nice if the devs or other contributors could fix that:-

I didn't know until Wizard said it's been going on for years.
 
It's really a shame that there's a boxing match over the bootlaoder.
Be nice if the devs or other contributors could fix that:-

I didn't know until Wizard said it's been going on for years.
Apparently it's a matter of "the Arch way or the highway"! o_O
 
Apparently it's a matter of "the Arch way or the highway"! o_O
Yup-

I had the same problem with LILO and Grub when I was running Slackware.
The only way I was able to solve it was install Slackware first than install Linux Mint and than Debian 10.
LILO didn't want to give up even after I removed it with elevated privileges.
Grub eventually took over 3 reboots later.
 
Apparently it's a matter of "the Arch way or the highway"! o_O

it seems that way, doesn't it? i find it a rather large fly in what is otherwise a very attractive ointment. i love the manjaroes, and arcolinux.

just uploading some pix and i'll be back

wiz
 
my grub menu is 2 and a bit screens long, so in screenshot i am showing the back page of it, on what was then my prime partition, held by Elementary OS (aka EOS).

where the highlighted line is, is the start of what is generated by my custom.cfg file


OhmLbhD.jpg


SCREENSHOT 1 - WIZARD'S ELEMENTARY GRUB - CUSTOMISED

mine has 2 arcolinux and 3 manjaro because i like calling those up quickly, but your custom.cfg need only have the one arch-based distro listed to achieve the desired outcome.

in the textual output for custom.cfg i provided alex the top line says GNOME, simply because that is what he is using, but i actually choose KDE, 2nd from the bottom, to get Screenshot 2.

vrai, the UUID you insert is that of your root partition / , eg /dev/sda1 , /dev/sdb2, whatever

you can get that from in gparted from right-clicking the partition entry, choosing information and copy and paste, or other partition editors as they require; or else at terminal with blkid - linux mint allows just blkid, debian and manjaro

sudo blkid

in my case, to shorten the output i focus on grepping the manjaroes, and i am writing from Debian Buster so

sudo blkid

Code:
chris@debian9dot8-MATE-SSD:~$ sudo blkid | grep -i mjro
[sudo] password for chris:
/dev/sda8: LABEL="MJRO-GNOME-HDD" UUID="e5a2cc40-0196-444a-bf0b-6c31480b53e0" TYPE="ext4" PARTUUID="b3b37ae9-5f4b-47c5-aba5-0c1cc982f3bc"
/dev/sdb4: LABEL="MJRO-Xfce-SSD" UUID="a27c129a-48b7-4158-8165-27756f6736cf" TYPE="ext4" PARTUUID="f00b23d8-4747-4dad-a158-257d2814c26b"
/dev/sdb5: LABEL="MJRO-KDE-SSD" UUID="04f35396-2f79-4d56-a1f0-312f6713d408" TYPE="ext4" PARTUUID="6ece6a86-ef94-4c90-aa5f-4b759f5fa5e3"
/dev/sdc5: LABEL="MJRO18.4-Xfce-WD" UUID="2802ee45-58d5-44f2-bf0f-7283b33e20bd" TYPE="ext4" PARTUUID="a805468a-020e-4926-a294-d2bd1230a4ed"
/dev/sdc10: LABEL="MJRO-Cinn-WD" UUID="394c75db-d300-4b79-b9b8-21e9997e884a" TYPE="ext4" PARTUUID="58c19e1c-399b-4234-9223-7cd540e5751f"
/dev/sdc20: LABEL="MJRO-Deepin-WD" UUID="f79ecc0a-ad43-40c0-9dac-c88d3ad12d3a" TYPE="ext4" PARTUUID="fd0adcaf-4216-400e-b2e7-c30006eda5ef"
/dev/sdc28: LABEL="MJRO-MATE-WD" UUID="58c5f278-e6b9-49cc-ab90-e100261da3c2" TYPE="ext4" PARTUUID="9ac02a25-311c-4837-b58b-5c0983703570"
chris@debian9dot8-MATE-SSD:~$

the highlighted uuid is for manjaro mate, but i put it in as gnome in the text before, as said.

with my root partitions, i label (not name) them with gparted after install, so mjro for manjaro &c. this then appears in my file manager and console output, makes for easier navigation.

so i chose KDE from the screen with the attractive lady you did not notice, and i get


fgJ1RDb.jpg


SCREENSHOT 2 - WIZARD'S CUSTOM.CFG PATH TO LAUNCH MANJARO

so custom.cfg provides a 2nd, full menu, not a submenu, with your chosen arch-based distro in primary spot, each distro has its own submenu for advanced options. this 2nd menu has its own timer countdown - i go with 10 secs but you can enter straight through. and this menu will launch any of my distros including the arcolinux and other manjaro

the 2nd menu is in the same order as the first except for that primary spot if your partitions for different drives housing linux are named the same in gparted. mine differ between /dev/sdbx and /dev/sdcx for reasons i can go into elsewhere some time.

i'll go a little further into building that custom.cfg next post, but rest my arm for now, and

... more coffee

wiz
 
Well, I installed Manjaro 20.0 KDE on my "test" box alongside Ubuntu 20.04 and Linux Mint 19.3 and did not encounter the dreaded 'kernel panic' :)
This machine I converted from BIOS MBR to UEFI GPT and created 7 partitions including the /boot/efi and /swap partitions.
During the installation of Manjaro I had to go back and forward with the installer several times to try and achieve the desired installation parameters. I was trying to keep the Grub boot-loader under the control of Mint but Manjaro was not very cooperative. The Manjaro installer insisted I mark or create a /boot/efi partition but I already had one so I pointed to that. Then I un-checked the box marked "boot".

Restarted the machine using the UEFI boot menu and booted into Linux Mint just fine. Ran sudo update-grub. Then restarted again and waited for the Grub menu - Manjaro had taken over but everything boots up just fine (so far). ¯\_(ツ)_/¯
 
Well, I installed Manjaro 20.0 KDE on my "test" box alongside Ubuntu 20.04 and Linux Mint 19.3 and did not encounter the dreaded 'kernel panic' :)
This machine I converted from BIOS MBR to UEFI GPT and created 7 partitions including the /boot/efi and /swap partitions.
During the installation of Manjaro I had to go back and forward with the installer several times to try and achieve the desired installation parameters. I was trying to keep the Grub boot-loader under the control of Mint but Manjaro was not very cooperative. The Manjaro installer insisted I mark or create a /boot/efi partition but I already had one so I pointed to that. Then I un-checked the box marked "boot".

Restarted the machine using the UEFI boot menu and booted into Linux Mint just fine. Ran sudo update-grub. Then restarted again and waited for the Grub menu - Manjaro had taken over but everything boots up just fine (so far). ¯\_(ツ)_/¯
Congrads on your fresh install.

Glad to hear you didn't have kernel panic.

Have a good weekend-:)
 
Well, I installed Manjaro 20.0 KDE on my "test" box alongside Ubuntu 20.04 and Linux Mint 19.3 and did not encounter the dreaded 'kernel panic' :)

vrai, that is because manjaro is on top in prime position, currently - that's right, isn't it? ubuntu and mint are below it.

that will endure while manjaro rules the roost, but it is a matter of time.

when certain updates are installed on ubuntu or linux mint, these could include but not be restricted to:
  • major update to grub or to
  • grub-efi-signed, grub-common
  • shim-signed
  • certain firmware updates
  • other, includes a reinstallation, sometimes a Timeshift restoration
... the subject distro, when rebooted, will once again assume primary position

that's when you get the kernel panic for manjaro.

that would be what happened with alex, which put mint xfce back on top (he can verify that or not)

cheers wiz

more light reading

https://linux.org/threads/manjaro-kernel-panics-and-other-tips-for-arch-based-distros.19795/
 
vrai, that is because manjaro is on top in prime position, currently - that's right, isn't it? ubuntu and mint are below it.

that will endure while manjaro rules the roost, but it is a matter of time.

when certain updates are installed on ubuntu or linux mint, these could include but not be restricted to:
  • major update to grub or to
  • grub-efi-signed, grub-common
  • shim-signed
  • certain firmware updates
  • other, includes a reinstallation, sometimes a Timeshift restoration
... the subject distro, when rebooted, will once again assume primary position

that's when you get the kernel panic for manjaro.

that would be what happened with alex, which put mint xfce back on top (he can verify that or not)

cheers wiz

more light reading

https://linux.org/threads/manjaro-kernel-panics-and-other-tips-for-arch-based-distros.19795/
@wizardfromoz
You are correct! :/
I spoke (posted) too soon without complete information or adequate testing. Sorry about that. My bad.

It seems that I am able to start the Linux Mint bootloader just fine and boot into Mint or Ubuntu if I use the UEFI "one time boot menu" (Dell). But if I try to boot Manjaro from that Linux Mint boot screen I end up with a "dead" computer. It just stops on a black screen and absolutely nothing is responsive. Have to use the power switch to restart.

If I leave the computer alone and let it proceed through it's machinations it will arrive at the Manjaro boot selection screen and from there I can boot Manjaro, Mint, or Ubuntu. Exactly as you said would happen.

My next feat of Linux-fu will be to try the config file you posted.

Sorry for speaking too soon and causing any misunderstanding. :rolleyes:
 
Sorry for speaking too soon and causing any misunderstanding. :rolleyes:

not at all, friend, understandable :):)

let us know how you go

wiz
 
Our Wizard is right-:)

It is only a matter of time before Mint or Ubuntu have an update or an upgrade to the grub bootloader and than Manjaro probably won't boot.

About 3 years ago I was running Manjaro on an old desktop and it had the boot.
At that time that machine was in a triple boot with Voyager Linux and Slackware.

One day Voyager LInux (Xubuntu) updated/upgraded grub and from that point on Manjaro wouldn't boot:-

It sure would be nice if this bootloader war would end.

I wonder; what would it take (aside from time) a developer or a contributor to fix this?
Maybe building and compiling a handful of lib's or writing some code to fix it?
Just a few questions I've thought about over the weekend:-

Heck, if I knew how......I'd fix it- Seriously--
 
a BTW to vrai - it is proactive to include a custom.cfg on each of your debian-based distros to prepare for when the order changes.

if you want to test that capability, before the event (of a change in primary partition), there are at least two ways i can show you on how to put a debian-based distro back in top spot.

cheers

wizard
 
a BTW to vrai - it is proactive to include a custom.cfg on each of your debian-based distros to prepare for when the order changes.

if you want to test that capability, before the event (of a change in primary partition), there are at least two ways i can show you on how to put a debian-based distro back in top spot.

cheers

wizard
Thank you @wizardfromoz ! That was going to be my next question - where to place the custom.config :)
 
Just installed Manjaro 20 Gnome on my laptop.
Looks and runs great!

One slight problem but I've got the fix-:)
On a fresh boot Manjaro doesn't light up the keyboard so I have to run this cmd as root for the backlight on the Sony Vaio to work.
echo 1 > /sys/devices/platform/sony-laptop/kbd_backlight
Screenshot from 2020-05-03 15-18-42.png
 
@Vrai,
When you ran your first updated your fresh installation did you automatically have the night light turned on?
 
@Vrai,
When you ran your first updated your fresh installation did you automatically have the night light turned on?
"Night light"? Not sure what that is. But yes, I have a night light plugged in under my desk but whereas it was still light out it did not come on :) jus' kiddin'!!
Do you mean a keyboard backlight? No, I have no keyboard backlight. Or are you referring to something else?
 
"Night light"? Not sure what that is. But yes, I have a night light plugged in under my desk but whereas it was still light out it did not come on :) jus' kiddin'!!
Do you mean a keyboard backlight? No, I have no keyboard backlight. Or are you referring to something else?
I mean something else.

My fresh install of Manjaro Gnome comes with a night light setting. It's disabled:-
In other words it dims the screen on the laptop.

I was wondering if your Manjaro KDE was automatically set to the night light setting after the first update to the system?
 

Members online


Top