LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-26-2002, 12:48 PM   #1
andrew001
Member
 
Registered: Nov 2002
Distribution: Slackware 9.0
Posts: 321

Rep: Reputation: 30
Question Slackware Install> kernel panic




Hi-

I tried to install Slackware last night, but I ran ito a few problems. I created the boot and root disk correctly (i think) using bare.i and color.gz .

When using the boot disk, everything seemed to go fine (ie hardware recognition seemed to be correct), but ther kernel would not boot. It gave me an error message about not being able to mount the root filesystem.

I assume that it was trying to mount on Windows side (FAT32), rather than the blank side of my hd. If this is indeed the problem, Is there anyway to control where it tries to mount during install? Anybody have any ideas as to anything else that could be going wrong here?

Thanks a lot,

Andrew
 
Old 12-26-2002, 01:16 PM   #2
DavidPhillips
LQ Guru
 
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,163

Rep: Reputation: 58
you should be able to use this


mount root=/dev/hd??

hd?? being the partition like hda5


Last edited by DavidPhillips; 12-26-2002 at 01:22 PM.
 
Old 12-26-2002, 05:12 PM   #3
Aussie
Senior Member
 
Registered: Sep 2001
Location: Brisvegas, Antipodes
Distribution: Slackware
Posts: 4,590

Rep: Reputation: 58
Is there any reason why your not booting the install cd?
 
Old 12-27-2002, 10:18 PM   #4
andrew001
Member
 
Registered: Nov 2002
Distribution: Slackware 9.0
Posts: 321

Original Poster
Rep: Reputation: 30
Yea-

When I issue the command:

mkisofs -o /tmp/slakware.iso -R -V "Slackware Install" \
-v -d -D -N -no-emul-boot -boot-load-size 4 -boot-info-table \
-b isolinux/isolinux.bin \
-c isolinux/isolinux.boot \
-A "Slackware 8.0 Install CD"

It says that my command is missing pathspec (whatever that means). Seeing as I am totally ignorant about the mkisofs command, I thought the disks would be easier (obviously I was wrong).

Thanks a lot,
Andrew
 
Old 12-27-2002, 11:02 PM   #5
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 46
<edit>
I just reread the command that you have and the end it states Slackware 8.0. There should be an iso image out there somewhere for that. IS there a reason though you didn't download the 8.1 iso image?

</edit>

The only reason I can think of for mkisofs is if you are using the slackware-current directory. Slackware 8.1 has an install iso image that only needs to be burned without using mkisofs, just cdrecord. Unless you need to reauthor for another reason.

But anyway I think that you are using the command that was provided in the README.TXT file in isolinux directory. That command was written to be executed from inside the slackware-current tree as the root of the cd image and at the very end of the command was a single period separated by a single space from your last closing quote. That period indicated the path to mkisofs as the current directory. That path can be modified to point to the correct directory but it is dependent on the current directory of the command execution unless a full explicit path from the root is specified. Since that may vary from one system to another, they choose to just reference the path using the simple period.

Hope it helps.

Last edited by Excalibur; 12-27-2002 at 11:05 PM.
 
Old 12-27-2002, 11:25 PM   #6
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 46
For Slackware 8.0, only two disks are required for a floppy boot. The kernel disk and the root file system. The kernel is the bare.i file and the root file system is the color.gz disk. After the kernel boots it should prompt for the second disk to be inserted and continue to decompress and mount the image as a ram disk. If it didn't prompt for the second disk then I can only suppose the wrong bare.i image was used that had a different root device specified without any prompting. Or the root disk was corrupted and it couldn't read it and it didn't have a root system to mount.

The files to use from the slackware 8.0 CD are bootdsks.144/bare.i and rootdsks/color.gz. But if you have the iso image or the 8.0 install CD, it should be a bootable CD.

Let us know what you are attempting to work with. It could really help in trying to provide some advice.
 
Old 12-28-2002, 12:41 PM   #7
andrew001
Member
 
Registered: Nov 2002
Distribution: Slackware 9.0
Posts: 321

Original Poster
Rep: Reputation: 30
I have the iso for the 8.0 install CD. I downloaded it at school before i left for break, now I feel like a moron because I'm stuck with the older version. I'm on 56k at home, so it would take days to download the 8.1 iso.
Today I'll see if one of my friends with broadband will dl the 8.1 iso for me and burn it. Then I'll just use the install iso, and everything will good.
Thanks for putting up with my *complete* ignorance on the subject!

-Andrew
 
Old 12-28-2002, 01:26 PM   #8
DavidPhillips
LQ Guru
 
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,163

Rep: Reputation: 58
no problem, just boot the cd and your good to go
 
Old 12-28-2002, 10:09 PM   #9
andrew001
Member
 
Registered: Nov 2002
Distribution: Slackware 9.0
Posts: 321

Original Poster
Rep: Reputation: 30
OK~

I paid a surprise visit to one of my buds from school, and dl'ed the 8.1 iso. I just finished installing everything succesfully (kind of).
The only problem is that when I issue the 'startx' command, my monitor just goes blank. I manually re-installed all of the gnome packages, and when I tried to use it with 'switchdesk', it said the command did not exist.
I'm probably only having trouble b/c switchdesk is a pamper-the-user redhat thing or something, but I really don't know what is going on.

Any ideas?

Thanks!

-Andrew
 
Old 12-28-2002, 10:42 PM   #10
DavidPhillips
LQ Guru
 
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,163

Rep: Reputation: 58
yes there is no switchdesk

you need to configure X first

you can try xfree86setup first, it is fool proof. If the screen is too big, 1600x1200 or 1800+ and you can't see anything that's easy to fix by switching screens with ctrl_+ or ctrl_- with the + and - on the numlock keypad. By adding a modes line in the default Depth's subsection in /etc/X11/XF86Config with the screen size you like you can get it the way you like it.

Modes "1024x768" "800x600"


you can use kdm on boot if you want to, which loads a login screen with a menu. You can do this several ways

one way would be to add this to /etc/rc.d/rc.local

/opt/kde/bin/kdm
you could also setup /etc/inittab to run it when you go to the specified runlevel

If you just want to use startx, the command to set a default window manager is xwmconfig

Last edited by DavidPhillips; 12-28-2002 at 10:51 PM.
 
Old 12-29-2002, 12:01 AM   #11
andrew001
Member
 
Registered: Nov 2002
Distribution: Slackware 9.0
Posts: 321

Original Poster
Rep: Reputation: 30
okay - xwindows is up and running! thanks!

my screen resolution is killing me though. i tried adding

Mode "600x800"

into

/etc/X11/XF86Config under the colour depth i chose, but it didn't work - what can i do to adjust it

Thanks a lot for ur help
Andrew
 
Old 12-29-2002, 12:38 AM   #12
gokulagiridaran
Member
 
Registered: Dec 2002
Posts: 36

Rep: Reputation: 15
try to mount it by root=/dev/hdxxx (x is your linux partition).
 
Old 12-29-2002, 01:39 AM   #13
DavidPhillips
LQ Guru
 
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,163

Rep: Reputation: 58
did you try 600x800 or 800x600

800x600 will work
here is mine
My default Depth is 24

SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600"
EndSubSection


Make sure you have Modes not Mode

Last edited by DavidPhillips; 12-29-2002 at 01:40 AM.
 
Old 12-29-2002, 12:12 PM   #14
tarballedtux
Member
 
Registered: Aug 2001
Location: Off the coast of Madadascar
Posts: 498

Rep: Reputation: 30
Just in case anyone was wondering. To make an ISO of the slackware-current tree make sure to put a '.' after the whole mkisofs command. It took me a while to figure it out. I thought it was an error in the README at first


--tarballedtux
 
Old 12-29-2002, 11:43 PM   #15
andrew001
Member
 
Registered: Nov 2002
Distribution: Slackware 9.0
Posts: 321

Original Poster
Rep: Reputation: 30
lol~o well, too late now! slack is working great. thanks for all ur help everybody.

-Andrew
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
compiled kernel 2.6.10 with slackware 10.0, kernel panic salviadud Linux - Newbie 1 02-09-2005 04:05 PM
Slackware install Kernel panic neilcpp Slackware 2 01-27-2004 09:07 PM
Slackware 9 Kernel Panic while trying to install in VMWare 4 Jesterace Slackware 4 10-28-2003 08:24 PM
Slackware Kernel Panic! Heretic1 Linux - Newbie 0 10-27-2003 09:35 PM
Slackware 8.1 -- Kernel panic appler Slackware 4 03-19-2003 02:59 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:47 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration