Gruso solved my problem on this thread in a separate topic I posted on a related matter.
My topic was here:
and his solution is here:
http://pandorawiki.org/Pnd_run.sh
It took some fiddling but I got it working for VLC and Midori. So anyone else asking this can get there answer above...
Thanks Gruso, I see you alot around here and am glad. I will try the pnd_run.sh on that page and wait for answers on the opkg
See you around!
Followup: I read the above page (http://pandorawiki.org/Pnd_run.sh)
Not a newbie solution I'd recommend but I got it working thank you. And it DOES...
What version os Angstrom Apps would one need from the repo as 2008 is no longer available?
Could someone make a disk version of the repo for archiving such as those by OSDisc.com (of which I have a few).
As a new Pandora RBE owner asking a lot of newbie questions I am going to start giving them Topics that announce them as such and hopefully help others find what I am sure are common questions (now or later).
OK, Angstrom announced that the 2008 apps are going going gone. So a double question...
So, now I have the USB2 port working (that was an adventure in forum searching - not always intuitive).
QUESTION: What is the difference in power usage & battery life with USB ports enabled at Boot in /etc/rc5.d/ verses normally not and later only enabled perhaps by a bash script when needed?
First I wanted to fix the default browser problem. I could not setup a PND browser as default.
fine, I realized that I could make a shell script like this
pnd_run /media/BOOT/pandora/menu/midori.pnd
and then set this "default-web.sh" file as the default browser.
so it works, now clicking...
success, and I learned a lot about the OS today.
Thanks. and it was the latest update to SD_install that forgot to add that detail. but you solved it. And I have saved this entire exchange as I do with all these solutions that work.
OK I dumped the emphasis. And yes, I added that above - that I tried both lid-close settings and this was attempted right after login with no apps started yet.
And this is with thhe OS on an Sd card. I am trying the updated NAND version now. Again, just a simple login then immediately try...
Last problem: now if I close the lid and then open it I get to stare at a dimly lit display with a flashing cursor in the upper left. Had to do a hard reboot...
And also, how do I set for low-power versus standby? I am reading this forum like mad and still have to ask these things...
Excellent, it now boots from the SD and gives me 3.2 after a uname -a as well. Got it! retrieving it from '/lib/boot/' once you told it was there - easy. Thanks.
Thanks
Thanks, maybe you could point me somewhere to understand the arguments or explain the basics. Here they are and I sincerely appreciate that you may save me from reflashing yet again. I did (or did not) do something....
[autoboot.txt]
setenv bootargs debug root=/dev/mmcblk0p3 rw rootdelay=2...
OK I finished reflashing the NAND and it boots to 3.2 Kernel by default.
I then ran SD_install and setup.
And when booting from the SD card I STILL get Kernel 2.6.27
It DOES say SuperZaxxon beta 3 and holding the [R] on powerup gives me the same boot choices with NORMAL supposed to be...
I misunderstood page 1
So I have to reflash the NAND before I can run SD_installer and put the new OS on an SD card. ARGH!
It'll be worth it. will I have to upgrade the NAND first everytime I want to upgrade the SD?
Now I have to ask again. Because I upgraded to SZb3 and am still booting with the old default kernel 2.6.27.
I was told upgrading the OS would upgrade the kernel which is all I originally wanted.
So how-now does the brown cow upgrade his kernels?
Not specific enough. I knew about that and understood the AutoLogin. It was the "Username Auto-populate of the login" that was the original question.
"Select Default User" is the option and answer.! Not exactly obvious for some of us.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.