On Fri, Oct 18, 2002 at 03:20:37AM -0700, Joseph Carter wrote: > On Fri, Oct 18, 2002 at 11:57:02AM +0200, Oliver Kurth wrote: > > ifplugd should work using mii calls with the eepro100 driver... or did > > I miss something? Maybe you could contribute to #164380. > > Nope, mii was no more useful than ethtool. Both claimed the device was > completely unsupported (2.4.19 kernel..) Unfortunately I didn't save the > mii-diag output, but basically I was able to conclude that mii-tool said > it didn't know the link status. Really strange, because I use the eepro100 driver and I am happy. At least as long as iflpugd is concerned. > I was kinda discouraged by the e100-source package since it also did not > support any of the necessary ioctls, but then I found out that the Debian > package is over a year old. Building a NM(N)U of the package with the > current version worked fine, and the resulting module did support ethtool, > so I considered the problem resolved. Please do the NMU and/or write this to the bug, to make the submitter happy. > Seems ifplugd acesses the disk regularly though - could be something else > though, haven't investigated yet. If ifplugd is responsible, I think > that's an issue worth fixing if possible since the primary target is > notebooks which typically have short lifespans when the disk is active. > I've also concluded that Debian's init does too damned much on a laptop, > but I haven't had time to gut it down to just the basics. I do not think it is ifplugd's fault. It just runs as a daemon, checking the NIC every second or so. Should not involve any disk activity. But I can look at that. Greetings, Oliver -- debian/rules http://zork.net/~nick/srom/
Attachment:
pgpg3x04IzMue.pgp
Description: PGP signature