[SOLVED] Slackware 64 14.1 unbootable

TrickyRickinOK · 02-12-2014, 04:06 AM

I just recently installed Slackware 64 14.1.
I made it multilib, installed Nvidia drivers and Chromium from slackbuids. I custom configured a kernel and compiled it but it wouldn't boot. I tried passing my root partition to the kernel and booting from the dvd but that does not work. So I booted the install dvd and mounted the root partition and chrooted my root partition and changed the l Iinks back to the original kernel and rerun lilo, but it boots and panics when loading sshd. It acts like it is out of ram but it hss 2 gig bytes. How can I start in single user mode and prevent it from trying to start the daemons?
I

harryhaller · 02-12-2014, 04:17 AM

Quote:

/sbin/telinit s

will put you in single user mode.

check "man telinit"

harryhaller · 02-12-2014, 04:57 AM

You can also do:

Quote:

telinit 1

and then to return to runlevel 3

Quote:

telinit 3

TrickyRickinOK · 02-12-2014, 08:24 AM

Will that work passing it to the kernel at boot? I guess I try it when I have time, but I need to know how to be In single user at boot.

Ramurd · 02-12-2014, 09:10 AM

In the LILO screen, when selecting the kernel to boot, given the label "Linux" you can do "Linux 1" which will tell it to start in runlevel 1, which is single-user mode.

TrickyRickinOK · 02-12-2014, 02:34 PM

Okay I tried Linux 1 it booted says
Going to single user mode. . .
but never starts a shell. Looks like I'm going to have to reinstall.

smoooth103 · 02-12-2014, 05:24 PM

I've been having issues as well. Not 100% sure it's Slackware 14.1 yet but having high instability issues and hangs on boot like you mention. On older and newer installs. I have a feeling it's related to my use of a HD that is 3TB.

smoooth103 · 02-12-2014, 07:38 PM

so I have a 3TB hard drive that I fresh installed 14.1 (64) on. I used gdisk to create efi partition, swap, and root partition. I ran setup and followed directions. Everything went smoothly. Then when I rebooted: Elilo hangs on "loading kernel vmlinuz... Done." The bios recognizes the drive as uefi.

Any ideas what might be causing this?

TrickyRickinOK · 02-13-2014, 12:46 AM

I'm fairly sure my problem was a misconfigured kernel and I guess I didn't have lilo configured correctly to select the install kernel as an alternate.
I decided to reinstall since I had just installed a couple of days ago, and it wasn't worth spending anymore time trying to fix it when I could reinstall.

Whatever problem you are having you should start a new thread.