[SOLVED] New debian11 install - now grub menu has gone

colorpurple21859 · 08-08-2022, 12:07 PM

What is in /etc/default/grub on the mxlinux partition? both /etc/default/grub from each distro should be similar

change this line back to

#GRUB_TERMINAL=console

and uncomment this line and change the numbers to a resolution that will work with the tv something like this:

GRUB_GFXMODE=1280x720

rerun update-grub

braithwaite · 08-08-2022, 12:24 PM

Quote:

Originally Posted by yancek

What TV would that be? You haven't mentioned a TV before. Is this a laptop, desktop and you have a monitor on the computer and also have it connected to a TV? Do you see a display or anything on the computer monitor?

I have a desktop with a new build.
The TV is connected via hdmi onto the desktop.
I used the same TV with my previous older build.

Quote:

Doesn't seem weird to me since in your initial post, you indicate that both MX and Debian booted successfully until you changed some setting in Debian. Use your notes from when you made the changes and change them back.

I used debian non-free.iso via netinstall.
The .iso already had amd drivers pre-installed.
I looked at /etc/apt/sources.list and contrib and non-free repos were already added.
I simply installed brave-browser after inputting their commands on the terminal.
I then installed my vpn app.
I don't think I changed anything else.

Quote:

If you aren't seeing the BIOS firmware page on boot, you have a more serious problem. Has that happened before?

No it hasn't happened before.
I don't understand why debian still boots.

During debian install the wizard said MX21 had created an efi partition.
So during my debian install I could choose to create another efi partition for debian to use.
I didn't choose that option because an efi partition already exists on the drive.

Is it possible the efi partition isn't being shared and the motherboard doesn't have access to it?

Quote:

It isn't clear from your posts whether you have a UEFI BIOS, do you know if you are using UEFI?

When I first installed MX21 I went into uefi to instruct it to boot from usb.

Quote:

Use one of your usb drives to boot and run sudo fdisk -l or parted -l to list the partitions. You should see a partition named EFI. If you don't, you are not using UEFI.

I'm not able to use my MX21 live usb when I insert it.
I just get a blank screen now.
But this new debian install boots from hard disk.
The output of fdisk -l is:

Code:

~# fdisk -l
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 850 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf45215aa

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048 245762047 245760000 117.2G 83 Linux
/dev/sda2       471605248 488382463  16777216     8G 83 Linux
/dev/sda3       245762048 471605247 225843200 107.7G 83 Linux

Partition table entries are not in disk order.

I think sda2 is the swap file shared by both OSs.
Bu I haven't checked if they both have the same uuid.

braithwaite · 08-08-2022, 12:51 PM

Quote:

Originally Posted by colorpurple21859

What is in /etc/default/grub on the mxlinux partition? both /etc/default/grub from each distro should be similar

change this line back to

#GRUB_TERMINAL=console

and uncomment this line and change the numbers to a resolution that will work with the tv something like this:

GRUB_GFXMODE=1280x720

rerun update-grub

I've done this.
Unfortunately there is no change to the boot process.
No motherboard screen, no grub menu. It opens into the debian login screen.

colorpurple21859 · 08-08-2022, 01:27 PM

Post the output of
lsblk -f

braithwaite · 08-08-2022, 01:57 PM

Quote:

Originally Posted by colorpurple21859

Post the output of
lsblk -f

This is it:

Code:

yayoi@debian11:~$ lsblk -f
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                         
├─sda1
│    ext4   1.0   rootMX21
│                       34038f0f-b601-4691-960a-671bc00d6095                
├─sda2
│    swap   1           21e3fcf0-dc7a-442a-82f7-9942613acfd5                [SWAP]
└─sda3
     ext4   1.0         b6df632a-d9a3-4082-adec-41224792601a   92.8G     7% /

colorpurple21859 · 08-08-2022, 05:31 PM

add this to /etc/default/grub and rerun grub-update

Code:

GRUB_PRELOAD_MODULES="all_video"

other grub video modules to try:
vga
video_bochs
video_cirrus
video_colors
video_fb
video
tga

suramya · 08-08-2022, 07:40 PM

Quote:

Originally Posted by braithwaite

I did this:

Code:

~# grub-install
Installing for i386-pc platform.
grub-install: error: install device isn't specified.

You need to pass the device where the grub should be installed, oOn my system it is on /dev/sda. From the manual: https://www.gnu.org/software/grub/ma...2dinstall.html

braithwaite · 08-09-2022, 03:49 AM

Quote:

Originally Posted by suramya

You need to pass the device where the grub should be installed, oOn my system it is on /dev/sda. From the manual: https://www.gnu.org/software/grub/ma...2dinstall.html

Yes I think it's a grub issue.
It always is every time I install debian.
It's amazing how the debian-installer is so pathetically outdated and debian just can't see it.

1. I can reinstall grub:

Code:

grub-install /dev/sda

I think I have to run update-grub or update initramfs after that.

My problem is if it doesn't work will I still be able to boot into this debian install?
My MX live usb isn't booting and I can't access uefi bios.

I mean is that even legal? Debian is preventing me from accessing my own motherboard.
Isn't there a violation of some permissions issue here?

2. I can delete MX OS from the ssd.
Then re-install grub to sda.
Grub should have full control of the mbr on the ssd.

Is this an option?

3. I can physically remove the ssd by disconnecting the data and power cables from the motherboard.
I should then be able to boot from MX live usb.
But if I re-connect my ssd will the live usb access it or does it require a re-boot?

colorpurple21859 · 08-09-2022, 05:13 AM

Update-grub regenerates the grub.cfg that is the grub menu seen, update initramfs updates initramfs needed for the kernel to boot, grub-install puts grub boot code into mbr of drive or efi partition.
Update-grub needs to be ran anytime a change is made to /etc/default/grub

yancek · 08-09-2022, 05:19 AM

Quote:

Legacy boot on HDD

You show the output above from Debian in post 14 which indicate it is a Legacy install and not UEFI. If you boot Debian and go to the /boot/efi/EFI partition, you would see an entry there for Debian if it was UEFI. One major reason a
Grub menu does not show on boot is if only one OS is installed or "detected". It is generally not a good idea to mix Legacy and UEFI installs which is what you appear to have done, MX in UEFI and Debian in Legacy. I have had a Legacy install on an external drive which booted EFI Linux systems on another drive so I don't know that is the only problem.

mean is that even legal?

You're kidding, right? The iso you downloaded and installed has a license and as it is free (as in no cost) it will come with absolutely no warranty. That should be stated in the license.

I don't know why you would think reinstalling Grub from Debian would help. That's the only OS that boots. If you haven't run sudo update grub from Debian, do that and reboot to test.

Quote:

But if I re-connect my ssd will the live usb access it or does it require a re-boot?

You won't need to reboot but you will have to manually mount the partitions.

Since you are not able to boot from the USB any longer as well as not access the BIOS firmware it is looking more like a hardware problem to me but that's just a guess.

suramya · 08-09-2022, 05:44 AM

Quote:

Originally Posted by braithwaite

Yes I think it's a grub issue.
It always is every time I install debian.
It's amazing how the debian-installer is so pathetically outdated and debian just can't see it.

Not sure why you are seeing this issue. I just reinstalled Debian on my laptop a few days ago and it detected all my installs without issue (Kali, Debian and Windows). I wanted Kali to manage the bootloader, so I booted into Kali and ran update-grub followed by grub-install and GRUB was updated.

Quote:

1. I can reinstall grub:

Code:

grub-install /dev/sda

I think I have to run update-grub or update initramfs after that.

No it is the other way round. Run the update followed by install.

Quote:

I mean is that even legal? Debian is preventing me from accessing my own motherboard.
Isn't there a violation of some permissions issue here?

How is it illegal? You not being able to do something on your system because of a system 'bug'/configuration issue doesn't mean that it is automatically illegal. If it locked you out and was demanding ransom to release your files then it would be illegal. Not the way it is.

Also, Debian has nothing to do with you not being able to access your BIOS/motherboard. The bootloader / OS comes into play way after you have to press the key to enter the BIOS. If the bootloader (GRUB) menu is up then it is too late to enter the BIOS and you need to reboot. Check online for the key you need to press to enter the BIOS. On my system it is F2/DEL key.

Quote:

3. I can physically remove the ssd by disconnecting the data and power cables from the motherboard.
I should then be able to boot from MX live usb.
But if I re-connect my ssd will the live usb access it or does it require a re-boot?

I would avoid disconnecting/reconnecting a SATA internal drive while the system is running. If you want to go this way you need to use an external drive caddy for the drive and connect it over USB. fooling around with power and data cables while the system is running is a good way to short out your system.

braithwaite · 08-09-2022, 07:46 AM

Quote:

Originally Posted by yancek

You show the output above from Debian in post 14 which indicate it is a Legacy install and not UEFI.

I don't understand why I have a legacy boot.
The .iso is for debian11 and the hardware is all new.

The motherboard would not boot initially when my 5-series cpu was installed.
So an older 3-series amd cpu was installed to the motherboard for it to switch on.
After that - drivers were installed via usb onto the motherboard.
After that the desktop booted with the newer 5-series cpu.

Quote:

If you boot Debian and go to the /boot/efi/EFI partition, you would see an entry there for Debian if it was UEFI.

This is the output I have:

Code:

:/boot$ ls -a
.   config-5.10.0-16-amd64  initrd.img-5.10.0-16-amd64  vmlinuz-5.10.0-16-amd64
..  grub                    System.map-5.10.0-16-amd64

Quote:

One major reason a Grub menu does not show on boot is if only one OS is installed or "detected". It is generally not a good idea to mix Legacy and UEFI installs which is what you appear to have done, MX in UEFI and Debian in Legacy.

The gigabyte b550m motherboard has uefi as far as I know.

Quote:

You won't need to reboot but you will have to manually mount the partitions.

Looks like taking out the ssd and wiping it is he only option.

colorpurple21859 · 08-09-2022, 09:08 AM

From what the op has posted there is one msdos drive, not gpt and has no efi partition. The system is connected to a tv through a hdmi cable. The tv stays black until debian finish booting, so not able to see the bios/firmware settings/boot menu to select the usb key.
I suspect a setting has changed in the firmware/bios and will need to connect to a regular monitor to get into the bios/firmware settings.

braithwaite · 08-09-2022, 10:02 AM

Quote:

Originally Posted by colorpurple21859

From what the op has posted there is one msdos drive, not gpt and has no efi partition. The system is connected to a tv through a hdmi cable. The tv stays black until debian finish booting, so not able to see the bios/firmware settings/boot menu to select the usb key.
I suspect a setting has changed in the firmware/bios and will need to connect to a regular monitor to get into the bios/firmware settings.

I did a reboot and when the pc LED light switched on to boot I pressed delete several times.
There was just a black screen and the OS failed o boot.
So I think the pc had opened uefi bios but nothing is being displayed.

It's possible uefi screen and grub splash screen are showing but it's not being displayed.
Once the debian login screen appears then the display activates.

I've used the display as tv and monitor for years.
It worked fine on my new install of mx linux.

Is it the uefi partition?
It was created when installing MX Linux.
But with this new debian 11 install - grub may have modified the existing uefi partition.
This may cause the motherboard screen and grub screen to not be displayed.
Is this possible?

colorpurple21859 · 08-09-2022, 11:16 AM

You don't have an efi partition. There are only three partitions, sda1=mx21 sda2=swap sda3=debian. Without an efi partition both distos are booting in legacy mode.

To be able to boot in efi mode you will need to convert the drive to gpt, create an efi partition, set up one of the distro bootloader to work in efi mode.

Do you have a regular monitor that you can hook up to see what happens. Maybe one of the keyboard f-keys are fn-fkey will change the output of the graphics to the hdmi port when first turned on.