sony-vaio-z-series team mailing list archive
-
sony-vaio-z-series team
-
Mailing list archive
-
Message #01652
Re: Ubuntu Natty Kernel .debs
Hi Adam,
Nope I am still trying things with Jesse.
It is a regression and now filed as:
https://bugs.freedesktop.org/show_bug.cgi?id=30877
>
> I guess that the question has to be whether the problem you have
happened
> before the fix for resume - if so then I'm probably fairly safe
updating, but
> if not then I probably shouldn't....
The flickering is (if I remember it correctly) independent of the resume
stuff (flickering was already there before Jesse started adding the
resume commits).
>
> Ok, though have you got to the bottom of your flicker issues yet? I'm not
> seeing them on my kernel but of course it could be the combination of X driver
> etc that is causing it for you - but what I don't want to do is update the
> kernel with that commit and find that the flickering problem happens :(.
Hehe. Then maybe wait :)
An EASY test for the flickering: Change to console (e.g. tty1) and
change back to X. If you (shortly) see a BLACK screen with white random
patterns - mostly thing lines - then you are already "infected" ;)
Knuth
>
> Adam.
>
>
>> Cheers,
>>
>> Knuth
>>
>> ---
>>
>> On 10/14/2010 12:21 PM, Adam Hill wrote:
>>>> However: resume from suspend mostly does not work (leaves the screen
>>>> black).
>>>>
>>> I would guess that means that more changes are required to make this
>>>
>>> work. The problem here is that the kernel which Jesse from Intel has that
>>> seems to work when resumed is a little different to this one. When I get
>>> a chance I'll have another look to see if I can work out what is needed.
>>>
>>> Adam.
>>>
>>>> I am about to try Ubuntu 10.10 next with this kernel (2.6.36).
>>>>
>>>> Philippe
>>>>
>>>>> The problem is not with the kernel but with the NVidia and Nouveau
>>>>>
>>>>> drivers ( or at least that is how it appears. ) The problem is that in
>>>>> both modes, both cards appear on the bus, and at boot time the BIOS
>>>>> sets up the Intel card REGARDLESS of the mode ( well, without booting
>>>>> the old kernel or setting static switching using the BIOS hack. ) So,
>>>>> when the NVidia driver tries to load, it assumes that it already has
>>>>> its resources mapped but in fact it doesn't - only the Intel card has
>>>>> been mapped in. So, you STILL have to boot the old kernel to use the
>>>>> NVidia card so that the Intel one is completely disabled and not
>>>>> mapped at boot time.
>>>>>
>>>>>>> glxinfo | grep ender
>>>>>>
>>>>>> This does not work, since I have no working glx module ("extension GLX
>>>>>> missing").
>>>>>>
>>>>> I think that the issue here may be that the NVidia driver also has
> its
>>>>>
>>>>> own mesa/glx libraries. I think that to get GLX working with Intel you
>>>>> will have to re-install the Ubuntu ones, and then again to get the
>>>>> NVidia working install the NVidia ones again. In my files directory is
>>>>> an rc.local file which in theory could be re-written to copy the
>>>>> appropriate files when needed... it should be fairly easy to do but
>>>>> unfortunately I don't have the time at the mo... if I get some time in
>>>>> the near future I'll give it a go.
>>>>>
>>>>>>> That would seem a little odd if you say you get the desktop - the
>>>>>>> desktop
>>>>>>>
>>>>>>> would seem to constitute a "screen" ! For speed mode you should not
>>>>>>> need an xorg.conf file at all - if you have one move it out of the
>>>>>>> way.
>>>>>>
>>>>>> There must be something wrong with my system configuration. I just
>>>>>> started in Speed mode a few times. X loads the i915 driver (lsmod
>>>>>> shows i915 loaded), although I blacklisted that, my xorg.conf
>>>>>> specifies "nvidia". X also tries to load the NVIDIA glx module.
>>>>>> Excerpt from my
>>>>>>
>>>>>> Xorg.0.log in Speed mode:
>>>>> As above, in "speed" mode both the Intel and NVidia cards are active.
>>>>> The
>>>>>
>>>>> NVidia driver needs to realise that! Also, in theory we should probably
>>>>> patch the i915 driver to not load in speed mode, but this would be a
>>>>> very Vaio-Z specific patch unless it could be fitted in with the vga
>>>>> switcheroo code.
>>>>>
>>>>>> I can currently only use my Z11 without problems if I boot the
>>>>>> 2.6.31-20 kernel with the NVIDIA proprietary drivers and an xorg.conf
>>>>>> that specifies to use the nvidia driver.
>>>>>>
>>>>> It should also work if you boot my 2.6.28 kernel which reboots ( then
>>>>>
>>>>> select the 2.6.36-0-vaioz one. )
>>>>>
>>>>> I'm sure that one day this will all "just work" :(.
>>>>>
>>>>> Adam
>>>>>
>>>>>> I hope this helpt in making the kernel work for everybody.
>>>>>> I'd gladly do some more testing.
>>>>>>
>>>>>> Philippe
>>>
>>> _______________________________________________
>>> 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
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
References