June 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Screensaver not working correctly
by Patrick Shanahan 19 Jun '13

19 Jun '13

My screensaver on 12.3 no longer goes into "Energy Saving" mode. It shows the screensaver and after the set time it blanks but doesn't go completely black. The monitor is a Samsung SyncMaster 2433bw and the video card is an nVidia GeForce GTS 450. Screen Locker is set to start automagically after 5 minutes Screen Locker type is "Screen Saver" "WhirlwindWarp" Power Management is set to: Dim Display after 5 min Screen Energy Saving is selected tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] repository settings gone
by Hans Witvliet 19 Jun '13

19 Jun '13

Hi all, I'm experimenting with automated installation, and i noticed that when adding aditional repositories during installation, that information is not stored when asking for an autoinstall.xml at the end of the installation. I tried both with 12.1 and 12.2 Furthermore i also tried to generate the xml-file after installation, through yast. Configfiles are created with content, but whatever i do, the settings of add-on repo's are ommited. This implies that a re-installation, based on that XML is not possible, as packages (only available from the add-on's) are not available.... Is this known / intentionally??? This used to work in older versions, as i used it quite often to create my own xml-files. Hans -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] pam_apparmor(crond:session): Unknown error occurred changing to root hat: Operation not permitted
by Carlos E. R. 19 Jun '13

19 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I get those messages in the messages log every time cron does something as another user. This is "Bug 807106". According to answer #2, I have "pam_apparmor installed, but not configured". Well, I installed the apparmour pattern, I didn't install that module myself, so it has the default configuration. The bug points to "http://wiki.apparmor.net/index.php/Pam_apparmor" for info, but I don't get it clear what exactly I have to do to silence those errors - they pollute the logs. - -- Cheers Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHBZmYACgkQtTMYHG2NR9US/wCgiw174z10YhQQcEDEWEHzBEkQ pB0AnjlSVxRTL+WrsOMQgGPAtxzYpD0W =ZzLm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Modules ipmi_si and ipmi_devintf (was: Systemd says: systemd-modules-load.service failed)
by Per Jessen 18 Jun '13

18 Jun '13

Cristian Rodríguez wrote: > El 17/06/13 04:02, Per Jessen escribió: > >> Hmm, how about these modules: >> >> ipmi_si, ipmi_devintf ? >> >> Sofar I have found no other/better way than creating >> a "/etc/modules-load.d/ipmi.conf". Works very well too :-) > > what package uses those modules ? software needing such modules must > load them either with an udev rule, or using libkmod , or whatever. > anything else, is a bug in my eyes. These two are used by 'ipmitool'. (there are others too). > Hrmm.. looking at the modules... ipmi_si has > > alias: pci:v*d*sv*sd*bc0Csc07i* > alias: pci:v0000103Cd0000121Asv*sd*bc*sc*i* > > Therefore, it must be magically autoloaded if the hardware matches in > the running system. if it does not, then there is a bug. Yeah, that is my thinking too, but so far it has not worked. I'm not intimately familiar with how those aliases work, am I right I thinking I need to match those against the information in these?: find /sys/devices/pci0000\:00/ -name modalias I am not sure, but I think the issue might be that the BMC that ipmi_si wants to talk to is not sat on the PCI bus, but on the SMbus. -- Per Jessen, Zürich (22.5°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] radeon crashes
by Peter 18 Jun '13

18 Jun '13

I'm starting a fresh thread following some comments I posted recently in http://lists.opensuse.org/opensuse/2013-05/msg00791.html I don't want to keep hijacking that as my own issue isn't strictly related. I'm trying to resolve long-running radeon issues (a laptop with a Mobility Radeon 9700, based off the 9600, RV350), going back to around the introduction of KMS in openSUSE 11.3 (i.e. years ago). On fresh installs of all openSUSE versions since then, things run fine for maybe a few days, then I get an issue where the screen momentarily blanks and comes back but everything's frozen. Occasionally other weird artefacts like the whole display gradually changing to rainbow vertical lines occurs. Only a Magic Keys reboot can get me out. Effectively, after it has crashed the first time, subsequent reboots usually result in the same happening again much sooner, as though there's some corruption in memory somewhere. Under this openSUSE 12.3 release I noted it was sometimes triggered when attempting keyboard input in a particular place such as in a web page text entry field or a simple text file, but over the years it could also just happen randomly at any moment. I can confirm it isn't likely to be a faulty card as I experienced exactly the same issues on a very different desktop system that had a radeon 9600 AGP card. In all cases I'm using the default 'radeon' driver pre-selected at install, since the ATI proprietary driver support for this card was dropped years ago. The only workaround I've ever found is to disable hardware acceleration in the 50-device.conf file. On 2013-05-30 10:09:26 -0400, Felix Miata wrote: > Exactly how? I didn't see you didn't say in your post or in your > bug. All my systems disable composite bling in 70-extensions.conf. > I have no systems, Radeon or otherwise, regardless of chip or driver > used except for Intel i845G, that have ever that I can remember > exhibited anything like your complaint. I do it via the following line (which does get adhered to regardless of the requirement Felix mentioned for a minimum criteria in the device, screen and monitor files): Option "NoAccel" "true" Unfortunately that renders my ageing laptop very slow and sluggish, falling back to software rendering and spinning the fan up to a consistent noisy speed. In this 12.3 release the machine is now on the brink of usability. However, following Felix's advice, in my latest attempt at testing, I've created a 50-device.conf with: Section "Device" Identifier "Default Device" Driver "radeon" # ## Required magic for radeon/radeonhd drivers; output name # ## (here: "DVI-0") can be figured out via 'xrandr -q' Option "monitor-LVDS" "Default Monitor" EndSection a 50-screen.conf with: Section "Screen" Identifier "Default Screen" Device "Default Device" # ## Doesn't help for radeon/radeonhd drivers; use magic in # ## 50-device.conf instead Monitor "Default Monitor" EndSection and a 50-monitor.conf with: Section "Monitor" Identifier "Default Monitor" # # ## If your monitor doesn't support DDC you may override the # ## defaults here # #HorizSync 28-85 # #VertRefresh 50-100 # # ## Add your mode lines here, use e.g the cvt tool DisplaySize 338 211 # 096 DPI @ 1280x800 Modeline "1280x800" 213.88 1280 1376 1520 1760 800 801 804 868 Option "DefaultModes" "on" # only sometimes necessary Option "PreferredMode" "1280x800" # insurance, usually unnecessary EndSection I don't know what is and isn't really necessary in that monitor file, or how to find out the correct sync/refresh rates to enter. Release Notes entries about radeon driver issues going back to the introduction of KMS mention booting with 'nomodeset', but I'm unable to do that since it hangs prior to the login screen (the 'Reached Target Graphical Interface [OK] part). Does booting with 'nomodeset' effectively switch to vesa or a non-radeon driver, or are the two things not inter-related? Thinking this may be KMS related I followed some advice to change the sysconfig entry 'NO_KMS_IN_INITRD' to 'yes'. Doing this in YaST appeared to automatically run mkinitrd afterwards. I then rebooted. The boot sequence was slightly different with a longer period of blank screen but the login screen than arrives as usual. I've rebooted a couple of times like this without issue, until today. It crashed just after login, before all services were finished loading. Whilst the screen froze and the cursor disappeared the HD was still chugging away loading services and trying Ctrl-Esc in KDE made the HD busy for a moment but no task manager appeared on screen. I tried Ctrl-Alt-F8 and just got a blinking cursor. Going back to Ctrl-Alt-F7 I got a blank screen with a moveable mouse cursor. Ctrl-Alt-2xBackspc got me back to a login from where I'm now back in KDE. I wasn't watching the boot sequence but the xorg log file suggests it booted with KMS, despite my changing the setting, so I'm puzzled. The log file may give other clues to what's up: http://paste.opensuse.org/17295823 I've started and contributed to various forum posts about this over the years but they all went stale and none of the suggestions helped. I've also contributed to Bugzilla reports that got closed and 'fixed' for certain others but not me, so I recent started another of my own here (currently no response): https://bugzilla.novell.com/show_bug.cgi?id=817528 Is there anything else I can try or is it really the end of the road for my legendary laptop? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] ParaView package maintainer?
by John Young 18 Jun '13

18 Jun '13

Does anyone know how to contact the maintainer of the ParaView package from the openSUSE Science repository? -- JY ------------------------------------------------------------ John E. Young NASA LaRC B1148/R226 Analytical Services and Materials, Inc. (757) 864-8659 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] ThinkPad shutdown takes long time
by James Knott 18 Jun '13

18 Jun '13

I've noticed sometimes it takes a long time for my ThinkPad E520 to reboot when running openSUSE 12.3. When this occurs and I press Esc, I see the following displayed for a couple of minutes or so before it progresses. This does not happen every time and I don't see any pattern to when it does. doing fast boot Creating device nodes with udev Welcome to openSUSE 12.3 "Dartmouth" - Kernel 3.7.10-1.11-desktop (tty1) E520 login: [ OK ] started Show Plymouth Reboot Screen. Any ideas? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 27

[opensuse] Odd results from df
by Otto Rodusek 18 Jun '13

18 Jun '13

Hi ListMates, I'm not sure if this issue has been covered before or if anyone has come across this before. I recently did a fresh install of OpenSuse 12.3_x64 on one of my user's HP UEFI 64bit machines - the install went smoothly, the 1Tb disk was setup as GPT. I now, however, have some strange results from the "df" command!! rsgpfp0002:~ # uname -a Linux rsgpfp0002.loc 3.7.10-1.11-default #1 SMP Thu May 16 20:27:27 UTC 2013 (adf31bb) x86_64 x86_64 x86_64 GNU/Linux rsgpfp0002:~ # df -vh Filesystem Size Used Avail Use% Mounted on devtmpfs 2.9G 32K 2.9G 1% /dev tmpfs 2.9G 0 2.9G 0% /dev/shm tmpfs 2.9G 18M 2.9G 1% /run /dev/sda3 25G 4.5G 19G 19% / tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup tmpfs 2.9G 18M 2.9G 1% /var/lock tmpfs 2.9G 18M 2.9G 1% /var/run /dev/sda1 156M 128K 156M 1% /boot/efi /dev/sda4 891G 759G 87G 90% /public rsgpfp0002:~ # df -v Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 2983260 32 2983228 1% /dev tmpfs 2998284 0 2998284 0% /dev/shm tmpfs 2998284 17764 2980520 1% /run /dev/sda3 25806716 4626136 19869656 19% / tmpfs 2998284 0 2998284 0% /sys/fs/cgroup tmpfs 2998284 17764 2980520 1% /var/lock tmpfs 2998284 17764 2980520 1% /var/run /dev/sda1 159564 128 159436 1% /boot/efi /dev/sda4 933396656 795685260 90297588 90% /public rsgpfp0002:~ # If I look at /dev/sd3 (25G - 4.5G does not equal 19G - I expect to get 20.5G!!!) or /dev/sda4 (891G - 759G does not equal 87G - I expect to get 132G!!!!), the numbers are way off!!!!! Has anyone seen this before, and where has all my disk space gone to?? Thanks for any insight into this!! Best regards. Otto. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 18

[opensuse] Systemd says: systemd-modules-load.service failed
by Carlos E. R. 17 Jun '13

17 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm being more polite and I'm not blaming systemd diretly this time ;-) Telcontar:~ # date;systemctl status systemd-modules-load.service Sun Jun 16 20:24:44 CEST 2013 systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Active: failed (Result: exit-code) since Sun, 2013-06-16 13:57:46 CEST; 6h ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Main PID: 4703 (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/systemd-modules-load.service Jun 16 13:57:46 Telcontar.valinor systemd[1]: Starting Load Kernel Modules... Jun 16 13:57:46 Telcontar.valinor systemd-modules-load[4703]: libkmod: kmod_config_parse: /etc/modprobe.d/10-unsupported-modules.conf line 10: ignoring bad line starting with 'allow_unsupported_modules' Jun 16 13:57:46 Telcontar.valinor systemd-modules-load[4703]: Module 'cryptoloop' is already loaded Jun 16 13:57:46 Telcontar.valinor systemd-modules-load[4703]: Module 'twofish_x86_64' is already loaded Jun 16 13:57:46 Telcontar.valinor systemd-modules-load[4703]: Module 'twofish_x86_64_3way' is already loaded Jun 16 13:57:46 Telcontar.valinor systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE Jun 16 13:57:46 Telcontar.valinor systemd[1]: Failed to start Load Kernel Modules. Jun 16 13:57:46 Telcontar.valinor systemd[1]: Unit systemd-modules-load.service entered failed state Telcontar:~ # cat /etc/modprobe.d/10-unsupported-modules.conf # # Every kernel module has a flag 'supported'. If this flag is not set loading # this module will taint your kernel. You will not get much help with a kernel # problem if your kernel is marked as tainted. In this case you firstly have # to avoid loading of unsupported modules. # # Setting allow_unsupported_modules 1 enables loading of unsupported modules # by modprobe, setting allow_unsupported_modules 0 disables it. This can # be overriden using the --allow-unsupported-modules commandline switch. allow_unsupported_modules 1 Telcontar:~ # cer@Telcontar:~> grep MODULES_LOADED_ON_BOOT /etc/sysconfig/kernel MODULES_LOADED_ON_BOOT="cryptoloop twofish" cer@Telcontar:~> No inline comments this time... The "/etc/modprobe.d/10-unsupported-modules.conf" dates from Nov 14 2012, and I don't remember what it was for. Is that one causing trouble? - -- Cheers Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG+BKMACgkQtTMYHG2NR9U0GQCfSNN/QiX7ujRz22nGxnLz+/dH LBcAoJaENDM8krlFP7xT2WAHFzb5ALh6 =LfSX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 25

[opensuse] RE: Stability of systemd
by Duaine Hechler 17 Jun '13

17 Jun '13

Is systemd more reliable and stable in 12.3, than in 12.1 and 12.2 ? Or is keeping with sysvinit the better way to stay ? -- Duaine Hechler Piano, Player Piano, Pump Organ - Tuning, Servicing & Rebuilding (314) 838-5587 / dahechler(a)att.net / www.hechlerpianoandorgan.com Home & Business user of Linux - 13 years -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

13 56