How can I get Linux to pick up my ethernet card, it is from a company called Safeway

.Safeway Website

I was reading through some stuff and it is in the /proc/pci

Myson Technology Inc

If you need some further information just let me know

what is the chipset that the card is based on? that is all thatis liekly to matter, manufacturers name raerly carry any weight in linux. check the card to see what the chip set... "lspci" should also tell you the chpiset. particulary i'd expect rtl-8139 or a similar name to be listed. with a silly picture of a crab on the chip in question.

I tried that it comes up with the following

Ethernet Controller: MYSON Technology Inc: Unknown Device 0803

I have looked at the card itself and there is no obvious markings as to the chipset although am led to believe it is based on a Realtek card but not sure which one.

Given the feedback (Myson Technology Inc), it would appear
that you have one of those odd Taiwanese/Chinese cards. I have
the same problem with my Asound cards.

While /proc/pci will probably be able to show you a card exists,
no functionality will be forthcoming unless a driver is loaded.
You will probably have to recompile your kernel (2.4.x) selecting
Myson under the networking drivers section of the configure
menu and compile in the kernel or as a module. If you compile as
a module include the following in /etc/rc.d/rc.modules (or
whatever your modules file is):

/sbin/modprobe/ fealnx

Don't forget to set it up as "eth0", "eth1" or whatever.

You should then be able to see it recognized as you boot or
with 'dmesg'.

If you're already aware of all this and the problem is something
else, forgive the rehash.

I did have a driver on disc although if I try to install it says it is too old for the Kernel I am using.

When I try to recompile using the following instructions

This is after following the instructions on readme.


Installation:

1. copy the source code fealnx.c to Linux,

2. compile the source code, the instruction for compiling the driver is
as follows:

#gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet -Wall
-Wstrict-prototypes -O6 -c fealnx.c

3. insert the driver as module,

#insmod fealnx.o

4. bind your card to an IP address

#ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}

5. add your card to IP routing table,

#route add -net ${NETWORK} netmask ${NETMADK} eth0

6. now, you should be able to ping local network.


I get lots of errors "Deferencing pointer to incomplete type"

And it is not creating fealnx.o file.

Any suggestions from there.

I also went through that type of hassle. What you are doing
is trying to compile the driver separately with the driver
source code. I cannot say for sure, but by doing this you are
bypassing needed support in the kernel.

You must recompile the kernel (must be 2.4.x ) with
Myson support and select either in kernel or module. If you
select module, and follow the rest of the build steps:

make bzImage
make modules
make modules_install

you will find fealnx.o in /lib/modules/2.4.x/kernel/drivers/net.
At least you find it there on a Slackware distribution.

Again add the following to /etc/rc.d/rc.modules:

/sbin/modprobe/ fealnx

and you should be ready to go.

If you are unfamiliar with recompiling a kernel here is some good
info:

Compile steps:

cd /lib/modules rm -r 2.4.5 if it exists. Best to compile modules with a clean slate so delete the /lib/modules/ directories for whatever version you are going to compile. or: mv 2.4.5 default (or whatever name you wish to associate with the installed kernel) to maintain a good copy to be used in case of compile problems

cd/usr/src/linux Do not try to use the symlink /usr/src/linux; works better if the actual source directory is used.

make menuconfig Select what you want to compile in the kernel and whether you want a module instead of direct kernel compile

make mrproper For a first time compile this cleans up some of the source files and purges whatever .config file you might have had in the directory from the install. Basically cleans the slate, but you might want to keep a copy of the installed .config before doing this

make dep This creates all the dependencies for the current configuration; i.e. which header and other source files are to be used to compile the kernel and various modules. (> dump quiets the output of all make steps and shows only errors and warnings - good for diagnostic purposes use in all steps)

make clean Cleans up any binary or intermediate files that may be left from the last compile

make bzImage > dump Compiles the kernel which will be located in: /usr/src/linux-/arch/i386/boot/bzImage

make modules > dump Compiles all modules

make modules_install > dump Creates the new /lib/modules/ directories and installs drivers and all other modules. (These modules will normally be compiled as driver.o/module.o whereas the installed modules will generally be of the module.o.gz variety)

copy the new kernel to /boot - cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-new (or whatever name you want)

Run LILO Update LILO for the new kernel (and System.map).

Note: You must have gcc and all of its associated libraries in order
to perform a kernel recompile. Also, the Myson support is only
available in the 2.4.x kernel versions. I use 2.4.5 which works
just fine.

Hope this is clear.

Before going that far... what does an "lsmod" show?
What does the file /etc/modules.conf look like?

What commonly happens is that as drivers mature, they get added into the kernel source so extra drivers are not often needed.

-K.

I have the same card with the same problem. I am using RH8.0 kernel version 2.4.18-14.

raypen

I tryed your instructions and when I get to "make modules"
it returns some errors. If any help I will write them here. Will it work if I run make dep, make bzImage and then add bzimage to grub.conf?

A question how to configure grub.conf to boot new kernel
this is may grub.conf

title Redhat 2.4.18-14
root (hd0,1)
kernel /vmlinuz-2.4.18-17.8.0 ro root=LABEL=/
initrd /initrd-2.4.18-17.8.0.img

how to add bzImage so that old kernel stay intact?

thanks!

I didn't mean to imply that you should skip any steps in a kernal
compile; all are necessary including 'make dep'. However, 'make mrproper' is usually only performed once when a kernel compile
is performed for the first time. If you skipped 'make dep', this
could be the source of your problem.

I do not use grub, but I'm sure it's similar to LILO. You have to
edit the grub.conf file to add the new kernal name (whatever
you call it). Before you make changes, take a good look at this
file and read the grub instructions. You'll see that you can compile
several different kernels, give them different names and the grub
startup menu should allow you to make a selection of any of
them each time you boot.

When you then run /sbin/grub (or whatever the command is),
grub takes the information in the grub.conf file to create a new
boot record reflecting the changes (same thing /sbin/lilo does).

I don't use Redhat, so the grub.conf file looks a little strange to
me, but it would appear that it identifies the same basic elements
that a LILO.conf file does, i.e:

image = /boot/newlinux
root = /dev/hda3
label = NewLinux
read-only

If I had saved the original kernel and wanted to be able to
select either one from a boot menu, lilo.conf might look like:

image = /vmlinuz
root = /dev/hda3
label = Linux
read-only

image = /boot/newlinux
root = /dev/hda3
label = NewLinux
read-only

Hope this helps.

me again.

followed your instructions raypen but the thing is not working. When I do "make modules" it returns a pile of warnings and finally an error. Then runinng "make modules_install" also returns errors and then stops. If any help I will upload returns of commands: lsmod, dmesg, make dep, make modules, make modules_install.

Before posting the entire output try compiling with
'> dump' to elminate extraneous output isolating
only warnings and errors. Like this:

make memuconfig
make dep > dump
make clean > dump
make bzImage > dump
make modules > dump
make modules_install > dump

Warnings are just that, warnings, and are not necessarily
cause for concern. Errors that actually halt the compile
are obviously serious and should be the focus of your
trouble shooting efforts.

Often compile errors are the result of missing libraries
because you have not installed all of the packages
required for a full development system. First look at
the error messages with this in mind; you might be able
to correct the situation by installing an extra
development package or two.

Failing that, go ahead and post the warnings and errors.