Frozen at boot - Loading initial ramdisk

I have a system76 laptop recently purchased. i7-10875H, 32 GB ram, 1TB NVMe SSD. Originally came with Pop OS. When I installed Garuda I left it there and went dual boot. I shrunk the drive to approximately 300 Gigs and left the rest for Garuda. No errors during install after reboot the screen came up to Loading initial ramdisk and just sits there. Reinstalled, instead of rebooting I stayed in the program and updated and loaded drivers and looked around some then I went to reboot again and still coming up to Loading initial ramdisk. As I was going to post this I turned it back on to get the error message again and it actually booted correctly. I shut it down and rebooted and now it only goes to frozen at loading initial ramdisk. So it only booted correctly once and I did nothing different that I can think of. Kind if hoping you can help me because I kind of like it but I am a Linux beginner at best.

Connect to charger and try to start
It happens that when on battery some laptops with nvidia wont boot up

1 Like

It's been plugged in the entire time. I went back and started from the other Garuda boot option (sorry I'm not at that screen and since you're answering real time this is what's up) and it flashed that ramdisk portion and now it's stuck at this screen.

So ... I rebooted and it just keeps freezing at that loading ramdisk. You mentioned plugging it in and it was so I unplugged it and it booted?!??? Which makes no logical sense to me whatsoever and I don't know if it's just random. Like I said, I really like what you guys have done with this build and really hope I get to use it as my driver driver.

The final part of this while post is that it keeps freezing. It boots maybe 1 every 10 or more times that I try to boot up.

So that's it? Just problems with Nvidia drivers and too bad for me? Part of the reason I bought this laptop was because of the Nvidia gpu I guess if I have to switch back to pop os I will. :frowning:

So Nvidia creates different drivers for Debian than for Arch? :thinking:, interesting.

Time to post your specs. You don't read

Post

inxi -Fxxxza

as text, please.

If inital means install, you must boot with free drivers, after installation you can install Nvidia v: 4.6.0 NVIDIA 460.39

1 Like

Ok, apologies but like I started with... "Linux beginner at best."

I don't know what you mean by that?? those are the words that are on my screen, "loading initial ramdisk"

I have no idea how to do that.

I'm once again sorry for my ignorance but I just don't know these things. I'm smart I swear to god and I learn fast and go ahead and laugh at me but I thought the OS creator wrote the driver for whatever hardware or that there was a different driver for every os for a thing. Like I said, laugh if you want but I take it from the context of what you said that a linux driver is a linux driver is.... Thank you because now I know.

I do, I'm just new to this. I appreciate your patience you really have an amazing product with Garuda and I'd like to use it as my main OS.

inxi -Fxxxza: PrivateBin

Sorry, I do not laugh, I am not a natural English speaker, so sorry about.
The bin expired in 6 days so I post here

 ╭─[email protected] in ~ 
 ╰λ inxi -Fxxxza
System:
  Kernel: 5.10.14-119-tkg-bmq x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: intel_pstate=passive 
  BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq 
  root=UUID=df46ed4e-57ee-4c94-96af-4e3bb1a3aa13 rw [email protected] 
  quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 
  systemd.unified_cgroup_hierarchy=1 loglevel=3 
  Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 
  dm: SDDM Distro: Garuda Linux 
Machine:
  Type: Laptop System: System76 product: Oryx Pro v: oryp6 
  serial: <filter> Chassis: type: 9 serial: <filter> 
  Mobo: System76 model: Oryx Pro v: oryp6 serial: <filter> UEFI: coreboot 
  v: 2021-01-19_d6d37c0 date: 01/19/2021 
Battery:
  ID-1: BAT0 charge: 74.3 Wh condition: 74.4/70.7 Wh (105%) 
  volts: 13.0/11.4 model: Notebook BAT type: Li-ion serial: <filter> 
  status: Unknown 
  Device-1: hidpp_battery_2 model: Logitech Wireless Mouse MX Master 
  serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
  status: Discharging 
CPU:
  Info: 8-Core model: Intel Core i7-10875H bits: 64 type: MT MCP 
  arch: Comet Lake family: 6 model-id: A5 (165) stepping: 2 microcode: E0 
  L2 cache: 16 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 73664 
  Speed: 4154 MHz min/max: 800/5100 MHz Core speeds (MHz): 1: 4154 2: 5110 
  3: 4916 4: 4902 5: 4893 6: 4915 7: 4905 8: 4932 9: 5001 10: 4992 
  11: 4910 12: 4906 13: 4918 14: 4899 15: 4920 16: 4916 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 
  mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel UHD Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:9bc4 class ID: 0300 
  Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] driver: nvidia 
  v: 460.39 alternate: nouveau,nvidia_drm bus ID: 01:00.0 
  chip ID: 10de:1f15 class ID: 0300 
  Device-3: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo 
  bus ID: 1-8:11 chip ID: 04f2:b685 class ID: 0e02 
  Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: 
  loaded: intel,nvidia unloaded: modesetting,nouveau 
  alternate: fbdev,nv,vesa display ID: :0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
  s-diag: 582mm (22.9") 
  Monitor-1: eDP1 res: 1920x1080 hz: 144 dpi: 128 
  size: 380x210mm (15.0x8.3") diag: 434mm (17.1") 
  OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.3.4 
  direct render: Yes 
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: CLEVO/KAPOK 
  driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci 
  bus ID: 00:1f.3 chip ID: 8086:06c8 class ID: 0403 
  Sound Server: ALSA v: k5.10.14-119-tkg-bmq 
Network:
  Device-1: Intel Wireless-AC 9462/9560 driver: iwlwifi v: kernel 
  port: 1000 bus ID: 00:14.3 chip ID: 8086:06f0 class ID: 0280 
  IF: wlp0s20f3 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: CLEVO/KAPOK driver: r8169 v: kernel port: 5000 bus ID: 29:00.0 
  chip ID: 10ec:8168 class ID: 0200 
  IF: enp41s0 state: down mac: <filter> 
Bluetooth:
  Device-1: Intel type: USB driver: btusb v: 0.8 bus ID: 1-14:12 
  chip ID: 8087:0026 class ID: e001 
  Message: Required tool hciconfig not installed. Check --recommends 
Drives:
  Local Storage: total: 1.82 TiB used: 64.32 GiB (3.5%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital 
  model: WDS100T2B0C-00PXH0 size: 931.51 GiB block size: physical: 512 B 
  logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> 
  rev: 211070WD temp: 39.9 C scheme: GPT 
  ID-2: /dev/nvme1n1 maj-min: 259:6 vendor: Samsung 
  model: SSD 970 EVO Plus 1TB size: 931.51 GiB block size: physical: 512 B 
  logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> 
  rev: 2B2QEXM7 temp: 39.9 C scheme: GPT 
Partition:
  ID-1: / raw size: 649.27 GiB size: 649.27 GiB (100.00%) 
  used: 17.03 GiB (2.6%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5 
  ID-2: /boot/efi raw size: 512 MiB size: 511 MiB (99.80%) 
  used: 322.2 MiB (63.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 
  ID-3: /home raw size: 649.27 GiB size: 649.27 GiB (100.00%) 
  used: 17.03 GiB (2.6%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5 
  ID-4: /var/log raw size: 649.27 GiB size: 649.27 GiB (100.00%) 
  used: 17.03 GiB (2.6%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5 
  ID-5: /var/tmp raw size: 649.27 GiB size: 649.27 GiB (100.00%) 
  used: 17.03 GiB (2.6%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5 
Swap:
  Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100) 
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/nvme0n1p4 maj-min: 259:4 
  ID-2: swap-2 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram0 
  ID-3: swap-3 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram1 
  ID-4: swap-4 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram2 
  ID-5: swap-5 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram3 
  ID-6: swap-6 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram4 
  ID-7: swap-7 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram5 
  ID-8: swap-8 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram6 
  ID-9: swap-9 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram7 
  ID-10: swap-10 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram8 
  ID-11: swap-11 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram9 
  ID-12: swap-12 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram10 
  ID-13: swap-13 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram11 
  ID-14: swap-14 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram12 
  ID-15: swap-15 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram13 
  ID-16: swap-16 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram14 
  ID-17: swap-17 type: zram size: 1.95 GiB used: 0 KiB (0.0%) 
  priority: 32767 dev: /dev/zram15 
Sensors:
  System Temperatures: cpu: 72.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 370 Uptime: 49m wakeups: 10 Memory: 31.23 GiB 
  used: 5.49 GiB (17.6%) Init: systemd v: 247 Compilers: gcc: 10.2.0 
  clang: 11.0.1 Packages: pacman: 1640 lib: 506 Shell: fish v: 3.1.2 
  running in: konsole inxi: 3.3.01 

I delete resolve.

In live ISO, the newest show it better, you start with free driver.
Not with nonfree nvidia driver.


BTW, nice piece of Hardware, I am now more for AMD, but nice :slight_smile:

1 Like

Thank you, I'm proud of it, best system I have ever had. I think I understand what you mean I will start with the live iso and go from there. Thank you for your help.

2 Likes

Did you ever end up getting a graphical interface?

The answer is sometimes :frowning: randomly it will boot with no issues with me not interfering with the boot process. That is seldom. Most often it won't boot. When I choose advanced options it gives me 4 of them,,, on linux-tkg-bmq, linux-tkg-bmq (fallback intramfs.), on linux-lts, on linux-lts (fallback intramfs.)

Most of the time it will boot to the very last one but not the first 3. I want you to know I really appreciate your help. Please let me know if there's anything I can do.

(Can I ask what tkg-bmq and lts is?)

Those are custom kernels, why are you running custom kernels?
Maybe try the default kernel for sake of troubleshooting?

It won't boot that way. When the grub screen comes up instead of Garuda I select the second one down that gives me other options. That's The only way I've been able to get it to boot consistently.

When you select Garuda can you press ALT-F5 after a minute to enable a tty console?

No, I get no response from the keyboard at all.

I don't know if this matters at all please remember I'm just uneducated about this part, but my gpu fan comes on high when this is happening. I only mention that because in all my time of using pop os which is only a few weeks, I never heard my gpu fan come on at all.

No OS no fan control, so its better high then destroy the CPU with stopped fan's

Have you tried this?

At grub enter E to edit the boot command, remove quiet and splash and add nomodeset i915.modeset=0 nouveau.modeset=0 to the same line.
Then try again ALT-F5 to get a tty console after waiting a minute.

Disabling modesetting

You may want to disable KMS for various reasons, such as getting a blank screen or a "no signal" error from the display, when using the Catalyst driver, etc. To disable KMS add nomodeset as a kernel parameter. See Kernel parameters for more info.

Along with nomodeset kernel parameter, for Intel graphics card you need to add i915.modeset=0 and for Nvidia graphics card you need to add nouveau.modeset=0. For Nvidia Optimus dual-graphics system, you need to add all the three kernel parameters (i.e. "nomodeset i915.modeset=0 nouveau.modeset=0").

Note: Some Xorg drivers will not work with KMS disabled. See the wiki page on your specific driver for details.

1 Like

This might be nothing, but how did you burn your iso?

I had to redo my iso two times before I could get a consistent boot from my cheap USB stick, I didn't try to figure out why, I just retried a couple times until I had one working and once working I installed to disk.

If you haven't tried this yet, it might be faster to try recreating the iso before trying a bunch of other things. I found it faster and easier to just keep reburning the iso until I got a copy that would boot. Also, I used dd to burn the iso from an ubuntu linux install, if you were using some installed package to burn, maybe try dd instead.

Example, don't just run this, you have to be sure you have your specific usb disk (sdX in my example), google how if you don't know for sure.

sudo dd if=garuda-dr460nized-linux-tkg-bmq-210107.iso of=/dev/sdX bs=1M status=progress
2 Likes

Removing quiet and splash will show us exactly where it is halting, if you could report back with that information.

1 Like