Re: NSLU2 won't reboot after recent etch upgrade
On Thu, 18 Sep 2008 23:00:37 +0200, you wrote:
> Heinrich,
>
> this kernel seems to reboot just fine here. Is that the kernel you used?
>
> Regards,
> Rainer
>
> Linux nslu2 2.6.18-6-ixp4xx #1 Tue Aug 19 20:03:53 UTC 2008 armv5tel
Not shure as I can't see this login prompt ;-)
I saved the /boot folder to another folder:
1186532 2008-08-20 14:09 vmlinuz-2.6.18-6-ixp4xx
The file date is one day after yours...
The file date of the initrd is the date I upgraded the system.
Don't know whether the the date / time - stamps are of any relevance
here, but it's clear that I didn't made any changes the 20. August.
This year I upgraded two times the kernel. From my dpkg.log:
--------------------------------------------------------------------------
this is the first upgrade:
2008-07-24 17:47:53 upgrade linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch1 2.6.18.dfsg.1-18etch6
2008-07-24 17:47:53 status half-configured linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch1
2008-07-24 17:48:04 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch1
2008-07-24 17:48:04 status half-installed linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch1
2008-07-24 17:48:58 status half-installed linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch1
2008-07-24 17:49:13 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch6
2008-07-24 17:49:14 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch6
...
2008-07-29 17:36:11 upgrade linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch6 2.6.18.dfsg.1-22
2008-07-29 17:36:11 status half-configured linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch6
2008-07-29 17:36:28 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch6
2008-07-29 17:36:28 status half-installed linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch6
2008-07-29 17:37:10 status half-installed linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-18etch6
2008-07-29 17:37:23 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22
2008-07-29 17:37:24 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22
2008-07-29 17:37:24 upgrade initscripts 2.86.ds1-38
2.86.ds1-38+etchnhalf.1
2008-07-29 17:37:24 status half-configured initscripts 2.86.ds1-38
2008-07-29 17:37:25 status unpacked initscripts 2.86.ds1-38
2008-07-29 17:37:25 status half-installed initscripts 2.86.ds1-38
2008-07-29 17:37:25 status half-installed initscripts 2.86.ds1-38
2008-07-29 17:37:26 status unpacked initscripts
2.86.ds1-38+etchnhalf.1
...
this is the second faulty upgrade: -----------------------------------
2008-09-09 13:59:20 upgrade linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22 2.6.18.dfsg.1-22etch2
2008-09-09 13:59:20 status half-configured linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22
2008-09-09 13:59:30 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22
2008-09-09 13:59:30 status half-installed linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22
2008-09-09 14:00:10 status half-installed linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22
2008-09-09 14:00:25 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22etch2
2008-09-09 14:00:26 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22etch2
2008-09-09 14:00:26 upgrade libxml2 2.6.27.dfsg-2 2.6.27.dfsg-4
2008-09-09 14:00:26 status half-configured libxml2 2.6.27.dfsg-2
2008-09-09 14:00:27 status unpacked libxml2 2.6.27.dfsg-2
2008-09-09 14:00:27 status half-installed libxml2 2.6.27.dfsg-2
2008-09-09 14:00:27 status half-installed libxml2 2.6.27.dfsg-2
2008-09-09 14:00:29 status unpacked libxml2 2.6.27.dfsg-4
2008-09-09 14:00:29 status unpacked libxml2 2.6.27.dfsg-4
2008-09-09 14:00:29 status unpacked linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22etch2
2008-09-09 14:00:30 status half-configured linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22etch2
2008-09-09 14:05:07 status installed linux-image-2.6.18-6-ixp4xx
2.6.18.dfsg.1-22etch2
2008-09-09 14:05:08 status unpacked libxml2 2.6.27.dfsg-4
2008-09-09 14:05:08 status half-configured libxml2 2.6.27.dfsg-4
2008-09-09 14:05:09 status installed libxml2 2.6.27.dfsg-4
--------------------------------------------------------------------------
Would be nice If you can look up your dpkg.log to see whether you are
running the kernel version which was faulty here or not.
Until now I didn't understand the boot process of the slug. AFAIK the
kernel and the initrd is flashed to the internal EEPROM during the
update process and the slug boots from the EEPROM. So the files in
/boot may be there only for compatibility reasons?
Reply to: