* help
@ 2011-07-28 23:33 Martin Partridge
2011-07-28 23:47 ` help Christian Lamparter
2011-07-29 3:12 ` help Pavel Roskin
0 siblings, 2 replies; 8+ messages in thread
From: Martin Partridge @ 2011-07-28 23:33 UTC (permalink / raw)
To: linux-wireless
Hello,
I don't understand the last 2 steps, i'm running fedora (ok i lie its
Fuduntu, but to all intents and purposes its fedora) Kernel version:
2.6.39.3-1.fc14.i686
i'm using a WG511v2 PCMCIA card, i've downloaded the correct firmware,
renamed it and modprobed everything as instructed, the bit i'm having
trouble with is this bit:
Enabling p54
To enable p54, you must first enable mac80211:
Networking Support --->
Wireless --->
<M> cfg80211 - wireless configuration API
<M> Generic IEEE 802.11 Networking Stack (mac80211)
You can then enable p54 in the kernel configuration under
Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Wireless LAN (IEEE 802.11)
<M> Softmac Prism54 support
<M> Prism54 USB support
<M> Prism54 PCI support
<M> Prism54 SPI (stlc45xx) support
where do i type this, or what does it mean? I i don't have a 'networking
support' menu and it's not a program, where do i find this? is it a conf
file? I'm no stranger to linux but this is perplexing, the card works fine
on windows, but i can't get it work now. I have a kernel config file in
/etc/sysconfig but its a bit bare, as shown below:
# UPDATEDEFAULT specifies if new-kernel-pkg should make
# new kernels the default
UPDATEDEFAULT=yes
# DEFAULTKERNEL specifies the default kernel package type
DEFAULTKERNEL=kernel
That's the whole thing.
How do i enable p54 and mac80211, i'm not sure and its bloody annoying.
regards
Martin Partridge
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: help
2011-07-28 23:33 help Martin Partridge
@ 2011-07-28 23:47 ` Christian Lamparter
[not found] ` <op.vzexmjbnhgplxr@melanie>
2011-07-29 3:12 ` help Pavel Roskin
1 sibling, 1 reply; 8+ messages in thread
From: Christian Lamparter @ 2011-07-28 23:47 UTC (permalink / raw)
To: Martin Partridge; +Cc: linux-wireless
On Friday, July 29, 2011 01:33:13 AM Martin Partridge wrote:
> I don't understand the last 2 steps, i'm running fedora (ok i lie its
> Fuduntu, but to all intents and purposes its fedora) Kernel version:
> 2.6.39.3-1.fc14.i686
recent enough.
> i'm using a WG511v2 PCMCIA card, i've downloaded the correct firmware,
> renamed it and modprobed everything as instructed, the bit i'm having
> trouble with is this bit:
>
> Enabling p54
>
> To enable p54, you must first enable mac80211:
>
> Networking Support --->
> Wireless --->
> <M> cfg80211 - wireless configuration API
> <M> Generic IEEE 802.11 Networking Stack (mac80211)
>
> You can then enable p54 in the kernel configuration under
>
> Device Drivers --->
> [*] Network device support --->
> Wireless LAN --->
> [*] Wireless LAN (IEEE 802.11)
> <M> Softmac Prism54 support
> <M> Prism54 USB support
> <M> Prism54 PCI support
> <M> Prism54 SPI (stlc45xx) support
>
> where do i type this, or what does it mean? I i don't have a 'networking
> support' menu and it's not a program, where do i find this? is it a conf
> file? I'm no stranger to linux but this is perplexing, the card works fine
> on windows, but i can't get it work now. I have a kernel config file in
> /etc/sysconfig but its a bit bare, as shown below:
>
> # UPDATEDEFAULT specifies if new-kernel-pkg should make
> # new kernels the default
> UPDATEDEFAULT=yes
>
> # DEFAULTKERNEL specifies the default kernel package type
> DEFAULTKERNEL=kernel
>
> That's the whole thing.
>
> How do i enable p54 and mac80211, i'm not sure and its bloody annoying.
Ah you see, you don't need to do that. This step is only necessary if you
make your own kernel [from scratch] and you haven't enabled p54 yet. But
since your using fedora's default 2.6.39.3-1.fc14.i686 kernel, I hope they
have taken care of it and provided you with a fitting p54common and p54pci
modules.
In fact, the device should show up right away soon as you insert the pcmcia
card into the slot. Check networkmanager/wicd/ifconfig -a/iw list for any
new devices. If it doesn't show up, you might want to post your `dmesg`,
[releavant p54 extract] syslog right here. I also have a WG511v2 so it should
work pretty much out of the box.
Regards,
Chr
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: help
2011-07-28 23:33 help Martin Partridge
2011-07-28 23:47 ` help Christian Lamparter
@ 2011-07-29 3:12 ` Pavel Roskin
2011-07-29 16:32 ` help Pavel Roskin
1 sibling, 1 reply; 8+ messages in thread
From: Pavel Roskin @ 2011-07-29 3:12 UTC (permalink / raw)
To: Martin Partridge; +Cc: linux-wireless
Hello!
Please use meaningful subjects for the list posts.
On 07/28/2011 07:33 PM, Martin Partridge wrote:
>
> I don't understand the last 2 steps, i'm running fedora (ok i lie its
> Fuduntu, but to all intents and purposes its fedora) Kernel version:
> 2.6.39.3-1.fc14.i686
Please always give information about the location of the documentation
if you have any problems with it.
> Enabling p54
>
> To enable p54, you must first enable mac80211:
I used Google and found this text on the linux-wireless wiki:
http://linuxwireless.org/en/users/Drivers/p54
I rephrased the text to make it more clear that it only applied to
configuring the kernel.
Since you are using a precompiled kernel, you don't have that option.
> I have a kernel config
> file in /etc/sysconfig but its a bit bare, as shown below:
That's something totally different. The wiki talks about compile-time
configuration.
> How do i enable p54 and mac80211, i'm not sure and its bloody annoying.
You only need to check if the modules are present in the kernel you are
using. You can do that by running "modprobe p54".
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: help
2011-07-29 3:12 ` help Pavel Roskin
@ 2011-07-29 16:32 ` Pavel Roskin
0 siblings, 0 replies; 8+ messages in thread
From: Pavel Roskin @ 2011-07-29 16:32 UTC (permalink / raw)
To: Martin Partridge; +Cc: linux-wireless
On 07/28/2011 11:12 PM, Pavel Roskin wrote:
> You only need to check if the modules are present in the kernel you are
> using. You can do that by running "modprobe p54".
Sorry, it should be "modproble p54pci" for PCI cards and "modprobe
p54usb" for USB devices. I checked Fuduntu, and it has both drivers.
It doesn't have the firmware, but I guess you have no problems with that
part of the instructions.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: help with wg511v2
[not found] ` <op.vzexmjbnhgplxr@melanie>
@ 2011-07-30 11:12 ` Christian Lamparter
2011-08-01 21:10 ` Pavel Roskin
0 siblings, 1 reply; 8+ messages in thread
From: Christian Lamparter @ 2011-07-30 11:12 UTC (permalink / raw)
To: Martin Partridge; +Cc: linux-wireless
On Saturday 30 July 2011 05:36:09 Martin Partridge wrote:
> I've checked everything and the WG511v2 is still not lighting up and it
> isn't showing as a network card, it is detected when plugged in:
>
> [13523.594828] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0
> [13524.917077] pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
> [13524.917132] pci 0000:02:00.0: [11ab:1faa] type 0 class 0x000200
> [13524.917176] pci 0000:02:00.0: reg 10: [mem 0xd0000000-0xd000ffff]
> [13524.917200] pci 0000:02:00.0: reg 14: [mem 0xc0000000-0xc000ffff]
>...
> and when the output from lspci is:
>
> 00:09.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro
> 100 (rev 09)
> 00:09.1 Serial controller: Agere Systems LT WinModem
> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
^^^^^^^
Ah, this explains it everything. You are unfortunately a victim of Netgear's stupid
naming scam. The situation is explained at http://daemonizer.de/prism54/wg511/
The upshot is: there are two WG511 v2 versions, but only the first v2 works with
p54. The second one needs a driver from marvell.
Regards,
Chr
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: help with wg511v2
2011-07-30 11:12 ` help with wg511v2 Christian Lamparter
@ 2011-08-01 21:10 ` Pavel Roskin
0 siblings, 0 replies; 8+ messages in thread
From: Pavel Roskin @ 2011-08-01 21:10 UTC (permalink / raw)
To: Christian Lamparter; +Cc: Martin Partridge, linux-wireless
On 07/30/2011 07:12 AM, Christian Lamparter wrote:
> On Saturday 30 July 2011 05:36:09 Martin Partridge wrote:
>> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
> ^^^^^^^
>
> Ah, this explains it everything. You are unfortunately a victim of Netgear's stupid
> naming scam. The situation is explained at http://daemonizer.de/prism54/wg511/
> The upshot is: there are two WG511 v2 versions, but only the first v2 works with
> p54. The second one needs a driver from marvell.
The driver is called mrv8k, but it's not in the Linux tree, not even in
staging. I don't know why. Perhaps it's not functional.
Several pages recommend disabling mrv8k and using ndiswrapper with
Windows drivers. Until ndiswrapper 1.57 is released, you'll need the
current snapshot from subversion, as ndiswrapper 1.56 doesn't compile
for Linux 2.6.35 and newer.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 8+ messages in thread
* help
@ 2014-12-04 19:01 m_del_buon
2014-12-04 19:19 ` help Arend van Spriel
0 siblings, 1 reply; 8+ messages in thread
From: m_del_buon @ 2014-12-04 19:01 UTC (permalink / raw)
To: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 4160 bytes --]
can you help me with this problems? thx
Sent from Libero Mobile
________________________________
Il 04/12/2014, m_del_buon@libero.it ha scritto:
hi I am an italian user of one realtek based device Bus 001 Device 005: ID 0df6:004b Sitecom Europe B.V. WL-349v3 Wireless Micro Adapter 150N X1 [Realtek RTL8192SU] on an ubuntu 14.04 64bit 3.13.0-40-generic kernel and I received following error
make
make -C /lib/modules/3.13.0-40-generic/build M=/home/hp/rtl8192su-master/rtlwifi CONFIG_RTL_CARDS=y CONFIG_RTLWIFI=m CONFIG_RTLWIFI_DEBUG=y CONFIG_RTLWIFI_DEBUGFS=y CONFIG_RTLWIFI_USB=m CONFIG_RTLWIFI_PCI=m CONFIG_RTL8192SU=m CONFIG_RTL8192SE=m CONFIG_RTL8192S_COMMON=m CONFIG_RTL8192CU=n CONFIG_RTL8192DE=n CONFIG_RTL8192CE=n CONFIG_RTL8192C_COMMON=n CONFIG_RTL8723AE=n CONFIG_RTL8188EE=n EXTRA_CFLAGS="-DDEBUG -DCONFIG_RTLWIFI_DEBUGFS=m -w"
make[1]: ingresso nella directory "/usr/src/linux-headers-3.13.0-40-generic"
CC [M] /home/hp/rtl8192su-master/rtlwifi/regd.o
In file included from include/net/cfg80211.h:23:0,
from include/net/mac80211.h:21,
from /home/hp/rtl8192su-master/rtlwifi/wifi.h:41,
from /home/hp/rtl8192su-master/rtlwifi/regd.c:30:
/home/hp/rtl8192su-master/rtlwifi/regd.c:62:4: error: ‘NL80211_RRF_NO_IR’ undeclared here (not in a function)
NL80211_RRF_NO_IR)
^
include/net/regulatory.h:128:11: note: in definition of macro ‘REG_RULE’
.flags = reg_flags, \
^
/home/hp/rtl8192su-master/rtlwifi/regd.c:99:6: note: in expansion of macro ‘RTL819x_2GHZ_CH12_13’
RTL819x_2GHZ_CH12_13,
^
/home/hp/rtl8192su-master/rtlwifi/regd.c: In function ‘_rtl_reg_apply_beaconing_flags’:
/home/hp/rtl8192su-master/rtlwifi/regd.c:186:20: error: ‘IEEE80211_CHAN_NO_IR’ undeclared (first use in this function)
ch->flags &= ~IEEE80211_CHAN_NO_IR;
^
/home/hp/rtl8192su-master/rtlwifi/regd.c:186:20: note: each undeclared identifier is reported only once for each function it appears in
/home/hp/rtl8192su-master/rtlwifi/regd.c: In function ‘_rtl_reg_apply_active_scan_flags’:
/home/hp/rtl8192su-master/rtlwifi/regd.c:214:19: error: ‘IEEE80211_CHAN_NO_IR’ undeclared (first use in this function)
if (ch->flags & IEEE80211_CHAN_NO_IR)
^
/home/hp/rtl8192su-master/rtlwifi/regd.c: In function ‘_rtl_reg_apply_radar_flags’:
/home/hp/rtl8192su-master/rtlwifi/regd.c:279:10: error: ‘IEEE80211_CHAN_NO_IR’ undeclared (first use in this function)
IEEE80211_CHAN_NO_IR;
^
/home/hp/rtl8192su-master/rtlwifi/regd.c: In function ‘_rtl_regd_init_wiphy’:
/home/hp/rtl8192su-master/rtlwifi/regd.c:348:7: error: ‘struct wiphy’ has no member named ‘regulatory_flags’
wiphy->regulatory_flags |= REGULATORY_CUSTOM_REG;
^
/home/hp/rtl8192su-master/rtlwifi/regd.c:348:29: error: ‘REGULATORY_CUSTOM_REG’ undeclared (first use in this function)
wiphy->regulatory_flags |= REGULATORY_CUSTOM_REG;
^
/home/hp/rtl8192su-master/rtlwifi/regd.c:349:7: error: ‘struct wiphy’ has no member named ‘regulatory_flags’
wiphy->regulatory_flags &= ~REGULATORY_STRICT_REG;
^
/home/hp/rtl8192su-master/rtlwifi/regd.c:349:30: error: ‘REGULATORY_STRICT_REG’ undeclared (first use in this function)
wiphy->regulatory_flags &= ~REGULATORY_STRICT_REG;
^
/home/hp/rtl8192su-master/rtlwifi/regd.c:350:7: error: ‘struct wiphy’ has no member named ‘regulatory_flags’
wiphy->regulatory_flags &= ~REGULATORY_DISABLE_BEACON_HINTS;
^
/home/hp/rtl8192su-master/rtlwifi/regd.c:350:30: error: ‘REGULATORY_DISABLE_BEACON_HINTS’ undeclared (first use in this function)
wiphy->regulatory_flags &= ~REGULATORY_DISABLE_BEACON_HINTS;
^
make[2]: *** [/home/hp/rtl8192su-master/rtlwifi/regd.o] Errore 1
make[1]: *** [_module_/home/hp/rtl8192su-master/rtlwifi] Errore 2
make[1]: uscita dalla directory "/usr/src/linux-headers-3.13.0-40-generic"
make: *** [all] Errore 2
can you help me?
Sent from Libero Mobile
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: help
2014-12-04 19:01 help m_del_buon
@ 2014-12-04 19:19 ` Arend van Spriel
0 siblings, 0 replies; 8+ messages in thread
From: Arend van Spriel @ 2014-12-04 19:19 UTC (permalink / raw)
To: m_del_buon; +Cc: linux-wireless
On 12/04/14 20:01, m_del_buon@libero.it wrote:
> can you help me with this problems? thx
Suspect that you are building newer kernel driver code against an older
kernel. How did you populate /home/hp/rtl8192su-master/rtlwifi?
Regards,
Arend
> Sent from Libero Mobile
> ________________________________
>
> Il 04/12/2014, m_del_buon@libero.it ha scritto:
>
> hi I am an italian user of one realtek based device Bus 001 Device 005: ID 0df6:004b Sitecom Europe B.V. WL-349v3 Wireless Micro Adapter 150N X1 [Realtek RTL8192SU] on an ubuntu 14.04 64bit 3.13.0-40-generic kernel and I received following error
> make
> make -C /lib/modules/3.13.0-40-generic/build M=/home/hp/rtl8192su-master/rtlwifi CONFIG_RTL_CARDS=y CONFIG_RTLWIFI=m CONFIG_RTLWIFI_DEBUG=y CONFIG_RTLWIFI_DEBUGFS=y CONFIG_RTLWIFI_USB=m CONFIG_RTLWIFI_PCI=m CONFIG_RTL8192SU=m CONFIG_RTL8192SE=m CONFIG_RTL8192S_COMMON=m CONFIG_RTL8192CU=n CONFIG_RTL8192DE=n CONFIG_RTL8192CE=n CONFIG_RTL8192C_COMMON=n CONFIG_RTL8723AE=n CONFIG_RTL8188EE=n EXTRA_CFLAGS="-DDEBUG -DCONFIG_RTLWIFI_DEBUGFS=m -w"
> make[1]: ingresso nella directory "/usr/src/linux-headers-3.13.0-40-generic"
> CC [M] /home/hp/rtl8192su-master/rtlwifi/regd.o
> In file included from include/net/cfg80211.h:23:0,
> from include/net/mac80211.h:21,
> from /home/hp/rtl8192su-master/rtlwifi/wifi.h:41,
> from /home/hp/rtl8192su-master/rtlwifi/regd.c:30:
> /home/hp/rtl8192su-master/rtlwifi/regd.c:62:4: error: ‘NL80211_RRF_NO_IR’ undeclared here (not in a function)
> NL80211_RRF_NO_IR)
> ^
> include/net/regulatory.h:128:11: note: in definition of macro ‘REG_RULE’
> .flags = reg_flags, \
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c:99:6: note: in expansion of macro ‘RTL819x_2GHZ_CH12_13’
> RTL819x_2GHZ_CH12_13,
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c: In function ‘_rtl_reg_apply_beaconing_flags’:
> /home/hp/rtl8192su-master/rtlwifi/regd.c:186:20: error: ‘IEEE80211_CHAN_NO_IR’ undeclared (first use in this function)
> ch->flags&= ~IEEE80211_CHAN_NO_IR;
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c:186:20: note: each undeclared identifier is reported only once for each function it appears in
> /home/hp/rtl8192su-master/rtlwifi/regd.c: In function ‘_rtl_reg_apply_active_scan_flags’:
> /home/hp/rtl8192su-master/rtlwifi/regd.c:214:19: error: ‘IEEE80211_CHAN_NO_IR’ undeclared (first use in this function)
> if (ch->flags& IEEE80211_CHAN_NO_IR)
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c: In function ‘_rtl_reg_apply_radar_flags’:
> /home/hp/rtl8192su-master/rtlwifi/regd.c:279:10: error: ‘IEEE80211_CHAN_NO_IR’ undeclared (first use in this function)
> IEEE80211_CHAN_NO_IR;
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c: In function ‘_rtl_regd_init_wiphy’:
> /home/hp/rtl8192su-master/rtlwifi/regd.c:348:7: error: ‘struct wiphy’ has no member named ‘regulatory_flags’
> wiphy->regulatory_flags |= REGULATORY_CUSTOM_REG;
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c:348:29: error: ‘REGULATORY_CUSTOM_REG’ undeclared (first use in this function)
> wiphy->regulatory_flags |= REGULATORY_CUSTOM_REG;
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c:349:7: error: ‘struct wiphy’ has no member named ‘regulatory_flags’
> wiphy->regulatory_flags&= ~REGULATORY_STRICT_REG;
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c:349:30: error: ‘REGULATORY_STRICT_REG’ undeclared (first use in this function)
> wiphy->regulatory_flags&= ~REGULATORY_STRICT_REG;
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c:350:7: error: ‘struct wiphy’ has no member named ‘regulatory_flags’
> wiphy->regulatory_flags&= ~REGULATORY_DISABLE_BEACON_HINTS;
> ^
> /home/hp/rtl8192su-master/rtlwifi/regd.c:350:30: error: ‘REGULATORY_DISABLE_BEACON_HINTS’ undeclared (first use in this function)
> wiphy->regulatory_flags&= ~REGULATORY_DISABLE_BEACON_HINTS;
> ^
> make[2]: *** [/home/hp/rtl8192su-master/rtlwifi/regd.o] Errore 1
> make[1]: *** [_module_/home/hp/rtl8192su-master/rtlwifi] Errore 2
> make[1]: uscita dalla directory "/usr/src/linux-headers-3.13.0-40-generic"
> make: *** [all] Errore 2
> can you help me?
>
> Sent from Libero Mobile
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2014-12-04 19:20 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-28 23:33 help Martin Partridge
2011-07-28 23:47 ` help Christian Lamparter
[not found] ` <op.vzexmjbnhgplxr@melanie>
2011-07-30 11:12 ` help with wg511v2 Christian Lamparter
2011-08-01 21:10 ` Pavel Roskin
2011-07-29 3:12 ` help Pavel Roskin
2011-07-29 16:32 ` help Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2014-12-04 19:01 help m_del_buon
2014-12-04 19:19 ` help Arend van Spriel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).