Hi all,

Odd problem with Lilo having re-complied my kernel to 2.6.11.11.

I am running Lilo 22.5.9 that came packaged with Slackware 10.1. Having setup my system using the stock 2.4.29 kernel that comes with Slackware i downloaded 2.6.11.11 from kernel.org and configured it. Having added the needed lines to lilo.conf i typed lilo - and saw what i expected - it added the new boot option in.

Rebooted the system, selected my new kernel and it boots fine. Now if i use the lilo command while running 2.6.11.11 i get the following:

'part_nowrite: read: : Input/output error'

However, if i boot back into my old stock kernel it works fine. Thought at first it was a problem with lilo however if this was the case i cant explain it working under the old kernel and not the new.

Having done some reading on other peoples findings on this I see some suggestion that its down to a partitioning issue. My system has 2 160gb SATA disks, sda and sdb - sda simply as a swap and a root partition, sdb is currently not in use and is not being mounted.

Any ideas?

Thanks,

Grimm

post ur lilo.conf here
also u can follow this thread

http://www.experts-exchange.com/Oper..._20871000.html

till the end

regards

Hi,

Lilo.conf as folows:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# 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
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking

image = /boot/bzImage
root = /dev/sda1
label = Experimental
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

Having a read through that artical now.

Thanks,

Grimm.

Hi again,

Have managed to resolve this now. Problem was basically a second HDD in the system that wasnt partitioned / formatted / mounted correctly. Having sorted that it works fine.

Thanks for your help.

Grimm

did u try as that article mentioned?

also post the O/p of

fdisk /dev/sda

regards

masand,

how can you read that article ?
i have to sign-up and pay to see that answer...
( well...they say so )

egag

egag, scroll down the page, the answer is marked as
' Accepted Answer' in an user comment

thanks keefaz

egag

thanks for answering that

also i mentioned in my first post

read till the end............

regards

well....it sais on that page " sign up to see this solution ".
not " solution below ".

ah...i guess i also didn't read your post till the end

egag