> -----Original Message----- > From: fedora-list-bounces@xxxxxxxxxx > [mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Karl Larsen > Sent: Sunday, May 21, 2006 11:10 PM > To: For users of Fedora Core releases > Subject: Re: FC4 rmmod does not work > > Tomas Larsson wrote: > >> -----Original Message----- > >> From: fedora-list-bounces@xxxxxxxxxx > >> [mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Dave Jones > >> Sent: Sunday, May 21, 2006 8:57 PM > >> To: For users of Fedora Core releases > >> Subject: Re: FC4 rmmod does not work > >> > >> On Sun, May 21, 2006 at 08:46:17PM +0200, Tomas Larsson wrote: > >> > Trying to remove a driver with rmmod > > According to > lsmod the > >> driver is unused, but rmmod refuses to remove it, > there is no > >> messages. > >> > > >> > Looking in the log, I find that the driver is removed > and directly > >> inserted > again. > >> > Is this a FC4 issue or is it a driver issue? > >> > >> You didn't mention which driver it was, so there's no way > to answer > >> this question. > >> > >> Dave > >> > >> > > Rt61pci is the name of the driver. > > I know that it is a beta, not working very well, that's why > I want to > > remove it, to change it to a newer version. > > This is what I finde in the logs: > > > > > > May 21 11:45:17 springbox kernel: Unloading module: rt61pci - CVS > > (N/A) by http://rt2x00.serialmonkey.com. > > May 21 11:45:18 springbox kernel: ACPI: PCI interrupt for device > > 0000:03:00.0 disabled May 21 11:45:19 springbox kernel: Loading > > module: rt61pci - CVS (N/A) by http://rt2x00.serialmonkey.com. > > May 21 11:45:19 springbox kernel: ACPI: PCI Interrupt > 0000:03:00.0[A] > > -> Link [C0B9] -> GSI 11 (level, low) -> IRQ 11 > > > > Question is obviously is this because FC4 or is it due to > the driver itself. > > > > So-far I have to eject the card, delete the drivers, do a > depmod and > > insert the card again. > > > > With best regards > > > > Tomas Larsson > > Sweden > > > > Verus Amicus Est Tamquam Alter Idem > > > > > Please try # modprobe -r and see what happens. But > both rmmod and modprobe act on the kernel not on what is > saved on the hard drive. If you want to remove the mod that > takes another action. > The logs above is after modprobe -r What I want to is to remove the mod from the kernel, not from the disk. But it refuses to remove it, wondering if the pnp-stuff has something to do with it. With best regards Tomas Larsson Sweden Verus Amicus Est Tamquam Alter Idem
