Re: [SLE] slackware is better than SuSE --> to deal with upgrade

From: Adagilson Batista Bispo da Silva (adagilson_at_cpqam.fiocruz.br)
Date: 11/11/05

  • Next message: James Knott: "Re: [SLE] Gnome disappointment" 
    Date: Fri, 11 Nov 2005 09:48:25 -0200
To: SLE <suse-linux-e@suse.com>

        I edited /etc/sysconfig/kernel and added:
    INITRD_MODULES="via89cxxx"

        After running again
    $mkdir /mnt/gonow
    $mount /dev/hda6 /mnt/gonow
    $chroot /mnt/gonow
    $mkinitrd -R -u
    ...the system told me:

    Root device: /dev/root (mounted on / ext2)
    Module list: via82cxxx
    You may now have to update your boot loader configuration

        Then, I rebooted my box.

    ...and a new sequence of error messages continues:
    [...]
    Loading kernel/fs/jbd/jbd.ko
    Loading kernel/fs/ext3/ext3.ko
    /linuxrc: 264: syntax error: Bad substitution
    VFS: Cannot open root device "hda6" or unknown-block(0,0)
    Please apend a correct "root=" boot option
    Kernel panic - not syncing: VFS: Unable to mount root fs on
    unknown-block(0,0)

        Could you help me again? I just don't know what is missing. I
    thought just making it a new initrd with a redefined root, it would work.
    adagilson

    PS--my current boot loader, Grub, has this line to label SuSE 9.3:
    kernel (hd0,5) /boot/vmlinuz too=/dev/hda6 vga=0x31a selinux=0
    splash=silent resume=/dev/hda7 showapts
    initrd (hd0,5) /boot/initrd

    Hans du Plooy escreveu:

    >On Thursday 10 November 2005 13:42, Adagilson Batista Bispo da Silva wrote:
    >
    >
    >>I follow your tips, typing 3 to the boot options, but an error occurred:
    >>"Waiting for device /dev/hda6 to appear .....not found -- exiting to
    >>/bin/sh sh: can't access tty; job control turned off"
    >>
    >>
    >The difference is that Slackware probably builds all their IDE drivers into
    >the kernel, or include all of them in the initrd (dunno which, I haven't
    >worked with Slack in ages), while SUSE only puts what's needed in there.
    >
    >So you previous board probably had a ALi chipset (popular on boards K6 boards
    >of that era), while the new one is a VIA. when you boot of the rescue CD, d
    >an lsmod and make note of which VIA module is loaded.
    >
    >
    >
    >>Ps--I tried Rescue mode:
    >>$mkdir /mnt/gonow
    >>$mount /dev/hda6 /mnt/gonow
    >>$mkinitrd -R -u
    >>--reboot--
    >>
    >>
    >
    >You're leaving out a crucial step. Edit /etc/sysconfig/kernel, and add the
    >required module to the list. Then make the new initrd.
    >
    >Hans
    >
    >
    >

  • Next message: James Knott: "Re: [SLE] Gnome disappointment"

    Relevant Pages

    • 2.6.12 initrd module loading seems parallel on bootup
      ... I'm witnessing a problem with mounting root on a system that loads ... modules from initrd in order to be able to mount root, ... The printk output over the console indicates the module loading is ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Fw: ERROR: /bin/insmod exited abnormally!
      ... Boot loader: lilo ... I'm running Redhat ES 3 release and after much struggle finally succeeded ... insmod QM_MODULES: ... Cannot open root device or unknown-block ...
      (Linux-Kernel)
    • Re: Read-only root (/) except /etc
      ... in the boot loader, use the kernel option ... where /pre-init.sh is executable by root and contains something like this: ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • Re: Root account desactivated
      ... Instant root shell. ... so securing the boot loader is a good idea. ...
      (Security-Basics)
    • problem with rrload Boot loader on innovator using CCS
      ... After bulild when i am try to run on CCS its runing and its loading, ... but its not displaying the menu on serial console. ... Do we have any other method to burn the boot loader to flash.i have ...
      (comp.arch.embedded)