problems with grub boot loader LL 2.8 beta

[melb1938]

I have a hard drive with Only Linux Distros on it no windows on any of my machines. I have a couple of Linux distros installed and working fine. I partitioned and installed LL 2.8 beta. all goes well until it is finished installing and time to boot. I then get a error message that says Error: File name expected. I can boot log into my other distros but LL will not boot. Seems several are having the same problem. What is going on and how can I fix it. I refuse to install windows. I want to install LL on a slower computer because it is not so resource intensive. If I can't get this issue resolved I will have to find another distro. I would really like to get this fixed as I used LL on another machine which I no longer have.
Mel

[Valtam]

This is covered plenty on the forums. Please use the Search box on the first page. Cheers

[melb1938]

This is covered plenty on the forums. Please use the Search box on the first page. Cheers

If it is I can't find it for my particular case. I would not have posted if I could have found the information that I seek when I searched the forum. I get tired of people telling those who ask a question RTFM or search the forum. It is not in the Manual and my problem was not addressed when I read several threads in the forum and did a search. I would really like to use Linux Lite, But refuse to put windows on my main machine.

Now can anyone in the forum help me with my problem. Here are the facts. My main computer does not have windows on it. I have several linux distributions that I run duel and triple boot. No windows. I am not opposed to putting LL boot loader in the MBR. I have done this with several distros. When I install LL and go to boot I get a error saying ERROR: can't find File or something like that. It appears that is looking for Windows or a Dos partition. Can anyone help me with this problem or is it not possible without windows? I feel the Dev's have made a big mistake by modifying the boot loader for window. When a person new to linux wants to try it, they can use the live CD /DVD if they install it on their hard drive they can always use windows boot repair when they remove it. Just my 02 cents worth. I hope that someone can help in a civil manner.
Mel

[firenice03]

Searching "GRUB" as suggested has many results, with various configurations... Further research and information may be required..

Here's a few links that may be a good place to start:
https://www.freecinema2022.gq/forums/insta...ue-please/

Or:
https://www.freecinema2022.gq/forums/insta...ith-grub2/

Also, I see that you are trying to install 2.8 beta, if you're looking to test the distro you may want to install LL 2.6 as this is the current release and may yield better results.
https://www.freecinema2022.gq/download.html

[rafa]

Linux is not a good place for lazy people, someone who have a couple of linux's distros installed should know it.

Try use the forum to improve your skills and find a solution by reading more than one post. Instant and customized support is an expensive thing available on specialized sites. Forum have a more collaborative spirit.
Good luck

[gold_finger]

@melb1938,

LL's grub has alterations to it that cause problem booting it when another Linux distro's grub is in charge of booting computer.  Because of that, best solution is to just make LL's grub be the one installed to the MBR of drive and in control of booting.

If it's installed but you can't boot into it now, just boot again with live LL dvd/usb that you installed with and follow these instructions to install grub to the MBR of drive: https://www.freecinema2022.gq/forums/insta.../#msg14247 .

When done, all other distros on computer should boot from LL's grub menu.  If they aren't listed right away, boot into LL and run this in a terminal to update grub and all should appear on next boot:

Code:

sudo update-grub

[melb1938]

I am posting this to Thank Jerry, Fireice03, and Gold_Finger, who have taken the time to respond to my post, and to help me with my problem.  This is also a rebuttal to the unhelpful reply by Rafa by insinuating that people who ask questions are lazy. Rafa you do not know me or what my knowledge of Linux is. You have been no help in your sarcastic remarks, which have no place in a support or help forum. I notice that you are 24 years of age and only have 5 posts in the forum. Does this make you a expert on who is lazy or not? I asked in my second post for help and for people to be civil in their replies. You were not Helpful at all, and your reply was very immature for someone purported to be 24 years of age. I do not want to get a flame war started, and this will be my last post in this thread.

I will repost my question in another post using a different context regards the modified grub boot loader in LL. I have worked with and used Linux for 21 years. I am a retired Computer Tech and have a Novel Education Certificate for configuration and installation,for Networking. I am not a programmer or a Developer so don't know how to go about changing the Grub Boot loader in LL so it doesn't have to be in the MBR to boot LL 2.6 and 2.8. I will discuss this in another post.
Mel

[rokytnji]

Back in the day when I multi-booted  on 2 different internal hard drives. But before grub2 became the standard.

I could multiboot frugal installs and full installs between two different ide internal hard drives.
The only thing I did when deciding to chainload iso installs so they would boot.

I would decide which bootloader would control the mbr and install the preferred grub from the preferred there on the mbr.
Like in the Lord of the rings. One ring to rule them all.
Then when it became time  for the other distro install.
I'd tell it to install to / of the iso partition I was installing to.
Not the mbr.

Then hand make chainload entries to cover booting.
This was all before os-prober and grub2 though.

https://www.gnu.org/software/grub/manual...ading.html
http://ubuntuforums.org/showthread.php?t=1300461

I ceased multi-boots on individual drives after I started picking up my free computers from city hall.
Now I have enough equipment to experiment with without using multiboot.
Just a old example of one of my old menu.lst

Code:

timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message


title AntiX  at sda1, kernel 3.3.5-antix.1-486-smp
kernel /boot/vmlinuz-3.3.5-antix.1-486-smp root=/dev/sda1 nomce quiet nosplash nouveau.modeset=0 vga=791
initrd /boot/initrd.img-3.3.5-antix.1-486-smp
boot

title Semplice GNU/Linux, with Linux 3.2.0-3-486
rootnoverify (hd1,1)
chainloader +1

title Vector STD Gold 7 at /dev/sda2
rootnoverify (hd0,1)
chainloader +1

title Puppy Linux 529 frugal in sdb1 dir macpup529frugal
rootnoverify (hd1,0)
kernel /macpup529frugal/vmlinuz pmedia=atahd psubdir=macpup529frugal
initrd /macpup529frugal/initrd.gz

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro
# kopt_2_6=root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro nosplash quiet

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(single-user) single
# altoptions=(init-3) 3

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title      Debian GNU/Linux, kernel 3.5.2-antix.1-486-smp
root      (hd0,0)
kernel      /boot/vmlinuz-3.5.2-antix.1-486-smp root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro
initrd      /boot/initrd.img-3.5.2-antix.1-486-smp

title      Debian GNU/Linux, kernel 3.5.2-antix.1-486-smp (init-3)
root      (hd0,0)
kernel      /boot/vmlinuz-3.5.2-antix.1-486-smp root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro 3
initrd      /boot/initrd.img-3.5.2-antix.1-486-smp

title      Debian GNU/Linux, kernel 3.3.5-antix.1-486-smp
root      (hd0,0)
kernel      /boot/vmlinuz-3.3.5-antix.1-486-smp root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro
initrd      /boot/initrd.img-3.3.5-antix.1-486-smp

title      Debian GNU/Linux, kernel 3.3.5-antix.1-486-smp (init-3)
root      (hd0,0)
kernel      /boot/vmlinuz-3.3.5-antix.1-486-smp root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro 3
initrd      /boot/initrd.img-3.3.5-antix.1-486-smp

title      Debian GNU/Linux, kernel memtest86+
root      (hd0,0)
kernel      /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

The Semplice linux entry was grub2 (Semplice being Debian Unstable had grub2 at that time).
That menu entry invoked Semplice grub installed to root and let Semplice grub take over booting.
Kinda hard to explain. But it was easy for me then to muti-boot that way.
Just info I am posting. Nothing more.

Edit: I forgot this. I keep a live iso disk of this but it can also be installed in Ubuntu or Mint as a repair application.

https://help.ubuntu.com/community/Boot-Repair