lilo breaks after disable nouveau

Rita G. · 07-04-2016, 06:13 PM

14.2 KDE

after installing nvidia driver, lilo broke.

have to insert slackware usb installer and type at boot prompt:

boot: huge.s root=/dev/sda2 rdinit= ro

so i can login.

anybody know how to fix it?

cwizardone · 07-04-2016, 06:58 PM

Not sure what is happening here... I'm not sure LILO has much to do, if anything, with the Nvidia driver.....
What exactly happens?
Have you tried passing nomodeset to the kernel via LILO when you boot up?
Did you disable nouveau? Usually the nvidia proprietary driver won't install until you blacklist nouveau. An example here,
https://www.linuxquestions.org/quest...3/#post5570251

Rita G. · 07-04-2016, 07:20 PM

that's exactly what i did. i disabled nouveau 1st and the lilo bootloader broke and i used my usb slackware 14.2 installer with
boot: hugesmp.s root=/dev/hda1 rdinit= ro
to boot up & login. then installed the downloaded nvidia driver and lilo is still broke.

cwizardone · 07-04-2016, 08:57 PM

What card (gpu) and driver version are you trying to install?

Here is the applicable part of my lilo.conf:

Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda

#compact # faster, but won't work on all systems.

# 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
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Append any additional kernel parameters:
append="iommu=noapeture vt.default_utf8=0"
prompt
#timeout = 300
# VESA framebuffer console @ 1024x768x256
#vga = 773
# Normal VGA console
#vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins....

Like I said, I don't see where the Nvidia driver is involved.

Edit in: Of course, as you know, when you make any changes to lilo.conf you have to re-run, lilo.

Rita G. · 07-04-2016, 10:31 PM

i'm going to re-install 14.2 and report back.

Rita G. · 07-04-2016, 11:03 PM

just logged into fresh 14.2 KDE @11:58pm & going to disable nouveau per https://www.linuxquestions.org/quest...3/#post5570251

Rita G. · 07-04-2016, 11:21 PM

disabled nouveau and rebooted. lilo began to boot & died about 5 seconds into boot sequence. so, it has nothing to do with nvidia driver (i didn't download one this time).
had to reboot with slackware 14.2 usb installer using
boot: huge.s root=/dev/sda2 rdinit= ro
to boot & login again.

cwizardone · 07-04-2016, 11:39 PM

It has been a while.......
Somewhere along the way I found I could no longer pick the higher resolution display for lilo when sitting it up as part of the installation, that is, the VESA section as shown in post #4, above.
To get around that, without having to do a re-install, .... it has been a while so I don't remember exactly how it is done, but IIRC, when the lilo splash screen comes up, you hit the tab key? Then enter, nomodeset
and continue to boot the system.
To avoid that since, I have just selected the 'safe' resolution in the LILO setup.

elcore · 07-05-2016, 12:44 AM

Code:

#nouveau framebuffer: [no blacklist, no binary driver, needs firmware if monitor can't pass edid]
 video=nouveaufb:1680x1050-32@60 drm_kms_helper.edid_firmware=edid/1680x1050.bin
#vesa framebuffer: [blacklist nouveau]
 video=vesafb:1024x768
#vesa vga: [blacklist nouveau]
 vga=normal nomodeset

I use these depending on the driver and the chip, sometimes works with vesafb + nvidia X driver, but vga=normal is recommended by nvidia.
This is because if X crashed, nvidia module can fall off the bus and lose signal while failing to reload X driver on top of fb driver.
Note that recent binary drivers aim to provide DRM interface for the fb driver, they do not provide fb driver yet.

RadicalDreamer · 07-05-2016, 07:42 AM

I updated lilo quite a bit lately screwing around with my laptop. Did you load your slackware install partition with the usb disk? You can mount it later and use the lilo.conf file in /etc. You can play with lilo by editing the file and then in liloconfig menu select expert and then reinstall to read the lilo.config in /etc and try again.

What nvidia card driver version are you using? I got the legacy ones working off of slackbuild.

Rita G. · 07-05-2016, 02:37 PM

ok, at lilo prompt, i choose Linux (dual boot) and press tab, then type Linux nomodeset. . . and that will bring me all the way to login prompt without blacking out.