Slackware 14.1 won't boot on thinkpad t61
I installed 14.1 from dvd over a fresh windows 7 installation. I used one partition for boot and one for root. The installation went fine. lilo works fine and can boot windows without problem. But when I try to boot slackware I get what I assume is a kernel crash. I get a message like:
[4.1233] ret from kernel thread end trace I have had slackware 14 on the same computer without problems. The only thing I changed is replacing the harddrive. I logged in via dvd, mounted root and looked at the logs in /var/log but they were all empty. How do I figure out whats wrong? |
Looks strange. I have a T61 too and no issue booting a freshly installed Slackware64-14.1 (alongside Windows7 and Slackware-14.0).
I don't use a separate partition for /boot though (by the way, what is the need for that?), only one partition for /. To investigate further, please launch the installer again, and once logged in as root don't run 'setup' but please type "fdisk -l" and "cat /proc/partitions" and report the results here. Also, you can mount your Linux / partition as /mnt and post output of "cat /mnt/etc/fstab". Output of "cat /mnt/etc/lilo.conf" could be useful as well. You could save all results on a mounted USB stick, for instance. |
Quote:
|
Quote:
Niki |
Ok, here is the requested info. I usually boot from a separate partition so that I have the option to totally wipe the root partition when upgrading without affecting other os:es.
Edit: I installed 32 bit slackware. Code:
fdisk -l (sdb is just my usb stick) Code:
cat /proc/partitions: Code:
cat /mnt/etc/fstab: Code:
cat /mnt/etc/lilo.conf: |
Not sure of my answer (I never used such a setting), but I do find a few things questionable in you settings.
|
I do want to put bootsector on MBR. But I want /boot on a separate partition. So mbr points to /boot partition which in turns boots and mounts root.
The boot= parameter in lilo.conf specifies where to install MBR. According to lilo.conf manual: boot=<boot-device> Sets the name of the device (e.g. a hard disk partition) that contains the boot sector. I think that the root= should point to the boot partition but I'm not sure. Where should it point when root and boot are separated? |
When /boot and / are separated the root= parameter has to point to the /-partition. At the point the variable is evaluated the kernel is already loaded and the /boot-partition is not needed anymore. This parameter tells the kernel where to find the /-partition. Since the kernel can't find init in your /boot partition it panics. Set that to sda6 instead.
Regarding the boot= parameter, it doesn't matter at all if it points to the /boot or /-partition. Different topic, but also relevant: You use a disk with physical sector size of 4KB, but your partition layout is not aligned to that (as fdisk tells you with its "Partition X does not start on physical sector boundary.". This can have serious impacts on performance, especially write performance. This misaligned partition layout usually happens when older versions of fdisk are used (for example that from Windows XP or older Linux distributions), or if you have used cfdisk on modern Linux distributions. I recommend to always use modern versions of fdisk or (g)parted instead to partition the disk, they align the layout by default. |
I followed TobiSGD's advice and changed the root= partition to the actual root, and it worked!
Regarding partitioning I have another question here, but I think it's better to ask it in a separate thread. |
All times are GMT -5. The time now is 09:06 AM. |