Network card and kernel module problems

Network card and kernel module problems

[Amin]

Hi all,

I use a Surecom EP-320X-S 100/10M Ethernet PCI adapter; I believe it's
Myson MTD3xx compatible --- at least, I've used it before with Myson's
fealnx.o module in Red Hat Linux 7.3.  The problem is I upgraded to RH8.0
and find that the kernel does not already support the card.  I tried
recompiling with built-in support (for the Myson module).  kudzu detected
the card at startup and configured it.  I've set it up it using Red Hat's
``neat'' tool (it uses DHCP), but it says it can't determine IP
information, and to check the cables.

Also, could anybody tell me of a way to check the various distros' kernels
to see if they come with built-in support for my card?

Help is much appreciated.

Yawar Amin

--
Why can't we just spell it orderves?
(Get Witty Auto-Generated Signatures from http://SmartBee.org)


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Network card and kernel module problems

[pa3gcu]

On Sunday 02 February 2003 15:56, Amin wrote:
> Hi all,
>
> I use a Surecom EP-320X-S 100/10M Ethernet PCI adapter; I believe it's
> Myson MTD3xx compatible --- at least, I've used it before with Myson's
> fealnx.o module in Red Hat Linux 7.3.  The problem is I upgraded to RH8.0
> and find that the kernel does not already support the card.  I tried
> recompiling with built-in support (for the Myson module).  kudzu detected
> the card at startup and configured it.  I've set it up it using Red Hat's
> ``neat'' tool (it uses DHCP), but it says it can't determine IP
> information, and to check the cables.

Then that means the card was detected and the module was loaded, have you 
done what it says.????

You may need to use dhcpcd with options to obtain a IP# from your isp.
IE, hostname ??.

>
> Also, could anybody tell me of a way to check the various distros' kernels
> to see if they come with built-in support for my card?
>
> Help is much appreciated.
>
> Yawar Amin

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Network card and kernel module problems

[Amin]

Hi Richard,

> Then that means the card was detected and the module was loaded, have
you
> done what it says.????

I have made sure that the hardware works.  In fact, I dual-boot Windows 98
on the same machine and Windows never has any problems with the card,
including now.

> You may need to use dhcpcd with options to obtain a IP# from your isp.
> IE, hostname ??.

Do you mean that I have to set up a DHCP server on my machine and
configure it ... ?  I sure hope there's an easier way than that ... .

I'm beginning to think I've mixed up different kernel module dependencies.
The short story is I need help sorting out the modules for use with my two
kernels: 2.4.18-14 and 2.4.18-14custom.  The long story is: when I
originally installed RH8.0 and found it didn't already support my NIC, I
recompiled the kernel with

make xconfig; make dep; make modules; make modules_install; make bzImage

and tried to boot the new kernel.  Eventually I got it to boot, but it
failed to detect/insert a lot of modules, which seems strange in
retrospect because I think I actually specified only one loadable module;
all the others were built-in.  I recompiled again, with the same results.
A lot of error messages courtesy of depmod as it tries to find module
dependencies --- things like input.o, soundcore.o, etc.  I've recompiled
twice after that, with a slightly different command order:

make xconfig; make dep; make bzImage; make modules; make modules_install

But still I get the same module dependency problems during boot.  Help!

Yawar Amin

----- Original Message -----
From: "pa3gcu" <pa3gcu@zeelandnet.nl>
To: "Amin" <raihan@citech-bd.com>; <linux-newbie@vger.kernel.org>
Sent: Sunday, 02 February, 2003 22:15
Subject: Re: Network card and kernel module problems

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Network card and kernel module problems

[pa3gcu]

On Monday 03 February 2003 12:09, Amin wrote:
> Hi Richard,
>
> > Then that means the card was detected and the module was loaded, have
>
> you
>
> > done what it says.????
>
> I have made sure that the hardware works.  In fact, I dual-boot Windows 98
> on the same machine and Windows never has any problems with the card,
> including now.
>
> > You may need to use dhcpcd with options to obtain a IP# from your isp.
> > IE, hostname ??.
>
> Do you mean that I have to set up a DHCP server on my machine and
> configure it ... ?  I sure hope there's an easier way than that ... .

No, dhcpcd is the "client" that contacts a server, the server being your 
ISP's machine. So no you dont need to setup a server.
I was under the impression that you use dhcp top obtain a IP#.

>
> I'm beginning to think I've mixed up different kernel module dependencies.
> The short story is I need help sorting out the modules for use with my two
> kernels: 2.4.18-14 and 2.4.18-14custom.  The long story is: when I
> originally installed RH8.0 and found it didn't already support my NIC, I
> recompiled the kernel with

Dependancies is a big word when it comes to modules, most dependacy problems 
arise because of misconfiguration in /etc/modules.conf and not when compiling 
a new kernel, or tho' that can sometimes be the case.

>
> make xconfig; make dep; make modules; make modules_install; make bzImage
>
> and tried to boot the new kernel.  Eventually I got it to boot, but it
> failed to detect/insert a lot of modules, which seems strange in
> retrospect because I think I actually specified only one loadable module;
> all the others were built-in.  I recompiled again, with the same results.
> A lot of error messages courtesy of depmod as it tries to find module
> dependencies --- things like input.o, soundcore.o, etc.  I've recompiled
> twice after that, with a slightly different command order:


AFAIK, all recent distribution kernel verstions will support most all 
ethernet cards, unless of course your card is the newest of the newest.
So this means you should be able to use the kernel which was installed when 
you installed Linux, be it what ever distro...
What you must make sure is that "modprobe" knows which driver to use, this 
can be done via /etc/modules.conf

alias eth0 8139too # a Realtech 8139A/B or C type chip.

To be honest i have forgotten what type of card you have and all your other 
details, i cleaned out my mailbox this morning and i seem to have deleted 
mails replyed too as well.

>
> make xconfig; make dep; make bzImage; make modules; make modules_install

Use;
make dep clean bzImage modules modules_install

>
> But still I get the same module dependency problems during boot.  Help!

It would be better to show us the error messages, then we can advise more 
precisly, to say anything now would be pure guess work.


>
> Yawar Amin
>

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Network card and kernel module problems

[whitnl73]

On Mon, 3 Feb 2003, Amin wrote:

> I'm beginning to think I've mixed up different kernel module dependencies.
> The short story is I need help sorting out the modules for use with my two
> kernels: 2.4.18-14 and 2.4.18-14custom.  The long story is: when I
> originally installed RH8.0 and found it didn't already support my NIC, I
> recompiled the kernel with
>
> make xconfig; make dep; make modules; make modules_install; make bzImage
>
> and tried to boot the new kernel.  Eventually I got it to boot, but it
> failed to detect/insert a lot of modules, which seems strange in
> retrospect because I think I actually specified only one loadable module;
> all the others were built-in.  I recompiled again, with the same results.

If you didn't change EXTRAVERSION in the Makefile, you will have the
leftover modules from the modular kernel in /lib/modules/`uname -r`
but they will not be able to load with the kernel that has them builtin.
I'd use a unique EXTRAVERSION for each new custom configuration.
When you get it right you can remove all the false starts.

> A lot of error messages courtesy of depmod as it tries to find module
> dependencies --- things like input.o, soundcore.o, etc.  I've recompiled
> twice after that, with a slightly different command order:
>
> make xconfig; make dep; make bzImage; make modules; make modules_install
>
> But still I get the same module dependency problems during boot.  Help!
>
> Yawar Amin
>
Lawson
--
---oops---




________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Network card and kernel module problems

[Ray Olszewski]

At 09:56 PM 2/2/03 +0600, Amin wrote:
>Hi all,
>
>I use a Surecom EP-320X-S 100/10M Ethernet PCI adapter; I believe it's
>Myson MTD3xx compatible --- at least, I've used it before with Myson's
>fealnx.o module in Red Hat Linux 7.3.  The problem is I upgraded to RH8.0
>and find that the kernel does not already support the card.  I tried
>recompiling with built-in support (for the Myson module).  kudzu detected
>the card at startup and configured it.  I've set it up it using Red Hat's
>``neat'' tool (it uses DHCP), but it says it can't determine IP
>information, and to check the cables.


Richard has given you good advice in his replies, but in looking at the 
exchange, I think you may need a more plainly described troubleshooting 
strategy. So I suggest this procedure:

1. After boot/init has completed, use "lsmod" to see which modules have 
been loaded. Look for fealnx on the list.

2. If fealnx is not on the list, then look at the dmesg buffer (with the 
"dmesg" comand) or your log files (probably in /var/log) to see if the 
module tried to load and failed.

3. Use "ifconfig -a" to see if your eth0 interface was created. If it was, 
then either the kernel has builtin support for your NIC card or a suitable 
module was loaded. If it was not, then you have some kernel- or 
module-level problem that the prior steps failed to unearth.

4. How does your host get its IP address? (I'm not sure how RH specifies 
this -- look in the init file that starts networking, or see if your system 
uses /etc/network/interfaces to control this.) If it is by DHCP, then check 
if you omitted some kernel feature needed by DHCP when you did your custom 
compile. This is easy to do because some of the kernel capabilities neede 
for DHCP are not well described in the kernel-make Help file.

Likely candidates for this mistake are in this part of the config file:

         # Networking options
         #
         CONFIG_PACKET=y
                 # CONFIG_PACKET_MMAP is not set
                 # CONFIG_NETLINK_DEV is not set
                 # CONFIG_NETFILTER is not set
         CONFIG_FILTER=y
         CONFIG_UNIX=y
         CONFIG_INET=y

5. If your interface gets its address by some means other than DHCP, you'll 
need to tell us what it is.

Finally -- in the future, please quote commands and their error-message 
replies completely and exactly. Do not summarize of paraphrase ... it 
requires us to guess too much about what is going on.
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Network card and kernel module problems

[Amin]

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

Hi people,

First --- sorry about not including specific error messages earlier.  The
attached file is a (snipped) list of bootup messages, and contains the
messages I'm concerned with.

I've decided to reinstall, perhaps try a different distro, and see if that
will do the trick.  And thanks
to Lawson for pointing out the EXTRAVERSION point.  Just want to make sure
about something --- you're talking about
/usr/src/linux-2.4.18-14/Makefile, right?

Yawar Amin

P.S.  Is it a good sign or a bad sign that I've got my kernel version
memorized?


[-- Attachment #2: startup_errors.txt --]
[-- Type: text/plain, Size: 3107 bytes --]

...

Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol try_inc_mod_count_Re6105b23 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol jiffies_R0da02d67 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol del_timer_Rfc62f16d 
Feb  4 15:41:26 localhost netfs: Mounting other filesystems:  succeeded
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol sprintf_R1d26aa98 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol printk_R1b7d4074 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: insmod /lib/modules/2.4.18-14/kernel/drivers/input/input.o failed 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: insmod keybdev failed 
Feb  4 15:40:45 localhost rc.sysinit: Initializing USB keyboard:  failed 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o:  
Feb  4 15:40:45 localhost modprobe: unresolved symbol mod_timer_R1f13d309 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol unregister_chrdev_Rc192d491 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol register_chrdev_R44b36f42 
Feb  4 15:41:27 localhost autofs: automount startup succeeded
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol request_module_R27e4dc04 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol try_inc_mod_count_Re6105b23 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol jiffies_R0da02d67 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol del_timer_Rfc62f16d 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol sprintf_R1d26aa98 
Feb  4 15:41:27 localhost sshd: Starting sshd:
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol printk_R1b7d4074 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: insmod /lib/modules/2.4.18-14/kernel/drivers/input/input.o failed 
Feb  4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: insmod mousedev failed 

... [snip]

Feb  4 15:41:15 localhost network: Setting network parameters:  succeeded 
Feb  4 15:41:16 localhost network: Bringing up loopback interface:  succeeded 
Feb  4 15:41:17 localhost ifup:  
Feb  4 15:41:17 localhost ifup: Determining IP information for eth0... 
Feb  4 15:41:22 localhost ifup:  failed; no link present.  Check cable? 
Feb  4 15:41:22 localhost network: Bringing up interface eth0:  failed 

...

Re: Network card and kernel module problems

[Ray Olszewski]

At 10:47 AM 2/5/03 +0600, Amin wrote:
>Hi people,
>
>First --- sorry about not including specific error messages earlier.  The
>attached file is a (snipped) list of bootup messages, and contains the
>messages I'm concerned with.

All the modprobe messages your include in the edited log relate to the 
"input.o" module. To be honest, I'd never even realized that module existed 
in Linux. After reading its documentation (in 
/usr/src/linux/Documentation/input/), I think it is just a prototype module 
provided as an example for people who want to learn how to write modules. 
Its described purpose seems unrelated to typical hardware configurations in 
any case. Perhaps you can tell us why you are loading this module (or if it 
is loaded as a dependency, what other module is causing modprobe to load it)?

The other messages you quote are from ifup, and they say that it cannot 
configure eth0. These messages viewed alone are not terribly informative, 
and I would suggest again that you follow the troubleshooting procedure I 
outlined in my prior message ... boot/init logs are neither the only or, 
often, the best way to investigate problems. These message taken alone do 
not tell us if (a) the kernel lacks support for DHCP address requests, (b) 
the DHCP request works but you get no response from whatever eth0 is 
connected to, or even, just conceivably, (c) the eth0 interface is not created.

>I've decided to reinstall, perhaps try a different distro, and see if that
>will do the trick.  And thanks
>to Lawson for pointing out the EXTRAVERSION point.  Just want to make sure
>about something --- you're talking about
>/usr/src/linux-2.4.18-14/Makefile, right?

The EXTRAVERSION shell variable is in that file, yes. For the kernel you 
are describing, the "-14" at the end is the EXTRAVERSION part of the name.


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Network card and kernel module problems

[whitnl73]

On Wed, 5 Feb 2003, Amin wrote:

> Hi people,
>
> First --- sorry about not including specific error messages earlier.  The
> attached file is a (snipped) list of bootup messages, and contains the
> messages I'm concerned with.
>
> I've decided to reinstall, perhaps try a different distro, and see if that
> will do the trick.  And thanks
> to Lawson for pointing out the EXTRAVERSION point.  Just want to make sure
> about something --- you're talking about
> /usr/src/linux-2.4.18-14/Makefile, right?

Well, the README says not to put it in /usr/src/linux, that belongs to
glibc for its <linux/xxxx.h>, so I have mine in /oof/linux-2.4.13, but
yes, the top level Makefile for the kernel source tree you are working
with.
>
> Yawar Amin
>
> P.S.  Is it a good sign or a bad sign that I've got my kernel version
> memorized?
>
>

--
---oops---



________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Network card and kernel module problems

[Whitnl73@juno.com]

Originally to: All

On Wed, 5 Feb 2003, Amin wrote:

> Hi people,
>
> First --- sorry about not including specific error messages earlier.  The
> attached file is a (snipped) list of bootup messages, and contains the
> messages I'm concerned with.
>
> I've decided to reinstall, perhaps try a different distro, and see if that
> will do the trick.  And thanks
> to Lawson for pointing out the EXTRAVERSION point.  Just want to make sure
> about something --- you're talking about
> /usr/src/linux-2.4.18-14/Makefile, right?

Well, the README says not to put it in /usr/src/linux, that belongs to
glibc for its <linux/xxxx.h>, so I have mine in /oof/linux-2.4.13, but
yes, the top level Makefile for the kernel source tree you are working
with.
>
> Yawar Amin
>
> P.S.  Is it a good sign or a bad sign that I've got my kernel version
> memorized?
>
>

--
---oops---



________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
-


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs