Sorry, maybe there's a post like this one, but i looked all over the forums (it took me like 2 hrs o less) and I didn't find a problem like this....

I use Slackware 10.0 which i boot from the Instalation CD, that means i have LILO installed at the Super Block and instead of the Master Boot Record, beacuse if i do that, when i try to boot Windows Xp (Home Ed SP 1) it boots the "System REcovery Utility" instead of the System itself... if i boot linux it boots perfectly... so i installed it (Linux) in a diferent Hard Drive and installed LILO at the Super Block instead of the Master Boot Record... it worked well but when i compliled a new Kernel... i used 2.4.20 and i upgraded to 2.6.12, so after making all the compiling stuff, i reboot and it stills boots with the 2.4.20 Kernel, then i run the "LILO" comand and i get an error like this:

#: LILO
Warning: /dev/hdd1 is no on the first disk
Added Windows *
Added Slack-2.6.12
#:

i want to know if i can fix the problem, or that the problem is that i have LILO installed at the Super Block instead of the Master Boot Record...

thanks a lot, and if there is a post like this, post the URL here... thanks...

First, there is really no reason to use the install CD to boot Slackware. If installing Lilo to the super block works best for you, then by all means do it that way. As a side note, that is the safest way to do it anyway. But you can use Windows XP's bootmanager to boot it vs the CD.

Your best bet is to follow the info in the SLackware book at http://www.slackware.com/book/index....ce=x1776.html. If you'll scroll down to the bottom, you'll see a section called Windows NT. Follow those insrtuctions to get XP's bootmanager to boot Slackware.

Second, you'll need to post your lilo.conf before we can be of much specific help. However, I noticed that you apparently have a listing for Windows in your lilo.conf, ie "Added Windows *". There is no need for this since you are not using lilo to boot Windows.

As to how to get the new kernel booting. You'll need to edit your lilo.conf file, move the kernel files to boot, and then re-run lilo. You'll then need to reobtain an image of the boot sector and move that to your windows partition if you want XP's bootloader to boot it. You get the image by running something like this after running lilo:
That command will need to be modified to suit your situation though, if Slackware isn't on hda2. You'll also need to copy the resulting file, /tmp/bootsect.lnx, to the Windows parition someway. If it's an NTFS partition, then the best way is to use a floppy.

thanks a lot for your reply DaHammer, i'll post the Lilo.conf as soon as i get to my house (i'm replying from school actually ) but as soon as i get to my computer i'll post my Lilo.conf... thanks a lot

i did what DaHammer told me... but when Windows boots Slack, it comes with this..

Slackware 2.6.12.1 Selected
Bioscheck Completed
Ok... Booting Kernel...

ok, those aren't the exact messages that come out... but if you boot Slack with windows, you will see them on every computer.. my pc FREEZES after the "...... Ok Booting Kernel" message. I don't know if the prob has to be with the Kernel Config or with LILO :S... my lilo conf it's like this:

# Slack NEW begins
image = /boot/vmlinuz-2.6.12.1
root = /dev/hdd1
label = Slack_2.6.12.1
read-only
# Slack NEW ends
# Slack OLD begins
image = /boot/vmlinuz-old
root = /dev/hdd1
label = Slack_OLD
read-only
# Slack OLD ends

is that enough for you guys to figure out where did i screwed out? please help me here.. if you need more info, just ask for it.. thanks a lot....

Have you tried selecting Slack_OLD? My first thought is that your current problem lies within the way you configured your new kernel. I say that because you appear to be getting to lilo now and lilo appears to find the kernel you select. So that in and of itself means that Windows is loading lilo. That's if I interrupt your above comments correctly. Anyway, here is what you should expect when you boot the PC. The Windows bootloader should appear after your BIOS loads, you should have an option there to boot either Windows or Linux. If you select Linux, then lilo should appear and list your different kernel options to boot with. Is that what's happening?

Also, yeah it would probably help if you posted the entire lilo.conf. Up near the top is a very important setting:
Going by what you posted above, that's what you should have. Note the hdd1 vs hdd. hdd1 instructs lilo to install to the super block of the first partition on that disk. If it were hdd, then it would install to the MBR. I'm sure you have that right though, else you wouldn't have gotten this far. Anyway, you're certain that hdd1 is your linux partition and the one that contains /boot?

here's my Lilo.conf

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hdd1
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x32k
vga = 790
# 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
# End LILO global section
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Slack NEW Begins
image = /boot/vmlinuz-2.6.12.1
label = Slack_2.6.12.1
root = /dev/hdd1
read-only
# Slack NEW Ends
# Slack OLD Begins
image = /boot/vmlinuz-old
root = /dev/hdd1
label = Slack_Old
read-only
# Slack OLD Ends

hope it helps you to get an answer.. thanks you've helped me a lot... xD

Looks fine. As I said above, have tried booting the old kernel?
or else the new one with VGA normal?

i've tried to do that, but it freezes too.... :S i've tried to boot the new kernel and the old one... but none of them boot... they always get stuck after the "...Ok Booting the Kernel" :S... do you think i must reinstall and recompile everything?

every time you run lilo, you'll have to make a new copy of the bootsector ( the dd if=hdd1 of=....etc thing )
and move that to your windos partition.
did you do that the last time ?

egag

In addition to what egag said. It looks like a VESA problem to me, like you left something related to it out of the kernel, which is why I said to try "vga=normal".

Is the old kernel a default slackware kernel or one you've compiled yourself as well? If the latter then you may have to install a default slackware kernel, like the one you use on the boot CD since you know it works, and go from there. But again, the "vga=normal" should at least get you to the point of seeing the kernel bootup process and any errors that occur.

thanks egag i've done that but that didn't solve the problem..........

DaHammer i'll try what you've said about the "VGA=NORMAL" stuff.... and yes... the old Kernel it's the kernel that came with the distro CD... Slackware 2.4.29 and i compiled 2.6.12.1.... so it's the original one... i'll try that option you told me...

hey guys i tried what you told me about the "VGA = NORMAL" but it didn't have any effect on it..... :S the errors stays like i told you.... :S

It's
or
typed in exactly like that. Not VGA = NORMAL or VGA=NORMAL.

man, sorry.. but that didn't work... it still freezes after the "Ok booting Kernel..." stuff.... if you think there's no solution to it, i'll just erase and reinstall.... =S

hey guys.... i reinstalled everything... but when i boot the kernel reboots the computer.... and if i boot the old kernel it boots normally :S