OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

> Newbie Install Woes, stuck in a getty loop!
Wildherb
post Aug 11 2007, 02:15 PM
Post #1





Group: Members
Posts: 92
Joined: 9-January 06
Member No.: 8,887



Hello, this is my first post on this forum but I've had my 3100 for nearly 2 years and been through just about all the ROMs except OpenBSD so I thought I'd give it a try because I like X and want to use a 'native' system rather than a bolt-on or cut-down system.

I have decided to use 4.1 for now and I'm using this method to load the installer, and I've put the install sets on a CF card as I dont have an ethernet card for my Z (wireless only)

# insmod zbsdmod.o
# cp bsd.rd /proc/zboot

Everything seems to go OK. I get to calibrate the X screen and invited to reboot. At this point I copy the config file to /mnt/mtdflash2/pcmcia/config and reboot. The reboot gets as far as this, then gets stuck in a loop of getty messages.

init: kernel security level changed from 0 to 1
init: can't exec getty 'usr/libexec/getty for port /dev/ttyC0: no such file or directory
init: can't exec getty 'usr/libexec/getty for port /dev/ttyC1: no such file or directory

I've been through this twice with the same results. Any ideas what I can do?
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
ZDevil
post Aug 22 2007, 04:19 AM
Post #2





Group: Members
Posts: 2,003
Joined: 16-April 04
From: the Netherlands && /dev/null
Member No.: 2,882



Well, i don't actually have big problems with suspend and resume. The On/Off buttons works just fine.
Suspending by zzz works as expected. No issue so far (finger crossed).
Lid suspend has been reported to be broken under the current 4.2.
If the screen goes dark after resume, probably it's just because the backlight is turned off. Run a simple script with wsconsctl display.backlight=100 will bring the view back.
I do the same to adjust backlight (up and down) as well. (i.e. wsconsctl display.brightness+=1 and wsconsctl display.brightness-=1)

Good to see that some of us are building new stuff for 4.2!
I've already started a feed dedicated to 4.2. It is being constantly updated every day.
http://www.oesf.org/forums/index.php?showtopic=24586
All the packages there are compiled with optimization flags, so they are supposed to run faster than those without.
A million thanks to jpmatrix for offering the space to host the packages.

How about we compiling things in a kinda concerted fashion? We don't actually have to port things all on our own. You can ask jpmatrix for the detail of uploading your packages. smile.gif
Go to the top of the page
 
+Quote Post
mathemajikian
post Aug 22 2007, 04:49 AM
Post #3





Group: Members
Posts: 304
Joined: 8-July 06
From: United Kingdom for now....
Member No.: 10,349



QUOTE(ZDevil @ Aug 22 2007, 12:19 PM)
Lid suspend has been reported to be broken under the current 4.2.
If the screen goes dark after resume, probably it's just because the backlight is turned off. Run a simple script with wsconsctl display.backlight=100 will bring the view back.

The lid suspend function works if you update your sources via cvs and rebuild your system. It might appear that the Z is down for the count after doing a lid suspend, but as ZDevil stated it's just do to the fact that the backlight isn't turned back on after the resume. This could easily be corrected by making apmd run a /etc/rc.resume script after it resumes. However, this functionally doesn't seem to work as advertised. I've reported it but never received a response. Hopefully it will be corrected this release. Here's an example of what I've included in the /etc/rc.resume script.

#!/bin/sh
wsconsctl display.backlight=100


Here's some info from the man page:

Actions can be configured for the following five transitions: suspend,
standby, resume, powerup and powerdown. The suspend and standby actions
are run prior to apmd performing any other actions (such as disk syncs)
and entering the new state. The resume program is run after resuming
from a stand-by or suspended state. The powerup and powerdown programs
are run after the power status (AC connected or not) changes, as well as
after a resume (if the power status changed in the mean time).

/etc/apm/suspend
/etc/apm/standby
/etc/apm/resume
/etc/apm/powerup
/etc/apm/powerdown


These files contain the host's customized actions.
Each file must be an executable binary or shell
script suitable for execution by the execve(2)
function. If you wish to have the same program or
script control all transitions, it may determine
which transition is in progress by examining its
argv[0], which is set to one of suspend, standby,
resume, powerup, or powerdown.
Go to the top of the page
 
+Quote Post

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 23rd September 2014 - 12:26 PM