OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => OpenBSD => Topic started by: fquindos on May 20, 2006, 03:20:15 pm
-
Hello. I have consistent crashes when suspending for more than a few minutes. It doesn't matter if I click the power button, use "apm -S", "zzz" or close the lid with lidsuspend=1. Pressing the power button after it has been suspended for a short while works, but I get console messages saying, for example
wd0e: aborted command writing fsbn 5248 of 5248-5251 (wd0 bn 1562608; cn ...
wd0: soft error (corrected)
However, if I let the Zaurus sleep for 15 - 30 minutes, after pressing the power button the disk drive (green led) comes up, but the display remains black and the keyboard doesn't work. I need to do a reset.
Does anyone have any suggestion? Does it work for you?
By the way, I have a 3200 and an OpenBSD 3.9 snapshot. It also happened with 3.9-release and a prerelease snapshot.
Thank you,
Francisco
-
Same here on a 3000 with 3.9 snapshot. I've been leaving the Z running all the time.
-
I have only had the problem with suspending where it doesn't resume once. There is a seperate suspend issue where it won't resume after being charged if it has gone into a 'panic suspend' state due to low battery which may be resolved by resuming the unit a couple of times after plugging in the charger though.
The error that you receive is normal on the Zaurus and it just reflects that OpenBSD is writing the unflushed data that it needed to write but that was interrupted by the suspend sequence.
-Andy
-
I have only had the problem with suspending where it doesn't resume once. There is a seperate suspend issue where it won't resume after being charged if it has gone into a 'panic suspend' state due to low battery which may be resolved by resuming the unit a couple of times after plugging in the charger though.
The error that you receive is normal on the Zaurus and it just reflects that OpenBSD is writing the unflushed data that it needed to write but that was interrupted by the suspend sequence.
-Andy
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127986\"][{POST_SNAPBACK}][/a][/div]
I've also had the "panic suspend" issue on my 3000 where even after a charging the z wont turn on. eventually it did turn on after removing the battery, plugging/unplugging the power. I wish the z didn't lose charge so fast. I try to keep it plugged in when possible but it seems wrong that it would lose it's charge after a day of not being plugged in.
-
I have only had the problem with suspending where it doesn't resume once. There is a seperate suspend issue where it won't resume after being charged if it has gone into a 'panic suspend' state due to low battery which may be resolved by resuming the unit a couple of times after plugging in the charger though.
The error that you receive is normal on the Zaurus and it just reflects that OpenBSD is writing the unflushed data that it needed to write but that was interrupted by the suspend sequence.
-Andy
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127986\"][{POST_SNAPBACK}][/a][/div]
I've also had the "panic suspend" issue on my 3000 where even after a charging the z wont turn on. eventually it did turn on after removing the battery, plugging/unplugging the power. I wish the z didn't lose charge so fast. I try to keep it plugged in when possible but it seems wrong that it would lose it's charge after a day of not being plugged in.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128320\"][{POST_SNAPBACK}][/a][/div]
I would suggest cycling the unit at least once a month... full charge and let it run to panic suspend.
This helps to condition the battery. I do this and can reliably get 3 hours runtime (remember the hd is constantly active) and charge every 3 days or so if I'm using the unit infrequently.
-Andy
-
now in regards to a full charge... there's an orange led when the unit is charging, which is normal... my powerbook does the same. orange for charging, green for charged. there are times that apm will report the unit as 100% charged, but the light remains on. In fact, if I listened to apm's stats I'd probably never have a fully charged zaurus because it will report 100% charged after an hour or so when the light will actually remain orange for much longer - never timed it but 3-5 hours?
is this just my z or is it across the board?
-
Yes, I see that, too. Apm almost always tells me it's 100% charge. I've had the Zaurus off the charger for as long as an hour and apm tells me it's 90% I guess I get kickin' battery life.
-
Yes, I see that, too. Apm almost always tells me it's 100% charge. I've had the Zaurus off the charger for as long as an hour and apm tells me it's 90% I guess I get kickin' battery life.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128436\"][{POST_SNAPBACK}][/a][/div]
right...except that it will take an hour go from from 100% to 90% and then 10 minutes to go from 75% to 0%
-
Yes, apm charge not 100% means the battery is almost empty
I get more than 3 h, and that would be good enough if I could suspend.
But I can't. I need to shutdown because it is faster to restart with clean
filesystems. I was wondering what could be different between my setup,
that crashes always on suspend, and the setup of some of you, that only
crashes from time to time.
Any idea?
Yes, I see that, too. Apm almost always tells me it's 100% charge. I've had the Zaurus off the charger for as long as an hour and apm tells me it's 90% I guess I get kickin' battery life.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128436\"][{POST_SNAPBACK}][/a][/div]
right...except that it will take an hour go from from 100% to 90% and then 10 minutes to go from 75% to 0%
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128499\"][{POST_SNAPBACK}][/a][/div]
-
Suspend was working VERY well for me until recently. I'm not sure if it was something that has changed in recentish snapshots or just the face I've been running on the "cool" apm setting.
I haven't been in a convenient place to record the ddb info though.
I'm reinstalling with the latest snapshot today to see if that helps.
-
Does anyone have some news about this crash ? or knows a way to avoid it (other than never suspending) ?
The two latests snapshots works worst on this issue and seems not to be able to resume after a suspend (the bug is systematic).
(my zaurus is a C3100)
-
I've got it working on my C3000, mostly. I'm using a recent snapshot (June 12). apmd is NOT running, and I use the power button (hold it in for 2s) to suspend. I haven't done extensive testing, but I remember having issues when running at 90mhz, but 208 has been working just fine.
-
http://marc.theaimsgroup.com/?l=openbsd-cv...82806831678&w=2 (http://marc.theaimsgroup.com/?l=openbsd-cvs&m=115082806831678&w=2)
Looks like it's been fixed...
-
http://marc.theaimsgroup.com/?l=openbsd-cv...82806831678&w=2 (http://marc.theaimsgroup.com/?l=openbsd-cvs&m=115082806831678&w=2)
Looks like it's been fixed...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=132074\"][{POST_SNAPBACK}][/a][/div]
Yep, it seems fixed in the 3.9 stable. But it looks like there is a new bug introduced in snapshot.
However, hugs to the guy that fixed it
-
Yep, it seems fixed in the 3.9 stable. But it looks like there is a new bug introduced in snapshot.
yes,
i've installed latest snapshot and the suspend bug is still there...
did someone find a proper method to suspend ?
mine for now is to boot qtopia then suspend.........
except from that i'm totally happy about OpenBSD on my Z ! keep up the good work!
-
The latest snapshot totally bails for me (booting bsd.rd). Looks like it may (and I don't know what I'm doing ) be related to recent disklabel work.
-
Hello. I have consistent crashes when suspending for more than a few minutes. It doesn't matter if I click the power button, use "apm -S", "zzz" or close the lid with lidsuspend=1. Pressing the power button after it has been suspended for a short while works, but I get console messages saying, for example
wd0e: aborted command writing fsbn 5248 of 5248-5251 (wd0 bn 1562608; cn ...
wd0: soft error (corrected)
However, if I let the Zaurus sleep for 15 - 30 minutes, after pressing the power button the disk drive (green led) comes up, but the display remains black and the keyboard doesn't work. I need to do a reset.
Does anyone have any suggestion? Does it work for you?
By the way, I have a 3200 and an OpenBSD 3.9 snapshot. It also happened with 3.9-release and a prerelease snapshot.
Thank you,
Francisco
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127887\"][{POST_SNAPBACK}][/a][/div]
well,
i've just tried to suspend with my 4.0beta-slc3000 and :
-apm -S : does nothing (!!)
-zzz : error message = cannot connect to apmd
-power button : works! then i waited for 1 minute then i tried to switch on the Z and i 'd the same wd0 error messsage like you but it worked! right now i'm trying to suspend it for 1 hour and i'll see if it switchs on again
see you soon
(hope!)
ps: apm tells me "91% batt remaining" .... the zaurus is not power connected.
-
well,
i've just tried to suspend with my 4.0beta-slc3000 and :
-apm -S : does nothing (!!)
-zzz : error message = cannot connect to apmd
-power button : works! then i waited for 1 minute then i tried to switch on the Z and i 'd the same wd0 error messsage like you but it worked! right now i'm trying to suspend it for 1 hour and i'll see if it switchs on again
see you soon
(hope!)
ps: apm tells me "91% batt remaining" .... the zaurus is not power connected.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=144572\"][{POST_SNAPBACK}][/a][/div]
If apmd is not running the zzz command will not work. I haven't tried apmd with the snap I'm running, but after reinstalling (3.9 then updating to the latest snap) suspend is finally working for me again...
-
I had the same problem booting the 4.0 snap bsd.rd. I ended up going to 3.9 release. Guess I'll try 4.0 again now.
-
Hello. I have consistent crashes when suspending for more than a few minutes. It doesn't matter if I click the power button, use "apm -S", "zzz" or close the lid with lidsuspend=1. Pressing the power button after it has been suspended for a short while works, but I get console messages saying, for example
wd0e: aborted command writing fsbn 5248 of 5248-5251 (wd0 bn 1562608; cn ...
wd0: soft error (corrected)
However, if I let the Zaurus sleep for 15 - 30 minutes, after pressing the power button the disk drive (green led) comes up, but the display remains black and the keyboard doesn't work. I need to do a reset.
Does anyone have any suggestion? Does it work for you?
By the way, I have a 3200 and an OpenBSD 3.9 snapshot. It also happened with 3.9-release and a prerelease snapshot.
Thank you,
Francisco
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127887\"][{POST_SNAPBACK}][/a][/div]
well,
i've just tried to suspend with my 4.0beta-slc3000 and :
-apm -S : does nothing (!!)
-zzz : error message = cannot connect to apmd
-power button : works! then i waited for 1 minute then i tried to switch on the Z and i 'd the same wd0 error messsage like you but it worked! right now i'm trying to suspend it for 1 hour and i'll see if it switchs on again
see you soon
(hope!)
ps: apm tells me "91% batt remaining" .... the zaurus is not power connected.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=144572\"][{POST_SNAPBACK}][/a][/div]
hello again
i woke up my 4.0 openbsd zaurus this morning and it sent me en error message then it felt into debug mode !!!
i found a "boot reboot" command to reboot, i didn't find a 'quit' command...
-
hi
yesterday night i started some compilation and i turned off the screen via this command:
wsconsctl display.backlight=0
this morning i could not find any way to resume the Zaurus... it ended up with hard battery removal...any idea?
-
I also run into issues of apm:
-- closing the lid (with the setting in /etc/sysctl.conf): fails to resume; screen remains dark; but it is surely on because Ctrl-Alt-BS will kill X.
-- pressing the power button to suspend: [EDITED: just tested again. it seems to work now. need more testing ... ]
-- It seems running apmd and suspending with "zzz" works fine so far, although it did fail a couple of times also.
About apm:
How can i check the exact percentage of battery power? i type apm and it keeps saying the battery is 100% all the time both with and without AC.
Thanks!
-
hi
yesterday night i started some compilation and i turned off the screen via this command:
wsconsctl display.backlight=0
this morning i could not find any way to resume the Zaurus... it ended up with hard battery removal...any idea?
Did you reissue the following command?
wsconsctl display.backlight=100
-
hi
yesterday night i started some compilation and i turned off the screen via this command:
wsconsctl display.backlight=0
this morning i could not find any way to resume the Zaurus... it ended up with hard battery removal...any idea?
Did you reissue the following command?
wsconsctl display.backlight=100
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160586\"][{POST_SNAPBACK}][/a][/div]
do you mean i've to type that command each type i typed the =0 one ??? isn't it automatic as you type any key or use the stylus?
-
hi
yesterday night i started some compilation and i turned off the screen via this command:
wsconsctl display.backlight=0
this morning i could not find any way to resume the Zaurus... it ended up with hard battery removal...any idea?
Did you reissue the following command?
wsconsctl display.backlight=100
do you mean i've to type that command each type i typed the =0 one ??? isn't it automatic as you type any key or use the stylus?
wsconsctl display.backlight=0 turns the LCD back light off. To turn the back light back on you'll have to issue the inverse command wsconsctl display.backlight=100. Pressing random keys or tapping the LCD screen with the stylus will not result in the LCD back light turning back on.
-
hi
yesterday night i started some compilation and i turned off the screen via this command:
wsconsctl display.backlight=0
this morning i could not find any way to resume the Zaurus... it ended up with hard battery removal...any idea?
Did you reissue the following command?
wsconsctl display.backlight=100
do you mean i've to type that command each type i typed the =0 one ??? isn't it automatic as you type any key or use the stylus?
wsconsctl display.backlight=0 turns the LCD back light off. To turn the back light back on you'll have to issue the inverse command wsconsctl display.backlight=100. Pressing random keys or tapping the LCD screen with the stylus will not result in the LCD back light turning back on.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]
(http://index.php?act=findpost&pid=160629\")
okay!
so that should be specified in that tip&tricks pages :
[a href=\"http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html]http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html[/url]
http://planetofidiots.com/zaurus/#afterboot (http://planetofidiots.com/zaurus/#afterboot)
-
hi
yesterday night i started some compilation and i turned off the screen via this command:
wsconsctl display.backlight=0
this morning i could not find any way to resume the Zaurus... it ended up with hard battery removal...any idea?
Did you reissue the following command?
wsconsctl display.backlight=100
do you mean i've to type that command each type i typed the =0 one ??? isn't it automatic as you type any key or use the stylus?
wsconsctl display.backlight=0 turns the LCD back light off. To turn the back light back on you'll have to issue the inverse command wsconsctl display.backlight=100. Pressing random keys or tapping the LCD screen with the stylus will not result in the LCD back light turning back on.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]
(http://index.php?act=findpost&pid=160629\")
okay!
so that should be specified in that tip&tricks pages :
[a href=\"http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html]http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html[/url]
http://planetofidiots.com/zaurus/#afterboot (http://planetofidiots.com/zaurus/#afterboot)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160631\"][{POST_SNAPBACK}][/a][/div]
that makes sense, it sounds logical, but isn't very user friendly
-
okay! so that should be specified in that tip&tricks pages :
http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html (http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html)
http://planetofidiots.com/zaurus/#afterboot (http://planetofidiots.com/zaurus/#afterboot)
Done.
-
Here is what i got more than once when the Z fails to resume:
wdc0:0:0: not ready, st = 0x88, err = 0x00
wdc0 channel 0: reset failed for drive 0
wd0f : device timeout reading fsbn 156672 of 156672-0 (wd0 bn 7791264 cn 7729 tn 6 sn 54)
It seems that resuming in X works better than in console. Maybe i am wrong.
Also does the close-lip-to-suspend thing involve both suspend and turning off the lcd?
-
Here is what i got more than once when the Z fails to resume:
wdc0:0:0: not ready, st = 0x88, err = 0x00
wdc0 channel 0: reset failed for drive 0
wd0f : device timeout reading fsbn 156672 of 156672-0 (wd0 bn 7791264 cn 7729 tn 6 sn 54)
It seems that resuming in X works better than in console. Maybe i am wrong.
Also does the close-lip-to-suspend thing involve both suspend and turning off the lcd?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160638\"][{POST_SNAPBACK}][/a][/div]
What does your /etc/fstab look like? Have you enable the microdrives cache?
-
What does your /etc/fstab look like? Have you enable the microdrives cache?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=160648\")
This is my /etc/fstab. Thanks!
/dev/wd0a / ffs rw,noatime,softdep 1 1
/dev/wd0d /home ffs rw,noatime,softdep 1 2
/dev/wd0e /tmp ffs rw,noatime,softdep 1 2
/dev/wd0f /usr ffs rw,noatime,softdep 1 2
/dev/wd0g /home ffs rw,noatime,softdep 1 2
And i have harddisk cache enabled, following the suggestions in [a href=\"http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html]http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html[/url]
-
Here is what i got more than once when the Z fails to resume:
wdc0:0:0: not ready, st = 0x88, err = 0x00
wdc0 channel 0: reset failed for drive 0
wd0f : device timeout reading fsbn 156672 of 156672-0 (wd0 bn 7791264 cn 7729 tn 6 sn 54)
It seems that resuming in X works better than in console. Maybe i am wrong.
Also does the close-lip-to-suspend thing involve both suspend and turning off the lcd?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160638\"][{POST_SNAPBACK}][/a][/div]
well
it seems today i felt into a resume bug too......i suspend this morning (in X under fluxbox) and this afternoon it was impossible to resume............ i had to remove the battery...
i wonder if it could be linked to my old zbsdmod.o/zboot in my flash...i'm updating to see if it helps...
-
This is what mathemajikian told me today:
For a normal openbsd system I would use the 6 partitions. The Z it has to read the drive upon resuming, and 6 partitions might be a little to much for the slow hard drive. Thats why you are seeing those errors when you resume. The disks motor can't keep up with the kernel requests.
I am using 6 partitions following the advice here: http://www.planetofidiots.com/zaurus/#install (http://www.planetofidiots.com/zaurus/#install)
So there seem to be two solutions:
1) Use one big partitions for everything + one swap partition (or simply one partition with swapfile -- which one is better?)
2) Swap the internal MD with a hi-speed CF
Anyway i will install the system again in one big partition and see if the problem persists.
-
This is what mathemajikian told me today:
For a normal Openbsd system I would use the 6 partitions. The Z has to read the drive upon resuming, and 6 partitions might be a little to much for the slow hard drive. Thats why you are seeing those errors when you resume. The micro drives motor can't keep up with the kernel requests.
I am using 6 partitions following the advice here: http://www.planetofidiots.com/zaurus/#install (http://www.planetofidiots.com/zaurus/#install)
So there seem to be two solutions:
1) Use one big partitions for everything + one swap partition (or simply one partition with swapfile -- which one is better?)
2) Swap the internal MD with a hi-speed CF
Anyway i will install the system again in one big partition and see if the problem persists.
What's the output of the following two commands:
# fdisk wd0
# disklabel wd0
If you created the partitions outside the bounds of the disk, then you would be attempting to read beyond the disk and this could cause these errors. I would try and use the one big partition wd0a + swap. Remember not to change wd0c.
-
What does your /etc/fstab look like? Have you enable the microdrives cache?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160648\"][{POST_SNAPBACK}][/a][/div]
This is my /etc/fstab. Thanks!
/dev/wd0a / ffs rw,noatime,softdep 1 1
/dev/wd0d /home ffs rw,noatime,softdep 1 2
/dev/wd0e /tmp ffs rw,noatime,softdep 1 2
/dev/wd0f /usr ffs rw,noatime,softdep 1 2
/dev/wd0g /home ffs rw,noatime,softdep 1 2
Also, I just noticed that you have softdep in your fstab. This will not work with the snapshot GENERIC kernel! In order to utilize softdep you'll have to rebuild the kernel from source with the following option:
option FFS_SOFTUPDATES
-
Here are the results of both:
Disk: wd0 geometry: 11905/16/63 [12000556 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
------------------------------------------------------------------------
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
*3: A6 0 1 1 - 11904 15 63 [ 63: 12000177 ] OpenBSD
# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: HMS360606D5CF00
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 11905
total sectors: 12000556
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg]
a: 409185 63 4.2BSD 2048 16384 1 # Cyl 0*- 405
b: 524160 409248 swap # Cyl 406 - 925
c: 12000556 0 unused 0 0 # Cyl 0 - 11905*
d: 408240 933408 4.2BSD 2048 16384 1 # Cyl 926 - 1330
e: 6290928 1342656 4.2BSD 2048 16384 1 # Cyl 1332 - 7572
f: 613872 7634592 4.2BSD 2048 16384 1 # Cyl 7574 - 8182
g: 3750768 8249472 4.2BSD 2048 16384 1 # Cyl 8184 - 11904
-
Also, I just noticed that you have softdep in your fstab. This will not work with the snapshot GENERIC kernel! In order to utilize softdep you'll have to rebuild the kernel from source with the following option:
option FFS_SOFTUPDATES
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160719\"][{POST_SNAPBACK}][/a][/div]
Thanks. But I am not yet familiar with obsd, let alone compiling the kernel. So would it be possible for you to upload the new kernel somewhere? Thanks in advance!
-
What does your /etc/fstab look like? Have you enable the microdrives cache?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160648\"][{POST_SNAPBACK}][/a][/div]
This is my /etc/fstab. Thanks!
/dev/wd0a / ffs rw,noatime,softdep 1 1
/dev/wd0d /home ffs rw,noatime,softdep 1 2
/dev/wd0e /tmp ffs rw,noatime,softdep 1 2
/dev/wd0f /usr ffs rw,noatime,softdep 1 2
/dev/wd0g /home ffs rw,noatime,softdep 1 2
Also, I just noticed that you have softdep in your fstab. This will not work with the snapshot GENERIC kernel! In order to utilize softdep you'll have to rebuild the kernel from source with the following option:
option FFS_SOFTUPDATES
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160719\"][{POST_SNAPBACK}][/a][/div]
ok for the softdep, but since i put noatime in /, now the boot process is much much longer: after the "/dev/rwd0a: file system is clean; not checking", the zaurus is doing something with the harddrive for a long time before the boot continue.....
what is happenning there???
EDITED:
after the long wait, i finally have this message:
/dev/rwd0j: Invalid signature in fsinfo block/dev/dwd0j: 74237 files, 887368 free (221842 clusters)
what does it mean??
-
Also, I just noticed that you have softdep in your fstab. This will not work with the snapshot GENERIC kernel! In order to utilize softdep you'll have to rebuild the kernel from source with the following option:
option FFS_SOFTUPDATES
It's compiled in GENERIC now, so you should be fine with softdep in your fstab:
To use Soft Updates, your kernel must have
option FFS_SOFTUPDATES
compiled in, this is already in place on GENERIC.
-
it seems i went again into an mission impossible to resume ! ... even the charge light didn't lit... only way was to remove battery....
any clue about that ??
-
The suspend problem doesn't go away, and actually becomes even worse, since I reinstalled the system from the latest snapshots in one partition last night (i did absolutely nothing else apart from following the Afterboot suggestions religiously.
zzz suspend can be resumed sometimes, but fails sometimes as well;
closing lid to suspend fails to resume *100%* of the time.
Is it really that there is nothing broken in the apm, or i go wrong somewhere?
Suspend/resume is such a basic thing that must work out of the box for a healthy distro, isn't it?
Now i am really confused about what to do with the setup ...
-
Also can someone kindly tell me explicitly how to use apm or other means to show accurate remaining power?
I've tried all the options possible with apm and only have 100% or 180 minutes all the time. Even though the battery is actually running low (when i boot into cacko and check).
-
Okay, just to be more precise to the symptoms:
When suspending in console (both zzz and closing the lid), resume will produce a very short white flash on the screen, followed by screen black out. Typing "wsconsctl display.backlight=100" doesn't work at all.
After waiting a while i see the green light on, which i guess is the system trying desparately to resume the microdrive, but keeps failing (sometimes i see the error message of failing to reset wdc0 blah, but most of the time just everything in the dark).
When suspending in X, resume usually can bring the screen back, but then the system freezes. After a while the screen goes dark and the green LED turns on, which probably also indicate the harddrive reset failure ...
***
So here i would really appreciate clear answers to the questions ( the more i read the documentation and the tips pages, the more i seem to get confused, just because things do not work as described )
Sorry for getting a bit paranoid now because i am beginning to get a bit frustrated after spending two weeks without getting a stable enough system working.
1) Which version is actually more preferred? The snapshots (which I've been trying to get working but always got errors) or the "official" releases (from the 4.1 dir)?
2) What should I put in /etc/fstab about wd0 if I install the snaphot in one big partition?
3) Should writecacheenable be enabled or not?
4) About swapfile: is it fine to set up swapfile after installing *everything* (including all the distribution sets) in one big partition?
5) And of course, what is the source of the suspend trouble? Frankly, I have already tested a few dozen times (believe me) trying to exhaust all the possibilities: with/without memory cards mounted, with/without cards inserted, with/without AC, with/without disk cache, with/without turning on mechdep.lidsuspend in /etc/sysctl.conf ...
-
Sorry for getting a bit paranoid now because i am beginning to get a bit frustrated after spending two weeks without getting a stable enough system working.
1) Which version is actually more preferred? The snapshots (which I've been trying to get working but always got errors) or the "official" releases (from the 4.1 dir)?
Releases are generally preferred. Snapshots = -current which is the bleeding edge, and as stated before there can be a lot of bleeding involved!
2) What should I put in /etc/fstab about wd0 if I install the snaphot in one big partition?
If your swap file is on this partition then you can't put in softdep. Other than that you should be fine.
3) Should writecacheenable be enabled or not?
Your choice.
4) About swapfile: is it fine to set up swapfile after installing *everything* (including all the distribution sets) in one big partition?
I don't see any problems with this, but thats just me.
5) And of course, what is the source of the suspend trouble? Frankly, I have already tested a few dozen times (believe me) trying to exhaust all the possibilities: with/without memory cards mounted, with/without cards inserted, with/without AC, with/without disk cache, with/without turning on mechdep.lidsuspend in /etc/sysctl.conf ...
Try this:
use zzz -z suspend and see if it still fails to resume, if so then try zzz -S standby and see what happens.
zzz -z suspend puts the Z in a deep sleep whereas zzz -S standby puts the Z in a light sleep.
If that doesn't work then use shutdown -hp now until the problem is corrected. If you can't wait then convert back to a penguin distribution.
-
Also can someone kindly tell me explicitly how to use apm or other means to show accurate remaining power?
I've tried all the options possible with apm and only have 100% or 180 minutes all the time. Even though the battery is actually running low (when i boot into cacko and check).
The apm battery monitor doesn't work all that great. Here's a list of known problems which are currently being worked on:
* Repair pcmcia issues that are causing "white-out" problems with some devices.
* Fix the odd suspend crashing bugs and RTC skew.
* C860/C1000 support.
* Support the I2C GPIO controller (C3100 and C3200) using the machine-independent i2c code.
* Internal flash memory support as a sd(4) device.
* Fix battery drain during suspend.
* Fix remaining issues in SDIO support.
-
5) And of course, what is the source of the suspend trouble? Frankly, I have already tested a few dozen times (believe me) trying to exhaust all the possibilities: with/without memory cards mounted, with/without cards inserted, with/without AC, with/without disk cache, with/without turning on mechdep.lidsuspend in /etc/sysctl.conf ...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160982\"][{POST_SNAPBACK}][/a][/div]
well well,
i only use the button to suspend and resume (as i'm compiling a lot under the console), and it seems i've less troubles than you... by the way which zaurus model do you have ?
-
well well,
i only use the button to suspend and resume (as i'm compiling a lot under the console), and it seems i've less troubles than you... by the way which zaurus model do you have ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161042\"][{POST_SNAPBACK}][/a][/div]
Mine is 3200.
Do you mean using the On/Off button to suspend only? I cannot resume when suspending this way.
Which version (snapshots or official release or your own build) do you use?
How do you partition the space?
What are your settings with respect to the harddrive(/etc/fstab, /etc/sysctl.conf, /etc/rc.local. etc)?
Sorry for asking so many questions. I tried mathemajikan's advice but the same story.
How can i use a machine which cannot suspend and resume properly?
-
Thanks again.
1) Which version is actually more preferred? The snapshots (which I've been trying to get working but always got errors) or the "official" releases (from the 4.1 dir)?
Releases are generally preferred. Snapshots = -current which is the bleeding edge, and as stated before there can be a lot of bleeding involved!
But iirc somewhere in the documentatiopn says snapshots are better ...
2) What should I put in /etc/fstab about wd0 if I install the snaphot in one big partition?
If your swap file is on this partition then you can't put in softdep. Other than that you should be fine.
I only add noatime to wd0 and not softdep. Didn't notice anything different.
Try this:
use zzz -z suspend and see if it still fails to resume, if so then try zzz -S standby and see what happens.
zzz -z suspend puts the Z in a deep sleep whereas zzz -S standby puts the Z in a light sleep.
If that doesn't work then use shutdown -hp now until the problem is corrected. If you can't wait then convert back to a penguin distribution.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160987\"][{POST_SNAPBACK}][/a][/div]
Tried both zzz -z suspend and zzz -S standby. Resume still fails.
-
well well,
i only use the button to suspend and resume (as i'm compiling a lot under the console), and it seems i've less troubles than you... by the way which zaurus model do you have ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161042\"][{POST_SNAPBACK}][/a][/div]
Mine is 3200.
Do you mean using the On/Off button to suspend only? I cannot resume when suspending this way.
Which version (snapshots or official release or your own build) do you use?
How do you partition the space?
What are your settings with respect to the harddrive(/etc/fstab, /etc/sysctl.conf, /etc/rc.local. etc)?
Sorry for asking so many questions. I tried mathemajikan's advice but the same story.
How can i use a machine which cannot suspend and resume properly?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161044\"][{POST_SNAPBACK}][/a][/div]
yes i always suspend using the on/off button. most of the times it works well, although i had some strange resume problems like you some times : same wd0 errors, or resume flashing the screen...
i think developpers will find what is happenning bad, i remember on my initial openbsd installation years ago suspend/resume was not working at all !! (see firsts messages of this post so let's wait, report and see
my partition layout is from pdaxii13 install process, so 2GB/128MB/2GB, but i only use the first partition for openbsd which i cut into 1.8MB BSD and 0.2MB for swap. however it is not a very good layout because my bsd partition appears to be too small...
in sysctl.conf i didn't put suspend on lit.
i cannot tell you more because i haven't my Z with me : i let it home compiling kdepim and it was compiling mysql when i left
hope this helps
JP
-
Thanks. Now I will reinstall the whole thing with the 4.1 release version and see if things get any better...
-
well well,
i think we still have some resume troubles: this morning i hit the ON button, then the screen resume with hard drive error messages like this one :
wdc0 channel 0: reset failed for drive 0
wd0a: device timeout reading fsbn 1595200 of 1595200-0 (wd0 bn 1595201; cn 1582 tn 8 sn 41), retrying
wdc0:0:0: not ready,st=0x88<BSY,DRQ>, err=0x00
and the harddrive green light stays on.........
i'll google search for this messages
-
well well,
i think we still have some resume troubles: this morning i hit the ON button, then the screen resume with hard drive error messages like this one :
wdc0 channel 0: reset failed for drive 0
wd0a: device timeout reading fsbn 1595200 of 1595200-0 (wd0 bn 1595201; cn 1582 tn 8 sn 41), retrying
wdc0:0:0: not ready,st=0x88<BSY,DRQ>, err=0x00
and the harddrive green light stays on.........
i'll google search for this messages
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161132\"][{POST_SNAPBACK}][/a][/div]
Hey, this is exactly what i've run into almost all the time! So i am not the only one...
The constantly lit green light seems to indicate that the system is trying desparately to get the harddrive resumed, but keep failing ...
So now i am quite sure that there is something wrong with apm in the builds.
Yet I've installed the 4.1 release version. It seems zzz works again. Perhaps the release version is more stable? Will test further.
One difference i notice in the 4.1 release build: the green LED is always on even though the hard drive is not spinning.
Haven't tried "lidsuspend", which doesn't seem to work at all, i'm afraid.
(But see my next post below... )
-
the release version seems to be rather old on
ftp://ftp.openbsd.org/pub/OpenBSD/4.1/zaurus (http://ftp://ftp.openbsd.org/pub/OpenBSD/4.1/zaurus) : march 2007
latest snapshot is may 08
i wonder if i wait for the next snapshot...
-
the release version seems to be rather old on
ftp://ftp.openbsd.org/pub/OpenBSD/4.1/zaurus (http://ftp://ftp.openbsd.org/pub/OpenBSD/4.1/zaurus) : march 2007
latest snapshot is may 08
i wonder if i wait for the next snapshot...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161145\"][{POST_SNAPBACK}][/a][/div]
or better yet why not update your sources and rebuild the kernel and user world? Then you wont have to wait for the next snapshot.
-
the release version seems to be rather old on
ftp://ftp.openbsd.org/pub/OpenBSD/4.1/zaurus (http://ftp://ftp.openbsd.org/pub/OpenBSD/4.1/zaurus) : march 2007
latest snapshot is may 08
i wonder if i wait for the next snapshot...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161145\"][{POST_SNAPBACK}][/a][/div]
True. But interestingly the release version does seem more stable than the snapshots: it is my very first time that i get zzz, lidsuspend and the power off button ALL working!
Still let me see if things are really stable during the weekend.
-
To add another data point here, these errors
wdc0:0:0: not ready, st = 0x88, err = 0x00
wdc0 channel 0: reset failed for drive 0
wd0f : device timeout reading fsbn 156672 of 156672-0 (wd0 bn 7791264 cn 7729 tn 6 sn 54)
are not exclusive to the 6 partition setup. I don't know the precise sequence of commands which wake the drive and start addressing the hardware, but I'd like to know if multiple partitions is truly the issue...seems like something else changed which has lowered a threshold somewhere.
Problem is persistent since at least 3.8, however I never saw any errors of any kind on 4.0, with a 6 partition setup. Smells like beta buglets...
Discussion of the issue dates back at least here:
http://archive.netbsd.se/?ml=openbsd-arm&a=2005-12&t=1551843 (http://archive.netbsd.se/?ml=openbsd-arm&a=2005-12&t=1551843)
I get this using todays snapshot, one / partition and one swap, no config edits of any kind anywhere after booting (other than adding apmd):
wd0a: aborted command reading fsbn 5397260 of 5397260-0 (wd0 bn 5397323; cn 5354 tn 7 sn 50), retrying
wd0: soft error corrected
However it seems to work.
I get this using todays snapshot, using the 6 partition setup, no config edits of any kind anywhere after booting (other than adding apmd):
wd0a: aborted command reading fsbn 4982464 of 4982464-0 (wd0 bn 6002560; cn 5954 tn 14 sn 46), retrying
wd0: soft error corrected
And this too seems to work. zzz -S is causing sleep, and it wakes up, gives that error, but works.
Investigation continues...
-
True. But interestingly the release version does seem more stable than the snapshots: it is my very first time that i get zzz, lidsuspend and the power off button ALL working!
Still let me see if things are really stable during the weekend.
Last night I suspended my Z from within X using the lidsuspend option and when I resumed the device this morning the only problem was that the back light failed to turn back on. I saw a half second white flash on the screen, as if it was attempting to turn on, then a blank/black screen. I ssh'd into the Zaurus and issued wsconsctl display.back light=100 and everything returned to normal. I also used lidsuspend outside of X and got similar results. (The back light failed to turn back on) However, if I used the power on/off button in X or from the console the back light never failed to turn back on. So there is an issue with lidsuspend, but it dosn't result in complete catastrophic device lockup. Though out the day I've suspended and resumed the device via the on/off button and lidsuspend multiple times and never once had the Z lock up or produce the error you describe below:
wdc0 channel 0: reset failed for drive 0
wd0a: device timeout reading fsbn 1595200 of 1595200-0 (wd0 bn 1595201; cn 1582 tn 8 sn 41), retrying
wdc0:0:0: not ready,st=0x88<BSY,DRQ>, err=0x00.
Finally, in regards to your battery status concerns:
From the apmd manual
-t seconds
apmd periodically polls the APM driver for the current power
state. If the battery charge level changes substantially or the
external power status changes, the new status is logged. The
polling rate defaults to once per 10 minutes, but may be speci-
fied using the -t command-line flag.
Therefore to get better battery status reports add the following to rc.conf.local
apmd_flags="-t 300"
This changes the polling rate to once every 5 minutes instead of once every 10 minutes.
You might also want to check out: http://ports.openbsd.nu/x11/asapm (http://ports.openbsd.nu/x11/asapm)
-
wd0a: aborted command reading fsbn 5397260 of 5397260-0 (wd0 bn 5397323; cn 5354 tn 7 sn 50), retrying
wd0: soft error corrected
This is normal. If you don't want to see these messages then redirect the output.
-
wd0a: aborted command reading fsbn 5397260 of 5397260-0 (wd0 bn 5397323; cn 5354 tn 7 sn 50), retrying
wd0: soft error corrected
This is normal. If you don't want to see these messages then redirect the output.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161172\"][{POST_SNAPBACK}][/a][/div]
Perhaps normal for 4.1, I never saw them on 4.0.
-
So there is an issue with lidsuspend, but it dosn't result in complete catastrophic device lockup.
Just noticed the following from 3.9 changes located here: http://www.openbsd.org/plus39.html (http://www.openbsd.org/plus39.html)
On Zaurus, allow sysctl machdep.lidsuspend=1 to cause suspend on screen closure. Opening does not yet wake it up though.
The Z wakes up it just fails to turn the back light back on.
-
So there is an issue with lidsuspend, but it dosn't result in complete catastrophic device lockup.
Just noticed the following from 3.9 changes located here: http://www.openbsd.org/plus39.html (http://www.openbsd.org/plus39.html)
On Zaurus, allow sysctl machdep.lidsuspend=1 to cause suspend on screen closure. Opening does not yet wake it up though.
The Z wakes up it just fails to turn the back light back on.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161181\"][{POST_SNAPBACK}][/a][/div]
Current testing here produces full lockup on lidsuspend, no ssh'ing in possible, no status lights a flashin. I'm running 6 partitions, sleep DOES work as advertised using # zzz -S. Unable to verify any specific link between 6 partition scheme and suspend/wake problems.
I can handle typing instead of just closing the lid. Moving on.
-
Just another update:
I have tried suspending with closing lid, zzz and power off button several times under the 4.1 release version, with at least half an hour interval between suspend and resume. Everything works so far.
Pray that the issue won't come back again...
-
More update:
I've updated the kernel to 4.1-current (GENERIC) #100 (8 May 2007).
Suspend and resumes now works like a charm!
Even closing lid is no longer a problem.
Tried two days and haven't experienced any resume failure yet, except on one occasion after building stuff overnight the system refused to suspend. A reboot fixed that.
Thanks for the hard work!
[Update+]
Shortly after posting I ran into one incidence of failing to resume.
A handy tip:
Just create either a tiny shell script or alias as shortcuts to the backlight commands: wsconsctl display.backlight=100, wsconsctl display.brightness+=1, wsconsctl display.brightness-=1.
For example, i am using don ("Display On"), bup ("Brightness Up") and bdn ("Brightness Down") respectively.
-
Updated to GENERIC#110 last night. Suspend by closing lid and pressing power button quite a few times. Resume hasn't failed yet.
GREAT JOB! THANK YOU FOR THE CONSTANT AND PERSISTENT UPDATING!
I really hope I can contribute my small part soon by submitting packages to the repository.
I've been collecting OBSD tips and making notes of them. Will try to make a newbie starter guide in addition to the great installation documentations.
-
Great piece of news ! I think i ll be back to openbsd as soon as i come back from holidays
any news about bluetooth and sd card support in latest builds ?
-
well, it seems suspend/resume troubles are now gone
i've zzz -S a couple of time and resume always worked for me let's touch some wood ! (french proverb
however i've some troubles when i suspend and the usb host cable is plugged (and perhaps pppd is running): when i resume i got lot of messages which fills the screen and i cannot do anything other than reboot.....
messages are:
uhub0: device problem, disabling port 2
would someone help?
-
however i've some troubles when i suspend and the usb host cable is plugged (and perhaps pppd is running): when i resume i got lot of messages which fills the screen and i cannot do anything other than reboot.....
messages are:
uhub0: device problem, disabling port 2
would someone help?
Disconnect usb host cable before suspending?
-
however i've some troubles when i suspend and the usb host cable is plugged (and perhaps pppd is running): when i resume i got lot of messages which fills the screen and i cannot do anything other than reboot.....
messages are:
uhub0: device problem, disabling port 2
would someone help?
Disconnect usb host cable before suspending?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=162531\"][{POST_SNAPBACK}][/a][/div]
lol i didn't thought about it
you know this weekend i let the zaurus plugged to the nokia and internet up for quite all saturday and sunday compilation stories then i said to myself : perhaps the zaurus would need some pause to rest a little so sometimes i just switched the backlight off (i created scripts) .
but sometimes you also need to zzz it no? perhaps the suspend/resume process should be modified to disconnect the usb bus before and reconnect it on resume?
-
guys,
i'm running into a new problem : suspend just doesn't work !
nothing happens as i type zzz -S ........
just a "suspending system..." message then back to prompt......
any clue before i reboot ?
-
I've tried zzz -S, zzz -z, with and without sd card, cf card, and cf wifi card, with apm -A, apm -At 300, apm -t 300, machdep.maxspeed=520 or #machdep.maxspeed=520...
my new z (3200) fails to shut down its charge light during an overnight suspend charge session (~6hrs)
any idea? when I boot back to sharp rom the charge light usually disappears after a few hours.
Also, if suspend charging under OpenBSD works for anyone, can someone post their configurations?
I am using OpenBSD #current 114 dual booting OpenBSD and sharp original rom. Resume works, but I prefer not to use lidsuspend.
-
I've tried zzz -S, zzz -z, with and without sd card, cf card, and cf wifi card, with apm -A, apm -At 300, apm -t 300, machdep.maxspeed=520 or #machdep.maxspeed=520...
my new z (3200) fails to shut down its charge light during an overnight suspend charge session (~6hrs)
any idea? when I boot back to sharp rom the charge light usually disappears after a few hours.
Also, if suspend charging under OpenBSD works for anyone, can someone post their configurations?
I am using OpenBSD #current 114 dual booting OpenBSD and sharp original rom. Resume works, but I prefer not to use lidsuspend.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163097\"][{POST_SNAPBACK}][/a][/div]
well,
with apmd -A that didn't work for me too...
but with apmd="" or -t 300 it does work
but it probably depends on what you're doing with your Zaurus (wifi ? bluetooth?)
when i let the zaurus up to compile, i'm used to plug my nokia via its usb cable so power requirements are at low level
-
guys,
i'm running into a new problem : suspend just doesn't work !
nothing happens as i type zzz -S ........
just a "suspending system..." message then back to prompt......
any clue before i reboot ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163044\"][{POST_SNAPBACK}][/a][/div]
any news about how to solve this bug ? i'm having it again....
-
guys,
i'm running into a new problem : suspend just doesn't work !
nothing happens as i type zzz -S ........
just a "suspending system..." message then back to prompt......
any clue before i reboot ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163044\"][{POST_SNAPBACK}][/a][/div]
any news about how to solve this bug ? i'm having it again....
Here's some new news:
"Revision 1.3, Mon Oct 8 20:18:19 2007 UTC (2 weeks, 4 days ago)
Branch: MAIN
CVS Tags: HEAD
Changes since 1.2: +2 -1 lines
Diff to previous 1.2
Align the suspend saved data to a cache line boundary, apparently prevents issues upon resume."