Wally
I am a banana!
The Booting 3.2 Kernel at shutdown is annoying
It's sigstop and it's already doing that. It doesn't solve the clock problem.Hmm, the old powersave mode sent a sigpause to all running PNDs, right?
Why not do the same before going into suspend?
+1, label should change accordingly.The Booting 3.2 Kernel at shutdown is annoying
Create a file in the initialization stuff:I didn't know that command, my Linux knowledge is very limited indeed! Do I need to input this every time?
sudo gedit /etc/rc5.d/S98rc.local
modprobe ehci-hcd
sudo chmod +x /etc/rc5.d/S98rc.local
Doesn't reproduce here.Sound recording does not work with Beta 3. In Beta 2 I used
arecord -f cd -V mono -D hw:0,1 file.wav
But now I got arecord: pcm_read:1617: read error: Input/output error
I know that on PSP, the game is responsible for cleaning stuff up, stopping audio, etc. on suspend. I remember having to add special code when I did PicoDrive PSP port, Sony simply put all responsibility on the developer, they probably don't approve the game for release until it suspends properly.Dunno, was a blind idea ^^. I never used any form of suspend, even on laptops so it's all new here for me.How's that supposed to help with time jump problem?Isn't there a way to use bash job control before and after a suspend ?
I suppose this is a problem encountered on other platforms ? If yes maybe there's some tricks other ppl found ? (blind idea, again)
You will break powersaving if you do this.Create a file in the initialization stuff:I didn't know that command, my Linux knowledge is very limited indeed! Do I need to input this every time?
Code:sudo gedit /etc/rc5.d/S98rc.local
And add this in it:
Code:modprobe ehci-hcd
Save and exit. Now ensure the file can be executed:
Code:sudo chmod +x /etc/rc5.d/S98rc.local
Reboot.
Should work.
same here, use arecord -lWhat do you get if you enter
arecord -L
I've got only
null
Discard all samples (playback) or generate zero samples (capture)
Why is this needed, what's wrong with already included one?attached is module to use 8192cu chipset usb wifi dongle in experimental kernel. extract to root, sudo rmmod rtl8192cu, then sudo insmod <path to .ko>
In which way ? I mean it will just consume a bit more current or something more ?You will break powersaving if you do this.Create a file in the initialization stuff:I didn't know that command, my Linux knowledge is very limited indeed! Do I need to input this every time?
Code:sudo gedit /etc/rc5.d/S98rc.local
And add this in it:
Code:modprobe ehci-hcd
Save and exit. Now ensure the file can be executed:
Code:sudo chmod +x /etc/rc5.d/S98rc.local
Reboot.
Should work.
Why is this needed, what's wrong with already included one?attached is module to use 8192cu chipset usb wifi dongle in experimental kernel. extract to root, sudo rmmod rtl8192cu, then sudo insmod <path to .ko>
Use around 3x more power when idle, fail to suspend properly. Usual OMAP driver breakage, OMAP EHCI is poorly maintained in mainline. At least you can rmmod the damned thing and everything's back to normal.In which way ? I mean it will just consume a bit more current or something more ?You will break powersaving if you do this.Create a file in the initialization stuff:I didn't know that command, my Linux knowledge is very limited indeed! Do I need to input this every time?
Code:sudo gedit /etc/rc5.d/S98rc.local
And add this in it:
Code:modprobe ehci-hcd
Save and exit. Now ensure the file can be executed:
Code:sudo chmod +x /etc/rc5.d/S98rc.local
Reboot.
Should work.
Should be already done, unless it's broken.What about rmmod'ing ehci-hcd and all modules depending on this, in the suspend script ?
Doesn't happen for me, no idea.I've tried reflashing the firmware on my Pandora, but I still get the bug with power saving, that when I resume from it, my left nib stops working. I've tried resetting the nubs through the configuration, but it doesnt work. Even when I reboot, the nubs don't work properly again unless I boot into the older kernel.
It's PicoDrive bug, works on old kernel because of luck.I've also spotted graphical glitches using Picodrive on the new kernel which aren't present if using the older one(try running the Pal version of Sensible Soccer for easy evidence of this?)
What hub issue?Oh, I also didn't get to add that USB startup file yet, sounds like I should hold off on it for the time being? Will this USB hub issue be fixable in the next beta?
- reboot holding the R button and select to boot into CLI
- login with your useraccount
Strange... : In CLI mode (of kernel 3.2) my login credentials do not work! (Tried multiple boots and multiple logins)
Rebooted to MiniMenu, started Terminal, tested my username + password there, worked without any problems.
FYI: My username consists of 2 lowercase letters, password of lower case letters and numbers.
If I cannot get my login to work in CLI mode (why?), is it ok to start in GUI mode and switch to console via alt-ctrl-F1 and do it there?
I guess not as the GUI is still running in parallel...
Maybe log out from GUI, switch to console via alt-ctrl-F1, then try it. Then no user related stuff should be open (and endangered).
Other ideas?
attached is module to use 8192cu chipset usb wifi dongle in experimental kernel. extract to root, sudo rmmod rtl8192cu, then sudo insmod <path to .ko>
all compiling credit goes to Cloudef