Bought a new laptop. Aorus x5
Fantastic laptop.
Came with 2 256GB M.2 SSD in RAID0 and a 1TB spinner. Scrapped that. Changed from UEFI to Legacy BIOS. ACHI sata operation. Reinstalled 8.1 on /dev/sdb. Made the 1TB spinner a data drive for games/music/movies etc on /dev/sda1. Only way I could install slackware was to remove the second M.2 and install that way. Trying to edit Lilo to boot at all now as putting back the M.2 after install changes the naming convention of the Device identifier. So slackware was on /dev/sdb1, after replacing the M.2 it is now /dev/sdc1. Just trying to edit lilo to boot before adding windows partition to Lilo for dual-boot config I get the following error while booting off USB and issuing the following to get into my slack install
Code:
mount /dev/sdc1 /mnt
mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
chroot /mnt
Without this I get kernel panics and random reboots. After the install I was able to boot to slackware no problems. made my user and logged into X. It is after replacing the M.2 with windows on it and trying to edit lilo the issues occur.
I tried installing slack with the Windows M.2 installed and Linux Loader install just hangs. no errors no messages, hanged for 30 minutes before I stopped it.
Code:
root@slackware:/# lilo
Waring: LBA32 addressing assumed
Reference: disk "/dev/sdb" (8,16) 0810
LILO wants to assign a new Volume ID to this disk drive. However, changing the Volume ID of a Windows NT, 2000, or XP boot disk is a fatal Windows error. This caution does not apply to Windows 95 or 98, or to NT data disks.
Is the above disk an NT boot disk? [Y/n]y
Aborting...
Im not even trying to change anything for the windows disk yet.
My current lilo.conf I am retrieving.
Windows Disk (/dev/sdb) is GPT
Slackware Disk (/dev/sdc) is MBR fs=JFS