Messages

1

Users / Re: touchscreen problem

« on: September 18, 2009, 05:42:28 am »

========== NEW LOG SECTION ==========
1   09/17/09 23:17:52   33 (spawning-device)   Starting... 2
1   09/17/09 23:17:52   33 (spawning-device)   Found /usr/pluto/bin/LaunchOrbiter.sh
05   09/17/09 23:17:54.829      Creating child 34 <0xb6fa48e0>
05   09/17/09 23:17:54.881      Creating child 36 <0xb6fa48e0>
05   09/17/09 23:17:54.935      Creating child 37 <0xb6fa48e0>
05   09/17/09 23:17:54.993      Creating child 38 <0xb6fa48e0>
05   09/17/09 23:17:55.056      Creating child 39 <0xb6fa48e0>
08   09/17/09 23:20:15.885      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:20:15.887      acquiring 4482.0.0.4484.2410 <0xb6f63b90>
08   09/17/09 23:20:15.889      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:20:15.891      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:20:16.183      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:20:16.183      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:20:16.184      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:20:18.478      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:20:18.478      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:20:18.479      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:22:16.519      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:22:16.519      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:22:16.520      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:22:16.881      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:22:16.881      acquiring 4482.0.0.4484.2410 <0xb6f63b90>
08   09/17/09 23:22:16.884      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:22:16.886      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:22:17.152      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:22:17.152      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:22:17.153      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:22:19.408      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:22:19.408      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:22:19.409      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
05   09/17/09 23:22:47.459      Event type 1 <0xb6fa48e0>
05   09/17/09 23:22:47.460      Event type 1 <0xb6fa48e0>

2

Users / Re: touchscreen problem

« on: September 18, 2009, 05:38:49 am »

here is the log from the md

== ATTEMPT FRESH START ==
1   09/11/09 10:04:38   /usr/pluto/bin/Spawn_Device.sh 33 (spawning-device)   25394 Dev: 33; Already Running list: 32,
== FRESH START ==
1   09/11/09 10:04:39   /usr/pluto/bin/Spawn_Device.sh 33 (spawning-device)   device: 33 ip: dcerouter cmd_line: LaunchOrbiter.sh
0   09/11/09 10:04:39   33 (spawning-device)   Entering 33
========== NEW LOG SECTION ==========
1   09/11/09 10:04:39   33 (spawning-device)   Starting... 1
1   09/11/09 10:04:39   33 (spawning-device)   Found /usr/pluto/bin/LaunchOrbiter.sh
05   09/11/09 10:11:14.597      Xlib: ErrorHandler_Grabber() // static int X11wrapper::ErrorHandler_Grabber(Display*, XErrorEvent*) <0xb70ec8e0>
05   09/11/09 10:11:14.634      Xlib: ErrorHandler_Grabber() // static int X11wrapper::ErrorHandler_Grabber(Display*, XErrorEvent*) <0xb70ec8e0>

3

Users / Re: touchscreen problem

« on: September 18, 2009, 05:33:03 am »

short reads happen when the handler tries to read from a device that is no longer there...hmm..

do you not see DecodeEventinFD messages?

-Thom

yes, could that be due to the removal of another md days ago? should i post sections of the whole log to give you a better idea of what is happening?

4

Users / Re: touchscreen problem

« on: September 18, 2009, 05:21:52 am »

you should not see a short read at all. did you remove an input device?

-Thom

thom, nope buddy. i only don't leave the mds on since i don't use it since the problem began.  maybe wrong dir/log i'm looking into?   

5

Users / Re: touchscreen problem

« on: September 18, 2009, 03:35:21 am »

bb90>
01      09/16/09 17:13:09.761           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:13.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:17.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:21.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:25.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:29.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:33.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:37.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>

device number is 31, got error message grep: /var/log/pluto/31_LaunchOrbiter.sh.log: No such file or directory. pulled up above log using grep -i generichidinterface /var/log/pluto/21_LaunchOrbiter.sh.log. 21_LaunchOrbiter.sh.log being the only log under that directory.  Also pulled up the log on the md itself, but it had no mention of genericHIDInterface. pretty sure that the above is not what is needed, but that all that seems to come up remotely close to the request. let me know where to find the correct log if so. thanks alot guys. I appreciate the help big time fellas. thanks again.

6

Users / Re: touchscreen problem

« on: September 17, 2009, 08:54:19 pm »

tschak: if this is really a regression, it has to be fixed asap. We can't trash existing stuff with new patches. And just as a note, that hid stuff should not really be handled in orbiter.

br, Hari

Zaerc, i tend to agree with the statement above. i can't understand why you would even jump in here and not have anything beneficial to say.  I am aware that it is alpha, but does it really makes sense to say my statement is bullshit, taking into account it was working up until a recent update? i could understand you saying that if i was expecting a new feature or something that has been broken prior to a recent update. so how is the error all mine?  come on dude, i was only making sure that thom didn't take offense to my posts because no disrespect was intended. read the post, i even thanked him for his help in trying to fix it back.  Thom, once again, thanks.  zaerc, take it easy

7

Users / Re: touchscreen problem

« on: September 17, 2009, 05:37:26 pm »

apparently, there still is more to do, nevermind that you guys are using a setup i can't reproduce. *hmm*

-Thom

Thom, i understand, and i appreciate you responding to my post.  I appreciate your attempt to repair the driver.  Hope you understand where we're coming from from, it's a little frustrating to have something working one day, and spending alot of money to purchase more hardware that was proven compatible, to only have your entire setup made useless the next day because of an error i did not make, nor have the equip to fix. please do not take my anxiety any way.      

8

Users / Re: touchscreen problem

« on: September 16, 2009, 09:47:12 pm »

hey guys, my experience as of today is as follows:

1) any selection is still being appended with a 1, thereby bringing you to the lighting menu
2)it has gotten worse. the curser does not follow most selections now. before today it would follow wherever you touch.  Before you were able to use the touchscreen on the kubuntu desktop. it worked perfectly. now the cursor does not follow where you touch on there too.  works fine booting kubuntu from harddrive without lmce, so it's a problem with lmce. 
3) all my md hardware is unusable because of this, spent alot of money when it did work, now all is just a waste of money.
4) like hari said, this a regression. 

9

Users / Re: touchscreen problem

« on: September 11, 2009, 05:23:51 pm »

oh ok thanks

10

Users / Re: touchscreen problem

« on: September 11, 2009, 04:51:14 pm »

This has been fixed, and should be available once the next round of updates is built. \

-Thom

Thom, ahey buddy, has this fix been rolled in? i rebuilt my core and did a reinstall last night and was excited,  tried to use my md, but the same issues still occur.  

11

Users / Re: touchscreen problem

« on: September 02, 2009, 05:21:10 am »

yeah thanks tom, appreciate it

12

Users / Re: Call for donations for features.

« on: August 21, 2009, 03:29:45 pm »

I think projects that would benefit everyone and at the same time bring in more users which will in turn bring more interest and donations are... ( these are also projects that I would personally donate the $100 for)

1. Recompiling- xinelib (or whatever it takes) to take advantage of vdpau. This way all you need is a $30 card to be able to play HD movies flawlessly.
2. HDPVR- whatever it would take to make the HDPVR work, supposedly its functional now with MythTV trunk. In my opinion MythTV is just about useless since the very best quality a person can get is from s-video. The HDPVR encodes in x264 which would workout perfect if we have xinelib with vdpau support.
3. Pick a popular board and make it the LinuxMCE recommended board and make it pnp. For example, the Zotac board has everything that you would need for a great media director (if we have xinelib with vdpau) and can be up and running for about $160. When someone new comes to the project and wants a board that will work right now there are too many hoops to jump through and no clear answer on what will work with LinuxMCE.


Looks like most people support kris' suggestions. vdpau and the MD mainboard for LinuxMCE does make sense. I would do a mobile orbiter, but those two do make sense in my opinion.

13

Users / Re: Call for donations for features.

« on: August 20, 2009, 04:43:46 pm »

I apologise that my comments have come across wrong, this happens.. a lot.

I didn't mean to sound condecending.

-Thom

Ok Thom, I apologise also.

14

Users / Re: Call for donations for features.

« on: August 20, 2009, 01:34:16 am »

Are you guys not grasping that I am working on this because I have no other choice?

I am trying to get donations, so I do not starve. I have no job. People are not hiring me, I am being TURNED DOWN from LESSER jobs because I am in their words, "OVERQUALIFIED"

So, you guys can sit back, with your jobs, and use the software, for free, as it is right now... or... you can help pay for my expenses so I can EAT, so I can have a ROOF OVER MY HEAD..and oh yeah, SO I CAN WORK ON THIS THING I LOVE SO MUCH.

-Thom

Hold the F@ck up a minute!!!!! Before I respond to that.....please tell me that response wasn't suppose to be as condescending and crude as it sounded! I may not be a linuxmce genius, but I can m@therfu@king read and your post was:

"So this means, that we need:

(1) features that most people want
(2) and are willing to pay for.

So please, don't just think of yourselves, think of what would be of benefit to most people."

So how the hell is me trying to help you by giving a suggestion to get the ball rolling by posting a poll for what probably will turn out to be a feature that is not a benefit for me, but i would contribute to help you out anyway, turn into you asking me if i'm "grasping" your request for a "donation"?!?! Now forgive me if i took it the wrong way, but if not, this is the second time you had some less then humble response for a man in your position.

15

Users / Re: Call for donations for features.

« on: August 19, 2009, 04:51:38 pm »

Question?  Thom...not sure if you have started a project already, but why don't you edit this post and add a poll so we can get the ball rolling.  Which ever feature request garners the most interest will get the most financial support, thereby becoming the first project. I would do a poll myself, but only you know how much work each project would entail and which ones could be grouped together to achieve the 20hrs. just a question.