Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - pga57

Pages: 1 ... 5 6 [7] 8 9
91
Humm... I've look at the Xorg.0.log and I think it is not those errors that cause my black screen:

dcerouter_1001027:~# cat /usr/pluto/diskless/72/var/log/Xorg.0.log | grep '(EE)'
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed

What is the "NewInputDeviceRequest" ?

I have the same error on other MDs and they work very well.
I think the problem come after the X start.
On the screen I have for a few millisecond the orbiter creation screen (I suppose it because it is really quick) and it go away and nothing else.
When I click on the mouse, same things. It come for a few millisecond and go away.

It is very strange.

So do you have another suggestion I can look for ?

Philippe




 
Philippe

92
Hi,

I need some help to resolve black screens on 2 of my 6 MDs.
One with a nividia 6200LE video card (TV connected) and the other with an onboard 7100 nvidia (VGA connected).
The AVwizard steep worked with no problem.
I have the black screen (with white cursor) before Sarah and the location configuration.

I've look at all the msgs and wiki articles but don't find the solution.
The 2 MDs worked with Lmce 710.

I have regenerate the orbiters, modify the xorg.conf, switch the xorg.conf with another MD that work, rebuild the MD image, add the 810 updates, downgrade the nvidia driver, etc...
I don't find :-(
 
How can I resolve this ?

Thank's !
Philippe


93
Users / Re: beta update the MDs?
« on: August 14, 2009, 10:45:16 am »
Hi,

I've not the /etc/apt/apt.conf.d/02proxy on the core or MD's (installed from alpha 2.28).
May I create it with a touch command or is there something else to do ?


Thanl's.
Philippe

94
Users / 810 alpha2 and motion wrapper
« on: July 31, 2009, 09:40:45 am »
Hello All,

What does a reload router exactly?
I ask this because I have a problem with motion wrapper on LMCE 810 alpha 2.24 and upgrade to 2.26.
I has a PV-149 - 4 port video capture card with 2 analog cameras.
Everything was working perfectly with LMCE 710 for over a year.
Since the update I've done mid-July, motion wrapper stops acquiring data from one camera randomsly (not allways the same).
I only had to reload the router to retrive the missing camera.
This happens about once a day.

How to determine the problem?
I don't understand what information the log gives me:

Code: [Select]
========== NEW LOG SECTION ==========
1 07/30/09 07:18:46 45 (spawning-device) Starting... 1
1 07/30/09 07:18:46 45 (spawning-device) Found /usr/pluto/bin/Motion_Wrapper
05 07/30/09 7:18:47.070 Connect() failed, Error Code 111 (Connection refused)) <0xb79b26c0>
05 07/30/09 7:18:48.071 Connect() failed, Error Code 111 (Connection refused)) <0xb79b26c0>
05 07/30/09 7:18:49.070 Connect() failed, Error Code 111 (Connection refused)) <0xb79b26c0>
05 07/30/09 7:18:52.179 Creating child 46 <0xb79b26c0>
05 07/30/09 7:18:52.179 Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb79b26c0>
05 07/30/09 7:18:52.179 Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb79b26c0>
05 07/30/09 7:18:52.179 Creating child 47 <0xb79b26c0>
05 07/30/09 7:18:52.179 Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb79b26c0>
05 07/30/09 7:18:52.179 Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb79b26c0>
05 07/30/09 8:24:13.351 Going to rotate logs... <0xb71b0b90>
05 07/30/09 8:41:33.592 Going to rotate logs... <0xb71b0b90>
05 07/31/09 8:03:17.283 Going to rotate logs... <0xb71b0b90>
05 07/31/09 8:10:29.777 Going to rotate logs... <0xb71b0b90>
05 07/31/09 8:42:50.515 Got a reload command from 0  <0xb71b0b90>
05 07/31/09 8:42:50.854 void ClientSocket::Disconnect() on this socket: 0x8083fa0 (m_Socket: 7) <0xb79b26c0>
Return code: 2
2 07/31/09 08:42:50 45 (spawning-device) Device requests restart... count=1/50 dev=45
Fri Jul 31 08:42:50 CEST 2009 Restart
========== NEW LOG SECTION ==========
1 07/31/09 08:42:58 45 (spawning-device) Starting... 1
1 07/31/09 08:42:58 45 (spawning-device) Found /usr/pluto/bin/Motion_Wrapper
05 07/31/09 8:42:59.904 Connect() failed, Error Code 111 (Connection refused)) <0xb79a36c0>
05 07/31/09 8:43:00.904 Connect() failed, Error Code 111 (Connection refused)) <0xb79a36c0>
05 07/31/09 8:43:01.904 Connect() failed, Error Code 111 (Connection refused)) <0xb79a36c0>
05 07/31/09 8:43:03.999 Creating child 46 <0xb79a36c0>
05 07/31/09 8:43:03.999 Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb79a36c0>
05 07/31/09 8:43:04.000 Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb79a36c0>
05 07/31/09 8:43:04.000 Creating child 47 <0xb79a36c0>
05 07/31/09 8:43:04.000 Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb79a36c0>
05 07/31/09 8:43:04.000 Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb79a36c0>

Philippe

95
Users / Re: Shoutcast Plugin
« on: July 27, 2009, 06:30:15 pm »
and I deselect all other sources besides shoutcast....

96
Users / Re: Shoutcast Plugin
« on: July 27, 2009, 06:14:16 pm »
Humm... I have now the genres displayed on the webdt but still nothing on the N810. :-(
Very strange.

Best regards,
Philippe

97
Users / Re: Shoutcast Plugin
« on: July 24, 2009, 02:03:17 pm »
Hello Sambuca,

Is there a reason why the station genre are note displayed on an (external) orbiter ?
I try it on a N810 and a Webdt366 and it give me nothing when I select the shoutcast option (UI1)
It work with the orbiter from the PC media director.

Philippe


98
Users / Re: New Z-Wave driver
« on: June 09, 2009, 06:54:41 pm »
The StatusReport command works, but ZWave worked again this after-noon without intervention.
I thought the reset would be automatic with this new driver.
I did not translate correctly your exchanges.

Thank you for these details

Philippe

99
Users / Re: New Z-Wave driver
« on: June 09, 2009, 07:24:57 am »
Hello Hari,

For me, the lastest ZWave driver (ZWave-0710-32bit-20090605.bz2) don't resolve the error I have    
after a few days of proper functioning.
The Seluxit viaSENS Homecontroller give me the same problem I have with my previous Tricklestar 300ZW-EU-W and ZWave-0.0.2-0710-32bit.bz2 driver.

36   06/09/09 7:12:43.254      ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb792fb90>
36   06/09/09 7:12:46.353      No callback received: await_callback: 141 timer: 31 <0xb792fb90>
36   06/09/09 7:12:46.353      ERROR: Dropping command, no callback received after three resends <0xb792fb90>
36   06/09/09 7:13:16.461      We have been idle for 30 seconds, polling device states <0xb792fb90>

Do I set all associations    again?

Philippe

100
Users / Re: New Z-Wave driver
« on: June 07, 2009, 09:03:17 pm »
Hi Philippe,

It is not a tar archive. All you need is to bunzip it (command is bunzip2 if I remember correctly).

Good luck,
Mark

[/quote]

Hi Mark,
I thought there was a problem because the input file did not have the same name as the previous version (ZWave-0710-32bit-20090605 instead ZWave).
So, I've use bunzip2 and have install this new version on my core.
I'll see if that corrects the problems that I described
previously (April 15)

Thank's for your help !
Philippe


101
Users / Re: New Z-Wave driver
« on: June 07, 2009, 07:18:50 pm »
http://vt100.at/files/ZWave-0710-32bit-20090605.bz2

br, Hari

Hello Hari,

I have those errors when extracting the archive:

linuxmce@dcerouter:~$ sudo tar jxvf ZWave-0710-32bit-20090605.bz2
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Error exit delayed from previous errors

I have made a lot of downloads with the same result :-(
Is the file ok on your side ?

Philippe

102
Users / Re: Setting up Siemens Gigaset IP
« on: May 22, 2009, 05:38:41 pm »
It's ok !
I can now consult my voicemail with the gigaset S675IP.
I had to check "RFC 2833" in the advanced phone parameters.

Philippe

 

103
Users / Re: Setting up Siemens Gigaset IP
« on: May 22, 2009, 03:29:23 pm »
Hi,

I've just finished to setup my gigaset S675IP phone with mce710.
It work but I can't access to my voicemail.
When asterisk ask me for the mailbox number and password it does not recognize them.
I've not this problem with the cisco 7970.
Is there something to be done to resolve this ?


Thank's
Philippe

104
Users / Re: New Z-Wave driver
« on: April 17, 2009, 08:43:44 am »
Strange...this morning my shutters were reopened without changing my config and I can control my lights again.
It appears that the system work after a while.
The Zwave log seems ok.

Philippe


105
Users / Re: New Z-Wave driver
« on: April 16, 2009, 06:59:02 am »
My remote controleur is a Tricklestar 200ZW-EU-W and the stick is a Tricklestar 300ZW-EU-W.
I use the SIS mode I've find in the Zwave wiki.
It worked for about 1 month (with 1 shutter only) without problem.

I think like you that the stick has a defect.
I've order another one (Seluxit now) to verify

Best regards,
Philippe


Pages: 1 ... 5 6 [7] 8 9