Porteus-v2.0-x86_64 bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
User avatar
oranus
Contributor
Contributor
Posts: 69
Joined: 25 Aug 2011, 13:46
Location: Turkey

Re: Porteus-v2.0-x86_64 bug reports

Post#61 by oranus » 01 May 2013, 06:05

Hi Ahau,
In fact I don't find to xrandr option or parameter to multi screen on fit resolution. It doesn't work with manually and auto yet.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v2.0-x86_64 bug reports

Post#62 by Rava » 24 May 2013, 20:35

A new attempt to get Porteus-v2.0-x86_64 to run on one of my multi-core machines, the Dual Athlon with Asus Board.

Since it crashes when I start it the usual way (aka: start X by itself) I edited /etc/inittab back to the slackware default:

Code: Select all

id:3:initdefault:
(that was id:4:initdefault: )


Now, trying to start X gives me this:
Xorg.0.log:

Code: Select all

[    75.043] 
X.Org X Server 1.12.3
Release Date: 2012-07-09
[    75.044] X Protocol Version 11, Revision 0
[    75.044] Build Operating System: Slackware 14.0 Slackware Linux Project
[    75.045] Current Operating System: Linux porteus 3.7.8-porteus #1 SMP PREEMPT Fri Feb 15 11:30:14 UTC 2013 x86_64
[    75.045] Kernel command line: quiet initrd=initrd.xz xfce  BOOT_IMAGE=vmlinuz 
[    75.045] Build Date: 23 August 2012  02:03:27PM
[    75.046]  
[    75.046] Current version of pixman: 0.26.2
[    75.047] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    75.047] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    75.048] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 23 05:55:35 2013
[    75.050] (==) Using config file: "/etc/X11/xorg.conf"
[    75.050] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    75.051] (==) ServerLayout "X.org Configured"
[    75.051] (**) |-->Screen "Screen0" (0)
[    75.051] (**) |   |-->Monitor "Monitor0"
[    75.051] (**) |   |-->Device "Card0"
[    75.051] (**) |-->Input Device "Mouse0"
[    75.051] (**) |-->Input Device "Keyboard0"
[    75.051] (==) Automatically adding devices
[    75.051] (==) Automatically enabling devices
[    75.051] (WW) The directory "/usr/share/fonts/local" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".
[    75.051] 	Entry deleted from font path.
[    75.051] 	(Run 'mkfontdir' on "/usr/share/fonts/TTF").
[    75.051] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (WW) The directory "/usr/share/fonts/misc" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (WW) The directory "/usr/share/fonts/CID" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (WW) The directory "/usr/share/fonts/75dpi/" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (WW) The directory "/usr/share/fonts/100dpi/" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (WW) The directory "/usr/share/fonts/cyrillic" does not exist.
[    75.051] 	Entry deleted from font path.
[    75.051] (==) FontPath set to:
	
[    75.051] (==) ModulePath set to "/usr/lib64/xorg/modules"
[    75.051] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    75.051] (WW) Disabling Mouse0
[    75.051] (WW) Disabling Keyboard0
[    75.051] (II) Loader magic: 0x7c48e0
[    75.051] (II) Module ABI versions:
[    75.051] 	X.Org ANSI C Emulation: 0.4
[    75.051] 	X.Org Video Driver: 12.0
[    75.051] 	X.Org XInput driver : 16.0
[    75.051] 	X.Org Server Extension : 6.0
[    75.052] (--) PCI:*(0:4:0:0) 10de:0163:1043:820b rev 161, Mem @ 0xdf000000/16777216, 0xe0000000/268435456, 0xde000000/16777216, BIOS @ 0x????????/131072
[    75.053] (II) Open ACPI successful (/var/run/acpid.socket)
[    75.053] (II) LoadModule: "extmod"
[    75.054] (II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so
[    75.055] (II) Module extmod: vendor="X.Org Foundation"
[    75.055] 	compiled for 1.12.3, module version = 1.0.0
[    75.055] 	Module class: X.Org Server Extension
[    75.055] 	ABI class: X.Org Server Extension, version 6.0
[    75.055] (II) Loading extension MIT-SCREEN-SAVER
[    75.055] (II) Loading extension XFree86-VidModeExtension
[    75.055] (II) Loading extension XFree86-DGA
[    75.055] (II) Loading extension DPMS
[    75.055] (II) Loading extension XVideo
[    75.055] (II) Loading extension XVideo-MotionCompensation
[    75.055] (II) Loading extension X-Resource
[    75.055] (II) LoadModule: "dbe"
[    75.055] (II) Loading /usr/lib64/xorg/modules/extensions/libdbe.so
[    75.055] (II) Module dbe: vendor="X.Org Foundation"
[    75.055] 	compiled for 1.12.3, module version = 1.0.0
[    75.055] 	Module class: X.Org Server Extension
[    75.055] 	ABI class: X.Org Server Extension, version 6.0
[    75.055] (II) Loading extension DOUBLE-BUFFER
[    75.056] (II) LoadModule: "glx"
[    75.056] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[    75.080] (II) Module glx: vendor="NVIDIA Corporation"
[    75.080] 	compiled for 4.0.2, module version = 1.0.0
[    75.080] 	Module class: X.Org Server Extension
[    75.080] (II) NVIDIA GLX Module  310.32  Mon Jan 14 15:02:04 PST 2013
[    75.080] (II) Loading extension GLX
[    75.080] (II) LoadModule: "record"
[    75.081] (II) Loading /usr/lib64/xorg/modules/extensions/librecord.so
[    75.081] (II) Module record: vendor="X.Org Foundation"
[    75.081] 	compiled for 1.12.3, module version = 1.13.0
[    75.081] 	Module class: X.Org Server Extension
[    75.081] 	ABI class: X.Org Server Extension, version 6.0
[    75.081] (II) Loading extension RECORD
[    75.081] (II) LoadModule: "dri"
[    75.082] (II) Loading /usr/lib64/xorg/modules/extensions/libdri.so
[    75.082] (II) Module dri: vendor="X.Org Foundation"
[    75.082] 	compiled for 1.12.3, module version = 1.0.0
[    75.082] 	ABI class: X.Org Server Extension, version 6.0
[    75.082] (II) Loading extension XFree86-DRI
[    75.082] (II) LoadModule: "dri2"
[    75.083] (II) Loading /usr/lib64/xorg/modules/extensions/libdri2.so
[    75.083] (II) Module dri2: vendor="X.Org Foundation"
[    75.083] 	compiled for 1.12.3, module version = 1.2.0
[    75.083] 	ABI class: X.Org Server Extension, version 6.0
[    75.083] (II) Loading extension DRI2
[    75.083] (II) LoadModule: "nvidia"
[    75.083] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[    75.084] (II) Module nvidia: vendor="NVIDIA Corporation"
[    75.084] 	compiled for 4.0.2, module version = 1.0.0
[    75.084] 	Module class: X.Org Video Driver
[    75.144] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
[    75.144] (EE) NVIDIA:     system's kernel log for additional error messages.
[    75.144] (II) UnloadModule: "nvidia"
[    75.144] (II) Unloading nvidia
[    75.144] (EE) Failed to load module "nvidia" (module-specific error, 0)
[    75.144] (EE) No drivers available.
[    75.145] 
Fatal server error:
[    75.145] no screens found
[    75.146] 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    75.147] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    75.147] 
and here is the info from psinfo:

Code: Select all

----------------------
Output from psinfo
----------------------
script by jayflood
.

====== USER INFO =====
User is: root
.
===== MACHINE INFO =====
Platform: x86_64
Kernel: 3.7.8-porteus
Processor: Intel(R) Pentium(R) D  CPU 2.66GHz
Base Board Information
	Manufacturer: ASUSTeK Computer INC.
	Product Name: P5PL2-E
MemTotal:        3475672 kB
MemFree:         3095132 kB
Bootparam: quiet initrd=initrd.xz xfce  BOOT_IMAGE=vmlinuz 
.
===== LIVE DEBUG INFO =====
# Recognized devices:
/dev/sda1: LABEL=myUSB" UUID="[...]" TYPE="ext2" 

# Booting device:
/mnt/sda1

# Porteus data found in:
/mnt/sda1/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/sda1/porteus/base/000-kernel.xzm
/mnt/sda1/porteus/base/001-core.xzm
/mnt/sda1/porteus/base/002-xorg.xzm
/mnt/sda1/porteus/base/006-firefox-x86-64_en-GB_21.0_incl_Flash.tar.bz2.xzm
/mnt/sda1/porteus/base/0090-xfce.xzm
/mnt/sda1/porteus/base/0091-xfce-apps.xzm
/mnt/sda1/porteus/base/010-nVidia-310.32-porteus-v2.0-x86_64-1ftm.xzm
/mnt/sda1/porteus/base/050-viewnior-1.3-x86_64-1gv.xzm
.
===== SOUND INFO =====
Sound card:  0 [Intel          ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xdddf8000 irq 44
Sound driver: Advanced Linux Sound Architecture Driver Version k3.7.8-porteus.
.
===== PARTITION INFO =====
Mounted: 
devtmpfs       devtmpfs  1.7G     0  1.7G   0% /dev
/dev/sda1      ext2      3.8G  2.2G  1.5G  61% /mnt/sda1
.
===== OPTICAl DRIVE =====
sr0
.
===== USB INFO =====
Removables: DataTraveler
Removable status: sd4:0:0:0:[sda]Protect
.
lsusb: Bus 001 Device 002: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
.
===== SCREEN INFO =====

.
===== ACTIVATED MODULES =====
000-kernel.xzm
001-core.xzm
002-xorg.xzm
006-firefox-x86-64_en-GB_21.0_incl_Flash.tar.bz2.xzm
0090-xfce.xzm
0091-xfce-apps.xzm
010-nVidia-310.32-porteus-v2.0-x86_64-1ftm.xzm
050-viewnior-1.3-x86_64-1gv.xzm
.
===== NETWORK INFO =====
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:1a:92:31:92:08  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 12  bytes 832 (832.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12  bytes 832 (832.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
.
search example.net
.
===== PCI INFO =====
lspci: 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8178]
00:01.0 PCI bridge [0604]: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port [8086:2771] (rev 02)
	Kernel driver in use: pcieport
00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5LD2-VM Mainboard (Realtek ALC 882 codec) [1043:817f]
	Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 01)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 4 [8086:27d6] (rev 01)
	Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8179]
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8179]
	Kernel driver in use: ata_piix
00:1f.2 IDE interface [0101]: Intel Corporation N10/ICH7 Family SATA Controller [IDE mode] [8086:27c0] (rev 01)
	Subsystem: ASUSTeK Computer Inc. Device [1043:2601]
	Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller [8086:27da] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8179]
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5B [1043:81aa]
	Kernel driver in use: r8169
04:00.0 VGA compatible controller [0300]: nVidia Corporation NV44 [GeForce 6200 LE] [10de:0163] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:820b]
.
.
===== LOGS INFO =====
dmesg | tail 
.
[   44.924697] NVRM:  visit http://www.nvidia.com/object/unix.html for more
[   44.924697] NVRM:  information.  The 310.32 NVIDIA driver will ignore
[   44.924697] NVRM:  this GPU.  Continuing probe...
[   44.924739] NVRM: No NVIDIA graphics adapter found!
[   75.136111] NVRM: The NVIDIA GeForce 6200 LE GPU installed in this system is
[   75.136111] NVRM:  supported through the NVIDIA 304.xx Legacy drivers. Please
[   75.136111] NVRM:  visit http://www.nvidia.com/object/unix.html for more
[   75.136111] NVRM:  information.  The 310.32 NVIDIA driver will ignore
[   75.136111] NVRM:  this GPU.  Continuing probe...
[   75.136152] NVRM: No NVIDIA graphics adapter found!
.
.
cat /var/log/messages | tail
.
May 23 05:54:38 porteus modem-manager[1716]: <info>  Loaded plugin SimTech 
May 23 05:54:38 porteus modem-manager[1716]: <info>  Loaded plugin Wavecom 
May 23 05:54:38 porteus modem-manager[1716]: <info>  Loaded plugin X22X 
May 23 05:54:38 porteus modem-manager[1716]: <info>  Loaded plugin ZTE 
May 23 05:55:03 porteus acpid: client connected from 1809[0:1000]
May 23 05:55:03 porteus acpid: 1 client rule loaded
May 23 05:55:10 porteus acpid: client 1809[0:1000] has disconnected
May 23 05:55:35 porteus acpid: client connected from 1837[0:1000]
May 23 05:55:35 porteus acpid: 1 client rule loaded
May 23 05:55:42 porteus acpid: client 1837[0:1000] has disconnected
..

Dunno why modprobe complains, it seems that the nvidia.ko is just where it should be. Any idea why X is not starting? nVidia-310.32-porteus-v2.0-x86_64-1ftm.xzm is the correct module, yes?

I tried it "out of the box" and with manually started nvidia-xconfig, but both result in the same errors...
Cheers!
Yours Rava

User avatar
fanthom
Site Admin
Site Admin
Posts: 4586
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v2.0-x86_64 bug reports

Post#63 by fanthom » 24 May 2013, 21:16

hi Rava,
Any idea why X is not starting? nVidia-310.32-porteus-v2.0-x86_64-1ftm.xzm is the correct module, yes?
nope - it isn't. it's even shown in the log file:

Code: Select all

[   44.924739] NVRM: No NVIDIA graphics adapter found!
[   75.136111] NVRM: The NVIDIA GeForce 6200 LE GPU installed in this system is
[   75.136111] NVRM:  supported through the NVIDIA 304.xx Legacy drivers. Please
[   75.136111] NVRM:  visit http://www.nvidia.com/object/unix.html for more
[   75.136111] NVRM:  information.  The 310.32 NVIDIA driver will ignore
[   75.136111] NVRM:  this GPU.  Continuing probe...
[   75.136152] NVRM: No NVIDIA graphics adapter found!
please use 304.x driver.

btw: if you are not sure which driver supports which GPU then simply move them all to /porteus/optional and use 'vga_detect' cheatcode which usually is smart enough to pick up the right driver.
Please add [Solved] to your thread title if the solution was found.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v2.0-x86_64 bug reports

Post#64 by Rava » 25 May 2013, 13:40

nope - it isn't. it's even shown in the log file:
Arghhlll Image :oops:

btw: if you are not sure which driver supports which GPU then simply move them all to /porteus/optional and use 'vga_detect' cheatcode which usually is smart enough to pick up the right driver

I did not know about the ability of that cheatcode... :Yahoo!:

How does it work, when I have, say,

Code: Select all

nVidia-173.14.37-porteus-v2.0-i486-1ftm.xzm
nVidia-304.88-porteus-v2.0-x86_64-1ftm.xzm
nVidia-310.32-porteus-v2.0-x86_64-1ftm.xzm
nVidia-313.30-porteus-v2.0-x86_64-1ftm.xzm
in /porteus/optional. I presume 173.14.37 and 304.88 both would work but 304.88 would be preferred, would the cheatcode choose 304.88?

Where can I find that code to look how it handles things? :)
Cheers!
Yours Rava

User avatar
Hamza
Warlord
Warlord
Posts: 1847
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: Porteus-v2.0-x86_64 bug reports

Post#65 by Hamza » 25 May 2013, 14:00

Where can I find that code to look how it handles things?
linuxrc.

Please be careful about what you post on this topic. As you may see, it's a topic about bug reports, not about joking with images. Be a bit more serious here, please.
NjVFQzY2Rg==

Kriss
Samurai
Samurai
Posts: 133
Joined: 06 Jul 2011, 07:07
Location: Russia

Re: Porteus-v2.0-x86_64 bug reports

Post#66 by Kriss » 26 May 2013, 07:29

Hello!
Just wanted to let you know that console command "activate" still can't handle paths with spaces.
Suggestions/corrections/additions are always welcome.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4586
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v2.0-x86_64 bug reports

Post#67 by fanthom » 27 May 2013, 20:41

@Rava
linuxrc tries to match pciid of the GPU to the pciid-list included in initrd then activate correct driver.

@Hamza
c'mon - this site is for nerdy geeks so being serious is not desirable.

@Kriss,
i had to revert this function as activation of multiple modules was broken.
sorry about that.
Please add [Solved] to your thread title if the solution was found.

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Porteus-v2.0-x86_64 bug reports

Post#68 by cttan » 06 Jun 2013, 00:54

cttan wrote:Hi fanthom,

I am not able to get the crash from simulation even without removing the external drivers. Maybe it is a very intermittent problem.

I have found that when my laptop come back from sleep, the fan is running at full speed.
In Porteus 1.2, it is working fine.

Is there a setting to tweak it as per ArchLinux?
cat /sys/class/hwmon/hwmon0/device/fan1_input

Code: Select all

cat: /sys/class/hwmon/hwmon0/device/fan1_input: No such file or directory
When I run fancontrol, it cannot find the config file.

Code: Select all

fancontrol 
Loading configuration from /etc/fancontrol ...
Error: Can't read configuration file
I have found a workaround solution to stop the fan spinning at full speed after resuming from sleep.
Firstly you need to take down the settings before sleep:-
1. cat /sys/class/thermal/cooling_deviceX/cur_state
where X is 0 to 9
For my case, 7 is for screen brightness so I have leave it out when checking current state.
2. sensor

Code: Select all

# cat /sys/class/thermal/cooling_device0/cur_state 
0
# cat /sys/class/thermal/cooling_device1/cur_state 
0
# cat /sys/class/thermal/cooling_device2/cur_state 
0
# cat /sys/class/thermal/cooling_device3/cur_state 
1
# cat /sys/class/thermal/cooling_device4/cur_state 
1
# cat /sys/class/thermal/cooling_device5/cur_state 
0
# cat /sys/class/thermal/cooling_device6/cur_state
After resuming from sleep key in:-

Code: Select all

echo 0 > /sys/class/thermal/cooling_device0/cur_state 
echo 0 > /sys/class/thermal/cooling_device1/cur_state 
echo 0 > /sys/class/thermal/cooling_device2/cur_state 
echo 1 > /sys/class/thermal/cooling_device3/cur_state 
echo 1 > /sys/class/thermal/cooling_device4/cur_state 
echo 0 > /sys/class/thermal/cooling_device5/cur_state 
echo 0 > /sys/class/thermal/cooling_device6/cur_state 
watch -n5 sensors
Every 5.0s: sensors                                                           Thu Jun  6 08:37:54 2013

acpitz-virtual-0
Adapter: Virtual device
temp1:        +58.0 C  (crit = +256.0 C)
temp2:        +52.0 C  (crit = +107.0 C)
temp3:        +49.0 C  (crit = +105.0 C)
temp4:        +30.5 C  (crit = +107.0 C)
temp5:        +50.0 C  (crit = +110.0 C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +50.0 C  (high = +100.0 C, crit = +100.0 C)
Core 1:       +51.0 C  (high = +100.0 C, crit = +100.0 C)
The last command is to monitor the temperature status. For me, the settings works well and the temperature is control with the maximum reaching 80+C.

Try it at you own risk. Pls monitor the temperature closely.
Hope it is working well for you. 8)

Edited:-
The problem is not solved in 2.1 RC1 with kernel 3.9.4.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v2.0-x86_64 bug reports

Post#69 by Rava » 15 Jun 2013, 10:14

cttan wrote: For my case, 7 is for screen brightness so I have leave it out when checking current state.
2. sensor
How do you figure out which sub-number is doing what exactly in a certain system?
Cheers!
Yours Rava

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Porteus-v2.0-x86_64 bug reports

Post#70 by cttan » 16 Jun 2013, 13:06

Hi Rava,

I do not know.

After echo something to it then I found out. :wink:

For your reference, I came across something like this after some googling after having that problem for a few months.
https://bugzilla.redhat.com/show_bug.cgi?id=895276

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v2.0-x86_64 bug reports

Post#71 by Rava » 18 Jun 2013, 19:24

@cttan:
The current notebook I run has no fan so I cannot check, but I wonder about this response:

Comment 11 jblistat 2013-02-26 18:38:33 EST on https://bugzilla.redhat.com/show_bug.cgi?id=895276

It mentioned to put the fix either in /etc/pm/sleep.d/ or /usr/lib/systemd/system-sleep/, and while Porteus has the former folder, me thinks the fix should be put in there...

But as it is said in this thread, and by cttan, it should be checked and monitored first to be sure which setting should be set to 0 and which to 1...

But even more interesting is the fix named in Zhang Rui 2013-05-15 20:56:06 EDT :

Code: Select all

    My original idea in that commit is that:
     - when the current temperature is above the trip point,
       keep the fan on, even if the temperature is dropping.
     - when the current temperature is below the trip point,
       turn on the fan when the temperature is raising,
       turn off the fan when the temperature is dropping.
    
    But this is what the code actually does:
     - when the current temperature is above the trip point,
       the fan keeps on.
     - when the current temperature is below the trip point,
       the fan is always on because thermal_get_trend()
       in driver/acpi/thermal.c returns THERMAL_TREND_RAISING.
    Thus the fan keeps running even if the system is idle.
    
    Fix this in drivers/acpi/thermal.c.
    
    [rjw: Changelog]
    References: https://bugzilla.kernel.org/show_bug.cgi?id=56591
    References: https://bugzilla.kernel.org/show_bug.cgi?id=56601
    References: https://bugzilla.kernel.org/show_bug.cgi?id=50041#c45
    Signed-off-by: Zhang Rui <rui.zhang@intel.com>
    Tested-by: Matthias <morpheusxyz123@yahoo.de>
    Tested-by: Ville Syrjälä <syrjala@sci.fi>
    Cc: 3.7+ <stable@vger.kernel.org>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
But at least one user claims that this fix did not resolve the issue.
Cheers!
Yours Rava

Post Reply