December 2014 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] NetworkManager fails with dhcp time-out
by John Andersen 05 Dec '14

05 Dec '14

On 12/04/2014 04:11 PM, Patrick Shanahan wrote: > "All users", but only after > issuing "/sbin/dhcpcd <dev>" and if the network get reset, the current > version of dhcpcd must be killed and restarted before another successful > connect. See, I don't think dhcpcd should be running At ALL. Its not on my machine, it has nothing in /var/lib/dhcpcd for it's pid. If I launch System Monitor, and look at the Process Table and type dhcpcd in the search field it shows nothing, but if I type dhclient it is running. (set the pull-down to all processes tree, and you can see that dhclient is started byt network manager, which in turn is started by systemd) I wonder if this isn't being started by some historical artifact of your prior struggles. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] crash with 13.2/ssd
by jdd 04 Dec '14

04 Dec '14

Hello, I installed 13.2 on a brand new 256Gb ssd. So far so good. all works perfectly, but crash without visible reason twice a day. * I see nothing in the logs (journalctl -b -1 from memory) by the way is there a way to look at the logs from an other install, that is a 13.1 install? how can I look at the binary file system.journal? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] test
by jdd 04 Dec '14

04 Dec '14

sorry it seems than my posts do not reach the list anymore jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] [RESOLVED] oS 13.2: losetup not working - permission denied?
by Greg Freemyer 04 Dec '14

04 Dec '14

The issue is that I was running the fuse mount command as a normal user and mount as root. By default fuse does NOT allow root to access filesystems it creates unless root created them. For me there are 2 work-arounds: - Add sudo in front of my command creating the filesytem - Set an option in /etc/fuse.conf to allow none-owners of a filesystem to use the filesystem. Greg On Wed, Dec 3, 2014 at 6:58 PM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > On Wed, Dec 3, 2014 at 4:36 PM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: >> I know I've used loopback mounts on openSUSE before, but today they >> aren't working for me. >> >> As an example: >> >> === >> + ls -l /mnt-ewf/ewf1 >> -r--r--r-- 1 root root 1000555581440 Dec 3 16:33 /mnt-ewf/ewf1 >> + sudo /usr/sbin/losetup /dev/loop0 /mnt-ewf/ewf1 -o 209735680 >> root's password: >> losetup: /mnt-ewf/ewf1: failed to set up loop device: Permission denied >> === >> >> I have the loop module loaded: >>> sudo /sbin/lsmod | grep loop >> loop 28312 0 >> >> I tried "modprobe loop" just in case, but it doesn't help. >> >> What am I forgetting? >> >> Thanks >> Greg >> -- >> Greg Freemyer > > This just gets stranger. > > I've found that if use a true file to loopback mount from, then all is good. > > Instead I'm using a virtual block device to mount. In past versions of > openSUSE I could do that and it worked fine. > > [to be more explicit I'm using ewfmount to leverage the fuse kernel > subsystem to create a single non-segmented, non-compressed dd image > from a segmented / compressed image. I've done this many times before > but with 13.1 and older.] > > With opensuse 13.2, it is failing. I'm wondering if something in the > kernel changed. > > I have no idea how to troubleshoot this. > > Thoughts? > > Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] WARNING: CPU: 5 PID: 301 at /home/abuild/rpmbuild/BUILD/kernel-pae-3.11.10/linux-3.11/block/blk-core.c:493 blk_queue_bypass_end+0x52/0x60()
by Per Jessen 04 Dec '14

04 Dec '14

See full text: http://files.jessen.ch/antonov-tracetxt Environment - pretty ancient HP box, openSUSE 13.1, 4Gb RAM. This error happens on every startup, but does not seem to cause any further problems. The box is dedicated to testing, can be accessed at all times. I'll be happy to open a bugreport if anyone wants to pursue. -- Per Jessen, Zürich (4.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] dracut - how do I get to see a summary of kernel modules and dracut modules chosen?
by Per Jessen 03 Dec '14

03 Dec '14

See $SUBJ - with mkinitrd, there was always a couple of lines listing which modules had been included. With dracut, I get what looks mostly like debug output, but no summary of what was built, see below. # mkinitrd -k vmlinuz-3.16.6-2-default -i initrd-3.16.6-2-default Creating initrd: /boot/initrd-3.16.6-2-default Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-3.16.6-2-default 3.16.6-2-default dracut module 'plymouth' will not be installed, because command 'plymouthd' could not be found! dracut module 'plymouth' will not be installed, because command 'plymouth' could not be found! dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! *** Including module: bash *** *** Including module: warpclock *** *** Including module: i18n *** *** Including module: network *** *** Including module: ifcfg *** *** Including module: kernel-modules *** Omitting driver i2o_scsi *** Including module: nfs *** *** Including module: rootfs-block *** *** Including module: terminfo *** *** Including module: udev-rules *** Skipping udev rule: 91-permissions.rules Skipping udev rule: 80-drivers-modprobe.rules *** Including module: systemd *** *** Including module: usrmount *** *** Including module: base *** *** Including module: fs-lib *** *** Including module: shutdown *** *** Including module: suse *** *** Including modules done *** *** Installing kernel module dependencies and firmware *** *** Installing kernel module dependencies and firmware done *** *** Resolving executable dependencies *** *** Resolving executable dependencies done*** *** Hardlinking files *** *** Hardlinking files done *** *** Stripping files *** *** Stripping files done *** *** Generating early-microcode cpio image *** *** Constructing GenuineIntel.bin **** *** Store current command line parameters *** Stored kernel commandline: root=nfs4:mirage:/home/airbus:rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.146,local_lock=none,addr=192.168.2.151 ip=enp3s1f0:static *** Creating image file *** *** Creating image file done *** Update bootloader... -- Per Jessen, Zürich (5.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] OpenSuse 13.2 and grub2
by Moby 03 Dec '14

03 Dec '14

I performed a new installation of OSS 13.2 on a laptop. As per default, it uses grub2. When the machine boots, I see a menu with options "Opensuse", and "Advanced". If I choose (or let the system choose by default) OpenSuse, then the machine proceeds to boot, comes to the GUI login screen, and at that point my keyboard and mouse do not work at all. If I choose "Advanced" from the grub menu, and then choose the latest kernel that is displayed, everything works fine. My question is whether there is away to see what options are being used by the various grub menu entries once the machine is up and running (as it is now and I'd rather not reboot it if I do not have to)? The old GRUB used a text based configuration file, which was fine but limited. The new one is much more dynamic in that most of the configuration is done via scripts, but it would be nice if it writes the "final results" and menu options etc somewhere for debugging purposes. If not, then is my only option to trace through the code of all the scripts to see what those options are presenting or reboot the machine and then examine the menu options? Regards, -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] Broadcom BCM43xx WiFi driver and 13.2
by Vojtěch Zeisek 03 Dec '14

03 Dec '14

Hello, in previous versions it was more or less working that driver for Broadcom wifi card was automatically installed. I tried fresh install of 13.2 on two different machines equipped with Broadcom (BCM4313) and during installation, I could connect to the wifi and use on-line repositories. But after installation the driver was missing and network card was not configured. This is really weird: some HW works during installation but fails later. This driver should be part of kernel, I think. I had to install it manually. KDE4 wasn't able to tell me what is wrong. XFCE told me that firmware is missing. And I had to configure the network card in YaST. I see this as regression when comparing with 13.1. Anyone has similar experience? Should I report is as a bug? Best, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/

2 4

[opensuse] Long wait between password and shell on SSH on OS13.2
by Tom Bühlmann 03 Dec '14

03 Dec '14

Hello list! I see a strange effect on my updated OpenSuSE 13.2: I can login via ssh without problems. But after the pasword promt there is a env. 30 sec wait time until the shell finally appears. I see the same effect also while using "sudo". in the /var/log/messages i see this: tbuhl dbus[19657]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' 2014-12-02T22:16:26.153336+01:00 tbuhl dbus[19657]: [system] Failed to activate service 'org.freedesktop.login1': timed out 2014-12-02T22:16:26.153878+01:00 tbuhl cron[15446]: pam_systemd(crond:session): Failed to create session: Die Wartezeit für die Verbindung ist abgelaufen 2014-12-02T22:16:26.720197+01:00 tbuhl CRON[15446]: pam_unix(crond:session): session closed for user root Die Wartezeit für die Verbindung ist abgelaufen -> timeout waiting for connection and systemd's journalctl -u dbus tells me : Dez 02 22:16:26 tbuhl dbus[19657]: [system] Failed to activate service 'org.freedesktop.login1': timed out Any idea what can go wrong here? Thanks for any input that can help! --Tom -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 5

[opensuse] Regression in Qt 5.4.0 from KDE:Qt5
by Stanislav Baiduzhyi 03 Dec '14

03 Dec '14

Using openSUSE 13.2, just updated Qt to 5.4.0~rc from KDE:Qt5 repository. Here's how my yast looks like now: https://drive.google.com/open?id=0B5Kp-cB1sXJrQjcxSktvUDVJWlk&authuser=0 That is 5pt font on 167DPI 13" laptop. With Qt 5.3.2 from the same repository everything worked correcly. Is that expected behaviour and I have to do something after update to 5.4.0, or that is regression? -- Regards, Stas -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6