Vesamenu c32 not a com32r image как исправить

I setup the latest rc3 on a USB drive. When it boots, I get the error: ‘vesamenu.c32 not a com32r image’.

I’m able to type ‘GRAPHICAL’ and it boots and works well. Is there a way to fix this so it will boot without any errors? I have tried copying the VESAMENU.C32 file so the two versions on the USB drive match in size and version. This didn’t help.

Other than that error, rc3 with Cinnamon seems to work well, saves my changes, etc.

Ed_P wrote: ↑

05 Apr 2022, 16:25

An interesting problem rick619. Maybe the file on the USB drive is fragmented. Rebuilding the drive or using a different USB drive might resolve the problem.

I did try that, no difference. Is there a line I can add to startup to use the GRAPHICAL option so I don’t have to type it every time? I tried adding this in the default startup area, but it still prompts with the message.

So you are saying when you boot you’re ending up at a terminal screen and not getting to the boot menu? And your entering GRAPHICAL without signing on? What does a ls -l command show for the file? This is what I have.

/boot/syslinux$ ls -l vesa*
-rw-r--r-- 1 root root 26684 May  9  2020 vesamenu.c32

Ed_P wrote: ↑

05 Apr 2022, 16:55

So you are saying when you boot you’re ending up at a terminal screen and not getting to the boot menu? And your entering GRAPHICAL without signing on? What does a ls -l command show for the file? This is what I have.

Code: Select all

/boot/syslinux$ ls -l vesa*
-rw-r--r-- 1 root root 26684 May  9  2020 vesamenu.c32

Correct, I’ve never seen a boot menu. Just the prompt where you can enter cheat codes. I am typing GRAPHICAL before sign in. I’ve tried the copy2ram option, but then it doesn’t save my changes.

I’ll try the above and post results.

So here’s a picture of what it’s doing. It’s stops at the boot prompt and displays this message every few seconds. I can then type GRAPHICAL and it will start.

I did try it on one laptop and it would just get a ‘kernel not found’ error.

Tried another laptop:

If I boot to UEFI and select the drive, I just get a black screen.

If I do the legacy boot, the photo is what happens.

EDIT: Looks like I can’t attach pictures…

It will show
line 1: boot:
line2: vesamenu.c32: not a COM32R image

This will repeat until you type GRAPHICAL

To post pictures upload them to a free image server then post a link to the images. I prefer postimage.org but there are others.

It sounds like your boot problems are more than just the vesamenu problem. What is the size and format of your USB drive and how did you install Porteus to it? Did you follow the steps in the ISO’s USB_INSTALLATION.txt file? How are you booting the drive in the various laptops, machine ESP/BIOS selection or Grub2 menus? Did you do an ls -l on the vesamenu.c32 file? And can you do one of the USB drive?

The USB drive is 32GB and is currently formatted with NTFS.

I extracted the ISO to it and ran bootPorteus-installer-for-Windows.exe

Looking at the USB installation file, looks like I will need to re-do the USB drive and follow the EFI instructions, make sure the first partition is FAT32 first. I’ll give that a shot and try it again.

rick619 wrote: ↑

06 Apr 2022, 18:43

The USB drive is 32GB and is currently formatted with NTFS.

Not a good choice for a USB drive. Journeling adds overhead and wear.

rick619 wrote: ↑

06 Apr 2022, 18:43

make sure the first partition is FAT32 first.

Make the whole drive FAT32, that’s what I do for mine.

Ok, I just formatted the drive as FAT32 and it did get the boot menu and booted right up! Appears to be working well. I’ll mess with it more later.

Thanks for your help!

Ed_P wrote: ↑

06 Apr 2022, 19:53

Make the whole drive FAT32, that’s what I do for mine.

Or create a FAT32 as 1st partition and a small 2nd partition as ext2 (without journaling!) as 2nd, then you can use the UUID cheatcodes and have a rootcopy folder.
Or just use that partition for Linux files, because Windóws is unable to see any partitions on a USB thumbdrive that is not the 1st partition. (That is only valid for USB thumbdrives, Windoze can see all partitions on USB harddrives)

Since I have a 2GB SD card and no real use for such a small SD card, I formatted it as ext2 and use it as my USB boot drive (using a quality USB-cardreader, booting directly using the notebook’s own SD card slot not works)

root@porteus:~# fdisk -l /dev/sdc
Disk /dev/sdc: 1.84 GiB, 1977614336 bytes, 3862528 sectors
Disk model: STORAGE DEVICE  
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: 0x009000b0

Device     Boot Start     End Sectors  Size Id Type
/dev/sdc1  *      135 3862527 3862393  1.8G 83 Linux

Rava wrote: ↑

07 Apr 2022, 22:34

Ed_P wrote: ↑

06 Apr 2022, 19:53

Make the whole drive FAT32, that’s what I do for mine.

Or create a FAT32 as 1st partition and a small 2nd partition as ext2 (without journaling!) as 2nd, then you can use the UUID cheatcodes and have a rootcopy folder.
Or just use that partition for Linux files, because Windóws is unable to see any partitions on a USB thumbdrive that is not the 1st partition. (That is only valid for USB thumbdrives, Windoze can see all partitions on USB harddrives)

Since I have a 2GB SD card and no real use for such a small SD card, I formatted it as ext2 and use it as my USB boot drive (using a quality USB-cardreader, booting directly using the notebook’s own SD card slot not works)

Code: Select all

root@porteus:~# fdisk -l /dev/sdc
Disk /dev/sdc: 1.84 GiB, 1977614336 bytes, 3862528 sectors
Disk model: STORAGE DEVICE  
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: 0x009000b0

Device     Boot Start     End Sectors  Size Id Type
/dev/sdc1  *      135 3862527 3862393  1.8G 83 Linux

Probably going to keep it simple and have one fat32 partition. That way I can still use all the space as a thumb drive.

asked Dec 5, 2011 at 6:00

I recently had this problem and I solved it this way:

• hit “TAB”: the installer will show a list of possible images
• type the correct image name (watch caps!)
• hit enter

KeidaxKeidax

7713 gold badges8 silver badges20 bronze badges

ThugThug

1111 bronze badge