From: adam@address.invalid
unruh wrote:
> On 2012-09-27, Adam wrote:
Thanks for replying, Bill! The latest news here is that the problem
with wired connections turned out to be -- a bad cat5e cable between the
computer and router. I replaced that, and now the distros that had no
connection (including Mageia) now have a working wired connection and
the latest updates. I want a working wireless connection for all the
distros on this box, though, as this is my "test" system (named "eris")
which will soon be going back to the other room where there's only
wireless connectivity.
> You need to give more information. What wireless card does your computer
> use? What wired card? Do you have the driver modules loaded for them?
> What is in /var/log/messages when you try to connect?
> What are you trying to connect to?
Yep, those are good questions. The ones that I don't have an answer for
yet, I need to look into. "eris" has a wired card as part of the
motherboard, and I've had no problems with that under any distro I've
tried it with. Its PCI wireless card is a Ralink which uses the
rt2661.bin driver which I had to download from the Ralink web site, and
that driver's loaded in the two distros which have a working wireless
connection.
Now the part where I need to find more answers. (I'm using another
distro to write and post this.) The Ralink rt2661 driver is installed
in Mageia but from looking at its /var/log/messages file, Mageia /may/
be trying to use the rt61pci driver instead. The most common relevant
messages there seem to be "device is not ready" and "link beat not
detected". I'll reboot into Mageia and investigate some more. I'm
trying to connect first to my router, since all my 'net traffic passes
through that. All works fine with a wired connection, but so far a
wireless connection can't even successfully ping the router.
> Note that the draknetcenter on Mageia is somewhat broken in that the
> netcenter display does not keep up with the status of the connection,
> and it will always say that the connection times out, even if the
> connection was made. Look instead at the state of the network applet on
> the task bar, which does keep up.
Oh, okay. Thanks for letting me know!
> You can also try just running ifup-eth directly.
> (as root to
> ifup-eth wlan0
> for example, assuming wlan0 is the wireless)
I've tried ifup, but not ifup-eth. Another thing to look into.
>> TJ said the updates to Mageia 2 include a better "wireless config"
>> helper.
>
> I have not seen any improvement.
My mistake, TJ said it had been /updated/. I naively assumed that meant
an improvement.
>> Destination Gateway Genmask Flags Metric Ref Use Iface
>> 0.0.0.0 192.168.1.13 0.0.0.0 UG 5 0 0 eth0
>> 169.254.0.0 0.0.0.0 255.255.0.0 U 5 0 0 eth0
>> 192.168.1.0 0.0.0.0 255.255.255.192 U 5 0 0 eth0
>
> And you think you have no connection why?
That's fixed now, but I thought so because ping lost many packets, and I
couldn't get to any web page at all, not even the router's main menu.
> It even one ping gets through then the problem is not your network
> connection. You are looking at the wrong place for solving your
> problems.
Yep, I was. I wouldn't have thought to check the cat5e cable if Jim
Beard hadn't suggested it.
>> I can't be the only person that has more than one computer plugged into
>> a single router!
>
> IF the two computers have the same IP address, then your system will be
> very very confused, and your symptoms will be exactly what you have now.
> All connections MUST have different ip addresses.
Since posting last evening, I've made "eris.aplomb.invalid" 192.168.1.23
for the wireless connection, and "eris-wired.aplomb.invalid"
192.168.1.24 (for the distros with a wired connection). Since I know I
can't use both of them at the same time, in /etc I have files
hostname-wired and hostname-wireless, and hostname itself is just a link
to whichever of the two is appropriate at the moment.
Adam
--
Registered Linux User #536473
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
