On 04/27/2018 02:23 AM, Steve Litt wrote:
[snip]
> Not mentioned is which WM/DE is being used. Some WM/DEs are a crash
> waiting to happen. Why not temporarily use LXDE, and see whether that
> effects the frequency of the hang. If so, determine what about your
> former WM/DE was causing the problem
Am Freitag 27 April 2018 schrieb Florian Zieboll:
> Am 27. April 2018 15:27:46 MESZ schrieb Stefan Krusche
:
> > It's the default for the default distribution you are using, I think.
> > You can change that in /etc/apt/preference with pinning.
>
> Yeah, thanks - I was just wondering where this def
Am 27. April 2018 15:13:28 MESZ schrieb KatolaZ :
> it's determined in the repo config, and apt acquires this in formation
> from the Release files. In particular, if the following fields are
> present in the Release file of a suite:
>
> NotAutomatic: yes
> ButAutomaticUpgrades: yes
>
> then
Am 27. April 2018 15:27:46 MESZ schrieb Stefan Krusche
:
> It's the default for the default distribution you are using, I think.
> You can change that in /etc/apt/preference with pinning.
Yeah, thanks - I was just wondering where this default is defined, if not in
/etc/apt/preferences[.d/], a
Am Freitag 27 April 2018 schrieb Florian Zieboll:
> obviously I hit "send" too fast, as I couldn't find that configuration
> anywhere under "/etc/apt/". Where is this behavior defined, resp. how
> would I change it? (Just in case...)
It's the default for the default distribution you are using, I t
On Fri, Apr 27, 2018 at 02:24:36PM +0200, Florian Zieboll wrote:
> On Fri, 27 Apr 2018 14:13:15 +0200
> Florian Zieboll wrote:
>
> > On Fri, 27 Apr 2018 10:07:02 +0100
> > KatolaZ wrote:
> >
> > >
> > > Pinning should not be needed any more, since the *-backports suites
> > > are at prio 100 b
On 04/27/2018 02:23 AM, Steve Litt wrote:
[snip]
First thing I'd do is test the RAM and the disk. Easy to do, and it
would be real shame to chase your video driver tail for a month when
it was bad RAM. I'm pretty sure bad RAM can cause almost anything: Why
not rule it out early.
[snip]
Thanks
On Fri, 27 Apr 2018 14:13:15 +0200
Florian Zieboll wrote:
> On Fri, 27 Apr 2018 10:07:02 +0100
> KatolaZ wrote:
>
> >
> > Pinning should not be needed any more, since the *-backports suites
> > are at prio 100 by default (it was not like that in the past
> > though, I know...) while $codename.
On Fri, 27 Apr 2018 10:31:43 +0200
Florian Zieboll wrote:
> If you really want to have the "backports" version, in the worst case,
> you'll have to specify the needed version for every package in the
> dependency chain (...)
Hallo Lars,
in the meantime i remembered that there is also aptitude,
On Fri, 27 Apr 2018 10:07:02 +0100
KatolaZ wrote:
> On Fri, Apr 27, 2018 at 10:31:43AM +0200, Florian Zieboll wrote:
> >
> > On Thu, 26 Apr 2018 21:05:41 +0300
> > Lars Noodén wrote:
> >
> [...]
> >
> > Not sure if you are aware that your system tries to pull the package
> > from the "ba
On Fri, Apr 27, 2018 at 10:31:43AM +0200, Florian Zieboll wrote:
>
> On Thu, 26 Apr 2018 21:05:41 +0300
> Lars Noodén wrote:
>
> > # apt-cache show nvidia-driver-bin | head -n 3
> > Package: nvidia-driver-bin
> > Source: nvidia-graphics-drivers
> > Version: 390.48-2~bpo9+1
>
> Not sure if you a
On Thu, 26 Apr 2018 21:05:41 +0300
Lars Noodén wrote:
> # apt-cache show nvidia-driver-bin | head -n 3
> Package: nvidia-driver-bin
> Source: nvidia-graphics-drivers
> Version: 390.48-2~bpo9+1
Not sure if you are aware that your system tries to pull the package
from the "backports" repo... To a
On Thu, 26 Apr 2018 14:03:53 -0500
goli...@dyne.org wrote:
> On 2018-04-26 13:05, Lars Noodén wrote:
> > On 04/26/2018 08:34 PM, KatolaZ wrote:
> > [snip]> the drivers you get from Debian Stretch repos are exactly
> > the same
> >> drivers (bit-by-bit) that you get through Devuan ASCII repos.
On Thu, Apr 26, 2018 at 07:56:52PM +0200, J. Fahrner wrote:
> I can second this. I have long years of experience with Nvidia and Amd
> graphic cards under Linux, and I can say: the "free" drivers for these cards
> (made by reverse engeneering) can drive you mad. Use the proprietary drivers
> for th
On 2018-04-26 13:05, Lars Noodén wrote:
On 04/26/2018 08:34 PM, KatolaZ wrote:
[snip]> the drivers you get from Debian Stretch repos are exactly the
same
drivers (bit-by-bit) that you get through Devuan ASCII repos. And I
mean it. Whatever it is, it's indeed the very same package, really,
*the*
On 04/26/2018 01:05 PM, Lars Noodén wrote:
On 04/26/2018 08:42 PM, Florian Zieboll wrote:
[snip]
in one of your previous mails you pasted the output of your attempt to
install the "nvidia-driver" package. If you follow down the dependency
chain by manually trying to install the "not installabl
Lars Noodén wrote on 26.04.2018 20:05:
> Package nvidia-installer-cleanup is not available, but is referred to by
> another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> E: Package 'nvidia-installer-cleanup' has no installa
On Thu, Apr 26, 2018 at 09:05:41PM +0300, Lars Noodén wrote:
> On 04/26/2018 08:42 PM, Florian Zieboll wrote:
> [snip]
> > in one of your previous mails you pasted the output of your attempt to
> > install the "nvidia-driver" package. If you follow down the dependency
> > chain by manually trying t
On 04/26/2018 08:42 PM, Florian Zieboll wrote:
[snip]
> in one of your previous mails you pasted the output of your attempt to
> install the "nvidia-driver" package. If you follow down the dependency
> chain by manually trying to install the "not installable" predepends,
> sooner or later you'll re
On 04/26/2018 08:34 PM, KatolaZ wrote:
[snip]> the drivers you get from Debian Stretch repos are exactly the same
> drivers (bit-by-bit) that you get through Devuan ASCII repos. And I
> mean it. Whatever it is, it's indeed the very same package, really,
> *the* *very* *same* *package*.
[snip]
Ok
Am 2018-04-26 19:34, schrieb KatolaZ:
the drivers you get from Debian Stretch repos are exactly the same
drivers (bit-by-bit) that you get through Devuan ASCII repos. And I
mean it. Whatever it is, it's indeed the very same package, really,
*the* *very* *same* *package*.
Your problem looks like
On Thu, 26 Apr 2018 19:51:47 +0300
Lars Noodén wrote:
> I suspect that if I could figure out 1) the appropriate drivers, and
> 2) how to get them from Debian, that would be the solution.
Hallo Lars,
in one of your previous mails you pasted the output of your attempt to
install the "nvidia-dri
On Thu, Apr 26, 2018 at 07:51:47PM +0300, Lars Noodén wrote:
> On 04/26/2018 06:37 PM, Steve Litt wrote:
> > On Thu, 26 Apr 2018 06:36:14 +0300
> > Lars Noodén wrote:
> [snip]
> >> Looking at the task manager in XCFE and top in the shell, the RAM and
> >> swap usage eventually start to climb more
On 04/26/2018 06:37 PM, Steve Litt wrote:
> On Thu, 26 Apr 2018 06:36:14 +0300
> Lars Noodén wrote:
[snip]
>> Looking at the task manager in XCFE and top in the shell, the RAM and
>> swap usage eventually start to climb more and more rapidly until >99%
>> of RAM is in use and >99% of swap. Then t
On Thu, 26 Apr 2018 06:36:14 +0300
Lars Noodén wrote:
> On 01/15/2018 06:13 PM, Chillfan wrote:
> [snip]
> > Try with the official NVIDIA drivers and see what happens.
> >
> > https://wiki.debian.org/NvidiaGraphicsDrivers
>
> Thanks. I've been unable to install the driver. Would I have to g
On Thu, 26 Apr 2018 06:36:14 +0300, Lars wrote in message
<47850509-8a3c-3d51-ed44-f0416e372...@gmail.com>:
> On 01/15/2018 06:13 PM, Chillfan wrote:
> [snip]
> > Try with the official NVIDIA drivers and see what happens.
> >
> > https://wiki.debian.org/NvidiaGraphicsDrivers
..does your machi
On 04/21/2018 09:56 PM, Arnt Karlsen wrote:
> On Sat, 21 Apr 2018 20:37:24 +0300, Lars wrote in message
> :
>
>> On 04/21/2018 08:17 PM, Arnt Karlsen wrote:
>> [snip]
>>> ..you have 2 video cards fighting each other for access to your
>>> screen hw??? Choose one, I recommend nouveau on your GM1
On 01/15/2018 06:13 PM, Chillfan wrote:
[snip]
> Try with the official NVIDIA drivers and see what happens.
>
> https://wiki.debian.org/NvidiaGraphicsDrivers
Thanks. I've been unable to install the driver. Would I have to get
that straight from Debian? See below for the missing dependencies.
On Sat, 21 Apr 2018 20:37:24 +0300, Lars wrote in message
:
> On 04/21/2018 08:17 PM, Arnt Karlsen wrote:
> [snip]
> > ..you have 2 video cards fighting each other for access to your
> > screen hw??? Choose one, I recommend nouveau on your GM108M.
>
> Thanks. I thought that was sorted autom
On 04/21/2018 08:17 PM, Arnt Karlsen wrote:
[snip]
> ..you have 2 video cards fighting each other for access to your
> screen hw??? Choose one, I recommend nouveau on your GM108M.
Thanks. I thought that was sorted automatically. What do I need to set
to prioritize one over the other?
/Lars
_
On Sat, 21 Apr 2018 11:29:36 +0300, Lars wrote in message
<4be922af-f137-8de8-5337-ee846cd59...@gmail.com>:
> I'm still getting freezes nearly daily. Some are temporary and last
> only a few seconds and then let up. The ones that last longer
> eventually freeze also the mouse pointer and then t
I'm still getting freezes nearly daily. Some are temporary and last
only a few seconds and then let up. The ones that last longer
eventually freeze also the mouse pointer and then the entire machine.
$ lsb_release -rd
Description:Devuan GNU/Linux 2.0 (ascii)
Release:2.0
I have the l
What hardware are you using?
I suspect the problem is with the nouveau driver, I had issues like this with
my graphics card until reclocking support was finished.
Nouveau has limited support for some of the newer cards (pascal if I remember)
because nvidia hasn't released the signed firmware ye
I have some new hardware that locks up a lot with Ascii. Sometimes it
happens on its own, other times it seems it can be triggered by going to
the console (ctrl-alt-f1 for example) and back to the X session
(ctrl-alt-f7). Any suggestions about how to diagnose or fix or work
around this? I'm not
34 matches
Mail list logo