yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Moving forward

Hi.

Well, now we have made the installation a little more userfriendly. You still have to create a linux partition, but the zImage, haret and the startup script are now pulled in to a WinCe cab file installer.

To use this you will have to have the linux partition on your second partition on your SD card.

You can boot linux as you start a regular WinCe application. Take a look at this screenshot: http://gnulinux.biz/files/Universal/Linux.png (i have installed all 4 of the cab file)

Here is a new website i have made just to make it more userfriendly:

http://gnulinux.biz/files//Universal/

Sponged: Thanks for the tips about lcab, i had never thought of it before you mension it. All credit to you for this.

Note: Next kernel updates and images i make will be upped like this. For updateing images and kernels you will have to uninstall the bootloader and install the new updated one. This is because of the kernel zImage is pulled in to the cab file.

Enjoy
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
No, you don't have WinMo 6.0 on you Universal :`)

Will try the cab stuff in the next days. Any idea, about the TS problem with latest hh kernel?
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Yes there are some common drivers wich is updated. We havent followed it up so now TS is broken an power is broken.

I think cr2 is about to update it, but i dont know ehen. He is also involved in other prosjects you know.

Update: I didnt knew WinCe and WInxp couldnt read a SD card with ext3 on first partition and vfat on the second partition. So we have to have it as we had it with VFAT on partition 1 and the linux partition on the rest.
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Openmoko-dialer running on Opie

This one is quite cool. Seems like we can use opnemoko-dialer with Opie :-)

Update, now with openmoko-theme: http://gnulinux.biz/files//Universal/pics/sc_Mon_Apr_9_18.23.29_2007.png
[JASJAR, XDA Exec, MDA Pro General] BigDamHero:
Hi,

I just tried the new X11 Angstrom-X11 image.

GPE-Mini-Browser starts up, but still dies with a segmentation fault whenever I try to navigate somewhere. Run from a terminal the output looks like this

Path /
Segmentation fault

It also throws some errors on start up about "NotYetImplemented". Anyone else getting segmentation faults? Any ideas?

thanks

Lewis
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
hey goxbloxlive,

the openmoko loader, you build does not work for me. I get a kernel panic on boot. The reason is, that it tryes to boot from partition 2 but my installation is on partition 1 on my SD card.

UPDATE:

Forget about it, i found the install directory and changed in startup.txt :`)
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
:-) Yes, read the HOWTO and you see. I started to have the installation booting from first partition, but it showed up that wince isent able to read vfat partition on the second partition. And i dont think it's necesarry to have two versions
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
Yes, you are right. Good work by the way :`)
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Hi there. That's nothing to do with our images. It is a bug in gpe-mionibrowser. Please report this as a bug at http://bugs.linuxtogo.org/ and then they will fix this i guess..
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
does not work in current openmoko rom
[JASJAR, XDA Exec, MDA Pro General] BigDamHero:
Hi,

Thanks for the help. But the thing is it makes the program totally unusable, so I'm suspicious that no one has reported it yet... does that not seem unlikely?

Also other programs that use the network also fail (gaim for example) with a segmentation fault.

So is there any chance some program or library they rely on is responsible instead?

thanks - great job by the way. Keep up the amazing work

Lewis
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
I dont think its named panel-app.sh anymore.

Try running xrandr -o normal it should work.
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
IYes i agree with you, but as long as no one reports bugs it wouldnt be fixed. I have also noticed some of the bugs you are talking about. And i agree with you that it is useless when it's not working, but keep up the testing and send in bugs and one say we will have a usefull device.
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
works, but normal is wrong now. I set it to "-o left" to make it fit the screen

UPDATE:

Btw. Openmoko keyboard has been gone in the latest build. Also there are many apps missing, like the new calculator, they implemented in the last week. Is it possible for you, to upgrade into a much richer release?
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
I have noticed the -o left and so. The panel app.sh where a script wich where editable. Havent looked at the source for xrandr.

The openmoko stuff isent included because it isent presented in openembedded. You have to wait until they add the packages. I dont want to have a much differ oe db than the official one.

But try out the Opie-custom image, it's much more fun to have openmoko-dialer running in Opie. It works even bether too. Last evening i solved the hangup call issue, but i havent implemnted it yet in any new images. I am waiting for cr2 to update the sounddriver.

to start openmoko-dialer in Opie you have to, firs rotate screen til portrait mode then:

Start Xqt from its icon under application
Open opie-console
write: export DISPLAY=:0 [enter]
write: openmoko-dialer -s & [enter]

It
[JASJAR, XDA Exec, MDA Pro General] r3bel:
hi :¬D

I installed the gpe image on my universal's sd card using the ramdisk image (which worked fine), and installed the launcher cab in wm6, but when i try to boot, i get a message about a kernel panic and to try init.

i wiped the ext3 partition and tried again with the opie image which did the same thing - i assume this means it is an issue with the current Familiar image.

is it a known problem? please note that this is my first use of linux so i might need to do a bit of learning ;¬)

edit: but what a way to start!! :¬D
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Are you sure you created the linux partition on partition 2. It sounds like your linux partition (ext3 filesystem) is on your first partition.

You can check this out by booting the ramdisk image and type 'fdisk -l'

Look at the out put and check.

If it is on partion2 you can try to check in your wincw filesystem:

\Program Files\BootLinux\gpe-linux\startup.txt.

check what the content is in your set CMDLINE . Is it mmsblk0p2 or is it mmcblk0p1 ??

I have once again read true the howto, and i cant see that anything is wrong in it. It should just work. Because i am using the same way to do it myself.
[JASJAR, XDA Exec, MDA Pro General] r3bel:
Thanks for the reply :¬)

the ext3 partition is definitely /dev/mmc/blk0/part2 (see I've learnt some linux already ;¬)

startup.txt is:

I have a 1GB SD which I've partitioned into:

Partition 1: 512MB VFAT

Partition 2: 512MB ext3

Is it this that is causing the problem? I'm getting a new 2GB tomorrow so I can dedicate the 1GB to Linux if necessary.

edit:

I think these are the relevant bits of the startup output:

edit2: what bootrom do you have? mine is v2.02 (so a G4 universal). the G1/G2/G3 uni's are ever so slightly different from the G4 ones.
[JASJAR, XDA Exec, MDA Pro General] onlineemails:
wep cracking whit universal

Hi guys,

i seen many guys installed linux on there universal,i have a question about it, is there an way to put universal wlan in monitoing mode? if it canbee we can crack wep keys with universal 2:) :) :) :)
[JASJAR, XDA Exec, MDA Pro General] cr2:
FYI: such "devfs" device naming is obsolete.

The right syntax is /dev/mmcblk0p2, which you are actually using :)

Did you compile the kernel yourself ?

A "can't find init' message can happen if the kernel and SD image

disagree on the binary format (EABI vs. legacy ABI)

The only hardware difference between Universals is the board_id.

I have not heard yet about the board_id !=5 ( Samsung LCD instead of Sony).

Your bootrom is completely irrelevant (with the possible exception of resume

code path, but i doubt it will ever happen).
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
No you dont need 1GB for Linux partition. I guess 128 should be enuogh (even smaller).

But maybe it has something to do with your sd card, it might be that your card isent supported in the linuxdriver.

Else is everything looking good. Your startup.txt is the one i created and hsall not be edited.

Try out with your new sd card, maybe that will help.
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
It can also be a sync issue. I experienced this many times. When i forgot to run "sync" after uncompressing the image, or forget to unmount before removing ... the file system on sd can be corrupt.
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
ah, right. I have also have had some problems with sync issues after writeing to SD card. I'll add sync three times in the howto.
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
Hey goxboxlive,

is it possible to build and root image with 100% openmoko distribution? So we have also the initrd from openmoko and all current applications?

I read something about a openmoko make script, that does all the jobs riquired, but i don't have a clue if this could help.

By the way, i will try your latest opie image the next days.
[JASJAR, XDA Exec, MDA Pro General] Midget_1990:
Just fyi there is a hardware difference between G3 and G4 phones, they have a different DOC, G4's are much more stable, feel faster, bench faster (i have both), and have a different bootloader (G3 is 0.xx or 1.xx, G4 is 2.xx)
[JASJAR, XDA Exec, MDA Pro General] cr2:
Ok. Can you tell me the board_id for MDoC G4 Unversal ?

Where can i find the G4 SPL ? i'd like to have a look on the resume code path.
[JASJAR, XDA Exec, MDA Pro General] r3bel:
Aaaalrighty then...

I'll try again from scratch, but I have noticed a few things now i know a bit more.

1) tutorial says to do what you called "devfs", not the /dev/mmcblk0p2 that is in startup

2) tutorial says to do sync (which I did every time anything was done with the SD) but not to unmount! (is it strictly necessary?)

3) when I tar-ed an image, sync-ed, then ls-ed, I can only see the .tar.bz2 file, not a new extracted folder structure. is this normal? or have I misunderstood tar?

oh, and the new sd is the same type as the old one (sandisk's clever usb/sd combo)
[JASJAR, XDA Exec, MDA Pro General] raytracer:
Quote:

kjournald starting. Commit interval 5 seconds

EXT3 FS on mmcblk0p2, internal journal

EXT3-fs: recovery complete.

EXT3-fs: mounted filesystem with ordered data mode.

VFS: Mounted root (ext3 filesystem).

Freeing init memory: 96K

Warning: unable to open an initial console.

Kernel panic - not syncing: No init found. Try passing init= option to kernel.

_

Quote:

I have the same problem...
[JASJAR, XDA Exec, MDA Pro General] raytracer:
kjournald starting. Commit interval 5 seconds

EXT3 FS on mmcblk0p2, internal journal

EXT3-fs: recovery complete.

EXT3-fs: mounted filesystem with ordered data mode.

VFS: Mounted root (ext3 filesystem).

Freeing init memory: 96K

Warning: unable to open an initial console.

Kernel panic - not syncing: No init found. Try passing init= option to kernel.

I have the same problem...
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Ok, there seems like there are alot of you wich have problems with this. I'll try the tutorial my self with and old SD card (128MB). Maybe there is something wrong in it, i just cant see it.

** UPDATE **

Ok, there seem to be a bug. I am sorry for that. But it seems like the tar/bunzip version in the ramdisk image is to old to handle the untar/bunzip part in one command. But there is a way to ovveride this. DO AS FOLLOW:

bash # bunzip2 "the tar.bz2 file" [enter] (take some time)
bash # tar xvpf "the tar file you extracted in the step above"

Thanks for testing. Now go on and play with your linux distro. In the meantime i'll update the Howto.

** UPDATE 2 **

Yes, now i tried to boot it and it booted. Problem solved.
[JASJAR, XDA Exec, MDA Pro General] raytracer:
-sh: bash: not found

...

:-(

I will wait fot the new version...
[JASJAR, XDA Exec, MDA Pro General] raytracer:
-sh: bunzip: not found
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
I wouldnt build a new RAMDISK image.

But you are not suposed to write sh or bash or #, just write: bunzip2 "the tar.bz2 file " )without the quotes)

and then write tar xvpf "the tar file" (without the quotes)

The bash # just shows that you are at the command prompt.
[JASJAR, XDA Exec, MDA Pro General] raytracer:
Obviously I had wrote just bunzip....

I substituted "bunzip" with "bunzip2" and seems to be working!!!
[JASJAR, XDA Exec, MDA Pro General] raytracer:
yeeeeeeeeeeeeeesssss!!!! Thanks for being patiente!!!
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
of course, my fault.
[JASJAR, XDA Exec, MDA Pro General] r3bel:
apparently it's better to use

than
[JASJAR, XDA Exec, MDA Pro General] cr2:
Why not just "tar xvpfj tarfile" ?
[JASJAR, XDA Exec, MDA Pro General] Midget_1990:
cr2: will do as soon as i find my phone (can't remeber where i put it lol)
[JASJAR, XDA Exec, MDA Pro General] r3bel:
because the version of tar in the ramdisk image doesn't support the compression or something in the current roms.
[JASJAR, XDA Exec, MDA Pro General] cr2:
Do you know if it a problem of an outdated busybox ?

i see the ENABLE_FEATURE_TAR_BZIP2

option in 1.2.1

and if 'tar' is accepting input from the stdin, you can also do

bzip2 -dc file.tar.bz2 | tar xfvp -
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
cr2: I dont know if it is because of an oudated tar version or not. But what i know is that this has worked before with older images, and suddenly after OE changed some options in local.conf (you have to set tar.bz2 to have it bzipped) this suddenly happend with the ramdisk image.

But i cant see that this is a problem as long as we know how to do it. To do this in two steps instead of one isent a big deal anyway.
[JASJAR, XDA Exec, MDA Pro General] TehPenguin:
Why is it that the images all seem to be running version 2.6.20-hh4 of the Kernel, but on the Handhelds.org website, it says that the Universal is upto version 2.6.20-hh6?

Also, why do neither the GPE and the X11 roms use Gomunicator? And what is the difference between the GPE and X11 roms?

Any info would be great,

Thanks
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Now there is also a hh7 version, but since hh4 there has been some bugs, like nonworking touchscreen and some outdated stuff universal still use. So the patched hh4 is the best for now, maybe further back where we could have a working power module but i do not remember when it didnt work 100%.

Because Openmoko-dialer runs bether on Universal, and it is bether supported. But you are free to write support for Universal in Gomunicator if you like. If it gets bether than Openmoko-dialer i'll replace it.

Not much. X11 is a clean basic (GPE) image wich doesnt contain as much applications as the GPE image. Also our distro make some predefined GUI and one of them are x11.

If you run a x11 image you just can install applications to have it like a GPE image. I am thinking of stopping uploads of GPE image since x11 can do the same.

You welcome.
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
* Please Test *

Could someone test this zImage.

Just replace the one you have with this. It will complain about missing modules but nevermind this.

I need help to test this because when i am trying it i dont have a working touchscreen. But when cr2 is running it (the same zImage) his touchscreen works just fine.

I would be niuce to figure out what might be wrong, is it my device or is it because he boots via NFS.

Download this and try out. Please post your result.

http://www.gnulinux.biz/files/Universal/tmp/zImage
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
Not working, ts is still not working. Using your last openmoko rom

UPDATE: Now I know, where the missing apps are. Just scroll down the main view :`) But this only works, if you use it with the keyboard.
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
I knew that EOTS. :-) Yesterday i made a opemmoko distro image. but it has some lacks, like phone support and so.

Not that much diffrent from angstrom-openmkoko.

So, the TS didnt work for you either with the provided zImage. Then it has have something to do with NFS vs SD boot.
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Touchscreen bug

It seems like we have found out what causes the touchscreen to not work now and then.

There where some switches wich created some bugs, they ar now commented out in the source.

There has also been som updates to the libgsmd lately. Our patch isent working with it yet so i have to wait until that hgas been fixed before i upload updated images.
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
Thanks goxboxlive
[JASJAR, XDA Exec, MDA Pro General] briosix:
Development environment.

Hi all,

I just started using it, so forgive me if I ask something stupid.

I'm trying to setup a build environment, now for testing, in future maybe to put more applications to the opie image (a phone one would be great and probabily will have to go with openmoko-dialer).

I have installed the openembedded and are building the angstrom-x11 image, but there is not an angstrom-opie equivalent.

What do you have to build? angstrom-console (or x11?) and then add opie apps?

Is there some documentation on how to setup a testing environment? (have not read all the forum posts so if it's in there just say so and I'll look through it)

Thanks
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Angstrom doesent support Opie . But you can build it just by typing:

bitbake opie-image
[JASJAR, XDA Exec, MDA Pro General] briosix:
Development

ok, thanks.
[JASJAR, XDA Exec, MDA Pro General] briosix:
By the way. With "current" opie image O experience strange thinkgs with (busybox) wget and DNS. I used netusb through my linux box, and I can ping everithing on the internet (used Nat), but when I try to ping with dns names it tells me Unknown host.

Then if I put wget http://<IP>/page.html I get: No route to host. though I can ping the host... (?!)

Is this a known issue? Should I try with a gpe image?
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
no idea, they are using the same base if it is theuniversal images you are talking about
[JASJAR, XDA Exec, MDA Pro General] briosix:
yes talking about htcuniveral.

I'm going to try the gpe one, or even the console...

You never experienced this before or simply never tested it?

To have more images on same SD do I have to update haret config and fstab only or there is something else?

tnx

OK Never mind. The GPE image works, so probaly I messed around with the opie one... I'll try a fresh one.
[JASJAR, XDA Exec, MDA Pro General] peteredworthy:
What CVS tag?

What is the CVS tag for the current branch?

I have TK2-6-12-hh2-xda0-un0 but it seems very out of date.
[JASJAR, XDA Exec, MDA Pro General] cr2:
The current CVS is on handhelds.org
[JASJAR, XDA Exec, MDA Pro General] peteredworthy:
Thanks, for reference I used

cvs -d : pserver:anoncvs@cvs.handhelds.org:/cvs login

[type anoncvs]

cvs -d : pserver:anoncvs@cvs.handhelds.org:/cvs checkout linux/kernel26

There should be no space between the ':' and the 'p' but it changes it to smilies if I don't.

which I hope is right, and hence can help others.
[JASJAR, XDA Exec, MDA Pro General] maxstegi:
phone ...

hello guys,

i've just installed the new x11-image, and tried to make a call ... it says, that it's dialing, but it doesn't do it ...

i can't recieve any call, too: the number, you have called is currently not available ...

where can I enter the PIN and the default network?

thanks and sorry for my bad english, i'm german ....

max
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
I dont think PIN code is supported in openmoko-dialer yet. It might be that it works with openmoko-image but i have no idea if it does. I am not using PIN code on my test machine.
[JASJAR, XDA Exec, MDA Pro General] maxstegi:
ok, i've switched off the PIN code, but it's still not working ...
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
ok, then i have no idea what you doing wrong.
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Quite this days, just a status report.

Well, some might think that we have given up our project since there it has been so quite here lately.

So why is it so quite here?

Have you lost the intrest? Is it because you think that the Universal has become obsolete? Is is still to less userfriendly to try this out? Or might it be that it has become so userfriendly that you dont need any help anymore :-) ?

Well, but i can inform you of our progress lately.

We are back to try out Opie2. A guy named BabelO at the IRC has done some great work with it, and it is now compiling again, but i cant start it because of some bugs in gnokii (phone). But i guess we are now quite near the goal to have Opie2 running with phonesupport.

Else, when it comes to the kernel:

cr2, has cleaned someof it up, we have figred out what cases the non working TS happends occasionally. It has something to do with the night sensor, so we have exclude it from the kernel for now.

Else, has cr2 also added phonemic support to the kernel, so we are now able to take calls both incomming and outgoing.

There are still some issues when it comes to Openmoko-dialer regard the other part close a call so i'll wait to the bug is fixed to upload new images.

If we get Opie2 running i think also cr2 will take a look at the camera drivers. Opie2 is suplied with a camera application so it would be nice to also have that running.

So to all of you who considering sell you Universal this days, dont do it, it is still a good device considering hardware spesification. It is still in the one of the devices with the best specs.

I'll get back when we have some good news again.
[JASJAR, XDA Exec, MDA Pro General] i386:
Hi goxboxlive

thanks for the great work done and i am waiting for my spare SD card to come to try out linux on universal - so at least there is someone who is keenly looking forward to running linux on this platform. I am a c++ programmer coding academic projects under linux myself and will be more than happy to see my universal being able to compile my libraries ... :-)
[JASJAR, XDA Exec, MDA Pro General] sponged:
goxboxlive:

I've gone back to lurking, but I've been lurking very attentively! I've seen a lot of the fascinating stuff going on on the IRC channel - I just hope it's not too much of a sideline from the main effort. Personally, the wifi instability would be the most interesting thing to fix, but I'm some way away from having the skills to do that.

Please don't think I've lost interest! I'm checking every day for the appearance of the next batch of images, and looking forward to incremental progress towards a fully working device!

Thanks for your and others' hard work - it's really appreciated and enjoyed! Please keep going!
[JASJAR, XDA Exec, MDA Pro General] ryaske:
is there a website showing your progress?

If you do, and theres a donate button, i'd certainly be clicking it
[JASJAR, XDA Exec, MDA Pro General] TehPenguin:
You can see all the info for Lnux on the Universal at:

http://www.handhelds.org/moin/moin.cgi/Universal

Otherwise, the status page is:

http://www.handhelds.org/moin/moin.cgi/UniversalStatus

I haven't seen a donation button there yet, otherwise it'd have a couple of clicks from me...
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Donating money

If you want to donate, donate to xda-developers. They are the reason we have this going on, and the donation will just gain the forum at xda.

Thanks alot.

gox.
[JASJAR, XDA Exec, MDA Pro General] dr_derqami:
Ok