Messages

31

6000 - Tosa / Angstrom Status On Tosa

« on: December 23, 2008, 01:38:22 pm »

please reflash the kernel with http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin
It should fix the power key problem.

It does.   But are all of the debug options turned on?  It's very noisy!

Also, I was playing around a bit and got e-wm installed and running up to the point where locale is asked for...but it doesn't seem to register the touch screen.  Is that a kernel thing, or an e thing?

32

6000 - Tosa / Angstrom Status On Tosa

« on: December 22, 2008, 02:21:46 pm »

could you please post the result of

Code: [Select]

# grep Name /proc/bus/input/devices
N: Name="Tosa Keyboard"
N: Name="wm97xx touchscreen"

Also please check the exact version of kernel package in those images.

Not sure what you meant specifically, but here's:

Code: [Select]

# uname -a
Linux tosa 2.6.24 #1 PREEMPT Fri Nov 21 16:46:51 MSK 2008 armv5tel unknown
and:

Code: [Select]

#opkg list | grep kernel
.
.
.
kernel - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel - 2.6.24-r16.1 -
kernel-2.6.24 - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel-2.6.24 - 2.6.24-r16.1 -
kernel-cmdline-2.6.24 - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel-cmdline-2.6.24 - 2.6.24-r16.1 -
kernel-dev - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel-image-2.6.24 - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
.
.
.
Hope that's what you needed.

BTW: apm -s worked quite nicely.  Hardware button brought Tosa back to life.  I had to reset my network settings (which brought back wifi), but at least the module wasn't frozen.

33

6000 - Tosa / Angstrom Status On Tosa

« on: December 20, 2008, 06:15:02 pm »

I pried my eyes a bit wider and found a few other of the 2008.1 images.  None of the x11 images allow me to enter info into the login screens, so I tried the console image and found opkg.  Suspend did not work via hardware on this image either.  What's the command?

I'm curious to try e-wm...is the one that's in the feed the same as what's showing up on the openmoko devices?  

I have to say it's been fun trying new stuff with this device that had been gathering dust!

34

6000 - Tosa / Angstrom Status On Tosa

« on: December 20, 2008, 01:00:43 am »

OK...I was looking in that directory before, but the images I downloaded still use ipkg.

I do notice the following:

Code: [Select]

Angstrom-x11-image-glibc-ipk-2008.1-test-20081127-tosa-installkit.tgz
which I suppose is the "2008" track you speak of.  I'll try that out.

[EDIT]
Just tried it out.  Show stopper is apparently the keyboard does not work.  "new user details" screen is the first...but neither HW or SW keyboard are placing text in the fields.  Orange lines are back too.  This is with the above installkit and Dmitry's kernel.
[/EDIT]

35

6000 - Tosa / Angstrom Status On Tosa

« on: December 10, 2008, 01:09:44 am »

Angstrom 2008 uses opkg. Do you track 2008 (unstable) or 2007 (stable) branch?

Not sure what you mean by "track", however update specified 2007.

Tell me more, please
Most probably there should be several problems related to incorrect keymappings,

You jogged my memory.  

• Key repeat is still too sensitive. Very easy to do www.goooooogle.commm
• Testing the sketchpad app, I discovered I could not draw a straight line; just jagged ones (even after recalibrating)
• I'd like to be able to install Minimo or Midori, but ran into the "locale not supported" error.
• Installing to SD or CF requires linking to get libs to work.

I'm sure at least a couple of the above are kernel related.
[!--quoteo(post=0:date=:name=lumag)--][div class=\'quotetop\']QUOTE(lumag)[/div][div class=\'quotemain\'][!--quotec--]I did not test GPE at all for a long time. Currently busy with work, RL, providing upgraded kernel via OE (I plan to provide 2.6.27 or 2.6.28-rc soon) and fixing opie issues.[/quote]
Your work is appreciated.  

36

6000 - Tosa / Angstrom Status On Tosa

« on: December 09, 2008, 08:12:36 pm »

Speaking of keymappings;  I did an

Code: [Select]

ipkg update, ipkg upgrade
which eliminated my ability to get to the Fn generated keys (numbers, punctuation, etc...)

Suspend still has the problem of freezing the prism2_usb module.  Can't reload (unload or load) this module after suspend.

I've noticed some other behaviors; but they're specific to Opie or GPE.

Feeling hopeful!

37

6000 - Tosa / Considering Graphic Driver For Tosa

« on: December 05, 2008, 01:02:38 am »

From my experience, most things other than video ran acceptably on the Tosa.

Most Tosa hardware on Angstrom works?

I wasn't thinking Angstrom when I posted that.   Mostly experience from SharpRom.  If we're talking pure Angstrom, I wouldn't know where to start, since I have only now been able to run it with any stability.  That said, standard opie and gpe on Angstrom on Tosa are very snappy and quite acceptable speed wise.

38

6000 - Tosa / Considering Graphic Driver For Tosa

« on: December 04, 2008, 01:58:09 am »

From my experience, most things other than video ran acceptably on the Tosa.

39

6000 - Tosa / Angstrom Status On Tosa

« on: November 24, 2008, 06:21:16 pm »

--edit-- hm, doesn't seem to suspend. is that normal?

It suspended for me using the menu (QPE, or Opie); not with the button.  Comes out of suspend via the button, however.

Still no access to increasing / decreasing backlight via settings on either opie or gpe, haven't tested sound through alsa(mixer, player, etc...), but wifi is working (open network at least)!

40

6000 - Tosa / Angstrom Status On Tosa

« on: November 24, 2008, 02:00:50 pm »

OK...I had forgotten about the autobuild directory.  I tried the new kernel with the older installkits, so I'm assuming that's why things like sound and backlight are not impacted by Opie or GPE.

Aside from that, things look REALLY good!  Response is very snappy, boot time is short, suspend works (though needs "Menu | Suspend" to go into suspend, button brings out of suspend).  Today I'll try the autobuild rootfs's to see what the difference is.

Excellent work Dmitri!!  

41

OpenMoko / Android Ported To Openmoko Devices

« on: November 14, 2008, 12:59:23 am »

I tried it out on my FR.  Looks really nice, and I'm happy with the UI.

The biggest hangup right now is that the software was designed with 4 hardware buttons in mind.  What this means currently is that there is no way to accept an incoming call.

Things are looking good though.

42

Ubuntu / The Birth Of Zubuntu

« on: November 14, 2008, 12:48:49 am »

An added "Please!" for the 6000.

Question: Are you using OE kernels, or rolling them yourself?  The reason I ask is that IIRC, the 6000 OE kernel is still lacking support for some critical events such as suspend (and wifi, I think).

43

OpenMoko / Fdom

« on: September 22, 2008, 02:19:46 am »

I HAVE tried it.  Consider it a "convenience image".  It includes some of the popular apps that have shown up on the lists and feeds.  It includes fixes and scripts that folks have come up with, but haven't made it (or will never make it) to mainstream OM.

Effectively what you get is OM 2008.8 with the above addons that save time having to configure everything to work.  It's not a fork, though it does have some additions that apparently will not make it to OM (such as Raster's keyboard).

44

OpenMoko / Stable Om2008.8

« on: September 11, 2008, 03:43:50 pm »

As always; "stable" is relative.

Not sure about anyone else, but the mix of qtopia, enlightenment, and GTK is driving me nuts.  I understand the need (at least for now) for the mix, but they don't "seem" to play well together.

Either way, having fun!

45

OpenMoko / Freerunner 6000 Frankenstein?

« on: August 14, 2008, 02:23:22 am »

I've been playing with my Freerunner...it's been frustrating fun.  I took i t out today to try it as my phone, and a major shortcoming startled me.  The screen was completely washed out in the afternoon sun!  I was getting a call, and i couldn't see the button to accept the call.

That led me down a few other hardware paths (such as using a software keyboard) and I got to thinkin'...

What if i put the innards of the Neo into my SL6000 case and use the 6000's gorgeous screen?  I never had a problem with the size of the 6000 (some felt it too big), and having some of the other hardware available might be nice.

Could be a pipe dream...but I plan on at least looking into it.

Anyone have any thoughts?