SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am having an error on loading part of the "wpa_supplicant" in my startup. I don't have the error handy as I am at work right now.
But my issue is that I can't get to a login prompt to resolve the problem because it is hanging well doing the startup. I tried booting off the install dvd and using my root for reference but it still hangs when it gets to that spot.
I know what I need to disable to get rid of it but my problem is not being able to access the system to do that.
How do I go about getting logged in at this point? I tried using the startup disk and mounting my root partition but I could only mount it as read-only.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
How do I go about getting logged in at this point? I tried using the startup disk and mounting my root partition but I could only mount it as read-only.
In the past I have booted using the original Slackware DVD and mounted my root directory to a mount point then made changes to the /etc/rc.d/ directory to fix things. Just as a test I have tried this again just now and all is well.
Out of interest, why can you only mount your root directory read only ? Is the FS corrupt or something ?
Does Ctrl+C pressed during the hangup skip the network setup and let you boot? Otherwise you *should* be able to mount the partition as rw using a LiveCD (or else you are probably doing something incorrectly, or your filesystem may be corrupt).
The easiest way would be to use the install cd1 to boot the system as if you were going to install.
After you get to the login then from the cli (command line);
Code:
~#mkdir /slacktemp #temporary mount point
~#mount /dev/your_device /slacktemp #this is the device you installed to
~#chroot /slacktemp #change to yours
You should now be able to do edits or whatever to your system.
I tried the ctrl+c initially with no success unfortunately..
And I also tried mounting the partition manually after running the install cd/dvd but failed. I thought it was my most likely me getting my mount command incorrect for the setup, so I did some research and I had it right. Also something to note it's difficult to find many live cd's that recognize the "JFS" filesystem on a sidenote.
Turns out the drive itself was on it's last legs and crashing out it finally just spun down and called it quits.
So turned out to be a hardware issue as to why it wouldn't behave correctly, thanks for the assistance anyway!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.