5:42 p.m.
When I do an ifconfig I only see eth0 and lo.
system-config-network only shows eth0
I know the Atheros card is there...
12:47 p.m.
Rodney Morris wrote:
On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
> Rodney Morris wrote:
>
>
>> On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
>>
>>
>>
>>> Rodney Morris wrote:
>>>
>>>
[trimmed]
>>>> The stock F10 kernel should support the ar5413, according to the ath5k
>>>> website.[1] Is the ath5k module being loaded? What does "lsmod |
>>>> grep ath" return?
>>>>
>>>>
>>>>
>>>>
>>>>
>>> dm_multipath 17164 0
>>> ath5k 112520 0
>>> mac80211 173668 1 ath5k
>>> cfg80211 23816 2 ath5k,mac80211
>>>
>>>
>>>
>>>
>> The ath5k module is definitely loaded. For NetworkManager to use your
>> wireless card, it must be present in HAL. Run "lshal" from the
>> command line and see if "atheros" or "ar5413" appears in the
output.
>>
>>
> No. Nothing like that there.
>
Hmmm. . .. Other than looking through the log file and dmesg for
anything odd, I only have a couple of more things for you to try.
1. Edit /etc/modprobe.conf and add "alias wifi0 ath5k", making sure
to include a blank line at the end of the file. Then, reboot.
NO /etc/modprobe.conf !!!!!!
Why? This is probably why no sound either!
#locate modprobe.conf
/etc/modprobe.d/modprobe.conf.dist
/sbin/generate-modprobe.conf
/usr/share/doc/irda-utils-0.9.18/modprobe.conf.irda
/usr/share/logwatch/default.conf/services/modprobe.conf
/usr/share/man/man5/modprobe.conf.5.gz
# ls -ls /etc/modprobe.d/
total 28
4 -rw-r--r-- 1 root root 52 2008-12-01 11:42 anaconda
4 -rw-r--r-- 1 root root 845 2008-07-23 06:25 blacklist
4 -rw-r--r-- 1 root root 16 2008-01-04 03:43 blacklist-visor
4 -rw-r--r-- 1 root root 26 2008-11-10 13:24 floppy-pnp
4 -rw-r--r-- 1 root root 177 2008-10-01 01:28 i915modeset
8 -rw-r--r-- 1 root root 5766 2008-10-13 06:11 modprobe.conf.dist
2. If you can obtain your wireless card's MAC address, add an
entry
to /etc/udev/rules.d/70-persistent-net, using what is listed for eth0
as a guide. (I don't know if modifying the udev rules in this manner
is considered the best practice.)
Well it looks like something is recognized:
# iwconfig wlan0
wlan0 IEEE 802.11b ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
# cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
face | tus | link level noise | nwid crypt frag retry misc | beacon | 22
wlan0: 0000 0 0 0 0 0 0 0 0 0
If neither of the above work, file a bug (my guess would be against
HAL or udev) and use the madwifi packages from rpmfusion or atrpms
until the bug is fixed.
Challenge with atrpms is kernel patching. I got to like the dkms
approach that is available via rpmforge for Centos. I was hoping that
things would be more integrated...
1:28 p.m.
On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
[snip]
> > 2. If you can obtain your wireless card's MAC address, add an entry
> > to /etc/udev/rules.d/70-persistent-net, using what is
> listed for eth0
> > as a guide. (I don't know if modifying the udev rules in this manner
> > is considered the best practice.)
> > > Well it looks like something
is recognized:
> # iwconfig wlan0
> wlan0 IEEE 802.11b ESSID:""
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Tx-Power=0 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> # cat /proc/net/wireless
> Inter-| sta-| Quality | Discarded packets | Missed | WE
> face | tus | link level noise | nwid crypt frag retry misc | beacon | 22
> wlan0: 0000 0 0 0 0 0 0 0 0 0
Are you now able to see access points using NetworkManager and
nm-applet? If not, does "iwlist wlan0 scan" list access points around
you?
> > If neither of the above
work, file a bug (my guess would be against
> > HAL or udev) and use the madwifi packages from rpmfusion or atrpms
> > until the bug is fixed.
> > Challenge with atrpms is
kernel patching. I got to like the dkms approach
> that is available via rpmforge for Centos. I was hoping that things would be
> more integrated...
If you like the dkms approach, you should check out the akmod-madwifi
packages in the rpmfusion repo. From my understanding, akmod packages
are similar to dkms packages in that a new module is compiled when a
new kernel is installed. I have yet to use any of the akmod packages.
I'm waiting till amd releases an fglrx driver that works with F10,
but that is another thread.
Rod
Rodney Morris wrote:
> On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
> > Rodney Morris wrote:
> > > >
> > On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
> > > > > > >
> > > > > Rodney Morris wrote:
> > > > > > > > > >
> > > [trimmed]
> >
> > > > >
> > > > The stock F10 kernel should support the ar5413, according to the
ath5k
> > > > > website.[1] Is the ath5k module being loaded? What does
"lsmod |
> > > > > grep ath" return?
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > dm_multipath 17164 0
> > > > ath5k 112520 0
> > > > mac80211 173668 1 ath5k
> > > > cfg80211 23816 2 ath5k,mac80211
> > > > > > > > > >
> > > > > > > > The ath5k module is definitely loaded. For
NetworkManager to use your
> > > wireless card, it must be present in HAL. Run "lshal" from the
> > > command line and see if "atheros" or "ar5413" appears
in the output.
> > > > > > >
> No. Nothing like that there.
> > >
Hmmm. . .. Other than looking through the log file and dmesg for
> anything odd, I only have a couple of more things for you to try.
> 1. Edit /etc/modprobe.conf and add "alias wifi0
ath5k", making sure
> to include a blank line at the end of the file. Then, reboot.
NO /etc/modprobe.conf !!!!!!
Why? This is probably why no sound either!
I was equally vexed when I found no /etc/modprobe.conf on my F10
installation. I needed to add an modprobe option for my case's LCD
display to work properly. Fortunately, creating the file and adding
the appropriate stanza worked.
7:12 a.m.
I've been following this thread, as I have the Atheros AR242x. My symptoms,
and output from each of the suggested commands, are very close to identical to
Robert's.
On Thursday 04 December 2008 22:01:31 Rodney Morris wrote:
I created my /etc/modprobe.conf using emacs and adding the single
stanza I needed. I do not know how to create a /etc/modprobe.conf
that would encompass all of the hardware on a machine (i.e. sound,
network adapters). However, I did notice in a previous post that you
had /sbin/generate-modprobe.conf installed. My google search for
information on generate-modprobe.conf was not particularly
enlightening. Perhaps you will have better luck.
I tried generate-modprobe.conf, and it returned
Cannot find old version of modprobe. Giving up.
Spectacularly useless, then.
Anne
12:53 p.m.
On Thu, Dec 04, 2008 at 01:47:57PM -0500, Robert Moskowitz wrote:
> If neither of the above work, file a bug (my guess would be
against
> HAL or udev) and use the madwifi packages from rpmfusion or atrpms
> until the bug is fixed.
Challenge with atrpms is kernel patching. I got to like the dkms
approach that is available via rpmforge for Centos. I was hoping that
things would be more integrated...
ATrpms doesn't do/need kernel patching. The kmdl are shipped as an add
on package for the supported kernels, you just install the kmdls and
if you also install yum/plugin-kmdl then yum will also keep up the
needed kmdls for future kernels.
And if you need a kmdl for you own specific breed of kernel packages
then you just grap the src.rpm and do an rpmbuild --rebuild on it.
--
Axel.Thimm at ATrpms.net
1:53 p.m.
Rodney Morris wrote:
On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
> Rodney Morris wrote:
>
>
>> On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
>>
>>
>>
>>> Rodney Morris wrote:
>>>
>>>
>>>
>>>
>>>> On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Rodney Morris wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>> [trimmed]
>>
>>
>>
>>>>>> The stock F10 kernel should support the ar5413, according to the
>>>>>>
> ath5k
>
>>>>>> website.[1] Is the ath5k module being loaded? What does
"lsmod |
>>>>>> grep ath" return?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> dm_multipath 17164 0
>>>>> ath5k 112520 0
>>>>> mac80211 173668 1 ath5k
>>>>> cfg80211 23816 2 ath5k,mac80211
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> The ath5k module is definitely loaded. For NetworkManager to use your
>>>> wireless card, it must be present in HAL. Run "lshal" from
the
>>>> command line and see if "atheros" or "ar5413" appears
in the output.
>>>>
>>>>
>>>>
>>>>
>>> No. Nothing like that there.
>>>
>>>
>>>
>> Hmmm. . .. Other than looking through the log file and dmesg for
>> anything odd, I only have a couple of more things for you to try.
>>
>> 1. Edit /etc/modprobe.conf and add "alias wifi0 ath5k", making sure
>> to include a blank line at the end of the file. Then, reboot.
>>
>>
>>
> NO /etc/modprobe.conf !!!!!!
>
> Why? This is probably why no sound either!
>
I was equally vexed when I found no /etc/modprobe.conf on my F10
installation. I needed to add an modprobe option for my case's LCD
display to work properly. Fortunately, creating the file and adding
the appropriate stanza worked.
So how do you start making /etc/modprobe.conf? And what to do for
Atheros and sound. the /etc/modprobe.conf on an identical unit running
Centos 5.2 has:
alias eth0 8139too
alias snd-card-0 snd-hda-intel
options snd-card-0 index=0
options snd-hda-intel index=0
remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ;
}; /sbin/modprobe -r --ignore-remove snd-hda-intel
>> 2. If you can obtain your wireless card's MAC address,
add an entry
>> to /etc/udev/rules.d/70-persistent-net, using what is
>>
> listed for eth0
>
>> as a guide. (I don't know if modifying the udev rules in this manner
>> is considered the best practice.)
>>
>>
>>
> Well it looks like something is recognized:
>
> # iwconfig wlan0
> wlan0 IEEE 802.11b ESSID:""
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Tx-Power=0 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> # cat /proc/net/wireless
> Inter-| sta-| Quality | Discarded packets | Missed | WE
> face | tus | link level noise | nwid crypt frag retry misc | beacon | 22
> wlan0: 0000 0 0 0 0 0 0 0 0 0
>
>
Are you now able to see access points using NetworkManager and
nm-applet? If not, does "iwlist wlan0 scan" list access points around
you?
#iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
No wlan0 interface it seems.
>
>> If neither of the above work, file a bug (my guess would be against
>> HAL or udev) and use the madwifi packages from rpmfusion or atrpms
>> until the bug is fixed.
>>
>>
> Challenge with atrpms is kernel patching. I got to like the dkms approach
> that is available via rpmforge for Centos. I was hoping that things would be
> more integrated...
>
>
If you like the dkms approach, you should check out the akmod-madwifi
packages in the rpmfusion repo. From my understanding, akmod packages
are similar to dkms packages in that a new module is compiled when a
new kernel is installed. I have yet to use any of the akmod packages.
I'm waiting till amd releases an fglrx driver that works with F10,
but that is another thread.
How closely linked is the compile of akmod packages and releases of new
kernels?
12:06 p.m.
On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
Rodney Morris wrote:
> On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
>
>
> > Rodney Morris wrote:
> >
[trimmed]
> > > The stock F10 kernel should support the ar5413,
according to the ath5k
> > > website.[1] Is the ath5k module being loaded? What does "lsmod |
> > > grep ath" return?
> > >
> > >
> > >
> > >
> > dm_multipath 17164 0
> > ath5k 112520 0
> > mac80211 173668 1 ath5k
> > cfg80211 23816 2 ath5k,mac80211
> >
> >
> >
>
> The ath5k module is definitely loaded. For NetworkManager to use your
> wireless card, it must be present in HAL. Run "lshal" from the
> command line and see if "atheros" or "ar5413" appears in the
output.
>
No. Nothing like that there.
Hmmm. . .. Other than looking through the log file and dmesg for
anything odd, I only have a couple of more things for you to try.
1. Edit /etc/modprobe.conf and add "alias wifi0 ath5k", making sure
to include a blank line at the end of the file. Then, reboot.
2. If you can obtain your wireless card's MAC address, add an entry
to /etc/udev/rules.d/70-persistent-net, using what is listed for eth0
as a guide. (I don't know if modifying the udev rules in this manner
is considered the best practice.)
If neither of the above work, file a bug (my guess would be against
HAL or udev) and use the madwifi packages from rpmfusion or atrpms
until the bug is fixed.
Rod
11:06 a.m.
Rodney Morris wrote:
On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
> Rodney Morris wrote:
>
>
>> On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
>>
>>
>>> iarly selbir wrote:
>>>
>>>
>>>
>>>> check if exists this file:
>>>>
>>>> /etc/sysconfig/network-scripts/ifcfg-wlan0
>>>>
>>>>
>>>>
>>>>
>>> No it does not exist. And I have been crafting ifcfg-<interface>
files
>>>
> for
>
>>> years so I know why I need these. How does this get created in F10?
>>>
> Given
>
>>> that this is a madwifi, is there any other file needed? (my experience
>>>
> is
>
>>> limited to Centos 5 so I am use to seeing ath0 and wifi0 interfaces).
>>>
>>>
>>>
>>>
>> The stock F10 kernel should support the ar5413, according to the ath5k
>> website.[1] Is the ath5k module being loaded? What does "lsmod |
>> grep ath" return?
>>
>>
>>
> dm_multipath 17164 0
> ath5k 112520 0
> mac80211 173668 1 ath5k
> cfg80211 23816 2 ath5k,mac80211
>
>
The ath5k module is definitely loaded. For NetworkManager to use your
wireless card, it must be present in HAL. Run "lshal" from the
command line and see if "atheros" or "ar5413" appears in the output.
No. Nothing like that there.
10:46 a.m.
On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
Rodney Morris wrote:
> On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
>
>
> > iarly selbir wrote:
> >
> >
> >
> > > check if exists this file:
> > >
> > > /etc/sysconfig/network-scripts/ifcfg-wlan0
> > >
> > >
> > >
> > No it does not exist. And I have been crafting ifcfg-<interface> files
for
> > years so I know why I need these. How does this get created in F10?
Given
> > that this is a madwifi, is there any other file needed? (my experience
is
> > limited to Centos 5 so I am use to seeing ath0 and wifi0 interfaces).
> >
> >
> >
>
> The stock F10 kernel should support the ar5413, according to the ath5k
> website.[1] Is the ath5k module being loaded? What does "lsmod |
> grep ath" return?
>
>
dm_multipath 17164 0
ath5k 112520 0
mac80211 173668 1 ath5k
cfg80211 23816 2 ath5k,mac80211
The ath5k module is definitely loaded. For NetworkManager to use your
wireless card, it must be present in HAL. Run "lshal" from the
command line and see if "atheros" or "ar5413" appears in the output.
Rod
10:03 a.m.
Rodney Morris wrote:
On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
> iarly selbir wrote:
>
>
>> check if exists this file:
>>
>> /etc/sysconfig/network-scripts/ifcfg-wlan0
>>
>>
> No it does not exist. And I have been crafting ifcfg-<interface> files for
> years so I know why I need these. How does this get created in F10? Given
> that this is a madwifi, is there any other file needed? (my experience is
> limited to Centos 5 so I am use to seeing ath0 and wifi0 interfaces).
>
>
The stock F10 kernel should support the ar5413, according to the ath5k
website.[1] Is the ath5k module being loaded? What does "lsmod |
grep ath" return?
dm_multipath 17164 0
ath5k 112520 0
mac80211 173668 1 ath5k
cfg80211 23816 2 ath5k,mac80211
9:45 a.m.
On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
iarly selbir wrote:
> check if exists this file:
>
> /etc/sysconfig/network-scripts/ifcfg-wlan0
>
No it does not exist. And I have been crafting ifcfg-<interface> files for
years so I know why I need these. How does this get created in F10? Given
that this is a madwifi, is there any other file needed? (my experience is
limited to Centos 5 so I am use to seeing ath0 and wifi0 interfaces).
The stock F10 kernel should support the ar5413, according to the ath5k
website.[1] Is the ath5k module being loaded? What does "lsmod |
grep ath" return?
Rod
[1] http://linuxwireless.org/en/users/Drivers/ath5k
7:57 a.m.
This helped me with fc9.
http://kernelreloaded.blog385.com/index.php/archives/madwifi-wireless-for...
Regards,
---------------------------------------------
iarly Selbir ( Ski0s )
On Thu, Dec 4, 2008 at 10:38 AM, Robert Moskowitz <rgm(a)htt-consult.com>wrote:
iarly selbir wrote:
> check if exists this file:
>
> /etc/sysconfig/network-scripts/ifcfg-wlan0
>
No it does not exist. And I have been crafting ifcfg-<interface> files for
years so I know why I need these. How does this get created in F10? Given
that this is a madwifi, is there any other file needed? (my experience is
limited to Centos 5 so I am use to seeing ath0 and wifi0 interfaces).
> if yes.
>
> verify if exists this line on the file:
>
> NM_CONTROLLED=yes
>
>
> Regards,
>
> ---------------------------------------------
> iarly Selbir ( Ski0s )
>
>
>
> On Thu, Dec 4, 2008 at 9:46 AM, Robert Moskowitz <rgm(a)htt-consult.com<mailto:
> rgm(a)htt-consult.com>> wrote:
>
> iarly selbir wrote:
>
> run the command lspci and see if the "atheros" appears on the
> output
>
>
> Example, my lspci:
>
> 0c:00.0 Ethernet controller: Atheros Communications Inc.
> AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
>
>
> It does.
> 03:04.0 Ethernet controller: Atheros Communications Inc. AR5413
> 802.11abg NIC (rev 01)
> Subsystem: Atheros Communications Inc. EnGenius EMP-8602
> (400mw) or Compex WLM54AG (SuperAG)
> Flags: bus master, medium devsel, latency 168, IRQ 17
> Memory at c2100000 (32-bit, non-prefetchable) [size=64K]
> Capabilities: [44] Power Management version 2
> Kernel driver in use: ath5k_pci
> Kernel modules: ath5k
>
>
> Now what? How do I define the interface so I can bring it up? And
> so NetworkManager will recognize it?
>
>
>
> Regards,
>
> ---------------------------------------------
> iarly Selbir ( Ski0s )
>
>
>
>
> On Wed, Dec 3, 2008 at 8:42 PM, Robert Moskowitz
> <rgm(a)htt-consult.com <mailto:rgm@htt-consult.com>
> <mailto:rgm@htt-consult.com <mailto:rgm@htt-consult.com>>>
wrote:
>
> When I do an ifconfig I only see eth0 and lo.
>
> system-config-network only shows eth0
>
> I know the Atheros card is there...
>
>
> -- fedora-list mailing list
> fedora-list(a)redhat.com <mailto:fedora-list@redhat.com>
> <mailto:fedora-list@redhat.com <mailto:fedora-list@redhat.com>>
>
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines:
> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>
>
>
> -- fedora-list mailing list
> fedora-list(a)redhat.com <mailto:fedora-list@redhat.com>
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines:
> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>
>
>
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
7:38 a.m.
iarly selbir wrote:
check if exists this file:
/etc/sysconfig/network-scripts/ifcfg-wlan0
No it does not exist. And I have been crafting ifcfg-<interface> files
for years so I know why I need these. How does this get created in
F10? Given that this is a madwifi, is there any other file needed? (my
experience is limited to Centos 5 so I am use to seeing ath0 and wifi0
interfaces).
if yes.
verify if exists this line on the file:
NM_CONTROLLED=yes
Regards,
---------------------------------------------
iarly Selbir ( Ski0s )
On Thu, Dec 4, 2008 at 9:46 AM, Robert Moskowitz <rgm(a)htt-consult.com
<mailto:rgm@htt-consult.com>> wrote:
iarly selbir wrote:
run the command lspci and see if the "atheros" appears on the
output
Example, my lspci:
0c:00.0 Ethernet controller: Atheros Communications Inc.
AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
It does.
03:04.0 Ethernet controller: Atheros Communications Inc. AR5413
802.11abg NIC (rev 01)
Subsystem: Atheros Communications Inc. EnGenius EMP-8602
(400mw) or Compex WLM54AG (SuperAG)
Flags: bus master, medium devsel, latency 168, IRQ 17
Memory at c2100000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Kernel driver in use: ath5k_pci
Kernel modules: ath5k
Now what? How do I define the interface so I can bring it up? And
so NetworkManager will recognize it?
Regards,
---------------------------------------------
iarly Selbir ( Ski0s )
On Wed, Dec 3, 2008 at 8:42 PM, Robert Moskowitz
<rgm(a)htt-consult.com <mailto:rgm@htt-consult.com>
<mailto:rgm@htt-consult.com <mailto:rgm@htt-consult.com>>> wrote:
When I do an ifconfig I only see eth0 and lo.
system-config-network only shows eth0
I know the Atheros card is there...
-- fedora-list mailing list
fedora-list(a)redhat.com <mailto:fedora-list@redhat.com>
<mailto:fedora-list@redhat.com <mailto:fedora-list@redhat.com>>
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
fedora-list mailing list
fedora-list(a)redhat.com <mailto:fedora-list@redhat.com>
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
6:54 a.m.
check if exists this file:
/etc/sysconfig/network-scripts/ifcfg-wlan0
if yes.
verify if exists this line on the file:
NM_CONTROLLED=yes
Regards,
---------------------------------------------
iarly Selbir ( Ski0s )
On Thu, Dec 4, 2008 at 9:46 AM, Robert Moskowitz <rgm(a)htt-consult.com>wrote:
iarly selbir wrote:
> run the command lspci and see if the "atheros" appears on the output
>
>
> Example, my lspci:
>
> 0c:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg
> Wireless PCI Express Adapter (rev 01)
>
It does.
03:04.0 Ethernet controller: Atheros Communications Inc. AR5413 802.11abg
NIC (rev 01)
Subsystem: Atheros Communications Inc. EnGenius EMP-8602 (400mw) or
Compex WLM54AG (SuperAG)
Flags: bus master, medium devsel, latency 168, IRQ 17
Memory at c2100000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Kernel driver in use: ath5k_pci
Kernel modules: ath5k
Now what? How do I define the interface so I can bring it up? And so
NetworkManager will recognize it?
> Regards,
>
> ---------------------------------------------
> iarly Selbir ( Ski0s )
>
>
>
> On Wed, Dec 3, 2008 at 8:42 PM, Robert Moskowitz <rgm(a)htt-consult.com<mailto:
> rgm(a)htt-consult.com>> wrote:
>
> When I do an ifconfig I only see eth0 and lo.
>
> system-config-network only shows eth0
>
> I know the Atheros card is there...
>
>
> -- fedora-list mailing list
> fedora-list(a)redhat.com <mailto:fedora-list@redhat.com>
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines:
> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>
>
>
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
6:46 a.m.
iarly selbir wrote:
run the command lspci and see if the "atheros" appears on
the output
Example, my lspci:
0c:00.0 Ethernet controller: Atheros Communications Inc. AR242x
802.11abg Wireless PCI Express Adapter (rev 01)
It does.
03:04.0 Ethernet controller: Atheros Communications Inc. AR5413
802.11abg NIC (rev 01)
Subsystem: Atheros Communications Inc. EnGenius EMP-8602 (400mw)
or Compex WLM54AG (SuperAG)
Flags: bus master, medium devsel, latency 168, IRQ 17
Memory at c2100000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Kernel driver in use: ath5k_pci
Kernel modules: ath5k
Now what? How do I define the interface so I can bring it up? And so
NetworkManager will recognize it?
Regards,
---------------------------------------------
iarly Selbir ( Ski0s )
On Wed, Dec 3, 2008 at 8:42 PM, Robert Moskowitz <rgm(a)htt-consult.com
<mailto:rgm@htt-consult.com>> wrote:
When I do an ifconfig I only see eth0 and lo.
system-config-network only shows eth0
I know the Atheros card is there...
--
fedora-list mailing list
fedora-list(a)redhat.com <mailto:fedora-list@redhat.com>
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
5:12 a.m.
run the command lspci and see if the "atheros" appears on the output
Example, my lspci:
0c:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg
Wireless PCI Express Adapter (rev 01)
Regards,
---------------------------------------------
iarly Selbir ( Ski0s )
On Wed, Dec 3, 2008 at 8:42 PM, Robert Moskowitz <rgm(a)htt-consult.com>wrote:
When I do an ifconfig I only see eth0 and lo.
system-config-network only shows eth0
I know the Atheros card is there...
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
4:01 p.m.
On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
Rodney Morris wrote:
> On 12/4/08, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
[snip]
> > > Hmmm. . .. Other than looking through the log file
and dmesg for
> > > anything odd, I only have a couple of more things for you to try.
> > >
> > > 1. Edit /etc/modprobe.conf and add "alias wifi0 ath5k", making
sure
> > > to include a blank line at the end of the file. Then, reboot.
> > >
> > >
> > >
> > >
> > NO /etc/modprobe.conf !!!!!!
> >
> > Why? This is probably why no sound either!
> >
> >
>
> I was equally vexed when I found no /etc/modprobe.conf on my F10
> installation. I needed to add an modprobe option for my case's LCD
> display to work properly. Fortunately, creating the file and adding
> the appropriate stanza worked.
>
>
So how do you start making /etc/modprobe.conf? And what to do for Atheros
and sound. the /etc/modprobe.conf on an identical unit running Centos 5.2
has:
I created my /etc/modprobe.conf using emacs and adding the single
stanza I needed. I do not know how to create a /etc/modprobe.conf
that would encompass all of the hardware on a machine (i.e. sound,
network adapters). However, I did notice in a previous post that you
had /sbin/generate-modprobe.conf installed. My google search for
information on generate-modprobe.conf was not particularly
enlightening. Perhaps you will have better luck.
> >
> > > 2. If you can obtain your wireless card's MAC address, add an entry
> > > to /etc/udev/rules.d/70-persistent-net, using what is
> > >
> > >
> > listed for eth0
> >
> >
> > > as a guide. (I don't know if modifying the udev rules in this manner
> > > is considered the best practice.)
> > >
> > >
> > >
> > >
> > Well it looks like something is recognized:
> >
> > # iwconfig wlan0
> > wlan0 IEEE 802.11b ESSID:""
> > Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> > Tx-Power=0 dBm
> > Retry min limit:7 RTS thr:off Fragment thr=2352 B
> > Encryption key:off
> > Power Management:off
> > Link Quality:0 Signal level:0 Noise level:0
> > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> > Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> >
> > # cat /proc/net/wireless
> > Inter-| sta-| Quality | Discarded packets | Missed | WE
> > face | tus | link level noise | nwid crypt frag retry misc | beacon |
22
> > wlan0: 0000 0 0 0 0 0 0 0 0 0
> >
> >
> >
>
> Are you now able to see access points using NetworkManager and
> nm-applet? If not, does "iwlist wlan0 scan" list access points around
> you?
>
>
#iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
No wlan0 interface it seems.
Hmmm. . . What do the system logs have to say about the wireless card
and/or NetworkManager (assuming that you have NetworkManager on)? Do
the logs show that a HW killswitch is active? Do the logs show
NetworkManager attempting to bring up wlan0 or eth0? If so, please
post those sections of the logs here.
> >
> > > If neither of the above work, file a bug (my guess would be against
> > > HAL or udev) and use the madwifi packages from rpmfusion or atrpms
> > > until the bug is fixed.
> > >
> > >
> > >
> > Challenge with atrpms is kernel patching. I got to like the dkms
approach
> > that is available via rpmforge for Centos. I was hoping that things
would be
> > more integrated...
> >
> >
> >
>
> If you like the dkms approach, you should check out the akmod-madwifi
> packages in the rpmfusion repo. From my understanding, akmod packages
> are similar to dkms packages in that a new module is compiled when a
> new kernel is installed. I have yet to use any of the akmod packages.
> I'm waiting till amd releases an fglrx driver that works with F10,
> but that is another thread.
>
How closely linked is the compile of akmod packages and releases of new
kernels?
That I don't know. I have not used them and, thus, have no experience
with akmods. Someone on the rpmfusion list could probably answer that
question.
Rod
5627
days inactive
5631
days old
16 comments
5 participants
participants (5)
-
Anne Wilson -
Axel Thimm -
iarly selbir -
Robert Moskowitz -
Rodney Morris