|
On September 29 2018 05:34 plasmidghost wrote:
Is anyone here a frequent user of Debian/Kali? My Kali OS keeps rebooting after 15 minutes of being idle and it just started doing it last week. I posted this question on the Kali troubleshooting forums (https://forums.kali.org/showthread.php?42125-Kali-automatically-logging-out-rebooting-when-idle) but haven't received a reply yet. Just curious if anyone knew where I should look to see what the problem could be
Read your syslog at the time of the reboot. Check dmesg -T. I like to check the kernel log but I doubt anything would be in there.
Check what systemd https://wiki.debian.org/Suspend is doing at the time of suspend.
Here is a StackExchange reply for Ubuntu recommending almost the same thing: https://askubuntu.com/questions/47311/how-do-i-disable-my-system-from-going-to-sleep
|
|
|
On September 29 2018 12:37 plasmidghost wrote:Show nested quote +On September 29 2018 10:29 Thaniri wrote:On September 29 2018 05:34 plasmidghost wrote:
Is anyone here a frequent user of Debian/Kali? My Kali OS keeps rebooting after 15 minutes of being idle and it just started doing it last week. I posted this question on the Kali troubleshooting forums (https://forums.kali.org/showthread.php?42125-Kali-automatically-logging-out-rebooting-when-idle) but haven't received a reply yet. Just curious if anyone knew where I should look to see what the problem could be Read your syslog at the time of the reboot. Check dmesg -T. I like to check the kernel log but I doubt anything would be in there. Check what systemd https://wiki.debian.org/Suspend is doing at the time of suspend. Here is a StackExchange reply for Ubuntu recommending almost the same thing: https://askubuntu.com/questions/47311/how-do-i-disable-my-system-from-going-to-sleep Thank you for the reply. I ran the command from the AskUbuntu thread and it still rebooted itself. I looked at my /var/log/syslog file and this is what systemd said for around the time it rebooted itself: + Show Spoiler +Sep 28 22:12:38 kali dbus-daemon[652]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=653 comm="/usr/sbin/NetworkManager --no-daemon ")
Sep 28 22:12:38 kali systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 28 22:12:38 kali systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 28 22:12:38 kali gsd-sharing[1380]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
Sep 28 22:12:38 kali gsd-sharing[1380]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
Sep 28 22:12:38 kali systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Sep 28 22:12:38 kali systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Sep 28 22:12:38 kali systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Sep 28 22:12:41 kali systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
Sep 28 22:12:41 kali systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
Sep 28 22:12:41 kali /usr/lib/gdm3/gdm-x-session[874]: (EE) systemd-logind disappeared (stopped/restarted?)
Sep 28 22:12:41 kali systemd[1]: systemd-logind.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Sep 28 22:12:41 kali systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 1.
Sep 28 22:12:41 kali dbus-daemon[652]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.14' (uid=130 pid=876 comm="/usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/use")
Sep 28 22:12:41 kali systemd[1]: Stopped Login Service.
Sep 28 22:12:42 kali systemd[1]: Starting Login Service...
Sep 28 22:12:42 kali systemd[1]: Started Login Service.
Sep 28 22:12:42 kali /usr/lib/gdm3/gdm-x-session[1174]: (EE) systemd-logind disappeared (stopped/restarted?)
Sep 28 22:12:42 kali /usr/lib/gdm3/gdm-x-session[874]: (EE) systemd-logind: ReleaseControl failed: You are not in control of this session
Sep 28 22:12:42 kali /usr/lib/gdm3/gdm-x-session[1174]: (EE) systemd-logind: ReleaseControl failed: You are not in control of this session
Sep 28 22:12:42 kali systemd[1148]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
Sep 28 22:12:42 kali systemd[1148]: gnome-terminal-server.service: Failed with result 'exit-code'.
Sep 28 22:12:42 kali systemd[1148]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
Sep 28 22:12:42 kali systemd[1148]: pulseaudio.service: Failed with result 'exit-code'.
Sep 28 22:12:42 kali systemd[1]: Started Session c2 of user Debian-gdm.
Sep 28 22:12:42 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
Sep 28 22:12:42 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
Sep 28 22:12:42 kali systemd[1148]: pulseaudio.service: Service RestartSec=100ms expired, scheduling restart.
Sep 28 22:12:42 kali systemd[1148]: pulseaudio.service: Scheduled restart job, restart counter is at 1.
Sep 28 22:12:42 kali systemd[1148]: Stopped Sound Service.
Sep 28 22:12:42 kali systemd[1148]: Starting Sound Service...
Sep 28 22:12:42 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 21 paused 0
Sep 28 22:12:42 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event10 13:74 fd 24 paused 0
Sep 28 22:12:42 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 25 paused 0
Sep 28 22:12:42 kali dbus-daemon[652]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.250' (uid=0 pid=2798 comm="/usr/bin/pulseaudio --daemonize=no ")
Sep 28 22:12:42 kali dbus-daemon[652]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Sep 28 22:12:42 kali systemd[1148]: Started Sound Service.
Sep 28 22:12:42 kali pulseaudio[2798]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
Sep 28 22:12:42 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 26 paused 0
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 27 paused 0
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event19 13:83 fd 28 paused 1
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: releasing fd for 13:83
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 28 paused 1
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: releasing fd for 13:64
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 28 paused 1
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: releasing fd for 13:67
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 28 paused 1
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: releasing fd for 13:68
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got fd for /dev/input/event8 13:72 fd 28 paused 1
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: releasing fd for 13:72
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: returning pre-existing fd for /dev/input/event2 13:66
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: not releasing fd for 13:66, still in use
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (EE)(II) systemd-logind: got pause for 13:70
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (EE)(II) systemd-logind: got pause for 13:66
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got pause for 13:74
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got pause for 13:71
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (EE) (II) systemd-logind: got pause for 13:65
Sep 28 22:12:43 kali /usr/lib/gdm3/gdm-x-session[2790]: (II) systemd-logind: got pause for 226:0
Sep 28 22:12:44 kali dbus-daemon[652]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.254' (uid=130 pid=2839 comm="/usr/bin/gnome-shell ")
Sep 28 22:12:44 kali systemd[1]: Starting Locale Service...
Sep 28 22:12:45 kali dbus-daemon[652]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.254' (uid=130 pid=2839 comm="/usr/bin/gnome-shell ")
Sep 28 22:12:45 kali systemd[1]: Starting Location Lookup Service...
Sep 28 22:12:45 kali systemd[1]: Started Locale Service.
Sep 28 22:12:45 kali systemd[1]: Started Location Lookup Service.
Sep 28 22:12:45 kali dbus-daemon[652]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.258' (uid=130 pid=2877 comm="/usr/lib/gnome-settings-daemon/gsd-media-keys ")
Sep 28 22:12:45 kali systemd[1]: Starting Hostname Service...
Sep 28 22:12:45 kali dbus-daemon[652]: [system] Activating via systemd: service name='org.freedesktop.realmd' unit='realmd.service' requested by ':1.254' (uid=130 pid=2839 comm="/usr/bin/gnome-shell ")
Sep 28 22:12:45 kali systemd[1]: Starting Realm and Domain Configuration...
Sep 28 22:12:45 kali systemd[1]: Started Realm and Domain Configuration.
Sep 28 22:12:45 kali systemd[1]: Started Hostname Service.
Sep 28 22:12:48 kali systemd[1]: user-runtime-dir@0.service: Unit not needed anymore. Stopping.
Sep 28 22:12:48 kali systemd[1]: Stopping User Manager for UID 0...
Sep 28 22:12:48 kali systemd[1148]: Stopping D-Bus User Message Bus...
Sep 28 22:12:48 kali systemd[1148]: Stopping Virtual filesystem service...
Sep 28 22:12:48 kali systemd[1148]: Stopping Accessibility services bus...
Sep 28 22:12:48 kali systemd[1148]: Stopping Evolution calendar service...
Sep 28 22:12:48 kali systemd[1148]: Stopping Virtual filesystem metadata service...
Sep 28 22:12:48 kali systemd[1148]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Sep 28 22:12:48 kali systemd[1148]: Stopping Virtual filesystem service - disk device monitor...
Sep 28 22:12:48 kali systemd[1148]: Stopping Evolution source registry...
Sep 28 22:12:48 kali systemd[1148]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Sep 28 22:12:48 kali systemd[1148]: Stopping Tracker metadata database store and lookup manager...
Sep 28 22:12:48 kali systemd[1148]: Stopping Virtual filesystem service - digital camera monitor...
Sep 28 22:12:48 kali systemd[1148]: Stopped target Default.
Sep 28 22:12:48 kali systemd[1148]: Stopping Sound Service...
Sep 28 22:12:48 kali systemd[1148]: Stopping Evolution address book service...
Sep 28 22:12:48 kali systemd[1148]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Sep 28 22:12:48 kali systemd[1148]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Sep 28 22:12:48 kali systemd[1148]: Stopped Virtual filesystem service - digital camera monitor.
Sep 28 22:12:48 kali systemd[1148]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Sep 28 22:12:48 kali systemd[1148]: Stopped Virtual filesystem metadata service.
Sep 28 22:12:48 kali systemd[1148]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Sep 28 22:12:48 kali systemd[1148]: Stopped Accessibility services bus.
Sep 28 22:12:48 kali systemd[1148]: Stopped Sound Service.
Sep 28 22:12:48 kali systemd[1148]: Stopped Virtual filesystem service - disk device monitor.
Sep 28 22:12:48 kali systemd[1148]: Stopped Evolution source registry.
Sep 28 22:12:48 kali systemd[1148]: Stopped Evolution calendar service.
Sep 28 22:12:48 kali systemd[1148]: Stopped Evolution address book service.
Sep 28 22:12:48 kali systemd[1148]: Stopped D-Bus User Message Bus.
Sep 28 22:12:48 kali systemd[1148]: Stopped Tracker metadata database store and lookup manager.
Sep 28 22:12:48 kali systemd[1148]: Stopped Virtual filesystem service.
Sep 28 22:12:48 kali systemd[1148]: Stopped target Basic System.
Sep 28 22:12:48 kali systemd[1148]: Stopped target Timers.
Sep 28 22:12:48 kali systemd[1148]: Stopped target Paths.
Sep 28 22:12:48 kali systemd[1148]: Stopped target Sockets.
Sep 28 22:12:48 kali systemd[1148]: Closed Sound System.
Sep 28 22:12:48 kali systemd[1148]: Closed GnuPG network certificate management daemon.
Sep 28 22:12:48 kali systemd[1148]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 28 22:12:48 kali systemd[1148]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 28 22:12:48 kali systemd[1148]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 28 22:12:48 kali systemd[1148]: Closed GnuPG cryptographic agent and passphrase cache.
Sep 28 22:12:48 kali systemd[1148]: Closed D-Bus User Message Bus Socket.
Sep 28 22:12:48 kali systemd[1148]: Reached target Shutdown.
Sep 28 22:12:48 kali systemd[1148]: Starting Exit the Session...
Sep 28 22:12:48 kali systemd[1]: Stopped User Manager for UID 0.
Sep 28 22:12:48 kali systemd[1]: user-runtime-dir@0.service: Unit not needed anymore. Stopping.
Sep 28 22:12:48 kali systemd[1]: Removed slice User Slice of UID 0.
Sep 28 22:12:48 kali systemd[1]: Stopping /run/user/0 mount wrapper...
Sep 28 22:12:48 kali systemd[1]: Stopped /run/user/0 mount wrapper.
Sep 28 22:12:50 kali systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Sep 28 22:12:50 kali systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Sep 28 22:12:50 kali systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
I have many more entries, but it would take up way too much text (plus, I posted it as a reply to my thread on the Kali support forum and am waiting for it to be approved).
Sep 28 22:12:41 kali systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
try to use journalctl to get the logs of that service, I think if you figure out why this service crashes you can figure it out the reboot problem. I also find it hilarious that later on the logs tell you that you are no longer in control of your session. But ignore that.
|
|
|
frameratcap=60 useful in sc2?
I do have 60+ without it in the first minutes (rather 90fps). I noitced that I never have 60 with it, it is always <55. Maybe the cap is too low so that cpu and gpu "can't run properly? Like a ferrari have to drive 10km/h when its real power begins in higher velocity?
edit: Replays shows the same. Some locations/areas of the map have 60+ fps while frameratecap=60 never shows above 55fps.
|
United Kingdom20343 Posts
On October 03 2018 19:11 Dingodile wrote:
frameratcap=60 useful in sc2?
I do have 60+ without it in the first minutes (rather 90fps). I noitced that I never have 60 with it, it is always <55. Maybe the cap is too low so that cpu and gpu "can't run properly? Like a ferrari have to drive 10km/h when its real power begins in higher velocity?
edit: Replays shows the same. Some locations/areas of the map have 60+ fps while frameratecap=60 never shows above 55fps.
Frametimes are extremely inconsistent in the sc2 engine because the CPU requirement varies dramatically over time. ~22 times per second the game engine has to simulate everything that's happening in a discrete step and this happens instead of frame generation which makes the next frame take far longer than expected.
When you see "100fps", many of those frames are taking much longer than 1/60'th of a second to be generated. The "100" average comes because it's a count of how many frames happened in the last second, not how long any individual frame took.
For an overly basic example, you could get 2 frames in half a second and then 98 frames in the second half of the second and it would still say 100fps but it would be unplayable.
FPS caps generally work on a frame by frame basis, looking at the times that it took to complete the last few frames. Setting a cap of 60 could then delay or not generate the frames that are faster than 1/60'th of a second but can't do anything to speed up the frames that are slower than 1/60'th ("60fps") because your CPU is too slow.
To get all frames faster than 1/60'th of a second in SC2 you need to maintain something like 150 "fps" which is not possible on any hardware.
For the best experience you should use a Gsync monitor with a wide refresh range and a low minimum refresh rate. Second best (lacking good adaptive sync) is just uncapped AFAIK, but with as high a refresh rate as possible.
|
Thanks.
I tested a bit with frameratecap and uncapped.
Sc2:
Uncapped means I do have 90+ fps at "black screen" (unscouted locations) but back at my base or army it goes to ~60fps or less if you fight.
frameratecap=60 means 60fps at unscouted locations and ~55fps at army/base and less if you fight.
Diablo3 goes differently at frameratecap=60. Doesn't matter if you don't fight or you have a hard fight in a solo or multiplayer modus. You are always at 55-60fps. framerates seem consistent in the d3 engine. uncapped do 55 - 110 fps in my case.
There seem to be a huge difference in GPU Clock and GPU Voltage. They are always at full speed (1750Mhz and 1050mV) if you play uncapped, regardless of fps display in both games.
Capped at 60fps is always 936Mhz and 675mV in both games.
|
United Kingdom20343 Posts
They change power states depending on the load, so a weaker GPU would stay at full clocks + boost but a higher end one could sit in the low power states (high efficiency) even with uncapped FPS because the CPU performance is acting as an FPS limiter
|
Yes I noticed that aswell. Uncapped is always around 60-80% load (GPU Usage) while capped is around 35-45%. Tempratures are 45°C vs 31°C.
edit: looks like CPU is the "fps limiter" in both games. So a fps cap for gpu makes sense for me. Makes no sense that a gpu have to do 100fps if a cpu can only do 60 or 40fps in cpu-related games.
|
do playstation 4 games released now generally lag on normal non pro ps4's (like bad super low frame rate lag)? the last game I bought was super laggy but I don't know if it's just the game or if their just assuming people have pros now.
|
United Kingdom20343 Posts
On October 13 2018 08:42 Karis Vas Ryaar wrote:
do playstation 4 games released now generally lag on normal non pro ps4's (like bad super low frame rate lag)? the last game I bought was super laggy but I don't know if it's just the game or if their just assuming people have pros now.
Many games on PS4/XB1 run with extremely low framerates and bad settings (such as forcing 60hz vsync even though the game framerates vary from sub-30 to 60+) even from before the ps4 pro era, it's been really bad this console gen.
Embarrassing that this is the way that the console companies go, running games substantially worse than older consoles did even with >10x more powerful hardware.
The Pro does run a lot of games at higher framerates than the regular ps4, particularly GPU-bound stuff that the developers haven't gone too wild with the resolution on.
This channel has a lot of great overviews of performance - https://www.youtube.com/user/DigitalFoundry/videos
|
cool. thanks for the information. didn't realize it was so widespread. I'll check that out
|
Is Ocenaudio a scam?
MORE SPECIFICALLY:- Does anybody have any reason to believe that 'Ocenaudio' - the free audio editing application - contains any software designed to compromise the security on ones system?
Many thanks to anyone who takes the time to read and/or respond.
|
There are reviews about it on several reasonably well-known sites and none mention any malware concerns.
|
Craton,
Thank you for taking the time to respond.
I did some cursory research before asking the question, and while what you say is true, it doesn't preclude the possibility.
I was hoping that somebody in Inf0s3c, or other similar background might have checked it out at some point, and could relay their findings. ( I admit that it wasn't the likeliest of outcomes)
Additionally, only one of those sites which have it reviewed explicitly claimed to check for scams (that site itself wasn't exactly what I'd call unimpeachable).
Thanks again.
|
What is the problem if a game is super laggy (shakes?) with 60++fps?
Oh lord, that was very laggy, it felt like 10fps in other games. Very unlikely the network.
|
United Kingdom20343 Posts
Gonna assume you're talking about SC2 i guess
There is a "tick" 22x per second where all of the stuff happening in the game is calculated in discrete steps. These have to be synchronized between players. If the other player's system is too slow or if there is an interruption in the network connection between either of you and the server, the game will (AFAIK) increase the amount of buffered ticks which increases the latency on performing actions. If that fails still, it will start to alter the flow of time so that there are weird pauses and skips with the game time no longer matching real time.
If it gets really bad or a player stops responding altogether you see that screen where it's waiting for them to time out. Sometimes it will be doing this for a while and then the screen will pop up showing that somebody has e.g. 45 seconds of wait time left instead of 60 seconds, that's an indication that they've been causing a ton of the previous lag but it hasn't been quite enough to pull up the disconnect window.
This is especially bad in 4v4 or customs where that one guy playing on a potato from Mars ruins the whole game regularly, there are 8 players and it's also more taxing because of more stuff on the map so you're highly likely to have a weak link somewhere. It still happens in 1v1 but not as frequently.
|
yes sc2 coop (2 players vs 2 AI) and only today. I asked the other players about it, they dont have/see anything. Funny also that this only happens at 60++fps and is much smoother at 40-60fps.
edit: problem is solved. I installed the newest net framework.
|
I think a lightning strike killed my graphics card, but want to know if there is any chance it can be rescued before binning it and buying a new one.
My PC is plugged into our TV via an HDMI cable and was not turned on at the time of the lightning strike. The TV was turned on and was temporarily messed up (not accepting any inputs from remote, refusing to turn off, picture went a weird purple hue) but recovered after turning it off and on at the wall a few times. No other electrical equipment that wasn't connected to the TV was affected so we suspect the surge came via the TV antenna cable, not the power points. When I next turned on my PC it booted normally, but no signal was coming from the graphics card. I tried a different monitor and both HDMI and DVI outputs with no success.
Plugging the TV/monitor into the motherboard outputs works fine and everything else seems to be working OK. The graphics card (an XFX rx470 4gb) lights up when the computer is on but cannot be found/recognised. I tried to reinstall the Radeon drivers but get a "no Radeon graphics card detected" error. The part that is confusing me is that my PC will happily boot / POST with the graphics card still installed. When my old graphics card died in my last PC it wouldn't boot at all. Unfortunately I don't have a spare graphics card to test with or another PC to test the broken graphics card in.
So with this information is it possible to tell whether:
1) Is my graphics card dead? (Can a PC boot / POST with a broken graphics card installed?)
2)Is there anything I should try before chucking it out and buying a new one? I know you can sometimes cook a graphics card to repair cracked solder connections, but could this possible help with lightning damage?
I know the simplest answer is probably the right one, but any advice would be appreciated.
|
United Kingdom20343 Posts
1: Sometimes
2: Nothing comes to mind, maybe try another PCI-E slot or try the graphics card in a different system. Oven is bad.
|
|
|
|
|
|
EPT
