On Thu, 2005-01-27 at 00:35 +0100, Tom Parker wrote:
> I've managed to figure out how to fix my problems, and it may also help
> some of the other people with issues re: net.80203.link. HAL appears to
> have undergone some considerable changes (e.g. what looks like the start
> of a complete rewr
I think there are two separate bugs though they may be related. The one
I submitted to the hal component of bugzilla had to do with the freezing
of the value of net.80203.link as reported by the hal-device-manager. I
just repeated part of the experiment to look at the /sys/.../carrier
file. Yes
Tom Parker wrote:
NetworkManager: SWITCH: old device no longer good, but no better
device was available
Given this wired card is the only one in this machine, this is
somewhat annoying. Now, I *think* this might be linked into the fact
that my crappy network card is breaking HAL somewhat, a
On Wed, 2005-01-26 at 17:24 -0500, Bill Moss wrote:
> CVS-1-26
>
> Boot with wire unplugged. NM has not obtained a wireless connection to a
> Cisco AP after several minutes (works fine with SMC AP).
> Plug in wire. NM gets a wired connection. hal-device-manager outputs:
> PropertyModified, device
I submitted the bug to bugzilla as suggested. The text is below.
David Zeuthen wrote: hal-0.4.7 in FC3 and FC Rawhide just listens to the
netlink socket for link changes and gets the initial state from the
carrier file in sysfs. It works great for me and I've not seen any bugs
on this (apart fro
CVS-1-26
Boot with wire unplugged. NM has not obtained a wireless connection to a
Cisco AP after several minutes (works fine with SMC AP).
Plug in wire. NM gets a wired connection. hal-device-manager outputs:
PropertyModified, device=/org/freedesktop/Hal/devices/pci_8086_101e
key=net.80203.rate,
On Wed, 2005-01-26 at 12:44 +0100, Tom Parker wrote:
> One of the machines I'm on has a 3com 3c940 onboard ethernet using the
> sk98lin driver. Now, the card apparently has MII support, but the linux
> driver doesn't support it, not even with either 2.6.10 or the card
> manufacturer's supplied d
On Tue, 2005-01-25 at 20:56 -0500, Bill Moss wrote:
> FC3 kernel-2.6.10-1.741
> hal 0.4.7.1
> dbus 0.22-10
> e1000 driver for Intel Corp. 82540EP Gigabit Ethernet Controller
> ipw2200-0.21 driver for Intel Corp. PRO/Wireless 2200BG
> setup: network service turned off, eth0 onboot=no (wired) eth1 on
Dan Williams wrote:
That would be great. I'm not quite sure how to fit this in, perhaps we
need to add this into the "wired" device activation process and wait for
10s or so for a frame before continuing or failing. Thoughts?
This seemed like an interesting little project (especially after a fe
On Wed, 26 Jan 2005, Tom Parker wrote:
> And then it just sits there and does nothing until I get annoyed and
> press Ctrl-C. If we have an MII-less link, then we need another way to
> be able to determine whether it's alive. One option that comes to mind
> is opening up a raw socket and listeni
Neal,
It appears here that the machine went to sleep? The "errno = 19" reported
by NetworkManager is ENODEV, and the telltale "remove event not handled",
followed by the stuff about ACPI seem to indicate that the machine went to
sleep for some reason, then woke up.
Right now, NM doesn't hand
Testing NM on FC3 using driverloader. Seems to work for a while, but when I
left it on overnight it stopped working. Here's some info:
Jan 25 20:40:47 nbecker2 kernel: eth1: New link status: Connected (0001)
Jan 25 20:40:54 nbecker2 NetworkManager: found! (encrypted)
Jan 25 20:40:54 nbecker2
One of the machines I'm on has a 3com 3c940 onboard ethernet using the
sk98lin driver. Now, the card apparently has MII support, but the linux
driver doesn't support it, not even with either 2.6.10 or the card
manufacturer's supplied driver. I know from some googling that it's
there on the Free
13 matches
Mail list logo
