Re: Vmalloc.h implicit functions
On Wed, 08 Sep 2021 07:46:13 +0200, Omar Mustafa said:
Okay my kernel is 5.13.9-generic and I have tried what you mentioned but failed the only remaining solution I can think of is trying to install the Windows driver through NDISWrapper and it’s the RTL8822BE Bluetooth not the WiFi
First, Linux kernel email conventions are that you do a "reply all", so that others can comment even if I'm busy or don't know the answer. I've re-added kernelnewbies to the cc: list. Second, you still haven't said what driver you were trying to fix. The rest of us can't help with an out-of-tree driver unless we know where it's from. Also, can you give us what lspci or lsusb says your widget is?
The driver is RTL8822BE Bluetooth Sent from my iPhone
On 8 Sep 2021, at 7:54 AM, Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote:
On Wed, 08 Sep 2021 07:46:13 +0200, Omar Mustafa said:
Okay my kernel is 5.13.9-generic and I have tried what you mentioned but failed the only remaining solution I can think of is trying to install the Windows driver through NDISWrapper and it’s the RTL8822BE Bluetooth not the WiFi
First, Linux kernel email conventions are that you do a "reply all", so that others can comment even if I'm busy or don't know the answer. I've re-added kernelnewbies to the cc: list.
Second, you still haven't said what driver you were trying to fix. The rest of us can't help with an out-of-tree driver unless we know where it's from.
Also, can you give us what lspci or lsusb says your widget is?
On Wed, 08 Sep 2021 12:02:39 +0200, Omar Mustafa said:
The driver is RTL8822BE Bluetooth
That's not what I asked for. And that's not the *driver*, that's the *device*. For example, this laptop has an Ethernet and a wireless card: [~] lspci -nn |grep -i net 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 07) 02:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) and there's no RTL810xE or QCA8565 driver. The first actually uses the r8169 driver, and the second uses the ath9k driver. Both those drivers support a wide range of devices. iwlwifi is another driver that supports a whole bunch of devices. Meanwhile, a USB trackball I use is: [~] lsusb | grep Track Bus 001 Device 002: ID 045e:0023 Microsoft Corp. Trackball Optical And those [10ec:8136], [168c:0036], and [045e:0023] are actually important, as that is what the *HARDWARE* device identifies itself as, and what the kernel uses to identify which driver should be used to support the device.. There are many actual instances where the hardware device has both a USB and PCI variant - and only one or the other is actually supported by an in-tree driver. And you still haven't told us what driver source you're trying to compile, or where it came from.
Sorry for being late but it took me so long to find this: 10ec:b822:103c:831b Is this the driver you were talking about??
On 9 Sep 2021, at 3:40 AM, Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote:
On Wed, 08 Sep 2021 12:02:39 +0200, Omar Mustafa said:
The driver is RTL8822BE Bluetooth
That's not what I asked for. And that's not the *driver*, that's the *device*.
For example, this laptop has an Ethernet and a wireless card: [~] lspci -nn |grep -i net 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 07) 02:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)
and there's no RTL810xE or QCA8565 driver. The first actually uses the r8169 driver, and the second uses the ath9k driver. Both those drivers support a wide range of devices. iwlwifi is another driver that supports a whole bunch of devices.
Meanwhile, a USB trackball I use is:
[~] lsusb | grep Track Bus 001 Device 002: ID 045e:0023 Microsoft Corp. Trackball Optical
And those [10ec:8136], [168c:0036], and [045e:0023] are actually important, as that is what the *HARDWARE* device identifies itself as, and what the kernel uses to identify which driver should be used to support the device.. There are many actual instances where the hardware device has both a USB and PCI variant - and only one or the other is actually supported by an in-tree driver.
And you still haven't told us what driver source you're trying to compile, or where it came from. _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Wed, Sep 15, 2021 at 04:32:45PM +0200, Omar Mustafa wrote:
Sorry for being late but it took me so long to find this:
10ec:b822:103c:831b
Is this the driver you were talking about??
That is some sort of id. We need a link to the exact source code that you are trying to build and having problems with, in order to determine how to help you. But step back, why are you trying to build a driver out of the kernel tree? Why does the latest kernel release not support your device already? greg k-h
participants (3)
-
Greg KH -
Omar Mustafa -
Valdis Klētnieks