LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   [Slackware-64 current] Issue with LILO (Bug Report?) (https://www.linuxquestions.org/questions/slackware-14/%5Bslackware-64-current%5D-issue-with-lilo-bug-report-4175553458/)

metalforever 09-14-2015 09:24 AM

[Slackware-64 current] Issue with LILO (Bug Report?)
 
During my install of Slackware-64 current, I am unaware as to whether any changes have been made recently with LILO - I tried slackware current about two months ago with the same machine and didn't have this issue.

LILO can't detect my graphics card, and wants to revert to text mode during the install of slackware. This in itself is fine, but the generation of lilo.conf in this case leaves syntax errors.

I went in and manually reinstalled LILO. Adjusting the lilo.conf to not include the line having the error (The Windows Line), and LILO installed correctly, leaving a booting system with a Slackware Logo.

I don't have any Windows installs on my machine, but I do have two other hard disks with NTFS partitions, and had a flash drive plugged into the machine during the install that was formatted FAT. I installed from DVD.

Didier Spaier 09-15-2015 06:52 AM

Hi,

just a reminder to folks using -current: keep your system up to date and in that aim, frequently read the ChangeLog for your architecture.

lilo provided for Slackware64-current has last been updated on Sat Feb 21 00:00:27 UTC 2015, so the problem might be caused by some other component.

Also for a bug report to be useful it should include a precise and detailed information about the hardware, the software, the environment and the exact steps taken that triggered the error.

For instance the output of a commands like
Code:

lspci -knn|grep -iA3 vga
lsblk -o model,name,fstype,mountpoint,size,state,uuid

typed during installation just before running lilo could help.

allend 09-15-2015 08:34 AM

From CHANGES_AND_HINTS.TXT
Quote:

Speaking of lilo.conf and KMS, make sure you use either vga=normal or
vga=extended -- some of the framebuffers don't like KMS very much...

metalforever 09-17-2015 01:52 PM

This version of slack -current was the one updated on Sept 8th.

Didier Spaier 09-17-2015 01:55 PM

Quote:

Originally Posted by metalforever (Post 5421803)
This version of slack -current was the one updated on Sept 8th.

Still the information you provided is insufficient to analyze your issue (and even to determine if there is or not a bug). See my previous post.


All times are GMT -5. The time now is 04:34 AM.