November 2016 - openSUSE Users - openSUSE Mailing Lists

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

[opensuse] Monitoring WiFi
by Koenraad Lelong 24 Nov '16

24 Nov '16

Hi, It's a bit off-topic, but I don't know where else to ask, so I try here ;-) I would like to monitor some WiFi-networks. With that I mean, check if I can associate with the SSID and get an ip-address. If that works, all is good, and dis-associate. If it fails send an alert (email) and/or log it (e.g. cacti). Try again some time later. etc., ad infinitum ;-) To do this I would need some device like a raspberry pi with a LAN (to send alerts) and a WiFi interface. Is there software that does this ? TIA, Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 7

[opensuse] identifying device in dmesg output
by Istvan Gabor 24 Nov '16

24 Nov '16

Hello: Occasionally I experience long, 40-50 secs hangup in my openSUSE 13.1 system. Following such hangup dmesg output contains the following lines at the end: [ 6537.719073] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 6537.719079] ata1.00: failed command: FLUSH CACHE EXT [ 6537.719085] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 6537.719096] ata1.00: status: { DRDY } [ 6537.719101] ata1: hard resetting link [ 6538.025944] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 6538.028155] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.028162] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030462] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.030467] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030558] ata1.00: configured for UDMA/133 [ 6538.030561] ata1.00: retrying FLUSH 0xea Emask 0x4 [ 6538.030599] ata1.00: device reported invalid CHS sector 0 [ 6538.030609] ata1: EH complete [ 6538.269793] show_signal_msg: 81 callbacks suppressed [ 6538.269798] plugin-containe[5320]: segfault at 0 ip 00007f8119a9a785 sp 00007f810e691a30 error 4 in libflashplayer.so[7f8119792000+1193000] Either one of the disks is bad or the motherboard has problem. How can I identify which disk is, or which SATA link/connector is the indicated ata1.00 device? What is/are the exact meaning of the above dmesg error messages? Thanks in advance, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 11

Re: [opensuse] Canon CanoScan LiDe 210 scanner
by stakanov＠freenet.de 23 Nov '16

23 Nov '16

> -----Ursprüngliche Nachricht----- > Von: Albert Oszkó > Gesendet: Mi. 23.11.2016 18:37 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Canon CanoScan LiDe 210 scanner > > 2016-11-22 22:22 keltezéssel, stakanov(a)freenet.de írta: >> >>> -----Ursprüngliche Nachricht----- >>> Von: Albert Oszkó >>> Gesendet: Di. 22.11.2016 19:25 >>> An: opensuse(a)opensuse.org >>> Betreff: Re: [opensuse] Canon CanoScan LiDe 210 scanner >>> >>> 2016-11-22 17:51 keltezéssel, stakanov(a)freenet.de írta: >>>>> -----Ursprüngliche Nachricht----- >>>>> Von: Albert Oszkó >>>>> Gesendet: Di. 22.11.2016 16:06 >>>>> An: suse , >>>>> Betreff: [opensuse] Canon CanoScan LiDe 210 scanner >>>>> >>>>> Hi all, >>>>> >>>>> The above mentioned USB scanner used to work - except the buttons on it >>>>> - up to oS 13.2. SDB says it is fully compatible using genesys driver -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] Canon CanoScan LiDe 210 scanner
by stakanov＠freenet.de 23 Nov '16

23 Nov '16

> -----Ursprüngliche Nachricht----- > Von: Albert Oszkó > Gesendet: Mi. 23.11.2016 18:37 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Canon CanoScan LiDe 210 scanner > > 2016-11-22 22:22 keltezéssel, stakanov(a)freenet.de írta: >> >>> -----Ursprüngliche Nachricht----- >>> Von: Albert Oszkó >>> Gesendet: Di. 22.11.2016 19:25 >>> An: opensuse(a)opensuse.org >>> Betreff: Re: [opensuse] Canon CanoScan LiDe 210 scanner >>> >>> 2016-11-22 17:51 keltezéssel, stakanov(a)freenet.de írta: >>>>> -----Ursprüngliche Nachricht----- >>>>> Von: Albert Oszkó >>>>> Gesendet: Di. 22.11.2016 16:06 >>>>> An: suse , >>>>> Betreff: [opensuse] Canon CanoScan LiDe 210 scanner >>>>> >>>>> Hi all, >>>>> >>>>> The above mentioned USB scanner used to work - except the buttons on it >>>>> - up to oS 13.2. SDB says it is fully compatible using genesys driver -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] Canon CanoScan LiDe 210 scanner
by stakanov＠freenet.de 23 Nov '16

23 Nov '16

> -----Ursprüngliche Nachricht----- > Von: Albert Oszkó > Gesendet: Di. 22.11.2016 19:25 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Canon CanoScan LiDe 210 scanner > > 2016-11-22 17:51 keltezéssel, stakanov(a)freenet.de írta: >> >>> -----Ursprüngliche Nachricht----- >>> Von: Albert Oszkó >>> Gesendet: Di. 22.11.2016 16:06 >>> An: suse , >>> Betreff: [opensuse] Canon CanoScan LiDe 210 scanner >>> >>> Hi all, >>> >>> The above mentioned USB scanner used to work - except the buttons on it >>> - up to oS 13.2. SDB says it is fully compatible using genesys driver. >>> Canon says it is not supported at all on linuxes. I could not make it >>> work on any of the Leap systems. The hardware is correctly recognized, >>> but neither Skanlite, nor Xsane work, only an invalid argument message >>> and frightening noise from the scanner are returned. >>> Interestingly, Debian 8 and Win7 virtual machines have no problems with >>> it. So I suspect the kernel 4.x has some problem with it. Am I right? >>> >>> Can you suggest some workaround? >>> >>> Thanks, Albert >>> >>> >>> >>> -----Ursprüngliche Nachricht Ende----- >> Hi Albert. >> By coincidence I own this scanner "Canon Light 210". >> It worked perfectly with 42.1 original kernel and as well with the 4.4 kernel from kernel stable. >> I employ the 4.4 because of a wlan problem with the 4.1 and the Lenovo X201, not because of the scanner. >> Could you check (sorry for naming stupid things: >> lsusb on the command line an put the output here? >> Then: >> - is the scanner unlocked (we sometimes do not see the obvious) >> - try to change from usb hub to direct if you use one. >> - try to change usb port >> - try to change cable. >> >> Curious on your lsusb. >> >> >> >> >> --- >> Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im >https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! >> >> > Thanks for the tips. > > lsusb gives: > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 004: ID 8087:0a2a Intel Corp. > Bus 001 Device 003: ID 0bda:57ed Realtek Semiconductor Corp. > Bus 001 Device 017: ID 04a9:190a Canon, Inc. CanoScan LiDE 210 > Bus 001 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) > NetScroll+ Mini Traveler / Genius NetScroll 120 > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > The scanner is directly connected to an Asus K501UX laptop. It has > 2xusb2 and 2xusb3 slots. I tried all of them with the same result. I > cannot change cable since this is the only data&supply cable I have. But > as I mentioned virtual machines can use the scanner. What do you mean by > unlocking the scanner? In the meantime I also tried Ubuntu 16.10 and > Linux Mint 18 in virtual machine, the latter have newer kernel than > Debian. All have simple scan, and all worked fine. So it is not a kernel > 4.x problem finally. Unfortunately I do not have TW any more to test an > oS version. > > (BTW I also had probelms with kernel 4.1.x in Leap 42.1. Not only > because of toucpad - I could live without it, but with wlan and also > with sleep/hibernate and also with logout/reboot/shutdown. They > practcially did not work normally) > > Albert > > > > -----Ursprüngliche Nachricht Ende----- So, unlock meant the mechanical lock on the backside, so disregard. As it works in other linux o.K. To be sure: You branched the scanner (and it is seen by lsusb) You went to yast and went to hardware submenu, choose scanner and did configure the scanner? It is seen there. Then you were trying to scan with scanlite and it did not work. Did you try other software for scan than scanlite and which version of scanlite do you have installed (from what vendor / repo?) Did you by any chance have a special repo activated for OCR software from buildservice? This will install some libraries that may not work. If not go following repo for 42.1 (if you do not want to install 42.2 right away) and install the kernel from kernel stable. That should work in every case (as it works here with the very same setup). --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] kwin_x11 causing full cpu load
by cagsm 23 Nov '16

23 Nov '16

Some hours ago there were some leap 42.2 updates for some kde or graphics stuff. I think I remote ssh'd into the machine and zypper ref zypper up and eventually saw some cpu load via top After the zypper up zypper ps showed lot of graphics stuff from the real running machine, so I systemctl restart displaymanager.service or its real name. After that top showed those cpu lod of kwin_x11 106% cpu load it printed out On the whole internet I have seen endless discussions at fedora and also other places but even dating back as far as 2009 or earlier about kwin_x11 and cpu trouble What gives? :( Thank you -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] [opensuse-kde] kdm added to minimal X 42.2 installs 67 packages, requires gstreamer&&&
by Felix Miata 23 Nov '16

23 Nov '16

That seems like an awful lot of stuff just to get a greeter that's fully configurable. Are these really _required_ of a login-manager/greeter?: sound (gstreamer, gstreamer-plugins-base, libpuls*) spell checker (hunspell, libaspell15) PIM support (libakonadi*) activities (libkactivities6) libQtWebKit4 ??? -- "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

2 1

re: [opensuse] Canon CanoScan LiDe 210 scanner
by stakanov＠freenet.de 22 Nov '16

22 Nov '16

> -----Ursprüngliche Nachricht----- > Von: Albert Oszkó > Gesendet: Di. 22.11.2016 16:06 > An: suse , > Betreff: [opensuse] Canon CanoScan LiDe 210 scanner > > Hi all, > > The above mentioned USB scanner used to work - except the buttons on it > - up to oS 13.2. SDB says it is fully compatible using genesys driver. > Canon says it is not supported at all on linuxes. I could not make it > work on any of the Leap systems. The hardware is correctly recognized, > but neither Skanlite, nor Xsane work, only an invalid argument message > and frightening noise from the scanner are returned. > Interestingly, Debian 8 and Win7 virtual machines have no problems with > it. So I suspect the kernel 4.x has some problem with it. Am I right? > > Can you suggest some workaround? > > Thanks, Albert > > > > -----Ursprüngliche Nachricht Ende----- Hi Albert. By coincidence I own this scanner "Canon Light 210". It worked perfectly with 42.1 original kernel and as well with the 4.4 kernel from kernel stable. I employ the 4.4 because of a wlan problem with the 4.1 and the Lenovo X201, not because of the scanner. Could you check (sorry for naming stupid things: lsusb on the command line an put the output here? Then: - is the scanner unlocked (we sometimes do not see the obvious) - try to change from usb hub to direct if you use one. - try to change usb port - try to change cable. Curious on your lsusb. --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Canon CanoScan LiDe 210 scanner
by Albert Oszkó 22 Nov '16

22 Nov '16

Hi all, The above mentioned USB scanner used to work - except the buttons on it - up to oS 13.2. SDB says it is fully compatible using genesys driver. Canon says it is not supported at all on linuxes. I could not make it work on any of the Leap systems. The hardware is correctly recognized, but neither Skanlite, nor Xsane work, only an invalid argument message and frightening noise from the scanner are returned. Interestingly, Debian 8 and Win7 virtual machines have no problems with it. So I suspect the kernel 4.x has some problem with it. Am I right? Can you suggest some workaround? Thanks, Albert

1 0