kernel panic with ntfs slackware 14

donnestorin · 09-21-2013, 11:54 PM

I can not since returned kernel panic

allend · 09-22-2013, 03:45 AM

So your problem is that you cannot successfully boot your Slackware install.

This suggests a problem with your bootloader setup but we would need the output requested in post#11.

gnashley · 09-22-2013, 04:15 AM

Slackware can't be installed to an NTFS partition.

Didier Spaier · 09-22-2013, 04:43 AM

You will need to boot with your installation media.

After logging in as root, don't run setup again but issue following command:

Code:

fdisk -l

take a note of the output and report it here.

You can also tell how these partitions are used.

Consider the partitions that have Linux as System (as shown in fdisk -l) and do this (I assume /dev/sda1 has System Linux, adapt accordingly for the other ones case occuring):

Code:

mkdir /P1
mount -t auto /dev/sda1 /P1
ls -1 /P1

So you will know what's in it. I assume you have a / (root) partition for Slackware, maybe another one for /home.

If you report the layout you find we will be able to help you.

Also if you find the root partition, let's say as /P1 (with /etc in it), please do

Code:

cat /P1/etc/fstab
cat /P1/etc/lilo.conf

and tell us what you find.

To avoid you the hassle of copying all that on a paper you could also mount an USB key. Plug it in, assuming it is recognized as /dev/sdb1 (you can check with cat /proc/partitions), mount it:

Code:

mkdir /key
mount -t auto /dev/sdb1 /key

After that you can copy the file to the key, e.g.

Code:

cp /P1/etc/fstab /key/fstab.txt

The same way you can copy the results of a command, e.g.

Code:

fdisk -l > /key/fdisk.txt
ls -l /P1 > /key/lsP1.txt

When copying files is over, don't forget to umount the key:

Code:

umount /key

EDIT Again, It seems that I like to complicate things uselessly - just boot your system using the DVD as told in the first screen of the installer to get the info we need

guanx · 09-24-2013, 03:36 AM

Quote:

Originally Posted by gnashley

Slackware can't be installed to an NTFS partition.

You can load Linux from NTFS with LILO, though this is not a good idea due to lack of POSIX permissions and etc..

gnashley · 09-24-2013, 11:16 AM

You might be able to load the linux kernel from NTFS, but no distro is going to be able to boot from an NTFS filesystem -except for one which loop-mounts an FS image from NTFS.

guanx · 09-24-2013, 12:31 PM

Quote:

Originally Posted by gnashley

You might be able to load the linux kernel from NTFS, but no distro is going to be able to boot from an NTFS filesystem -except for one which loop-mounts an FS image from NTFS.

As long as you can load the kernel image you can have a complete system. I've made a demo a few years ago:

Code:

chmod +x bbsplay.txt
./bbsplay.txt ntfs_slack.log

gnashley · 09-24-2013, 01:42 PM

Yeah, well you got me there -I meant an installed system. Sounds pretty safe to assume the OP is not booting a fat kernel with a huge intrdfs inside...

guanx · 09-24-2013, 03:09 PM

Quote:

Originally Posted by gnashley

...
Sounds pretty safe to assume the OP is not booting a fat kernel with a huge intrdfs inside...

This demo is using the official "generic" kernel. LILO loaded both the bzImage and the initrd from NTFS (LILO does not care about the FS actually).

However, I agree that the OP is unlikely doing this way.

WhiteWolf1776 · 09-25-2013, 01:03 PM

Calling Troll on this guy... he did similar in the G+ slackware group... helping just lead to frustration as the answers kept changing and the story got more and more bizarre... sry, not buying this is a real problem.

Just like on G+, he never answers your questions with anything useful, never answers them the same way twice, and never gives you any idea of what is really going on... you could get more information from emacs psychoanalyze scripts.