Intel Core i5-6600k The kernel parameters established i915.preliminary_hw_support = 1 option for the new processors. When connected to a monitor, then everything is fine, but when I connect a second monitor to get the hang of the moment of transition to the login screen.
Sorry for my english. Help me please.
You should file a bug against the Intel drivers. See https://01.org/linuxgraphics/documentation/how-report-bugs for details.
Related
So, my knowladge in embedded development is quite bad and now I am trying to receive some data from PC inside my MCu STM32F429IGT6 which is on WaveShare Core4X9I dev-board and send it back via USB Virtual COM Port.
I realized how to set up connection from MCu part and I even see connected device from Windows 10 Device Manager but... it appears as STM Device in DFU Mode
I have tryed already to install drivers from ST for such things but they are useless and official documentation says that they are not needed for Windows 10.
I have been following tutorials where guys just clicked several times inside Cube MX, generated code and VCP worked out of the box.
The question is what am I doing wrong? I don`t even know what information you might ask for thats why I created GitHub repo: https://github.com/dessy4oko/stm32f429-vcp-appears-as-dfu
And this is events from Device Manager of Windows 10 (translation from ru lang):
Device USB\VID_0483&PID_DF11\305233703237 is running. code 410
Device USB\VID_0483&PID_DF11\305233703237 is configured. code 400
Device USB\VID_0483&PID_DF11\305233703237 have not been moved due to partial or ambiguous matching. code 442
Device USB\VID_0483&PID_DF11\305233703237 requires further installation. code 430
Thank you for any information about my mistakes.
STM32 starts in DFU mode if BOOT-pins are pulled accordingly:
"System memory" means embedded bootloader, DFU in this case. You need "Main Flash" to run your app.
Check jumpers and switches on your board. Refer also to the AN2606 app note for complete information.
I am currently building a cost efficient Open Thread network. In my setup i have few Full thread devices and Minimal Thread Device which will be sending data to cloud via Border Router. I have currently setup a RCP design Open Thread Border Router on RPi 3B+ by following the open thread docs and its working fine.
Doc Link: Open Thread Border Router Build and Configuration
Now as i want my final product to be as cost efficient as it can be, i would like to consider using RPi Zero W for setting up my Open Thread Border Router. So i was following the same steps mentioned in OTBR doc to setup it on RPi Zero W, i came across this line in Step 3 which states " Before you continue, make sure your configured hardware platform is connected to the internet using Ethernet. The bootstrap script disables the platform's WiFi interface and the setup script requires internet connectivity to download and install several packages. "
But my RPi Zero W only have WiFi interface. So i wanted to know, is it even possible to run OTBR setup on RPi Zero W ?
I have also read in docs that "Open Thread Border Router (OTBR) provides support for the Raspberry Pi 3B or newer (RPi) platform". But have anyone tried the same setup on RPi Zero W and was successful ? Because in the end as i said, i would like my final product to be as cost effective as possible.
Also find the attachment of the error i am facing:
If you are not setting NETWORK_MANAGER=1 when running ./script/setup, I think it would work with just the Wi-Fi interface.
You can try running the following setup command:
INFRA_IF_NAME=wlan0 ./script/setup
Hello everyone and sorry for my mistakes,
I am new with the virtual machine and I have to work on it. To do so, my school forced me to work on VMWare VSphere Client. The version I am currently using is the 5.5.
My problem is that when I do a right on the desktop, there is an offset between the mouse and the menu. I tried to unistall and reinstall it, but this problem always appears. I also tried to tun it with the Windows 7 compatibility and the others compatibility.
My problem : Offset between the mouse and the menu
I know that this problem is due to my computer because the same version of VMWare VSpere Client works perfectly on similar computers but not on mine.
My computer config :
ASUS K501UW
RAM 8Go
64 Bits
Intel Core i7
Tank you by advance for yours helps.
This is really very late, but perhaps this helps others. I had the mouse click problem with Windows 10 and viclient 5.5 too. This was because I was using custom display scaling in Windows 10. I changed to de-select the option "Let Windows try to fix apps so they're not blurry" and then the mouse clicks worked again in viclient. I did not have to disable custom scaling.
I have a Windows 7 Ent - 64bit system.
I am stuck in a loop, where the login screen is presented, i enter my network credentials, the welcome spinner is shown, the screen flickers like when resized, then the system goes to logging off screen and then finally goes back to the control alt delete screen.
I cannot get out of that loop for the life of me.
I contacted corp support, he came over and logged in using his login (admin level) and was able to get a desktop up.
The support people are not allowed to access the registry to correct or even look at my users settings, and my user IS NOT AN ADMIN on this machine.
Question is - is there a way to blow away my profile on this machine, or reset my registry branch to that of a new user or something???
i have bitlocker enabled on the drive - so using the emergency boot disks are almost rendered useless...
im stuck, and i dont know where to look....
any ideas would be wonderful
thanks
the admin level user logged in, and turned his back for a moment, and i was able to go in and reset the autologon registry entry...
rebooted,and all is well.
Disconnect Your USB Devices
If you like using all sorts of USB devices such as the mouse, keyboard, speakers, Bluetooth speakers, USB dongles, USB Wi-Fi adapters etc. However, these connected devices might cause the Windows 7 stuck on the welcome screen for a long time issue. Therefore, a common solution to the problem is to disconnect all externally connected devices from your PC.
Disconnect from the Internet
Sometimes Windows 10 gets stuck on the login screen because it's trying to connect to your wireless connection. If your Windows gets stuck on the welcome screen, you should make sure that you are not connected to the internet before proceeding to log in.
Run system checks
In some case, corrupt system files on your computer will cause this problem – stuck on welcome screen Windows 10/8/7. Therefore, to fix the Windows 10 freezes on startup problem, you can use CHKDSK to run some checks on your computer to see if it is the corrupted files that cause your startup problem.Restart Windows Update service
You can try restarting Windows Update service and then rename few files if you still get stuck on welcome screen Windows 10 issue.
Here are the steps:
Step 1. Open command prompt.
Step 2. Type net stop wuauserv in the run dialogue and press Enter.
Step 3. Type cd %systemroot% command and press Enter.
Step 4. Type ren SoftwareDistribution SD.old and press Enter.
Step 5. Type net start wuauserv and press Enter.
Step 6. Type exit and press Enter to close Command Prompt and restart your PC.
Step 7. Now, reboot your PC/laptop and check if the stuck on welcome screen has gone.
Restore Windows by using System Restore
System Restore is a useful feature that allows you to restore your operating system to a previous state and fixes any boot problems such as Windows 10 freezes on startup, Windows 7 hangs on welcome screen, etc.
I have this strange problem in an embedded system (linux) we build, so I don't have normal GUI trouble-shooting tools on Linux or Windows machines.
The problem is the NIC is no longer usable after cable removed. Even if I re-plug the cable, the lights on it never come back on again and nothing can be sent or received. ifconfig still works on the surface, but doesn't have real effect. Only a reboot will solve the problem. I guess the problem is in the ethernet driver.
My question is how the trouble-shoot it. Any clues/hints? Thanks.
====================
Thank you guys! The board is a gumstix and the PHY is SMSC911x. We are running on Linux 3.0.12. It turns out the smsc911x_soft_reset() of the NIC fails when driver calls smsc911x_open(). The symptom also includes we must run ifconfig multiple times (not consistent) to bring the NIC up and the system can detect it.
I did a search on "SMSC911x soft reset failed" and find this link. http://comments.gmane.org/gmane.linux.network/216467. I removed SMSC_PHY=y in the linux build config file and that fixed the problem. It seems the driver is not compatible. Can somebody explain this, or is there a better solution?