Loading ...
Sorry, an error occurred while loading the content.
 

Upgrading the kernel

Expand Messages
  • Dan
    Maybe I m just being stupid, but I don t see how to upgrade the kernel on the NSLU2 with OpenSlug. I installed OpenSlug, added the unstable tree to my ipkg
    Message 1 of 5 , May 14 12:32 PM
      Maybe I'm just being stupid, but I don't see how to upgrade the kernel
      on the NSLU2 with OpenSlug.

      I installed OpenSlug, added the unstable tree to my ipkg config, and
      ran an "ipkg update; ipkg upgrade". I see the new kernel installed
      and the vmlinuz link in /boot points to it, but the system is still
      booting up with 2.6.16. I need some of the drivers from the unstable
      tree that only work with 2.6.21, so the upgrade is kinda important to me.

      What is the magic step I'm missing? Do I have to perform some magic
      on the flash? I know in the regular linux world I would just update
      lilo/grub, but trying a "reflash -k" gave me an excuse to try out
      upslug2 -- not really what I had in mind. :)

      Here is some of the relevant data from the system:

      drich@delirium:~$ ls -l /boot/
      -rwxr-xr-x 1 root root 1487 Apr 6 03:10 disk
      -rwxr-xr-x 1 root root 407 Apr 6 03:10 flash
      -rwxr-xr-x 1 root root 556 Apr 6 03:10 network
      -rwxr-xr-x 1 root root 471 Apr 6 03:10 nfs
      -rwxr-xr-x 1 root root 1263 Apr 6 03:10 ram
      -rwxr-xr-x 1 root root 452 Apr 6 03:10 udhcpc.script
      lrwxrwxrwx 1 root root 27 May 12 16:12 zImage ->
      /boot/zImage-nslu2be-2.6.21
      -rw-r--r-- 1 root root 1028776 Nov 16 07:39
      zImage-nslu2be-2.6.16
      -rw-r--r-- 1 root root 1039272 Apr 27 20:51
      zImage-nslu2be-2.6.21
      drich@delirium:~$ ipkg list_installed | grep kernel
      kernel - 2.6.21-r0.824 - Linux kernel for the Intel IXP4xx device
      kernel-2.6.21 - 2.6.21-r0.824 - Linux kernel for the Intel IXP4xx device
      kernel-image-2.6.16 - 2.6.16-r6.6 - Linux kernel for the LinkSys NSLU2
      kernel-image-2.6.21 - 2.6.21-r0.824 - Linux kernel for the LinkSys NSLU2
      kernel-module-af-packet - 2.6.16-r6.6 - af-packet kernel module
      kernel-module-autofs4 - 2.6.21-r0.824 - autofs4 kernel module
      kernel-module-cp2101 - 2.6.21-r0.824 - cp2101 kernel module; Silicon
      Labs CP2101/CP2102 RS232 serial adaptor driver
      kernel-module-exportfs - 2.6.21-r0.824 - exportfs kernel module
      kernel-module-ext2 - 2.6.21-r0.824 - ext2 kernel module; Second
      Extended Filesystem
      kernel-module-ext3 - 2.6.21-r0.824 - ext3 kernel module; Second
      Extended Filesystem with journaling extensions
      kernel-module-fat - 2.6.21-r0.824 - fat kernel module
      kernel-module-isofs - 2.6.21-r0.824 - isofs kernel module
      kernel-module-jbd - 2.6.21-r0.824 - jbd kernel module
      kernel-module-lockd - 2.6.21-r0.824 - lockd kernel module; NFS file
      locking service version 0.5.
      kernel-module-mbcache - 2.6.21-r0.824 - mbcache kernel module; Meta
      block cache (for extended attributes)
      kernel-module-netconsole - 2.6.21-r0.824 - netconsole kernel module;
      Console driver for network interfaces
      kernel-module-nfs - 2.6.21-r0.824 - nfs kernel module
      kernel-module-nfsd - 2.6.21-r0.824 - nfsd kernel module
      kernel-module-nls-base - 2.6.21-r0.824 - nls-base kernel module
      kernel-module-nls-cp437 - 2.6.21-r0.824 - nls-cp437 kernel module
      kernel-module-nls-utf8 - 2.6.21-r0.824 - nls-utf8 kernel module
      kernel-module-ntfs - 2.6.21-r0.824 - ntfs kernel module; NTFS 1.2/3.x
      driver - Copyright (c) 2001-2007 Anton Altaparmakov
      kernel-module-reiserfs - 2.6.21-r0.824 - reiserfs kernel module;
      ReiserFS journaled filesystem
      kernel-module-sunrpc - 2.6.21-r0.824 - sunrpc kernel module
      kernel-module-udf - 2.6.21-r0.824 - udf kernel module; Universal Disk
      Format Filesystem
      kernel-module-usbserial - 2.6.21-r0.824 - usbserial kernel module; USB
      Serial Driver core
      kernel-module-vfat - 2.6.21-r0.824 - vfat kernel module; VFAT
      filesystem supportmodule-init-tools - 3.2.2-r2 - This package contains
      a set of programs for loading, inserting, and removing kernel modules
      for Linux (versions 2.5.48 and abov
      module-init-tools-depmod - 3.2.2-r2 - This package contains a set of
      programs for loading, inserting, and removing kernel modules for Linux
      (versions 2.5.48 and abov
      nfs-utils - 1.0.6-r7 - userspace utilities for kernel nfs

      Any thoughts?
    • Mike (mwester)
      reflash -k is indeed the magic incantation you need to put the new kernel into the flash. The NSLU2 bootloader is not able to read any filesystems, so it
      Message 2 of 5 , May 14 1:08 PM
        "reflash -k" is indeed the magic incantation you need to put the new kernel
        into the flash. The NSLU2 bootloader is not able to read any filesystems,
        so it cannot see the kernel in /boot at all; it only knows how to load the
        kernel from flash. And actually, only the first 1MB of the kernel, if its
        larger than 1MB in size.

        The bootloader also does a poor job of setting up to run the kernel (no
        command-line is passed; no information on the amount of memory, etc) so your
        build must also include either the APEX bootloader (as a second-stage
        bootloader) or the ARM kernel-shim. This is done for you if you use the
        nslu2-linux.org kernel build mechanism.

        You don't say how the kernel you flashed failed, so I can't comment on that.
        But it's possible that the new kernel just won't boot up with the older
        OpenSlug 3.10 flash rootfs.

        Since you've gotten this far with the build, why not just build all of the
        latest SlugOS release from OE? That would get you a complete image that you
        could flash that is known to work with the .21 kernel.

        Mike (mwester)

        ----- Original Message -----
        From: "Dan" <drich@...>
        To: <nslu2-linux@yahoogroups.com>
        Sent: Monday, May 14, 2007 2:32 PM
        Subject: [nslu2-linux] Upgrading the kernel


        Maybe I'm just being stupid, but I don't see how to upgrade the kernel
        on the NSLU2 with OpenSlug.

        I installed OpenSlug, added the unstable tree to my ipkg config, and
        ran an "ipkg update; ipkg upgrade". I see the new kernel installed
        and the vmlinuz link in /boot points to it, but the system is still
        booting up with 2.6.16. I need some of the drivers from the unstable
        tree that only work with 2.6.21, so the upgrade is kinda important to me.

        What is the magic step I'm missing? Do I have to perform some magic
        on the flash? I know in the regular linux world I would just update
        lilo/grub, but trying a "reflash -k" gave me an excuse to try out
        upslug2 -- not really what I had in mind. :)

        Here is some of the relevant data from the system:

        drich@delirium:~$ ls -l /boot/
        -rwxr-xr-x 1 root root 1487 Apr 6 03:10 disk
        -rwxr-xr-x 1 root root 407 Apr 6 03:10 flash
        -rwxr-xr-x 1 root root 556 Apr 6 03:10 network
        -rwxr-xr-x 1 root root 471 Apr 6 03:10 nfs
        -rwxr-xr-x 1 root root 1263 Apr 6 03:10 ram
        -rwxr-xr-x 1 root root 452 Apr 6 03:10 udhcpc.script
        lrwxrwxrwx 1 root root 27 May 12 16:12 zImage ->
        /boot/zImage-nslu2be-2.6.21
        -rw-r--r-- 1 root root 1028776 Nov 16 07:39
        zImage-nslu2be-2.6.16
        -rw-r--r-- 1 root root 1039272 Apr 27 20:51
        zImage-nslu2be-2.6.21
        drich@delirium:~$ ipkg list_installed | grep kernel
        kernel - 2.6.21-r0.824 - Linux kernel for the Intel IXP4xx device
        kernel-2.6.21 - 2.6.21-r0.824 - Linux kernel for the Intel IXP4xx device
        kernel-image-2.6.16 - 2.6.16-r6.6 - Linux kernel for the LinkSys NSLU2
        kernel-image-2.6.21 - 2.6.21-r0.824 - Linux kernel for the LinkSys NSLU2
        kernel-module-af-packet - 2.6.16-r6.6 - af-packet kernel module
        kernel-module-autofs4 - 2.6.21-r0.824 - autofs4 kernel module
        kernel-module-cp2101 - 2.6.21-r0.824 - cp2101 kernel module; Silicon
        Labs CP2101/CP2102 RS232 serial adaptor driver
        kernel-module-exportfs - 2.6.21-r0.824 - exportfs kernel module
        kernel-module-ext2 - 2.6.21-r0.824 - ext2 kernel module; Second
        Extended Filesystem
        kernel-module-ext3 - 2.6.21-r0.824 - ext3 kernel module; Second
        Extended Filesystem with journaling extensions
        kernel-module-fat - 2.6.21-r0.824 - fat kernel module
        kernel-module-isofs - 2.6.21-r0.824 - isofs kernel module
        kernel-module-jbd - 2.6.21-r0.824 - jbd kernel module
        kernel-module-lockd - 2.6.21-r0.824 - lockd kernel module; NFS file
        locking service version 0.5.
        kernel-module-mbcache - 2.6.21-r0.824 - mbcache kernel module; Meta
        block cache (for extended attributes)
        kernel-module-netconsole - 2.6.21-r0.824 - netconsole kernel module;
        Console driver for network interfaces
        kernel-module-nfs - 2.6.21-r0.824 - nfs kernel module
        kernel-module-nfsd - 2.6.21-r0.824 - nfsd kernel module
        kernel-module-nls-base - 2.6.21-r0.824 - nls-base kernel module
        kernel-module-nls-cp437 - 2.6.21-r0.824 - nls-cp437 kernel module
        kernel-module-nls-utf8 - 2.6.21-r0.824 - nls-utf8 kernel module
        kernel-module-ntfs - 2.6.21-r0.824 - ntfs kernel module; NTFS 1.2/3.x
        driver - Copyright (c) 2001-2007 Anton Altaparmakov
        kernel-module-reiserfs - 2.6.21-r0.824 - reiserfs kernel module;
        ReiserFS journaled filesystem
        kernel-module-sunrpc - 2.6.21-r0.824 - sunrpc kernel module
        kernel-module-udf - 2.6.21-r0.824 - udf kernel module; Universal Disk
        Format Filesystem
        kernel-module-usbserial - 2.6.21-r0.824 - usbserial kernel module; USB
        Serial Driver core
        kernel-module-vfat - 2.6.21-r0.824 - vfat kernel module; VFAT
        filesystem supportmodule-init-tools - 3.2.2-r2 - This package contains
        a set of programs for loading, inserting, and removing kernel modules
        for Linux (versions 2.5.48 and abov
        module-init-tools-depmod - 3.2.2-r2 - This package contains a set of
        programs for loading, inserting, and removing kernel modules for Linux
        (versions 2.5.48 and abov
        nfs-utils - 1.0.6-r7 - userspace utilities for kernel nfs

        Any thoughts?
      • Dan
        ... so your ... I m running from the openslug packages in the unstable tree rather than doing my own build. Although, I m tempted to go that route so I could
        Message 3 of 5 , May 14 3:35 PM
          --- In nslu2-linux@yahoogroups.com, "Mike \(mwester\)" <mwester@...>
          wrote:
          >
          > The bootloader also does a poor job of setting up to run the kernel (no
          > command-line is passed; no information on the amount of memory, etc)
          so your
          > build must also include either the APEX bootloader (as a second-stage
          > bootloader) or the ARM kernel-shim. This is done for you if you use the
          > nslu2-linux.org kernel build mechanism.

          I'm running from the openslug packages in the unstable tree rather
          than doing my own build. Although, I'm tempted to go that route so I
          could just build the driver I need against the 2.6.16 kernel.

          > You don't say how the kernel you flashed failed, so I can't comment
          on that.
          > But it's possible that the new kernel just won't boot up with the older
          > OpenSlug 3.10 flash rootfs.

          That's not a pleasant thought. I'll have to try it when I'm near the
          box rather than doing it remotely. From the looks of the LEDs on the
          slug, it did boot -- I'm guessing w/o a network driver. However, I
          haven't added a serial port (yet, I think), so it's tough to tell what
          is going on w/o a network connection.

          > Since you've gotten this far with the build, why not just build all
          of the
          > latest SlugOS release from OE? That would get you a complete image
          that you
          > could flash that is known to work with the .21 kernel.

          That's one of the things I've considered. The only drawback is
          getting the build environment up and running. At the moment, the slug
          is the only Linux box in the house -- everything else is either
          FreeBSD or OSX (since I deal with ~1500 Linux boxen all day M-F, I
          want something stable at home :) ).

          I'll try the reflash tonight while I'm there to see it happen and let
          you know how it goes. With my luck it will work since I'll be there to
          watch it.
        • Dan
          So using the kernel from http://ipkg.nslu2-linux.org/feeds/openslug/unstable bad things happen. I ran reflash -k /boot/zImage-nslu2be-2.6.21 and rebooted. I
          Message 4 of 5 , May 14 8:55 PM
            So using the kernel from
            http://ipkg.nslu2-linux.org/feeds/openslug/unstable bad things happen.
            I ran reflash -k /boot/zImage-nslu2be-2.6.21 and rebooted. I heard
            the normal boot beep, followed by two lower pitched beeps, then a
            single beep again. The LEDs flashed for a bit and I ended up with a
            flashing yellow LED.

            Any thoughts as to what might be happening and/or what I can try from
            here? I probably should try it again with someone else writing down
            the beeps and LED status while I watch.

            Fortunately it is easy enough to reflash and reboot!

            --- In nslu2-linux@yahoogroups.com, "Dan" <drich@...> wrote:
            >
            > --- In nslu2-linux@yahoogroups.com, "Mike \(mwester\)" <mwester@>
            > wrote:
            > >
            > > The bootloader also does a poor job of setting up to run the
            kernel (no
            > > command-line is passed; no information on the amount of memory, etc)
            > so your
            > > build must also include either the APEX bootloader (as a second-stage
            > > bootloader) or the ARM kernel-shim. This is done for you if you
            use the
            > > nslu2-linux.org kernel build mechanism.
            >
            > I'm running from the openslug packages in the unstable tree rather
            > than doing my own build. Although, I'm tempted to go that route so I
            > could just build the driver I need against the 2.6.16 kernel.
            >
            > > You don't say how the kernel you flashed failed, so I can't comment
            > on that.
            > > But it's possible that the new kernel just won't boot up with the
            older
            > > OpenSlug 3.10 flash rootfs.
            >
            > That's not a pleasant thought. I'll have to try it when I'm near the
            > box rather than doing it remotely. From the looks of the LEDs on the
            > slug, it did boot -- I'm guessing w/o a network driver. However, I
            > haven't added a serial port (yet, I think), so it's tough to tell what
            > is going on w/o a network connection.
            >
            > > Since you've gotten this far with the build, why not just build all
            > of the
            > > latest SlugOS release from OE? That would get you a complete image
            > that you
            > > could flash that is known to work with the .21 kernel.
            >
            > That's one of the things I've considered. The only drawback is
            > getting the build environment up and running. At the moment, the slug
            > is the only Linux box in the house -- everything else is either
            > FreeBSD or OSX (since I deal with ~1500 Linux boxen all day M-F, I
            > want something stable at home :) ).
            >
            > I'll try the reflash tonight while I'm there to see it happen and let
            > you know how it goes. With my luck it will work since I'll be there to
            > watch it.
            >
          • bernhardthoni
            hi dan, i got a similar prob, when upgrading the kernel to 2.6.21 (from unstable-feed): my procedure was: 1. turnup memstick /dev/sdc1 (verified, that -after
            Message 5 of 5 , Sep 16, 2007
              hi dan,
              i got a similar prob, when upgrading the kernel to 2.6.21 (from
              unstable-feed):

              my procedure was:

              1. turnup memstick /dev/sdc1 (verified, that -after reboot-
              /dev/sdc1 is used as / (via mount and /etc/fstab))
              2. edited conf-files , so that ipkg uses unstable openslug-feed
              3. ipkg update && ipkg upgrade

              results:
              - all installed packages up-dated/-graded
              - 2 diff kernels in boot; /boot/vmlinuz still sym-linked to 2.6.16

              afterwards i did:
              reflash -k /boot/kernel-nslu2-2.6.21 && shutdown -h reboot

              BUT: here it did not stop with yellow LED, but all 2 gree
              BUT: i was not able to log in (ssh) anymore (whether 192.168.0.250
              nor 192.168.1.77 worked);

              did i miss something? should i have symlinked /boot/vmlinuz
              to /boot/kernel-nslu2-2.6.21 ???
              should i have run a tuneup-command again/ modified /etc/fstab?

              pls help
              thx in advance,
              greeting,
              bernhard



              --- In nslu2-linux@yahoogroups.com, "Dan" <drich@...> wrote:
              >
              > So using the kernel from
              > http://ipkg.nslu2-linux.org/feeds/openslug/unstable bad things
              happen.
              > I ran reflash -k /boot/zImage-nslu2be-2.6.21 and rebooted. I heard
              > the normal boot beep, followed by two lower pitched beeps, then a
              > single beep again. The LEDs flashed for a bit and I ended up with a
              > flashing yellow LED.
              >
              > Any thoughts as to what might be happening and/or what I can try
              from
              > here? I probably should try it again with someone else writing down
              > the beeps and LED status while I watch.
              >
              > Fortunately it is easy enough to reflash and reboot!
              >
              > --- In nslu2-linux@yahoogroups.com, "Dan" <drich@> wrote:
              > >
              > > --- In nslu2-linux@yahoogroups.com, "Mike \(mwester\)" <mwester@>
              > > wrote:
              > > >
              > > > The bootloader also does a poor job of setting up to run the
              > kernel (no
              > > > command-line is passed; no information on the amount of memory,
              etc)
              > > so your
              > > > build must also include either the APEX bootloader (as a second-
              stage
              > > > bootloader) or the ARM kernel-shim. This is done for you if you
              > use the
              > > > nslu2-linux.org kernel build mechanism.
              > >
              > > I'm running from the openslug packages in the unstable tree rather
              > > than doing my own build. Although, I'm tempted to go that route
              so I
              > > could just build the driver I need against the 2.6.16 kernel.
              > >
              > > > You don't say how the kernel you flashed failed, so I can't
              comment
              > > on that.
              > > > But it's possible that the new kernel just won't boot up with
              the
              > older
              > > > OpenSlug 3.10 flash rootfs.
              > >
              > > That's not a pleasant thought. I'll have to try it when I'm near
              the
              > > box rather than doing it remotely. From the looks of the LEDs on
              the
              > > slug, it did boot -- I'm guessing w/o a network driver. However,
              I
              > > haven't added a serial port (yet, I think), so it's tough to tell
              what
              > > is going on w/o a network connection.
              > >
              > > > Since you've gotten this far with the build, why not just build
              all
              > > of the
              > > > latest SlugOS release from OE? That would get you a complete
              image
              > > that you
              > > > could flash that is known to work with the .21 kernel.
              > >
              > > That's one of the things I've considered. The only drawback is
              > > getting the build environment up and running. At the moment, the
              slug
              > > is the only Linux box in the house -- everything else is either
              > > FreeBSD or OSX (since I deal with ~1500 Linux boxen all day M-F, I
              > > want something stable at home :) ).
              > >
              > > I'll try the reflash tonight while I'm there to see it happen and
              let
              > > you know how it goes. With my luck it will work since I'll be
              there to
              > > watch it.
              > >
              >
            Your message has been successfully submitted and would be delivered to recipients shortly.