On Wed, Jul 10, 2013 at 10:13:01AM +0200, Ralf Mardorf wrote:
> On Wed, 2013-07-10 at 14:58 +1200, Chris Bannister wrote:
> > On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
> > > From the package description of dkms (Dynamic Kernel Module Support
> > > Framework);
> >
> > Then why is
On Wed, 10 Jul 2013 14:58:03 +1200
Chris Bannister wrote:
Hello Chris,
>On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
>> From the package description of dkms (Dynamic Kernel Module Support
>> Framework);
>Then why isn't it dkmsf?
:-)
--
Regards _
/ ) "The b
On Wed, 2013-07-10 at 14:58 +1200, Chris Bannister wrote:
> On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
> > From the package description of dkms (Dynamic Kernel Module Support
> > Framework);
>
> Then why isn't it dkmsf?
Why is it
mkdir
and not
md
or
mdir
resp. why isn't
m
On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
> From the package description of dkms (Dynamic Kernel Module Support
> Framework);
Then why isn't it dkmsf?
--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who a
On Tue, 09 Jul 2013 18:03:40 +0200, Brad Rogers wrote:
From the package description of dkms (Dynamic Kernel Module Support
Framework);
DKMS is a framework designed to allow individual kernel modules to be
upgraded without changing the whole kernel. It is also very easy to
rebuild modules as you
On Tue, 9 Jul 2013 16:49:04 +0300
andrey.ry...@bilkent.edu.tr wrote:
Hello andrey.ry...@bilkent.edu.tr,
>> Really? I've always needed an xorg.conf file to allow the use of the
>> nVidia driver.
>Yes man! its true. For example, if i reload system to my old kernel -
>everything is ok. And i have n
> Really? I've always needed an xorg.conf file to allow the use of the
> nVidia driver.
Yes man! its true. For example, if i reload system to my old kernel -
everything is ok. And i have not any xorg.conf.
i should do rectification. I am talking about system on notebook with
intel and nvidia vid
On 07/07/2013 12:01 PM, andrey.ry...@bilkent.edu.tr wrote:
i have jessy. why modprobe cannot find nvidia_drv.so? when i used wheezy i
didnot need the xorg.conf. it stopped to work after upgrading. There was
no problem when i had upgraded from wheeze to jessy. But when kernel
version was changed t
On Sun, 7 Jul 2013 22:01:06 +0300
andrey.ry...@bilkent.edu.tr wrote:
Hello andrey.ry...@bilkent.edu.tr,
>i have jessy. why modprobe cannot find nvidia_drv.so? when i used
>wheezy i didnot need the xorg.conf. it stopped to work after upgrading.
Really? I've always needed an xorg.conf file to all
On Sun, 07 Jul 2013, andrey.ry...@bilkent.edu.tr wrote:
>
> > Check to see if you have a symbolic link "nvidia"
> > in /usr/lib/nvidia which eventually points
> > to /usr/lib/nvidia/current/nvidia_drv.so
> yes i have:
>
> /usr/lib/nvidia/nvidia: symbolic link to `/etc/alternatives/nvidia'
> /etc
> Check to see if you have a symbolic link "nvidia"
> in /usr/lib/nvidia which eventually points
> to /usr/lib/nvidia/current/nvidia_drv.so
yes i have:
/usr/lib/nvidia/nvidia: symbolic link to `/etc/alternatives/nvidia'
/etc/alternatives/nvidia: symbolic link to `/usr/lib/nvidia/current'
# file /
On Sun, 07 Jul 2013, andrey.ry...@bilkent.edu.tr wrote:
> hi!
> if i do command:
> # modprobe nvidia
> i retrieve next message:
>
> FATAL: Module nvidia not found.
>
> but i have many nvidia-* packages installed
> and between them:
>
> ii nvidia-kernel-common
> 20130505+1 i386 NVIDIA b
> For what Debian release, resp. from what repository?
#lsb_release -a
Release:testing
Codename: jessie
# uname -a
Linux hostname 3.9-1-686-pae #1 SMP Debian 3.9.6-1 i686 GNU/Linux
> The module might be somewhere in /lib/modules/$(uname -r)/ .
#ls /lib/modules/$(uname -r)/
build
On Sun, 2013-07-07 at 17:19 +0300, andrey.ry...@bilkent.edu.tr wrote:
> hi!
> if i do command:
> # modprobe nvidia
> i retrieve next message:
>
> FATAL: Module nvidia not found.
>
> but i have many nvidia-* packages installed
> and between them:
>
> ii nvidia-kernel-common
Sean Whalen wrote:
> Hello All,
>
> I recently made the switch from Kubuntu 11.10 to Debain stable.
> Everything was running very well until I installed the Nvidia module
> "the Debian way". Then, the system became highly unstable. I noticed
> that the system would become very sluggish during sim
Hi Sean,
For the past few days, I've been trying to install Squueze on my PC and have
experienced very similar troubles. My card is a GeForce 8400 GS. The screen and
the whole system freeze as soon as gdm3 starts. I installed the Nvidia module
"the Debian Way", and also (after some reluctance)
Richard wrote:
Hi
I had to purge everything I downloaded previously, blacklist nouveau, kill X &
gdm3, the run
NVIDIA-Linux-x86_64-290.10.run, then reboot.
No more shakey display and I can watch TV again without X crashing.
Good news. IMO the reboot is not necessary, just run
NVIDIA-Linux-x86
On Thu, 2011-11-24 at 20:32 +, Richard wrote:
> Hi
> I had to purge everything I downloaded previously, blacklist nouveau, kill X
> & gdm3, the run
> NVIDIA-Linux-x86_64-290.10.run, then reboot.
> No more shakey display and I can watch TV again without X crashing.
Good news :)
- Ralf
--
T
Tim Wood wrote:
I decided to follow the advise in one of Florian' links (Thanks Florian)
and use the NVIDIA_kernel-1.0-8178-1444349.diff.txt patch to the 7676
driver. After fixing a few links, it's up and running.
Must say that I'm a bit bemused at applying an 8178 patch to the 7676
driver,
I decided to follow the advise in one of Florian' links (Thanks Florian)
and use the NVIDIA_kernel-1.0-8178-1444349.diff.txt patch to the 7676
driver. After fixing a few links, it's up and running.
Must say that I'm a bit bemused at applying an 8178 patch to the 7676
driver, but have not gone
I receive the digest, so hope this reads ok.
Tim Wood wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some erro
H.S. wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).
Searchi
H.S. wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).
Searching
Tim Wood wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).
Sear
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).
Searching google has
RParr wrote:
> I am not sure if we have the same problem.
>
> On my recently upgraded system the module-assistant fails with a message
> "/usr/src/linux-headers-2.6.16-1 seems to contain unconfigured kernel
> source"
>
> None of the suggested commands seems to be able to fix this problem.
>
> W
H.S. wrote:
> I have installed the new 2.6.16 kernel on two machines running Debian
> Sid and tried to install nvidia module. On both machines, the module
> compilation (using module-assistant) fails with some error messages
> (IIRC there was some error about rlim structure not being defined).
>
>
H.S. wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).
Searchin
On Fri, 2003-02-07 at 16:54, Alan Thompson wrote:
> On Sat, Feb 08, 2003 at 12:26:29AM +, Nic Strong wrote:
> > Hi,
> >
> > Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
> > whenever I start x the nvidia module does not auto load i have to do an
> > explicit 'insmod nvidi
On Sat, Feb 08, 2003 at 12:26:29AM +, Nic Strong wrote:
> Hi,
>
> Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
> whenever I start x the nvidia module does not auto load i have to do an
> explicit 'insmod nvidia' (i never had to do this in the past).
>
> /etc/modules has
Perhaps a stupid question, since your system seemed to work before you
used 2.4.20.
I think it is X that loads the kernel when reading the XF86Config.
What does your XF86config contain?
Mine has
Section "Device"
Identifier "NVIDIA Corporation GeForce2 Go [NV11]"
Driver
I'm running 2.4.20/woody/nv(4191) and mine works fine, the only
difference I can see is that I didn't bother with any of the aliases.
I just have this in /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be load
32 matches
Mail list logo