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