Announcement
Collapse
No announcement yet.
NVIDIA Issues New 302 Linux Beta
Collapse
X
-
Wow... I haven't interacted with runlevels since the olllllllllllllllllllllllllllld (OLD) days of RedHat. I thought I was done with those forever. But I'll come back to this and give it a try the next time an update comes out. Thanks.
-
Originally posted by johnc View PostHow can I do this then? Because I get nvidia driver updates frequently and if there's an easier way, I'd want to do it.
The way I was doing it was to log out of my gnome session, go to a VT, login, kill all gnome and X stuff, rmmod the module, insmod the new one, then restart X and gnome, logout on the VT console then go back to my X VT and login. Is there an easier way?
Instead of wasting your time ~ open gnome-terminal and type: 'sudo init 3' - which will do all of that in one fowl swoop, minus switching VTs which isn't even needed in this case.... then once you have unloaded / reloaded (new) nvidia... then just type; sudo init 5 (which will start up everything again) ~ that's what i mean about linux basics, understanding what something as old and common place as runlevels. what they are and how to use them, properly.
you are doing a bunch of unnecessary stuff, that probably does make rebooting seem easier.
Originally posted by johnc View PostIn comparison, rebooting takes about 15 seconds for me and requires no input after selecting the option. The biggest neg to the reboot is that I lose my open windows and have to login and restart everything, but that seems necessary regardless.
Originally posted by johnc View PostMaybe on the same topic... I'm kinda surprised that kernel hot-swapping isn't available yet. Haven't they been talking about this for years?Last edited by ninez; 21 May 2012, 05:02 PM.
Leave a comment:
-
Originally posted by ninez View PostI don't think that 'not.sure' was overstating it at all. Going from init 5 to init3, unload/reload nvidia, then switch back to init 5 is not a big deal, nor difficult to do and is many times faster than rebooting.
I would argue that rebooting is only easier if the user doesn't really know what i would call "linux basics" and/or they are uncomfortable with maintaining their own system.
The way I was doing it was to log out of my gnome session, go to a VT, login, kill all gnome and X stuff, rmmod the module, insmod the new one, then restart X and gnome, logout on the VT console then go back to my X VT and login. Is there an easier way?
In comparison, rebooting takes about 15 seconds for me and requires no input after selecting the option. The biggest neg to the reboot is that I lose my open windows and have to login and restart everything, but that seems necessary regardless.
Maybe on the same topic... I'm kinda surprised that kernel hot-swapping isn't available yet. Haven't they been talking about this for years?
Leave a comment:
-
Originally posted by johnc View PostWell... "easy driver updates w/o reboot" is overstating it a bit. I mean you do have to close down X, unload the blob kernel module, reload the new one, then restart X. You can do it... but rebooting is probably easier.
I would argue that rebooting is only easier if the user doesn't really know what i would call "linux basics" and/or they are uncomfortable with maintaining their own system.
Leave a comment:
-
Originally posted by smitty3268 View Postkernel modesetting is required, KMS is not.
They really should have named KMS something else, because it seems every single time KMS comes up people confuse the OSS API implementation with the general idea the acronym stands for.
Leave a comment:
-
Originally posted by not.sure View PostI'm not.sure KMS was such a great idea to begin with. For example, is it possible to switch between nouveau and blob without rebooting? It seems thanks to KMS you can't ever unload the nouveau kernel module, whereas the blob is only needed to start X. That also allows for easy driver updates w/o reboot.
Leave a comment:
-
Originally posted by crazycheese View PostIsn't KMS also required to run Xorg as non-root, due to drivers shifting into kernelspace ring (so no root priviledges for hardware-level calls are needed with KMS) ? So, KMS = tolerance against priveledge escals in Xorg.
They really should have named KMS something else, because it seems every single time KMS comes up people confuse the OSS API implementation with the general idea the acronym stands for.
Leave a comment:
-
Originally posted by Gusar View PostAnd yes, you can switch between drivers without reboot. You need to unbind nouveau from the console, then you can rmmod the module. From here:Code:echo 0 > /sys/class/vtconsole/vtcon1/bind rmmod nouveau /etc/init.d/consolefont restart rmmod ttm rmmod drm_kms_helper rmmod drm
Leave a comment:
-
Originally posted by Gusar View PostI recall tests showing that KMS/DRI2 actually has a bit lower performance than UMS/DRI1.
Leave a comment:
-
Originally posted by crazycheese View PostIsn't KMS also required to run Xorg as non-root, due to drivers shifting into kernelspace ring (so no root priviledges for hardware-level calls are needed with KMS) ?
Originally posted by crazycheese View PostAlso, KMS gives a bit of performance boost and frees from Xorg dependency for graphics per se.
Leave a comment:
Leave a comment: