fettouhi
Active Member
Might we see an update of xfce at some point? 4.10 has been out for some time now. SuperZaxxon seems to take quite a long time to boot compared to the last hotfix. Does the codec pack work with SuperZaxxon btw?
Release SuperZaxxon Final released!
- Thread starter EvilDragon
- Start date
slaeshjag
¯\_(ツ)_/¯
Userspace upgrades will come with .next.
Zink
Member
- Joined
- Mar 8, 2012
- Messages
- 170
spiralofhope
Member
That's really curious since things were working and after my doing things via symlink, but not after the update. Thanks for the tip, I'll investigate along those lines.
I'm not sure, but I thought there was a weakness in the hardware which made wifi poor.
Last edited by a moderator:
i was referring to initial connection to an access point (when the login wifi message box reappears repeatedly), on hotfix 6 no such issues. i think the hardware wifi issues relate to connection speed and disconnections when downloading large files?
hmc
Active Member
Thank you,
the workaround works flawlessly.
Kernel 3.2 now booting from SD.
Is there a way to have a choice between both kernels ON SD?
Thanks!
Daniel
Okay, I'll do more testings with the battery charging with brand new units.
As the charging chip learns with usage, it might be that the old setup (which wasn't 100% correct) fed the chip with bad values.
Maybe that's why the reports for the percentage of the battery is not correct.
These should automatically fix themselves after a few charging cycles, but I'll check with new units where no bad values have been learned yet.
As the charging chip learns with usage, it might be that the old setup (which wasn't 100% correct) fed the chip with bad values.
Maybe that's why the reports for the percentage of the battery is not correct.
These should automatically fix themselves after a few charging cycles, but I'll check with new units where no bad values have been learned yet.
White Demon
Sandy Wich's Boy
Thanks for this tip, I took the battery out for a few mintues not long after you posted, and when I put it back in the meter showed 94%.
Interesting. Maybe,as ED has noted, after a few charge cycles it might read correctly.
Also I have been meaning to install Conky for a while now. Definitely going to do that ASAP now.
The codec pack works under the SuperZaxxon, it was the first thing I tried.
And I have noticed that sometimes my Panda take a while to boot now too.
Last edited by a moderator:
Linux-SWAT
Forum Addict!
- Joined
- Feb 13, 2010
- Messages
- 9,194
udev slows down the boot process a lot.
It takes about 5 seconds before it continues to boot... same on my laptops.
I always wondered what udev is doing all the time...
It takes about 5 seconds before it continues to boot... same on my laptops.
I always wondered what udev is doing all the time...
notaz
Certified Guru
It's scanning every possible kernel module, then tries to modprobe various things. 3.2 has way more drivers so this process takes several times longer than on 2.6.
Thanks, now I finally know what udev does 
I guess that's the reason why a normal desktop system boots way faster if you compile your own kernel only selecting modules you really need on your system
I guess that's the reason why a normal desktop system boots way faster if you compile your own kernel only selecting modules you really need on your system
hmc
Active Member
Hi,
is there any reason, why you reconfigured uBoot to boot fro mthe root partition instead of booting from the boot partition of the SD card?
What about simply replacing the 2.6.x kernel image with the 3.2 kernel image on BOOT and keeping the default boot.txt and autoboot.txt as they were generated by the SD installer? Shouldn't this work, too?
If so, I think I would prefer that solution, due to the fact (which I learned just a few days ago), that if the root fs is flagged inconsistent and needs a check, the kernel on it cannot be booted, and the fs cannot be checked.
Thanks,
Daniel
hm, no way of letting uBoot offer the choice at boot time?
is there any reason, why you reconfigured uBoot to boot fro mthe root partition instead of booting from the boot partition of the SD card?
What about simply replacing the 2.6.x kernel image with the 3.2 kernel image on BOOT and keeping the default boot.txt and autoboot.txt as they were generated by the SD installer? Shouldn't this work, too?
If so, I think I would prefer that solution, due to the fact (which I learned just a few days ago), that if the root fs is flagged inconsistent and needs a check, the kernel on it cannot be booted, and the fs cannot be checked.
Thanks,
Daniel
hm, no way of letting uBoot offer the choice at boot time?
Kernel 3.2 was on the root-partition until the final release of SuperZaxxon.
The reason for that was that the boot-partition wasn't too big and we wanted to keep some space left there.
However, the reason for the NAND-Crashes were exactly what you mentioned above as well:
When the kernel was on an inconsistent file system, it couldn't boot anymore.
That's the reason that both Kernel 3.2 and Kernel 2.6 are now on the Boot-Partition of the NAND.
You can easily put the kernel onto your SD Card as well.
boot.txt and autoboot.txt are being read from the SD Card, so if you tell these files to boot the kernel from your card, then they will do that.
autoboot.txt is being autorun when the SD-Card is in whereas boot.txt is only being run if you select "Boot from SD:1" in the boot menu.
So you basically have the choice at boot-time and you can easily put your kernel on your SD-Card.
The reason for that was that the boot-partition wasn't too big and we wanted to keep some space left there.
However, the reason for the NAND-Crashes were exactly what you mentioned above as well:
When the kernel was on an inconsistent file system, it couldn't boot anymore.
That's the reason that both Kernel 3.2 and Kernel 2.6 are now on the Boot-Partition of the NAND.
You can easily put the kernel onto your SD Card as well.
boot.txt and autoboot.txt are being read from the SD Card, so if you tell these files to boot the kernel from your card, then they will do that.
autoboot.txt is being autorun when the SD-Card is in whereas boot.txt is only being run if you select "Boot from SD:1" in the boot menu.
So you basically have the choice at boot-time and you can easily put your kernel on your SD-Card.
Asmo
Advanced Member
- Joined
- Oct 18, 2008
- Messages
- 2,279
EDIT: Ninja'd by ED
For those still curious about 'fixing' an SD Installer created card, without having first installed Super Zaxxon firmware on Nand, is the uImage-3 kernel on http://openpandora.o...irmware/images/ ?
I resorted to extracting the rootfs.tar.bz2 image on PC so I could take it from there.
For those still curious about 'fixing' an SD Installer created card, without having first installed Super Zaxxon firmware on Nand, is the uImage-3 kernel on http://openpandora.o...irmware/images/ ?
I resorted to extracting the rootfs.tar.bz2 image on PC so I could take it from there.
Last edited by a moderator:
hmc
Active Member
The kernel was on SD card already, but it was in the root, not in the boot bartition, as per Gausen's workaround.
But I will now move it to the boot partiton again. It's better I guess ;-)
Oh, and the choice at boot time is "indirectly" possible then, by putting a reference to kernel 3.2 into autoboot.txt and a reference to the old kernel into boot.txt, so if I let it boot automatically, it boots 3.2 and if I boot from SD manually (R button), it boots 2.6. RIght? Well, not very elegant, but sounds doable.
What does this mean?
I wanted to reply to this one, too, now it's gone.Daniel
Last edited by a moderator:
hmc
Active Member
okay, found Asmo's post it in the browser cache ;-)
Some time ago I wrote about multiple partition boot setup from SD in the Pandora Wiki:
http://www.pandorawi...rds_for_booting
This explains some of the things in boot.txt and autoboot.txt.
HTH
Daniel
For those (like me) totally green on these matters, what should be added to the two .txt files read to allow switching kernels?
I don't have SuperZaxxon on Nand to refer to, when I fixed my SD installer created card I just took the two text files from Gausen's workaround, and changed 'uImage' to 'uImage-3'. Then I extracted the rootfs image on PC, and took the uImage-3 kernel from that, placing it in a newly created 'boot' folder in the ROOT partition of the card (some use of terminal, obv!). I'd like the dual option so I don't have to swap cards to see all my Mame stuff
Some time ago I wrote about multiple partition boot setup from SD in the Pandora Wiki:
http://www.pandorawi...rds_for_booting
This explains some of the things in boot.txt and autoboot.txt.
HTH
Daniel
Last edited by a moderator:
hmc
Active Member
I just updated that wiki page section with some clearer info and the recommendation to put the kernel into a dedicated boot partition:
http://www.pandorawiki.org/Running_Linux_from_an_SD_card#Setting_up_mutliple-partition_SD_cards_for_booting
http://www.pandorawiki.org/Running_Linux_from_an_SD_card#Setting_up_mutliple-partition_SD_cards_for_booting
Christoph.Krn
Advanced Member
Regarding the charging issue, I can report the following:
When my Pandora's battery meter was < 10% for the first time after SuperZaxxon final was installed, I connected the Pandora to mains power. Charging suddenly stopped at 24%. I unplugged the cable, but having read about the previous reports here, I assumed (yuck!) that this problem could be solved by re-plugging the power cable, and so I left the Pandora turned on for some time before shutting it down.
That was yesterday. Today I wanted to charge the Pandora, and so I plugged it in (without turning it on beforehand). It didn't power on when plugged into mains power (by the way, it's one of the Pandoras that don't work without a battery). After about 15 seconds I removed the power cable and booted the Pandora up. The battery meter showed 6% left, and after reconnecting the Pandora to power, it still didn't charge. Then I shut it down again.
Not knowing a lot about hardware, and in particular not about the low-level bootup-when-power-connected process of the Pandora (what parts are responsible for what there?), I figured it would be best to write here (feel free to move this post to a separate thread if you think that's better). What would be the best thing to do now? The Pandora can hand control over to code outside of the NAND when the Start button is held on bootup, but would loading Zaxxon (non-Super) from there help? Obviously, if only 6% of power are left in the battery and charging really doesn't work, then there's not much room for trial-and-error.
PS: I remember that at one time there used to be a shortage in the supply of chargers, and then for a limited time chargers from a different manufacturer were bundled with newly shipped Pandoras. I think I got one of those (my charger does *not* look like this charger, my Pandora was shipped to me on 2011-05-10 (date of shipment)). I don't own a PSP charger that I could try out.
When my Pandora's battery meter was < 10% for the first time after SuperZaxxon final was installed, I connected the Pandora to mains power. Charging suddenly stopped at 24%. I unplugged the cable, but having read about the previous reports here, I assumed (yuck!) that this problem could be solved by re-plugging the power cable, and so I left the Pandora turned on for some time before shutting it down.
That was yesterday. Today I wanted to charge the Pandora, and so I plugged it in (without turning it on beforehand). It didn't power on when plugged into mains power (by the way, it's one of the Pandoras that don't work without a battery). After about 15 seconds I removed the power cable and booted the Pandora up. The battery meter showed 6% left, and after reconnecting the Pandora to power, it still didn't charge. Then I shut it down again.
Not knowing a lot about hardware, and in particular not about the low-level bootup-when-power-connected process of the Pandora (what parts are responsible for what there?), I figured it would be best to write here (feel free to move this post to a separate thread if you think that's better). What would be the best thing to do now? The Pandora can hand control over to code outside of the NAND when the Start button is held on bootup, but would loading Zaxxon (non-Super) from there help? Obviously, if only 6% of power are left in the battery and charging really doesn't work, then there's not much room for trial-and-error.
PS: I remember that at one time there used to be a shortage in the supply of chargers, and then for a limited time chargers from a different manufacturer were bundled with newly shipped Pandoras. I think I got one of those (my charger does *not* look like this charger, my Pandora was shipped to me on 2011-05-10 (date of shipment)). I don't own a PSP charger that I could try out.
Last edited by a moderator:
