Same issue as most other people, can't boot after upgrading graphics drivers. All I get is a flashing cursor in top left. Can't switch tty with alt+f1/f2 etc or ctrl+alt+f1/f2 etc can't get grub to load with holding shiftkey on boot. Completely lost. Ubuntu 13.10.
I know what to do IF I get to the prompt or terminal. But I can't even get there.
Best regards.
Can be loaded in text mode.
Press 'e' to edit
Add in the right place 'nomodeset' and CTRL+X
P.S. images for example
Related
I'm using Apache Guacamole 1.2.0 and XRDP 0.9.12 on Ubuntu 20.04.
When looking at the remote desktop the fonts are shown sometimes reasonably sharp (alas still less than when opening an RDP connection directly), but often become blurry/blocky, as shown in the following screenshot.
It's possible to "provoke" this by letting the browser window loosing the input focus. But it also happens while working on the remote desktop. By triggerings repaints (e.g. by going with the mouse over the text) the fonts become sharp again at the repainted screen regions while staying blurry at the other screen regions.
The RDP connection settings in Guacamole are configured like this:
I played a bit with the font smoothing and caching options, but could not improve the situation.
Is there any way to keep the fonts from "going blurry"?
Best regards,
Bernd
I reinstalled with compiled versions xrdp 0.9.14 and xorgxrdp 0.2.14 - I had to do this anyway, because file sharing does not work between Guacamole and xrdp 0.9.12.
As a "side effect", the blocky/blurry appearance is gone now, too.
Either it has been fixed with the newer version or my old installation was somehow faulty.
I am using a BBB with the Debian distro. I access Cloud9 (192.168.7.2:3000) via Chrome on my Windows 7 machine. I am able to access existing demo js programs and have written a test program (myblink.js). The editor and overall system works fine.
But when I try to run the program, nothing happens for a few seconds, then eventually, it appears to stop on the first line (which becomes highlighted yellow). When this happens, the debugger panel pops out and the bottom window shows that the "debugger listening on port 15454" and I have the option to stop the program. At this point I can step through the program, well, at least to the point where there is some asynchronous events handling required.
However, if I run "node myblink.js" app from the bash tab in Cloud9 or from a shell (via putty) it works perfectly fine.
Do I have to set anything up to enable debugging? Or is it too much to expect from the debugger and a BBB system?
I have installed fresh Arch Linux with linux-ck and awesomewm. After that I have installed google-chrome and started it. Everything works well, but if I open other application (chrome lose focus) and then got back to the chrome, it freezes. Mouse cursor works as expected (cursor changes after hovering link, input field, etc) but view is not updated.
Everything works well again if I change desktop to the second and go back to the first again (mod+2, mod+1). Chrome works, responses etc well.
I bet this issue has something in common with hardware acceleration. If I run some game (steam), lose focus, get back to the game - it shows last rendered screen before focus has been lost (sound is ok, game is responsible but does not update screen).
I use nvidia. Do I need some extra configuration to handle it ?
You want to disable "Use hardware acceleration when available" in Chrome settings.
For me, disabling hardware acceleration as Alex pointed out solved the issue. This bug has been brought forward before in awesome's issues GitHub page.
Apparently, the problem is not awesome. Graphics drivers might be involved but the main suspect seems to be the compositing manager. Running awesome with the "--no-argb" flag and disabling the comp manager seems to solve the problem.
The problem was xcompmgr which caused "freezing" view. I switched it to unagi and all of the problems have gone.
Hope this doesn't sound crazy or something
I am trying to create a mini O.S. (who didn't?, it is like visiting Mecca for a muslim - any programmer must do it at least once in his life)
So, I created a simple boot-loader, that works fine when executed from a virtual boot-able ISO, in a virtual machine (Oracle VM Virtual Box). It just displays a message for now.
At this point, I am supposed to give the control to another code, that would start being my O.S. All this will be executed from the virtual optical disk. I could burn it on a CD and run it on a i386.
No, to make this really something, I want to run the "O.S". from a hard disk, so I wonder if there's a way to "burn" the boot-able information (boot-loader and other files to be loaded) directly on a virtual disk (like .vmi, .vhd, .hdd)
When I install a conventional O.S., like Windows or Linux, from an ISO image, on the virtual machine, the boot-loader starts a new code section, that installs the O.S. on the virtual disk. That is how I should do it, too: create a installer for the O.S., that would write my booting section on the virtual disk. That means that everytime I make a change to my O.S. I must re-install it. I don't like that. I would like to be able to write the booting code directly inside the virtual disk file, start the machine in Virtual Box, and see it running. I opened the .vmi file with an HEX editor but I cannot figure out where should I place the code to be considered boot-able.
Now, tell me whether I don't know what am I talking about or is there a solution for this.
Thanks to everybody!
I found out how to do it. Create a vmdk disk, open in in a HEX editor and paste the bootable information starting from 0
I have a strange bug somewhere in my system that causes the screen to move very fast when it occurs (I can't really describe it) and I learned to deal with it by putting my laptop to sleep then waking it up ..
I'm suspecting it's something with the display driver, and it gets fixed if the driver is restarted.
Is there a way to restart the display driver programmatically?
I noticed sometimes in vista the screen blanks for 2 seconds and a ballon tip appears in the tray saying the display driver had to restarted due to something blah blah.
So I figured there must be a way to restart it in code.
What I want to do is write a command line tool that restarts the display driver so that I can launch it with a keyboard combination when I need to.
[ UPDATE (30/1/2009) I tried restarting the aero service as suggested, but it didn't solve the problem. ]
it seems the name of the display driver "service" is igfx, however, I can't stop it from the command line
C:\>net stop igfx
The requested pause, continue, or stop is not valid for this service.
More help is available by typing NET HELPMSG 2191.
C:\>NET HELPMSG 2191
The requested pause, continue, or stop is not valid for this service.
There are two things you can try, which will restart various parts of the video stack.
Restart DWM (Aero/Glass) with:
net stop uxsms
net start uxsms
Change the resolution with a utility such as setres.exe