Slackware boots to "Verifying DMI Data Pool ........ L99 99 99 99 99 99 99 99 99..."
Hello, I have chosen to install Slackware Linux in order to make myself learn more about it. After the first install I rebooted, and the computer stopped at this message. I read on the Slackware installation FAQ that this was normal because the kernel used for installation was bare bones. I started up off of the install DVD and managed to boot into the system by typing
huge.s root=/dev/sda2 rdinit= ro at the boot: prompt
At that point I logged in as root and recompiled the kernal following the instructions here: http://www.slackbook.org/html/system...on-kernel.html Then I rebooted and still had the same results. I configured the kernel to not do anything with SMP as I thought that was the problem (and thus why huge.s worked).
I'm trying to install 13.1
The system I'm trying to do it with has an athlon xp 1600+ and 2 gigs of ram.
Should I switch the system to huge.s permanently (is that possible?) or should I look up how to configure the kernel the best way for this cpu (or would that information even exist for a cpu this old and a distro version this new?)
I'm kind of a newb at some of this stuff but really *really* want to pick it apart and know as much or more than anyone at work, its seems to be just a matter of finding a piece of thread to start unraveling the sweater with. I know how to use vi, chmod, and some other basic things. Anyway, thanks in advance for any help/advice.
From 'man lilo':
Here is a recent post describing how to fix this.
You may also have to edit /etc/lilo.conf so that lilo runs without error.
Thank you for the reply.
I tried the first suggestion of running liloconfig, then I tried removing lilo and installing grub as suggested. Both left with me with the same results. In the thread you linked the guy says that he just ended up installing grub from another live cd. I have a few guesses
-1 This is something to do with the hardware being so old and not being supported or not supported without knowing how to really dial configurations in for such hardware.
-2 The 9s aren't from a LILO error but from something else since they still persist when LILO is gone and grub has been installed..unless grub has error codes that are exactly the same or those instructions do not really remove lilo and install grub all the way.
That note is pretty old and doesn't really apply anymore. There are no SCSI-specific images in 13.1 (and haven't been since...11.0?). The only kernels you'll find (assuming you're using 32-bit Slackware) are huge.s and hugesmp.s on the install CD/DVD (and you should use hugesmp.s where possible even if you do not have an SMP-capable kernel), and huge/huge-smp/generic/generic-smp kernels on the installed system (assuming you installed all kernels). Again you should use an SMP-capable kernel wherever possible, and preferably the generic-smp kernel (which requires creating an initrd):
Alright, so after booting up from the cd and configuring alpine with gmail (which is totally aweseome..here's the link if anyone wants http://groups.google.com/group/comp....67c10336?pli=1) here is my lilo.conf and fstab
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/sda2
#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:
timeout = 300
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# VESA framebuffer console @ 1024x768x32k
# VESA framebuffer console @ 1024x768x256
# VESA framebuffer console @ 800x600x64k
# VESA framebuffer console @ 800x600x32k
# VESA framebuffer console @ 800x600x256
# VESA framebuffer console @ 640x480x64k
# VESA framebuffer console @ 640x480x32k
# VESA framebuffer console @ 640x480x256
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda2
label = Slackware
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
/dev/sda1 swap swap defaults 0 0
/dev/sda2 / ext4 defaults 1 1
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
You've installed LILO to the root partition of your Slackware install instead of to the MBR, so I *think* the problem is that it never gets to LILO in the first place. Unless you have a good reason not to, you should change the "boot = /dev/sda2" line near the top of your lilo.conf to "boot = /dev/sda" and rerun `lilo` as root to write to the MBR. If you really don't want to write to the MBR then you would have to mark sda2 as bootable (I think) so your BIOS will pass off to that partition by default.
In the setup I've tried specifying to install on the slackware partition and on the MBR and it fails both ways. I'll change it manually tonight though like you suggest and see what happens.
|All times are GMT -5. The time now is 10:15 AM.|