LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   Installing ethernet card driver (https://www.linuxquestions.org/questions/linux-wireless-networking-41/installing-ethernet-card-driver-633411/)

Completely Clueless 04-06-2008 07:44 AM

Installing ethernet card driver
 
Hi guys,

I would have thought this would be a very straightforward and basic operation, but it appears otherwise from the searches I've made. Is the procedure generally the same regardless of the hardware concerned or does it vary accordingly? And does it invariably involve compiling a source file with a compiler that's compatible with the kernel?

THanks

tredegar 04-06-2008 09:02 AM

Plug it in. Boot. The chances are that it will be recognised and the appropriate module loaded.

What is the card you are trying to install?
What is your distro?
What have you tried so far?

vwvr9 04-06-2008 09:14 AM

what NIC card are u using?

pixellany 04-06-2008 09:49 AM

Quote:

Originally Posted by Completely Clueless (Post 3112406)
Hi guys,

I would have thought this would be a very straightforward and basic operation, but it appears otherwise from the searches I've made. Is the procedure generally the same regardless of the hardware concerned or does it vary accordingly? And does it invariably involve compiling a source file with a compiler that's compatible with the kernel?

THanks

I've never had trouble with any conventional Ethernet (AKA wired) card.

Please put your distro in your profile--and include other relevant info (eg hardware) when you post,

Completely Clueless 04-06-2008 02:56 PM

Apologies, all, I've now entered a profile.

This is what the interogation of my notebook says about networks:

00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02)
Subsystem: Fujitsu Siemens Computer GmbH: Unknown device 1125
Flags: bus master, medium devsel, latency 0, IRQ 4
Memory at d4407000 (32-bit, non-prefetchable) [size=128]
I/O ports at 1080 [size=128]
Capabilities: [40] Power Management version 2

[....]

02:00.0 Ethernet controller: Atheros Communications, Inc.: Unknown device 001c (rev 01)
Subsystem: Atheros Communications, Inc.: Unknown device 3067
Flags: fast devsel, IRQ 9
Memory at d4100000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
Capabilities: [60] #10 [0011]
Capabilities: [90] #11 [0000]


Now I'm assuming it's the Atheros card that's in-built and I have downloaded a driver that reportedly is compatible with all 3 variants of it. What now?

CC.

tredegar 04-06-2008 04:49 PM

Quote:

Apologies, all, I've now entered a profile.
A good start :)
Quote:

This is what the interogation of my notebook says about networks:
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02)
Subsystem: Fujitsu Siemens Computer GmbH: Unknown device 1125
Flags: bus master, medium devsel, latency 0, IRQ 4
Memory at d4407000 (32-bit, non-prefetchable) [size=128]
I/O ports at 1080 [size=128]
Capabilities: [40] Power Management version 2
What "interrogation"?
That output is not telling you anything about "networks", it is telling you about what hardware you have installed (but that is still useful information..)

What command gave you that output?

Quote:

Now I'm assuming it's the Atheros card that's in-built and I have downloaded a driver that reportedly is....
Please do not assume anything: Find out, confirm, then post here.

You have downloaded "a driver". WTF?
How are we supposed to know what "driver" you have "downloaded"?
What did you do with it once you had "downloaded" it?
Did you install it?

Which "driver" did you download? Linux uses modules, not "drivers".

Your question was "Installing ethernet card driver" so we are assuming (because you have not provided any details) that you are trying to install a PCI Ethernet (wired) card. If this is not the case, please explain exactly what it is you are trying to do.

See my post at #2, and answer the questions.

Grrrrrr :(

Completely Clueless 04-07-2008 09:35 AM

Quote:

Originally Posted by tredegar (Post 3112833)
A good start :)

What "interrogation"?
That output is not telling you anything about "networks", it is telling you about what hardware you have installed (but that is still useful information..)

What command gave you that output?

this one: /sbin/lspci -v
If you know of a better one for displaying a list of hardware devices, please share it.

Quote:

Originally Posted by tredegar (Post 3112833)
Please do not assume anything: Find out, confirm, then post here.

You have downloaded "a driver". WTF?
How are we supposed to know what "driver" you have "downloaded"?
What did you do with it once you had "downloaded" it?
Did you install it?

Which "driver" did you download? Linux uses modules, not "drivers".

I was under the impression that "driver" and "module" mean one and the same; that a person refers to "modules" as opposed to "drivers" in Linux simply because it's a naming convention. Is that not the case? I'll call them "modules" in future if that's the accepted convention here.

I downloaded it from the author's website to the desktop on my Windows PC, from there I unzipped it to a usb memory stick ready to transfer to the Linux machine. I have not installed it as I don't know how to. It's obviously not as simple as just copying it over to a directory like C:\win32\drivers as with Windows. Hence my original question.

Quote:

Originally Posted by tredegar (Post 3112833)
Your question was "Installing ethernet card driver" so we are assuming (because you have not provided any details) that you are trying to install a PCI Ethernet (wired) card. If this is not the case, please explain exactly what it is you are trying to do.

I think there's some misuderstanding here. I'm not trying to *physically* install a network card. It's already integrated into the motherboard of this notebook. I simply need to get it working, which obviuously requires some kind of software interface by whatever name, to enable the kernel to talk to it.

Here's the relevant spec from the user guide:

Networking

Networking: Network adapter

Wireless LAN Supported: Yes

Data Link Protocol: Ethernet, Fast Ethernet, Gigabit Ethernet, IEEE 802.11b, IEEE 802.11g

Compliant Standards: IEEE 802.11b, IEEE 802.11g

So again, how do I go about getting wireless lan capability activated?

THanks,

CC.

tredegar 04-07-2008 02:10 PM

Quote:

/sbin/lspci -v
If you know of a better one for displaying a list of hardware devices, please share it.
No, this is good for hardware, and lspci -vvv is even better! (But I misunderstood your post, and thought that you were looking at output for "network"). No matter.

Quote:

I was under the impression that "driver" and "module" mean one and the same;
Well, they do & they don't ;)
When people talk about "drivers" as in "I have a driver downloaded", the assumption (dangerous things those) is that it's a windows driver that'll then need special handling by linux (eg by using ndiswrapper or similar)
If it is a native linux module, perhaps best to call it that.

Quote:

I think there's some misunderstanding here. I'm not trying to *physically* install a network card...
There was misunderstanding, but we are clearing it up fast :) especially now you are explaining your situation and problem better ;)

So, now to your problem: you have on-board [SiS] 191 Gigabit Ethernet (which is wired), that you do not wish to use.
It seems you do want a wireless connection, via your Atheros Communications, Inc.: Unknown device 001c
You are running Fedora 8.

The fact that lspci reports your Atheros is "unknown", doesn't look good, but is maybe fixable. I googled for a while and there was a developer message saying "we don't support this chip yet" dated 2007/11/23 [ http://www.spinics.net/lists/linux-w.../msg08178.html ] :( Maybe it is supported now. Perhaps by madwifi

Unfortunately you haven't told us exactly what it is you have downloaded "from the author's website", or even given us a link to it, so we need more information on this before we can go any further.

In future, as a general rule, when buying laptops for linux, choose from those with NVIDIA graphics chipsets, and INTEL wireless chipsets, because then they "just work" (TM) :)

Ps A bit more searching and it looks like you'll need ndiswrapper. Please see here http://ndiswrapper.sourceforge.net/j...3/id,list_c-f/
and search for 001c on that page.

Completely Clueless 04-07-2008 04:23 PM

Many thanks for the tips, which I've snipped.

Quote:

Originally Posted by tredegar (Post 3113711)
So, now to your problem: you have on-board [SiS] 191 Gigabit Ethernet (which is wired), that you do not wish to use.
It seems you do want a wireless connection, via your Atheros Communications, Inc.: Unknown device 001c
You are running Fedora 8.

I actually have NO idea whatsoever what the SIS 191 Gb Ethernet card is, what it does or is capable of. As you have gathered, I'm primarily concerned with getting wi-fi access on the move via public hotspots, which is why I "assumed" - sorry, won't do that again - that it was the Atheros device, as opposed to the SIS 191 one, which I needed a driver/module for.

Quote:

Originally Posted by tredegar (Post 3113711)
The fact that lspci reports your Atheros is "unknown", doesn't look good, but is maybe fixable. I googled for a while and there was a developer message saying "we don't support this chip yet" dated 2007/11/23 [ http://www.spinics.net/lists/linux-w.../msg08178.html ] :( Maybe it is supported now. Perhaps by madwifi

Unfortunately you haven't told us exactly what it is you have downloaded "from the author's website", or even given us a link to it, so we need more information on this before we can go any further.

Well it's odd that you should mention Madwifi, because it is they who have written the software which I believe will interface the hardware to the OS. They claim it NOW functions fine on ALL variants of these Atheros wireless cards. Here's what it says in the Readme file. Perhaps you can tell me how to proceed from here as it's all Greek to me...

Readme contents:-

MADWIFI: Multimode Atheros Driver for WiFi on Linux (VAP branch)
================================================================

* Copyright (c) 2002-2005 Sam Leffler. All rights reserved.

Read the file COPYRIGHT for the complete copyright.


WARNING: THIS IS A BETA DISTRIBUTION. THIS SOFTWARE HAS KNOWN PROBLEMS
WARNING: AND LIMITATIONS THAT WILL BE CORRECTED BEFORE A PRODUCTION
WARNING: RELEASE. DON'T BLAME US IF THE SOFTWARE EATS YOUR SYSTEM,
WARNING: DESTROYS YOUR DISK OR MAKES YOUR CORN-FLAKES SOGGY.
WARNING: USE AT YOUR OWN RISK!


Introduction
------------

This software contains a Linux kernel driver for Atheros-based Wireless
LAN devices. The driver supports station, AP, ad-hoc, and monitor modes
of operation. The Atheros driver depends on a device-independent
implementation of the 802.11 protocols that originated in the BSD
community (NetBSD in particular).

The driver functions as a normal network device and uses the Wireless
Extensions API. As such normal Linux tools can and should be used with
it. Where the wireless extensions are lacking private ioctls have been
added.

There is only one driver included here; it supports PCI, MiniPCI and
Cardbus devices - USB devices are currently not supported by this
driver! The driver can be built as a module or linked directly into the
kernel. Note however that the net80211 layer is device-independent;
there is no reason it cannot be used with any 802.11 device (in fact
this is the case on BSD systems).

This software is broken into multiple modules. The Atheros-specific
device support is found in the ath_pci module; it should be loaded when
an Atheros wireless device is recognized. The ath_pci module requires
an additional device specific module, ath_hal, which is described more
below. In addition the driver requires the wlan module which contains
the 802.11 state machine, protocol support, and other device-independent
support needed by any 802.11 device. This code is derived from work
that first appeared in NetBSD and then FreeBSD. The wlan module may
also force the loading of additional modules for crypto support
(wlan_wep, wlan_tkip, wlan_ccmp, etc.), for MAC-based ACL support
(wlan_acl), and for 802.1x authenticator support (wlan_auth,
wlan_radius). The latter modules are only used when operating as an AP.
The crypto modules are loaded when keys of that type are created.

The ath_hal module contains the Atheros Hardware Access Layer (HAL).
This code manages much of the chip-specific operation of the driver.
The HAL is provided in a binary-only form in order to comply with FCC
regulations. In particular, a radio transmitter can only be operated at
power levels and on frequency channels for which it is approved. The
FCC requires that a software-defined radio cannot be configured by the
user to operate outside the approved power levels and frequency
channels. This makes it difficult to open-source code that enforces
limits on the power levels, frequency channels and other parameters of
the radio transmitter. See
http://ftp.fcc.gov/Bureaus/Engineeri...1/fcc01264.pdf
for the specific FCC regulation. Because the module is provided in a
binary-only form it is marked "Proprietary"; this means when you load it
you will see messages that your system is now "tainted".

A detailed discussion of the pros and cons of this design can be found
at http://madwifi.org/wiki/HAL

If you wish to use this driver on a platform for which an ath_hal module
is not already provided please contact the author. Note that this is
only necessary for new _architectures_; the HAL is not tied to any
specific version of Linux - in fact the identical HAL binary code is
used unchanged with other operating systems.


Atheros Hardware
----------------

There are currently three "programming generations" of Atheros 802.11
wireless devices (some of these have multiple hardware implementations
but otherwise appear identical to users):

5210 supports 11a only
5211 supports both 11a and 11b
5212 supports 11a, 11b, and 11g

These parts have been incorporated in a variety of retail products
including Cardbus cards from D-Link, Linksys, Netgear, Orinoco, Proxim,
and 3Com; and mini-pci cards from some of these same vendors. In
addition, many laptop vendors use Atheros mini-pci cards for their
built-in wireless support.

For an up-to-date list of cards based on Atheros parts visit:
http://customerproducts.atheros.com/customerproducts

A list of products that have been reported to be supported by MadWifi
can be found here:
http://madwifi.org/wiki/Compatibility

In general, if a device is identified as ``11a only'', it is almost
certain to contain an Atheros 5210 part in it. Most retail a+b products
use the 5211. Many a+b+g combo products use the 5212 though other
vendors have started to offer dual-band support. When in doubt, check
the PCI vendor ID with a tool like lspci, the Atheros vendor ID is
0x168c; e.g.

00:13.0 Ethernet controller: Unknown device 168c:0012 (rev 01)

but beware that some vendors use alternate vendor IDs (e.g 3Com, IBM).
The file hal/ah_devid.h has a list of known PCI IDs.


Building the driver
-------------------

The procedure to build the driver is described in the file INSTALL.


Using the driver
----------------

The driver should support any Atheros-based Cardbus or PCI device. This
version of the driver is managed and controlled by the usual Linux tools
(ifconfig, iwconfig, iwpriv) plus the wlanconfig tool, which is included
with the driver in the tools directory and gets installed on your system
with make install.

First, run "modprobe ath_pci" or the equivalent using "insmod". When
the driver is successfully loaded it creates two devices, named "wifi0"
and "ath0". The output from iwconfig should look like this:

lo no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11b ESSID:""
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:50 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


This driver uses wifi%d only as a placeholder for the physical device,
and will create one wifi device for each wireless NIC in the system.
These wifi devices will reject ifconfig and iwconfig commands. The wifi
interface indicates the existence of a physical MadWifi device, but it
is not of any functional interest other than as the starting point for
VAP creation via wlanconfig (see Virtual AP section below).

By default, an ath%d Managed mode interface is also created. This
device is a "virtual ap" (VAP) of the wifi%d physical device, and is
configurable by the standard networking tools - ifconfig, iwconfig,
iwpriv.

The autocreation function can be manipulated to create any one of the
other supported device types automatically by using the autocreate=mode
option when the ath_pci module is first loaded. The following example
will cause ath%d to be in Master mode:

modprobe ath_pci autocreate=ap

Autocreation can be disabled:

modprobe ath_pci autocreate=none

Please see the following link for more information:
http://madwifi.org/wiki/UserDocs/autocreate


Virtual APs (VAPs) and wlanconfig
---------------------------------

An interesting feature of MadWifi is Virtual AP (VAP) mode, which allows
the operation of multiple concurrent (virtual) access points, and
concurrent interfaces running in both AP and station mode. To
manipulate VAP's, MadWifi comes with a tool called wlanconfig which is
used to create and destroy VAPS with various different modes.

The following examples assume that the "autocreate=none" option has been
parsed to the module at load time. This allows fine control over
management of VAP's, as the creation of a Managed mode station should be
delayed until all other required VAP's are first created, as only one
sta mode VAP can exist per physical device.

To create an access point, use:

wlanconfig ath0 create wlandev wifi0 wlanmode ap

To create an access point and a station, use:

wlanconfig ath0 create wlandev wifi0 wlanmode ap
wlanconfig ath1 create wlandev wifi0 wlanmode sta nosbeacon

To create APs that share a single MAC address, use the -bssid flag when
creating the VAPs:

wlanconfig ath0 create wlandev wifi0 wlanmode ap -bssid
wlanconfig ath1 create wlandev wifi0 wlanmode ap -bssid

Finally, to destroy a VAP, issue the command:

wlanconfig ath0 destroy

For more information about Virtual AP's, please refer to the users-guide
document distributed with the MadWifi source code.

For more information about wlanconfig, see its manpage, it is installed
when you run "make install".


Operating Mode
--------------

If you have a multi-mode card, use one of the following commands to lock
the operating mode to one of 11a, 11b, or 11g:

iwpriv ath0 mode 1 lock operation to 11a only
iwpriv ath0 mode 2 lock operation to 11b only
iwpriv ath0 mode 3 lock operation to 11g only
iwpriv ath0 mode 0 autoselect from 11a/b/g (default)


Debugging
---------

There are some debugging mechanisms for the curious/masochistic:

sysctl -w dev.ath.debug=0xXXX enable console msgs from the driver
sysctl -w net.wlan0.debug=0xYYY enable console msgs from the wlan module

The values specified for 0XXX and 0xYYY are bit masks that enable
debugging in various parts of each module. For the wlan module these
values are found in the file net80211/ieee80211_var.h (search for MSG_).
For the ath driver look in ath/if_ath.c (search for ATH_DEBUG). Beware
that enabling some debugging msgs can affect the operation of the
software by slowing it down too much.

A more comfortable way to manipulate the debug settings is to make use
of athdebug and 80211debug tools. Call them with the parameter "-h" to
learn how they are used, or refer to the appropriate man pages.

In addition the programs tools/athstats and tools/80211stats can be very
useful in understanding what is going on. In particular, something like

athstats 1

will give a running display of the most interesting statistics sampled
every 1 second. Running athstats without any options will display a
summary of all non-zero statistics from the time the driver was loaded.
By default the ath0 device is used; to override this use the -i option.

A wiki page describes common MadWifi debugging methods here:
http://madwifi.org/wiki/DevDocs/AthDebug


Security/Crypto Support
-----------------------

All Atheros devices implement fixed/shared key WEP in hardware. Newer
Atheros hardware is capable of much more (e.g. AES, TKIP and Michael).
When hardware support is not available for a cipher the net80211 layer
will automatically do the work in software.

WPA/802.11i station operation (aka supplicant) is supported using Jouni
Malinen's wpa_supplicant program. This can be obtained from:

http://hostap.epitest.fi/wpa_supplicant/

wpa_supplicant also supports a wide range of 802.1x EAP methods, either
together with WPA/WPA2 or without; consult the wpa_supplicant
documentation for an up to date list.

MadWifi supports the use of the Wireless Extensions ioctl's equal to or
greater than WE18 (linux 2.6.15). When using wpa_supplicant with a
recent linux kernel, it is preferred to use the 'wext' driver backend,
rather than the private MadWifi ioctl's. This means that '-D wext'
option should be used with wpa_supplicant when the linux kernel version
is 2.6.15 or above.

NOTE: the in-kernel authenticator is being replaced; to use it you need
to follow the directions in net80211/Makefile.

When operating as an AP, you can use fixed/shared key ciphers and/or
802.1x authentication. The authentication mode is specified using
iwpriv:

iwpriv ath0 authmode 1 # open authentication
iwpriv ath0 authmode 2 # shared key authentication
iwpriv ath0 authmode 3 # 802.1x authentication

To use the 802.1x authenticator you must install and configure the
hostapd program from the same place you got wpa_supplicant from.
Consult the hostapd documentation for further information.


Live Monitoring and Writing Raw 802.11 Packets
----------------------------------------------

The driver can be used in a live "monitor" mode, by creating a monitor
VAP and sending packets to it. All packets sent to a monitor mode VAP
will bypass any state machine.

To create a monitor VAP, use:

wlanconfig ath1 create wlandev wifi0 wlanmode monitor
ifconfig ath1 up

Finally, you can choose to receive packets on ath1 in several different
packet formats:

echo '801' > /proc/sys/net/ath1/dev_type # only 802.11 headers
echo '802' > /proc/sys/net/ath1/dev_type # prism2 headers
echo '803' > /proc/sys/net/ath1/dev_type # radiotap headers
echo '804' > /proc/sys/net/ath1/dev_type # atheros descriptors


Known Problems
--------------

[All these problems are to be fixed in future revisions.]

1. Ad-hoc mode is broken; symptoms are intermittent operation.

Other issues might be mentioned in our ticket tracker:
http://madwifi.org/report/1


Getting Support
---------------

User support is provided via the madwifi-users mailing list, which can
be reached at:

madwifi-users@lists.sourceforge.net

Contact this mailing list if you need help in getting your installation
up and running. We suggest that you subscribe to the list before
sending your request (see below).

We also offer an IRC channel that might be a better help in urgent
cases. Learn more about the different ways to get support by visiting:

http://madwifi.org/wiki/Support

When sending a support request or problem report be sure to include the
version of the driver and the part identification the driver prints to
the console when the module is loaded. For example:

ath_hal: 0.8.2.0
wlan: 0.7.0.0
ath_pci: 0.8.2.0
PCI: Found IRQ 11 for device 00:13.0
ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 802.11 address: 00:05:5d:6f:99:5f
ath0: Atheros 5211: mem=0xfebf0000, irq=11

This says the HAL module is version 0.8.2, the wlan module is version
0.7, the driver is version 0.8.2 and the hardware uses an Atheros 5211
chip (which supports 11a and 11b modes).

We will try to respond in a timely manner but understand this software
is provided as-is, without any promise of support.


Feedback and Contributions
--------------------------

Reports about reproducible bugs, feature requests and patches should be
submitted in the form of a trouble ticket:

http://madwifi.org/newticket

Fixes and enhancements are encouraged.

[Readme ends]

Many thanks for your time and trouble. It's appreciated.
CC.

tredegar 04-07-2008 05:25 PM

Quote:

I actually have NO idea whatsoever what the SIS 191 Gb Ethernet card is
The SIS 191 is the interface for your wired (Ethernet) connection. But you have chosen not to use this.

There'll be a socket on your laptop that looks a bit like a phone socket, but a bit bigger. You can plug in a CAT5 cable there, and connect it to your router (which will have a similar socket to receive the other end of the cable), and it'll probably work. Always has done in my recent years with linux. But this is a wired connection, which you do not want.

To go back: You want wireless connectivity. That's a diferent matter altogether: You want to be able to use your wireless interface, and that is the Atheros one.

You have posted a huge "readme" file to this forum, but why didn't you just do as I suggested and post a LINK to wherever you have "downloaded a driver" from ?

I do not want to read the "readme" when I cannot see the files it is referring to, which you have "downloaded to windows and unzipped". This tells me nothing. Grrrrr :(

You started off on the wrong foot with this thread, by titling it "Installing ethernet card driver"

- It's not an "Ethernet card", because what you want is wireless. That's not "Ethernet", it's "Wireless".
- You are not "installing" anything, it is (at last we now know) a built-in piece of hardware to your laptop's motherboard.

You might have had a better response if you had titled your thread "Atheros Communications, Inc.: Unknown device 3067" not working.

You really aren't helping us to help you. Maybe CC is an apt moniker ;)

I ask you to think very carefully. Compose your reply offline. Read and re-read it to make sure it answers all the questions posed. Check and double-check. All questions answered? All links supplied? All outputs from commands listed?

Have you read: http://linuxsilo.net//docs/smart-questions_en.html

Then post ;)
We'll all try to help you, but if you do not explain your problem, there are misunderstandings, assumptions (probably incorrectly) made and confusion reigns :(

Details, details, details. Please :)

Completely Clueless 04-07-2008 06:14 PM

Hello Tredegar,

I'm sorry for any confusion. As you have noted, my screen name is highly appropriate. I am totally wet-behind-the-ears when it comes to Linux and thought that by the choice of this name, people would make a few more allowances for my ignorance of the subject.

Sorry I didn't post a link to the site, I expected everything you needed to know would be in the Readme file I posted. But having said that, since I don't fully understand the text of it, perhaps that expectation was an *assumption* too far!

As regards to the term "Ethernet Card" I believe I'm entitled to be fully confused by it. The key term, "Ether" is an old-fashioned word for the space through which wireless waves propagate. To me, it was clearly implicit in the term "Ethernet Card" that a piece of hardware could communicate via the 'Ether' - free space in other words. The term is actually very old (as am I) so you may never have encountered it. Nevertheless, it clearly implies, to persons of a certain age that it is purely a WIRELESS connection device!

In view of my very great age, perhaps you would be good enough to summarize, in full, in one paragraph, what details I have yet to provide?

Many thanks indeed for your time and effort.

cc

PS: will guarantee to answer EVERY point if it's within ONE paragraph (memory's not what it was, I'm afraid).

cc.

tredegar 04-08-2008 08:43 AM

Easy, one Q:
What "driver" have you downloaded, and where did you download it from [I need a link].

tredegar 04-08-2008 09:55 AM

I have been doing some searching.....

Q1] - Most laptops have some sort of switch to turn wireless on & off. Does yours have this? Is your wireless turned on?

My laptop (which doesn't use the atheros chipset) is running kubuntu 6.06 [ http://www.kubuntu.org/download.php#lts ] and already has the ath_pci module that the Atheros chipsets need; available, but not loaded. Yours probably has too. So I doubt you'll need to go to the trouble of compiling it from source.

As root, try:
lsmod | grep ath
Q2] - Is anything listed?
If not, try inserting the module (as root again):
modprobe ath_pci
Once the module has loaded (it loads some others that are needed as well) try (again, as root)
iwlist scan
Q3] - What happens?

Off-topic: I'm old enough to remember when ther was written "correctly" ;)

Completely Clueless 04-08-2008 02:52 PM

Quote:

Originally Posted by tredegar (Post 3114621)
I have been doing some searching.....

Q1] - Most laptops have some sort of switch to turn wireless on & off. Does yours have this? Is your wireless turned on?

My laptop (which doesn't use the atheros chipset) is running kubuntu 6.06 [ http://www.kubuntu.org/download.php#lts ] and already has the ath_pci module that the Atheros chipsets need; available, but not loaded. Yours probably has too. So I doubt you'll need to go to the trouble of compiling it from source.

As root, try:
lsmod | grep ath
Q2] - Is anything listed?
If not, try inserting the module (as root again):
modprobe ath_pci
Once the module has loaded (it loads some others that are needed as well) try (again, as root)
iwlist scan
Q3] - What happens?

Okay, sorry for the delay; I had to pop down to Luxemberg today and have only just got home. I'll get to work on your suggestions and hope to post back the results before 11pm UK time.

Many thanks,
CC

Completely Clueless 04-08-2008 03:41 PM

Okay, here's some interim results in part:

I'm not sure what you mean by the phrase "as root" - I've taken it to mean I should enter a forward slash before each command, like this:

"/lsmod | grep ath" (without the quotes) is that correct? Response is: "bash: /lsmod: No such file or directory"

I then tried again without the forward slash prefix and got the response: "bash: lsmod: command not found"

And this was the case for all your suggested inputs, I'm sorry to say. Looks like Fedora doesn't recognise them.

YOu mention an on/off switch. Would this be a physical switch on the case somewhere, or a virtual switch in the BIOS or something of that sort?

I'll try to find the link to the site where I downloaded the module....

CC.

Completely Clueless 04-08-2008 03:53 PM

In answer to your posting number 12...


This is a link to the page I downloaded it from:

http://sourceforge.net/project/showf...group_id=82936

And FROM this page I downloaded THIS file: madwifi-0.9.4.tar.gz

I'd be interested to know why you place such importance on the source of the module/driver?

Thanks,

cc.

Completely Clueless 04-08-2008 04:01 PM

Further info from the boot up report. Everything else in the boot up goes fine, but for
these two failure points which I've reproduced verbatim from the screen:


Determining IP information for eth0... failed; no link present. Check cable

Bringing up interface wlan0: SIOCSIFFLAGS: invalid argument. Failed.

I'm inclined to believe these are further clues as to the problem, but since they're in 'computerspeak'
and I'm a mere mortal, I'm afraid they're incomprehensible to me. :-(

CC.

tredegar 04-08-2008 06:44 PM

Quote:

I'm not sure what you mean by the phrase "as root"
Ouch!
You have 37 posts to LQ and you haven't grasped the concept of the "root" or "superuser" or in windows terms maybe "the administrator"??? :(

Yes, it is (potentially) confusing that the "root" of the filesystem, /, is also referred to as "root" (but that's because the linux filesystem is built like a tree, with a root, and then "branches" off it.

It probably doesn't help that this "tree" is usually depicted upside-down or sideways, but we are imaginative people, and can do 90 and 180 degree rotations in our heads without too much stress on the organic processor ;) )

Anyway, please take a look at this document: http://tldp.org/LDP/intro-linux/html/ or
here (as a nice PDF): http://tldp.org/LDP/intro-linux/intro-linux.pdf
If you D/L the PDF, you can search it for root, and learn a bit about it.

So you need to be the root user to use those commands I gave you in post #13. To do this with fedora you give the command "switch user", abbreviated to su like this:

su -

The "-" is there, so you inherit root's environment. You need this, although at the moment I appreciate you may have no idea what this means.

You will be asked for "root's password", you gave the system this when you installed. I hope you have remembered it. Once you have given the correct password you will be the root user.

You will notice that your prompt has changed, to remind you that you are root, all-powerful, and can trash your system with a 7 character command (that I'll leave you to discover for yourself), so be careful with what you type. To stop being the root user type exit at the terminal (.. and yes, you do have to press the return key for anything to happen). Then you will be back as yourself, do you notice the change in the prompt?

Type the commands I gave you. Do not prefix them with "/". They will be recognised by fedora when you are the root user. Otherwise, they won't, and you'll get an error message.

See how you get on.

[PAUSE]

I see you have posted whilst I am typing this. So .... .. .
Quote:

In answer to your posting number 12...
This is a link to the page I downloaded it from:
http://sourceforge.net/project/showf...group_id=82936
And FROM this page I downloaded THIS file: madwifi-0.9.4.tar.gz
Yes, I have already been there (I guessed it, sorry, but it needed confirming :) )

Quote:

I'd be interested to know why you place such importance on the source of the module/driver?
So I can find out just what exactly it is you have downloaded and what (if anything) needs to be done with it. In my post #13 I am saying that you probably do not need this download, it's probably already on your system. The instructions I gave you there are to see if this is indeed the case. Please try them out as the root user.

Quote:

Determining IP information for eth0... failed; no link present. Check cable
Means that it cannot bring up your wired connection because you have not plugged it in. If you had plugged in a cable, it would probably be working.
But you want wireless, sigh.

Quote:

Bringing up interface wlan0: SIOCSIFFLAGS: invalid argument. Failed.
Means that there is something wrong with your wireless interface. We are trying to fix that.

Finally:
Quote:

YOu mention an on/off switch. Would this be a physical switch on the case somewhere, or a virtual switch in the BIOS or something of that sort?
I have no idea. It could be any of the above, but, as usual, you are not providing any useful information: You have your PC listed as "Fujitsu-Siemens Esprimo Notebook" but which fscking one? Believe me I have been to their site (on your behalf), and there are lots of variations. I gave up, because I do not know your model number. It matters, especially with laptops as the hardware is often non-standard, and cut-down to save a bit of weight, and a "Fujitsu-Siemens Esprimo Notebook XXXYYYZZZ" is completely different from a "XXXYYYZZF". Otherwise they wouldn't have changed the model number, would they?

It's a bit like you posting "My car isn't working"
- "What type of car is it?"
- "It's a BMW"
- "Tell me more"
- "It's a 720, I think"
- "Ooooo Kaaaaaay: 720i, 720g, 720Tig, 720F1, ...."
I am making this up, but do you get the idea?

So, it's late for me now, a long day and I'm tired. Please print this out, and decide for yourself where the Q's are.
Make notes. Provide the requested information, and error messages. Then maybe we can make some progress.

Oh, one last thought: Please search for "Linux for CC" or even "Linux for dummies" (no offence meant) and read some introductory texts. You need to do some homework. I'll bet the first time you were confronted with a windows machine, you needed some help to work it. Maybe you found this yourself, maybe somebody helped you. Linux is no different.

Linux is not windows. It's not clicky-clicky, Yum it WORKS! I can watch TV, and IM my "friends", (Windows is a little slow sometimes but maybe that is because I am invaded by trojans, my bank account has been emptied, and I am spamming the world, but I don't care, I just plugged it in clicked "Yes" to everything and I'm HAAAPPPPY :) :) )

Linux is much better, but it takes some re-learning. Persevere, be prepared to learn (education probably wards off Alzheimer's :) ), and you'll be amply rewarded ;)

Now: Go and do your homework. Come back when you have done it. Help will be provided if you can show that you are able to help yourself by reading and learning. We all started where you are now. Then doors begin to open and I hope you'll walk through them and be content, as I am :)

Completely Clueless 04-08-2008 07:00 PM

Quote:

Originally Posted by tredegar (Post 3115104)
Now: Go and do your homework. Come back when you have done it. Help will be provided if you can show that you are able to help yourself by reading and learning. We all started where you are now. Then doors begin to open and I hope you'll walk through them and be content, as I am :)

Okay, well thanks.
There's an awful lot of information in your last post, and it will take some time for me to assimilate it - which I don't propose to do now as it's 1.00am here already and I don't want to piss you off by missing out any instruction.

Thanks for your input; I'll be back in due course - and hopefully a bit less Clueless.

CC.

tredegar 04-08-2008 08:00 PM

Quote:

There's an awful lot of information in your last post,
Yes there is, and you'll see that it took me quite some time to write it. But I'd like to help you leap the first hurdles, as others did for me waaaay back in time, when it was much more complicated than it is now.
Quote:

it will take some time for me to assimilate it
That's completely understandable. "Completely Clueless" I can understand and accept, and am more than willing to help but "Completely Helpless" or "Completely lazy" is a No No.

Don't get dispirited. There's no rush. Find the time to do a bit of homework. Experiment a little. Just try things out (you still have windows to go back to) until you are more comfortable with the way linux does things.

When you understand the concept of "Do this as root", please come back and reply to this thread, as we'll be ready and waiting to help you pick up from where we left off.

Quote:

I don't want to piss you off by missing out any instruction.
Sorry, but sometimes I too, get frustrated. "You can lead a horse to water but you can't make it drink". I am not "pissed off". I just *assumed* you knew about water. My mistake :(

Cheer up - linux is an adventure: lots to learn, puzzles to be solved, mistakes to be made, but in the end life (at least with wretched PCs) gets better.
Come back here whenever you are ready :)

Good luck.

Completely Clueless 04-09-2008 09:47 AM

Hi again,

I'm just about to execute the commands you suggested "as root" now you've explained what that means. It's obvious a lot of these problems I've been having seem to be caused by naming conventions rather than any fundamental lack of understanding on my part. Here again, there's a naming problem. "Root" to me as an escaping WhineDos luser means the root directory of C:\ from whence all other directories spread out. If you had simply said, "as administrator" rather than "as root" I would have known exactly what you meant! And yes, I am fully familiar with the directory tree structure! :-)

I do plead guilty on the imprecise description of the notebook, however. I'll alter my profile accordingly to leave no room for ambiguity. My apologies. I appreciate you're trying to save me from the nightmare future of MS style Big Brother slavery for which I am most thankful.

Now I shall enter the commands and see what comes back.

CC

Completely Clueless 04-09-2008 10:33 AM

Okay, now I have some outputs. Going back to your earlier post you suggested:

As root, try:
lsmod | grep ath
Q2] - Is anything listed?
If not, try inserting the module (as root again):
modprobe ath_pci
Once the module has loaded (it loads some others that are needed as well) try (again, as root)
iwlist scan
Q3] - What happens?

Here's the results:

[root@localhost ~]# lsmod | grep ath
dm_multipath 18249 0
ath5k 85197 0
mac80211 131409 2 rc80211_simple,ath5k
dm_mod 46209 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
[root@localhost ~]# modprobe ath_pci
FATAL: Module ath_pci not found.
[root@localhost ~]# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Interface doesn't support scanning : Network is down

[root@localhost ~]#


Obviously the commands you have suggested mean nothing to me. But if they are to get the system to look for the module, then ought it (the module) be copied over to someplace the system will expect to find it? At the moment It's still on the USB memory stick which whilst plugged into the notebook, may not be where the system is looking.

Any ideas?

CC.

tredegar 04-09-2008 11:47 AM

Ok, some progress.

Code:

[root@localhost ~]# lsmod | grep ath
 dm_multipath 18249 0
 ath5k 85197 0
 mac80211 131409 2 rc80211_simple,ath5k
 dm_mod 46209 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror

Well we do not see the module ath_pci, but we do see the module ath5k, which is another module that (maybe) can control your Atheros chipset. The ath5k homepage is here: http://madwifi.org/ It is still under development.

Code:

[root@localhost ~]# modprobe ath_pci
 FATAL: Module ath_pci not found.

The module ath_pci is not available on your system. It looks like fedora wants to use ath5k instead.

Code:

[root@localhost ~]# iwlist scan
 lo Interface doesn't support scanning.
 
 eth0 Interface doesn't support scanning.
 
 wmaster0 Interface doesn't support scanning.
 
 wlan0 Interface doesn't support scanning : Network is down

wlan0 looks as though it is the name of your wireless interface. But it "doesn't support scanning : Network is down"

So there is something wrong.

If you search for device 001c on this page http://madwifi.org/wiki/Compatibility/Atheros
you will see some data referring to an Atheros AR5007EG (which could well be your chipset [Edit:] Is your chipset, with PCI vendor/system IDs: 168c:001c [/Edit]) and references to some Fujitsu-Siemens computers (but not your exact one).
There are also comments like "Works perfectly with latest madwifi snapshot and this patch --> http://madwifi.org/ticket/1679 "

On that page there's also this link explaining how to get it to work with (k)ubuntu:
http://www.ubuntugeek.com/atheros-50...-platform.html

Unfortunately, (k)ubuntu handles networking setup very differently from Fedora. Applying (k)ubuntu network configuration to Fedora will not work, and I do not know Fedora, so I am unable to help you with specifics here. (My maintained distros are Debian / kubuntu).

But there is hope yet.

I searched around and found this page http://menkou.homelinux.net/serendip...f-the-box.html
which tells you how to install the ath_pci driver on F8, and they say it works.

Give it a go?

Quote:

Obviously the commands you have suggested mean nothing to me.
You can find out what any commands are with the man CommandName command. Eg:
man ifconfig or even
man man
[Page-up, Page-Down, q to Quit]
Or you could put man ifconfig into your search engine if you'd like a nicely formatted page in your browser.

Quote:

At the moment It's still on the USB memory stick which whilst plugged into the notebook,..
The module you have download is as source code. It will need compiling against your kernel before you can use it. Really, I'd rather not go there, as you are CC and I am unfamiliar with Fedora! Much easier is to use the link I gave you above, and install a precompiled module.

If you do need to compile the ath_pci module from source, I think you'll need to start another thread, because I can't help you here.

Best wishes & have fun ;)

Completely Clueless 04-09-2008 05:25 PM

Okay, thanks for that lot.

Since you think it best to try the solution described in the link you posted (http://menkou.homelinux.net/serendip...f-the-box.html) that is what I shall do. Having visited the site and checked the files are still available (and downloaded them) I will have a stab at it but it will take me a while to do so by the look of it.

Just a couple of final questions for the time being:

1). When installing any given Linux module on any PC., is there a particular location on the system that said module must be placed in order for it to be most easily found?

2). I read in some beginner's guide to Linux that irrespective of the distro, they all use a single, common kernel. Is that not true?

Thanks again for your help.

CC.

tredegar 04-09-2008 05:56 PM

Quote:

1). When installing any given Linux module on any PC., is there a particular location on the system that said module must be placed in order for it to be most easily found?
Different linux distros install things in different places. It depends on the distro. That's why it's usually better to use your distro's "package manager" to install any additional software you might need. Or download an rpm that matches your distro & kernel number. If that fails, compile-from-source always worked for me, but it's a PITA.

The .rpm's in that link should install themslves in the right places for your distro. But please check your kernel number, as it says on that page. It should match exactly. If it doesn't, perhaps you can search for one that does and then download that.

You have read http://tldp.org/LDP/intro-linux/intro-linux.pdf I take it?
It's homework :(

Quote:

2). I read in some beginner's guide to Linux that irrespective of the distro, they all use a single, common kernel. Is that not true?
This is off the topic of this thread. Please post that Q in "Linux-General" ;)

Completely Clueless 04-10-2008 08:00 AM

Oh, so package managers install modules as well as applications; that's useful to know.

I hadn't seen the pdf document you posted a link to before. It does look interesting, though, so I've saved a copy and will endeavour to work through it. Priorities first, though and I must get this wlan business sorted out!

Thanks again,

CC.

Completely Clueless 04-10-2008 02:43 PM

Okay, well I've now carried out the suggested solution from that third party site. Everything appeared to be in accordance with that guy's step-by-step instructions, but I regret to say still no change. :-(
However, in overcoming some unforeseen obstacles along the way, it became my first up-close-and-personal fiddle with Linux and though it was scarey at times, I quite enjoyed it. Took me to some unexpected (but useful and interesting places) too. :-) Pity there was no pay off, though. :-(

There's a log file (varlog) of highly detailed mumbo-jumbo that probably shows what went wrong, but it's very long. Even if I only post today's segment of it and I'm not sure what the LQ policy on posting long text files is.

If it's acceptable, I'll post the relevant part.

CC.

tredegar 04-10-2008 03:23 PM

Quote:

I'm not sure what the LQ policy on posting long text files is.
Neither am I, but they need to be split up, and become difficult to read.

You can post stuff like that to a site like this: http://rafb.net

Click the Paste link, Set your languge as "Plain Text", Give yourself a nickname, give it a description, Do not convert tabs, Paste in the log to the blank space, and finally click the Paste button. You should get a link to publish for us here.

It should stay available for us to read for 24 hours.

When you post the link, please also tell us the outputs of:
uname -a
ls /usr/src
which gcc

Thanks.

Glad you are having an interesting journey, maybe one day, we'll get you to your destination. Meanwhile, time for a bit more sightseeing?

Completely Clueless 04-10-2008 05:31 PM

Quote:

Originally Posted by tredegar (Post 3117142)
Neither am I, but they need to be split up, and become difficult to read.

You can post stuff like that to a site like this: http://rafb.net

Click the Paste link, Set your languge as "Plain Text", Give yourself a nickname, give it a description, Do not convert tabs, Paste in the log to the blank space, and finally click the Paste button. You should get a link to publish for us here.

It should stay available for us to read for 24 hours.

When you post the link, please also tell us the outputs of:
uname -a
ls /usr/src
which gcc

Thanks.

Glad you are having an interesting journey, maybe one day, we'll get you to your destination. Meanwhile, time for a bit more sightseeing?

Absolutely. Maybe I'll become hooked! At first glance it certainly 'feels' like a REAL *system* unlike Windoze, which always comes across a bit 'plasticy' like a kid's pedal car - and very matriarchal. For example:
"You do NOT have permission to access this file!"
"WTF do you mean? I OWN the Goddamn system! If I want to trash it, I can!!"
"Not possible! You're not the SuperUser!"
"Yes I am!! I have Administrator privileges! I bought this pile of junk OS for good money in perpetuity!"
"Your initials, for one thing, do not correspond to those of the SuperUser."
"What the hell are you talking about? What initials??"
"BG"
"Who??"
"Anyway, whatever you enter, however many times, you cannot change this file. Access is denied!"

Get this: I'm NOT joking. My 16 credit card accounts with FULL details were stuck inside this Windows SYSTEM file (yeah, you read that right) UNENCRYPTED - for any trojan to come along and steal. And worse still was that Windoze refused to even ackowledge said file existed! It didn't even show up under the 'reveal all files' system settings. It took 3rd party software to track it down and when it did it was in a WINDOWS SYSTEM FILE THAT IS NORMALLY "open" on the hard drive as unencrypted. What kind of security is THAT?????

Anyway, I'll stop the rant here because I could easily go on too far.

Until then, thanks again for the info, Tredegar. Since there's a strict time deadline of just 24 hours on this site you quote, I'd best post it (plus your output requests) with forewarning. So that'll now be sometime in the evening, UK-time tomorrow.

tredegar 04-10-2008 07:47 PM

Woah!

Rant off please, you are preaching to the converted: I quit at win98 ;)
Quote:

"You do NOT have permission to access this file!"
Linux can be bossy too, as you'll soon find out. But it usually has good reasons ;)

You can put your unencrypted credit card information into any linux PC, and it won't necessarily be any more secure than a windows PC, but at least you can find out how your OS is dealing with "security".

I don't want this thread to go "off-topic", so just post the outputs / log files / whatever so we can understand what it is you are trying to do ( = , I hope, "Get the Atheros wireless chipset working" rather than "Installing ethernet card driver", and read the error messages you are receiving and try to help you understand and resolve them.

When things go wrong with linux it doesn't just say "Unexpected error 0FF5F32". Blue Screen of Death. Die. Usually, there's something useful reported, that points you to the problem. But if you do not understand what the error messages mean, maybe we can help.

Now, I am going to be a bit "picky" here: There's no need to quote my entire previous entry to this thread: It's there for all to read in the thread, they've already read it, it doesn't need repeating. Just post your follow-up. You are free to say "in post #XYZ you said, but ...."

So, post the (long) error log to wherever, give us the link to it, and we'll do what we can to help you.
Welcome to the world of puzzle-solving. I hope you like to solve puzzles :)

Completely Clueless 04-11-2008 10:01 AM

Quote:

Originally Posted by tredegar (Post 3117364)
So, post the (long) error log to wherever, give us the link to it, and we'll do what we can to help you.
Welcome to the world of puzzle-solving. I hope you like to solve puzzles :)

Well, I do like solving puzzles, but would prefer to get some work done in between times! :-)

I expect to have the post up for around 7pm UK time tonight.

Thanks again,

CC.

Completely Clueless 04-11-2008 01:38 PM

Okay, pretty neat idea, that site. Please see:

http://rafb.net/p/PkAGzr38.html (

if that fails it's under "clueless" "log file")

I'll get the output info and post it here directly.

CC

tredegar 04-11-2008 01:46 PM

Errr, no.
That file, interesting though it is, looks as though it is your kernel boot message log.
It has nothing to do the the errors you may have received when trying to install ath_pci.

Perhaps you should just tell us what happened as you followed each step.

Completely Clueless 04-11-2008 02:32 PM

Quote:

Originally Posted by tredegar (Post 3118193)
Errr, no.
That file, interesting though it is, looks as though it is your kernel boot message log.
It has nothing to do the the errors you may have received when trying to install ath_pci.

Perhaps you should just tell us what happened as you followed each step.

Hang on! Something has changed during boot up. Give me 10 minutes....

Completely Clueless 04-11-2008 02:46 PM

Right, well. I can only report that I no longer get the wlan error message on boot-up. I still get the ethernet one (obviously) but that's all. When I go into "networks" it tells me I have an "inactive wlan wireless device" and under networks/hardware it says:

"ath_pci wireless wlan0 configured"

So that's definitely not as it was and the new driver has gone in, it seems! Funny thing is, this has only happened since I did a FULL restart. Certainly, that guy's suggestion of "restart network system" (only) didn't work by itself.

Anyway, it looks like a simple re-boot MAY have done the trick. But I can't say for sure. How should I proceed from here? I'm fortunately in an area where there are quite a few strong local wireless internet signals, incidentally.

CC.

Completely Clueless 04-11-2008 03:54 PM

Uh-oh.

Spoke too soon. Noticed an "activate" option box for the wlan device and get told it's not installed and wlan0.bak "not found."

This isn't a puzzle, it's a jinx.

CC.

tredegar 04-11-2008 06:13 PM

Quote:

When I go into "networks" it tells me I have an "inactive wlan wireless device" and under networks/hardware it says:

"ath_pci wireless wlan0 configured"
It looks as though the ath_pci module is handling your wireless chipset, because it is reported as "configured". To me, this means that your chipset is recognised, and responding. So this is a step forward. Maybe it now needs setting up with some details.

But what does "When I go into "networks"" mean? I am not runing Fedora8, and have no idea what it looks like, what you are clicking on, or what you are talking about. Grrrrr.

Quote:

How should I proceed from here? I'm fortunately in an area where there are quite a few strong local wireless internet signals, incidentally.
Some questions follow, but I am learning that you are not as good at answering as you are at asking.

0] How do you know that "there are quite a few strong local wireless internet signals"?
1] Which wireless network is yours?
2] What is the name (ESSID) of your wireless network?
3] How is your wireless Access Point configured?
4] What encryption are you using (WEP, WAP, Other?)
5] What channel is it using?
6] What have you tried to enable a connection to be made to your, presumably encrypted, wireless AP?

Quote:

Noticed an "activate" option box for the wlan device and get told it's not installed and wlan0.bak "not found."
7] Maybe you can clue me in here?

Completely Clueless 04-12-2008 08:24 AM

Quote:

Originally Posted by tredegar (Post 3118442)
But what does "When I go into "networks"" mean? I am not runing Fedora8, and have no idea what it looks like, what you are clicking on, or what you are talking about. Grrrrr.

It's a real pity you can't see what I'm seeing here. It would make life a lot simpler. Basically, from the Fedora desktop, there are 3 drop down menus on the title bar: Applications, Places and System. I go into System, then click on Administration, then Network. At this point I have to give the root password. Then up pops a dialogue box entitled Network Configuration. This has 4 tabs: Devices, Hardware, IPsec and Hosts. Under Devices there are 2 entries: ethernet and wireless (both are shown as "inactive") Under Hardware, again 2 devices: sis190/eth0 and ath_pci/wlan0 which has satus "configured" shown. Under IPsec, DNS and Hosts, nothing is entered.

Also in the top area of the box are two big buttons: Activate and Deactivate. If I check the wlan box and click "Activate" it first tells me "saving changes, restart required" but then shortly after and before I get the chance to restart, I get a pop up message from "System-config-network" saying "Cannot activate network device wlan0.bak! - ath_pci device wlan0 does not seem to be present, delaying initialization."

[QUOTE=tredegar;3118442]
0] How do you know that "there are quite a few strong local wireless internet signals"?

My wireless-enabled Windows laptop can pick them up. I'm in the middle of a large apartment block in a very built-up area.

1] Which wireless network is yours?

None of them. I don't have a network myself. I use internet cafes with wireless lans. They operate on a range of channels and my Windows laptop just scans the whole band and shows all the local signals and their respective strengths, whether they're encrypted or not and so forth.

I hope that's made things a little clearer.

Thanks,

CC.

tredegar 04-12-2008 09:45 AM

I can't help you with the GUI, I have no idea that the Fedora GUI tools do. But we can try to establish if the wireless is configured.
You'll need to be root to do these steps:

See if the ath5k module is still being loaded:
lsmod | grep ath5k
Remove it if it is:
rmmod ath5k
If you had to remove it, reload the ath_pci module:
rmmod ath_pci
modprobe ath_pci

See if your wireless can see any networks:
iwlist scan
See what your available interfaces are:
ifconfig

Completely Clueless 04-12-2008 10:46 AM

Okay, here we go:

The first and third commands generated no response to the screen:

[root@localhost ~]# lsmod | grep ath5k
[root@localhost ~]# rmmod ath5k
ERROR: Module ath5k does not exist in /proc/modules
[root@localhost ~]# modprobe ath_pci
[root@localhost ~]# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

[root@localhost ~]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3233 errors:0 dropped:0 overruns:0 frame:0
TX packets:3233 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2643328 (2.5 MiB) TX bytes:2643328 (2.5 MiB)

[root@localhost ~]#


These are the earlier outputs you requested (sorry for the delay)

[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:55:12 EDT 2007 i686 i686 i386 GNU/Linux
[root@localhost ~]# ls /usr/src
[root@localhost ~]# which gcc
/usr/bin/which: no gcc in (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
[root@localhost ~]#


NB: the second command generates no response to the screen.

tredegar 04-12-2008 11:47 AM

It is not working :(

Lots of people are having serious trouble getting the AR5007EG chipset to work. They can get other Atheros chipsets working, but not yours.
So far as google can tell me, nobody using Fedora8 has managed it :(
It may be time for you to try another distro...

missniceness got your chipset working with kubuntu by using ndiswrapper. ndiswrapper is a way of using the windows driver under linux. Her journal post is here:
http://missniceness.livejournal.com/

And search on that page for "Wireless is working!"

I don't think I can help you any further with fedora. Sorry :(
We tried, and you may have learnt something along the way.

Completely Clueless 04-12-2008 12:10 PM

Well, hey! We tried and I'm grateful for all the help you've provided anyway. At least I now know it's no failing on my part.

I'm not married to Fedora. I only went with it because Suse 10.3 couldn't see my hard drive. Have you any idea WHICH distro WOULD work with this laptop? I mean a full-blown distro with all the bells and whistles on it?

Once again, a big thanks.

tredegar 04-12-2008 12:28 PM

Maybe kubuntu 7.10 ?

(k)ubuntu is generally considered a newbie-friendly distro, but it has all the features I require, and as I said, I am very happy with 6.06 (now running as 6.2, I think, after all the updates.)

kubuntu 8.04 is still in "Beta", and so probably perhaps not the best to start with when you are new.
Whatever you choose, you are going to have trouble with your wireless chipset (As a general rule, only buy laptops with NVIDIA video (although ATI are supposedly getting better with linux support), intel video seems to be OK too, and Intel wireless - these manufacturers are very supportive of linux)

If you want to keep things fairly simple (recommended), I'd avoid the fancy 3D "glamour" of rotating cubic desktops and the like (AKA compiz fusion beryl etc.), as these are somewhat unreliable at the moment. Give them time though. Who knows, in another couple of months your AR5007EG may be fully supported by a native linux module, and the problems will be gone.

Good luck ;)

Completely Clueless 04-12-2008 06:31 PM

Okay, well I'll take some comfort from that! Just out of curiosity I have tried wlan capability with a Knoppix live CD and that doesn't recognize it either. I imagine that will be the case for the majority of distros. I'll take a gander at Kubuntu since you suggested it.

Once again, thanks for your valiant efforts.

CC

tredegar 04-13-2008 06:24 AM

Quote:

Just out of curiosity I have tried wlan capability with a Knoppix live CD and that doesn't recognize it either.
Hmmmm. knoppix is renowned for its excellent hardware detection, and "making it work", so if knoppix can't get your wireless working, it is a bad sign.

But, as I posted above missniceness got your wireless chipset working with kubuntu and ndiswrapper.
Take a look at her site for instructions, if they are not sufficiently clear, I expect you could politely email her for the full details.

Happy hacking!

Completely Clueless 04-13-2008 08:36 AM

THanks, I'll certainly take a look at what she's done.

CC.

tredegar 04-13-2008 08:49 AM

I already emailed her. This was her reply:
Quote:

Hello,

You know being that I'm not the "natural hacker" type....I sometimes do not
remember what I did....or if I did, I sometimes am not able to explain it
very well. However, I did do a livejournal post after I got it working
here:

http://missniceness.livejournal.com/158990.html

I do remember that it was not ndiswrapper that was the problem, rather the
driver. If I did not download that driver for my chipset (which
honestly...I had a tough time figuring out which one it was)...it would have
never worked.

Maybe that's the problem?

Oh I was using Feisty Fawn.
"Feisty Fawn" is kubuntu 7.04, but 7.10 should be OK too.
It was the correct windows driver that she needed to download, there's a link to it from her site. Then she had to use that driver by wrapping it up with ndiswrapper. So, if she made it work, so can you!

Completely Clueless 04-14-2008 08:35 AM

Hi,

Okay, well she's obviously inuitively better at these things than I am. I've noticed that from time to time with some people who have no formal qualifications but just a remarkable natural flair for getting things working (not saying misniceness is unqualified as I know nothing whatever about her, but it's just an observation that suddenly came to mind).

I think perhaps a better solution at this stage is to swap systems between laptops. I'll migrate my Windows system and data to the new laptop from the old one and install Linux in its place. (I KNOW Suse 10.3 installs on my old machine, which is a good sign). Maybe down the road aways I'll swap back once the newer hardware enjoys better Linux support...

Thanks again,

CC.


All times are GMT -5. The time now is 11:35 PM.