Archiv > Development
Testbericht Mld 3.0.3 Mit Tt-s2-6400
Christian:
--- Quote --- Hallo,
--- Quote ---MLD> modprobe -r asus_atk0110
MLD> modprobe -r coretemp
MLD> lsmod
Module Size Used by Tainted: G
isl6423 1540 2
stv6110x 3104 2
stv090x 38637 2
saa716x_ff 19552 0
saa716x_core 42189 23 saa716x_ff
dvb_core 60265 2 saa716x_ff,saa716x_core
button 3477 0
processor 22891 0
r8169 39572 0
hwmon_vid 1708 0
fuse 48185 0
MLD> modprobe w83627ehf
modprobe: can't load module w83627ehf (kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy
--- End quote ---
Gruß Gerhard
--- End quote ---
Probiere einfach mal :
modprobe w83627ehf force_id=0x8860
gkd-berlin:
Hallo Christian,
hier ist das Ergebnis:
--- Quote ---MLD> modprobe -r coretemp
MLD> modprobe -r asus_atk0110
MLD> modprobe w83627ehf force_id=0x8860
modprobe: can't load module w83627ehf (kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy
MLD> lsmod
Module Size Used by Tainted: G
hwmon 897 0
isl6423 1540 2
stv6110x 3104 2
stv090x 38637 2
saa716x_ff 19552 0
saa716x_core 42189 24 saa716x_ff
dvb_core 60265 2 saa716x_ff,saa716x_core
button 3477 0
processor 22891 0
r8169 39572 0
hwmon_vid 1708 0
fuse 48185 0
MLD>
--- End quote ---
Gruß Gerhard
gkd-berlin:
Hallo,
Test: MLD-3.0.3_ff-hd-2013.07.20-56.iso vom 21.7.
Nichts Neues.
-----------------------------------------------------------------
--- Quote ---MLD> modprobe -r coretemp
MLD> modprobe -r asus_atk0110
MLD> modprobe w83627ehf
modprobe: can't load module w83627ehf (kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy
MLD> modprobe -r w83627ehf
MLD> modprobe w83627ehf
modprobe: can't load module w83627ehf (kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy
MLD> lsmod
Module Size Used by Tainted: G
hwmon 897 0
hwmon_vid 1708 0
isl6423 1540 2
stv6110x 3104 2
stv090x 38637 2
saa716x_ff 19552 0
saa716x_core 42189 22 saa716x_ff
dvb_core 60265 2 saa716x_ff,saa716x_core
button 3477 0
processor 22891 0
r8169 39572 0
fuse 48185 0
MLD>
--- End quote ---
Gruß Gerhard
Christian:
Das habe ich gefunden:
At start the system swears
... conflicts with ACPI region HWRE [0x290-0x299]
But lm_sensors successfully starts and sensors shows a state of all sensors.
Thanks.
Has found still here
http://bugzilla.kernel.org/show_bug.cgi?id=13571
"From now on you can add acpi_enforce_resources=lax to the kernel command line
to restore old behaviour."
And now I am confused, let and further swears at start or I should add an
option acpi_enforce_resources=lax.
-----------
Boot parameter acpi_enforce_resources is to restore the old (and dangerous)
behavior where the kernel did not prevent resource conflicts. It is discouraged
to use it, especially in your case were the asus_atk0110 driver works just
fine.
BTW, if you no longer attempt to load the w83627ehf driver, the error message
should no longer show at boot time.
I'm leaving this bug opened as a reminder that sensors-detect needs to be
somehow made aware of ACPI resource conflicts.
-------
Du kannst versuchen mit dem Kernelparameter : acpi_enforce_resources=lax
dein System zu starten oder das neuere Modul asus_atk0110 zu nehmen. Wenn du nicht auf vbat verzichten möchtest kannst du den Parameter ja einmal Testen.
gkd-berlin:
Hallo Christian,
???, wie mache ich das mit dem Kernelparameter?
Gruß Gerhard
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version