On 08/13/18 13:14, Corentin �Nado� Pazdera wrote:
> August 13, 2018 6:58 PM, "james" wrote:
>
>> Here's what I got running your script::
>>
>> /etc # /root/profile-explorer.sh
>> --- Invalid atom in /etc/portage/package.use/explored-packages:
>> /usr/portage/profiles/base/packages
>> ---
On 08/15 08:13, Nikos Chantziaras wrote:
> On 15/08/18 18:45, tu...@posteo.de wrote:
> >
> > I put nvidia-uvm explictly into /etc/conf.d/modules - which was not
> > necessary ever beforeand it shows the same problems: No cuda
> > devices.
> >
> > I think I will dream this night of no cuda
On 15/08/18 18:45, tu...@posteo.de wrote:
I put nvidia-uvm explictly into /etc/conf.d/modules - which was not
necessary ever beforeand it shows the same problems: No cuda
devices.
I think I will dream this night of no cuda devices... ;(
Or you might want to use the LTS (Long Term
August 15, 2018 5:45 PM, tu...@posteo.de wrote:
> I put nvidia-uvm explictly into /etc/conf.d/modules - which was not
> necessary ever beforeand it shows the same problems: No cuda
> devices.
>
> I think I will dream this night of no cuda devices... ;(
>
> On 08/15 05:11, tu...@posteo.de
I put nvidia-uvm explictly into /etc/conf.d/modules - which was not
necessary ever beforeand it shows the same problems: No cuda
devices.
I think I will dream this night of no cuda devices... ;(
On 08/15 05:11, tu...@posteo.de wrote:
> On 08/15 02:32, Corentin “Nado” Pazdera wrote:
> >
On Wednesday, 15 August 2018 12:45:05 BST Franz Fellner wrote:
> I think that's the way "equery w" works:
> >> Display the path to the ebuild that would be used by Portage with the
>
> current configuration. <<
> With your current configuration there is no package matching your query.
>
>
On 08/15 02:32, Corentin “Nado” Pazdera wrote:
> August 15, 2018 2:59 PM, tu...@posteo.de wrote:
>
> > Yes I did reboot the sustem. In my initial mail I mentioned a tool
> > called CUDA-Z and Blender, which both reports a missing CUDA device.
>
> Ok, so you do not have a specific error which
August 15, 2018 2:59 PM, tu...@posteo.de wrote:
> Yes I did reboot the sustem. In my initial mail I mentioned a tool
> called CUDA-Z and Blender, which both reports a missing CUDA device.
Ok, so you do not have a specific error which might have been thrown by the
module?
Other ideas, check
On 08/15 12:45, Corentin “Nado” Pazdera wrote:
> August 15, 2018 2:02 PM, tu...@posteo.de wrote:
> > ...sorry, I am no native speaker...I dont understand.
> >
> > I did not know how to disable CUDA on both cards.
> > So...since it works perfectly with the old driver I would think:
> > No, CUDA is
On 08/15 03:35, Nikos Chantziaras wrote:
> On 15/08/18 15:02, tu...@posteo.de wrote:
> > Then I do an "emerge " and CUDA stops
> > working. I do not change anything else nor do I know, who/what could
> > disable CUDA on both cards ... except for the driver itsself.
>
> Dumb question, but just to
August 15, 2018 2:02 PM, tu...@posteo.de wrote:
> ...sorry, I am no native speaker...I dont understand.
>
> I did not know how to disable CUDA on both cards.
> So...since it works perfectly with the old driver I would think:
> No, CUDA is enabled (or at least the old driver does this for me).
>
On 15/08/18 15:02, tu...@posteo.de wrote:
Then I do an "emerge " and CUDA stops
working. I do not change anything else nor do I know, who/what could
disable CUDA on both cards ... except for the driver itsself.
Dumb question, but just to be sure: did you reboot after upgrading the
driver? The
On 2018-08-15, Peter Humphrey wrote:
> Hello list,
>
> While trying to get a USB printer recognised on an Atom box, I found this,
> immediately after emerge --sync && eix-update:
>
> (atom) peak / # eix -c kyocera
> [N] net-print/kyocera-1x2x-mfp-driver (--): Printer descriptions (PPDs) and
>
On 08/15 11:39, Corentin “Nado” Pazdera wrote:
> August 15, 2018 1:16 PM, tu...@posteo.de wrote:
>
> > The wiki-page is old...it speaks of nvidia-driver-174.
>
> Yeah, for legacy cards... If you check the history its also been updated
> quite frequently.
>
> > modprobe.d/nvidia.conf:
> >
I think that's the way "equery w" works:
>> Display the path to the ebuild that would be used by Portage with the
current configuration. <<
With your current configuration there is no package matching your query.
Alternatives for future use in such cases:
❯ epkginfo -k kyocera-1x2x-mfp-driver
*
August 15, 2018 1:16 PM, tu...@posteo.de wrote:
> The wiki-page is old...it speaks of nvidia-driver-174.
Yeah, for legacy cards... If you check the history its also been updated quite
frequently.
> modprobe.d/nvidia.conf:
>
> # Nvidia drivers support
> alias
On 08/15 10:33, Corentin “Nado” Pazdera wrote:
> August 15, 2018 4:19 AM, tu...@posteo.de wrote:
>
> > On 08/14 11:16, Nikos Chantziaras wrote:
> >
> >> On 14/08/18 13:35, tu...@posteo.de wrote:
> >> Hi,
> >>
> >> after upgrading to nvidia-drivers-396.51 no CUDA devices were found.
> >> Last
On Wed, 15 Aug 2018 02:45:20 -0400,
J. Roeleveld wrote:
>
> On Tuesday, August 14, 2018 10:52:30 PM CEST John Covici wrote:
> > On Tue, 14 Aug 2018 16:06:21 -0400,
> >
> > J. Roeleveld wrote:
> > > On August 14, 2018 11:42:18 AM UTC, John Covici
> wrote:
> > > >I use sanoid/syncoid to back up
August 15, 2018 4:19 AM, tu...@posteo.de wrote:
> On 08/14 11:16, Nikos Chantziaras wrote:
>
>> On 14/08/18 13:35, tu...@posteo.de wrote:
>> Hi,
>>
>> after upgrading to nvidia-drivers-396.51 no CUDA devices were found.
>> Last version, which works for me is nvidia-drivers-396.24-r1.
>>
>> Do
On 15 August 2018 at 11:22, Peter Humphrey wrote:
> On Wednesday, 15 August 2018 09:50:09 BST Franz Fellner wrote:
> (atom) peak / # equery w net-print/kyocera-1x2x-mfp-driver
>
> Something does seem to be, if not broken, somewhat bent.
That seems to be correct. equery w takes your configuration
On Wednesday, 15 August 2018 09:50:09 BST Franz Fellner wrote:
>
> Am Mi., 15. Aug. 2018 um 11:29 Uhr schrieb Peter Humphrey <
>
> pe...@prh.myzen.co.uk>:
> > Hello list,
> >
> > While trying to get a USB printer recognised on an Atom box, I found
> > this, immediately after emerge --sync &&
On Wed, 15 Aug 2018 08:53:03 +0100, Peter Humphrey wrote:
> > ISTR something about not setting USB_PRINTER in the kernel config, but
> > it's been a while since I used a USB printer. When I did, it was on a
> > headless box.
>
> Yes, I knew about the kernel printer support being obsolete, and
It's ~amd64 only. So if you get missing keyword, could it be you are on x86?
Am Mi., 15. Aug. 2018 um 11:29 Uhr schrieb Peter Humphrey <
pe...@prh.myzen.co.uk>:
> Hello list,
>
> While trying to get a USB printer recognised on an Atom box, I found this,
> immediately after emerge --sync &&
Hello list,
While trying to get a USB printer recognised on an Atom box, I found this,
immediately after emerge --sync && eix-update:
(atom) peak / # eix -c kyocera
[N] net-print/kyocera-1x2x-mfp-driver (--): Printer descriptions (PPDs) and
filters for Kyocera 1x2x MFP
[N]
On Tuesday, 14 August 2018 17:32:47 BST Neil Bothwick wrote:
> On Tue, 14 Aug 2018 15:24:48 +0100, Peter Humphrey wrote:
> > My problem is that, even though the system detects the printer being
> > connected, cups can't see it. I've tried everything I can think of so
> > I'm now hoping that
On Tuesday, August 14, 2018 10:52:30 PM CEST John Covici wrote:
> On Tue, 14 Aug 2018 16:06:21 -0400,
>
> J. Roeleveld wrote:
> > On August 14, 2018 11:42:18 AM UTC, John Covici
wrote:
> > >I use sanoid/syncoid to back up using zfs. Its great, keeps snapshots
> > >for as long as I want them (I
26 matches
Mail list logo
