On Mon, 2011-10-31 at 18:30 +0100, Tino Schmidt wrote:
> > On Sun, 2011-10-16 at 22:25 +0200, Tino Schmidt wrote:
> > [...]
> >
> >> Hi,
> >> I'm sorry for the long delay but I can use the laptop only on weekend.
> >> Here is the output:
> >>
> >> # modprobe wistron_btns force=1
> >> FATAL: Error inserting wistron_btns
> >> (/lib/modules/2.6.26-2-686/kernel/drivers/input/misc/wistron_btns.ko):
> >> No such device
> >>
> > It looks like this model is rather different, maybe not a Wistron design
> > at all.
> >
> > I would prefer you to test against Linux 3.0, but it appears that the
> > model detection has not changed since 2.6.26.
> >
> >
> >> # dmesg
> >> [ 168.628474] wistron_btns: BIOS entry point not found
> >>
> >> and
> >> # grep . /sys/class/dmi/id/*_{vendor,name,version}
> >> /sys/class/dmi/id/bios_vendor:FUJITSU SIEMENS
> >> /sys/class/dmi/id/board_vendor:FUJITSU SIEMENS
> >> /sys/class/dmi/id/chassis_vendor:FUJITSU SIEMENS
> >> /sys/class/dmi/id/sys_vendor:FUJITSU SIEMENS
> >> /sys/class/dmi/id/board_name:AMILO A1655
> >> /sys/class/dmi/id/product_name:AMILO A Series
> >> /sys/class/dmi/id/bios_version:1.0C-8044-8A20
> >> /sys/class/dmi/id/board_version:Rev0.4b
> >> /sys/class/dmi/id/chassis_version:N/A
> >> /sys/class/dmi/id/product_version:0100
> >>
> > Please build and test the attached driver (make&& insmod
> > amilo-rfkill.ko). It provides a standard rfkill device which you can
> > control with e.g. the 'rfkill' command, and will only bind to specific
> > models.
> >
> > If this works, I'll submit the code upstream.
> >
> > Ben.
> >
> >
> Hi Ben,
> Thank you for your code!
>
> Before I built the module (Kernel 2.6.32) I had to insert the include
> line #include <asm/io.h> ( -> inb()-function ?)
That should be <linux/io.h>, actually.
> With Kernel 2.6.26 I couldn't even built the module.
>
> But loading of the module failed:
> # insmod amilo-rfkill.ko
> insmod: error inserting 'amilo-rfkill.ko': -1 No such device
Sorry, I made the driver look for product name "AMILO A1655" but that is
actually the board name. Could you try changing DMI_PRODUCT_NAME to
DMI_BOARD_NAME?
> In kernel 2.6.32 exists /dev/rfkill but
>
> # rfkill list
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: yes
>
> # rfkill unblock all
>
> # rfkill list
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: yes
>
> doesn't work here. Nothing changed.
This is the rfkill device exposed by the regular wireless driver. Since
it doesn't know anything about the model-specific blocking behaviour, it
appears to treat it as hard-blocking. But that shouldn't matter if we
can get this new driver working.
Ben.
--
Ben Hutchings
Computers are not intelligent. They only think they are.
Attachment:
signature.asc
Description: This is a digitally signed message part