LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-09-2024, 12:56 PM   #1
plisken
Member
 
Registered: Dec 2001
Location: Scotland
Distribution: Slackware 9.1-15 RH 6.2/7, RHEL 6.5 SuSE 8.2/11.1, Debian 10.5
Posts: 516

Rep: Reputation: 32
Fresh install and Lilo does this


I have installed Slackware more times that I care to remember and while I've in the past had issues with Lilo (not so much in recent years), this is the first I have seen this;
https://i.imgur.com/dhMdA3h.png

In case the image link doesnt work, this issue basically showing the basic and default lilo OS selection screen but there is garbage text scrolling for the duration of the timeout.

It does still boot and the strange thing, even after editing lilo.conf to change the timeout value, something I always do, it remains unchanged.

If I can upload a video I will.

Any thoughts on what might be causing this?

Last edited by plisken; 02-09-2024 at 01:00 PM. Reason: Amending image url
 
Old 02-09-2024, 04:05 PM   #2
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,813

Rep: Reputation: 4451Reputation: 4451Reputation: 4451Reputation: 4451Reputation: 4451Reputation: 4451Reputation: 4451Reputation: 4451Reputation: 4451Reputation: 4451Reputation: 4451
There are several possibilities I can think of but first maybe try something. How easy it would be would depend on what you have for bootable media since I'm not certain all the Slackware install media still supports kernel options at the start that allow a user to indicate a different disk/partition. It used to be noted in print that one could type such as "huge.s root=/dev/foo2 rdinit = ro" and Bingo! Salvation! In any case if you have any media or install that allows for options, you could temporarily change the first active line of lilo.conf from the MBR to the Root partition, tun lilo and then put it back to MBR. Then you could easily determine if you had some sort of corruption in the MBR code.

Just so this isn't merely what could be an empty suggestion, the first thing I'd check is for any odd syntax in the lines calling the .bmp menu screen. It could also be useful to add a stanza to hand off to the root lilo as a chainload if you decide to experiment. Just spitballin'. Maybe this can stimulate some ideas.
 
Old 02-09-2024, 07:56 PM   #3
glorsplitz
Senior Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 1,320

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
you don't indicate bare metal or virtual so check this out and this

Last edited by glorsplitz; 02-09-2024 at 08:32 PM.
 
2 members found this post helpful.
Old 02-09-2024, 10:35 PM   #4
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,994

Rep: Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565
That look like it's from a VirtualBox virtual machine. Since I think 7.0. This was my fix.

Code:
# ------ menu -------
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
#bitmap=/boot/124827-slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
#bmp-colors=255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
#bmp-table=60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
#bmp-timer=65,27,0,255
 
2 members found this post helpful.
Old 02-10-2024, 04:05 AM   #5
plisken
Member
 
Registered: Dec 2001
Location: Scotland
Distribution: Slackware 9.1-15 RH 6.2/7, RHEL 6.5 SuSE 8.2/11.1, Debian 10.5
Posts: 516

Original Poster
Rep: Reputation: 32
Thanks all, yes this was a Virtualbox install (to test something out before deploying in an industrial environment).

As I say, I've installed Slackware many, many times on both real and vm's but this is for sure the first time I've seen this and it might actually be the first install with virtual box 7.0

Thanks again all...
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Edit lilo.conf, run /sbin/lilo, but lilo won't take changes lukameen Slackware 2 02-10-2012 12:10 PM
Pre-existing GRUB eats LILO on fresh install of SW13 anarchic_birdsong Slackware 31 11-04-2009 05:01 AM
Ok fresh slack install and screwed up lilo... silverbullet Slackware 5 11-26-2004 01:34 PM
fresh install (fresh headache) powadha Slackware 2 03-06-2004 01:03 PM
LILO problem with fresh install Bruce Hill Linux - Software 26 08-11-2003 07:26 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:59 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration