search

GalliumOS / galliumos-distro

Docs, issues, and artwork sources for GalliumOS
https://galliumos.org/
GNU General Public License v2.0
348 stars 11 forks source link

Urgent: Fan doesn't work on Lars #395

Closed LufyCZ closed 6 years ago

LufyCZ commented 6 years ago

Here I am again.

To keep it as short as possible: The fan doesn't work. It doesn't show up in pwmconfig, and it doesn't spin up when the CPU's hot (it starts throttling pretty hard). I hope that it's not a hw failure. Doesn't work on Arch either.

Anybody with Lars, could you please check ?

Thanks

dvdmuckle commented 6 years ago

I have a LARS, will check this issue soon.

LufyCZ commented 6 years ago

Thanks, kinda hoping it won't work 😐

LufyCZ commented 6 years ago

Hi, have you already checked ?

dvdmuckle commented 6 years ago

Yep, fans work on my device. I think your issue might be a hardware issue. You might want to try testing with some other distros, but I'd start figuring out how to get the device repaired by Acer.

I'll close this issue for now, will reopen if you can confirm it's not a hardware issue, or if anyone else runs into the same issue.

uteck commented 4 years ago

Hate to necrothread, but I also have this issue on my Lars system. Fans work when I boot into ChromeOS, but nothing in 3.1. Has not been much of an issue except for overheating when rendering video with MakeMKV, and when doing video chat while power is plugged in. I had some issues last year and had to reinstall, fans did not work then and still don't. So not going to wipe and reinstall if asked.

ghost commented 4 years ago

MakeMKV doesn't really render, does it? Pretty sure it just remuxes.

uteck commented 4 years ago

Does it really matter that I used the wrong word to describe what MakeMKV does? It makes the CPU really hot and the system shuts down because the fans never start.

ghost commented 4 years ago

It does matter a lot because rendering is a computationally intense process and remuxing is childs play for a cheap smartphone as long as there isn't too big of an I/O bottleneck.

ghost commented 4 years ago

Basically what I'm saying is that MakeMKV shouldn't be making your system that hot, but it seems likely that you have some hardware issue. I don't have a LARS (I've considered getting one but can't really unless someone else buys it for me) and I haven't spoken to the person on the team who does have one, but it is otherwise a fairly popular model so I feel like we would have heard if it was a widespread issue. If you can find a friend or two who has the same issue, then we might be talking.

uteck commented 4 years ago

For most of my use, heat is not an issue. Saying it is a hardware issue is just lazy as the fans work when I boot into ChromeOS.

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

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

The original poster also had the same issue. I doubt many people take the time to create an account here to post a bug report. I almost did not considering the support I read was just passing it off as a hardware problem.

reynhout commented 4 years ago

@uteck We were unable to repro the original reporter's issue on LARS at the time, and I am not able to repro on another Skylake model presently.

It sounds like you're dual-booting, which means you're running RW_LEGACY firmware.

The first thing I'd try is updating your RWL firmware to the latest version, using the script from MrChromebox.

The next thing I'd try is switching to full ROM/UEFI firmware, but that would remove dual-boot capability (and would require a reinstall, which it sounds like you're not able to do).

ghost commented 4 years ago

The original poster also had the same issue. I doubt many people take the time to create an account here to post a bug report. I almost did not considering the support I read was just passing it off as a hardware problem.

The original poster likely already had a GitHub account. It's not like we're asking you to create an account on our private Bugzilla or Flyspray instance. In cases like this where we can't reproduce things we have no choice but to assume it's a hardware issue, unless you're comfortable and can cover the cost of shipping your computer to the team (which currently may not even be arrange-able!)

reynhout's advice is always good, so please try the things he mentioned first.

uteck commented 4 years ago

@raynhout I ran the firmware update script from Mr. Chromebox, but the bios version is still 2018, so no change there. I have to remove the write protect screw to enable the full ROM, which evolves taking things apart. If the fans require full ROM to be enabled, at least that is an answer and would explain the original posters issue also.

ghost commented 4 years ago

Not necessarily, the original poster didn't specify the firmware they were using and their post was made over two years ago, things could have changed significantly. We always recommend using full ROM custom firmware if you don't want to boot Chrome OS.