Re: [gentoo-user] Pale Moon Air-Gapped portage EAPI 6 Install WAS: [Logging] SSL with PM

[Miroslav Rovis]

On 161223-17:58+0100, Miroslav Rovis wrote:
> On 161223-05:38+0100, Miroslav Rovis wrote:
> > It took me all of my skills ;-) . But I installed Pale Moon
> ...
> > That's new technology. EAPI=6 in the ebuild
> > Nothing I've seen in my previous 7 years as Gentoo
...
> 
> The git object pack sources, guess where they are by looking up:
> 
> # du -hs /usr/portage/distfiles/git3-src\
> EGIT_MIRROR_URI\=git\:/localhost/cgi-bin/cgit.cgi/cgi-bin_cgit.cgi_Pale-Moon.git/*/
> 
> 48K   /usr/portage/distfiles/git3-src
> EGIT_MIRROR_URI=git:/localhost/cgi-bin/cgit.cgi/cgi-bin_cgit.cgi_Pale-Moon.git/hooks/
> 
> 8.0K  /usr/portage/distfiles/git3-src
> EGIT_MIRROR_URI=git:/localhost/cgi-bin/cgit.cgi/cgi-bin_cgit.cgi_Pale-Moon.git/info/
> 
> 283M  /usr/portage/distfiles/git3-src
> EGIT_MIRROR_URI=git:/localhost/cgi-bin/cgit.cgi/cgi-bin_cgit.cgi_Pale-Moon.git/objects/
> 
> 744K  /usr/portage/distfiles/git3-src
> EGIT_MIRROR_URI=git:/localhost/cgi-bin/cgit.cgi/cgi-bin_cgit.cgi_Pale-Moon.git/refs/
> 
> #
> 
> ( reformatted the above output for email, but those are 5 distinct lines of
> stdout only )
> 
...
> 
> What is needed in the /etc/portage/make.conf is:
> 
> EGIT3_STORE_DIR=${DISTDIR}/git3-src"
> EGIT_MIRROR_URI=git://localhost/cgi-bin/cgit.cgi/"
> 
> ( Note at proofreading time: true, that is still stuck in the make.conf,
> and it is what was in there when the successful install happend, but
> shouldn't it be http://localhost/cgi-bin/cgit.cgi/ instead? )

I tried changing that (and updated, the Air-Gapped way, to

www-client/palemoon-27.0.3-r7

(which is my local bump of 
www-client/palemoon-27.0.3-r1 from unofficial)

, and the only difference is that now, the top dir
in /usr/portage/distfiles/ looks:

# ls -l /usr/portage/distfiles/git3-src\ EGIT_MIRROR_URI\=http\:/
total 4
drwxr-xr-x 3 portage portage 4096 2017-01-10 02:54 localhost
# 

while previously was:

EGIT_MIRROR_URI\=git\:/

instead of what is now:

EGIT_MIRROR_URI\=http\:/

The rest is all the same.

But, again, Palemoon works just fine. And my wonder about it still
remains. But it works, and seems a reliable method.

Just thought to make clear on this. This email should appear in reply to
where I explained it as really the best I could.

-- 
Miroslav Rovis
Zagreb, Croatia
http://www.CroatiaFidelis.hr


signature.asc
Description: Digital signature

Re: [gentoo-user] Re: Problem matching latest kernel with latest Nvidia

[Corbin Bird]

On 01/10/2017 01:29 PM, Nikos Chantziaras wrote:
> On 01/10/2017 06:31 PM, Corbin Bird wrote:
>> You might want to add "static-libs" to the use flags as well. Another
>> useful utility gets built by it.
>
> There doesn't seem to be anything installed by it, except a static lib
> (libXNVCtrl.a) and some header files (/usr/include/NVCtrl). No
> executables.
>
>

Thanks for that info. You did jog the memory.

"sys-apps/hwloc" USE = gl ... is dependent on that lib being built
static. ( NVCtrl )

USE = gl  :  Enable GL display device discovery (NVCtrl)
USE = opencl : Enable OpenCL device discovery (AMD only)

Re: [gentoo-user] KDE5: no desktop

[Frank Steinmetzger]

On Mon, Jan 09, 2017 at 06:57:16PM +0700, Robin Atwood wrote:
> On Sunday 08 January 2017, Fernando Rodriguez wrote:
> > Try to login as a new user (or move your home directory out of the
> > way). If it works start selectively deleting dot files/directories
> > from your home directory. Start with .cache, .kde4 and everything that
> > starts with a k in .config and .local and go from there. I had the
> > exact same problem when I upgraded one of my laptops and that's how I
> > fixed it. Also delete anything in /var/cache and any files belonging
> > to your uses in /tmp and /run.
> > 
> > You can also try switching to a VT and kill plasmashell and if it
> > doesn't restart automatically start it with the DISPLAY environment
> > variable properly set.
> > 
> > Also look at the system logs, .xsession-errors, xorg logs, etc for
> > clues. You can also run kdebugdialog5 from another DE to enable a lot
> > of kde debug output to the system logs.
> > 
> 
> I said above that I created a new user and got exactly same problem, so that 
> pretty much excludes old files as a possibility.

A short while ago Plasma (5.8.5) started crashing right after login on my
PC. I have no idea why, even a clean user didn’t help. But I could still run
KDE normally when running startx from the TTY. But then other stuff didn’t
work, such as mounting media as a user. Eventually I tried a different login
manager (sddm instead of lightdm) and it worked again. Too bad – I don’t
really like sddm because it is not keyboard friendly (well, lightdm is not
that much better either, I truely miss kdm).

In the end, I still started with a fresh user config, because I used the
opportunity to clean away old KDE 4 stuff. And since this cost me two days’
spare time already, I can’t be bothered with it anymore. :/

-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any social network.

It’s a pity that at the end of the money there’s so much month left.


signature.asc
Description: Digital signature

[gentoo-user] Re: Problem matching latest kernel with latest Nvidia

[Nikos Chantziaras]

On 01/10/2017 06:31 PM, Corbin Bird wrote:

You might want to add "static-libs" to the use flags as well. Another
useful utility gets built by it.


There doesn't seem to be anything installed by it, except a static lib 
(libXNVCtrl.a) and some header files (/usr/include/NVCtrl). No executables.

Re: [gentoo-user] Problem matching latest kernel with latest Nvidia

[Dale]

Dale wrote:
> Corbin Bird wrote:
>> On 01/10/2017 10:46 AM, J. Roeleveld wrote:
>>> Which one would that be?
>>> I would not expect any tools or utilities to be added when selecting static 
>>> libraries.
>>>
>>> --
>>> Joost
>> I can't remember the specific name of it, had to do with ?OpenCL? or ?CUDA?
>> Other posters on this list using "x11-drivers/nvidia-drivers" could tell
>> you exactly why.
>> I should have saved those e-mails, but didn't. :(
>>
>> -
>> The link has the whole list all libs && utilities that are built /
>> installed.
>>
>> Reference / Doc Link :
>> ftp://download.nvidia.com/XFree86/Linux-x86/375.26/README/README.txt
>>
>>
>
> Somewhat lengthy post but here is a file listing for mine.  It is a
> somewhat older version since my card is a bit older.  I'm also adding
> the version and USE flags for it at the bottom.  All in one paste tho.
>
>
> root@fireball / # equery f nvidia-drivers
>  * Searching for nvidia-drivers ...
>  * Contents of x11-drivers/nvidia-drivers-340.101:
> /etc<<< SNIP >>>
> root@fireball / # emerge -vp nvidia-drivers
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R] x11-drivers/nvidia-drivers-340.101:0/340::gentoo 
> USE="X acpi multilib tools -pax_kernel -static-libs -uvm" 0 KiB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
> root@fireball / #
>
>
> Hope that helps.
>
> Dale
>
> :-)  :-) 
>


And I just noticed I have static-libs disabled which means this post
won't likely do a bit of good. 

< Dale slaps hand > 

Dale

:-)  :-) 

Re: [gentoo-user] Problem matching latest kernel with latest Nvidia

[Dale]

Corbin Bird wrote:
> On 01/10/2017 10:46 AM, J. Roeleveld wrote:
>>
>> Which one would that be?
>> I would not expect any tools or utilities to be added when selecting static 
>> libraries.
>>
>> --
>> Joost
> I can't remember the specific name of it, had to do with ?OpenCL? or ?CUDA?
> Other posters on this list using "x11-drivers/nvidia-drivers" could tell
> you exactly why.
> I should have saved those e-mails, but didn't. :(
>
> -
> The link has the whole list all libs && utilities that are built /
> installed.
>
> Reference / Doc Link :
> ftp://download.nvidia.com/XFree86/Linux-x86/375.26/README/README.txt
>
>


Somewhat lengthy post but here is a file listing for mine.  It is a
somewhat older version since my card is a bit older.  I'm also adding
the version and USE flags for it at the bottom.  All in one paste tho.


root@fireball / # equery f nvidia-drivers
 * Searching for nvidia-drivers ...
 * Contents of x11-drivers/nvidia-drivers-340.101:
/etc
/etc/OpenCL
/etc/OpenCL/vendors
/etc/OpenCL/vendors/nvidia.icd
/etc/X11
/etc/X11/xinit
/etc/X11/xinit/xinitrc.d
/etc/X11/xinit/xinitrc.d/95-nvidia-settings
/etc/conf.d
/etc/conf.d/nvidia-persistenced
/etc/config_examples
/etc/config_examples/x11-drivers
/etc/config_examples/x11-drivers/nvidia-drivers ->
/usr/share/doc/nvidia-drivers-340.101/html
/etc/init.d
/etc/init.d/nvidia-persistenced
/etc/init.d/nvidia-smi
/etc/modprobe.d
/etc/modprobe.d/nvidia.conf
/etc/nvidia
/etc/nvidia/nvidia-application-profiles-rc
/lib
/lib/modules
/lib/modules/4.5.2-gentoo
/lib/modules/4.5.2-gentoo/video
/lib/modules/4.5.2-gentoo/video/nvidia.ko
/lib/udev
/lib/udev/nvidia-udev.sh
/lib/udev/rules.d
/lib/udev/rules.d/99-nvidia.rules
/opt
/opt/bin
/opt/bin/nvidia-cuda-mps-control
/opt/bin/nvidia-cuda-mps-server
/opt/bin/nvidia-debugdump
/opt/bin/nvidia-modprobe
/opt/bin/nvidia-persistenced
/opt/bin/nvidia-smi
/opt/bin/nvidia-xconfig
/usr
/usr/bin
/usr/bin/nvidia-bug-report.sh
/usr/bin/nvidia-modprobe -> /opt/bin/nvidia-modprobe
/usr/bin/nvidia-settings
/usr/lib32
/usr/lib32/OpenCL
/usr/lib32/OpenCL/vendors
/usr/lib32/OpenCL/vendors/nvidia
/usr/lib32/OpenCL/vendors/nvidia/libOpenCL.so -> libOpenCL.so.1
/usr/lib32/OpenCL/vendors/nvidia/libOpenCL.so.1 -> libOpenCL.so.1.0.0
/usr/lib32/OpenCL/vendors/nvidia/libOpenCL.so.1.0.0
/usr/lib32/libcuda.so -> libcuda.so.1
/usr/lib32/libcuda.so.1 -> libcuda.so.340.101
/usr/lib32/libcuda.so.340.101
/usr/lib32/libnvidia-compiler.so -> libnvidia-compiler.so.1
/usr/lib32/libnvidia-compiler.so.1 -> libnvidia-compiler.so.340.101
/usr/lib32/libnvidia-compiler.so.340.101
/usr/lib32/libnvidia-eglcore.so -> libnvidia-eglcore.so.1
/usr/lib32/libnvidia-eglcore.so.1 -> libnvidia-eglcore.so.340.101
/usr/lib32/libnvidia-eglcore.so.340.101
/usr/lib32/libnvidia-glcore.so -> libnvidia-glcore.so.1
/usr/lib32/libnvidia-glcore.so.1 -> libnvidia-glcore.so.340.101
/usr/lib32/libnvidia-glcore.so.340.101
/usr/lib32/libnvidia-glsi.so -> libnvidia-glsi.so.1
/usr/lib32/libnvidia-glsi.so.1 -> libnvidia-glsi.so.340.101
/usr/lib32/libnvidia-glsi.so.340.101
/usr/lib32/libnvidia-ifr.so -> libnvidia-ifr.so.1
/usr/lib32/libnvidia-ifr.so.1 -> libnvidia-ifr.so.340.101
/usr/lib32/libnvidia-ifr.so.340.101
/usr/lib32/libnvidia-ml.so -> libnvidia-ml.so.1
/usr/lib32/libnvidia-ml.so.1 -> libnvidia-ml.so.340.101
/usr/lib32/libnvidia-ml.so.340.101
/usr/lib32/libnvidia-opencl.so -> libnvidia-opencl.so.1
/usr/lib32/libnvidia-opencl.so.1 -> libnvidia-opencl.so.340.101
/usr/lib32/libnvidia-opencl.so.340.101
/usr/lib32/libnvidia-tls.so -> libnvidia-tls.so.1
/usr/lib32/libnvidia-tls.so.1 -> libnvidia-tls.so.340.101
/usr/lib32/libnvidia-tls.so.340.101
/usr/lib32/libvdpau_nvidia.so -> libvdpau_nvidia.so.1
/usr/lib32/libvdpau_nvidia.so.1 -> libvdpau_nvidia.so.340.101
/usr/lib32/libvdpau_nvidia.so.340.101
/usr/lib32/opengl
/usr/lib32/opengl/nvidia
/usr/lib32/opengl/nvidia/lib
/usr/lib32/opengl/nvidia/lib/libEGL.so -> libEGL.so.1
/usr/lib32/opengl/nvidia/lib/libEGL.so.1 -> libEGL.so.340.101
/usr/lib32/opengl/nvidia/lib/libEGL.so.340.101
/usr/lib32/opengl/nvidia/lib/libGL.so -> libGL.so.1
/usr/lib32/opengl/nvidia/lib/libGL.so.1 -> libGL.so.340.101
/usr/lib32/opengl/nvidia/lib/libGL.so.340.101
/usr/lib32/opengl/nvidia/lib/libGLESv1_CM.so -> libGLESv1_CM.so.1
/usr/lib32/opengl/nvidia/lib/libGLESv1_CM.so.1 -> libGLESv1_CM.so.340.101
/usr/lib32/opengl/nvidia/lib/libGLESv1_CM.so.340.101
/usr/lib32/opengl/nvidia/lib/libGLESv2.so -> libGLESv2.so.2
/usr/lib32/opengl/nvidia/lib/libGLESv2.so.2 -> libGLESv2.so.340.101
/usr/lib32/opengl/nvidia/lib/libGLESv2.so.340.101
/usr/lib64
/usr/lib64/OpenCL
/usr/lib64/OpenCL/vendors
/usr/lib64/OpenCL/vendors/nvidia
/usr/lib64/OpenCL/vendors/nvidia/libOpenCL.so -> libOpenCL.so.1
/usr/lib64/OpenCL/vendors/nvidia/libOpenCL.so.1 -> libOpenCL.so.1.0.0
/usr/lib64/OpenCL/vendors/nvidia/libOpenCL.so.1.0.0
/usr/lib64/libcuda.so -> libcuda.so.1
/usr/lib64/libcuda.so.1 -> libcuda.so.340.101
/usr/lib64/libcuda.so.340.101
/usr/lib64/libnvcuvid.so -> 

Re: [gentoo-user] Problem matching latest kernel with latest Nvidia

[Corbin Bird]

On 01/10/2017 10:46 AM, J. Roeleveld wrote:
> On January 10, 2017 5:31:19 PM GMT+01:00, Corbin Bird 
>  wrote:
>> On 01/10/2017 04:22 AM, J. Roeleveld wrote:
>>> On January 10, 2017 10:01:12 AM GMT+01:00, Philip Webb
>>  wrote:
 170109 Nikos Chantziaras wrote:
> On 01/09/2017 10:09 AM, Philip Webb wrote:
>> I had a previous thread re Kernel 4.9.0 + Nvidia 375.26 (now
 stable).
>> I tried recompiling that kernel with DRM disabled,
>> & remerged Nvidia 375.26 , but X won't start.
> The nvidia driver isn't "automatic". It's not used by X.Org by
 default.
> X.Org only uses its own drivers by default.
> For the nvidia driver, you need a conf file.
> Something like this in /etc/X11/xorg.conf.d/nvidia.conf:
> http://pastebin.com/raw/0y3NMndp
 I didn't need this with earlier versions of Nvidia-drivers,
 but I've copied your template & am willing to give it a try.
 It looks as if there are several lines which wouldn't fit my
>> machine.
> The nvidia driver has a tool to help with this too,
> it's called `nvidia-xconfig`.
 It doesn't seem to be available on my machine :

  root:515 xorg.conf.d> which nvidia-xconfig
 which: no nvidia-xconfig in
 (/sbin:/usr/sbin:/usr/local/sbin::/bin:/usr/bin:/usr/local/bin:)
  root:517 xorg.conf.d> nvidia-xconfig
   bash: nvidia-xconfig: command not found

 Thanks to the others who replied.  One asked for USE flags : here
>> they
 are :

  root:518 xorg.conf.d> eix nvidia-drivers
   ...
 Installed versions:  361.28^msd{tbz2}([2017-01-09 02:41:57])(X
>> driver
 gtk3 kms -acpi -multilib -pax_kernel -static-libs -tools -uvm
 KERNEL="linux -FreeBSD")

 Those are for the version which works & which I've had to restore,
 but I didn't change them for 375.26 .

 Further suggestions are very welcome.
>>> Add the "tools" USE flag to get nvidiasettings and similar.
>>>
>>> Am going to try a later version of drivers and kernel myself later.
>>>
>>> --
>>> Joost
>> You might want to add "static-libs" to the use flags as well. Another
>> useful utility gets built by it.
> Which one would that be?
> I would not expect any tools or utilities to be added when selecting static 
> libraries.
>
> --
> Joost

I can't remember the specific name of it, had to do with ?OpenCL? or ?CUDA?
Other posters on this list using "x11-drivers/nvidia-drivers" could tell
you exactly why.
I should have saved those e-mails, but didn't. :(

-
The link has the whole list all libs && utilities that are built /
installed.

Reference / Doc Link :
ftp://download.nvidia.com/XFree86/Linux-x86/375.26/README/README.txt

[gentoo-user] Midi keyboard "Oxygene61", jackd/alsa and the rest of the band...

[Meino . Cramer]

Hi,

I want to setup the following things:
An midi keyboard called "Oxygene61"
(no, it was'nt previously owned by Mister Jarre...),
jackd/alsa (qjackctrl) and ZynAddSubFX.

The problem is: The keyboard shows up under
the "ALSA"-Tab of qjackctrl and it is alone there
with "Midi Through".

Zyns output shows up under the "AUDIO"-tab and
Zyns input is located under the "MIDI"-tab.

There is no "midi through" output port.

What do I have to do to connect the midi
keyboards outputs to the inputs of Zyn?

I am confused...

Cheers
Meino

[gentoo-user] Re: Problem matching latest kernel with latest Nvidia

[Nikos Chantziaras]

On 01/10/2017 11:01 AM, Philip Webb wrote:

170109 Nikos Chantziaras wrote:

On 01/09/2017 10:09 AM, Philip Webb wrote:

I had a previous thread re Kernel 4.9.0 + Nvidia 375.26 (now stable).
I tried recompiling that kernel with DRM disabled,
& remerged Nvidia 375.26 , but X won't start.

The nvidia driver isn't "automatic". It's not used by X.Org by default.
X.Org only uses its own drivers by default.
For the nvidia driver, you need a conf file.
Something like this in /etc/X11/xorg.conf.d/nvidia.conf:
http://pastebin.com/raw/0y3NMndp


I didn't need this with earlier versions of Nvidia-drivers,
but I've copied your template & am willing to give it a try.
It looks as if there are several lines which wouldn't fit my machine.


The file is generic. The only thing specific to me is "G2770PF", which 
my monitor's model name. Which is not parsed anyway.

Re: [gentoo-user] Linux error messages trying to mimic w*nd*ws ?

[Corbin Bird]

On 01/09/2017 10:15 PM, meino.cra...@gmx.de wrote:
> Corbin Bird  [17-01-10 05:12]:
>> On 01/09/2017 02:11 PM, meino.cra...@gmx.de wrote:
>>> Hi,
>>>
>>> I want to burn an iso image onto a rewritable
>>> CD (CD-RW) with k3b.
>>>
>>> I loaded the empty CDRW medium into the burner.
>>>
>>> I started k3b.
>>>
>>> Top left it says:
>>>
>>> "Empty CDRW-medium"
>>>
>>> I pressed "Burn ISO".
>>>
>>> A dialog pops up, asking for a ISO image
>>> which did select.
>>>
>>> Then it calculates the Hash and asked
>>> me "Please insert an empty medium"
>>>
>>> "Okay", I thought, "may erasing helps!"
>>>
>>> I choosed "Erase CDRW". A dialog pops
>>> up and offers "Start", which I pressed.
>>>
>>> Instantly another error dialog pop up, which 
>>> seems to be presented by another, foreign
>>> OS...it looks so familiar, saying:
>>>
>>> "Found medium: Empty CD-RW medium
>>> Please insert rewritable CD medium into drive."
>>>
>>> Lost?
>>>
>>> What went so badly here?
>>>
>>> Cheers
>>> Meino
>>>
>>>
>>>
>>>
>>>
>> Question for you :
>>
>> Did you format the CD-RW media first? ( Yes, it must be formatted before
>> anything gets written. )
>>
>>
>>
>>
> Answer for you:
> Yes
>
>
>
>

You would not believe how many do NOT know to do that first.  :)

That screwy error you got can very easily be from hardware not properly
setting up.

If you are willing to troubleshoot, there are some things to check.

First check ... in the dmesg log, does the kernel see the burner?
( it seems the SFF / ATAPI devices can have problems,
 with having to go communicate through the kernels ahci layer )

sample from my dmesg log :

[2.027722] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[2.031197] ata4: FORCE: cable set to sata
[2.031332] ata4.00: FORCE: horkage modified (noncq)
[2.031459] ata4.00: FORCE: horkage modified (atapi_dmadir)
[2.031576] ata4.00: ATAPI: PIONEER BD-RW   BDR-208M, 1.50, max
UDMA/100, DMADIR
[2.035319] ata4.00: configured for UDMA/100
[2.046988] scsi 4:0:0:0: CD-ROMPIONEER  BD-RW   BDR-208M
1.50 PQ: 0 ANSI: 5
[2.089230] sr 4:0:0:0: [sr0] scsi3-mmc drive: 125x/125x writer
dvd-ram cd/rw xa/form2 cdda tray
[2.089422] cdrom: Uniform CD-ROM driver Revision: 3.20
[2.089656] sr 4:0:0:0: Attached scsi CD-ROM sr0
[2.089723] sr 4:0:0:0: Attached scsi generic sg3 type 5

NOTE : this is a BD-RW drive. The kernel has to be forced to recognize it.
The kernel parameter : libata.force=4.00:sata,1.5,noncq,atapi_dmadir

The reason I ask, is that if the kernel can't or hasn't recognized it,
the wrong command sets are used.

Hope this helps.

Re: [gentoo-user] Problem matching latest kernel with latest Nvidia

[J. Roeleveld]

On January 10, 2017 5:31:19 PM GMT+01:00, Corbin Bird  
wrote:
>
>On 01/10/2017 04:22 AM, J. Roeleveld wrote:
>> On January 10, 2017 10:01:12 AM GMT+01:00, Philip Webb
> wrote:
>>> 170109 Nikos Chantziaras wrote:
 On 01/09/2017 10:09 AM, Philip Webb wrote:
> I had a previous thread re Kernel 4.9.0 + Nvidia 375.26 (now
>>> stable).
> I tried recompiling that kernel with DRM disabled,
> & remerged Nvidia 375.26 , but X won't start.
 The nvidia driver isn't "automatic". It's not used by X.Org by
>>> default.
 X.Org only uses its own drivers by default.
 For the nvidia driver, you need a conf file.
 Something like this in /etc/X11/xorg.conf.d/nvidia.conf:
 http://pastebin.com/raw/0y3NMndp
>>> I didn't need this with earlier versions of Nvidia-drivers,
>>> but I've copied your template & am willing to give it a try.
>>> It looks as if there are several lines which wouldn't fit my
>machine.
>>>
 The nvidia driver has a tool to help with this too,
 it's called `nvidia-xconfig`.
>>> It doesn't seem to be available on my machine :
>>>
>>>  root:515 xorg.conf.d> which nvidia-xconfig
>>> which: no nvidia-xconfig in
>>> (/sbin:/usr/sbin:/usr/local/sbin::/bin:/usr/bin:/usr/local/bin:)
>>>  root:517 xorg.conf.d> nvidia-xconfig
>>>   bash: nvidia-xconfig: command not found
>>>
>>> Thanks to the others who replied.  One asked for USE flags : here
>they
>>> are :
>>>
>>>  root:518 xorg.conf.d> eix nvidia-drivers
>>>   ...
>>> Installed versions:  361.28^msd{tbz2}([2017-01-09 02:41:57])(X
>driver
>>> gtk3 kms -acpi -multilib -pax_kernel -static-libs -tools -uvm
>>> KERNEL="linux -FreeBSD")
>>>
>>> Those are for the version which works & which I've had to restore,
>>> but I didn't change them for 375.26 .
>>>
>>> Further suggestions are very welcome.
>> Add the "tools" USE flag to get nvidiasettings and similar.
>>
>> Am going to try a later version of drivers and kernel myself later.
>>
>> --
>> Joost
>You might want to add "static-libs" to the use flags as well. Another
>useful utility gets built by it.

Which one would that be?
I would not expect any tools or utilities to be added when selecting static 
libraries.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Problem matching latest kernel with latest Nvidia

[Corbin Bird]

On 01/10/2017 04:22 AM, J. Roeleveld wrote:
> On January 10, 2017 10:01:12 AM GMT+01:00, Philip Webb  
> wrote:
>> 170109 Nikos Chantziaras wrote:
>>> On 01/09/2017 10:09 AM, Philip Webb wrote:
 I had a previous thread re Kernel 4.9.0 + Nvidia 375.26 (now
>> stable).
 I tried recompiling that kernel with DRM disabled,
 & remerged Nvidia 375.26 , but X won't start.
>>> The nvidia driver isn't "automatic". It's not used by X.Org by
>> default.
>>> X.Org only uses its own drivers by default.
>>> For the nvidia driver, you need a conf file.
>>> Something like this in /etc/X11/xorg.conf.d/nvidia.conf:
>>> http://pastebin.com/raw/0y3NMndp
>> I didn't need this with earlier versions of Nvidia-drivers,
>> but I've copied your template & am willing to give it a try.
>> It looks as if there are several lines which wouldn't fit my machine.
>>
>>> The nvidia driver has a tool to help with this too,
>>> it's called `nvidia-xconfig`.
>> It doesn't seem to be available on my machine :
>>
>>  root:515 xorg.conf.d> which nvidia-xconfig
>> which: no nvidia-xconfig in
>> (/sbin:/usr/sbin:/usr/local/sbin::/bin:/usr/bin:/usr/local/bin:)
>>  root:517 xorg.conf.d> nvidia-xconfig
>>   bash: nvidia-xconfig: command not found
>>
>> Thanks to the others who replied.  One asked for USE flags : here they
>> are :
>>
>>  root:518 xorg.conf.d> eix nvidia-drivers
>>   ...
>> Installed versions:  361.28^msd{tbz2}([2017-01-09 02:41:57])(X driver
>> gtk3 kms -acpi -multilib -pax_kernel -static-libs -tools -uvm
>> KERNEL="linux -FreeBSD")
>>
>> Those are for the version which works & which I've had to restore,
>> but I didn't change them for 375.26 .
>>
>> Further suggestions are very welcome.
> Add the "tools" USE flag to get nvidiasettings and similar.
>
> Am going to try a later version of drivers and kernel myself later.
>
> --
> Joost
You might want to add "static-libs" to the use flags as well. Another
useful utility gets built by it.

Re: [gentoo-user] Problem matching latest kernel with latest Nvidia

[J. Roeleveld]

On January 10, 2017 10:01:12 AM GMT+01:00, Philip Webb  
wrote:
>170109 Nikos Chantziaras wrote:
>> On 01/09/2017 10:09 AM, Philip Webb wrote:
>>> I had a previous thread re Kernel 4.9.0 + Nvidia 375.26 (now
>stable).
>>> I tried recompiling that kernel with DRM disabled,
>>> & remerged Nvidia 375.26 , but X won't start.
>> The nvidia driver isn't "automatic". It's not used by X.Org by
>default.
>> X.Org only uses its own drivers by default.
>> For the nvidia driver, you need a conf file.
>> Something like this in /etc/X11/xorg.conf.d/nvidia.conf:
>> http://pastebin.com/raw/0y3NMndp
>
>I didn't need this with earlier versions of Nvidia-drivers,
>but I've copied your template & am willing to give it a try.
>It looks as if there are several lines which wouldn't fit my machine.
>
>> The nvidia driver has a tool to help with this too,
>> it's called `nvidia-xconfig`.
>
>It doesn't seem to be available on my machine :
>
>  root:515 xorg.conf.d> which nvidia-xconfig
>which: no nvidia-xconfig in
>(/sbin:/usr/sbin:/usr/local/sbin::/bin:/usr/bin:/usr/local/bin:)
>  root:517 xorg.conf.d> nvidia-xconfig
>   bash: nvidia-xconfig: command not found
>
>Thanks to the others who replied.  One asked for USE flags : here they
>are :
>
>  root:518 xorg.conf.d> eix nvidia-drivers
>   ...
>Installed versions:  361.28^msd{tbz2}([2017-01-09 02:41:57])(X driver
>gtk3 kms -acpi -multilib -pax_kernel -static-libs -tools -uvm
>KERNEL="linux -FreeBSD")
>
>Those are for the version which works & which I've had to restore,
>but I didn't change them for 375.26 .
>
>Further suggestions are very welcome.

Add the "tools" USE flag to get nvidiasettings and similar.

Am going to try a later version of drivers and kernel myself later.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Linux error messages trying to mimic w*nd*ws ?

[Konstantin Shakhnov]

On Mon, Jan 09, 2017 at 09:11:04PM +0100, meino.cra...@gmx.de wrote:
> Hi,
>
> I want to burn an iso image onto a rewritable
> CD (CD-RW) with k3b.
>
> I loaded the empty CDRW medium into the burner.
>
> I started k3b.
>
> Top left it says:
>
> "Empty CDRW-medium"
>
> I pressed "Burn ISO".
>
> A dialog pops up, asking for a ISO image
> which did select.
>
> Then it calculates the Hash and asked
> me "Please insert an empty medium"
>
> "Okay", I thought, "may erasing helps!"
>
> I choosed "Erase CDRW". A dialog pops
> up and offers "Start", which I pressed.
>
> Instantly another error dialog pop up, which
> seems to be presented by another, foreign
> OS...it looks so familiar, saying:
>
> "Found medium: Empty CD-RW medium
> Please insert rewritable CD medium into drive."
>
> Lost?
>
> What went so badly here?

Try to run k3b not by clicking icon, but from console and repeat
writing cd. Sometimes "userfriendly" gui programs write something useful
to STDERR.

BTW great phraseology!

[gentoo-user] Problem matching latest kernel with latest Nvidia

[Philip Webb]

170109 Nikos Chantziaras wrote:
> On 01/09/2017 10:09 AM, Philip Webb wrote:
>> I had a previous thread re Kernel 4.9.0 + Nvidia 375.26 (now stable).
>> I tried recompiling that kernel with DRM disabled,
>> & remerged Nvidia 375.26 , but X won't start.
> The nvidia driver isn't "automatic". It's not used by X.Org by default.
> X.Org only uses its own drivers by default.
> For the nvidia driver, you need a conf file.
> Something like this in /etc/X11/xorg.conf.d/nvidia.conf:
> http://pastebin.com/raw/0y3NMndp

I didn't need this with earlier versions of Nvidia-drivers,
but I've copied your template & am willing to give it a try.
It looks as if there are several lines which wouldn't fit my machine.

> The nvidia driver has a tool to help with this too,
> it's called `nvidia-xconfig`.

It doesn't seem to be available on my machine :

  root:515 xorg.conf.d> which nvidia-xconfig
   which: no nvidia-xconfig in 
(/sbin:/usr/sbin:/usr/local/sbin::/bin:/usr/bin:/usr/local/bin:)
  root:517 xorg.conf.d> nvidia-xconfig
   bash: nvidia-xconfig: command not found

Thanks to the others who replied.  One asked for USE flags : here they are :

  root:518 xorg.conf.d> eix nvidia-drivers
   ...
   Installed versions:  361.28^msd{tbz2}([2017-01-09 02:41:57])(X driver gtk3 
kms -acpi -multilib -pax_kernel -static-libs -tools -uvm KERNEL="linux 
-FreeBSD")

Those are for the version which works & which I've had to restore,
but I didn't change them for 375.26 .

Further suggestions are very welcome.

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