LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 09-17-2016, 07:11 PM   #1
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Rep: Reputation: 28
32-bit upgrade 14.1 to 14.2: no lilo display


Upgraded my Dell 2100 (32-bit atom CPU) following each step of the UPGRADE.TXT file as usual. Removed old packages, processed *.new (replacing old, leaving old, modifying old as appropriate), made a new initrd for the 4.4.14 kernel, modified /boot/System.map, config, and vmlinuz to point to the generic-smp kernel versions, modified /etc/lilo.conf for generic-smp-4.4.14 vmlinuz and the huge-smp-4.4.14 as an backup alternative, ran /sbin/lilo, removed cdrom from external drive and tried rebooting.

After the POST the cursor blinks in the upper left corner but the lilo boot box does not display. I've not before encountered this. Obviously I messed up something without realizing it.

Tried booting using the distribution disk and mounting /dev/sda1 on /mnt, but there were only empty directories from /.

Please advise me on how to can recover from this situation. If I can make a USB rescue disk from the distribution DVD on another host I'll do that. But, I've not before encountered a blank screen after the POST.
 
Old 09-17-2016, 08:19 PM   #2
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,323
Blog Entries: 28

Rep: Reputation: 6142Reputation: 6142Reputation: 6142Reputation: 6142Reputation: 6142Reputation: 6142Reputation: 6142Reputation: 6142Reputation: 6142Reputation: 6142Reputation: 6142
The first thing I'd try would be this:

Try booting to the install disk, starting the Setup routine, and then skipping right to the part about "Configure your new Linux system," then reinstalling Lilo.

Personally, I've never had any luck with the automatic Lilo installation; if that's what you tried, this time try the "expert" install, making sure it doesn't entice you into skipping any of the steps. If you don't pay attention, you can get about half-way through and think you are done.
 
Old 09-18-2016, 02:06 PM   #3
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
This is the first time in my 19 years of running linux (Red Hat-4to 7, then Slackware-8.0 to 14.2) that a distribution upgrade failed.

I booted using hugemp.s /dev/sda1 rdinit= ro then ran mkinitrd again, checked /etc/lilo.conf, ran /sbin/lilo and stll no LILO screen. Re-installed lilo off the 14.2 disk, re-ran /sbin/lilo, rebooted, and still no screen.

Very strange. I guess my only option is to do a complete installation rather than an upgrade. This notebook is used for e-mail and Web access, note taking at meetings, and reading PDF files when I don't need the power and applications of my Dell E5410 laptop so I lose only time by installing.

I'll wait until later today (or tomorrow) to see if anyone has a suggestion that can fix this problem

Thanks,

Rich
 
Old 09-18-2016, 02:08 PM   #4
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
frankbell:

Re-reading your message I see what's different from what I just tried. I'll follow your suggeston and report on results.

Rich
 
Old 09-18-2016, 02:20 PM   #5
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
Tried using the Configure option in setup, but I'm not allowed to do this. I press 'C' (or move down until the Configure option is highlighted) and press the [Enter] key. The selection jumps back to the top.

I also tried the Install software option but was denied until I set up the target and source partitions.

Rich
 
Old 09-18-2016, 04:16 PM   #6
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
OK. The hard drive died. Three kernel panics trying to boot from the distribution DVD. Time for a replacement.

Rich
 
Old 11-20-2016, 07:44 PM   #7
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
Replaced the hard drive with an SSD and today did a complete 32-bit installation off the DVD. When the distribution is fully installed and I'm offered the opportunity to reboot, I do so. But, there's no lilo screen visible, only the cursor in the upper left corner.

I did a complete re-installation with the same result: no lilo screen.

This machine had no issues with 14.1 and I need ideas of how to determine the source of the problem.

Rich
 
Old 11-21-2016, 08:19 AM   #8
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
I thought the problem was caused by the wrong screen resolution so I booted from the install disk, mounted /dev/sda1 on /mnt and looked at /etc/lilo.conf. It shows vga=normal so apparently screen resolution is not the issue.

The Dell Latitude 2100 spec sheet shows native screen resolution to be 1024x578 and that's not available as a selection during configuration. (BTW, I cannot run setup then skip to 'configure your system.' The installation insists on starting from the top and working down.

All ideas on diagnosing the source of this issue are needed.

Rich
 
Old 11-21-2016, 09:02 AM   #9
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
Just did another complete re-installation accepting all defaults. Still no lilo screen.
 
Old 11-21-2016, 09:29 AM   #10
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
I think I found the source of the problem. I had not checked the Dell specs for this unit before purchasing a 120G SSD to replace the failed 80G hard drive. The specs tell me that while this unit will support a 5400 RPM hard drive up to 250G, it supports only a 16G SSD. I've no idea why; I thought it had a higher SSD capacity.

Rich
 
Old 11-21-2016, 06:43 PM   #11
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
My last post was incorrect. The chipset in the Latitude 2100 will support larger SSDs; the limit shown in the Dell specs was likely the largest that they sold back then.

I'm still looking for advice on how to determine why the lilo screen does not display after the POST completes.
 
Old 11-21-2016, 07:17 PM   #12
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Have you tried using nomodeset in your appends line?
 
Old 11-22-2016, 09:48 AM   #13
rshepard
Member
 
Registered: Oct 2007
Location: Troutdale, Oregon
Distribution: Slackware
Posts: 435

Original Poster
Rep: Reputation: 28
Quote:
Originally Posted by bassmadrigal View Post
Have you tried using nomodeset in your appends line?
No, I hadn't.

I just re-installed 14.2 and at the end I did not specify an option to add to the kernel, then selected to go to a shell rather than reboot. When I cd'd to /etc/ I discovered there is no lilo.conf file, only lilo-error.32054. I thought I could add nomodeset to lilo.conf, run /sbin/lilo, then reboot.

Perhaps the missing /etc/lilo.conf is causing the problem. If it's not present when the installation is complete, when is it created? Before, I'd just reboot an upgraded or new installation without any problems.

Will try once more re-installing, then adding nomodeset to the kernel when offered the opportunity to do so.

Thanks,

Rich
 
Old 11-22-2016, 10:21 AM   #14
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
I'm not terribly familiar with innards of the install process, but I believe it is created when doing the lilo portion in the setup wizard after installation has completed (but before the installer actually exits... this is the same timeframe that network config, timezone config, etc are done).

But the error file might give a bit more of an indication on what is going on. Is it a text file that you can view?

Are you by chance running a newer system with UEFI? Maybe there is something going on with it that is causing your lilo issue. If you are running a UEFI-based system, you need to make sure you're running legacy (or mixed) mode to emulate BIOS support, or you'll need to switch to a UEFI-capable boot manager, since lilo doesn't support UEFI booting (elilo is used by default in Slackware, but it also includes grub2 -- both of which support UEFI).
 
Old 11-22-2016, 10:41 AM   #15
TracyTiger
Member
 
Registered: Apr 2011
Location: California, USA
Distribution: Slackware
Posts: 528

Rep: Reputation: 273Reputation: 273Reputation: 273
Quote:
Originally Posted by rshepard View Post
When I cd'd to /etc/ I discovered there is no lilo.conf file, only lilo-error.32054. I thought I could add nomodeset to lilo.conf, run /sbin/lilo, then reboot.
Before a reboot when installing Slackware, try looking in /mnt/etc which is where the new system should have been installed.

When running lilo a second time you may have to use the -C option to point to the desired configuration file in /mnt/etc.

Last edited by TracyTiger; 11-22-2016 at 10:43 AM.
 
  


Reply

Tags
14.2, boot failure, no lilo screen



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] Kernel 4.4.14 too big for lilo 24.0: upgrade lilo and run it before rebooting. Didier Spaier Slackware 12 06-27-2016 02:42 AM
[SOLVED] re-install lilo - 64-bit system and a 32-bit installer? tuubaaku Slackware 14 08-04-2015 07:48 PM
Stuck between 32 bit DVD & 64 bit installed partitions w/phone Internet - upgrade fai offplanet Slackware - Installation 4 07-13-2015 07:09 AM
[SOLVED] LILO confusion when both 64-Bit and 32-Bit Slackware are installed luvr Slackware 5 09-10-2012 11:27 AM
LXer: Upgrade from 32-bit to 64-bit Fedora Linux without a system reinstall LXer Syndicated Linux News 0 01-11-2008 09:42 PM

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

All times are GMT -5. The time now is 04:21 PM.

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