LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (http://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   unhappy with slack (http://www.linuxquestions.org/questions/slackware-installation-40/unhappy-with-slack-4175459961/)

Pedroski 04-29-2013 03:40 AM

unhappy with slack
 
I just installed slack 14. It was the first time I've tried slack. Installation went smoothly, no problems or error messages. After installing, I told it to install lilo, and added windows and ubuntu partitions to the lilo.conf, following the instructions. Reboot, I get the nice slack login screen, choose slack:

[7.396294] usb 3-4: serial number MU418ASA

Seven seconds into boot is as far as it goes! I tried to boot Ubuntu, also stops. Windows will boot, but who wants windows?? Everything worked fine using grub and Ubuntu or Fedora, so I rule out mechanical failure.

Not very impressed with Slackware!!

Didn't have a Ubu disc, so had to reinstall Fedora to get grub back, so that I could complain here!! Why didn't slack boot?? Anyone else had this trouble?

H_TeXMeX_H 04-29-2013 03:52 AM

Why install lilo if you already have a bootloader ? Why not just add Slackware to that bootloader ? Why re-install Fedora when you could have re-installed GRUB.

Where did you install lilo ? Did you configure it properly ?

Sure, go ahead blame Slackware, it is obviously at fault.

Pedroski 04-29-2013 04:00 AM

Well I just followed the instructions, I am not a guru like you, just a peasant! It wanted to install a bootloader. I thought LILO woould work as well as Grub. I put it in the MBR, following the instructions. After that, I could not boot into Linux, so it was a bit hard to reinstall grub, even if I knew how to do that!

H_TeXMeX_H 04-29-2013 06:08 AM

So now everything boots properly ?

I don't know why it would hang at that line. Did you try to boot multiple times and it always hangs at the same line on boot ?

Make sure the Slackware DVD or CD you are using was burned properly.

TobiSGD 04-29-2013 06:37 AM

Quote:

Originally Posted by Pedroski (Post 4940969)
[7.396294] usb 3-4: serial number MU418ASA

If it hangs at that line the first thing to do is to remove all unnecessary USB devices and see if it works after that.

cynwulf 04-29-2013 06:41 AM

I agree with tex, you did not need to install yet another bootloader. If you'd have installed Slackware, skipped the lilo install and then just re-run grub2 on one of your existing distros it would have picked it up...

In all honesty as you have not posted up the contents of your /etc/lilo.conf and details of your partitioning schema, this thread seems rather pointless.

Pedroski 04-29-2013 06:57 AM

I suppose I just wanted to moan! Sorry about that.

No usb devices were plugged in, just my little loud speakers, but they just get their juice from the usb port.

Actually, it also said, I wrote it down:

[7.396294] usb 3-4: serial number MU418ASA
Enter runlevel:

So I entered 6, to which the machine answered:

Init: entering runlevel: 6
Init : no more processes left

That was all! I tried 4 times to boot slack, then gave it up! Couldn't enter runlevel 3 either!

JWJones 04-29-2013 07:13 AM

Quote:

Originally Posted by Pedroski (Post 4941079)
So I entered 6, to which the machine answered:

Init: entering runlevel: 6
Init : no more processes left

That was all! I tried 4 times to boot slack, then gave it up! Couldn't enter runlevel 3 either!

Do not use runlevel 0 or 6.

Slackware isn't really the kind of distro you install on a whim. It will not hold your hand. There was no need for you to install LILO when you already had GRUB set up.

Maybe start here, next time.

Pedroski 04-29-2013 07:24 AM

Although I am no expert, I have installed other distros, and they work. One presumes LILO functions, as the boot process started. The dvd was fine, I checked it, and as I said, the install did not complain at all.

What got me worried was when Ubuntu also failed to start. Then I said some words about slack which one should not utter in polite company!

rokytnji 04-29-2013 07:30 AM

Quote:

so that I could complain here!!
Hahahaha, complaining in a slackware forum about slackware is about as sensible as going into a barrio and complaining about the tacos el cabron at a cholos mothers house. At least no bodily harm ensues at a forum.

Quote:

Why didn't slack boot?? Anyone else had this trouble?
I guess since like was mentioned. No lilo conf. No answer to "Why didn't slack boot".

Same Same with "Anyone else had this trouble".

Hopefully you learned to include documentation in code tags next time (like lilo conf).

Happy trails, Rok.

brianL 04-29-2013 07:39 AM

Quote:

Originally Posted by rokytnji (Post 4941104)
At least no bodily harm ensues at a forum.
Happy trails, Rok.

Don't be too sure. There may be a Slack Death Squad on their way to his house now. :eek:

BadAvocado 05-01-2013 04:34 AM

Quote:

Originally Posted by Pedroski (Post 4941079)
I suppose I just wanted to moan! Sorry about that.

No usb devices were plugged in, just my little loud speakers, but they just get their juice from the usb port.

Actually, it also said, I wrote it down:

[7.396294] usb 3-4: serial number MU418ASA
Enter runlevel:

So I entered 6, to which the machine answered:

Init: entering runlevel: 6
Init : no more processes left

That was all! I tried 4 times to boot slack, then gave it up! Couldn't enter runlevel 3 either!

I think slackware uses runlevel 4 for graphical desktop and 3 for console. Runlevel 6 is 'reboot', I believe.

You should post the contents of your /etc/lilo.conf, as mentioned earlier.

Pedroski 05-01-2013 05:40 AM

Yeah, well 3 didn't work either, so I gave up. Later I had great trouble reinstalling Ubuntu. It installed fine, but then kept saying it cannot find init, and stopped during boot, just like slack. I have no idea what was wrong. I ran 'recovery mode' which threw up the same error as Slack, mentioned above. But as I did not format sda3, the older kernels were still there. I finally got a 3.2 kernel to boot. The touchpad would not work, the sound would not work, but I could run an update. That installed kernel 3.5.something. A reboot using this kernel worked and Ubuntu now works, everything fine. But something weird was happening. I got no errors during install.

I have installed Fedora 18 3 times these last few days, no problem, which kind of negates my theory that my laptop is somehow broken.

Some other time I'll try Slack again!!

frankbell 05-01-2013 09:52 PM

A couple of thoughts come to mind about the initial post:

If Grub was installed to the master boot record, attempting to install Lilo to the MBR may not work unless the MBR is first reformatted.

Also, I have never had Slackware's so-called "install Lilo automatically" option work, and I've never had the "expert" Lilo install fail, as long as I did not skip a step (which is admitted easy to do the first time)--except when Grub was previously installed to the MBR. In that case, see above.

In order to figure out what exactly went wrong, we need to know exactly what steps were followed, step by step, to install Lilo.

Without that information, we are just whistling in the dark.

Pedroski 05-01-2013 10:01 PM

Thanks for that: I really don't know, but I think LILO installed ok, beccause, on boot I had the screen with the Slackware logo and the choice of os. I nearly went and bought a new laptop, although this one is only a year old, but now I have Fedora and Ubuntu and Windows running ok, I don't think there is an mechanical/electronic failure.

A mystery! Next time I try, I will say no to LILO, and just run grub-update after installation!!


All times are GMT -5. The time now is 08:01 PM.