1.1.0r121 Is Out!, New name for betas by svn revision №;) Options

[Chero]

decided to try r121
instructions are fine, etc.

1st problem:
accidentally tapped the screen during calibration--no recalibrate giu app?

how do I recalibrate (actually I am going to reflash, but this sort of thing maybe should be easy?)

there is a file called pointercal under /etc
remove it and next time you boot up, it will make you to recalibrate

or start "ts_calibrate" from a terminal

[adf]

quick question (may have been answered many time before, anyway...): what's preventing Tosa rom to advance beyond beta1?

nothing....except maybe sashz doesn't have one? ( I don't actualy know. just guessing)

[adf]

the package manager does;t work? On mine, it loads but lists niether available nor installed packages.
Tell me this is something simple. I have a great fondness for gui package managers.

[dinorex]

I saw one r121 today having qpkg "Systems -> Package Manager" doesn't work as well...

in console i typed 'qpkg' and gets 'Command not found' ....

of course i typed 'which qpkg' also have no result....

[adf]

I saw one r121 today having qpkg "Systems -> Package Manager" doesn't work as well...

in console i typed 'qpkg' and gets 'Command not found' ....

of course i typed 'which qpkg' also have no result.... 

ugh. typing it in worked.

[xjqian]

quick question (may have been answered many time before, anyway...): what's preventing Tosa rom to advance beyond beta1?

nothing....except maybe sashz doesn't have one? ( I don't actualy know. just guessing)

then what gets beta1 done for Tosa in the first place? Are you suggesting nothing stops Tosa user to try newer beta except for a brave soul (i.e. there's no hardware limitations built into the newer betas)?

[adf]

I think you might have to build it for a tosa? there are some distinct hardware differences... certainly the kernel and some modules would have to be built..afterwhich maybe the 7x0-860 feed might work if you stayed away from the ati video stuff.

I was thinking that maybe some of the tisastuff had been done "blind"

have you looked at the pdaxrom builder? does it have stuff to build for tosa?

[InSearchOf]

Post # 500....

Well adf to answer your question... there isn't a build set currently put together for a tosa under rc121... but I think with some time an effort you could prolly put together to right combinations under ptxdist to get it work with uboot... I dont know if just including the config settings for initrd will do the trick on not...

Late

PS. Did I mention this is post # 500 for me... oh yea... I did... :-)

[ZDevil]

Just tried the zgcc.img from the r121 feed and got this upon mounting:

CODE

mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage, or too many mounted file systems

Pass -t cramfs to mount doesn't help.
The older file in the Beta4 feed is working.

it seems to be a squashfs

I have a script doing :

CODE

losetup /dev/loop0 /home/root/zgcc-3.4.6.img
mount /dev/loop0 /opt/native/arm/3.4.6-xscale-softvfp -t squashfs

and I could compile the latest xarchiver natively.

Chero.

Oh, thanks for clarifying this!
But how come the zgcc changes format (cramfs -> squashfs) silently but the documentation is not updated?

[InSearchOf]

Just tried the zgcc.img from the r121 feed and got this upon mounting:

CODE

mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage, or too many mounted file systems

Pass -t cramfs to mount doesn't help.
The older file in the Beta4 feed is working.

it seems to be a squashfs

I have a script doing :

CODE

losetup /dev/loop0 /home/root/zgcc-3.4.6.img
mount /dev/loop0 /opt/native/arm/3.4.6-xscale-softvfp -t squashfs

and I could compile the latest xarchiver natively.

Chero.

Oh, thanks for clarifying this!
But how come the zgcc changes format (cramfs -> squashfs) silently but the documentation is not updated?

I will make the needed changes to the site... But, I do remeber there being something in the boot up scripts to mount this image if it is placed in t he correct place... I will see if I can find it... and maybe we could start pointing users to where it should be placed to mount at boot instead of mounting by manual means.

Late

[Chero]

I will make the needed changes to the site... But, I do remeber there being something in the boot up scripts to mount this image if it is placed in t he correct place... I will see if I can find it... and maybe we could start pointing users to where it should be placed to mount at boot instead of mounting by manual means.

Late

Agreed.
Just took me a while to figure out how to mount it, in previous versions it was pretty straightforward, so I already guessed there would be a better way to do it.

Thanks,
Chero.

[Meanie]

I will make the needed changes to the site... But, I do remeber there being something in the boot up scripts to mount this image if it is placed in t he correct place... I will see if I can find it... and maybe we could start pointing users to where it should be placed to mount at boot instead of mounting by manual means.

Late

Agreed.
Just took me a while to figure out how to mount it, in previous versions it was pretty straightforward, so I already guessed there would be a better way to do it.

Thanks,
Chero.

place it in /home/root

[InSearchOf]

I will make the needed changes to the site... But, I do remeber there being something in the boot up scripts to mount this image if it is placed in t he correct place... I will see if I can find it... and maybe we could start pointing users to where it should be placed to mount at boot instead of mounting by manual means.

Late

Agreed.
Just took me a while to figure out how to mount it, in previous versions it was pretty straightforward, so I already guessed there would be a better way to do it.

Thanks,
Chero.

place it in /home/root

Thats what I thought... but i wanted to clarify... i know I hate having files "lay around" out in the open... so I will edit my config file (cant remember which one) and point it to a hidden dir like ~/.gcc/

Late

[InSearchOf]

ok... yea... I found it again...

the "at boot" mounting action is located in
/etc/rc.d/rc.sysint

the begining of the script starts on line 164

if you want to change the location of where the zgcc*.img is located and or the version you are using... you can change it there...

Late

[cycle_55]

Would it be possible for someone to tell us how close we are to a new release of r121, I understand that wireless has been fixed and am just curious when I can go back to r121. Thanks for all the hard work.

cycle_55