I have the onboard 'integrated' video plus Nvidia Optimus on my
laptop... think I'll try switching to integrated only in the BIOS and
see if that helps.
On 04/12/2013 07:13 AM, Kristian Erik Hermansen wrote:
> Does everyone here have TWO or more graphics chips on their hardware?
> That's the problem I have. Think it may be the root cause.
> On Apr 12, 2013 9:55 AM, "Vreixo Formoso" <email address hidden> wrote:
>
>> I have the same problem with no ATI card but NVIDIA:
>>
>> lspci |grep VGA
>> 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
>> processor Graphics Controller (rev 09)
>> 01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT
>> 650M] (rev a1)
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1163512).
>> https://bugs.launchpad.net/bugs/1167114
>>
>> Title:
>> Ubuntu Kernel 3.5.0-27 does not boot
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167114/+subscriptions
>>
I have the onboard 'integrated' video plus Nvidia Optimus on my
laptop... think I'll try switching to integrated only in the BIOS and
see if that helps.
On 04/12/2013 07:13 AM, Kristian Erik Hermansen wrote: /bugs.launchpad .net/bugs/ 1167114 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1167114/ +subscriptions
> Does everyone here have TWO or more graphics chips on their hardware?
> That's the problem I have. Think it may be the root cause.
> On Apr 12, 2013 9:55 AM, "Vreixo Formoso" <email address hidden> wrote:
>
>> I have the same problem with no ATI card but NVIDIA:
>>
>> lspci |grep VGA
>> 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
>> processor Graphics Controller (rev 09)
>> 01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT
>> 650M] (rev a1)
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1163512).
>> https:/
>>
>> Title:
>> Ubuntu Kernel 3.5.0-27 does not boot
>>
>> To manage notifications about this bug go to:
>> https:/
>>