I was told to reseat my video card and after doing so I had no
connectivity. Could someone help me get it going?
On Nov 5, 2017 3:42 PM, "Matthew Crews" <
mailinglists@mattcrews.com> wrote:
It's possible to activate the onboard video and keep the graphics card
installed. You will need to play around with BIOS settings most likely.
However it's also possible that just having the card in your system is
causing system hangs, even if it's not being used. It's worth a try.
Sent from ProtonMail <
https://protonmail.com>, Swiss-based encrypted email.
-------- Original Message --------
On Nov 4, 2017, 20:15, Michael <
bmike1@gmail.com> wrote:
Before I take everything apart I better ask how to get the onboard video to
work? I tried taking that card out and it really doesn't want to to come
out easily! Could I just activate the onboard video and leave the card in?
On Sat, Nov 4, 2017 at 11:04 PM, Michael <
bmike1@gmail.com> wrote:
> I opened the case and the internal fans are whirring.
>
> On Sat, Nov 4, 2017 at 11:03 PM, Brien Dieterle <briend@gmail.com> wrote:
>
>> You have onboard video and a separate graphics card? I would remove the
>> graphics card and use the onboard for a while. If it doesn't crash you
>> know it is related to that card.
>> Have you already ruled out overheating by opening the case and blasting
>> it with a fan?
>>
>> On Sat, Nov 4, 2017 at 7:45 PM, Michael <bmike1@gmail.com> wrote:
>>
>>> Well darn... that wasn't the problem. It just crashed the entire system
>>> after about 15 minutes. SOOOOOO.... back to the original request for
>>> information:
>>>
>>> probably you graphics card driver. Which one do you use on which
>>> platform and operating system?
>>>
>>> the driver manager on my Linux Mint18 system says the driver is:
>>>
>>> amd64-microcode
>>> Version 2.20160316.1
>>> Processor microcode firmware for AMD CPUs
>>>
>>> Which I guess is the driver if I was using the on-board video but I just
>>> looked at the card and written on the back is 'RoHS'. I wasn't to sure if
>>> that was the video card's manufacturer so I looked it up.... and it is. Now
>>> I'm lost..... I don't know how to find out the specific card or how to
>>> install it's driver:(
>>>
>>>
>>> On Sat, Nov 4, 2017 at 6:03 PM, Michael <bmike1@gmail.com> wrote:
>>>
>>>> As it is looking now it was my card. This is a note to someone who I
>>>> hope helped: Thanks for inspiring me to look up the video card driver.
>>>> There was one listed but the button next to 'do not use' was blacked in.
>>>>
>>>>
>>>> On Sat, Nov 4, 2017 at 4:32 PM, Michael <bmike1@gmail.com> wrote:
>>>>
>>>>> I am thinking it is my video card. Is there something I need to do to
>>>>> access the video card or to make usable??
>>>>>
>>>>> On Sat, Nov 4, 2017 at 4:19 PM, Michael <bmike1@gmail.com> wrote:
>>>>>
>>>>>> nope.... that did not seem to do anything:
>>>>>> bmike1@MikesBeast ~ $ modprobe k10temp
>>>>>> bmike1@MikesBeast ~ $ sensors
>>>>>> radeon-pci-0100
>>>>>> Adapter: PCI adapter
>>>>>> temp1: +66.0°C
>>>>>>
>>>>>> it8718-isa-0228
>>>>>> Adapter: ISA adapter
>>>>>> in0: +1.46 V (min = +0.00 V, max = +4.08 V)
>>>>>> in1: +1.94 V (min = +0.00 V, max = +4.08 V)
>>>>>> in2: +3.25 V (min = +0.00 V, max = +4.08 V)
>>>>>> +5V: +2.99 V (min = +0.00 V, max = +4.08 V)
>>>>>> in4: +3.10 V (min = +0.00 V, max = +4.08 V)
>>>>>> in5: +3.25 V (min = +0.00 V, max = +4.08 V)
>>>>>> in6: +4.08 V (min = +0.00 V, max = +4.08 V)
>>>>>> in7: +2.35 V (min = +0.00 V, max = +4.08 V)
>>>>>> Vbat: +3.15 V
>>>>>> fan1: 3139 RPM (min = 0 RPM)
>>>>>> fan2: 0 RPM (min = 0 RPM)
>>>>>> fan3: 0 RPM (min = 0 RPM)
>>>>>> fan5: 0 RPM (min = 0 RPM)
>>>>>> temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor =
>>>>>> thermistor
>>>>>> temp2: +51.0°C (low = +127.0°C, high = +127.0°C) sensor =
>>>>>> thermal diode
>>>>>> temp3: +52.0°C (low = +127.0°C, high = +127.0°C) sensor =
>>>>>> thermistor
>>>>>> cpu0_vid: +1.050 V
>>>>>> intrusion0: ALARM
>>>>>>
>>>>>> k10temp-pci-00c3
>>>>>> Adapter: PCI adapter
>>>>>> temp1: +48.8°C (high = +70.0°C)
>>>>>> (crit = +72.0°C, hyst = +70.0°C)
>>>>>>
>>>>>> bmike1@MikesBeast ~ $
>>>>>>
>>>>>>
>>>>>> Cool.... I do have a video card after all!
>>>>>>
>>>>>> On Thu, Nov 2, 2017 at 5:19 PM, Jerry Snitselaar <dev@snitselaar.org>
>>>>>> wrote:
>>>>>>
>>>>>>> On Wed Nov 01 17, Michael wrote:
>>>>>>>
>>>>>>>> so what command do I execute to utilize the probe?
>>>>>>>>
>>>>>>>>
>>>>>>> modprobe k10temp
>>>>>>>
>>>>>>> and then check the output of the sensors command
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Oct 31, 2017 at 8:58 PM, Michael <bmike1@gmail.com> wrote:
>>>>>>>>
>>>>>>>> it is there:
>>>>>>>>> $ modinfo k10temp
>>>>>>>>> filename: /lib/modules/4.4.0-53-generic
>>>>>>>>> /kernel/drivers/hwmon/
>>>>>>>>> k10temp.ko
>>>>>>>>> license: GPL
>>>>>>>>> author: Clemens Ladisch <clemens@ladisch.de>
>>>>>>>>> description: AMD Family 10h+ CPU core temperature monitor
>>>>>>>>> srcversion: 4BBE5D56D6917F9D3D415AA
>>>>>>>>> alias: pci:v00001022d00001583sv*sd*bc*sc*i*
>>>>>>>>> alias: pci:v00001022d00001533sv*sd*bc*sc*i*
>>>>>>>>> alias: pci:v00001022d00001573sv*sd*bc*sc*i*
>>>>>>>>> alias: pci:v00001022d0000141Dsv*sd*bc*sc*i*
>>>>>>>>> alias: pci:v00001022d00001403sv*sd*bc*sc*i*
>>>>>>>>> alias: pci:v00001022d00001603sv*sd*bc*sc*i*
>>>>>>>>> alias: pci:v00001022d00001703sv*sd*bc*sc*i*
>>>>>>>>> alias: pci:v00001022d00001303sv*sd*bc*sc*i*
>>>>>>>>> alias: pci:v00001022d00001203sv*sd*bc*sc*i*
>>>>>>>>> depends:
>>>>>>>>> intree: Y
>>>>>>>>> vermagic: 4.4.0-53-generic SMP mod_unload modversions
>>>>>>>>> parm: force:force loading on processors with erratum 319
>>>>>>>>> (bool)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Oct 31, 2017 at 4:44 PM, Jerry Snitselaar <
>>>>>>>>> dev@snitselaar.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> On Tue Oct 31 17, Michael wrote:
>>>>>>>>>>
>>>>>>>>>> Sorry to say but yes it is.
>>>>>>>>>>>
>>>>>>>>>>> $ lscpu
>>>>>>>>>>> Architecture: x86_64
>>>>>>>>>>> CPU op-mode(s): 32-bit, 64-bit
>>>>>>>>>>> Byte Order: Little Endian
>>>>>>>>>>> CPU(s): 4
>>>>>>>>>>> On-line CPU(s) list: 0-3
>>>>>>>>>>> Thread(s) per core: 1
>>>>>>>>>>> Core(s) per socket: 4
>>>>>>>>>>> Socket(s): 1
>>>>>>>>>>> NUMA node(s): 1
>>>>>>>>>>> Vendor ID: AuthenticAMD
>>>>>>>>>>> CPU family: 16
>>>>>>>>>>> Model: 5
>>>>>>>>>>> Model name: AMD Athlon(tm) II X4 620 Processor
>>>>>>>>>>> Stepping: 2
>>>>>>>>>>> CPU MHz: 1400.000
>>>>>>>>>>> CPU max MHz: 2600.0000
>>>>>>>>>>> CPU min MHz: 800.0000
>>>>>>>>>>> BogoMIPS: 5223.39
>>>>>>>>>>> Virtualization: AMD-V
>>>>>>>>>>> L1d cache: 64K
>>>>>>>>>>> L1i cache: 64K
>>>>>>>>>>> L2 cache: 512K
>>>>>>>>>>> NUMA node0 CPU(s): 0-3
>>>>>>>>>>> Flags: fpu vme de pse tsc msr pae mce cx8 apic
>>>>>>>>>>> sep mtrr
>>>>>>>>>>> pge
>>>>>>>>>>> mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
>>>>>>>>>>> fxsr_opt
>>>>>>>>>>> pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl
>>>>>>>>>>> nonstop_tsc
>>>>>>>>>>> extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm
>>>>>>>>>>> extapic
>>>>>>>>>>> cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit
>>>>>>>>>>> wdt
>>>>>>>>>>> hw_pstate vmmcall npt lbrv svm_lock nrip_save
>>>>>>>>>>>
>>>>>>>>>>> After looking further into this I found something <below>. Do
>>>>>>>>>>> you think I
>>>>>>>>>>> should compile it?
>>>>>>>>>>> Date Fri, 20 Nov 2009 09:15:23 +0100
>>>>>>>>>>> From Clemens Ladisch <>
>>>>>>>>>>> Subject [PATCH] k10temp: temperature sensor for AMD Family
>>>>>>>>>>> 10h/11h CPUs
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The k10temp driver has been in the kernel since 2.6.33. look at
>>>>>>>>>> the
>>>>>>>>>> config for
>>>>>>>>>> your kernel to see if CONFIG_SENSORS_K10TEMP is there. I imagine
>>>>>>>>>> your
>>>>>>>>>> kernel
>>>>>>>>>> already has the moduile built, unless you have been building your
>>>>>>>>>> own.
>>>>>>>>>>
>>>>>>>>>> try 'modinfo k10temp' and see if it is there already.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------
>>>>>>>>>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>>>>>>>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>>>>>>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> :-)~MIKE~(-:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> :-)~MIKE~(-:
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> :-)~MIKE~(-:
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> :-)~MIKE~(-:
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> :-)~MIKE~(-:
>>>>
>>>
>>>
>>>
>>> --
>>> :-)~MIKE~(-:
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>
>>
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>
>
>
> --
> :-)~MIKE~(-:
>
--
:-)~MIKE~(-:
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)