[Angstrom-distro-users] CF boot stopped at e2fsck prompt -20070918 h2200 image
joshua at willowisp.net
Tue Sep 25 07:34:28 CEST 2007
Joshua Layne wrote:
> On Tue, 25 Sep 2007 02:21:46 +0300, Paul Sokolovsky <pmiscml at gmail.com>
>> Hello Joshua,
>> Sunday, September 23, 2007, 6:50:00 PM, you wrote:
>>> Hi All,
>>> I am new to the list, although I have lurked in the archives for quite
>>> time and tried a few of the much earlier images.
>>> I have an h2200 with the april 22, 2006 LAB installed and tried several
>>> times unsuccessfully to test the new september 18th images on a spare SD
>>> card I had lying around - I have since determined that this SD card is
>>> (and my only spare), so I switched to CF. CF booted fine (meaning that
>>> got the angstrom splash) but it stopped for an unreasonable amount of
>>> So I set the pssplash=false and tried again. This time it stopped at a
>>> user prompt:
>>> Running e2fsck on a mounted filesystem does really bad things!!!
>> Ok, I finally caught this insanely annoying issue.
>> http://bugs.openembedded.org/show_bug.cgi?id=3065 submitted for it,
>> workaround committed. We should consider checking and upgrading to
>> newer busybox.
> thanks for submitting the bug on that paul - didn't mean to farm out
> responsibility for it - I've been away from this stuff for a while and was
> willing to believe it was user error somehow (it usually is with me).
>>> my fstab is below if it matters (my labrun works fine, so not including
>>> /dev/hda1 / ext2 defaults 1 0
>>> proc /proc proc defaults 0 0
>>> sys /sys sysfs defaults 0 0
>>> tmpfs /var/volatile tmpfs mode=0755 0 0
>>> tmpfs /dev/shm tmpfs mode=0777 0 0
>>> /dev/mmcblk0p1 /media/card auto
>>> 0 0
>> I wonder where such an fstab came from? This is not what OE used to
>> have. (And that wasn't correct either, but now its fixed.)
> sorry - should have been more clear - these are my modifications to the
> fstab included in the sep 18 image, since it looked like that one was set
> up for a reflashed system (and I am running off of CF). May have been
> unnecessary, but if so, my understanding of fstab is worse than I thought.
> I also had to add a labrun file too (and copy over some apps I like.... etc
> thanks for the reply - I have retrieved my serial cable and so hopefully
> can boot tonight.
successfully booted, with the following kernel arguments: root=/dev/hda2
(had to have the ttyS0 as the last argument (and thus default terminal)
to be able to interact with it) - I'm still not sure why it thinks the
disk is unchecked, but that is neither here nor there.
interface seems a bit dodgy right now - keyboard (inside a session) is a
bit munged up (bad spacing) - I'll send a screenshot once I have the
network working - the keyboard for login and session resume is fine.
and I seem to have died on:
1469.520000] bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
[ 1469.760000] bcsp_pkt_cull: Peer acked invalid packet
[ 1469.770000] bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
[ 1470.010000] bcsp_pkt_cull: Peer acked invalid packet
over and over and over and over (well, you get the picture....) again.
the irony is that if I had ttyS0 set to anything other than the default,
I could log in and kill bcsp (or whatever the parent BT daemon is for
this), but the terminal is unusable with the messages :)
ok, actually - I got it. PITA typing over error messages, but possible.
I am however unable to get the PDA screen to come back - even with a
not looking for help on this, just trying to report back my experience
with the h2200 images - if there are any other tests I can run, please
let me know.
> Angstrom-distro-users mailing list
> Angstrom-distro-users at linuxtogo.org
More information about the Angstrom-distro-users