to...@tuxteam.de composed on 2017-07-25 21:47 (UTC+0200):
> On Tue, Jul 25, 2017 at 13:15:48 -0600, D. R. Evans wrote:
>> Felix Miata wrote:
...
https://wiki.archlinux.org/index.php/GRUB/Tips_and_tricks#Setting_the_framebuffer_resolution
...
>>> The cited URL has more to offer than what you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jul 25, 2017 at 01:15:48PM -0600, D. R. Evans wrote:
> Felix Miata wrote on 07/23/2017 08:26 PM:
>
> >
> >> I tried this solution (for Arch; I saw some posts about Debian, but nothing
> >> that seemed to be a definitive solution):
> >
> >> h
Felix Miata wrote on 07/23/2017 08:26 PM:
>
>> I tried this solution (for Arch; I saw some posts about Debian, but nothing
>> that seemed to be a definitive solution):
>
>> https://wiki.archlinux.org/index.php/GRUB/Tips_and_tricks#Setting_the_framebuffer_resolution
>
[material elided]
> The c
On Mon, 24 Jul 2017, Greg Wooledge wrote:
> On Mon, Jul 24, 2017 at 02:20:08PM +0100, Darac Marjal wrote:
> > You'd need some sort of system logging daemon. Something which runs with
> > the privileges necessary to write to the log file, and which can accept
> > log messages from unprivileged proce
On Mon, Jul 24, 2017 at 02:20:08PM +0100, Darac Marjal wrote:
> You'd need some sort of system logging daemon. Something which runs with
> the privileges necessary to write to the log file, and which can accept
> log messages from unprivileged processes, perhaps by listening on a UNIX
> socket.
Li
On Mon, Jul 24, 2017 at 08:59:56AM -0400, Greg Wooledge wrote:
On Sat, Jul 22, 2017 at 04:27:42PM -0400, Felix Miata wrote:
I don't often here fail to find a current /var/log/Xorg.0.log. I think what's
happening is the one in .local/share/ is getting copied to /var/log/ so that it
remains availa
On Sat, Jul 22, 2017 at 04:27:42PM -0400, Felix Miata wrote:
> I don't often here fail to find a current /var/log/Xorg.0.log. I think what's
> happening is the one in .local/share/ is getting copied to /var/log/ so that
> it
> remains available in the location people historically expect, where Goo
D. R. Evans composed on 2017-07-23 17:52 (UTC-0600):
> D. R. Evans wrote:
>> I am 99+% sure that the proprietary driver is being used, because the screen
>> looks quite different during the boot sequence, and slightly different once I
> I have discovered that if I open a console after switching
On Sun 23 Jul 2017 at 17:52:19 (-0600), D. R. Evans wrote:
> D. R. Evans wrote on 07/22/2017 11:48 AM:
>
> > I am 99+% sure that the proprietary driver is being used, because the screen
> > looks quite different during the boot sequence, and slightly different once
> > I
>
> I have discovered th
D. R. Evans wrote on 07/22/2017 11:48 AM:
> I am 99+% sure that the proprietary driver is being used, because the screen
> looks quite different during the boot sequence, and slightly different once I
I have discovered that if I open a console after switching to the NVIDIA
driver, the text is hug
Curt composed on 2017-07-22 15:58 (UTC-0400):
> Felix Miata wrote:
>> D. R. Evans composed on 2017-07-22 13:06 (UTC-0600):
>>> Reco wrote:
grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
>>> [HN:~] grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
>>> grep: /home/n7dr/.local/share/xorg/Xorg
On 2017-07-22, Felix Miata wrote:
> D. R. Evans composed on 2017-07-22 13:06 (UTC-0600):
>
>> Reco wrote:
>
>>> grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
>
>> [HN:~] grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
>> grep: /home/n7dr/.local/share/xorg/Xorg.[0-9]*.log: No such file or directo
D. R. Evans composed on 2017-07-22 13:06 (UTC-0600):
> Reco wrote:
>> grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
> [HN:~] grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
> grep: /home/n7dr/.local/share/xorg/Xorg.[0-9]*.log: No such file or directory
> [HN:~]
>
I don't know why he suggeste
Hans wrote on 07/22/2017 11:55 AM:
> Maybe try to add a file /etc/X11/xorg.conf (ask google, how it has to look),
> and in it set the driver "nvidia".
>
nvidia-xconfig created such a file, and the driver in it is set to "nvidia",
so I think that is indeed the confirmation I was looking for.
Tha
Reco wrote on 07/22/2017 12:37 PM:
> grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
[HN:~] grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
grep: /home/n7dr/.local/share/xorg/Xorg.[0-9]*.log: No such file or directory
[HN:~]
Doc
--
Web: http://enginehousebooks.com/drevans
signature.asc
De
Hi.
On Sat, 22 Jul 2017 11:48:42 -0600
"D. R. Evans" wrote:
> As my old thread has been hijacked, I thought that I'd better start a new one.
>
> Teemu Likonen wrote on 07/17/2017 03:09 PM:
> > D. R. Evans [2017-07-17 14:19:32-06] wrote:
> >
> >> Beginning a couple of weeks ago, I starte
Maybe try to add a file /etc/X11/xorg.conf (ask google, how it has to look),
and in it set the driver "nvidia".
Make sure, the nouveau kernel driver is blacklisted.
BTW: Is the proprietrary driver compatible with latest xserver-xorg again?
Best regards
Hans
> Thanks to people for their helpfu
As my old thread has been hijacked, I thought that I'd better start a new one.
Teemu Likonen wrote on 07/17/2017 03:09 PM:
> D. R. Evans [2017-07-17 14:19:32-06] wrote:
>
>> Beginning a couple of weeks ago, I started to experience occasional freezes
>> or
>> sudden blank screens on my 64-bit jess
18 matches
Mail list logo