You are not logged in.

#1 2022-07-10 19:09:54

aylie
Member
Registered: 2022-07-10
Posts: 30

stuck on “loading initial ramdisk …”

I just installed arch linux, and while i try to boot it says “loading initial ramdisk …” and nothing. I tried installing both linux and linux-lts. No one don’t work. I use grub. Laptop specs:
Core 2 Duo T8100M
Geforce 8600M GT
4GB DDR2
120GB SSD
tried to set loglevel=7 and remove quiet, that doesn’t change anything, i have intel-ucode also. Before reinstalling it i also had fresh arch even without intel-ucode and it didn’t change anything
During this install in arch-chroot i installed xfce4 and xorg
I didn’t changed any display driver’s

Offline

#2 2022-07-10 21:00:05

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

update: it worked once when i activated ahci in bios but after reboot it still stuck (loaded with default linux not ltc)

Offline

#3 2022-07-10 23:00:40

loqs
Member
Registered: 2014-03-06
Posts: 18,603

Re: stuck on “loading initial ramdisk …”

As you can boot the live media successfully,  if you chroot into the installation from the live media is anything record in the journal from the failed boots?  If so please post it to a pastebin.  (URL contains details on how to post from the console to a pastebin)

Offline

#4 2022-07-11 06:37:46

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

mount /dev/sda2
arch-chroot /mnt
journalctl -b-1 | curl -F ‘f:1<-‘ ix.io
http://ix.io/4436

Offline

#5 2022-07-11 07:51:29

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,326

Re: stuck on “loading initial ramdisk …”

You're booting fine

Jul 11 06:31:56 archay systemd[1]: Reached target Graphical Interface.
Jul 11 06:32:24 archay systemd[1]: Stopped target Graphical Interface.

But nouveau doesn't support your HW (mostly because it seems invalid)

Jul 11 06:31:52 archay kernel: nouveau 0000:01:00.0: enabling device (0000 -> 0003)
Jul 11 06:31:52 archay kernel: nouveau 0000:01:00.0: unknown chipset (ffffffff)

Output of

lspci -k

Is "Geforce 8600M GT" the thing from ~2007?
Can you boot "nomodeset" or the multi-user.target (2nd link below)?
Do you try to vfio it?

Make sure you've linux-firmware installed, post the journal from the archiso boot (simply w/o chrooting) and brace yourself for your GPU mght have moved to a renderfarm upstate…

Offline

#6 2022-07-11 15:32:20

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

journal -b in livecd usb: http://0x0.st/o1Kq.txt
That thing with gpu is strange bcz when boot in livecd(usb) it also says nouveau unknown chipset (ffffffff) but i can see it
also when it boots successfully from drive i have my monitor resolution like driver is working
lspci -k : http:/0x0.st/o1KP.txt (in livecd)
Yes Geforce 8600M GT it’s ~2007

Offline

#7 2022-07-11 15:36:45

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

lmao it’s currectly loaded with nouveau in livecd and resolution is fine wth
i made journal of the boot http://0x0.st/o1KQ.txt

Offline

#8 2022-07-11 15:44:37

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

also when i made boot with nomodeset it also stuck
but i made journal from chroot: http://0x0.st/o1K1.txt
forgot to mention that previously (maybe month ago) i had lubuntu at it worked fine

Last edited by aylie (2022-07-11 15:45:42)

Offline

#9 2022-07-11 16:03:31

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,326

Re: stuck on “loading initial ramdisk …”

All posted journals are from the installation iso.

One has

Jul 11 14:51:18 archiso kernel: nouveau 0000:01:00.0: enabling device (0000 -> 0003)
Jul 11 14:51:18 archiso kernel: nouveau 0000:01:00.0: unknown chipset (ffffffff)

The other two have

Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: vgaarb: deactivate vga console
Jul 11 15:24:14 archiso kernel: Console: switching to colour dummy device 80x25
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: NVIDIA G84 (084700a2)
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: bios: version 60.84.42.00.23
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: bios: M0203T not found
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: bios: M0203E not matched!
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: fb: 256 MiB DDR2
Jul 11 15:24:14 archiso kernel: tg3 0000:04:00.0: VPD access failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: VRAM: 256 MiB
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: DCB outp 00: 01000323 00000034
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: DCB outp 01: 02011300 00000028
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: DCB outp 02: 010223f1 0020c070
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: DCB conn 00: 0040
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: DCB conn 01: 0100
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: DCB conn 02: 0210
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: DCB conn 03: 0211
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: MM: using CRYPT for buffer copies
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: failed to create encoder 0/1/0: -19
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: TV-1 has no encoders, removing
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: therm: temperature (89 C) hit the 'fanboost' threshold
Jul 11 15:24:14 archiso kernel: nouveau 0000:01:00.0: DRM: allocated 1280x800 fb: 0x50000, bo (____ptrval____)
Jul 11 15:24:14 archiso kernel: fbcon: nouveaudrmfb (fb0) is primary device

because they're for the exact same boot.

lspci says

01:00.0 VGA compatible controller: NVIDIA Corporation G84M [GeForce 8600M GT] (rev a1)
	Subsystem: COMPAL Electronics Inc Device 0025
	Kernel modules: nouveau

but no "Kernel driver in use"

Was lubuntu w/ nouveau or and aged nvidia blob?

Offline

#10 2022-07-11 16:32:15

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

lubuntu was nouveau
so what that can mean when sometimes it loads nouveau sometimes not
do i need to install nvidia driver?

Offline

#11 2022-07-11 16:47:15

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,326

Re: stuck on “loading initial ramdisk …”

so what that can mean when sometimes it loads nouveau sometimes not

That the chip sometimes responds and sometimes not.
I'd tell you to try the LTS kernel and also use https://wiki.archlinux.org/title/Kernel … _KMS_start but non-deterministic HW behavior is rarely a good sign.

do i need to install nvidia driver?

https://wiki.archlinux.org/title/NVIDIA … ed_drivers
https://aur.archlinux.org/packages/nvidia-340xx-dkms might not work w/ X11 anymore.

Offline

#12 2022-07-11 17:17:57

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

so, in mkinitcpio.conf I already had nouveau in MODULES(nouveau), so i tried to do exact opposite thing and removed it, rebuilt with mkinitcpio -P and… nothing changed
i tried both linux and linux-lts and none of them worked.

Offline

#13 2022-07-11 17:21:41

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

also, yes, when i had the same problems before reinstalling i tried to install nvidia 340 but xfce4 was saying like it couldn’t start

Offline

#14 2022-07-11 18:16:00

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

so, what should i do?
also, i forgot to mention that i also tried syslinux bootloader and it shows me that nouveau chipset unknown

Last edited by aylie (2022-07-11 18:17:17)

Offline

#15 2022-07-11 19:40:31

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,326

Re: stuck on “loading initial ramdisk …”

Please don't bump.
If nobody has responded, edit your previous posts for additional questions/statements.

If you cannot get the GPU to deterministically respond, regardless of the software stack, chances are that it (or something™: could also be a power supply issue) is dying.

If the system is "stuck" despite the GPU respoding, please post such journal.
I'm btw. not sure about

also when i made boot with nomodeset it also stuck

here - unless you're looping to fail starting X11, this should™ not happen.
What is your graphical.target?

Offline

#16 2022-07-12 14:52:38

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

Sorry for long time answer and bumping

graphical.target? If I get question right, it’s xfce4
I will try syslinux when i will be able to reach my laptop then bcz it’s just says nouveau unknown chipset but i see the ui(terminal)

Last edited by aylie (2022-07-12 14:53:24)

Offline

#17 2022-07-12 17:04:09

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,326

Re: stuck on “loading initial ramdisk …”

If I get question right, it’s xfce4

It'll be something like lightdm or gdm or sddm or startx, or … not your GUI session.

Offline

#18 2022-07-13 14:48:01

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

Plan’s changed a lot

I decided to install syslinux + nvidia 340
but I don’t know how to patch it to work on 5.18.10 kernel
Without nouveau it boots normally but in rescue(i thing?)

Offline

#19 2022-07-13 15:19:14

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,326

Re: stuck on “loading initial ramdisk …”

https://aur.archlinux.org/packages/nvidia-340xx-dkms has a patch for 5.18, what's more likely to fail is the X11 driver.
The bootloader won't change much here, the error is from the nouveau kernel module and the nvidia blob will (most likely) tell you that chip has fallen off the bus.

Did you try https://wiki.archlinux.org/title/Kernel … _KMS_start (that's not about syslinux, but about moving the kernel modules into the initramfs!)?
You could also try to pass "pcie_aspm=off" to the kernel, https://wiki.archlinux.org/title/Kernel_parameters

Offline

#20 2022-07-13 18:05:20

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

so, that is happening when i try to patch it
any ideas? i thing it says that something wrong with —strip
https://drive.google.com/file/d/1FtFSze … p=drivesdk
https://drive.google.com/file/d/1-NFx9t … p=drivesdk

Offline

#21 2022-07-13 18:49:33

loqs
Member
Registered: 2014-03-06
Posts: 18,603

Re: stuck on “loading initial ramdisk …”

The prepare function of nvidia-340xx contains the following which applies any file with .patch extension and the source array already contains a patch for 5.18

  local src
  for src in "${source[@]}"; do
    src="${src%%::*}"
    src="${src##*/}"
    [[ $src = 0*.patch ]] || continue
    echo "Applying patch $src..."
    patch -Np1 < "../$src"
  done

So you do not need to change the 340xx PKGBUILD to support 5.18.

Offline

#22 2022-07-13 19:12:16

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

Offline

#23 2022-07-13 19:20:10

loqs
Member
Registered: 2014-03-06
Posts: 18,603

Re: stuck on “loading initial ramdisk …”

Use `makepkg -C` to clean $srcdir and see if that helps.  Please do not post pictures of text.
Edit:
nvidia-340xx-340.108-30-x86_64-prepare.log

Creating directory NVIDIA-Linux-x86_64-340.108-no-compat32
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 340.108...........................................................................................................................................................................................................
Applying patch 0001-kernel-5.7.patch...
patching file kernel/Makefile
patching file kernel/conftest.sh
patching file kernel/dkms.conf
patching file kernel/nv-drm.c
patching file kernel/nv-linux.h
patching file kernel/nv-procfs.c
patching file kernel/nv-time.h
patching file kernel/nv.c
patching file kernel/os-interface.c
patching file kernel/uvm/Makefile
patching file kernel/uvm/conftest.sh
patching file kernel/uvm/nvidia_uvm_lite.c
Applying patch 0002-kernel-5.8.patch...
patching file kernel/nv-linux.h
patching file kernel/nvidia-modules-common.mk
patching file kernel/os-mlock.c
patching file kernel/uvm/nvidia_uvm_lite_api.c
Applying patch 0003-kernel-5.9.patch...
patching file kernel/nv-drm.c
patching file kernel/nv-linux.h
patching file kernel/nv.c
patching file kernel/uvm/nvidia_uvm_linux.h
Applying patch 0004-kernel-5.10.patch...
patching file kernel/nv-drm.c
Hunk #1 succeeded at 364 (offset 42 lines).
Applying patch 0005-kernel-5.11.patch...
patching file kernel/conftest.sh
patching file kernel/nv-drm.c
Hunk #1 succeeded at 59 (offset -1 lines).
Hunk #2 succeeded at 211 (offset -1 lines).
Hunk #3 succeeded at 242 (offset -1 lines).
Hunk #4 succeeded at 278 (offset -1 lines).
Hunk #5 succeeded at 408 (offset -2 lines).
Hunk #6 succeeded at 459 (offset -2 lines).
patching file kernel/nv-linux.h
patching file kernel/uvm/nvidia_uvm_linux.h
Applying patch 0006-kernel-5.14.patch...
patching file kernel/nv-drm.c
patching file kernel/os-interface.c
Applying patch 0007-kernel-5.15.patch...
patching file kernel/nv-drm.c
Hunk #1 succeeded at 606 (offset 77 lines).
Applying patch 0008-kernel-5.16.patch...
patching file kernel/os-interface.h
patching file kernel/nv.h
Applying patch 0009-kernel-5.17.patch...
patching file kernel/conftest.sh
patching file kernel/nv-linux.h
patching file kernel/uvm/conftest.sh
Applying patch 0010-kernel-5.18.patch...
patching file kernel/nv-acpi.c
patching file kernel/nv-dma.c
patching file kernel/nv-drm.c
patching file kernel/nv-vm.c
patching file kernel/nv-frontend.c

Last edited by loqs (2022-07-13 19:30:29)

Offline

#24 2022-07-13 19:46:13

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,326

Re: stuck on “loading initial ramdisk …”

I will stress that nvidia 340xx will most likely not help you - the chip is very likely dying.

Offline

#25 2022-07-13 19:55:09

aylie
Member
Registered: 2022-07-10
Posts: 30

Re: stuck on “loading initial ramdisk …”

http://0x0.st/o1jL.txt
that happens after installing nvidia-340 from arch-chroot
issue is very similar with the grub

also i had this when installed nvidia driver

petaling kerneluv vm.c rate hing lile kernelzny frontend.c -- > Starting build ( ) ... NUIDIA : calling KBUILD ... makel11 : Entering directory ' /usr/lib/modules/5.18.10-arch1-1/build ' test e include / generated / autoconf.h -a -e include / config / auto.conf ii echo > & 2 : echo > & Z " ERROR : Kernel configuration is invalid . " ; echo > & 2 missing . ' echo > & 2 " ; echo > & 2 : / bin / false ) include / generated / autoconf.h or include / config / auto.conf are Run ' make oldconfig && make prepare ' on kernel src to fix it . warning compiler differs from the one used to build the kernel The kernel was built by : gcc ( GCC ) 12.1.0 You are using : cc ( GCC ) 12.1.0 make -f ./scripts/Makefile.build obj = / nvidia / nvidia - 340xx / src / NUIDIA - Linux - x86_6 4-340.108 - no - compat32 / kernel single - build = \ need - builtin - 1 need - modorder = 1

Last edited by aylie (2022-07-13 19:56:48)

Offline

Board footer

Powered by FluxBB