There are a few users left that I know about. We had been playing with 5.4 but since cmake would crash on arm, it left us without the ability to build a lot of ports. We've tried going to 5.5 but that is when X failed to run. I had been watching the snapshots and noticed X wasn't even building for Zaurus for a while and the older snapshot tarballs were linked against different libs and couldn't be used. I see it's been built since but I haven't tried it.
Suspend/resume has been a problem for a while, too. That all said, I haven't had a problem with booting. I use a modified boot image (not the stock Sharp linux) and a full disk install of OpenBSD. The 5.6 snapshot from a month or so ago, boots fine. Tim. On Wed, Aug 13, 2014 at 10:50 AM, Sacha El Masry <li...@devilray.eu> wrote: > I have had OpenBSD 4.2 on the Zaurus C3100 for years now, and in need of > further (latest) software, I decided to upgrade. > > There are at least three problems that did not exist on 4.2: > > 1. When the system gets to the 'boot>' prompt, it fails, as it's unable > to find /bsd, for whatever reason. Of course, I just load the Linux > partition with the 'b' and 'd' key combination, and run: > > $ insmod zbsd... > $ cp bsd /proc/zboot > > and it's off, booting as it always used to, after which everything works > as usual. > > 2. When the device comes out of sleep/suspend, it never brings back the > backlight, forcing the following: > > $ wsconsctl display.backlight=100 > > which is a tad inconvenient, as I may not be in a shell (having > suspended with the lid), and as the keyboard isn't exactly accurate, > often sending more than one character for one keypress. > > 3. X just doesn't work-it tries to load, returning half a minute later > with an error message. > > While none of these are complete show-stoppers, the booting always > worked fine, in all the versions up to 4.2, the backlight wasn't a > problem, and X worked. On the other hand, it is nice that the SD card is > now recognised. > > I've tried all of this with a snapshot (from the 2nd of August, I > think), and the same problems remain. > > Now, I know this platform isn't the hot topic it used to be, but it > still has its (numerous) uses. Is it being worked on, or is it on its > way to deprecation? If it is still alive, is anyone using it, and > experiencing the same problems? Perhaps with some solutions? > > Hope there's still some life left in this platform's support yet. > > Regards, > > Sacha
