On Tuesday 22 February 2005 23:09, jm macip wrote:
Matt: I've allready tryied to add memory addresses reported by windows to the config.opts but no luck.
I didn't mean "add" but I meant "use only". Meaning outcomment everything else, all memory range and all ports *not* used by winXP.
One strange thing is happening, all my PCMCIA 16 bit cards are working: Compaq wl110, compact flash adapter and Thoshiba 2GB HD card but none of the 32 bit like a serial ata, USB 2.0, firewire and a conceptronic c54c, or vodafone 3g card are detected by the pcmcia subsystem.
Very interesting. That could be a clue in this puzzle. Can anyone confirm this?
Ok, I will give a look to pcimcia Forums.
Yes, I think that is the right place now to follow up.
"Matt T."
21/02/2005 17:57:13 >>> On Monday 21 February 2005 03:11, jm macip wrote:
** High Priority **
The only significant messages I get form dmesg are: Feb 20 21:05:04 JMA64 kernel: psargs-0352: *** Error: Looking up [Z005] in namespace, AE_NOT_FOUND Feb 20 21:05:04 JMA64 kernel: search_node 0000010037e05c30
start_node
0000010037e05c30 return_node 0000000000000000
sorry, doesn't ring a bell here.
I haven't worked with PCMCIA to USB bridges yet, so I do not exactly know what to expect.
I'm just guessing now, but what you could do is to make the memory and port ranges smaller. For a start, reduce it to the values you took from winXP only. Nothing else.
Or you could load the module used by pcmcia for the usb bridge manually. I don't know how it's called now, I'm not at the notebook now. Look up the name of the module in the /etc/pcmcia/config file. (This is the way I get the Axen / Sagem GPRS card to work.)
Then the next step would be to have a look at the PCMCIA mailing list and see if you find something there. May be the developers can guide you through debugging. This is not just said like that, I did find there the info which enabled me to get the Sierra Wireless aircard working on my amd64 notebook.
Nice challenge. Good luck! Matt
Matt T.
02/20/05 8:52 pm >>> On Monday 21 February 2005 01:07, jm macip wrote:
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?
Why not, give it a try.
After what Pascal reported about his card using memory and ports different from what lspci reported it would not surprise me.
However please be aware that we could help you much better if you
would
answer more clearly about what you find in /var/log/messages or as dmesg output. Did you see my questions?
If there would be indeed No messages, as you said earlier, then
PCMCIA
would not even start to try to talk to the card, and then adjusting the
memory
and port range would not help, the PCMCIA code would not get started.
I have a modem card, when I insert it, then kde freezes. Until I take
it
out again. After that kde works fine again. When I close down the memory
/
port ranges then it does not get recognized, but PCMCIA starts and gives
some
output. May be I just have not found the winning port / memory range
for
it.
This just to demonstrate you that PCMCIA can work for some cards,
and
for others not (yet). In order to understand if you have such a not
working
card, your clear report of /var/log/messages or as dmesg output might be helpful.
Also, have you seen my post that I need to kill and restart
cardmanager
before any card gets recognized. (I did not test yet if that is true for
older
kernels, or only for the latest ones which I have installed
currently.
As far as I remember it was not like that for the kernels current 2 or 3
months
ago.
HTH, Matt
Thanks in advanve. Josep Maria Macip
Matt T.
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
19/02/2005 20:49 >>> jm macip
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
[snip]
>>Andreas Jaeger
19/02/2005 15:15 >>> jm macip
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@suse.com
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com