Thread: �No suitable video mode found� error, booting in blind mode
First Cup of Ubuntu 
�No suitable video mode found� error, booting in blind mode
Since a few days I am getting the error written in the tittle when booting my PC, having the current Ubuntu 18.04.1 LTS bionic.
I have searched the web for a solution, tried to reinstall grub2 and it did not work. I also tried out a solution, where the following lines:
loadfont "unicode" set gfxmode=auto set gfxpayload=keep insmod all_video insmod gfxterm terminal_output gfxterm
should be added to /boot/grub/grub.cfg
however all of this commands are already (a little bit scattered around the file, and some of them in some if blocks.
Did someone have a similar problem and if yes, you maybe have some advices what else I could try out?
Ubuntu addict and loving it 
Join Date Aug 2011 Location 51.8� N 5.8� E Beans 6,758 —> Beans 6,758 Distro Xubuntu 22.04 Jammy Jellyfish
Re: �No suitable video mode found� error, booting in blind mode
Changing stuff in /boot/grub/grub.cfg is a bit pointless as all changes are overwritten whenever the update-grub script runs, which is after every kernel update/removal.
I once had a very similar problem with an old computer after connecting a new monitor. The trick was to disable the graphical terminal by uncommenting one line in /etc/default/grub, so that it now reads
# Uncomment to disable graphical terminal (grub-pc only) GRUB_TERMINAL=console
Whether that applies to your situation too, I don’t know.
After changing /etc/default/grub, you can apply the changes with
Arch Linux: booting in blind mode UEFI
I recently installed Arch on an old box for someone else, and I’m running into a problem: I am booting to a GRUB shell, and when I manually load the kernel with linux /boot/vmlinuz-linux and initrd /boot/initramfs-linux.img , I get a message saying this:
error: no suitable video mode found Booting in blind mode It seems that the kernel was loaded, but none of the userspace is displayed. For a few minutes, I am not allowed to use the keyboard in any sort of way, but after the only thing I am able to do is Ctrl-Alt-Del to reboot. I do not know if this is a graphics driver issue, as I’m not too aware of the modes GRUB has. If it is necessary, the graphics card is an ATI/AMD Radeon 6470M HD «Seymour». This issue has never happened on any of my computers running Arch; does anyone know how to get around this?
2 Answers 2
I went through this with my laptop.
Grub does require you to initialize the display as well as have UEFI support in the kernel that supports display handoff.
Once you do this you should be able to see all of the boot process (at some point during boot the display is initialized and you should be able to see output.)
I don’t use the mess of a file that grub2 creates, I wrote my own, which I’ll share. It is set up to dual boot linux and windows but will have to be modified for your installation (drive and partitions) so not completely a copy and paste. I also don’t bother with an initramfs so you’ll have to add that to the linux entry.
timeout=10 default=0 # Declare where the Grub modules are located set prefix=(hd3,gpt3)/grub # Load EFI video drivers. This device is EFI so keep the # video mode while booting the linux kernel. insmod efi_gop insmod font if loadfont $/fonts/unicode.pf2 then insmod gfxterm set gfxmode=auto set gfxpayload=keep terminal_output gfxterm fi # Declare boot entries below this line menuentry 'Linux' < root=hd3,gpt3 linux /vmlinuz root=PARTUUID=038f0d56-22ed-e346-b243-a86b4abf8410 quiet rootfstype=ext4 net.ifnames=0 biosdevname=0 >menuentry 'Windows 7' < root=hd2,gpt2 chainloader (hd2,gpt2)/EFI/MICROSOFT/BOOT/bootmgfw.efi > It is important that that your /boot/grub/fonts/unicode.pf2 file actually exists! You also need to tell grub where the modules are located.
Linux no suitable mode found
I just installed Gentoo on my machine following the
Handbook and this
guide
for encrypted disk. Everything worked fine untill booting the installed
OS.
| Код: |
| Loading initial ramdisk . |
| Цитата: |
| When using a LUKS passphrase and there is no visible prompt after loading the initramfs, try typing the passphrase. If this continues loading try Grub without gfxterm/ in text-only mode. Depending on the BIOS it might help to boot legacy first to check if there’s a prompt at all. |
So I decided to run GRUB2 on text-mode only. Here is an extract of
/etc/default/grub
| Код: |
| GRUB_DISTRIBUTOR=»Gentoo» GRUB_CMDLINE_LINUX=»dolvm crypt=UUID=. GRUB_CMDLINE_LINUX_DEFAULT=»quiet splash» GRUB_TERMINAL=console GRUB_GFXPAYLOAD_LINUX=text |
Then, I have the two following lines after Loading initial ramdisk :
| Код: |
| error: nosuitable video mode found Booting in blind mode |
I tried adding insmod all_video in /boot/grub/grub.cfg but I get the same
thing.
I looked at similar questions in the gentoo and arch forums but I still have
this issue.
Note that CONFIG_FRAMEBUFFER_* features are all enabled in my
configuration. Same with CONFIG_EFI_* features.
Do you know where the issue comes from and how to solve it?
Added the same lines in my grub.cfg : I do not have the message about Booting in blind mode, however, it is stuck on Loading initial ramdisk
Here are some materials:
.config : https://pastebin.com/hgPa3sJ8
grub.cfg: https://pastebin.com/LtZd78eW
blkid:
| Код: |
| /dev/loop0: TYPE=»squashfs» /dev/nvme0n1p1: UUID=»6F07-FA00″ BLOCK_SIZE=»512″ TYPE=»vfat» PARTLABEL=»grub» PARTUUID=»0824cffe-505d-476f-a5bd-7c5f52bd442c» /dev/nvme0n1p2: UUID=»EDCA-2FF9″ BLOCK_SIZE=»512″ TYPE=»vfat» PARTLABEL=»boot» PARTUUID=»8aa18b8e-f348-4771-85ea-80c793238e40″ /dev/nvme0n1p3: UUID=»b2670a94-041e-4133-8dc9-58c6278384a0″ TYPE=»crypto_LUKS» PARTLABEL=»lvm» PARTUUID=»cc58e84a-6469-4ce8-9716-1336fe3bc923″ /dev/sda1: BLOCK_SIZE=»2048″ UUID=»2021-08-08-17-56-45-97″ LABEL=»Gentoo amd64 20210808T170546Z» TYPE=»iso9660″ PTUUID=»7057d8c5″ PTTYPE=»dos» PARTUUID=»7057d8c5-01″ /dev/sda2: SEC_TYPE=»msdos» LABEL_FATBOOT=»GENTOOLIVE» LABEL=»GENTOOLIVE» UUID=»ADDC-CDE8″ BLOCK_SIZE=»512″ TYPE=»vfat» PARTUUID=»7057d8c5-02″ /dev/mapper/lvm: UUID=»ZZBdD3-nV0X-Xc0W-Mh3l-exlY-fY9C-kayrGc» TYPE=»LVM2_member» /dev/mapper/vg0-root: UUID=»133177fa-24fa-4a71-a37d-59a1743460a6″ BLOCK_SIZE=»4096″ TYPE=»ext4″ /dev/mapper/vg0-var: UUID=»18dd3474-5b22-4cca-8c13-28022f4a802d» BLOCK_SIZE=»4096″ TYPE=»ext4″ /dev/mapper/vg0-home: UUID=»d8aba8b6-94c1-466c-bc95-8a778380223c» BLOCK_SIZE=»4096″ TYPE=»ext4″ |
(The line
| Код: |
| search —no-floppy —fs-uuid —set=root —hint=’lvmid/icUlx2-s4O2-Kjqk-5BD7-I2pf-SnTW-ZJfOoH/7lIvQf-0h0G-5vqT-Xxdb-jzd1-CATz-mvLV1F’ 133177fa-24fa-4a71-a37d-59a1743460a6 |
)
It should now be working in text mode, but grub.cfg still says:
| Код: |
| terminal_output gfxterm |
so the change to GRUB_TERMINAL=console doesn’t seem to have taken effect. Did you redo grub-mkconfig?
I’m assuming /dev/nvme0n1p2 has a partition containing both /vmlinuz-5.10.52-gentoo-x86_64 and /initramfs-5.10.52-gentoo-x86_64.img (note, not in /boot on that disk. If you meant that, the linux/initrd lines would be /boot/vmlinux. or /boot/initramfs. and you’d need to adjust your GRUB settings.
Copyright 2001-2023 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy
error: no suitable mode found
Computer hangs for about 45 seconds and then continues to boot normally.
I gather from reading that this has to do with the video mode being improperly set in grub, but all of the solutions require booting a live cd (which I cannot do). Any suggestions?
No. It’s an older computer and the BIOS doesn’t support booting from USB. I can use a live disk from a smaller distro like puppy, but I’m not sure if I can do what needs done (and really don’t understand what I need to do) without using an ubuntu disk.
You need to edit the /etc/default/grub and change the GRUB_GFXMODE=640×480 to a suitable value for your PC and remove the # from the beginning of the line.Then run sudo update-grub to create a new grub.cfg.
You need to edit the /etc/default/grub and change the GRUB_GFXMODE=640×480 to a suitable value for your PC and remove the # from the beginning of the line.Then run sudo update-grub to create a new grub.cfg.
Unfortunately, that didn’t do it. Thanks, though. The Grub2 link was especially useful.
I’ve been working at it for the last couple of hours, and no matter what I do, the errors remain. Passing different boot options (disabling ACPI, xforcevesa, modesets), using the mainline kernel, altering GRUB_GFXMODE — everything leaves me with the same error.
The only thing left that I know to do is to move to an older kernel or live with the error and just be glad that it eventually boots.
Hi all because I’am new on this forum.
I’m quite new user of ubuntu.
Yesterday I installed on old computer (pentium III 800Hz 192MB of RAM) Ubuntu 10.04 Server for my small home file server. Also I want to run one app under wine so i need GUI
I Think fluxbox is the best here. So I install xorg and fluxbox and then I thinked konqueror may be usefull so I install it. Today I turned on the computer and display shows grub bug (I think )
Hi all because I’am new on this forum.
I’m quite new user of ubuntu.
Yesterday I installed on old computer (pentium III 800Hz 192MB of RAM) Ubuntu 10.04 Server for my small home file server. Also I want to run one app under wine so i need GUI
I Think fluxbox is the best here. So I install xorg and fluxbox and then I thinked konqueror may be usefull so I install it. Today I turned on the computer and display shows grub bug (I think )
How to fix it.
Please don’t tell me that I must reinstall the system (again. ):(
I get this too, in Maverick alpha. The same error messages on boot.
error file not found
no suitable mode found
and the complaint about missing terminal.
My situation may offer someone out there a clue.
My system didn’t start doing this (as far as I know) until after I used squashfs-tools to compress my /usr folder for speed and space-saving.
Here’s my run-through. I don’t recommend newcomers attempt this.
sudo apt-get install squashfs-tools
Don’t install aufs-tools (or backup your partition or something first) because it breaks the system on karmic, or it used to (I haven’t tried installing aufs-tools in maverick).
sudo mkdir /squashed
sudo mkdir /squashed/usr
sudo mkdir /squashed/usr/ro
sudo mkdir /squashed/usr/rw
compress the /usr folder with
sudo mksquashfs /usr /squashed/usr/usr.sfs -b 65536
Add the following 2 lines to /etc/fstab, probably after the line that defines «/»:
/squashed/usr/usr.sfs /squashed/usr/ro squashfs loop,ro 0 0
usr /usr aufs udba=reval,br:/squashed/usr/rw:/squashed/usr/ro 0 0
Reboot to a Puppy Linux liveusb, but you can use most any live cd or usb that you’re able to boot with. Mount the hard drive, renamed /usr to /usr-old and created an empty folder named /usr. Then reboot and pray to whatever god you believe in, or Chuck Norris. He believes in you, and he’ll kick. Delete the /usr.old folder to free that space.
Typically, this little procedure will get you’re usr folder down to about half size, more or less, with actually a performance increase over uncompressed usually. Maintenance on this is a recompression of the /usr folder, following basically the steps above except make the destination to /squashed-new then booting into your live usb or cd to rename the old /squashed folder to squashed-old and the new one to /squashed, then delete the old one once you know the new one is working. I recommend the use of something like Clonezilla to make a partition backup first if you have enough storage to write the backup to, before doing something advanced like the above.
Everything else seems to be fine. I just never used to see those error messages before and now I do.
vBulletin �2000 — 2023, Jelsoft Enterprises Ltd. Ubuntu Logo, Ubuntu and Canonical � Canonical Ltd. Tango Icons � Tango Desktop Project.
User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License. For details and our forum data attribution, retention and privacy policy, see here