mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <200311181924.10765.ben@jeeves.bpa.nu> (raw)
In-Reply-To: <200311161011.03804.ben@jeeves.bpa.nu>

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.\r 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
> \r 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

  reply	other threads:[~2003-11-18  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15  4:42 Ben Hoskings
2003-11-15  9:59 ` Andrew Morton
2003-11-16  0:11   ` Ben Hoskings
2003-11-18  9:24     ` Ben Hoskings [this message]
     [not found] <15270833.1069152610368.JavaMail.ngmail@webmail06.arcor-online.net>
     [not found] ` <200311182243.18614.ben@jeeves.bpa.nu>
2003-11-19  5:44   ` Ben Hoskings

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200311181924.10765.ben@jeeves.bpa.nu \
    --to=ben@jeeves.bpa.nu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome