On Tue, Oct 6, 2009 at 12:26 PM, Carl Karsten <[email protected]>wrote:
> On Tue, Oct 6, 2009 at 2:17 PM, drew wymore <[email protected]> wrote: > > On Tue, Oct 6, 2009 at 12:15 PM, Carl Karsten <[email protected] > >wrote: > > > >> On Tue, Oct 6, 2009 at 2:04 PM, drew wymore <[email protected]> > wrote: > >> > Hi Plug, > >> > I'm working with moblin which is fedora/ubuntu like so I figure this > >> might > >> > be the best place to ask. I have an atheros chipset which is causing > the > >> > system to lock up, it's reproduceable with a few moves in the moblin > UI. > >> I > >> > have an alternate kernel module I have built and it will run on the > >> system, > >> > however the ath5k/ath9k drivers are built in to the kernel and are > being > >> > used by the system. Rolling my own kernel is an option but I'd rather > try > >> > and avoid it right now. What is the fedora/ubuntu way of forcing the > >> system > >> > to use a module instead of whats built in to the kernel for driver > >> support > >> > for a given piece of hardware? I've tried aliasing the network > interface > >> in > >> > modprobe.conf but not getting any joy with it. Google so far has > failed > >> me. > >> > > >> > >> I have done 1/2 of what you want, but it has been a while, so I'l > >> giveyou what I can verify today: > >> > >> $ ls /etc/modprobe.d/ > >> blacklist-ath_pci.conf blacklist-firewire.conf > blacklist-watchdog.conf > >> blacklist.conf blacklist-framebuffer.conf > >> > >> That is the area you want to mess with to prevent the 'bad' module from > >> loading. > >> > >> how you get yours to load is a different problem. /etc/modules still > >> works, but I think there is a 'new way' (like putting a file in > >> /etc/modprobe.d/ that is dedicated to your issue, makes updates easer) > >> > >> -- > >> Carl K > >> _______________________________________________ > >> PLUG mailing list > >> [email protected] > >> http://lists.pdxlinux.org/mailman/listinfo/plug > >> > > > > Carl, > > Thanks, at least I know I'm messing around in the right area. The problem > > is, the driver being used is built in and not modular > > Are you sure? that seems very odd for ubuntu, and I am pretty sure it > was the ath5k module that I blacklisted. this was about 1.5 years > ago, so 3 ubuntus ago... > > -- > Carl K > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > Carl, It's not quite Ubuntu proper, just Ubuntu/Fedora like, hence my confusion as I'm used to Slackware. I went into the kernel config and indeed ath5k was built in and not as a module. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
