Not only grub but also lilo is being effected, that is if you are using
lilo and lilo.conf look at my lilo.conf. good think I saw it before I
reboot the system (SuSE 10.2):
# Modified by YaST2. Last modification on Thu Nov 8 09:15:38 EST 2007
menu-scheme = Wb:kw:Wb:Wb
timeout = 600
lba32
change-rules
reset
read-only
prompt
restricted
password
default =
Uncaught_exception_from_user_code:__Cannot_open_/dev/tty_for_read_at_/usr/lib/YaST2/servers_non_y2/ag_tty_line_79__at_/usr/lib/perl5/vendor_perl/5.8.8/i586-linux-thread-multi/Term/ReadLine/Gnu.pm_line_240__Term::ReadLine::Gnu::new('Term::ReadLine',_'Simple_Readline_interface')_called_at_/usr/lib/YaST2/servers_non_y2/ag_tty_line_79
message = /boot/message
boot = /dev/sda
image = /boot/vmlinuz-2.6.18.8-0.7-default
###Don't change this comment - YaST2 identifier: Original name: linux###
label = Uncaught_ex
append = " splash=silent showopts"
vga = 0x317
initrd = /boot/initrd-2.6.18.8-0.7-default
root = /dev/sda1
image = /boot/vmlinuz-2.6.18.8-0.7-default
###Don't change this comment - YaST2 identifier: Original name: failsafe###
label = Failsafe
append = "showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0
edd=off 3"
vga = 0x317
initrd = /boot/initrd-2.6.18.8-0.7-default
root = /dev/sda1
eddie wrote:
On Thursday 08 November 2007 21:54:06 Jeff Mahoney wrote:
Jeff Mahoney wrote:
Randall R Schulz wrote:
On Thursday 08 November 2007 13:20, Marcus Meissner wrote:
...
What is causing this and how can I fix it?
What is in /boot/grub/devices.map ? Is /dev/sdb listed there as hd0?
2635# pwd
/boot/grub
2636#
2636# ll
total 312
-rw-r--r-- 1 root root 10 2007-03-05 12:13 default
-rw------- 1 root root 0 2007-10-18 12:18 device.map
-rw------- 1 root root 0 2007-10-18 12:17 device.map.old
-rw-r--r-- 1 root root 7576 2007-09-21 14:59 e2fs_stage1_5
-rw-r--r-- 1 root root 7424 2007-09-21 14:59 fat_stage1_5
-rw-r--r-- 1 root root 6664 2007-09-21 14:59 ffs_stage1_5
-rw-r--r-- 1 root root 6656 2007-09-21 14:59 iso9660_stage1_5
-rw-r--r-- 1 root root 8128 2007-09-21 14:59 jfs_stage1_5
-rw------- 1 root root 1632 2007-11-08 11:16 menu.lst
-rw------- 1 root root 1280 2007-11-08 10:28 menu.lst.old
-rw-r--r-- 1 root root 6844 2007-09-21 14:59 minix_stage1_5
-rw-r--r-- 1 root root 9160 2007-09-21 14:59 reiserfs_stage1_5
-rw-r--r-- 1 root root 512 2007-09-21 14:59 stage1
-rw-r--r-- 1 root root 103162 2007-10-18 10:55 stage2
-rw-r--r-- 1 root root 104042 2006-12-07 20:01 stage2.old
-rw-r--r-- 1 root root 7004 2007-09-21 14:59 ufs2_stage1_5
-rw-r--r-- 1 root root 6228 2007-09-21 14:59 vstafs_stage1_5
-rw-r--r-- 1 root root 8820 2007-09-21 14:59 xfs_stage1_5
I'm gonna' say "no."
Did I mention that the upgrade process bombed when it came time to
install the boot loader and I had to patch it manually??
I guess I can use my 10.0 "device.map" file as a pattern for creating
one for the 10.3 system?
-==--==--=device.map{=--==--==-
(hd1) /dev/sdd
(fd0) /dev/fd0
(hd3) /dev/sda
(hd2) /dev/sdc
(hd0) /dev/sdb
-==--==--=}device.map=--==--==-
Not that I'm afraid of editing "device.map" myself (I've been fixing /
munging "menu.lst"), but is there a way using the openSUSE
administrative tools to repair such damage?
Can you file a bug report for this? The important bit is that device.map
is empty and perl-Bootloader isn't coming up with a sane default.
Actually, two bug reports. One against the installation component, and
the other against the kernel component. It's not a kernel bug, but part
of the process. I'll route it through to the perl-Bootloader maintainer.
-Jeff
--
Jeff Mahoney
SUSE Labs
Glad to see this is finally getting some attention. I put this to the list
when 10.3 first came out (IIRC) and I upgraded my computer but I didn't get a
response and have been manually fixing menu.lst. This morning having done
the kernel upgrade, I've had to edit menu.lst again. I was thinking that I
was the only person in the world with this problem. :-(
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
