[opensuse-factory] Problem booting a new hard drive with openSUSE 10.3

Sid Boyce

1 Dec 2007 1 Dec '07

21:11

# cat /etc/SuSE-release openSUSE 11.0 (X86-64) Alpha0 VERSION = 11.0 1. Used rsync to backup my ext3 320G SATA HD that's getting full to a jfs SATA 500G drive, / and swap on each. 2. Swapped over drive cables so the new one now becomes /dev/sdb and the old one /dev/sdc. /dev/sda is a 250G IDE I use as /ftp and swap. 3. Booted up with the 10.3 x86_64 DVD. # mount /dev/sdb1 /mnt # mount -o bind /dev /mnt/dev # mount -o bind /proc /mnt/proc # mount -o bind /sys /mnt/sys # rm /mnt/etc/mtab* # cp /proc/mounts /mnt/etc/mtab (mtab is 0 bytes) # chroot /mnt /bin/bash # grub-install /dev/sdb (looks good "/ jfs", result "success") # less /etc/fstab /dev/disk/by-id/scsi-SATA_MAXTOR_STM35006_6QG0YKMR-part1 / jfs defaults 1 1 /dev/disk/by-id/scsi-SATA_MAXTOR_STM35006_6QG0YKMR-part2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 /dev/sda1 /ftp ext3 defaults 0 0 From /boot/grub/menu.lst ========================= gfxmenu (hd1,0)/boot/message title 2.6.24-rc3-git5-smp kernel /boot/2.6.24-rc3-git5-smp root=/dev/disk/by-id/scsi-SATA_MAXTOR_STM35006_6QG0YKMR-part1 vga=0x31a resume=/dev/sdb2 splash=silent showopts elevator=cfq initrd /boot/initrd2.6.24-rc3-git5-smp # o /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/sdb # ls /boot/grub device.map fat_stage1_5~ jfs_stage1_5 menu.lst.old~ reiserfs_stage1_5~ stage2.old vstafs_stage1_5~ device.map.old ffs_stage1_5 jfs_stage1_5~ menu.lst_SAV stage1 stage2.old~ xfs_stage1_5 e2fs_stage1_5 ffs_stage1_5~ menu.lst minix_stage1_5 stage1~ ufs2_stage1_5 xfs_stage1_5~ e2fs_stage1_5~ iso9660_stage1_5 menu.lst~ minix_stage1_5~ stage2 ufs2_stage1_5~ fat_stage1_5 iso9660_stage1_5~ menu.lst.old reiserfs_stage1_5 stage2~ vstafs_stage1_5 Rebooted. "(hd1,0)/boot/message" can't be found. Also tried "(hd0,0)/boot/message". After the "kernel" line is displayed, I get initrd /boot/initrd2.6.24-rc3-git5-smp Error 2: Bad file or directory type Press any key to continue ... I rebuilt the kernel on the chrooted / and did a fresh mkinitrd, but I get exactly the same when I reboot. I've even removed the 320G SATA ext3 drive and done it all again, no luck. Can't figure out what the trouble is, filesystems mismatch, like you can't use a jfs HD backed up from an ext3 HD? grub is the same on both HD's, so is mkinitrd, gcc, etc., etc., everything got rsync'd across. Back on the original ext3 HD as /dev/sdb1, everything works. title 2.6.24-rc3-git5-smp kernel /boot/2.6.24-rc3-git5-smp root=/dev/disk/by-id/scsi-SATA_WDC_WD3200AAKS-_WD-WCAPZ1455963-part1 vga=0x31a resume=/dev/sdb2 splash=silent showopts elevator=cfq initrd /boot/initrd2.6.24-rc3-git5-smp Any ideas? Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Show replies by date

Patrick Shanahan

1 Dec 1 Dec

21:32

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 * Sid Boyce [12-01-07 16:13]: [...]

...

Back on the original ext3 HD as /dev/sdb1, everything works. title 2.6.24-rc3-git5-smp kernel /boot/2.6.24-rc3-git5-smp root=/dev/disk/by-id/scsi-SATA_WDC_WD3200AAKS-_WD-WCAPZ1455963-part1 vga=0x31a resume=/dev/sdb2 splash=silent showopts elevator=cfq initrd /boot/initrd2.6.24-rc3-git5-smp

Any ideas?

with the new hard-drive, boot with a "Live" or "Install" cd and choose "Boot Installed System" reinstall the grub from your installed system. - -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFHUdLXClSjbQz1U5oRAnyNAJ4qHYsGARQwAXVdqu1iojqqfzbzRACgjwUd SEfxCuamv+xfE6wNI2TEynk= =v0ff -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Sid Boyce

23:57

Patrick Shanahan wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

* Sid Boyce [12-01-07 16:13]: [...]

...
Back on the original ext3 HD as /dev/sdb1, everything works. title 2.6.24-rc3-git5-smp kernel /boot/2.6.24-rc3-git5-smp root=/dev/disk/by-id/scsi-SATA_WDC_WD3200AAKS-_WD-WCAPZ1455963-part1 vga=0x31a resume=/dev/sdb2 splash=silent showopts elevator=cfq initrd /boot/initrd2.6.24-rc3-git5-smp

Any ideas?

with the new hard-drive, boot with a "Live" or "Install" cd and choose "Boot Installed System"

reinstall the grub from your installed system.

Doubtful as it won't boot the installed system, i.e from HD, "Rescue" seems more likely and I've used the 10.3 x86_64 DVD. When I choose "Repair System" it fails not finding yast2, but I shall try the "Live" as that may have yast2 on it. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Viljo Mustonen

2 Dec 2 Dec

15:45

Sid Boyce wrote:

...

Can't figure out what the trouble is, filesystems mismatch, like you can't use a jfs HD backed up from an ext3 HD? grub is the same on both HD's, so is mkinitrd, gcc, etc., etc., everything got rsync'd across.

I think that this is reason. If initrd not contain jfs driver module, it can not to boot. Your should boot jfs system using rescue and execute mkinitrd. Other ways its not so easy.

...

Any ideas? Regards Sid. -- Viljo

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Viljo Mustonen

18:50

Viljo Mustonen wrote:

...

Sid Boyce wrote:

...
Can't figure out what the trouble is, filesystems mismatch, like you can't use a jfs HD backed up from an ext3 HD? grub is the same on both HD's, so is mkinitrd, gcc, etc., etc., everything got rsync'd across.

I think that this is reason. If initrd not contain jfs driver module, it can not to boot. Your should boot jfs system using rescue and execute mkinitrd. Other ways its not so easy.

...
Any ideas? Regards Sid.

Issue is not so easy, because it seems that originally in openSuse 10.3 is not support for jfs. Perhaps it is easier boot without initrd if jfs support is compiled into kernel.

-- Viljo --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Sid Boyce

19:05

Viljo Mustonen wrote:

...

Viljo Mustonen wrote:

...
Sid Boyce wrote:

...
Can't figure out what the trouble is, filesystems mismatch, like you can't use a jfs HD backed up from an ext3 HD? grub is the same on both HD's, so is mkinitrd, gcc, etc., etc., everything got rsync'd across.

I think that this is reason. If initrd not contain jfs driver module, it can not to boot. Your should boot jfs system using rescue and execute mkinitrd. Other ways its not so easy.

...
Any ideas? Regards Sid.

Issue is not so easy, because it seems that originally in openSuse 10.3 is not support for jfs. Perhaps it is easier boot without initrd if jfs support is compiled into kernel.

Thanks, that's worth a try. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Sid Boyce

21:39

Sid Boyce wrote:

...

Viljo Mustonen wrote:

...
Viljo Mustonen wrote:

...
Sid Boyce wrote:

...
Can't figure out what the trouble is, filesystems mismatch, like you can't use a jfs HD backed up from an ext3 HD? grub is the same on both HD's, so is mkinitrd, gcc, etc., etc., everything got rsync'd across.

I think that this is reason. If initrd not contain jfs driver module, it can not to boot. Your should boot jfs system using rescue and execute mkinitrd. Other ways its not so easy.

...
Any ideas? Regards Sid.

Issue is not so easy, because it seems that originally in openSuse 10.3 is not support for jfs. Perhaps it is easier boot without initrd if jfs support is compiled into kernel.

Thanks, that's worth a try. Regards Sid.

I booted from DVD and chrooted /dev/sdb1. Rebuilt the kernel with jfs built-in. With the "initrd" line commented out --- VFS: Cannot open root device "disk/by-id/scsi-SATA_MAXTOR_STM35006_6QG0YKMR-part1 or unknown-block(0,0) Please append a correct "root=" boot option, here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs or unknown-block(0,0). When I executed the "mkinitrd", I got a message for each kernel in menu.lst: WARNING: GRUB:: GrubPath2UnixPath: Path /boot/2.6.24-rc3-git5-smp in UNIX form, not modifying it. I also tried using /dev/sdb1 in /etc/fstab and in menu.lst with the same result. fsck.jfs says the partition is clean. just noticed something and wonder if that could be it, but neither is ext3 there. I have put a line "jfs" in /etc/filesystems for a try perhaps later. # cat /etc/filesystems vfat hfs minix reiserfs * Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Sid Boyce

19:04

Viljo Mustonen wrote:

...

Sid Boyce wrote:

...
Can't figure out what the trouble is, filesystems mismatch, like you can't use a jfs HD backed up from an ext3 HD? grub is the same on both HD's, so is mkinitrd, gcc, etc., etc., everything got rsync'd across.

I think that this is reason. If initrd not contain jfs driver module, it can not to boot. Your should boot jfs system using rescue and execute mkinitrd. Other ways its not so easy.

...
Any ideas? Regards Sid. From /etc/sysconfig/kernel INITRD_MODULES="processor thermal pata_amd sata_nv ahci pata_jmicron fan jbd ext3 edd jfs capability"

When I boot from 10.3 x86_64 DVD or from the ext3 drive, I can mount the jfs partition, also chroot works. In rescue mkinitrd also says the jfs module is included. I may try with jfs in front of ext3 in case it's due to a race condition. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Carlos E. R.

3 Dec 3 Dec

01:46

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-12-02 at 19:04 -0000, Sid Boyce wrote:

...

When I boot from 10.3 x86_64 DVD or from the ext3 drive, I can mount the jfs partition, also chroot works. In rescue mkinitrd also says the jfs module is included. I may try with jfs in front of ext3 in case it's due to a race condition.

I think you need a small /boot partition in ext2 format. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHU1/ntTMYHG2NR9URAt11AJ4yBMrjTAOAZiToRG+WGJpGy4ublQCggGAK VKfNQj9fyQbsGOb/7/V2+uk= =38ya -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Sid Boyce

13:07

Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2007-12-02 at 19:04 -0000, Sid Boyce wrote:

...
When I boot from 10.3 x86_64 DVD or from the ext3 drive, I can mount the jfs partition, also chroot works. In rescue mkinitrd also says the jfs module is included. I may try with jfs in front of ext3 in case it's due to a race condition.

I think you need a small /boot partition in ext2 format.

- -- Cheers, Carlos E. R.

That would be a step a long way back in time. I thought slicing and dicing a separate /boot partition went out with the need for steam trains, when PC BIOS restrictions meant you couldn't boot from a partition extending beyond the first 1024 cylinders. If the partition is ext3, reiserfs or anything else, it doesn't matter and I suspect jfs wouldn't be that immature. Having said that, there is a gremlin in there somewhere. Perhaps later this week I shall try a new 10.3 jfs install on a relative's box currently running 10.0, we have a spare 160G IDE drive sitting there ready. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Viljo Mustonen

23:39

Sid Boyce kirjoitti:

...

Carlos E. R. wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2007-12-02 at 19:04 -0000, Sid Boyce wrote:

...
When I boot from 10.3 x86_64 DVD or from the ext3 drive, I can mount the jfs partition, also chroot works. In rescue mkinitrd also says the jfs module is included. I may try with jfs in front of ext3 in case it's due to a race condition.

I think you need a small /boot partition in ext2 format.

- -- Cheers, Carlos E. R.

That would be a step a long way back in time. I thought slicing and dicing a separate /boot partition went out with the need for steam trains, when PC BIOS restrictions meant you couldn't boot from a partition extending beyond the first 1024 cylinders. If the partition is ext3, reiserfs or anything else, it doesn't matter and I suspect jfs wouldn't be that immature. Having said that, there is a gremlin in there somewhere. Perhaps later this week I shall try a new 10.3 jfs install on a relative's box currently running 10.0, we have a spare 160G IDE drive sitting there ready.

This problem exist also ext3 -> reiserfs change, perhaps in every file system change. Man mkinitrd tels: What should you do if the initrd is broken and you want to fix it using a chroot? I assume /mnt is your target root and /boot is mounted inside. 1. mount --bind /dev /mnt/dev 2. chroot /mnt 3. mount /proc 4. mount /sys 5. mkinitrd This worked in my 32 bit system. Old times it was much simpler. :) -- Viljo --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Sid Boyce

5 Dec 5 Dec

01:52

Viljo Mustonen wrote:

...

Sid Boyce kirjoitti:

...
Carlos E. R. wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2007-12-02 at 19:04 -0000, Sid Boyce wrote:

...
When I boot from 10.3 x86_64 DVD or from the ext3 drive, I can mount the jfs partition, also chroot works. In rescue mkinitrd also says the jfs module is included. I may try with jfs in front of ext3 in case it's due to a race condition. I think you need a small /boot partition in ext2 format.

- -- Cheers, Carlos E. R.

That would be a step a long way back in time. I thought slicing and dicing a separate /boot partition went out with the need for steam trains, when PC BIOS restrictions meant you couldn't boot from a partition extending beyond the first 1024 cylinders. If the partition is ext3, reiserfs or anything else, it doesn't matter and I suspect jfs wouldn't be that immature. Having said that, there is a gremlin in there somewhere. Perhaps later this week I shall try a new 10.3 jfs install on a relative's box currently running 10.0, we have a spare 160G IDE drive sitting there ready.

This problem exist also ext3 -> reiserfs change, perhaps in every file

system change. Man mkinitrd tels:

What should you do if the initrd is broken and you want to fix it using a chroot? I assume /mnt is your target root and /boot is mounted inside.

1. mount --bind /dev /mnt/dev 2. chroot /mnt 3. mount /proc 4. mount /sys 5. mkinitrd

This worked in my 32 bit system.

Old times it was much simpler. :)

-- Viljo

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

OK, I shall give that a try. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Carlos E. R.

4 Dec 4 Dec

01:25

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-12-03 at 13:07 -0000, Sid Boyce wrote:

...

That would be a step a long way back in time. I thought slicing and dicing a separate /boot partition went out with the need for steam trains, when PC BIOS restrictions meant you couldn't boot from a partition extending beyond the first 1024 cylinders.

Saying that is as if the politicians say that there is no need for protection or that your job and savings are secure :-P The theory is that you do not need a separate boot partition. However... the truth is that in some scenarios it does help, and my xtall ball tells me this /may/ be one of those cases. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHVKx7tTMYHG2NR9URAiMiAJ0dzCX1BCK/m3ijlB/WY4KLrPjODQCeMttH yRCDWqv5Zfo6tMEVTqYaQEA= =UMlM -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Hans Witvliet

08:51

New subject: [opensuse-factory] Problem booting a new hard drive with openSUSE 10.3

On Tue, 2007-12-04 at 02:25 +0100, Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Monday 2007-12-03 at 13:07 -0000, Sid Boyce wrote:

...
That would be a step a long way back in time. I thought slicing and dicing a separate /boot partition went out with the need for steam trains, when PC BIOS restrictions meant you couldn't boot from a partition extending beyond the first 1024 cylinders.

Saying that is as if the politicians say that there is no need for protection or that your job and savings are secure :-P

The theory is that you do not need a separate boot partition. However... the truth is that in some scenarios it does help, and my xtall ball tells me this /may/ be one of those cases.

AFAIK, /boot can not be put in an LVM. everything else can. hw --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Sid Boyce

5 Dec 5 Dec

01:58

Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Monday 2007-12-03 at 13:07 -0000, Sid Boyce wrote:

...
That would be a step a long way back in time. I thought slicing and dicing a separate /boot partition went out with the need for steam trains, when PC BIOS restrictions meant you couldn't boot from a partition extending beyond the first 1024 cylinders.

Saying that is as if the politicians say that there is no need for protection or that your job and savings are secure :-P

The theory is that you do not need a separate boot partition. However... the truth is that in some scenarios it does help, and my xtall ball tells me this /may/ be one of those cases.

- -- Cheers, Carlos E. R.

Worth a try, using parted and squeezing /dev/sdb3 as /boot.

...

Thandk and Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Sid Boyce

7 Dec 7 Dec

21:32

Sid Boyce wrote:

...

Carlos E. R. wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Monday 2007-12-03 at 13:07 -0000, Sid Boyce wrote:

...
That would be a step a long way back in time. I thought slicing and dicing a separate /boot partition went out with the need for steam trains, when PC BIOS restrictions meant you couldn't boot from a partition extending beyond the first 1024 cylinders.

Saying that is as if the politicians say that there is no need for protection or that your job and savings are secure :-P

The theory is that you do not need a separate boot partition. However... the truth is that in some scenarios it does help, and my xtall ball tells me this /may/ be one of those cases.

- -- Cheers, Carlos E. R.

Worth a try, using parted and squeezing /dev/sdb3 as /boot.

...
Thandk and Regards Sid.

I repartitioned the drive, /dev/sdb1 as / (jfs), /dev/sdb2 as /boot (reiserfs) and /dev/sdb3 as swap and used rsync to copy all the data across. After several tries, I finally got it boot, except for a problem with gfxmenu not being found. (hd1,1)/message, (hd1,0)/boot/message, (hd1,0)/message (after cp /boot/message /), /dev/sdb2/message have all been tried. Tried YaST, but when I click on Finish and go back in again /boot/message is gone from the previous YaST setup. Tried some other stuff from the YaST script by hand after "mkdir /tmp/gfxmenu", everything there looks fine. # /usr/bin/cpio -i < /boot/message # ls /tmp/gfxmenu/ 16x16.fnt back.jpg en.hlp en.tr gfxboot.cfg init lang languages pabout.txt panim_a.jpg panim.jpg pback.jpg phead.jpg timer_a.jpg translations.en # less /tmp/gfxmenu/pabout.txt Penguin theme originally made by Raphael Quinet (http://www.gamers.org/~quinet/lilo/). Modernized for openSUSE by Steffen Winterfeldt. Like it or hate it? Edit gfxboot.cfg in /boot/message to have it always or to get rid of it. # less /tmp/gfxmenu/gfxboot.cfg # penguin theme likelihood in percent; -1 = auto penguin=0 welcome=1 # /usr/lib/YaST2/bin/update_gfxmenu 760 blocks cp: missing destination file operand after `./translations.' Try `cp --help' for more information. tindog:/tmp/gfxmenu # ls | cpio -o >/boot/message.new && mv /boot/message.new /boot/message 760 blocks tindog:/tmp/gfxmenu # l /boot/message -rw-r--r-- 1 root root 389120 2007-12-07 21:18 /boot/message # rpm -qf /usr/lib/YaST2/bin/update_gfxmenu yast2-bootloader-2.16.2-14 Still, "/boot/message" can't be found. Checked to make sure ImageMagick is installed in case it's used. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

5991

Age (days ago)

5997

Last active (days ago)

List overview

Download

15 comments

5 participants

participants (5)

Carlos E. R.
Hans Witvliet
Patrick Shanahan
Sid Boyce
Viljo Mustonen