June 2009 - openSUSE Users - openSUSE Mailing Lists

[opensuse] kde4.2 plasmarc resets
by Tamas Sarga 30 Jun '09

30 Jun '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm totally confused. Right now happened again that my plasma settings reseted. From a login (shutdown, than boot) to login, every plasma settings were lost. But only plasma, other things, like focus follows mouse and keyboard shortcuts etc. are fine. I don't know what is the cause. Maybe, if I remember correct then the last time and now I ran out of space on /home while I ran kde, than deleted some files to create space and work on, and shutdown, boot, and plasma setting are gone. So at the shutdown time I had free space. I can't see, how it could cause problem, so maybe it is just coincidence. It happened twice in a week, and never before. Thanks for any help or idea. I absolutely lost, so I don't know, what else information needed. Standard openSuse 11.1 with the kde 4.2 repo. x86 with nvidia fx5200. TIA. Tamas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkpJdXoACgkQsuVyj8v2Zy5i4QCfQ8ksb/ePNNgVvvlXOz5SU5Dw 1NIAnR6hGzuBSrM9YkRFKVt8chnH5uSv =W64p -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Re: Problems with ATI Radeon HD 2400 Pro
by Dr. Ing. Dieter Jurzitza 30 Jun '09

30 Jun '09

Hi Chuck, I am facing similar issues with anything related to fglrx from any version higher than 8.573 (the one from January, 30th). Anything more recent than this causes me an issue that reminds me of what you tell: - screen goes black, - if I log in remotely, X11 hangs at 100% CPU load, - nothing happens any more. I have a HD 2600 Pro and guess your's is AGP like mine(?). If so, you'd better act as follows: - get yourself the version from ATI with the revision number 8.573 - do a /bin/sh ./atiati-driver-installer-9-1-x86.x86_64.run --buildpkg SuSE/SUSE111- IA32 (or whatever version is apropriate for your system, you'll get them by the command bin/sh ./atiati-driver-installer-9-1-x86.x86_64.run --listpkg) - remove all other fglrx-related packages, - install the rpm that has been generated by the call you performed rpm -hiv fglrx_7_1_0_SUSE103-8.573-1.i386.rpm (in my case, naming might differ for your system) - do a sax2 -r -m 0=fglrx - be happy (hopefully!) Hope this helps, If it does, let me know. Take care Dieter Jurzitza -- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) ----------------------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] cannot find why postfix says "relay denied" when mailing from localhost
by Leen de Braal 29 Jun '09

29 Jun '09

Hi all, Strange thing: - opensuse11.1 - postfix - squirrelmail Sending mail out from squirrelmail gives a "Relay access denied" message. Also mailing from the command line with telnet to port25 gives same error. I have mynetworks: mynetworks = 192.168.1.0/24, 127.0.0.0/8 so what am I missing?? Incoming mail is fine, fetchmail is also working ok. -- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 F +31 115 649444 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 3

[opensuse] Dansguardian Anti-Virus Scanning Enabled?
by Anthony Simonelli 29 Jun '09

29 Jun '09

I downloaded Dansguardian 2.10 from the Education repository. Everything is installed and works great with Squid on openSUSE. However, I was wondering about anti-virus scanning. According to the Dansguardian FAQ, anti-virus scanning has been integrated into version 2.10 but still exists as a plugin for earlier versions. Since I am using version 2.10, I was wondering how to enable this because I cannot find anything in the configuration file, nor does it detect a virus when downloading the EICAR test files. Do I have to download the source package and compile it with Anti-Virus Support or am I missing something in my configuration file? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] kernel mismatch with uname and pkg installed
by Shawn Protsman 29 Jun '09

29 Jun '09

I've been running 11.1 for some time now without a hitch (mostly). After an update this morning I noticed a very odd issue. When I boot I have one selection for the 2.6.27.23 kernel. Once I log in and check uname it displays the old kernel. Any ideas how I can remedy this oddity? ~] uname -r 2.6.27.21-0.1-default ~] rpm -qa | grep kernel kernel-default-extra-2.6.27.23-0.1.1 kernel-default-base-2.6.27.23-0.1.1 linux-kernel-headers-2.6.27-2.28 kernel-syms-2.6.27.23-0.1.1 kernel-default-2.6.27.23-0.1.1 kernel-source-2.6.27.23-0.1.1 --Shawn -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] susefox Firefox Plugin
by Sascha 'saigkill' Manns 29 Jun '09

29 Jun '09

Hello Mates, after my last Firefox update i've noticed that an new Plugin are installed, called "susefox". What makes this Plugin? Does anyone knows this? -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com

2 2

[opensuse] Re: Nvidia GFX kernel modules for older 11.1-kernel 2.6.27.7-9, anywhere?
by Joachim Schrod 29 Jun '09

29 Jun '09

Manfred Hollstein wrote: > On Mon, 29 Jun 2009, 14:04:04 +0200, Joachim Schrod wrote: >> Per Jessen wrote: >> > Joachim Schrod wrote: >> > >> >> I'm looking for the proprietary Nvidia driver (kernel module) for a >> >> GeForce FX 5200 graphics card. A rpm is supposed to be at >> >> http://download.nvidia.com/opensuse/11.1/, named >> >> nvidia-gfxG01-kmp-pae. >> >> >> >> But there is only a RPM for the most current 11.1 kernel, version >> >> 2.6.27.23_0.1. I need one for kernel 2.6.27.7-9. (I can't use the >> >> most current kernel since VMware Server 1 doesn't work properly >> >> with it anymore.) >> >> >> >> Is there anywhere a repository archive for older versions where I >> >> can fetch a respective RPM for my kernel? >> >> Alternatively, is there another possibility to install that driver? >> > >> > If the actual nvidia driver isn't any different, you could just install >> > the latest rpm with --force ? >> >> Of course, I tried that already... :-) That doesn't work, the >> kernel modules don't fit. (The error message at insmod time is >> "Invalid module format".) >> >> Actually, I didn't expect them to work, calling insmod was pure >> mischief. From my VMware problems I know that quite a lot seemed to >> have happened between 2.6.27.7 and 2.6.27.23. > > Dunno for how long it'll work, but the following site helped me: > > <http://www.insecure.ws/2008/10/20/vmware-specific-specific-55x-and-kernel-2…> That's the patch I'm using that works on 2.6.27.7. Starting with the upgrade to 2.6.27.21 (and now 2.6.27.23), Windows clients use 100% CPU time all the time. Linux clients are OK. Windows clients also have serious problems with clock thrift. Between 2.6.27.7 and 2.6.27.21/2.6.27.23 are quite some changes in SUSE's kernel config that concern the clock, virtualization, and others, IIRC. Maybe if one changes some of them back, it might work again. But my next step will probably be to try Workstation 6.5 on a trial system and see if it has the same problem or not. Actually, the NVidia setup is one of the few things missing to get a new workstation working so that I can use the old ones for such experiments... ;-) Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] dmraid partitions Lost & Found - howto
by David C. Rankin 29 Jun '09

29 Jun '09

Listmates, I had not had the opportunity to deal with a complete loss of all partition information before and had to do a quick bit of learning on how to recover them (the long way because I was too dumb to move my "fdisk -l" saved information to a remote disk before beginning to beta test dmraid releases). Anyway, this information applies to all partition recovery and I stumbled across several tools I hadn't known of before so I thought I would pass the fun along. Also included is the information to recover your grub installation that is always a fairly hot topic, so this just might help some other lucky soul down the road. dmraid Partition Loss with dmraid-1.0.0rc15 Testing dmraid-1.0.0rc15 on a box with two separate dmraid arrays, I experienced the total loss of all partitions on the second dmraid array. The first array held an openSuSE install running dmraid-1.0.0rc14 while the second held Archlinux with dmraid-1.0.0rc15 where testing was being done. All testing of dmraid-1.0.0rc15 on Archlinux went fine, the problem occurred when the machine was boot back into openSuSE. There was a kenel update involved at the time that just might have created the perfect storm of differing dmraid metadata formats across OS's and a kernel update that the partitioning just couldn't handle. Regardless of the situation, whether using a raid setup or not, partition loss is serious business and hopefully this will help get you going again. dmraid Partition Recovery Recovery of dmraid partitions proceed in the same manner as recovering partitions from a singe drive. if you haven't destroyed the information on the array, you should be able to put the pieces of the puzzle back together again. The basic outline for the process is to locate and restore the partitions on the array and then reinstall the boot loader so your box is functional again. (Note: if you were smart enough to save the "fdisk -l" information for your drives, you can simply fdisk your array and be done) Tools Required A. Partition location and recovery software (I used testdisk) http://www.cgsecurity.org/ (main site) http://www.cgsecurity.org/wiki/TestDisk_Download (download page) http://www.cgsecurity.org/testdisk-6.11.linux26.tar.bz2 (prebuilt for 2.6 kernels) B. Rescue CD for your OS (generally your install CD/DVD, or knoppix, etc.) Using testdisk testdisk is a great piece of GPL code written by Christophe Grenier. testdisk can be used with most operating systems and will scan you disk or array and locate partition boundaries and give you the opportunity to recover them. I had 4 partitions dedicated to my Archlinux install totaling roughly 70G on a 750G raid array. To start testdisk, for Linux26, you will untar the bzip archive and then cd into the linux subdirectory. The prebuilt binary is: ./testdisk_static The first thing you will need to do is set the correct disk geometry. In my case the disk reported 254 heads and needed to be changed to 255 heads to work properly. (This is recommended if the first Quick Scan doesn't find your partitions and should be true of most 500G-1T drives on the market). After setting the geometry, just choose "Analyze" and "Quick Scan" and go get a coffee or something. In my case since the 70G I was using was at the front of the 750G array, it had found my partitions within 5 minutes or so. Once all of your partitions are found you can "Stop" the scan by hitting the return key. You are then presented with the list of found partitions. You may only want to recover some of the partitions found. They will be initially labeled "D" for deleted and you simply toggle on the partitions you need to recover by selecting ("P" Primary, "*" Primary Boot, "L" Logical or leave as "D" for Deleted). You are provided with the CHS information on the screen so you can map out what parts do and do not belong. testdisk will check your selections for partition overlap and give you confirmation in green if your partition layout is OK. Just hit return to continue. Don't worry about the extended partition boundary, it will be provided. Review the partitions to be recovered and choose "Write" and your are done. (a reboot is required to activate the partitions) If no partitions were found during the "Quick Scan", then (1) check your drive geometry setting; and (2) you will be given the option to do an "In Depth Scan" (go get 4 cups of coffee, walk the dog, etc...) Have Your Rescue CD Handy Once the partition information has been recovered and the partition table changed, there is a near 100% chance your boot loader configuration will be messed up. Don't worry, everything is still there, you just have to reinstall grub or lilo into the boot record to recover from the situation. The following grub recipe will apply regardless of whether you are working with dmraid or mdraid or just a plain single drive. Just use md-X for mdraid and use the normal sda, sdb, etc. for individual disks. dmraid was the example here because that just happened to be my lock set of disks for the day. Reinstalling Grub Here you will be booting from your CD or DVD into rescue mode, using dmraid to activate the arrays, and then using the information about the dm nodes in /dev/mapper and /dev/dm-X and the partition information in from "cat /proc/partitions" to create a chroot of your install to repair the boot loader: (1) boot from the install DVD (2) choose "Rescue System", login as "root" (no password needed) (3) activate the dmraid arrays with "dmraid -ay" (4) check which device nodes to use to create the chroot with "ls -al /dev/dm*" or "ls -al /dev/mapper". I was dealing with 2 separate arrays, 9 partitions (duplicated by having both dmraid-1.0.0rc14 and dmraid-1.0.0rc15 metadata) that left me with dm-0 to dm-20 to deal with. Compare the size shown for dm-X, /dev/mapper/raiddevice_name and the size shown from "cat /proc/partitions" to determine your "/", "/home", and "/boot" and any other partitions you need to setup in your chroot environment. (5) mount all dm-X devices or /dev/mapper devices under /mnt to create your actual filesystem, and then bind /dev/, /proc/ and /sys/ to their respective mount points under /mnt and chroot. **Note, you need to mount the device containing the / (root) filesystem first before mounting /boot and /home. Otherwise, the /boot and /home mount points will not exist: Example: mount /dev/dm-5 /mnt mount /dev/dm-7 /mnt/boot mount /dev/dm-6 /mnt/home mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys cd /mnt chroot /mnt (6) Reinstall grub to fix the mbr on your raid discs (mine were hd0 and hd1). See http://wiki.archlinux.org/index.php/Installing_with_Fake-RAID#Install_GRUB for my notes on getting the (hdX,Y) numbers right. When you start grub, you get a small ">" prompt, just use the following as a guide. If you only have a single array, you will only need to worry about setting up hd0: grub >root (hd0,4) >setup (hd0) >*** few lines of grub output *** >root (hd1,5) >setup (hd1) >*** more lines of grub output *** >quit (7) check your /etc/grub.conf to make sure it agrees with the way you have just configured grub. For the example above, it should look like this for hd0 (I boot to hd0 and then chainload to get to hd1 and the second array) setup --stage2=/boot/grub/stage2 (hd0) (hd0,4) quit (8) exit (to exit chroot) and reboot, and if you were successful (or just damn lucky), your system will be 100% again. Now immediately do "fdisk -l > part.info.dev.name" on each of your arrays and drives and save that information remotely so if this happens again, you have a shortcut;-) This stuff was always painful, so I just took a moment to write it down so I would have it for the next go-round;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

8 15

[opensuse] SuSE 11.1 problem with mouse model detection
by Maura Monville 29 Jun '09

29 Jun '09

I cannot get SuSE 11.1 correctly recognize either a DELL USB mouse or a PS2 LOGITECH mouse. The problem in either case is that the wheel is recognized as a middle button but it won't scroll regardless of the brand, model, and options choice from the list popped up by Yast (DELL is not in the list). It looks like the drivers are not there .... Thank you in advance for any help. Maura -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Re: Nvidia GFX kernel modules for older 11.1-kernel 2.6.27.7-9, anywhere?
by Joachim Schrod 29 Jun '09

29 Jun '09

Per Jessen wrote: > Joachim Schrod wrote: > >> I'm looking for the proprietary Nvidia driver (kernel module) for a >> GeForce FX 5200 graphics card. A rpm is supposed to be at >> http://download.nvidia.com/opensuse/11.1/, named >> nvidia-gfxG01-kmp-pae. >> >> But there is only a RPM for the most current 11.1 kernel, version >> 2.6.27.23_0.1. I need one for kernel 2.6.27.7-9. (I can't use the >> most current kernel since VMware Server 1 doesn't work properly >> with it anymore.) >> >> Is there anywhere a repository archive for older versions where I >> can fetch a respective RPM for my kernel? >> Alternatively, is there another possibility to install that driver? > > If the actual nvidia driver isn't any different, you could just install > the latest rpm with --force ? Of course, I tried that already... :-) That doesn't work, the kernel modules don't fit. (The error message at insmod time is "Invalid module format".) Actually, I didn't expect them to work, calling insmod was pure mischief. From my VMware problems I know that quite a lot seemed to have happened between 2.6.27.7 and 2.6.27.23. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2