i have installed slackware from cd
i take full install and after all i make reboot

and then it start with 999999999999 and so.

what can i do now i have already try to installed new again and reboot but it happend again.

what must i do to help this out.

thank you

You're probably installing the wrong kernel.

Boot from floppy disk, and when done, load ... .. well i forgot the exact link for it, but its on the cd
the 'bare.i' kernel

I think I had something similar happen once. Does the entire screen just fill with 9's?

another thing you could do, if you have an internet connection,

remove all yoru kernels from pkgtool, download the following into a folder
http://slackware.com/pb/searchpkg.ph...&string=kernel

pkgtool (current)
lilo
reboot

I got 40 40 40 40 40 40 so it is a Kernel issue. Be sure the Format you use matches the Kernel. Use Reiserjfs format, then use jfs.s kernel, use Ext2 then use bare.i ir atapiide, use a full scsi subsystem, then use the approprate to match the controller, or the jfs.s.

the Ext3 Journaling file system I believe you would have to use the speak one. I have only been able to make the reisrjfs and jfs.s form work. Hope I am not confusing it.

Ive had this problem once. I could be wrong but i think lilo was not written to mbr correctly. booting from the second cd, chrooting and rerunning lilo shoul fix it.

well i wll say the llo config needs to be set for a header and then add the linux drive, and then setup and installed, it then writes to the drive if your system is setup corretly. Even with a boot disk it will go to panic mode.

I think your correct. That seems like the problem I had as well. Matter of fact, I'm certain of it.

i also think that's the cause.

999999....... is a lilo error message.

post the lilo.conf file,
and thell smth about the system lay-out.
( what disk and partition did you install on; are other os like windoz present ? )

egag

Is this a dual boot machine? I have slack installed with XP as a dual boot and lilo is installed on the slack root partition (the superblock option during the slack install). I've had the 999.... s happen on several occasions, usually after I make changes to lilo.config. I found the easiest solution (using both slack 9.1 and 10) is to grab the first 512 bytes off the slack boot partition again and copy the bootsect.lnx file to the XP root partiton. Just let it overwrite the existing bootsect.lnx. Reboot and you will be a happy slacker once again.

i have installed again with boot ext2 and i take kernel bare-i
i made also diskette boot from this installation
the strange is when i start it happend again with all 9999999

but when i start from diskette he load and slackware start.
but how or what can i do when i wanted start from normal with out diskette.
what can i change or made.

Bascially, you want to install lilo to the MBR. That's effectively what lukameen did, but you can make it one step easier by putting the line 'boot = /dev/hda' (without quotes) at the beginning of /etc/lilo.conf. I know it says during install that this is potentially dangerous, but I've never had a problem with it. Remeber to run the command 'lilo' as root any time you make a change to the lilo.conf file.

If you'd like more detailed help, please post your lilo.conf, or have a look at the lilo.conf man page. There is a very thorough example at the very beginning.

Ok here goes.

Dual Boot system:

Format ext2

Be sure to - Add the Start Header in the Lilo Config - as it says on install, you can start here and leave it blank.

Then after that add the Linux Partition /dev/hdaX, where X=Drive or Partition on HDA

If this is successful then it will move to your graphics and mouse settings. After the screen goes through this it will ask to write to the MBR, let it. Should work without a problem.

thoray, you and i have the same problem, and ive yet to find a fix on my end, ive tried everything this site has had to offer. and still no love. right now, this is the only problem ive had with the slack installation.
for those willing to aid me in a fix for this. here is my lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# 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
# Windows bootable partition config begins
other = /dev/hda1
label = windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb3
label = slack
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

as you will notice, the two OSes are on different disks. but i dont think that should cause a problem, but then again, im as fresh as they come when it comes to linux.

btw, i tried booting off the second disc so i could chroot... and for me, booting off the second disk of slack is not possible 0_o.

You actually would need to boot off the first disc. Not sure why he said second disc.

This lilo.conf looks basically like mine, except that linux is on hdb. I've never tried that, but as far as I know it shouldn't be a problem. One thing that occurs to me is that maybe, somehow, hdb is the master on the ide chain, and not hda, in which case you would want to install to hdb instead of hda.

I've only seen this error once, and it was when I had grub installed and I destroyed the partition where grub.conf was stored. It did exactly the same thing.