Alexander Dalloz wrote:
Am Fr, den 16.04.2004 schrieb Clint Harshaw um 22:41:
Mike DeHaan wrote:
What does "uname -r" yield in runlevel 3 verses runlevel 5?
2.4.22-1.2179.nptl for both 3 and 5
Sure, what was to be expecting. The kernel can only change on boot time. Once a kernel is loaded and init runs, changing the runlevel does not change anything with the (monolithic Linux) kernel itself. The init scripts for each runlevel only say whether a service is running or not.
Alexander
I wanted to be sure that I described what I did earlier correctly. I did. I changed the run level to 3, rebooted into 2179, logged in as root, and typed:
CC="gcc32" sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --add-this-kernel
followed by:
CC="gcc32" sh NVIDIA-Linux-x86-1.0-5336-pkg1-custom.run
(I made sure that I was using 2174 kernel by typing uname -a before doing those steps, even though I knew I selected that in the boot).
I then edited XF86Config, commenting out the load dri line and making sure the driver was nvidia rather than nv.
I then exited as root, and logged in as me. I typed startx, and the nvidia splash screen came up, and I could run all the GL packages just fine.
Then I exited, and logged in as root. I edited /etc/inittab to change the run level to 5. I then did shutdown -r now. When the boot comes up, I select the 2179 kernel. Among the startup details is the line:
nvidia.o module for 2.4.22-1.2179.nptl not found Disabling nvidia driver
X does start up, but not with capability to run any GL-related packages (such as glxgears). The nvidia splash screen does not display.
Here are the other approaches I have tried with the same symptoms a) just doing sh NVIDIA-Linux-x86-1.0-5336-pkg1.run b) tried an older driver using the same instructions I gave earlier
I rebooted into the old 2174 kernel, and using the same steps outlined, have compiled the nvidia driver so that it is working just fine for runlevel 3 and 5. I just can't get it to function with runlevel 5 and the 2179 kernel. I have a similar machine at my office, that the instructions for the driver worked flawlessly with the new kernel. So I'm inclined to believe it may be something machine specific. But I don't know what else to try.
Clint -- Clint Harshaw <clint@xxxxxxxxxxxxxxxxxxxx>
