LinuxQuestions.org
Visit Jeremy's Blog.
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 04-07-2003, 08:31 PM   #1
kierse
Member
 
Registered: Apr 2003
Distribution: Slackware!
Posts: 73

Rep: Reputation: 15
Question Slackware 9 installation problem


Hey guys,

I'm having problems installing slackware 9.0 on my laptop. I partitioned and formatted the hard drive and made it through the installation ok, but when it comes time to boot it doesn't work. As far as I can tell lilo wasn't installed and I can't seem to get it to boot off a floppy disk either. Where I start to run into problems is during the configuration process. Here are the problems I'm having:

1. First when the setup program tries to set a root password it fails saying that the passwd file doesn't exist

2. I'm not asked what kernal I want to be installed

3. never prompted to setup lilo (in fact I don't think its ever installed).

Any ideas?
Thanks
Kierse
 
Old 04-08-2003, 01:08 AM   #2
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45
Re: Slackware 9 installation problem

Quote:
Originally posted by kierse
... and made it through the installation ok, but ...
It doesn't sound like it to me. All the items you mentioned are a part of the basic setup and installation procedure.

1st suggestion: Verify your install CD is good. Your download site should have an md5sum file posted to verify with. It requires a 700 MByte CDR.

2nd suggestion: After booting and logged in as root. Run the "dmesg" command and make sure there are no error messages displayed regarding hardware. During the install, as often as you like, switch to console 2 and run dmesg again and see if any new error messages are being reported. Switch to console 2 via [ctrl][alt][f2] and back to 1 via [ctrl][alt][f1]. (Or [alt][f1], [alt][f2] if you prefer.) No new messages should be reported during the installation process. When a full install is complete and you exit the setup program, use the "df" command to report disk usage. It should use about 2 GByte.

Perhaps it will help. Please post back if you encounter specific hardware issues and need help to identify. Your problem sounds like the kernel may be shutting down the hard disk during the install.
 
Old 04-08-2003, 11:38 AM   #3
kierse
Member
 
Registered: Apr 2003
Distribution: Slackware!
Posts: 73

Original Poster
Rep: Reputation: 15
ok, I'll give that a try and I'll let you know how it turns out!

Thanks
Kierse
 
Old 04-08-2003, 03:46 PM   #4
kierse
Member
 
Registered: Apr 2003
Distribution: Slackware!
Posts: 73

Original Poster
Rep: Reputation: 15
ok, when installing I get the following error message (when using dmesg):

kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2

Anyone got any ideas?

Thanks
kierse
 
Old 04-08-2003, 04:13 PM   #5
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45
If this message is at the very beginning of the install and none other follow, then I suggest it is an attempt to load scsi adapter module to see if one is present. You can probably ignore it.

However, if there were other error messages or you actually have a scsi based system then this might be required. Less likely if you were able to partition your drive for the install before the attempt to load it.

The real key here is if other error messages were presented. Did the install complete as required, requesting a kernel and installing lilo, etc.? Or was this attempt the same as the prior incomplete attempt?
 
Old 04-08-2003, 04:20 PM   #6
kierse
Member
 
Registered: Apr 2003
Distribution: Slackware!
Posts: 73

Original Poster
Rep: Reputation: 15
At that point I stopped the installation, I'll try the installation again to see if it completes successfully
 
Old 04-08-2003, 04:53 PM   #7
kierse
Member
 
Registered: Apr 2003
Distribution: Slackware!
Posts: 73

Original Poster
Rep: Reputation: 15
Ok, installation done. Still the same problems:

1. When I try to set the root password it says that the passwd file doesn't exist

2. Says config is done and that I should reboot.

After this is done the system still doesn't work. I'm gonna check the md5 checksum (I found the file on the server but didn't realize I had to do anything with it ) to see if that could be the problem. Is there any way to do checksum on a windows machine or is it only available on linux?

Kierse
 
Old 04-08-2003, 06:26 PM   #8
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45
After the install was complete, did you run dmesg again to see if any new error messages?

To my knowledge at least, I have only used md5sum on a Linux based system. However, I did a quick google and came up with the link below. It appears to be a MS based program. Suggest running against the downloaded iso image first, then against the CD itself. (If possible with the program.) A good image but bad burn still produces unusable CD.

http://www.etree.org/md5com.html

From Linux though, you boot the CD and login as root. The limited install system available does include the md5sum program. Mount the CD and change directory to the CD slackware directory and type "md5sum --check CHECKSUMS.MD5 | less". I would expect that it will produce somewhere around 190 errors. That is because they usually do not adjust the file after removing the "k" and "kdei" disk sets. During this process you can also run the dmesg command from another console to detect any CD reading errors.

For the root file system for the system that the CD uses to install from, I think it is the isolinux/initrd.img file. So I think the following should check that file.

Change dir to the CD isolinux directory.
md5sum initrd.img
grep initrd.img ../CHECKSUMS.MD5

The MD5 sum output from the above two commands should match.
 
Old 04-08-2003, 06:55 PM   #9
kierse
Member
 
Registered: Apr 2003
Distribution: Slackware!
Posts: 73

Original Poster
Rep: Reputation: 15
Ok, I tried what you said and here is what I got:

1. doing md5sum on slackware/CHECKSUMS.md5 yielded like 252 files that could not be read

2. when I used grep of CHECKSUMS.md5 and the md5sum of initrd.img I got the same value.

I also found a DOS app to determine md5 sum and I checked the image file. The value it calculated was different from the posted md5 sum, so I'm currently downloading another iso image.
 
Old 04-08-2003, 07:02 PM   #10
kierse
Member
 
Registered: Apr 2003
Distribution: Slackware!
Posts: 73

Original Poster
Rep: Reputation: 15
Alright

the md5sum of the new iso is the same as the posted value, I'll burn this image and let you know how it turns out!

kierse
 
Old 04-08-2003, 08:34 PM   #11
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45
I mounted the iso image that I downloaded from slackware.at using the loopback device and ran md5sum accross the slackware directory tree. The results were;

md5sum: WARNING: 262 of 1538 listed files could not be read

This total would be 8 files for the "k" set and 254 files for "kdei" set for the 262 total files above.

This total was way higher than what I estimated earlier. Now I can't remember where that other number came from. But anyway, your post stated 252, so I wonder if a different set of files could of been left off. Since the md5sum didn't match on the iso image perhaps that will solve the problem. But it is still a good practice to verify even after the burn from the CD itself. It can save a lot time and aggrevation. If you pipe the output to "less" then you cna review the output to determine which files are effected. Or you can pipe it to "grep FAILED" and see just the failures.

md5sum --check CHECKSUMS.md5 | less
md5sum --check CHECKSUMS.md5 | grep FAILED

Perhaps it will help to verify your 2nd CD before you attempt to install again.
 
Old 04-09-2003, 06:47 PM   #12
kierse
Member
 
Registered: Apr 2003
Distribution: Slackware!
Posts: 73

Original Poster
Rep: Reputation: 15
The new image checked out and the md5sum of reported by the cd is accurate.

The install went ok this time, it asked what kernal I wanted to install (I chose bare.i as this is what I used when booting) and tried to install lilo. It went ok until it tried to install lilo in the root (or floppy, neither would work). It said that lilo encountered an error and that it was still posible to install lilo by editing the lilo.conf file. I'm gonna try and see if I can figure it out. Again, any help would be nice

Thanks
Kierse
 
Old 04-09-2003, 09:16 PM   #13
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45
Sounds like you are a lot further along this time. It is still bewildering as to why lilo is having a problem. But I can offer what steps I take during the install for lilo and then maybe a method to allow a correction. I normally choose to start with a new config and select expert mode. Enter my root partition, select normal vga or vga = 1024x768x65K if framebuffer desired. I choose to install on the MBR of the hard disk. I just call it a name "Linux". Provide any append statements and set the delay for five seconds. About all I can remember. Then install it. I have not known it to fail.

For your correction attempt. Boot your install CD and login as root.
Sub your partition for hda1 below. Mount the root partition:

mount /dev/hda1 /mnt
cd /mnt/etc
cat lilo.conf

Review the output and see what you can determine.
If you want to make changes I think the install system is limited to vi as an editor.
And I don't think it is elvis anymore. I think it was changed to something called busybox. Probably because it was a smaller program. (vi lilo.conf)
If it looks OK then try to install it again or edit as desired then
write the config:

cd /
lilo -r /mnt
umount /mnt
Then you can remove the CD and reboot: telinit 6

I will post my lilo.conf below.

Code:
# Start LILO global section
lba32
append="hdd=ide-scsi"
boot = /dev/hda
#compact        # faster, but won't work on all systems.
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x64k
vga = 791
# 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-ide-2.4.20DVD
  root = /dev/hda2
  label = Linux
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.20
  root = /dev/hda2
  label = Maint
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
Since I have to run a custom kernel, the original boot record was the section labeled "Maint" it was originally "Linux". And my install root partition was hda2. The "boot=/dev/hda" instructs to install to the MBR of the hard disk. Perhaps it will help if you have something to compare against.

Last edited by Excalibur; 04-09-2003 at 09:19 PM.
 
Old 04-09-2003, 09:23 PM   #14
kierse
Member
 
Registered: Apr 2003
Distribution: Slackware!
Posts: 73

Original Poster
Rep: Reputation: 15
Thanks, I was able to figure out what I was doing wrong. I was trying to install lilo to the root instead of the MBR. It works fine now. The problem I am now experiencing is that when I try to load the window manager I get an error and it says that it cannot find the default font cursor. I'm trying a few things right now to see if that will correct the problem
 
Old 04-09-2003, 10:03 PM   #15
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45
If you setup the lilo.conf to use vga=791 for framebuffer mode then default XF86Config file should work OK. If you set up lilo.conf for vga=normal then you might try VESA mode.

mv /etc/X11/XF86Config /etc/X11/XF86Config.orig
cp /etc/X11/XF86Config-vesa /etc/X11/XF86Config
startx

If not then perhaps setting lilo.conf to vga=791 or as proper for your laptop, write the boot info (lilo) and then reboot and just use the default file that is installed.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Slackware installation problem DC12k Slackware 10 11-30-2006 01:44 PM
Slackware 9.1 installation problem FinalSolution Linux - Hardware 1 04-29-2004 06:25 PM
slackware installation problem 286 Linux - Newbie 2 11-24-2003 03:04 PM
slackware 9.1 installation problem apax Slackware 4 11-03-2003 10:43 AM
Slackware 9.0 installation problem zag_zag Slackware 5 08-09-2003 08:04 PM


All times are GMT -5. The time now is 12:58 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration