Stuck at the GPE login with latest Narcissus build
eelcor
Hi,
Just downloaded a full image using the Narcissus build system.
Unfortunately I am stuck at the GPE login screen (something tells me
that the window manager cannot be started). After entering username
and password, the screen becomes black, shows the cross cursor and
after approx. 5-10 seconds it returns to the login screen.
Any suggestions? I've tried reinstalling gpe-dm and gpe-login. Do I
need to reconfigure stuff?
Kind regards, Eelco
eelcor
for the image. However, as there is no easy to find documentation on
the building system, I am stuck. For my configuration I have installed
all packages, I only left out the task-base and task-extended (first
part of the menu).
It is really frustrating as I can't find any way to get into the
window manager, the annoying login screen keeps on popping up. Running
vnc viewer on my linux machine shows the login screen, but after
logging in the connection to the beagleboard is closed. If I run the
vncviewer after that, I get the login screen.
Kind regards,
Eelco
Koen Kooi
Op 1 jun 2009, om 08:55 heeft eelcor het volgende geschreven:
>
> It seems to be a conflict between the various packages you can select
> for the image. However, as there is no easy to find documentation on
> the building system, I am stuck. For my configuration I have installed
> all packages, I only left out the task-base and task-extended (first
> part of the menu).
>
> It is really frustrating as I can't find any way to get into the
> window manager, the annoying login screen keeps on popping up. Running
> vnc viewer on my linux machine shows the login screen, but after
> logging in the connection to the beagleboard is closed. If I run the
> vncviewer after that, I get the login screen.
What I did this morning:
1) go to http://amethyst.openembedded.net/~koen/narcissus/
2) Check the following options:
[x] extended (task-base-extended)
Environment: [X11]
X11 window managers:
[x] Enlightenment
Additional console packages:
[x] Beagleboard demo
3) click "build me"
4) download the 2 files files
5) insert sd card into card reader
6) 'time zcat narcissus-test-image-beagleboard-sd.img.gz > /dev/
sdX' (takes slightly over 3 minutes on my old 1GB card)
7) remove and reinsert card
8) 'mount /dev/sdX2 /media/card -o async,relatime'
9) (as root) 'tar xjf beagleboard/2cca6e/narcissus-test-image-
beagleboard.tar.bz2 -C /media/card/ ; umount /media/card'
10) put card into beagle, apply power
That will start booting and after entering the new user details and
language selection I made the screenshot that's attached.
Now that we know one configuration that works, I'm curious what
combinations don't work :)
regards,
Koen
eelcor
I can't find any documentation.
On 1 jun, 11:39, Koen Kooi <k...@beagleboard.org> wrote:
> Op 1 jun 2009, om 08:55 heeft eelcor het volgende geschreven:
>
>
>
> > It seems to be a conflict between the various packages you can select
> > for the image. However, as there is no easy to find documentation on
> > the building system, I am stuck. For my configuration I have installed
> > all packages, I only left out the task-base and task-extended (first
> > part of the menu).
>
> > It is really frustrating as I can't find any way to get into the
> > window manager, the annoying login screen keeps on popping up. Running
> > vnc viewer on my linux machine shows the login screen, but after
> > logging in the connection to the beagleboard is closed. If I run the
> > vncviewer after that, I get the login screen.
>
> What I did this morning:
>
>
> [x] extended (task-base-extended)
> Environment: [X11]
> X11 window managers:
> [x] Enlightenment
> Additional console packages:
> [x] Beagleboard demo
>
> 3) click "build me"
> 4) download the 2 files files
> 5) insert sd card into card reader
> 6) 'time zcat narcissus-test-image-beagleboard-sd.img.gz > /dev/
> sdX' (takes slightly over 3 minutes on my old 1GB card)
> 7) remove and reinsert card
> 8) 'mount /dev/sdX2 /media/card -o async,relatime'
> 9) (as root) 'tar xjf beagleboard/2cca6e/narcissus-test-image-
> beagleboard.tar.bz2 -C /media/card/ ; umount /media/card'
> 10) put card into beagle, apply power
>
> That will start booting and after entering the new user details and
> language selection I made the screenshot that's attached.
>
> Now that we know one configuration that works, I'm curious what
> combinations don't work :)
>
> regards,
>
> Koen
>
> 102KWeergevenDownloaden
>
> PGP.sig
> < 1 KWeergevenDownloaden
eelcor
Did you get Quake (1, 2 or 3) to work with the image?
Regards, Eelco
>
> - Tekst uit oorspronkelijk bericht weergeven -
Joker B
the end the same thing always happens:
I put the SD card into the BB, power up and when it comes time to
autoboot:
"Hit any key to stop autoboot: 0
reading uImage
** Unable to read "uImage" from mmc 0:1 **
Wrong image format for bootm command
ERROR: Can't get kernel image!
OMAP3 beagleboard.org #"
Is my (C2) board in an incorrect state?
(The card I made according to directions from the Digikey video, then
tweaked around with R.Nelson's binary, DOES launch -- it jsut sadly
has no UVC or OpenCV support.)
kb
Dan
Joker B wrote:
> No matter whether I use zcat (as here) or dd to create the SD card, in
> the end the same thing always happens:
>
> I put the SD card into the BB, power up and when it comes time to
> autoboot:
>
> "Hit any key to stop autoboot: 0
> reading uImage
>
> ** Unable to read "uImage" from mmc 0:1 **
> Wrong image format for bootm command
> ERROR: Can't get kernel image!
> OMAP3 beagleboard.org #"
>
> Is my (C2) board in an incorrect state?
>
> (The card I made according to directions from the Digikey video, then
> tweaked around with R.Nelson's binary, DOES launch -- it jsut sadly
> has no UVC or OpenCV support.)
>
>
> kb
>
>
>
>
That sounds like your u-boot is looking for "uImage" but yours might be
named something else like "uImage.bin" or "uImage.fis". Is that the case?
- Dan
Joker B
as specified at
http://elinux.org/BeagleBoardBeginners#Writing_the_.C3.85ngstr.C3.B6m_image_into_the_SDcard_and_finally_booting_GNU.2FLinux
uses "uImage" only:
# setenv bootcmd 'mmcinit;fatload mmc 0 80300000 uImage;bootm
80300000'
In the long run, which do you think is better: altering the file(S) on
the SD or changing the botcmd env variable depending on which SD I
want to boot from?
(and hopefully this will find its way into the docs/pages as a guide
for other explorers....)
thanks!
kb
Joker B
up! :) :)
Dan
Joker B wrote:
> Dan, you nailed it! The narcissus SD has "uImage.bin" tho the bootcmd
> as specified at
> http://elinux.org/BeagleBoardBeginners#Writing_the_.C3.85ngstr.C3.B6m_image_into_the_SDcard_and_finally_booting_GNU.2FLinux
> uses "uImage" only:
>
> # setenv bootcmd 'mmcinit;fatload mmc 0 80300000 uImage;bootm
> 80300000'
>
> In the long run, which do you think is better: altering the file(S) on
> the SD or changing the botcmd env variable depending on which SD I
> want to boot from?
>
> (and hopefully this will find its way into the docs/pages as a guide
> for other explorers....)
>
> thanks!
> kb
>
rename the u-boot environment variable. I think that's how all of Koen's
new Angstrom demos work - with a "uImage.bin".
- Dan
Ihar Hrachyshka
>
> That worked! I am still curious why it doesn't work the way I did it,
> I can't find any documentation.