On Wed, Jun 4, 2008 at 10:44 AM, Paul Johnson [EMAIL PROTECTED] wrote:
2008/5/29 Robert Cahn [EMAIL PROTECTED]:
I have updated my desktop using the 64-bit desktop of F9 from F7. My
wireless is described by:
00:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
chipset
2008/5/29 Robert Cahn [EMAIL PROTECTED]:
I have updated my desktop using the 64-bit desktop of F9 from F7. My
wireless is described by:
00:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset
(rev 01)
Subsystem: Netgear MA311 802.11b wireless adapter
Flags: bus
On Fri, May 30, 2008 at 3:09 PM, Patrick O'Callaghan [EMAIL PROTECTED]
wrote:
On Fri, 2008-05-30 at 13:46 +0100, Timothy Murphy wrote:
The NM developers suffer from the delusion
that NM always works.
Of course it always works. Says so right here in the man page :-)
poc
--
fedora-list
Marc Ferguson wrote:
I did the iwlist scan and I noticed it did scans for: lo, eth1, wifi0,
eth0, irda0, and pan0. My wireless device, according to Network
Configuration is eth0. I find that weird; in prior distros wireless
devices where labeled wlan0, wlan1, etc.
The scan did pick up
As A test I downloaded Fedora-8-Live-x86_64 iso. When I boot from this disk
all the wireless problems go away. It connects immediately. In F9 the
services have been changed. There is a Network Manager but no
NetworkManagerDispatcher. That would seem to indicate a major rewrite.
This test
On Fri, 2008-05-30 at 13:46 +0100, Timothy Murphy wrote:
The NM developers suffer from the delusion
that NM always works.
Of course it always works. Says so right here in the man page :-)
poc
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe:
On Wed, 2008-05-28 at 23:00 -0430, Patrick O'Callaghan wrote:
On Wed, 2008-05-28 at 21:31 -0400, Marc Ferguson wrote:
Hi,
The PATH variable seems to already have a value in it:
PATH=$PATH:$HOME/bin
I should hope so. $PATH is where the Shell looks for commands to
execute. It's a
On Wed, 2008-05-28 at 21:09 -0400, Marc Ferguson wrote:
I tried the lspci command, but it says command not found. I'm
logged in as root, in the terminal. Also; ifconfig, iwconfig are not
found either? How do I get these back.
How did you log in? I'm guessing you used su rather than su -.
Yes I did log in using su, what's the difference with the - option?
Well I did get the lspci command to work. I exported it to a text
file. As soon as I get to work I'll post the result. Thanks for the
detailed help. VI is a very cool application, but hard to figure out
at first. I spent a couple
Hi,
The PATH variable seems to already have a value in it:
PATH=$PATH:$HOME/bin
Add the actual path after what's there, i.e.
PATH=$PATH:$HOME/bin:/search/path/1:/search/path/2
As for the locate command I got this error:
locate: can not open '/var/lib/mlocate/mlocate.db' : No such file
Yes I did log in using su, what's the difference with the - option?
Well I did get the lspci command to work. I exported it to a text
file. As soon as I get to work I'll post the result. Thanks for the
detailed help. VI is a very cool application, but hard to figure out
at first. I spent a
On Thu, May 29, 2008 at 9:53 AM, Mike Burger [EMAIL PROTECTED]
wrote:
Yes I did log in using su, what's the difference with the - option?
Well I did get the lspci command to work. I exported it to a text
file. As soon as I get to work I'll post the result. Thanks for the
detailed help.
On Thu, May 29, 2008 at 12:58 PM, Patrick O'Callaghan [EMAIL PROTECTED]
wrote:
On Thu, 2008-05-29 at 12:22 -0400, Matthew Saltzman wrote:
On Thu, 2008-05-29 at 08:18 -0430, Patrick O'Callaghan wrote:
On Thu, 2008-05-29 at 05:15 -0400, Matthew Saltzman wrote:
On Wed, 2008-05-28 at 23:00
On Thu, 2008-05-29 at 10:20 -0400, Marc Ferguson wrote:
Excellent, thanks for that info. Here is the result of lspci:
02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
chipset
(rev 01)
Subsystem: Actiontec Electronics Inc Unknown device 2406
Flags: bus master,
On Thu, May 29, 2008 at 2:41 PM, Patrick O'Callaghan [EMAIL PROTECTED]
wrote:
On Thu, 2008-05-29 at 10:20 -0400, Marc Ferguson wrote:
Excellent, thanks for that info. Here is the result of lspci:
02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
chipset
(rev 01)
I have updated my desktop using the 64-bit desktop of F9 from F7. My
wireless is described by:
00:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset
(rev 01)
Subsystem: Netgear MA311 802.11b wireless adapter
Flags: bus master, medium devsel, latency 32, IRQ 18
On Thu, 2008-05-29 at 14:56 -0400, Marc Ferguson wrote:
The scan did pick up something for wifi0 and eth0. Does that mean
that they are conflicting in some way?
I don't think so. AFAIK the wifi0 is effectively a pseudo-interface on
top of eth0. Something to do with how the kernel drivers are
What wireless card do you have in your laptop?
Olusola
*I would like to know if anyone is having problems getting their wireless
connection to actually connect in Fedora 9 using Network Manager?*
I just installed Fedora 9 on my laptop (Thinkpad R40). I did not do the 76
updates yet, but
I have, based on my system-config-network, an Intersil Corporation
Pri. To be honest - I'm not too clear what I have.
On 5/28/08, Olusola Fadero [EMAIL PROTECTED] wrote:
What wireless card do you have in your laptop?
Olusola
*I would like to know if anyone is having problems getting
On Wed, 2008-05-28 at 21:31 -0400, Marc Ferguson wrote:
Hi,
The PATH variable seems to already have a value in it:
PATH=$PATH:$HOME/bin
I should hope so. $PATH is where the Shell looks for commands to
execute. It's a list of directories to look in.
lspci and friends are in /sbin (or
20 matches
Mail list logo
