rtl-wifi-devel Mailing List for Realtek Linux wireless driver
Status: Alpha
Brought to you by:
hauke-m
Menu
▾
▴
rtl-wifi-devel — Open Developer Mailing Lists
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Hosam H. <h.h...@gm...> - 2014-07-20 08:33:26
|
Recompiling the kernel or installing a new one would not work. Because I would recompile Adapter’s 2 driver and that would probably cause the same conflict again. I recompiled backports 3.15 source files with my custom settings, but this time for both chipsets. I needed to use “make defconfig-wifi” because RTL8187B is not listed in “make menuconfig” or compiled when using “make defconfig-rtlwifi” After using “make defconfig-wifi” I manipulated my settings and now everything works Thank you! Regards, Eng. Hosam Hittini On Jul 19, 2014, at 5:04 AM, Markus Gothe <nie...@ly...> wrote: > [ 3097.162716] rtl8187: Unknown symbol wiphy_rfkill_start_polling (err -22) > [ 3097.162739] rtl8187: disagrees about version of symbol ieee80211_unregister_hw > > Tells me you should recompile your driver and kernel… > FWIW. > > //M > > On 19 Jul 2014, at 03:02 , Markus Gothe <nie...@ly...> wrote: > >> Welcome to the beauty of open source…. >> If it ain’t working use KGDB to debug it, fix it yourself. >> >> That’s the real beauty of a long time dead driver… >> >> //M >> >> On 17 Jul 2014, at 12:14 , Hosam Hittini <h.h...@gm...> wrote: >> >>> Hello there, >>> >>> I have Ubuntu 13.10 Server running 3.11 kernel, I also have two USB Wireless adapters as follows: >>> Adapter 1: Realtek RTL8187B chipset https://www.thinkpenguin.com/gnu-lin...-g-usb-adapter >>> Adapter 2: AR7010+AR9280 chipsets https://www.thinkpenguin.com/gnu-lin...nux-tpe-nusbdb >>> They claim that they work out of the box and they did, however, Adapter 2 had some limitations on frequency use >>> So, I recompiled backports 3.15 source files after doing some manipulations to get a more opened driver, these manipulations were only for Atheros drivers >>> Now, Adapter 1 stopped working, I tested the same adapter on another computer and it works fine >>> The adapter doesn't even show up in lshw -C network >>> I looked at the module in /lib/modules and the module is still there, apparently it wasn't modified recently >>> Kindly look at the following codes >>> >>> hosam@Robin-05:~$ sudo modprobe rtl8187 >>> ERROR: could not insert 'rtl8187': Invalid argument >>> >>> hosam@Robin-05:~$ sudo insmod /lib/modules/3.11.0-12-generic/kernel/drivers/net/wireless/rtl818x/rtl8187/rtl8187.ko >>> Error: could not insert module /lib/modules/3.11.0-12-generic/kernel/drivers/net/wireless/rtl818x/rtl8187/rtl8187.ko: Invalid parameters >>> >>> hosam@Robin-05:~$ dmesg | tail >>> [ 3097.162711] rtl8187: disagrees about version of symbol wiphy_rfkill_start_polling >>> [ 3097.162716] rtl8187: Unknown symbol wiphy_rfkill_start_polling (err -22) >>> [ 3097.162739] rtl8187: disagrees about version of symbol ieee80211_unregister_hw >>> [ 3097.162744] rtl8187: Unknown symbol ieee80211_unregister_hw (err -22) >>> [ 3097.162757] rtl8187: disagrees about version of symbol ieee80211_beacon_get_tim >>> [ 3097.162761] rtl8187: Unknown symbol ieee80211_beacon_get_tim (err -22) >>> [ 3097.162800] rtl8187: disagrees about version of symbol ieee80211_rx_irqsafe >>> [ 3097.162805] rtl8187: Unknown symbol ieee80211_rx_irqsafe (err -22) >>> [ 3097.162828] rtl8187: disagrees about version of symbol ieee80211_rts_duration >>> [ 3097.162833] rtl8187: Unknown symbol ieee80211_rts_duration (err -22) >>> >>> Do you have any suggestions? >>> Thank you >>> >>> Regards, >>> Eng. Hosam Hittini >>> >>> ------------------------------------------------------------------------------ >>> Want fast and easy access to all the code in your enterprise? Index and >>> search up to 200,000 lines of code with a free copy of Black Duck >>> Code Sight - the same software that powers the world's largest code >>> search on Ohloh, the Black Duck Open Hub! Try it now. >>> http://p.sf.net/sfu/bds_______________________________________________ >>> Rtl-wifi-devel mailing list >>> Rtl...@li... >>> https://lists.sourceforge.net/lists/listinfo/rtl-wifi-devel >> >> >> >> //Markus - The panama-hat hacker >> >> ------------------------------------------------------------------------------ >> Want fast and easy access to all the code in your enterprise? Index and >> search up to 200,000 lines of code with a free copy of Black Duck >> Code Sight - the same software that powers the world's largest code >> search on Ohloh, the Black Duck Open Hub! Try it now. >> http://p.sf.net/sfu/bds_______________________________________________ >> Rtl-wifi-devel mailing list >> Rtl...@li... >> https://lists.sourceforge.net/lists/listinfo/rtl-wifi-devel > > > > //Markus - The panama-hat hacker > |
|
From: Markus G. <nie...@ly...> - 2014-07-19 01:02:17
|
[ 3097.162716] rtl8187: Unknown symbol wiphy_rfkill_start_polling (err -22) [ 3097.162739] rtl8187: disagrees about version of symbol ieee80211_unregister_hw Tells me you should recompile your driver and kernel… FWIW. //M On 19 Jul 2014, at 03:02 , Markus Gothe <nie...@ly...> wrote: > Welcome to the beauty of open source…. > If it ain’t working use KGDB to debug it, fix it yourself. > > That’s the real beauty of a long time dead driver… > > //M > > On 17 Jul 2014, at 12:14 , Hosam Hittini <h.h...@gm...> wrote: > >> Hello there, >> >> I have Ubuntu 13.10 Server running 3.11 kernel, I also have two USB Wireless adapters as follows: >> Adapter 1: Realtek RTL8187B chipset https://www.thinkpenguin.com/gnu-lin...-g-usb-adapter >> Adapter 2: AR7010+AR9280 chipsets https://www.thinkpenguin.com/gnu-lin...nux-tpe-nusbdb >> They claim that they work out of the box and they did, however, Adapter 2 had some limitations on frequency use >> So, I recompiled backports 3.15 source files after doing some manipulations to get a more opened driver, these manipulations were only for Atheros drivers >> Now, Adapter 1 stopped working, I tested the same adapter on another computer and it works fine >> The adapter doesn't even show up in lshw -C network >> I looked at the module in /lib/modules and the module is still there, apparently it wasn't modified recently >> Kindly look at the following codes >> >> hosam@Robin-05:~$ sudo modprobe rtl8187 >> ERROR: could not insert 'rtl8187': Invalid argument >> >> hosam@Robin-05:~$ sudo insmod /lib/modules/3.11.0-12-generic/kernel/drivers/net/wireless/rtl818x/rtl8187/rtl8187.ko >> Error: could not insert module /lib/modules/3.11.0-12-generic/kernel/drivers/net/wireless/rtl818x/rtl8187/rtl8187.ko: Invalid parameters >> >> hosam@Robin-05:~$ dmesg | tail >> [ 3097.162711] rtl8187: disagrees about version of symbol wiphy_rfkill_start_polling >> [ 3097.162716] rtl8187: Unknown symbol wiphy_rfkill_start_polling (err -22) >> [ 3097.162739] rtl8187: disagrees about version of symbol ieee80211_unregister_hw >> [ 3097.162744] rtl8187: Unknown symbol ieee80211_unregister_hw (err -22) >> [ 3097.162757] rtl8187: disagrees about version of symbol ieee80211_beacon_get_tim >> [ 3097.162761] rtl8187: Unknown symbol ieee80211_beacon_get_tim (err -22) >> [ 3097.162800] rtl8187: disagrees about version of symbol ieee80211_rx_irqsafe >> [ 3097.162805] rtl8187: Unknown symbol ieee80211_rx_irqsafe (err -22) >> [ 3097.162828] rtl8187: disagrees about version of symbol ieee80211_rts_duration >> [ 3097.162833] rtl8187: Unknown symbol ieee80211_rts_duration (err -22) >> >> Do you have any suggestions? >> Thank you >> >> Regards, >> Eng. Hosam Hittini >> >> ------------------------------------------------------------------------------ >> Want fast and easy access to all the code in your enterprise? Index and >> search up to 200,000 lines of code with a free copy of Black Duck >> Code Sight - the same software that powers the world's largest code >> search on Ohloh, the Black Duck Open Hub! Try it now. >> http://p.sf.net/sfu/bds_______________________________________________ >> Rtl-wifi-devel mailing list >> Rtl...@li... >> https://lists.sourceforge.net/lists/listinfo/rtl-wifi-devel > > > > //Markus - The panama-hat hacker > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds_______________________________________________ > Rtl-wifi-devel mailing list > Rtl...@li... > https://lists.sourceforge.net/lists/listinfo/rtl-wifi-devel //Markus - The panama-hat hacker |
|
From: Markus G. <nie...@ly...> - 2014-07-19 00:59:58
|
Welcome to the beauty of open source…. If it ain’t working use KGDB to debug it, fix it yourself. That’s the real beauty of a long time dead driver… //M On 17 Jul 2014, at 12:14 , Hosam Hittini <h.h...@gm...> wrote: > Hello there, > > I have Ubuntu 13.10 Server running 3.11 kernel, I also have two USB Wireless adapters as follows: > Adapter 1: Realtek RTL8187B chipset https://www.thinkpenguin.com/gnu-lin...-g-usb-adapter > Adapter 2: AR7010+AR9280 chipsets https://www.thinkpenguin.com/gnu-lin...nux-tpe-nusbdb > They claim that they work out of the box and they did, however, Adapter 2 had some limitations on frequency use > So, I recompiled backports 3.15 source files after doing some manipulations to get a more opened driver, these manipulations were only for Atheros drivers > Now, Adapter 1 stopped working, I tested the same adapter on another computer and it works fine > The adapter doesn't even show up in lshw -C network > I looked at the module in /lib/modules and the module is still there, apparently it wasn't modified recently > Kindly look at the following codes > > hosam@Robin-05:~$ sudo modprobe rtl8187 > ERROR: could not insert 'rtl8187': Invalid argument > > hosam@Robin-05:~$ sudo insmod /lib/modules/3.11.0-12-generic/kernel/drivers/net/wireless/rtl818x/rtl8187/rtl8187.ko > Error: could not insert module /lib/modules/3.11.0-12-generic/kernel/drivers/net/wireless/rtl818x/rtl8187/rtl8187.ko: Invalid parameters > > hosam@Robin-05:~$ dmesg | tail > [ 3097.162711] rtl8187: disagrees about version of symbol wiphy_rfkill_start_polling > [ 3097.162716] rtl8187: Unknown symbol wiphy_rfkill_start_polling (err -22) > [ 3097.162739] rtl8187: disagrees about version of symbol ieee80211_unregister_hw > [ 3097.162744] rtl8187: Unknown symbol ieee80211_unregister_hw (err -22) > [ 3097.162757] rtl8187: disagrees about version of symbol ieee80211_beacon_get_tim > [ 3097.162761] rtl8187: Unknown symbol ieee80211_beacon_get_tim (err -22) > [ 3097.162800] rtl8187: disagrees about version of symbol ieee80211_rx_irqsafe > [ 3097.162805] rtl8187: Unknown symbol ieee80211_rx_irqsafe (err -22) > [ 3097.162828] rtl8187: disagrees about version of symbol ieee80211_rts_duration > [ 3097.162833] rtl8187: Unknown symbol ieee80211_rts_duration (err -22) > > Do you have any suggestions? > Thank you > > Regards, > Eng. Hosam Hittini > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds_______________________________________________ > Rtl-wifi-devel mailing list > Rtl...@li... > https://lists.sourceforge.net/lists/listinfo/rtl-wifi-devel //Markus - The panama-hat hacker |
|
From: Hosam H. <h.h...@gm...> - 2014-07-17 11:12:26
|
Hello there, I have Ubuntu 13.10 Server running 3.11 kernel, I also have two USB Wireless adapters as follows: Adapter 1: Realtek RTL8187B chipset https://www.thinkpenguin.com/gnu-lin...-g-usb-adapter Adapter 2: AR7010+AR9280 chipsets https://www.thinkpenguin.com/gnu-lin...nux-tpe-nusbdb They claim that they work out of the box and they did, however, Adapter 2 had some limitations on frequency use So, I recompiled backports 3.15 source files after doing some manipulations to get a more opened driver, these manipulations were only for Atheros drivers Now, Adapter 1 stopped working, I tested the same adapter on another computer and it works fine The adapter doesn't even show up in lshw -C network I looked at the module in /lib/modules and the module is still there, apparently it wasn't modified recently Kindly look at the following codes hosam@Robin-05:~$ sudo modprobe rtl8187 ERROR: could not insert 'rtl8187': Invalid argument hosam@Robin-05:~$ sudo insmod /lib/modules/3.11.0-12-generic/kernel/drivers/net/wireless/rtl818x/rtl8187/rtl8187.ko Error: could not insert module /lib/modules/3.11.0-12-generic/kernel/drivers/net/wireless/rtl818x/rtl8187/rtl8187.ko: Invalid parameters hosam@Robin-05:~$ dmesg | tail [ 3097.162711] rtl8187: disagrees about version of symbol wiphy_rfkill_start_polling [ 3097.162716] rtl8187: Unknown symbol wiphy_rfkill_start_polling (err -22) [ 3097.162739] rtl8187: disagrees about version of symbol ieee80211_unregister_hw [ 3097.162744] rtl8187: Unknown symbol ieee80211_unregister_hw (err -22) [ 3097.162757] rtl8187: disagrees about version of symbol ieee80211_beacon_get_tim [ 3097.162761] rtl8187: Unknown symbol ieee80211_beacon_get_tim (err -22) [ 3097.162800] rtl8187: disagrees about version of symbol ieee80211_rx_irqsafe [ 3097.162805] rtl8187: Unknown symbol ieee80211_rx_irqsafe (err -22) [ 3097.162828] rtl8187: disagrees about version of symbol ieee80211_rts_duration [ 3097.162833] rtl8187: Unknown symbol ieee80211_rts_duration (err -22) Do you have any suggestions? Thank you Regards, Eng. Hosam Hittini |
|
From: Marco <ne...@la...> - 2012-07-26 12:08:35
|
Hi, I own an Alfa AWUS036H network adapter using the rtl8187 driver on a Debian box. I plan to use it with hostap, which apparently requires master mode to be enabled in the driver. The page http://linuxwireless.org/en/users/Drivers/rtl8187 states: not working yet: AP/Master mode What means *yet*? Is it planned to add master mode support in the near future? Do you have other suggestions what I could do to get the driver to work together with hostap? Disclaimer: I am not an expert in those things. I set up the access point some years ago, then the network adapter started to function unreliably. I then replaced it with a different one (the abovementioned 036H) and didn't manage to get my setup running again. Best regards Marco |
|
From: <fal...@us...> - 2010-02-13 15:29:05
|
Radu Potop wrote: > Hi, > > I contacted the Linux kernel developers using the netdev mailing list ( > ne...@vg... ) and they are interested in applying ad-hoc and master > mode patches to the rtl8180 kernel driver. > I know that your driver, rtl-wifi, already has these patches. Would you be > willing to contribute/adapt them for the rtl8180 kernel driver? > The kernel driver is actually the old version of the Realtek driver, from which > rtl-wifi was forked, so it wouldn't be too hard to make them work. > This would be great since a lot of folks would like to use their hardware to > its full potential. > > Thank you, > Radu Potop > If you think anything I've done is useful, the Linux kernel is welcome to use it. Bruce |
|
From: Markus G. <nie...@ly...> - 2010-02-12 15:54:10
|
Surely... //Markus On 12 Feb 2010, at 16:44, Radu Potop wrote: > Hi, > > I contacted the Linux kernel developers using the netdev mailing > list ( > ne...@vg... ) and they are interested in applying ad-hoc > and master > mode patches to the rtl8180 kernel driver. > I know that your driver, rtl-wifi, already has these patches. Would > you be > willing to contribute/adapt them for the rtl8180 kernel driver? > The kernel driver is actually the old version of the Realtek driver, > from which > rtl-wifi was forked, so it wouldn't be too hard to make them work. > This would be great since a lot of folks would like to use their > hardware to > its full potential. > > Thank you, > Radu Potop > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as > DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Rtl-wifi-devel mailing list > Rtl...@li... > https://lists.sourceforge.net/lists/listinfo/rtl-wifi-devel |
|
From: Radu P. <wo...@gm...> - 2010-02-12 15:50:34
|
Hi, I contacted the Linux kernel developers using the netdev mailing list ( ne...@vg... ) and they are interested in applying ad-hoc and master mode patches to the rtl8180 kernel driver. I know that your driver, rtl-wifi, already has these patches. Would you be willing to contribute/adapt them for the rtl8180 kernel driver? The kernel driver is actually the old version of the Realtek driver, from which rtl-wifi was forked, so it wouldn't be too hard to make them work. This would be great since a lot of folks would like to use their hardware to its full potential. Thank you, Radu Potop |
|
From: Hin-Tak L. <hin...@ya...> - 2008-05-15 13:38:24
|
Johnny Cuervo wrote: <snipped> > It's functional, just a little glitchy. I've had people tell me WEP/WPA > breaks, and signal strength isn't reported. The on/off switch doesn't do > much of anything, either, but I don't know if that's the device's > problem or the rest of the system's. <snipped> > If I can help at all, let me know. There is a new mac80211-based driver available from Herton of Mandriva, and it needs a little change to get all functional, but it is working alright. all the stuff, patches and discussions are in the bug report. Would be useful if you have a go at it. >>> https://bugzilla.redhat.com/show_bug.cgi?id=432280 It is interesting to re-read what was written some weeks ago; yes, my motivation for making the new driver work was that WEP causes kernel-oops - and I have also observed that the on/off switch does nothing (unlike how it is under Vista). I have not tried encryption with the new driver yet, but it is likely to be cleaner and probably would "just work". (I believe the old driver breaks because of crypto changes in the kernel). Also the new driver is quite happy to be unloaded (modprobe -r'ed) so one can change/mod within limits and just overwrite the old module and do depmod -a and reload again. The old driver is quite buggy in that it sometimes(often?) locks up on unload. |
|
From: Hin-Tak L. <hin...@ya...> - 2008-03-26 18:12:05
|
I just checked Johnny Cuervo's web site on the 2.6.24 change he received - it is actually
somewhat different from my 2.6.24-related diff I made - I used sg_init_one() rather than
sg_set_page(). Well, I haven't had any 2.6.24 crashes yet (I am using wireless while
writing this). Maybe you can have my diff for reference also. This is to be applied
*in addition* to the earlier vender-id/product-id related change.
Can I make a suggestion: I prefer having the changes as diff's - rather than downloading
a whole modified tarball, and a diff file isn't too much so maybe Johnny can try to provide both?
___________________________________________________________
Rise to the challenge for Sport Relief with Yahoo! For Good
http://uk.promotions.yahoo.com/forgood/ |
|
From: Hin-Tak L. <hin...@ya...> - 2008-03-25 15:25:36
|
> On Tue, Mar 25, 2008 at 01:19:22PM +0100, Andrea Merello
> wrote:
> Can someone please summarize me what is going on
> there?
> I had no time to follow things in driver development
> since quite a bit of time..
> Is this to add support for rtl8187B?
Don't worry, It is all in good hands... I attached Johnny Cuervo's mod's
and and some of my enhancements to a redhat bug report (a dkms config file
to rebuild the kernel module automatically for a new redhat kernel release
in the next reboot, and also a 2.6.23<->2.6.24 patch I made recently) to a
redhat bug report.
The redhat people said they don't have to incoporate my ideas but choose
to enhance the in-kernel realtek driver; so eventually that's going to happen, I believe; meanwhile, I am using my own mod with dkms (dynamic
kernel module support) on my satellite A210 until I get an official redhat kernel update.
__________________________________________________________
Sent from Yahoo! Mail.
More Ways to Keep in Touch. http://uk.docs.yahoo.com/nowyoucan.html
|
|
From: Andrea M. <and...@ti...> - 2008-03-25 12:19:26
|
Can someone please summarize me what is going on there? I had no time to follow things in driver development since quite a bit of time.. Is this to add support for rtl8187B? Even if I had no time to study well the chip, it seems it is quite different from the rtl8187L (some registers changed offset, a lot of new, undocumented registers appared, radio programming seems also very different, as well as the RTX mechanism). I wish to write a new driver for those device, but I have no time no. furthermore someone told me that some card with Rtl8187B has PCI id like rtl8187L. I wonder if there are two different rtl8187B chip version. I can ask to Realtek eventually, however I was waiting to have a free time slot to evaluate things more carefully.. Also I have some pending patches to prepare for rtl8180 code but I have had no time yet to prepare them Andrea On Mon, Mar 24, 2008 at 2:57 PM, Hin-Tak Leung <hin...@ya...> wrote: > Hi, I thought I should mention that there were some 2.6.23<->26.24 > breakage and I have attached the change to the redhat bug report > I filed earlier - the redhat folks wanted to enhance the in-kernel > realtek driver rather than talking this is directly, but they are > not ready yet, so I have an interrim patch for for the driver to > make it work in kernel 2.6.24: > > https://bugzilla.redhat.com/show_bug.cgi?id=432280 > > --- On Sun, 10/2/08, Hin-Tak Leung <hin...@ya...> wrote: > > > From: Hin-Tak Leung <hin...@ya...> > > Subject: Realtek rtl8187B wireless chip support for linux > > To: wl...@re... > > Cc: rtl...@li..., cu...@ze..., and...@ti..., fla...@so... > > Date: Sunday, 10 February, 2008, 8:59 PM > > One question: why is the official driver for 8187B not > > available for download? > > I have got it off a 3rd-party site: > > http://www.datanorth.net/~cuervo/rtl8187b/ > > > > I have reworked the modification made by Johnny Cuervo > > (attached as > > rtl8187-modified-diff) with a more useful kernel debug > > message and some > > comments about why the drop through to default doesn't > > work > > (rtl8187B_linux_24...diff), and I am currently using the > > mod right now > > on the 8187B chip which has a product id 0x8197. > > > > I hope this change get more widely and officially > > adopted... > > > > > > > > > > ___________________________________________________________ > > Yahoo! Answers - Got a question? Someone out there knows > > the answer. Try it > > now. > > http://uk.answers.yahoo.com/diff -ruBb > > old/rtl8187B_linux_24.6.1024.0822.2007/rtl8187/r8187_core.c > > rtl8187B_linux_24.6.1024.0822.2007/rtl8187/r8187_core.c > > --- > > old/rtl8187B_linux_24.6.1024.0822.2007/rtl8187/r8187_core.c 2007-08-22 > > 08:54:58.000000000 +0100 > > +++ > > rtl8187B_linux_24.6.1024.0822.2007/rtl8187/r8187_core.c 2008-02-10 > > 03:25:46.000000000 +0000 > > @@ -93,6 +93,7 @@ > > static struct usb_device_id rtl8187_usb_id_tbl[] = { > > {USB_DEVICE(USB_VENDOR_ID_REALTEK, 0x8187)}, > > {USB_DEVICE(USB_VENDOR_ID_REALTEK, 0x8189)}, > > + {USB_DEVICE(USB_VENDOR_ID_REALTEK, 0x8197)}, > > // {USB_DEVICE_VER(USB_VENDOR_ID_REALTEK, > > 0x8187,0x0200,0x0200)}, > > {USB_DEVICE(USB_VENDOR_ID_NETGEAR, 0x6100)}, > > {USB_DEVICE(USB_VENDOR_ID_NETGEAR, 0x6a00)}, > > @@ -2833,6 +2834,11 @@ > > idProduct = le16_to_cpu(udev->descriptor.idProduct); > > > > switch (idProduct) { > > + case 0x8197: > > + /* priv->rf_chip = 6 for this chip, > > > EPROM_RFCHIPID_RTL8225U = 5 */ > > + /* rtl8225_is_V_z2(dev) return false, and drop through > > to default: does not work */ > > + /* drop through to 0x8189 */ > > + DMESG("Using configuration of Product id 0x8189 > > for newer 0x8197"); > > case 0x8189: > > /* check RF frontend chipset */ > > priv->card_8187 = NIC_8187B; > > > > __________________________________________________________ > Sent from Yahoo! Mail. > More Ways to Keep in Touch. http://uk.docs.yahoo.com/nowyoucan.html > |
|
From: Hin-Tak L. <hin...@ya...> - 2008-03-24 13:58:05
|
Hi, I thought I should mention that there were some 2.6.23<->26.24 breakage and I have attached the change to the redhat bug report I filed earlier - the redhat folks wanted to enhance the in-kernel realtek driver rather than talking this is directly, but they are not ready yet, so I have an interrim patch for for the driver to make it work in kernel 2.6.24: https://bugzilla.redhat.com/show_bug.cgi?id=432280 --- On Sun, 10/2/08, Hin-Tak Leung <hin...@ya...> wrote: > From: Hin-Tak Leung <hin...@ya...> > Subject: Realtek rtl8187B wireless chip support for linux > To: wl...@re... > Cc: rtl...@li..., cu...@ze..., and...@ti..., fla...@so... > Date: Sunday, 10 February, 2008, 8:59 PM > One question: why is the official driver for 8187B not > available for download? > I have got it off a 3rd-party site: > http://www.datanorth.net/~cuervo/rtl8187b/ > > I have reworked the modification made by Johnny Cuervo > (attached as > rtl8187-modified-diff) with a more useful kernel debug > message and some > comments about why the drop through to default doesn't > work > (rtl8187B_linux_24...diff), and I am currently using the > mod right now > on the 8187B chip which has a product id 0x8197. > > I hope this change get more widely and officially > adopted... > > > > > ___________________________________________________________ > Yahoo! Answers - Got a question? Someone out there knows > the answer. Try it > now. > http://uk.answers.yahoo.com/diff -ruBb > old/rtl8187B_linux_24.6.1024.0822.2007/rtl8187/r8187_core.c > rtl8187B_linux_24.6.1024.0822.2007/rtl8187/r8187_core.c > --- > old/rtl8187B_linux_24.6.1024.0822.2007/rtl8187/r8187_core.c 2007-08-22 > 08:54:58.000000000 +0100 > +++ > rtl8187B_linux_24.6.1024.0822.2007/rtl8187/r8187_core.c 2008-02-10 > 03:25:46.000000000 +0000 > @@ -93,6 +93,7 @@ > static struct usb_device_id rtl8187_usb_id_tbl[] = { > {USB_DEVICE(USB_VENDOR_ID_REALTEK, 0x8187)}, > {USB_DEVICE(USB_VENDOR_ID_REALTEK, 0x8189)}, > + {USB_DEVICE(USB_VENDOR_ID_REALTEK, 0x8197)}, > // {USB_DEVICE_VER(USB_VENDOR_ID_REALTEK, > 0x8187,0x0200,0x0200)}, > {USB_DEVICE(USB_VENDOR_ID_NETGEAR, 0x6100)}, > {USB_DEVICE(USB_VENDOR_ID_NETGEAR, 0x6a00)}, > @@ -2833,6 +2834,11 @@ > idProduct = le16_to_cpu(udev->descriptor.idProduct); > > switch (idProduct) { > + case 0x8197: > + /* priv->rf_chip = 6 for this chip, > > EPROM_RFCHIPID_RTL8225U = 5 */ > + /* rtl8225_is_V_z2(dev) return false, and drop through > to default: does not work */ > + /* drop through to 0x8189 */ > + DMESG("Using configuration of Product id 0x8189 > for newer 0x8197"); > case 0x8189: > /* check RF frontend chipset */ > priv->card_8187 = NIC_8187B; __________________________________________________________ Sent from Yahoo! Mail. More Ways to Keep in Touch. http://uk.docs.yahoo.com/nowyoucan.html |
|
From: Hin-Tak L. <hin...@ya...> - 2008-02-10 21:00:00
|
One question: why is the official driver for 8187B not available for download? I have got it off a 3rd-party site: http://www.datanorth.net/~cuervo/rtl8187b/ I have reworked the modification made by Johnny Cuervo (attached as rtl8187-modified-diff) with a more useful kernel debug message and some comments about why the drop through to default doesn't work (rtl8187B_linux_24...diff), and I am currently using the mod right now on the 8187B chip which has a product id 0x8197. I hope this change get more widely and officially adopted... ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ |
|
From: Festor <fes...@gm...> - 2007-07-25 06:03:18
|
> > I don't get the warning about ISO C90 not liking mixed declarations and > code. Checking the version of my C compiler gives > ~/rtl-wifi$ cc -v > Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.5/specs > Configured with: ../src/configure -v > --enable-languages=3Dc,c++,java,f77,pascal,objc,ada,treelang --prefix=3D/= usr > --mandir=3D/usr/share/man > --infodir=3D/usr/share/info--with-gxx-include-dir=3D/usr/include/c++/3.3 > --enable-shared --enable-__cxa_atexit --with-system-zlib --enable-nls > --without-included-gettext --enable-clocale=3Dgnu --enable-debug > --enable-java-gc=3Dboehm --enable-java-awt=3Dxlib --enable-objc-gci486-li= nux > Thread model: posix > gcc version 3.3.5 (Debian 1:3.3.5-13) festor@sniper-win:~$ cc -v Usando especificaciones internas. Objetivo: i486-linux-gnu Configurado con: ../src/configure -v --enable-languages=3Dc,c++,fortran,objc,obj-c++,treelang --prefix=3D/usr --enable-shared --with-system-zlib --libexecdir=3D/usr/lib --without-included-gettext --enable-threads=3Dposix --enable-nls --program-suffix=3D-4.1 --enable-__cxa_atexit --enable-clocale=3Dgnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=3Drelease i486-linux-gnu Modelo de hilos: posix gcc versi=F3n 4.1.2 (Ubuntu 4.1.2-0ubuntu4) I expect that you have a different version/configuration that causes you > to get the warning. I think you can ignore this warning as well. ok, but when I do this: insmod rtl818x-newstack/r8180.ko The system is blocked and I cannot work nor do nothing. Does not have anything to do with the errors of before? More info: https://sourceforge.net/forum/forum.php?thread_id=3D1784690&forum_id=3D6521= 49 Sorry for my bad English |
|
From: Bruce R. <bns...@ho...> - 2007-07-24 22:38:04
|
Festor wrote: > I use Ubuntu 7.04 with 2.6.18.8 <http://2.6.18.8> , 2.6.20, 2.6.21 > kernel vanilla and when I use "make" I get this: > > festor@sniper-win :~/rtl-wifi$ make > make -C /lib/modules/2.6.18.8-custom/build M=/home/festor/rtl-wifi modules > make[1]: se ingresa al directorio `/usr/src/linux-2.6.18.8 > <http://2.6.18.8>' > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_softmac.o > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_rx.o > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_tx.o > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_wx.o > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_module.o > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_softmac_wx.o > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt.o > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_ccmp.o > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_tkip.o > CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_wep.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211- rtl.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt-rtl.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_wep- rtl.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_tkip-rtl.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_ccmp- rtl.o > CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8187_core.o > CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8180_93cx6.o > CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8180_wx.o > CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8180_rtl8225.o > CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8180_rtl8225z2.o > LD [M] /home/festor/rtl-wifi/rtl8187-newstack/r8187.o > CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_core.o > CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_sa2400.o > CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_93cx6.o > CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_wx.o > /home/festor/rtl-wifi/rtl818x-newstack/r8180_wx.c:469: aviso: se definió > 'r8180_wx_set_monitor_type' pero no se usa > CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_max2820.o > CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_gct.o > CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8225.o > CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.o > /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.c: En la función > 'rtl8255_rf_init': > /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.c:1710: aviso: ISO > C90 prohíbe las declaraciones mezcladas y código > LD [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180.o > Building modules, stage 2. > MODPOST > CC /home/festor/rtl-wifi/ieee80211/ieee80211-rtl.mod.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211- rtl.ko > CC /home/festor/rtl-wifi/ieee80211/ieee80211_crypt-rtl.mod.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt- rtl.ko > CC /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_ccmp-rtl.mod.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_ccmp-rtl.ko > CC /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_tkip-rtl.mod.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_tkip-rtl.ko > CC /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_wep- rtl.mod.o > LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_wep-rtl.ko > CC /home/festor/rtl-wifi/rtl8187-newstack/r8187.mod.o > LD [M] /home/festor/rtl-wifi/rtl8187-newstack/r8187.ko > CC /home/festor/rtl-wifi/rtl818x-newstack/r8180.mod.o > LD [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180.ko > make[1]: se sale del directorio `/usr/src/linux-2.6.18.8 <http://2.6.18.8>' > > In English: > > /home/festor/rtl-wifi/rtl818x-newstack/r8180_wx.c:469: warning: `was > defined r8180_wx_set_monitor_type' but it is not used > > /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.c: In the function > `rtl8255_rf_init': > /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.c:1710: warning: > ISO C90 prohibits the mixed declarations and code > Building modules, stage 2. > MODPOST > > Any ideas? > I'm running on Debian "Sarge" kernel 2.6.8-4-686 I do get the warning CC [M] /home/bruce/rtl-wifi/rtl818x-newstack/r8180_wx.o /home/bruce/rtl-wifi/rtl818x-newstack/r8180_wx.c:469: warning: `r8180_wx_set_monitor_type' defined but not used I've just been ignoring this warning. I don't get the warning about ISO C90 not liking mixed declarations and code. Checking the version of my C compiler gives ~/rtl-wifi$ cc -v Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.5/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --enable-__cxa_atexit --with-system-zlib --enable-nls --without-included-gettext --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gci486-linux Thread model: posix gcc version 3.3.5 (Debian 1:3.3.5-13) I expect that you have a different version/configuration that causes you to get the warning. I think you can ignore this warning as well. |
|
From: Festor <fes...@gm...> - 2007-07-24 14:30:07
|
I use Ubuntu 7.04 with 2.6.18.8 , 2.6.20, 2.6.21 kernel vanilla and when I use "make" I get this: festor@sniper-win:~/rtl-wifi$ make make -C /lib/modules/2.6.18.8-custom/build M=3D/home/festor/rtl-wifi module= s make[1]: se ingresa al directorio `/usr/src/linux-2.6.18.8' CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_softmac.o CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_rx.o CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_tx.o CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_wx.o CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_module.o CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_softmac_wx.o CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt.o CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_ccmp.o CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_tkip.o CC [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_wep.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211-rtl.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt-rtl.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_wep-rtl.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_tkip-rtl.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_ccmp-rtl.o CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8187_core.o CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8180_93cx6.o CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8180_wx.o CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8180_rtl8225.o CC [M] /home/festor/rtl-wifi/rtl8187-newstack/r8180_rtl8225z2.o LD [M] /home/festor/rtl-wifi/rtl8187-newstack/r8187.o CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_core.o CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_sa2400.o CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_93cx6.o CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_wx.o /home/festor/rtl-wifi/rtl818x-newstack/r8180_wx.c:469: aviso: se defini=F3 'r8180_wx_set_monitor_type' pero no se usa CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_max2820.o CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_gct.o CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8225.o CC [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.o /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.c: En la funci=F3n 'rtl8255_rf_init': /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.c:1710: aviso: ISO C90 proh=EDbe las declaraciones mezcladas y c=F3digo LD [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180.o Building modules, stage 2. MODPOST CC /home/festor/rtl-wifi/ieee80211/ieee80211-rtl.mod.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211-rtl.ko CC /home/festor/rtl-wifi/ieee80211/ieee80211_crypt-rtl.mod.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt-rtl.ko CC /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_ccmp-rtl.mod.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_ccmp-rtl.ko CC /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_tkip-rtl.mod.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_tkip-rtl.ko CC /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_wep-rtl.mod.o LD [M] /home/festor/rtl-wifi/ieee80211/ieee80211_crypt_wep-rtl.ko CC /home/festor/rtl-wifi/rtl8187-newstack/r8187.mod.o LD [M] /home/festor/rtl-wifi/rtl8187-newstack/r8187.ko CC /home/festor/rtl-wifi/rtl818x-newstack/r8180.mod.o LD [M] /home/festor/rtl-wifi/rtl818x-newstack/r8180.ko make[1]: se sale del directorio `/usr/src/linux-2.6.18.8' In English: /home/festor/rtl-wifi/rtl818x-newstack/r8180_wx.c:469: warning: `was define= d r8180_wx_set_monitor_type' but it is not used /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.c: In the function `rtl8255_rf_init': /home/festor/rtl-wifi/rtl818x-newstack/r8180_rtl8255.c:1710: warning: ISO C90 prohibits the mixed declarations and code Building modules, stage 2. MODPOST Any ideas? |
|
From: <fal...@us...> - 2007-02-27 17:45:01
|
I believe that some of the changes that were made at revisions 31 and 36 should not have been made. I've made a patch to reverse the changes and started a thread about this patch on the rtl-wifi forum https://sourceforge.net/forum/forum.php?thread_id=1682823&forum_id=652149 Please look at my changes and comment in the forum about them. TIA |
