April 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] help with zypper
by don fisher 11 Apr '15

11 Apr '15

I wanted to build a openSuse 13.2 system on an AMD rather than my current Intel platform. I was planning on installing 13.2 from the installation disk, then adding the packages required to mirror my current system. I have studied a lot of the zypper manpage, bloody 1953 lines long! I found a file /var/log/zypp/history that appears to contain all of the updates to my system. The manpage suggests "see the shell command". But the manpage also says "shell support is not complete so expect bugs there". The history file appears to have installation date and time, a command, package name, version, architecture, followed by what appears to be maybe some path to the RPM? Is this what the shell is expecting, and will it read these lines and update my other machine? Or is this the wrong approach all together? The manpage states that if I had set the keeppackages property, all of the RPMs would be saved in /var/cache/zypp/packages and I could use zypper to install them directly from there. But I did not know about that property until recently. Comments, suggestions? Thanks Don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 19

[opensuse] Problem adding Wireless after install
by Carl Spitzer 11 Apr '15

11 Apr '15

On laptops and desktops this works aucomagically when the wireless is connected at install time. However if you forgot it or went old school and later decide to add wireless your in problems. Currently I have an older system with 11.4 on it and I am trying to add wireless after the fact with Yast. I have installed iw and smpppd and gone into Yast to setup the Engenious 9603H which works fine on the laptops. I have tried setup in Yast with manual trigger ifup ifdown and no go. What is the best way to overcome this short of reinstall. And before you ask most of my stuff is to old for 13.x even my best systems choke on Gnome 3. so upgrading to a hung system is not in the works. CWSIV -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

Re: [opensuse] Problem adding Wireless after install
by I.Petrov 11 Apr '15

11 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, Please reply to the mailing list where the next essential question in this topic has been asked almost at the same time when this email has been received. Do you have wpa_supplicant installed ? Best Regards, I. Petrov On 04/11/2015 02:35 AM, Carl Spitzer wrote: > On Sat, 2015-04-11 at 00:32 +0300, I.Petrov wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> Hello, >> >> Please explain where exactly is the problem. The device cannot be recognized at all? The device cannot connect to a wireless network ? The >> device cannot be configured through Yast ? Something else ? > > Yast can see and configure the device after warning me I needed to install IW and SMPPPD but then ifup does not turn it on when i checked manual > for activation as opposed to on hotplug. > > CWSIV -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVKHEpAAoJEH8sJoKRFRU5xlAQAKTSHBn4J/OKrrFu3Q7B2nSn aLZWv0MuaJFXkHBe8pDWhB8rYeMLg/VGxywjumIrAanggsAqaopIoAlYa/WqtjXe s8rBvo5L6tG/ygfLpTi0f20nVfiFKvmnPDIwHNqi4veMPCmag+PszvLeoqfs6iG5 Vrvd2HnB8PxVmiH9d24ElmQEzG6Uxzce0YDJdjIAtu6vkz0WeuDwzv0tUc9lHUnG ZlQMS5GHS6v4lpmED45MPXmc/2pPYezObT9iMLpwsUfY4nM5OdjZ4eaKnhlOW/dA fdRP6K8g3bAsSb4M/sACXxsc16S8jdgDBLZbN5qkFlvy35CCLnsOTYi/HweKlM1+ 19sKvwAoRRZGdJBODvCcikbRUTwO6tHh/yMsRpvarcs/OOya0Jkpad42ktnHRuqP roVcPdWPTa3QBM3xoLFa0SzUEG3e6BK2cPW+u5v5IYWYSL6gSf5DrDyV3gJtQCu2 iSov2Y8lFVgB0acfZU44dlZYpYfnTi1HRLttyXmBdB67V2o3Ksh7MgylF8LQqxq9 WZyxWVMkyhHZnYvYQBCY9/pJLkX55hiii1Y+Q0p/ym4VkPXq355KqDSRxDaVagax PizvE6EVqCXvMixB3Q3ZemloE2YqeoKCLokph+5yeQhA6ZpcSUegBgjXyrRhiDUD 1bYGt/wvivglRALdN7sN =D9Qp -----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] Help with VGA display on laptop.
by don fisher 10 Apr '15

10 Apr '15

I have just begun researching this problem, so pardon me if I missed the obvious again;-) I have a Dell 1721 laptop with an AMD/ATI RD690M {Radeon Express 1200/1250/1270] graphics controller. OpenSuse 13.2 functions perfectly on the internal UXGA laptop screen. But when I connect an external monitor (Dell 2405FPW also UXGA) and boot the system the graphics are trashed. Both are UXGA, and I tried Unified Outputs. And this also happens when the monitor is turned off during the boot. So I assume it is the presence of the VGA plug that is causing the corruption during boot. If I plug the monitor in after the system has been booted the monitor does not detect the computer, suggesting that the computer is in a sleep mode. But if I look at System Settings/Display Configuration GUI both screens are shown. The laptop monitor is working great and the external monitor sees nothing. I have successfully used this pair of devices since 2008 under Fedora?? So I assume it is a setup problem. Tomorrow I will try a fresh install from the distribution disk with the monitor connected to see if there are any variations. I also tried to make a VGA connection from my laptop that provides HDMI connections. It has an Intel graphics chipset. I used an HDMI to VGA adapter and achieved similar results. But if I connect this unit via the HDMI cable rather than the VGA cable it functions correctly. Tomorrow I will also try connecting the this computer through the VGA cable to the HDMI monitor, as opposed to the UXGA monitor. Is there a guide to setting up X under openSuse 13.2? Since the system works in single monitor mode, I am assuming that the kernel modules etc. are correct. Nothing obvious was present in my dmesg file, but I am not sure what to look for. I have edited xorg.conf files since the 90s, but I believe that is discouraged now. Any suggestions would be appreciated. Thanks, Don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] sshd.service (openssh) fails on boot when primary listener is a bridge (br0) instead of real interface (eth0). What dependency is needed?
by lyndat3＠your-mail.com 10 Apr '15

10 Apr '15

Hi, opensuse 13.2's openssh /usr/lib/systemctl/systemd/sshd.service has a After=network.target dependency. When a real ethernet interface, eth0, is the primary 'net listener, cat /etc/sysconfig/network/ifcfg-eth0 STARTMODE='auto' BOOTPROTO='static' IPADDR='192.168.1.1/24' sshd, listening on 192.168.1.1, has no problems on boot. But, if I switch to using a bridge interface, br0, with eth0 as the real interface assigned to it, cat /etc/sysconfig/network/ifcfg-eth0 STARTMODE='auto' BOOTPROTO='none' cat /etc/sysconfig/network/ifcfg-br0 STARTMODE='auto' BOOTPROTO='static' BRIDGE='yes' BRIDGE_PORTS='eth0' IPADDR0='192.168.1.1/24' sshd fails on boot journalctl -b | grep -i sshd ... Apr 10 15:30:49 xen01 sshd[1345]: error: Bind to port 22 on 192.168.1.1 failed: Cannot assign requested address. ... Apparently, network.target 'waits' for *real* interfaces only. Once at the shell, br0 is fully up. sshd can be started, and it functions normally. What specific dependency can I add to the sshd unit to get it to wait for br0 being fully up? LT -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Trying out wordpress - can't install a theme?
by Greg Freemyer 10 Apr '15

10 Apr '15

All, Is there write-up for how to get wordpress to run and allow themes to be installed in opensuse? == my status == Wordpress is in the server:php:applications repo so I installed it. I've hit 2 errors so far, and still can't install a theme: - Issue one: mod_php5 not enabled Solution: a2enmod mod_php5 (or can be done via yast) That allows basic wordpress to run and new posts to be made. The first thing I tried after that was installing a theme. - Error when trying to install a theme: "There are no HTTP transports available which can complete the requested request." Solution I used: zypper in php5_curl - Exposes a second error when trying to install a theme: === Downloading install package from https://downloads.wordpress.org/theme/guardian.2.0.zip… Unpacking the package… Abort class-pclzip.php : Missing zlib extensions === I haven't found the fix for that yet, but I'm surprised to hit these issues trying to get a popular package to work. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] After fixing bridge interface activation on boot, wicked slows down boot time significantly?
by lyndat3＠your-mail.com 10 Apr '15

10 Apr '15

I'm running opensuse 13.2. For running Xen, I need a bridge interface. To get the network bridge to be activated on boot, you have to enable wicked-nanny /etc/wicked/common.xml - <use-nanny>false</use-nanny> + <use-nanny>true</use-nanny> It's a known bug that say's "fixed" by a new wicked release. I'm not seeing it https://bugzilla.novell.com/show_bug.cgi?id=911562#c21 After enabling nanny, boot takes noticeably longer. It's due mostly to wicked systemd-analyze blame 44.082s wicked.service 3.745s lvm2-activation-early.service 1.101s lvm2-activation.service ... journalctl -b | grep -i wicked Apr 10 11:27:46 xen01 wickedd-dhcp6[1261]: Using netlink event receive buffer of 1048576 bytes Apr 10 11:27:46 xen01 wickedd-dhcp4[1262]: Using netlink event receive buffer of 1048576 bytes Apr 10 11:27:46 xen01 wickedd-auto4[1263]: Using netlink event receive buffer of 1048576 bytes Apr 10 11:27:46 xen01 wickedd[1283]: Using netlink event receive buffer of 1048576 bytes Apr 10 11:27:46 xen01 wicked[1305]: eno1: configuration applied to nanny Apr 10 11:28:23 xen01 wicked[1305]: br0: configuration applied to nanny Apr 10 11:28:23 xen01 wickedd[1283]: br0: successfully verified address '192.168.1.1' Apr 10 11:28:24 xen01 wickedd[1283]: br0: successfully notified about address '192.168.1.1' Apr 10 11:28:29 xen01 wickedd[1283]: br0: No duplicates for IP address 192.168.1.1 detected Apr 10 11:28:29 xen01 wickedd[1283]: br0: Notified neighbours about IP address 192.168.1.1 Apr 10 11:28:30 xen01 wicked[1305]: lo: configuration applied to nanny Apr 10 11:28:30 xen01 wicked[1305]: Interface wait time reached Apr 10 11:28:30 xen01 wickedd[1283]: ni_process_reap: process 1583 has not exited yet; now doing a blocking waitpid() Apr 10 11:28:30 xen01 wickedd[1283]: lo: address 127.0.0.1 covered by a static lease Apr 10 11:28:31 xen01 wickedd[1283]: lo: address ::1 covered by a static lease Apr 10 11:28:33 xen01 wicked[1305]: lo device-unconfigured Apr 10 11:28:33 xen01 wicked[1305]: eno1 enslaved Apr 10 11:28:33 xen01 wicked[1305]: br0 up I'd like to have both (1) br0 up on boot (2) an improved boot time, reducing wicked's 'wait' What config changes need to be made to get both? LT -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] Manually checking ext4 file system for any errors
by Anton Aylward 08 Apr '15

08 Apr '15

On 04/08/2015 07:04 PM, Joe Zappa wrote: > Anton Aylward wrote: >> On 04/05/2015 03:28 AM, Basil Chupin wrote: >>> >>> I got the response (error msg) that- >>> >>> mount: / is busy >> >> Subtext and slightly off topic. >> >> This is one reason I have a very small ROOT file system and lots and >> lots of mounted file systems. In maintenance mode I can unmount then >> all and easily fsck them. Yes the ROOT-fs is another matter, ... > > > I'm the same way: > > .... > > /dev/sda1 on /boot type ext4 (rw,relatime,data=ordered) Excellent! Despite anything that basic may say, having a /boot partition, especially as a primary rather than on LVM is an excellent idea and adds greatly to the resilience and manageability of your system It should be part of the default installation. > What's wrong with C? You mean compared to modern scripting languages like Ruby and or even older ones like Perl, tcl, functional languages (Lisp, Scheme, Clojure, etc.) ones with type inference (ML, OCaml, Haskell, Scala), specialized ones like Mathematica, Matlab, R, or Maple, and even shell. Ah right, applications rather than kernel. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Manually checking ext4 file system for any errors
by Basil Chupin 08 Apr '15

08 Apr '15

In a galaxy long ago one could boot into openSUSE by putting level 1 in the boot command and login as root after which you could manually check for any errors in the ext3 or ext4 file system by issuing the following commands: mount -o remount, ro /dev/<hdX>/<sdX> followed by e2fsck /dev/<hdX>/<sdX> and, if errors were found, follow the prompt(s) to have any errors repaired. A few minutes ago I tried this on the laptop which has Tumbleweed installed on ext4 file system (I didn't want to this experiment on my main system on the desktop). Booting into level 1 seems to be OK and logging in as root was OK but then when I issued the command- mount -o remount, ro /dev/sda5 [#] I got the response (error msg) that- mount: / is busy The above sequence of commands worked for years in SuSE and then openSUSE so why has it now stopped working? Or put another way, how does one go about manually checking the file system for errors by running "e2fsck"? Why run "e2fsck" manually you may ask? Because I have found that the checking which is done automatically after X number of boots by the built-in system does not always pickup the errors in the ext3/4 file system. (Don't try to convince me otherwise because I have proven that to myself several times over the years. In any case, this is not the point. The point is why I now cannot check the file system using the method above which was spelt out in detail in the Administrative Manual which came with the version of S.u.S.E.?) Can anyone please give details on how now to manually check the ext3/4 file system for errors? [#] sda5 is where / of TW is installed. BC -- Using openSUSE 13.2, KDE 4.14.6 & kernel 3.19.3-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+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 30

[opensuse] default routeS post-13.1
by Felix Miata 08 Apr '15

08 Apr '15

[13.2 and Tumbleweed, with Wicked; no wireless; 1 interface per host] Googling 'site:opensuse.org sdb: network" produces nothing containing string "wicked". 'site:opensuse.org sdb: network wicked' produces nothing containing string "sdb:". https://en.opensuse.org/Portal:Wicked contains nothing obviously about configuration in its few listed topics. Now that the old ways have been replaced with Wicked, search results are even harder to sift through, assuming one can get onto the web in the first place... Can more than one default route per interface be configured? If so, where? /etc/sysconfig/network/ifroute-<interface> ??? /etc/sysconfig/network/routes ??? elsewhere ??? If not, which file or files must be changed to contain the relevant GW IP? I configure my own installations with fixed IP. I want to be able to take any of them elsewhere, discover the IP of the relevant gateway/router, and using mcedit, change, or add, whatever is necessary, without starting any GUI, YaST, or any kind of "manager". Is this asking too much? I tried this several hours ago. Getting/using an IP was no problem. Working DNS was no problem. Never could get a default route into a routing table. 'route add default gw <IP>' didn't do anything regardless of what I tried changing in /etc/sysconfig/network/. What else I tried I cannot remember. :-( Same machine I specially preconfigured before leaving here with an additional 13.1 with DHCP. So when I left here, I had 1 DHCP and 3 fixed IP openSUSE installations that worked. Routing worked there in 13.1 with DHCP initially (e.g. success to ping www.google.com) but never again after lost Dlink DIR-655 router password required doing a hard reset, which reset its IP to its default 192.168.0.1. Afterward, no matter what I booted, if ifconfig -a showed a properly configured interface, I could reach the router and login with Firefox, and I could ping the router, but I could not ping www.google.com ('no route to host', among other observed failures, such as no reaction at all, depending on which OS booted). I gave YaST2 a try in either 13.2 or TW, but it didn't give me a working GW either. :~( -- "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+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 25