On Thu, 2014-07-31 at 20:22 +0200, J. Roeleveld wrote: > On 31 July 2014 19:40:07 CEST, Nilesh Govindrajan <m...@nileshgr.com> wrote: > >On Wed, 2014-07-30 at 16:32 +0530, Nilesh Govindrajan wrote: > >> On 30-Jul-2014 4:30 pm, "Mick" <michaelkintz...@gmail.com> wrote: > >> > > >> > On Wednesday 30 Jul 2014 11:53:25 Nilesh Govindrajan wrote: > >> > > So I got a new Lenovo G50. > >> > > I found all the required drivers in kernel itself. Seems to be > >> quite Linux > >> > > friendly so far (not installed desktop yet). > >> > > > >> > > There's one problem though. The kernel module ideapad-laptop > >which > >> > > apparently recognizes the hotkey stuff, backlight and some other > >> things > >> > > doesn't let me use wireless. rfkill shows it's hard blocked. Is > >> there any > >> > > way to change this? > >> > > > >> > > Some Google results tell me that this is related to the WiFi > >> toggle via > >> > > windows. The machine never contained windows ( I bought it with > >> freedos). > >> > > > >> > > I'm not comfortable with opening it to remove CMOS battery as > >> suggested by > >> > > yet another Google search result. > >> > > >> > What does 'rfkill enable wlan0' give you? It should be able to > >> override any > >> > hotkey setting. > >> > > >> > -- > >> > Regards, > >> > Mick > >> > >> The soft block gets removed, but hard block remains, and there's no > >> hardware switch for the same. If I remove the module it works without > >> any problems. > >> > > > >I don't really understand the exact purpose of that module. Touchpad, > >brightness control, sound control, camera, radio everything works out > >of > >the box without the module. Except that I'm not able to toggle airplane > >mode using the hotkey, but that's not a big issue. > > I am not familiar with that module. > But in a long distant past I wrote a module to handle the special keys on an > ASUS laptop which were exposed via ACPI. > I always assume these modules add support for special keys and settings not > handled by any other driver. > > -- > Joost
Yes, a quick scan through the code told me that. But I still don't understand why radio gets hard blocked when the module is enabled and works perfectly when the module is not loaded. I found this bug today - https://bugzilla.kernel.org/show_bug.cgi?id=56381 So I guess, it's just a matter of time. Wish I knew kernel coding to supply a patch.
