I installed ArcoLinux successfully via USB stick, when I boot my PC (I have a dual boot with Win10 and ArcoLinux both installed on the same SSD) GRUB shows up successfully with the option for ArcoLinux or Win10. Choosing Win10 boots the windows environment successfully, but when I choose ArcoLinux I get the screen you see below and it just hangs without successfully booting. I have wiped ArcoLinux completely and reinstalled clean numerous times and I get the same situation. I was thinking it may be a driver issue, but then the USB live environment wouldn't have loaded successfully, correct? For background, my PC is Intel i7, 32GB RAM, ASUS Maximus VIII board, Nvidia 1080 card.
Can somebody help me out? Thanks in advance!
Code: Select all
Code: Select all
System: Host: ArcoLinux Kernel: 4.20.0-arch1-1-ARCH x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: ArcoLinux v19.01.4 Machine: Type: Desktop Mobo: ASUSTeK model: MAXIMUS VIII HERO v: Rev 1.xx serial: <root required> UEFI: American Megatrends v: 1701 date: 03/25/2016 CPU: Topology: Quad Core model: Intel Core i7-6700K bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 800 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 801 8: 800 Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nouveau v: kernel Display: x11 server: X.Org 1.20.3 driver: modesetting unloaded: fbdev,vesa resolution: 3840x2160~60Hz OpenGL: renderer: NV134 v: 4.3 Mesa 18.3.2 Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio driver: snd_hda_intel Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k4.20.0-arch1-1-ARCH Network: Device-1: Intel Ethernet I219-V driver: e1000e IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: 2c:56:dc:3d:c2:56 Drives: Local Storage: total: 698.65 GiB used: 8.72 GiB (1.2%) ID-1: /dev/sda vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB Partition: ID-1: / size: 96.31 GiB used: 8.70 GiB (9.0%) fs: ext4 dev: /dev/sdb5 Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 49 C Fan Speeds (RPM): cpu: 0 gpu: nouveau fan: 0 Info: Processes: 223 Uptime: 1h 58m Memory: 31.34 GiB used: 1.52 GiB (4.8%) Shell: bash inxi: 3.0.30
If you are up to it, what if you remove the graphical card and see if that works all the way ... till you reboot into ArcoLinux.
It is not that difficult and it would tell us if it is this Nvidia card or not.
It's also running an NVIDIA Card, but a different model. Some other troubleshooting I did on the other PC that still returned the same error state was I installed on a completely empty drive that was MBR partitioned (no other OS was on the drive) -- the install obviously set a GPT partition for ArcoLinux.
On the new successful install, Arco is installed alongside Windows10 on an MBR partitioned drive. Not sure if MBR vs. GPT is making a difference. But here's something weird: on the unsuccessful install, I noticed last night that the Arco login screen was up (i thought someone was playing a cruel trick on me) I went ahead an logged in as the user I set up during the install and I was able to successfully get in and run Arco successfully. I booted down, then tried to boot into Arco again and had success. I thought it resolved itself until I booted into Win10 successfully, then restarted the PC and tried to boot Arco and low and behold the same error issue occurred. I'm not sure how the Arco login screen magically appeared as I was not in front of the PC when the magic happened. I have not been able to recreate that scenario, so maybe it was just a fluke.
I'm baffled as if it was a hardware issue wouldn't the USB environment not boot?
Here's the inxi of the successful install:
Code: Select all
System: Host: ArcoLinux Kernel: 4.20.0-arch1-1-ARCH x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: ArcoLinux v19.01.4 Machine: Type: Desktop System: MSI product: MS-7673 v: 1.0 serial: <root required> Mobo: MSI model: P67A-C43 (MS-7673) v: 1.0 serial: <root required> BIOS: American Megatrends v: 1.9 date: 03/02/2011 CPU: Topology: Quad Core model: Intel Core i7-2600 bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1597 MHz min/max: 1600/3800 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1596 4: 1596 5: 1596 6: 1596 7: 1596 8: 1596 Graphics: Device-1: NVIDIA GM206 [GeForce GTX 960] driver: nouveau v: kernel Display: x11 server: X.Org 1.20.3 driver: modesetting unloaded: fbdev,vesa resolution: 3840x2160~30Hz OpenGL: renderer: NV126 v: 4.3 Mesa 18.3.1 Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Device-2: NVIDIA GM206 High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k4.20.0-arch1-1-ARCH Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: 6c:62:6d:3f:44:ab Drives: Local Storage: total: 4.55 TiB used: 7.94 GiB (0.2%) ID-1: /dev/sda type: USB vendor: Seagate model: ST4000DM000-1CD168 size: 3.64 TiB ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB Partition: ID-1: / size: 96.53 GiB used: 7.94 GiB (8.2%) fs: ext4 dev: /dev/sdb3 Sensors: System Temperatures: cpu: 41.0 C mobo: N/A gpu: nouveau temp: 34 C Fan Speeds (RPM): N/A gpu: nouveau fan: 0 Info: Processes: 212 Uptime: 6m Memory: 7.77 GiB used: 1.10 GiB (14.2%) Shell: bash inxi: 3.0.30
I just do single boots both MBR and EFI.
Both just work here.
Dual booting is always tricky.
General rule is
First Windows and then Linux.
I had an Apple keyboard connected via USB -- had a hunch maybe that was it so disconnected it and connected a generic USB wireless keyboard and everything is fine! Can boot into both Windows10 and Arco with no problem -- by the way, the only reason I have a dual boot on my PC's is because they are shared with my kids and wife and god forbid I force them to use Linux (even though it is the best OS in the land)