LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Problem installing Slackware 14.1 on my desktop (https://www.linuxquestions.org/questions/slackware-14/problem-installing-slackware-14-1-on-my-desktop-4175508916/)

kristofer12 06-23-2014 12:51 PM

Problem installing Slackware 14.1 on my desktop
 
I just bought slackware 14.1 for installing it on my dt.
The setup works well unpacking the pkgs but when i then going to reboot it it loads some text and then goes black. Maybe weak hardware ?
I then loaded the kernel following with it from the disc and it workt.
I can start KDE when i load it from the disc but when i compiling the kernel with final push "make bzImage V=1" it goes over to that state that i can reboot the system without have to have the cd in it. But in remote it gets lockt.
When i try to run kde after that it just hangs at some line saying:
Gpa dev -t mouse...

My desktop is not that good but it should still run slackware ?

business_kid 06-23-2014 01:57 PM

If you read the page of type that slackware install cd throws up at login, you will see you can boot your system with the line they suggest. Reboot, and type in that line when it says 'boot:'

kristofer12 06-24-2014 07:11 AM

I do that.
Boot: huge.s root=/dev/sda* rdinit= ro

This works at startup and i can use kde too, but i want to have that option without having a bootcd in it.

business_kid 06-24-2014 08:46 AM

Well, what are you using to boot. No EFI here (switched off) I just use lilo until grub2 and efi stabilise from a linux users perspective.

aaazen 06-24-2014 10:19 AM

Quote:

Originally Posted by kristofer12 (Post 5193073)
I do that.
Boot: huge.s root=/dev/sda* rdinit= ro

This works at startup and i can use kde too, but i want to have that option without having a bootcd in it.

If the system starts up using well using the bootcd then it should startup well using the huge kernel.

Maybe install the huge kernel?

After starting the system with the bootcd then mount the bootcd under /mnt/cdrom

The huge kernel is in /mnt/cdrom/slackware64/a/ for a 64-bit system.
Or in /mnt/cdrom/slackware/a/ for a 32-bit system.

Then for a 64-bit system:

upgradepkg kernel-huge-3.10.17-x86_64-3.txz

or for a 32-bit system:

upgradepkg kernel-huge-smp-3.10.17_smp-i686-3.txz

And then run lilo.

There are several Slackware specific forums that may be helpful:

http://www.linuxquestions.org/questi...stallation-40/

http://www.linuxquestions.org/questions/slackware-14/

TobiSGD 06-24-2014 01:30 PM

Moved: This thread is more suitable in <Distributions - Slackware> and has been moved accordingly to help your thread/question get the exposure it deserves.

garpu 06-24-2014 04:04 PM

When your computer boots and then freezes, where does the text stop? That might give us a clue as to what's going on. You can find it all in /var/log/messages. (Boot from CD/DVD, mount your hard drive, and take a peek.)

kristofer12 06-26-2014 07:18 AM

Quote:

Originally Posted by garpu (Post 5193332)
When your computer boots and then freezes, where does the text stop? That might give us a clue as to what's going on. You can find it all in /var/log/messages. (Boot from CD/DVD, mount your hard drive, and take a peek.)

READ_INIT

It stops there. Should be some configurations that have to be solved ?

BCarey 06-26-2014 11:02 AM

In your first post you mentioned you are compiling a kernel. You should get slackware up and running (booting without the CD) with the generic kernel before trying to build your own.

Brian

garpu 06-26-2014 05:14 PM

Quote:

Originally Posted by kristofer12 (Post 5194330)
READ_INIT

It stops there. Should be some configurations that have to be solved ?

Is that the only thing in the log? Seeing as though you were messing about with compiling a kernel, I'd recommend a clean install. If it's never booted properly, there's something messed up, and it could be easier/faster to make sure it's running on the stock (huge.s) kernel first.

enorbet 06-26-2014 05:56 PM

If OP is happy with the way the system operates once it's up I see no reason to reinstall. I agree with comet.berkeley that all he needs do is properly install huge.s kernel before he tries compiling one. Then maybe try generic to see if he needs either an initrd or in-kernel module support such as for ext3 and/or ext4 file systems. While it might possibly be a little faster to just wipe and reinstall, OP would learn less IMHO.

irgunII 06-27-2014 09:09 PM

I had to install 14.1 (32 bit) on my moms system today on a new hdd because her old hdd was dying.

After the installation and booting the first time after taking out the dvd, it kept stopping at a blinking cursor and black screen.

This sounds sorta like what's happening to the OP.

What I did was boot using the dvd and the 'hugesmp.s stuff' until I finally got to a login shell.

I then used 'mc' to take a look at the lilo.conf and sure enough it was slightly messed up.

At the top where it has what device to boot from, it had
Code:

boot = /dev/sda2
, but it should have been only
Code:

boot = /dev/sda
, and at the bottom of the conf file where it has root=, it was correct.

Once I fixed that, it would boot without the dvd just fine. I have no clue why, during the setup where it asks if you want a lilo simple made , that it didn't make it correctly, but no big deal.

Hopefully this will help and if not, I hope the OP finds out soon what the problem is.

BCarey 06-28-2014 12:54 PM

@irgunII - When you were asked where you want to install lilo you must have selected to install to the boot block of the partition. If you had chosen to install to the Master Boot Record then the "boot =" line would have been the way you wanted it.

Brian


All times are GMT -5. The time now is 09:03 AM.