Hi,

From the logfile in /var/log/boot I get:
Sat Feb 14 21:24:47 2009:mv: cannot move `/usr/share/fluxbox/menu-install' to `/home/piet/.fluxbox/menu': No such file or directory
Sat Feb 14 21:24:47 2009: Updating icewm menu.
Sat Feb 14 21:24:47 2009: mv: cannot move `/usr/share/icewm/menu-install' to `/home/piet/.icewm/menu': No such file or directory

But these are not the first lines when starting up. It starts with (no in the logfile boot):
ACPI: Bios Age (1999) fails cutoff (2000) ACPI=force is required to enable ACPI
then readily behind this first line:
usplash: no usable theme for 1024 x ?? (path ???) Unknown symbol in module or unknown parameter. See demsg.
screen init failed
Fatal: error inserting fan (path ????) : no such device
Warning: error inserting processor
Fatal: error inserting thermal

Well, I think this was it.

Any help or comment?

Piedie

Not sure why it's trying to move"menu-install". anti may have to help out there.

For acpi, I would edit the /boot/grub/menu.lst and add acpi=force or acpi=off. This should clear up those errors.

The usplash error should be corrected by either using nosplash in the /boot/grub/menu.lst or using a splash with a lower resolution (800x600). If you install startupmanager it will help you set it up.

The rest is related to acpi so the above should work.

To fix the first one, you can remove these 2 files
/usr/share/fluxbox/menu-install
/usr/share/icewm/menu-install

(Once installed, the menu-install files in those folders get moved to your /home folder so the install antiX line in the livecd menu is removed. It seems if you have /home on a separate partition the script automating the mentioned process doesn't work)

For others, eriefishers solutions should work.

Also for the splash, use the third option in the boot menu and it should boot without the error message.

anticapitalista wrote:To fix the first one, you can remove these 2 files
/usr/share/fluxbox/menu-install
/usr/share/icewm/menu-install

(Once installed, the menu-install files in those folders get moved to your /home folder so the install antiX line in the livecd menu is removed. It seems if you have /home on a separate partition the script automating the mentioned process doesn't work)

For others, eriefishers solutions should work.

Also for the splash, use the third option in the boot menu and it should boot without the error message.

Hi Anti,

Removing the menu-install files worked. And yes, to some reason my /home is in a separate partition.

Using the third boot menu option gives:
Unknown ??? /mnt/mepis/boot/grub/menu.lst: ignoring boot option

Itried eriefisher editing of menu.lst but __{{emoticon}}__ __{{emoticon}}__ how do I edit when I am as su in bash???

thanks,

Piedie

Once in a terminal su to root and enter your password. Then....... OR

Open run via the menu and type"gksu leafpad /boot/grub/menu.lst".

!!!!!!!!MAKE A COPY BEFORE YOU EDIT FOR A BACKUP IN CASE OF ERROR!!!!!!!!!

That is a MEPIS bug when using initrd option (default) when installing.
As erie says, edit the /boot/grub/menu.lst file and on that third line, just remove the bit that shows,
/mnt/mepis/boot/grub/menu.lst

Have a look at this thread, how to to set up the menu.lst file better.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/how-to-set-up-boot-grub-menu-lst-for-automatic-updates-t1244.html#p9035"
linktext was:"antix.freeforu ms.org/how-to-set- ... html#p9035"
====================================
" onclick="window.open(this.href);return false

anticapitalista wrote:That is a MEPIS bug when using initrd option (default) when installing.
As erie says, edit the /boot/grub/menu.lst file and on that third line, just remove the bit that shows,
/mnt/mepis/boot/grub/menu.lst

Have a look at this thread, how to to set up the menu.lst file better.

how-to-set-up-boot-grub-menu-lst-for-automatic-updates-t1244.html#p9035

Well, I managed to make the changes. Starting up with the third menu choice gives no more errors.
Starting up with the first menu choice gives still gives the two Fatals and one Warning as described earlier.

I looked at the thread, but I do not feel confident to make the changes (yet). Where can I find my UUID __{{emoticon}}__ I heard of id but that seems to be something else.

Thanks,

Piedie

eriefisher wrote:Once in a terminal su to root and enter your password. Then.......

Code: Select all

nano /boot/grub/menu.lst

Thanks, erie.
But...I've been searching before I put this question in here. Where could I have found nano to be a text editer in the bash terminal __{{emoticon}}__ __{{emoticon}}__ __{{emoticon}}__ __{{emoticon}}__

/home/username/Document/installed.txt will show you everything installed.