2008/5/7 Aaron Konstam <akonstam@sbcglobal.net>:

> No I am wrong. nm-applet runs as the user. I am now not sure what causes
> it to run.

/etc/xdg/autostart/nm-appet.desktop

No idea how to override it; normally I just delete it.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

John W. Linville wrote:

On Mon, May 05, 2008 at 08:19:56PM -0400, Mail Lists wrote:




http://koji.fedoraproject.org/koji/buildinfo?buildID=47941

Hth!

John



Unfortunately i have a laptop with a new nvidia graphics chip that
the nv driver does not have a clue about - so I have to use the nvidia
driver - any idea when these might roll into mainline ?





--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Wed, May 7, 2008 at 2:09 PM, Mail Lists <lists@sapience.com> wrote:
> John W. Linville wrote:
>>
>> On Mon, May 05, 2008 at 08:19:56PM -0400, Mail Lists wrote:
>>
>>
>> http://koji.fedoraproject.org/koji/buildinfo?buildID=47941
>>
>> Hth!
>>
>> John
>>
>
> Unfortunately i have a laptop with a new nvidia graphics chip that the nv
> driver does not have a clue about - so I have to use the nvidia driver -
> any idea when these might roll into mainline ?

Stop using livna rpms for nvidia. Install the freshrpms nvidia
framework and the Fedora dkms package. That will rebuild the kernel
module for you when you restart a new kernel. I installed that about 2
months ago on 2 machines and it has worked perfectly through 2 kernel
updates.

pj

--
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

John W. Linville wrote:

O
You may wish to try the latest available F8 kernel in Fedora. It has
some recent fixes that have improved the situation for a number of
iwl3945 and iwl4965 users (but not all of them):

http://koji.fedoraproject.org/koji/buildinfo?buildID=47941

Hth!

John


Just tried kernel-2.6.24.7-92.fc8
Same problem.
The magic does not always work - same with latest kernel

It is quite frustrating not to be able to use wireless ... sniff sniff.

Any other suggestions ?


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Mail Lists wrote:

John W. Linville wrote:

O
You may wish to try the latest available F8 kernel in Fedora. It has
some recent fixes that have improved the situation for a number of
iwl3945 and iwl4965 users (but not all of them):

http://koji.fedoraproject.org/koji/buildinfo?buildID=47941

Hth!

John


Just tried kernel-2.6.24.7-92.fc8
Same problem.
The magic does not always work - same with latest kernel

It is quite frustrating not to be able to use wireless ... sniff sniff.

Any other suggestions ?



Hi,

I am having a similar experience. My wireless network worked with kernel
2.6.24.4-64 and prior versions, but it does not start at boot with
kernel 2.6.24.5-85. Neither does it startup when booting with kernel
2.6.24.7-92. I can start my iwl4965 (aliased in modprobe.conf to wlan0)
manually by executing the following commands:


iwconfig wlan0 ap xx:xx:xx:xx:xx:xx
iwconfig wlan0 channel 11
/etc/rc.d/init.d/network restart

where, of course, I enter my access point's mac address. I am not using
NetworkManager.


It would appear that something was reordered surrounding the wireless
card startup at 2.6.24.5-85. Here are snippets around the network
messages from my dmesg output after booting in each of the three most
recent kernel builds.


2.6.24.4-64 (iwl4965 wireless starts up at boot)

firewire_ohci: Added fw-ohci device 0000:09:01.0, OHCI version 1.0
sdhci: SDHCI controller found at 0000:09:01.1 [1180:0822] (rev 22)
ACPI: PCI Interrupt 0000:09:01.1[b] -> GSI 17 (level, low) -> IRQ 17
sdhci:slot0: Will use DMA mode even though HW doesn't fully claim to
support it.

mmc0: SDHCI at 0xfeaff400 irq 17 DMA
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.26kds
iwl4965: Copyright(c) 2003-2008 Intel Corporation
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:04:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-4965-rs'
usb 4-2: new full speed USB device using uhci_hcd and address 2
...
ip_tables: (C) 2000-2006 Netfilter Core Team
ADDRCONF(NETDEV_UP): eth0: link is not ready
usb 4-2: USB disconnect, address 2
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP xx:xx:xx:xx:xx:xx
wlan0: RX authentication from xx:xx:xx:xx:xx:xx (alg=0 transaction=2
status=0)

wlan0: authenticated
wlan0: associate with AP xx:xx:xx:xx:xx:xx
wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x431 status=0 aid=5)
wlan0: associated
wlan0: CTS protection enabled (BSSID=xx:xx:xx:xx:xx:xx)
wlan0: switched to long barker preamble (BSSID=xx:xx:xx:xx:xx:xx)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
fuse init (API version 7.9)

2.6.24.5-85 (wireless does not startup)

firewire_ohci: Added fw-ohci device 0000:09:01.0, OHCI version 1.0
usb 4-2: new full speed USB device using uhci_hcd and address 2
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.26kds
iwl4965: Copyright(c) 2003-2008 Intel Corporation
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:01:00.0 to 64
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 169.12 Thu Feb 14
17:51:09 PST 2008

ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:04:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
firewire_core: created device fw0: GUID 00e0180003a38746, S400
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-4965-rs'
ACPI: PCI interrupt for device 0000:04:00.0 disabled
input: 4965AGN as /class/input/input8
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
...
ip_tables: (C) 2000-2006 Netfilter Core Team
ADDRCONF(NETDEV_UP): eth0: link is not ready
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
usb 4-2: USB disconnect, address 2
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
fuse init (API version 7.9)

2.6.24.7-92 (wireless does not startup)

ACPI: PCI Interrupt 0000:09:01.1[b] -> GSI 17 (level, low) -> IRQ 17
sdhci:slot0: Will use DMA mode even though HW doesn't fully claim to
support it.

mmc0: SDHCI at 0xfeaff400 irq 17 DMA
ACPI: PCI Interrupt 0000:09:01.0[A] -> GSI 16 (level, low) -> IRQ 16
firewire_ohci: Added fw-ohci device 0000:09:01.0, OHCI version 1.0
input: Video Bus as /class/input/input7
ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.26kds
iwl4965: Copyright(c) 2003-2008 Intel Corporation
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:04:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-4965-rs'
usb 4-2: new full speed USB device using uhci_hcd and address 2
ACPI: PCI interrupt for device 0000:04:00.0 disabled
input: 4965AGN as /class/input/input8
firewire_core: created device fw0: GUID 00e0180003a38746, S400
...
ip_tables: (C) 2000-2006 Netfilter Core Team
usb 4-2: USB disconnect, address 2
ADDRCONF(NETDEV_UP): eth0: link is not ready
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ACPI: PCI interrupt for device 0000:04:00.0 disabled
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
fuse init (API version 7.9)


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Mail Lists wrote:


I have F8 installed on a new Lenovo T61p with a 4965 wireless. I
have the following odd behaviour. There are 3 AP's in on the same
network - in fact no others are within scan range.


I


Ok after much experimentation - I now have the magic recipe to
connect which seems to work.


(i) Set up appropriate configs (ie populate
/etc/sysconfig/network-scripts/ifcfg*


(ii) ifup wlan0 ; ifdown wlan0

(iii) modprobe -r iwl4965
(iv) turn radio off with hardware switch
(v) turn on radio
(vi) iwconfig wlan0 channel 11
Adjust to channle of close AP
(vii) iwlist wlan0 scan

This will fail - repeat - it may still not see the AP that is
close - repeat until you see the AP picked up in the scan.

If you cannot see the AP - go back to (iii)

(viii) killall dhclient
(ix) ifup wlan0

(x) iwconfig wlan0
to confirm it has the correct AP

10 easy steps ... and it works ... yay!

good luck.

(There may be a smaller set but this does work)

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Mail Lists wrote:
Ok after much experimentation - I now have the magic recipe to
connect which seems to work.


(i) Set up appropriate configs (ie populate
/etc/sysconfig/network-scripts/ifcfg*


(ii) ifup wlan0 ; ifdown wlan0

(iii) modprobe -r iwl4965
(iv) turn radio off with hardware switch
(v) turn on radio


Doh me. Wrong order

(vi) iwlist wlan0 scan

This will fail - repeat - it may still not see the AP that is
close - repeat until you see the AP picked up in the scan.

If you cannot see the AP - go back to (iii)


(vii) iwconfig wlan0 channel 11
Adjust to channle of close AP



(viii) killall dhclient
(ix) ifup wlan0

(x) iwconfig wlan0
to confirm it has the correct AP

10 easy steps ... and it works ... yay!

good luck.

(There may be a smaller set but this does work)



--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list