IS there any wlan RTL 8187B support in OpenSuse. My YAst canoot detect it and I cannot get it working.
Please advise.
veki
veki wrote:
> IS there any wlan RTL 8187B support in OpenSuse. My YAst canoot detect
> it and I cannot get it working.
The RTL8187 driver in the kernel does not work for an 8187B - thus it
will not work. There is a small group of us that have a working
driver, and are working to get it incorporated into the kernel, but it
will not be ready until 2.6…28, or so.
If you are willing to build your own kernel, I can get you the
necessary patches. You can send a PM to lwfinger.
Larry
does the RTL 8187B driver provided by Realtek work in Open SUSE 10.3 and 11 versions.
they had sent me the driver ny mail.
vspunn wrote:
> does the RTL 8187B driver provided by Realtek work in Open SUSE 10.3 and
> 11 versions.
> they had sent me the driver ny mail.
The Realtek drivers that I know about for the RTL8187B use
ieee80211_softmac for the MAC layer. That should work for 10.3 with a
2.6.22 kernel, but it will not for 11.0 with a 2.6.25 kernel.
There is a patch for 8187B devices using mac80211 (the new MAC code),
but it is not yet in any distributed kernel.
Larry
Can you pls send me the patches to Ptero.4@gmail.com. I’m getting Sabayon (kernel 2.6.25) and wanna get my rtl8187b wifi going on it.
Can somone write instructions how to apply patch on kernel 2.6.25 in OpenSuse 11.0.
Thanks in advance,
Vedran
I would love to keep this post alive. I am pretty new to linux but not to compiling. I would like to get the patches and I will teach myself the “art” of compiling a custom kernel. I have OpenSuse running on a VM at work and spare laptop at home so borking my system is not an issue. 
Could you also send me the patches?
Thanks!
jorge lopez74 wrote:
> I would love to keep this post alive. I am pretty new to linux but not
> to compiling. I would like to get the patches and I will teach myself
> the “art” of compiling a custom kernel. I have OpenSuse running on a
> VM at work and spare laptop at home so borking my system is not an
> issue.
>
> Could you also send me the patches?
PM me with your E-mail address.
Larry
:\
being new to Linux there is much jargon in these posts that goes straight over my head!! however the jist of it is a Realtek RTL8187B wireless card (which I seem to have built into my laptop) will not work with OpenSuse 11 (I got my distro recently from Linux Format mag) - yes???
I have been through the very helpful ‘sticky’ on wireless connection problems, and this is what I end up with
/usr/sbin/iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
and
sudo /usr/sbin/iwlist scan
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
so I conclude the only way to get my wireless working is to use a different Linux distro - can anyone suggest a good one?
banjomaniac wrote:
> :
>
> being new to Linux there is much jargon in these posts that goes
> straight over my head!! however the jist of it is a Realtek RTL8187B
> wireless card (which I seem to have built into my laptop) will not work
> with OpenSuse 11 (I got my distro recently from Linux Format mag) -
> yes???
>
> I have been through the very helpful ‘sticky’ on wireless connection
> problems, and this is what I end up with
>
>> /usr/sbin/iwconfig
>>
>> lo no wireless extensions.
>>
>> eth0 no wireless extensions.
>>
>
> and
>> sudo /usr/sbin/iwlist scan
>>
>> lo Interface doesn’t support scanning.
>>
>> eth0 Interface doesn’t support scanning.
>
>
> so I conclude the only way to get my wireless working is to use a
> different Linux distro - can anyone suggest a good one?
No distro will help you. Support for the RTL8187B will not be in any
mainline kernel until 2.6.27, which is now in testing. If you download
the kernel sources for 2.6.27-rc3 from kernel.org and build your own,
it will work for you.
Larry
:?
its not a question of giving up, its a question of getting to grips with what to do
I need help (ie simple step by step instructions) on how to build my own kernel (!) or use ndiswrapper (!!)
if anyone can guide me, at my beginner’s level of understanding and experience, through how to get around problems like getting the wireless to work, I would be very grateful and at the end of it become a little more experienced in using Linux
being a layman to LINUX, i donot understand this kernel. The main reson for sitching to LINUX is that windows gets too may spyware and virus, which I beleive are rare in LINUX.
By when will this kernel (under development) be out and how will we know about it.
I have downlaoded 10.3 . Which kernel is there in it. And is there any layman way to setup RTL 8187B Wireless or should I use wired lan till the driver is developed.
banjomaniac wrote:
> :?
>
> its not a question of giving up, its a question of getting to grips
> with what to do
>
> I need help (ie simple step by step instructions) on how to build my
> own kernel (!) or use ndiswrapper (!!)
>
> if anyone can guide me, at my beginner’s level of understanding and
> experience, through how to get around problems like getting the
> wireless to work, I would be very grateful and at the end of it become
> a little more experienced in using Linux
To build a new kernel, do the following:
-
Log in as your normal user, not as root, and download
http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.27-rc3.tar.bz2
to your home directory. -
In a terminal, enter the command
tar jxvf patch-2.6.27-rc3.bz2 -
Enter the command ‘cd linux-2.6.27-rc3’
-
Enter the command ‘make cloneconfig’
-
Enter the command ‘make’
-
Enter the command ‘sudo make modules_install install’
-
Reboot to the new kernel.
If any of the ‘make’ commands return a command not found, use YaST to
install make. You will also need to have gcc installed. Item number 4
will ask you some configuration questions. Just hit an enter to accept
the default answer.
Post any error messages not covered by this note. It is normal to get
warnings from some of the compilations - ignore them.
Larry
cookdav wrote:
> Everyone wants to give up before trying ndiswrapper?
I had plenty of BSOD’s when running Windows. Why would I want any more
with Linux? In addition, I am a kernel developer, and when my kernel
gets a oops, I want to be able to post the message and get help from
the gurus. If your kernel is tainted by loading ndiswrapper, no one
will look at your error.
Larry
vspunn wrote:
> being a layman to LINUX, i donot understand this kernel. The main reson
> for sitching to LINUX is that windows gets too may spyware and virus,
> which I beleive are rare in LINUX.
>
> By when will this kernel (under development) be out and how will we
> know about it.
> I have downlaoded 10.3 . Which kernel is there in it. And is there any
> layman way to setup RTL 8187B Wireless or should I use wired lan till
> the driver is developed.
Kernel 2.6.27, which contains the RTL8187B fix, will likely be
released in about 6 weeks. It all depends on how many bugs are found.
It has been “feature frozen” for about 3 weeks. At this point, nothing
but bug fixes are to be added.
OpenSUSE has kernel 2.6.22. You can always determin what kernel you
are using by entering the command ‘uname -r’. The only “layman’s” way
to use RTL8187B is to wait for a distro to be released with 2.6.27, or
generate your own following the commands I just posted in this thread.
Generating a kernel is not really very hard. The built-in tools are
all very good.
I would not expect a 2.6.27 or later kernel to appear in openSUSE
until 11.2. The kernel in 11.1 alpha 1 is 2.6.26.
Larry
On Thu, 14 Aug 2008 19:47:25 GMT
Larry Finger <Larry.Finger@lwfinger.net> wrote:
> cookdav wrote:
> > Everyone wants to give up before trying ndiswrapper?
>
> I had plenty of BSOD’s when running Windows. Why would I want any more
> with Linux? In addition, I am a kernel developer, and when my kernel
> gets a oops, I want to be able to post the message and get help from
> the gurus. If your kernel is tainted by loading ndiswrapper, no one
> will look at your error.
>
> Larry
Pretty broad definition of “no one”… Some people are capable enough to tell
if ndiswrapper (or any other drivers) is relevant or not.
You should be able to uninstall ndiswrapper (or any module/driver) and see if
the error/oops continues to occur. Pretty simple to remove any suspicion if
it still happens.
Seems pretty snobbish to refuse to even LOOK at a problem if there was a
tainting module/driver installed. Gee, pretty much cuts out having to
help anyone using the nice 3D ATI or NVidia drivers too. HEY! You don’t have
to help anyone if you can prove it’s tainted… (4. Profit!!!)
Sounds like some of the “tech support” I’ve spoken to…
“Hi, I have a problem, blah, blah, I have ndiswrapper installed”
“We’re sorry, we can’t help you with your sound card”
“But it’s YOUR sound card, well supported in linux…”
“Sorry, but you have ndiswrapper installed, <click>”
Yeah, that’s happened… really.
Well, you sit on your “I’m a Kernel Developer” pedestal… I’ll keep helping
people.
Compiling a kernel isn’t that difficult, I’ll agree. But unless you’re an
“ubér Kernel Developer”… it causes headaches and issues down the road for
the typical user which are hard to explain and hard to resolve. Suddenly
things don’t install because you don’t have the stock kernel that the nice
rpm’s are built for.
ndiswrapper is a good solution for hardware not supported (yet, or ever) in
linux. Sometimes it doesn’t work. Many times it does. It allows the
typical user to use the equipment they have rather than bludgeon them
with the “go buy compatible equipment” club. Yes, I’ve learned what I can
buy and use immediately, and what might not work. But maybe I’m not your
typical user either.
As you just mentioned, the rtl 8187 B will be supported in the upcoming
2.6.27 kernel. So why shouldn’t the typical user use ndiswrapper, enjoy
the use of their neato hardware, all of the precompiled goodness of a
favorite distro, and when the new kernel has become mainstream, begin using
the native drivers? Your solution forces the typical user to endure many
issues that, while often trivial, “taint” (ha!) their view of the linux
experience.
I’d rather hear a new user say “Hey, I had an ubér-cool rtl8187b nic that
didn’t work right away, but with ndiswrapper and a little help, it works
great now!” instead of “well, I had to learn how to install a new kernel, the
rtl8187b works now, but I can’t install my video drivers with the automatic
tools, and my sound card had problems… goodness! it was painful!”.
Yeah… you touched a nerve.
Loni (typical user)
–
L R Nix
lornix@lornix.com
L R Nix wrote:
> On Thu, 14 Aug 2008 19:47:25 GMT
> Larry Finger <Larry.Finger@lwfinger.net> wrote:
>
>> cookdav wrote:
>>> Everyone wants to give up before trying ndiswrapper?
>> I had plenty of BSOD’s when running Windows. Why would I want any more
>> with Linux? In addition, I am a kernel developer, and when my kernel
>> gets a oops, I want to be able to post the message and get help from
>> the gurus. If your kernel is tainted by loading ndiswrapper, no one
>> will look at your error.
>>
>> Larry
>
> Pretty broad definition of “no one”… Some people are capable enough to tell
> if ndiswrapper (or any other drivers) is relevant or not.
>
> You should be able to uninstall ndiswrapper (or any module/driver) and see if
> the error/oops continues to occur. Pretty simple to remove any suspicion if
> it still happens.
>
> Seems pretty snobbish to refuse to even LOOK at a problem if there was a
> tainting module/driver installed. Gee, pretty much cuts out having to
> help anyone using the nice 3D ATI or NVidia drivers too. HEY! You don’t have
> to help anyone if you can prove it’s tainted… (4. Profit!!!)
>
> Sounds like some of the “tech support” I’ve spoken to…
> “Hi, I have a problem, blah, blah, I have ndiswrapper installed”
> “We’re sorry, we can’t help you with your sound card”
> “But it’s YOUR sound card, well supported in linux…”
> “Sorry, but you have ndiswrapper installed, <click>”
>
> Yeah, that’s happened… really.
>
> Well, you sit on your “I’m a Kernel Developer” pedestal… I’ll keep helping
> people.
>
> Compiling a kernel isn’t that difficult, I’ll agree. But unless you’re an
> “ubér Kernel Developer”… it causes headaches and issues down the road for
> the typical user which are hard to explain and hard to resolve. Suddenly
> things don’t install because you don’t have the stock kernel that the nice
> rpm’s are built for.
>
> ndiswrapper is a good solution for hardware not supported (yet, or ever) in
> linux. Sometimes it doesn’t work. Many times it does. It allows the
> typical user to use the equipment they have rather than bludgeon them
> with the “go buy compatible equipment” club. Yes, I’ve learned what I can
> buy and use immediately, and what might not work. But maybe I’m not your
> typical user either.
>
> As you just mentioned, the rtl 8187 B will be supported in the upcoming
> 2.6.27 kernel. So why shouldn’t the typical user use ndiswrapper, enjoy
> the use of their neato hardware, all of the precompiled goodness of a
> favorite distro, and when the new kernel has become mainstream, begin using
> the native drivers? Your solution forces the typical user to endure many
> issues that, while often trivial, “taint” (ha!) their view of the linux
> experience.
>
> I’d rather hear a new user say “Hey, I had an ubér-cool rtl8187b nic that
> didn’t work right away, but with ndiswrapper and a little help, it works
> great now!” instead of “well, I had to learn how to install a new kernel, the
> rtl8187b works now, but I can’t install my video drivers with the automatic
> tools, and my sound card had problems… goodness! it was painful!”.
>
> Yeah… you touched a nerve.
Experience has shown that a runaway “tainted” driver can affect any
place in the kernel. The Windows wireless driver loaded by ndiswrapper
could be tromping on your ide disk driver, and the Nvidia driver could
be killing your sould card. BTW, grep for “ndiswrapper killed sound
card” and see how often that happens. If my post educates some people,
that is good. How many users realize that using ndiswrapper lets a
piece of Windows have full, unrestricted access to their kernel?
The concept of “tainting” was added in Linux 2.6 and was a direct
result of the time wasted trying to debug kernel problems that were
due to foreign, non-GPLed drivers.
Incidentally, I have an Nvidia card in my computer, but I find that
the GPLed framebuffer driver gives me all the performance I need, and
it does not taint my kernel.
Larry
Thanks for the info.
I beleive that hardware support is the only thing that is stopping LINUX from taking over Windows.
Many newbies like me face problems in hardware and have to switch back to windows till some proper support is provided.
I suggest that there should be live chat support by professional LINUX users who can help newbies.
On Sat, 16 Aug 2008 06:16:03 GMT
vspunn <vspunn@no-mx.forums.opensuse.org> wrote:
>
> Thanks for the info.
>
> I beleive that hardware support is the only thing that is stopping
> LINUX from taking over Windows.
>
> Many newbies like me face problems in hardware and have to switch back
> to windows till some proper support is provided.
>
> I suggest that there should be live chat support by professional LINUX
> users who can help newbies.
>
>
Hey! {Grin} Isn’t that what we are? Well… slow live support… sorta.
Wait… what’s a “Professional LINUX user”?
Ooo! Sounds neat! You think I could qualify to be a “Professional LINUX
User”? Must have to be pretty smart though…
{Grin}
Loni
–
L R Nix
lornix@lornix.com