kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: fulwang@linux.vnet.ibm.com
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: How to install kernel modules after a successful compiling
Date: Thu, 10 Dec 2020 10:28:50 +0200	[thread overview]
Message-ID: <CAJ1xhMVvJ_cYnGFFA0PnRq_orvPbDY4k9mxxz-rC4-px1HHVVg@mail.gmail.com> (raw)
In-Reply-To: <08f660b8-570e-5ec1-6aa9-1e40e5e39aec@linux.vnet.ibm.com>

On Thu, Dec 10, 2020 at 9:51 AM FuLong Wang <fulwang@linux.vnet.ibm.com> wrote:
>
>
>
> When I try to install the new built kernel and modules, i found the
> install script will assign the kernel version as "3.10.0".

The kernel version is set via these config options via scripts/setlocalversion:
CONFIG_LOCALVERSION
CONFIG_LOCALVERSION_AUTO

In your setup, CONFIG_LOCALVERSION is probably set to 3.10.0.
If that is the case, try setting CONFIG_LOCALVERSION="" via 'make
menuconfig', and ensure that CONFIG_LOCALVERSION_AUTO is set to 'y'.

>
> Where is this defined?
> Can we keep it as the current kernel version or change it as we want?
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> [zbrand@bz094f linux-3.10.0-957.el7.s390x]$ sudo make install
>    CHK     include/generated/uapi/linux/version.h
>    CHK     include/generated/utsrelease.h
>    CHK     include/generated/qrwlock.h
>    CHK     include/generated/qrwlock_api_smp.h
>    CHK     include/generated/qrwlock_types.h
>    CHK     kernel/qrwlock_gen.c
>    CHK     lib/qrwlock_debug.c
>    CALL    scripts/checksyscalls.sh
>    CC      scripts/mod/devicetable-offsets.s
>    GEN     scripts/mod/devicetable-offsets.h
>    HOSTCC  scripts/mod/file2alias.o
>    HOSTLD  scripts/mod/modpost
>    CHK     include/generated/compile.h
>    SKIPPED include/generated/compile.h
>    CHK     include/generated/uapi/linux/version.h
> sh -x  ./arch/s390/boot/install.sh 3.10.0 arch/s390/boot/bzImage \
>        System.map "/boot"
> + '[' -x /root/bin/installkernel ']'
> + '[' -x /sbin/installkernel ']'
> + exec /sbin/installkernel 3.10.0 arch/s390/boot/bzImage System.map /boot
> [zbrand@bz094f linux-3.10.0-957.el7.s390x]$
> [zbrand@bz094f linux-3.10.0-957.el7.s390x]$
> [zbrand@bz094f linux-3.10.0-957.el7.s390x]$ pwd
> /home/zbrand/rpmbuild/BUILD/kernel-3.10.0-957.el7/linux-3.10.0-957.el7.s390x
> [zbrand@bz094f linux-3.10.0-957.el7.s390x]$
>
>
>
>
> --
> Regards
> FuLong Wang
> _______________________________________________
>
> On 12/10/20 12:25, FuLong Wang wrote:
> >
> > Alexander,
> >
> >
> > Thanks for the reminder!
> >
> >
> > I realized that the new build module is with version "3.10.0" and so not
> > match with my running kernel version "3.10.0-957.el7.s390x".
> >
> > I do confirm that i was using the right kernel source rpm.
> >
> > So, the question turns to why the "make modules" command changed the
> > kernel version of built modules to "3.10.0" instead of
> > "3.10.0-957.el7.s390x".
> >
> >
> > Is there any special steps i need to follow to keep the original kernel
> > naming convention?
> >
> > btw: I'm following below article to compile the kernel modules.
> >
> > https://wiki.centos.org/HowTos/BuildingKernelModules
> >
> >
> > Thanks!
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> >
> > [root@bz094f ~]# modinfo ib_ipoib
> > filename:
> > /lib/modules/3.10.0-957.el7.s390x/kernel/drivers/infiniband/ulp/ipoib/ib_ipoib.ko
> >
> >   license:        Dual BSD/GPL
> >   description:    IP-over-InfiniBand net driver
> >   author:         Roland Dreier
> >   alias:          rtnl-link-ipoib
> >   rhelversion:    7.6
> >   srcversion:     917AA4365B3509F0B347217
> >   depends:        ib_core,ib_cm
> >   intree:         Y
> >   vermagic:       3.10.0 SMP mod_unload modversions
> >   parm:           max_nonsrq_conn_qp:Max number of connected-mode QPs per
> >   interface (applied only if shared receive queue is not available) (int)
> >   parm:           cm_data_debug_level:Enable data path debug tracing for
> >   connected mode if > 0 (int)
> >   parm:           mcast_debug_level:Enable multicast debug tracing if > 0
> >   (int)
> >   parm:           data_debug_level:Enable data path debug tracing if > 0
> > (int)
> >   parm:           send_queue_size:Number of descriptors in send queue (int)
> >   parm:           recv_queue_size:Number of descriptors in receive queue
> > (int)
> >   parm:           ipoib_enhanced:Enable IPoIB enhanced for capable devices
> >   (default = 1) (0-1) (int)
> >   parm:           debug_level:Enable debug tracing if > 0 (int)
> >   [root@bz094f ~]#
> >
> >
> > [root@bz094f ~]# uname -ar
> > Linux bz094f 3.10.0-957.el7.s390x #1 SMP Thu Oct 4 16:53:20 EDT 2018
> > s390x s390x s390x GNU/Linux
> >
> >
> > [root@bz094f ~]# ls -l /home/zbrand/sourcerpm/
> > total 102468
> > -rw-r--r--. 1 zbrand zbrand    257644 Dec  8 13:44
> > asciidoc-8.6.8-5.el7.noarch.rpm
> > -rw-r--r--. 1 zbrand zbrand   1551156 Dec  8 13:45
> > glibc-static-2.17-260.el7.s390x.rpm
> > -rw-r--r--. 1 zbrand zbrand   1307048 Dec  8 14:01
> > graphviz-2.30.1-21.el7.s390x.rpm
> > -rw-r--r--. 1 zbrand zbrand 101028281 Dec  8 13:15
> > kernel-3.10.0-957.el7.src.rpm
> > -rw-r--r--. 1 zbrand zbrand     52620 Dec  8 13:44
> > newt-devel-0.52.15-4.el7.s390x.rpm
> > -rw-r--r--. 1 zbrand zbrand     93176 Dec  8 14:07
> > slang-devel-2.2.4-11.el7.s390x.rpm
> > -rw-r--r--. 1 zbrand zbrand    625688 Dec  8 14:02
> > source-highlight-3.1.6-6.el7.s390x.rpm
> > [root@bz094f ~]#
> >
> >
> >
> >

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2020-12-10  8:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  9:30 How to install kernel modules after a successful compiling FuLong Wang
2020-12-09 15:19 ` Alexander Kapshuk
2020-12-10  4:25   ` FuLong Wang
2020-12-10  7:49     ` FuLong Wang
2020-12-10  8:28       ` Alexander Kapshuk [this message]
2020-12-10 14:18         ` FuLong Wang
2020-12-10 14:44           ` Alexander Kapshuk
2020-12-10 15:02             ` FuLong Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ1xhMVvJ_cYnGFFA0PnRq_orvPbDY4k9mxxz-rC4-px1HHVVg@mail.gmail.com \
    --to=alexander.kapshuk@gmail.com \
    --cc=fulwang@linux.vnet.ibm.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).