Neil Bothwick wrote:
> On Fri, 21 Apr 2023 09:55:24 -0500, Dale wrote:
>
Also, I switch to the current kernel, it failed in the same way. It
isn't just the new kernel, it seems to be any of them. I wonder how
hard it is to switch to that other driver. From the wiki page, it
l
On Fri, 21 Apr 2023 09:55:24 -0500, Dale wrote:
> >> Also, I switch to the current kernel, it failed in the same way. It
> >> isn't just the new kernel, it seems to be any of them. I wonder how
> >> hard it is to switch to that other driver. From the wiki page, it
> >> looks like a big deal.
Dr Rainer Woitok wrote:
> Dale,
>
> On Thursday, 2023-04-20 17:36:23 -0500, you wrote:
>
>> ...
>> * Package: x11-drivers/nvidia-drivers-470.182.03:0/470
>> * Repository: mine
> Maybe I'm missing something, but as of today "x11-drivers/nvidia-dri-
> vers" version 470.182.03 is still in the n
Arve Barsnes wrote:
> On Fri, 21 Apr 2023 at 11:55, Dale wrote:
>> Did something change with overlays? In the past, I copied the ebuild
>> over to local overlay and ran the ebuild command for the manifest. It
>> downloaded everything that was needed. Now, it seems it doesn't. They
>> add a ste
Neil Bothwick wrote:
> On Fri, 21 Apr 2023 03:58:11 -0500, Dale wrote:
>
>> I did a emerge -ef nvidia-drivers and it still fails. I was hoping that
>> would pick up the needed files. Guess not. I decided to do some more
>> digging. I noticed that the same version is still in the tree. I
>> cop
Neil Bothwick wrote:
> On Thu, 20 Apr 2023 20:33:22 -0500, Dale wrote:
>
>> Also, I switch to the current kernel, it failed in the same way. It
>> isn't just the new kernel, it seems to be any of them. I wonder how
>> hard it is to switch to that other driver. From the wiki page, it looks
>> lik
On Thu, 20 Apr 2023 20:33:22 -0500, Dale wrote:
> Also, I switch to the current kernel, it failed in the same way. It
> isn't just the new kernel, it seems to be any of them. I wonder how
> hard it is to switch to that other driver. From the wiki page, it looks
> like a big deal.
Not really,
On Fri, 21 Apr 2023 03:58:11 -0500, Dale wrote:
> I did a emerge -ef nvidia-drivers and it still fails. I was hoping that
> would pick up the needed files. Guess not. I decided to do some more
> digging. I noticed that the same version is still in the tree. I
> copied the ebuild a while back
On Thu, Apr 20, 2023 at 05:36:23PM -0500, Dale wrote:
> /var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch:
> No such file or directory
This sounds like you copied the ebuild to your local overlay but not
the files/ dir which includes the patch. So
Dale,
On Thursday, 2023-04-20 17:36:23 -0500, you wrote:
> ...
> * Package: x11-drivers/nvidia-drivers-470.182.03:0/470
> * Repository: mine
Maybe I'm missing something, but as of today "x11-drivers/nvidia-dri-
vers" version 470.182.03 is still in the normal Gentoo tree. So why use
your
On Fri, 21 Apr 2023 at 11:55, Dale wrote:
> Did something change with overlays? In the past, I copied the ebuild
> over to local overlay and ran the ebuild command for the manifest. It
> downloaded everything that was needed. Now, it seems it doesn't. They
> add a step? I miss a step that sli
Arve Barsnes wrote:
> On Fri, 21 Apr 2023 at 10:58, Dale wrote:
>> I put my local ebuilds in /usr/local/portage. Obviously emerge sees it
>> since it was trying to use it. I don't understand why it doesn't work
>> tho. I looked at the ebuild in the tree and my overlay, they look the
>> same, in
On Fri, 21 Apr 2023 at 10:58, Dale wrote:
> I put my local ebuilds in /usr/local/portage. Obviously emerge sees it
> since it was trying to use it. I don't understand why it doesn't work
> tho. I looked at the ebuild in the tree and my overlay, they look the
> same, including the patches from d
Frank Steinmetzger wrote:
> Am Thu, Apr 20, 2023 at 08:33:22PM -0500 schrieb Dale:
>
>> I cleared the tmp files to give it a fresh start. It still failed. The
>> directory and files it complains about being missing, they are. I went
>> to the ebuild to see what patches are supposed to be install
Am Thu, Apr 20, 2023 at 08:33:22PM -0500 schrieb Dale:
> I cleared the tmp files to give it a fresh start. It still failed. The
> directory and files it complains about being missing, they are. I went
> to the ebuild to see what patches are supposed to be installed. This is
> the part of the e
Morgan Wesström wrote:
> On 2023-04-21 00:36, Dale wrote:
>> /var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/temp/environment:
>> line 1291:
>> /var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch:
>>
>> No such file or directory
>>
>> Any thou
On 2023-04-21 00:36, Dale wrote:
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/temp/environment:
line 1291:
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch:
No such file or directory
Any thoughts? Ideas?
I couldn't reproduce the e
On Thu, Apr 20, 2023 at 3:36 PM Dale wrote:
> * patch -p1 failed with
>
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch
You know I don't run Gentoo, right?
That looks weird to me - building 470.182.03 but patching it with
470.141.03.
Jus
Howdy,
I tried a while back to upgrade my kernel but nvidia didn't like it.
Given I can do this a piece at a time, I thought I'd try again. Kernel
compiled fine and when nvidia complained about missing options, I fixed
those and recompiled the kernel. I finally got it happy as far as
missing ke
Howdy,
A while back during my routine upgrades, I got a update to
nvidia-drivers. I went from nvidia-drivers-470.129.06 to
nvidia-drivers-470.141.03. Since then, I'm having trouble getting
screen 2 to stay on. When I turn the TV on, it disables screen 2 which
makes TV 2 not have a signal. I en
Arve Barsnes wrote:
> On Sun, 13 Feb 2022 at 14:12, Dale wrote:
>> I suspect Kicad is not used by most but removing digikam seemed to be
>> the one that opened the door to a clear path for emerge. That package
>> is commonly used. So, that info may help if a person runs into this.
>> I'm not sur
On Sun, 13 Feb 2022 at 14:12, Dale wrote:
> I suspect Kicad is not used by most but removing digikam seemed to be
> the one that opened the door to a clear path for emerge. That package
> is commonly used. So, that info may help if a person runs into this.
> I'm not sure what if any effect boost
Arve Barsnes wrote:
> On Sun, 13 Feb 2022 at 09:43, Dale wrote:
>> The following USE changes are necessary to proceed:
>> (see "package.use" in the portage(5) man page for more details)
>> # required by sci-libs/vtk-9.0.3-r4::gentoo[video_cards_nvidia]
>> # required by sci-libs/opencascade-7.5.2-
On Sun, 13 Feb 2022 at 09:43, Dale wrote:
> The following USE changes are necessary to proceed:
> (see "package.use" in the portage(5) man page for more details)
> # required by sci-libs/vtk-9.0.3-r4::gentoo[video_cards_nvidia]
> # required by sci-libs/opencascade-7.5.2-r5::gentoo[vtk]
> # requir
Howdy,
I recently did my weekly updates. It wanted nvidia-drivers to have the
static-libs USE flag enabled so I did it. Then the video card wouldn't
work when I logged out and back in because of a mismatch somewhere so I
disabled static-libs and emerged it again. That fixed the problem of no
GU
On 21/05/2020 20:25, Ashley Dixon wrote:
On Thu, May 21, 2020 at 08:13:38PM +0100, Ján Zahornadský wrote:
when updating the system today, a new revision of nvidia-drivers ebuild
fails with
ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf are
On 21/05/2020 20:25, Ashley Dixon wrote:
On Thu, May 21, 2020 at 08:13:38PM +0100, Ján Zahornadský wrote:
when updating the system today, a new revision of nvidia-drivers ebuild
fails with
ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf are m
On Thu, May 21, 2020 at 08:13:38PM +0100, Ján Zahornadský wrote:
> when updating the system today, a new revision of nvidia-drivers ebuild
> fails with
>
> ERROR: Kernel configuration is invalid.
>include/generated/autoconf.h or include/config/auto.conf are missing.
>Run 'make oldconfig &&
On Thu, May 21, 2020 at 12:14 PM Ján Zahornadský wrote:
>
> bolt /usr/src/linux-5.6.14-gentoo # ls -l include/generated/autoconf.h
> include/config/auto.conf
> -rw--- 1 root root 26144 May 21 10:13 include/config/auto.conf
> -rw--- 1 root root 35329 May 21 10:13 include/generated/autoconf
180709 Davyd McColl wrote:
> 180610 Philip Webb wrote:
>> I updated to the latest stable Nvidia-drivers-396.24-r1 ,
>> rebooted & 'startx' :
>> the result was an X error "No devices detected ... no screens found".
>> I updated to kernel 4.14.52-gentoo & tried Nvidia-drivers as above
>> with the sam
I have exactly the same kernel (4.14.52-gentoo) and nvidia-drivers
(396.24-r1) and I don't experience this issue (though games requiring
Vulkan crash out sporadically - there's an ongoing issue on the nvidia
forums for this, where apparently it's already been fixed in some ancient
fork, and not
On 2018.07.08 18:46, Philip Webb wrote:
180610 Philip Webb wrote:
> I updated to the latest stable Nvidia-drivers-396.24-r1 ,
> rebooted & 'startx' :
> the result was an X error "No devices detected ... no screens
found".
> Downgrading to 390.48 got X working again.
> Nothing to see on the For
180610 Philip Webb wrote:
> I updated to the latest stable Nvidia-drivers-396.24-r1 ,
> rebooted & 'startx' :
> the result was an X error "No devices detected ... no screens found".
> Downgrading to 390.48 got X working again.
> Nothing to see on the Forum or among Gentoo 'nvidia' bugs.
> My kernel
On 18-06-09 10:22 PM, Philip Webb wrote:
I updated to the latest stable Nvidia-drivers-396.24-r1 ,
rebooted & 'startx' :
the result was an X error "No devices detected ... no screens found".
Downgrading to 390.48 got X working again.
Nothing to see on the Forum or among Gentoo 'nvidia' bugs.
My k
I updated to the latest stable Nvidia-drivers-396.24-r1 ,
rebooted & 'startx' :
the result was an X error "No devices detected ... no screens found".
Downgrading to 390.48 got X working again.
Nothing to see on the Forum or among Gentoo 'nvidia' bugs.
My kernel is 4.9.16-gentoo.
Has anyone else ru
Some time around when Spectre/Meltdown were announced, I started
experiencing similar problems. I don't know "what's wrong" because so
far I have found no answers.
The best I can offer at this point is that on my system, it seems that
it will work with Nouveau drivers much better than the system
Gentlemen, we have a problem...
Okay, ~ a week ago there was a power outage at my place, everything goes
down for a day or two. I had recently refreshed my UPS batteries, so I
had a chance to put that into the circuit, no biggy.
Since nobody will offer me a job, I was playing Kerbal space program
Am Mittwoch, 5. April 2017, 18:53:43 CEST schrieb Alan Grimes:
> I hit the "view raw" link and used save as... I then copied it into the
> "files" subdirectoy and portage threw a hissy fit
Please re-read the instructions in Fabio's mail.
--
Andreas K. Hüttel
dilfri...@gentoo.org
Gentoo Linux de
On Wed, 05 Apr 2017 12:53:43 -0400, Alan Grimes wrote:
> I hit the "view raw" link and used save as... I then copied it into the
> "files" subdirectoy and portage threw a hissy fit and refused to do
> anything because letting the user patch a package is simply
> unthinkable!!! A mere USER, applyin
On Wed, Apr 5, 2017 at 9:53 AM, Alan Grimes wrote:
> I hit the "view raw" link and used save as... I then copied it into the
> "files" subdirectoy and portage threw a hissy fit and refused to do
> anything because letting the user patch a package is simply
> unthinkable!!! A mere USER, applying a
I hit the "view raw" link and used save as... I then copied it into the
"files" subdirectoy and portage threw a hissy fit and refused to do
anything because letting the user patch a package is simply
unthinkable!!! A mere USER, applying a custom patch to one of our
immaculate packages on HIS OWN CO
You can drop it in /etc/portage/patches/x11-drivers/nvidia-drivers folder,
portage should take care of the rest when you emerge the package. You
should see 3 lines near the prepare phase, before the configure phase,
saying something like "applying user patches from... Applying
...Done applying user
Looks like a good patch but can you link to instructions for applying
this patch?
Fabio Scaccabarozzi wrote:
>
> Hi Alan,
>
> That is expected with 4.10 kernels.
> You can grab a patch from my /etc/portage repository:
> https://github.com/fsvm88/gentoo-portage_etc/blob/master/patches/x11-drivers/
Hi Alan,
That is expected with 4.10 kernels.
You can grab a patch from my /etc/portage repository:
https://github.com/fsvm88/gentoo-portage_etc/blob/master/patches/x11-drivers/nvidia-drivers/378.09-4.10-rc8.patch
I took it from the NVidia forums, you can also find it there, I just
rebased it for
I'm still running on my old kernel as I re-build my system, Nvidia
drivers just barfed
###
tortoise src # ls -l
total 12
lrwxrwxrwx 1 root root 13 Apr 5 09:50 linux -> linux-4.10.8/
drwxr-xr-x 25 root root 4096 Apr 5 10:01 linux-4.10.8
drwxrwxr-x 25 root root 4096 Apr
This was discussed on the forum but I did not see it here: recent nvidia-drivers update on
~amd64 require tens of new abi_x86_32 use flag additions for all kinds of packages.
https://bugs.gentoo.org/show_bug.cgi?id=605664
The suggested workaround (build nvidia-drivers with -tools) worked for me
Hello Meino,
On Sat, 30 Jul 2016, meino.cra...@gmx.de wrote:
[..]
>WHOW! Thanks a lot for the patch!
As this issue has just come up on gentoo-dev as well, has the patch
worked for you (so far)? Please give a report if it worked or not.
I've been unable to run/test my system with that patch for l
Hello,
On Sat, 30 Jul 2016, meino.cra...@gmx.de wrote:
>David Haller [16-07-30 13:24]:
[..]
>> I've got it working with the attached patch in
>> /etc/portage/patches/x11-drivers/nvidia-drivers-367.35/
[..]
>Short qyestion: How can I apply it...I mean...as soon as I do an
>emerge, either the origi
james [16-07-30 20:52]:
> On 07/30/2016 01:15 PM, meino.cra...@gmx.de wrote:
>
> >>>Short qyestion: How can I apply it...I mean...as soon as I do an
> >>>emerge, either the original source will be unpacked or my package
> >>>will be rejected for being modified an different from the one, which
> >
On 07/30/2016 01:15 PM, meino.cra...@gmx.de wrote:
Short qyestion: How can I apply it...I mean...as soon as I do an
emerge, either the original source will be unpacked or my package
will be rejected for being modified an different from the one, which
does not compile...
http://tinyurl.com/jur
Andrew Lowe [16-07-30 20:12]:
> On 31/07/2016 1:54 AM, meino.cra...@gmx.de wrote:
> >David Haller [16-07-30 13:24]:
> >>Hello,
> >>
> >>On Sat, 30 Jul 2016, meino.cra...@gmx.de wrote:
> >>>trying the new kernel linux-4.7 (vanilla, downloaded from
>
> [snip]
>
> >
> >Short qyestion: How can I ap
On 31/07/2016 1:54 AM, meino.cra...@gmx.de wrote:
David Haller [16-07-30 13:24]:
Hello,
On Sat, 30 Jul 2016, meino.cra...@gmx.de wrote:
trying the new kernel linux-4.7 (vanilla, downloaded from
[snip]
Short qyestion: How can I apply it...I mean...as soon as I do an
emerge, either the ori
David Haller [16-07-30 13:24]:
> Hello,
>
> On Sat, 30 Jul 2016, meino.cra...@gmx.de wrote:
> >trying the new kernel linux-4.7 (vanilla, downloaded from
> >ftp.kernel.org) with nvidia drivers
> >(Installed versions: 367.35-r1^md(03:00:46 07/30/16)(X driver kms
> >multilib uvm -acpi -compat -gtk
Hello,
On Sat, 30 Jul 2016, meino.cra...@gmx.de wrote:
>trying the new kernel linux-4.7 (vanilla, downloaded from
>ftp.kernel.org) with nvidia drivers
>(Installed versions: 367.35-r1^md(03:00:46 07/30/16)(X driver kms
>multilib uvm -acpi -compat -gtk3 -pax_kernel -static-libs -tools
>-wayland KE
Andrew Lowe [16-07-30 08:44]:
> On 30/07/16 14:09, meino.cra...@gmx.de wrote:
> >Hi,
> >
> >thank you for your reply ! :)
> >I have to use the nvidia drivers, because I am using Blender, which
> >renders via CUDA on the GPU...
> >
> >Best regards
> >Meino
> >
> >
> >
> >
> >Jigme Datse Yli-RAsk
On 30/07/16 14:09, meino.cra...@gmx.de wrote:
Hi,
thank you for your reply ! :)
I have to use the nvidia drivers, because I am using Blender, which
renders via CUDA on the GPU...
Best regards
Meino
Jigme Datse Yli-RAsku [16-07-30 08:04]:
I have an earlier version of the x11-drivers/nvidia
Hi,
thank you for your reply ! :)
I have to use the nvidia drivers, because I am using Blender, which
renders via CUDA on the GPU...
Best regards
Meino
Jigme Datse Yli-RAsku [16-07-30 08:04]:
> I have an earlier version of the x11-drivers/nvidia-drivers installed
> (361.28), but if I recall
I have an earlier version of the x11-drivers/nvidia-drivers installed (361.28),
but if I recall, I couldn't get x11 to use them. Or maybe they are already
using them, but I don't know it (but I believe I couldn't get the tools to
recognize that they were being used). My understanding is that u
Hi,
trying the new kernel linux-4.7 (vanilla, downloaded from
ftp.kernel.org) with nvidia drivers
(Installed versions: 367.35-r1^md(03:00:46 07/30/16)(X driver kms
multilib uvm -acpi -compat -gtk3 -pax_kernel -static-libs -tools
-wayland KERNEL="linux -FreeBSD")).
The kernel compiled fine, the n
2016-04-30 17:41 GMT+02:00 Jacques Montier :
> 2016-04-30 15:25 GMT+02:00 Neil Bothwick :
>
>> On Sat, 30 Apr 2016 14:01:12 +0200, Jacques Montier wrote:
>>
>> > You can get the complete log in the attached file
>> > x11-drivers:nvidia-drivers-340.76:20160430-104727.log
>>
>> Which ends with
>>
>>
On Sat, 30 Apr 2016 14:01:12 +0200, Jacques Montier wrote:
> You can get the complete log in the attached file
> x11-drivers:nvidia-drivers-340.76:20160430-104727.log
Which ends with
!!! User patches were applied to this build!
Are you applying your own patches? Do you have anything
in /etc/po
On 30/04/2016 12:52, Jacques Montier wrote:
> Hello all,
>
> I need nvidia-drivers-340.76 for my Nvidia GeForce GT240 graphic card.
> I use nvidia-drivers-340.76 from a local overlay with the
> nvidia-drivers-340-76-kernel-4.0.patch which works fine with
> gentoo-sources-4.1.15-r1.
> I would like
Hello all,
I need nvidia-drivers-340.76 for my Nvidia GeForce GT240 graphic card.
I use nvidia-drivers-340.76 from a local overlay with the
nvidia-drivers-340-76-kernel-4.0.patch which works fine with
gentoo-sources-4.1.15-r1.
I would like to upgrade to the 4.4.6 kernel.
Unfortunately, nvidia-driv
On Tue, 9 Feb 2016 11:00:07 +0300, Andrew Savchenko wrote:
> > > The idea is that users should ping developers with appropriate bug
> > > reports.
> >
> > Instead, they ask in here or on the forums. Shouldn't the devs see
> > such messages anyway and already be aware of the need to update the
>
On Mon, 1 Feb 2016 10:00:40 + Neil Bothwick wrote:
> On Mon, 1 Feb 2016 12:38:45 +0300, Andrew Savchenko wrote:
>
> > > It's nothing to worry about, deprecated only mean is will be broken at
> > > some time in the future, it still works for now. IMO ebuild QA
> > > messages like this should no
On Mon, 1 Feb 2016 05:04:14 -0500 Philip Webb wrote:
> 160201 Andrew Savchenko wrote:
> > On Mon, 1 Feb 2016 09:03:50 + Neil Bothwick wrote:
> >> On Mon, 1 Feb 2016 05:56:37 +0100, meino.cra...@gmx.de wrote:
> >>> Switching to nvidia OpenCL interface... done
> >>> * x11-drivers/nvidia-drivers
160201 Andrew Savchenko wrote:
> On Mon, 1 Feb 2016 09:03:50 + Neil Bothwick wrote:
>> On Mon, 1 Feb 2016 05:56:37 +0100, meino.cra...@gmx.de wrote:
>>> Switching to nvidia OpenCL interface... done
>>> * x11-drivers/nvidia-drivers is using the deprecated
>>> readme.gentoo.eclass.<<>>
>>>
On Mon, 1 Feb 2016 12:38:45 +0300, Andrew Savchenko wrote:
> > It's nothing to worry about, deprecated only mean is will be broken at
> > some time in the future, it still works for now. IMO ebuild QA
> > messages like this should not be shown to users.
>
> The idea is that users should ping de
On Mon, 1 Feb 2016 09:03:50 + Neil Bothwick wrote:
> On Mon, 1 Feb 2016 05:56:37 +0100, meino.cra...@gmx.de wrote:
>
> > Switching to nvidia OpenCL interface... done
> > * x11-drivers/nvidia-drivers is using the deprecated
> > readme.gentoo.eclass.<<>>
> > * Please use readme.gentoo-r1 i
On Mon, 1 Feb 2016 05:56:37 +0100, meino.cra...@gmx.de wrote:
> Switching to nvidia OpenCL interface... done
> * x11-drivers/nvidia-drivers is using the deprecated
> readme.gentoo.eclass.<<>>
> * Please use readme.gentoo-r1 instead.
> What does the marked line implies? This is an outdated r
hi,
ths morning brings an update to the nividia-drivers, whch where
successfully emerged and installed. Right at the end of this process
this was prointed on the console:
* Removing x11-drivers/nvidia-drivers-361.18-r2 from moduledb.
Switching to nvidia OpenGL interface... done
>>> Regenerating
Hi all,
Because of an old graphic card, i have to compile nvidia-drivers-340.76.
nvidia-drivers-340.76 does not compile with the new 4.0.5 kernel.
Here is the output error :
/var/tmp/portage/x11-drivers/nvidia-drivers-340.76/work/kernel/nv-pat.o]
Error 1
I saw a topic about that problem on Gentoo
131214 »Q« wrote:
> It looks to me as if the removal of nvidia-drivers-325.15 was a mistake
> I run mostly stable amd64.
> I *think* 325.15 was the latest stable
[I] x11-drivers/nvidia-drivers
Available versions: 96.43.23^msd 173.14.39^msd 304.116^msd ~304.117^msd
319.76^msd 331.20^msd {+
It looks to me as if the removal of nvidia-drivers-325.15 was a
mistake, but I've got a lot going on in the meat world right now, and I
don't want to file a bug if I've simply gotten confused.
I run mostly stable amd64. I have 325.15 installed, and nothing
regarding nvidia-drivers in /etc/portage
Hi there,
When I start X (or start kdm), I get a segmentation fault and no X.
The Xorg-log says:
[ 8675.702] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 8675.702] (==) NVIDIA(0): RGB weight 888
[ 8675.702] (==) NVIDIA(0): Default visual is TrueColor
[ 8675.702] (==) NVIDIA(0): Using g
Paul Hartman wrote:
> On Sun, May 26, 2013 at 4:12 AM, Dale wrote:
>> The problem. After I am logged into KDE for a good while, like several
>> hours to maybe a day or so, the kicker thingy at the bottom locks up
>> tight. I can't switch desktops, clock stops working, can't click the K
>> menu t
On Sun, May 26, 2013 at 4:12 AM, Dale wrote:
> The problem. After I am logged into KDE for a good while, like several
> hours to maybe a day or so, the kicker thingy at the bottom locks up
> tight. I can't switch desktops, clock stops working, can't click the K
> menu thingy either. Everything
On Sun, 26 May 2013 07:10:53 -0500
Dale wrote:
> Alan McKinnon wrote:
> > On 26/05/2013 13:03, Dale wrote:
> >> Alan McKinnon wrote:
> >>> On 26/05/2013 11:51, Dale wrote:
> >>>
> What package provides the kicker thingy? I think in KDE3 it was called
> kicker but it appears to have cha
Am 26.05.2013 11:12, schrieb Dale:
> Howdy,
>
> I been letting portage upgrade nvidia drivers as usual. Thing is, the
> last two or three drivers seems to cause a issue. First, versions that
> cause the issue:
>
> =x11-drivers/nvidia-drivers-319.12
> =x11-drivers/nvidia-drivers-319.17
> =x11-driv
Alan McKinnon wrote:
> On 26/05/2013 13:03, Dale wrote:
>> Alan McKinnon wrote:
>>> On 26/05/2013 11:51, Dale wrote:
>>>
What package provides the kicker thingy? I think in KDE3 it was called
kicker but it appears to have changed to something else. Is that
krunner that has it now?
On 26/05/2013 13:03, Dale wrote:
> Alan McKinnon wrote:
>> On 26/05/2013 11:51, Dale wrote:
>>
>>> What package provides the kicker thingy? I think in KDE3 it was called
>>> kicker but it appears to have changed to something else. Is that
>>> krunner that has it now?
>> Maybe it's time you used t
Alan McKinnon wrote:
> On 26/05/2013 11:51, Dale wrote:
>
>> What package provides the kicker thingy? I think in KDE3 it was called
>> kicker but it appears to have changed to something else. Is that
>> krunner that has it now?
> Maybe it's time you used the "thingy" suffix a little less and the
On 26/05/2013 11:51, Dale wrote:
> Alan McKinnon wrote:
>> I get a similar issue, my video card is an ATI and I use the radeon
>> drivers. Same symptom as you - plasma stops updating it's widgets like
>> clocks and stops responding to the mouse. Keyboard works. In my case,
>> it's usually linked to
Alan McKinnon wrote:
> I get a similar issue, my video card is an ATI and I use the radeon
> drivers. Same symptom as you - plasma stops updating it's widgets like
> clocks and stops responding to the mouse. Keyboard works. In my case,
> it's usually linked to nfs and smb mounts that went away (eg,
On 26/05/2013 11:12, Dale wrote:
> Howdy,
>
> I been letting portage upgrade nvidia drivers as usual. Thing is, the
> last two or three drivers seems to cause a issue. First, versions that
> cause the issue:
>
> =x11-drivers/nvidia-drivers-319.12
> =x11-drivers/nvidia-drivers-319.17
> =x11-driv
Howdy,
I been letting portage upgrade nvidia drivers as usual. Thing is, the
last two or three drivers seems to cause a issue. First, versions that
cause the issue:
=x11-drivers/nvidia-drivers-319.12
=x11-drivers/nvidia-drivers-319.17
=x11-drivers/nvidia-drivers-319.23
I'm currently using this
Hi,
It could be because it's hard coded in the nvidia sh script...
It used to be like that, don't know if it's still the case...
Le 5 févr. 2013 16:32, a écrit :
> Hi Alexandre,
>
> thanks for your reply! :)
>
> Both kernels were compiled the same way prior to emergeing the
> nvidia-drivers. In
meino.cra...@gmx.de wrote:
> Hi Alexandre,
>
> thanks for your reply! :)
>
> Both kernels were compiled the same way prior to emergeing the
> nvidia-drivers. In both cases the symlink /usr/src/linux points to
> the correct kernel sources...
> I also to booted into the kernel for which I want to eme
Hi Alexandre,
thanks for your reply! :)
Both kernels were compiled the same way prior to emergeing the
nvidia-drivers. In both cases the symlink /usr/src/linux points to
the correct kernel sources...
I also to booted into the kernel for which I want to emerge the
drivers which doesnt make a diffe
Note sure it's something wrong that you did, but that sure is strange... It
usually happens when switching from 3.x to 3.y kernel version...
When you're trying to emerge nvidia-drivers, are you running the recently
compiled kernel?
2013/2/5
> Hi,
>
> when using vanilla kernel 3.7.5 (appropiate
Hi,
when using vanilla kernel 3.7.5 (appropiate kernel headers installed)
emergeing nvidia-drivers 313.18 works fine.
As soon vanilla kernel 3.7.6 are installed the emerge process fails
because the kernel version couldnt be determined.
Both times /usr/src/linux symlinks to the according kernel so
On 01/27/2013 01:06 AM, staticsafe wrote:
> I just grabbed vanilla 3.7.4 from kernel.org, the kernel build itself
> went fine but when I did a modules-rebuild, the nvidia module failed to
> build. As requested by the error message:
I had the same problem, I had success with this:
https://devtalk.
I just grabbed vanilla 3.7.4 from kernel.org, the kernel build itself
went fine but when I did a modules-rebuild, the nvidia module failed to
build. As requested by the error message:
output of `emerge --info '=x11-drivers/nvidia-drivers-304.64'`:
http://sprunge.us/QLUN
output of `emerge -pqv '=x
120615 microcai wrote:
> 2012/6/15 Philip Webb
>> after installing Kernel 3.4 , Nvidia-drivers 295.49 wouldn't compile.
>> The solution (via Google + Launchpad bugzilla) is to copy 4 header files
>> from /usr/src/linux/arch/arm/include/asm to -/-/-/-/x86/include/asm :
>> system.h compiler.h
don't, use 295.59 :)
2012/6/15 Philip Webb
> I haven't seen any mention of the problem here,
> but after installing Kernel 3.4 , Nvidia-drivers 295.49 wouldn't compile.
> The solution (via Google + Launchpad bugzilla) is to copy 4 header files
> from /usr/src/linux/arch/arm/include/asm to -
I haven't seen any mention of the problem here,
but after installing Kernel 3.4 , Nvidia-drivers 295.49 wouldn't compile.
The solution (via Google + Launchpad bugzilla) is to copy 4 header files
from /usr/src/linux/arch/arm/include/asm to -/-/-/-/x86/include/asm :
system.h compiler.h system_i
On Wed, Apr 11, 2012 at 4:36 PM, Canek Peláez Valdés wrote:
> On Wed, Apr 11, 2012 at 4:30 PM, Stefan G. Weichinger wrote:
>> Am 11.04.2012 23:16, schrieb ny6...@gmail.com:
>>
>>> I use the nouveau drivers because they update themselves when you update the
>>> kernel, and there's less work involv
On Thu, Apr 12, 2012 at 3:06 AM, Helmut Jarausch
wrote:
> What's the difference (in performance) between fglrx and xf86-video-ati ?
My experience with my first and only ATI video card (a Mobility Radeon
9700), is that the opensource drivers for my chipset are basically
useless for anything 3D. Sl
On Thu, Apr 12, 2012 at 09:09:16AM +0200, Alan McKinnon wrote:
> On Wed, 11 Apr 2012 16:36:06 -0500
> Canek Pel?ez Vald?s wrote:
>
> > On Wed, Apr 11, 2012 at 4:30 PM, Stefan G. Weichinger
> > wrote:
> > > Am 11.04.2012 23:16, schrieb ny6...@gmail.com:
> > >
> > >> I use the nouveau drivers beca
On Thu, 12 Apr 2012 10:06:17 +0200
Helmut Jarausch wrote:
> On 04/12/2012 09:09:16 AM, Alan McKinnon wrote:
> > That was the previous laptop. This current one has an ATI card and I
> > use ati drivers rather than fglrx for the same reason.
>
> What's the difference (in performance) between fglrx
1 - 100 of 223 matches
Mail list logo
