slackware 10.1 install

[hurleyint1386]

I'm going to feel like a total idiot by asking this. I tried to install Slackware 10.1, and it finished, however it toldme to reboot, so when I did, i just got half of a screen filled with "99 99 99 99" and it just hangs. Any suggestions?

[je_fro]

install lilo/grub on the mbr.

[hurleyint1386]

ok, i'll see what i can do, but i'm still a newb to linux, so dont be surprised if i have difficulties

[hurleyint1386]

ok, so that problem is fixed... howevere now i have another problem. the screen reads "Kernel panic: No init found. Try passing init= option to kernel." I'm not sure what this means

[je_fro]

it means that you're going to need a live cd to boot from to fix lilo.conf. either that, or (easier) be more careful about your partitioning layout during your next reinstall. it's probably looking for / but not finding it...(specifically it's looking for /sbin/init the first process which runs)

[hurleyint1386]

that sounds like it. i think that i may have had 2 partitions named root. when i try to do setup, i have one partition that i make root, then i found out the other one has root, but there is no way to go back. ill try re installing again. third times a charm

[nabis]

When installing, configure Lilo manually, don't trust Patrick :) I belive you don't need the initrd line in lilo.conf. Who has 10.1 post your lilo.conf for hurleyint1386.
That's 8.1 (Linux and BSD on primary slave):

append="hdd=ide-scsi"
boot = /dev/hda
default = Slackware
prompt
compact
delay = 50
lba32
timeout = 60
vga = 794

image = /boot/vmlinuz
root = /dev/hdb5
label = Slackware
read-only

other = /dev/hdb1
label = FreeBSD
table = /dev/hdb

other = /dev/hda1
label = Windows
table = /dev/hda

[quip]

You can probably use your first slack install cd to rescue-boot the system. At least you could on previous versions (I know I can w/my 10.0 cd) It will give you instructions on what options to pass to the kernel. Then, once you get to the shell, you can edit lilo.conf to your taste, or re-run pkgtool, which will let you run the lilo config tool again. Because of all the things you would probably have to change (partitions, kernels, video settings) you will be much better off just re-running liloconfig and trusting Patrick.

[nabis]

10.1 doesn't use initrd, does it?

[hurleyint1386]

OK, so should I re-install slackware? or should I try to re configure lilo? I desperately need help. I use my laptop for my classes, and I certainly wasn't expecting installation to be as difficult. Thanks to every one who's helping me out though.

[quip]

nabis: I don't know. I don't have any reference to it in my lilo.conf. However, I don't think that's what the error refers to. I think it's looking for what jefro mentioned: /sbin/init, and can't find it because hurleyint1386 mislabeled his root partition.

hurleyint1386: I would boot from the first Slack install cd. I believe it will let you boot the system like a live cd. If it will, it will give you instructions on how to do so when your computer starts to boot the cd. Once you are at a cli after booting, edit the file in vi by giving "vi /etc/lilo.conf". Make sure under your kernel image stanza that the correct partition is labeled as root. You will know what the correct partition is because you had to pass it to get the Slack cd to boot up. If this is all too much, reinstall and be more careful and attentive when doing your partitioning (as jefro suggested).

[soulestream]

1. 10.1 dropped the recovery cd.

2. if it were me and I was really new, I would

reinstall
create only 2 partitions. / and /swap(about 512meg)
leave the rest for /
then do a full install.

put lilo in the mbr

you should have a fully running version of slack at that point


soule

[psych-major]

I would reinstall. I recently did a 10.1 install on my laptop in order to dual-boot with XP and it went without as hitch. I did, however, install lilo to the MBR.

If you're not dual-booting, and if you have the hard drive space, I would create 2 partitions, swap and the rest, then choose the bareacpi.i kernel, full install, and take defaults for everything else. You might end up with some bloat from items you don't necessarily want or need, but it will get you up and running quickly, and then you can customize after school gets out! ;)

[quip]

Originally posted by soulestream
1. 10.1 dropped the recovery cd.


I knew there was a reason I hung onto my 10.0 cds!

:D

[hurleyint1386]

ok, so the primary would be the / and the logical would be the /swap? then select the / as boot?

[hurleyint1386]

ok, so the primary would be the / and the logical would be the /swap? then select the / as boot?

im using cfdisk to re partition my drive, so should they both be linux fs type? or should one of them be different? thanks

[hurleyint1386]

it has officially been installed. can anyone help me start up kde? thanks

[psych-major]

As you've probably noticed, Slack starts up to a console. To start a graphical session, type 'startx'

Once everything looks good, you can make it boot to a GUI login by doing the following:

as root, edit the /etc/inittab file.

Change

# Default runlevel. (Do not set to 0 or 6)
id:3:initdefault:


to

# Default runlevel. (Do not set to 0 or 6)
id:4:initdefault:


Also, make sure you create a non-root user to do your daily business as. Routinely logging in as root is a bad idea.

[hurleyint1386]

i just got back from my class, and i figured out the /etc/innittab part, so ive got gdb running now, but im not sure how to create a new user in the console and i know that staying logged in as root is a bad thing

[psych-major]

from a console, as root, run 'adduser' It's pretty self-explanatory from there.

Once logged in as a user, if you need root access for something, KDE will prompt you for the password. If you're in a console, type 'su' and then the root password.

[hurleyint1386]

yea, i was using mandrake 10.1 for a few months, and i learned all of those commands. but with mandrake, when i installed, i created a user name easily, so i never needed to learn anything about adduser. thanks a lot for everyones help. ill be frequently asking more and more questions because i would love to be fluent with linux.

[nabis]

less /etc/X11/xorg.conf (check it first, before rebooting)
ls /usr/X11R6/bin (to see which programs are available for configuring your X-server)
You still may want to edit xorg.conf manually:
vim -N /etc/X11/xorg.conf

[5l4c|<3l2]

For first time Slackers and just for the wealth of info I always point everyone to this (http://www.bitbenderforums.com/vb22/showthread.php?postid=311808) site. it gives you a very nice step by step guide for installing Slackware.

[szero]

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/fd0
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb1
label = Linux2.4
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
image = /boot/vmlinuz-generic-2.6.10
initrd = /boot/initrd.gz
root = /dev/hdb1
label = Linux2.6.10
read-only
# Windows bootable partition config begins
other = /dev/hda1
label = WindowsXP
table = /dev/hda
# Windows bootable partition config ends


There's my lilo.conf. I generated it first using liloconfig and then I added my stuff for 2.6.10 (installed off the testing folder on the second disc).

I am on Slackware 10.1