Cacko3k Feedback

[iamasmith]

My results with the new values:


1,Turbo (624/312/78 MHz),2000218,e     Immediately locked up, had to pull the battery.  Went back the old values
1,Overclocked (520/260/64 MHz),2000214,c     Works fine
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78265\"][{POST_SNAPBACK}][/a][/div]

Spooky, this was the value that BatteryPlus-1.0.6 used for overclocking to 624Mhz, I was sure that was going to be safe. OK, I haven't had a lockup myself but I haven't really put it through its paces.

Post your freqchange.conf and lets all try and see if things are stable on a range of 3Ks.

- Andy

[sriley]

OK, I commented out several lines:

0,Turbo,1e2,0
0,Overclocked,162,0
0,Default (PXA255),161,0
0,Normal,242,0
0,Default (PXA250),241,0
0,Power Saving,121,0
#1,Turbo (624/312/156 MHz),a000218,e
1,Turbo (624/208/104 MHz),2000310,e
#1,Overclocked (520/260/130 MHz),a000214,c
1,Overclocked (520/260/64 MHz),2000290,c
1,Standard (416/208/104 MHz),2000210,a
#1,Power Saving (208/104/104 MHz),0000110,9
1,Power Saving (143/143/71 MHz),0200010b,8

Leaves only one setting for each CPU speed.

None of the above values cause lockups for me, I just commented those three lines out to unclutter the applet.

[iamasmith]

I wonder how many developers look at user mods to data files with comments added realising there's no implicit support for comments and realise, OK it will work any way, the lines fail the integrity check so will be ignored.

Are you happy with the screen flicker at the lowest rate? I thought you wanted to read ebooks whilst underclocked.

[sriley]

Heh.  I didn't know for sure that the comments would be ignored, I just gave it a try and it worked.

As for the screen flicker, that's why I used comments.  When I have more time to really see how it feels I may try the other underclocked value to see which I like better.  I just started with the lowest because it should have the biggest impact on battery life.



BTW, I was very confused about the difference between USB mini-A (host) and mini-B (device) cables until a recent post elsewhere on this site.  I didn't want to buy a mini-A USB cable until I tried making one myself by cutting the connector open and soldering a short between pins 4 and 5.  Finally got around to it, now my tiny Targus USB optical mouse with the retractable cable works.  Very cool!  I'm going to shorten my mini-A cable to about 12" tomorrow, and I need to go find a USB hub with a very low-profile power supply so I can connect other stuff.

[iamasmith]

...
BTW, I was very confused about the difference between USB mini-A (host) and mini-B (device) cables until a recent post elsewhere on this site.  I didn't want to buy a mini-A USB cable until I tried making one myself by cutting the connector open and soldering a short between pins 4 and 5.  Finally got around to it, now my tiny Targus USB optical mouse with the retractable cable works.  Very cool!  I'm going to shorten my mini-A cable to about 12" tomorrow, and I need to go find a USB hub with a very low-profile power supply so I can connect other stuff.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78279\"][{POST_SNAPBACK}][/a][/div]

Yeah, I got a retractable mouse from Maplin in the UK recently, optical, scrollwheel, fits in your pocket without tangling and you can use it without getting cramp.... for £12, awesome! I guess that's about $20 or thereabouts. These things are fantastic and you can practically carry them in a spare pocket with your Z.

Man, I've got to get an X server running under QT that supports the mouse now... I think my next project may be to look at porting the QT framebuffer and touchscreen stuff as modular drivers into either XFree86 or XOrg so that you can actually use some of the other more standard stuff like the mouse support with the display server... (I just know that this is going to be one of those when I get around to it sort of projects though).

- Andy

[sriley]

These things are fantastic and you can practically carry them in a spare pocket with your Z.

Exactly!  That's why I'm going to reduce the length of the mini-A cable I made.  I'll be able to get everything (mouse, power cable, LAN and wifi cards, and JumpDrive that takes SD cards, and maybe a super slim USB hub) in one very small camera bag.

[kahm]

These things are fantastic and you can practically carry them in a spare pocket with your Z.

Exactly!  That's why I'm going to reduce the length of the mini-A cable I made.  I'll be able to get everything (mouse, power cable, LAN and wifi cards, and JumpDrive that takes SD cards, and maybe a super slim USB hub) in one very small camera bag.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78284\"][{POST_SNAPBACK}][/a][/div]

I've got a targus leather case that's about the same size as my Z, which carries 4 CF cards (3 data, 1 bt), my iRiver cable, a spare stylus, and my wi-fi card. A mini-mouse *might* fit, but it'd be tight.  The Z itself is in my pocket.

[kahm]

Close enough for rock'n'roll
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Okay. You're right. I should have been able to guess that one.  

Here's the new Apache IPK with the user Webauthor, group webauthor:

[a href=\"http://www3.telus.net/~ranko/apache-1.3.27-php-4.2.3_0.2-c3k-2_arm.ipk]http://www3.telus.net/~ranko/apache-1.3.27...2-c3k-2_arm.ipk[/url]

It's been quiet in here ever since the beta release...

[iamasmith]

Close enough for rock'n'roll
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Okay. You're right. I should have been able to guess that one.  

Here's the new Apache IPK with the user Webauthor, group webauthor:

[a href=\"http://www3.telus.net/~ranko/apache-1.3.27-php-4.2.3_0.2-c3k-2_arm.ipk]http://www3.telus.net/~ranko/apache-1.3.27...2-c3k-2_arm.ipk[/url]

It's been quiet in here ever since the beta release...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78481\"][{POST_SNAPBACK}][/a][/div]

Yes, I release the battery applet update the other day, there are a couple of issues related to cards which may be script related that could do with being hunted down but I'm also talking to Bryan (stupkid) about getting a bugtracker set up.

I anticipate trying out the 18a Tetsu Kernel with this ROM too, currently it's using 17h. 18a updates a few bits here and there and adds the granularity stuff into the /proc/apm output (translate : Gives hi res % on the battery power )

[collywobbles]

I anticipate trying out the 18a Tetsu Kernel with this ROM too, currently it's using 17h. 18a updates a few bits here and there and adds the granularity stuff into the /proc/apm output (translate : Gives hi res % on the battery power )

Andy - will you incorporate the new kernel/mplayer/other fixes into a new beta (or cefrnr) and if so do you have a timescale?
Thanks
Russell

[iamasmith]

I anticipate trying out the 18a Tetsu Kernel with this ROM too, currently it's using 17h. 18a updates a few bits here and there and adds the granularity stuff into the /proc/apm output (translate : Gives hi res % on the battery power )

Andy - will you incorporate the new kernel/mplayer/other fixes into a new beta (or cefrnr) and if so do you have a timescale?
Thanks
Russell
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78503\"][{POST_SNAPBACK}][/a][/div]

Currently there's only one 'verified' update. That would be the Battery Applet.

I started a new thread to discuss testing with the v18a Kernel before layering that into the Cacko3K beta because it requires an update to initrd and any full ROM release requires testers to zero the devices.

My thoughts about release interval are to stabilise as many features as we can so that testers don't get racked-off about zeroing their device and copying everything back - I think we all want to use our Zs as real devices too.

mplayer won't get 'built in' just yet. It can be installed fairly easily but if you took a look at atty's page he's pretty active on the project. It wouldn't make sense to put something that's in 'flux' into a ROM image.

We will hopefully have a bugtracker up and running soon to track reported issues as they come in.

Beta testing on this device, bug tracking and reporting is going to be really important because we can answer some of the questions before they are raised on the SL-C1000 build... if you don't know.. here's what's likely to happen..

1. Alpha, Betas and cefrr releases of Cacko3K on the SL-C3000, gathering stability data and developing applets/tools/background on the SL-C3000 models.

2. Possibly similar Alpha/Beta program driven by Maslovsky for the SL-C1000, gathering similar data. Slightly different focus - Maslovsky has more focus on unified kernel etc...

During this time there will be crossover stuff being passed backwards and forwards..

3. Crossover stuff encorporated into new 3K/1K betas etc..

4. SL-C1000 release.

5. Adaption system built to create SL-C3000 from SL-C1000 ROM + add any 3K specifics that for some reason aren't suited to 1K - and remove 1K specifics not suited to 3K (and yes there may be some).

6. SL-C3000 release.

The aim of this is really to converge the ROM creation of the two devices.

...so to answer the question, don't expect a ROM every week but there will be some activity and potentially some 'quickfix' stuff like the Battery Monitor/CPU Overclock.

Andy

[iamasmith]

There's a feature that I would like to discuss.

/home in the current ROM and in the Sharp ROM lives in flash, there are symbolic links from /home/zaurus/Applications to /hdd2/Applications and /home/zaurus/Documents to /hdd3/Documents so that using standard Sharp stuff all main storage requirements are handled by these locations.

I considered initially putting /home on hdd2 but my initial thoughts were that because /etc is actually in /home/etc that may cause problems with suspend/resume whilst we waiting for the hdd to resume.

This can actually be resolved quite simply by linking /etc to a different location in flash and making /home/etc a symbolic link to that same location in flash.

The advantages are going to be that users will not need to be extra careful about the use of storage in /home/zaurus (i.e. currently if you sftp a large file to the Z then you better make sure you don't put it in your home directory) and more applications will install 'out of the box' without custom tweaks (sorry for your efforts Kahm, this may be better in the long run).

Can anyone spot any obvious gotchas before I go and try this out? I know that the OZ team already do this but we are looking at Sharp ROM IPK compatibility here - I'll also obviously have to modify the 'device clearing' process so that it knows about the new locations.

- Andy

[mammothrept]

Is there any way that the Cacko ROM can be tweaked to allow the Japanese input and dictionaries to remain?  The Zaurus has a great dictionary built in and it would be a shame to lose it.

[iamasmith]

Is there any way that the Cacko ROM can be tweaked to allow the Japanese input and dictionaries to remain?  The Zaurus has a great dictionary built in and it would be a shame to lose it.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78538\"][{POST_SNAPBACK}][/a][/div]

This is covered in the readme file. Yes it should eventually be done but only when we have a 'milestone' ROM (either cefrr or official Cacko).

[kahm]

There's a feature that I would like to discuss.

/home in the current ROM and in the Sharp ROM lives in flash, there are symbolic links from /home/zaurus/Applications to /hdd2/Applications and /home/zaurus/Documents to /hdd3/Documents so that using standard Sharp stuff all main storage requirements are handled by these locations.

I considered initially putting /home on hdd2 but my initial thoughts were that because /etc is actually in /home/etc that may cause problems with suspend/resume whilst we waiting for the hdd to resume.

This can actually be resolved quite simply by linking /etc to a different location in flash and making /home/etc a symbolic link to that same location in flash.

The advantages are going to be that users will not need to be extra careful about the use of storage in /home/zaurus (i.e. currently if you sftp a large file to the Z then you better make sure you don't put it in your home directory) and more applications will install 'out of the box' without custom tweaks (sorry for your efforts Kahm, this may be better in the long run).

Can anyone spot any obvious gotchas before I go and try this out? I know that the OZ team already do this but we are looking at Sharp ROM IPK compatibility here - I'll also obviously have to modify the 'device clearing' process so that it knows about the new locations.

- Andy
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78513\"][{POST_SNAPBACK}][/a][/div]

Well, I say move it and save me the hassle of having to rebuild any *more* packages!  

Quite seriously, though, the /home/zaurus on flash is the *worst* thing about the C3k by far. If it is possible to move it then please do, and I'll gladly test it to death for you