Hello again, cosmoswang. Yes I am quite aware of what "No Screens found" Fatal Server Error means as I used to have a nasty HD TV for a monitor with a garbage EDID which required "etc/X11/xorg.conf" to specifically declare what the monitor could and could not do. I had tried modeline calculations, attempting to force native resolution only, and many other methods to solve either the "no screens" error or fonts literally 4 inches tall.
The point is xorg.conf may not
generally be required but it can really come to the rescue if any of the hardware (and often, the culprit is the monitor) is "hinky". Similarly lilo has great powers and quirkiness, too. I find that systems employing grub I must use "nomodeset" for best results but just the opposite for lilo. I just try to lock it down to something I KNOW will work. Here's the pertinent part of my "etc/lilo.conf". Note that I have my UEFI mobo in Legacy mode so I don't need eLilo.
Code:
# Start LILO global section
boot = /dev/sda
###added to stop annoying warning
lba32
###
#compact # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/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 = "video=640x480"
prompt
#timeout = 300
# Normal VGA console
vga = normal
######
# End LILO global section
# Linux bootable partition config begins
#####
image = /boot/vmlinuz-custom-3.12
root = /dev/sda9
label = Slack14-13.12
read-only ##
In my case my xorg.conf file is only hardcore in that I specify exact horiz and Vert refresh rates
Code:
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "VIZ M322i-B1"
HorizSync 31.0 - 80.0
VertRefresh 56.0 - 76.0
EndSection
In fact I forgot to take out the EDIDDpi refusal needed for my old troublesome HDTV monitor
Code:
Section "Device"
Identifier "Card1"
Driver "nvidia"
Option "UseEDIDDpi" "False"
BusID "PCI:1:0:0"
EndSection
But it works properly so just didn't bother. Hopefully by watching your logs and researching/playing with lilo.conf and xorg.conf you will soon discover what is the deal breaker for a workable screen. Your idea about UEFI has merit as well. Do I understand correctly that you had this board working before with lilo instead of eLilo? If that is the case you must be set to legacy mode and need to go back to plain ol' lilo.
