Not a member yet? Why not Sign up today
Create an account  

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
I need reassurance that I am booting from the M2 drive

How can I confirm that xanmod has installed itself on the correct drive and that I am booting from the M2 drive?

I have recently installed an M2 drive and have been running Ubuntu 18.04 from it. Today I tried to install xanmod but found that I was booting from a hard drive instead of the SSDe. 

I reinstalled using the command line. It installed without error but I noticed a report entry that it had found the system on sda2 where as the m2 drive as /dev/nm...

Quote:cat /proc/versioncat /proc/version
cat: /proc/versioncat: No such file or directory
Linux version 5.1.14-xanmod9 (root@mascote) (gcc version 9.1.1 20190612 (Debian 9.1.0-4)) #1.190622 SMP PREEMPT Sat Jun 22 10:45:25 -03 2019

This is the installation feedback via command line. Please see the line in bold towards the end:

Quote:robins@robins-desktop:~$ sudo apt update && sudo apt install linux-xanmod
E: Type ‘gpg’ is not known on line 1 in source list /etc/apt/sources.list.d/xanmod-kernel.list
E: The list of sources could not be read.
robins@robins-desktop:~$ echo 'deb releases main' | sudo tee /etc/apt/sources.list.d/xanmod-kernel.list && wget -qO - | sudo apt-key add -
deb releases main
robins@robins-desktop:~$ sudo apt update && sudo apt install linux-xanmod
Hit:1 artful InRelease
Hit:2 bionic InRelease
Hit:3 bionic InRelease
Hit:4 releases InRelease
Get:5 bionic-updates InRelease [88.7 kB]
Hit:6 bionic InRelease
Get:7 bionic-security InRelease [88.7 kB]
Get:8 bionic-backports InRelease [74.6 kB]
Fetched 252 kB in 2s (163 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up-to-date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libc-dev-bin libc6-dev libelf-dev linux-headers-5.1.14-xanmod9
linux-image-5.1.14-xanmod9 linux-libc-dev manpages-dev zlib1g-dev
Suggested packages:
glibc-doc preload
The following NEW packages will be installed
libc-dev-bin libc6-dev libelf-dev linux-headers-5.1.14-xanmod9
linux-image-5.1.14-xanmod9 linux-libc-dev linux-xanmod manpages-dev
0 to upgrade, 9 to newly install, 0 to remove and 0 not to upgrade.
Need to get 75.1 MB of archives.
After this operation, 427 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 bionic/main amd64 libc-dev-bin amd64 2.27-3ubuntu1 [71.8 kB]
Get:2 releases/main amd64 linux-headers-5.1.14-xanmod9 amd64 1.190622 [11.3 MB]
Get:4 bionic/main amd64 libc6-dev amd64 2.27-3ubuntu1 [2,587 kB]
Get:3 bionic-updates/main amd64 linux-libc-dev amd64 4.15.0-52.56 [1,004 kB]
Get:5 bionic/main amd64 zlib1g-dev amd64 1:1.2.11.dfsg-0ubuntu2 [176 kB]
Get:6 bionic-updates/main amd64 libelf-dev amd64 0.170-0.4ubuntu0.1 [57.3 kB]
Get:7 bionic/main amd64 manpages-dev all 4.15-1 [2,217 kB]
Get:8 releases/main amd64 linux-image-5.1.14-xanmod9 amd64 1.190622 [57.7 MB]
Get:9 releases/main amd64 linux-xanmod amd64 1.190622 [912 B]
Fetched 75.1 MB in 1min 10s (1,067 kB/s)
Selecting previously unselected package libc-dev-bin.
(Reading database ... 195983 files and directories currently installed.)
Preparing to unpack .../0-libc-dev-bin_2.27-3ubuntu1_amd64.deb ...
Unpacking libc-dev-bin (2.27-3ubuntu1) ...
Selecting previously unselected package linux-libc-dev:amd64.
Preparing to unpack .../1-linux-libc-dev_4.15.0-52.56_amd64.deb ...
Unpacking linux-libc-dev:amd64 (4.15.0-52.56) ...
Selecting previously unselected package libc6-dev:amd64.
Preparing to unpack .../2-libc6-dev_2.27-3ubuntu1_amd64.deb ...
Unpacking libc6-dev:amd64 (2.27-3ubuntu1) ...
Selecting previously unselected package zlib1g-dev:amd64.
Preparing to unpack .../3-zlib1g-dev_1%3a1.2.11.dfsg-0ubuntu2_amd64.deb ...
Unpacking zlib1g-dev:amd64 (1:1.2.11.dfsg-0ubuntu2) ...
Selecting previously unselected package libelf-dev:amd64.
Preparing to unpack .../4-libelf-dev_0.170-0.4ubuntu0.1_amd64.deb ...
Unpacking libelf-dev:amd64 (0.170-0.4ubuntu0.1) ...
Selecting previously unselected package linux-headers-5.1.14-xanmod9.
Preparing to unpack .../5-linux-headers-5.1.14-xanmod9_1.190622_amd64.deb ...
Unpacking linux-headers-5.1.14-xanmod9 (1.190622) ...
Selecting previously unselected package linux-image-5.1.14-xanmod9.
Preparing to unpack .../6-linux-image-5.1.14-xanmod9_1.190622_amd64.deb ...
Unpacking linux-image-5.1.14-xanmod9 (1.190622) ...
Selecting previously unselected package linux-xanmod.
Preparing to unpack .../7-linux-xanmod_1.190622_amd64.deb ...
Unpacking linux-xanmod (1.190622) ...
Selecting previously unselected package manpages-dev.
Preparing to unpack .../8-manpages-dev_4.15-1_all.deb ...
Unpacking manpages-dev (4.15-1) ...
Setting up linux-headers-5.1.14-xanmod9 (1.190622) ...
Setting up linux-image-5.1.14-xanmod9 (1.190622) ...
update-initramfs: Generating /boot/initrd.img-5.1.14-xanmod9
I: The initramfs will attempt to resume from /dev/sda8
I: (UUID=02c1d09e-54db-4346-863d-1097ff0ed637)
I: Set the RESUME variable to override this.
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.1.14-xanmod9
Found initrd image: /boot/initrd.img-5.1.14-xanmod9
Found linux image: /boot/vmlinuz-4.18.0-22-generic
Found initrd image: /boot/initrd.img-4.18.0-22-generic
Found linux image: /boot/vmlinuz-4.18.0-21-generic
Found initrd image: /boot/initrd.img-4.18.0-21-generic
Found memtest86+ image: /@/boot/memtest86+.elf
Found memtest86+ image: /@/boot/memtest86+.bin
Found Ubuntu 18.04.2 LTS (18.04) on /dev/sda2
Setting up linux-libc-dev:amd64 (4.15.0-52.56) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Setting up linux-xanmod (1.190622) ...
Setting up libc-dev-bin (2.27-3ubuntu1) ...
Setting up manpages-dev (4.15-1) ...
Setting up libc6-dev:amd64 (2.27-3ubuntu1) ...
Setting up zlib1g-dev:amd64 (1:1.2.11.dfsg-0ubuntu2) ...
Setting up libelf-dev:amd64 (0.170-0.4ubuntu0.1) ..
p { margin-bottom: 0.25cm; line-height: 115%; }

This is not a kernel-related topic. You need to set the new drive to "bootable," see if this topic helps:

Quick Reply
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Forum Jump:

Users browsing this thread:
1 Guest(s)