Hello,
I'm so sorry. > ALL
In the Message;
Subject : Re: [opensuse] mkiss kernel module missing
Message-ID : <87r1w4wfak.wl-nomiya@galaxy.dti.ne.jp>
Date & Time: Fri, 01 May 2020 11:38:11 +0900
[MN] == Masaru Nomiya has written:
MN> Hello,
MN> In the Message;
MN> Subject : Re: [opensuse] mkiss kernel module missing
MN> Message-ID : <8275726.tdObdPNiu0@knurpht-hp>
MN> Date & Time: Fri, 01 May 2020 01:34:58 +0200
MN> [GL] == Knurpht-openSUSE has written:
[...]
MN> The messase;
MN> [...]
MN> suserelease: openSUSE Tumbleweed
MN> [...]
MN> might give you a clue.
with seeing this mail;
In the Message;
Subject : Re: [opensuse] mkiss kernel module missing
Message-ID : <2288717.QIW0atoefT@knurpht-hp>
Date & Time: Fri, 01 May 2020 06:24:59 +0200
[Gl] == Knurpht-openSUSE has written:
[...]
Gl> > > I know, so I have to explain him how to clone the existing config, then
Gl> > > how to modify the correct setting for what he needs, and how to make it
Gl> > > all. Not trivial.
Gl> > >
Gl> > > (assuming the module builds and was not removed intentionally)
Gl> > Which would leave Marc with a sytem that can no way be upgraded to 15.2
Gl> > without a lot of manual interference. Why not deal with defaults and really
Gl> > fix things?
Gl> > From what I read - following the list - almost every one of you is running a
Gl> > modified system. How would packagers, realease people ever be able to deal
Gl> > with that? No one f.e. will create an openQA test for upgrading a 15.1
Gl> > install with a 15.2 kernel.
I downloaded and checked the openSUSE Leap 15.1's original kernel
(4.12.14), and recognized that the it doesn't include the mkiss's
driver.
So, I wrote a script for the mkiss's driver, and attach it.
Then try as follows;
1.
$ gunzip mkissbuild.sh.gz
2.
$ sh ./mkissbuild.sh
Please confirm if insmod ends successfully, or not.
If there exists a problem, let me know.
Good Luck.
Regards,
---
┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp
┃\/彡
┗━━┛ Think.
-- The IBM slogan --