St1000lx015-1u7172 Driver

0 views
Skip to first unread message

Elenor Waas

unread,
Aug 5, 2024, 3:25:48 AM8/5/24
to viorihanria
Lookfor the Audio Realtek driver for your laptop here. Download that and run the installer. This should update or reinstall the latest certified audio driver for the onboard sound. Make sure you properly restart the system afterwards. That means, click the Start (Windows Flag button) choose power, choose restart computer, not shutdown. Let it reboot, then relaunch and see if that helps.

Go to Documents.

Look for Diablo IV.

Find the LocalPrefs file in here.

Rename this file, then re-launch the game. This will reset the game settings to their defaults. So it will put you through first time setup, and you may need to reset any graphic settings you were using. But do this only after trying the driver from Asus.


You may try sudo dnf distro-sync to see if that will solve the issue. You also could use pkcon refresh --force to ensure that the gnome software tool is fully synced with the system status and the repo as well. I would recommend that you do both to ensure your current messages are suppressed.


To check if nvidia is in use repeat the commands I gave you above.

lsmod grep nvidia

If that returns a list of modules that are active then the nvidia driver is in use.

Also please post the output from cat /etc/X11/xorg.conf.d/nvidia.conf


The only issue I see with the nvidia GPU is that with wayland the external monitor does not function, whether nvidia is set as primary or not. When I use xorg both monitors work properly, either mirrored or independently.


Is this bug significant? :

[ 4.925954] nvidia-gpu 0000:01:00.3: i2c timeout error e0000000

dnf list installed kernel-devel kernel-headers

[ 4.955384] nvidia: module verification failed: signature and/or required key missing - tainting kernel


Edit: New discovery! It seems there is something about idling that's getting to it. If I load a program immediately as after the OS is finished loading the speed is perfect and phenomenal, but if I wait for say half an hour or more before loading anything from disk it works too slowly. I suspect Windows 10 is doing something on it if it's left for idle too long.


I have a SSD as main disk drive for frequently used applications and OS (Windows 10) and a second HDD 1TB Seagate Barracuda. The SSD is fine, the problem is with the HDD. It has the exact same issue as it was with the previous unit before it was replaced.


Early on the disk was running fine for about a month or two, but recently it became slower than dirt. Any read write action would lead to 100% disk usage with barely a few KB of data transfer actually happening.


In the Task Manager I noticed it was msmpeng.exe scanning it all the time which is Windows' antimalware tool, so I added the drive into exclusions for it so that it no longer scans the disk leading to disk usage because of it, but the problem stopped only temporarily


Opening a large file like a video is so slow that the playback become choppy as the system struggles to read the file as it is being played. It sometimes becomes universally slow as in anything that uses the drive becomes dirt slow as well, including defragmentator, chkdisk, image thumbnail generation or any disk check utilities.


Since it was sealed packed and everything like its predecessor I don't suspect a vendor foul play yet, but rather something wrong with the configuration of the system or damage from a faulty power supply, etc.


Suggest 1. testing that adequate power supply is available for this drive.2. check that corrrect PM and ACPI drivers are loaded (my experience is with Lenovo, and they are quite famous for providing bad drivers)3. if possible replace drive with another one as a test.


Even though the post is a bit older I thought id share my experience for future readers:I had a somehwat similar experience with a 3TB Seagate Harddrive that suddenly operated excruciatingly slow. That also showed in the TaskManager, the hard drive was always at 100% utilisation.


I then checked the services and processes again, sorting by drive utilisation, and found the Oracle RDBMS kernel executable among the top processes with about 10% usage (its always hard to tell which drive is used, since I got 3 in the computer and TaskManager wont tell you which one is used). After killing that the usage of the "bad" drive went down to 0% again. I have no idea what oracle's executable was doing there, but it did the trick.


So I recommend checking your process list and getting rid of this and that before you start messing with the Registry or the BIOS like I did (the latter screwed up my boot order and PC would not boot, got a bit scared there but managed to fix it), sometimes the solution can also be simple ;)


Windows 10 seems to have some serious driver issues with SSDs, from my limited experience. Windows 7 seemed quite hunky-dory and happy with having one swapped in (did that about a year ago for someone who was very happy with it.)


I just helped a kid replace a drive on Windows 10 and it kept going to 100% disk use (reported; and it would become unresponsive/hung) with no (or very little) actual disk use, a search found many instances of the same problem, and various "solutions" (many of which did not work for us.) In this particular case, what worked for us eventually was setting the drive mode (which started out as "RAID" - kinda odd for a 1-disk-space laptop) and also failed for us as AHCI back to IDE.


There's a Microsoft forum post claiming that changing the interrupt setting fixes the problem, but it did not work for us...likewise someone claimed that going from RAID to AHCI worked for them. So what will work for you, I don't know - I just report what appears to have finally worked for us.


I should note that this problem did not "wait a month" - we could not get get the initial windows 10 updates to load because the computer kept hanging (original disk died, no backup, reinstall 7 from CD and re-upgrade to 10)


I would say reboot computer and wait for it to fully load. Press ctrl+alt+del to access Task Manager. If the hard drive is constantly reading/writing at 100% when system should be at complete idle, check for updates. Ever since Windows 10 came out pending updates cause PC to run at snail speed due to this.


If it's not an update issue run chkdsk (run CMD as admin then type in "chkdsk D: /f" , with D being the whatever letter your drive is. But from my experience, it can still pass Check Disk with flying colors and 100% be a failed/failing hard drive. No matter what if you have a spinning-disk hard drive you should upgrade to SSD (They start at $15 for SATA SSD). If it passed chkdsk then it will likely pass any hard drive test your Bios has available.


If there are no updates available, reboot the PC again and double check for the constant read/write at 100%. If everything is normal yet it still runs incredibly slow then it is for sure defective. Backup your data immediately. Then load a new Windows system for your final confirmation. If it still runs slow (and you'll likely notice it during the OS install), then the disk is bad.


This might help someone: my HDD was suddenly super slow with projects taking like half a day to copy. THEN I realized I moved the PC recently, and since I was in headphones I couldn't hear it was now making bad noises. After I re-adjusted the PC so it was less slanted everything is now FAST again! So literally, if this happens to anyone just try to make sure your PC is sitting on a flatt-er surface first. cheers!


I use linux kernel 6.1 in my laptop and it causes kernel panic after boot up

I try to disable mt76x0e driver by modify /etc/modprobe.d/modprobe.conf

And I modprobe the driver manually and nothing happens

kernel panic only occurs when I try to get the network connection(wherever dhcp or static IP)


I downgrade linux kernel to 6.0.12 which fixed the issue.

At the moment of kernel panic, system is dead, long press power button is the only thing I can do.

How can I get more information for debugging?


But turning the resolution back should then solve the issue. As it does not get the performance back there seems to be a different modification done to your hardware/drivers/operating system too ... are you aware of any changes?


Well, I don't know that, but could imagine what happens ... each movement of the mouse and so the crosshair means AutoCAD has to look at the position of the mouse if there exists an object at that location (to highlight the object) or if there exist multiple objects at that location (to show the SELECTIONCYCLING icon) and a lot more test are done.


When you now tell AutoCAD to select objects 1000 times a second means it blocks the mouse as it can't select that fast ... however, with 125 seconds AutoCAD has enough time to get the selection and proceed.


I am not able to figure out why windows is not recognizing the daplink drive. It does not show up at all. When I opened the create and format hard disk drive partitions, I figured out that windows is asking me to initialize it everytime (shown below)


My point was to help you determine in which state your board currently is. According to the guide what I shared above.

So if you determined your board is in a bricked state, then is probably no other way to do it.


Here you can find different firmwares for that board, you have to choose depending on which MCU you are about to program with. If you have a second MAX32625PICO board you can try to upload max32625pico_max32625pico.bin to your problematic board over the second one. That should help if your pico just can not go into maintenance mode for some reason but is still not bricked. However if also this does not help, then chances are high it is not recoverable anymore.


That is interesting as i work on windows only and never faced the issue with my MAX32625PICOs you described. So hard to tell what could have caused it, but luckily it does not mean the board is bricked.


Hey, that worked like a charm! Initially when I uninstalled the drivers and plugged it in it showed the DAPLINK drive. But I could not get it to go into MAINTAINANCE drive at all. So this time, I uninstalled the driver and then directly made it to go to MAINTAINANCE drive. And after that it started showing DAPLINK and MAINTAINANCE drives properly! Thanks a lot!

3a8082e126
Reply all
Reply to author
Forward
0 new messages