From: Ben Hoskings <ben@jeeves.bpa.nu>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 yenta_socket eats kernel time on Toshiba Laptop
Date: Tue, 18 Nov 2003 19:24:10 +1000
User-Agent: KMail/1.5.93
References: <43376.138.130.214.20.1068871325.squirrel@jeeves.home.house> <20031115015927.4e31e6ee.akpm@osdl.org> <200311161011.03804.ben@jeeves.bpa.nu>
In-Reply-To: <200311161011.03804.ben@jeeves.bpa.nu>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Message-Id: <200311181924.10765.ben@jeeves.bpa.nu>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1331
Lines: 31

On Sun, 16 Nov 2003 10:11 am, Ben Hoskings wrote:
> Thanks for the reply, Andrew.
>
> > >  Attepting a modprobe on any of the other PCMCIA bus drivers gives a
> > >  'device not found' error.
> > >
> > >  Under 2.4, the PCMCIA bus uses the i82365 module, which works
> > > perfectly.
 Under 2.6, it appears that the related driver has been
> > > moved to the yenta_socket module (It's a ToPIC100 Controller; see dmesg
> > > below).
> >
> > Have you tried disabling i82365 in kernel config?
> 
> All the PCMCIA options are configured as modules, and when I modprobed 
> yenta_socket, the only one already loaded was pcmcia_core. Disabling in the
> 
 kernel config won't make a difference here will it?
> 
Anyone else have any suggestions on what I could do to start debugging this 
problem? I don't like to ask again, but I figure this is too good a chance to 
miss.
I'd like to get my laptop working with 2.6, sure, but more importantly a 
problem like this that affects hardware I own is the perfect chance for me to 
poke my head into the kernel sources and start learning. ;)


ben_h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/