custom kernel

R

rshad muhammad

uname -aKU
FreeBSD 14.3-STABLE FreeBSD 14.3-STABLE stable/14-730405499ecb MYGEN amd64 1403501 1403501.
I have several conf files in /usr/src. MYGEN, MYG n 14.

I compiled the kernel using this command;
doas make -j $(sysctl -n hw.ncpu) buildkernel KERNCONF=14

Why is it stated MYGEN.

I even did doas make -j $(sysctl -n hw.ncpu) buildworld buildkernel KERNCONF=14
 
cyric said:
That comes from ident keyword, i.e. grep ^ident /sys/amd64/conf/14.
Click to expand...
I corrected the ident n changed MYGEN to 14 n tried compiling again. I received error message about configuration. apparently i need to put an alphabet. I changed from 14 to S14 and the compilation was successful.
My issue now is my swap is disabled. I do not know why. is it due to my configuration.

Host: ThinkPad T14s Gen 1
yo`:. :o `+- Kernel: FreeBSD 14.3-STABLE
y/ -/` -o/ Uptime: 52 mins
.- ::/sy+:. Packages: 695 (pkg)
/ `-- / Shell: sh
`: :` Display (eDP-1): 1920x1080 @ 60 Hz in 14" [Built-in]
`: :` WM: Hyprland (Wayland)
/ / Theme: Fusion [Qt]
.- -. Icons: breeze [Qt]
-- -. Font: Noto Sans (12pt, Regular) [Qt]
`:` `:` Cursor: crystalblue
.-- `--. Terminal: xfce4-terminal 1.1.5
.---.....----. Terminal Font: Hack (12pt, Bold)
CPU: Intel(R) Core(TM) i7-10610U (8) @ 4.90 GHz
GPU: Intel UHD Graphics [Integrated]
Memory: 6.72 GiB / 31.73 GiB (21%)
Swap: Disabled
Disk (/): 16.84 GiB / 193.90 GiB (9%) - zfs
Disk (/zroot): 96.00 KiB / 177.07 GiB (0%) - zfs
Local IP (ue0): 192.168.100.29/24
Battery (5B10W13955): 32% (1 hour, 22 mins remaining) [Discharging]
Locale: en_US.UTF-8
 
Why run developer versions if you expect stability? Keep in mind that both CURRENT as well as STABLE may be fully usable, but there's always an underlying risk of issues popping up.

Anyway.... no offense but just stating "it doesn't work (anymore)!" without providing any other info isn't enough to even provide educated guesses as to what might be going on. For example... is your swap part of your ZFS pool or was it a separate partition? Speaking of said ZFS pool: can that even be used, are the datasets accessible?

I guess it all depends on how much you trimmed down your kernel.

Maybe you did away with da?
 
ShelLuser said:
Why run developer versions if you expect stability? Keep in mind that both CURRENT as well as STABLE may be fully usable, but there's always an underlying risk of issues popping up.

Anyway.... no offense but just stating "it doesn't work (anymore)!" without providing any other info isn't enough to even provide educated guesses as to what might be going on. For example... is your swap part of your ZFS pool or was it a separate partition? Speaking of said ZFS pool: can that even be used, are the datasets accessible?

I guess it all depends on how much you trimmed down your kernel.

Maybe you did away with da?
Click to expand...
is your swap part of your ZFS pool or was it a separate partition?
yes. it was created when i installed freebsd.

are the datasets accessible?
yes, everything is accesible. i could even do poudriere bulk.

Maybe you did away with da?
device scbus # SCSI bus (required for ATA/SCSI)
device ch # SCSI media changers
device da # Direct Access (disks)
device sa # Sequential Access (tape etc)
nodevice cd # CD
device pass # Passthrough device (direct ATA/SCSI access)
device ses # Enclosure Services (SES and SAF-TE)
#device ctl # CAM Target Layer
 
rshad muhammad said:
is your swap part of your ZFS pool or was it a separate partition?
yes. it was created when i installed freebsd.

are the datasets accessible?
yes, everything is accesible. i could even do poudriere bulk.

Maybe you did away with da?
device scbus # SCSI bus (required for ATA/SCSI)
device ch # SCSI media changers
device da # Direct Access (disks)
device sa # Sequential Access (tape etc)
nodevice cd # CD
device pass # Passthrough device (direct ATA/SCSI access)
device ses # Enclosure Services (SES and SAF-TE)
#device ctl # CAM Target Layer
Click to expand...
ShelLuser said:
Why run developer versions if you expect stability? Keep in mind that both CURRENT as well as STABLE may be fully usable, but there's always an underlying risk of issues popping up.

Anyway.... no offense but just stating "it doesn't work (anymore)!" without providing any other info isn't enough to even provide educated guesses as to what might be going on. For example... is your swap part of your ZFS pool or was it a separate partition? Speaking of said ZFS pool: can that even be used, are the datasets accessible?

I guess it all depends on how much you trimmed down your kernel.

Maybe you did away with da?
Click to expand...
Why run developer versions if you expect stability? Keep in mind that both CURRENT as well as STABLE may be fully usable, but there's always an underlying risk of issues popping up.
It is a way for me to help freebsd. To test n report the issue n share with community.
I m not a programmer or developer. I do not know how to report to github or wherever
 
it seems adding
device nda # NVMe direct access devices (aka disks)
options NVME_USE_NVD=1 # Use nvd(4) instead of the CAM nda(4) driver

caused me to lose swap in my case.
 
You must log in or register to reply here.
Back
Top