November 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] installation report, leap422 on lenovo b70-80
by Per Jessen 27 Nov '16

27 Nov '16

We're looking at upgrading some laptops in the office, and as Toshiba appears to have stopped making laptops, we're looking for a new make. Lenovo's consumer range seems to be good value for money and we don't really need the sturdy/pricey Lenovo Thinkpads. Lenovo B70-80 - after clearing out the Windows stuff and fiddling with the BIOS, the installation over pxe+ssh+http went without a hitch. afaict, all hardware is supported, sound, wifi, all in all it looks good. However - to hit a function key (f1,f2,f3,f4...), you need to press "Fn" and the function key .... closing a window with alt-f4 now becomes a three-key job, switching to a console means pressing four keys .... I think the machine might be going back. -- Per Jessen, Zürich (9.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 50

[opensuse] what's wrong?
by jdd 26 Nov '16

26 Nov '16

Hello, I experiment hard crashes (Leap 42.1) on some circumstances, so I wanted to look at the logs. I get this, it seems that I have no recent journal. How to reset this to normal? thanks jdd # journalctl --list-boots -9 a1f4383d42834c499d7220225a6519aa ven. 2016-07-29 07:52:00 CEST—ven. 2016-07-29 14:03:48 CEST (...) -1 20c1ce44c7ce4b628c5cd410aeb0cb98 dim. 2016-07-31 07:25:08 CEST—dim. 2016-07-31 21:49:21 CEST 0 a382b60f8b1b4866aa5a87cbfd3e54cc lun. 2016-08-01 08:29:53 CEST—lun. 2016-08-01 10:07:04 CEST linux-w4v5:/home/jdd # date sam. nov. 26 10:30:41 CET 2016 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 12

[opensuse] KDE: konsole always starts with mc midnight commander ever since I started mc from the kde start menu
by cagsm 26 Nov '16

26 Nov '16

What happen? I am a noob kde wise and for desktop usage. I just started mc midnight commander from inside an empty konsole as a normal user on a kde desktop. Then eventually exited it via f10 keypress. Whole konsole vanished. I try to fire up a new konsole from kde start menu, be it by entering konsole in the search area or by navigaing recently used apps and such stuff. I never get a normal konsole any more but always populated with a midnight commander inside. What the heck? I hate graphical desktops ;( Thanks for helping. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 20

[opensuse] lenovo b70-80, leap422, intel wireless 3160 not working
by Per Jessen 26 Nov '16

26 Nov '16

continuation of my installation report, specific to the wifi interface not working. The Intel Wireless 3160 device seems to be correctly recognised, firmware is loaded etc. Still, the network does not come up, ifup just reports "device-not-running". I thought perhaps it was a firmware issue and updated to the latest from Kernel:stable, made no difference. I have not had to deal with this sort of thing in a while, I'm not sure where to begin. -- Per Jessen, Zürich (11.2°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 6

[opensuse] zypper dup from 42.1 to 42.2 pulls Mesa on headless VM
by Thomas Wagner 25 Nov '16

25 Nov '16

Hi, I have a headless virtual machine (just apache running and i connect via ssh) with Leap 42.1. Thus no Mesa or X installed. This maschine I wanted to upgrade to Leap 42.2. So, I replaced the 42.1 repos with the repos for 42.2. However, a "zypper dup --no-recommends" tries to pull Mesa with quite some other graphic related libX* and libdrm* packages. I dug around a bit and IMHO python-gobject has now a dependency on all the graphic stuff. On the other hand snapper-zypp-plugin needs python-gobject. Now my question: How to upgrade from 42.1 to 42.2 without installing Mesa but keep snapper? Best regards Thomas -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Leap 42.2: Optimus graphics intel/nvidia; asus touchpad with Skylake...
by Daniel Bauer 25 Nov '16

25 Nov '16

Hell dear listers, I've been away for a while and now see that leap 42.2 has been released. On my leap 42.1 I had some problems using the optimus graphics card (an intel/nvidia mix) which I somehow could resolve using suse-prime. Also the Asus touchpad on a Skylake machine does not work as the kernel doesn't recognize it. My questions: - Does 42.2 support Optimus intel/nvidia now or is suse-prime still needed? If so, will it simply work after a zypper dup to 42.2? - Are the new touchpads now recognized and working; any experiences? - and in general: can I just change the repositories to 42.2 and then run a zypper dup? Or do I have to consider/do some special things? Would you recommend upgrading to 42.2 or would that just be versionitis? Thanks for your input! Daniel -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 6

[opensuse] Toshiba Satellite Laptop & UEFI Secure Boot Fail
by sdm 25 Nov '16

25 Nov '16

I am trying to install Leap 42.2 on a Toshiba Satellite i7 laptop that is a few years old. The only way I can get the 42.2 USB key image I created on my main 42.2 desktop to boot is to shut Secure Boot off in the UEFI firmare on this laptop. If it's enabled I get this error message programmed into the firmware: "Boot failure: A proper digital signature was not found. One of the files on the selected boot device was rejected by the secure boot feature." So essentially I am being forced to use Windows if I want secure boot. If I want to use openSUSE, I have to downgrade the entire security of the machine. Is there any way around this? For years I kept reading about how great UEFI is and how it's the future of booting. But I have dealt with 100-fold more problems helping people (and myself) get out of UEFI booby traps, with crappy vendor UEFI firmware that is buggy and not Linux-friendly, vendor lock-in, bad EFI vars stuck in the firmware that prevent the computer from booting at all, and firmware updates or power loss that clear the NVRAM which then completely wipes out the EFI vars and the system is left unbootable. It that last example, the user would have to run a Linux rescue disk and run a series of commands to re-write the variables back into the nvram. What average user knows how to do that? So we have some additional security at the cost of reliability. I never had any of these issues with BIOS-based PC's, and as soon as UEFI computers hit the market the openSUSE forums lit up with 100's-1000's of people writing in about all types of problems that all were all due to UEFI. It seems to me that all UEFI did is create additonal variables with people's computers that could go awry, and it's bloated and overly complicated to just simply boot a computer. It's an OS to boot the OS. Manufacturers appeared to take whatever UEFI standard that was created and bastardize it. There needs to be a consortium that specifically focuses on actually making manufacturers adhere to the exact UEFI standard if they want to use the UEFI name and logo, and make it so users are not locked into using Windows only. It looks to me that UEFI has taken the same direcion as ACPI. Hardware vendors writing the specs of their hardware to interop with Microsoft's non-standard driver programming. The BIOS standard could have been improved and expanded, and instead of doing that, they threw it away and wrote this bloated kludge standard called "UEFI" that manufacturers don't adhere to more often than not. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

Re: [opensuse] Re: wireless keyboards
by Carlos E. R. 25 Nov '16

25 Nov '16

On 2016-11-25 13:18, Roger Oberholtzer wrote: > In our measurement systems, we use the Veza Wireless Touchpad Keyboard. > It works great. It is USB. It is also nice in that the function keys > work without the need for a key modifier, which the Logitech devices > use. We make great use of the function keys, so this was important to us. Nice one, normal size. I was rather looking at small keyboards, but I'll consider it, thanks :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

1 0

[opensuse] dummy interface disappears after service network restart
by Juan Sierra Pons 24 Nov '16

24 Nov '16

Hi, I have configured a dummy interface that will be used as a bridge member called mgmt0 that can survive server reboots but not service network restart Here you are my config files 1.- To ensure consistent names between reboots /etc/udev/rules.d/71-persistent-mgmt0-net.rules SUBSYSTEM=="net", KERNEL=="dummy0", NAME="mgmt0" 2.- Load the dummy module on system boot /etc/modules-load.d/dummy.conf # Load dummy.ko at boot dummy 3.- To configure the interfaces members of the bridge /etc/sysconfig/network/ifcfg-eth1 STARTMODE='auto' ONBOOT='yes' DEVICE='eth1' BRIDGE='external' BOOTPROTO='none' HOTPLUG='no' /etc/sysconfig/network/ifcfg-mgmt0 STARTMODE='auto' ONBOOT='yes' DEVICE='mgmt0' BRIDGE='external' BOOTPROTO='none' HOTPLUG='no' 4 .- To configure the bridge STARTMODE='auto' ONBOOT='yes' BOOTPROTO='static' BRIDGE='yes' BRIDGE_FORWARDDELAY='0' BRIDGE_PORTS='eth1 mgmt0' BRIDGE_STP='off' IPADDR='X.X.X.X/24' GATEWAY='X.X.X.254' When I reboot the server the interface external gets the IP address: # ifconfig external external Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:X.X.X.X Bcast:136.225.185.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 And the bridge can be seen: # brctl show bridge name bridge id STP enabled interfaces external 8000.5820b1e47ef8 no eth1 mgmt0 The problem appears when service network restart is used as it removes the interface mgmt0 that triggers the problem as if the mgmt0 the bridge external cannot be configured properly PS: Interface and bridge can be restored by removing the dummy module, adding it again and do a ifup external Any idea how to fix/workaround this? Thanks for your time. Juan Sierra Pons -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Fwd: [opensuse] identifying device in dmesg output
by Greg Freemyer 24 Nov '16

24 Nov '16

resend with the list in copy. Sorry about private reply. ---------- Forwarded message ---------- From: Greg Freemyer <greg.freemyer(a)gmail.com> Date: Thu, Nov 24, 2016 at 8:39 AM Subject: [opensuse] identifying device in dmesg output To: John Andersen <jsamyth(a)gmail.com> On Thursday, November 24, 2016, John Andersen <jsamyth(a)gmail.com> wrote: > > On November 23, 2016 9:10:19 PM PST, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > >On Wed, Nov 23, 2016 at 11:13 AM, John Andersen <jsamyth(a)gmail.com> > >wrote: > >> On November 23, 2016 7:49:57 AM PST, Malcolm > ><malcolmlewis(a)cableone.net> wrote: > >>>On Wed 23 Nov 2016 04:42:15 PM CST, Istvan Gabor wrote: > >>> > >>>>Knurpht - Gertjan Lettink írta: > >>>>>Op woensdag 23 november 2016 15:25:24 CET schreef Istvan Gabor: > >>>>>> ata1.00: device reported invalid CHS sector 0 > >>>>> > >>>>>A quick search indicates a drive failure / degrading condition. To > >>>>>find out which entry in /dev is meant by ata1 run > >>>>> > >>>>>ls -l /sys/block/sd* | sed 's/.*\(sd.*\) -.*\(ata.*\)\/h.*/\2 => > >>>>>\1/' > >>>> > >>>>Thanks, running this gives: > >>>> > >>>>ls -l /sys/block/sd* | sed 's/.*\(sd.*\) -.*\(ata.*\)\/h.*/\2 => > >\1/' > >>>>ata1 => sda > >>>>ata3 => sdb > >>>>ata4 => sdc > >>>> > >>>>ls for these devices gives: > >>>> > >>>>ls -gG /sys/block/ > >>>>lrwxrwxrwx 1 0 Nov 23 11:04 sda > >>>>-> > >>>../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda > >>>>lrwxrwxrwx 1 0 Nov 23 11:04 sdb > >>>>-> > >>>../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb > >>>>lrwxrwxrwx 1 0 Nov 23 11:04 sdc > >>>>-> > >>>../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc > >>>> > >>>> > >>>>Here there's no .00 in the names like in the dmesg message. > >>>>What is then ata1.00 exactly? Why is .00 attached to the device name > >>>>in dmesg? What does it mean? > >>>> > >>>>Thanks, > >>>> > >>>>Istvan > >>>> > >>>Hi > >>>The hwinfo --disk command should give you all the info, device files > >>>etc which should help clarify? > >> > >> > >> More to the point he already knows which drive is ata1 and it's time > >to order a new drive. It's failing. > >> > >> Smartctl might show some info, but to what purpose? > >> > >> He needs to start moving that data now. > > > >If smartctl doesn't show historical drive errors, it probably isn't > >the drive. I've had lots of sata cables fail over the years. > >Unreliable communications causes strange error reports. Drive's tend > >to have total failure or bad sectors. > > > >If this is a bad drive, I'd say it's a rare failure mode. > > > >Greg > > Wait, what? > > Drive failure is rare, but cable failure is common? > > Greg, what bizarro world do you live? > > All drives fail. John, I used to be part of the QA team at a end of life PC recycler (I was an outside consultant that did quarterly audits of their process). Used(end of life) PCs were tested and resold. 30,000 PCs a month. If an overall PC failed and wasn't easily repaired the good parts were pulled and stocked for repairs of other PCs. Every drive was wiped with at least a 7 pass wipe. Any that had hardware issues where pulled and run through a mechanical shredder. The 7 pass wipe was done with a Linux boot and shred was invoked by a custom written control program that documented the process. The Linux log files were scanned and if the drive had issues it was tagged for physical destruction. Data security (destruction) was the primary selling feature of this company, and it was my job to ensure no data got through the wiping process. I saw the wiping results and the error reports. In your world, the facility would be buying hard drives to replace all the failed drives coming in the otherwise good computers they were recycling. In mine, they scrapped so many PCs that they had a hard drive stock room with thousands of drives in it that got pulled from the PCs that weren't worth repairing. They sold off excess used hard drive stock. SATA cables they did NOT try to re-use/salvage; simply not reliable enough. If a PC came in with a bad cable, they put in a new one. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0