I followed this tutorial to install ChromeOS on my dell XPS laptop.
But After installing the ChromeOS I get stuck in a boot loop where I am told 'Loading Brunch Framework...' and then it infinitely reboots in a loop.
the same issue is seen here:
https://github.com/sebanc/brunch/issues/756#issuecomment-752710319
I've also tried the volteer image and have the same results
how do I get out of the boot loop and complete the chrome installation?
Related
Running Windows 10 on my laptop (with a compatible GPU) and just started using tensorflow-gpu 2 days ago. Every time I close the lid to put the laptop to sleep, it restarts when I wake it up. This never happened when I was just running normal tensorflow. I thought I'd see here if this is normal or known before running it up the flagpole on their git repo.
I'm making an application with WebVR using React VR. I'll test the application with my Oculus Rift and HTC-Vive. I'm using the browser Firefox Nightly to access the WebVR API's.
If I browse to my application using Firefox Nightly or Chromium, I arrive in an empty space with a loading message. A few seconds later I got this message on my Oculus Rift:
Sorry, firefox.exe/chrome.exe is taking a while to load. If this issue persists, please take off your headset and check this app on your computer.
On the HTC-Vive I got this message in Steam VR but it doesn't load at all.
(unresponsive) firefox.exe/chrome.exe
In the webbrouwser, I got the result I must see inside the headset with motion tracking.
I'm using this browsers
Version Firefox nightly: 55.0a1
Version Chromium: 56.0.2910.0
And this are my specifications:
GeForce: GTX 970
GeForce Game Ready Driver: 378.66
Processor: Intel® Core™ i7-6700 CPU # 3.40GHz
RAM: 15.87 GB
This isn't the Oculus software at all. The problem is an NVIDIA driver update that broke everything. You need to go to the NVIDIA site and download drivers from the "376" generation (Dec'16-Feb'17). Install those and the problems go away. I confirmed that things are working with Oculus 1.12, 1.14, and 1.14 beta channel.
It looked like Oculus broke things because 1.14 came out on almost the same day as the "381" NVidia driver update.
Downgrading my Nvidia driver to 376 worked as a charm for me, but I can't run the VR scenes on Nightly, just on Chromium.
I was able to get my Oculus to work with WebVR by enabling the Beta channel within the oculus app and letting it install an update. Seems like the current Oculus version might be broken.
Try installing SteamVR. SteamVR overrides the Oculus runtime and runs applications on its own.
Try closing Oculus Home before you launch your WebVR application using the WebVR button.
Make sure you are not in the Beta/Dash mode in Oculus
Try to disable the auto-opening of Oculus Home. Oculus home opens automatically on wearing the rift. To disable, select “Run as admin” field in the properties of the Oculus app. More specifically, go to /Oculus-Directory/Support/oculus-client/OculusClient, right click, select properties, check “Run as Administrator”.
Make sure that your Desktop and Rift are connected to the same Graphic card. You might need an HDMI to DVI converter for the same. This is what fixed the problem for me.
Ever since I have upgraded my laptop (Click here for hardware specs.) my screen usually freezes. Mostly in chrome or Firefox browser. I am pretty sure this is a Nvidia driver problem but I can't seem to find the solution. I am running a Nvidia Quadro K2100M.
I am currently running Nvidia 361.42. I have tried using open source Xorg server without any luck.
The only solution I have found so far is forcefully turning off the computer by holding down the power button.
Things that I have tried:
I got keyboard input
I cannot switch to another terminal to restart lightdm
This problem came to me occasionally, making me really annoyed.
As illustrated in many blogs, this may be caused by graphic driver problem. For me, my desktop has a NVIDIA video card, you can run lspci | grep VGA to see what type of your video type, in my case, it returned:
02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1)
I followed the instruction on jiakai zhang's blog to reinstall proper drivers for the desktop, hope this will help you.
The key steps in [1] are to reinstall the ubuntu desktop and nvidia drivier by:
$ sudo su
$ apt-get update
$ apt-get install --reinstall ubuntu-desktop
$ apt-get install unity
$ apt-get remove --purge nvidia*
$ reboot
$ sudo apt-get install nvidia-current
$ sudo reboot
Updating the grub settings worked for me! Do the following:
1. Open the GRUB configuration
sudo vi /etc/default/grub
2. Change the value of GRUB_CMDLINE_LINUX_DEFAULT from "quiet splash" to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"
and save the file.
3. Update & Reboot
sudo update-grub
sudo reboot
More info:
This is a bug in the processor, known as the c-state bug. It causes total freezes when the CPU tries to enter an unsupported sleep state. It's a problem for many Bay Trail devices especially with newer (4.*) kernels. There is a simple workaround until it gets properly fixed upstream. You just need to pass a kernel boot parameter and the random freezing stops completely. The parameter may increase battery consumption slightly, but it will give you a usable system. You do this by editing the configuration file for GRUB as described above.
GRUB - boot loader package from the GNU Project, which provides a user the choice to boot one of multiple operating systems
installed on a computer or select a specific kernel configuration available on a particular operating system's partitions;
Intel Bay Trail - new Atom Processors from Intel. Atom is Intel's family of x86 and x86-64 processors that are optimized
for small computing devices, such as smartphones and mobile Internet devices;
C-States - used to optimize optimize or reduce power consumption in idle mode (i. e. when no code is executed) - (C0 to C8)
Reference: here.
I have since fixed this problem by re-installing Ubuntu 16.04 and not switching from the nouveau video driver. I also disable updates and everything been working good for about 2 months now.
Gaming is pretty good but I usually play steam games so doesn't push any kinda hard core graphics
Well, I had the same problem: My PC was freezing randomly. I tried Ubuntu 16, 17 and 18.04 and everything was the same. I tried several drivers and didn't get a solution. I tried several solutions that I found in the forums (including this) and got bad and harmful results.
My solution was: I stopped using the graphical nvidia card, removed it and now I'm using the integrated Intel HD graphics card (Intel® HD Graphics 530 card (Skylake GT2)) and all the problems were solved!
I fixed mine using a few commands from #Qoros solution above. i just ran apt-get update, apt-get install nvidia-current, and sudo reboot. cheers to #Qoros btw!
For me, none of the approaches described in rest of the answers worked.
I was opening multiple terminal tabs running some heavy processes and ubuntu used to freeze when I had 6-7 tabs. I tried monitoring the resources used while I was starting my processes in terminal tabs. You can do it by opening System Monitor app and going to Resources tab.
What I noticed is that when my RAM(8GB) and my swap space(1GB) were completely used up, ubuntu would freeze.
As a solution, I increased my swap space and made it 16GB. After this memory never gets used completely and ubuntu doesn't freeze.
https://askubuntu.com/questions/178712/how-to-increase-swap-space decsibes how to increase swap space.
Goal
I was attempting to install Elastix 4.0 on a home PC via a Bootable USB, but never had any luck getting it to install past the CentOS7 part (it kept giving me a "Warning: /dev/root does not exist" error).
What I've Tried
My main PC is Windows 10 Pro, so after downloading the latest Elastix 4.0 .iso from "http://www.elastix.com/en/downloads/" (Elastix-4.0.74-Stable-x86_64-bin-10Feb2016.iso) I used UNetbootin to create my Bootable USB for Elastix 4.0. I put the now Bootable USB into the PC I want to put Elastix 4.0 on and started it up.
It gave me the "Install Elastix 4" menu, so I hit enter and waited. Then the install proceeded to do its checks for CentOS7, but ended up getting stuck and gave me an error message "dracut-initqueue[580]: Warning: Could not boot." and "Warning: /dev/root does not exist".
This is where I am stuck and cannot proceed.
EDIT #1: I signed up for the Elastix forms, and someone else also had this issue. They said they downloaded the .iso and used Rufus to make a Bootable USB, and then booted the installation using the Troubleshooting -> Install CentOS 7 using Basic Graphics ... but according to them, that apparently corrupted something else and then they opted to just use a DVD.
EDIT #2: I tested this, and making a Bootable DVD of the .iso does work great for local machines. Installing it via a VM also seems to work without hassle. As a personal goal, I would like to get this working via a Bootable USB.
Research
I did some research but a lot of the solutions I've noticed are using the dd command in Linux to make a Bootable USB for just CentOS7 because it is (was?) known that UNetbootin did not properly make a Bootable USB for CentOS7, and I can't seem to find anything that would assist in making the Elastix 4.0 .iso work properly via a Bootable USB. I did try other tools such as Rufus 2.7, Win32 Disk Imager, ISO2USB, and dd for Windows, though most rendered my USB not bootable at all (Rufus worked OK, but still got stuck at the CentOS7 part). Also, installing via a CD/DVD is not ideal, as I have no CD/DVD drive (and I want to see if I can get this working via a Bootable USB drive).
There seem to be a few guides out there for trying to create a Bootable USB for Elastix 2.x, but nothing for Elastix 4.0. Reviewing those, it looks like the guides reference some files that do not exist in the new .iso (ex: ks_default.cfg). Still, my issue pertains mainly to the CentOS7 error I'm getting so I don't think this is related.
Any assistance with this is appreciated, and if you require more information from my end just let me know. I'm willing to try / re-try anything.
Thank you in advance.
http://henrysittechblog.blogspot.ru/2014/01/install-elastix-from-usb-step-by-step.html
Look for this line, but it may change:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Change it to:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=sdb1:/dev/sdb1:/ks/anaconda-ks.cfg quiet
Hi there i solve this problem 80%.
i did some manual change at line:
inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Mine:
inst.ks=scsi:/dev/sdb1:/ks/anaconda-ks.cfg quiet
hd is not recogniced by Centos7.
made my usb bootable with rufus 2.9
then open isolinux.cfg with notepad++
just change the line
inst.ks=hd:sdb1:/ks/anaconda-ks.cfg quiet
where sdb1 used to say cdrom
I creating SD card by this guide: Archlinux Raspberry-pi-2 installation.
Previously everything working fine. 2016-01-11 I Archlinux OS with command "pacman -Syu". And it started to fail. And throw errors.
I think that it is becouse of SD card model and it corrupdet (see note "1").
So I tried to reinstall Archlinux and preapere again clean SD card.
Downloaded latest Archlinux and installed be using same guide.
But it on launch still throws same error.
Then I tried to install Archlinux to another newly bought SD card. But same error :(.
2.1 I tried to install Raspbian to same card, and it worked perfectly.
It looks to me for now that the latest Archlinux version is faulty. What is your suggestions, how to fix this, or something now about latest Archlinux release and if it is faulty, maybe know when next version (fixed) will be release?
See attached images with errors.
Note:
My SD card slot (the locking mechanism) in PI is broken so I have some tape to handle it in place.
I am using memory Transcend micro SDHC 32GB w/adapt/class10 ts32gusdu1 SD card.
I tried different 8 GB card and it worked. So this is latest Archlinux version problem with that Transcend micro SDHC 32GB SD card drivers (becouse I tried two new same vendor cards and Archlinux was failing to boot). Previously (installed , updated one month before) the OS worked fine with that card.