LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-24-2006, 11:30 AM   #1
b3rx
Member
 
Registered: Mar 2006
Distribution: Slackware 13.0
Posts: 75

Rep: Reputation: 15
lilo problem after installing new kernel


i have just installed a new kernel (2.6.16.20) from the slackware ftp site. at first i was able to edit the lilo.conf.. so now there are 3 items in my lilo.conf

1. windows
2. LINUX
3. LNX261620

saved the changes and run lilo.. [no problems here yet]

i tried rebooting my system and tried booting using the new kernel... no problems or whatsoever. so i decided to delete the lilo entry of my old kernel. and this is where the problem begins. after editing lilo.conf and save the changes, i tried running lilo again and this is the error i received.

Code:
Warning: '/proc/partitions' does not match '/dev' directory structure.
    Name change: '/dev/hdd2' -> '/dev/hdd2'
part_nowrite check:: No such file or directory
i thought it was just a warning message and thought that the changes were made. i tried rebooting my system and sad to say that the there are still 3 items in my lilo.

anyone knows why this happend? any solutions?

cheers!

b3rx
 
Old 06-24-2006, 11:40 AM   #2
shadowz
LQ Newbie
 
Registered: Jun 2006
Distribution: Ubuntu 6.06
Posts: 15

Rep: Reputation: 0
lilo wont change until the config file has no errors. look like u need to change something in there before u can get rid of the third entry
 
Old 06-24-2006, 12:01 PM   #3
jimX86
Member
 
Registered: Mar 2006
Distribution: Slackware64 14.1
Posts: 231
Blog Entries: 1

Rep: Reputation: 34
Maybe you should post /etc/lilo.conf to see if anyone notices anything. Also, are all the partitions on the same drive?

It looks to me like there might be two separate problems. I think the first one is non-fatal, but you might try adding "append=devfs=mount" to lilo.conf to see if that fixes error #1.
 
Old 06-24-2006, 06:29 PM   #4
evilDagmar
Member
 
Registered: Mar 2005
Location: Right behind you.
Distribution: NBG, then randomed.
Posts: 480

Rep: Reputation: 31
AFAIK that message means that lilo is getting miffed about /dev/hdd2 being referenced when it doesn't actually exist. Post your lilo.conf.
 
Old 06-24-2006, 11:30 PM   #5
b3rx
Member
 
Registered: Mar 2006
Distribution: Slackware 13.0
Posts: 75

Original Poster
Rep: Reputation: 15
hi guys thanks for the replies.. here is my lilo.conf and yes all the partition are in the same drive.

Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hdc
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# 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
# End LILO global section
# Windows bootable partition config begins
other = /dev/hdc1
  label = Windows
  table = /dev/hdc
# Windows bootable partition config ends

# Linux bootable partition config begins
#image = /boot/vmlinuz
#  root = /dev/hdc3
#  label = Linux
#  read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.16.20
  initrd = /boot/initrd.gz
  root = /dev/hdc3
  label = Linux
  read-only
# Linux bootable partition config ends
 
Old 06-25-2006, 12:35 AM   #6
cereal83
Member
 
Registered: Feb 2004
Location: Canada
Distribution: Slackware
Posts: 478

Rep: Reputation: 30
Thats what your lilo looks like for slackware? Looks weird mine is just

Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sdb
#compact        # faster, but won't work on all systems.
#prompt
#timeout = 50
# 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/sdb2
  label = Linux
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
 
Old 06-25-2006, 12:40 AM   #7
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Rep: Reputation: 65
You were saying '/dev/hdd2' in your original post, and lilo.conf is showing '/dev/hdc3'

Which is it?

How about posting the output of 'fdisk -l'
 
Old 06-25-2006, 05:48 AM   #8
b3rx
Member
 
Registered: Mar 2006
Distribution: Slackware 13.0
Posts: 75

Original Poster
Rep: Reputation: 15
yeah i know.. thats why im confused.. my boot partition is /dev/hdc for windows and /dev/hdc3 for linux.. i dont know here does lilo get that hdd error thing..

here is my fdisk -l result

Code:
root@zu:/home/b3rx# fdisk -l

Disk /dev/hdc: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1   *           1        2550    20482843+   7  HPFS/NTFS
/dev/hdc2            2551        2613      506047+  82  Linux swap
/dev/hdc3            2614        4865    18089190   83  Linux

Disk /dev/hdd: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdd1               1        3825    30724281    c  W95 FAT32 (LBA)
/dev/hdd2            3826        9729    47423880    f  W95 Ext'd (LBA)
/dev/hdd5            3826        7650    30724281    b  W95 FAT32
/dev/hdd6            7651        9729    16699536    b  W95 FAT32
 
Old 06-25-2006, 09:59 AM   #9
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 52
did you already retry to run lilo ?

"'/proc/partitions' does not match '/dev' directory structure."
....might be gone after a reboot.

egag
 
Old 06-25-2006, 01:55 PM   #10
jimX86
Member
 
Registered: Mar 2006
Distribution: Slackware64 14.1
Posts: 231
Blog Entries: 1

Rep: Reputation: 34
The only thing I can think of is that lilo was written to the MBR on /dev/hdd and that /dev/hdd is controlling the boot. That would explain both the error message and the unchanged lilo menu.

I'm at a loss to explain how that would have happened though. Were there any other changes to the system before rerunning lilo last?
 
Old 06-25-2006, 02:19 PM   #11
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Rep: Reputation: 65
Quote:
Originally Posted by jimX86
The only thing I can think of is that lilo was written to the MBR on /dev/hdd and that /dev/hdd is controlling the boot. That would explain both the error message and the unchanged lilo menu.
Bingo. Glad you saw that...My brain is getting old....

You should have lilo install to the MBR of /dev/hdc (first hdd boot device)
 
Old 06-25-2006, 02:51 PM   #12
jimX86
Member
 
Registered: Mar 2006
Distribution: Slackware64 14.1
Posts: 231
Blog Entries: 1

Rep: Reputation: 34
Quote:
Originally Posted by cwwilson721
You should have lilo install to the MBR of /dev/hdc
Yes, but shouldn't his current lilo.conf already be writing it to /dev/hdc? I'm not sure I understand why that isn't working.

Maybe the BIOS is set to boot from /dev/hdd? Or would pointing the current lilo.conf to boot from /dev/hdd solve this? Why did it work before? I'm afraid I still have more questions than answers...
 
Old 06-25-2006, 02:54 PM   #13
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Rep: Reputation: 65
it might, it might not.

May want to run liloconfig again, use expert mode, follow the prompts, and install to mbr of hdc. Then, after a succesfull boot, add in the other partitions.
 
Old 06-25-2006, 03:52 PM   #14
b3rx
Member
 
Registered: Mar 2006
Distribution: Slackware 13.0
Posts: 75

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by cwwilson721
it might, it might not.

May want to run liloconfig again, use expert mode, follow the prompts, and install to mbr of hdc. Then, after a succesfull boot, add in the other partitions.
i have tried what you have suggested but i when i started intalling lilo again. it has error.. and when i tried to manually edit lilo and not using the liloconfig and tried to run lilo again. same error regarding the hdd2 partition.

yes, i have lilo installed at the MBR of hdc dont know whats causing me the problem. should i switch to GRUB?
 
Old 06-25-2006, 04:02 PM   #15
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 52
do you still get the same error as in post#1 ?
if so, what's the output of "cat /proc/partitions " ?

egag
 
  


Reply

Tags
lilo, liloconf


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
problem installing LILO mandrakelinux Slackware 40 03-22-2006 12:50 PM
Problem installing LILO from YAST jrattner1 Suse/Novell 1 08-06-2005 04:08 AM
How to compile a new kernel *without* installing LILO vharishankar Slackware 20 02-19-2005 03:17 AM
lilo slack/XP kernel problem yocompia Slackware 2 07-17-2003 05:06 PM
Lilo / Kernel Panic problem oulevon Linux - General 1 11-20-2002 08:53 AM


All times are GMT -5. The time now is 03:14 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration