SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slack64-Current, Windows 11, EndeavourOS
Posts: 97
Rep:
Kernel panics on boot
Hello again...
I am not having much luck getting Slack64 installed on this rig.
Previous issues of dual booting Win7 x64 + Slack64 14.0 on two SSD's was resolved after preventing M$ from creating the "System Reserved" partition installing W7.
Now I am getting Kernel Panics when trying to boot into Slack.
Code:
Kernel Panic - not syncing: No init found
Pid: 1, comm: swapper/0 Not tainted 3.2.29 #2\
Call Trace:
I've found that recent kernels identify hdd's, external hdd's, usb's, sdd's (and whatever else you may have "plugged-in") differently with each boot.
Hence, when you first installed Slackware64, your boot hdd may have been /dev/sdb, yet on a reboot, it's /dev/sdc, or /sdf...basically, one can't be sure what /dev/sdx your boot partition may be (this also affects your fstab.)
To expound somewhat on what Didier has suggested, the solution is to use /dev/disk/by-(label/uuid) in both your lilo.conf and fstab, in conjunction with an initrd.
Bear in mind that I'm no expert, so my experience may be anecdotal....
#LILO configuration file
#
append=" vt.default_utf8=0"
boot=/dev/sda
#
bitmap = /boot/slack.bmp
#
bmp-colors = 255,0,255,0,255,0
#
bmp-table = 60,6,1,16
#
bmp-timer = 65,27,0,255
#
prompt
#
timeout=1200
#
change-rules
reset
#
vga = normal
#
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# End
# Linux bootable partition config beings
image = /boot/vmlinuz
root = /dev/sde1
label = Linux
read-only
# End
Also, I did not make an initrd, & did not see any reason to edit lilo. This is my first dual boot of Slack coming from Debian "lenny". So I am in layman's terms a noob.
so that I can see Windows from Linux, but in lilo.conf I have :
Code:
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends
So I can boot Windows from its system partition.
In any case I would boot Linux from the Linux root partition, not from the MBR. To do that, just replace in your /etc/lilo.conf
Code:
boot=/dev/sda
with
Code:
boot=/dev/sde1
and make /dev/sde1 bootable with fdisk or cfdisk. Then run 'lilo -t -v' and if all goes well 'lilo'.
Or, run 'liloconfig' as root in the 'expert' mode. Of course then do not choose the 'Recycle' option, but 'Begin' then 'Linux' then 'Windows' then 'Install' and, when asked, choose to put LILO in your Linux root partition. Still, you will have to make that partition bootable with fdisk or cfdisk.
I really don't know why you prevented Windows 7 to create a system partition, this doesn't hurt.
I also prevented windows (XP) to create a system partition. I don't trust window$ to play nice when it has been violated by linux. If I ever need to access the windows partition from linux I can always mount it (ro) myself.
In my understanding, this has nothing to do with that. You can let Windows have its own system partition and never access it from Linux (or only read only, choosing or not to put a line in /etc/fstab for that. If it detects a Windows partition, Slackware's installer asks what you want to do with that. You will answer 'nothing' for the system partition and either 'nothing' or 'I want to be able to access it from Linux' for the other. In the latter case the installer asks you how it should set the permissions in /etc/fstab.)
Besides that, would I think Windows be that dangerous for Linux, I would simply wipe it out completely.
Anyhow I realize that we are not addressing captkrill's question with that discussion, so let's go back to the topic.
Last edited by Didier Spaier; 02-16-2013 at 01:57 AM.
Seems to me the windows is a non issue at this point. Considering lilo is functioning correctly and he can pick either windows or Slack. Windows boots but the Slack kernel panics. His motherboard is listed as MB: ASUS P8Z68-V Pro.
Does anyone know if vmlinuz-huge-3.2.29 has full support for this board? Or perhaps he needs to build a newer kernel?
It might be difficult to build a new kernel if captkrill can't boot into linux (and a bit ambitious to boot). Assuming that captkrill is correctly loading the huge kernel and getting nowhere, an alternative might be to download the 3.7.1 kernel from Slackware Current and try that instead.
Assuming that captkrill is correctly loading the huge kernel and getting nowhere, an alternative might be to download the 3.7.1 kernel from Slackware Current and try that instead.
I agree. Googling "ASUS P8Z68-V Pro linux kernel" returns a bunch of bad experiences, but some say that a bug was fixed using a recent kernel.
EDIT. No, don't reuse the kernel from Slackware-current as is. If you want to try that kernel, you will have to compile it yourself, see post #13.
Last edited by Didier Spaier; 02-16-2013 at 03:50 PM.
Reason: EDIT added
Distribution: Slack64-Current, Windows 11, EndeavourOS
Posts: 97
Original Poster
Rep:
Ok I will try and change booting to the huge kernel.
In the meantime, as I am away from my home PC. Is there anywhere I can download a stable slack-current ISO just to have that as a possible fix if changing the boot does not work?
Also, would building a slack64 ISO with kernel 3.7.8 be a possible solution as well?
PS.
Just to give some insight on my installation method.
The reason that I prevented Windows from creating the system reserved partition is because it was the only way that my current set up dual boot with dual drives would boot lilo, a non working slack and windows. Without doing so, no matter the install method, Lilo would not load and thus not be able to get into windows or a non-working Slack.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.