July 2014 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] empty tty10
by Felix Miata 18 Jul '14

18 Jul '14

Anyone know why post-13.1 vtty10 is nothing but black instead of kernel messages? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Factory Updates
by gm1mqe＠aol.com 17 Jul '14

17 Jul '14

Thanks for the info. I will go back to sleep for a bit ! Cheers, Andy -----Original Message----- From: Alberto Planas Dominguez <aplanas(a)suse.de> To: opensuse-factory <opensuse-factory(a)opensuse.org> Sent: Thu, 17 Jul 2014 16:32 Subject: Re: [opensuse-factory] Factory Updates On Thursday, July 17, 2014 11:28:00 AM gm1mqe(a)aol.com wrote: > Am I right in thinking there have been no new snapshots since 29th June? This is the last one, from two weeks ago. We create snapshots when we see that makes sense. For the next release we are waiting to fix some kernel BtrFS details that openQA tell us in the FactoryToTest images. This ISO is also the recommended way today to install Factory from scratch. > Thanks, Andy -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Factory Updates
by gm1mqe＠aol.com 17 Jul '14

17 Jul '14

Am I right in thinking there have been no new snapshots since 29th June? Thanks, Andy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] factory-oss key expired
by Stefan Seyfried 17 Jul '14

17 Jul '14

Warning: The gpg key signing file 'content' has expired. Repository: factory-oss Key Name: openSUSE Project Signing Key <opensuse(a)opensuse.org> Key Fingerprint: 22C07BA5 34178CD0 2EFE22AA B88B2FD4 3DBDC284 Key Created: Fri Nov 7 15:10:07 2008 Key Expires: Sun May 4 17:01:33 2014 (EXPIRED) Rpm Name: gpg-pubkey-3dbdc284-49144c3f I already uninstalled gpg-pubkey-3dbdc284-49144c3f (the one I had installed had expired in 2010), but the one I got from the repo then is also already over its time... -- Stefan Seyfried "Your mail is 7 pages of printout. Do you seriously expect people that do openSUSE in their free time to read that? Little less Castro, little more JFK..." -- coolo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] New package depencies for Saltstack
by Niels Abspoel 15 Jul '14

15 Jul '14

Hi Everyone, I want to inform you all about the following new packages that I want to submit to factory: python-ioflo source https://github.com/ioflo/ioflo python-libnacl source https://github.com/saltstack/libnacl python-raet source https://github.com/saltstack/raet These new packages will be used with the upcoming salt major release. ioflo is a framework for programming rules/behavior libnacl is a python binding for libsodium (needed for new security within saltstack) raet is a new transport protocol developed by saltstack With kind regards, Niels Abspoel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Automatically unlocking kwallet on login
by Olav Reinert 15 Jul '14

15 Jul '14

I recently came across this very interesting article: https://www.dennogumi.org/2014/04/unlocking-kwallet-with-pam/ Ever since I started using KDE, it has annoyed me that that kwallet *always* asks for a password on login, even if it's the same as my login password. Apparently, I'm not the only one, and now someone seems to be working on a proper solution. My question is, will this functionality make it into openSUSE 13.2? Yes, I tried the solution proposed in the article, but couldn't get it to work. Debugging this stuff is a bit beyond me. \Olav -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Encrypted Messenger for OpenSuse v.0.9.07
by Randolph 14 Jul '14

14 Jul '14

https://sourceforge.net/projects/goldbug/files/goldbug-im_OPENSUSE13.1/ http://software.opensuse.org/package/goldbug?search_term=goldbug http://goldbug.sourceforge.net/ goldbug v.0.9.07 Secure instant messenger GoldBug is a secure Instant Messenger. You can be sure with using GoldBug (GB), that no third party can look testinto your chat communication. Private user-to-user communication remains private. GoldBug therefore uses strong multi-encryption with different layers of modern encryption technologies of well known and revised crypto libraries (like libgcrypt (GnuPG) and OpenSSL). The app offers as well decentral and encrypted Email and decentral public E*IRC-Chat. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] Effort to push Julia to openSUSE Factory
by Ronan Chagas 14 Jul '14

14 Jul '14

Hi guys, I'm maintaining Julia (http://www.julialang.org) package for openSUSE 13.1 and Tumbleweed here: https://build.opensuse.org/package/show/home:Ronis_BR/julia Additionally, Alin helped me to build it for Factory: https://build.opensuse.org/package/show/home:Ronis_BR:factory/julia The problem is that there are some libraries that are bundled with the package: _ OpenLIBM _ OpenSpecFun _ SuiteSparse (can be easily unbundled) _ RMATH _ libuv Some libraries seem to be heavily patched to be used with Julia (RMATH and libuv, I think). The others seem to need a specific version otherwise the building process could fail. To avoid those problems, I looked to the Archlinux and Ubuntu package to verify which libs are bundled and then I copied the configuration for my openSUSE package. Notice that all those bundled libs are installed in /usr/lib{64}/julia so it should not conflict if we have a another version of such libs installed concurrently. I just want to know if everything seems fine before submitting it to Factory. Best regards, Ronan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] no nfs/bad rpcbind: unknown host/protocol not supported
by Felix Miata 13 Jul '14

13 Jul '14

I just did a fresh HTTP Factory install, and am having an inexplicable problem with NFS that my other Factory installations have never had. Anyone know from the following what I'm missing, or if there is a known rpcbind/nfs configuration problem? To/from internet works fine. # showmount -e <hostname> clnt_create: RPC: Unknown host # showmount -e <hostIP> clnt_create: RPC: Unknown host # mount -t nfs <IP:export> <mountpoint> mount.nfs: Protocol not supported # chkconfig -l | grep nfs nfs 0:off 1:off 2:off 3:on 4:off 5:on 6:off nfsserver 0:off 1:off 2:off 3:on 4:off 5:on 6:off # systemctl list-unit-files | grep rpc rpc-statd.service static rpcbind.service enabled rpcbind.socket enabled rpcbind.target static # systemctl list-units | grep nfs proc-fs-nfsd.mount loaded active mounted /proc/fs/nfsd var-lib-nfs-rpc_pipefs.mount loaded active mounted /var/lib/nfs/rpc_pipefs nfs.service loaded active running LSB: NFS client services nfsserver.service loaded failed failed LSB: Start the kernel based NFS daemon # (packages) libdcerpc-binding0-4.1.9-1.1.i586 libdcerpc0-4.1.9-1.1.i586 libtirpc1-0.2.3-5.3.i586 nfs-client-1.3.0-1.1.i586 nfs-kernel-server-1.3.0-1.1.i586 nfsidmap-0.25-5.3.i586 rpcbind-0.2.1_rc4-7.1.i586 yast2-nfs-client-3.1.5-1.1.noarch yast2-nfs-common-3.1.7-1.1.noarch # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] /tmp permissions problem
by Sid Boyce 10 Jul '14

10 Jul '14

This happens only on one x86_64 box with the effect that X fails and Xorg.0.log ends as follows [ 32.801] (II) NOUVEAU(0): NVLeaveVT is called. [ 32.802] (II) NOUVEAU(0): Closed GPU channel 0 [ 32.880] (EE) Server terminated successfully (0). Closing log file. /etc/permissions setting is not honoured, it gets set to drwxr-xr-x instead. sabre:~ # grep tmp /etc/permissions /tmp/ root:root 1777 /tmp/.X11-unix/ root:root 1777 /tmp/.ICE-unix/ root:root 1777 /var/tmp/ root:root 1777 /var/log/wtmp root:utmp 664 /var/log/btmp root:root 600 /var/run/utmp root:utmp 664 /run/utmp root:utmp 664 /usr/sbin/utempter root:utmp 2755 /usr/lib/utempter/utempter root:utmp 2755 Setting it manually but it reverts to the wrong permissions after a reboot. I can't find what is causing this to happen. sabre:~ # umask 0022 No problem on the other 2 boxes. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] supportconfig question
by Günther J. Niederwimmer 10 Jul '14

10 Jul '14

Hello, Is this a "normal" working for supportconfig, it do not include the zipped y2log? only the last unzipped yast2.log are included? so when run logrotade before no Info from YaST2 is Included be supportconfig? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Require feedback on assigning block size for partitions for new drive
by Roman Bysh 09 Jul '14

09 Jul '14

Hello List Mates, I have noticed that when formatting partitions I click on the Option button under EXT4. The block size is set to auto to let the filesystem select the block size according to size etc. When all is done, I boot my SystemRescue CD and run TestDisk. It informs me about a problem with the superblock. My question to you is.. Can I assign 4096 bytes rather than use auto? -- Cheers! Roman -------------------------------------------- openSUSE -- Get it! Discover it! Share it! -------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] Need patch for openSUSE:Factory prjconf
by Dirk Müller 09 Jul '14

09 Jul '14

Hi, we renamed the java packages back to -openjdk, so we need this patch for ARM to restore being able to build factory: TIA, Dirk

1 0

Re: [opensuse-factory] /tmp permissions problem
by Andrey Borzenkov 09 Jul '14

09 Jul '14

On Wed, Jul 9, 2014 at 6:57 AM, Sid Boyce <sboyce(a)blueyonder.co.uk> wrote: > On 09/07/14 03:28, Andrey Borzenkov wrote: >> >> В Wed, 09 Jul 2014 03:02:29 +0100 >> Sid Boyce <sboyce(a)blueyonder.co.uk> пишет: >> >>> /etc/permissions setting is not honoured, it gets set to drwxr-xr-x >>> instead. >>> sabre:~ # grep tmp /etc/permissions >>> /tmp/ root:root 1777 >> >> ... >>> >>> Setting it manually but it reverts to the wrong permissions after a >>> reboot. >> >> >> Is it separate filesystem? >> > Partition 1 is ext4 /boot, 2 is ext4 /. It does not answer my question. It can also be tmpfs as example. > sabre:~ # fdisk -l /dev/sda > > Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disklabel type: dos > Disk identifier: 0x0004b03b > > Device Boot Start End Blocks Id System > /dev/sda1 * 16065 104872319 52428127+ 83 Linux > /dev/sda2 104872320 1911558284 903342982+ 83 Linux > /dev/sda3 1911558285 1953487934 20964825 82 Linux swap / Solaris > Regards > Sid. > > -- > Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot > Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support > Senior Staff Specialist, Cricket Coach > Microsoft Windows Free Zone - Linux used for all Computing Tasks > -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] About Factory's Version
by Stephan Kulow 09 Jul '14

09 Jul '14

Hi, As mentioned in several situations, it's my declared goal to seperate Factory from openSUSE releases in people's mindset and run it as a rolling distribution with its own agenda. So far Factory was meant purely as testbed for the next openSUSE release. But this has changed, and e.g. Factory releases DVDs whenever they are tested as good enough - see http://download.opensuse.org/factory/iso/ While openSUSE releases benefit from being "13.2", I feel we need something else than "13.2 Milestone 0" for Factory. But I miss a good idea what it can be - the "Snapshot20140605" the ISOs bear is unfortunately not good enough as this is tagged when the ISOs are ready - but the SuSE-release file is generated from things I need to copy. - I can image commiting an increasing commit ID whenever Factory is changed. We would talk about "I'm running Factory 20272, 172 builds behind"? - I can also imagine commiting every first of a month or every sunday or ... Now it's time for your creativity - what are your preferences for a Factory version? Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

13 25

[opensuse-factory] Chromium segfaults -- what's this about?
by Neil Rickert 08 Jul '14

08 Jul '14

This is from a system running factory (up to date, as of this morning). From systemd-journalctl: Jul 07 07:21:33 nwr2 kernel: chromium[5282]: segfault at 200 ip 00007f27a71599e8 sp 00007fff9ac55d60 error 4 in i965_dri.so[7f27a6e40000+4e5000] Jul 07 07:21:33 nwr2 kernel: chromium[5323]: segfault at 200 ip 00007f84ec22a9e8 sp 00007fffad1ae730 error 4 in i965_dri.so[7f84ebf11000+4e5000] Jul 07 07:21:33 nwr2 kernel: chromium[5331]: segfault at 200 ip 00007fb4127ba9e8 sp 00007fffc8bd56d0 error 4 in i965_dri.so[7fb4124a1000+4e5000] and many more similar lines. I do have a few earlier logs from July 05. I later installed "rsyslog", and then the messages started to show up in "/var/log/messages": 2014-07-07T20:09:00.622776-05:00 nwr2 kernel: [ 2863.598061] chromium[5282]: segfault at 200 ip 00007f27a71599e8 sp 00007fff9ac55d60 error 4 in i965_dri.so[7f27a6e40000+4e5000] 2014-07-07T20:09:00.622777-05:00 nwr2 kernel: [ 2863.686185] chromium[5323]: segfault at 200 ip 00007f84ec22a9e8 sp 00007fffad1ae730 error 4 in i965_dri.so[7f84ebf11000+4e5000] 2014-07-07T20:09:00.622781-05:00 nwr2 kernel: [ 2863.744936] chromium[5331]: segfault at 200 ip 00007fb4127ba9e8 sp 00007fffc8bd56d0 error 4 in i965_dri.so[7fb4124a1000+4e5000] 2014-07-07T20:10:50.321502-05:00 nwr2 kernel: [49021.016232] chromium[21589]: segfault at 200 ip 00007f874a2d29e8 sp 00007fff4fe0d7e0 error 4 in i965_dri.so[7f8749fb9000+4e5000] 2014-07-07T20:10:50.393506-05:00 nwr2 kernel: [49021.088654] chromium[21630]: segfault at 200 ip 00007f701e6879e8 sp 00007fff9ba43c70 error 4 in i965_dri.so[7f701e36e000+4e5000] 2014-07-07T20:10:50.465503-05:00 nwr2 kernel: [49021.160565] chromium[21641]: segfault at 200 ip 00007f5247ff59e8 sp 00007fffac5a19b0 error 4 in i965_dri.so[7f5247cdc000+4e5000] But no more, since that time. I do have "chromium" installed, but as far as I knew, it was not running during the times of the logged messages. I did start "chromium" this morning. I'm not sure of the exact time, but it may have been before those first logged messages. I ran it only briefly. I did not see any problems from running chromium. After noticing the logs in "/var/log/messages", I started "chromium" again. It ran fine. I shut it down. File times suggest that I shut it down at 20:12. It looks to me as if the segfaults stopped after that second run of "chromium". Maybe "chromium" leaves some small skeletal program behind that is periodically starting "chromium" and crashing, and maybe it is happy if "rsyslogd" is actually running (instead of "systemd" picking up the logs). But those are all guesses. It seems odd. Perhaps someone else can check if this is happening there. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] ha-networking repo error
by lynn 06 Jul '14

06 Jul '14

13.1 Hi I need a copy of drbd 8.4 so I did a one click install from opensuse.org But I get this error: An error occurred while initializing the software repository. Details: network:ha-clustering:Factory: [|] Valid metadata not found at specified URL History: - File /var/tmp/TmpFile.9qpP14 doesn't contain public key data Try again? At this url: http://download.opensuse.org/repositories/network:/ha-clustering:/Factory/o… 1. Could someone put 'Valid metadata' to satisfy yast? 2. Any other recommended drdb 8.4 repos? Thanks, L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] Reasons to switch to Factory
by Stephan Kulow 06 Jul '14

06 Jul '14

Hi, We[¹]'re working on a news article on Factory becoming a true rolling distribution[²] instead of being the development branch. As you will be very well aware, it's been a while since 13.1 (acording to the original 8 month cycle we would release in 3 weeks - and I'm actually quite happy we're not putting a release out a day after the Final ;-) But I still would like to listen reasons why people should not be sad 13.2 is not released, but rather take a second look at switching to Factory. And for this I need your help: why did you switch to Factory or why do you consider it? What are the selling points of Factory? What killer features are in Factory that we don't have in 13.1? Greetings, Stephan [1] The etherpad has 8 authors and it's just a draft :) [2] http://en.wikipedia.org/wiki/Rolling_Release#True-rolling_distributions -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

19 23

[opensuse-factory] drbd problems
by lynn 05 Jul '14

05 Jul '14

13.1 Hi drbd which comes with 13.1 is broken so I tried the factory repo here: http://download.opensuse.org/repositories/network:/ha-clustering:/Factory/o… But this has a module missing: FATAL: Could not read '/lib/modules/3.11.10-17-default/weak-updates/updates/drbd.ko': No such file or directory I see in that directory that drbd.ko is a link to an older kernel: smb1:/lib/modules/3.11.10-17-default/weak-updates/updates # ls -l total 0 lrwxrwxrwx 1 root root 45 Jul 5 17:19 drbd.ko -> /lib/modules/3.11.6-4-default/updates/drbd.ko BUT, drbd.ko is not present there either. Do we have any version of drbd which is working? Thanks, L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Trident
by Ilya Chernykh 04 Jul '14

04 Jul '14

Hello, everyone! Just wanted to inform you that from the project KDE:KDE3:Trident it is now possible to install the KDE3 packages modifyed by the patchset Trident by Serghei Amelian. The packages still have some issues (not passing the post-build-checks, which I disabled). Please report any issues you may encounter. Especially check the following - Auto-mounting and unmounting media. The patchset includes a polkit client, also sync mounting is disabled in Trident. - New Kpowermanager (not available in Factory). - Check for sound issues (Trident uses Arts while openSUSE's KDE3 uses Kde Media Manager). - Check whether all the power off & suspend & hybernate dialogs work properly. - Check everything else. To test Trident you have to replace three packages from the Trident repository: qt3, kdelibs3, kdebase3. Here is a list of Trident repositories for different openSUSE releases: http://download.opensuse.org/repositories/KDE:/KDE3:/Trident/openSUSE_12.3/ http://download.opensuse.org/repositories/KDE:/KDE3:/Trident/openSUSE_13.1/ http://download.opensuse.org/repositories/KDE:/KDE3:/Trident/openSUSE_Facto… P.S. Something is wrong with the opensuse-kde3 mailing list, I has been blacklisted there "for spam" and had to contact the maillist administration. It seems that other users may be also having problems if to judge by the drop in traffic volume last month. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Who is right, who is wrong?
by Basil Chupin 03 Jul '14

03 Jul '14

Last night I downlaoded Factory Snapshot 201406626, burnt it to a DVD and a short time ago tried to follow, word for word, what is stated in- http://en.opensuse.org/openSUSE:Factory_installation Specifically this bit quote: Then add the new repos zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug Oh, yea, pigs will fly, senor! :-( No such repos were added - but invoking each of the above commands produced the "help" screen for zypper. Then I decided to use YaST to install the above repos - and guess what? The piggies did not even begin to show signs of growing wings! :-( The YaST repository screen was empty and remained empty. So, is the blurb in http://en.opensuse.org/openSUSE:Factory_installation rubbish or is there something missing in the Factory Snapshot I downloaded last night? Does anyone have an answer re this, please? BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 26

[opensuse-factory] BFQ KMP for testing
by Takashi Iwai 03 Jul '14

03 Jul '14

Hi, I made a quick add-on KMP for BFQ I/O scheduler that has been posted recently to LKML: https://lkml.org/lkml/2014/5/29/411 If you have a problem regarding I/O and desktop latency, this might be interesting. The KMP is found in OBS home:tiwai:bfq/bfq repo. It's currently built for openSUSE-FACTORY, openSUSE-13.1, SLE12 and Kernel:HEAD kernels. After installing the KMP, load bfq-iosched kernel module, and change the scheduler like: # echo bfq > /sys/block/sda/queue/scheduler If you want to make BFQ as default from the beginning, do like below: - Put "bfq-iosched" in $INITRD_MODULES in /etc/sysconfig/kernel - Run /sbin/mkinitrd once to rebuild initrd - Add a boot parameter "elevator=bfq" Then the BFQ module will be loaded automatically and used as default I/O scheduler at the next reboot. Have fun, Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 15

[opensuse-factory] Grub2 with XFS in root and no /boot ?
by vetter＠physik.uni-wuerzburg.de 02 Jul '14

02 Jul '14

Hi, should it be possible to have XFS in the root partition without separate /boot partition, when using grub2? Here is why I'm asking: I downloaded the Net-Install-CD: openSUSE-Factory-NET-x86_64-Snapshot20140619-Media.iso I booted a VMware VM from it. The VM has 1 GB RAM and a 60 GB disk. I partitioned: sda1 512 MB swap sda2 59.5 GB / xfs Then installed default KDE selection. There are 2 things: 1) When the machine has only 1 GB RAM, installation of bootloader gives no error, but after reboot system hangs in grub2 shell complaining: error: not a correct XFS inode. error: attempt to read or write outside of oartition. error: file '/boot/grub/i386-pc/xxxxx' not found I'm not sure, what xxxxx was. When I use ls (hd0,msdos2)/ it complains: error: not a correct XFS inode. error: attempt to read or write outside of oartition. error: not a correct XFS inode. 2) When system has 2 GB RAM, installing bootloader gives an error, giving the chance to do it again. But that also does not work. rebooting gives the same problems as above. In this case the missing file xxxxx is normal.mod. -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] Is published factory repo up to date?
by vetter＠physik.uni-wuerzburg.de 02 Jul '14

02 Jul '14

Hi, I'm waiting for the grub2 packages with support for xfs v5 superblocks. On https://build.opensuse.org/package/binaries/openSUSE:Factory/grub2?reposito… grub2 has build 14.1 (e.g. grub2-2.02~beta2-14.1.x86_64.rpm) . But in the repo http://download.opensuse.org/factory/repo/oss/suse/x86_64/ grub2 only has build 13.1 (e.g. grub2-2.02~beta2-13.1.x86_64.rpm ) from 24 June. If this is unintentionally (maybe fallout from the SAN problem), can someone please republish the Factory repo? -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1