Newbie Install Woes, stuck in a getty loop! Options

[Wildherb]

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?

[Wildherb]

Doh!
Checking everything through I found the base41.tgz file on my CF card was not the correct size. I re-copied it and the Z now boots up just fine. ;o)

[mathemajikian]

Doh!
Checking everything through I found the base41.tgz file on my CF card was not the correct size. I re-copied it and the Z now boots up just fine. ;o)

Did you utilize the install files posted here: OpenBSD/Zaurus Installation Files ?
I made some changes to the SL-C3100 installation files and needed someone with a C3100 to verify their functionality.

[Wildherb]

Yes, I used those files but there is nothing wrong with the files themeselves, my problem was that one of the tgz files became trunkated during download. I downloaded it again and installation completed OK. My apologies, but it was late at night and I had overlooked checking the obvious before posting.

Briefly, OpenBSD was running on my 3100 and I had got WiFi working and could install packages . I was trying to get XFCE4 installed but unfortunately I've had a major crash and now require a rebuild. Oh well, tomorrow is another day!

My main concerns at the moment are:

1) The disk light is almost constantly on. Is this normal?
2) The machine will suspend (close clamshell or press power button) but will not resume (open clamshell or press power button). Am I missing something obvious?

For info I'm using *all* the 3100's disk for BSD

size offset fstype
a: 3.4G 0.0G 4.2BSD
b: 0.3G 3.4G swap
c: 3.8G 0.0G unused

I am a security professional so I'm quite excited about having OpenBSD on my Z. I just hope I can resolve these early teething troubles.

[Capn_Fish]

For the disk light, it is running from the microdrive, so that would be normal. For resuming, have you tried the home key? Never tried OBSD, but it may work.

[mathemajikian]

My main concerns at the moment are:

1) The disk light is almost constantly on. Is this normal?
2) The machine will suspend (close clamshell or press power button) but will not resume (open clamshell or press power button). Am I missing something obvious?

Both of these issues have been resolved in 4.1-current = 4.2-beta. You should follow the updating via cvs instructions found here: BSD Zaurus

See the following threads for more information:
Hdd Led
Suspend Crashes

[Wildherb]

My main concerns at the moment are:

1) The disk light is almost constantly on. Is this normal?
2) The machine will suspend (close clamshell or press power button) but will not resume (open clamshell or press power button). Am I missing something obvious?

Both of these issues have been resolved in 4.1-current = 4.2-beta. You should follow the updating via cvs instructions found here: BSD Zaurus

See the following threads for more information:
Hdd Led
Suspend Crashes

Hope I'm not missing something obvious again, but the FTP link on the exit3 site appears to be broken. I can connect to: ftp.openbsd.org/pub/ but there is no snapshots directory.

[mathemajikian]

Hope I'm not missing something obvious again, but the FTP link on the exit3 site appears to be broken. I can connect to: ftp.openbsd.org/pub/ but there is no snapshots directory.

ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus/

Maybe you forgot the OpenBSD portion?

[Wildherb]

Hope I'm not missing something obvious again, but the FTP link on the exit3 site appears to be broken. I can connect to: ftp.openbsd.org/pub/ but there is no snapshots directory.

ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus/

Maybe you forgot the OpenBSD portion?

Thanks, I'll give this a try.

I copied the link from here, which is missing the OpenBSD bit.
http://exit3.i-55.com/%7Exikon/ZaurusUpgrade.html

**************************************************************************
HOW TO UPGRADE YOUR OPENBSD ZAURUS TO CURRENT SNAPSHOT
**************************************************************************

Warning! upgrades of OpenBSD are currently only supported from the
immediately previous release.

a. Copy the latest and greatest zbsdmod.o and bsd.rd from
ftp.openbsd.org/pub/snapshots/zaurus to sd/cf card.

[mathemajikian]

And then again maybe I forgot the OpenBSD part. It's been corrected. Thanks!

[dbdg]

hello can i ask some newbie questions here?
i see that someone updated till openbsd-4.2-beta

1)have anyone screen rotation(under X) without restarting (XServer) or have plans to do it?
2)sd cards works or not?
3)have anyone working suspend? or maybe suspend not needed and just turn off backlight of lcd will safe same power?

sorry for bad english:)

[Wildherb]

Hope I'm not missing something obvious again, but the FTP link on the exit3 site appears to be broken. I can connect to: ftp.openbsd.org/pub/ but there is no snapshots directory.

ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus/

Maybe you forgot the OpenBSD portion?

Thanks, I'll give this a try.

I copied the link from here, which is missing the OpenBSD bit.
http://exit3.i-55.com/%7Exikon/ZaurusUpgrade.html

**************************************************************************
HOW TO UPGRADE YOUR OPENBSD ZAURUS TO CURRENT SNAPSHOT
**************************************************************************

Warning! upgrades of OpenBSD are currently only supported from the
immediately previous release.

a. Copy the latest and greatest zbsdmod.o and bsd.rd from
ftp.openbsd.org/pub/snapshots/zaurus to sd/cf card.

OK, I've ended up doing a complete rebuild using the latest 4.2 files and the good news is that the LED problem is now fixed.

Suspend/resume is not fixed, I have never managed to get my 3100 to resume, but I can now suspend it with the on/off button. After starting apmd I can also suspend it with zzz -z or zzz-S. Not being able to resume is a big problem, and from other threads it looks as if others such as Zdevil have also found it very frustrating. Did you ever find a fix ZDevil?

I am currently doing some builds from the port tree against my 4.2 system as the other 4.1 package feeds do not appear to be compatible. building from ports is slow but appears to work well so I am encouraged to persevere but I cant see that I will be able to stick with OpenBSD without being able to suspend/resume.

[ZDevil]

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.

[mathemajikian]

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.

[Wildherb]

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

Maybe someone else could give it a try?

Here's the 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.

Thanks, I'll try the CVS update although I am puzzled as to what difference this might make compared to rebuilding 4.2 from scratch.

I cannot recover network connection to the Z (not even PING) so I dont think it is resuming but with the screen turned off.