LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   tulip.c installation (https://www.linuxquestions.org/questions/linux-software-2/tulip-c-installation-16520/)

c0c0deuz 03-18-2002 11:14 AM

tulip.c installation
 
My pcmcia card xircom 10/100 network pc card XE-2000 as not been detect by my RH7.2.

It seems that it could be a tulip.c but i never install a driver so far, what is the way to go, i download the driver and here i am... begging for help :-)

Also: How can i tell if it sees my pcmcia card?
thanks.

acid_kewpie 03-18-2002 11:25 AM

you'll already have the tulip driver installed on your system, you'd need to add a line like "alias eth0 tulip" to /etc/modules.conf and maybe insmod it, and then maybe insmod it, and then use netconfig or such. to be honest, i'm never really sure what to suggest with things like that, as mine always seem to work first time if ever...

finegan 03-18-2002 11:49 AM

I don't think its tulip anyway... it might be tulip_cs, or possibly another one. The pcmcia drivers tend not to be the same drivers as the normal pci cards. You might also be having problems with pcmcia because RedHat switched to in-kernel pcmcia a little early and a number of people are having problems with it. What's the output from "lsmod"?

Is there a 'yenta_socket' listed? also post anything called 'tulip_cs', or for that matter, anything with a '_cs' from "lsmod".

Another big telltale of whether the drivers are loading correctly is the beep-code of pcmcia. If you hear one high-pitched tone on load that's the cardmgr finding the card. If you hear another one, that's the thing loading the module and binding it to the card. If the second tone is more like a "bonk", then it failed to initialize the card.

Cheers,

Finegan

c0c0deuz 03-18-2002 11:52 AM

if i insert "alias eth0 tulip" to /etc/modules.conf
i do have a light on my card but it doesn't work, the light is not green...
the reason i ask how to install that particular module is that they change the offset address to 0x166 instead of 0x170 for it to work with xircom cards (see: http://ivs.cs.uni-magdeburg.de/~danilo/linux.shtml )
i have the driver but i don't know how to load it :-(

c0c0deuz 03-18-2002 05:07 PM

the output of lsmod give me
xirc2ps_cs 12032 0
ds 7056 1 (xirc2ps_cs)
yenta_socket 9488 1
pcmcia_core 41600 0 (xirc2ps_cs ds yenta_socket)

no sound... i guess that the sound is not coufigured yet...

c0c0deuz 03-18-2002 05:13 PM

OK, after the sound config,
i've got a double bip at startup.
Bip kind of bip, if you know what i mean :^)

finegan 03-18-2002 06:30 PM

Dude, Xirc2ps_cs is the device driver for that card... at least I'm pretty certain. From the man page:


NAME
xirc2ps_cs - Xircom CE2ps (and newer) device driver

SYNOPSIS
insmod xirc2ps_cs.o [pc_debug=n] [full_duplex=n]
[irq_list=i,j,...] [if_port=n] [lockup_hack=n]

DESCRIPTION
xirc2ps_cs is the low-level Card Services driver for the
Xircom 16-bit PCMCIA ethernet adapters. When this driver
is attached to a card, it allocates the next available
ethernet device.

PARAMETERS
pc_debug=n
Selects the PCMCIA debugging level. This parameter
is only available if the module is compiled with
debugging enabled. A non-zero value enables debug-
ging.

if_port=n


It should ifconfig eth0 up. If those two tones were more or less the same then it loaded the right module and initialized the card.

Cheers,

Finegan

c0c0deuz 03-18-2002 06:41 PM

Those two tone are the same if i use 'alias eth0 xirc2ps_cs
but if i try:
/etc/rc.d/init.d/network start,
it fails eth0
by the way, it is the same as when i use alias eth0 tulip_cs

finegan 03-18-2002 06:48 PM

Who cares what RH's init scripts think... they're not built for pcmcia. Your pcmcia drivers like pcmcia_core and yenta_socket are getting loaded after all of the normal network boot stuff so of course its failing. If you want to use pre-built scripts, the ones you should be aiming for are /etc/pcmcia/network.opts and if you want to restart networking by hand, invoke:

/etc/rc.d/init.d/pcmcia restart

To see if the nic is working:

ifconfig eth0 111.111.111.111 up

then,

ifconfig

If it keeps settings its ready to roll. Offhand, are you using dhcp or assigning everything statically?

Cheers,

Finegan

c0c0deuz 03-18-2002 07:08 PM

dhcp
how to get my ip then?

finegan 03-18-2002 07:23 PM

In that script there's an option for dhcp=Y, but really, hand invoke the nasty little daemon:

dhcpcd eth0

Cheers,

Finegan

c0c0deuz 03-18-2002 07:28 PM

Wo!
that's too fast for me dude...
i look in config.opts and how the hell am i supposed to know the option to put in?
maybe:
module ''xirc2ps_cs'' with no option?

finegan 03-18-2002 07:35 PM

No no, not config.opts, cardmgr reads that, don't fiddle with that, network.opts, should have a section like:

# Network adapter configuration
#
# The address format is "scheme,socket,instance,hwaddr".
#
# Note: the "network address" here is NOT the same as the IP address.
# See the Networking HOWTO. In short, the network address is the IP
# address masked by the netmask.
#
case "$ADDRESS" in
*,*,*,*)
INFO="Sample private network setup"
# Transceiver selection, for some cards -- see 'man ifport'
IF_PORT=""
# Use BOOTP (via /sbin/bootpc, or /sbin/pump)? [y/n]
BOOTP="n"
# Use DHCP (via /sbin/dhcpcd, /sbin/dhclient, or /sbin/pump)? [y/n]
DHCP="n"
# If you need to explicitly specify a hostname for DHCP requests
DHCP_HOSTNAME=""
# Host's IP address, netmask, network address, broadcast address
IPADDR=""
NETMASK="255.255.255.0"


change DHCP="n" to "y" and you're good to go.

Cheers,

Finegan

c0c0deuz 03-18-2002 07:36 PM

trying dhcpcd eth0 takes a while,
but come back to #
if i do ifconfig then... it gives me the loopback only.
it doesn't seems to work! :^(

c0c0deuz 03-18-2002 07:40 PM

There is no config file under *network ???


All times are GMT -5. The time now is 10:46 PM.