Fans not working after dual booting ubuntu18.04 on acer preadator helios 300


#1

Hello guys it would be really great if you could help me with my ubuntu 18.04 installation on my preadator helios 300,

the problem is that after dual booting my ubuntu is not able to detect my fans. I typed in the following commands

"sudo pwmconfig; only to find the error statement no pwm modules found’.

my fans are not being detected.

on typing" sensors" in the terminal , i am not getting a reading of my fan speed

and on typing" fancontrol’ again the fans are not shown to be detected.

if you can help me . it would be really great as i have been running around this for almost a week and i really really need my environment set up before i can begin my programming.

Thank you


#2

Hi jack,

I’m not familiar with Acer, and this model is an expensive gaming laptop, unless there is member who has first hand experience, to guide you. There is a good chance of it becoming an expensive paper weight.

A cursory search: Acer Predator Helios 300, fans not working
https://community.acer.com/en/search?adv=&search=Acer+Predator+Helios+300%2C+fans+not+working&title=&author=&cat=all&tags=&discussion_d=1&discussion_question=1&discussion_poll=1&comment_c=1&comment_answer=1&within=1+day&date=

Dual boot:
https://community.acer.com/en/search?adv=&search=dual+boot+&title=&author=&cat=all&tags=&discussion_d=1&discussion_question=1&discussion_poll=1&comment_c=1&comment_answer=1&within=1+day&date=

Install method
It will be very useful to explain how you installed Ubuntu, using either the “alongside” or “something else” method. Did you disable Secure Boot or not, and did you format the partiton(s) with GPT/Ext 4.?

Please run this command: inxi -Fxz and when you reply look for this </> on the bar of the reply box, it formats and keeps the integrity of the inxi -Fxz print out.

:sunglasses:


#3

while booting , i chose the something else option
disabled secure boot
and i formated the partition //“with GPT/Ext 4.?” i think so
and alloted the swap root and home.

had to set nomodeset to get in to ubuntu
and had to edit the quick splash to get the trackpad working
ill run the command and get back.


#4

okPreformatted text


#5

Tanks mack,
Please run this command: inxi -Fxz --you mean on the terminal right


#6

Yes, and place print out in reply box click on </> symbol and click left mouse button and cover entire text.


#7

Jack have you tried doing a repair to see if that works? Sometimes things don’t quite get sorted in the install and you can sort it out by doing this. Just a thought for you.


#8
System:    Host: joseph-Predator-PH315-51 Kernel: 4.18.0-15-generic x86_64
           bits: 64 gcc: 7.3.0
           Desktop: Gnome 3.28.3 (Gtk 3.22.30-1ubuntu1)
           Distro: Ubuntu 18.04.2 LTS
Machine:   Device: laptop System: Acer product: Predator PH315-51 v: V1.19 serial: N/A
           Mobo: CFL model: Sienta_CFS v: V1.19 serial: N/A
           UEFI: Insyde v: V1.19 date: 07/13/2018
Battery    BAT1: charge: 45.8 Wh 100.0% condition: 45.8/48.9 Wh (94%)
           model: LG PABAS0241231 status: Full
CPU:       6 core Intel Core i7-8750H (-MT-MCP-) 
           arch: Skylake rev.10 cache: 9216 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 26496
           clock speeds: max: 4100 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz
           4: 800 MHz 5: 800 MHz 6: 800 MHz 7: 800 MHz 8: 800 MHz 9: 800 MHz
           10: 800 MHz 11: 800 MHz 12: 800 MHz
Graphics:  Card-1: Intel Device 3e9b bus-ID: 00:02.0
           Card-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] bus-ID: 01:00.0
           Display Server: wayland (X.Org 1.19.6 )
           drivers: (unloaded: modesetting) FAILED: fbdev,vesa,nouveau
           Resolution: 1920x1080@59.96hz
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2)
           version: 4.5 Mesa 18.2.2 Direct Render: Yes
Audio:     Card Intel Device a348 driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.18.0-15-generic
Network:   Card-1: Intel Device a370 driver: iwlwifi bus-ID: 00:14.3
           IF: wlp0s20f3 state: down mac: <filter>
           Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 3000 bus-ID: 06:00.1
           IF: enp6s0f1 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1128.2GB (2.0% used)
           ID-1: /dev/sda model: HFS128G39TND size: 128.0GB temp: 41C
           ID-2: /dev/sdb model: HGST_HTS721010A9 size: 1000.2GB temp: 37C
Partition: ID-1: / size: 55G used: 7.6G (15%) fs: ext4 dev: /dev/sdb2
           ID-2: /home size: 222G used: 3.1G (2%) fs: ext4 dev: /dev/sdb4
           ID-3: swap-1 size: 12.00GB used: 0.00GB (0%)
           fs: swap dev: /dev/sdb3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 61.0C m``obo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 370 Uptime: 4 min Memory: 2018.3/7817.2MB
           Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56 
    indent preformatted text by 4 spaces`Preformatted text`

#9

well i tried everythin on ubuntu forums and stack exchange that i could find , there are a lot of people reporting the same problem but i cannot find a clear cut solution .


#10

can you tell me why i have the failed on the line of drivers


#11

see the fan speeds
thats the prob


#12

Just run sensors, pwmconfig and fancontrol. This is Ubuntu on a multiple boot Dell 5430 I use to distro hop.

The read outs were inconclusive, I do not have a 3 wire fan, does your laptop have such a device…?


#13

so are your fans working
i have the same error message with fancontrol

joseph@joseph-Predator-PH315-51:~$ sudo pwmconfig

pwmconfig revision 6243 (2014-03-20)

This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed
indent preformatted text by 4 spaces


#14
oseph@joseph-Predator-PH315-51:~$ sensors
iwlwifi-virtual-0
Adapter: Virtual device
temp1:            N/A  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +63.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +51.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +52.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +54.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +50.0°C  (high = +100.0°C, crit = +100.0°C)
Core 4:        +64.0°C  (high = +100.0°C, crit = +100.0°C)
Core 5:        +50.0°C  (high = +100.0°C, crit = +100.0°C)

pch_cannonlake-virtual-0
Adapter: Virtual device
temp1:        +62.0°C

#15

nothing about the fan speed


#16
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +18.8°C)
temp2:        +27.8°C  (crit = +119.0°C)
temp3:        +29.8°C  (crit = +119.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +31.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:        +29.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:        +30.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:        +29.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:        +29.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:        +30.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:        +28.0°C  (high = +82.0°C, crit = +100.0°C)



# pwmconfig revision $Revision$ ($Date$)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

/usr/bin/pwmconfig: There are no pwm-capable sensor modules installed



fancontrol
Loading configuration from /etc/fancontrol ...
Error: Can't read configuration file

This is the print out from my 8th Gen Master Cooler Aorus Gaming Rig, it has 3x120mm fans at the front and 1x120mm on bottom panel. It has been up and running since 10am this morning, cool as a cucumber.

Edit 20/02/19 1730hrs addition info below

Both my computers the ATX sized rig and the old Dell 5430 laptop do not have a cooling problem nor do either run hot. There for I do see an issue, though the commands you used do contradict this.

Old adage, if it ain’t broke, don’t fix it. :sunglasses:


#17

Your Graphic card is being choked, as it going through Intel’s GPU and Nvidia.

This my print out for my gaming rig graphic card. I use Manjaro (and did not need to do the nomodeset trick) it allowed me to install, then enable the the Nvidia driver, currently the 415 nvidia driver whereas Ubuntu comes with their default 390 driver, unless you are knowledgeable to unstall the latest from Nvidia site.

Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1060 6GB] vendor: Gigabyte 
  driver: nvidia v: 415.27 bus ID: 01:00.0 
  Display: x11 server: X.org 1.20.3 driver: nvidia 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 415.27 
  direct render: Yes 

:sunglasses:


#18

@jack Any updates?

.

.
.


.
.


#19

@jack

I found this answer, selected as the best answer to a forum post.

A three wire fan reports its speed. Add a fourth wire, and the fan’s speed can be varied by the motherboard.

The simplest PC fan requires two wires. The red wire provides power (+12 VDC), the black wire is ground (0 V). Applying power to will start the fan running full speed. If a modern fan’s blades are stopped, the fan’s drive circuitry interrupts power to the fan motor, then retries starting the fan periodically. This prevents the fan from overheating, resulting in a burned out fan (and a potential fire - and keeps the manufacturer from achieving CE/UL/CSA/TUV certification). You can try this by stopping a running fan, then letting it go. If, after you free the fan blades, the fan doesn’t start for a moment, you have this modern kind of fan.

A three wire fan adds a tachometer output to the two wire fan. The yellow wire pulses an output voltage twice per fan revolution. With the fan spinning at 6000 RPM, you would measure a 200 Hz pulse rate (6000 rev/min / 60 s * 2 pulses/rev = 200 pulses/sec). Some PC motherboards monitor this input. In the case of fan failure, the motherboard can send an alert (beeper, message to the OS, etc.), or take action directly, like slow the CPU or even shut down the system.

Add a fourth wire to control the fan’s speed. The fourth wire operates similarly to the third wire, but in reverse: this wire controls the fan speed. Intel created a wiring standard for this fan, including the connector type, pin positions, and wire color code. I haven’t cited the Intel standard here, but it is widely reported to be: Black - 0 V, Yellow 12 V, Green - Tachometer output, Blue - PWM speed control input.

The fan’s speed is controlled by pulsing the voltage on the fourth wire. This wire does not power the fan. The frequency of the pulsed signal changes the speed of the fan. This common method of controlling an analog device (fan, light, heater) with a digital control is called pulse width modulation, or PWM.

shareimprove this answer edited Jan 8 at 3:50 answered Nov 13 '18 at 22:10 ndemarco

:sunglasses:


#20

Indeed a satisfyingly thorough explanation.