Re: 3com network card, trouble w pcmcia-modules

2003-02-12 Thread mi
Hello David !

D.Emerson:
> Well maybe next message I'll change the subject to "network config"...
:-)

> Card Recognized! problems with debian packaging... isn't that why I decided
> on debian rather than Mandrake? It was because I was expecting the
> packaging to work better... hmph.

I did experience such things also. However, I'm quite sure that it wasn't 
because of a weak package management but instead becuase of my own ignorance, 
wrong reactions at critical points or very unfortunate circumstances.
It's not possible to foresee anything wickened happening in a system or 
human, and for half of what one can imageine it's not possibe to write a 
software - often, simply for limited resources.
DPKG is working on a igh level of safety, but still gives the user most 
possibilities to customize and decide about things.
Where other distro's ( imho ) tend to make it easy and transparent, but more 
'closed behind the doors' and rather influencable.
Debian requests you, and urges you to learn, and get your brain active ;-)
Usually nobody says it's the best distro for beginners
but i would say, if you first learn it this way, you've learned something 
for life, with computers.

> The big problem I had here is that pcmcia-cs was not properly installed,
> but it THOUGHT it was properly installed. apt-get said it was properly
> installed
I guess there were some failure messages at the first install.
One has to get used to look carefully, and _read_, with debian
( that apllies for me as well )

> So since it thought it was properly installed, I had to uninstall pcmcia-cs
> (and pcmcia-module-xx) and reinstall them both, and TADA! two high beeps,
> card properly identified and configured.
You see ? That's how it should be :-)

> Feb 11 02:22:09 lakshmi cardmgr[246]: + Ignoring unknown interface
> eth0=eth0.
nono...first do your reading !
( which means, I've got no idea ;)

> >Why testing ? I thought you're running stable woody ?
> >Please check your /etc/apt/sources.list. Maybe it's out of date.
> >My woody apt tells me 'pcmcia-modules-2.2.20' are compiled for
> > 'kernel-image 2.2.20-5'.
>
> Well, the kernel image 2.2.20-5 is stable, but the pcmcia-modules-2.2.20-5
> is testing, and there is another version of it that is marked unstable. But
> I had to upgrade the kernel from 2.2.20-1 which is what came on the CD,
> because I couldn't find a pcmcia-modules-2.2.20-1.

Now, look. Package versioning sometimes is confusing, i know 
There's a kernel package version 2.2.20-5 for kernel image 2.2.20,
here in my 'stable' database;
and also a package pcmcia-modules 2.2.20 which in the description is said to 
be compiled for kernel-package 2.2.20-5.
So it seems it's all here in woody.
However, I've got a set of cd's here, 4 weeks old. Maybe it has changed.

> yup, that sure was it!
yepp, and on to next stuff !


-- 

micha.



Re: 3com network card, trouble w pcmcia-modules

2003-02-12 Thread mi
Hello David !

D.Emerson:
> Well maybe next message I'll change the subject to "network config"...
:-)

> Card Recognized! problems with debian packaging... isn't that why I decided
> on debian rather than Mandrake? It was because I was expecting the
> packaging to work better... hmph.

I did experience such things also. However, I'm quite sure that it wasn't 
because of a weak package management but instead becuase of my own ignorance, 
wrong reactions at critical points or very unfortunate circumstances.
It's not possible to foresee anything wickened happening in a system or 
human, and for half of what one can imageine it's not possibe to write a 
software - often, simply for limited resources.
DPKG is working on a igh level of safety, but still gives the user most 
possibilities to customize and decide about things.
Where other distro's ( imho ) tend to make it easy and transparent, but more 
'closed behind the doors' and rather influencable.
Debian requests you, and urges you to learn, and get your brain active ;-)
Usually nobody says it's the best distro for beginners
but i would say, if you first learn it this way, you've learned something 
for life, with computers.

> The big problem I had here is that pcmcia-cs was not properly installed,
> but it THOUGHT it was properly installed. apt-get said it was properly
> installed
I guess there were some failure messages at the first install.
One has to get used to look carefully, and _read_, with debian
( that apllies for me as well )

> So since it thought it was properly installed, I had to uninstall pcmcia-cs
> (and pcmcia-module-xx) and reinstall them both, and TADA! two high beeps,
> card properly identified and configured.
You see ? That's how it should be :-)

> Feb 11 02:22:09 lakshmi cardmgr[246]: + Ignoring unknown interface
> eth0=eth0.
nono...first do your reading !
( which means, I've got no idea ;)

> >Why testing ? I thought you're running stable woody ?
> >Please check your /etc/apt/sources.list. Maybe it's out of date.
> >My woody apt tells me 'pcmcia-modules-2.2.20' are compiled for
> > 'kernel-image 2.2.20-5'.
>
> Well, the kernel image 2.2.20-5 is stable, but the pcmcia-modules-2.2.20-5
> is testing, and there is another version of it that is marked unstable. But
> I had to upgrade the kernel from 2.2.20-1 which is what came on the CD,
> because I couldn't find a pcmcia-modules-2.2.20-1.

Now, look. Package versioning sometimes is confusing, i know 
There's a kernel package version 2.2.20-5 for kernel image 2.2.20,
here in my 'stable' database;
and also a package pcmcia-modules 2.2.20 which in the description is said to 
be compiled for kernel-package 2.2.20-5.
So it seems it's all here in woody.
However, I've got a set of cd's here, 4 weeks old. Maybe it has changed.

> yup, that sure was it!
yepp, and on to next stuff !


-- 

micha.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 3com network card, trouble w pcmcia-modules

2003-02-11 Thread David Emerson
Hi Micha,

Well maybe next message I'll change the subject to "network config"...

Card Recognized! problems with debian packaging... isn't that why I decided on 
debian rather than Mandrake? It was because I was expecting the packaging to 
work better... hmph.

Of course the network stuff isn't configured yet, so it's not seeing the router 
yet... netenv was my very first step when the card didn't work, but way back 
then I should have been paying attention to the lack of beeping sounds.

The big problem I had here is that pcmcia-cs was not properly installed, but it 
THOUGHT it was properly installed. apt-get said it was properly installed, and 
so did the K Package tool - but most of the files listed in dpkg -L pcmcia-cs 
were not installed! The entire directory /etc/pcmcia is supposed to be filled 
with all kinds of configuration and data files, and the directory was totally 
empty - so pcmcia-cs somehow got messed up. And that's what was causing all the 
problems.

So since it thought it was properly installed, I had to uninstall pcmcia-cs 
(and pcmcia-module-xx) and reinstall them both, and TADA! two high beeps, card 
properly identified and configured.

>> >In /etc/modutils/ether, try to define alias eth0 3c589_cs
>> >(don't forget update-modules afterw.)
>>
>> No such file exists /etc/modutils/ether
>ok
>Anyway, it's probably not the main point now.
>(But for setting up your eth0 later, you just can create this file, and put 
>any options for the module there.)
>But let's put off all network configuration ( ifconfig stuff ) for now.
>Focus is how to get your card detected by the kernel / modul.

Well, it's about time for network stuff now :) But I should do a little reading 
before going straight to questions; but I may as well tell you what I've got:

Last problematic message was:

Feb 11 02:22:09 lakshmi cardmgr[246]: + Ignoring unknown interface eth0=eth0.


>Why testing ? I thought you're running stable woody ?
>Please check your /etc/apt/sources.list. Maybe it's out of date.
>My woody apt tells me 'pcmcia-modules-2.2.20' are compiled for 'kernel-image 
>2.2.20-5'. 

Well, the kernel image 2.2.20-5 is stable, but the pcmcia-modules-2.2.20-5 is 
testing, and there is another version of it that is marked unstable. But I had 
to upgrade the kernel from 2.2.20-1 which is what came on the CD, because I 
couldn't find a pcmcia-modules-2.2.20-1.

>> >Is there a /etc/pcmcia/config ?
>>
>> No. It seems like the pcmcia-modules wasn't installed correctly but... I
>
>There it is.
>What says 'dpkg -L pcmcia-cs' and the same for 'pcmcia-modules' ?
>Also try 'dpkg -s pcmcia-modules' and 'dpkg -C' and 
>'dpkg-reconfigure pcmcia-modules'

yup, that sure was it!
Thanks,
David

>Now back to repair my own system ;-)
>
> 
>-- 
>micha.



Re: 3com network card, trouble w pcmcia-modules

2003-02-11 Thread David Emerson
Hi Micha,

Well maybe next message I'll change the subject to "network config"...

Card Recognized! problems with debian packaging... isn't that why I decided on debian 
rather than Mandrake? It was because I was expecting the packaging to work better... 
hmph.

Of course the network stuff isn't configured yet, so it's not seeing the router yet... 
netenv was my very first step when the card didn't work, but way back then I should 
have been paying attention to the lack of beeping sounds.

The big problem I had here is that pcmcia-cs was not properly installed, but it 
THOUGHT it was properly installed. apt-get said it was properly installed, and so did 
the K Package tool - but most of the files listed in dpkg -L pcmcia-cs were not 
installed! The entire directory /etc/pcmcia is supposed to be filled with all kinds of 
configuration and data files, and the directory was totally empty - so pcmcia-cs 
somehow got messed up. And that's what was causing all the problems.

So since it thought it was properly installed, I had to uninstall pcmcia-cs (and 
pcmcia-module-xx) and reinstall them both, and TADA! two high beeps, card properly 
identified and configured.

>> >In /etc/modutils/ether, try to define alias eth0 3c589_cs
>> >(don't forget update-modules afterw.)
>>
>> No such file exists /etc/modutils/ether
>ok
>Anyway, it's probably not the main point now.
>(But for setting up your eth0 later, you just can create this file, and put 
>any options for the module there.)
>But let's put off all network configuration ( ifconfig stuff ) for now.
>Focus is how to get your card detected by the kernel / modul.

Well, it's about time for network stuff now :) But I should do a little reading before 
going straight to questions; but I may as well tell you what I've got:

Last problematic message was:

Feb 11 02:22:09 lakshmi cardmgr[246]: + Ignoring unknown interface eth0=eth0.


>Why testing ? I thought you're running stable woody ?
>Please check your /etc/apt/sources.list. Maybe it's out of date.
>My woody apt tells me 'pcmcia-modules-2.2.20' are compiled for 'kernel-image 
>2.2.20-5'. 

Well, the kernel image 2.2.20-5 is stable, but the pcmcia-modules-2.2.20-5 is testing, 
and there is another version of it that is marked unstable. But I had to upgrade the 
kernel from 2.2.20-1 which is what came on the CD, because I couldn't find a 
pcmcia-modules-2.2.20-1.

>> >Is there a /etc/pcmcia/config ?
>>
>> No. It seems like the pcmcia-modules wasn't installed correctly but... I
>
>There it is.
>What says 'dpkg -L pcmcia-cs' and the same for 'pcmcia-modules' ?
>Also try 'dpkg -s pcmcia-modules' and 'dpkg -C' and 
>'dpkg-reconfigure pcmcia-modules'

yup, that sure was it!
Thanks,
David

>Now back to repair my own system ;-)
>
> 
>-- 
>micha.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 3com network card, trouble w pcmcia-modules

2003-02-11 Thread mi
Hello David.
Now i try to help you but remind I didn't have just started the work here you 
are doing there. I have to find out things as well,  and cannot provide more  
than some ideas how to track it down.  

> 3c589_cs8544   0  (unused)
> ds  6400   0  [3c589_cs]
> i82365 22672   2
> pcmcia_core45824   0  [3c589_cs ds i82365]

> If I read correctly, according to PCMCIA-HOWTO, this is correct - I do need
> all of these.

I see.
What's ds ?

> >In /etc/modutils/ether, try to define alias eth0 3c589_cs
> >(don't forget update-modules afterw.)
>
> No such file exists /etc/modutils/ether
ok
Anyway, it's probably not the main point now.
(But for setting up your eth0 later, you just can create this file, and put 
any options for the module there.)
But let's put off all network configuration ( ifconfig stuff ) for now.
Focus is how to get your card detected by the kernel / modul.

> pcmcia restart successfully shuts down and restarts cardmgr, but the
> daemon.log shows that cardmgr can't open the config file because it
> doesn't exist (See below)
> >> I have no /var/lib/pcmcia directory, thus couldn't check the stab.
> >
> >Look into /var/run
>
> Directory doesn't exist /var/run/pcmcia

;-)

I meant the file /var/run/stab



> However, /etc/pcmcia/config MUST be sourced, because during bootup, cardmgr
> gives the message "could not open 'config': No such file or directory
> But I also don't know what file to edit that modifies bootup sequences.
> But since it can't open up config, I don't think it's even trying to
> identify the card. On my very first linux bootup a couple days ago, it
> correctly identified it as a 3com 589ec network card, but it hasn't ever
> done that again since first bootup.
We should find out what has changed then.

> First boot:
>
> Feb  7 17:08:15 lakshmi cardmgr[176]: starting, version is 3.1.33
> Feb  7 17:08:15 lakshmi cardmgr[176]: watching 2 sockets
> Feb  7 17:08:15 lakshmi cardmgr[176]: socket 1: 3Com 589 Ethernet
> Feb  7 17:08:15 lakshmi cardmgr[176]: executing: 'modprobe 3c589_cs'
> Feb  7 17:08:16 lakshmi cardmgr[176]: executing: './network start eth0'
> Feb  7 17:08:16 lakshmi cardmgr[176]: + Ignoring unknown interface
> eth0=eth0.
>
> But then after the first boot everything fell apart I don't know why.
> modprobe 3c589_cs failed, and it appeared that the package that includes
> modprobe was no longer there.

> You can check the archives for my first
> message sent saturday at 1:29PM +0800
ok
just did it
whoo, you tried to track it hard.
Let's see. We'll find it out, somehow.


>>> So I downloaded a newer kernel image (testing #5 and another 
>>> pcmcia-modules testing #5 package to match, as opposed to the unstable #6 
 
Why testing ? I thought you're running stable woody ?
Please check your /etc/apt/sources.list. Maybe it's out of date.
My woody apt tells me 'pcmcia-modules-2.2.20' are compiled for 'kernel-image 
2.2.20-5'. 

To be sure about the kernel, you can lookup "less  /usr/src/linux/.config"
(I don't know if you're familiar with shell commands)
and use "/" to search for keywords like 
PCMCIA (and look for CONFIG_PCMCIA_3c589)
CARDBUS

To post the above, type "grep 'xxx' /usr/src/linux/.config > outputfile.txt"
replacing xxx with the keyword. 
btw directory linux might not exist, it's a standard symbolic link to 
directory kernel-source-2.2.20, in your case.

> If I insert or eject the card, no beeping sounds happen - but my current
> situation isn't addressed well by the pcmcia-howto troubleshooting
>
> >Is there a /etc/pcmcia/config ?
>
> No. It seems like the pcmcia-modules wasn't installed correctly but... I

There it is.
What says 'dpkg -L pcmcia-cs' and the same for 'pcmcia-modules' ?
Also try 'dpkg -s pcmcia-modules' and 'dpkg -C' and 
'dpkg-reconfigure pcmcia-modules'

Now back to repair my own system ;-)

 
-- 
micha.



Re: 3com network card, trouble w pcmcia-modules

2003-02-11 Thread mi
Hello David.
Now i try to help you but remind I didn't have just started the work here you 
are doing there. I have to find out things as well,  and cannot provide more  
than some ideas how to track it down.  

> 3c589_cs8544   0  (unused)
> ds  6400   0  [3c589_cs]
> i82365 22672   2
> pcmcia_core45824   0  [3c589_cs ds i82365]

> If I read correctly, according to PCMCIA-HOWTO, this is correct - I do need
> all of these.

I see.
What's ds ?

> >In /etc/modutils/ether, try to define alias eth0 3c589_cs
> >(don't forget update-modules afterw.)
>
> No such file exists /etc/modutils/ether
ok
Anyway, it's probably not the main point now.
(But for setting up your eth0 later, you just can create this file, and put 
any options for the module there.)
But let's put off all network configuration ( ifconfig stuff ) for now.
Focus is how to get your card detected by the kernel / modul.

> pcmcia restart successfully shuts down and restarts cardmgr, but the
> daemon.log shows that cardmgr can't open the config file because it
> doesn't exist (See below)
> >> I have no /var/lib/pcmcia directory, thus couldn't check the stab.
> >
> >Look into /var/run
>
> Directory doesn't exist /var/run/pcmcia

;-)

I meant the file /var/run/stab



> However, /etc/pcmcia/config MUST be sourced, because during bootup, cardmgr
> gives the message "could not open 'config': No such file or directory
> But I also don't know what file to edit that modifies bootup sequences.
> But since it can't open up config, I don't think it's even trying to
> identify the card. On my very first linux bootup a couple days ago, it
> correctly identified it as a 3com 589ec network card, but it hasn't ever
> done that again since first bootup.
We should find out what has changed then.

> First boot:
>
> Feb  7 17:08:15 lakshmi cardmgr[176]: starting, version is 3.1.33
> Feb  7 17:08:15 lakshmi cardmgr[176]: watching 2 sockets
> Feb  7 17:08:15 lakshmi cardmgr[176]: socket 1: 3Com 589 Ethernet
> Feb  7 17:08:15 lakshmi cardmgr[176]: executing: 'modprobe 3c589_cs'
> Feb  7 17:08:16 lakshmi cardmgr[176]: executing: './network start eth0'
> Feb  7 17:08:16 lakshmi cardmgr[176]: + Ignoring unknown interface
> eth0=eth0.
>
> But then after the first boot everything fell apart I don't know why.
> modprobe 3c589_cs failed, and it appeared that the package that includes
> modprobe was no longer there.

> You can check the archives for my first
> message sent saturday at 1:29PM +0800
ok
just did it
whoo, you tried to track it hard.
Let's see. We'll find it out, somehow.


>>> So I downloaded a newer kernel image (testing #5 and another 
>>> pcmcia-modules testing #5 package to match, as opposed to the unstable #6 
 
Why testing ? I thought you're running stable woody ?
Please check your /etc/apt/sources.list. Maybe it's out of date.
My woody apt tells me 'pcmcia-modules-2.2.20' are compiled for 'kernel-image 
2.2.20-5'. 

To be sure about the kernel, you can lookup "less  /usr/src/linux/.config"
(I don't know if you're familiar with shell commands)
and use "/" to search for keywords like 
PCMCIA (and look for CONFIG_PCMCIA_3c589)
CARDBUS

To post the above, type "grep 'xxx' /usr/src/linux/.config > outputfile.txt"
replacing xxx with the keyword. 
btw directory linux might not exist, it's a standard symbolic link to 
directory kernel-source-2.2.20, in your case.

> If I insert or eject the card, no beeping sounds happen - but my current
> situation isn't addressed well by the pcmcia-howto troubleshooting
>
> >Is there a /etc/pcmcia/config ?
>
> No. It seems like the pcmcia-modules wasn't installed correctly but... I

There it is.
What says 'dpkg -L pcmcia-cs' and the same for 'pcmcia-modules' ?
Also try 'dpkg -s pcmcia-modules' and 'dpkg -C' and 
'dpkg-reconfigure pcmcia-modules'

Now back to repair my own system ;-)

 
-- 
micha.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 3com network card, trouble w pcmcia-modules

2003-02-10 Thread David Emerson
At 02:51 AM 2/10/03, mi wrote:
>Good mornig,  David !
>
>Hope you've had a good night.  ;-)
>
>> lsmod now includes:
>>
>> 3c589_cs8544   0  (unused)
>> ds  6400   0  [3c589_cs]
>> i82365 22672   2
>> pcmcia_core45824   0  [3c589_cs ds i82365]
>Why do you have 2 modules for the same card ?
>One from the kernel source...i suppose you need the pcmcia-cs one.
>i82365 is a modular pcmcia-cs socket driver from this package ?

If I read correctly, according to PCMCIA-HOWTO, this is correct - I do need all 
of these.

>> and modprobe is successful.
>In /etc/modutils/ether, try to define alias eth0 3c589_cs 
>(don't forget update-modules afterw.)

No such file exists /etc/modutils/ether

If:
>/etc/init.d/pcmcia restart
>gives you an ident it's porobably a coldplug problem.
>Or just try eject and insert again.

pcmcia restart successfully shuts down and restarts cardmgr, but the 
daemon.log shows that cardmgr can't open the config file because it 
doesn't exist (See below)

>> I have no /var/lib/pcmcia directory, thus couldn't check the stab.
>Look into /var/run

Directory doesn't exist /var/run/pcmcia


>> From /var/log/messages :
>>
>> Feb  9 22:51:40 lakshmi kernel: cs: warning: no high memory space
>> available!
>> Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!
>> Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!

Got a good response elsewhere to this one:
> But the high memory complaint may be fixed by adding
> port 0x1000-0x1fff
> to the line "include port..." in /etc/pcmcia/config.opts

But I don't have /etc/pcmcia/config.opts - and I guess config.opts is 
old-fashioned, anyways, according to pcmcia-howto.

>Wild guess: On bootup the card is identified as memory card ?
>Is /etc/pcmcia/config sourced at all ?

No, not identified as a memory card - not identified at all.

However, /etc/pcmcia/config MUST be sourced, because during bootup, cardmgr 
gives the message "could not open 'config': No such file or directory

But I also don't know what file to edit that modifies bootup sequences.

But since it can't open up config, I don't think it's even trying to 
identify the card. On my very first linux bootup a couple days ago, it 
correctly identified it as a 3com 589ec network card, but it hasn't ever 
done that again since first bootup.

First boot:

Feb  7 17:08:15 lakshmi cardmgr[176]: starting, version is 3.1.33
Feb  7 17:08:15 lakshmi cardmgr[176]: watching 2 sockets
Feb  7 17:08:15 lakshmi cardmgr[176]: socket 1: 3Com 589 Ethernet
Feb  7 17:08:15 lakshmi cardmgr[176]: executing: 'modprobe 3c589_cs'
Feb  7 17:08:16 lakshmi cardmgr[176]: executing: './network start eth0'
Feb  7 17:08:16 lakshmi cardmgr[176]: + Ignoring unknown interface eth0=eth0.

But then after the first boot everything fell apart I don't know why. modprobe 
3c589_cs failed, and it appeared that the package that includes modprobe was no 
longer there. You can check the archives for my first message sent saturday at 
1:29PM +0800

If I insert or eject the card, no beeping sounds happen - but my current 
situation isn't addressed well by the pcmcia-howto troubleshooting

>Is there a /etc/pcmcia/config ?

No. It seems like the pcmcia-modules wasn't installed correctly but... I don't 
really know how to check. When I installed the package it sure looked alright, 
and I'm definitely further along than I was before, but also definitely not 
workin' yet!

>micha.

Thanks Micha :)
-David



Re: 3com network card, trouble w pcmcia-modules

2003-02-10 Thread David Emerson
At 02:51 AM 2/10/03, mi wrote:
>Good mornig,  David !
>
>Hope you've had a good night.  ;-)
>
>> lsmod now includes:
>>
>> 3c589_cs8544   0  (unused)
>> ds  6400   0  [3c589_cs]
>> i82365 22672   2
>> pcmcia_core45824   0  [3c589_cs ds i82365]
>Why do you have 2 modules for the same card ?
>One from the kernel source...i suppose you need the pcmcia-cs one.
>i82365 is a modular pcmcia-cs socket driver from this package ?

If I read correctly, according to PCMCIA-HOWTO, this is correct - I do need all of 
these.

>> and modprobe is successful.
>In /etc/modutils/ether, try to define alias eth0 3c589_cs 
>(don't forget update-modules afterw.)

No such file exists /etc/modutils/ether

If:
>/etc/init.d/pcmcia restart
>gives you an ident it's porobably a coldplug problem.
>Or just try eject and insert again.

pcmcia restart successfully shuts down and restarts cardmgr, but the 
daemon.log shows that cardmgr can't open the config file because it 
doesn't exist (See below)

>> I have no /var/lib/pcmcia directory, thus couldn't check the stab.
>Look into /var/run

Directory doesn't exist /var/run/pcmcia


>> From /var/log/messages :
>>
>> Feb  9 22:51:40 lakshmi kernel: cs: warning: no high memory space
>> available!
>> Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!
>> Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!

Got a good response elsewhere to this one:
> But the high memory complaint may be fixed by adding
> port 0x1000-0x1fff
> to the line "include port..." in /etc/pcmcia/config.opts

But I don't have /etc/pcmcia/config.opts - and I guess config.opts is old-fashioned, 
anyways, according to pcmcia-howto.

>Wild guess: On bootup the card is identified as memory card ?
>Is /etc/pcmcia/config sourced at all ?

No, not identified as a memory card - not identified at all.

However, /etc/pcmcia/config MUST be sourced, because during bootup, cardmgr gives the 
message "could not open 'config': No such file or directory

But I also don't know what file to edit that modifies bootup sequences.

But since it can't open up config, I don't think it's even trying to 
identify the card. On my very first linux bootup a couple days ago, it 
correctly identified it as a 3com 589ec network card, but it hasn't ever 
done that again since first bootup.

First boot:

Feb  7 17:08:15 lakshmi cardmgr[176]: starting, version is 3.1.33
Feb  7 17:08:15 lakshmi cardmgr[176]: watching 2 sockets
Feb  7 17:08:15 lakshmi cardmgr[176]: socket 1: 3Com 589 Ethernet
Feb  7 17:08:15 lakshmi cardmgr[176]: executing: 'modprobe 3c589_cs'
Feb  7 17:08:16 lakshmi cardmgr[176]: executing: './network start eth0'
Feb  7 17:08:16 lakshmi cardmgr[176]: + Ignoring unknown interface eth0=eth0.

But then after the first boot everything fell apart I don't know why. modprobe 
3c589_cs failed, and it appeared that the package that includes modprobe was no longer 
there. You can check the archives for my first message sent saturday at 1:29PM +0800

If I insert or eject the card, no beeping sounds happen - but my current situation 
isn't addressed well by the pcmcia-howto troubleshooting

>Is there a /etc/pcmcia/config ?

No. It seems like the pcmcia-modules wasn't installed correctly but... I don't really 
know how to check. When I installed the package it sure looked alright, and I'm 
definitely further along than I was before, but also definitely not workin' yet!

>micha.

Thanks Micha :)
-David


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 3com network card, trouble w pcmcia-modules

2003-02-10 Thread mi
Good mornig,  David !

Hope you've had a good night.  ;-)

David Emerson:
> another update, really going to bed this time...
>
> successfully installed kernel 2.2.20-5 and the pcmcia-modules pkgs. Feels
> like I'm getting closer...
>
> lsmod now includes:
>
> 3c589_cs8544   0  (unused)
> ds  6400   0  [3c589_cs]
> i82365 22672   2
> pcmcia_core45824   0  [3c589_cs ds i82365]
Why do you have 2 modules for the same card ?
One from the kernel source...i suppose you need the pcmcia-cs one.
i82365 is a modular pcmcia-cs socket driver from this package ?

> and modprobe is successful.
In /etc/modutils/ether, try to define alias eth0 3c589_cs 
(don't forget update-modules afterw.)

> # cardctl ident
> Socket 0:
>   no product info available
> Socket 1:
>   no product info available
>
> (Socket 0 holds the network card, Socket 1 is currently empty.)

If:
/etc/init.d/pcmcia restart
gives you an ident it's porobably a coldplug problem.
Or just try eject and insert again.

> I have no /var/lib/pcmcia directory, thus couldn't check the stab.
Look into /var/run

> From /var/log/messages :
>
> Feb  9 22:51:40 lakshmi kernel: cs: warning: no high memory space
> available!
> Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!
> Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!
Wild guess: On bootup the card is identified as memory card ?
Is /etc/pcmcia/config sourced at all ?

> From daemon.log:
>
> Feb  9 22:56:41 lakshmi cardmgr[246]: starting, version is 3.1.33
> Feb  9 22:56:41 lakshmi cardmgr[246]: could not open 'config': No such
> file or directory
> Feb  9 22:56:41 lakshmi cardmgr[246]: exiting
Is there a /etc/pcmcia/config ?

I've experience some similar problems here, with 2.4 kernel inbuilt pcmcia 
though. Please, continuo with your updates !


-- 

micha.



Re: 3com network card, trouble w pcmcia-modules

2003-02-10 Thread mi
Good mornig,  David !

Hope you've had a good night.  ;-)

David Emerson:
> another update, really going to bed this time...
>
> successfully installed kernel 2.2.20-5 and the pcmcia-modules pkgs. Feels
> like I'm getting closer...
>
> lsmod now includes:
>
> 3c589_cs8544   0  (unused)
> ds  6400   0  [3c589_cs]
> i82365 22672   2
> pcmcia_core45824   0  [3c589_cs ds i82365]
Why do you have 2 modules for the same card ?
One from the kernel source...i suppose you need the pcmcia-cs one.
i82365 is a modular pcmcia-cs socket driver from this package ?

> and modprobe is successful.
In /etc/modutils/ether, try to define alias eth0 3c589_cs 
(don't forget update-modules afterw.)

> # cardctl ident
> Socket 0:
>   no product info available
> Socket 1:
>   no product info available
>
> (Socket 0 holds the network card, Socket 1 is currently empty.)

If:
/etc/init.d/pcmcia restart
gives you an ident it's porobably a coldplug problem.
Or just try eject and insert again.

> I have no /var/lib/pcmcia directory, thus couldn't check the stab.
Look into /var/run

> From /var/log/messages :
>
> Feb  9 22:51:40 lakshmi kernel: cs: warning: no high memory space
> available!
> Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!
> Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!
Wild guess: On bootup the card is identified as memory card ?
Is /etc/pcmcia/config sourced at all ?

> From daemon.log:
>
> Feb  9 22:56:41 lakshmi cardmgr[246]: starting, version is 3.1.33
> Feb  9 22:56:41 lakshmi cardmgr[246]: could not open 'config': No such
> file or directory
> Feb  9 22:56:41 lakshmi cardmgr[246]: exiting
Is there a /etc/pcmcia/config ?

I've experience some similar problems here, with 2.4 kernel inbuilt pcmcia 
though. Please, continuo with your updates !


-- 

micha.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 3com network card, trouble w pcmcia-modules

2003-02-10 Thread David Emerson
another update, really going to bed this time...

successfully installed kernel 2.2.20-5 and the pcmcia-modules pkgs. Feels like 
I'm getting closer...

lsmod now includes:

3c589_cs8544   0  (unused)
ds  6400   0  [3c589_cs]
i82365 22672   2
pcmcia_core45824   0  [3c589_cs ds i82365]

and modprobe is successful.

# cardctl ident
Socket 0:
  no product info available
Socket 1:
  no product info available

(Socket 0 holds the network card, Socket 1 is currently empty.)

I have no /var/lib/pcmcia directory, thus couldn't check the stab.

>From /var/log/messages :

Feb  9 22:51:40 lakshmi kernel: cs: warning: no high memory space 
available!
Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!
Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!

>From daemon.log:

Feb  9 22:56:41 lakshmi cardmgr[246]: starting, version is 3.1.33
Feb  9 22:56:41 lakshmi cardmgr[246]: could not open 'config': No such 
file or directory
Feb  9 22:56:41 lakshmi cardmgr[246]: exiting

When doing /etc/init.d/pcmcia restart   these same lines show up again at 
the bottom of the daemon.log.


-David



Re: 3com network card, trouble w pcmcia-modules

2003-02-10 Thread David Emerson
update...

I tried to install the pcmcia-modules-2.2.20 package, and it told me I had a 
different kernel-image than it wanted. I figured out that I'm running 
kernel-image 2.2.20 (#1) and the module was expecting 2.2.20 (#6) ... a world 
of difference, I guess.

So I downloaded a newer kernel image (testing #5 and another pcmcia-modules 
testing #5 package to match, as opposed to the unstable #6 versions) and will 
try to install them most likely tomorrow...

-David



Re: 3com network card, trouble w pcmcia-modules

2003-02-10 Thread David Emerson
another update, really going to bed this time...

successfully installed kernel 2.2.20-5 and the pcmcia-modules pkgs. Feels like I'm 
getting closer...

lsmod now includes:

3c589_cs8544   0  (unused)
ds  6400   0  [3c589_cs]
i82365 22672   2
pcmcia_core45824   0  [3c589_cs ds i82365]

and modprobe is successful.

# cardctl ident
Socket 0:
  no product info available
Socket 1:
  no product info available

(Socket 0 holds the network card, Socket 1 is currently empty.)

I have no /var/lib/pcmcia directory, thus couldn't check the stab.

>From /var/log/messages :

Feb  9 22:51:40 lakshmi kernel: cs: warning: no high memory space 
available!
Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!
Feb  9 22:51:40 lakshmi kernel: cs: unable to map card memory!

>From daemon.log:

Feb  9 22:56:41 lakshmi cardmgr[246]: starting, version is 3.1.33
Feb  9 22:56:41 lakshmi cardmgr[246]: could not open 'config': No such 
file or directory
Feb  9 22:56:41 lakshmi cardmgr[246]: exiting

When doing /etc/init.d/pcmcia restart   these same lines show up again at 
the bottom of the daemon.log.


-David


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 3com network card, trouble w pcmcia-modules

2003-02-09 Thread David Emerson
update...

I tried to install the pcmcia-modules-2.2.20 package, and it told me I had a different 
kernel-image than it wanted. I figured out that I'm running kernel-image 2.2.20 (#1) 
and the module was expecting 2.2.20 (#6) ... a world of difference, I guess.

So I downloaded a newer kernel image (testing #5 and another pcmcia-modules testing #5 
package to match, as opposed to the unstable #6 versions) and will try to install them 
most likely tomorrow...

-David


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 3com network card, trouble w pcmcia-modules

2003-02-09 Thread David Emerson
At 10:59 AM 2/9/03, Marc Mongeon wrote:
>I'll try to address what I think is the fundamental problem:  your PCMCIA
>modules are not installed.
>
>The package you want to install is "pcmcia-modules-2.2.xx" [...]

Still not workin' ... apt-get install pcmcia-modules-2.2.20 gave me exactly the 
same error as apt-get install pcmcia-modules did:

Package pcmcia-modules-2.2.20 has no available version, but exists in the 
database.
This typically means that the package was mentioned in a dependency and
never uploaded, has been obsoleted or is not available with the contents
of sources.list
E: Package pcmcia-modules-2.2.20 has no installation candidate

I looked in dselect and it does not appear to be there - a search for pcmcia 
yielded only pcmcia-sources, and the already-installed pcmcia-cs (Both version 
3.1.33-6), but no pcmcia-modules.

Just to be sure, I updated the source list, and it said it updated 2000-some 
files; but it didn't spin the cd. And when I asked it to update again, it said 
it updated the same 2000-some number of files (I'd imagine it's the number of 
.deb files)

Although there isn't an option to display the current apt-get source, if you go 
to the change source menu and do the default file/http/ftp, it first prompts 
and says there's something else selected, which was listed as:

deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-2 
(20021218)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-1 
(20021218)]/ unstable contrib main non-US/contrib non-US/main

Can I just download the .deb with the pcmcia-modules somewhere off the net? 
Would it work if saved in windows FAT file system?

Thanks!
-David



Re: 3com network card, trouble w pcmcia-modules

2003-02-09 Thread David Emerson
At 10:59 AM 2/9/03, Marc Mongeon wrote:
>I'll try to address what I think is the fundamental problem:  your PCMCIA
>modules are not installed.
>
>The package you want to install is "pcmcia-modules-2.2.xx" [...]

Still not workin' ... apt-get install pcmcia-modules-2.2.20 gave me exactly the same 
error as apt-get install pcmcia-modules did:

Package pcmcia-modules-2.2.20 has no available version, but exists in the database.
This typically means that the package was mentioned in a dependency and
never uploaded, has been obsoleted or is not available with the contents
of sources.list
E: Package pcmcia-modules-2.2.20 has no installation candidate

I looked in dselect and it does not appear to be there - a search for pcmcia yielded 
only pcmcia-sources, and the already-installed pcmcia-cs (Both version 3.1.33-6), but 
no pcmcia-modules.

Just to be sure, I updated the source list, and it said it updated 2000-some files; 
but it didn't spin the cd. And when I asked it to update again, it said it updated the 
same 2000-some number of files (I'd imagine it's the number of .deb files)

Although there isn't an option to display the current apt-get source, if you go to the 
change source menu and do the default file/http/ftp, it first prompts and says there's 
something else selected, which was listed as:

deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-2 
(20021218)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-1 
(20021218)]/ unstable contrib main non-US/contrib non-US/main

Can I just download the .deb with the pcmcia-modules somewhere off the net? Would it 
work if saved in windows FAT file system?

Thanks!
-David


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 3com network card, trouble w pcmcia-modules

2003-02-09 Thread ronin2
You can keep the package names from being truncated by doing this:
sirius:~$ columns=120;dpkg -l package*|less

Kevin

On Sun, 9 Feb 2003 12:59:27 -0600
Marc Mongeon <[EMAIL PROTECTED]> wrote:

> I'll try to address what I think is the fundamental problem:  your
> PCMCIA modules are not installed.
> 
> On Sat, Feb 08, 2003 at 01:29:52PM -0800, David Emerson wrote:
> 
> > I'll start with what appears (to my ignr'nt eyes) to be the problem:
> > 
> > /lib/modules/2.2.20/pcmcia/   does not exist.
> > 
> > /etc/pcmcia/exists but only contains one empty file, "cis"
> > /etc/pcmcia.confdoes not exist either.
> > 
> > This is probably because the pcmcia-modules package was not installed
> > properly (see below)
> 
> I think you're right about that.  See below.
> 
> > (( (And can someone explain to me why the above command works, but I
> > can't run pcmcia from the init.d directory?)   lakshmi:/etc/init.d#
> > pcmcia restart   bash: pcmcia: command not found
> > ))
> 
> The "current directory" (.) is not in your command path (nor should it
> be, as this is considered a security risk).  Use "./pcmcia restart".
> 
> > # apt-get install pcmcia-modules
> > Reading Package Lists... Done
> > Building Dependency Tree... Done
> > Package pcmcia-modules has no available version, but exists in the
> > database. This typically means that the package was mentioned in a
> > dependency and never uploaded, has been obsoleted or is not available
> > with the contents of sources.list
> > E: Package pcmcia-modules has no installation candidate
> > #
> 
> The package you want to install is "pcmcia-modules-2.2.xx" where "xx"
> matches the revision of your installed kernel.  Unfortunately, "dpkg
> --list" truncates package names (a real pain, in my opinion), so it's
> difficult to determine the exact name of the package to pass to
> "apt-get".  For that reason, I usually use "dselect" to find and install
> problematic packages like that.
> 
> Hmmm... I thought I'd read something in your original post that lead me
> to believe you were running a 2.2 kernel... I'm not sure it that's the
> case; anyway, if you're running a 2.4 kernel, the package name will be
> "kernel- pcmcia-2.4.xx".
> 
> > 
> > # apt-get install pcmcia-cs
> > Reading Package Lists... Done
> > Building Dependency Tree... Done
> > Sorry, pcmcia-cs is already the newest version.
> > 0 packages upgraded, 0 newly installed, 0 to remove and 0  not
> > upgraded.#
> > 
> 
> Looks like this is installed fine.
> 
> Marc
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> 



Re: 3com network card, trouble w pcmcia-modules

2003-02-09 Thread ronin2
You can keep the package names from being truncated by doing this:
sirius:~$ columns=120;dpkg -l package*|less

Kevin

On Sun, 9 Feb 2003 12:59:27 -0600
Marc Mongeon <[EMAIL PROTECTED]> wrote:

> I'll try to address what I think is the fundamental problem:  your
> PCMCIA modules are not installed.
> 
> On Sat, Feb 08, 2003 at 01:29:52PM -0800, David Emerson wrote:
> 
> > I'll start with what appears (to my ignr'nt eyes) to be the problem:
> > 
> > /lib/modules/2.2.20/pcmcia/   does not exist.
> > 
> > /etc/pcmcia/exists but only contains one empty file, "cis"
> > /etc/pcmcia.confdoes not exist either.
> > 
> > This is probably because the pcmcia-modules package was not installed
> > properly (see below)
> 
> I think you're right about that.  See below.
> 
> > (( (And can someone explain to me why the above command works, but I
> > can't run pcmcia from the init.d directory?)   lakshmi:/etc/init.d#
> > pcmcia restart   bash: pcmcia: command not found
> > ))
> 
> The "current directory" (.) is not in your command path (nor should it
> be, as this is considered a security risk).  Use "./pcmcia restart".
> 
> > # apt-get install pcmcia-modules
> > Reading Package Lists... Done
> > Building Dependency Tree... Done
> > Package pcmcia-modules has no available version, but exists in the
> > database. This typically means that the package was mentioned in a
> > dependency and never uploaded, has been obsoleted or is not available
> > with the contents of sources.list
> > E: Package pcmcia-modules has no installation candidate
> > #
> 
> The package you want to install is "pcmcia-modules-2.2.xx" where "xx"
> matches the revision of your installed kernel.  Unfortunately, "dpkg
> --list" truncates package names (a real pain, in my opinion), so it's
> difficult to determine the exact name of the package to pass to
> "apt-get".  For that reason, I usually use "dselect" to find and install
> problematic packages like that.
> 
> Hmmm... I thought I'd read something in your original post that lead me
> to believe you were running a 2.2 kernel... I'm not sure it that's the
> case; anyway, if you're running a 2.4 kernel, the package name will be
> "kernel- pcmcia-2.4.xx".
> 
> > 
> > # apt-get install pcmcia-cs
> > Reading Package Lists... Done
> > Building Dependency Tree... Done
> > Sorry, pcmcia-cs is already the newest version.
> > 0 packages upgraded, 0 newly installed, 0 to remove and 0  not
> > upgraded.#
> > 
> 
> Looks like this is installed fine.
> 
> Marc
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 3com network card, trouble w pcmcia-modules

2003-02-09 Thread Marc Mongeon
I'll try to address what I think is the fundamental problem:  your PCMCIA
modules are not installed.

On Sat, Feb 08, 2003 at 01:29:52PM -0800, David Emerson wrote:

> I'll start with what appears (to my ignr'nt eyes) to be the problem:
> 
> /lib/modules/2.2.20/pcmcia/   does not exist.
> 
> /etc/pcmcia/exists but only contains one empty file, "cis"
> /etc/pcmcia.confdoes not exist either.
> 
> This is probably because the pcmcia-modules package was not installed 
> properly (see below)

I think you're right about that.  See below.

> (( (And can someone explain to me why the above command works, but I can't 
> run pcmcia from the init.d directory?)
>lakshmi:/etc/init.d# pcmcia restart
>bash: pcmcia: command not found
> ))

The "current directory" (.) is not in your command path (nor should it be,
as this is considered a security risk).  Use "./pcmcia restart".

> # apt-get install pcmcia-modules
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Package pcmcia-modules has no available version, but exists in the database.
> This typically means that the package was mentioned in a dependency and
> never uploaded, has been obsoleted or is not available with the contents
> of sources.list
> E: Package pcmcia-modules has no installation candidate
> #

The package you want to install is "pcmcia-modules-2.2.xx" where "xx"
matches the revision of your installed kernel.  Unfortunately, "dpkg --list"
truncates package names (a real pain, in my opinion), so it's difficult to
determine the exact name of the package to pass to "apt-get".  For that
reason, I usually use "dselect" to find and install problematic packages
like that.

Hmmm... I thought I'd read something in your original post that lead me to
believe you were running a 2.2 kernel... I'm not sure it that's the case;
anyway, if you're running a 2.4 kernel, the package name will be "kernel-
pcmcia-2.4.xx".

> 
> # apt-get install pcmcia-cs
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Sorry, pcmcia-cs is already the newest version.
> 0 packages upgraded, 0 newly installed, 0 to remove and 0  not upgraded.
> #
> 

Looks like this is installed fine.

Marc



Re: 3com network card, trouble w pcmcia-modules

2003-02-09 Thread Marc Mongeon
I'll try to address what I think is the fundamental problem:  your PCMCIA
modules are not installed.

On Sat, Feb 08, 2003 at 01:29:52PM -0800, David Emerson wrote:

> I'll start with what appears (to my ignr'nt eyes) to be the problem:
> 
> /lib/modules/2.2.20/pcmcia/   does not exist.
> 
> /etc/pcmcia/exists but only contains one empty file, "cis"
> /etc/pcmcia.confdoes not exist either.
> 
> This is probably because the pcmcia-modules package was not installed properly (see 
>below)

I think you're right about that.  See below.

> (( (And can someone explain to me why the above command works, but I can't run 
>pcmcia from the init.d directory?)
>lakshmi:/etc/init.d# pcmcia restart
>bash: pcmcia: command not found
> ))

The "current directory" (.) is not in your command path (nor should it be,
as this is considered a security risk).  Use "./pcmcia restart".

> # apt-get install pcmcia-modules
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Package pcmcia-modules has no available version, but exists in the database.
> This typically means that the package was mentioned in a dependency and
> never uploaded, has been obsoleted or is not available with the contents
> of sources.list
> E: Package pcmcia-modules has no installation candidate
> #

The package you want to install is "pcmcia-modules-2.2.xx" where "xx"
matches the revision of your installed kernel.  Unfortunately, "dpkg --list"
truncates package names (a real pain, in my opinion), so it's difficult to
determine the exact name of the package to pass to "apt-get".  For that
reason, I usually use "dselect" to find and install problematic packages
like that.

Hmmm... I thought I'd read something in your original post that lead me to
believe you were running a 2.2 kernel... I'm not sure it that's the case;
anyway, if you're running a 2.4 kernel, the package name will be "kernel-
pcmcia-2.4.xx".

> 
> # apt-get install pcmcia-cs
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Sorry, pcmcia-cs is already the newest version.
> 0 packages upgraded, 0 newly installed, 0 to remove and 0  not upgraded.
> #
> 

Looks like this is installed fine.

Marc


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




3com network card, trouble w pcmcia-modules

2003-02-08 Thread David Emerson
Hi all,

Sorry for such a dump on my first post to the group :-) but I've spent almost 
10 hours struggling with this card. I'm sure there are archived suggestions 
that I have not tried, but as you can probably gather from the length of this 
message I have already tried and researched a lot of things - so I'm hoping 
someone can take 3 minutes to point me in the right direction. Also, if anyone 
feels inclined to point me to an etiquette link it would be appreciated!

I'm trying to get a 3com pcmcia network card (3CXE589EC) working with Debian 
3.0 r1. I installed fresh (my very first linux install & boots ever) from Cd's 
1 and 2 I downloaded. Don't know if CD 2 was necessary. I did a vanilla install.

I'm using an Intel PII / 333MHz / 64MB / Compaq Armada 1750.

It is worth noting that inserting and ejecting the card makes no beeping 
sounds. (While I have not configured the sound card - a much lower priority 
than network - I do get system beeps if I, say, try to backspace a blank line 
in xterm.)

I'll start with what appears (to my ignr'nt eyes) to be the problem:

/lib/modules/2.2.20/pcmcia/   does not exist.

/etc/pcmcia/exists but only contains one empty file, "cis"
/etc/pcmcia.confdoes not exist either.

This is probably because the pcmcia-modules package was not installed properly 
(see below)


Here's all the stuff I tried to no avail, copied from the terminal, though not 
in the same order. Most of these things I did several times at different points 
in my struggle...

# /etc/init.d/pcmcia restart
Shutting down PCMCIA services:.
Starting PCMCIA services: module directory /lib/modules/2.2.20/pcmcia not found.
#
(This same starting svcs message flashes by during bootup)

(( (And can someone explain to me why the above command works, but I can't run 
pcmcia from the init.d directory?)
   lakshmi:/etc/init.d# pcmcia restart
   bash: pcmcia: command not found
))


# cardctl ident
no pcmcia driver in /proc/devices
#

# modprobe 3c589_cs
modprobe: Can't locate module 3c589_cs
#

modconf
... doesn't list anything pcmcia.


# apt-get install pcmcia-modules
Reading Package Lists... Done
Building Dependency Tree... Done
Package pcmcia-modules has no available version, but exists in the database.
This typically means that the package was mentioned in a dependency and
never uploaded, has been obsoleted or is not available with the contents
of sources.list
E: Package pcmcia-modules has no installation candidate
#

# apt-get install pcmcia-cs
Reading Package Lists... Done
Building Dependency Tree... Done
Sorry, pcmcia-cs is already the newest version.
0 packages upgraded, 0 newly installed, 0 to remove and 0  not upgraded.
#


Interestingly, during my very first linux bootup, it appears that it might have 
gotten some of this stuff right. But on the second and every subsequent bootup, 
it is definitely not right.

((Maybe it was a big mistake to follow the advice from the unofficial guide and 
the official manual, which both said to disable pcmcia stuff when prompted, 
because it's only necessary for an External PCMCIA CD-ROM drive that's being 
used for install. Oops??))


Here are the excerpts from /var/log/daemon.log :

First boot:

Feb  7 17:08:15 lakshmi cardmgr[176]: starting, version is 3.1.33
Feb  7 17:08:15 lakshmi cardmgr[176]: watching 2 sockets
Feb  7 17:08:15 lakshmi cardmgr[176]: socket 1: 3Com 589 Ethernet
Feb  7 17:08:15 lakshmi cardmgr[176]: executing: 'modprobe 3c589_cs'
Feb  7 17:08:16 lakshmi cardmgr[176]: executing: './network start eth0'
Feb  7 17:08:16 lakshmi cardmgr[176]: + Ignoring unknown interface eth0=eth0.

And later on... (Why are the time/dates are out of sequence??)

Feb  7 18:52:58 lakshmi modprobe: modprobe: Can't locate module char-major-45
Feb  8 02:52:59 lakshmi cardmgr[176]: executing: './network check eth0'
Feb  8 02:52:59 lakshmi cardmgr[176]: + sh: ./network: No such file or directory
Feb  8 02:52:59 lakshmi cardmgr[176]: check cmd exited with status 127
Feb  8 02:52:59 lakshmi cardmgr[176]: exiting
Feb  7 18:53:03 lakshmi wwwoffled[9835]: Exit signalled. 

The above are the only cardmgr calls in my entire daemon.log, which has a good 
number of linux boots listed (I was going back and forth from windoze to linux 
so I could get internet access and then try this stuff!)


And here are excerpts from /var/log/messages (I edited some repetetive lines 
out where you see "Note from David"):

First boot:

Feb  7 17:08:14 lakshmi kernel: Adding Swap: 188992k swap-space (priority -1)
Feb  7 17:08:14 lakshmi kernel: Linux PCMCIA Card Services 3.1.33
Feb  7 17:08:14 lakshmi kernel:   kernel build: 2.2.20 #1 Sat Apr 20 11:45:28 
EST 2002
Feb  7 17:08:14 lakshmi kernel:   options:  [pci] [cardbus] [apm]
Feb  7 17:08:14 lakshmi kernel: PCI routing table version 1.0 at 0xf09a0
Feb  7 17:08:14 lakshmi kernel:   00:11.0 -> irq 11
Feb  7 17:08:14 lakshmi kernel:   00:11.1 -> irq 11
Feb  7 17:08:14 lakshmi kernel: Intel ISA/PCI/CardBus PCIC probe:
Feb  7 17:08:14 lakshmi ker

3com network card, trouble w pcmcia-modules

2003-02-08 Thread David Emerson
Hi all,

Sorry for such a dump on my first post to the group :-) but I've spent almost 10 hours 
struggling with this card. I'm sure there are archived suggestions that I have not 
tried, but as you can probably gather from the length of this message I have already 
tried and researched a lot of things - so I'm hoping someone can take 3 minutes to 
point me in the right direction. Also, if anyone feels inclined to point me to an 
etiquette link it would be appreciated!

I'm trying to get a 3com pcmcia network card (3CXE589EC) working with Debian 3.0 r1. I 
installed fresh (my very first linux install & boots ever) from Cd's 1 and 2 I 
downloaded. Don't know if CD 2 was necessary. I did a vanilla install.

I'm using an Intel PII / 333MHz / 64MB / Compaq Armada 1750.

It is worth noting that inserting and ejecting the card makes no beeping sounds. 
(While I have not configured the sound card - a much lower priority than network - I 
do get system beeps if I, say, try to backspace a blank line in xterm.)

I'll start with what appears (to my ignr'nt eyes) to be the problem:

/lib/modules/2.2.20/pcmcia/   does not exist.

/etc/pcmcia/exists but only contains one empty file, "cis"
/etc/pcmcia.confdoes not exist either.

This is probably because the pcmcia-modules package was not installed properly (see 
below)


Here's all the stuff I tried to no avail, copied from the terminal, though not in the 
same order. Most of these things I did several times at different points in my 
struggle...

# /etc/init.d/pcmcia restart
Shutting down PCMCIA services:.
Starting PCMCIA services: module directory /lib/modules/2.2.20/pcmcia not found.
#
(This same starting svcs message flashes by during bootup)

(( (And can someone explain to me why the above command works, but I can't run pcmcia 
from the init.d directory?)
   lakshmi:/etc/init.d# pcmcia restart
   bash: pcmcia: command not found
))


# cardctl ident
no pcmcia driver in /proc/devices
#

# modprobe 3c589_cs
modprobe: Can't locate module 3c589_cs
#

modconf
... doesn't list anything pcmcia.


# apt-get install pcmcia-modules
Reading Package Lists... Done
Building Dependency Tree... Done
Package pcmcia-modules has no available version, but exists in the database.
This typically means that the package was mentioned in a dependency and
never uploaded, has been obsoleted or is not available with the contents
of sources.list
E: Package pcmcia-modules has no installation candidate
#

# apt-get install pcmcia-cs
Reading Package Lists... Done
Building Dependency Tree... Done
Sorry, pcmcia-cs is already the newest version.
0 packages upgraded, 0 newly installed, 0 to remove and 0  not upgraded.
#


Interestingly, during my very first linux bootup, it appears that it might have gotten 
some of this stuff right. But on the second and every subsequent bootup, it is 
definitely not right.

((Maybe it was a big mistake to follow the advice from the unofficial guide and the 
official manual, which both said to disable pcmcia stuff when prompted, because it's 
only necessary for an External PCMCIA CD-ROM drive that's being used for install. 
Oops??))


Here are the excerpts from /var/log/daemon.log :

First boot:

Feb  7 17:08:15 lakshmi cardmgr[176]: starting, version is 3.1.33
Feb  7 17:08:15 lakshmi cardmgr[176]: watching 2 sockets
Feb  7 17:08:15 lakshmi cardmgr[176]: socket 1: 3Com 589 Ethernet
Feb  7 17:08:15 lakshmi cardmgr[176]: executing: 'modprobe 3c589_cs'
Feb  7 17:08:16 lakshmi cardmgr[176]: executing: './network start eth0'
Feb  7 17:08:16 lakshmi cardmgr[176]: + Ignoring unknown interface eth0=eth0.

And later on... (Why are the time/dates are out of sequence??)

Feb  7 18:52:58 lakshmi modprobe: modprobe: Can't locate module char-major-45
Feb  8 02:52:59 lakshmi cardmgr[176]: executing: './network check eth0'
Feb  8 02:52:59 lakshmi cardmgr[176]: + sh: ./network: No such file or directory
Feb  8 02:52:59 lakshmi cardmgr[176]: check cmd exited with status 127
Feb  8 02:52:59 lakshmi cardmgr[176]: exiting
Feb  7 18:53:03 lakshmi wwwoffled[9835]: Exit signalled. 

The above are the only cardmgr calls in my entire daemon.log, which has a good number 
of linux boots listed (I was going back and forth from windoze to linux so I could get 
internet access and then try this stuff!)


And here are excerpts from /var/log/messages (I edited some repetetive lines out where 
you see "Note from David"):

First boot:

Feb  7 17:08:14 lakshmi kernel: Adding Swap: 188992k swap-space (priority -1)
Feb  7 17:08:14 lakshmi kernel: Linux PCMCIA Card Services 3.1.33
Feb  7 17:08:14 lakshmi kernel:   kernel build: 2.2.20 #1 Sat Apr 20 11:45:28 EST 2002
Feb  7 17:08:14 lakshmi kernel:   options:  [pci] [cardbus] [apm]
Feb  7 17:08:14 lakshmi kernel: PCI routing table version 1.0 at 0xf09a0
Feb  7 17:08:14 lakshmi kernel:   00:11.0 -> irq 11
Feb  7 17:08:14 lakshmi kernel:   00:11.1 -> irq 11
Feb  7 17:08:14 lakshmi kernel: Intel ISA/PCI/CardBus PCIC probe:
Feb  7 17:08:14 lakshmi kerne