September 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Testing: DVD vs. CD and kernel 3.0
by Roger Luedecke 09 Sep '11

09 Sep '11

I vaguely remember saying I would do some testing, but as I need my computers to be functional and they are too weak to run a VM this hadn't come to fruition; until now. I was checking out Mandriva, and though it had a lot of promise it sucked in critical ways... thus I had to reinstall. For some reason all I had was a CD ISO of openSUSE. Which was fine since I wanted to get some fresh notes between the discrepancies of the DVD and CD installs. In the course of the first reinstall I decided to try Kernel 3.0 since the reviews were positive enough for me to feel safe To keep it simple here is a list, plus I'm a little drunk. KPackageKit/Updater Does not work in DVD install (at all), works perfectly in CD install(everything). NetworkManager DVD install ye olde KNetworkManager, CD installs Plasmoid. I remember from before there being discrepancies in the behavior of samba betweenst the two. As I have no systems on the network that are able to communicate in that fashion anymore, I cannot pinpoint these. I did however get some help from a fellow on IRC for getting samba to work between openSUSE and my roomies Mac. He was very helpful, I would recommend somebody trying to get some feedback from him on samba. He is "kukks" on IRC. **** **** **** My experience with Kernel 3.0 was fairly positive. Power consumption was down, heat was down, noise was down. Speed slightly up. Weird 30 second countdown in the boot, "connecting." Only managed to load RPM NVidia driver once. I found no application anomalies with using that kernel. I hear there are some vicious problems with the Sandy Bridge architectures, and would recommend adding some sort of release notes to the SUSE welcomer thingy that pops up after a fresh install. I attempted Tumbleweed and got alot of strange errors in the boot process, but since I was having trouble getting to a graphical interface to begin with (thanks to removing the Nouveau driver) I could not be sure if they were critical. Some miscellaneous notes: It seems the brcm80211 driver has come a long way, since it isn't causing any kernel panics anymore. However, it behaved typically off the LiveCD... but after installed behaves superior to the WL driver. This could be due to upgraded kernel (I don't think so) or because its pulling configuration from the unformatted /home partition. I must make note, that whatever the reason it works correctly it is faster by a wide margin to connect to the WIFI. Nouveau is much much better. I imagine that in a years time I may no longer bother to install the proprietary driver. I have discovered some boot arguments that make my netbook run cooler, and the reports all over the web are similar. acpi_osi=Windows or Linux have a cooling effect... they seem to both be equal. There was another one that I was made aware of that I observed no definite effect from; I'll look it up later. I would have suggested that maybe we should include those arguments in future installs, but 3.0 handles power better for the most part (unless you have sandy-bridge) so it may not be relevant anymore. I think this is everything ATM. I will append this if I remember other things. Om namah Shivaaya! Roger Luedecke openSUSE Ambassador -- 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] systemd and not powering off the system
by Robert Kaiser 08 Sep '11

08 Sep '11

Hi, Since I switched from sysvinit to systemd on my Factory system, I notice that it fails to power down after a shutdown, while it did that OK before. Now, it just sits there and tells me the system has been halted but leaves it running. Is that a configuration problem or a systemd-related bug? I found none on file in Bugzilla as a dependency of the "systemd by default" bug, so I wanted to ask here if it's just a one-off. (I found a bug for my second problem, which is apache not starting properly, so I won't complain about that here.) Cheers, Robert Kaiser -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 4

[opensuse-factory] Any words on Plymouth and 12.1 ?
by Nelson Marques 08 Sep '11

08 Sep '11

Like the subject states: "Any word on Plymouth and 12.1" ? Jeff, still working on Plymouth? NM -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

8 21

[opensuse-factory] how come
by Donn Washburn 08 Sep '11

08 Sep '11

could this becausing part of the compile problems. Two same files with different sizes. Which one is correct? -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Skype:n5xwbg BMWMOA #:4146 Ambassador " http://counter.li.org " #279316

3 2

[opensuse-factory] lizards.opensuse.org broken?
by Roger Luedecke 08 Sep '11

08 Sep '11

I can't sign in, and when I click sign up nothing happens... is it broken? -- 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] Systemd experiences (was How to enable systemd at installation time)
by Vahis 08 Sep '11

08 Sep '11

I have now enabled systemd more or less successfully in an M5 running in VBox. Some things and probs that I have ran into: This installation runs in Oracle VBox and I'm used to run also their guest additions. So normally always after a kernel installation I run a script of theirs, 'VBoxLinuxAdditions.run' which has always worked. It did now, but not when booted with (F5) systemd. I booted the default way then and this script did its job normally. A reboot with systemd and I was in business :) There have been some persistent errors in '/var/log/messages' though: Sep 3 11:08:44 121 SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Sep 3 11:08:47 121 SuSEfirewall2: Error: iptables-batch failed, re-running using iptables Sep 3 11:08:48 121 SuSEfirewall2: Error: ip6tables-batch failed, re-running using ip6tables Sep 3 11:08:50 121 SuSEfirewall2: Firewall rules successfully set The above and some others appears frequently: Sep 2 12:03:48 a88-112-25-185 gnomesu-pam-backend: pam_systemd(gnomesu-pam:session): Failed to create session: Invalid argument Sep 3 11:41:09 121 sudo: pam_systemd(sudo:session): Failed to parse message: Message has only 3 arguments, but more were expected Sep 3 11:10:11 121 systemd[1]: Unit NetworkManager.service entered failed state. Sep 3 11:10:11 121 systemd[1]: Unit dev-sda1.swap entered failed state. Sep 3 11:10:11 121 systemd[1]: Job remote-fs.target/start failed with result 'dependency'. Sep 3 11:10:11 121 systemd[1]: Unit data5.mount entered failed state. Sep 3 11:10:14 121 systemd[1]: Unit home-mcman-waxborg_home.mount entered failed state. Sep 3 11:10:14 121 systemd[1]: Unit data1.mount entered failed state. Sep 3 11:10:14 121 systemd[1]: Unit data75.mount entered failed state. Sep 3 11:11:40 121 systemd[1]: Unit NetworkManager.service entered failed state. Sep 3 11:11:40 121 systemd[1]: Unit dev-sda1.swap entered failed state. Sep 3 11:11:41 121 systemd[1]: Unit data1.mount entered failed state. Sep 3 11:11:41 121 systemd[1]: Unit nfs.service entered failed state. Then I thought I'd boot the default way to see how everything goes. The NFS client lost all shares. # mount -a Starting rpc.statd ... portmapper not running failed mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified Starting rpc.statd ... portmapper not running failed mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified Starting rpc.statd ... portmapper not running failed mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified And tens of other stuff. I guess I'll revert to snapshot before systemd and wait for a while. This is interesting and I'm interested in testing but I guess I would need to know what exctly is meant to be achieved with systemd. It must be good, why otherwise would it be pushed, but my skills ran out, sorry for that. Vahis -- http://waxborg.servepics.com openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default "Evergreen" main host openSUSE 12.1 Milestone 5 (x86_64) 3.0.0-4-desktop in VirtualBox openSUSE 11.4 (i586) 3.0.4-43-desktop "Tumbleweed" in EeePC 900 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

16 50

[opensuse-factory] Have builds of openSUSE-DVD-x86_64-Build0nnn-Media.iso stopped ?
by doiggl＠velocitynet.com.au 07 Sep '11

07 Sep '11

Hello Have builds of openSUSE-DVD-x86_64-Build0nnn-Media.iso stopped ? The reason I ask is the last built images I see are: - openSUSE-DVD-x86_64-Build0263-Media.iso 06-Sep-2011 08:33 4.2G - openSUSE-DVD-i586-Build0270-Media.iso 08-Sep-2011 02:55 3.7G Source:http://openqa.opensuse.org/opensuse/factory/iso/ Cheers Glenn -- 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] Taking notes from Mandriva.
by Roger Luedecke 07 Sep '11

07 Sep '11

Taking Notes from Mandriva I recently caught wind that a new version of Mandriva was released. Having checked out the last version on the advice of a good friend, and having been underwhelmed by it I took a look again to see if I could see the magic he spoke of to me. Overall this was indeed a much better release, and were it not for a few show-stopping bugs it may very well have remained on my beloved netbook. One interesting thing of note is that Mandriva has discontinued their multiple versions. They have even abandoned the Gnome environment in favor of KDE. However, their approach was quite unique. Clearly like I had, they too took away some interesting ideas away from Gnome3; and like me were not willing to suffer the bugs. There were a couple interface elements of note. They replaced Kickoff with an interesting full screen ordeal with a document time-line view called SimpleWelcome. Though many don't like the shifting paradigm of including smart phone and tablet interfaces on a desktop, I found its layout mostly comfortable on my tiny netbook. It is very reminiscent of Gnome3. This was part of their new default Plasma panel called RocketBar. The RocketBar is not terribly different from the upstream default, with the exception of SimpleWelcome. I personally did like that their Task Manager was designed so as to only show the application icon, and not a description. As I am fond of docks, I liked this. This is something that should be integrated into the Task Manager as a option. When my friend first told me of Mandriva, he told me that it was all about the eye-candy and polish. This latest release was certainly a good example of that. With a gorgeous new GTK based widget theme, and a simple but elegant set of icons and window decoration Mandriva managed to distinguish itself. But even before that, it is distinguished in its beautiful boot splash, KDM theme, and finally the login splash. Here we can take some pointers seeing as the presentation is encouraging to the new user. They see polish and anticipate a professional distribution. It is of course not a major technological point... but then success rarely comes to the best, but rather to the clever. Now for a brief review of what was under the hood. Mandriva has switched to using systemD, which though not a very obviously faster boot from HD is brilliant when having to boot from Live media. Frankly the prior release of Mandriva was the very very slowest Live boot ever from USB... now it is second in live boot speed only to Fedora. Once again, this may not be critical but it helps. Especially since openSUSE is slow enough when booting from live media as it is, making people think the installer or live boot has frozen. Mandriva also uses the Plymouth splash, which seeing as it resembles the last splash nearly identically I assume it used last time. Since I am unfamiliar with Plymouth vs. Splashy I can only say one should go take a look. There were two show stopping bugs for me, one which we share in some degree. That being the issue with overheating. In Mandriva the overheating was extreme enough to shut my netbook down. From what I understand this is caused by a poor ACPI implementation. One thing that has helped is to add a line pertaining to ACPI into the grub boot options string. We may want to add one of these parameters by default. I apologize for the verbosity of my letter, but considering the number of points I wished to bring up felt it necessary. So in an effort to relieve tedium, I hope my letter has been as engaging of a read as I hoped. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 35

[opensuse-factory] systemd or not systemd - todays bug?
by jdd 07 Sep '11

07 Sep '11

Hello, I have two factory boot: one with systemd on the kernel command line, and the very same one, but without the option. after a today zypper dup (only complaining about some libreoffice library), the one with systemd option do not find the harddrive so no log), but the version without systemd boots perfectly That said, my /var/log/messages is full of systemd calls! (here the end: Sep 7 13:43:15 linux-lpd0 systemd[1]: Child 7672 died (code=exited, status=0/SUCCESS) Sep 7 13:43:15 linux-lpd0 systemd[1]: Child 7672 belongs to network.service Sep 7 13:43:15 linux-lpd0 systemd[1]: network.service: control process exited, code=exited status=0 Sep 7 13:43:15 linux-lpd0 systemd[1]: network.service got final SIGCHLD for state stop Sep 7 13:43:15 linux-lpd0 systemd[1]: network.service changed stop -> dead Sep 7 13:43:15 linux-lpd0 systemd[1]: Job network.service/stop finished, result=done Sep 7 13:43:15 linux-lpd0 kernel: Kernel logging (proc) stopped. Sep 7 13:43:15 linux-lpd0 rsyslogd: [origin software="rsyslogd" swVersion="5.8.4" x-pid="899" x-info="http://www.rsyslog.com"] exiting on signal 15. ) so I wonder if systemd is now default? if not may I fill a bug report for the other one (the one that stops at HDD not found) thanks jdd -- http://www.dodin.net http://pizzanetti.fr -- 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] (most likely) kiwi broke x86_64 factory
by Stephan Kulow 07 Sep '11

07 Sep '11

Hi, If you zypper dup your factory installation, don't be suprised if zypper suggests to reinstall your system as 32bit - the current FTP tree has no x86_64 packages that zypper would see. Most likely cause of this is a new kiwi checked in yesterday, so hopefully it's easy enough to fix. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 1