Not (yet) enabled kernel modules in -current

SCerovec · 09-21-2017, 01:38 PM

We actually don't have a rolling (pinned?) thread where we could note drMozes of present modules not enabled to compile on -current or even an updated release kernel.

How come, You ask

?

Being cheap as I am, I couldn't keep off from buying the cheapest mac802 b/g/n USB dongle there is - couldn't I?

No I couldn't - "what the hack, I will build it if not shipped, that darn module!" :^]

Guess what? Bleeding edge and bleeding nose again X_^

Long story short:

Kindly please drMozes, could You please enable the following module(s) for the next kernel release [snip(edit)] :
rtl8xxxu.ko

since I happen to own an Realtek 8192EU based wifi dongle?
(I checked they are not enabled ( drivers > wireless > Realtek > ...) in the currently shipped kernel)

drmozes · 09-22-2017, 06:24 AM

Quote:

Originally Posted by SCerovec

Long story short:

that's what I like :-)

Quote:

Originally Posted by SCerovec

drMozes, could You please enable the following module(s) for the next kernel release [snip(edit)] :

Done.

SCerovec · 09-23-2017, 07:07 AM

Kindest thanks for the swift response sir!
^_^

Just checking:
Is there a particular reason not to enable /input devices support/touchscreens/<many modules here>, besides compile time?

Maybe they are obsolete devices?

I even found some I was intending to tryout (SPI touchscreens for one), those certainly are hard to detect if not loaded as module?

thoughts anyone: to enable or not (too specific case of use - must be coded hard - not as module etc)?

drmozes · 09-24-2017, 12:12 PM

Quote:

Originally Posted by SCerovec

Is there a particular reason not to enable /input devices support/touchscreens/<many modules here>, besides compile time?

I add what I know is needed by the devices officially supported, plus anything else that looks useful or people ask for.
I have to try and make sure that the installer doesn't get too big either, otherwise it won't boot and I have to spend more time figuring out how to remove stuff.

If there's anything in particular, let me know!

SCerovec · 09-27-2017, 03:14 AM

Kindest thanks,

making any needed module (overnight

) isn't a chore as it used to be, would there a need suddenly arise.

Otherwise I (or anyone else, most probably

) will report any product that could benefit from any missing inclusion.

SCerovec · 11-13-2017, 01:23 PM

TL;DR:
after the latest update on -current I'm missing:
ath9x fammily including: ath9k_htc
on my x86 laptop, # lsmod shows:

Code:

ath9k_htc              51526  0
ath9k_common           24156  1 ath9k_htc
ath9k_hw              425616  2 ath9k_common,ath9k_htc
ath                    18006  3 ath9k_common,ath9k_htc,ath9k_hw

plus some (all?) rtl* drivers on staging ^_^?

drmozes · 11-13-2017, 04:41 PM

Quote:

Originally Posted by SCerovec

TL;DR:
after the latest update on -current I'm missing:
ath9x fammily including: ath9k_htc
on my x86 laptop, # lsmod shows:

Code:

ath9k_htc              51526  0
ath9k_common           24156  1 ath9k_htc
ath9k_hw              425616  2 ath9k_common,ath9k_htc
ath                    18006  3 ath9k_common,ath9k_htc,ath9k_hw

plus some (all?) rtl* drivers on staging ^_^?

They aren't missing since the latest update - they were never there.

SCerovec · 11-14-2017, 02:54 AM

!Caught!
When I wrote missing, I meant compared to 14.2 vs current, and in a kind of personal way. Not quite clear from my post, eh?

Can it be the two configs went out of sync?

One way, or the other, i type this on xvkbd on a banana pi, I plan to publish yet.
Of course thru the Atheros 9270 USB dongle, brought to life with said

ath9k_htc

module.

implying:
1 it builds clean
2 it supports latest USB dongles
3 there will be reports regarding my latest dwellings ^_^

drmozes · 11-14-2017, 04:13 AM

Quote:

Originally Posted by SCerovec

!Caught!
When I wrote missing, I meant compared to 14.2 vs current, and in a kind of personal way. Not quite clear from my post, eh?

Code:

root@stokely:~/armedslack/slackwarearm-14.2/patches/source/kernel/kernel-pkgs/configs# grep ATH config-armv7
CONFIG_IP_ROUTE_MULTIPATH=y
# CONFIG_BT_ATH3K is not set
CONFIG_MD_MULTIPATH=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_QL=m
CONFIG_DM_MULTIPATH_ST=m
# CONFIG_NET_VENDOR_ATHEROS is not set
# CONFIG_ATH_CARDS is not set
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_SECURITY_PATH is not set

No atheros in there either.
There are lots of RTL modules though.

Which specific ones do you want?

SCerovec · 11-14-2017, 09:42 AM

We might there be up to something?
http://bear.alienbase.nl/mirrors/sla...ric-4.4.14.x64

Code:

[snip]
CONFIG_WLAN=y
CONFIG_PCMCIA_RAYCS=m
CONFIG_LIBERTAS_THINFIRM=m
# CONFIG_LIBERTAS_THINFIRM_DEBUG is not set
CONFIG_LIBERTAS_THINFIRM_USB=m
CONFIG_AIRO=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m
CONFIG_PCMCIA_ATMEL=m
CONFIG_AT76C50X_USB=m
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_WL3501=m
CONFIG_PRISM54=m
CONFIG_USB_ZD1201=m
CONFIG_USB_NET_RNDIS_WLAN=m
CONFIG_ADM8211=m
CONFIG_RTL8180=m
CONFIG_RTL8187=m
CONFIG_RTL8187_LEDS=y
# CONFIG_MAC80211_HWSIM is not set
CONFIG_MWL8K=m
CONFIG_ATH_COMMON=m
CONFIG_ATH_CARDS=m
# CONFIG_ATH_DEBUG is not set
CONFIG_ATH5K=m
# CONFIG_ATH5K_DEBUG is not set
# CONFIG_ATH5K_TRACER is not set
CONFIG_ATH5K_PCI=y
CONFIG_ATH9K_HW=m
CONFIG_ATH9K_COMMON=m
CONFIG_ATH9K_BTCOEX_SUPPORT=y
CONFIG_ATH9K=m
CONFIG_ATH9K_PCI=y
# CONFIG_ATH9K_AHB is not set
# CONFIG_ATH9K_DEBUGFS is not set
# CONFIG_ATH9K_DYNACK is not set
CONFIG_ATH9K_WOW=y
CONFIG_ATH9K_RFKILL=y
CONFIG_ATH9K_CHANNEL_CONTEXT=y
CONFIG_ATH9K_PCOEM=y
CONFIG_ATH9K_HTC=m
# CONFIG_ATH9K_HTC_DEBUGFS is not set
[snip]

the Realtek of interest is:

Code:

[snip]
CONFIG_STAGING=y
# CONFIG_SLICOSS is not set
# CONFIG_PRISM2_USB is not set
# CONFIG_COMEDI is not set
# CONFIG_PANEL is not set
[snip]
CONFIG_RTLLIB=m
CONFIG_RTLLIB_CRYPTO_CCMP=m
CONFIG_RTLLIB_CRYPTO_TKIP=m
CONFIG_RTLLIB_CRYPTO_WEP=m
CONFIG_RTL8192E=m
CONFIG_R8712U=m
CONFIG_R8188EU=m
CONFIG_R8723AU=m
[snip]
CONFIG_8723AU_BT_COEXIST=y
[snip]

When i referred to 14.2 i was thinking on x86-14.2, and the arm-14.2 seems to differ quite a bit in module for module from it?

I'm trying to imply:
1. I was not specific enough (now I see)
2. Alienbase is certainly exact copy of Slackware's source?
3. Is there (if any) a reason not to have each USB module/driver from x86 enabled in arm too?

drmozes · 11-14-2017, 04:20 PM

Quote:

Originally Posted by SCerovec

Code:

CONFIG_PCMCIA_RAYCS=m

2. Alienbase is certainly exact copy of Slackware's source?

I don't know. I don't use it.

Quote:

3. Is there (if any) a reason not to have each USB module/driver from x86 enabled in arm too?

Yes because it has support for hardware that doesn't exist on ARM - such as PCMCIA - plus hardware that I cannot imagine anybody would ever conceivably use on ARM - and even if they wanted to, they can just go into the /usr/src/linux and add it to the config, then make modules_install
The ARM kernel has never been feature parity with x86. In an ideal world, the base set of modules ought to be, but unless something breaks, there's nothing to fix.

The ARM kernel provided is there to support the supported devices so that they work out of the box for basics such as networking, video (if possible), disc support and so on. If there's any real need for a new module, I'll add it - but I'm not going to add lists of modules just because someone has one on a shelf or plugged into another machine :-)

SCerovec · 11-15-2017, 11:51 AM

Sounds quite reasonable to me.

So, another surprise to Linux - the Arm and x86 are quite different beasts to tame?

Kind thanks sir, for the swift responses.

I still wonder how long until the rtl8xxx divers hits the mainline (even in staging), and the ever awaited /dev/fb0 on Orange PI?

For those following this thread - savvy buyers should stick to Atheros WiFi dongles - if anything - they just work.

SCerovec · 12-25-2017, 11:13 AM

It seems the official ARM config lost the

Quote:

CONFIG_ATH9K_HTC=m

line somehow ?

Or is it by purpose?

It takes about 4+ hours to compile the modules natively on that Banana Pi.

SCerovec · 02-09-2019, 04:08 PM

Code:

Support for small TFT LCD display modules  --->

FB_TFT [=m]

it is in drivers/staging/ and is somewhat a generic driver for projects like this:

https://kaspars.net/blog/spi-display-orange-pi-zero

... implying many SBC would potentially benefit of it being included now on IMHO.

i'd personally prefer it be module, but hard coding it would also have benefits - not my call

drmozes · 02-10-2019, 05:56 AM

Quote:

Originally Posted by SCerovec

It seems the official ARM config lost the .. CONFIG_ATH9K_HTC=m

It hasn't.

I'll look at the other FB stuff.