Re: PCMCIA Ethernet failure under 2.4.9
from the menuconfig--> help option:
To use your PC-cards, you will need supporting software from David x
x Hinds' pcmcia-cs package (see the file Documentation/Changes for x
x location). Please also read the PCMCIA-HOWTO, available from x
x http://www.linuxdoc.org/docs.html#howto
have you installed the pcmcia-cs package as well? Did you look in /usr/share/doc/pcmcia-cs?
there's a README-2.4 in there. if you don't have cardctl, you probably haven't installed the package(s)
glen
On Sun, Sep 30, 2001 at 01:13:06PM +0900, Curt Howland wrote:
> Glen Mehn wrote:
> >
> > your pcmcia settings should still remain in /etc/pcmcia. Try removing the stuf fyou did and adding the entry for pcmcia in /etc/pcmcia/network.opts.
>
> I did. The only difference now is that I get "ignorning unknown
> interface eth0=eth0".
>
> > you can use ifup/ifdown to manage the intervace, but also cardctl will stop/start the card (and the interface).
>
> I have no such command as "cardctl", all I have is "cardmgr", and there
> is no manual entry for it.
>
> Simply running the command causes two beeps to sound, and no change in
> response.
>
> I found /etc/pcmcia/network script, tried ./network start eth0, and got
> the error:
>
> cat: /var/lib/misc/pcmcia-scheme: No such file or directory
>
> > You'll probably also want to read the kernel-pcmcia docs, assuming <?> that you're using the kernel drivers, rather than the third party add-ons.
>
> Your assumption is correct. Would you kindly point me to the location of
> such documents?
>
> > glne
>
> Curt-
>
> > On Sat, Sep 29, 2001 at 09:19:07PM +0900, Curt Howland wrote:
> > > After trying to upgrade to woody from potato, I found that my pcmcia
> > > ethernet card would not work under kernel 2.4.9-AMD-K6.
> > >
> > > With 2.2.18, the hardware was pcmcia i82365, ethernet card NE2000
> > > (module ne) with io and irq set by hand.
> > >
> > > I looked through the list archives, and found that under 2.4.x kernels,
> > > the pcmcia driver is supposed to now be yenta_socket, and the ethernet
> > > card as pcnet_cs. Both modules load fine, and the LED's show link
> > > active, but eth0 will not activate.
> > >
> > > At this point I decided to eliminate any conflict problems, downloaded
> > > the latest woody cd, reformatted and installed with no legacy software,
> > > and repeated the above with no success.
> > >
> > > "linuxconf" and "netconf" create the /etc/conf.modules file in it, which
> > > the kernel ignores and uses /etc/modules.conf They also do not recognize
> > > pcnet_cs as a valid network interface module.
> > >
> > > I added "alias eth0 pcnet_cs" to the modules.conf by hand in the
> > > modutils directory first. The port still does not activate. I put an
> > > entry in /etc/network/interfaces for both the loopback and eth0
> > > interfaces. I was a little bit surprised that no loopback interface had
> > > been defined.
> > >
> > > This is all I can get out of it: Please forgive any typo's, I have also
> > > been completely unsuccessful in trying to get copy and paste working in
> > > the KDE workspace. Every step forward for me seems to break two other
> > > things. I had to type the below by hand.
> > >
> > > # ifup eth0
> > > ifup: interface eth0 already configured
> > > # ifdown eth0
> > > eth0: unknown interface: No such device
> > > # ifup eth0
> > > SIOCSIFADDR: No such device
> > > eth0: unknown interface: No such device
> > > SIOCSIFNETMASK: No such device
> > > eth0: unknown interface: No such device
> > >
> > > If anyone can say "use this and this driver", I would be very grateful.
> > > Unfortunately, the only instructions I've been able to find, which I
> > > have tried, have failed.
> > >
> > > Curt-
> > >
> > > ---
> > > September 11th, 2001
> > > The proudest day for gun control and central planning
> > > advocates in American history.
> > >
> > >
> > > --
> > > To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> > >
> >
> > --
> > Glen S Mehn
> > Lead Systems Administrator SquareTrade, Inc
> > glen@squaretrade.com Building Trust in Transactions (sm)
>
--
Glen S Mehn
Lead Systems Administrator SquareTrade, Inc
glen@squaretrade.com Building Trust in Transactions (sm)
Reply to: