November 2008 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Root password to shutdown
by Quentin Jackson 23 Nov '08

23 Nov '08

Anyone else experiencing having to type in the root password all the time to shut their machine down? Don't see anything logged for this. Q -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 4

[opensuse-factory] Major Upgrade to Nvidia Driver for Video Playback
by Quentin Jackson 23 Nov '08

23 Nov '08

May be old news to some, but new news to me :) For those of you that like to play video on your machine and have NVIDIA cards (not legacy ones) the latest Nvidia driver (1.80.06) has support for what they're calling VDPAU which is apparently basically a unix implementation of PureVideo which has until now been available on Windows only as I understand it. The end result is much less CPU usage while running it with something such as mplayer-vdpau. Released November 14 2008 so fairly recent :) Benchmarks at: http://www.phoronix.com/scan.php?page=article&item=nvidia_vdpau&num=2 Looks nice to me, by the looks of below, will help with the new OpenSuSE compositing also...... downloading now.... ;) Thought people on here would like to know. Q Additional Release Highlights: * Added support for CUDA 2.1. * Added initial support for PureVideo-like features on Linux via the new VDPAU API (see the vdpau.h header file installed with the driver). * Added new workstation performance optimizations. * Enabled the X Render "GlyphCache" by default. * Disabled shared memory X pixmaps by default; see theAllowSHMPixmaps" option. * Fixed a regression that could result in window decorationcorruption when running Compiz using Geforce 6 and 7 series GPUs. * Improved X pixmap placement on GeForce 8 series and later GPUs. * Improved compatibility with recent Linux kernels. * Improved stability on some GeForce 8 series and newer GPUs. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 13

Re: [opensuse-factory] Major Upgrade to Nvidia Driver for Video Playback
by Quentin Jackson 23 Nov '08

23 Nov '08

On Sat, 2008-11-22 at 07:58 -0600, David C. Rankin wrote: > Quentin Jackson wrote: > > On Fri, 2008-11-21 at 23:51 -0500, Patrick Shanahan wrote: > >> * Sid Boyce <sboyce(a)blueyonder.co.uk> [11-21-08 23:39]: > >>> I have always had to do so or the long way before I found out about > >>> cloneconfig, "cd /usr/src/linux;cp /boot/config-`uname -r` .config;make > >>> oldconfig". > >> Using the NV...pkg directly from NVidia? > >> > >>> It's mentioned in an obscure place, see /usr/src/linux/README.SUSE, but > >>> no doubt documented elsewhere. > >> I don't recall it being with the install instructions referred by the > >> NVidia package specifically for openSUSE. > >> > >> You say you "have always had to", have you ever tried w/o? How do you > >> know this? > >> -- > >> Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 > >> http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 > >> Registered Linux User #207535 @ http://counter.li.org > > > > Actually it would be great to know what the perfect way of doing this > > and what the benefits are, if we can get more fps or somehow a more > > stable driver I'm sure everyone would want to know :) > > > > Q > > > > Q > > It has nothing to do with getting any more FPS out of a driver or making it > more stable, it has to do with making sure the driver (kernel module actually) > gets built (compiled against the present kernel) in the first place so that you > can run the driver package you are trying to install. > > In the past you needed to "prepare" the kernel before compiling a new module > against it. Which essentially meant cleaning up and getting rid of all the > pieces left over from whatever you built against the kernel last in case it > didn't do that for itself. > > The prescribed manner for doing that was/is: > > cd /usr/src/linux > make mrproper > make cloneconfig > /dev/null 2>&1 > make modules_prepare > make clean > > However, today, I have been told that preparing the kernel is no longer > necessary before building a kernel module because the opensuse kernel is in the > prepared state at the time it is installed. > > My view is that the traditional manner for preparing the kernel prior to > module compilation is a no-cost bit of insurance that everything has the best > chance of going right during the module build. Not to mention that if you throw > the 5 lines in a file and either put #!/bin/bash on top or call it with 'sh > filename' there's not a whole lot of work involved with doing it right anyway. > > And like was already suggested: > > cd /usr/src/linux > make help > > 07:56 alchemy/usr/src/linux> make help > Cleaning targets: > clean - Remove most generated files but keep the config and > enough build support to build external modules > mrproper - Remove all generated files + config + various backup files > distclean - mrproper + remove editor backup and patch files > > Configuration targets: > config - Update current config utilising a line-oriented program > menuconfig - Update current config utilising a menu based program > xconfig - Update current config utilising a QT based front-end > gconfig - Update current config utilising a GTK based front-end > oldconfig - Update current config utilising a provided .config as base > silentoldconfig - Same as oldconfig, but quietly > randconfig - New config with random answer to all options > defconfig - New config with default answer to all options > allmodconfig - New config selecting modules when possible > allyesconfig - New config where all options are accepted with yes > allnoconfig - New config where all options are answered with no > > Other generic targets: > all - Build all targets marked with [*] > * vmlinux - Build the bare kernel > * modules - Build all modules > modules_install - Install all modules to INSTALL_MOD_PATH (default: /) > dir/ - Build all files in dir and below > dir/file.[ois] - Build specified target only > dir/file.ko - Build module including final link > prepare - Set up for building external modules > tags/TAGS - Generate tags file for editors > cscope - Generate cscope index > kernelrelease - Output the release version string > kernelversion - Output the version stored in Makefile > headers_install - Install sanitised kernel headers to INSTALL_HDR_PATH > (default: /usr/src/linux-2.6.25.18-0.2/usr) > > Static analysers > checkstack - Generate a list of stack hogs > namespacecheck - Name space analysis on compiled kernel > versioncheck - Sanity check on version.h usage > includecheck - Check for duplicate included header files > export_report - List the usages of all exported symbols > headers_check - Sanity check on exported headers > > Kernel packaging: > rpm-pkg - Build both source and binary RPM kernel packages > binrpm-pkg - Build only the binary kernel package > deb-pkg - Build the kernel as an deb package > tar-pkg - Build the kernel as an uncompressed tarball > targz-pkg - Build the kernel as a gzip compressed tarball > tarbz2-pkg - Build the kernel as a bzip2 compressed tarball > > Documentation targets: > Linux kernel internal documentation in different formats: > htmldocs - HTML > installmandocs - install man pages generated by mandocs > mandocs - man pages > pdfdocs - PDF > psdocs - Postscript > xmldocs - XML DocBook > > Architecture specific targets (x86_64): > * bzImage - Compressed kernel image (arch/x86/boot/bzImage) > install - Install kernel using > (your) ~/bin/installkernel or > (distribution) /sbin/installkernel or > install to $(INSTALL_PATH) and run lilo > fdimage - Create 1.4MB boot floppy image (arch/x86/boot/fdimage) > fdimage144 - Create 1.4MB boot floppy image (arch/x86/boot/fdimage) > fdimage288 - Create 2.8MB boot floppy image (arch/x86/boot/fdimage) > isoimage - Create a boot CD-ROM image (arch/x86/boot/image.iso) > bzdisk/fdimage*/isoimage also accept: > FDARGS="..." arguments for the booted kernel > FDINITRD=file initrd for the booted kernel > > make V=0|1 [targets] 0 => quiet build (default), 1 => verbose build > make V=2 [targets] 2 => give reason for rebuild of target > make O=dir [targets] Locate all output files in "dir", including .config > make C=1 [targets] Check all c source with $CHECK (sparse by default) > make C=2 [targets] Force check of all c source with $CHECK > > > > > -- > David C. Rankin, J.D.,P.E. | > Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 > www.rankinlawfirm.com | http://counter.opensuse.org/11.1/small OK Thanks for the info, I guess if it's only to do with compiling the kernel module and performance etc isn't effected I can just keep doing what I always do, INIT 3, run the NVIDIA driver script, let it uninstall and fix everything up, INIT 5. Seems to work for me and is about as simple as it gets next to one click. I actually do the whole sax2 -r -m 0=nvidia thing too, but from what I'm reading here it seems I don't need to. Q > -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Compiz openSUSE 11.0 Beta 5 anyone working with Nvidia driver?
by Ben Kevan 23 Nov '08

23 Nov '08

Hey folks, I just wanted to see if the problem was with compiz, or with my nvidia driver ( i haven't yet tried the nv driver) have gotten compiz from the oss repository working on their box.. None of my compiz decorations start, and none of the compiz features actually work. I just want to see if it's a bigger problem then I expected. Ben -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 6

Re: [opensuse-factory] Root password to shutdown
by Quentin Jackson 22 Nov '08

22 Nov '08

On Sat, 2008-11-22 at 12:21 +0100, Stephan Binner wrote: > On Saturday 22 November 2008 03:32:26 Quentin Jackson wrote: > > > Anyone else experiencing having to type in the root password all the > > time to shut their machine down? Don't see anything logged for this. > > http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.1_dev > > Bye, > Steve Thanks! I didn't notice it. Q -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

Re: [opensuse-factory] Major Upgrade to Nvidia Driver for Video Playback
by Quentin Jackson 22 Nov '08

22 Nov '08

On Fri, 2008-11-21 at 23:51 -0500, Patrick Shanahan wrote: > * Sid Boyce <sboyce(a)blueyonder.co.uk> [11-21-08 23:39]: > > > > I have always had to do so or the long way before I found out about > > cloneconfig, "cd /usr/src/linux;cp /boot/config-`uname -r` .config;make > > oldconfig". > > Using the NV...pkg directly from NVidia? > > > It's mentioned in an obscure place, see /usr/src/linux/README.SUSE, but > > no doubt documented elsewhere. > > I don't recall it being with the install instructions referred by the > NVidia package specifically for openSUSE. > > You say you "have always had to", have you ever tried w/o? How do you > know this? > -- > Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 > http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 > Registered Linux User #207535 @ http://counter.li.org Actually it would be great to know what the perfect way of doing this and what the benefits are, if we can get more fps or somehow a more stable driver I'm sure everyone would want to know :) Q -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 7

Re: [opensuse-factory] Compiz openSUSE 11.0 Beta 5 anyone working with Nvidia driver?]
by Jogchum Reitsma 22 Nov '08

22 Nov '08

<off-topic> It seems to be netiquette not to top-post, but personally I'm stubborn enough to firmly believe that that's quite unhandy in at least my workflow, and I absolutely prefer topposting. But I seem to be one of few in this; nice to see I have a companion :-) </off-topic> Quentin Jackson schreef: >> Please try to post underneath your replies. It makes threading a whole >> > lot > >> easier. >> > > Whoops, someone else pointed that out, it's a new habit which goes > against my corporate teachings whereby they encourage you not to do > that! Why can't everything be simple. :) > > regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] updating from beta's to RC, etc
by Richard Allen 22 Nov '08

22 Nov '08

Hi I have a question that seems to get mixed answers. On news.opensuse.org it has been stated by people that we can update from the beta to the release candidate to then the final release without having to download and do a fresh install. However on the Opensuse Forum, the moderators speak against it saying that we should do a clean install because config files from the beta could be left behind. Gets confusing when you have one part of Opensuse saying you can do it, and another part saying you shouldn't do it. So could someone please clarify whether updating from the beta to the RC to the final release is recommend, or if we should do a clean install Thanks. Richard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

[opensuse-factory] Is Bug 446947 fixed or not?
by David C. Rankin 22 Nov '08

22 Nov '08

List, I don't know how to interpret what I read in bugzilla with regard to the disposition of: https://bugzilla.novell.com/show_bug.cgi?id=446947 Bug 446947 was filed because KDE 4 kdesudo did not honor visudo changes. Sudo users were still prompted for a work around described in the bug. Bug 446947 was 'Resolved' by being marked as a 'Duplicate of Bug 400903' which dealt with "kdesu does not acknowledge NOPASSWD: ALL in sudoers" The closing comment was 'It is kdesu, not kdesudo' Now here is where it gets murky: Bug 400903 is closed as 'Resolved WONTFIX'. The closing comments of were "Kdesu now again defaults to using su instead of sudo because of various problems with using sudo there. You can change the default using 'kwriteconfig --file kdesurc --group super-user-command --key super-user-command sudo'." What does this mean? Does it mean the problem, regardless of whether it is with kdesu or sudo that the problem is being fixed? Does it mean that whatever the problem is, it is *not* being fixed and perplexed users are left to hopefully stumble across bug No. 400903 to find a work around? Why doesn't somebody just put a comment in the visudo file to warn users about this problem? -- David C. Rankin, J.D.,P.E. | Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 www.rankinlawfirm.com | http://counter.opensuse.org/11.1/small -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] Opera opensuse 11.1 Beta 5.2 Fonts shrunk for google
by Ben Kevan 22 Nov '08

22 Nov '08

Just wanted to see if others have experienced this issue: Here's a screenshot of the fonts from a previous build (9.62-1.1) [1] And another from the newest build of 9.62-2.1 [2] Both are using the same .opera folders, and have uninstalled and re-installed serveral times to make sure I wasn't losing it. I've filed a bug report [3] for anyone that cares [1] https://bugzilla.novell.com/attachment.cgi?id=254503 [2] https://bugzilla.novell.com/attachment.cgi?id=254504 [3] https://bugzilla.novell.com/show_bug.cgi?id=447882 Anyone experience this? I used finance.google.com to check. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2