Sunday, May 5, 2024
 Popular · Latest · Hot · Upcoming
2
rated 0 times [  2] [ 0]  / answers: 1 / hits: 1821  / 3 Years ago, sun, november 14, 2021, 7:52:35

I have bought a new Acer Aspire V3 laptop yesterday, which I wanted to have running with Ubuntu.

So I installed Ubuntu 14.04 from DVD which worked fine for me until this noon.



I tried to shut it down and it froze up on me.
So I used the MagicSysRQ to get out of there and tried rebooting to see if everything was still ok.

It wasn't. The system wouldn't come up any more, sometimes it would get farther into the startup then other times.

E. G:




  • I could start typing my password but everything would freeze

  • The Ubuntu purple screen would appear, the dots below the logo moving for some time and finally coming to a halt.



Ok, maybe something was wrong with the harddrive so I inserted the DVD again and tried reinstalling Ubuntu, trusting that in the process the harddrive would be checked and cleaned. Since I just installed Ubuntu, the loss of data was negligable.



To put it in a nutshell: The installation did not even get close to the point where anything would be installed. Either it did not reach the start of any user interface at all or it hung up on me during one of the (early) steps.



So I tried booting from DVD and have the "try Ubuntu" option to check the hardware from there, but that would not work either. (Same results: Startups hanging in various stages).



Meanwhile I kept googling for similar problems and hopefully their solutions but to no avail so far. I just can't think of any reason that a system that would install fine one day could not be booted from another medium the other.



During Install as well as boot from medium I tried using the boot option "noplymouth" instead of "quiet splash". The messages shown until the start of xserver showed no errors, or at least none that I could see.
Also in all cases I tried switching to some terminal using "CTRL+ALT+F1" but that wouldn't work either.



I am quite new to running Ubuntu, so yes, the task of using Ubuntu as sole OS on a new laptop might be a wee bit over my head.



I hope some of you have an idea of what might be wrong or at which part of my setup I might need to look. If I asked the wrong questions before, let me know as well. I really want this fella to run.



The hardware:




  • Acer Aspire V3-772G


    • Intel i7-4702MQ 2. 2GHz

    • Nvidia GeForce GTX 760M

    • 16 GB DDR3 L RAM

    • 1 TB HD

    • Blu-ray Disc RE drive

    • Acer Nplify 802.11 a/b/g/n + BT 4.0




After the n-th retry to get the laptop started it suddenly came back up as if nothing had happened. I ran some system checks I found on the system (which was not much, but then again, I am new with Ubuntu).



After playing around with it a bit I thought to try the much feared reboot and behold, it hung again. So I tried installing again now using bootoption "nomodeset" and I finally managed to get into the installation.



In some forum someone suggested to first get a clean install from USB/DVD without any updates whatsoever which worked as well.
I tried rebooting the system and it hung up on me again (during shutdown).



So, I tried changing the Nvidia driver to the proprietary, tested one and adding NOMODESET to the grub.
Tried rebooting ... and it hung up on me again (during shutdown). This time even the magic sysrq B does not work



Somehow I managed to get the system into a state, in which it would reboot, if that reboot was triggered from one of the Terminals (cTRL+ALT+F2 in my case). The login to Unity however does not work anymore, but leaves me in a state that has been thoroughly discussed here:
Unity doesn't load no launcher no dash appearsUnity doesn't load, no Launcher, no Dash appears



The proposed answers did not my cause at all so I think something might be very much broken either with the software or hardware on my machine. I am not going to give up just yet.



After another round of reinstallation I installed a basic system with only English language support (previously German). Shutdown went awry again: When I was supposed to hit enter after ejecting the install medium nothing happened.
After the reboot, I installed all updates first and then tried a reboot from Terminal (CTRL-ALT-F2) by using



sudo shutdown -r now


Nothing happened until after two minutes some stack traces came dripping into the terminal.



rcu_sched detected stalls on cpus


and



task kworker/u16 blocked for more than 120 seconds


Google told me that this may occur during times of heavy harddisk traffic or due to some bugs in some older kernels, but I am lost why a newly installed system might be producing this traffic?



I realize that all of these problems might not have anything to do with one another but I cannot say for sure.


More From » boot

 Answers
1

If your primary OS is Ubuntu:
1. Format the whole Hard disk.
2. Check for memory errors using any memory test tools (or) the Ubuntu's memtest tool. Recommended tool- Memtest86
3. Try to do the installation again.
4. Comment...


[#25506] Tuesday, November 16, 2021, 3 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
uccase

Total Points: 473
Total Questions: 100
Total Answers: 110

Location: Anguilla
Member since Sun, Jan 29, 2023
1 Year ago
uccase questions
;