Mailinglist Archive: opensuse-amd64 (342 mails)

["jm macip" <jmmacip@xxxxxxxx>]

Yes, I have corrected config.opts and also added the memory areas
reported by Windows. I also added the PCI bridge memory area.
In windows the card is reported as a OPTi 82c861 PCI to USB open Host
Controller using memory D04FE000-D04FEFFF, should I add this mem area to
config.opts?
Thanks in advanve.
Josep Maria Macip

>>> "Matt T." <Matt@xxxxxxxxx> 20/02/2005 16:46 >>>
On Sunday 20 February 2005 03:09, jm macip wrote:
> I'm sure PCMCIA is working
>

PCMCIA on AMD64 might be working for some cards, but may be not for
all.

I understand that you already corrected your config.opts file using the
output 
of lspci, correct?

However if one card works that does not mean that all can work. Every
card 
uses a different memory range / port range to talk to your system. I
assume 
that some cannot use the memory / port range offered by amd64 64bit
systems.

Also different cards / different functions use different parts of the
PCMCIA 
code. network cards and modem cards use different modules of the PCMCIA

package. Some parts might work better than the others.

> >>> Andreas Jaeger <aj@xxxxxxx> 19/02/2005 20:49 >>>
>
> "jm macip" <jmmacip@xxxxxxxx> writes:
> > No messages! card is not recognized!

Nothing in /var/log/messages? Nothing at all? Nothing about "anonymous

memory"?  Nothing about "unable to access memory"?

Ususally there is something showing that PCMCIA understood there is
something 
to do for it, it wakes up, checks, and if it does not recognize what is
going 
on there usually is a message. And as far as I've seen, if a card does
not 
get identified, the PCMCIA code seems to try the memory_cs module,
which does 
the output listed above.

Also, type "dmesg" in a konsole window, after you inserted the card.
Look at 
the last lines of the output. There should be something. Is it?

>
> Really nothing at all?  Search the archives of this list, could be
the
> PCMCIA issue we discussed several times,
>

yes, not all cards could get to work, and some need dirty workarounds
(as 
postet here this and last month)

> Andreas
>

Andreas,
is SuSE working with the PCMCIA guys to get a better amd64 support in
PCMCIA, 
or is SuSE doing something to have yast do a better configuration of 
config.opts at install time with SuSE 9.3?

If SuSE does nothing I would try to find the time to report the issue
to the 
PCMCIA code owners, but I'm probably too short of time for working it
out.

It would be great, and also great for SuSE, if amd64 and PCMCIA would
work out 
of the box with SuSE 9.3, but I can understand if amd64 notebooks would
be 
too small a market to invest time in it. Just let us know, please.

> >>>> Andreas Jaeger <aj@xxxxxxx> 19/02/2005 15:15 >>>
> >
> > "jm macip" <jmmacip@xxxxxxxx> writes:
> >> Hi all:
> >> I recently bought a Vodafone 3g pcmcia card but i'm unable to
make
> >
> > it
> >
> >> work.
> >> I have followed the steps stated in this how-to
> >> http://www.pharscape.org/index.php?option=content&task=view&id=28

> >> but I get stuck beacause cardctl doesn't identify the card. (it
is
> >> currently working with my Wl-110 wireless card)
> >
> > What is the output of /var/log/messages?
> >
> > Andreas

HTH,
Matt

-- 
Check the List-Unsubscribe header to unsubscribe
For additional commands, email: suse-amd64-help@xxxxxxxx