Bug#815888: nvidia-detect: GF119M [GeForce 610M] nvidia-detect=ok for nvidia-driver . . . not ok
Fulano Diego Perez
fulanoperez at cryptolab.net
Thu Mar 10 13:01:35 UTC 2016
Luca Boccassi:
> On Mar 9, 2016 14:29, "Fulano Diego Perez" <fulanoperez at cryptolab.net>
> wrote:
>>
>>
>>
>> Luca Boccassi:
>>> On 9 March 2016 at 13:42, Fulano Diego Perez <fulanoperez at cryptolab.net>
> wrote:
>>>>
>>>>
>>>> Luca Boccassi:
>>>>> On 9 March 2016 at 11:49, Fulano Diego Perez <
> fulanoperez at cryptolab.net> wrote:
>>>>>> hi luca,
>>>>>>
>>>>>> Luca Boccassi:
>>>>>>> On 9 March 2016 at 10:05, Fulano Diego Perez <
> fulanoperez at cryptolab.net> wrote:
>>>>>>>> hi luca
>>>>>>>>
>>>>>>>> Luca Boccassi:
>>>>>>>>> Control: package -1 nvidia-driver
>>>>>>>>> Control: tag -1 moreinfo
>>>>>>>>> Control: severity -1 normal
>>>>>>>>>
>>>>>>>>> On Thu, 2016-02-25 at 23:34 +1100, Fulano Diego Perez wrote:
>>>>>>>>>> Package: nvidia-detect
>>>>>>>>>> Severity: grave
>>>>>>>>>> Justification: renders package unusable
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _disclaimer_
>>>>>>>>>>
>>>>>>>>>> 1.
>>>>>>>>>> i do not know if the problem lies with nvidia-detect,
> nvidia-driver and its
>>>>>>>>>> dependencies, or neither
>>>>>>>>>>
>>>>>>>>>> 2.
>>>>>>>>>> this bug report was submitted after removal and revert back to
> nouveau
>>>>>>>>>>
>>>>>>>>>> 3.
>>>>>>>>>> applies to intel ivy bridge chipset with built-in intel graphics
> +
>>>>>>>>>> nvidia below
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> nvidia-detect recommends nvidia-driver
>>>>>>>>>>
>>>>>>>>>> i then install nvidia-driver, its dependencies and nvidia-xconfig
>>>>>>>>>>
>>>>>>>>>> NB i attempted this ~6 months ago and yesterday, i do not know
> the affect of
>>>>>>>>>> the recent nvidia updates to xserver and whether nvidia-xconfig
> is still
>>>>>>>>>> necessary
>>>>>>>>>>
>>>>>>>>>> gdm3 cannot proceed after reboot
>>>>>>>>>>
>>>>>>>>>> please advise any further log provision where necessary:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> It looks like you have a laptop with a switchable Optimus system
> (610M).
>>>>>>>>> If that's indeed the case, you cannot just install the nvidia
> stack, as
>>>>>>>>> your hardware is wired to use the Intel card to drive the display.
>>>>>>>>>
>>>>>>>>> If you want to use the discrete Nvidia card, you must do so
> through
>>>>>>>>> bumblebee. Please install
>>>>>>>>>
>>>>>>>>> bumblebee-nvidia
>>>>>>>>>
>>>>>>>>> Then run:
>>>>>>>>>
>>>>>>>>> sudo update-glx --config glx
>>>>>>>>>
>>>>>>>>> And make sure nvidia/bumblebee is selected, if not pick it.
>>>>>>>>
>>>>>>>> done above
>>>>>>>>
>>>>>>>>>
>>>>>>>>> If the problem persists, please add more information by running:
>>>>>>>>>
>>>>>>>>> reportbug -N 815888
>>>>>>>>
>>>>>>>> sorry, this is out ATM, nevertheless...
>>>>>>>>
>>>>>>>>> Kind regards,
>>>>>>>>> Luca Boccassi
>>>>>>>>
>>>>>>>> i get the following:
>>>>>>>>
>>>>>>>> $ primusrun glxgears
>>>>>>>> primus: fatal: Bumblebee daemon reported: error: [XORG] (EE)
>>>>>>>>
>>>>>>>> $ optirun glxgears
>>>>>>>> [23162.070642] [ERROR]Cannot access secondary GPU - error: [XORG]
> (EE)
>>>>>>>>
>>>>>>>> ive tried various basic amendments such as
>>>>>>>>
>>>>>>>> adding my user to the bumblebee group;
>>>>>>>>
>>>>>>>> manually specifying the nvidia option in
> /etc/bumblebee/bumblebee.conf;
>>>>>>>>
>>>>>>>> manually specifying BusID "PCI:1:0:0" in
> /etc/bumblebee/xorg.conf.nvidia
>>>>>>>> (from the github FAQ)
>>>>>>>>
>>>>>>>> $ lspci | egrep 'VGA|3D'
>>>>>>>> 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
>>>>>>>> processor Graphics Controller (rev 09)
>>>>>>>> 01:00.0 VGA compatible controller: NVIDIA Corporation GF119M
> [GeForce
>>>>>>>> 610M] (rev a1)
>>>>>>>>
>>>>>>>> i admit im stuck
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Sorry for your troubles.
>>>>>>>
>>>>>>> Unfortunately there's not much I can do without looking at the full
>>>>>>> system report. If reportbug -N is not working for you, could you
>>>>>>> please manually attach the output of:
>>>>>>
>>>>>> sure makes sense
>>>>>>
>>>>>>> reportbug --template nvidia-driver
>>>>>>
>>>>>> i enclose
>>>>>>
>>>>>> thanks for your help
>>>>>
>>>>> Hi,
>>>>>
>>>>> >From the log, it looks like nouveau is being loaded:
>>>>>
>>>>> 2367.838] (II) LoadModule: "nouveau"
>>>>> [ 2367.838] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
>>>>> [ 2367.838] (II) Module nouveau: vendor="X.Org Foundation"
>>>>> [ 2367.838] compiled for 1.18.0, module version = 1.0.12
>>>>> [ 2367.838] Module class: X.Org Video Driver
>>>>> [ 2367.838] ABI class: X.Org Video Driver, version 20.0
>>>>>
>>>>> <cut>
>>>>>
>>>>> [ 2367.839] (II) NOUVEAU driver Date: Tue Dec 8 15:52:25 2015 +1000
>>>>> [ 2367.839] (II) NOUVEAU driver for NVIDIA chipset families :
>>>>> [ 2367.839] RIVA TNT (NV04)
>>>>> [ 2367.839] RIVA TNT2 (NV05)
>>>>> [ 2367.840] GeForce 256 (NV10)
>>>>> [ 2367.840] GeForce 2 (NV11, NV15)
>>>>> [ 2367.840] GeForce 4MX (NV17, NV18)
>>>>> [ 2367.840] GeForce 3 (NV20)
>>>>> [ 2367.840] GeForce 4Ti (NV25, NV28)
>>>>> [ 2367.840] GeForce FX (NV3x)
>>>>> [ 2367.840] GeForce 6 (NV4x)
>>>>> [ 2367.840] GeForce 7 (G7x)
>>>>> [ 2367.840] GeForce 8 (G8x)
>>>>> [ 2367.840] GeForce GTX 200 (NVA0)
>>>>> [ 2367.840] GeForce GTX 400 (NVC0)
>>>>>
>>>>>
>>>>> Even though the module is blacklisted.
>>>>>
>>>>> Have you rebooted after installing the nvidia stuff?
>>>>
>>>> yes, actually ive only come back to this after about 2 weeks
>>>>
>>>>>
>>>>> To make sure the module configs are parsed and up to date, please run:
>>>>>
>>>>> sudo depmod
>>>>> sudo update-initramfs -u
>>>>
>>>> yep
>>>>
>>>>>
>>>>> and then reboot and try again.
>>>>
>>>> ok, i rebooted
>>>>
>>>> seems not to work again:
>>>>
>>>> $ primusrun glxgears
>>>> primus: fatal: Bumblebee daemon reported: error: [XORG] (EE)
>>>>
>>>> $ optirun glxgears
>>>> [ 169.135208] [ERROR]Cannot access secondary GPU - error: [XORG] (EE)
>>>>
>>>> [ 169.135306] [WARN]The Bumblebee server was not available.
>>>> Running synchronized to the vertical refresh. The framerate should be
>>>> approximately the same as the monitor refresh rate.
>>>> 458 frames in 5.0 seconds = 91.477 FPS
>>>> 302 frames in 5.0 seconds = 60.301 FPS
>>>> XIO: fatal IO error 11 (Resource temporarily unavailable) on X server
> ":0"
>>>> after 2556 requests (2556 known processed) with 0 events
> remaining.
>>>>
>>>>
>>>>>
>>>>> If the problem persists, please attach /var/log/Xorg.8.log (I'll take
>>>>> a note to collect that in the reportbug script, it doesn't at the
>>>>> moment).
>>>>
>>>> strange?
>>>>
>>>> does not exist...only this
>>>>
>>>> -rw-r--r-- 1 root root 32804 Mar 9 01:41 Xorg.0.log
>>>> -rw-r--r-- 1 root root 34420 Mar 1 20:50
> Xorg.0.log.old
>>>> -rw-r--r-- 1 root root 29633 Aug 2 2015 Xorg.1.log
>>>
>>> That means it's not even trying to start the Xorg instance on the
> nvidia driver.
>>>
>>> That warning is worrying about bumblebeed.
>>>
>>> If you are running on systemd, can you please check the output of:
>>>
>>> sudo systemctl status bumblebeed
>>>
>>> sudo journalctl -b -u bumblebeed
>>
>> you're right, big trouble in little china
>>
>> $ sudo systemctl status bumblebeed
>> [sudo] password for fulano:
>> ● bumblebeed.service - Bumblebee C Daemon
>> Loaded: loaded (/lib/systemd/system/bumblebeed.service; enabled;
>> vendor preset: enabled)
>> Active: active (running) since Thu 2016-03-10 00:27:14 AEDT; 58min ago
>> Main PID: 826 (bumblebeed)
>> CGroup: /system.slice/bumblebeed.service
>> └─826 /usr/sbin/bumblebeed
>>
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349621] [ERROR][XORG] (EE)
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349626] [ERROR][XORG] (EE)
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349630] [ERROR][XORG] (EE)
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349634] [ERROR]X did not
>> start properly
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135116] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135145] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135158] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135163] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135169] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135174] [ERROR]X did not
>> start properly
>>
>> $ sudo journalctl -b -u bumblebeed
>> -- Logs begin at Thu 2016-03-10 00:27:05 AEDT, end at Thu 2016-03-10
>> 01:26:13 AEDT. --
>> Mar 10 00:27:14 hesse systemd[1]: Started Bumblebee C Daemon.
>> Mar 10 00:27:26 hesse bumblebeed[826]: [ 44.974058]
>> [INFO]/usr/sbin/bumblebeed 3.2.1 started
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349590] [ERROR][XORG] (EE)
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349612] [ERROR][XORG] (EE)
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349621] [ERROR][XORG] (EE)
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349626] [ERROR][XORG] (EE)
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349630] [ERROR][XORG] (EE)
>> Mar 10 00:29:19 hesse bumblebeed[826]: [ 158.349634] [ERROR]X did not
>> start properly
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135116] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135145] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135158] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135163] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135169] [ERROR][XORG] (EE)
>> Mar 10 00:29:30 hesse bumblebeed[826]: [ 169.135174] [ERROR]X did not
>> start properly
>
> Sorry forgot to ask, could you please attach /var/log/Xorg.0.log too?
> Together with the status and the journal of bumblebeed. Maybe as the first
> thing do a systemctl restart bumblebeed and then optirun, and then collect
> the logs.
>
> I see that you are running stretch, so I'm beginning to think it's an
> incompatibility with the rootless xorg that's in stretch/sid, we've already
> seen bug reports about that.
>
> Kind regards,
> Luca Boccassi
sure, i ran primusrun and optirun again
systemctl restart bumblebeed
then primusrun and optirun again
the resultant logs enclosed
thanks a lot
there is no rush at all
also, i have doubts about what reportbug 'reports' concerning which
dependencies are installed for packages - it very often lists missing
dependencies when in fact they are installed
i have filed a bug about it...
just so you know, if its important...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xorg.0.log
Type: text/x-log
Size: 30072 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20160311/3ad52594/attachment-0001.bin>
More information about the pkg-nvidia-devel
mailing list