Results 1 to 6 of 6

Thread: kernel advice

  1. #1

    kernel advice

    Hello there , just wondered if any of you good folks at wht could lend some advice here.

    System is running Redhat 7.3

    rpm -q kernel reads
    kernel-2.4.18-3
    kernel-2.4.18-17.7.x

    uname -r reads
    2.4.19

    I have no idea where the 2.4.19 came from - as you see below I think i need the bigmem kernel on this system, also the img file for any kernel other than 2.4.18-3 is not located within /boot (Puzzling part)

    Boot logs
    Warning only 896MB will be used.
    Use a HIGHMEM enabled kernel.
    896MB LOWMEM available.

    I also got this from the boot logs

    Kernel command line: auto BOOT_IMAGE=via root=302 BOOT_FILE=/boot/vmlinuz-2.4.19-via
    No local APIC present or hardware disabled
    Initializing CPU#0
    Detected 2000.003 MHz processor.
    Console: colour VGA+ 80x25

    Is that normal or did someone at the console do that - The server was rebooted via the cosole at that time - why I have no idea.

    OK so i guess I need the bigmem kernel installed - the system has 1GB Ram.

    Easy, so off I go to download the bigmem kernel from redhat:

    rpm -ivh kernel-bigmem-2.4.18-17.7.x.i686.rpm

    messages after intalling that
    stdin is not a tty
    stdin is not a tty
    stdin is not a tty
    All of your loop back devices are in use

    Not sure what that meant.. off to /boot

    Here is what i see.. notice the img files are not there, only the one for the initial kernel installation 2.4.18-3

    config-2.4.18-17.7.x
    config-2.4.18-17.7.xbigmem
    config-2.4.18-3

    initrd-2.4.18-3.img (I expected to see the img for the 2.4.19 and 2.4.18-7.7.x + bigmem kernels here too)

    module-info -> module-info-2.4.18-17.7.x
    module-info-2.4.18-17.7.x
    module-info-2.4.18-17.7.xbigmem
    module-info-2.4.18-3

    System.map -> System.map-2.4.18-17.7.x
    System.map-2.4.18-17.7.x
    System.map-2.4.18-17.7.xbigmem
    System.map-2.4.18-3

    vmlinux-2.4.18-17.7.x*
    vmlinux-2.4.18-17.7.xbigmem*
    vmlinux-2.4.18-3

    vmlinuz -> vmlinuz-2.4.18-17.7.x
    vmlinuz-2.4.18-17.7.x
    vmlinuz-2.4.18-17.7.xbigmem
    vmlinuz-2.4.18-3
    vmlinuz-2.4.19-via

    cat /root/anaconda-ks.cfg | grep 'bootloader'
    bootloader --useLilo

    So this server uses lilo:

    This is the current contents of lilo.conf

    default=via
    prompt
    timeout=50
    boot=/dev/hda
    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    lba32

    image=/boot/vmlinuz-2.4.18-3
    label=linux
    initrd=/boot/initrd-2.4.18-3.img
    read-only
    root=/dev/hda2

    image=/boot/vmlinuz-2.4.19-via
    label=via
    root=/dev/hda2

    image=/boot/vmlinuz-2.4.18-17.7.x
    label=linux-up.bak
    root=/dev/hda2
    read-only

    image=/boot/vmlinuz-2.4.18-17.7.x
    label=linux-up
    root=/dev/hda2
    read-only


    I realise that the default has to be altered and then run lilo -v -v to make the changes.

    What I can't work out is where the .img files are for the other installed kernels and indeed if everything is installed that needs to be for a successfull reboot.

    As I want to install the bigmem kernel , can anyone offer any advice on this?

    Thanks for any help in advance.

    Adrian
    Last edited by Fire; 10-21-2002 at 06:51 AM.

  2. #2
    Anyone help with this?

  3. #3
    Maybe someone installed kernel from sources?

  4. #4
    Maybe the 2.4.19 was - I don't know, but why would the img not install when installing the rpm for the bigmem kernel? - Also there is only the initrd-2.4.18-3.img - is that correct? Feel uneasy about the whole thing.

    Any help appreciated.

  5. #5
    OK,

    I have just upgraded another machine and all went well.

    On this machine however every time I install a kernel rpm - I get this error:-

    stdin is not a tty
    stdin is not a tty
    stdin is not a tty
    All of your loop block devices are in use

    The last line is relating to the initrd-2.4.18-x.x.img install i think. Is the initrd-2.4.18-x.x.img required or will that only enable ext3 on /boot?

    There is no initrd-2.4.18-x.x.img installed as a result.
    Therefore lilo.conf reads:

    image=/boot/vmlinuz-2.4.18-17.7.x
    label=linux-up
    root=/dev/hda2
    read-only

    There are also many initrd.xxx directories, 1 created with each attempt to install the kernel rpm - within /tmp

    Cheers for any help.
    Last edited by Fire; 10-23-2002 at 07:04 AM.

  6. #6
    Well here you go, thought I'd finish the story off, hopefully may be usefull to someone else at some stage.

    The 2.4.19 kernel was installed from source with inadequate loop block support. After much looking I found that out.

    I rebooted to already installed 2.4.18-3 kernel and then installed the the 2.4.18-7.7.x kernel - This successfully installed the initrd-2.4.18-17.7.x.img

    Edited lilo and did lilo -v -v

    Rebooted, removed the 2.4.19 kernel that was causing problems and everything is good

    Thx for the help guys...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •