sony-vaio-z-series team mailing list archive

[Rob Mukai <dothedog2010@xxxxxxxxx>]

Ok, so I kinda got compiz working with the PMD. But now I can't get it
working with the intel card on the normal laptop screen. I am using the
same xorg.conf that Gyhor noted above. I did try with a xinerama section
but that made it almost unusable although I did get two x screens, one on
the external monitor attached to the pmd and one on the laptop. As an FYI
here is what my xorg.conf looks like:

Section "Device"
    Identifier "radeon"
    Driver "radeon"
    BusID "PCI:22:00:0"
EndSection

Section "Device"
    Identifier "intel"
    Driver "intel"
    BusID "PCI:00:02:0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "radeon"
EndSection

Section "Screen"
    Identifier "Screen1"
    Device "intel"
EndSection

#Section "ServerLayout"
#    Identifier "DualHead"
#    Screen "Screen0"
#    Screen "Screen0" RightOf "Screen1"
#    Option "Xinerama" "On"
#EndSection

If you uncomment the bottom section you do get both screens working with an
X session. But with the issues I noted above. Anybody get compiz working
with both the PMD and the sandy bridge intel graphics card?

Rob

On Sun, Sep 2, 2012 at 11:13 AM, Rob Mukai <dothedog2010@xxxxxxxxx> wrote:

> Another quick note. Compiz kinda works through the PMD. I don't get the
> unity launcher or top bar but I do get the desktop cube.
>
> Rob
>
>
> On Sun, Sep 2, 2012 at 10:29 AM, Rob Mukai <dothedog2010@xxxxxxxxx> wrote:
>
>> Ok, I have discovered another issue. not sure when this popped up. But
>> compiz now doesn't work. I can only use "Ubuntu 2D". Trying "compiz
>> --replace" causes all kinds of issues. Now I also have another issue that
>> may be related. I cannot change anything in the ccsm
>> (CompizConfig-Settings-Manager). I can't check or uncheck any options. If I
>> run it as root "sudo ccsm" I can change stuff but nothing changes. Not sure
>> if they are related.
>>
>> As a side note. I have just compiled 3.6.0-rc4 and it appears that the
>> power problem is fixed-ish (running in the 15-17w range. Not great but a
>> lot better than the 30w range it was before). It also appears that the
>> fuser problem is fixed as well (ntfs read write is working). So no need for
>> patches at this point.
>>
>> qcserial still doesn't work though. Interestingly, my Gobi 3000 card is
>> actually a  Huawei and qcserial seems to call it a Qualcomm. Not sure if
>> that makes any difference but seems weird.
>>
>> Rob
>>
>> On Sat, Sep 1, 2012 at 3:54 PM, Rob Mukai <dothedog2010@xxxxxxxxx> wrote:
>>
>>> Forgot to copy the list;
>>>
>>>
>>>
>>>
>>>> Vick,
>>>> Thanks for the response. Yes, I can modprobe qcserial without compiling
>>>> a new module, however, none of the ttyUSB devices seem to work. By the way
>>>> the ttyUSB0, ttyUSB1, ttyUSB2, and ttyUSB3, are created at boot without the
>>>> qcserial module loaded. Also, it looks like
>>>>
>>>> usb_wwan               19863  1 option
>>>> usbserial              42302  2 option,usb_wwan
>>>>
>>>> are loaded as well.
>>>>
>>>> dmesg output from modprobe qcserial
>>>> [  893.577556] usbcore: registered new interface driver qcserial
>>>> [  893.577574] USB Serial support registered for Qualcomm USB modem
>>>>
>>>> sony-laptop is also loaded. Not sure what you mean by "device is on via
>>>> the rfkill interface".
>>>>
>>>> Here is the output of rfkill list
>>>> sudo rfkill list
>>>>
>>>> 0: sony-wifi: Wireless LAN
>>>> Soft blocked: no
>>>>  Hard blocked: no
>>>> 1: sony-bluetooth: Bluetooth
>>>> Soft blocked: no
>>>> Hard blocked: no
>>>> 2: sony-wwan: Wireless WAN
>>>> Soft blocked: no
>>>> Hard blocked: no
>>>> 3: hci0: Bluetooth
>>>>  Soft blocked: no
>>>> Hard blocked: no
>>>> 4: phy0: Wireless LAN
>>>> Soft blocked: no
>>>>  Hard blocked: no
>>>>
>>>> Rob
>>>>
>>>> On Fri, Aug 31, 2012 at 7:18 PM, vick <weasalandme@xxxxxxxxx> wrote:
>>>>
>>>>>
>>>>> >________________________________
>>>>> >
>>>>> >I tried compiling the qcserial module but it pukes
>>>>> >
>>>>>
>>>>>
>>>>> There should be no need to compile qcserial, the device ID made it in
>>>>> the kernel in 3.4. I actually had to blacklist it because network manager
>>>>> was connecting via the serial device and I wanted to use the direct usb
>>>>> interface for the gobi card. Just do sudo modprobe qcserial and see if
>>>>> something shows in dmesg and if you get any ttyUSB devices. Also make sure
>>>>> you have the sony-laptop module installed and the device is on via the
>>>>> rfkill interface.
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~sony-vaio-z-series
>>>>> Post to     : sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~sony-vaio-z-series
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>
>>>>
>>>
>>
>