* Doug McGarrett <dmcgarrett@optonline.net> [10-14-20 15:12]:
On 10/12/20 5:10 PM, DennisG wrote:
On 10/12/20 3:19 PM, Carlos E. R. wrote:
On 12/10/2020 20.16, DennisG wrote:
On 10/12/20 1:27 PM, Carlos E. R. wrote:
On 12/10/2020 19.05, DennisG wrote:
On 10/11/20 10:41 PM, Carlos E.R. wrote:
snip
That was my meaning, i.e., because the scanner uses proprietary code installed by a proprietary script, it is vulnerable to kernel updates, including on Leap. OP's scanner situation is analogous to using the compiled (non-repo) version of the nvidia driver which must be re-installed with each kernel update.
I see what you mean.
However, does the scanner software needs to access the kernel?
It is "remote", over the network, so it just need standard network functions to transmit and receive data. The proprietary part would be in the processing of that data, and in sending packages that are commands to the scanner. No need to interface with the computer hardware at all.
Even if the driver uses usb, I suppose the situation would be similar, but maybe less so.
Interesting.
Good question. I don't know. And in all honesty, I don't see any benefit in digging into the Epson installation package again.
IIRC there are 4 rpm's, one of which includes proprietary code under the Seiko license. The dependencies indicate it gets compiled at installation. There is a network component which is required whether or not the device is networked. And there is an end-user management app in there, too.
In any event, checking whether a kernel update is the source of the problem is relatively easy: Boot from the previous kernel; does the scanner now work? Or re-install the software; does the scanner now work? Not foolproof, but seems to me the first things to try. If either of these simple tasks isn't the solution (and which AFAICT, the OP has not tried), OP is probably stuck because it is doubtful anyone can find/unwind which TW update (or something else) it was that borked the device.
--dg I would be happy to try that if I knew how. And the only previous kernel I have is on the install disk--2020-0826, which ought to be early enough, but how do I boot from that and now trigger a complete reinstall? Thanx for your assistance! --doug PS: There is now another update: should I install it?
That you feel the need to ask is evidence you should go back to Leap and alter your machine as little as possible. The questions is impossible for anyone but you to answer and since you do not know the answer, ... Tumbleweed is an ever changing environment which has great system stability but must be administered with understanding and knowledge. The requirements for Leap in that respect are similar but much less. The likelihood of your machine(s) being compromised is(are), or becoming of them becoming unusable is great! -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org