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 02-21-2007, 10:00 PM   #46
inspiron_Droid
Member
 
Registered: Dec 2006
Distribution: Debian (Wheeze)
Posts: 391

Rep: Reputation: Disabled

Have you tried using grub yet?
 
Old 02-21-2007, 10:09 PM   #47
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Quote:
Originally Posted by sse007
can you post ur lilo.conf file and the result of "ls -l /boot"
# ls -l /boot
Code:
total 7531
lrwxrwxrwx 1 root root      37 Feb  8 23:14 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
lrwxrwxrwx 1 root root      25 Feb 21 17:35 System.map -> System.map-generic-2.6.20
-rw-r--r-- 1 root root 1122219 Sep 30 21:48 System.map-generic-2.6.16.29
-rw-r--r-- 1 root root  294610 Feb 10 18:46 System.map-generic-2.6.20
-rw-r--r-- 1 root root     512 Feb  9 05:55 boot.0200
-rw-r--r-- 1 root root     512 Feb 10 00:26 boot.0800
-rw-r--r-- 1 root root     512 Feb  8 23:40 boot.0802
-rw-r--r-- 1 root root     168 Feb  9 05:55 boot_message.txt
lrwxrwxrwx 1 root root      21 Feb 21 17:35 config -> config-generic-2.6.20
-rw-r--r-- 1 root root   52358 Sep 30 21:48 config-generic-2.6.16.29
-rw-r--r-- 1 root root   16613 Feb 10 18:46 config-generic-2.6.20
-rw-r--r-- 1 root root    5032 Aug  3  2006 diag1.img
drwx------ 2 root root   12288 Feb  8 23:01 lost+found
-rw------- 1 root root   17920 Feb 21 18:56 map
lrwxrwxrwx 1 root root      22 Feb 21 17:35 vmlinuz -> vmlinuz-generic-2.6.20
-rw-r--r-- 1 root root 3028097 Sep 30 21:48 vmlinuz-generic-2.6.16.29
-rw-r--r-- 1 root root 3115605 Feb 10 18:46 vmlinuz-generic-2.6.20
# cat /etc/lilo.conf
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# boot = /dev/fd0
boot = /dev/sda
message = /boot/boot_message.txt
compact
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
vga = normal

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.16.29
  root = /dev/sda2
  label = Linux-2.6.16.29
  read-only

image = /boot/vmlinuz-generic-2.6.20
root = /dev/sda2
label = linux-2.6.20
read-only

# Linux bootable partition config ends
B.R.
satimis
 
Old 02-21-2007, 10:33 PM   #48
sse007
Member
 
Registered: Nov 2005
Posts: 39

Rep: Reputation: 15
try remove the 2 packages kernel-generic-2.6.20 and kernel-modules-2.6.20 and reinstall them, make sure System.map-generic-2.6.20, config-generic-2.6.20 and vmlinuz-generic-2.6.20 are gone before reinstall. Run lilo again after reinstall. Good luck ;-)
 
Old 02-23-2007, 09:33 AM   #49
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Quote:
Originally Posted by sse007
try remove the 2 packages kernel-generic-2.6.20 and kernel-modules-2.6.20 and reinstall them, make sure System.map-generic-2.6.20, config-generic-2.6.20 and vmlinuz-generic-2.6.20 are gone before reinstall. Run lilo again after reinstall. Good luck ;-)
Hi sse007,

# removepkg kernel-generic.tgz
# removepkg kernel-modules.tgz
both went through without complaint.

# ls -al /boot
Code:
total 4171
drwxr-xr-x  3 root root    1024 Feb 23 21:04 .
drwxr-xr-x 20 root root    4096 Feb 23 20:59 ..
lrwxrwxrwx  1 root root      37 Feb  8 23:14 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd                           
lrwxrwxrwx  1 root root      25 Feb 21 17:35 System.map -> System.map-generic-2.6.20                                 
-rw-r--r--  1 root root 1122219 Sep 30 21:48 System.map-generic-2.6.16.29
-rw-r--r--  1 root root     512 Feb  9 05:55 boot.0200
-rw-r--r--  1 root root     512 Feb 10 00:26 boot.0800
-rw-r--r--  1 root root     512 Feb  8 23:40 boot.0802
-rw-r--r--  1 root root     168 Feb  9 05:55 boot_message.txt
lrwxrwxrwx  1 root root      21 Feb 21 17:35 config -> config-generic-2.6.20
-rw-r--r--  1 root root   52358 Sep 30 21:48 config-generic-2.6.16.29
-rw-r--r--  1 root root    5032 Aug  3  2006 diag1.img
drwx------  2 root root   12288 Feb  8 23:01 lost+found
-rw-------  1 root root   17920 Feb 23 20:57 map
lrwxrwxrwx  1 root root      22 Feb 21 17:35 vmlinuz -> vmlinuz-generic-2.6.20
-rw-r--r--  1 root root 3028097 Sep 30 21:48 vmlinuz-generic-2.6.16.29
System.map-generic-2.6.20, config-generic-2.6.20 and vmlinuz-generic-2.6.20 all gone. Only the symlink of vmlinuz and the symlink of config still there.

Reinstallation:-

# installpkg Desktop/smp_kernel/kernel-generic-2.6.20_smp-x86_64-1.tgz
Code:
Installing package kernel-generic-2.6.20_smp-x86_64-1...
PACKAGE DESCRIPTION:
kernel-generic: kernel-generic (a general purpose Linux kernel)
kernel-generic:
kernel-generic: This is a Linux kernel with built-in support for most IDE controllers
kernel-generic: and the ext2 filesystem.  If you need more advanced filesystems, or
kernel-generic: need to load support for a SCSI or other controller, then you'll need
kernel-generic: to load one or more kernel modules using an initial ramdisk, or
kernel-generic: initrd.  For more information about creating an initrd, see the
kernel-generic: README.initrd file in the /boot directory.
kernel-generic:
Executing install script for kernel-generic-2.6.20_smp-x86_64-1...
# installpkg Desktop/smp_kernel/kernel-modules-2.6.20_smp-x86_64-1.tgz
Code:
Installing package kernel-modules-2.6.20_smp-x86_64-1...
PACKAGE DESCRIPTION:
kernel-modules: kernel-modules (Linux kernel modules)
kernel-modules:
kernel-modules: A kernel module is a piece of object code that can be dynamically
kernel-modules: loaded into the Linux kernel to provide new kernel functions.  Most of
kernel-modules: these modules provide support for devices such as CD-ROM drives, tape
kernel-modules: drives, and ethernet cards.  You can choose which modules to load by
kernel-modules: editing /etc/rc.d/rc.modules.
kernel-modules:
Executing install script for kernel-modules-2.6.20_smp-x86_64-1...
install/doinst.sh: line 30:  6405 Segmentation fault      chroot . /sbin/depmod -a >/dev/null 2>/dev/null
# ls -al /boot/
Code:
total 7536
drwxr-xr-x  3 root root    1024 Feb 23 21:23 .
drwxr-xr-x 20 root root    4096 Feb 23 21:24 ..
lrwxrwxrwx  1 root root      37 Feb  8 23:14 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
lrwxrwxrwx  1 root root      25 Feb 23 21:23 System.map -> System.map-generic-2.6.20
-rw-r--r--  1 root root 1122219 Sep 30 21:48 System.map-generic-2.6.16.29
-rw-r--r--  1 root root  294610 Feb 10 18:46 System.map-generic-2.6.20
-rw-r--r--  1 root root     512 Feb  9 05:55 boot.0200
-rw-r--r--  1 root root     512 Feb 10 00:26 boot.0800
-rw-r--r--  1 root root     512 Feb  8 23:40 boot.0802
-rw-r--r--  1 root root     168 Feb  9 05:55 boot_message.txt
lrwxrwxrwx  1 root root      21 Feb 23 21:23 config -> config-generic-2.6.20
-rw-r--r--  1 root root   52358 Sep 30 21:48 config-generic-2.6.16.29
-rw-r--r--  1 root root   16613 Feb 10 18:46 config-generic-2.6.20
-rw-r--r--  1 root root    5032 Aug  3  2006 diag1.img
drwx------  2 root root   12288 Feb  8 23:01 lost+found
-rw-------  1 root root   17920 Feb 23 20:57 map
lrwxrwxrwx  1 root root      22 Feb 23 21:23 vmlinuz -> vmlinuz-generic-2.6.20
-rw-r--r--  1 root root 3028097 Sep 30 21:48 vmlinuz-generic-2.6.16.29
-rw-r--r--  1 root root 3115605 Feb 10 18:46 vmlinuz-generic-2.6.20
# ls -al /usr/src/
Code:
total 20
drwxr-xr-x  5 root root 4096 Feb 21 17:53 .
drwxr-xr-x 20 root root 4096 Jan 28 22:09 ..
lrwxrwxrwx  1 root root   16 Feb 20 22:18 linux -> linux-2.6.16.29/
drwxr-xr-x 19 root root 4096 Sep 30 22:01 linux-2.6.16.29
drwxr-xr-x 19 root root 4096 Feb  5 02:44 linux-2.6.20
drwxr-xr-x  7 root root 4096 Jul 28  2006 rpm
# lilo
Added Linux *
Added linux-2.6.20


Rebooted PC. Select linux-2.6.20 (new kernel). PC booted to runlevel 3. Still unable to start X

"uname -a" displayed Linux-2.6.20

Rebooted PC back to old kernel. PC failed to boot requesting to run "fsck /dev/sda2"

Took approx >20 min to fix errors.

Now PC succeeds booting to old kernel - Linux-2.6.16.29 with X started without problem

$ df -l
Code:
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda2              7578540   3734448   3452912  52% /
/dev/sda1               101086     11646     84221  13% /boot
/dev/sda3            113524192    196588 107467896   1% /var
/dev/sda6             29232684   2210688  25513096   8% /home
During booting following error displayed;
run fsck /dev/sda3 to fix some error
run fsck /dev/sda6 to fix some error

I'll start another topic
1) can I umount /dev/sda3 and /dev/sda6 on runlevel 3? If YES, how to make it.
2) how to boot to runlevel 1, single user mode and umount /dev/sda3 and /dev/sda6.


I don't know whether the new kernel can boot now.


B.R.
satimis
 
Old 02-23-2007, 02:56 PM   #50
sse007
Member
 
Registered: Nov 2005
Posts: 39

Rep: Reputation: 15
if u can start the new kernel into level 3 but can't startx, looks like some issue with xorg. You can check the log in /var/log/Xorg.0.log to see what's the problem. You can also try using vesa instead of nvidia driver to startx to see if it is the driver problem as u can startx with the old kernel.
 
Old 02-23-2007, 08:54 PM   #51
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Quote:
Originally Posted by sse007
if u can start the new kernel into level 3 but can't startx, looks like some issue with xorg. You can check the log in /var/log/Xorg.0.log to see what's the problem. You can also try using vesa instead of nvidia driver to startx to see if it is the driver problem as u can startx with the old kernel.
Hi sse007,

To get X started on new kernel is not the major issue. I can fix it. What I expect to find out is why after booting the new kernel, rebooting the old kernel made the PC fail to boot and have to running fsck /dev/sda2 (/) to fix the errors. But there are still some errors on /dev/sda3 (/var) and /dev/sda6 (/home) unable to fix. I think I have to sort out this problem first.

B.R.
satimis
 
Old 02-24-2007, 12:03 AM   #52
sse007
Member
 
Registered: Nov 2005
Posts: 39

Rep: Reputation: 15
when i looked at your installation log again, i noticed theres a segmentation fault on installing kernel-modules, u may want to check on that one.
 
Old 02-24-2007, 07:03 AM   #53
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Quote:
Originally Posted by sse007
when i looked at your installation log again, i noticed theres a segmentation fault on installing kernel-modules, u may want to check on that one.
Hi sse007,

Code:
Executing install script for kernel-modules-2.6.20_smp-x86_64-1...
install/doinst.sh: line 30:  6405 Segmentation fault      chroot . /sbin/depmod -a >/dev/null 2>/dev/null
# find / -name doinst.sh
# find / -name doinst
Both no printout. I can't locate this file.

I can download the package again and reinstall it. But I can't find md5sum on;
http://ftp.scarlet.be/pub/slamd64/sl.../huge26_smp.s/


Edit:

Looking back on posting #40
There was no warning there on its first installation


B.R.
satimis

Last edited by satimis; 02-24-2007 at 07:06 AM.
 
Old 02-24-2007, 09:59 PM   #54
sse007
Member
 
Registered: Nov 2005
Posts: 39

Rep: Reputation: 15
that is the script in installpkg. Try use pkgtool to install, pkgtool is pretty self explanatory.
 
Old 02-25-2007, 10:14 PM   #55
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Quote:
Originally Posted by sse007
that is the script in installpkg. Try use pkgtool to install, pkgtool is pretty self explanatory.
Hi sse007

# removepkg kernel-generic
# removepkg kernel-modules
both without complaint.


ls -al /boot
Code:
total 4171
drwxr-xr-x  3 root root    1024 Feb 26 01:27 .
drwxr-xr-x 20 root root    4096 Feb 26 09:40 ..
lrwxrwxrwx  1 root root      37 Feb  8 23:14 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
lrwxrwxrwx  1 root root      25 Feb 23 21:23 System.map -> System.map-generic-2.6.20
-rw-r--r--  1 root root 1122219 Sep 30 21:48 System.map-generic-2.6.16.29
-rw-r--r--  1 root root     512 Feb  9 05:55 boot.0200
-rw-r--r--  1 root root     512 Feb 10 00:26 boot.0800
-rw-r--r--  1 root root     512 Feb  8 23:40 boot.0802
-rw-r--r--  1 root root     168 Feb  9 05:55 boot_message.txt
lrwxrwxrwx  1 root root      21 Feb 23 21:23 config -> config-generic-2.6.20
-rw-r--r--  1 root root   52358 Sep 30 21:48 config-generic-2.6.16.29
-rw-r--r--  1 root root    5032 Aug  3  2006 diag1.img
drwx------  2 root root   12288 Feb  8 23:01 lost+found
-rw-------  1 root root   17920 Feb 23 21:28 map
lrwxrwxrwx  1 root root      22 Feb 23 21:23 vmlinuz -> vmlinuz-generic-2.6.20
-rw-r--r--  1 root root 3028097 Sep 30 21:48 vmlinuz-generic-2.6.16.29

removed following packages.
kernel-generic-2.6.20_smp-x86_64-1.tgz
kernel-generic-2.6.20_smp-x86_64-1.tgz.asc
kernel-generic-2.6.20_smp-x86_64-1.txt
kernel-modules-2.6.20_smp-x86_64-1.tgz
kernel-modules-2.6.20_smp-x86_64-1.tgz.asc
kernel-modules-2.6.20_smp-x86_64-1.txt


Redownload them on;
http://ftp.scarlet.be/pub/slamd64/sl.../huge26_smp.s/

Started pkgtool

Installed "kernel-generic-2.6.20_smp-x86_64-1.tgz"
without complaint.

Installed "kernel-modules-2.6.20_smp-x86_64-1.tgz"
Code:
install/doinst.sh: line 30:  4366 Segmentation fault      chroot . /sbin/depmod -a >/dev/null 2>/dev/null
Installation failed.


B.R.
satimis
 
Old 02-26-2007, 06:14 PM   #56
sse007
Member
 
Registered: Nov 2005
Posts: 39

Rep: Reputation: 15
try download the package from another location, there are different locations u can download from slamd64.com under get slamd64.
 
Old 02-26-2007, 10:04 PM   #57
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Quote:
Originally Posted by sse007
try download the package from another location, there are different locations u can download from slamd64.com under get slamd64.
Hi sse007,

Dowload new
kernel-modules-2.6.20_smp-x86_64-1.tgz
kernel-modules-2.6.20_smp-x86_64-1.tgz.asc
kernel-modules-2.6.20_smp-x86_64-1.txt

on
ftp://mirror.vbfx.com/slamd64/slamd6...0/huge26_smp.s

# ls -al /boot/
Code:
total 4171
drwxr-xr-x  3 root root    1024 Feb 26 11:04 .
drwxr-xr-x 20 root root    4096 Feb 27 09:42 ..
lrwxrwxrwx  1 root root      37 Feb  8 23:14 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
lrwxrwxrwx  1 root root      25 Feb 26 11:03 System.map -> System.map-generic-2.6.20
-rw-r--r--  1 root root 1122219 Sep 30 21:48 System.map-generic-2.6.16.29
-rw-r--r--  1 root root     512 Feb  9 05:55 boot.0200
-rw-r--r--  1 root root     512 Feb 10 00:26 boot.0800
-rw-r--r--  1 root root     512 Feb  8 23:40 boot.0802
-rw-r--r--  1 root root     168 Feb  9 05:55 boot_message.txt
lrwxrwxrwx  1 root root      21 Feb 26 11:03 config -> config-generic-2.6.20
-rw-r--r--  1 root root   52358 Sep 30 21:48 config-generic-2.6.16.29
-rw-r--r--  1 root root    5032 Aug  3  2006 diag1.img
drwx------  2 root root   12288 Feb  8 23:01 lost+found
-rw-------  1 root root   17920 Feb 23 21:28 map
lrwxrwxrwx  1 root root      22 Feb 26 11:03 vmlinuz -> vmlinuz-generic-2.6.20
-rw-r--r--  1 root root 3028097 Sep 30 21:48 vmlinuz-generic-2.6.16.29
# rm /boot/config
# rm /vmlinuz
# rm System.map

bash-3.1# ls -al /boot/
Code:
total 4171
drwxr-xr-x  3 root root    1024 Feb 27 10:37 .
drwxr-xr-x 20 root root    4096 Feb 27 09:42 ..
lrwxrwxrwx  1 root root      37 Feb  8 23:14 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
-rw-r--r--  1 root root 1122219 Sep 30 21:48 System.map-generic-2.6.16.29
-rw-r--r--  1 root root     512 Feb  9 05:55 boot.0200
-rw-r--r--  1 root root     512 Feb 10 00:26 boot.0800
-rw-r--r--  1 root root     512 Feb  8 23:40 boot.0802
-rw-r--r--  1 root root     168 Feb  9 05:55 boot_message.txt
-rw-r--r--  1 root root   52358 Sep 30 21:48 config-generic-2.6.16.29
-rw-r--r--  1 root root    5032 Aug  3  2006 diag1.img
drwx------  2 root root   12288 Feb  8 23:01 lost+found
-rw-------  1 root root   17920 Feb 23 21:28 map
-rw-r--r--  1 root root 3028097 Sep 30 21:48 vmlinuz-generic-2.6.16.29
# pkgtool
install "kernel-generic-2.6.20_smp-x86_64-1.tgz"
without complaint.

install "kernel-modules-2.6.20_smp-x86_64-1.tgz"
Code:
install/doinst.sh: line 30:  3519 Segmentation fault      chroot . /sbin/depmod -a >/dev/null 2>/dev/null
Still failed

Browsing the download site
Code:
Up to higher level directory
File: System.map.gz 	288 KB 	02/10/2007 	10:43:00 AM
File: bzImage 	3043 KB 	02/10/2007 	10:43:00 AM
File: config.gz 	17 KB 	02/10/2007 	10:43:00 AM
File: kernel-generic-2.6.20_smp-x86_64-1.tgz 	3317 KB 	02/10/2007 	10:48:00 AM
File: kernel-generic-2.6.20_smp-x86_64-1.tgz.asc 	1 KB 	02/10/2007 	10:48:00 AM
File: kernel-generic-2.6.20_smp-x86_64-1.txt 	1 KB 	02/10/2007 	10:48:00 AM
File: kernel-modules-2.6.20_smp-x86_64-1.tgz 	12312 KB 	02/10/2007 	10:43:00 AM
File: kernel-modules-2.6.20_smp-x86_64-1.tgz.asc 	1 KB 	02/10/2007 	10:43:00 AM
File: kernel-modules-2.6.20_smp-x86_64-1.txt 	1 KB 	02/10/2007 	10:43:00 AM
What will be following files for?
Code:
File: System.map.gz 	288 KB 	02/10/2007 	10:43:00 AM
File: bzImage 	3043 KB 	02/10/2007 	10:43:00 AM
File: config.gz

B.R.
satimis
 
Old 02-27-2007, 02:18 PM   #58
sse007
Member
 
Registered: Nov 2005
Posts: 39

Rep: Reputation: 15
i think when u install kernel-generic, it'll copy those 3 files to /boot. Looks like segmentation fault caused by "chroot . /sbin/depmod -a >/dev/null 2>/dev/null" in script file doinst.sh. Try delete directory /lib/modules/2.6.20 and install again.
 
Old 02-28-2007, 05:45 AM   #59
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
Sorry to see you've had so many problems getting slamd64 up and running, I confess I never had these issues even with RC versions of slamd64. Anyway not having problems does not help solve yours ...

So, first of all some generic information for you:

1. nVidia drivers compile a kernel module, which clearly must reside *per kernel*. This is something you can live without until such time as the rest of the system is stable ... which means no errors on installs.

2. In old versions of slamd64 I had problems with the installer on the cd / dvd; it would segfault pretty randomly installing packages and so on. It looks like you're using the installer on your actual install, however, so this may not be applicable. You can use pkgtool on the slackware cds (cd 1 for "rescue disk") to install packages for slamd64.

As pertaining to your current problems:

The fact that you are having problems, even on a fresh installation, and never the same problem twice is leading me to be concerned about the quality of your hardware. Specifically, your hard drive. Failure to boot a kernel should not leave the partitions in a state that requires them to be fsck'd. Download the Ultimate Boot CD and run the disk checks necessary for your harddrive (make sure you get the manufacturer correct), you may also wish to perform a low-level format to correct any sector problems you may have aquired.

http://www.ultimatebootcd.com/

I encourage you *not* to do anything with the rest of this post until you have ascertained your hardware is not faulty.

Files
System.map.gz: Part of your kernel, really. See here http://www.dirac.org/linux/system.map/ for a complete discourse.
bzImage: Your kernel image file.
config.gz: A compressed version of the .config used to make the kernel.

The problems with installing multiple kernel from slackware packages

It's easy to install packages, but unless you know what symlinks to remove, you will get bitten when installing multiple kernels from packages.

As you've already found out, most of them symlink to /boot/vmlinuz from things like /boot/vmlinuz-generic-2.6.12 and so on. Ensuring you never use these symlinks in lilo is the best way of dealing with the problem.

You will find lilo doesn't like long filenames, so you may be best off symlinking your long kernel names like this:

ln -s /boot/vmlinuz-generic-2.6.12 /boot/vmlinuz-1
ln -s /boot/vmlinuz-smp-2.6.12 /boot/vmlinuz-2

Whatever your scheme, you would be wise to ensure System.map matches your kernel prefix, like so:

/boot/vmlinuz-generic-2.6.12
/boot/System.map-generic-2.6.12

/boot/vmlinuz-smp-2.6.12
/boot/System.map-smp-2.6.12

If you've symlinked the kernels above and are using them in lilo, you should symlink your System.map files as well, for example:

ln -s /boot/System.map-generic-2.6.12 /boot/System.map-1

In closing ...

Check your hardware. If that's faultless, try reading things like /var/log/messages and dmesg to make sure there's no problems there. My suspicion is that you had a bad install due to bad sectors, and now your kernel is struggling to fix these problems that have occured with your FS on the fly (by having lots more bad sectors, or by the ext3 module being corrupted on install), all the while you're trying to install new stuff on a shakey foundation.

The steps to return to your desired state are very, very simple from a new install.

1. Format the whole drive, use the Slackware disk or a live CD to be confident there are no problems with the slamd64 one.
2. Repartition & reformat, again use a different disk.
3. Install from slamd64 media - do not activate swap, do this manually later - install whichever kernel you booted from - have lilo install itself to the MBR (if this is the only install, otherwise I trust you know where to put it).
4. Install the modules & smp kernel from packages, then hack the symlinks in /boot if necessary, tweaking lilo appropriately to have both kernels appear.

None of this should trigger segfaults, and if it does, there is some other problem than poorly typed commands.

Hope this helps,
- Piete.
 
Old 03-03-2007, 10:57 AM   #60
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Quote:
Originally Posted by sse007
i think when u install kernel-generic, it'll copy those 3 files to /boot. Looks like segmentation fault caused by "chroot . /sbin/depmod -a >/dev/null 2>/dev/null" in script file doinst.sh. Try delete directory /lib/modules/2.6.20 and install again.
Hi sse007

# ls -al /lib/modules/
Code:
total 16
drwxr-xr-x 4 root root 4096 Feb 27 10:50 .
drwxr-xr-x 5 root root 4096 Feb  9 19:16 ..
drwxr-xr-x 3 root root 4096 Feb 21 17:36 2.6.16.29
drwxr-xr-x 3 root root 4096 Feb 20 21:51 2.6.18
the directory "2.6.20" does not exist.

I think my problem was caused right from the begining by "installing kernel-2.6.20", with its package download on http://kernel.org/. Actually smp is still running on kernel-2.6.16.29. fred named the new kernel after recompilation as kernel-generic-smp-2.6.20 which makes some confusion.

Now I have deleled kernel-2.6.20. How to reinstate slamd64-11.0 to its original state? It needs consideration.

B.R.
satimis

Last edited by satimis; 03-03-2007 at 10:58 AM.
 
  


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
SUSE USB installation boot up fails dep. on IDE or SATA oozie Linux - Kernel 0 10-23-2006 06:00 PM
Slamd64 RC4 won't boot? cheater1034 Slackware - Installation 7 03-02-2006 11:24 PM
Mandrake 10.0 Community installation - boot floppy fails at reckognizing SCSI CDROM nixguide Mandriva 5 06-03-2004 12:38 PM
Installation success, boot load fails nimonm Linux - Newbie 2 01-12-2004 10:43 PM
RH9 installation fails on boot JezzerP Linux - Distributions 1 07-06-2003 07:20 AM


All times are GMT -5. The time now is 05:39 AM.

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