February 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] nouveau/modesetting speed
by mh＠mike.franken.de 28 Feb '17

28 Feb '17

Hi *, is there anything I can do to improve graphics speed (2D and 3D) when using the nouveau driver and the modesetting X server module? At the moment this combination works without too many problems with my graphics adapter, but is way slower than the native nvidia driver and X server module (375.26). My system is openSuSE Leap 42.2 and I tested with the latest kernel 4.10.1 and the latest X server and Mesa packages from http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Leap_42.2/. They are faster than the original combination that came with Leap 42.2, but are still much slower than the nvidia bundle. I don't expect the same speed as with the nvidia driver, but I'd like to do everything to get the most out of nouveau/modesetting. Here is the lspci output for my graphics adapter: 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 8517 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at f6000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at f7000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [258] L1 PM Substates Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Thx and bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] How to repair btrfs (was: Btrfs ...)
by Richard Brown 28 Feb '17

28 Feb '17

On 27 February 2017 at 18:43, Andrei Borzenkov <arvidjaar(a)gmail.com> wrote: > 26.02.2017 14:38, Richard Brown пишет: > > Good. So as you appear to be expert in repairng corrupted btrfs - after > reboot I get "parent transid failed". Without doing anything in between > at all - I just booted and after 10 minutes did "reboot". Of course, > even grub does not load now as it itself is located on btrfs and cannot > read its modules. > > Your suggestion? OK I must not use btrfcsk. What I *must* use now? The below are the steps I would recommend for ANY btrfs issue, smart people reading dmesg or syslog can probably figure out which of these steps they'd need to skip to in order to fix their particular problem. Step 1 - boot to a suitable alternative system, such as a different installation of openSUSE, a liveCD, or an openSUSE installation DVD. The installation DVD for the version of openSUSE you are running is usually the best choice as it will certainly use the same kernel/btrfs version. Step 2 - Go to a suitable console and make sure you do the below as root Step 3 - Try to mount your partition to /mnt, just to confirm it's really broken (eg. "mount /dev/sda1 /mnt") Step 4 - If it mounts - are you sure it's broken? if Yes - run "btrfs scrub start /mnt" to scrub the system, and "btrfs scrub status /mnt" to monitor it Step 5 - If it doesn't mount, try to scrub the device just in case it works (eg. "btrfs scrub start /dev/sda1" and "btrfs scrub status /dev/sda1" to monitor). Try mounting, if yes, you're fixed. Step 6 - If scrubbing is not an option or does not resolve the issue then try "mount -o usebackuproot" instead (eg. "mount -o usebackuproot /dev/sda1 /mnt"). ==Interlude== All of the above steps are considered safe and should make no destructive changes to disk, and have fixed every filesystem issue I've had on btrfs in the last 5 years Full disk issues need a different approach (basically, delete stuff ;)) documented here: https://www.suse.com/documentation/sles-12/stor_admin/data/sect_filesystems… If the above doesn't fix things for you, you can continue with the below steps but the situation is serious enough to justify a bug report, please! == Step 7 - Run "btrfs check <device>" (eg. "btrfs check /dev/sda1"). This isn't going to help, but save the log somewhere, it will be useful for the bug report. Step 8 - Seriously consider running "btrfs restore <device> <somewhere to copy data>" (eg. "btrfs restore /dev/sda1 /mnt/usbdrive"). This won't fix anything but it will scan the filesystem and recover everything it can to the mounted device. This especially useful if your btrfs issues are actually caused by failing hardware and not btrfs fault. Step 9 - Run "btrfs rescue super-recover <device>" (eg. "btrfs rescue super-recover /dev/sda1"). Then try to mount the device normally. If it works, stop going. Step 10 - Run "btrfs rescue zero-log <device>" (eg. "btrfs rescue zero-log /dev/sda1"). Then try to mount the device normally. If it works, stop going. Step 11 - Run "btrfs rescue chunk-recover <device>" (eg. "btrfs rescue chunk-recover /dev/sda1"). This will take a LONG while. Then try to mount the device normally. If it works, stop going. Step 12 - Don't just consider it this time, don't be an idiot, run "btrfs restore <device> <somewhere to copy data>" (eg. "btrfs restore /dev/sda1 /mnt/usbdrive"). Step 13 - Seriously, don't be an idiot, use btrfs restore ==Danger zone= The above tools had a small chance of making unwelcome changes, but now you're in the seriously suicidal territory, do not do the following unless you're prepared to accept the consequences of your choice. == Step 14 - Now, ONLY NOW, try btrfsck aka "btrfs check --repair <device>" (eg. "btrfs check --repair /dev/sda1") There, I'm very confident the above will help you Andrei, and for everyone else, can we please bury the nonsense that btrfs is lacking when it comes to repair and recovery tools? You have scrub which is safe for day to day use, the perfectly safe usebackuproot mount option, and the various "btrfs rescue" commands which are only moderately worrying compared to the practical Russian roulette which is "btrfs check" -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

11 17

[opensuse] zypper switch for ipv4/ipv6 only?
by Per Jessen 28 Feb '17

28 Feb '17

Is there such a switch? I'm running qemu-arm, and although the host system is dual-stack, it seems the arm emulation is ipv4 only. -- Per Jessen, Zürich (11.3°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

2 2

[opensuse] wlan not visible in YaST firewall configuration
by gumb 26 Feb '17

26 Feb '17

Recently did a fresh install of Leap 42.2 on my laptop. Most of the time I only use ethernet with the wi-fi switch disabled, but wi-fi also works fine using Network Manager when I activate it. In YaST Firewall Configuration, under Interfaces, I only see eth0 configured in the External Zone. I'd have expected to see the wi-fi as a separate entry (I'm sure that's how it was in the past under previous OS versions). I've tried activating the wi-fi connection and going back into the Firewall Configuration, and I've tried rebooting with wi-fi activated, but nothing else ever appears there, and there's no facility to add an entry. I began thinking that maybe 'eth0' is just a misleading collective name for any connection, but in my sistemd journal entries I see the line "using default zone 'ext' for interface wlan0". I only know about the basics of firewall configuration in YaST and not how to configure it otherwise. Can I be sure that this is set up correctly, and why is a separate wlan0 entry not visible? gumb -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 5

[opensuse] 
by Felix Miata 26 Feb '17

26 Feb '17

# /etc/fonts/conf.d/30-metric-aliases.conf   I don't want any web page request for unavailable Vista fonts to be substituted by anything other than the configured generic sans-serif. e.g. Calibri should not be aliased to Carlito. I tried to rpm -e google-carlito-fonts so that couldn't happen, but LibreOffice depends on it. The man page for fonts-config doesn't say how to excise specific metric aliases from the default configuration. How is that supposed to be done if the file isn't supposed to be edited? The following is what I want permanently gone from my fonts configuration: <alias binding="same"> <test name="search_metric_aliases"><bool>true</bool></test> <family>Caladea</family> <default> <family>Cambria</family> </default> </alias> <alias binding="same"> <test name="search_metric_aliases"><bool>true</bool></test> <family>Carlito</family> <default> <family>Calibri</family> </default> </alias> Here's the inane CSS declaration that lead to this: font-family: Calibri,Verdana,Arial,Sans-Serif; Calibri, like other Vista fonts, is little more than half the apparent size of Verdana, roughly the same apparent size as the very much smaller looking than Verdana Times New Roman. :-p -- "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

1 0

[opensuse] networkmanager + nfs + resume
by Per Jessen 26 Feb '17

26 Feb '17

Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name. On Leap422 with KDE, how do I get NetworkManager to start early enough or everything to wait until NetworkManager has an active connection? Surely this isn't such an unusual problem? -- Per Jessen, Zürich (7.6°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

8 56

[opensuse] Opensuse Leap 42.4 upgrade PHP 5.5.14 to 5.6
by Otto Rodusek 25 Feb '17

25 Feb '17

Hi, I'm running Opensuse Leap42.2 (kernel 4.4.49-16-default x86_64) and php 5.5.14. Is there an easy way to upgrade to php 5.6 including all the extensions? is there repo that can do this automatically? Thanks. Otto. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] What is needed to play a video in LO Impress in oS?
by Albert, Oszkó 24 Feb '17

24 Feb '17

Hi all, I thought I should ask the question in the subject. I would like to embed some short videos in a presentation in the unfortunately not too far future. But I can't. I read a lot of text and watched youtube videos so I know how to do that. I know not all video formats work, but ogg would work. And still I failed. I use Leap 42.2. with Plasma5. LO version 5.2.3.3. And then I tried it in some distros in Virtualbox. Linux Mint 18 worked out of the box. Ubuntu 16.10 did not work first but suggested and offered to install some additional packages which drew in numerous other packages. And then it worked. But I simply cannot make it work on my main box. What else is needed? How could I fugure it out? Is it a KDE thing (Mint and buntu were not with KDE) or a SUSE thing? Help is welcome Albert

2 1

[opensuse] oSC17 IRC Meeting - Week 3
by Douglas DeMaio 22 Feb '17

22 Feb '17

Hi All, Just a quick update on oSC17. We will have a half hour meeting tonight at 1900 to discuss planning. Last week, the topic of T-Shirt design came up. One design for the T-Shirt was submitted during last weeks meeting - https://goo.gl/photos/ewvVE5ZmB8UqTjxN8 I will start a thread for the T-Shirt design for the conference for those who would like to submit a design. Below are the topics we will discuss tonight and the links to the previous meetings: #topic Status #topic Volunteers / Teams #topic Summits / Events #topic Keynote #topic T-Shirts #topic Gift Bags #topic Videos #topic Ideas #topic Topics for next meeting #topics Links #link Week 1 - https://community.opensuse.org/meetings/opensuse-project/2017/opensuse-proj… #link Week 2 - http://community.opensuse.org/meetings/opensuse-project/2017/opensuse-proje… v/r Doug

3 4

[opensuse] login screen does not appear after booting (still a problem)
by Joseph Comfort 21 Feb '17

21 Feb '17

On Feb. 15, I wrote that I could not reboot a computer that had been updated from v13.2 to v42.2. After communincations, it appeared that I had made a mistake. Now I am not sure I had, because I still have a problem. I successfully got things working on the original computer (#1), not quite sure how. I have a second one (#2) with nearly identical hardware, and did the same upgrade to it. But the console X display does not come up after a reboot. There is a quick flash of a line of 'login', then a blank screen except for a dash on the top line. I can log into #2 from #1 and even get a display (e.g. yast2) on #1. I examined the Xorg.0.log files side-by-side. They are very similar most of the way, but diverge when dealing with KB and mouse lines (different hardware). However, the .xsession-errors-:0 file on #2 has the lines The X11 connection broke: I/O error (code 1) XIO: fatal IO error 17 (File exists) on X server ":0" after 24 requests (24 known processed) with 0 events remaining. The /etc/X11 directories are identical on the two computers. Specs: Motherboard: Gigabyte GA-970A-D3 (v1.1) Bios: Award F7 Graphics card: nVidia GT218 [GeForce 8400 GS, Rev.3] Driver: nouveau, with drm Monitors: Viewsonic VA2431 (#1) and VX2450 (#2), in 1920x1080 mode (from auto mode) I need both computers for students. Thank you for the help. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 11