Re: upgrade to 2.6.5 problem

2004-05-18 Thread Keir Lawson
On Fri, 2004-05-14 at 14:38 -0400, Emma Jane Hogbin wrote:
> On Fri, May 14, 2004 at 03:19:32PM +0100, Keir Lawson wrote:
> > On Wed, 2004-05-12 at 16:03 -0400, Emma Jane Hogbin wrote:
> > > On Wed, May 12, 2004 at 09:17:54AM +0100, Keir Lawson wrote:
> > > ### update-modules: start processing /etc/modutils/nvidia-kernel
> > > alias /dev/nvidia* nvidia
> > > alias char-major-195 nvidia
> > > ### update-modules: end processing /etc/modutils/nvidia-kernel
> > > 
> > > ### update-modules: start processing /etc/modutils/nvidia-kernel-2.4.20.basil
> > > alias /dev/nvidia* NVdriver
> > > alias char-major-195 NVdriver
> > > ### update-modules: end processing /etc/modutils/nvidia-kernel-2.4.20.basil
> > > 
> > > ### update-modules: start processing /etc/modutils/nvidia-kernel-nkc
> > > alias char-major-195 nvidia
> > > ### update-modules: end processing /etc/modutils/nvidia-kernel-nkc
> > > 
> > > There's only the one line that's different:
> > >   alias /dev/nvidia* nvidia
> > > (the NVdriver is the old name that doesn't get used anymore.) But I've
> > > *never* had to edit this file by hand for Nvidia (yes for sound though).
> > > You can just edit it by hand...I had to for sound...and the world didn't
> > > collapse. :)
> > well i i dont seem to have a /etc/modutils/nvidia-kernel-2.4.20.basil or
> > equivalent file... perhaps this is the problem?
> 
> It's only a problem if you named your kernel version "basil." You should
> have the parts that are *in between* the ### commented out lines.
> 
> emma
i think my modules.conf is configured OK, perhaps the module isnt in the
search path where do i look to find the nvidia module explicitly
pointing to the nvidio,ko file?

Keir


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



Re: upgrade to 2.6.5 problem

2004-05-15 Thread John L Fjellstad
csj <[EMAIL PROTECTED]> writes:

>> He would be better off doing it the udev way, namely adding it to the
>> rules file, like this:
>> KERNEL="mixer*", NAME="sound/%k", SYMLINK="%k"
>> (add the SYMLINK statement to the rule)
>
> Or maybe by creating a custom rules file in rules.d, which can be
> retained across upgrades, like:
>
> /etc/udev/rules.d/mixer.rule

If you are going to do that, make sure that the rule is
KERNEL="mixer*", SYMLINK="%k"

That is, you remove the NAME statement, since udev will only use one
NAME statement pr node.
Also, there is a bug current udev (024) where the udev rule parser will
stop at the first rule with NAME, so you have to make sure your rules
comes up before the rule with the NAME statement (although, this might
have been fixed in the debian version of udev... I really should convert
over one of these days).

-- 
John L. Fjellstad
web: http://www.fjellstad.org/  Quis custodiet ipsos custodes


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



Re: upgrade to 2.6.5 problem

2004-05-14 Thread csj
On 14. May 2004 at 3:11PM +0200,
John L Fjellstad <[EMAIL PROTECTED]> wrote:

> csj <[EMAIL PROTECTED]> writes:
> 
> >> yup... anyway i discovered that to get audio etc i just had to
> >> add myself to the audio and video groups... problem solved,
> >> just one now, when i create a '/dev/sound' directory and put a
> >> link to /dev/mixer in it (gnome volume control needs this for
> >> some reason) when i reboot it disapears
> >
> > Do you create the /dev/sound directory via /etc/udev/links.conf?
> > If not, maybe you can put in /etc/udev/links.conf something like:
> >
> > D sound
> > L sound/mixer   /dev/mixer
> 
> He would be better off doing it the udev way, namely adding it to the
> rules file, like this:
> KERNEL="mixer*", NAME="sound/%k", SYMLINK="%k"
> (add the SYMLINK statement to the rule)

Or maybe by creating a custom rules file in rules.d, which can be
retained across upgrades, like:

/etc/udev/rules.d/mixer.rule


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



Re: upgrade to 2.6.5 problem

2004-05-14 Thread Emma Jane Hogbin
On Fri, May 14, 2004 at 03:19:32PM +0100, Keir Lawson wrote:
> On Wed, 2004-05-12 at 16:03 -0400, Emma Jane Hogbin wrote:
> > On Wed, May 12, 2004 at 09:17:54AM +0100, Keir Lawson wrote:
> > ### update-modules: start processing /etc/modutils/nvidia-kernel
> > alias /dev/nvidia* nvidia
> > alias char-major-195 nvidia
> > ### update-modules: end processing /etc/modutils/nvidia-kernel
> > 
> > ### update-modules: start processing /etc/modutils/nvidia-kernel-2.4.20.basil
> > alias /dev/nvidia* NVdriver
> > alias char-major-195 NVdriver
> > ### update-modules: end processing /etc/modutils/nvidia-kernel-2.4.20.basil
> > 
> > ### update-modules: start processing /etc/modutils/nvidia-kernel-nkc
> > alias char-major-195 nvidia
> > ### update-modules: end processing /etc/modutils/nvidia-kernel-nkc
> > 
> > There's only the one line that's different:
> > alias /dev/nvidia* nvidia
> > (the NVdriver is the old name that doesn't get used anymore.) But I've
> > *never* had to edit this file by hand for Nvidia (yes for sound though).
> > You can just edit it by hand...I had to for sound...and the world didn't
> > collapse. :)
> well i i dont seem to have a /etc/modutils/nvidia-kernel-2.4.20.basil or
> equivalent file... perhaps this is the problem?

It's only a problem if you named your kernel version "basil." You should
have the parts that are *in between* the ### commented out lines.

emma

-- 
Emma Jane Hogbin
[[ 416 417 2868 ][ www.xtrinsic.com ]]


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



Re: upgrade to 2.6.5 problem

2004-05-14 Thread Keir Lawson
On Wed, 2004-05-12 at 16:03 -0400, Emma Jane Hogbin wrote:
> On Wed, May 12, 2004 at 09:17:54AM +0100, Keir Lawson wrote:
> > the only line mentioning nvidia is this one:
> > alias char-major-195 nvidia
> 
> Did you load the module using insmod and then run update-modules? This
> *should* edit the /etc/modules.conf file for you, but you must load the
> module before running the program.
> 
> > but having rebooted with this line present the problem still persists. i
> > dont know exactly how to edit modules.conf and at the top it has a
> > warning about not editing it 
> 
> Mine has the following:
> 
> ### update-modules: start processing /etc/modutils/nvidia-kernel
> alias /dev/nvidia* nvidia
> alias char-major-195 nvidia
> ### update-modules: end processing /etc/modutils/nvidia-kernel
> 
> ### update-modules: start processing /etc/modutils/nvidia-kernel-2.4.20.basil
> alias /dev/nvidia* NVdriver
> alias char-major-195 NVdriver
> ### update-modules: end processing /etc/modutils/nvidia-kernel-2.4.20.basil
> 
> ### update-modules: start processing /etc/modutils/nvidia-kernel-nkc
> alias char-major-195 nvidia
> ### update-modules: end processing /etc/modutils/nvidia-kernel-nkc
> 
> There's only the one line that's different:
>   alias /dev/nvidia* nvidia
> (the NVdriver is the old name that doesn't get used anymore.) But I've
> *never* had to edit this file by hand for Nvidia (yes for sound though).
> You can just edit it by hand...I had to for sound...and the world didn't
> collapse. :)
well i i dont seem to have a /etc/modutils/nvidia-kernel-2.4.20.basil or
equivalent file... perhaps this is the problem?

keir lawson


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



Re: upgrade to 2.6.5 problem

2004-05-14 Thread John L Fjellstad
csj <[EMAIL PROTECTED]> writes:

>> yup... anyway i discovered that to get audio etc i just had to
>> add myself to the audio and video groups... problem solved,
>> just one now, when i create a '/dev/sound' directory and put a
>> link to /dev/mixer in it (gnome volume control needs this for
>> some reason) when i reboot it disapears
>
> Do you create the /dev/sound directory via /etc/udev/links.conf?
> If not, maybe you can put in /etc/udev/links.conf something like:
>
> D sound
> L sound/mixer /dev/mixer

He would be better off doing it the udev way, namely adding it to the
rules file, like this:
KERNEL="mixer*", NAME="sound/%k", SYMLINK="%k"
(add the SYMLINK statement to the rule)

Or even better, change where gnome volume control can find the mixer

-- 
John L. Fjellstad
web: http://www.fjellstad.org/  Quis custodiet ipsos custodes


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



Re: upgrade to 2.6.5 problem

2004-05-13 Thread csj
On 12. May 2004 at 8:59AM +0100,
Keir Lawson <[EMAIL PROTECTED]> wrote:

> On Wed, 2004-05-12 at 06:22 +0800, csj wrote:
> > On 11. May 2004 at 7:34PM +0100,
> > Keir Lawson <[EMAIL PROTECTED]> wrote:
> > 
> > > I recently upgraded from kernel 2.4.25 to kernel 2.6.5 (im using
> > > unstable) - the upgrade went OK but now i have two problems:
> > > 
> > > 1. the nvidia graphics module isnt loaded on startup (i have to
> > > do insmod /lib/modules/2.6.5-1-k7/nvidia/nvidia.ko before i can
> > > enter the xserver)
> > > 
> > > 2. permission are mucked up, for both oss (/dev/dsp,/dev/mixer)
> > > alsa (/dev/snd/*), and nvidia stuff (/dev/nv*), when i change
> > > anything in /dev (creating a folder, changing permissions) the
> > > changes revert on reboot
> > 
> > Do you have udev installed?
>
> yup... anyway i discovered that to get audio etc i just had to
> add myself to the audio and video groups... problem solved,
> just one now, when i create a '/dev/sound' directory and put a
> link to /dev/mixer in it (gnome volume control needs this for
> some reason) when i reboot it disapears

Do you create the /dev/sound directory via /etc/udev/links.conf?
If not, maybe you can put in /etc/udev/links.conf something like:

D sound
L sound/mixer   /dev/mixer


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



Re: upgrade to 2.6.5 problem

2004-05-11 Thread csj
On 11. May 2004 at 7:34PM +0100,
Keir Lawson <[EMAIL PROTECTED]> wrote:

> I recently upgraded from kernel 2.4.25 to kernel 2.6.5 (im using
> unstable) - the upgrade went OK but now i have two problems:
> 
> 1. the nvidia graphics module isnt loaded on startup (i have to
> do insmod /lib/modules/2.6.5-1-k7/nvidia/nvidia.ko before i can
> enter the xserver)
> 
> 2. permission are mucked up, for both oss (/dev/dsp,/dev/mixer)
> alsa (/dev/snd/*), and nvidia stuff (/dev/nv*), when i change
> anything in /dev (creating a folder, changing permissions) the
> changes revert on reboot

Do you have udev installed?


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



Re: upgrade to 2.6.5 problem

2004-05-11 Thread Emma Jane Hogbin
On Tue, May 11, 2004 at 07:34:16PM +0100, Keir Lawson wrote:
> 1. the nvidia graphics module isnt loaded on startup (i have to do
> insmod /lib/modules/2.6.5-1-k7/nvidia/nvidia.ko before i can enter the
> xserver)

/etc/init.d/nvidia-glx start
cd /lib/modules/2.6.5.dilbert/nvidia
modprobe nvidia

Then in /etc/modules.conf make sure you have the "nvidia" module listed.
You may also want to run "update-modules" after loading the module. It
seems to append the /etc/modules.conf file with whatever extras you have
loaded, but aren't in that file.

hope that helps,
emma

-- 
Emma Jane Hogbin
[[ 416 417 2868 ][ www.xtrinsic.com ]]


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



upgrade to 2.6.5 problem

2004-05-11 Thread Keir Lawson
I recently upgraded from kernel 2.4.25 to kernel 2.6.5 (im using
unstable) - the upgrade went OK but now i have two problems:

1. the nvidia graphics module isnt loaded on startup (i have to do
insmod /lib/modules/2.6.5-1-k7/nvidia/nvidia.ko before i can enter the
xserver)

2. permission are mucked up, for both oss (/dev/dsp,/dev/mixer) alsa
(/dev/snd/*), and nvidia stuff (/dev/nv*), when i change anything
in /dev (creating a folder, changing permissions) the changes revert on
reboot

Keir Lawson



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