OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: Grimwiz on March 09, 2004, 01:30:29 pm
-
I am using the 1.20 \"Daniela\" rom. I have to say this is a stunning piece of work, looking much better than the standard Sharp rom, making better use of the available space and much more secure.
It successfully configured access to the net through my bluetooth phone and through my wlan card without having to edit text files.
The fonts are much more suitable for that size of screen (though I think I\'d like to try something between 12 and 16 point in Qconsole.
I have found the following issues...
Fatal
* eject my Bluemonkey Bluetooth card through software - the user interface locks up but plugging and unplugging the USB cable causes \"boing\" noises in Windows so I guess something must still be running. Just ripping the card out without stopping it does not always lock up the zaurus.
* typing reboot as root in a console window seems to stop it dead too.
Nonfatal-
* rotate the screen, play mahjongg (it runs in low rez) for a bit then when you rotate back again the user interface crashes and restarts
Wierd
* swapping sd cards sometimes means the next card is not recognised, sometimes it becomes a \"zero\" length device and requires a reboot to fix.
* Some fonts have the \"\" character showing up as a Y-ish character.
I have the following suggestions for the next version...
* when you are not the \"root\" user, don\'t use \"# \" as the prompt
* get rid of colour \"ls\" (personal preference, but it should be configurable)
* a pointer to a compatible development environment would be helpful to those who like to code during long journeys.
* how do you disable fn-shift-c taking a screenshot?
-
Just expecting the next question - this is on a Sharp SL-C860.
-
I too installed the new ROM on the C860. I have been very happy with it for the most part. My issues have been the folowing:
1) I can\'t get Wellenreiter to work know matter what I do about wlan-ng, hermes, or host-ap drivers. This is true with both my Ambicon CF1100 and SanDisk (D-Link 660) cards.
2) When I run any 5500 series low resolution apps and rotate the screen to the palm mode, Cacko frequently crashes and reboots itself automatically when you later rotate the screen back to the normal landscape mode. This doesn\'t happen with higher resolution apps designed for the C860 screen.
3) I cant\' change the type size in Konsole no matter what I do. It is just stuck at 36 which is too big for me. I wish there was a way to manually edit a file where this is stored.
Other than that I have had no problems. The new Cacko 1.20 ROM seems like a great piece of work.
-
anytime an alarm goes off on my 860 with this new rom qtopia restarts.
no other real problems, the new features are great!
-
I confirm the stretched screen bug which was there in the previous version of the cacko ROM. It actually only crashes QTopia, not a full reboot. I also had sporadic QTopia restarts with both the previous and sadly this version of the ROM. The screen will go black with a sideways message (too hard to read), followed by a blank white screen and eventually the time setup. I suspect it is only QTopia crashing here too. Usually occurs when the screen saver is active.
But aside from these, its the best ROM out there until PDAXRom gets full PIM synch!
-
Fatal
* eject my Bluemonkey Bluetooth card through software - the user interface locks up but plugging and unplugging the USB cable causes \"boing\" noises in Windows so I guess something must still be running. Just ripping the card out without stopping it does not always lock up the zaurus.
I had the same problem with previous Cacko ROM and Bluemonkey. If you suspend first, then remove, no more lockup.
-
eject my Bluemonkey Bluetooth card through software - the user interface locks up
Sorry, I don\'t that card, so I cannot help you. My bluetooth card worls fine.
typing reboot as root in a console window seems to stop it dead too
Just tried that and my zaurus just reboots...
rotate the screen, play mahjongg (it runs in low rez) for a bit then when you rotate back again the user interface crashes and restarts
Regarding low res mode - it\'s known to be buggy in Qtopia, better not to run apps in that mode. Tap&Hold app\'s icon and clear the magnified screen option.
I have the following suggestions for the next version...
* when you are not the \"root\" user, don\'t use \"# \" as the prompt
* get rid of colour \"ls\" (personal preference, but it should be configurable)
You can do it all yourself. Just do a search in some linux docs - you\'ll find out how.
-
1) I can\'t get Wellenreiter to work know matter what I do about wlan-ng, hermes, or host-ap drivers. This is true with both my Ambicon CF1100 and SanDisk (D-Link 660) cards
See my recent post in the other thread. Maybe it will be helfull.
3) I cant\' change the type size in Konsole no matter what I do. It is just stuck at 36 which is too big for me. I wish there was a way to manually edit a file where this is stored.
The file is /home/zaurus/Settings/QKonsole.conf. Try to edit it or just delete, so that konsole app recents to default settings.
a pointer to a compatible development environment would be helpful to those who like to code during long journeys
http://www.zaurususergroup.com/modules.php...q=getit&lid=207 (http://www.zaurususergroup.com/modules.php?op=modload&name=UpDownload&file=index&req=getit&lid=207)
-
The link above takes me to the main zaurususergroup download index, where the only reference to gcc I see is under the X11 rom. I\'ll try that thanks.
The \"ls\" seems hardcoded with control characters, not using TERM or any sensible configuration files. As there is a check on the output device in busybox I can get rid of colours by using \"ls | cat\" or avoid the whole issue with \"echo *\" but thats not the point. At the moment I cannot compile so recompiling \"ls\" is also not an option yet. (I\'m considering binary patching busybox but I\'m not that irritated yet)
For simple things like changing prompts I am capable of changing PS1=\"# \" to PS1=\'$ \' in the /home/zaurus/.profile for myself but would like to offer such modifications as being beneficial to the generic rom. Would you prefer a \"diff -c\" in future rather than a verbal description of the suggested modification?
-
I have the same bluetooth card as Grimwiz (well actually it\'s the same card but rebranded) and I have the same problems as him. My card is a Armadillo Accessories Bluetooth CF Card V1.1 with \"BLUeCF\" written down the side.
If I try to cardctl eject the card my zaurus will freeze completely. I have to remove the battery and reboot. The same also happens in suspend and when I shutdown/reboot because I\'m guessing there\'s a \"eject bluetooth CF card on suspend\" routine. This is peculiar because in old Cacko Qtopia ROM\'s I had no problems (I could reboot fine, eject fine, suspend fine).
This problem only happens in recent Cacko ROM\'s (pdaXrom, Qtopia) and the original Sharp ROM that came with my Zaurus when I imported it (but it had an english conversion by the person I bought it from, I\'m not sure if that counts).
-
The link above takes me to the main zaurususergroup download index, where the only reference to gcc I see is under the X11 rom. I\'ll try that thanks.
Scroll down to Recently Added Downloads. It\'s called Developer Image
-
I have the same bluetooth card as Grimwiz (well actually it\'s the same card but rebranded) and I have the same problems as him. My card is a Armadillo Accessories Bluetooth CF Card V1.1 with \"BLUeCF\" written down the side.
If I try to cardctl eject the card my zaurus will freeze completely. I have to remove the battery and reboot. The same also happens in suspend and when I shutdown/reboot because I\'m guessing there\'s a \"eject bluetooth CF card on suspend\" routine. This is peculiar because in old Cacko Qtopia ROM\'s I had no problems (I could reboot fine, eject fine, suspend fine).
This problem only happens in recent Cacko ROM\'s (pdaXrom, Qtopia) and the original Sharp ROM that came with my Zaurus when I imported it (but it had an english conversion by the person I bought it from, I\'m not sure if that counts).
I wish I could help, but my bluetooth card works fine. I hope someone with the same card as your will be able to figure out the problem...
-
The \"ls\" seems hardcoded with control characters, not using TERM or any sensible configuration files. As there is a check on the output device in busybox I can get rid of colours by using \"ls | cat\" or avoid the whole issue with \"echo *\" but thats not the point. At the moment I cannot compile so recompiling \"ls\" is also not an option yet. (I\'m considering binary patching busybox but I\'m not that irritated yet)
For simple things like changing prompts I am capable of changing PS1=\"# \" to PS1=\'$ \' in the /home/zaurus/.profile for myself but would like to offer such modifications as being beneficial to the generic rom. Would you prefer a \"diff -c\" in future rather than a verbal description of the suggested modification?
I\'m not sure these modifications are \"beneficial to the generic rom\". Those are basicaly your own preferences, which are not nesserely the same as others. In fact, you\'re the only person I see here who does not like a colored ls output...
-
I added a fix for the Bluemonkey card in the BlueZ ipks referenced from the Bluetooth howto. Basically the card hangs a Z on eject if it is not given enough time to shutdown. I added a \'sleep 1\' to /etc/pcmcia/bluetooth to fix this, but if it is not working on these new roms, then maybe the sleep time needs increasing.
-
Thankyou very much for the pointer to the development download, I\'ve downloaded it and expect to play with it tonight.
I\'m not against colouring of ls, I am against it corrupting the output with control codes at inappropriate times (e.g. if you are using a remote terminal). I would like to choose colours when I need them and suppress them when I\'m using things like \"expect\".
As for the prompt, this seems to be a bug that has crept in between the sharp rom and the new one. (sharp got it right). It is considered good practice for the shell prompt on a unix machine to be different when you are root because you are working in a different security environment.
Regarding adding a sleep into /etc/pcmcia/blootooth, I added it to the line after \"echo \"Done.\" when stopping the card but it did not seem to make any difference. Should I redownload the latest BlueZ ipks? Does it help diagnose the fault if I say the bluetooth card\'s green light goes on and stays on? Ahh well, out with the battery....
-
I\'m not against colouring of ls, I am against it corrupting the output with control codes at inappropriate times (e.g. if you are using a remote terminal). I would like to choose colours when I need them and suppress them when I\'m using things like \"expect\".
Changing ls means changing busybox, which also means breaking compatibility with lots of utils. We cannot afford that, we\'re not Sharp
If yuu want you can build your self a better version of busybox and replace it.
Regarding adding a sleep into /etc/pcmcia/blootooth, I added it to the line after \"echo \"Done.\" when stopping the card but it did not seem to make any difference. Should I redownload the latest BlueZ ipks? Does it help diagnose the fault if I say the bluetooth card\'s green light goes on and stays on? Ahh well, out with the battery....
Try to add it just inside the \"stop\" case, before any other actions like rmmod, etc are done.
-
I\'ve got the development package installed and running - compiling angband as I type.
Direct link is http://www.zaurususergroup.com/modules.php...q=getit&lid=207 (http://www.zaurususergroup.com/modules.php?op=modload&name=UpDownload&file=index&req=getit&lid=207)
I dont really want to go near busybox but I will compile a standalone \"ls\"
bluetooth update - I moved the sleep 1 so it was between \"stop_uarts\" and \"rmmod rfcomm\" but it still halts as before.
-
bluetooth update - I moved the sleep 1 so it was between \"stop_uarts\" and \"rmmod rfcomm\" but it still halts as before.
Sounds like you\'re editing the wrong file. I\'m pretty sure I said /etc/pcmcia/bluetooth, which is what I mean. In that script in the latest BlueZ ipks I put a sleep command. It\'s probable the sleep time just needs increasing.
See the BlueZ Howto (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=Bluetooth) for the latest packages
-
* eject my Bluemonkey Bluetooth card through software - the user interface locks up but plugging and unplugging the USB cable causes \"boing\" noises in Windows so I guess something must still be running. Just ripping the card out without stopping it does not always lock up the zaurus.
I have the same card and the same problem.
Just install \"bluez-zaurus_2.3-2.4.18d_arm.ipk\" (thanks again tumnus) and your problem will go away.
no need to edit or remove anything, just whack it straight on over the top of the exiting stuff.
***** EDIT ******
Erm, actually, don\'t do this.
It *was* all working fine until I rebooted it, and now it\'s not working at all.
At least it doesn\'t crash when you eject the card anymore
Peter
-
OK, reflashed and started again.
Here is what I have discovered. if you issue hciconfig hci0 down before doing an eject, it works.
tumnus,
your /etc/pcmcia/bluetooth and the one in this rom are *totally* different.
This is much much bigger.
I will continue to experiment.
Peter
-
ok,
I seem to have it working now.
for the 5/3/04 qtrom do this as root :-
vi /etc/pcmcia/bluetooth
:56 (to jump to line 56)
o (to insert a line after "echo -n $"Shutting down $prog... ")
{tab key}hciconfig hci0 down
{cancel x key} (to escape from insert mode in vi)
:wq (to save and exit)
works for me, how about you?
Peter
-
Adding the hciconfig line fixes the problem for me too. My line numbers match with yours, Zbones.
-
For those who were following the angband saga - it works fine if I shut down the gui and use the raw console but sadly doesnt work inside Qconsole.
-
tumnus,
your /etc/pcmcia/bluetooth and the one in this rom are *totally* different.
This is much much bigger.
Basicaly that\'s because new ROM initializes bluetooth only upon card insertion, while original tumnus packages start bluetooth upon zaurus boot. The bluetooth script in /etc/pcmcia is basicaly the one that used to be in /etc/rc.d/init.d directory.
-
look, as far as the ls... just compile gnu ls and put it in your path before the busybox ls, etc. you can then
set LS_COLORS=none or whatever. that way, you configure YOUR machine for YOUR taste, etc.
me, I hate ls color, and whenever I have had it, I was able to disable it with a setting, if you can\'t do that
with busybox, then put another bin in your path before... if that doesn\'t work, break the link to busybox, etc.
It\'s your machine -- configure it as you wish.
Scott
-
:-) ScottYelich. that makes two of us that dont like colours so far, but you missed my point - blindly adding control characters is in my view a bug, nothing to do with preferences. One reason why linux has improved so much so fast is because people roll back bugfixes into the distributed code so that we dont all have to reproduce the same fixes to progress. I would concur that this forum is the wrong place to discuss busybox bugs though. Consider the matter closed, I will not discuss \"ls\" further.
-
I agree... in the past I have hard coded vt control codes into some programs ...
good luck to anyone not on a VT compatible, eh?
so, same goes with colors, etc. :-]
Scott
ps: ever come across a rabid mirc user in irc?
-
Installed Xqt, looks like running angband in an xterm works perfectly.