Messages

The asound.conf that worked before the new audio sheme:

http://pastebin.com/v1NAqujj

For information I have 2 sound cards and only use the M Audio for squeezeslave on the core.
I don't have a media director on the core.

The new asound.conf after the new audio sheme.

http://pastebin.com/SP48tBdt

Humm... I'm not sure but I think that squeezeslave is broken with the new scheme.
Mine don't work anymore.

I've lost my core virtual card config and if I replace the new generated asound.conf with a backup I have, squeezeslave miss the -o parameter:

Code Select Expand


linuxmce  7953  0.0  0.0   3344   840 pts/11   S+   16:51   0:00 grep --color=auto squeezeslave
root     15039  9.0  0.2  60812  6844 ?        Ssl  16:27   2:10 /usr/bin/squeezeslave -m00:00:00:00:00:01 -r5 -M/var/log/squeezeslave.log localhost
root     16223  9.1  0.2  60944  6728 ?        Ssl  16:27   2:10 /usr/bin/squeezeslave -m00:00:00:00:00:02 -r5 -M/var/log/squeezeslave.log localhost
root     16781  0.6  0.2  59920  6816 ?        Ssl  16:27   0:08 /usr/bin/squeezeslave -m00:00:00:00:00:03 -r5 -M/var/log/squeezeslave.log localhost



February is approaching and I hope that Posde can go to the Linux Expo.
So I've made ​​a second donation and have doubling my first amount! ;-)

Thank's to all the team for the work you do.

Philippe

No I confirm Thom that this command does not work on this Shuttle all-in-one computer.
The screen will turn off and on immediately (UI1) or goes into Flickr screen saver (UI2).

The only command that work is the "/usr/sbin/vbetool dmps off".

I have the crontab solution but I want a little more interactivity.
A key on the keyboard, screen or remote control would be more appropriate to turn off/on this screen.

Philippe

Hello Posde,

I had translated filebinning by sending the file to a service and did not try to do otherwise.
(Having an account on oron I did not see that it was less evident for non-registered)

So I start with pastbin!

http://pastebin.com/dM6069xH

Philippe

Merry Christmas to all!

I found a command that allows me to remotely turn off the screen: "vbetool dpms off".
But I do not know how to combine it to a touch of the screen and then re activate the screen with "vbetool dpms on" because the screen and touchscreen are no longer active!
Does anyone have a suggestion?

New xorg.conf download link: http://oron.com/yl3m4yu540k4

Philippe

Sorry for the side question but does the touchscreen work properly?

It works but the screens of the orbit (UI1) do not all use the maximum size of the Shuttle screen and it sometimes generates unintended actions.
And UI2 is not easy to use with fingers.

Ho... maybe this service is not avalaible for other countrys. Sorry.
Can you give me a filebin url to use ?
I'm not familiar with those...

You can download it here:

http://dl.free.fr/vttG8eWAf

Philippe

Coukd you update the wiki if necessary? Because I never got resolution properly working.

Yes I will do that but I still have to translate the notes I took during the complete Shuttle configuration. ;-)

For the resolution I have put a modeline in xorg.conf:

Section "Monitor"
   Identifier   "Monitor0"
   VendorName   "Unknown Monitor Vendor"
   ModelName   "Unknown Monitor Model"
   Option          "DPMS"
   # 1368x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 85.86 MHz
      
   Modeline    "1360x768"      84.50  1360 1392 1712 1744    768  783  791  807
   HorizSync   20-500
   VertRefresh   59-61
EndSection

And modify the Display subsection of "Screen" in xorg.conf:

Section "Screen"
   Identifier   "Screen0"
   Device      "Card0"
   Monitor      "Monitor0"
   DefaultDepth   24
   SubSection "Display"
      Modes      "1366x768"
      Virtual      1366 768
   EndSubSection
................

After that you have to report the same resolution for the Shuttle orbiter in lcme-admin.

Greetings,

Philippe

Hi,

After hassle to set up my "Shuttle X50V2 Plus" as MD (network adapter problem, screen resolution, etc. ..), it now works (thanks for the information found on the wiki).

But is there a reason why "DPMS monitor" does not work properly, knowing that this MD has an Intel video card (lmce 10.04)?
The screen turns off and comes back right away.

I know that Intel card is currently not recommended but that Shuttle seems perfect for integrating my kitchen! ;-)
And I think it's the only way to turn off the screen when I do not use it.

Greetings,

Philippe

Hello Hari,

After insert the 10 and 36 level code in pluto.conf, I have done some tests:

Turn light on/of work without problems:

Code Select Expand


10 11/22/11 19:11:06.839 Received MESSAGE 67             0x8e7ba20 device: 74 <0xb59e6b70>
10 11/22/11 19:11:06.839 Received Message type 1 ID 193 from 0 to 79 (device: 74) resp 0 <0xb59e6b70>
36 11/22/11 19:11:06.839 Received command for child <0xb59e6b70>
36 11/22/11 19:11:06.839 OFF RECEIVED FOR CHILD 3 <0xb59e6b70>
10 11/22/11 19:11:10.638 Received MESSAGE 67             0x8e7ba20 device: 74 <0xb59e6b70>
10 11/22/11 19:11:10.638 Received Message type 1 ID 192 from 0 to 79 (device: 74) resp 0 <0xb59e6b70>
36 11/22/11 19:11:10.638 Received command for child <0xb59e6b70>
36 11/22/11 19:11:10.638 ON RECEIVED FOR CHILD 3/0 <0xb59e6b70>


Open the shutter do nothing !

Code Select Expand


10 11/22/11 19:12:06.998 Received MESSAGE 67             0x8e7ba20 device: 74 <0xb59e6b70>
10 11/22/11 19:12:06.998 Received Message type 1 ID 193 from 0 to 85 (device: 74) resp 0 <0xb59e6b70>
36 11/22/11 19:12:06.998 Received command for child <0xb59e6b70>
36 11/22/11 19:12:06.998 OFF RECEIVED FOR CHILD 9 <0xb59e6b70>


But close the same shutter allready close, open it !!!

Code Select Expand


36 11/22/11 19:14:13.812 COMMAND_CLASS_BASIC -  <0xb6de8b70>
36 11/22/11 19:14:13.812 Got basic report from node 7, value: 0 <0xb6de8b70>
10 11/22/11 19:14:15.863 Received MESSAGE 67             0x8e7ba20 device: 74 <0xb59e6b70>
10 11/22/11 19:14:15.863 Received Message type 1 ID 192 from 0 to 85 (device: 74) resp 0 <0xb59e6b70>
36 11/22/11 19:14:15.863 Received command for child <0xb59e6b70>
36 11/22/11 19:14:15.863 ON RECEIVED FOR CHILD 9/0 <0xb59e6b70>


It seems that the controls are reversed in the Wizard Lights and probably elsewhere.
But I still had to use a "Send to this device the command - Status Report" because as a point the zwave give me error in logs :

Code Select Expand


05 11/22/11 19:03:21.016 No callback received: await_callback: 122 timer: 31 <0xb6de8b70>
01 11/22/11 19:03:21.016 ERROR: Dropping command, no callback received after three resends <0xb6de8b70>
05 11/22/11 19:03:21.124 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
05 11/22/11 19:03:24.336 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
05 11/22/11 19:03:27.549 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
01 11/22/11 19:03:30.653 ERROR: Dropping command, no callback received after three resends <0xb6de8b70>
05 11/22/11 19:04:00.896 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
05 11/22/11 19:04:04.108 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
05 11/22/11 19:04:07.320 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
01 11/22/11 19:04:10.424 ERROR: Dropping command, no callback received after three resends <0xb6de8b70>
05 11/22/11 19:04:10.532 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
05 11/22/11 19:04:16.961 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
01 11/22/11 19:04:20.065 ERROR: Dropping command, no callback received after three resends <0xb6de8b70>
05 11/22/11 19:04:20.173 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
05 11/22/11 19:04:23.384 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
05 11/22/11 19:04:26.596 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb6de8b70>
01


The schedules do not follow but that's normal because I have redone tests for reporting the problems I have.

This suggests that it is not too serious but enough to make the programming of event does not produce the desired effect (close or open my shutters). ;-)
But I confirm that without the use sometime the "Status Report" command, the system stops responding.

Notify me when this is corrected, I will test again

Greetings,

Philippe

Hello Hari,

I rejoice too quickly because there is still a problem with my last Zwave setup.
I have done a new 1004 install yesterday (to have a clean install) and I encountered the following problems:

My Seluxit viaSENS Homecontroller was not detected when configuring the core.
I had to install the pluto-zwave deb and because it was not sufficient, had to create a child zwave device before the controleur be detected.

The lamp plugins works but my 4 drape switchs not.
There are present but doen't respond when I want to open or close them.
I have those errors in the 74_zwave.log

Code Select Expand


05 11/20/11 16:35:22.549 ZWave::InternalIDToDevice() No device found for id 7/2 <0xb6cf2b70>
05 11/20/11 16:37:29.547 No callback received: await_callback: 218 timer: 31 <0xb6cf2b70>
05 11/20/11 16:37:29.710 ZWave::InternalIDToDevice() No device found for id 9/2 <0xb6cf2b70>
05 11/20/11 16:37:31.152 ZWave::InternalIDToDevice() No device found for id 7/2 <0xb6cf2b70>
05 11/20/11 16:47:27.069 No callback received: await_callback: 20 timer: 31 <0xb6cf2b70>
05 11/20/11 16:47:27.645 ZWave::InternalIDToDevice() No device found for id 9/2 <0xb6cf2b70>
05 11/20/11 16:47:27.729 ZWave::InternalIDToDevice() No device found for id 7/2 <0xb6cf2b70>
05 11/20/11 16:47:27.861 ZWave::InternalIDToDevice() No device found for id 8/2 <0xb6cf2b70>
05 11/20/11 16:51:41.192 No callback received: await_callback: 44 timer: 31 <0xb6cf2b70>
05 11/20/11 16:51:41.724 ZWave::InternalIDToDevice() No device found for id 9/2 <0xb6cf2b70>
05 11/20/11 16:51:42.444 ZWave::InternalIDToDevice() No device found for id 6/2 <0xb6cf2b70>
05 11/20/11 16:51:42.704 ZWave::InternalIDToDevice() No device found for id 7/2 <0xb6cf2b70>


Have you an idea of ​​what is happening ?

Greetings,
Philippe

Ok, it will be done.