Messages

1

Software / Opie-keypebble Vnc And Mythtv

« on: February 05, 2006, 01:55:49 pm »

Hi,

I have a problem using opie-keypebble VNC client.

When I try to control my HTPC (MythTV 0.18.1) I have to use ESC (Zaurus Cancel key) to go back to "previous" menu. The problem is that this same key EXIT's the VNC client software!!!
As far as i know there are no possibilities to config MythTV to use a different key for this.

I am now using Sharp ROM and Meanie's keyhelper.xml.

Anyone having a solution?

I have tried other VNC clients (java-based) but no luck so far...

I have no problems with TightVNC or RealVNC client on my Win XP computer controlling MythTV because it doesn't exit when ESC key is hit.

EDIT: I found this on MythTV homepage (I had forgotten mythweb, not tried it yet);
"The keys.txt file describes what the various keyboard commands are. If you have loaded mythweb, you may change the default keys to your liking."
[div align=\"right\"][a href=\"index.php?act=findpost&pid=113657\"][{POST_SNAPBACK}][/a][/div]

Solution:
You could edit databasetable "keybindings" directly or install mythweb and use keybindings setup. I solved my problem by changing keybinding from Esc to Tab,Esc.
Now it works OK from VNC client.

2

Software / Opie-keypebble Vnc And Mythtv

« on: February 04, 2006, 04:53:44 pm »

Hi,

I have a problem using opie-keypebble VNC client.

When I try to control my HTPC (MythTV 0.18.1) I have to use ESC (Zaurus Cancel key) to go back to "previous" menu. The problem is that this same key EXIT's the VNC client software!!!
As far as i know there are no possibilities to config MythTV to use a different key for this.

I am now using Sharp ROM and Meanie's keyhelper.xml.

Anyone having a solution?

I have tried other VNC clients (java-based) but no luck so far...

I have no problems with TightVNC or RealVNC client on my Win XP computer controlling MythTV because it doesn't exit when ESC key is hit.

EDIT: I found this on MythTV homepage (I had forgotten mythweb, not tried it yet);
"The keys.txt file describes what the various keyboard commands are. If you have loaded mythweb, you may change the default keys to your liking."

3

Sharp ROMs / Cacko 1.23 Full And Linksys Wcf12

« on: February 02, 2006, 01:46:45 pm »

I have now upgrade the firmware in WCF12 to pk010101.hex and sf010804.hex.

Upgrade went fine, but same result!

I purchased my C1000 from FigLabs. I have no problem with my WCF12 with original firmware and FigLabs ROM version.

Strange?

I will now take a NAND-backup of Cacko 1.23 and go back to FigLabs ROM just to test if it still working there.

I will be back with results.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=113409\"][{POST_SNAPBACK}][/a][/div]

Cacko use hostap for these card. FigLabs, Sharp, use wlan-ng.

I beleive this is a hostap trouble.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=113414\"][{POST_SNAPBACK}][/a][/div]

Yes I think you are right. I get this message when connection are up and running for the first time after reboot:

wlan0 (WE) : Buffer for request 8B1B too small (0<13)

This is the only error/warning message after this first connection is established.
google gives only one indication to this problem; driver problems.

This is what dmesg gives during disconnecting:
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg=0x8888
wifi0: hfa384x_cmd: entry still in list? (entry=c24715a0, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg=0x8888
wifi0: hfa384x_cmd: entry still in list? (entry=c24715a0, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg=0x8888
wifi0: hfa384x_cmd: entry still in list? (entry=c24715a0, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg=0x8888
wifi0: hfa384x_cmd: entry still in list? (entry=c24715a0, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)

4

Sharp ROMs / Cacko 1.23 Full And Linksys Wcf12

« on: February 02, 2006, 12:27:25 pm »

I have now upgrade the firmware in WCF12 to pk010101.hex and sf010804.hex.

Upgrade went fine, but same result!

I purchased my C1000 from FigLabs. I have no problem with my WCF12 with original firmware and FigLabs ROM version.

Strange?

I will now take a NAND-backup of Cacko 1.23 and go back to FigLabs ROM just to test if it still working there.

I will be back with results.

5

Sharp ROMs / Cacko 1.23 Full And Linksys Wcf12

« on: February 02, 2006, 07:05:48 am »

>first try: with zaurus on, remove card, wait 5 seconds, reinsert.

>second try: remove card, execute "/etc/rc.d/init.d/pcmcia restart", reinsert card.

Thank you for fast reply!

The first method does work sometimes and sometimes not (Waiting 10 sec.).
(I was trying it myself before posting but I must av been to fast reinserting the card)

The second method work most of the times, but I had one situation during testing where I had to experiment myself because pcmcia restart didn't work; I then tried pcmcia stop -> pcmcia start (WiFi card removed). After inserting card I get connection!

It seems to be a problem with deinitializing of WiFi card during disconnecting phase. This problem is consistent. I can never reconnect right after a disconnect. I must always use one of your methods to get connected after a disconnect. Frustrating!!!

Is this problem just for WCF12?

It would be great if you or someone else (Cacko?) had a permanent solution for this!

WCF12 has been working for Cacko 1.22, right?

6

Sharp ROMs / Cacko 1.23 Full And Linksys Wcf12

« on: February 01, 2006, 08:04:09 pm »

Hi,

I installed Cacko 1.23 full on my brand new SL-C1000.

I configure WLAN with static IP etc. (without WLAN card in CF)
Then put in WCF12 card for the first time.
Tip on Connect and it connects. OK

Then, when I disconnects and reconnects for second time Cacko 1.23 full is hanging when trying to initialise WCF12, and timeouts after a while!
I can never get it up and running anymore (have to reinstall Cacko, then same again).

dmesg:
CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
etc. ....

Any solution?

______
dhas