F5F Stay Refreshed Software Operating Systems Ubuntu sets up on the loading screen after a recent installation.

Ubuntu sets up on the loading screen after a recent installation.

Ubuntu sets up on the loading screen after a recent installation.

Pages (2): 1 2 Next
B
BooshDev
Member
207
07-21-2016, 12:33 AM
#1
Hi, after facing numerous issues with Windows 10, I decided to revert to the software I had before I owned a gaming PC. I returned to Ubuntu, downloaded my ISO from the NAS and burned it onto a USB drive. Everything proceeded smoothly until I restarted. Linux displayed an SCPI error, but I ignored it and kept hoping for that striking purple background. Then I noticed the loading screen appeared, but the small white dots remained unchanged and stayed white. There was no progress whatsoever. This incident happened last night, so I left it overnight, assuming it would take its time. In the morning it was identical—no disk activity at all. It was version 16.04.4 LTS. I then tried 17.10.1, believing a newer Ubuntu version might help with my MSI GL62 7RD i5 7300HQ. Still nothing. Eventually, I went for 16.04.4 LTS and installed it. The same errors persisted, including an ACPI-related issue, and I stuck on the loading screen. Before you suggest turning off ACPI, I’m pretty sure there’s no option left on my laptop. Is there anything I’m doing incorrectly with Rufus or burning it as a DD image? Please assist me—I’m really frustrated with both Windows 10 and Windows 7. Thanks in advance. James
B
BooshDev
07-21-2016, 12:33 AM #1

Hi, after facing numerous issues with Windows 10, I decided to revert to the software I had before I owned a gaming PC. I returned to Ubuntu, downloaded my ISO from the NAS and burned it onto a USB drive. Everything proceeded smoothly until I restarted. Linux displayed an SCPI error, but I ignored it and kept hoping for that striking purple background. Then I noticed the loading screen appeared, but the small white dots remained unchanged and stayed white. There was no progress whatsoever. This incident happened last night, so I left it overnight, assuming it would take its time. In the morning it was identical—no disk activity at all. It was version 16.04.4 LTS. I then tried 17.10.1, believing a newer Ubuntu version might help with my MSI GL62 7RD i5 7300HQ. Still nothing. Eventually, I went for 16.04.4 LTS and installed it. The same errors persisted, including an ACPI-related issue, and I stuck on the loading screen. Before you suggest turning off ACPI, I’m pretty sure there’s no option left on my laptop. Is there anything I’m doing incorrectly with Rufus or burning it as a DD image? Please assist me—I’m really frustrated with both Windows 10 and Windows 7. Thanks in advance. James

T
Tysaber
Member
60
07-22-2016, 02:10 PM
#2
Hi @Joelsome Yes, refusing can sometimes cause issues when using dd, since it isn't exactly the same as from a Linux terminal. The default settings on Rufus should work fine. Alternatively, if you have another Linux PC, install it there to avoid any boot problems. This method has consistently succeeded for me. You might want to try it first before diving into troubleshooting, assuming you're familiar with the command. If you need more details, feel free to ask.
T
Tysaber
07-22-2016, 02:10 PM #2

Hi @Joelsome Yes, refusing can sometimes cause issues when using dd, since it isn't exactly the same as from a Linux terminal. The default settings on Rufus should work fine. Alternatively, if you have another Linux PC, install it there to avoid any boot problems. This method has consistently succeeded for me. You might want to try it first before diving into troubleshooting, assuming you're familiar with the command. If you need more details, feel free to ask.

L
liron374
Member
57
07-22-2016, 07:04 PM
#3
You successfully got it to boot, thanks! To save your changes, you need to add the acpi=off line at the end of the Linux command in Grub. The trackpad issue and volume/lighting problems might require further tweaks, but they don’t seem like major fixes. It wasn’t a simple one—some adjustments were needed.
L
liron374
07-22-2016, 07:04 PM #3

You successfully got it to boot, thanks! To save your changes, you need to add the acpi=off line at the end of the Linux command in Grub. The trackpad issue and volume/lighting problems might require further tweaks, but they don’t seem like major fixes. It wasn’t a simple one—some adjustments were needed.

Y
yar_pvp
Member
166
07-24-2016, 02:00 AM
#4
To save changes to grub, first modify a configuration file and then run a command to apply the updates. This ensures the changes are permanent. The same FN problems have occurred, but at Arch Linux I encountered kernel-level support issues that couldn't be resolved easily—this might also apply to Ubuntu. Regarding "tracking-wise," it seems the system isn't capturing your input with perfect precision, which can happen over time. Below are commands to help you get started. sudo nano /etc/default/grub sudo update-grub
Y
yar_pvp
07-24-2016, 02:00 AM #4

To save changes to grub, first modify a configuration file and then run a command to apply the updates. This ensures the changes are permanent. The same FN problems have occurred, but at Arch Linux I encountered kernel-level support issues that couldn't be resolved easily—this might also apply to Ubuntu. Regarding "tracking-wise," it seems the system isn't capturing your input with perfect precision, which can happen over time. Below are commands to help you get started. sudo nano /etc/default/grub sudo update-grub

J
jack_is_pro
Junior Member
14
07-24-2016, 06:17 AM
#5
thanks, what I mean by tracking-wise, is that it doesn't seem as good at tracking as in windows. it is a good trackpad, but the detailed small movements seem to just not get picked up in linux. Could this be due to lack of support?
J
jack_is_pro
07-24-2016, 06:17 AM #5

thanks, what I mean by tracking-wise, is that it doesn't seem as good at tracking as in windows. it is a good trackpad, but the detailed small movements seem to just not get picked up in linux. Could this be due to lack of support?

B
BadAtCosmic
Junior Member
45
07-25-2016, 08:05 PM
#6
Have you looked for any manufacturer-specific drivers? It’s likely it starts with an open-source option by default.
B
BadAtCosmic
07-25-2016, 08:05 PM #6

Have you looked for any manufacturer-specific drivers? It’s likely it starts with an open-source option by default.

M
malec0196
Junior Member
7
07-26-2016, 03:44 AM
#7
Checked MSI's site—they only list Windows 10 drivers. Wine seems out of place.
M
malec0196
07-26-2016, 03:44 AM #7

Checked MSI's site—they only list Windows 10 drivers. Wine seems out of place.

K
Kai4Christ
Member
177
07-26-2016, 05:01 AM
#8
You might want to explore other options since I haven’t installed a driver via Wine. There’s a chance it won’t work, and you’ll likely be limited to the current driver installed. Could also tell me what kind of trackpad you have? That way I can help you better. You can check your input devices by running the command below: cat /proc/bus/input/devices
K
Kai4Christ
07-26-2016, 05:01 AM #8

You might want to explore other options since I haven’t installed a driver via Wine. There’s a chance it won’t work, and you’ll likely be limited to the current driver installed. Could also tell me what kind of trackpad you have? That way I can help you better. You can check your input devices by running the command below: cat /proc/bus/input/devices

K
Kristijanman
Junior Member
38
07-26-2016, 09:15 AM
#9
It clearly states what the synPS/2 Synaptics Touchpad does.
K
Kristijanman
07-26-2016, 09:15 AM #9

It clearly states what the synPS/2 Synaptics Touchpad does.

B
biotit
Member
81
07-27-2016, 07:16 AM
#10
No, you wouldn't add it at the end. The correct format is to place "acpi=off" inside the quotes in GRUB_CMDLINE_LINUX.
B
biotit
07-27-2016, 07:16 AM #10

No, you wouldn't add it at the end. The correct format is to place "acpi=off" inside the quotes in GRUB_CMDLINE_LINUX.

Pages (2): 1 2 Next