F5F Stay Refreshed Software Operating Systems Problem with the custom Linux kernel installation.

Problem with the custom Linux kernel installation.

Problem with the custom Linux kernel installation.

Pages (2): 1 2 Next
S
Spidercyber
Senior Member
673
08-14-2016, 02:37 PM
#1
Because of earlier issues, I decided to build my own kernel to test if that would solve the problem. I repeated the process several times but kept encountering errors after running the CPU for two hours. This time I opted for the standard settings provided after configuring menuconfig. I encountered an error with the "make install_modules" command, likely because I hadn't included any modules during compilation. Despite that, the system reported that my bzImage was ready. I was unsure since the image was stored in the x86 directory instead of x86_64—was that normal? After copying the image and updating grub, selecting a custom kernel still only displayed loading text with the cursor stuck. It didn’t advance the boot process, and I heard fans shutting down intermittently. I’m currently using Arch Linux with a custom kernel version 6.8.1 from https://www.kernel.org/. I tried building with 8 threads, saved the default configuration, then ran make install_modules with 8 threads. I realized I probably should have run make as a regular user instead of sudo, which helped it compile successfully. I’m wondering whether I needed to include all my drivers and components during the build.
S
Spidercyber
08-14-2016, 02:37 PM #1

Because of earlier issues, I decided to build my own kernel to test if that would solve the problem. I repeated the process several times but kept encountering errors after running the CPU for two hours. This time I opted for the standard settings provided after configuring menuconfig. I encountered an error with the "make install_modules" command, likely because I hadn't included any modules during compilation. Despite that, the system reported that my bzImage was ready. I was unsure since the image was stored in the x86 directory instead of x86_64—was that normal? After copying the image and updating grub, selecting a custom kernel still only displayed loading text with the cursor stuck. It didn’t advance the boot process, and I heard fans shutting down intermittently. I’m currently using Arch Linux with a custom kernel version 6.8.1 from https://www.kernel.org/. I tried building with 8 threads, saved the default configuration, then ran make install_modules with 8 threads. I realized I probably should have run make as a regular user instead of sudo, which helped it compile successfully. I’m wondering whether I needed to include all my drivers and components during the build.

O
O_L_A_Y
Member
74
08-14-2016, 03:15 PM
#2
This script is a basic make file I wrote for a school assignment. When I run make, it executes server and client commands plus updates the executables with chmod. Underneath, it just compiles two binaries using gcc. You can also use make clean to remove the compiled files. The install command likely moves the binaries to your environment path, which usually requires root privileges. Also, if you compile from source at that link, it’s a standard build without custom kernel changes.

If your computer won’t start, check whether the kernel is placed in the /boot directory.
O
O_L_A_Y
08-14-2016, 03:15 PM #2

This script is a basic make file I wrote for a school assignment. When I run make, it executes server and client commands plus updates the executables with chmod. Underneath, it just compiles two binaries using gcc. You can also use make clean to remove the compiled files. The install command likely moves the binaries to your environment path, which usually requires root privileges. Also, if you compile from source at that link, it’s a standard build without custom kernel changes.

If your computer won’t start, check whether the kernel is placed in the /boot directory.

T
Ticou
Junior Member
36
08-14-2016, 04:16 PM
#3
He followed exactly what he said (without any kernel setup details). Yes, I moved it.
T
Ticou
08-14-2016, 04:16 PM #3

He followed exactly what he said (without any kernel setup details). Yes, I moved it.

I
iiSweeTzz
Posting Freak
862
08-14-2016, 08:51 PM
#4
The kernel likely failed since a required driver module was turned off in the make menu configuration.
I
iiSweeTzz
08-14-2016, 08:51 PM #4

The kernel likely failed since a required driver module was turned off in the make menu configuration.

F
FoxayFella
Member
163
08-16-2016, 04:46 AM
#5
I agree. I think I need to adjust some settings in the configuration.
F
FoxayFella
08-16-2016, 04:46 AM #5

I agree. I think I need to adjust some settings in the configuration.

C
ConDal26
Member
71
08-16-2016, 01:16 PM
#6
be aware the latest kernel might not function flawlessly or start at all. I previously relied on a repository to fetch and install the newest kernel on Ubuntu. The most recent version unexpectedly failed to boot, so I had to enter recovery mode to restore the previous kernel.
C
ConDal26
08-16-2016, 01:16 PM #6

be aware the latest kernel might not function flawlessly or start at all. I previously relied on a repository to fetch and install the newest kernel on Ubuntu. The most recent version unexpectedly failed to boot, so I had to enter recovery mode to restore the previous kernel.

D
duolux1511
Junior Member
10
08-20-2016, 04:12 AM
#7
D
duolux1511
08-20-2016, 04:12 AM #7

L
Loopsip
Member
55
08-20-2016, 07:15 AM
#8
Usually this happens because distro patches are added to the standard source and a few test cases bypassed. I've never seen vanilla sources break when the problem wasn't in the core (often due to PCI devices altering bus addresses between major updates or modular/static kernel settings breaking other configs).
L
Loopsip
08-20-2016, 07:15 AM #8

Usually this happens because distro patches are added to the standard source and a few test cases bypassed. I've never seen vanilla sources break when the problem wasn't in the core (often due to PCI devices altering bus addresses between major updates or modular/static kernel settings breaking other configs).

N
NinNja___
Junior Member
3
08-20-2016, 01:46 PM
#9
You're running version 6.8.1, and it's the same Arch distribution that comes with your default setup.
N
NinNja___
08-20-2016, 01:46 PM #9

You're running version 6.8.1, and it's the same Arch distribution that comes with your default setup.

E
ElitexWizard
Member
210
09-05-2016, 05:33 PM
#10
I corrected my earlier statement. The 6.8.2 kernel is correct; Arch uses 6.8.1 by default isn't standard. Running "lspci -k" shows details about the system, including the Intel Comet Lake-U and its components. The kernel drivers listed are accurate for your setup. Regarding the kernel modules, it depends on what you need. If you're using the correct drivers, you typically don’t need to install every single one unless you encounter specific issues. Check each module individually and see if it resolves your problem.
E
ElitexWizard
09-05-2016, 05:33 PM #10

I corrected my earlier statement. The 6.8.2 kernel is correct; Arch uses 6.8.1 by default isn't standard. Running "lspci -k" shows details about the system, including the Intel Comet Lake-U and its components. The kernel drivers listed are accurate for your setup. Regarding the kernel modules, it depends on what you need. If you're using the correct drivers, you typically don’t need to install every single one unless you encounter specific issues. Check each module individually and see if it resolves your problem.

Pages (2): 1 2 Next