I just installed Kubuntu 14.04 on my HP laptop, but the resolution is off. Everything is way too big...and when i go to my settings, the only resolution available is 800x600....Can anyone please help me fix that.
Also, i have searched online but have not found anything that helps.
You need to change graphic driver. Unfortunately you provided not enough information to give you correct answer. With what you said I can only suspect that you probably don't have intel build in graphic card. It should work immediately. I assume you have nvidia or ati graphic card.
If yes go to Settings > Repositories > Additional Drivers tab and select the correct driver, and click Apply changes.
Related
Got an message in Windows 10(1903) about it not finding Nvidia control panel.
Message: "Nvidia control panel not found"
I have downloaded and installed the latest Nvidia drivers for my grafic card but I don't understand why the control panel is not being installed when the driver is installed.
Anyway I found some information that says that I need to install the Nvidia control panel from MS Store but here comes the problem, I have no internet access from that particular computer. I guess I want to download it from MS Store or somewhere else but where?
Is there any other trick to get the control panel for Nvidia to work?
best regards,
Hans
I installed an older driver version and that works with the control panel. The new driver does not.
I've Installed the newest version of Android studio, including the newest version of HAXM, ndk, sdk and whatever other related dependencies it installs. Intel Virtualization bios setting thingy I can't remember the name of is enabled and I have no trouble in virtual box and such.
I created an empty activity and tried testing it on the phone, works perfectly. Then I tried it on the emulator and there is a problem when it is hardware accelerated. It just opens a white window. The android studio displays 0 errors and thinks it ran the app properly. The graphics card I have is a gtx 1060 6gb. When it is software accelerated it works but is so slow I would rather use a chisel on a rock to draw the application usage.
So if someone knows a fix it would be nice.
Thanks
Well I have discovered that in order to solve the issue you have to go to the sidebar menu click More>Settings>OpenGL ES Renderer and(in my case) set it to Angle(D3D11) or Angle(D3D9) or Swiftshader. After that you simply restart the emulator and the issue should be gone.
For me Desktop native OpenGL and Autodetect based on host(which probably sets it to the first thing) don't work and leave you with a white screen.
In case someone finds this useful, you can set software acceleration as below and this solved the issue for me on Mac OS. (OP also mentions it works with software acceleration)
Tools > AVD Manager
Select virtual device
Click on Edit (pencil icon for me)
Click "Show Advanced Settings"
Look for Emulated Performance - Graphics
Select "Software" option
Current version of the emulator (27.1.3) doesn't work for me. The emulator just shows a white screen. Even playing with the gpu in the .ini configuration didn't work.
Once I downgraded to 26.1.4 (https://dl.google.com/android/repository/emulator-darwin-4266726.zip) the emulator started working again.
It seems that the Android Emulator is somehow conflicting with the NVidia Web driver on Mac OS. I had the latest NVidia Web driver (378.05.05.25f04) installed and I was having this same problem - the white screen whenever I used Desktop Native rendering (or left it at the automatic default which selects that as well).
I tried the Swift Shader as well, it works but the performance is abysmal!
On a hunch, I switched back to the OS X Default Graphic Driver from the Nvidia Pref Pane in Apple menu settings, and the Desktop Native driver is now working great after the computer restart!
The same problem can happen to the lightning fast Microsoft Android Emulators utilizing Hyper-V that work on both Intel and AMD CPU based PCs. The solution is in the same line as the accepted answer. For those who use Microsoft Android Emulators and land here by searching "android emulator white screen", here is the screenshot showing how to solve the problem by changing the default hw.gpu.mode from the default "auto" to "mesa":
So sorry
Check your onCreate method in your MainActivity.java, it should have setContextView(R.layout.activity_main)
I've got a new Dell Inspiron 17 (7779) laptop with Windows 10 x64 (1703) which was working fine right up until the point where HyperV was installed. Now the host screen flickers like mad even with no Guest VM's created.
Dell are being particularly unhelpful, so I was wondering is anyone else was having the same issue.
Basically is anyone running Hyper V on a dell Inspiron successfully.
I guess it could also be a clash with the display drivers (Intel HD Graphics 620, driver ver 21.20.16.4627)
OK, I think I've resolved this with the latest Intel graphics drivers 21.20.16.4678, however there were a few issues...
So the Intel drivers (21.20.16.4627) installed on the machine were the ones installed via the Dell Driver Detect tool, if you just download the latest drivers from intel and install them, it wont update them....I think there is some versioning issue with the dell drivers, as it seems to think the existing drivers are newer than the ones your trying to install....
In order to make it accept the new drivers you need to uninstall the existing display driver AND delete the install files. Then after a re-boot the display drivers used should be the default Microsoft ones, you can then upgrade the driver (again via computer manager) selecting the location of the downloaded and unzipped intel drivers.
I'd like to be able to thank Dell for there help, but they failed miserably to provide any.
One last thing...
For some reason windows automatically 'upgrade' the display drivers and re-installed a old version (21.20.16.4627) replacing the latest drivers I installed. I then had to rollback the automatic update, which fixed the issue again. Hopefully I won't have to keep doing this...
It looks like someone has made a mess of versioning some of these updates, its difficult to tell whether its an issue with the Intel drivers or the Dell wrapping of them as part of the driver detect tool, but there's definitely an issue.
I have a POS terminal (APEXA G from POSBank) that comes with multi-touch screen made by Silicon Works. The touch works perfectly on Windows there are official drivers for it. But for Linux the touch does not work at all. After inspecting the device on Linux Ubuntu distribution using [lsusb -v] command I get the follow information:
Silicon Works Multi-touch Device, VID:PID 29bd:4101
The touchscreen is connected through usb not serial connection.
I tried several generic drivers online but none of them worked for me.
After emailing POSBank technical support I received their quick response which solves my problem.
Following their instructions here is what I did:
1. Uninstall the old touch drivers:
- Lanuch Device Manager
- Human Interface Device -> Usb Input Device
- Remove a USB input device with a value of VID_29BD in the attribute (PID is 3711 or 4101)
2. install latest drivers chipset, LAN, touch, etc... (These drivers downloaded from POSBank official website)
-------------------------------------------------
Please note:
-You need Windows only to run the software that applies the touch firmware upgrade.
-Touch firmware v1.8 is still not available from POSBank official website yet
you have to contact technical support or email me.
-You Must Install SiW Daemon Control Panel to upgrade the firmware (it is included in the touch driver zip file from POSBank official website)
-------------------------------------------------
upgrade the touch firmware to V1.8 using instructions below:
Open SiW Daemon Control Panel
On device tab press F6
Select Multi-touch device 0
Click File open then select the firmware update file
Click FW update
After Ubuntu boots the touch should start working out of the box no special configuration is needed.
Note: After the upgrade the touch may not work on Windows. Don't Panic. You will hear a beeping sound every time you click on the screen which is a good sign. To fix do the following:
Open SiW Daemon Control Panel on the Device tap
select Multi-touch Device_0 then click Open Device
select Mouse table(2nd tap) and check Emulation Mode
select About tab and click Preserve Settings which preserves the settings through Windows restarts.
If you have any questions please let me know.
I am happy with their solution now touch works for me on Windows and Ubuntu.
Thank you POSBank and special thanks to Peter Kim from the technical support.
This is a chronological continuation of this question.
I have simplified my board so it runs well with the DDK version of BulkUSB on 32bit versions of XP and Vista, but I'm not able to install it on Vista 64.(built with amd64 fre)
I've been able to make windows recognize the files it needs to install, using both BulkUSB and USBSamp, but once installed it says
Windows cannot load the device driver for this hardware.
The driver may be corrupted or missing. (Code 39)
In problem code property in the details, it says 27.
When I install it for the first time, it complains about the driver not being digitally signed, and I've tried running:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
As there are placed that mention it should make windows run unsigned drivers, but it doesn't help.
If anyone has an insight about this, any help will be appreciated.
Thank you,
Surd.
Edit another part of the deal it took me a long time to find that isn't anywhere in the questions or answers:
When unintalling a driver, you either need to check "remove driver" in the device manager or use pnputil -d oem##.inf to remove the driver, otherwise the new drivers won't be used.
Even after changing the bcedit options, it is impossible to load unsigned drivers under Windows Vista/7 64 bit. You need to make test-signing for the driver. I solved this problem following instructions from "Kernel-Mode Code Signing Walkthrough" document which can be downloaded from the Microsoft site: http://www.microsoft.com/whdc/driver/install/drvsign/kmcs-walkthrough.mspx
Unsigned drivers cannot be loaded by Vista/7 64 bit in any case. Test-signied drivers can be loaded after changing bcedit options. Release-signed drivers are loaded without restrictions, but with warning message. You can make test-signing yourself, following this document instructions. For release-signing, it is necessary to buy a code-signing certificate.
The final (and optional) step is passing the tests from the Windows Logo Kit (WLK). This allows to remove the warning message shown during driver installation.
I am getting this error message on windows 10: 'Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)'.
After following https://www.tenforums.com/tutorials/104025-turn-off-core-isolation-memory-integrity-windows-10-a.html this, the issue is solved for me.