> > The last stable 2.3 kernel I could use was around 2.3.3x, since around
> > 2.3.39 I guess is when 2.3 became quite unstable on this nec versa sx
> > laptop. I have attached the oops the I get when rmmod'ing pci_socket.
>
> Please check if it works fine for you if you compile everything into the
> kernel - what I'd like to know is just whether the _basic_ functionality
> is fine, and that it is only the fact that the new cardbus code really
> doesn't work as a module.
Ok, I'll try, but I bet my system will be less usable (no mouse) than it was
before with modules.
> I don't use modules. As a result, I haven't been all that interested
> in making them work - at worst I will just not allow the "m"odule answer
> in configure as nobody seems to be interested in fixing this.
I can tell, but the way I've always seen it, if you don't need it to boot,
you don't need it in the kernel.
> > By the way, the 2 irq's yenta gets for the 2 sockets are 5 and 10. LSPCI
> > reports irq 5 being used by the sound controller (which causes problems when
> > playing sound and using a cardbus device on that irq), and 10 is reported as
> > being used by the vga controller. What was wrong with the way pcmcia was
> > done in 2.2 (with David's pcmcia modules) by allocating IRQs as they were
> > needed?
>
> PCCARD really has two differentkinds of interrupts: the PCI interrupts and
> the legacy ISA interrupts. The legacy ISA interrupts are dynamic, the PCI
> interrupts are wired.
So are you saying that my cardbus controller is hard wired to irq's 5 and
10 which the bios has no control over?
> The new driver will use both. What you see as the "yenta irq" is the PCI
> interrupt routing information. It was always there, but the original
> PCMCIA driver didn't use it by default (aside: it DOES use it by default
> in newer versions, you are comparing a new kernel against an old PCMCIA
> package ;)
Well if I decide to insert a pcmcia card, does this mean it will use that
"yenta irq" or will it assign a new one?
> CardBus does need PCI interrupts. That's how it is spec'ed, and that's how
> it needs to be done at least for true cardbus cards (as opposed to the old
> 16-bit cards). Using the legacy ISA interrupts is a fallback that does not
> work on a number of machines. My Sony VAIO, for example, never could
> handle a regular tulip cardbus card with the old setup - which is kind of
> scary as that's probably the most common new cardbus network card out
> there.
Sony. Never cared for them, and I've never had a sony product that didn't
quit working. This was a sony tape deck (quit after 6 months), a cd player
(wasn't sony brand, but had mostly sony chips), logic failure 1 year later.
2 sony Qic-Wide, well they required formatting quite a few times.
> There seems to be many bad (or just one, but common) sound drivers that
> are unhappy with sharing an interrupt. That is a sounddriver bug, nothing
> less, nothing more. PCI interrupts are fundamentally shared, and they get
> shared depending on things like which slot the cards are in etc etc.
>
> Is this the same sound driver (ESS Maestro) or a new one?
Well, I must say the system worked better under 2.2.14 with david hinds
pcmcia (3.1.11 I believe). My nic is a 3com 3cxfe575ct (I hate these
numbers now). 2.2.14 I get IRQ3 for it and it doesn't have *ANY* problems.
Under 2.3.51, I put it in slot 0, irq 10. VGA has irq 10 (I wish I could
disable that!) and after downloading 180mb (of a 183mb file) the driver
pukes and spams my console with errors (the only way to fix is to remove the
card and reinsert). If I stick it in slot 1, it gets irq 5 and downloading
the same file causes errors after about 90mb downloaded.
I need to add while the cardbus has irq 5, the sound skips every first write
to the drive (constant writes only triggers it at start, but it happens at
every short write). As stated above, 2.2.14 did not do this.
The biggest problem I have with this thing is why it's always grabbing IRQs
that are already inuse as opposed to ones that are available. I currently
have USB disabled for 2 reasons, last time I tried the driver, it just
didn't work (timeout errors), and 2, I don't have any usb devices. So I
have irq 9 and irq 11 free. Maybe you could have something like
yentairqlist= and list irqs that I want to use there. I'm not sure how
windoze handles irq allocation, but I'll find out when I get to work monday.
-- Lab tests show that use of micro$oft causes cancer in lab animals- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:19 EST