Messages

1

Angstrom & OpenZaurus / Symliniks Disappearing?

« on: March 15, 2006, 09:22:15 am »

Thank you Mickeyl, you definetly pointed the right direction
A simple:
      ldconfig /media/card/usr/lib
fixes all the problems.

Even better, adding the following line:
      /media/card/usr/lib
to the file /etc/ld.so.conf assures the libraries are linked at each boot properly.

The only thing I am wondering about is why sometimes during the boot process the SD was not recognized properly, and then created this issue.

2

Angstrom & OpenZaurus / Symliniks Disappearing?

« on: March 14, 2006, 12:21:18 pm »

I am lately experiencing an odd problem.

For some undetermined reasons, symlinks tend to disappear randomly from my /usr/lib/ directory. Always the same ones, I am using hentges ROM, and when it happens always the same apps don't work anymore: opiemail, qpdf, konqueror, xmms, several games and some other apps. I've tried to launch the non-working apps from the console, they point to missing libraries (some of them being on /media/card/usr/lib and some on /usr/lib, but with different names). If I re-link the libs manually, things got back to working.

This problem has occoured me four times in the last week, even if I don't do nothing. One time I just suspended the Z, and when I powered it back again, the symlinks were puff. It's strange also because everything was working fine lately, then this problem shows up, and even after several re-flashing it does come back (usually before I am able to finish my installation and setup all my hardware and favorite apps).

Using ipkg-link mount /media/card does not help: the broken link are repaired, but the working one are messed up (and xmms got especially messed).
Manual linking does work pretty well, except that is time consuming and I am unable to get opiemail back to work. It just says: : QuickLauncher invoked as: opiemail

Since this same problem is coming every time but completly at random I am starting to think about a flash memory physical problem. May that be the issue? How to check it out? I know about the existence of service menus, but don't know how to call them on the SL-5500. I also know they may be dangerous. Any suggestion about this?
Or am I moving completly to the wrong direction?

Thanks for any help!

3

Accessories / Irk Customizations

« on: January 04, 2006, 07:08:02 pm »

If i try that command on my console, I get the glasshour icon, but nothing happens, nor error message is displayed.
I think this is due to different ROM: I'm using OZ + Opie.
Anybody knows the command to use in this case?

I think once the command is known, the problem of using it with IRK can be solved.
Maybe creating a simple script like this:

Code: [Select]

#!/bin/sh
qcop QPE/System 'execute(QString)' __rotate
making it executable, placing it somewhere in the path, and recalling it with the usual
*nameofthecommand in the IRK settings panel.
Maybe give it a try and tell me if it works this way.

4

Themes, Icons, and Backgrounds / Themes On Oz-opie

« on: January 04, 2006, 06:46:47 pm »

Ok then. Thank you for the suggestions.
I'll check in there, or give another look around. I'll come with any news I'll get.

5

Themes, Icons, and Backgrounds / Themes On Oz-opie

« on: January 03, 2006, 06:15:35 pm »

Yes, I've already checked inside of them.
Usually there is a file .ktheme
This file is another tarball containing a directory in which the true files are (i.e. the .themerc file and the various pixmaps/wallpapers/sounds files). No sub-directories are created, so no hints on where to try to place the files are provided.

6

Accessories / Irk Customizations

« on: January 03, 2006, 11:28:16 am »

Many thanks for your reply d.maddock1. Now I've setup all the keys on my keyboard in the proper way  

Just one more question: there is a way to actually associate the 'rotate' key (cmd + ") to the rotation function? That would be useful indeed.

7

Themes, Icons, and Backgrounds / Themes On Oz-opie

« on: December 27, 2005, 12:33:52 pm »

I'll gladly make some tests, but I have not any Linuxbox running KDE 2.x (or any KDE at all) handy to use as an example.

Can somebody hint me to the correct place on which to create the directories, basing upon a standard KDE 2.x installation?

From the screenies on this page:

http://www.ottaky.com/openzaurus.php

it looks like there is some way to use themes, since I can't recall of any transparent menus being by default on Opie.

8

Themes, Icons, and Backgrounds / Themes On Oz-opie

« on: December 26, 2005, 08:29:55 pm »

I know it is possible on the Sharp ROM, and I would like to know if
it is also possible to change/add themes on Opie 1.2 running on OZ 3.5.3.

I've managed to find this information:

http://opie.handhelds.org/cgi-bin/moin.cgi/Themes

but I am unable to locate any 'themes' (or '.themes') directory on my Z. Maybe should I create it manually?

9

Accessories / Irk Customizations

« on: December 26, 2005, 08:24:22 pm »

May sound like a silly question, but: how to create new macros?

I've managed to get a pocketop keyboard to work with OZ and I have done some minor tweaking at the configuration, e.g. making the CMD+Address combo popping up the menu.

But how to add new combos? The 'new' button on the configuration panel of IRK doesn't seems to work (unless I am missing something really basilar). I would like too to have CMD+a sorting out #8217

And how to create more macros? Would be pretty to have a console pop-up just on the pressure of a button

10

Angstrom & OpenZaurus / Bluetooth Problem On Henntges Oz 3.5.3

« on: September 18, 2005, 07:51:20 pm »

Uhm...
Following your suggestions I'm going somewhere.  
It is not much pratical right now, but still it works, more or less.

I've wrote a little script:

Code: [Select]

#!/bin/sh
modprobe hci_uart
sleep 1
setserial /dev/ttyS3 baud_base 921600
hciattach /dev/ttyS3 billionton
hciconfig hci0 up
/etc/init.d/bluetooth start
It basically does what /etc/init.d/bluetooth alone didn't do: setup my card and then startup the bluetooth services. Of course I too have commented out the references to HIDD in /etc/init.d/bluetooth.

However, even if when i run it everything seems to work well ("hciconfig -a" shows the device, and "hcitool -scan" gives the proper results), I get the following message just after running it:

      BCSP initialization time out

Making some test, I found that is due to the "hciconfig hci0 up" being in the script.
If I remove it from there and run it manually, I don't get the message.
I've tried also to put some sleep time between "hciattach" and "hciconfig" in the script, but still I get the message. Any hint on this?

I can remove the card running /etc/init.d/bluetooth stop. When I re-insert it I should re-run my script. When I suspend, I have to resume the card manually, by "cardctl resume 0".

At least this way, I've to run just one command upon starting/stopping the bluetooth.
Thanks for any help so far.


***little update***

The card is somewhat unreliable. Sometimes, upon insertion, the led doesn't blink.
Even if "cardctl status" shows the card as being active, it is not.
Doing "cardctl suspend 0", waiting a couple of seconds, and then "cardctl resume 0",
makes it up. Then the script works well, and doesn't give that "BCSP initialization time out" error message.

11

Angstrom & OpenZaurus / Bluetooth Problem On Henntges Oz 3.5.3

« on: September 14, 2005, 09:31:33 am »

First of all, many thanks for your help.  

I fear my problem is on a most basic level.
I'm not trying to setup a connection with a phone by now, but just to have the
bluetooth card running smoothly.
What I'm asking for, is if it your /etc/init.d/bluetooth script works well without any tweaking, and if it's sufficient by itself to make the bluetooth card up and running.
As I said in my previous posts, if I try to run it I get an error, and after tweaking the file I don't get the error anymore, but I'm still unable to use the card properly.
But if I use the sequence of 4 commands (setserial, modprobe, hciattach, hciconfig) everything is fine.

So, actually to make the card works you just run the script you posted, that in turns call the /etc/init.d/bluetooth script? No other tweaks?

If this kind of discussion is not of general interest maybe we can move to PM.

Thanks for your help so far!

12

Angstrom & OpenZaurus / Trying To Start Up Bluetooth On Oz

« on: September 08, 2005, 08:07:16 am »

Looks exactly as mine...
I'm unable to help you more, unfortunately.
As far as I can see, everything looks ok...

13

Angstrom & OpenZaurus / Bluetooth Problem On Henntges Oz 3.5.3

« on: September 08, 2005, 07:43:41 am »

Ok, I'm getting some progress  
Basing upon Lardman suggestion and the information I got here:

https://www.oesf.org/forums/index.php?showtopic=9347&hl=hidp

about the absence of the HIDP support, I edited the script, commenting out
all the references to it.
Now the script start and stop correctly:

Code: [Select]

/etc/init.d/bluetooth start
Starting Bluetooth subsystem: hcid sdpd rfcomm

/etc/init.d/bluetooth stop
Stopping Bluetooth subsystem: pand dund rfcomm sdpd hcid
But my device is still unavaiable: "hciconfig -a" gives no output
I've tried to load hci_uart manually (modprobe hci_uart) before running the demon, since that module is required and it's not loaded upon card insertion or by running the bluetooth demon itself.
But still no luck. "hciconfig -a" still giving me a blank output.
uhm...

14

Angstrom & OpenZaurus / Bluetooth Problem On Henntges Oz 3.5.3

« on: September 07, 2005, 07:50:16 pm »

Would you please help me reach your same result?

I've managed to install correctly a Billionton card at kernel level.
It is correctly recognized, and if i use

Code: [Select]

setserial /dev/ttyS3 baud_base 921600
modprobe hci_uart
hciattach /dev/ttyS3 billionton
hciconfig hci0 up
the cards go up and running. I've just tried to make some "hcitool scan" with other bt peripherals around, just to test, and everything is fine.

But if i try to run:
/etc/init.d/bluetooth start

I got this error:
Starting Bluetooth subsystem: hcid sdpd Can't open HIDP control socket: No such file or directory
  hidd rfcomm.

And nothing works.
I would like to make at least /etc/init.d/bluetooth start (and stop) to work.
Otherwise, being unable to stoppping the service, every time I extract the card I need to reboot the Z to make it work again.

Thanks for any help!

15

Angstrom & OpenZaurus / Trying To Start Up Bluetooth On Oz

« on: September 07, 2005, 01:34:03 pm »

Try to insert the card, and type from console:

cardctl ident

then compare the results with the content in your /etc/pcmia/bluetooth.conf
file. Maybe your card has a different chip?