[SOLVED] Upgraded to 13.37 (64bit) from 13.1 (64bit) and Lilo is all 9's.

mpyusko · 05-17-2011, 09:44 PM

Figured I just built a new computer, got it up and running and Pat decides to release a new version. Ugh. Everything installed perfectly except Lilo. After I installed it using the setup script, I rebooted and it came up all 9's (A screen full of "9" "99" or "999" - I can't remember how many were grouped) Anyway.... I think it has something to do with Framebuffer mode, but I can't seem to find one that works. I have an ATI Radeon HD 5670 on a Pentuim Dual-Core @ 3.2GHz. The machine should be perfect for this distro.

Here's the LILO.conf

Code:

bash-4.1$ cat /etc/lilo.conf
# 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/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=" vt.default_utf8=0"
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x64k
vga = ask
# 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
image = /boot/vmlinuz
  root = /dev/sdb6
  label = Linux
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/sda1
  label = WinXP
  table = /dev/sda
# Windows bootable partition config ends
bash-4.1$

The "vga =" statement has been set to many things but no matter what I try I still get 9's (except for once but with no changes and a reboot 9's appeared again). I also get the following errors

Code:

bash-4.1# lilo
Warning: LBA32 addressing assumed
Warning: Unable to determine video adapter in use in the present system.
Warning: The boot sector and map file are on different disks.
Warning: Video adapter does not support VESA BIOS extensions needed for
  display of 256 colors.  Boot loader will fall back to TEXT only operation.
Added Linux *
Added WinXP
4 warnings were issued.
bash-4.1#

Quote:

bash-4.1# lilo -M /dev/sda mbr
/boot/boot.0800 exists - no /dev/sda backup copy made.
The Master Boot Record of /dev/sda has been updated.
bash-4.1#

and neither solves the problem.

Thoughts?

bsdunix · 05-18-2011, 08:01 AM

May not solve your problem, but I recently fixed my LILO framebuffer ATI Radeon HD5450 problem.

allend · 05-18-2011, 09:29 AM

The 99 error is from lilo and occurs when the primary bootloader cannot pass control to your Linux setup.

You have a problem with your lilo.conf. Is the symlink /boot/vmlinuz pointing to the correct kernel?
You do not have an initrd specified, so the symlink should be pointing to vmlinuz-huge-2.6.37.6

Also, use vga=normal. There is a note in CHANGES_AND_HINTS.TXT about this.

The LBA32 addressing assumed warning can be removed by adding 'lba32' in the global section of lilo.conf.

mpyusko · 05-18-2011, 10:31 AM

Quote:

Originally Posted by allend

The 99 error is from lilo and occurs when the primary bootloader cannot pass control to your Linux setup.

You have a problem with your lilo.conf. Is the symlink /boot/vmlinuz pointing to the correct kernel?
You do not have an initrd specified, so the symlink should be pointing to vmlinuz-huge-2.6.37.6

Also, use vga=normal. There is a note in CHANGES_AND_HINTS.TXT about this.

The LBA32 addressing assumed warning can be removed by adding 'lba32' in the global section of lilo.conf.

I tried "vga = normal" and it still filled my screen with 9's. /dev/sda is for winXP (still have a few programs that require it and crash in VirtualBox) /dev/sdb is the 1TB SATA drive devoted to Linux. Lilo gets installed in the sda mbr..... or it's supposed to be anyway.

Code:

login as: root
root@192.168.1.10's password:
Last login: Tue May 17 11:09:11 2011
Linux 2.6.37.6.

Words must be weighed, not counted.

root@wopr:~# cd /boot
root@wopr:/boot# ls -l
total 4893
lrwxrwxrwx  1 root root      37 May 15 18:36 README.initrd -> /usr/doc/mkinitrd-1.4.6/README.initrd
lrwxrwxrwx  1 root root      24 May 17 09:27 System.map -> System.map-huge-2.6.37.6
-rw-r--r--  1 root root 1782099 Apr  9 14:25 System.map-generic-2.6.37.6
-rw-r--r--  1 root root       0 May 18 11:11 System.map-huge-2.6.37.6
-rw-r--r--  1 root root     512 May 17 11:12 boot.0800
-rw-r--r--  1 root root     209 May 16 05:07 boot_message.txt
lrwxrwxrwx  1 root root      20 May 17 09:27 config -> config-huge-2.6.37.6
-rw-r--r--  1 root root  112324 Apr  9 14:25 config-generic-2.6.37.6
-rw-r--r--  1 root root       0 May 18 11:11 config-huge-2.6.37.6
-rw-r--r--  1 root root    5040 Mar 27 02:53 diag1.img
-rw-r--r--  1 root root   17932 Mar 27 02:53 diag2.img
drwxr-xr-x 11 root root     544 Dec 19  2009 initrd-tree/
-rw-------  1 root root   92160 May 17 22:33 map
-rw-r--r--  1 root root   15634 Mar 27 01:32 slack.bmp
lrwxrwxrwx  1 root root      21 May 17 09:27 vmlinuz -> vmlinuz-huge-2.6.37.6
-rw-r--r--  1 root root 2956592 Apr  9 14:25 vmlinuz-generic-2.6.37.6
-rw-r--r--  1 root root       0 May 18 11:11 vmlinuz-huge-2.6.37.6
root@wopr:/boot#

allend · 05-18-2011, 11:13 AM

Does the zero size of the vmlinuz-huge-2.6.37.6 file that is pointed to by the vmlinuz symlink give you any clues?
Try reinstalling the huge kernel!

mpyusko · 05-18-2011, 11:50 AM

I suppose that might be a problem. The funny part about that one is I tried that too! Pkgtool in the k folder right?

Edit: DOH! That was the kernel source. Ok, trying again from the a folder. LOL.

mpyusko · 05-18-2011, 12:00 PM

Code:

login as: root
root@192.168.1.10's password:
Last login: Wed May 18 10:58:59 2011 from chicklet.yuskonet.com
Linux 2.6.37.6.

An economist is a man who would marry
Farrah Fawcett-Majors for her money.
root@wopr:~# mc

root@wopr:~/temp# pkgtool



 ┌────────────Slackware Package Tool (pkgtool version 13.37)───────────────┐
 │                                                                         │
 │ Welcome to the Slackware package tool.                                  │
 │                                                                         │
 │ Which option would you like?                                            │
 │ ┌─────────────────────────────────────────────────────────────────────┐ │
 │ │     Current  Install packages from the current directory            │ │
 │ │     Other    Install packages from some other directory             │ │
 │ │     Floppy   Install packages from floppy disks                     │ │
 │ │     Remove   Remove packages that are currently installed           │ │
 │ │     View     View the list of files contained in a package          │ │
 │ │     Setup    Choose Slackware installation scripts to run again     │ │
 │ │     Exit     Exit Pkgtool                                           │ │
 │ └─────────────────────────────────────────────────────────────────────┘ │
 ├─────────────────────────────────────────────────────────────────────────┤
 │                     <  OK  >           <Cancel>                         │
 └─────────────────────────────────────────────────────────────────────────┘




         ┌───Package Name: kernel-firmware-2.6.37.6-noarch-2 ──────┐
         │ kernel-firmware (Firmware installed by the kernel)      │
         │                                                         │
         │ These are the firmware files from the Linux kernel.     │
         │                                                         │
         │ You'll need these to use certain hardware with Linux.   │
         │                                                         │
         │                                                         │
         │                                                         │
         │                                                         │
         │                                                         │
         │                                                         │
         │                                                         │
         │ Size: Compressed: 1005K, uncompressed: 2.3M.            │
         │ ┌─────────────────────────────────────────────────────┐ │
         │ │Yes   Install package kernel-firmware-2.6.37.6-noarch│ │
         │ │No    Do not install package kernel-firmware-2.6.37.6│ │
         │ │Quit  Abort software installation completely         │ │
         │ └─────────────────────────────────────────────────────┘ │
         ├─────────────────────────────────────────────────────────┤
         │               <  OK  >        <Cancel>                  │
         └─────────────────────────────────────────────────────────┘


   ┌──────────Package Name: kernel-generic-2.6.37.6-x86_64-2 ─────────────┐
   │ kernel-generic (a general purpose SMP Linux kernel)                  │
   │                                                                      │
   │ This is a Linux kernel with built-in support for most disk           │
   │ controllers.  To use filesystems, or to load support for a SCSI or   │
   │ other controller, then you'll need to load one or more kernel        │
   │ modules using an initial ramdisk, or initrd.  For more information   │
   │ about creating an initrd, see the README.initrd file in the /boot    │
   │ directory.                                                           │
   │                                                                      │
   │ SMP is "Symmetric multiprocessing", or multiple CPU/core support.    │
   │                                                                      │
   │                                                                      │
   │ Size: Compressed: 3.1M, uncompressed: 4.6M.                          │
   │ ┌──────────────────────────────────────────────────────────────────┐ │
   │ │  Yes   Install package kernel-generic-2.6.37.6-x86_64-2          │ │
   │ │  No    Do not install package kernel-generic-2.6.37.6-x86_64-2   │ │
   │ │  Quit  Abort software installation completely                    │ │
   │ └──────────────────────────────────────────────────────────────────┘ │
   ├──────────────────────────────────────────────────────────────────────┤
   │                     <  OK  >           <Cancel>                      │
   └──────────────────────────────────────────────────────────────────────┘


  ┌─────────────Package Name: kernel-huge-2.6.37.6-x86_64-2 ───────────────┐
  │ kernel-huge (a fully-loaded SMP Linux kernel)                          │
  │                                                                        │
  │ This is a Linux kernel with built-in support for most disk             │
  │ controllers.  If you're looking for a more stripped down kernel        │
  │ (this one contains everything but the kitchen sink ;-), then install   │
  │ the kernel-generic in the /boot directory along with an initrd to      │
  │ load support for your boot device and filesystem.  For instructions    │
  │ on the initrd, see README.initrd in the /boot directory.               │
  │                                                                        │
  │ SMP is "Symmetric multiprocessing", or multiple CPU/core support.      │
  │                                                                        │
  │                                                                        │
  │ Size: Compressed: 6.1M, uncompressed: 8.2M.                            │
  │ ┌────────────────────────────────────────────────────────────────────┐ │
  │ │     Yes   Install package kernel-huge-2.6.37.6-x86_64-2            │ │
  │ │     No    Do not install package kernel-huge-2.6.37.6-x86_64-2     │ │
  │ │     Quit  Abort software installation completely                   │ │
  │ └────────────────────────────────────────────────────────────────────┘ │
  ├────────────────────────────────────────────────────────────────────────┤
  │                     <  OK  >           <Cancel>                        │
  └────────────────────────────────────────────────────────────────────────┘


 ┌────────────Package Name: kernel-modules-2.6.37.6-x86_64-2 ───────────────┐
 │ kernel-modules (Linux kernel modules)                                    │
 │                                                                          │
 │ A kernel module is a piece of object code that can be dynamically        │
 │ loaded into the Linux kernel to provide new kernel functions.  Most of   │
 │ these modules provide support for devices such as CD-ROM drives, tape    │
 │ drives, and ethernet cards.  You can choose which modules to load by     │
 │ editing /etc/rc.d/rc.modules.                                            │
 │                                                                          │
 │                                                                          │
 │                                                                          │
 │                                                                          │
 │                                                                          │
 │ Size: Compressed: 20M, uncompressed: 100M.                               │
 │ ┌──────────────────────────────────────────────────────────────────────┐ │
 │ │    Yes   Install package kernel-modules-2.6.37.6-x86_64-2            │ │
 │ │    No    Do not install package kernel-modules-2.6.37.6-x86_64-2     │ │
 │ │    Quit  Abort software installation completely                      │ │
 │ └──────────────────────────────────────────────────────────────────────┘ │
 ├──────────────────────────────────────────────────────────────────────────┤
 │                       <  OK  >            <Cancel>                       │
 └──────────────────────────────────────────────────────────────────────────┘

root@wopr:~/temp# mc

root@wopr:/boot# clear
root@wopr:/boot# ls -l
total 13389
lrwxrwxrwx  1 root root      37 May 15 18:36 README.initrd -> /usr/doc/mkinitrd-1.4.6/README.initrd
lrwxrwxrwx  1 root root      24 May 18 12:48 System.map -> System.map-huge-2.6.37.6
-rw-r--r--  1 root root 1782099 Apr  9 14:25 System.map-generic-2.6.37.6
-rw-r--r--  1 root root 2706772 Apr  9 23:50 System.map-huge-2.6.37.6
-rw-r--r--  1 root root     512 May 17 11:12 boot.0800
-rw-r--r--  1 root root     209 May 16 05:07 boot_message.txt
lrwxrwxrwx  1 root root      20 May 18 12:48 config -> config-huge-2.6.37.6
-rw-r--r--  1 root root  112324 Apr  9 14:25 config-generic-2.6.37.6
-rw-r--r--  1 root root  112298 Apr  9 23:50 config-huge-2.6.37.6
-rw-r--r--  1 root root    5040 Mar 27 02:53 diag1.img
-rw-r--r--  1 root root   17932 Mar 27 02:53 diag2.img
drwxr-xr-x 11 root root     544 Dec 19  2009 initrd-tree/
-rw-------  1 root root   92160 May 17 22:33 map
-rw-r--r--  1 root root   15634 Mar 27 01:32 slack.bmp
lrwxrwxrwx  1 root root      21 May 18 12:48 vmlinuz -> vmlinuz-huge-2.6.37.6
-rw-r--r--  1 root root 2956592 Apr  9 14:25 vmlinuz-generic-2.6.37.6
-rw-r--r--  1 root root 5866144 Apr  9 23:50 vmlinuz-huge-2.6.37.6
root@wopr:/boot#

Better? Now I just have to wait until I'm in front of it to see if it fixed the problem. (gotta love SSH)

Didier Spaier · 05-18-2011, 12:41 PM

Of course you ran lilo after that

mpyusko · 05-18-2011, 12:57 PM

Quote:

Originally Posted by Didier Spaier

Of course you ran lilo after that

Yes. Just just before I rebooted it. But still all I see is a gazillion 99's.

(edit vga = normal too)

<banging head on desk> I am able to run the system, um, "normally" if I use the 13.37 boot iso: "huge.s root=/dev/sdb6 rdinit= ro" but it still won't boot with LILO.

Darth Vader · 05-18-2011, 01:50 PM

@mpyusko

Man, why you want to install the LILO MBR into SDA, while the boot partition is in another disk, SDB? This setup will never work.

Just, if you don't want to touch the SDA disk, make the SDB bootable as default, from BIOS and install the LILO MBR into SDB. Enjoy!

Didier Spaier · 05-18-2011, 01:53 PM

I would try to put the boot loader on the root linux partition. In your case:
boot=/dev/sdb6

This partition should be made bootable as Darth Vader stated.

mpyusko · 05-18-2011, 03:02 PM

Quote:

Originally Posted by Darth Vader

@mpyusko

Man, why you want to install the LILO MBR into SDA, while the boot partition is in another disk, SDB? This setup will never work.

Just, if you don't want to touch the SDA disk, make the SDB bootable as default, from BIOS and install the LILO MBR into SDB. Enjoy!

I'm pretty sure it worked for 13.1. And I did get it to boot once properly with 13.37, not sure why though. Oh well. I'll try sdb mbr instead. I still need to boot to windows XP though.

BTW: How do I fix sda's MBR now?

mpyusko · 05-20-2011, 10:22 AM

I re-ran the liloconfig script and kept everything the same except I told it to install to /dev/sdb. Now it works. Thanks.

gezley · 05-21-2011, 09:29 PM

Quote:

Originally Posted by mpyusko

BTW: How do I fix sda's MBR now?

Safest thing is to disconnect sdb, and boot from an XP CD. Select R for repair, and type fixmbr. Press Enter, then type Exit and reboot. System should reboot into your XP OS. Reconnect sda and system should reboot into Slackware.
If you don't have a Windows XP CD try this instead. I have never tried it so read instructions carefully beforehand.