Re: nvida driver is not working after reboot

2005-10-25 Thread Rob Sims
On Tue, Oct 25, 2005 at 03:46:15PM +0200, FrekoDing wrote:
> there are mistakes...
> 
> case "$type" in
>   L) ln -s $arg1 /dev/$name ;;
>   D) mkdir -p /dev/$name ;;
>   M) mknod --mode=660 /dev/$name $arg1 ;;
>   O) chown $arg1 /dev/$name ;;
>   G) chgrp $arg1 /dev/$name ;;
>   P) chmod $arg1 /dev/$name ;;
>   *) log_warning_msg "links.conf: unparseable line ($type $name 
> $arg1)" ;;
> esac

In addition to the mistakes, the patch will not be accepted by the udev
maintainer.  Instead, I've proposed a patch against
nvidia-kernel-common:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334531

This one was tested...
-- 
Rob


signature.asc
Description: Digital signature


Re: nvida driver is not working after reboot

2005-10-25 Thread FrekoDing

Rob Sims ecrivait le 30.09.2005 22:54:


And in /etc/init.d/udev changed the case statement in make_extra_nodes:


case "$type" in
  L) ln -s $arg1 /dev/$name ;;
  D) mkdir -p /dev/$name ;;
  M) mknod --mode=600 /dev/$name $arg1 ;;
  O) chown /dev/$name $arg1 ;;
  G) chgrp /dev/$name $arg1 ;;
  P) chmod /dev/$name $arg1 ;;
  *) log_warning_msg "links.conf: unparseable line ($type $name $arg1)" ;;
esac



Hi,
there are mistakes...

case "$type" in
  L) ln -s $arg1 /dev/$name ;;
  D) mkdir -p /dev/$name ;;
  M) mknod --mode=660 /dev/$name $arg1 ;;
  O) chown $arg1 /dev/$name ;;
  G) chgrp $arg1 /dev/$name ;;
  P) chmod $arg1 /dev/$name ;;
  *) log_warning_msg "links.conf: unparseable line ($type $name 
$arg1)" ;;

esac

Like that it works great :-D
See you.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-30 Thread Rob Sims
On Mon, Sep 26, 2005 at 12:21:34AM +0200, Alexander Fieroch wrote:
> Lennart Sorensen wrote:
> > You can always try adding 'nvidia' to /etc/modules
> 
> Yes, I do have.
> 
> > Then it WILL load the module on boot.
> 
> No, the problem was udev that did not create the special nvidia devices.
> Thanks to Rob Sims (same thread) the problem now is fixed for me.

Of course the permissions aren't set - it isn't udev after all creating
the nodes; it's the init script (where I found links.conf in the first
place!).  My mistake.

There doesn't appear to be a "Debian way" of doing this; after all, it's
non-free software.  What I have done now is in links.conf:


# sysfs doesn't play with non-GPL modules as of 2.6.13
M nvidia0   c 195 0
M nvidia1   c 195 1
M nvidia2   c 195 2
M nvidia3   c 195 3
M nvidiactl c 195 255
G nvidia*   video
P nvidia*   0660



And in /etc/init.d/udev changed the case statement in make_extra_nodes:


case "$type" in
  L) ln -s $arg1 /dev/$name ;;
  D) mkdir -p /dev/$name ;;
  M) mknod --mode=600 /dev/$name $arg1 ;;
  O) chown /dev/$name $arg1 ;;
  G) chgrp /dev/$name $arg1 ;;
  P) chmod /dev/$name $arg1 ;;
  *) log_warning_msg "links.conf: unparseable line ($type $name $arg1)" ;;
esac


Anyone:
Is there a better/cleaner way of mixing udev, nvidia proprietary, and 2.6.13+?

The init.d says "I hate this hack.  -- Md" and links.conf says:
# This file does not exist. Please do not ask the debian maintainer about it.
# You may use it to do strange and wonderful things, at your risk.

If there's no better alternative, I'll submit a patch for the
init.d/udev script to add the O|G|P commands.  If desired, I'll also
submit one for links.conf with the entries for nvidia commented out.
-- 
Rob


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-26 Thread Alexander Fieroch

Rob Sims wrote:

/var/log/Xorg.0.log has the information to debug this.

Apparently, in 2.6.13 the sysfs symbols were marked GPL only.  This
means that the nvidia entries don't make it, so udev can't create the
special files in /dev.

Creating the files by hand worked for me.  I've also added lines to my
udev config, but haven't booted since.  The changes were:
At the end of /etc/udev/links.conf:
# sysfs doesn't play with non-GPL modules as of 2.6.13
M nvidia0   c 195 0
M nvidia1   c 195 1
M nvidia2   c 195 2
M nvidia3   c 195 3
M nvidiactl c 195 255


At the end of /etc/udev/permissions.rules:
# nVidia
KERNEL=="nvidia*", MODE="0660", GROUP="video"



Hm, I did both and xorg is running again, but the devices /dev/nvidia* 
do not belong to the group video and the mode is not set to 660:


crw---  1 root root 195,   0 2005-09-26 19:48 /dev/nvidia0
crw---  1 root root 195,   1 2005-09-26 19:48 /dev/nvidia1
crw---  1 root root 195,   2 2005-09-26 19:48 /dev/nvidia2
crw---  1 root root 195,   3 2005-09-26 19:48 /dev/nvidia3
crw---  1 root root 195, 255 2005-09-26 19:48 /dev/nvidiactl

The group video does exist and I added at the end of 
/etc/udev/permissions.rules:

# nvidia
KERNEL=="nvidia*", MODE="0660", GROUP="video"

So what's missing that no group permissions are set?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-25 Thread Alexander Fieroch
Lennart Sorensen wrote:
> You can always try adding 'nvidia' to /etc/modules

Yes, I do have.

> Then it WILL load the module on boot.

No, the problem was udev that did not create the special nvidia devices.
Thanks to Rob Sims (same thread) the problem now is fixed for me.

Regards,
Alexander


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-25 Thread Alexander Fieroch
Rob Sims wrote:
> Creating the files by hand worked for me.  I've also added lines to my
> udev config, but haven't booted since.  The changes were:
> At the end of /etc/udev/links.conf:
> # sysfs doesn't play with non-GPL modules as of 2.6.13
> M nvidia0   c 195 0
> M nvidia1   c 195 1
> M nvidia2   c 195 2
> M nvidia3   c 195 3
> M nvidiactl c 195 255
> 
> 
> At the end of /etc/udev/permissions.rules:
> # nVidia
> KERNEL=="nvidia*", MODE="0660", GROUP="video"

Thank you very much. That fixes the problem.

Regards,
Alexander


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-22 Thread Angel Claudio Alvarez
El jue, 22-09-2005 a las 12:24 +0200, Alexander Fieroch escribió:
> Hello,
> 
> every time I reboot my computer (SID, kernel 2.6.13) xorg can not load 
> the nvidia driver build with m-a.
> I have uninstalled the previously installed proprietary nvidia driver 
> and build the nvidia driver with m-a. Then I've installed nvidia-glx and 
> restarted gdm - xorg is working. After reboot the nvidia driver can not 
> be loaded and xorg does not start but I can reinstall the previously 
> build /usr/src/nvidia-kernel-2.6.13_1.0.7174-3_amd64.deb and xorg is 
> working again.
> What's the problem?
> 
The same here
I think that the problem is the creation of the device (or update)
If you run "/var/lib/dpkg/info/nvidia-kernel-2.6.13-ck2.postinst
configure"
and then
/etc/init.d/gdm restart ( or kdm or xdm)
plop!
you have X again
I could not researched about udev yet ( i have a lot of work)
take a look at /var/lib/dpkg/info/nvidia-kernel-2.6.13-ck2.postinst


> Regards,
> Alexander

> 
> 
-- 
Angel Claudio Alvarez
Usuario Linux Registrado 143466
GPG Public Key en http://pgp.mit.edu
key fingerprint = 3AED D95B 7E2D E954 61C8  F505 1884 473C FC8C 8AC4



signature.asc
Description: This is a digitally signed message part


Re: nvida driver is not working after reboot

2005-09-22 Thread Rob Sims
On Thu, Sep 22, 2005 at 12:24:24PM +0200, Alexander Fieroch wrote:
> every time I reboot my computer (SID, kernel 2.6.13) xorg can not load 
> the nvidia driver build with m-a.
> I have uninstalled the previously installed proprietary nvidia driver 
> and build the nvidia driver with m-a. Then I've installed nvidia-glx and 
> restarted gdm - xorg is working. After reboot the nvidia driver can not 
> be loaded and xorg does not start but I can reinstall the previously 
> build /usr/src/nvidia-kernel-2.6.13_1.0.7174-3_amd64.deb and xorg is 
> working again.
> What's the problem?

/var/log/Xorg.0.log has the information to debug this.

Apparently, in 2.6.13 the sysfs symbols were marked GPL only.  This
means that the nvidia entries don't make it, so udev can't create the
special files in /dev.

Creating the files by hand worked for me.  I've also added lines to my
udev config, but haven't booted since.  The changes were:
At the end of /etc/udev/links.conf:
# sysfs doesn't play with non-GPL modules as of 2.6.13
M nvidia0   c 195 0
M nvidia1   c 195 1
M nvidia2   c 195 2
M nvidia3   c 195 3
M nvidiactl c 195 255


At the end of /etc/udev/permissions.rules:
# nVidia
KERNEL=="nvidia*", MODE="0660", GROUP="video"
-- 
Rob


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-22 Thread tony mancill
Jo Shields wrote:

> 2.6.13 doesn't work with 7174.

Hmmm... then I had better exit this X session immediately!  ;)

[EMAIL PROTECTED]:~$ grep "NVIDIA X" /var/log/Xorg.0.log
(II) NVIDIA X Driver  1.0-7174  Tue Mar 22 06:47:49 PST 2005

[EMAIL PROTECTED]:~$ uname -a
Linux honig 2.6.13 #3 Sun Sep 11 13:37:58 PDT 2005 x86_64 GNU/Linux

Seriously, thanks for pointing this out.  Do you have a reference that
indicates that they don't work together.  It does work sometimes - it's
working on my machine now - but it's not very reliable.  Perhaps there
is a race condition or some other issue with the module initialization
that disagrees with 2.6.13.

Anyway, time to get the newer drivers.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-22 Thread Lennart Sorensen
On Thu, Sep 22, 2005 at 04:26:27PM +0200, Sythos wrote:
> For nVidia, and *ONLY* for nVidia, I prefer download&compile directly
> from nvidia installer, there are too critical aspect every kernel
> subversion...
> 
> The time spent with nv-installer is about the same of "apt-get&C."

Some of us prefer to not have a mess and follow the rule of 'everything
in /usr comes from dpkg except /usr/local'

Saves lots of headaches on upgrades too since properly diverted files
aren't overwritten by dpkg, while manually installed stuff (like the
nvidia installer) will be.

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-22 Thread Jo Shields

Sythos wrote:


On Thu, Sep 22, 2005 at 12:24:24PM +0200, Alexander Fieroch wrote:
 

every time I reboot my computer (SID, kernel 2.6.13) xorg can not load 
the nvidia driver build with m-a.
   



For nVidia, and *ONLY* for nVidia, I prefer download&compile directly
from nvidia installer, there are too critical aspect every kernel
subversion...

The time spent with nv-installer is about the same of "apt-get&C."



But nvidia-installer overwrites a bunch of files dpkg is meant to handle 
(and the --uninstall option does NOT cleanly remove it).


So if your packages are upgraded (see: recent security updates to xfree 
in sarge), then your nvidia setup is half-overwritten by xfree versions. 
a nice messy mush is made.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-22 Thread Sythos
On Thu, Sep 22, 2005 at 12:24:24PM +0200, Alexander Fieroch wrote:
> every time I reboot my computer (SID, kernel 2.6.13) xorg can not load 
> the nvidia driver build with m-a.

For nVidia, and *ONLY* for nVidia, I prefer download&compile directly
from nvidia installer, there are too critical aspect every kernel
subversion...

The time spent with nv-installer is about the same of "apt-get&C."

-- 

Sythos - http://www.sythos.net
  ()  ASCII Ribbon Campaign - against html/rtf/vCard in mail
  /\- against M$ attachments


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-22 Thread Jo Shields

tony mancill wrote:


Alexander Fieroch wrote:
 


Hello,

every time I reboot my computer (SID, kernel 2.6.13) xorg can not load
the nvidia driver build with m-a.
I have uninstalled the previously installed proprietary nvidia driver
and build the nvidia driver with m-a. Then I've installed nvidia-glx and
restarted gdm - xorg is working. After reboot the nvidia driver can not
be loaded and xorg does not start but I can reinstall the previously
build /usr/src/nvidia-kernel-2.6.13_1.0.7174-3_amd64.deb and xorg is
working again.
What's the problem?
   



I ran into this as well after a recent apt-get upgrade (sometime last
week, I believe).  I'm also running sid and the 2.6.13 kernel.  The
nvidia module is loaded according to lsmod, but for some reason Xorg
doesn't think it's there.

The only thing that seemed to help me is reinstalling the nvidia-kernel
package as well.  I believe something more subtle is going on...

Cheers,
tony


 


2.6.13 doesn't work with 7174.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-22 Thread tony mancill
Alexander Fieroch wrote:
> Hello,
> 
> every time I reboot my computer (SID, kernel 2.6.13) xorg can not load
> the nvidia driver build with m-a.
> I have uninstalled the previously installed proprietary nvidia driver
> and build the nvidia driver with m-a. Then I've installed nvidia-glx and
> restarted gdm - xorg is working. After reboot the nvidia driver can not
> be loaded and xorg does not start but I can reinstall the previously
> build /usr/src/nvidia-kernel-2.6.13_1.0.7174-3_amd64.deb and xorg is
> working again.
> What's the problem?

I ran into this as well after a recent apt-get upgrade (sometime last
week, I believe).  I'm also running sid and the 2.6.13 kernel.  The
nvidia module is loaded according to lsmod, but for some reason Xorg
doesn't think it's there.

The only thing that seemed to help me is reinstalling the nvidia-kernel
package as well.  I believe something more subtle is going on...

Cheers,
tony


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-22 Thread Jo Shields

Alexander Fieroch wrote:


Hello,

every time I reboot my computer (SID, kernel 2.6.13) xorg can not load 
the nvidia driver build with m-a.
I have uninstalled the previously installed proprietary nvidia driver 
and build the nvidia driver with m-a. Then I've installed nvidia-glx 
and restarted gdm - xorg is working. After reboot the nvidia driver 
can not be loaded and xorg does not start but I can reinstall the 
previously build /usr/src/nvidia-kernel-2.6.13_1.0.7174-3_amd64.deb 
and xorg is working again.

What's the problem?

Regards,
Alexander



echo nvidia >> /etc/modules


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: nvida driver is not working after reboot

2005-09-22 Thread Lennart Sorensen
On Thu, Sep 22, 2005 at 12:24:24PM +0200, Alexander Fieroch wrote:
> every time I reboot my computer (SID, kernel 2.6.13) xorg can not load 
> the nvidia driver build with m-a.
> I have uninstalled the previously installed proprietary nvidia driver 
> and build the nvidia driver with m-a. Then I've installed nvidia-glx and 
> restarted gdm - xorg is working. After reboot the nvidia driver can not 
> be loaded and xorg does not start but I can reinstall the previously 
> build /usr/src/nvidia-kernel-2.6.13_1.0.7174-3_amd64.deb and xorg is 
> working again.
> What's the problem?

You can always try adding 'nvidia' to /etc/modules

Then it WILL load the module on boot.

If you run udev or something else silly that makes /dev virtual then
there is likely nothing there for X to try and open to cause modprobe to
load the nvidia driver, while if you just load the nvidia driver, the
device nodes will appear and work just fine.

With a regular /dev it should just notify modprobe when something (X)
tries to open the /dev/nvidia* nodes and then modprobe loads the nvidia
module due to:
athlon:~# cat /etc/modprobe.d/nvidia-kernel-nkc
alias char-major-195* nvidia

So of course if /dev/nvidia* doesn't exist (thanks to udev use or devfs)
then the alias may not help anything, and the module doesn't load.

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]