SEO

I am having a horrible time trying to get either my lan, or wlan
working.
I dont know much of anything, and it is really starting to bother me.
I am running slackware version 10.0 kernel 2.4 and have the following
for
devices.
Network card: RealTek RTL8100C(L)
Wireless: Broadcom 802.11b/g

as far as what chipset the broadcom uses i have no idea.
they are both integrated with my labtop. a hp pavilion zv5404.

ive heard the broadcom will not work.
thanks for any help
-Cody

On Sat, 26 Nov 2005 03:59:25 +0100, <cflorek@gmail.com> wrote:

> I am running slackware version 10.0 kernel 2.4 and have the

In this kind of questions, it pays being quite specific.
2.4.what?

I believe wireless support has improved since 2.4. Why not the latest?
(But I believe there is still no native support for Broadcom. See
below.)

> following for devices.
>
> Network card: RealTek RTL8100C(L)
> Wireless: Broadcom 802.11b/g
>
> as far as what chipset the broadcom uses i have no idea.
> they are both integrated with my labtop. a hp pavilion zv5404.

What is the output of lspci?
Any pertinent error messages in /var/log/dmesg?
Any pertinent error messages in /var/log/messages?

What is the output of ifconfig?

Consider this link:

http://www.redrockcomputer.com/zv5340_wireless.htm

It reports of a successfull install of ndiswrapper with Win XP
driver, on a 2.6.9 kernel.

-Enrique

On 25 Nov 2005, in the Usenet newsgroup comp.os.linux.setup, in article
<1132973965.107415.280910@g49g2000cwa.googlegroups .com>, cflorek@gmail.com
wrote:

>I am having a horrible time trying to get either my lan, or wlan
>working.
>I dont know much of anything, and it is really starting to bother me.

You actually have given slightly more than zero information, but not much.
What is happening - is the computer catching fire or something? If you
want help, you've at least got to tell us what you expect to happen,
what you've tried, and most importantly, WHAT ARE THE ERROR MESSAGES?

You mention having two network devices - you aren't trying to run them
both on the same network, are you?

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 95017 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 420 lo

That one isn't going to work unless you play with the Adv-Routing-HOWTO,
because the kernel sees two routes going to the same place, and will
ignore one of them.

>they are both integrated with my labtop. a hp pavilion zv5404.

Have you tried a google search using the terms 'hp pavilion zv5404 linux'?
Might help.

Old guy

On Sat, 26 Nov 2005 14:19:05 -0600, ibuprofin@painkiller.example.tld
(Moe Trin) wrote:

>You mention having two network devices - you aren't trying to run them
>both on the same network, are you?
>
>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref Use Iface
>192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 95017 eth0
>192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
>127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 420 lo
>
>That one isn't going to work unless you play with the Adv-Routing-HOWTO,
>because the kernel sees two routes going to the same place, and will
>ignore one of them.

Is there an (easy) way to make linux prefer the eth0 interface if it is
connected and otherwise use the wlan0 interface?



cu, Martin
--
Ubi bene ibi Colonia!
ROT13 for email: znegva.trexra@jro.qr

In comp.os.linux.setup Martin Gerken <m_gerken@yahoo.com>:
> On Sat, 26 Nov 2005 14:19:05 -0600, ibuprofin@painkiller.example.tld
> (Moe Trin) wrote:

>>You mention having two network devices - you aren't trying to run them
>>both on the same network, are you?
>>
>>Kernel IP routing table
>>Destination Gateway Genmask Flags Metric Ref Use Iface
>>192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 95017 eth0
>>192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
>>127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 420 lo
>>
>>That one isn't going to work unless you play with the Adv-Routing-HOWTO,
>>because the kernel sees two routes going to the same place, and will
>>ignore one of them.

> Is there an (easy) way to make linux prefer the eth0 interface if it is
> connected and otherwise use the wlan0 interface?

Sounds like it should be possible with a clever setup of bonding
over devices. You should find all info (needs kernel source
installed) right on your system:
/usr/src/linux*/Documentation/networking/bonding.txt

"Easy" is hard to tell, YMMV.

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 77: Typo in the code

On Sun, 27 Nov 2005 11:26:15 +0100, Michael Heiming
<michael+USENET@www.heiming.de> wrote:

>> Is there an (easy) way to make linux prefer the eth0 interface if it is
>> connected and otherwise use the wlan0 interface?
>
>Sounds like it should be possible with a clever setup of bonding
>over devices. You should find all info (needs kernel source
>installed) right on your system:
>/usr/src/linux*/Documentation/networking/bonding.txt
>
>"Easy" is hard to tell, YMMV.

Well, sounds about above my level of knowledge ;-(

I've found ifplugd
http://www.stud.uni-hamburg.de/users...jects/ifplugd/
and it seems, that thingie could help.

All I want to do is automatically use the LAN-cable instead of the slow
WLAN whe I plug in the cable.


cu, Martin
--
Ubi bene ibi Colonia!
ROT13 for email: znegva.trexra@jro.qr