In my slackware 10.2 , I tried to install 2.6.17.11 kernel.
I did the menuconfig and copied the bzImage file to /boot/bzImage and edited lilo.conf

The present lilo file is:

"
boot="/dev/hdb6"
image="/boot/bzimage-2.6.17.11"
root="/dev/hdb6"
label="slack_2.6.17.11"
read-only

image="/boot/vmlinuz"
label="Slackware_10.2"
root="/dev/hdb6"
read-only

"

I ran the lilo command which returned no errors.

When I rebooted, I get the following error msg:

"
VFS: Can not open root device "346" or unknown block (3,70)

Please appen a correct "root=" boot option

Kernel panic - not syncing:VFS:

Unable to mount root fs on unknown block
(3,70)
"

Kindly guide me where I am wrong.

Do you need an initrd ?

I.e. did you make something essential at boottime (like the root file system) as a module rather than compiling into the kernel.

No.
Even then I tried mkinitrd and copied it to /boot.
Still the problem persists.

You need to get a bootable kernel as a benchmark and work up from there.

Can you boot anything from /dev/hdb6? Sounds like it's not near the beginning of the drive. there was that old problem with the 1024M limit which was fixed with the 'lba32' entry in lilo.

Can you take the test 2.6 from cd #2, compile it just as it is, and boot with it? (if you have reiserfs as root fs it needs an initrd for sure)

HTH

The default installation boots from /dev/hdb6 only and it works fine.
Anyhow I'll try to use the 2.6 kernel from slack cd and post the results.

I had this problem
try enabling ramdisk suport
with make menuconfig
youll find it under device driver then block devices then enable ramdisk support

I had the same problem. It was because I had not selected the correct IDE chipset support during make menuconfig. I just got careless.

Look in ATA/ATAPI/MFM/RLL Support and make sure your chipset driver is getting built in.

TP11235/sooty !

I have done what you both have told.
Still he problem persists.

I am compiling the kernel once more (final, of course !) and let you know the results soon.

At last partial success!

I could boot in the new kernel and get upto CLI.
But the startx command gives the following error:

"
(EE): GARTInit : Unable to open /dev/agpgart
No such device
(EE): I 810 (0) : AGPGART support is not available.
Make sure your kernel has agpgart support or that agpgart kernel module is loaded

(EE): Screen(s) found but none have a usable configuration.
"

Let me try to recompile the kernel once more!

I have now the 2.6.17.11 kernel working.
One last thing is that I have to correct the eth0 so that I could connect to the net.
I hope I could do this shortly.

Ok good to hear it!

did you chose for your .config the right drivers for your ethernet card chipset?
if so, then u have to know what to do in order to connect. in my case is.

ifconfig eth0 up; dhcpcd eth0

no pass no username..

Just one step short of 100 % success.
I could not get my adsl modem working.
I checked to enable Realtek RTL 8139 but still no success.
The pppoe-setup command gives no error.
But on pppoe-start, the modem does not blink at all and I get the time-out error.