Choose style:

Author Topic: Trouble installing pep9 64 on a m2 drive (solved)  (Read 1175 times)

0 Members and 1 Guest are viewing this topic.

chadwix

  • Guest
Trouble installing pep9 64 on a m2 drive (solved)
« on: August 17, 2018, 11:32:17 pm »
I can get it boot on occasion, but then it wont shut down (little white bar never moves after like 5%).  Restart doesnt work either.  Its a new computer so i plugged in my old 240ssd and its fine. 

Also is there a better video driver for the onboard amd video?  Its fine but update center didnt have anything for amd

Is the drive ID-1: /dev/nvme0n1 model: INTEL_SSDPEKKW256G8 size: 256.1GB

had@chad-C2SEA ~ $ inxi -Fz
System:    Host: chad-C2SEA Kernel: 4.15.0-32-generic x86_64 bits: 64 Desktop: N/A
           Distro: Peppermint Nine
Machine:   Device: desktop System: Gigabyte product: AB350M-DS3H serial: N/A
           Mobo: Gigabyte model: AB350M-DS3H-CF v: x.x serial: N/A
           UEFI [Legacy]: American Megatrends v: F23 date: 08/08/2018
CPU:       Quad core AMD Ryzen 3 2200G with Radeon Vega Graphics (-MCP-)
           cache: 2048 KB
           clock speeds: max: 3500 MHz 1: 1483 MHz 2: 1477 MHz 3: 3687 MHz
           4: 1585 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon Vega 8 Mobile]
           Display Server: x11 (X.Org 1.19.6 )
           drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: AMD RAVEN (DRM 3.23.0 / 4.15.0-32-generic, LLVM 6.0.0)
           version: 4.5 Mesa 18.0.5
Audio:     Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] Device 15de
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.15.0-32-generic
Network:   Card-1: Intel Wireless 7260 driver: iwlwifi
           IF: wlp3s0 state: up mac: <filter>
           Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
           driver: r8169
           IF: enp4s0 state: down mac: <filter>
Drives:    HDD Total Size: 1496.3GB (45.7% used)
           ID-1: /dev/nvme0n1 model: INTEL_SSDPEKKW256G8 size: 256.1GB
           ID-2: /dev/sda model: WDC_WD1001FALS size: 1000.2GB
           ID-3: /dev/sdb model: KINGSTON_SV300S3 size: 240.1GB
Partition: ID-1: / size: 220G used: 9.3G (5%) fs: ext4 dev: /dev/sdb1
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 39.5C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 214 Uptime: 25 min Memory: 1220.5/6979.2MB
           Client: Shell (bash) inxi: 2.3.56

Thanks
« Last Edit: December 03, 2018, 09:19:37 pm by chadwix »

chadwix

  • Guest
Re: Trouble installing pep9 64 on a m2 drive
« Reply #1 on: August 18, 2018, 01:26:24 am »
I started having boot issues, even with the old ssd.  I took the m2 out for now, but will put in again tomorrow.  I was getting a ton of a achi and cannot write to IOMMU errors on boot.  I disabled IOMMU in bios and it was better, no errors.  But then i looked a bit more and luckily found this.  Looks like someone messed up on default bios, both should be on, or both should be off.

"I checked the BIOS and the only mention of virtualization I could find is the option to enable IOMMU support. About to fire up Linux on this thing to see if it's just a Windows 10 thing, but if not then wtf? Has anyone else experienced the same thing with Ryzen? Why would Gigabyte exclude a feature that has been including in every AMD chip in the past decade? I sent them a support ticket but haven't gotten a reply yet.

Edit: So apparently to enable virtualization support, you have to enable SVM. To activate it, click on the MIT tab, then Advanced Frequency Settings and then Advanced Core settings. Even though the manual says it should be enabled by default, it wasn't on my board."

Will pop the m2 in tomorrow, when it worked, it was really nice.

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26466
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Trouble installing pep9 64 on a m2 drive
« Reply #2 on: August 18, 2018, 01:41:38 pm »
If you get any errors, can you post them verbatim.
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

chadwix

  • Guest
Re: Trouble installing pep9 64 on a m2 drive
« Reply #3 on: August 18, 2018, 07:37:22 pm »
Here is what it looks like in dos when it fails to boot.  Every 2nd or 3rd boot works.  After i get these messages, i restart, get the grub peppermint screen and it boots.

https://postimg.cc/gallery/h322rosy/d31afbba/

Thanks

Offline VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5611
  • Karma: 1013
  • Peppermint Mod
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Trouble installing pep9 64 on a m2 drive
« Reply #4 on: August 18, 2018, 08:16:05 pm »
Have you tried appending 'acpi=off' to your GRUB parameters?


chadwix

  • Guest
Re: Trouble installing pep9 64 on a m2 drive
« Reply #5 on: August 18, 2018, 09:52:20 pm »
Have you tried appending 'acpi=off' to your GRUB parameters?

Not sure how to do that. 

I did do a sudo update-grub and it seemed to really help.  Im no longer getting boot problems or those errors upon boot.

Thanks

Offline VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5611
  • Karma: 1013
  • Peppermint Mod
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Trouble installing pep9 64 on a m2 drive
« Reply #6 on: August 18, 2018, 11:03:45 pm »
Nice.

I'd cross my fingers and leave well enough alone for now, if it was me - see if that fixes it.  ;)

chadwix

  • Guest
Re: Trouble installing pep9 64 on a m2 drive
« Reply #7 on: August 18, 2018, 11:52:24 pm »
Nice.

I'd cross my fingers and leave well enough alone for now, if it was me - see if that fixes it.  ;)

BIos
SVM = Disabled
IOMMU = Disabled
Fast boot - There is no secure boot option, I think its built into normal.

Linux
Sudo update-grub 

I think those are the only settings that did something, realised i didnt get manual with mobo, was going to look up what they did.  They didnt give 2 sata cables either, box didnt have a sticker closing it.  Will get some money back maybe.

This motherboard isnt supposed to work on linux (from reviews).  M2 boot is another issue.  Very happy to get both working great, $348 for a beast of a machine (non gaming). 

Thanks for help, 4 reboots in a row.  Big test will be the full power down.  It worked twice, skin is back on the case.

Did the "try peppermint" off the usb, then installed so i could connect to network and fix res (hate the 4k but smooth on this one).
« Last Edit: August 19, 2018, 12:34:07 am by chadwix »

chadwix

  • Guest
Re: Trouble installing pep9 64 on a m2 drive (SOLVED)
« Reply #8 on: August 19, 2018, 01:02:45 am »
Grub is still messing up , failed reboot, hit load peppermint, redo grub and fixed.  Its like it isnt being saved if powered down
« Last Edit: August 19, 2018, 02:12:07 am by chadwix »

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26466
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Trouble installing pep9 64 on a m2 drive
« Reply #9 on: August 19, 2018, 10:14:08 am »
Can you post the output from:
Code: [Select]
sudo blkid
and the contents of both
Code: [Select]
xed /etc/default/grub
and
Code: [Select]
xed /boot/grub/grub.cfg

These links are here for my future reeference
https://forums.gentoo.org/viewtopic-t-1046366-start-0.html
https://forums.gentoo.org/viewtopic-t-1049514-start-0.html
« Last Edit: August 19, 2018, 10:22:17 am by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

chadwix

  • Guest
Re: Trouble installing pep9 64 on a m2 drive
« Reply #10 on: August 19, 2018, 04:42:12 pm »
Can you post the output from:
Code: [Select]
sudo blkid
and the contents of both
Code: [Select]
xed /etc/default/grub
and
Code: [Select]
xed /boot/grub/grub.cfg

These links are here for my future reeference
https://forums.gentoo.org/viewtopic-t-1046366-start-0.html
https://forums.gentoo.org/viewtopic-t-1049514-start-0.html

Code: [Select]
/dev/nvme0n1p1: UUID="275C-F366" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="1b5d39a8-8fb2-4d05-8aa0-019d623494ed"
/dev/nvme0n1p2: UUID="f430ba72-e35d-497b-a719-616616d880ab" TYPE="ext4" PARTUUID="37835a55-0e95-45e6-addb-5756303751b6"
/dev/sda1: LABEL="storage" UUID="1436096a-a579-44cc-808c-4ac7096ad27a" TYPE="ext4" PARTUUID="802af160-01"
/dev/nvme0n1: PTUUID="cf857bba-4a08-4ac2-8f79-b031fe358e40" PTTYPE="gpt"

----------------------------------------------

Code: [Select]
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

-------------------------------------------------------------

Spoiler (click here to view / hide)
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function recordfail {
  set recordfail=1
  if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  f430ba72-e35d-497b-a719-616616d880ab
else
  search --no-floppy --fs-uuid --set=root f430ba72-e35d-497b-a719-616616d880ab
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=hidden
    set timeout=10
  # Fallback hidden-timeout code in case the timeout_style feature is
  # unavailable.
  elif sleep --interruptible 10 ; then
    set timeout=0
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  f430ba72-e35d-497b-a719-616616d880ab
else
  search --no-floppy --fs-uuid --set=root f430ba72-e35d-497b-a719-616616d880ab
fi
insmod png
if background_image /boot/grub/grub-background.png; then
  true
else
  set menu_color_normal=light-gray/black
  set menu_color_highlight=white/red
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
   set gfxpayload="${1}"
   if [ "${1}" = "keep" ]; then
      set vt_handoff=vt.handoff=1
   else
      set vt_handoff=
   fi
}
if [ "${recordfail}" != 1 ]; then
  if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
      if [ ${match} = 0 ]; then
        set linux_gfx_mode=keep
      else
        set linux_gfx_mode=text
      fi
    else
      set linux_gfx_mode=text
    fi
  else
    set linux_gfx_mode=keep
  fi
else
  set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Peppermint GNU/Linux' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-f430ba72-e35d-497b-a719-616616d880ab' {
   recordfail
   load_video
   gfxmode $linux_gfx_mode
   insmod gzio
   if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
   insmod part_gpt
   insmod ext2
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root  f430ba72-e35d-497b-a719-616616d880ab
   else
     search --no-floppy --fs-uuid --set=root f430ba72-e35d-497b-a719-616616d880ab
   fi
        linux   /boot/vmlinuz-4.15.0-32-generic root=UUID=f430ba72-e35d-497b-a719-616616d880ab ro  quiet splash $vt_handoff
   initrd   /boot/initrd.img-4.15.0-32-generic
}
submenu 'Advanced options for Peppermint GNU/Linux' $menuentry_id_option 'gnulinux-advanced-f430ba72-e35d-497b-a719-616616d880ab' {
   menuentry 'Peppermint GNU/Linux, with Linux 4.15.0-32-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-32-generic-advanced-f430ba72-e35d-497b-a719-616616d880ab' {
      recordfail
      load_video
      gfxmode $linux_gfx_mode
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_gpt
      insmod ext2
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root  f430ba72-e35d-497b-a719-616616d880ab
      else
        search --no-floppy --fs-uuid --set=root f430ba72-e35d-497b-a719-616616d880ab
      fi
      echo   'Loading Linux 4.15.0-32-generic ...'
           linux   /boot/vmlinuz-4.15.0-32-generic root=UUID=f430ba72-e35d-497b-a719-616616d880ab ro  quiet splash $vt_handoff
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-4.15.0-32-generic
   }
   menuentry 'Peppermint GNU/Linux, with Linux 4.15.0-32-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-32-generic-recovery-f430ba72-e35d-497b-a719-616616d880ab' {
      recordfail
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_gpt
      insmod ext2
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root  f430ba72-e35d-497b-a719-616616d880ab
      else
        search --no-floppy --fs-uuid --set=root f430ba72-e35d-497b-a719-616616d880ab
      fi
      echo   'Loading Linux 4.15.0-32-generic ...'
           linux   /boot/vmlinuz-4.15.0-32-generic root=UUID=f430ba72-e35d-497b-a719-616616d880ab ro recovery nomodeset
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-4.15.0-32-generic
   }
   menuentry 'Peppermint GNU/Linux, with Linux 4.15.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-23-generic-advanced-f430ba72-e35d-497b-a719-616616d880ab' {
      recordfail
      load_video
      gfxmode $linux_gfx_mode
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_gpt
      insmod ext2
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root  f430ba72-e35d-497b-a719-616616d880ab
      else
        search --no-floppy --fs-uuid --set=root f430ba72-e35d-497b-a719-616616d880ab
      fi
      echo   'Loading Linux 4.15.0-23-generic ...'
           linux   /boot/vmlinuz-4.15.0-23-generic root=UUID=f430ba72-e35d-497b-a719-616616d880ab ro  quiet splash $vt_handoff
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-4.15.0-23-generic
   }
   menuentry 'Peppermint GNU/Linux, with Linux 4.15.0-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-23-generic-recovery-f430ba72-e35d-497b-a719-616616d880ab' {
      recordfail
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_gpt
      insmod ext2
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root  f430ba72-e35d-497b-a719-616616d880ab
      else
        search --no-floppy --fs-uuid --set=root f430ba72-e35d-497b-a719-616616d880ab
      fi
      echo   'Loading Linux 4.15.0-23-generic ...'
           linux   /boot/vmlinuz-4.15.0-23-generic root=UUID=f430ba72-e35d-497b-a719-616616d880ab ro recovery nomodeset
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-4.15.0-23-generic
   }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
   fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
[close]

Thanks


« Last Edit: August 19, 2018, 05:24:41 pm by AndyInMokum, Reason: encapsulating with [code] & [spoiler] »

Offline AndyInMokum

  • Global Moderator
  • Hero
  • *****
  • Posts: 4893
  • Karma: 1053
  • "Keep on Rockin' in the Free World"
    • View Profile
  • Peppermint version(s): PM 9 & PM 10 (64-bit)
Re: Trouble installing pep9 64 on a m2 drive
« Reply #11 on: August 19, 2018, 05:28:34 pm »
Hi chadwix, how's it going  :)?  When posting commands or edits for the text editor, could you please remember to encapsulate them with the Insert, Code # function.  For extra long entries, please use the Spoiler, Sp function.  If you're using either the Chromium Browser or Google Chrome, don't combine these functions.  Only use one or the other per output  ;).  These functions allow the user to see how entries look in the system text editor.  Doing this is a huge help  ;).  It makes it much easier for future visitors; especially novice or newbies  ;).

These functions are found in the forum editor, above the,  :-[ Embarrassed and  the :'( Cry emoticon respectively.  You can click on the Preview button to see how it'll look in the forum.  I've done it for you this time - many thanks  ;).
Backup! Backup! Backup! If you're missing any of these -  you ain't Backed Up!
For my system info please L/click HERE.

chadwix

  • Guest
Re: Trouble installing pep9 64 on a m2 drive
« Reply #12 on: August 20, 2018, 06:21:16 pm »
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

Is that the problem?  Everything is new and can be returned.

Its boots every other time now.  Once its up and running its perfectly stable.

I did try sleep mode, but the resolution comes back at low res.

Thanks



Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26466
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Trouble installing pep9 64 on a m2 drive
« Reply #13 on: August 20, 2018, 08:04:29 pm »
Quote
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

Is that the problem?  Everything is new and can be returned.

No that line in GRUB is a default example, in any case that line is commented out (starts with an #) so isn't being acted upon anyway.

We'll try using the partition UUID (PARTUUID) instead of the filesystem UUID (UUID) in GRUB next, but I need to do a bit of homework/testing before posting instructions.
« Last Edit: August 20, 2018, 08:07:13 pm by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

chadwix

  • Guest
Re: Trouble installing pep9 64 on a m2 drive (solved)
« Reply #14 on: December 03, 2018, 09:20:26 pm »
Has booted up everytime for the past week on the first try, runs really well.  Thanks for the updates, one of them did the trick :)