#Stuck in console when booting with custom vmlinuz and initramfs

25 messages · Page 1 of 1 (latest)

dapper light
#

Recently i managed to install Arch Linux 6.15.7 (running perfectly) and then I want to try to build kernel by myself and boot it. What I have done is below:

  1. git clone [email protected]:archlinux/linux.git ; git checkout -b 6.15.7-arch1 v6.15.7-arch1 (since the current running kernel is 6.15.7-arch1-1)
  2. cd linux ; zcat /proc/config.gz | tee .config; make oldconfig; make all; sudo make modules_install; sudo make install (i copy arch/x86/boot/install.sh to /root/bin/installkernel and change it so that -6.15.7-arch1 can be suffixed to vmlinuz)
  3. cd /boot ; sudo mkinitcpio -k 6.15.7-arch1 -g initramfs-6.15.7-arch1.img (95M , while original initramfs-linux.img only 50M)
  4. sudo grub-mkconfig -o /boot/grub/grub.cfg
  5. reboot

Booting stuck in console, failed to enter graphical login session.[attachment 1]
I enter tty2, ps aux | grep sddm, nothing but /usr/bin/sddm.
the normal boot see [attachment 2]

summer echo
#

Does your old kernel still work?

#

when poking your kernel in the eyes like this it makes good sense to keep backups

dapper light
summer echo
#

That's good

#

In your first pic I don't see an error. Is it just getting stuck?

#

Does this machine have a dedicated gpu?

#

My theory at the moment is that your graphics drivers are disagreeing with your custom kernel

dapper light
#

it just stays there, but i could login tty2 successfully, and manually systemctl start sddm also can't pull up gui login session. it has a nvidia card on this machine. with regard to "custom", actually i don't change anything just clone official github repo and checkout v6.15.7-arch1 branch, the .config comes from /proc/config.gz in the running system. IIUC, my "custom" kernel is basically the same thing with currently running one, isn't it?

summer echo
#

sddm dying really does suggest graphics issues

#

The kernel and kernel modules and drivers all need to agree on their versions and symbols. Typically the easiest way to do this is to upgrade them in lockstep

#

I suspect pacman -S <your drivers> would resolve this

#

However I also suspect that doing that might break the drivers for the other kernel

#

Yeah I think I'm right - you're building 6.15.7.arch1 when the arch kernel on the repos is 6.15.7.arch1-1

#

May also need to change the /usr/src/linux symlink to point to your custom sources as I believe pacman checks there for the kernel sources to build the drivers against

dapper light
#

I thought .arch1-1 and .arch1 shares the source code, just separate builds

summer echo
#

I might be completely wrong, that's how I understand it though

#

does systemctl status sddm say anything after it has failed?

#

or journalctl -u sddm.service for the whole log

dapper light
#

i will give a try later, thanks

dapper light
summer echo
dapper light
#

@summer echo thanks for pointing it out. i think u are right. if i pacman -Rs nvidia and regenerate initramfs-linux.img, boot with original 6.15.7-arch1-1, it has the same issue. and i noticed that there are nvidia.ko.zst things in /lib/modules/6.15.7-arch1-1/extramodules. while there's no such things in /lib/modules/6.15.7-arch1. but i have no idea how to install nvidia driver in particular to /lib/modules/6.15.7-arch1, also i'm not sure if there is corresponding nvidia driver packages for this custom kernel at all.

mossy flintBOT
#

mushroom.botherer received a thank you cookie!