June 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] raid1, ignore one HD when reading
by Ruediger Meier 06 Jun '13

06 Jun '13

Hi, I have a raid1 with 2 HDs. Is it possible somehow to let him use only one of them for reading? cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 17

[opensuse] wie in /boot löschen/Platz machen?
by Daniel Bauer 06 Jun '13

06 Jun '13

Guten Tag, Ich hab mein OS 12.3 so eingerichtet, dass bei einem Kernel-Update die alte Version noch vorhanden bleibt. Nun habe ich also schon einige Versionen in /boot und der Platz geht zu Ende wie Yast mitteilt. Kann ich die alten config..., initrd..., symtypes... sysctl.conf..., System.map... vmlinux..., vmlinuz... einfach ohne Weiteres löschen oder muss ich dabei Weiteres beachten oder irgendwo etwas ändern? Danke für Hinweise. Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com google+: https://plus.google.com/109534388657020287386 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] zypper update. What is changed?
by lynn 06 Jun '13

06 Jun '13

12.3 Hi zypper tells me of that are to be updated. How do I find out what within the package has been patched? Thanks, L x -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] xfce: seahorse refuses to create new pgp key.
by Carlos E. R. 06 Jun '13

06 Jun '13

I start “paswords and keys” (aka seahorse). Click “new”. Click “PGP key”. Fill name, email, comment. The “create” button remains disabled. This is a fresh 12.3 install from dvd with some gnome elements (from package depends). All mandatory patches applied. Session startup has “launch gnome services on startup” active. Applications “certificate and key storage (gnome keyring: pkcs#11 component)” and “GPG password agent (gnome keyring: GPG agent)” are both set to start (application autostart). -- Cheers / Saludos, Carlos E. R. (from oS 12.3 "Dartmouth" GM (rescate 1)) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Howto setup an "Attansic Ethernet controller" with OpenSuse 12.3
by Andreas 06 Jun '13

06 Jun '13

Hi, I installed OpenSuse 12.3 64Bit on a new box with an ASUS Mainboard. Suse wont automatically initialize the NIC. YAST does display an entry for an "Attansic Ethernet controller" but says it cant configure the thingy because the kernel device wlan0/eth0 was missing. I found references with google that this is an older issue with those Attansic NICs. There are hints at least for OpenSuse 12.2 to install those 2 packages compat-wireless-kmp-desktop compat-wireless-scripts They should contain the ALX kernel module. I didn't find those on the DVD though. How can I obtain the needed files and how will I install them as I don't have network access without them? Btw an Ubuntu Live-CD did work with this chip without having to setup anything manually so there must be a suitable driver somewhere. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Complete hibernation failure in 12.3
by Carlos E. R. 06 Jun '13

06 Jun '13

Hi, I'm testing openSUSE 12.3 XFCE in a spare disk on my main computer. Almost everything works, but there is something crucial that does not: hibernation. Machine is: CPU: Core(TM)2 Quad CPU Q9550 @ 2.83GHz Memory Size: 8 GB gfcard: nVidia G96 [GeForce 9500 GT] driver: nouveau, drm. AFAIK, either called from the xfce menu or from commandline in text mode (pm-hibernate), it appears to go through the motions, but fails miserably to restore. In fact, I it is possible that nothing is saved to the swap, because pm-hibernate happens in 3 seconds. My work partition takes about half a minute to hibernate, but I also run more things, so more memory is used. During restore I see that the computer goes automatically to boot from the right hard disk (the key to choose boot device is disabled for one go), then goes through grub without waiting, loads something, black screen fast, and normal boot proceeds (with filesystem check). I see in "/var/log/pm-suspend.log" that the hooks are run, except one. For instance, "/etc/pm/sleep.d/99at" runs, but not "/etc/pm/sleep.d/05cosas", no mention on the log of this. But that is a minor issue. In my messages log, a normal halt/boot sequence goes like this: +++··························· > 2013-06-02T19:02:24.844337+02:00 rescate1 sshd[3693]: Received signal 15; terminating. > 2013-06-02T19:02:24.844665+02:00 rescate1 systemd[1]: Stopped /etc/init.d/boot.local Compatibility. > 2013-06-02T19:02:24.844946+02:00 rescate1 systemd[1]: Stopping Login Prompts. > 2013-06-02T19:02:24.845574+02:00 rescate1 rsyslogd: [origin software="rsyslogd" swVersion="7.2.7" x-pid="1069" x-info="http://www.rsyslog.com"] exiting on signal 15. > 2013-06-02 19:02:24+02:00 - Halting the system now =========================================== uptime: 19:02pm up 0:08, 0 users, load average: 0.09, 0.10, 0.07 > 2013-06-02 19:04:17+02:00 - Booting the system now ================================================================================ Linux rescate1.site 3.7.10-1.11-desktop #1 SMP PREEMPT Thu May 16 20:27:27 UTC 2013 (adf31bb) x86_64 x86_64 x86_64 GNU/Linux > 2013-06-02T19:04:17.282712+02:00 rescate1 rsyslogd: [origin software="rsyslogd" swVersion="7.2.7" x-pid="844" x-info="http://www.rsyslog.com"] start > 2013-06-02T19:04:17.282935+02:00 rescate1 kernel: [ 0.000000] Initializing cgroup subsys cpuset > 2013-06-02T19:04:17.282939+02:00 rescate1 kernel: [ 0.000000] Initializing cgroup subsys cpu ···························++- However, when I attempt to hibernate, I see this: +++··························· > 2013-06-02T20:00:01.639396+02:00 rescate1 /USR/SBIN/CRON[6191]: pam_unix(crond:session): session closed for user root > 2013-06-02T20:02:24.794186+02:00 rescate1 systemd[1]: Starting Sleep. > 2013-06-02T20:02:24.804959+02:00 rescate1 systemd[1]: Reached target Sleep. > 2013-06-02T20:02:24.805326+02:00 rescate1 systemd[1]: Starting Hibernate... > 2013-06-02T20:02:24.834189+02:00 rescate1 systemd-sleep[6270]: Hibernating system... > 2013-06-02T20:02:24.962914+02:00 rescate1 network[6325]: redirecting to "systemctl --signal=9 kill network.service" > 2013-06-02T20:02:27.702751+02:00 rescate1 kernel: [ 3145.119158] PM: Marking nosave pages: [mem 0x0009f000-0x000fffff] > 2013-06-02T20:02:27.702768+02:00 rescate1 kernel: [ 3145.119164] PM: Marking nosave pages: [mem 0xbff90000-0xffffffff] > 2013-06-02T20:02:27.703647+02:00 rescate1 kernel: [ 3145.120341] PM: Basic memory bitmaps created > 2013-06-02 20:03:42+02:00 - Booting the system now ================================================================================ Linux rescate1.site 3.7.10-1.11-desktop #1 SMP PREEMPT Thu May 16 20:27:27 UTC 2013 (adf31bb) x86_64 x86_64 x86_64 GNU/Linux > 2013-06-02T20:03:42.526203+02:00 rescate1 rsyslogd: [origin software="rsyslogd" swVersion="7.2.7" x-pid="911" x-info="http://www.rsyslog.com"] start > 2013-06-02T20:03:42.526221+02:00 rescate1 systemd[1]: Started Collect Read-Ahead Data. > 2013-06-02T20:03:42.526296+02:00 rescate1 systemd[1]: Started Replay Read-Ahead Data. > 2013-06-02T20:03:42.526298+02:00 rescate1 kernel: [ 0.000000] Initializing cgroup subsys cpuset > 2013-06-02T20:03:42.526301+02:00 rescate1 systemd[1]: Starting Load Kernel Modules... ···························++- It does a normal boot after hibernate, not a restore. The kernel line used is: +++··························· > 2013-06-02T20:03:42.526307+02:00 rescate1 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.7.10-1.11-desktop root=UUID=3f875e95-5323-4527-88bd-39bce605e6e9 resume=/dev/disk/by-label/aux_swap showopts splash=verbose console=tty1 loglevel=3 ···························++- The partitions are correct: +++··························· > cer@rescate1:~> l /dev/disk/by-uuid/3f875e95-5323-4527-88bd-39bce605e6e9 > lrwxrwxrwx 1 root root 10 Jun 2 20:03 /dev/disk/by-uuid/3f875e95-5323-4527-88bd-39bce605e6e9 -> ../../sda1 > cer@rescate1:~> l /dev/disk/by-label/aux_swap > lrwxrwxrwx 1 root root 10 Jun 2 20:03 /dev/disk/by-label/aux_swap -> ../../sda2 > cer@rescate1:~> su > Password: > rescate1:/home/cer # file -s /dev/sda1 > /dev/sda1: x86 boot sector, code offset 0x63 > rescate1:/home/cer # file -s /dev/sda2 > /dev/sda2: Linux/i386 swap file (new style), version 1 (4K pages), size 1048575 pages, LABEL=aux_swap, UUID=dcc14c11-aa74-4ac9-955f-efd34a8cdb10 > rescate1:/home/cer # exit > cer@rescate1:~> > > cer@rescate1:~> cat /etc/fstab > LABEL=aux_extrasys / ext4 acl,user_xattr 1 1 > LABEL=aux_swap swap swap defaults 0 0 > > #/dev/mapper/cr_ata-ST2000DM001-1CH164_W1E4056F-part3 /data/aux xfs nofail 0 2 > /dev/mapper/cr_Aux_01 /data/aux xfs nofail 1 6 > > proc /proc proc defaults 0 0 > sysfs /sys sysfs noauto 0 0 > debugfs /sys/kernel/debug debugfs noauto 0 0 > usbfs /proc/bus/usb usbfs noauto 0 0 > devpts /dev/pts devpts mode=0620,gid=5 0 0 ... > rescate1:~ # swapon --summary > Filename Type Size Used Priority > /dev/sda2 partition 4194300 0 -1 ···························++- Mmm... swap is smaller than RAM. Should not be a problem, but it might be... :-? [...] Ok, I switched swap to another, bigger, partition. But I have the same problem. This is the used memory and swap table, taken from "top": +++··························· > top - 21:36:26 up 16 min, 6 users, load average: 0,09, 0,14, 0,13 > Tasks: 186 total, 1 running, 185 sleeping, 0 stopped, 0 zombie > %Cpu(s): 1,8 us, 1,0 sy, 0,0 ni, 95,6 id, 1,5 wa, 0,0 hi, 0,0 si, 0,0 st > KiB Mem: 8193808 total, 1291152 used, 6902656 free, 29848 buffers > KiB Swap: 10482376 total, 0 used, 10482376 free, 463608 cached ···························++- The next thing I could try is using the proprietary NVidia driver, instead of nouveau :-? -- Cheers / Saludos, Carlos E. R. (from oS 12.3 "Dartmouth" GM (rescate 1)) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Wrangling Gnome and Keyboard Layouts
by Aaron W. Hsu 05 Jun '13

05 Jun '13

Dear Readers: I hope that you can help me a bit with my Gnome 3.6 struggles. Mostly, things in OpenSUSE 12.3 with Gnome 3.6 are working swimmingly. However, I cannot seem to find anyway to achieve my first or secondary goals when it comes to keyboard layouts, despite all my searching. I have two keyboard layouts. One of them is my main layout, and the other contains a host of special symbols that I use nearly as much as the main layout for certain applications. Traditionally I would have a key set to be the Mode_switch key and then pressing that key would switch me to the alternative key layout while I held down the Mode_switch key, and then, when I released that key, it would return to the original layout. In Gnome 3.6, there seems to be no way to get the keyboard layout to switch only while a certain key is pressed. Question #1: How do I enable switching keyboard layouts only while a given modifier key (Mode_switch or other) is pressed? Through all my reading I am beginning to suspect that such a thing cannot be done at all. If this is indeed the case, then I was hoping to find a way to do a decent work around. Using the tweak tool I can set Gnome to switch my layout whenever I type a certain modifier key. That's pretty good, but the key that I want to use as my modifier key is, by default, not assigned to any symbol. I can set this key as a layout switcher shortcut in the normal Gnome settings, but it doesn't actually work. If I associate it together with a modifier key, like shift, then it does work as expected. What I am looking for is a way to map this key to a key that I can use to switch the layout when I press this key. Right now, it would suffice if I could remap the key to be the right alt key together with my other right alt key (I would then have two right alt keys). I would normally do this remapping using the Xmodmap interface, but it seems that Gnome no longer loads this file at login time. What is the method for doing this now? Question #2: How do I remap an arbitrary key to be an additional right alt key? I hae scoured the internet for a solution to these questions, but I have been unable to find anything. Right now, I am at a very uncomfortable situation of using shift+key or right alt to do a switch, but only after hitting them and releasing them, not while pressed. This is very far from my ideal. I would appreciate any help that you could give me on this. i tried the IRC channel but received no response there. Yours truly, Aaron W. Hsu -- Aaron W. Hsu | arcfide(a)sacrideo.us | http://www.sacrideo.us לֵ֤ב חֲכָמִים֙ בְּבֵ֣ית אֵ֔בֶל וְלֵ֥ב כְּסִילִ֖ים בְּבֵ֥ית שִׂמְחָֽה׃

1 0

[opensuse] Netflix on opeSUSE
by michael norman 05 Jun '13

05 Jun '13

A simple question. My son has a Netflix subscription used on his W7 box. I understand that Netflix can be shared to other devices. Is there a way to share it to my openSUSE box ? Mike -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 10

[opensuse] curious zypper and texlive packages behaviour (12.3)
by Carlos F. Lange 05 Jun '13

05 Jun '13

In openSUSE 12.3, if I issue the commands zypper install google-a* zypper install google-* zypper install google* then all Google fonts starting with letter "a" or all Google fonts are installed, as expected. However, if I want to do the same with texlive: zypper install texlive-a* zypper install texlive-* zypper install texlive* Only the last version works as expected. The first version says "Package 'texlive-a*' not found", even though there are possibly more than 100 packages starting with "texlive-a", and the second version just installs the one package texlive-2012.20120611-3.3.1.i586. It almost looks like there is something wrong with the dash character in the name of the texlive-* packages. -- Carlos F Lange -- Recursive: Adj. See Recursive. -- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] A note from Ted Tso (ext4 maintainer) about the differences between ext2/ext3/ext4
by Greg Freemyer 04 Jun '13

04 Jun '13

=== quote from ext4 mailing list === The right way to do this is to take a look at the file system features. In the superblock: __u32 s_feature_compat; /* compatible feature set */ __u32 s_feature_incompat; /* incompatible feature set */ __u32 s_feature_ro_compat; /* readonly-compatible feature set */ If your software doesn't understand a file system feature which is in the incompatible feature set, it must not try to do anything with the file system. If your software is only going to read from the file system (for example, in the case of a boot loader, or if the file system is going to be mounted read-only), then it can ignore the s_feature_ro_compat bitmask. If your software is intending to modify the file system and there is a filesystem feature bit set that it doesn't know about, it MUST NOT try to modify the file system. It's important to check the file system feature bitmasks, since over time, we've added new features to ext2, ext3, and ext4. It's more accurate to consider ext2, ext3, and ext4 to be different implementations of the same abstract file system, with the ext4 file system driver being the most fully featureful implementation. When people talk about a "ext4 file system", that's basically a shorthand for saying that it's an ext2/3/4 file system which has features enabled which the traditional ext2 and ext3 drivers in more recent kernels do not support. But it's not a very precise statement. If someone asks me to debug "an ext4 file system", I will tell them that it's critically important that the send me the output of "dumpe2fs -h" so I can see what file system features were enabled for that particular file system. Similarly, when an enterprise distribution states that they support "ext4 file systems", there may be some newer ext4 file system features (such as bigalloc, inline_data, metadata_csum) which they do not support, even if the enterprise kernel supports said feature. Generally, in these cases the distribution will ship an /etc/mke2fs.conf file that only enables the file system features that they support when the user runs the "mke2fs -t ext4" command. I hope this helps, - Ted ================= Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0