February 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] A hopefully stupid hardware question - power led?
by Greg Freemyer 02 Mar '17

02 Mar '17

All, I've got a PC that has power-on LED around the power button. I swear it used to be on when the PC was on and off when it was off. Now it seems the LED is almost always off (and maybe it is always off). Most of the time I don't care, but if I'm shutting down for some reason, I can't always tell when power down is done. Is there a bios setting to control that on some MBs? I just realized it could be the connector came loose. I don't recall when I last saw the light on. It's not something I look at most of the time, even though I sit 3 feet from it. fyi: AsRock X99 Extreme4 is my MB. Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] Very basic dd question
by Stevens 01 Mar '17

01 Mar '17

I ask this kinda stupid question only because I really don't want to experiment with my only running computer. A friend has a bunch of very old Windows crap and wanted to know if I could "clone" a couple of his drives so he gave me 2 good drives and several "target" drives - all laptop ide, I think - anyway, I have one usb adapter that I can use, so the question is will the following work to clone a drive? dd if= /dev/sdb (the usb drive) of=/user/[my user home]/temp/bck If so, what would I need to tell it to make a bootable clone? Just reverse the commands? The drive is 540MB so space isn't an issue... And yes, disk partitioning software does see the usb drive and when it is plugged in the system allows me to open it in Dolphin. Thanks, Fred -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 19

[opensuse] Leap 42.2 - missing uucp package
by mh＠mike.franken.de 01 Mar '17

01 Mar '17

Hi *, is there any reason why Taylor uucp is no longer part of Leap 42.2, while Leap 42.1 contained it? I rely heavily on uucp, *because* it is an ancient protocol and nearly nobody (especially hackers) cares about it. Would be great, if someone could include it in Leap 42.2. TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] HP printer Leap 42.2
by michael norman 01 Mar '17

01 Mar '17

My HP D2300 usb printer has worked for many years. It is attached to one of my two pcs and shared between the two. This worked fine up to 13.2 but I cannot get 42.2 to share the printer. Sharing fails in Yast whereas it worked up to 13.2, when I try to sahre it using the CUPS interface I am not offered adminstrator settings (I always used my root password for this hitherto) so cannot change the settings to share the printer. All of this works on Linux Mint 18.1 fwiw. Is there a known fix for this ? M -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 35

[opensuse] Leap 42.2 - xf86-video-intel - plasmashell freezing on notifications
by mh＠mike.franken.de 28 Feb '17

28 Feb '17

Hi *, after a few months the problem still exists, even with the latest kernel, the latest X server and Mesa packages and the latest KDE Frameworks5 packages. So I dare to ask again: On one of my machines (Lenovo T420 notebook) I have a problem with plasmashell freezing often when a notification is shown. The notification frame shows up, but no content and then the complete desktop freezes. Killing and restarting plasmashell cures the problem for a short time - til one of the the next notifications wants to display something. It doesn't happen for all notifications, though. Using tools like notify-send the problem can not be reproduced, but notifications stemming from plasma-nm and plasma-workspace itself (like the one for a removed plasmoid) always lead to the freeze. The system originally was openSuSE Leap 42.2, but because of the problem I upgraded step by step to - the latest kernel from the kernel stable repo, - the latest X server plus everyting from the X11:Xorg repo - and the latest plasma workspace including everything from the KDE:Framework5 repo. The problem remained unchanged, though. A few more facts: - The X server is xf86-video-intel. - Switching to the modesetting driver doesn't help. - Switching off the compositor doesn't help either. - Everything worked with Leap 42.1 - No according entry in the journal or .xsession-errors* can be found. - Logging off or restarting the machine doesn't help in case the problems exists at that time. - *Switching off notifications completely cures the problem.* In found a few bug reports for plasma freezes, but none of them seems to fit exactly. Can I debug it and if so, how? TIA. 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

[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