Author Topic: OZ336pre1+5600, boot to console?  (Read 2666 times)

zenken

  • Newbie
  • *
  • Posts: 17
    • View Profile
    • http://
OZ336pre1+5600, boot to console?
« on: August 02, 2004, 08:03:53 am »
Is there some script i can edit somewhere to make my
5600 with OZ336pre1 boot to a login: prompt instead
of to Opie?

Or is there some reliable way of shutting down Opie and
getting a login: prompt?

So that I can upgrade my Opie to 114 ... I really want to
voice recorder app    

thanks,
ken
5600 Poodle, OZ352, WinXP, Libranet281
256CF (hda1=vfat, hda2=ext2)

 Trying to make a multimedia poodle

lardman

  • Hero Member
  • *****
  • Posts: 4512
    • View Profile
    • http://people.bath.ac.uk/enpsgp/Zaurus/
OZ336pre1+5600, boot to console?
« Reply #1 on: August 02, 2004, 10:18:26 am »
Rename /etc/init.d/opie or change the names of the /etc/rc?.d/S??Opie files?

To just come out of it you could try running '/etc/init.d/opie stop' from the terminal within opie, or use the shutdown app to quit opie?


Si
C750 OZ3.5.4 (GPE, 2.6.x kernel)
SL5500 OZ3.5.4 (Opie)
Nokia 770
Serial GPS, WCF-12, Socket Ethernet & BT, Ratoc USB
WinXP, Mandriva

zenken

  • Newbie
  • *
  • Posts: 17
    • View Profile
    • http://
OZ336pre1+5600, boot to console?
« Reply #2 on: August 02, 2004, 09:35:01 pm »
renaming /etc/init.d/opie worked, thanks    

/etc/init.d/opie stop leads to login: prompt,
but keyboard doesn't work ... mostly frozen, some
keys produce characters on both press and release,
but wrong characters      

[Settings-Shutdown-TerminateOpie]  leads to GUI screen freeze, except
for tiny blinking square in bottom left    

now to work out how ipkg works !!
5600 Poodle, OZ352, WinXP, Libranet281
256CF (hda1=vfat, hda2=ext2)

 Trying to make a multimedia poodle

Mickeyl

  • Hero Member
  • *****
  • Posts: 1495
    • View Profile
    • http://www.Vanille.de
OZ336pre1+5600, boot to console?
« Reply #3 on: August 03, 2004, 08:17:31 am »
Opie inherited the shutdown problems from Qtopia. I'm slowly starting to improve things though. One of the coolest things I added is it now starts in the background like a real daemon and it runs on a dedicated terminal thus not rendering the current VT unusable.

There are still some bugs in the shutdown code which occasionally lead to a SIGSEGV which in turn prevents from important destructors being called... will fix that eventually.
Cheers,

Michael 'Mickey' Lauer | Embedded Linux Freelancer | www.Vanille-Media.de
Consider donating, if you like the software I contribute to.