Fellow Slackers,

My trusty Shuttle XS35 finally gave up the ghost after many years and I decided to build a 1U server for my new rack. The goal was a quiet, reliable device to serve up web pages; media via NFS,SMB and FTP and a backup target for my laptop via rsync.

Found a fanless board and a 1U case. This is the board: https://marketplace.intel.com/s/offe...language=en_US

Tried to install Slack 14.2 via USB, DVD, booting the old drive ... none work. Linux Mint installs with no problem, but that's not what I want. Secure boot disabled in BIOS.

When trying to boot from a USB drive or DVD via USB, I get a blank screen with a vertical line. The old slack drive is not recognized. I can't boot from it nor does it show up as a mountable device to the Mint install.

I could accomplish everything I need to do using Debian or a derivative, but what fun is that?

What am I missing?

Linux Mint installs with no problem

But some lines later ....

I can't boot from it nor does it show up as a mountable device to the Mint install

All this in slackware section ...

I understand 0

Have you only tried 14.2? Did you try -current? newer hardware you need the newer kernel drivers and such.

and wow, mitac I had forgotten all all about them, haven't seen that name in a long time.
Anyway your board says intel gen 10, the box I just got is Gen7 and 14.2 didn't have network and other issues.

Try Slackware 15 RC1 and see if it's a driver issue. Good chance your hardware is just too new for 14.2. This was my case when I built my new machine in December. ISO link

I've tried to boot from a Slack 14.2 DVD, from a Slack 14.2 USB and from the old Slack 14.2 HD. None worked. Many times, I've moved an existing drive to a new system and it's booted fine.

I tried Mint out of desperation and it installed fine, except, after a full install it did not recognize the old Slack hard drive. If I put that HDD in a USB enclosure, I can mount it and see the data.

Capisce?

1 members found this post helpful.

try -current / 15

1 members found this post helpful.

Interesting mobo. I have little to go on to know if Mini-PCIe presents any problems but I'm pretty certain you need a newer kernel. You could actually use the kernel packages from Current and substitute them into the 14.2 Install iso but I don't seen any reason for that with 15.0 so close and so great. It really is looking especially stellar.

New hardware requires a new version of Slackware. Slackware 14.2 is a little over 5 years old. Use Slackware64-current.

Here is another vote for using -current on this motherboard.

Intel, the CPU vendor, calls out a couple of different Ubuntu versions for the Comet Lake CPU, One uses the 5.4.x kernel and one uses the 5.11.x kernel. I also have personal experience with another system that runs fine under -current but wouldn't use 14.2, and if I recall correctly it wouldn't see the SATA ports either.

Have you tried Slackware-current

I went through this on my new Gigabyte 570 chip set for ryzen 3700x.
setting it to legacy then everything worked.
But I wanted to play with UEFI so I did. This was the big reason GPT partition and elilo for slackware 14.2.
After I got through playing with it and learning set it to auto legacy or UEFI .
https://www.gigabyte.com/Motherboard...WIFI-rev-10#kf

I think your running into a learning curve.
Set to legacy boot and throw your drives on.
I love my nvme drives also.

It is a learning curve. Hang in there.
Slackware 14.2 does not default to a UEFI install so you may want
pick your "CSM" legacy or auto. delete the windows key if your not using windows.

All the other distros as of the last couple years default to UEFI.
Basically creating a 100 mb win32 partition that mounts at /boot/UEFI
I have no use for it.
I believe this is the setting on your board that may cause you issues.
You will see yours comes default like this for windows. second photo
Disable security devices.

Attached Thumbnails

   

1 members found this post helpful.

I did a little more digging. One of the 5.x kernels added support for the Intel Comet Lake CPU. -Current is using a 5.13 kernel, so it'll run on this board. I didn't see Comet Lake support in any of the 4.x kernels.

At https://wiki.ubuntu.com/FocalFossa/ReleaseNotes I did see that Linux 5.4 has newly-added support for Comet Lake and Tiger Lake hardware:
TL;DR: 14.2 won't work on your computer. You need to upgrade to get it working.

HTH

I have no clue where your thinking the 4.4.276 kernel would not run that cpu. If so Red hat would be out of business.
Not detecting devices read my post lets see if his old none EFI installs are recognized
There is a reason why the newer distro's work 14.2 has that option not default. debian like the rest create a EFI secure win32
partition only thing new on that cpu is mvx-512 thats a tenth gen. has nothing to do with anything that would cause this.

I think you're right about the root cause being UEFI-related. The suggestions of old kernels and drivers don't explain why I can't even get to the setup screen.
Before posting, though, I tried a number of things in BIOS. Secure Boot is disabled. I removed the windows key and imported the UEFI key from the install ISO, using the "Custom" settings. Same result for all.

Does 15.0RC1 deal with UEFI? If so, I'll give it a shot. I was going to run Mint or some other distro as a live instance, mount the Slack ISO and try to install that way but ran out of patience.

I downloaded and expanded the 4.4.282 and the 5.13.13 kernels then ran the command "grep -r "Comet Lake" *" in the top-level directory of each kernel. On the 5.13.13 kernel I got hits on Documentation/i2c/busses/i2c-i801.rst, drivers/misc/mei/hw-me-regs.h, drivers/ata/ahci.c, drivers/gpu/drm/i915/intel_pch.c and drivers/gpu/drm/i915/intel_pch.h, drivers/i2c/busses/i2c-i801.c, drivers/i2c/busses/Kconfig, drivers/hwtracing/intel_th/pci.c, and include/linux/input/elan-i2c-ids.h. On the 4.4.282 kernel I got hits on . . . nothing. That CPU is not supported by the 4.4.282 kernel.

Just out of curiosity I searched both source trees for "Ryzen", with the same result. That explains why I had to upgrade from 14.2 to -current to use my new computer. The 4.4 kernels don't support Ryzen CPUs. And I had the same problem as the OP: I could not see the SATA drive.

1 members found this post helpful.