Major noob trying to shoot for a dualboot ubuntu/slack setup. Not even quite sure how to form this post, lol. As far as I can tell, I did my partitions correctly. I didn't choose lilo (or elilo) for the bootloader. I'm basically clueless with grub, but I'm trying to make sense of the whole booting with grub scenario. I'm fairly certain whatever the problem is, is something I did or didn't. I just can't seem to figure out what that might be. I guess if worse comes to worse, I could just wipe my ubuntu and dedicate the whole drive to slack, but I really don't want to make that leap yet. Still too much of a noob for a dedicated slack drive, lol. The only thing I know for sure, is I get about 4 seconds into the boot process and then it just sits there. There are a couple slowpath warnings and one panic error but for all intents and purposes, I'm not sure what I'm looking at. I'm enclosing a couple pics that might help point out what I could be doing wrong. Then again, who knows? At any rate, I made this my last resort as it seems I'm not smart enough to figure this one out on my own :-/

Attached Thumbnails

     

is ubuntututu efi or Mbr installed?

If slack is efi , use this check off list
https://docs.slackware.com/howtos:sl...based_hardware
to be sure you have it set up properly.
I use MBR so yeah... I'm stretchy on the efi set up here.

Yeah, it's efi. Thanks for the link, I'll be checkin that out :-)

I assume Ubuntu installed GRUB in your EFI system partition. If I were you, I'd stick to that as your boot loader for the time being (and I say that as someone who actually dislikes GRUB quite strongly). Always control GRUB from a single system to avoid complications, and again I recommend using Ubuntu for that initially. So after installing Slackware, you should reboot into Ubuntu and run update-grub from there. That should ensure that GRUB behaves consistently.

What kernel are you using for Slackware? If it's the recommended generic kernel, then you will also need an initrd image. Unusually Slackware doesn't create one automatically; you're expected to do that yourself using the mkinitrd script. There's a useful additional script in /usr/share/mkinitrd that will examine your hardware and tell you what options you need to give mkinitrd in order to get an image that contains the essential driver modules. Alternatively, you could install the huge kernel which contains all the drivers. I notice that one of your pics shows a kernel panic, and the usual cause of that is inability to access the root partition because the necessary drivers are missing.

I'm impressed that you want to go directly from Ubuntu to Slackware. I warn you that there will be culture shock. Ubuntu holds your hand all the time and Slackware doesn't. But you'll learn a lot more from Slackware.

That's just it. I can't get slack to install, lol. As to the culture shock, I can relate. I fooled with slackware a few years ago and I'm well aware that it's a whole different beast. That's one of the main reasons I want to install it (other than I'm a slacker extraordinaire). I've driven over the road for a living for 25 years but got injured on the job a year ago and haven't been able to work since. That's why I'm delving back into linux. I figure since I can't do much else, I might as well try to learn something :-/ I can't seem to make it work with either the generic kernel or the huge kernel.

try going MBR get a live os, one that has gparted included in the iso, I think linux mint has it, some of the manjaro does in there live os.

use gparted to create a new partition table (msdos=mbr) change your bios to legacy boot (make sure your BIOS has that which it should, and your drive is 2TB or lesser). then install it MBR style. no need to finagle the efi files to make them the way they're suppose to be then move them to where they're suppose to be in order for it to actually work.

I've looked in my bios and it doesn't show any options for booting in legacy mode. That said, I've read where if your current install is efi, then subsequent installs need to be efi as well. I'm still googling and reading everything I can find, though. Sooner or later, I'll throw something at the wall and maybe it'll stick, lol

give it a new partition table which btw wipes the hdd clean, making whatever in this case dos = MBR,
that is why I said check bios for other then efi aka legacy, mine had both separately or together. HP 840 g2;

though you say your BIOS does not afford you the option of one or the other or both together. sorry.

from when I did the efi in slack and a few other distros, I remember I had to if I remember correctly, boot a live mount the drive then get into the boot partition find the files and rename them while moving them to where they actually needed to be to get it to work but the particulars I do not remember, and I am not feeling like wiping my install to go though all of that to get the steps I figured out on the fly to get that to work.

Oh yes in mine it gave me an option on boot that allowed me to search the partitions to find the files, that is how I got to see what they were named.

just find out the exact file names that slack is suppose to be to boot, then find where they are being stored and where they are suppose to be and what they the move them while renaming them then whatever else with grub.

that is as much as I can say because I did it one step at a time figuring it out as I went using the options I had at my disposal.

I really don't want to wipe the drive. I've got an ubuntu install on here I can't afford to lose. Just call me the googling fool, lol. Appreciate the feedback, though :-)

yeah I know, just explaining and that is why I told you my experience in finding where the files are at and having to rename them and put them where they are suppose to be, so it will work and with two or more distros. I just do not remember the particulars, is all.

I'm pretty sure you have a legacy mode there somewhere but some uefis make it difficult to find. It's often disguised as "csm" (compatibility support module). But you shouldn't mix modes; that's very dangerous. If you have Ubuntu installed in uefi native mode and you want to keep it that way, then you should use native mode for Slackware as well.

You don't make it clear what boot are you having trouble with: the installation CD or the installed system. If it's the Slackware installation disc, try booting with another CD. Your Ubuntu live disc will do. If it boots successfully, then you have a bad Slackware disc and need to make another one. If it's the installed system, then I still think you need an initrd. You can make one within Slackware by chrooting in from your Ubuntu system, even if Slack itself won't boot.

at the grub menu, highlight the slackware entry, press e for edit.
on the line that starts with linux if there is a "root=UUID=......." change to root=/dev/sdc3, press ctl-x or f10 to boot.

If this works, in Slackware open a terminal as root
run the mkinitrd command that is generated.
reboot into ubuntu, rerun update-grub

another way
as root in ubuntu edit /etc/grub.d/40_custom with the following entry and run update-grub

I tried the 2nd option of editing the 40_custom file and here are the results. The grub listing didn't have the slackware entry on the bottom before I tried your suggestion. When I chose it, I got the error shown here. I'm going to remove the entry to the 40_custom file and try your 1st suggestion. The help is very much appreciated :-) (shoot...my pics didn't show up, lol)

Ok, once again..with pics. As I posted prior, I edited the custom_40 file and the slackware entry on the bottom wasn't there before I did so. When I chose said bottom slackware entry, I received the error shown in the pic...which I hope shows up this time :-/ (and still no pics. Not sure why they aren't loading)

this is what I had to use once,
you need to work out your partition the root is on on your system.

not sure what sd in on that other one, but the /dev/sdc is a oops forgot partition number.