kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bracht Laumann Jespersen <t@laumann.xyz>
To: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
Cc: Dhaval Giani <dhaval.giani@gmail.com>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Kernel Compile Issue
Date: Thu, 24 Jun 2021 19:29:23 +0200	[thread overview]
Message-ID: <20210624172923.m4qgx7dkwsnhqfol@zillasnegl> (raw)
In-Reply-To: <CAFSeFg95O+uSOLo8Mkoixdq3w0fc13cHa8O-TkZqxGAgkV5Pdg@mail.gmail.com>

> Yes,  I was getting that error when running "sudo make install". I
> have manually removed
> all instances of VirtualBox and any guest additions and that warning
> went away.

Interesting...

> When I select the new
> kernel it goes through all the usual steps of booting then hangs at
> the graphical login screen where
> I no longer have a mouse and Ctrl+Alt+F1 does not work either .

Is there a way you could increase the kernel log level to debug, and capture the
logs during boot? That might be informative.

> I have given below the output of: sudo time make install 2>&1 | tee
> make_install.txt
> 
> ==============================================================
> sh ./arch/x86/boot/install.sh 3.18.2-testing arch/x86/boot/bzImage \
>     System.map "/boot"
> run-parts: executing /etc/kernel/postinst.d/apt-auto-removal
> 3.18.2-testing /boot/vmlinuz-3.18.2-testing
> run-parts: executing /etc/kernel/postinst.d/initramfs-tools
> 3.18.2-testing /boot/vmlinuz-3.18.2-testing
> update-initramfs: Generating /boot/initrd.img-3.18.2-testing
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for
> module r8169
> run-parts: executing /etc/kernel/postinst.d/zz-update-grub
> 3.18.2-testing /boot/vmlinuz-3.18.2-testing
> Generating grub configuration file ...
> Found background image: /usr/share/images/desktop-base/desktop-grub.png
> Found linux image: /boot/vmlinuz-3.18.2-testing
> Found initrd image: /boot/initrd.img-3.18.2-testing
> Found linux image: /boot/vmlinuz-3.18.2-testing.old
> Found initrd image: /boot/initrd.img-3.18.2-testing
> Found linux image: /boot/vmlinuz-3.16.0-4-amd64
> Found initrd image: /boot/initrd.img-3.16.0-4-amd64
> Found memtest86+ image: /boot/memtest86+.bin
> Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
> Found Windows 7 (loader) on /dev/sda1
> Found Ubuntu 12.04.5 LTS (12.04) on /dev/sdb1
> Found Debian GNU/Linux (6.0.5) on /dev/sdb3
> Found Debian GNU/Linux (8.0) on /dev/sdb5
> Found Ubuntu 14.04.3 LTS (14.04) on /dev/sdb6
> done
> 1.33user 0.71system 0:29.75elapsed 6%CPU (0avgtext+0avgdata 16520maxresident)k
> 251456inputs+74824outputs (52major+1632571minor)pagefaults 0swaps
> 
> ==============================================================
> 
> Like I said I have a lot of old kernels lying around this box :-)

And Windowses :-) But nothing looks particularly erroneous about the output.

> The contents of the Makefile in ./arch/x86/include at line 167:
> 
> 166 - # prevent gcc from generating any FP code by mistake
> 167 - KBUILD_CFLAGS += -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
> 168 - KBUILD_CFLAGS += $(call cc-option,-mno-avx,)

Interesting, I see no mention of "Makefile.normal" here. But maybe that's
because you removed whatever required it?

> You have pointed me in the right direction so thank you. Ten plus years
> I have been dabbling with Linux and I just learnt something new. I had no idea
> about this:
> 
> aruna@debian:/media/aruna/kernel-stuff/linux-3.18.2$ ls -alh
> /etc/kernel/postinst.d
> total 20K
> drwxr-xr-x 2 root root 4.0K Jun 23 06:18 .
> drwxr-xr-x 7 root root 4.0K Mar 31 00:45 ..
> -rwxr-xr-x 1 root root 2.8K Apr 13  2015 apt-auto-removal
> -rwxr-xr-x 1 root root  858 Mar  1  2015 initramfs-tools
> -rwxr-xr-x 1 root root  641 Dec 14  2015 zz-update-grub
> 
> Thank you Thomas I will keep trying to fix the no mouse issue now.

No problem, I wasn't sure if I was helping :-)

-- Thomas

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

  parent reply	other threads:[~2021-06-24 17:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23  2:48 Kernel Compile Issue Aruna Hewapathirane
2021-06-24 10:21 ` Thomas Bracht Laumann Jespersen
2021-06-24 13:35   ` Aruna Hewapathirane
2021-06-24 16:13     ` Cindy Sue Causey
2021-06-24 17:56       ` Aruna Hewapathirane
2021-06-24 17:29     ` Thomas Bracht Laumann Jespersen [this message]
2021-06-24 18:19       ` Aruna Hewapathirane
2021-06-24 23:09         ` Valdis Klētnieks
2021-06-24 23:36           ` Aruna Hewapathirane
2021-06-25  0:51             ` Valdis Klētnieks
2021-06-25 20:05               ` Aruna Hewapathirane
2021-06-26  6:39                 ` Valdis Klētnieks
2021-06-28 11:58                   ` Aruna Hewapathirane
2021-06-29  9:25                     ` Thomas Bracht Laumann Jespersen

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=20210624172923.m4qgx7dkwsnhqfol@zillasnegl \
    --to=t@laumann.xyz \
    --cc=aruna.hewapathirane@gmail.com \
    --cc=dhaval.giani@gmail.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).