OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: gagware on June 15, 2006, 05:18:28 pm
-
I'm using Alt Boot to load into Opie - or well, that was the plan.
I stumbled (and got stuck) upon the 'new storage media detected screen'. Now I know that usually you have to remove the SD/CF cards after flashing/before booting, but since the loopfile is on SD that is not an option.
There should be some easy trick to bypass this screen, I searched on this forum and Google but I seem to be the only one that's stuck
Once I remember I got past it by loading into the console instead of the GUI and killing some SD related processes, but am not sure if this is ehhh...the appropriate way...
I'm using a SL-6000/Tosa and OZ 3.5.4, thanks.
-
I'm using Alt Boot to load into Opie - or well, that was the plan.
I stumbled (and got stuck) upon the 'new storage media detected screen'. Now I know that usually you have to remove the SD/CF cards after flashing/before booting, but since the loopfile is on SD that is not an option.
There should be some easy trick to bypass this screen, I searched on this forum and Google but I seem to be the only one that's stuck
Once I remember I got past it by loading into the console instead of the GUI and killing some SD related processes, but am not sure if this is ehhh...the appropriate way...
I'm using a SL-6000/Tosa and OZ 3.5.4, thanks.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=131315\"][{POST_SNAPBACK}][/a][/div]
I am having the same problem on my Collie as well.
-
I still have this problem, isn't there really anyone who knows how to solve it?
Anyway, I see I'm not alone anymore with this problem, hello Chris
-
I still have this problem, isn't there really anyone who knows how to solve it?
Anyway, I see I'm not alone anymore with this problem, hello Chris
[div align=\"right\"][a href=\"index.php?act=findpost&pid=133363\"][{POST_SNAPBACK}][/a][/div]
I saw someone in another thread ("hentges T1 akita rom"?) say they managed
to exit the dialogue after "pressing various key combinations"... although I still
can't get it to work, either :-(
-
Gary, you mean this post I presume?
Snappy, what do you do to get out of the wonderful De-You.... screen? Reboot/reset with the cards out or what?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=132325\"][{POST_SNAPBACK}][/a][/div]
Chris, I make sure everything is installed, oz/opie + cardfs ... #1 so I get the first boot with the size-me-up-dialog ( ) ....
#2 I just do a battery switch flip to power off and on.
#3 Remove SD and CF
#4 Pressed Cancel (a few times just in case) to power up.
#5 Got into opie screen calibrate page. Calibrate
#6 Got into OPIE with tabs but not all, since SD with cardfs is not inserted.
#7 Reboot or shutdown
#8 Insert SD before kernel finish loading, so that SD is loaded and cardfs is used
#8.5 The DocTab dialog pops up ... this time in right size. I clear everything.
#9 OZ boots and OPIE loads up with full hentges rom apps and tabs.
Its on my collie. Gonna try out gpe in awhile ... though unless I can get murphytalk running on opie or some form of chinese input in gpe, my Akita stays on Cacko1.23.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=132357\"][{POST_SNAPBACK}][/a][/div]
I didn't try it yet to be honest, am in a hurry to go to my work - but ehh wouldn't #2 (removing the battery/inserting it) mean it would reboot, ending up at the same screen? Anyway, I'm still puzzled.
As I said in my first post, I managed once to pass the screen (i.e. not get it on boot), but not loading into the GUI, kill some card related processes and then loading the GUI from the terminal. I tried it again of course, didn't work, I think I didn't kill the right process, and I don't want to do it over and over again - don't think my SD card likes it that much...
-
In GPE, Ctrl+Alt+Backspace sequence bypasses that dialog. (by restarting the X obviously)
It won't work in opie i guess, but if you have ability to change the VT and get a console, you can issue a ps aux command and kill that process maybe. Good luck.
-
Solved! Maybe not even the easiest way, but it worked for me. Humit, thanks for your tip, although I couldn't find a way to get a terminal running on my zaurus itself, it got me thinking and ended up with the following work-a-round.
Problem
Can't pass the 'new storage media detected' screen when booting into Opie using alt boot on a tosa (oz 3.5.4), probably also other models.
Fix
1. take your zaurus from the cradle and (re)boot it, choose to boot from SD/CF card in the alt boot menu
2. when the 'press any key within 5 seconds to cancel starting Opie' comes up do so (find the any key first ) and log into the console
3. before putting your zaurus back in the cradle (and lose the abbility to use the keyboard on a tosa) type '/etc/init.d/./opie start' (without the ' ', note the ./) in the console, don't press enter or OK, and put your zaurus in the cradle
>> make sure you've got a way to ssh into your zaurus, I at this point I had to put a static address for the usbd0 device in my /etc/network/interfaces
If you can't control your zaurus from another machine yet make sure you'll get this fixed first before continuing...
4. start a ssh connection from the other machine to your zaurus and log in
5. on your docked zaurus press the OK button which invokes the earlier typed '/etc/init.d/./opie start' command and loads Opie
>> on your zaurus now the 'new storage media detected screen appears
6. in the active ssh session type 'ps aux' at the console prompt and look for the process called '/opt/QtPalmtop/bin/qpe -terminal 2' and remember the process number (first nr. on the same line)
7. kill the process, in my case it was 2544 by typing 'kill 2544' at the console prompt (ssh)
>> the 'new storage media detected' screen should disappear on your zaurus and you can continue!
Gag.
-
Solved! Maybe not even the easiest way, but it worked for me. Humit, thanks for your tip, although I couldn't find a way to get a terminal running on my zaurus itself, it got me thinking and ended up with the following work-a-round.
Problem
Can't pass the 'new storage media detected' screen when booting into Opie using alt boot on a tosa (oz 3.5.4), probably also other models.
Fix
1. take your zaurus from the cradle and (re)boot it, choose to boot from SD/CF card in the alt boot menu
2. when the 'press any key within 5 seconds to cancel starting Opie' comes up do so (find the any key first ) and log into the console
3. before putting your zaurus back in the cradle (and lose the abbility to use the keyboard on a tosa) type '/etc/init.d/./opie start' (without the ' ', note the ./) in the console, don't press enter or OK, and put your zaurus in the cradle
>> make sure you've got a way to ssh into your zaurus, I at this point I had to put a static address for the usbd0 device in my /etc/network/interfaces
If you can't control your zaurus from another machine yet make sure you'll get this fixed first before continuing...
4. start a ssh connection from the other machine to your zaurus and log in
5. on your docked zaurus press the OK button which invokes the earlier typed '/etc/init.d/./opie start' command and loads Opie
>> on your zaurus now the 'new storage media detected screen appears
6. in the active ssh session type 'ps aux' at the console prompt and look for the process called '/opt/QtPalmtop/bin/qpe -terminal 2' and remember the process number (first nr. on the same line)
7. kill the process, in my case it was 2544 by typing 'kill 2544' at the console prompt (ssh)
>> the 'new storage media detected' screen should disappear on your zaurus and you can continue!
Gag.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=134255\"][{POST_SNAPBACK}][/a][/div]
Thanks for the solution. I found a work around a few weeks ago from another post by not having any media (CF or SD) in my machine for the first boot until the welcome to Opie sign comes up. I then pop both cards back in and it works fine. This has to be done only once.
Again, thanks for your feedback. I will keep your solution bookmarked in case of need.
Chris--
-
My earlier solution does exactly the same thing as what Chris' solution does.
-
My earlier solution does exactly the same thing as what Chris' solution does.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=134618\"][{POST_SNAPBACK}][/a][/div]
Actually, it may have been your post that I got the idea from.
Chris--
-
My earlier solution does exactly the same thing as what Chris' solution does.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=134618\"][{POST_SNAPBACK}][/a][/div]
Actually, it may have been your post that I got the idea from.
Chris--
[div align=\"right\"][a href=\"index.php?act=findpost&pid=134631\"][{POST_SNAPBACK}][/a][/div]
No worries ... I'm just glad that the nag screen can be bypassed.
-
I've come across this problem too - trying to setup boot from SD using a hentges tar.gz file. I've installed the filesystem to SD, and then when it tries to boot off the SD card, the "new storeage media detected" screen appears. I've tried a lot of different combinations of key presses, and nothing gets rid of it. I've also tried to boot into the console, kill SD related processes, and then run opie but that doesn't work either. I can't get USB networking to run, so can't ssh over USB to use the instructions above. I have got a wireless card (prism based), and have installed the necessary ipks from the command line to run it, but it doesn't start when I boot to console. Also, ifup wlan0 fails.
Does anyone have any other suggestions as to how to bypass this screen?
-
I've come across this problem too - trying to setup boot from SD using a hentges tar.gz file. I've installed the filesystem to SD, and then when it tries to boot off the SD card, the "new storeage media detected" screen appears. I've tried a lot of different combinations of key presses, and nothing gets rid of it. I've also tried to boot into the console, kill SD related processes, and then run opie but that doesn't work either. I can't get USB networking to run, so can't ssh over USB to use the instructions above. I have got a wireless card (prism based), and have installed the necessary ipks from the command line to run it, but it doesn't start when I boot to console. Also, ifup wlan0 fails.
Does anyone have any other suggestions as to how to bypass this screen?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136269\"][{POST_SNAPBACK}][/a][/div]
I just posted this on another thread. This thread says the issue is solved, in which it is not for Hentges tarball installations.
Chris--
-
thanks chrisl. hopefully there's a solution for non usb networked Zs