Hi everyone, I'm using backports 4.14 to build for a custom kernel 3.14. That kernel includes the RT2800 wifi driver, and if I configure backports with menuconfig to build a newer version of that driver it works perfectly. However, if I configure backports to build the RTL8821 driver, which my kernel otherwise does not include, the driver never gets built and backports shows it as not selected the next time I run menuconfig. Is this expected behaviour? Is there something I can do to force this driver to build? Thanks! Marlon -- To unsubscribe from this list: send the line "unsubscribe backports" in
On Mon, 2018-08-27 at 15:01 -0700, Marlon Smith wrote: > Hi everyone, Hi Marlon, > I'm using backports 4.14 to build for a custom kernel 3.14. That > kernel includes the RT2800 wifi driver, and if I configure backports > with menuconfig to build a newer version of that driver it works > perfectly. However, if I configure backports to build the RTL8821 > driver, which my kernel otherwise does not include, the driver never > gets built and backports shows it as not selected the next time I run > menuconfig. > > Is this expected behaviour? Is there something I can do to force > this > driver to build? This probably means that your 3.14 kernel doesn't have some of the dependencies needed by the RTL8821 driver from 4.14. Check the list of dependencies for the driver and make sure they are included in your 3.14 kernel. -- Luca. -- To unsubscribe from this list: send the line "unsubscribe backports" in
On Tue, 2018-08-28 at 07:42 +0300, Luca Coelho wrote:
> On Mon, 2018-08-27 at 15:01 -0700, Marlon Smith wrote:
> >
> > Hi everyone,
> Hi Marlon,
> > > >
> > I'm using backports 4.14 to build for a custom kernel 3.14. That
> > kernel includes the RT2800 wifi driver, and if I configure
> > backports
> > with menuconfig to build a newer version of that driver it works
> > perfectly. However, if I configure backports to build the RTL8821
> > driver, which my kernel otherwise does not include, the driver
> > never
> > gets built and backports shows it as not selected the next time I
> > run
> > menuconfig.
> >
> > Is this expected behaviour? Is there something I can do to force
> > this
> > driver to build?
> This probably means that your 3.14 kernel doesn't have some of the
> dependencies needed by the RTL8821 driver from 4.14. Check the list
> of
> dependencies for the driver and make sure they are included in your
> 3.14 kernel.
> > --
> Luca.
Hey Luca, thanks for the reply! The requirements in the backports 4.14
menuconfig are listed as follows:
Depends on: WLAN [=y] && WLAN_VENDOR_REALTEK [=y] && RTL_CARDS [=m] &&
m && BP_MODULES [=y] && PCI [=y]
I can find the symbol WLAN_VENDOR_REALTEK in the backports 4.14
menuconfig but not in the 3.14 kernel's menuconfig. Does this mean I
can't use the driver with this kernel?
--
To unsubscribe from this list: send the line "unsubscribe backports" in
On 08/29/2018 03:55 PM, Marlon Smith wrote:
> On Tue, 2018-08-28 at 07:42 +0300, Luca Coelho wrote:
>> On Mon, 2018-08-27 at 15:01 -0700, Marlon Smith wrote:
>>>
>>> Hi everyone,
>> Hi Marlon,
>>>>>
>>> I'm using backports 4.14 to build for a custom kernel 3.14. That
>>> kernel includes the RT2800 wifi driver, and if I configure
>>> backports
>>> with menuconfig to build a newer version of that driver it works
>>> perfectly. However, if I configure backports to build the RTL8821
>>> driver, which my kernel otherwise does not include, the driver
>>> never
>>> gets built and backports shows it as not selected the next time I
>>> run
>>> menuconfig.
>>>
>>> Is this expected behaviour? Is there something I can do to force
>>> this
>>> driver to build?
>> This probably means that your 3.14 kernel doesn't have some of the
>> dependencies needed by the RTL8821 driver from 4.14. Check the list
>> of
>> dependencies for the driver and make sure they are included in your
>> 3.14 kernel.
>>> --
>> Luca.
>
> Hey Luca, thanks for the reply! The requirements in the backports 4.14
> menuconfig are listed as follows:
>
> Depends on: WLAN [=y] && WLAN_VENDOR_REALTEK [=y] && RTL_CARDS [=m] &&
> m && BP_MODULES [=y] && PCI [=y]
>
> I can find the symbol WLAN_VENDOR_REALTEK in the backports 4.14
> menuconfig but not in the 3.14 kernel's menuconfig. Does this mean I
> can't use the driver with this kernel?
> --
Marlon,
That symbol postdates kernel 3.14. I have no idea if the backports code will
run, or even build, in kernels that old, but I think it would be safe for you to
edit the symbol WLAN_VENDOR_REALTEK out of that "depends on" line in the
configuration menu. At least, that will get you to the next problem. :)
Larry
--
To unsubscribe from this list: send the line "unsubscribe backports" in
On Wed, 2018-08-29 at 13:55 -0700, Marlon Smith wrote:
> Hey Luca, thanks for the reply! The requirements in the backports 4.14
> menuconfig are listed as follows:
>
> Depends on: WLAN [=y] && WLAN_VENDOR_REALTEK [=y] && RTL_CARDS [=m] &&
> m && BP_MODULES [=y] && PCI [=y]
>
> I can find the symbol WLAN_VENDOR_REALTEK in the backports 4.14
> menuconfig but not in the 3.14 kernel's menuconfig. Does this mean I
> can't use the driver with this kernel?
No, actually the symbol is enabled? See the [=y] above.
The above looks like it is actually enabled though, so something else
must be going on?
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Thanks everyone for the replies. The setting I was missing in the
kernel was that I need to have PCI enabled. I'm not sure why the
backports menuconfig said PCI [=y], since it was not enabled in the
kernel, but once I enabled it backports built the wifi driver
correctly.
Thanks again for the help!
Marlon
On Thu, 2018-08-30 at 09:33 +0200, Johannes Berg wrote:
> On Wed, 2018-08-29 at 13:55 -0700, Marlon Smith wrote:
>
> >
> > Hey Luca, thanks for the reply! The requirements in the backports
> > 4.14
> > menuconfig are listed as follows:
> >
> > Depends on: WLAN [=y] && WLAN_VENDOR_REALTEK [=y] && RTL_CARDS [=m]
> > &&
> > m && BP_MODULES [=y] && PCI [=y]
> >
> > I can find the symbol WLAN_VENDOR_REALTEK in the backports 4.14
> > menuconfig but not in the 3.14 kernel's menuconfig. Does this mean
> > I
> > can't use the driver with this kernel?
> No, actually the symbol is enabled? See the [=y] above.
>
> The above looks like it is actually enabled though, so something else
> must be going on?
>
> johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in