Pleas add modules from iConnect: dvb-usb-it913x and...

[lulo]

Pleas add kernel modules from iConnect (and any arm): dvb-usb-it913x and very important: lm63.Thanks.

[kmihelich]

LM63 I can get in the current kernel if you need it right away, but the IT913x driver won't be available until 3.2. You can add an issue for it in github so I don't forget.

[lulo]

added issue https://github.com/archlinuxarm/PKGBUILDs/issues/118 .Thanks

P.S. Build manualy from git, modyfication PKGBUILDs/core/linux/config (add module => uncoment one line and... "m") & PKGBUILDs/core/linux/PKGBUID (md5sum from config), build for makepkg and install/upgrade new kernel, and install lm-sensors, reboot system, load manualy lm63 and i2c_mv64xxx, and config :

$this->bbcode_second_pass_code('', '[lulo@lulo-iconnect ~]$ sudo sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Use of uninitialized value in concatenation (.) or string at /usr/sbin/sensors-detect line 6623, <STDIN> line 1.
FATAL: Module cpuid not found.
Failed to load module cpuid.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... Use of uninitialized value in string eq at /usr/sbin/sensors-detect line 6244, <STDIN> line 1.
No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... Use of uninitialized value in string eq at /usr/sbin/sensors-detect line 6259, <STDIN> line 1.
No
VIA Nano thermal sensor... Use of uninitialized value in string eq at /usr/sbin/sensors-detect line 6273, <STDIN> line 1.
No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Sorry, no supported PCI bus adapters found.

Next adapter: mv64xxx_i2c adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x4c
Handled by driver `lm63' (already loaded), chip type `lm63'

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `lm63':
* Bus `mv64xxx_i2c adapter'
Busdriver `i2c_mv64xxx', I2C address 0x4c
Chip `lm63' (confidence: 6)

Do you want to generate /etc/conf.d/lm_sensors? (YES/no):
You should now start the lm_sensors service to load the required
kernel modules.

[lulo@lulo-iconnect ~]$ sudo sensors
lm63-i2c-0-4c
Adapter: mv64xxx_i2c adapter
temp1: +52.0°C (high = +70.0°C)
temp2: +51.6°C (low = +0.0°C, high = +70.0°C)
(crit = +85.0°C, hyst = +75.0°C)')

simple...and long, long time build's from my iConnect...add demon "sensors" for /etc/rc.conf



hmmm...arteq...w końcu to dodałeś...długo nie trzeba było czekać...dzięki

add git repository...very nice...
https://github.com/archlinuxarm/PKGBUILDs/pull/119

[kmihelich]

Yep, I'm hooked on phonics. 3.1.4-2 with LM63 is in the repo now. There looks to be patches out there for the dvb device for 3.0/3.1, but I got tired of trying to find something usable. I'll leave the github issue open so that when 3.2 is finalized I'll remember to get it into the config.

[kmihelich]

I never had to do it, just saying I like languages that have (mostly) obvious phonetic pronunciation.