November 2011 - openSUSE Users - openSUSE Mailing Lists

[opensuse] 12.1 and /dev/ttyS# problem with mythtv
by terry 28 Nov '11

28 Nov '11

For some reason I have problems trying to install mythtv under opensuse 12.1. I posted a similar message in the mythtv forum however I think this is related to some changes in opensuse. ref: opnseuse 12.1 3.1.0-1.2-desktop mythtv 0.24 dct-channel v 1.7 HDPVR Motorola cable box Problem: the channel change script to use the serial port connected to the STB does not work. /dev/tty5 is present, permissions are OK, when call it to change channels hangs before DCT. $ channel -p /dev/ttyS5 -vv 12 cursor moves to the next line and produce no errors and stays there. If I $ channel Communication failed after 5 tries 0 Which show channel is working but /dev/ttyS0 (default) is not connected which is correct. Description. I have a machine with dual boot, having opensuse 11.4 and opensuse 12.1 in two different HD. Everything works Ok under opensuse 11.4 which ruled out BIOS setup as a problem. I did 2 clean installation in 12.1 with the same results. The pci serial card is recognized # dmesg | grep Oxford [ 1.726854] 2 ports detected on Oxford PCI Express device - ttyS5 is present in both - setserial gives the same result in both :~> setserial /dev/ttyS5 /dev/ttyS5, UART: 16950/954, Port: 0x0000, IRQ: 18 - the udev info is ALMOST the same in both #udevadm info -a -p $(udevadm info -q path -n /dev/ttyS5) every line in both OS is the same with one exception that the following line is present only in 11.4 ATTRS{modalias}=="pci:v00001415d0000C158sv00001415sd0000C158bc07sc00i02" but i do not think makes any difference ? # dmesg | grep serial [ 1.569725] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.720562] serial 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 1.752498] serial 0000:07:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 same in both OS versions # dmesg | grep tty [ 0.000000] console [tty0] enabled [ 1.569725] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.711140] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.720714] ttyS4: detected caps 00000700 should be 00000500 [ 1.720718] 0000:04:00.0: ttyS4 at MMIO 0xfb601000 (irq = 18) is a 16C950/954 [ 1.736566] ttyS5: detected caps 00000700 should be 00000500 [ 1.736579] 0000:04:00.0: ttyS5 at MMIO 0xfb601200 (irq = 18) is a 16C950/954 [ 1.773294] 0000:07:01.0: ttyS6 at I/O 0xd080 (irq = 19) is a 16550A In summary the serial port is recognized and udev produces the device. It could be that other device is being used by the serial but I have tried the other ttsS# with no good results. Any tips? Am I not loading a module required for this task? Thxs -=terry=- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] download.opensuse.org (Domain name not found) - "zypper up" fails after upgrade to 12.1
by Adam Tauno Williams 28 Nov '11

28 Nov '11

I updated my perfectly working openSUSE 11.4 to 12.1, after which "zypper up" fails and no repos on download.opensuse.org can be used - linux-yu4c:~ # zypper up Download (curl) error for 'http://download.opensuse.org/distribution/12.1/repo/oss/content': Error code: Connection failed Error message: Could not resolve host: download.opensuse.org (Domain name not found) Abort, retry, ignore? [a/r/i/?] (a): ^Clinux-yu4c:~ # host download.opensuse.org download.opensuse.org has address 195.135.221.134 download.opensuse.org has IPv6 address 2001:67c:2178:8::13 linux-yu4c:~ # I've tried disabling IPv6 and using a different DNS server. What the ... ? Another user, on a different network, has the same problem after upgrading. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Another clueless list member
by James Knott 28 Nov '11

28 Nov '11

I have received several of these messages because someone used a bogus email address, which causes messages posted to this list to bounce when sent to that person. Please do not *EVER* use a bogus email address on a mail list, as you will create a storm of bounced messages for other list members. Mail Delivery System wrote: > This is the mail system at host notebook-olli.site. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > > The mail system > > <oliver(a)localhost.site> (expanded from<oliver@localhost>): data format error. > Command output: oliver: Mailbox does not exist > > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

[opensuse] Booting with a shell in initrd with systemd
by Javier Conti 28 Nov '11

28 Nov '11

Hi list, I installed openSUSE 12.1 on an PC-Engines Alix system board, which uses the pata_amd driver to access its compact flash disk. Since I installed the system on a virtual machine before putting the flash in the real hardware, the driver was not included in the initrd image and obviously I couldn't see the disk on the real hardware. Booting the compact flash in the virtual machine and rebuilding the initrd image with the driver included solved the issue. However, I tried quite hard to get a shell early during the boot process, in the initrd environment, before trying to mount anything, but failed. I tried the various "Single", "S", "1", "init=/bin/bash", etc, as in older systems, but none stopped before trying to mount /dev/sda1. Then I tried "systemd.unit=emergency.target", but that didn't stop before trying to mount the disk. Since I'm very new to systemd, I'd like to know how to get a shell as early as possible during the boot process in order to easily troubleshoot situations where rootfs (or even the whole disk) is not accessible at boot time for some reason. Thanks, Javier -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] SUSE 12.1 - still "hdd killer bug"? Can't believe it.
by Juan R. de Silva 28 Nov '11

28 Nov '11

I installed openSUSE 12.1 to give it a try on my Dell Latitude D820 with WD 500G hdd on it. Luckily I checked it almost right away and to my astonishment found that Load_Cycle_Count of drive gets 22 times increase in 15 minutes. The drive APM_level = 254, KDE Power Management settings are all set for Performance. I just can't believe it... This is several years back bug. And it was fixed at least for a couple of years back on all major distributions. I have currently installed on the same laptop: Ubuntu 11.10, Kubuntu 11.10, Xubuntu 11.10, Lubuntu 11.10, Fedora 16, SL 6.1, Majea 1, Debian Squeeze, and openSUSE 12.1. Neither of mentioned, but openSUSE, is suffering from this bug. And yet interestingly enough I do not see any complaints of the sort neither on this list, nor on forums. Folks, what's wrong with me? :-) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 17

[opensuse] Can't build Samba 4 on 12.1
by lynn 28 Nov '11

28 Nov '11

Hi I have the latest git of Samba 4. It builds fine on Ubuntu 11.10 but not on 12.1. It falls over here: [ 976/3909] Compiling source4/lib/tls/tls.c ../source4/lib/tls/tls.c: In function ‘tls_init_server’: ../source4/lib/tls/tls.c:508:2: error: implicit declaration of function ‘gnutls_transport_set_lowat’ [-Werror=implicit-function-declaration] ../source4/lib/tls/tls.c: In function ‘tls_init_client’: ../source4/lib/tls/tls.c:569:2: warning: ‘gnutls_certificate_type_set_priority’ is deprecated (declared at /usr/include/gnutls/compat.h:288) [-Wdeprecated-declarations] cc1: some warnings being treated as errors Waf: Leaving directory `/home/lynn/samba-master/bin' Build failed: -> task failed (err #1): {task: cc tls.c -> tls_1.o} make: *** [all] Error 1 I have tried with all the gnutls devel stuff installed via zypper. Has anyone else had a go at Samba 4 on 12.1? can confirm error on 64 bit and via word of mouth on 32 bit. Thanks. L x -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] sabayon cannot edit profiles; "failed to create drawable"
by Adam Tauno Williams 28 Nov '11

28 Nov '11

Anyone used sabayon on openSUSE 12.1? Editing a profile always fails. awilliam@linux-dauq:~> gnomesu sabayon MainThread 2011/11/28 12:56:38.7378 (admin-tool): Creating profiles dialog MainThread 2011/11/28 12:56:38.7759 (admin-tool): Starting main loop MainThread 2011/11/28 12:56:41.0401 (USER): Starting to edit profile 'Kiosk' MainThread 2011/11/28 12:56:41.3838 (sabayon-session): Starting session window for profile_name='Kiosk', profile_path='/tmp/profile-sabayon-admin-b8rumk.zip', display_number='1' MainThread 2011/11/28 12:56:41.4251 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'Kiosk', '--admin-log-config=/etc/sabayon/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmpLNFMyg'] MainThread 2011/11/28 12:56:41.6435 (sabayon-apply): Applying profile 'Kiosk' for user 'sabayon-admin' failed to create drawable Success: created profile 'sabayon-admin' at '/tmp/sabayon-temp-home-BYm9gN/.mozilla/firefox/2ktmb09t.sabayon-admin/prefs.js' MainThread 2011/11/28 12:56:42.2073 (sabayon-apply): Finished applying profile 'Kiosk' for user 'sabayon-admin' ===== BEGIN MILESTONES (/usr/sbin/sabayon-apply) ===== MainThread 2011/11/28 12:56:41.6435 (sabayon-apply): Applying profile 'Kiosk' for user 'sabayon-admin' MainThread 2011/11/28 12:56:42.2073 (sabayon-apply): Finished applying profile 'Kiosk' for user 'sabayon-admin' ===== END MILESTONES (/usr/sbin/sabayon-apply) ===== ===== BEGIN RING BUFFER (/usr/sbin/sabayon-apply) ===== MainThread 2011/11/28 12:56:41.6435 (sabayon-apply): Applying profile 'Kiosk' for user 'sabayon-admin' MainThread 2011/11/28 12:56:42.2073 (sabayon-apply): Finished applying profile 'Kiosk' for user 'sabayon-admin' ===== END RING BUFFER (/usr/sbin/sabayon-apply) ===== This configuration for the debug log can be re-created by putting the following in /etc/sabayon/sabayon-debug-log.conf (use ';' to separate domain names): [debug log] max lines = 1000 MainThread 2011/11/28 12:56:42.2335 (proto-session): Finished running sabayon-apply with normal exit status MainThread 2011/11/28 12:56:42.4045 (sabayon-session): Entering main loop. Wheeee! MainThread 2011/11/28 12:56:42.4077 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop MainThread 2011/11/28 12:56:42.4089 (admin-tool): Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/sabayon/errors.py", line 125, in wrapper return func (*args, **kwargs) File "/usr/lib64/python2.7/site-packages/sabayon/sessionwindow.py", line 330, in __session_mapped self.session.start (str (self.session_widget.session_window.xid)) File "/usr/lib64/python2.7/site-packages/sabayon/protosession.py", line 490, in start self.__start_xephyr (parent_window) File "/usr/lib64/python2.7/site-packages/sabayon/protosession.py", line 326, in __start_xephyr self.xephyr_xauth_file = self.__write_temp_xauth_file (True) File "/usr/lib64/python2.7/site-packages/sabayon/protosession.py", line 283, in __write_temp_xauth_file xauth_data_len) + xauth_data error: 'h' format requires -32768 <= number <= 32767 MainThread 2011/11/28 12:56:42.4154 (sabayon-session): Terminating MainThread 2011/11/28 12:56:42.4155 (sabayon-session): Exiting abnormally; dumping log due to a fatal error ===== BEGIN MILESTONES (/usr/lib/sabayon/sabayon-session) ===== MainThread 2011/11/28 12:56:41.3838 (sabayon-session): Starting session window for profile_name='Kiosk', profile_path='/tmp/profile-sabayon-admin-b8rumk.zip', display_number='1' MainThread 2011/11/28 12:56:41.4251 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'Kiosk', '--admin-log-config=/etc/sabayon/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmpLNFMyg'] MainThread 2011/11/28 12:56:42.2335 (proto-session): Finished running sabayon-apply with normal exit status MainThread 2011/11/28 12:56:42.4045 (sabayon-session): Entering main loop. Wheeee! MainThread 2011/11/28 12:56:42.4077 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop MainThread 2011/11/28 12:56:42.4089 (admin-tool): Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/sabayon/errors.py", line 125, in wrapper return func (*args, **kwargs) File "/usr/lib64/python2.7/site-packages/sabayon/sessionwindow.py", line 330, in __session_mapped self.session.start (str (self.session_widget.session_window.xid)) File "/usr/lib64/python2.7/site-packages/sabayon/protosession.py", line 490, in start self.__start_xephyr (parent_window) File "/usr/lib64/python2.7/site-packages/sabayon/protosession.py", line 326, in __start_xephyr self.xephyr_xauth_file = self.__write_temp_xauth_file (True) File "/usr/lib64/python2.7/site-packages/sabayon/protosession.py", line 283, in __write_temp_xauth_file xauth_data_len) + xauth_data error: 'h' format requires -32768 <= number <= 32767 MainThread 2011/11/28 12:56:42.4154 (sabayon-session): Terminating MainThread 2011/11/28 12:56:42.4155 (sabayon-session): Exiting abnormally; dumping log due to a fatal error ===== END MILESTONES (/usr/lib/sabayon/sabayon-session) ===== ===== BEGIN RING BUFFER (/usr/lib/sabayon/sabayon-session) ===== MainThread 2011/11/28 12:56:41.3838 (sabayon-session): Starting session window for profile_name='Kiosk', profile_path='/tmp/profile-sabayon-admin-b8rumk.zip', display_number='1' MainThread 2011/11/28 12:56:41.4251 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'Kiosk', '--admin-log-config=/etc/sabayon/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmpLNFMyg'] MainThread 2011/11/28 12:56:42.2335 (proto-session): Finished running sabayon-apply with normal exit status MainThread 2011/11/28 12:56:42.4045 (sabayon-session): Entering main loop. Wheeee! MainThread 2011/11/28 12:56:42.4077 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop MainThread 2011/11/28 12:56:42.4089 (admin-tool): Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/sabayon/errors.py", line 125, in wrapper return func (*args, **kwargs) File "/usr/lib64/python2.7/site-packages/sabayon/sessionwindow.py", line 330, in __session_mapped self.session.start (str (self.session_widget.session_window.xid)) File "/usr/lib64/python2.7/site-packages/sabayon/protosession.py", line 490, in start self.__start_xephyr (parent_window) File "/usr/lib64/python2.7/site-packages/sabayon/protosession.py", line 326, in __start_xephyr self.xephyr_xauth_file = self.__write_temp_xauth_file (True) File "/usr/lib64/python2.7/site-packages/sabayon/protosession.py", line 283, in __write_temp_xauth_file xauth_data_len) + xauth_data error: 'h' format requires -32768 <= number <= 32767 MainThread 2011/11/28 12:56:42.4154 (sabayon-session): Terminating MainThread 2011/11/28 12:56:42.4155 (sabayon-session): Exiting abnormally; dumping log due to a fatal error ===== END RING BUFFER (/usr/lib/sabayon/sabayon-session) ===== This configuration for the debug log can be re-created by putting the following in /etc/sabayon/sabayon-debug-log.conf (use ';' to separate domain names): [debug log] max lines = 1000 MainThread 2011/11/28 12:56:42.4996 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1) usermod: Invalid home directory `'. MainThread 2011/11/28 12:56:42.5744 (USER): Finishing editing profile MainThread 2011/11/28 12:56:42.5748 (admin-tool): Terminating main loop MainThread 2011/11/28 12:56:42.5749 (admin-tool): Exiting abnormally; dumping log due to a fatal error Dumped debug log to /root/sabayon-debug-log-2011-11-28-12-56-42.txt -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] BTRFS Warnings
by Sascha Manns 28 Nov '11

28 Nov '11

Hello mates, atm i'm getting messages like that: ov 28 13:40:08 saigkill kernel: [ 159.876060] btrfs: free space inode generation (0) did not match free space cache generation (53938) Nov 28 13:40:08 saigkill kernel: [ 159.876264] btrfs: failed to load free space cache for block group 16806576128 Nov 28 13:40:08 saigkill kernel: [ 159.876428] btrfs: free space inode generation (0) did not match free space cache generation (53805) Nov 28 13:40:08 saigkill kernel: [ 159.876624] btrfs: failed to load free space cache for block group 18551406592 Nov 28 13:40:08 saigkill kernel: [ 159.876807] btrfs: free space inode generation (0) did not match free space cache generation (53944) Nov 28 13:40:08 saigkill kernel: [ 159.877002] btrfs: failed to load free space cache for block group 19625148416 Is that fixable? -- Sincerly yours Sascha Manns Community &Support Agent open-slx GmbH http://www.open-slx.de This mail is written with Balsam Professional 12.1

2 1

[opensuse] How does one activate a service now?
by Carlos E. R. 28 Nov '11

28 Nov '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elanor:~ # chkconfig postfix Note: Forwarding request to 'systemctl is-enabled postfix.service'. disabled postfix off Elanor:~ # chkconfig -s postfix on Elanor:~ # chkconfig postfix Note: Forwarding request to 'systemctl is-enabled postfix.service'. disabled postfix off Elanor:~ # So how do I activate it now? YaST? Or is it another bug? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk7Sy6IACgkQtTMYHG2NR9W92ACghUPgWgpUBBTbY7PA2zYOuNh+ cmgAn2kWFh1Jnx2dHA+th6K7oCn3rkMG =OGGw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 13

[opensuse] kde network plasmoid broken
by lynn 28 Nov '11

28 Nov '11

12.1 I have to give the root password and the wpa password every time I turn on my laptop. click on the plasmoid -> manage connections Choose connection and hit edit A popup appears BEHIND the window (so you have no idea it's there) asking for the root password. A popup appears 'No agents were available for this request' Click OK The Edit network connection window appears. Click on wireless security. The password has been deleted. Reenter the password and it finally connects. You have to do this evert time you boot. What a pain! There is no easy workaround I can find. I see that this was the same in Factory with 12.1 trials. I thought about wicd but it's not easy to install on 12.1. Anyone found a fix? Thanks L x -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 11