| Slackware - Installation This forum is for the discussion of installation issues with Slackware. |
| 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
01-30-2025, 03:55 PM
|
#16
|
|
Member
Registered: Dec 2003
Distribution: Slack 15-Current
Posts: 375
Original Poster
Rep: 
|
Quote:
Originally Posted by camorri
Since there is a question of is the partitioning mbr or gpt. You can tell if you run the command fdisk -l.
Here is the output of the command on a mbr partitioned disk.
Code:
root@alienware:~# fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WD Blue SA510 2.
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd3c5d4d8
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 104859647 104857600 50G 83 Linux
/dev/sda2 104859648 130025471 25165824 12G 82 Linux swap
/dev/sda3 130025472 976773167 846747696 403.8G 83 Linux
Notice the Disklabel type: dos; this is a mbr partitioning. If it is gpt it will say gpt. Since I haven't run Ubuntu inwell over 10 years, I can not say what that install might have done to your partitioning. If it is gpt, that will cause issues as far as I know.
At this point if you deide to re-install, delete the partitions, and re-partition the drive as mbr (dos). Then re-install. |
When I get home I will indeed do so, but a question.. Does slackware 15 -current "resolve" this issue? |
|
|
|
|
01-30-2025, 04:05 PM
|
#17
|
|
LQ 5k Club
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,505
|
What issue are you referring to?
I have 2 installs of current, both on GPT partitioned disks. I have not installed current on a DOS partitioned drive. lilo will not work with a gpt disk, grub will. I use e-lilo on my gpt partitioned systems.
|
|
|
|
|
01-30-2025, 04:10 PM
|
#18
|
|
Member
Registered: Dec 2003
Distribution: Slack 15-Current
Posts: 375
Original Poster
Rep:
|
Quote:
Originally Posted by camorri
What issue are you referring to?
I have 2 installs of current, both on GPT partitioned disks. I have not installed current on a DOS partitioned drive. lilo will not work with a gpt disk, grub will. I use e-lilo on my gpt partitioned systems.
|
I think you sort of answered it.. I am not having a "slack "issue"" but rather it may probably be trying to install Lilo using a drive that is GPT. So when I get home I will verify it is not [or is] GPT and change to MBR. But let me ask you this, if it IS gpt, should I not just convert to grub? |
|
|
|
|
01-30-2025, 04:18 PM
|
#19
|
|
LQ 5k Club
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,505
|
Quote:
|
should I not just convert to grub?
|
I can not say for sure, however, I suspect it would work. Have a look on slack-docs, I think there is a how to there that should help you get it working.
Personally, I'm not a fan of grub. It is way more complex than lilo or e-lilo. I know from the discussions here on LQ grub is the future, how long I can avoid it I do not know. |
|
|
|
|
01-30-2025, 08:56 PM
|
#20
|
|
Member
Registered: Dec 2003
Distribution: Slack 15-Current
Posts: 375
Original Poster
Rep:
|
Well, related partition, wrote it, change from gpt to dos. Partition, installed and same.
|
|
|
|
|
01-30-2025, 09:33 PM
|
#21
|
|
Member
Registered: Dec 2003
Distribution: Slack 15-Current
Posts: 375
Original Poster
Rep:
|
Never has this issue since 3.2 over 20 years ago. I’m thinking this ain’t for me n’more.
|
|
|
|
|
01-30-2025, 09:35 PM
|
#22
|
|
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 8,154
|
Quote:
|
lilo will not work with a gpt disk, grub will. I use e-lilo on my gpt partitioned systems.
|
Yes lilo will work on gpt disk if booting in legacy/csm mode.
As for the op, are you using lilo or elilo?
Last edited by colorpurple21859; 01-30-2025 at 09:40 PM.
|
|
|
|
|
01-30-2025, 09:50 PM
|
#23
|
|
Member
Registered: Dec 2003
Distribution: Slack 15-Current
Posts: 375
Original Poster
Rep:
|
Quote:
Originally Posted by colorpurple21859
Yes lilo will work on gpt disk if booting in legacy/csm mode.
As for the op, are you using lilo or elilo?
|
lilo. Never in my life have I installed or tried elilo |
|
|
|
|
01-30-2025, 10:08 PM
|
#24
|
|
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 8,154
|
Quote:
|
installed slack live, liked it but decided I didn’t want current on my day to day so went back to slack 15 and now it won’t install. … or.. reboot without kernel panic
|
Maybe the computer is new enough that slackware15 kernel doesn't have support for the hardware.
Last edited by colorpurple21859; 01-30-2025 at 10:09 PM.
|
|
|
|
|
01-30-2025, 10:16 PM
|
#25
|
|
Member
Registered: Dec 2003
Distribution: Slack 15-Current
Posts: 375
Original Poster
Rep:
|
Quote:
Originally Posted by colorpurple21859
Maybe the computer is new enough that slackware15 kernel doesn't have support for the hardware.
|
Yeah, it is not more than 2 years. I’ll try slack15-current just out of curiosity.
Or is there a way to imbed the latest kernel into the reg slack 15 or does it not work that way
Last edited by BAcidEvil; 01-30-2025 at 10:30 PM.
|
|
|
|
|
01-30-2025, 10:35 PM
|
#26
|
|
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 8,154
|
Installing the kernel-generic and maybe kernel-firmware from current onto slackware15 using installpkg may work.
|
|
|
|
|
01-30-2025, 10:39 PM
|
#27
|
|
Member
Registered: Dec 2003
Distribution: Slack 15-Current
Posts: 375
Original Poster
Rep:
|
Quote:
Originally Posted by colorpurple21859
Installing the kernel-generic and maybe kernel-firmware from current onto slackware15 using installpkg may work.
|
I mean wouldn’t it be done prior to installing? I mean I’d want it done before so it has the newest drivers but not sure at what stage it would be done. |
|
|
|
|
01-30-2025, 11:15 PM
|
#28
|
|
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 8,154
|
I think I had a brain-fart. If you was able to install from the slackware15 iso, the kernel wouldn't be the problem. It would have to be something wrong with the initrd.gz file. The internal drive wouldn't happen to be a usb type drive that would need the following modules added to the initrd.gz:
usb-storage xhci-hcd xhci-pci ohci-pci ehci-pci ehci-hcd usbhid ohci-hcd
Last edited by colorpurple21859; 01-30-2025 at 11:16 PM.
|
|
|
|
|
01-30-2025, 11:40 PM
|
#29
|
|
Member
Registered: Dec 2003
Distribution: Slack 15-Current
Posts: 375
Original Poster
Rep:
|
Quote:
Originally Posted by colorpurple21859
I think I had a brain-fart. If you was able to install from the slackware15 iso, the kernel wouldn't be the problem. It would have to be something wrong with the initrd.gz file. The internal drive wouldn't happen to be a usb type drive that would need the following modules added to the initrd.gz:
usb-storage xhci-hcd xhci-pci ohci-pci ehci-pci ehci-hcd usbhid ohci-hcd
|
Yeah I’ve tried both my USB-C and USB3.0 drives.
Like I showing a pic earlier the exact kernel panic I get after a reboot of a successful install.
Also, slack-live 100% worked fine and I am 99% sure slack-current did too… just the slack 15 itself won’t. It’s gotta be just a driver/ compatibility issue. I also installed drauger and unit no issues for fun.
Last edited by BAcidEvil; 01-30-2025 at 11:43 PM.
|
|
|
|
|
01-31-2025, 12:07 AM
|
#30
|
|
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 8,154
|
The error message indicates the filesystem couldn't be mounted. If the slackware15 iso boots and installs without any issue, I've seen several threads on LQ where the issue was the internal drive was some sort of usb device and the mkinitrd_command_generator wouldn't pick up on the needed usb modules.
from a iso, mount the filesystem, mount --bind dev proc sys run to the same files on the mounted system, chroot into the system,
regenerate the initrd with the added usb modules.
or attempt to install the downloaded kernel-generic file from current using installpkg and when mkinitrd is run use -k for kernel-version -o /boot/initrd.img-<kernel version>
or
Last edited by colorpurple21859; 01-31-2025 at 12:09 AM.
|
|
|
|
All times are GMT -5. The time now is 06:04 PM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
