Re: PCMCIA Ethernet failure under 2.4.9
> kernel pcmcia support is somewhat still experimental-- in the pcmcia-howto. Hmmm... Such is life, I guess. > however, I had trouble compiling the pcmcia-cs packages. I didn't compile anything, I used only the packages and modules that came with the kernel image. > Try installing the pcmcia-cs packages first, then the kernel, and then see > how we go. I think what worked was finally having every last piece of the puzzle, the pcmcia-cs package was just the last straw. Also, *NOT* using linuxconf or netconfig. > Did you install pcmcia support as modules? Yes, I selected the kernel modules for pcmcia. But I had to search the archives for mention of the fact that the names had changed since 2.2.18. The problem being that the old modules are *still there*. They just don't work. > glen Curt-
Re: PCMCIA Ethernet failure under 2.4.9
> kernel pcmcia support is somewhat still experimental-- in the pcmcia-howto. Hmmm... Such is life, I guess. > however, I had trouble compiling the pcmcia-cs packages. I didn't compile anything, I used only the packages and modules that came with the kernel image. > Try installing the pcmcia-cs packages first, then the kernel, and then see how we go. I think what worked was finally having every last piece of the puzzle, the pcmcia-cs package was just the last straw. Also, *NOT* using linuxconf or netconfig. > Did you install pcmcia support as modules? Yes, I selected the kernel modules for pcmcia. But I had to search the archives for mention of the fact that the names had changed since 2.2.18. The problem being that the old modules are *still there*. They just don't work. > glen Curt- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA Ethernet failure under 2.4.9
kernel pcmcia support is somewhat still experimental-- in the pcmcia-howto. however, I had trouble compiling the pcmcia-cs packages. Try installing the pcmcia-cs packages first, then the kernel, and then see how we go. Did you install pcmcia support as modules? Also, you'll need to install the pcmcia support packages-- apt-get install pcmcia-cs -- that's the additional software. I can send you the readme-2.4 if it doesn't show up there. glen > > 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) > > No, actually, there is no file named readme-2.4, there is a readme that > also says there's a readme-2.4. > > > glen > > Thanks, Glen. You've been wonderful. This has turned into a very > interesting quest. > > The last time I looked in the HOW-TO's, there was nothing about this > either. > > Interesting. Why would things get harder with a new version? > > Curt- > -- Glen S Mehn Lead Systems Administrator SquareTrade, Inc [EMAIL PROTECTED] Building Trust in Transactions (sm)
Re: PCMCIA Ethernet failure under 2.4.9
kernel pcmcia support is somewhat still experimental-- in the pcmcia-howto. however, I had trouble compiling the pcmcia-cs packages. Try installing the pcmcia-cs packages first, then the kernel, and then see how we go. Did you install pcmcia support as modules? Also, you'll need to install the pcmcia support packages-- apt-get install pcmcia-cs -- that's the additional software. I can send you the readme-2.4 if it doesn't show up there. glen > > 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) > > No, actually, there is no file named readme-2.4, there is a readme that > also says there's a readme-2.4. > > > glen > > Thanks, Glen. You've been wonderful. This has turned into a very > interesting quest. > > The last time I looked in the HOW-TO's, there was nothing about this > either. > > Interesting. Why would things get harder with a new version? > > Curt- > -- Glen S Mehn Lead Systems Administrator SquareTrade, Inc [EMAIL PROTECTED]Building Trust in Transactions (sm) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA Ethernet failure under 2.4.9
Glen Mehn wrote: > 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) No, actually, there is no file named readme-2.4, there is a readme that also says there's a readme-2.4. > glen Thanks, Glen. You've been wonderful. This has turned into a very interesting quest. The last time I looked in the HOW-TO's, there was nothing about this either. Interesting. Why would things get harder with a new version? Curt-
Re: PCMCIA Ethernet failure under 2.4.9
Final follow-up: Re-added entries to /etc/network/interfaces, getting the pcmcia-cs and iptables packages, and checking out the iptables masquerade instructions, the ethernet is now working and running as a gateway for my other machine. Happy days, thank you Glen. One point, it seems that there is an ipchains module that can be loaded in the debian 2.4.9 kernel. I deliberately did not use ipchains, so I don't hamstring myself into an older tech. It's nice to know it's there, however, but the ipchains syntax is almost identical. Thanks for the help, and I hope it's easier to point the next person to the answer. This should not have gotten harder, and linuxconf and netconfig need to be fixed. I will be submitting a bug report. Curt-
Re: PCMCIA Ethernet failure under 2.4.9
Glen Mehn wrote: > 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) No, actually, there is no file named readme-2.4, there is a readme that also says there's a readme-2.4. > glen Thanks, Glen. You've been wonderful. This has turned into a very interesting quest. The last time I looked in the HOW-TO's, there was nothing about this either. Interesting. Why would things get harder with a new version? Curt- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA Ethernet failure under 2.4.9
Final follow-up: Re-added entries to /etc/network/interfaces, getting the pcmcia-cs and iptables packages, and checking out the iptables masquerade instructions, the ethernet is now working and running as a gateway for my other machine. Happy days, thank you Glen. One point, it seems that there is an ipchains module that can be loaded in the debian 2.4.9 kernel. I deliberately did not use ipchains, so I don't hamstring myself into an older tech. It's nice to know it's there, however, but the ipchains syntax is almost identical. Thanks for the help, and I hope it's easier to point the next person to the answer. This should not have gotten harder, and linuxconf and netconfig need to be fixed. I will be submitting a bug report. Curt- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA Ethernet failure under 2.4.9
Glen Mehn wrote: > > 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 forx > x location). Please also read the PCMCIA-HOWTO, available fromx > x http://www.linuxdoc.org/docs.html#howto Thank you. I was hoping that the 2.4.9 kernel package would not require that I recompile it to do what the 2.2.18 kernel did "out of the box". Or should I say, "out of the .deb"? Thus I never was in the menuconfig. Only modconf. > 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) No, that package was not installed. The dependencies in dselect recomended "modules", but all the recomended modules were 2.2.x kernel, not 2.4, so I will have to assume that the 2.4.9 package has them. [music from Jepardy] Ok, dselect process done, it asked me to interactively configure the network interface. It doesn't work, ifup still says "ignoring unknown interface", but at least I can go off and read some docs that weren't there before. I'll just say that this was straight forward and working in 2.2.18, I'm surprised that it has gotten more obscure, more difficult in 2.4.x and the linuxconf and netconfig tools make it worse. H > glen Curt- > > 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. >
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 forx x location). Please also read the PCMCIA-HOWTO, available fromx 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 [EMAIL PROTECTED] > > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > > > -- > > Glen S Mehn > > Lead Systems Administrator SquareTrade, Inc > > [EMAIL PROTECTED]Building Trust in Transactions (sm) > -- Glen S Mehn Lead Systems Administrator SquareTrade, Inc [EMAIL PROTECTED] Building Trust in Transactions (sm)
Re: PCMCIA Ethernet failure under 2.4.9
Glen Mehn wrote: > > 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 forx > x location). Please also read the PCMCIA-HOWTO, available fromx > x http://www.linuxdoc.org/docs.html#howto Thank you. I was hoping that the 2.4.9 kernel package would not require that I recompile it to do what the 2.2.18 kernel did "out of the box". Or should I say, "out of the .deb"? Thus I never was in the menuconfig. Only modconf. > 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) No, that package was not installed. The dependencies in dselect recomended "modules", but all the recomended modules were 2.2.x kernel, not 2.4, so I will have to assume that the 2.4.9 package has them. [music from Jepardy] Ok, dselect process done, it asked me to interactively configure the network interface. It doesn't work, ifup still says "ignoring unknown interface", but at least I can go off and read some docs that weren't there before. I'll just say that this was straight forward and working in 2.2.18, I'm surprised that it has gotten more obscure, more difficult in 2.4.x and the linuxconf and netconfig tools make it worse. H > glen Curt- > > 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. > > > > > > > > >
Re: PCMCIA Ethernet failure under 2.4.9
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 [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > -- > Glen S Mehn > Lead Systems Administrator SquareTrade, Inc > [EMAIL PROTECTED]Building Trust in Transactions (sm)
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 forx x location). Please also read the PCMCIA-HOWTO, available fromx 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 [EMAIL PROTECTED] > > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > > > -- > > Glen S Mehn > > Lead Systems Administrator SquareTrade, Inc > > [EMAIL PROTECTED]Building Trust in Transactions (sm) > -- Glen S Mehn Lead Systems Administrator SquareTrade, Inc [EMAIL PROTECTED]Building Trust in Transactions (sm) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA Ethernet failure under 2.4.9
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 [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > -- > Glen S Mehn > Lead Systems Administrator SquareTrade, Inc > [EMAIL PROTECTED]Building Trust in Transactions (sm) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA Ethernet failure under 2.4.9
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. you can use ifup/ifdown to manage the intervace, but also cardctl will stop/start the card (and the interface). 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. glne 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 [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Glen S Mehn Lead Systems Administrator SquareTrade, Inc [EMAIL PROTECTED] Building Trust in Transactions (sm)
Re: PCMCIA Ethernet failure under 2.4.9
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. you can use ifup/ifdown to manage the intervace, but also cardctl will stop/start the card (and the interface). 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. glne 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 [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Glen S Mehn Lead Systems Administrator SquareTrade, Inc [EMAIL PROTECTED]Building Trust in Transactions (sm) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
PCMCIA Ethernet failure under 2.4.9
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.
PCMCIA Ethernet failure under 2.4.9
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 [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
