Hi! Have anyone any idea why w83793G driver is not in the upstream vendor kernel? do i have to compile my own kernel for this to work?
Thank you, Adrian
Adrian Sevcenco wrote:
Hi! Have anyone any idea why w83793G driver is not in the upstream vendor kernel? do i have to compile my own kernel for this to work?
Thank you, Adrian
Hi Adrian,
I guess the w83793 driver had not made the 2.6.18.4 kernel that RHEL5 is based off.
Anyway, luckily you don't need to build a whole kernel for one driver module - you can build the driver out of tree against the el5 kernel.
Even better, I've backported the module for you from the latest upstream kernel (2.6.30.5) as a kABI tracking kmod package and put it in the elrepo-testing repository here (kmod-w83793):
http://elrepo.org http://elrepo.org/linux/testing/el5/
As you have the hardware, I'd appreciate if you would test the driver and report back how it works, either here or on the elrepo mailing lists or bug tracker.
Thanks
Ned Slider wrote:
Adrian Sevcenco wrote:
Hi! Have anyone any idea why w83793G driver is not in the upstream vendor kernel? do i have to compile my own kernel for this to work?
Thank you, Adrian
Hi Adrian,
Hi,
I guess the w83793 driver had not made the 2.6.18.4 kernel that RHEL5 is based off.
Anyway, luckily you don't need to build a whole kernel for one driver module - you can build the driver out of tree against the el5 kernel.
Even better, I've backported the module for you from the latest upstream kernel (2.6.30.5) as a kABI tracking kmod package and put it in the elrepo-testing repository here (kmod-w83793):
Thanks a lot!!!!
http://elrepo.org http://elrepo.org/linux/testing/el5/
As you have the hardware, I'd appreciate if you would test the driver and report back how it works, either here or on the elrepo mailing lists or bug tracker.
Sure! I will let you know asap :)
Thanks! Adrian
Ned Slider wrote:
Even better, I've backported the module for you from the latest upstream kernel (2.6.30.5) as a kABI tracking kmod package and put it in the elrepo-testing repository here (kmod-w83793):
http://elrepo.org http://elrepo.org/linux/testing/el5/
As you have the hardware, I'd appreciate if you would test the driver and report back how it works, either here or on the elrepo mailing lists or bug tracker.
It seems that everything is ok :) Thanks a lot! Adrian
[root@alien /]# insmod /lib/modules/2.6.18-128.7.1.el5/weak-updates/w83793/w83793.ko [root@alien /]# sensors w83793-i2c-0-2f Adapter: SMBus I801 adapter at 1100 CPU Core 1: +1.08 V (min = +0.92 V, max = +1.49 V) CPU Core 2: +1.07 V (min = +0.92 V, max = +1.49 V) VTT: +1.09 V (min = +0.99 V, max = +1.33 V) -12V: -11.52 V (min = -12.53 V, max = -9.79 V) P1V5: +1.57 V (min = +1.34 V, max = +1.65 V) +3.3V: +3.31 V (min = +2.96 V, max = +3.63 V) +12V: +11.81 V (min = +10.75 V, max = +13.25 V) +5V: +5.14 V (min = +4.64 V, max = +5.65 V) 5VSB: +5.07 V (min = +4.64 V, max = +5.65 V) VBAT: +3.18 V (min = +2.99 V, max = +3.66 V) fan1: 6221 RPM (min = 712 RPM) fan2: 6279 RPM (min = 712 RPM) fan3: 6308 RPM (min = 712 RPM) fan4: 0 RPM (min = 712 RPM) ALARM CPU1 fan: 0 RPM (min = 712 RPM) ALARM CPU2 fan: 0 RPM (min = 712 RPM) ALARM CPU1 Temp: +28.0�C (high = +70.0�C, hyst = +65.0�C) sensor = Intel PECI CPU2 Temp: +33.0�C (high = +70.0�C, hyst = +65.0�C) sensor = Intel PECI System Temp: +26.0�C (high = +50.0�C, hyst = +45.0�C) sensor = thermistor beep_enable:disabled
Adrian Sevcenco wrote:
Ned Slider wrote:
Even better, I've backported the module for you from the latest upstream kernel (2.6.30.5) as a kABI tracking kmod package and put it in the elrepo-testing repository here (kmod-w83793):
http://elrepo.org http://elrepo.org/linux/testing/el5/
As you have the hardware, I'd appreciate if you would test the driver and report back how it works, either here or on the elrepo mailing lists or bug tracker.
It seems that everything is ok :) Thanks a lot! Adrian
Brilliant!
Thanks for reporting back. If you have no issues with it, I'll move it from testing to the main repository in a few days and will maintain it from there, so if you have elrepo installed, a 'yum update' will find future package updates for you.
BTW, because it's a kABI-tracking kmod package, it will work seamlessly across kernel updates :-)
Ned Slider wrote:
Adrian Sevcenco wrote:
Ned Slider wrote:
Even better, I've backported the module for you from the latest upstream kernel (2.6.30.5) as a kABI tracking kmod package and put it in the elrepo-testing repository here (kmod-w83793):
http://elrepo.org http://elrepo.org/linux/testing/el5/
As you have the hardware, I'd appreciate if you would test the driver and report back how it works, either here or on the elrepo mailing lists or bug tracker.
It seems that everything is ok :) Thanks a lot! Adrian
Brilliant!
Thanks for reporting back. If you have no issues with it, I'll move it
My pleasure :)
from testing to the main repository in a few days and will maintain it
beside using it, is there other things to do for testing if everything is alright?
from there, so if you have elrepo installed, a 'yum update' will find future package updates for you.
great! thanks!
BTW, because it's a kABI-tracking kmod package, it will work seamlessly across kernel updates :-)
thats great :)
Thanks! Adrian
Adrian Sevcenco wrote:
Ned Slider wrote:
Adrian Sevcenco wrote:
Ned Slider wrote:
Even better, I've backported the module for you from the latest upstream kernel (2.6.30.5) as a kABI tracking kmod package and put it in the elrepo-testing repository here (kmod-w83793):
http://elrepo.org http://elrepo.org/linux/testing/el5/
As you have the hardware, I'd appreciate if you would test the driver and report back how it works, either here or on the elrepo mailing lists or bug tracker.
It seems that everything is ok :) Thanks a lot! Adrian
Brilliant!
Thanks for reporting back. If you have no issues with it, I'll move it
My pleasure :)
from testing to the main repository in a few days and will maintain it
beside using it, is there other things to do for testing if everything is alright?
Not really, now you've confirmed it's working. If I don't hear anything further I'll just assume it continues to work as expected and move it out of testing and into the main repo.
Thanks again :-)