Re: [gentoo-user] trying to use Nouveau

2018-08-05 Thread Philip Webb
180805 Philip Webb wrote:
> 180804 Andrew Savchenko wrote:
>> Your xorg.conf -- or a file from xorg.conf.d directory --
>> must contain the following :
>> 
>>   Section "Device"
>>   Identifier  "Card1"
>>   Driver  "modesetting"
>>   ... (some options may follow)
>>   EndSection

I've done that, as described in my previous msg, without success.

Then I noticed that Wiki says the kernel needs recompiling
with 'Drivers->Graphics-><*>DirectRenderingManager
 <*>NouveauCards' ;
I also unset the "<->Backlight ... " just below, as I don't need it.
The new kernel is noticeably bigger than the previous version ;
I copied it to  /boot  as usual, updated  lilo.conf  & ran Lilo ;
the new kernel (called 4.14.52b) booted successfully,
but neither Nouveau nor Nvidia would start ;
even worse, neither would start with the previous version 4.14.52 ,
which had been working with Nvidia for some time.

The kernel log stops after several repeats of the lines :

  kernel: nvidia: Unknown symbol backlight_device_unregister (err 0)
  kernel: nvidia: Unknown symbol backlight_device_register (err 0)

Finally, I booted into kernel 4.9.95 & Nvidia still starts there.

This is turning into a nightmare.  It all started when 4.14.52
couldn't find my scanner, which 4.9.16 had no trouble with,
& then I found I couldn't test 4.9.16, as Nvidia no longer worked with it.
To test 4.9.16 it seems sensible to try Nouveau instead of Nvidia,
but that has led to a further tangle.

I suspect the problem with the scanner is that the Epson driver
needs an update to work with the most recent kernels.
That's something I'll have to take up with Epson, if I can.

However, the Nouveau/Nvidia mess is something I sb able to sort out.
Can anyone suggest what's gone wrong & how to put it right ?

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca




Re: [gentoo-user] What's wrong with 4.16.X?

2018-08-05 Thread Konstantinos Agouros
In <1533396747.28143.2.ca...@gentoo.org> l...@gentoo.org (Mart Raudsepp) writes:


>--=-rVvjIQxGphTC4iawWQmn
>Content-Type: text/plain; charset="UTF-8"
>Content-Transfer-Encoding: quoted-printable

>=C3=9Chel kenal p=C3=A4eval, L, 04.08.2018 kell 13:52, kirjutas Konstantino=
>s
>Agouros:
>> Hi,
>>=20
>4.14 is the LTS (long term support) kernel, thus that will have stable
>keywords only.
>4.16 is EOL (end of life) and doesn't receive fixes anymore, so it was
>removed from the main tree.
>4.17 is the new non-LTS series that still receives updates, so you
>probably want to upgrade to that, if you don't want to downgrade (or
>can't due to suboptimal Ryzen support there). In that case you want to
>upgrade to new series in a timely manner until at least a new LTS
>appears - then you could stick to that one instead (stable versions).

>See the nomenclature also on https://www.kernel.org/
Thanks for the clarification


>Mart
>--=-rVvjIQxGphTC4iawWQmn
>Content-Type: application/pgp-signature; name="signature.asc"
>Content-Description: This is a digitally signed message part
>Content-Transfer-Encoding: 7bit

>-BEGIN PGP SIGNATURE-
>Version: GnuPG v2

>iQKTBAABCgB9FiEEUdZn9pOq0mlNjRvdEKbJ+k9JlgYFAltlxwtfFIAALgAo
>aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDUx
>RDY2N0Y2OTNBQUQyNjk0RDhEMUJERDEwQTZDOUZBNEY0OTk2MDYACgkQEKbJ+k9J
>lgbW9BAAqG2XByzKyoHy7ayJ1lRlQ58+2oUEBd86tnixhfntt6DFZYsod6Y6lUhh
>QH9gqz0gaQj2/2C78QIwcEse29WQaSekjLTzASdxQVQEpF05M7BqhP33o1tSXsFS
>hRhNiArF/ghP/PL/ngUuO6hkJRQfveaOtb0nhxSF8bMnLR/qxCfcAAtXoY6Bcy1z
>hZ6uEF8oBUPuCwnKee8rUHZWGKAhLBkw3wnYQmBTSWPowpBnImQrtQEDZ/Y+Zii3
>kki/0JoTyd863T+Jl68t2L9OoLyvHl2RIF8iBcYp7BH9HjmKi53ct/hsXwDHZzq8
>vwH6jFQQmIIh/lXINDXJtQQXrSpPamvnt52JJEeaKDZXrjqD9pC5lvigeu93eMPw
>v3qlrGXz3I1ZsXvXtMIOeeyR1/RZDSVzmtR1awnEb+RQhkCXWx+CcNh16AGkBGe8
>gzQiKy3mf6oYDSuEc+l0J7ibSGtsoLSxY96+n2Autk4raQXTB2zfKFY5k6SQ1rAL
>kfNtGn2WcP+al9lFbvvoVvzCdFRW5lVD/q/zoyclrqravnVmNyvofAhCCayh+9dG
>8U4+FYQ6D9WK2EYetPRYWUbGyqSAyIhuZB6uLkGRomPamTSZ7cQj5HsFUwsZsoax
>fnQBU+aOguIKPfOSGUkYqusA0UbLPT6v1dtjvHJtVQXmx+kvJ5g=
>=7B40
>-END PGP SIGNATURE-

>--=-rVvjIQxGphTC4iawWQmn--


-- 
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet: elw...@agouros.de
Altersheimerstr. 1, 81545 Muenchen, Germany. Tel +49 89 69370185

"There is no 'dead' in team!" - Sameen Shaw



Re: [gentoo-user] trying to use Nouveau

2018-08-05 Thread T BkRl
I’m not sure if xorg is the only thing at fault. I’ve had issues in opensuse 
and mint where if I force nouveau it kernel panics during boot. Otherwise it 
loads Nvidia.



From: Philip Webb 
Sent: Sunday, August 5, 2018 3:40 AM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] trying to use Nouveau

180804 Andrew Savchenko wrote:
> Your xorg.conf -- or a file from xorg.conf.d directory --
> must contain the following :
>
> Section "Device"
> Identifier "Card1"
> Driver "modesetting"
> ... (some options may follow)
> EndSection
>
> You probably name `Driver "nvidia"` there right now.

I've created a file /etc/X11/xorg.conf.d/10nouveau.conf ,
which reads as above (apart from the "options" line, which is omitted) ;
I use spaces, not tabs. I've tried all 4 permutations
of "Card1" / "Card0" & "modesetting" / "nouveau".
I also tried naming it '99...' : there's a '20opengl.conf', which says :

Section "Files"
ModulePath "/usr/lib64/xorg/modules"
EndSection

I've also recompiled xorg-drivers , then xorg-server :
the former now has the USE flag 'nouveau'. I've rebooted between trials.

Every time, Nvidia starts :

(**) ModulePath set to "/usr/lib64/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
devices become available, reconfigure udev or disable AutoAddDevices.
(II) Loader magic: 0x55cc540cfc20
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 23.0
X.Org XInput driver : 24.1
X.Org Server Extension : 10.0
(--) PCI:*(0:1:0:0) 10de:104a:1043:8496 rev 161, Mem @ 0xfd00/16777216, 
0xf000/134217728, 0xf800/33554432, I/O @ 0xe000/128, BIOS @ 
0x/131072
(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.19.5, module version = 1.0.0
ABI class: X.Org Server Extension, version 10.0
(II) LoadModule: "nvidia"
(II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 390.67 Fri Jun 1 02:45:19 PDT 2018
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(--) using VT number 7

/usr/lib64/xorg/modules contains :

root:510 modules> ls -l
drwxr-xr-x 2 root root 184 Aug 5 02:56 drivers
drwxr-xr-x 2 root root 80 Aug 5 02:56 extensions
drwxr-xr-x 2 root root 80 Jun 2 20:57 input
-rwxr-xr-x 1 root root 92704 Aug 5 02:56 libexa.so
-rwxr-xr-x 1 root root 18480 Aug 5 02:56 libfbdevhw.so
-rwxr-xr-x 1 root root 142176 Aug 5 02:56 libfb.so
-rwxr-xr-x 1 root root 141848 Aug 5 02:56 libint10.so
-rwxr-xr-x 1 root root 10192 Aug 5 02:56 libshadowfb.so
-rwxr-xr-x 1 root root 34800 Aug 5 02:56 libshadow.so
-rwxr-xr-x 1 root root 22752 Aug 5 02:56 libvbe.so
-rwxr-xr-x 1 root root 31664 Aug 5 02:56 libvgahw.so
-rwxr-xr-x 1 root root 179040 Aug 5 02:56 libwfb.so
root:511 modules> ls -l drivers
-rwxr-xr-x 1 root root 69288 Aug 5 02:56 modesetting_drv.so
-rwxr-xr-x 1 root root 208600 Jul 26 15:39 nouveau_drv.so
-rw-r--r-- 1 root root 7780496 Jul 26 14:15 nvidia_drv.so
-rwxr-xr-x 1 root root 27512 May 12 20:20 vesa_drv.so

Is 'udev' getting entangled in this at some point ?

Does anyone have any further advice ? Thanks so far.

--
,,
SUPPORT ___//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O--O---' purslowatchassdotutorontodotca




Re: [gentoo-user] trying to use Nouveau

2018-08-05 Thread Philip Webb
180804 Andrew Savchenko wrote:
> Your xorg.conf -- or a file from xorg.conf.d directory --
> must contain the following :
> 
>   Section "Device"
>   Identifier  "Card1"
>   Driver  "modesetting"
>   ... (some options may follow)
>   EndSection
> 
> You probably name `Driver "nvidia"` there right now.

I've created a file  /etc/X11/xorg.conf.d/10nouveau.conf ,
which reads as above (apart from the "options" line, which is omitted) ;
I use spaces, not tabs.  I've tried all  4  permutations
of "Card1" / "Card0" & "modesetting" / "nouveau".
I also tried naming it '99...' : there's a '20opengl.conf', which says :

  Section "Files"
ModulePath "/usr/lib64/xorg/modules"
  EndSection

I've also recompiled  xorg-drivers , then  xorg-server :
the former now has the USE flag 'nouveau'.  I've rebooted between trials.

Every time, Nvidia starts :

  (**) ModulePath set to "/usr/lib64/xorg/modules"
  (II) The server relies on udev to provide the list of input devices.
   devices become available, reconfigure udev or disable AutoAddDevices.
  (II) Loader magic: 0x55cc540cfc20
  (II) Module ABI versions:
 X.Org ANSI C Emulation: 0.4
 X.Org Video Driver: 23.0
 X.Org XInput driver : 24.1
 X.Org Server Extension : 10.0
  (--) PCI:*(0:1:0:0) 10de:104a:1043:8496 rev 161, Mem @ 0xfd00/16777216, 
0xf000/134217728, 0xf800/33554432, I/O @ 0xe000/128, BIOS @ 
0x/131072
  (II) LoadModule: "glx"
  (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
  (II) Module glx: vendor="X.Org Foundation"
 compiled for 1.19.5, module version = 1.0.0
 ABI class: X.Org Server Extension, version 10.0
  (II) LoadModule: "nvidia"
  (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
  (II) Module nvidia: vendor="NVIDIA Corporation"
 compiled for 4.0.2, module version = 1.0.0
 Module class: X.Org Video Driver
  (II) NVIDIA dlloader X Driver  390.67  Fri Jun  1 02:45:19 PDT 2018
  (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
  (--) using VT number 7

 /usr/lib64/xorg/modules  contains :

  root:510 modules> ls -l
drwxr-xr-x 2 root root184 Aug  5 02:56 drivers
drwxr-xr-x 2 root root 80 Aug  5 02:56 extensions
drwxr-xr-x 2 root root 80 Jun  2 20:57 input
-rwxr-xr-x 1 root root  92704 Aug  5 02:56 libexa.so
-rwxr-xr-x 1 root root  18480 Aug  5 02:56 libfbdevhw.so
-rwxr-xr-x 1 root root 142176 Aug  5 02:56 libfb.so
-rwxr-xr-x 1 root root 141848 Aug  5 02:56 libint10.so
-rwxr-xr-x 1 root root  10192 Aug  5 02:56 libshadowfb.so
-rwxr-xr-x 1 root root  34800 Aug  5 02:56 libshadow.so
-rwxr-xr-x 1 root root  22752 Aug  5 02:56 libvbe.so
-rwxr-xr-x 1 root root  31664 Aug  5 02:56 libvgahw.so
-rwxr-xr-x 1 root root 179040 Aug  5 02:56 libwfb.so
  root:511 modules> ls -l drivers
-rwxr-xr-x 1 root root   69288 Aug  5 02:56 modesetting_drv.so
-rwxr-xr-x 1 root root  208600 Jul 26 15:39 nouveau_drv.so
-rw-r--r-- 1 root root 7780496 Jul 26 14:15 nvidia_drv.so
-rwxr-xr-x 1 root root   27512 May 12 20:20 vesa_drv.so

Is 'udev' getting entangled in this at some point ?

Does anyone have any further advice ?  Thanks so far.

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca