Hi,
Is anyone running an Nvidia card on a CPU that does not support
POPCNT?
I have been reading about Blue Screens of Death being experience by
Windows users due to Nvidia drivers not supporting CPUs which do not
have support for POPCNT.
I am wondering if this issue will affect Linux
Daniel Rodriguez writes:
> The solution of the post to this issue is to update the kernel from
> 6.1.0-13 -> 6.1.0.18; however, my kernel is a later version:
> 6.1.0-21-amd64, so I am stuck for solving this issue. Do you have any
> idea about what may be happening and/or how to solve it?
I wonde
Hello team,
by installing NVIDIA drivers as per the guideline of Debian on Debian 12,
it shows an error as follows:
Building initial module for 6.1.0-21-amd64
> readelf: Error: Not an ELF file - it has the wrong magic bytes at the start
> readelf: Error: Not an ELF file - it has the wrong
On 27/7/23 16:10, rudu wrote:
Le 26/07/2023 à 23:16, Greg Wooledge a écrit :
On Wed, Jul 26, 2023 at 11:15:13PM +0200, rudu wrote:
Thank you David, but I thought that non-free-firmware should be
enough for
the new testing repositories.
Should I had "non-free" to "main contrib non-free-firmware
Le 26/07/2023 à 23:16, Greg Wooledge a écrit :
On Wed, Jul 26, 2023 at 11:15:13PM +0200, rudu wrote:
Thank you David, but I thought that non-free-firmware should be enough for
the new testing repositories.
Should I had "non-free" to "main contrib non-free-firmware" ?
Sounds weird to me ... ??
T
On Wed, Jul 26, 2023 at 11:15:13PM +0200, rudu wrote:
> Thank you David, but I thought that non-free-firmware should be enough for
> the new testing repositories.
> Should I had "non-free" to "main contrib non-free-firmware" ?
> Sounds weird to me ... ??
The non-free-firmware section only contains
Le 26/07/2023 à 17:12, David Wright a écrit :
# cat /etc/apt/sources.list
# deb cdrom:[Debian GNU/Linux testing_Bookworm_ - Official Snapshot
amd64 NETINST 20221031-03:18]/ bookworm main
#deb cdrom:[Debian GNU/Linux testing_Bookworm_ - Official Snapshot
amd64 NETINST 20221031-03:18]/ bookworm
On Wed 26 Jul 2023 at 15:39:49 (+0200), rudu wrote:
> Switching from the nouveau driver to some nvidia-driver does not seam
> to be possible on my laptop running Debian Testing/Trixie.
> Now, it can be found right here apparently :
> https://packages.debian.org/trixie/nvidia-driver
> Am I missing s
Hi there,
Switching from the nouveau driver to some nvidia-driver does not seam to
be possible on my laptop running Debian Testing/Trixie.
Now, it can be found right here apparently :
https://packages.debian.org/trixie/nvidia-driver
Am I missing something ?
Some information about my system is f
Solved my own problem: I had to do `apt install
linux-headers-cloud-amd64` instead of `apt install
linux-headers-amd64`
On Thu, Jul 13, 2023 at 2:28 PM Sam Clearman wrote:
>
> Hi,
> I'm trying to get a Tesla T4 working under Debian 12.
>
> So far I've tried two approaches:
> 1. Using the Debian p
Hi,
I'm trying to get a Tesla T4 working under Debian 12.
So far I've tried two approaches:
1. Using the Debian provided drivers, per
https://wiki.debian.org/NvidiaGraphicsDrivers
2. Using the nVidia provided drivers installed via runfile, per
https://docs.nvidia.com/datacenter/tesla/tesla-install
ave a GNOME desktop environment, and the installation of Nvidia drivers
somehow made it get activated in the cases I mentioned earlier.
On Fri, Jan 21, 2022 at 3:24 PM Thanos Katsiolis
wrote:
> Hello,
>
> the title of the post says pretty much everything.
> I have the NVIDIA Quadro P
have GNOME desktop environment, and the installation of Nvidia drivers
somehow made it get activated in the cases I mention earlier.
>
Hello Andrei, thank you for your answer,
and sorry for my late answer, but today again I have access to this
machine.
On Sat, Jan 22, 2022 at 9:51 AM Andrei POPESCU
wrote:
>
> This is likely completely unrelated to installing the NVIDIA drivers.
>
>
I am certain that it has to
On Vi, 21 ian 22, 15:24:29, Thanos Katsiolis wrote:
> Hello,
>
> the title of the post says pretty much everything.
> I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA
> drivers as described in Debian wiki NVIDIA Proprietary Driver
> <ht
post says pretty much everything.
> I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA
> drivers as described in Debian wiki NVIDIA Proprietary Driver
> <https://wiki.debian.org/NvidiaGraphicsDrivers> for Debian 11.2.
>
> The message appears when an Applicatio
Hello,
the title of the post says pretty much everything.
I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA
drivers as described in Debian wiki NVIDIA Proprietary Driver
<https://wiki.debian.org/NvidiaGraphicsDrivers> for Debian 11.2.
The message appears when an Appli
ing to GPU Mag[1], the RTX 3070 card, in which I would be interested in
the most, will come around October, and two additional months is the time I am
willing to wait. But the question is, what is the usual time the newest
proprietary NVIDIA drivers drivin' their newest products hit the Debi
Hi,
On my Optimus laptop (with both Intel and Nvidia GPUs), I'm trying to
avoid loading the Nvidia drivers on startup (in order to power down the
Nvidia card with bbswitch). When I blacklist them in /etc/modprobe.d/,
they don't load on boot, but X seems to be loading them, despite the
f
is a
>
> Maybe.
>
> >[AMD/ATI] RV370 [Radeon X300/X550/X1050 Series]
>
> .It's a Radeon card. nVidia drivers are worthless to you.
>
> --
> Regards _
> / ) "The blindingly obvious is
> / _)radnever immediately apparent"
> No guarantee the stimuli must be perceived the same...
> Gary Gilmore's Eyes - The Adverts
Good idea, I'll check the metapackage, though.
Il giorno mer 13 mar 2019 alle ore 13:17 Brad Rogers ha
scritto:
> On Wed, 13 Mar 2019 12:55:40 +0100
> Andrea Borgia wrote:
>
> Hello Andrea,
>
> >Yup, my bad: I assumed that the package still had a reason to be
> >installed. It might have been a
On Wed, 13 Mar 2019 12:55:40 +0100
Andrea Borgia wrote:
Hello Andrea,
>Yup, my bad: I assumed that the package still had a reason to be
>installed. It might have been a mistake or a requirement of an earlier
The probable reason is that you've got the video drivers metapackage
(exact name escape
On Wed, Mar 13, 2019 at 12:51:58PM +0100, Andrea Borgia wrote:
> Duh :)
> Other than feeling a bit stupid [...]
Take it easy. Happens to me on a daily basis ;-)
On a more positive note, your question and the answers you got might
help somebody else to solve their problem...
Cheers
-- t
signatu
Brad Rogers ha
scritto:
> On Wed, 13 Mar 2019 12:27:51 +0100
> Andrea Borgia wrote:
>
> Hello Andrea,
>
> >Perhaps a silly question but... how do I know whether my card is a
>
> Maybe.
>
> >[AMD/ATI] RV370 [Radeon X300/X550/X1050 Series]
>
> ..
Duh :)
Other than feeling a bit stupid, now I have to find out why the system had
that package installed.
Thanks,
Andrea.
Il giorno mer 13 mar 2019 alle ore 12:37 ha scritto:
> On Wed, Mar 13, 2019 at 12:27:51PM +0100, Andrea Borgia wrote:
> > Il giorno mar 12 mar 2019 alle ore 22:34 Boyan Penk
On Wed, 13 Mar 2019 12:27:51 +0100
Andrea Borgia wrote:
Hello Andrea,
>Perhaps a silly question but... how do I know whether my card is a
Maybe.
>[AMD/ATI] RV370 [Radeon X300/X550/X1050 Series]
.It's a Radeon card. nVidia drivers are worthless to you.
-
On Wed, Mar 13, 2019 at 12:27:51PM +0100, Andrea Borgia wrote:
> Il giorno mar 12 mar 2019 alle ore 22:34 Boyan Penkov <
> boyan.pen...@gmail.com> ha scritto:
>
>
>
> > I installed nvidia-legacy-390, uninstalled nvidia-legacy-checker, and my
> > machine survived a reboot with the GUI coming up n
Il giorno mar 12 mar 2019 alle ore 22:34 Boyan Penkov <
boyan.pen...@gmail.com> ha scritto:
> I installed nvidia-legacy-390, uninstalled nvidia-legacy-checker, and my
> machine survived a reboot with the GUI coming up nicely.
>
Perhaps a silly question but... how do I know whether my card is a
On Wed, 13 Mar 2019 09:35:53 +0100
Erwan David wrote:
Hello Erwan,
>drivers. However, here I got a system in a dirty state, and no standard
>way to get it clean (how can I say "Ok revert the partial installation
>and keep the installed version" ?).
As it happens, I ended up in a similar positio
On 12/03/2019 19:33, Brad Rogers wrote:
> On Tue, 12 Mar 2019 19:03:12 +0100
> Erwan David wrote:
>
> Hello Erwan,
>
>> And what should I have done ? Install non working drivers ?
> You should have read the warning; It tells which version of the legacy
> packages you need to install.
Yes it doe
On 3/12/19 2:03 PM, Erwan David wrote:
When upgrading my lenovo T530 I was warned that nvidia-driver does not
support anymore my graphic card. Thus I chose to not upgrade in the dialog.
Now I have partially installed packages for nvidia driver, so what
should I do with this ?
And what should
On Tue, 12 Mar 2019 19:03:12 +0100
Erwan David wrote:
Hello Erwan,
>And what should I have done ? Install non working drivers ?
You should have read the warning; It tells which version of the legacy
packages you need to install.
I'm guessing, based on the fact that you updated today, you're u
When upgrading my lenovo T530 I was warned that nvidia-driver does not
support anymore my graphic card. Thus I chose to not upgrade in the dialog.
Now I have partially installed packages for nvidia driver, so what
should I do with this ?
And what should I have done ? Install non working drivers ?
On 09/15/2018 10:28 AM, Thakur Mahashaya wrote:
//"Есть два великих грехов в мире...
..грех невежества, грех от глупости.//
So stupidity is the mode of ignorance.
As the Sorting Hat once said, "I know what to do with YOU!" ...and off
you go into my junk folder. :) Ric
--
My father, Victor Mo
//here are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.//
So stupidity is the mode of ignorance.
15.09.2018, 17:20, "Ric Moore" :
> On 09/14/2018 07:54 AM, Marco Righi wrote:
>> Hello,
>> the NVIDIA drivers (384 from Debian and
//"Есть два великих грехов в мире...
..грех невежества, грех от глупости.//
So stupidity is the mode of ignorance.
15.09.2018, 17:20, "Ric Moore" :
> On 09/14/2018 07:54 AM, Marco Righi wrote:
>> Hello,
>> the NVIDIA drivers (384 from Debian and 390 repositories fr
On 09/14/2018 07:54 AM, Marco Righi wrote:
Hello,
the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia site) do not
allow me to have "virtual consoles" (to be clear, those that are activated with
Ctrl-Alt-F1 .. F6). By installing Nouveau the problem disappears, wi
Hello,
the NVIDIA drivers (384 from Debian and 390 repositories from the nvidia site)
do not allow me to have "virtual consoles" (to be clear, those that are
activated with Ctrl-Alt-F1 .. F6). By installing Nouveau the problem
disappears, with the two different versions of the NVID
Thanks for being a good guy and following up; I was looking into this
and this report was keeping me from apt-get dist-upgrade this evening,
so I know I'm OK now...
Silent thanks to all that have faffed with getting this sorted in the
last week -- cheers!
On 07/09/2018 02:17 PM, Matthew Crew
On 7/9/18 5:55 AM, Matthew Crews wrote:
> On Fri, Jul 06, 2018 at 09:55:45AM +0100, Darac Marjal wrote:
>>> On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote:
>>> This requires a workaround, a kernel parameter at boot.
>>> GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=
On Fri, Jul 06, 2018 at 09:55:45AM +0100, Darac Marjal wrote:
>> On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote:
>> This requires a workaround, a kernel parameter at boot.
>> GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y"
>> Edit the config file like this,
>>
& testing shared
the same version of the nvidia-drivers package for a few days. As Floris
pointed out, various reports from sid users *did* occur - I simply
didn't check properly.
Floris has also pointed out a bug report that has arisen from using the
fixed version. It may not affe
Hey all,
On Fri, 2018-07-06 at 11:37 +0100, Brad Rogers wrote:
>
> nVidia have made changes to the driver that negate the effects of a
> change in the kernel.
>
> So, it appears to be 'six of one, half a dozen of the other'. That
> said, maybe nVidia should have kept a closer eye on kernel chan
On Fri, 06 Jul 2018 16:10:40 +0200
floris wrote:
Hello floris,
>and there is a new bug:
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903121
>So be careful if you use the nvidia module.
Thanks for the warning.
--
Regards _
/ ) "The blindingly obvious is
/ _)r
On Fri, 06 Jul 2018 16:06:19 +0200
floris wrote:
Hello floris,
>They have found and reported this bug multiple times:
>
>see bug numbers: 901919, 901932, 901990, 902248, 902661, 902773,
>902868, 902891
Fair enough. As I was pointed to the initial report quite quickly, I
didn't search for other
s: #901919)
-- Andreas Beckmann Thu, 05 Jul 2018 02:01:31
+0200
[1]
http://metadata.ftp-master.debian.org/changelogs/non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_390.67-2_changelog
Thats good to know.
Unfortunately, Stretch-backports and Buster Nvidia-drivers are not in
sync wi
Brad Rogers schreef op 2018-07-06 12:37:
It's strange also that nobody using sid /seems/ to have been affected
by
the problem. Or maybe they were, knew the workaround and forgot to
report the bug. Who knows?
They have found and reported this bug multiple times:
see bug numbers: 90191
16.0-2-*
> or newer).
> (Closes: #901919)
>
>-- Andreas Beckmann Thu, 05 Jul 2018 02:01:31 +0200
>
> [1]
> http://metadata.ftp-master.debian.org/changelogs/non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_390.67-2_changelog
>
Thats good to know.
Unfortunate
On Fri, 06 Jul 2018 12:09:59 +0200
Francisco M Neto wrote:
Hello Francisco,
>assume it was something that was changed in the kernel since it was the
>kernel upgrade that "broke" the driver, but it might also have been
>something in the driver that was addressed in the kernel.
nVidia have made
Thanks for the answer!
First, checking installed kernel headers was the first thing I
tried when dkms failed.
I'll try using the workaround when I get home tonight and see
how it goes. I try not to use too much stuff from sid, especially on
essential systems like this.
Ho
On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote:
On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote:
Hey all,
I'm running kernel 4.15 with nvidia-driver 390.48-3 with no
problems. However, recently my kernel was automatically upgraded to 4.16
and it broke the nvidia driver.
X_DEFAULT="slab_common.usercopy_fallback=y"
> >
> > Edit the config file like this,
> >
> > $sudo gedit /etc/default/grub
> >
> > Then run $sudo update-grub.
> >
>
> As an aside, thank you for posting this fix. Although my drivers were
>
hen run $sudo update-grub.
>
As an aside, thank you for posting this fix. Although my drivers were
not broken, I did have a problem where xorg would not start correctly
with the 4.16 kernel and nvidia drivers 390.48 (both from Stretch
backports). That GRUB command seemed to resolve it my issue.
Cheers.
Sorry,
I failed to read your whole message. Make sure you have installed the
the kbuild and headers for your current running kernel. Then consider
upgrading your nvidia driver to the latest version (in sid, still, I
believe). If you do the latter, be sure and use the kernel parameter I
show
On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote:
Hey all,
I'm running kernel 4.15 with nvidia-driver 390.48-3 with no
problems. However, recently my kernel was automatically upgraded to 4.16
and it broke the nvidia driver.
Running 'dkms autoinstall --all' does not help, it compl
You sure you have the 4.16 headers installed and not the 4.15 headers?
Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.
Original Message
On Jul 5, 2018, 15:42, Francisco Mariano-Neto wrote:
> Hey all,
>
> I'm running kernel 4.15 with nvidia-driver 39
Hey all,
I'm running kernel 4.15 with nvidia-driver 390.48-3 with no
problems. However, recently my kernel was automatically upgraded to 4.16
and it broke the nvidia driver.
Running 'dkms autoinstall --all' does not help, it complains
about not finding kernel headers (which are i
On 2015-05-30, Stefan Malte Schumacher wrote:
> Yes, I have.
>> You have the non-free archive mentioned in your /etc/apt/sources.list?
You need contrib also, it would appear.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact l
re. :) Ric
p/s If the OP has one of the newest nVidia cards, there are some laptop
issues requiring more than plain nvidia drivers. I forget the name of
the special install system. But, the Op can just go to the nvidia site
for more info on his card's driver requirements
Or, he could rip
On 05/30/2015 04:18 PM, Stefan Malte Schumacher wrote:
Hello
I am trying to install the proprietary Nvidia-Drivers on my Laptop. I
have read
https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_8_.22Jessie.22
and have entered the following command according to the description:
aptitude -r
Yes, I have.
2015-05-30 18:45 GMT+02:00 Curt :
> On 2015-05-30, Stefan Malte Schumacher wrote:
>> Hello
>> This is the english version of the output of aptitude.
>>
>
> You have the non-free archive mentioned in your /etc/apt/sources.list?
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@l
On 2015-05-30, Stefan Malte Schumacher wrote:
> Hello
> This is the english version of the output of aptitude.
>
You have the non-free archive mentioned in your /etc/apt/sources.list?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
On Saturday 30 May 2015 15:36:52 Stefan Malte Schumacher wrote:
> Hello
> This is the english version of the output of aptitude.
>
> aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
> nvidia-kernel-dkmsThe following NEW packages will be installed:
> libegl1-nvidia{a} libgl1-nv
On 30/05/2015, Stefan Malte Schumacher wrote:
> Hello
>
> I am trying to install the proprietary Nvidia-Drivers on my Laptop.
Hello.
Whilst the above scenario relates to Debian 8, what is the nVidia
device that you have in your laptop?
I have not yet resolved a problem with a syst
Hello
This is the english version of the output of aptitude.
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-kernel-dkmsThe following NEW packages will be installed:
libegl1-nvidia{a} libgl1-nvidia-glx{ab} libgles1-nvidia{a}
libgles2-nvidia{a} libnvidia-eglcore{a}
l
On Saturday 30 May 2015 15:18:34 Stefan Malte Schumacher wrote:
> Hello
>
> I am trying to install the proprietary Nvidia-Drivers on my Laptop. I have
> read https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_8_.22Jessie.22
> and have entered the following command according to
Hello
I am trying to install the proprietary Nvidia-Drivers on my Laptop. I have
read https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_8_.22Jessie.22
and have entered the following command according to the description:
aptitude -r install linux-headers-$(uname -r|sed &#
Ok, that worked brilliantly! I just followed Mark's suggestion of putting
that line in my 20-nvidia.conf.
Thanks!
On 26 February 2015 at 19:46, Mark Neyhart wrote:
> On 02/26/2015 02:28 AM, James Allsopp wrote:
> > Hello,
> > I've just installed the nvidia dr
On 02/26/2015 02:28 AM, James Allsopp wrote:
> Hello,
> I've just installed the nvidia drivers after following the instructions
> here https://wiki.debian.org/NvidiaGraphicsDrivers
>
> but now my fonts are so small they are unreadable. My display is a HDMI
> television.
>
On 2015-02-26, James Allsopp wrote:
>
> I can't run nvidia-settings as I can't read the text,
>
> Any ideas what changes I need to make to fix this please?
>
Searching, I find
sudo nvidia-xconfig --no-use-edid-dpi
which generates a etc/X11/xorg.conf file disabling the DPI info from the
monitor'
Hello,
I've just installed the nvidia drivers after following the instructions
here https://wiki.debian.org/NvidiaGraphicsDrivers
but now my fonts are so small they are unreadable. My display is a HDMI
television.
I think this could be related to the EDID settings but I'm not sure
Short version: they worked for me for just under 1 day. After that the
system won't boot--at the point the NVIDIA logo should be displayed the
system hangs on a black screen, and the only thing I can do is power
off.
I can start in single-user mode, supply the root password and startx as
root. Fro
Am Sonntag, 17. November 2013, 16:57:30 schrieb Brad Rogers:
> On Sun, 17 Nov 2013 15:47:40 +
> Alex Naysmith wrote:
>
> Hello Alex,
>
> >#aptitude purge nvidia-kernel-dkms nvidia-glx
> >
> >The nvidia driver is still present and functioning. During the [failed]
> >purge, I received the mess
On Sun, 17 Nov 2013 15:47:40 +
Alex Naysmith wrote:
Hello Alex,
>#aptitude purge nvidia-kernel-dkms nvidia-glx
>
>The nvidia driver is still present and functioning. During the [failed]
>purge, I received the message 'No packages will be installed, upgraded,
>or removed'.
nvidia-glx is a tr
After purging the nvidia drivers with the following command:
#aptitude purge nvidia-kernel-dkms nvidia-glx
The nvidia driver is still present and functioning. During the [failed]
purge, I received the message 'No packages will be installed, upgraded, or
removed'.
On 10 November
On Jo, 14 nov 13, 18:52:25, Kailash Kalyani wrote:
>
> I've used the sgfxi script and it supports removing non-free drivers
> and installing free ones instead.
>
> http://smxi.org/site/about.htm#sgfxi
> What is sgfxi (simple graphics installer - s gfx i)
>
> The primary purpose of sgfxi is to in
On Monday 11 November 2013 11:11 PM, Curt wrote:
On 2013-11-11, Chris Bannister wrote:
Will the nouveau driver be "unblacklisted" after the purge?
Ask yourself - "Would you, as system administrator, expect this?" then
Oh, sorry, I thought you were answering the OP, a newbie who asked for
On Tue, 2013-11-12 at 21:17 +, Alex Naysmith wrote:
> Thank you all for the sed regex explanation. What possible kernel
> variations other than 'generic' are possible to require the sed
> substitution?
I guess there isn't a kernel named "generic" available by Debian
repositories and the name e
Thank you all for the sed regex explanation. What possible kernel
variations other than 'generic' are possible to require the sed
substitution?
After some googling, I've discovered that I'm actually compiling the nvidia
driver and hence the business with the Linux header.
On 12 November 2013 07:
On Tue, 2013-11-12 at 07:56 +, Alex Naysmith wrote:
> linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
It does complete the name "linux-headers-".
Run
echo $(uname -r|sed 's,[^-]*-[^-]*-,,')
or
uname -r|sed 's,[^-]*-[^-]*-,,'
to see what it does add. "uname -r" does show the kernel relea
On 11/12/2013 02:56 AM, Alex Naysmith wrote:
> From the nvidia install procedure is the following command:
>
> # aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
> nvidia-kernel-legacy-173xx-dkms
>
> I can see the pipe | symbol and the regular expressions but I don't
> really
>From the nvidia install procedure is the following command:
# aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-kernel-legacy-173xx-dkms
I can see the pipe | symbol and the regular expressions but I don't really
understand what this command is doing.
Alex
On 10 Nove
On 2013-11-11, Chris Bannister wrote:
>> >
>> Will the nouveau driver be "unblacklisted" after the purge?
>
> Ask yourself - "Would you, as system administrator, expect this?" then
Oh, sorry, I thought you were answering the OP, a newbie who asked for
the procedure (even a wiki) involved in going
Le 11/11/2013 18:14, Chris Bannister a écrit :
> On Mon, Nov 11, 2013 at 04:50:36PM +, Curt wrote:
>> On 2013-11-11, Ralf Mardorf wrote:
>>> I suspect that xorg.conf will not be removed, even not when using purge.
>>>
>> Will the nouveau driver be "unblacklisted" after the purge?
> Ask yoursel
On Mon, Nov 11, 2013 at 04:50:36PM +, Curt wrote:
> On 2013-11-11, Ralf Mardorf wrote:
> >
> > I suspect that xorg.conf will not be removed, even not when using purge.
> >
> Will the nouveau driver be "unblacklisted" after the purge?
Ask yourself - "Would you, as system administrator, expect
On 2013-11-11, Ralf Mardorf wrote:
>
> I suspect that xorg.conf will not be removed, even not when using purge.
>
Will the nouveau driver be "unblacklisted" after the purge?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
On Mon, 2013-11-11 at 16:20 +0100, berenger.mo...@neutralite.org wrote:
>
> Le 11.11.2013 16:18, Ralf Mardorf a écrit :
> > On Mon, 2013-11-11 at 15:25 +0100, berenger.mo...@neutralite.org
> > wrote:
> >>
> >> Le 10.11.2013 22:44, Alex Naysmith a écrit :
> >> > After following the procedure at
>
Le 11.11.2013 16:18, Ralf Mardorf a écrit :
On Mon, 2013-11-11 at 15:25 +0100, berenger.mo...@neutralite.org
wrote:
Le 10.11.2013 22:44, Alex Naysmith a écrit :
> After following the procedure at
> https://wiki.debian.org/NvidiaGraphicsDrivers [1] to install the
> nvidia-glx-legacy-173xx pack
On Mon, 2013-11-11 at 15:25 +0100, berenger.mo...@neutralite.org wrote:
>
> Le 10.11.2013 22:44, Alex Naysmith a écrit :
> > After following the procedure at
> > https://wiki.debian.org/NvidiaGraphicsDrivers [1] to install the
> > nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian
Le 10.11.2013 22:44, Alex Naysmith a écrit :
After following the procedure at
https://wiki.debian.org/NvidiaGraphicsDrivers [1] to install the
nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7
"Wheezy"], I would like to know the best method to return to the
nouveau driver wit
After following the procedure at
https://wiki.debian.org/NvidiaGraphicsDrivers to install the
nvidia-glx-legacy-173xx package for my GeForce FX5550 card [Debian 7
"Wheezy"], I would like to know the best method to return to the nouveau
driver with the files from the glx-legacy-1733 package removed
On 07/16/13 at 09:13pm, Brad Alexander wrote:
> I'm using the nvidia drivers from the repos on a sid machine. They were
> just upgraded to the long-term 319.32-1 from the repos. However, I have
> cisco's anyconnect, and when I launch it, I get
>
> $ /opt/cisco/anyconne
Am Tue, 16 Jul 2013 21:13:40 -0400
schrieb Brad Alexander :
> I'm using the nvidia drivers from the repos on a sid machine. They
> were just upgraded to the long-term 319.32-1 from the repos. However,
> I have cisco's anyconnect, and when I launch it, I get
>
> $ /opt/c
I'm using the nvidia drivers from the repos on a sid machine. They were
just upgraded to the long-term 319.32-1 from the repos. However, I have
cisco's anyconnect, and when I launch it, I get
$ /opt/cisco/anyconnect/bin/vpnui
/opt/cisco/anyconnect/bin/vpnui: error while loading shared
itor i am using i want to run at 2560x1440 but is only currently using
1600x1200
Does anyone have a working xorg.conf with an nvidia card that i could test with
please?
And also does anyone know if the xorg.conf is configured correctly to use the
GLX driver then does Vesa get disabled
by default o
On Thu, Jun 7, 2012 at 6:20 PM, jeremy jozwik wrote:
> sorry for not being so clear. i dont have the machine in front of me
> at the moment to type out the exact error but i installed the driver
> ones. the install was building the man triggers and i tossed up an
> error for the nvidia driver. sin
On Thu, Jun 7, 2012 at 6:11 PM, Nathan D'elboux wrote:
>> i have my gtx 580 working "ok" with the nvidia linux driver. sadly it
>> throws an install error for every install since i ran the nvidia
>> driver. i dont have the machine in front of me right now to list the
>> specific error.
>>
>> but t
t my xorg.conf config later
to compare to someone else's if thats possible.
All i want is to take advantage of my screen real estate in a clear / crisp way
:)
> Date: Thu, 7 Jun 2012 17:50:17 -0700
> Subject: Re: Nvidia drivers problem Geforce 570
> From: jerjoz.for...@gmail.c
On Thu, Jun 7, 2012 at 5:11 PM, Nathan D'elboux wrote:
> Hello everyone!
>
> I wanted to know has anyone had any issues getting nvidia drivers working
> for a Geforce 5xx series card under Debian 6 squeeze?
>
> I'm running a Geforce 570 running a Dell 27" IPS
Sorry was suppose to reply all :)
RE: Nvidia drivers problem Geforce 570, Have not used this model GPU, sorry.
What model are you using?
I also have a 5xxx series and a 8800GTX and 8800GT to swap out and see, i just
haven't tried that yet
Date: Thu, 7 Jun 2012 20:19:49 -0400
From: sa
1 - 100 of 493 matches
Mail list logo
