iw commands cannot "see" my rtl8192du device #17
Comments
|
Did you generate the driver with CFG80211 specified? I have not yet gotten to the point of debugging the CFG80211 interface, and the commands may very well be failing. I will gladly review any patches you generate. |
|
Thank you for your response. I am afraid I do not understand how to specify CFG80211. I ran make, then make install. I have tried to find documentation on how I would specify CFG80211 to the process, but without success. Would you tell me? At times, but not always, I have seen cfg80211 messages in dmesg since installing this driver. They had to do with the regulatory domain and frequencies of operation. So, possibly the CFG80211 is included in my generated driver, but I am unsure. Thank you. |
|
Check the define statements in include/autoconf.h to see what is enabled. |
|
They are commented out. I will uncomment them and rebuild. Thank you very much. Sorry I am such a newbie. :) |
|
Ouch. Now, make ends with errors. I must have done the wrong thing. /home/tim/Realtek/rtl8192du/rtl8192du/include/autoconf.h:26:1: error: unknown type name ‘ifdef’ |
|
Yes, that "define" needs to have "#" in front of it; however, even if you make that change it still will not build. I'm busy today and will not have a chance to find out what is wrong. Unless you want to debug the problems, you should not use iw. |
|
Ok. I am not asking you to look at this, now, just showing you my current results. I believe I have uncommented the proper line: #define CONFIG_IOCTL_CFG80211 1 Now, make fails. Several modules are compiled successfully, then: /home/tim/Realtek/rtl8192du/rtl8192du/core/rtw_p2p.c: In function ‘rtw_p2p_check_frames’: |
|
Ok, I made big progress since my last post. I saw that there are multiple branches of the repository and downloaded the one labeled kernel, which has the most recent changes. The good news is that it compiled everything successfully and, after a reboot, the r8192du module was associated with cfg80211. I could run the iw commands, successfully. However, I could no longer connect to my router. When I scanned for it, it only replied that the network is down. I tried several methods of connecting, but nothing could scan and find the SSID of the router. To connect, I had to reinstall the Master branch that does not work with cfg80211. I am back on the network, but still without iw capabilities. Thank you for any help you can give me, when you get time to look at it. |
|
I have the same issue as ratcheer. I look forward to any ideas. @ratcheer What does "modprobe 8192du" give you now? Have you tried the realtech drivers located below? |
|
Someone is trying to uncomment the "C directive". Unbelievable! :rolf: |
|
i am having same problem i donot know what is firmware i cannect to wifi but my wifi adapter is not shown in iw list and iw dev return nothing. I have realtek rtl8191s. PLEASe HELP |
|
Does that driver support nl80211/cfg80211? If not, you must use iwconfig. Saying you have rtl8192s is not sufficient. Is it an rtl8192su or rtl8192se? |
|
Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter
this is my network adapter
i donot know how to install the driver in linux
i am learning
plz help me
i will be really thankful
which driver should i download ,,,
i want to be programmar .
…On Sat, Aug 4, 2018 at 8:39 PM, lwfinger ***@***.***> wrote:
Does that driver support nl80211/cfg80211? If not, you must use iwconfig.
Saying you have rtl8192s is not sufficient. Is it an rtl8192su or
rtl8192se?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AoIkz7cX7FwJkS3s-fF7SpvcHkYT2Vzkks5uNbWMgaJpZM4Bziq9>
.
|
|
plz send the link of driver
…On Wed, Aug 8, 2018 at 6:46 PM, Sansar Sah ***@***.***> wrote:
Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter
this is my network adapter
i donot know how to install the driver in linux
i am learning
plz help me
i will be really thankful
which driver should i download ,,,
i want to be programmar .
On Sat, Aug 4, 2018 at 8:39 PM, lwfinger ***@***.***> wrote:
> Does that driver support nl80211/cfg80211? If not, you must use iwconfig.
>
> Saying you have rtl8192s is not sufficient. Is it an rtl8192su or
> rtl8192se?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#17 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AoIkz7cX7FwJkS3s-fF7SpvcHkYT2Vzkks5uNbWMgaJpZM4Bziq9>
> .
>
|
|
This type of low-level tutoring is best done by the forum for your Linux distribution. To clone this source repository, git clone git://github.com/lwfinger/rtl8192du.git To build the driver, cd rtl8192du For the "make step" to work, you must have the kernel headers installed and configured. If you do not know what that means, google "Linux build external drivers". Unlike Windows, every driver must be built for a given kernel and version of gcc. There is no way I could provide a pre-compiled version that would load and run on your computer. You obviously need to do some additional research. |
|
oke man i doing
…On Wed, Aug 8, 2018 at 9:31 PM, lwfinger ***@***.***> wrote:
This type of low-level tutoring is best done by the forum for your Linux
distribution. To clone this source repository,
git clone git://github.com/lwfinger/rtl8192du.git
To build the driver,
cd rtl8192du
make
sudo make install
For the "make step" to work, you must have the kernel headers installed
and configured. If you do not know what that means, google "Linux build
external drivers".
Unlike Windows, every driver must be built for a given kernel and version
of gcc. There is no way I could provide a pre-compiled version that would
load and run on your computer.
You obviously need to do some additional research.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AoIkz_YHG5TqhP5OvmZRuPG9QeCvB61oks5uOwfmgaJpZM4Bziq9>
.
|
|
you are so helpful
…On Fri, Aug 10, 2018 at 9:35 PM, Sansar Sah ***@***.***> wrote:
oke man i doing
On Wed, Aug 8, 2018 at 9:31 PM, lwfinger ***@***.***> wrote:
> This type of low-level tutoring is best done by the forum for your Linux
> distribution. To clone this source repository,
>
> git clone git://github.com/lwfinger/rtl8192du.git
>
> To build the driver,
>
> cd rtl8192du
> make
> sudo make install
>
> For the "make step" to work, you must have the kernel headers installed
> and configured. If you do not know what that means, google "Linux build
> external drivers".
>
> Unlike Windows, every driver must be built for a given kernel and version
> of gcc. There is no way I could provide a pre-compiled version that would
> load and run on your computer.
>
> You obviously need to do some additional research.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#17 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AoIkz_YHG5TqhP5OvmZRuPG9QeCvB61oks5uOwfmgaJpZM4Bziq9>
> .
>
|
|
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.15.0-kali2-amd64/build
M=/home/carl12/rtl8192du modules
make[1]: *** /lib/modules/4.15.0-kali2-amd64/build: No such file or
directory. Stop.
Makefile:682: recipe for target 'modules' failed
make: *** [modules] Error 2
…On Fri, Aug 10, 2018 at 11:50 AM, Sansar Sah ***@***.***> wrote:
you are so helpful
On Fri, Aug 10, 2018 at 9:35 PM, Sansar Sah ***@***.***> wrote:
> oke man i doing
>
>
> On Wed, Aug 8, 2018 at 9:31 PM, lwfinger ***@***.***>
> wrote:
>
>> This type of low-level tutoring is best done by the forum for your Linux
>> distribution. To clone this source repository,
>>
>> git clone git://github.com/lwfinger/rtl8192du.git
>>
>> To build the driver,
>>
>> cd rtl8192du
>> make
>> sudo make install
>>
>> For the "make step" to work, you must have the kernel headers installed
>> and configured. If you do not know what that means, google "Linux build
>> external drivers".
>>
>> Unlike Windows, every driver must be built for a given kernel and
>> version of gcc. There is no way I could provide a pre-compiled version that
>> would load and run on your computer.
>>
>> You obviously need to do some additional research.
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>> <#17 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AoIkz_YHG5TqhP5OvmZRuPG9QeCvB61oks5uOwfmgaJpZM4Bziq9>
>> .
>>
>
>
|
|
so which kernal header i should install
…On Sat, Aug 11, 2018 at 1:59 AM, Sansar Sah ***@***.***> wrote:
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.15.0-kali2-amd64/build
M=/home/carl12/rtl8192du modules
make[1]: *** /lib/modules/4.15.0-kali2-amd64/build: No such file or
directory. Stop.
Makefile:682: recipe for target 'modules' failed
make: *** [modules] Error 2
On Fri, Aug 10, 2018 at 11:50 AM, Sansar Sah ***@***.***> wrote:
> you are so helpful
>
>
> On Fri, Aug 10, 2018 at 9:35 PM, Sansar Sah ***@***.***> wrote:
>
>> oke man i doing
>>
>>
>> On Wed, Aug 8, 2018 at 9:31 PM, lwfinger ***@***.***>
>> wrote:
>>
>>> This type of low-level tutoring is best done by the forum for your
>>> Linux distribution. To clone this source repository,
>>>
>>> git clone git://github.com/lwfinger/rtl8192du.git
>>>
>>> To build the driver,
>>>
>>> cd rtl8192du
>>> make
>>> sudo make install
>>>
>>> For the "make step" to work, you must have the kernel headers installed
>>> and configured. If you do not know what that means, google "Linux build
>>> external drivers".
>>>
>>> Unlike Windows, every driver must be built for a given kernel and
>>> version of gcc. There is no way I could provide a pre-compiled version that
>>> would load and run on your computer.
>>>
>>> You obviously need to do some additional research.
>>>
>>> —
>>> You are receiving this because you commented.
>>> Reply to this email directly, view it on GitHub
>>> <#17 (comment)>,
>>> or mute the thread
>>> <https://github.com/notifications/unsubscribe-auth/AoIkz_YHG5TqhP5OvmZRuPG9QeCvB61oks5uOwfmgaJpZM4Bziq9>
>>> .
>>>
>>
>>
>
|
|
carl12@kali:~$ sudo apt-get install linux-headers-generic
[sudo] password for carl12:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-headers-generic
carl12@kali:~$
…On Sat, Aug 11, 2018 at 2:19 AM, Sansar Sah ***@***.***> wrote:
so which kernal header i should install
On Sat, Aug 11, 2018 at 1:59 AM, Sansar Sah ***@***.***> wrote:
> make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.15.0-kali2-amd64/build
> M=/home/carl12/rtl8192du modules
> make[1]: *** /lib/modules/4.15.0-kali2-amd64/build: No such file or
> directory. Stop.
> Makefile:682: recipe for target 'modules' failed
> make: *** [modules] Error 2
>
>
> On Fri, Aug 10, 2018 at 11:50 AM, Sansar Sah ***@***.***>
> wrote:
>
>> you are so helpful
>>
>>
>> On Fri, Aug 10, 2018 at 9:35 PM, Sansar Sah ***@***.***>
>> wrote:
>>
>>> oke man i doing
>>>
>>>
>>> On Wed, Aug 8, 2018 at 9:31 PM, lwfinger ***@***.***>
>>> wrote:
>>>
>>>> This type of low-level tutoring is best done by the forum for your
>>>> Linux distribution. To clone this source repository,
>>>>
>>>> git clone git://github.com/lwfinger/rtl8192du.git
>>>>
>>>> To build the driver,
>>>>
>>>> cd rtl8192du
>>>> make
>>>> sudo make install
>>>>
>>>> For the "make step" to work, you must have the kernel headers
>>>> installed and configured. If you do not know what that means, google "Linux
>>>> build external drivers".
>>>>
>>>> Unlike Windows, every driver must be built for a given kernel and
>>>> version of gcc. There is no way I could provide a pre-compiled version that
>>>> would load and run on your computer.
>>>>
>>>> You obviously need to do some additional research.
>>>>
>>>> —
>>>> You are receiving this because you commented.
>>>> Reply to this email directly, view it on GitHub
>>>> <#17 (comment)>,
>>>> or mute the thread
>>>> <https://github.com/notifications/unsubscribe-auth/AoIkz_YHG5TqhP5OvmZRuPG9QeCvB61oks5uOwfmgaJpZM4Bziq9>
>>>> .
>>>>
>>>
>>>
>>
>
|
|
when i type sudo apt-get install linux-headers-generic
it says as above
even this i type
sudo apt-get install linux-headers-$(uname -r) i get
carl12@kali:~$ sudo apt-get install linux-headers-$(uname -r)
[sudo] password for carl12:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-headers-4.15.0-kali2-amd64
E: Couldn't find any package by glob 'linux-headers-4.15.0-kali2-amd64'
E: Couldn't find any package by regex 'linux-headers-4.15.0-kali2-amd64'
carl12@kali:~$
…On Sat, Aug 11, 2018 at 2:25 AM, Sansar Sah ***@***.***> wrote:
***@***.***:~$ sudo apt-get install linux-headers-generic
[sudo] password for carl12:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-headers-generic
***@***.***:~$
On Sat, Aug 11, 2018 at 2:19 AM, Sansar Sah ***@***.***> wrote:
> so which kernal header i should install
>
>
> On Sat, Aug 11, 2018 at 1:59 AM, Sansar Sah ***@***.***> wrote:
>
>> make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.15.0-kali2-amd64/build
>> M=/home/carl12/rtl8192du modules
>> make[1]: *** /lib/modules/4.15.0-kali2-amd64/build: No such file or
>> directory. Stop.
>> Makefile:682: recipe for target 'modules' failed
>> make: *** [modules] Error 2
>>
>>
>> On Fri, Aug 10, 2018 at 11:50 AM, Sansar Sah ***@***.***>
>> wrote:
>>
>>> you are so helpful
>>>
>>>
>>> On Fri, Aug 10, 2018 at 9:35 PM, Sansar Sah ***@***.***>
>>> wrote:
>>>
>>>> oke man i doing
>>>>
>>>>
>>>> On Wed, Aug 8, 2018 at 9:31 PM, lwfinger ***@***.***>
>>>> wrote:
>>>>
>>>>> This type of low-level tutoring is best done by the forum for your
>>>>> Linux distribution. To clone this source repository,
>>>>>
>>>>> git clone git://github.com/lwfinger/rtl8192du.git
>>>>>
>>>>> To build the driver,
>>>>>
>>>>> cd rtl8192du
>>>>> make
>>>>> sudo make install
>>>>>
>>>>> For the "make step" to work, you must have the kernel headers
>>>>> installed and configured. If you do not know what that means, google "Linux
>>>>> build external drivers".
>>>>>
>>>>> Unlike Windows, every driver must be built for a given kernel and
>>>>> version of gcc. There is no way I could provide a pre-compiled version that
>>>>> would load and run on your computer.
>>>>>
>>>>> You obviously need to do some additional research.
>>>>>
>>>>> —
>>>>> You are receiving this because you commented.
>>>>> Reply to this email directly, view it on GitHub
>>>>> <#17 (comment)>,
>>>>> or mute the thread
>>>>> <https://github.com/notifications/unsubscribe-auth/AoIkz_YHG5TqhP5OvmZRuPG9QeCvB61oks5uOwfmgaJpZM4Bziq9>
>>>>> .
>>>>>
>>>>
>>>>
>>>
>>
>
|
|
Note that the headers must match EXACTLY the kernel you are running. I would first do an update to make sure you have the latest kernel version, and then reboot. Once the system comes back, then sudo apt-get install headers-$(uname -r) |
|
carl12@kali:~$ ls /lib/modules/$(uname -r)/build/include
ls: cannot access '/lib/modules/4.15.0-kali2-amd64/build/include': No such
file or directory
…On Sat, Aug 11, 2018 at 12:41 PM, lwfinger ***@***.***> wrote:
Note that the headers must match EXACTLY the kernel you are running. I
would first do an update to make sure you have the latest kernel version,
and then reboot. Once the system comes back, then sudo apt-get install
headers-$(uname -r)
That should do what you want, but be aware that I do not use Kali. That
command seems reasonable to me, but you may need additional steps. You will
know that it is correct when the command
ls /lib/modules/$(uname -r)/build/include
gives you a list of directories.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AoIkzxOL13CzbwHOrzv1GOCFW9XJUsQ3ks5uPwk1gaJpZM4Bziq9>
.
|
|
that command doesnt work
…On Mon, Aug 13, 2018 at 8:46 AM, Sansar Sah ***@***.***> wrote:
***@***.***:~$ ls /lib/modules/$(uname -r)/build/include
ls: cannot access '/lib/modules/4.15.0-kali2-amd64/build/include': No
such file or directory
On Sat, Aug 11, 2018 at 12:41 PM, lwfinger ***@***.***>
wrote:
> Note that the headers must match EXACTLY the kernel you are running. I
> would first do an update to make sure you have the latest kernel version,
> and then reboot. Once the system comes back, then sudo apt-get install
> headers-$(uname -r)
> That should do what you want, but be aware that I do not use Kali. That
> command seems reasonable to me, but you may need additional steps. You will
> know that it is correct when the command
> ls /lib/modules/$(uname -r)/build/include
> gives you a list of directories.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#17 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AoIkzxOL13CzbwHOrzv1GOCFW9XJUsQ3ks5uPwk1gaJpZM4Bziq9>
> .
>
|
|
my kernal version
carl12@kali:~$ uname -r
4.15.0-kali2-amd64
…On Mon, Aug 13, 2018 at 8:47 AM, Sansar Sah ***@***.***> wrote:
that command doesnt work
On Mon, Aug 13, 2018 at 8:46 AM, Sansar Sah ***@***.***> wrote:
> ***@***.***:~$ ls /lib/modules/$(uname -r)/build/include
> ls: cannot access '/lib/modules/4.15.0-kali2-amd64/build/include': No
> such file or directory
>
>
>
> On Sat, Aug 11, 2018 at 12:41 PM, lwfinger ***@***.***>
> wrote:
>
>> Note that the headers must match EXACTLY the kernel you are running. I
>> would first do an update to make sure you have the latest kernel version,
>> and then reboot. Once the system comes back, then sudo apt-get install
>> headers-$(uname -r)
>> That should do what you want, but be aware that I do not use Kali. That
>> command seems reasonable to me, but you may need additional steps. You will
>> know that it is correct when the command
>> ls /lib/modules/$(uname -r)/build/include
>> gives you a list of directories.
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>> <#17 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AoIkzxOL13CzbwHOrzv1GOCFW9XJUsQ3ks5uPwk1gaJpZM4Bziq9>
>> .
>>
>
>
|
|
wait a minute
when i boot
it says failed to load regulatory.db is there any connection with it
…On Mon, Aug 13, 2018 at 8:48 AM, Sansar Sah ***@***.***> wrote:
my kernal version
***@***.***:~$ uname -r
4.15.0-kali2-amd64
On Mon, Aug 13, 2018 at 8:47 AM, Sansar Sah ***@***.***> wrote:
> that command doesnt work
>
>
> On Mon, Aug 13, 2018 at 8:46 AM, Sansar Sah ***@***.***> wrote:
>
>> ***@***.***:~$ ls /lib/modules/$(uname -r)/build/include
>> ls: cannot access '/lib/modules/4.15.0-kali2-amd64/build/include': No
>> such file or directory
>>
>>
>>
>> On Sat, Aug 11, 2018 at 12:41 PM, lwfinger ***@***.***>
>> wrote:
>>
>>> Note that the headers must match EXACTLY the kernel you are running. I
>>> would first do an update to make sure you have the latest kernel version,
>>> and then reboot. Once the system comes back, then sudo apt-get install
>>> headers-$(uname -r)
>>> That should do what you want, but be aware that I do not use Kali. That
>>> command seems reasonable to me, but you may need additional steps. You will
>>> know that it is correct when the command
>>> ls /lib/modules/$(uname -r)/build/include
>>> gives you a list of directories.
>>>
>>> —
>>> You are receiving this because you commented.
>>> Reply to this email directly, view it on GitHub
>>> <#17 (comment)>,
>>> or mute the thread
>>> <https://github.com/notifications/unsubscribe-auth/AoIkzxOL13CzbwHOrzv1GOCFW9XJUsQ3ks5uPwk1gaJpZM4Bziq9>
>>> .
>>>
>>
>>
>
|
|
The "ls" command does not work because your kernel headers are not set up correctly. Until you fix that problem, the builds will fail exactly as you first reported. The missing regulatory.db indicates a different problem. The only thing in common is that it is a further indication that your system is incomplete. Either switch to a distro that works, or consult your distro's forums to find out how to build out-of-kernel modules. I cannot help you. |
|
so what should do , you mean i should upgrade distro how to do that
i have no idea
plz help me
i wanted to fix problem fast
…On Mon, Aug 13, 2018 at 11:22 AM, lwfinger ***@***.***> wrote:
The "ls" command does not work because your kernel headers are not set up
correctly. Until you fix that problem, the builds will fail exactly as you
first reported.
The missing regulatory.db indicates a different problem. The only thing in
common is that it is a further indication that your system is incomplete.
Either switch to a distro that works, or consult your distro's forums to
find out how to build out-of-kernel modules. I cannot help you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AoIkz5qImMeY5w4IPWyXlX5-WaXNGyz9ks5uQZmYgaJpZM4Bziq9>
.
|
|
how can we talk simultaneusly
…On Tue, Aug 14, 2018 at 3:33 AM, Sansar Sah ***@***.***> wrote:
so what should do , you mean i should upgrade distro how to do that
i have no idea
plz help me
i wanted to fix problem fast
On Mon, Aug 13, 2018 at 11:22 AM, lwfinger ***@***.***>
wrote:
> The "ls" command does not work because your kernel headers are not set up
> correctly. Until you fix that problem, the builds will fail exactly as you
> first reported.
>
> The missing regulatory.db indicates a different problem. The only thing
> in common is that it is a further indication that your system is incomplete.
>
> Either switch to a distro that works, or consult your distro's forums to
> find out how to build out-of-kernel modules. I cannot help you.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#17 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AoIkz5qImMeY5w4IPWyXlX5-WaXNGyz9ks5uQZmYgaJpZM4Bziq9>
> .
>
|
|
which linux distribution are you using so i could use same and you can give
me pre compile header.
…On Tue, Aug 14, 2018 at 3:33 AM, Sansar Sah ***@***.***> wrote:
how can we talk simultaneusly
On Tue, Aug 14, 2018 at 3:33 AM, Sansar Sah ***@***.***> wrote:
> so what should do , you mean i should upgrade distro how to do that
> i have no idea
>
> plz help me
> i wanted to fix problem fast
>
>
> On Mon, Aug 13, 2018 at 11:22 AM, lwfinger ***@***.***>
> wrote:
>
>> The "ls" command does not work because your kernel headers are not set
>> up correctly. Until you fix that problem, the builds will fail exactly as
>> you first reported.
>>
>> The missing regulatory.db indicates a different problem. The only thing
>> in common is that it is a further indication that your system is incomplete.
>>
>> Either switch to a distro that works, or consult your distro's forums to
>> find out how to build out-of-kernel modules. I cannot help you.
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>> <#17 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AoIkz5qImMeY5w4IPWyXlX5-WaXNGyz9ks5uQZmYgaJpZM4Bziq9>
>> .
>>
>
>
|
|
If you use my distro, I would not have to give you pre-compiled headers. You only need to install one additional package beyond the usual compiler and make packages. Go to https://software.opensuse.org/ and choose the Leap option. For installation only, you can either choose the DVD image (3.6 GB), or the Network image (120 MB). Using dd, burn the downloaded .iso to a USB stick, and boot it. The network image downloads the packages when they are installed. If you want to try openSUSE before installing, select the Live image. To be most like Kali, choose the Gnome desktop. Again that .iso should be burned to a USB stick. From the running live system, you can install. Once the OS is installed, you can get the necessary packages to build with the commands sudo zypper install git gcc kernel-devel Note: zypper is like "apt", and kernel-devel contains the kernel headers. At this point, you need to do a "git clone" the way you did before, change to the directory with the source, "make" and sudo "make install". |
|
OKe i will do that . But what is mean by {The network image downloads the
packages when they are installed.}
…On Tue, Aug 14, 2018 at 8:25 PM, lwfinger ***@***.***> wrote:
If you use my distro, I would not have to give you pre-compiled headers.
You only need to install one additional package beyond the usual compiler
and make packages.
Go to https://software.opensuse.org/ and choose the Leap option. For
installation only, you can either choose the DVD image (3.6 GB), or the
Network image (120 MB). Using dd, burn the downloaded .iso to a USB stick,
and boot it. The network image downloads the packages when they are
installed.
If you want to try openSUSE before installing, select the Live image. To
be most like Kali, choose the Gnome desktop. Again that .iso should be
burned to a USB stick. From the running live system, you can install.
Once the OS is installed, you can get the necessary packages to build with
the commands
sudo zypper install git gcc kernel-devel
Note: zypper is like "apt", and kernel-devel contains the kernel headers.
At this point, you need to do a "git clone" the way you did before, change
to the directory with the source, "make" and sudo "make install".
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AoIkzw_9Er8jAvHm0T2bzYevhx3xzm4Fks5uQuFTgaJpZM4Bziq9>
.
|
|
Thank you for your kind help,
…On Wed, Aug 15, 2018 at 2:35 PM, Sansar Sah ***@***.***> wrote:
OKe i will do that . But what is mean by {The network image downloads
the packages when they are installed.}
On Tue, Aug 14, 2018 at 8:25 PM, lwfinger ***@***.***>
wrote:
> If you use my distro, I would not have to give you pre-compiled headers.
> You only need to install one additional package beyond the usual compiler
> and make packages.
>
> Go to https://software.opensuse.org/ and choose the Leap option. For
> installation only, you can either choose the DVD image (3.6 GB), or the
> Network image (120 MB). Using dd, burn the downloaded .iso to a USB stick,
> and boot it. The network image downloads the packages when they are
> installed.
>
> If you want to try openSUSE before installing, select the Live image. To
> be most like Kali, choose the Gnome desktop. Again that .iso should be
> burned to a USB stick. From the running live system, you can install.
>
> Once the OS is installed, you can get the necessary packages to build
> with the commands
>
> sudo zypper install git gcc kernel-devel
>
> Note: zypper is like "apt", and kernel-devel contains the kernel headers.
> At this point, you need to do a "git clone" the way you did before, change
> to the directory with the source, "make" and sudo "make install".
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#17 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AoIkzw_9Er8jAvHm0T2bzYevhx3xzm4Fks5uQuFTgaJpZM4Bziq9>
> .
>
|
|
i ran the command sudo zypper install git gcc kernel-devel and is installed
…On Wed, Aug 15, 2018 at 4:55 AM, Sansar Sah ***@***.***> wrote:
Thank you for your kind help,
On Wed, Aug 15, 2018 at 2:35 PM, Sansar Sah ***@***.***> wrote:
> OKe i will do that . But what is mean by {The network image downloads
> the packages when they are installed.}
>
> On Tue, Aug 14, 2018 at 8:25 PM, lwfinger ***@***.***>
> wrote:
>
>> If you use my distro, I would not have to give you pre-compiled headers.
>> You only need to install one additional package beyond the usual compiler
>> and make packages.
>>
>> Go to https://software.opensuse.org/ and choose the Leap option. For
>> installation only, you can either choose the DVD image (3.6 GB), or the
>> Network image (120 MB). Using dd, burn the downloaded .iso to a USB stick,
>> and boot it. The network image downloads the packages when they are
>> installed.
>>
>> If you want to try openSUSE before installing, select the Live image. To
>> be most like Kali, choose the Gnome desktop. Again that .iso should be
>> burned to a USB stick. From the running live system, you can install.
>>
>> Once the OS is installed, you can get the necessary packages to build
>> with the commands
>>
>> sudo zypper install git gcc kernel-devel
>>
>> Note: zypper is like "apt", and kernel-devel contains the kernel
>> headers. At this point, you need to do a "git clone" the way you did
>> before, change to the directory with the source, "make" and sudo "make
>> install".
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>> <#17 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AoIkzw_9Er8jAvHm0T2bzYevhx3xzm4Fks5uQuFTgaJpZM4Bziq9>
>> .
>>
>
>
|
|
i didnt understand
[change to the directory with the source, "make" and sudo "make install".]
…On Wed, Aug 15, 2018 at 8:29 AM, Sansar Sah ***@***.***> wrote:
i ran the command sudo zypper install git gcc kernel-devel and is installed
On Wed, Aug 15, 2018 at 4:55 AM, Sansar Sah ***@***.***> wrote:
> Thank you for your kind help,
>
> On Wed, Aug 15, 2018 at 2:35 PM, Sansar Sah ***@***.***> wrote:
>
>> OKe i will do that . But what is mean by {The network image downloads
>> the packages when they are installed.}
>>
>> On Tue, Aug 14, 2018 at 8:25 PM, lwfinger ***@***.***>
>> wrote:
>>
>>> If you use my distro, I would not have to give you pre-compiled
>>> headers. You only need to install one additional package beyond the usual
>>> compiler and make packages.
>>>
>>> Go to https://software.opensuse.org/ and choose the Leap option. For
>>> installation only, you can either choose the DVD image (3.6 GB), or the
>>> Network image (120 MB). Using dd, burn the downloaded .iso to a USB stick,
>>> and boot it. The network image downloads the packages when they are
>>> installed.
>>>
>>> If you want to try openSUSE before installing, select the Live image.
>>> To be most like Kali, choose the Gnome desktop. Again that .iso should be
>>> burned to a USB stick. From the running live system, you can install.
>>>
>>> Once the OS is installed, you can get the necessary packages to build
>>> with the commands
>>>
>>> sudo zypper install git gcc kernel-devel
>>>
>>> Note: zypper is like "apt", and kernel-devel contains the kernel
>>> headers. At this point, you need to do a "git clone" the way you did
>>> before, change to the directory with the source, "make" and sudo "make
>>> install".
>>>
>>> —
>>> You are receiving this because you commented.
>>> Reply to this email directly, view it on GitHub
>>> <#17 (comment)>,
>>> or mute the thread
>>> <https://github.com/notifications/unsubscribe-auth/AoIkzw_9Er8jAvHm0T2bzYevhx3xzm4Fks5uQuFTgaJpZM4Bziq9>
>>> .
>>>
>>
>>
>
|
|
carl@linux-9p5o:~> ls
bin Desktop Documents Downloads Music Pictures Public Templates
Videos
carl@linux-9p5o:~> cd source
bash: cd: source: No such file or directory
carl@linux-9p5o:~> make
make: *** No targets specified and no makefile found. Stop.
carl@linux-9p5o:~>
…On Wed, Aug 15, 2018 at 8:30 AM, Sansar Sah ***@***.***> wrote:
i didnt understand
[change to the directory with the source, "make" and sudo "make install".]
On Wed, Aug 15, 2018 at 8:29 AM, Sansar Sah ***@***.***> wrote:
> i ran the command sudo zypper install git gcc kernel-devel and is
> installed
>
>
> On Wed, Aug 15, 2018 at 4:55 AM, Sansar Sah ***@***.***> wrote:
>
>> Thank you for your kind help,
>>
>> On Wed, Aug 15, 2018 at 2:35 PM, Sansar Sah ***@***.***>
>> wrote:
>>
>>> OKe i will do that . But what is mean by {The network image downloads
>>> the packages when they are installed.}
>>>
>>> On Tue, Aug 14, 2018 at 8:25 PM, lwfinger ***@***.***>
>>> wrote:
>>>
>>>> If you use my distro, I would not have to give you pre-compiled
>>>> headers. You only need to install one additional package beyond the usual
>>>> compiler and make packages.
>>>>
>>>> Go to https://software.opensuse.org/ and choose the Leap option. For
>>>> installation only, you can either choose the DVD image (3.6 GB), or the
>>>> Network image (120 MB). Using dd, burn the downloaded .iso to a USB stick,
>>>> and boot it. The network image downloads the packages when they are
>>>> installed.
>>>>
>>>> If you want to try openSUSE before installing, select the Live image.
>>>> To be most like Kali, choose the Gnome desktop. Again that .iso should be
>>>> burned to a USB stick. From the running live system, you can install.
>>>>
>>>> Once the OS is installed, you can get the necessary packages to build
>>>> with the commands
>>>>
>>>> sudo zypper install git gcc kernel-devel
>>>>
>>>> Note: zypper is like "apt", and kernel-devel contains the kernel
>>>> headers. At this point, you need to do a "git clone" the way you did
>>>> before, change to the directory with the source, "make" and sudo "make
>>>> install".
>>>>
>>>> —
>>>> You are receiving this because you commented.
>>>> Reply to this email directly, view it on GitHub
>>>> <#17 (comment)>,
>>>> or mute the thread
>>>> <https://github.com/notifications/unsubscribe-auth/AoIkzw_9Er8jAvHm0T2bzYevhx3xzm4Fks5uQuFTgaJpZM4Bziq9>
>>>> .
>>>>
>>>
>>>
>>
>
|
|
will i be able to hack wifi in open suse i mean will i be able to use
wifippisher
…On Wed, Aug 15, 2018 at 8:31 AM, Sansar Sah ***@***.***> wrote:
***@***.***:~> ls
bin Desktop Documents Downloads Music Pictures Public Templates
Videos
***@***.***:~> cd source
bash: cd: source: No such file or directory
***@***.***:~> make
make: *** No targets specified and no makefile found. Stop.
***@***.***:~>
On Wed, Aug 15, 2018 at 8:30 AM, Sansar Sah ***@***.***> wrote:
> i didnt understand
>
> [change to the directory with the source, "make" and sudo "make install".]
>
>
> On Wed, Aug 15, 2018 at 8:29 AM, Sansar Sah ***@***.***> wrote:
>
>> i ran the command sudo zypper install git gcc kernel-devel and is
>> installed
>>
>>
>> On Wed, Aug 15, 2018 at 4:55 AM, Sansar Sah ***@***.***>
>> wrote:
>>
>>> Thank you for your kind help,
>>>
>>> On Wed, Aug 15, 2018 at 2:35 PM, Sansar Sah ***@***.***>
>>> wrote:
>>>
>>>> OKe i will do that . But what is mean by {The network image
>>>> downloads the packages when they are installed.}
>>>>
>>>> On Tue, Aug 14, 2018 at 8:25 PM, lwfinger ***@***.***>
>>>> wrote:
>>>>
>>>>> If you use my distro, I would not have to give you pre-compiled
>>>>> headers. You only need to install one additional package beyond the usual
>>>>> compiler and make packages.
>>>>>
>>>>> Go to https://software.opensuse.org/ and choose the Leap option. For
>>>>> installation only, you can either choose the DVD image (3.6 GB), or the
>>>>> Network image (120 MB). Using dd, burn the downloaded .iso to a USB stick,
>>>>> and boot it. The network image downloads the packages when they are
>>>>> installed.
>>>>>
>>>>> If you want to try openSUSE before installing, select the Live image.
>>>>> To be most like Kali, choose the Gnome desktop. Again that .iso should be
>>>>> burned to a USB stick. From the running live system, you can install.
>>>>>
>>>>> Once the OS is installed, you can get the necessary packages to build
>>>>> with the commands
>>>>>
>>>>> sudo zypper install git gcc kernel-devel
>>>>>
>>>>> Note: zypper is like "apt", and kernel-devel contains the kernel
>>>>> headers. At this point, you need to do a "git clone" the way you did
>>>>> before, change to the directory with the source, "make" and sudo "make
>>>>> install".
>>>>>
>>>>> —
>>>>> You are receiving this because you commented.
>>>>> Reply to this email directly, view it on GitHub
>>>>> <#17 (comment)>,
>>>>> or mute the thread
>>>>> <https://github.com/notifications/unsubscribe-auth/AoIkzw_9Er8jAvHm0T2bzYevhx3xzm4Fks5uQuFTgaJpZM4Bziq9>
>>>>> .
>>>>>
>>>>
>>>>
>>>
>>
>
|
|
You need to "cd" to the actual directory where the rtl8192du source is downloaded. Just as with any other distro, you need to "git clone" the actual source. It is not part of any distro!!!! If you want to do anything other than connect to an AP, you are going to need to learn a lot. |
|
carl@linux-9p5o:~> cd rtl8192du
carl@linux-9p5o:~/rtl8192du> ls
core hal Makefile README.md rtl8192dufw_wol.bin
dkms.conf include os_dep rtl8192dufw.bin
carl@linux-9p5o:~/rtl8192du> make
make ARCH=x86_64 CROSS_COMPILE= -C
/lib/modules/4.12.14-lp150.11-default/build M=/home/carl/rtl8192du modules
make[1]: *** /lib/modules/4.12.14-lp150.11-default/build: No such file or
directory. Stop.
make: *** [Makefile:682: modules] Error 2
carl@linux-9p5o:~/rtl8192du>
still make command doesnt work.
…On Wed, Aug 15, 2018 at 9:47 PM, lwfinger ***@***.***> wrote:
You need to "cd" to the actual directory where the rtl8192du source is
downloaded. Just as with any other distro, you need to "git clone" the
actual source. It is not part of any distro!!!!
If you want to do anything other than connect to an AP, you are going to
need to learn a lot.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AoIkzzJD_7Eh5el5KlC0iiNxmYwrUgTyks5uREYkgaJpZM4Bziq9>
.
|
|
carl@linux-9p5o:~> sudo zypper install git gcc kernel-devel
[sudo] password for root:
root
Sorry, try again.
[sudo] password for root:
Loading repository data...
Reading installed packages...
'gcc' is already installed.
No update candidate for 'gcc-7-lp150.1.50.x86_64'. The highest available
version is already installed.
'git' is already installed.
No update candidate for 'git-2.16.4-lp150.2.3.1.x86_64'. The highest
available version is already installed.
'kernel-devel' is already installed.
No update candidate for 'kernel-devel-4.12.14-lp150.12.13.1.noarch'. The
highest available version is already installed.
Resolving package dependencies...
Nothing to do.
carl@linux-9p5o:~>
though i installed kernal deval
…On Thu, Aug 16, 2018 at 6:10 PM, Sansar Sah ***@***.***> wrote:
***@***.***:~> cd rtl8192du
***@***.***:~/rtl8192du> ls
core hal Makefile README.md rtl8192dufw_wol.bin
dkms.conf include os_dep rtl8192dufw.bin
***@***.***:~/rtl8192du> make
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.12.14-lp150.11-default/build
M=/home/carl/rtl8192du modules
make[1]: *** /lib/modules/4.12.14-lp150.11-default/build: No such file or
directory. Stop.
make: *** [Makefile:682: modules] Error 2
***@***.***:~/rtl8192du>
still make command doesnt work.
On Wed, Aug 15, 2018 at 9:47 PM, lwfinger ***@***.***>
wrote:
> You need to "cd" to the actual directory where the rtl8192du source is
> downloaded. Just as with any other distro, you need to "git clone" the
> actual source. It is not part of any distro!!!!
>
> If you want to do anything other than connect to an AP, you are going to
> need to learn a lot.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#17 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AoIkzzJD_7Eh5el5KlC0iiNxmYwrUgTyks5uREYkgaJpZM4Bziq9>
> .
>
|
|
what is your fb id dude
will you plz reply fast so i can solve my problem fast and i can focus in
my high school study
…On Thu, Aug 16, 2018 at 6:12 PM, Sansar Sah ***@***.***> wrote:
***@***.***:~> sudo zypper install git gcc kernel-devel
[sudo] password for root:
root
Sorry, try again.
[sudo] password for root:
Loading repository data...
Reading installed packages...
'gcc' is already installed.
No update candidate for 'gcc-7-lp150.1.50.x86_64'. The highest available
version is already installed.
'git' is already installed.
No update candidate for 'git-2.16.4-lp150.2.3.1.x86_64'. The highest
available version is already installed.
'kernel-devel' is already installed.
No update candidate for 'kernel-devel-4.12.14-lp150.12.13.1.noarch'. The
highest available version is already installed.
Resolving package dependencies...
Nothing to do.
***@***.***:~>
though i installed kernal deval
On Thu, Aug 16, 2018 at 6:10 PM, Sansar Sah ***@***.***> wrote:
> ***@***.***:~> cd rtl8192du
> ***@***.***:~/rtl8192du> ls
> core hal Makefile README.md rtl8192dufw_wol.bin
> dkms.conf include os_dep rtl8192dufw.bin
> ***@***.***:~/rtl8192du> make
> make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.12.14-lp150.11-default/build
> M=/home/carl/rtl8192du modules
> make[1]: *** /lib/modules/4.12.14-lp150.11-default/build: No such file
> or directory. Stop.
> make: *** [Makefile:682: modules] Error 2
> ***@***.***:~/rtl8192du>
>
>
>
>
> still make command doesnt work.
>
>
> On Wed, Aug 15, 2018 at 9:47 PM, lwfinger ***@***.***>
> wrote:
>
>> You need to "cd" to the actual directory where the rtl8192du source is
>> downloaded. Just as with any other distro, you need to "git clone" the
>> actual source. It is not part of any distro!!!!
>>
>> If you want to do anything other than connect to an AP, you are going to
>> need to learn a lot.
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>> <#17 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AoIkzzJD_7Eh5el5KlC0iiNxmYwrUgTyks5uREYkgaJpZM4Bziq9>
>> .
>>
>
>
|
|
You are so brilliant
…On Thu, Aug 16, 2018 at 6:31 PM, Sansar Sah ***@***.***> wrote:
what is your fb id dude
will you plz reply fast so i can solve my problem fast and i can focus in
my high school study
On Thu, Aug 16, 2018 at 6:12 PM, Sansar Sah ***@***.***> wrote:
> ***@***.***:~> sudo zypper install git gcc kernel-devel
> [sudo] password for root:
> root
> Sorry, try again.
> [sudo] password for root:
> Loading repository data...
> Reading installed packages...
> 'gcc' is already installed.
> No update candidate for 'gcc-7-lp150.1.50.x86_64'. The highest available
> version is already installed.
> 'git' is already installed.
> No update candidate for 'git-2.16.4-lp150.2.3.1.x86_64'. The highest
> available version is already installed.
> 'kernel-devel' is already installed.
> No update candidate for 'kernel-devel-4.12.14-lp150.12.13.1.noarch'. The
> highest available version is already installed.
> Resolving package dependencies...
>
> Nothing to do.
> ***@***.***:~>
>
>
>
> though i installed kernal deval
>
> On Thu, Aug 16, 2018 at 6:10 PM, Sansar Sah ***@***.***> wrote:
>
>> ***@***.***:~> cd rtl8192du
>> ***@***.***:~/rtl8192du> ls
>> core hal Makefile README.md rtl8192dufw_wol.bin
>> dkms.conf include os_dep rtl8192dufw.bin
>> ***@***.***:~/rtl8192du> make
>> make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.12.14-lp150.11-default/build
>> M=/home/carl/rtl8192du modules
>> make[1]: *** /lib/modules/4.12.14-lp150.11-default/build: No such file
>> or directory. Stop.
>> make: *** [Makefile:682: modules] Error 2
>> ***@***.***:~/rtl8192du>
>>
>>
>>
>>
>> still make command doesnt work.
>>
>>
>> On Wed, Aug 15, 2018 at 9:47 PM, lwfinger ***@***.***>
>> wrote:
>>
>>> You need to "cd" to the actual directory where the rtl8192du source is
>>> downloaded. Just as with any other distro, you need to "git clone" the
>>> actual source. It is not part of any distro!!!!
>>>
>>> If you want to do anything other than connect to an AP, you are going
>>> to need to learn a lot.
>>>
>>> —
>>> You are receiving this because you commented.
>>> Reply to this email directly, view it on GitHub
>>> <#17 (comment)>,
>>> or mute the thread
>>> <https://github.com/notifications/unsubscribe-auth/AoIkzzJD_7Eh5el5KlC0iiNxmYwrUgTyks5uREYkgaJpZM4Bziq9>
>>> .
>>>
>>
>>
>
|
|
I think you also need kernel-default-devel. Of courser you need to "sudo zypper inslall" that package. |
|
i typed the command sudo zypper inslall kernel-default-devel
i installed it
…On Thu, Aug 16, 2018 at 9:20 PM, lwfinger ***@***.***> wrote:
I think you also need kernel-default-devel. Of courser you need to "sudo
zypper inslall" that package.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AoIkz1ppl_nBvtm_YkNOnKS6mW-KcShUks5uRZFDgaJpZM4Bziq9>
.
|
|
carl@linux-9p5o:~/rtl8192du> make
make ARCH=x86_64 CROSS_COMPILE= -C
/lib/modules/4.12.14-lp150.11-default/build M=/home/carl/rtl8192du modules
make[1]: *** /lib/modules/4.12.14-lp150.11-default/build: No such file or
directory. Stop.
make: *** [Makefile:682: modules] Error 2
carl@linux-9p5o:~/rtl8192du>
still make command doesnt work
…On Fri, Aug 17, 2018 at 1:22 PM, Sansar Sah ***@***.***> wrote:
i typed the command sudo zypper inslall kernel-default-devel
i installed it
On Thu, Aug 16, 2018 at 9:20 PM, lwfinger ***@***.***>
wrote:
> I think you also need kernel-default-devel. Of courser you need to "sudo
> zypper inslall" that package.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#17 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AoIkz1ppl_nBvtm_YkNOnKS6mW-KcShUks5uRZFDgaJpZM4Bziq9>
> .
>
|
|
but still make command doesnt work
…On Fri, Aug 17, 2018 at 1:23 PM, Sansar Sah ***@***.***> wrote:
***@***.***:~/rtl8192du> make
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.12.14-lp150.11-default/build
M=/home/carl/rtl8192du modules
make[1]: *** /lib/modules/4.12.14-lp150.11-default/build: No such file or
directory. Stop.
make: *** [Makefile:682: modules] Error 2
***@***.***:~/rtl8192du>
still make command doesnt work
On Fri, Aug 17, 2018 at 1:22 PM, Sansar Sah ***@***.***> wrote:
> i typed the command sudo zypper inslall kernel-default-devel
>
> i installed it
>
>
> On Thu, Aug 16, 2018 at 9:20 PM, lwfinger ***@***.***>
> wrote:
>
>> I think you also need kernel-default-devel. Of courser you need to "sudo
>> zypper inslall" that package.
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>> <#17 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AoIkz1ppl_nBvtm_YkNOnKS6mW-KcShUks5uRZFDgaJpZM4Bziq9>
>> .
>>
>
>
|
|
what is your fb id
…On Fri, Aug 17, 2018 at 2:07 PM, Sansar Sah ***@***.***> wrote:
but still make command doesnt work
On Fri, Aug 17, 2018 at 1:23 PM, Sansar Sah ***@***.***> wrote:
> ***@***.***:~/rtl8192du> make
> make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.12.14-lp150.11-default/build
> M=/home/carl/rtl8192du modules
> make[1]: *** /lib/modules/4.12.14-lp150.11-default/build: No such file
> or directory. Stop.
> make: *** [Makefile:682: modules] Error 2
> ***@***.***:~/rtl8192du>
>
>
>
> still make command doesnt work
>
>
> On Fri, Aug 17, 2018 at 1:22 PM, Sansar Sah ***@***.***> wrote:
>
>> i typed the command sudo zypper inslall kernel-default-devel
>>
>> i installed it
>>
>>
>> On Thu, Aug 16, 2018 at 9:20 PM, lwfinger ***@***.***>
>> wrote:
>>
>>> I think you also need kernel-default-devel. Of courser you need to
>>> "sudo zypper inslall" that package.
>>>
>>> —
>>> You are receiving this because you commented.
>>> Reply to this email directly, view it on GitHub
>>> <#17 (comment)>,
>>> or mute the thread
>>> <https://github.com/notifications/unsubscribe-auth/AoIkz1ppl_nBvtm_YkNOnKS6mW-KcShUks5uRZFDgaJpZM4Bziq9>
>>> .
>>>
>>
>>
>
|
|
I have no idea what you are doing, or not doing. I used the openSUSE Leap 15 DVD to create a new virtual machine instance. After the initial reboot, I used the commands: After it rebooted, I did The driver compiled with no errors. |
|
sudo zypper update
sudo reboot
i neeed to do this
…On Fri, Aug 17, 2018 at 10:03 PM, lwfinger ***@***.***> wrote:
I have no idea what you are doing, or not doing.
I used the openSUSE Leap 15 DVD to create a new virtual machine instance.
After the initial reboot, I used the commands:
sudo zypper update
sudo reboot
After it rebooted, I did
sudo zypper install gcc make git kernel-devel kernel-default-devel
git clone git://github.com/lwfinger/rtl8192du.git
cd rtl8192du
make
The driver compiled with no errors.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AoIkzzmA7f4yQL6p3fOmD6D6qA3j0A5Gks5uRuzqgaJpZM4Bziq9>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I installed the driver and firmware, last night. For the first time, I got a working 802.11n connection, although my speeds are still no better than the "g" connection I had with another device. So, thank you very much for these modules.
The problem is that, even though the connection is working very well, the iw management commands do not see it, at all. "iw dev" returns nothing. "iw dev wlan1 link" returns "Not connected." "iw wlan1 connect " returns "command failed: No such device (-19)".
The ip commands work as intended, e.g., "ip addr show" returns "3: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000", etc. Also, when I was using a Ralink onboard PCI wireless adapter, the iw commands worked perfectly well.
My OS is Siduction Linux, my kernel is 3.14.1, and my wireless adapter is a Belkin F9L1108-TG.
The text was updated successfully, but these errors were encountered: