[prev in list] [next in list] [prev in thread] [next in thread]
List: openembedded-issues
Subject: [Bug 3893] New: H4350 hangs after ipkg update, upgrade
From: bugzilla-daemon () treke ! net (bugzilla-daemon at treke ! net)
Date: 2008-02-28 23:31:25
Message-ID: bug-3893-13 () http ! bugs ! openembedded ! net/
[Download RAW message or body]
http://bugs.openembedded.net/show_bug.cgi?id=3893
Summary: H4350 hangs after ipkg update, upgrade
Product: Openembedded
Version: Angstrom 2007.12
Platform: ARM
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Distributions
AssignedTo: openembedded-issues at lists.openembedded.org
ReportedBy: mark.just.mark at gmail.com
iPaq H4350
1GB SD card, partitioned into 32MB FAT, 960MB ext2
set up as per http://linuxadministration.us/2008/01/30/linux-on-the-ipaq-h4150/
(though I ignored trying to get the acx wireless bits to work - that's another
story)
System comes up fine, connects to PC via USB, can see the internet.
I run ipkg update and then ipkg upgrade.
Lots of things get upgraded.
I reboot with shutdown -r now
On the way back up (Angstrom compass logo screen) the system hangs.
Progress bar at about 30%.
Hard reset - back into PocketPC - set time - run Linux loader.
Hang at same point.
Remove SD card and extract 2007.12 tar back onto ext2 filesystem.
Hard reset - back into PocketPC - set time - run Linux loader.
Works this time.
ipkg update and upgrade.
ipkg remove anything acx related (firmware and kernel module)
Reboot.
This time I get the Angstrom compass logo screen and the progress bar makes it
to 100% at which point the iPaq hard resets itself back into PocketPC.
Other things I've tried:
Put the upgraded kernel (zImage...) from /boot into the FAT filesystem,
renaming the existing zImage out of the way, and naming the new one so that the
boot loader uses it.
Any other suggestions?
Any way to make the system log to /var/messages on the SD card?
--
Configure bugmail: http://bugs.openembedded.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic