[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 2.6 and nvidia

On Mon, 2004-05-10 at 03:33, Emma Jane Hogbin wrote:
> On Mon, May 10, 2004 at 03:19:18AM -0400, Emma Jane Hogbin wrote:
> > that works. (What's the new stuff in the kernel that has to do with screen
> > resolution? I probably messed up somewhere around there...when I did my
> > make oldconfig)

Here is my Odyssey of 2.6.x:

It actually started with me installing 2.6.0-test(something) and udev
quite a while ago (in internet terms a while ago). Every Freaking time I
installed udev, everything just died.

udev went bye-bye every-time I tried it, mainly cause I didn't have time
to mess with it.

So, here I go and actually build an exact replica of the Herbert Xu
Debian Kernel 2.6.5-1(2.6.5-4 revision) .deb and headers.deb and an
nvidia-modules.deb (1.0-5336). (I rather like to do this :) I can post
my madness^Wmethods for everyone to see, if anyone cares to see it.

I installed the kernel, nvidia, udev and VMware I was determined to make
it work. As neither the nvidia or vmware modules put info in the sysfs 

BTW put this into your fstab:

  sysfs /sys sysfs defaults 0 0
  none /sys/bus/usb usbfs defaults 0 0

It is needed to really make the whole process work better. I still am
using hotplug, so I removed discover(1 and 2) as hotplug and discover
overlap something fierce.

Well, I ended up having to add "nvidia" and "ide-cd" to /etc/modules and
make a script that created the udev nodes every-time (as neither nvidia
or VMware) to function properly.

here are the scripts:

if [ -e /dev/.udev.tdb ]; then
  for i in 0 1 2 3 4 5 6 7; do
      rm -f $node
      mknod $node c 195 $i || error "mknod \"$node\""
      chmod 0666 $node     || error "chmod \"$node\""
  rm -f $node
  mknod $node c 195 255    || error "mknod \"$node\""
  chmod 0666 $node         || error "chmod \"$node\""
exit 0

if [ -e /dev/.udev.tdb ]; then
  for i in 0 1 2 3; do
      rm -f $node
      mknod $node c 99 $i || error "mknod \"$node\""
      chmod 0600 $node    || error "chmod \"$node\""
  for i in 0 1 2 3 4 5 6 7 8 9; do
      rm -f $node
      mknod $node c 119 $i || error "mknod \"$node\""
      chmod 0600 $node     || error "chmod \"$node\""
  rm -f $node
  mknod $node c 10 165    || error "mknod \"$node\""
  chmod 0660 $node        || error "chmod \"$node\""
exit 0

(don't forget to flag them executable and owned by root.root)

I then created symbolic links in /etc/rcS.d/ as

  S26mknvdev -> ../init.d/mknvdev
  S26mkvmdev -> ../init.d/mkvmdev

Which is right after devmapper starts and way after udev starts.

That is how I have taken care of my problems... might not be "proper",
but then again it does work... EVERY-TIME!

ciao! Good luck!
REMEMBER ED CURRY! http://www.iwethey.org/ed_curry

Novell's Directory Services is a competitive product to Microsoft's
Active Directory in much the same way that the Saturn V is a competitive
product to those dinky little model rockets that kids light off down at
the playfield. -- Thane Walkup

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

Reply to: