Trying (in vain, I might add) to install Slack alongside Ubuntu

nohopeforme · 10-26-2019, 09:45 PM

Quote:

Originally Posted by colorpurple21859

so where did it fail at disk not found of post30 , or the kernel panic of your first post?

Ok, here we go. In my grub list at bootup, I have entries for:

Ubuntu
Advanced options for Ubuntu
Slackware 14.2 on /dev/sdc3 (my original slackware install)
Advanced options for Slackware 14.2
Slackware (this last entry is from where another member had me add the menu entry to my custom_40 file).

When I added noacpi to the first slackware entry, it tried to boot but errored out with the end trace line at the bottom

When I added noacpi to the advanced options for Slackware, it did the same thing.

When I added noacpi to the slackware entry that I added to the custom_40 file, grub informed me:
Booting a command list
error: hd2,gpt3 not found. Press any key to continue...

All of this was done with no usb drive attached.

colorpurple21859 · 10-26-2019, 10:01 PM

Quote:

When I added noacpi to the first slackware entry, it tried to boot but errored out with the end trace line at the bottom

This is the menu entry I was wanting you to add the noacpi option. try adding nomodeset and vga=normal along with the noacpi
what are the specs of your system, processor, graphics card, amount of memory?

nohopeforme · 10-26-2019, 10:13 PM

Quote:

Originally Posted by colorpurple21859

This is the menu entry I was wanting you to add the noacpi option. try adding nomodeset and vga=normal along with the noacpi
what are the specs of your system, processor, graphics card, amount of memory?

so, let me try and understand this correctly. Would that be something like this:

linux /boot/vmlinuz root=/dev/sdc3 noacpi, nomodeset, vga=normal

or the same syntax, only with spaces and no comma's? (I've never done any of this before)

colorpurple21859 · 10-26-2019, 10:18 PM

yes, spaces no commas

nohopeforme · 10-26-2019, 10:32 PM

Quote:

Originally Posted by colorpurple21859

yes, spaces no commas

Nope, errored out in the same place :-/

colorpurple21859 · 10-26-2019, 10:39 PM

Can you boot into the installed system from the usb?

nohopeforme · 10-26-2019, 10:43 PM

Quote:

Originally Posted by colorpurple21859

Can you boot into the installed system from the usb?

Don't fall over from laughing but I'm not quite sure what you mean :-/

colorpurple21859 · 10-26-2019, 10:52 PM

from the slackware install usb/dvd there is an option at the boot menu to boot an installed system

nohopeforme · 10-26-2019, 10:59 PM

Quote:

Originally Posted by colorpurple21859

from the slackware install usb there is an option at the boot menu to boot an installed system

That, I don't know. It'll have to be tomorrow's project. Unfortunately, I gotta run. I'm the last one to say it, but I think this has something to do with me having an EFI system. Of course, 95% of what I've read on it is above my level of understanding. The main reason I say that is that I don't think I would have all the necessary folders installed if it hadn't installed to the partition I set up for it. It seems I'm not the only one with slack/efi issues and surely, if it was something besides that, *something* you've had me try would have most certainly worked out. At least that's what I tell myself, lol

colorpurple21859 · 10-26-2019, 11:07 PM

This issue has nothing to do with efi. The efi only involves boot loaders. Your problem is after the vmlinuz is called up. A hardware issue of some sort. I'm suspecting that a driver is included in the install usb kernel that isn't included in the kernel of your installed system, otherwise you would have had the same problem with the install usb.

BW-userx · 10-27-2019, 01:03 PM

40_custom setup:

Look in your slack boot

Code:

$ ls -la /boot
lrwxrwxrwx  1 root root      20 Oct 20 18:35 vmlinuz -> vmlinuz-huge-4.19.80
lrwxrwxrwx  1 root root      23 Oct 20 18:35 vmlinuz-generic -> vmlinuz-generic-4.19.80
-rw-r--r--  1 root root 6088576 Oct 17 17:50 vmlinuz-generic-4.19.80
lrwxrwxrwx  1 root root      20 Oct 20 18:35 vmlinuz-huge -> vmlinuz-huge-4.19.80
-rw-r--r--  1 root root 9590656 Oct 17 17:49 vmlinuz-huge-4.19.80

try picking one of them instead of the two in red.

Code:

instead of this
linux /boot/vmlinuz  root=/dev/sdc3 
try this
linux /boot/vmlinuz-huge  root=/dev/sdc3

have you given that a try yet? Just have it take the default huge kernel to boot it.
https://docs.slackware.com/slackbook:booting

colorpurple21859 · 10-27-2019, 04:14 PM

find out what the PARTUUID is of the partition slackware is on by

Code:

sudo blkid

in ubuntu.
edit your slackware grub menu to something like this

Code:

linux /boot/vmlinuz  root=PARTUUID=</dev/sdc3 partuuid number>

Will look something like this linux /boot/vmlinuz root=PARTUUID=9a1589a8-4644-4e46-87fa-468944670a27 see it that helps

nohopeforme · 10-27-2019, 06:43 PM

Quote:

Originally Posted by BW-userx

40_custom setup:

Look in your slack boot

Code:

$ ls -la /boot
lrwxrwxrwx  1 root root      20 Oct 20 18:35 vmlinuz -> vmlinuz-huge-4.19.80
lrwxrwxrwx  1 root root      23 Oct 20 18:35 vmlinuz-generic -> vmlinuz-generic-4.19.80
-rw-r--r--  1 root root 6088576 Oct 17 17:50 vmlinuz-generic-4.19.80
lrwxrwxrwx  1 root root      20 Oct 20 18:35 vmlinuz-huge -> vmlinuz-huge-4.19.80
-rw-r--r--  1 root root 9590656 Oct 17 17:49 vmlinuz-huge-4.19.80

try picking one of them instead of the two in red.

Code:

instead of this
linux /boot/vmlinuz  root=/dev/sdc3 
try this
linux /boot/vmlinuz-huge  root=/dev/sdc3

have you given that a try yet? Just have it take the default huge kernel to boot it.
https://docs.slackware.com/slackbook:booting

This is what my custom_40 currently looks like

Code:

1 #!/bin/sh                                                                                                     
  2 exec tail -n +3 $0
  3 # This file provides an easy way to add custom menu entries.  Simply type the
  4 # menu entries you want to add after this comment.  Be careful not to change
  5 # the 'exec tail' line above.
  6 
  7 menuentry 'Slackware'{
  8 set root='(hd2,gpt3)'
  9 linux /boot/vmlinuz-huge-4.4.14 root=/dev/sdc3
 10 }

It looks almost the same. I wouldn't think the trailing -4.4.14 would make a difference. Then again, I'm not the swiftest when it comes to syntax in linux.
~

BW-userx · 10-27-2019, 07:09 PM

Quote:

Originally Posted by nohopeforme

This is what my custom_40 currently looks like

Code:

1 #!/bin/sh                                                                                                     
  2 exec tail -n +3 $0
  3 # This file provides an easy way to add custom menu entries.  Simply type the
  4 # menu entries you want to add after this comment.  Be careful not to change
  5 # the 'exec tail' line above.
  6 
  7 menuentry 'Slackware'{
  8 set root='(hd2,gpt3)'
  9 linux /boot/vmlinuz-huge-4.4.14 root=/dev/sdc3
 10 }

It looks almost the same. I wouldn't think the trailing -4.4.14 would make a difference. Then again, I'm not the swiftest when it comes to syntax in linux.
~

it is sym linked to /boot/vmlinuz-huge or should be. You an look to be sure. ls -la /boot/vmlinuz-huge

if you look at the my post on it and you'll see the arrow that indicates a symlink

Code:

vmlinuz-huge -> vmlinuz-huge-4.19.80

I'm not sure why you are trying gpt3
have you tried.

Code:

set root='(hd2,3)'
linux /boot/vmlinuz-huge-4.4.14 root=/dev/sdc3

nohopeforme · 10-27-2019, 09:38 PM

Quote:

Originally Posted by BW-userx

it is sym linked to /boot/vmlinuz-huge or should be. You an look to be sure. ls -la /boot/vmlinuz-huge

if you look at the my post on it and you'll see the arrow that indicates a symlink

Code:

vmlinuz-huge -> vmlinuz-huge-4.19.80

I'm not sure why you are trying gpt3
have you tried.

Code:

set root='(hd2,3)'
linux /boot/vmlinuz-huge-4.4.14 root=/dev/sdc3

I did try

Code:

set root='(hd2,3)'
linux /boot/vmlinuz-huge-4.4.14 root=/dev/sdc3

and it told me error: Could not find '(hd2,3)'. As to the why did I use the gpt question, I saw that all the other menu entries used gpt before the partition #, so I thought I would try that. Here are pics of my Slackware menu entries that 30_0s-prober automatically installed and the listing of my slackware /boot directory.