SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i was fetching the new updates from Slackware, using slackpg upgrade-all, then suddenly my laptop turned off due to overheat and interrupted my update, it was in the part where the kernel updates were being fetched.
then after that i rebooted my Slack and after the part where the lilo loads Linux, it reboots..
is there a way to fix my kernel configuration?
or is there a way to access my hard drive files because i need to get some files there before i recompile my Slackware again.
The easiest way would be to use Slackware install media to boot the system as if you were going to install.
After you get to the login then from the cli (command line);
~#mkdir /slacktemp #temporary mount point
~#mount /dev/your_device /slacktemp #device you installed to
~#chroot /slacktemp #change to yours
~#cd /slacktemp/etc #change to directory with lilo.conf
~#vi lilo.conf #edit lilo.conf, if need be
~#lilo -v -t -b /dev/your_device #sda, hda this will only test
~#lilo -v -b /dev/your_device #this will write to your boot device
You can 'man commands' in the above example to get a full understanding of the commands and options. Once lilo has been updated then reboot.
It would help to know some more about your setup.
Were you using the generic kernel with an initrd prior to attempting the upgrade?
If so, it is possible that you have upgraded the kernel but not the associated kernel modules.
Or, it is possible that you have installed the kernel-modules package but have not built the initrd to suit.
Can you boot from the install disk, get to the login and mount the Slackware partition?
sample output for 'fdisk -l'
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xfdc4297b
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 5125 41164800 7 HPFS/NTFS
/dev/sdb2 5126 5386 2096482+ 82 Linux swap
/dev/sdb3 5387 5781 3172837+ 83 Linux
I believe the OP typed the sample output and transposed the blocks count for 'bytes'. To the OP, notice the disk information at the top of the output for the 'fdisk -l'. Then look at the start & end with the Blocks count.
My suggestion for the OP would be restore from backup. What no backup? If the install is new then possibly gamble and attempt a repair by using the install disk then perform a 'fsck' on the filesystem for '/dev/sda1'.
This shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the BIOS. Definitely check to see if the disk is seen by the BIOS first (and that the BIOS detail is complete).
As noted above, check your BIOS to see if indeed the drive(s) are recognized.
Boot using the Install disk then please post the un-edited output for 'fdisk -l' (lower case l not 1(one).
Also post your 'lilo.conf' file.