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