Re: NIC install - found driver, need to compile(?)
Hello,
I just finished going through big problem with modules and NIC so I can
understand your confusion.
You have a 3com NIC (3CSOHO100-TX) so you likely need the 3c59x driver. First, check /lib/modules/'uname-r'/net to see if that module is there.
If it is not you will have to compile it. ('uname-r' is just your kernel version likely 2.2.17)
If you are compiling it make sure that you have the source code on your
machine, you will find this in /usr/src/linux. It may actually be somewhere
else but there should be symlink there. Change to that directory ( # cd
/usr/src/linux ) and make sure you are root.
Rather than doing everything as root it is safer (read better) to change to
superuser (#su), from within an xterm or alternatively Ctrl-Alt F1 through F6
will switch you into a virtual terminal. Your X session likely is running in
virtual terminal 7 ( Ctrl-Alt F7).
When in /usr/src/linux as root type #make xconfig. After a few preliminaries a
fairly simple point and click interface will pop up. This will contain the
config from the last time you compiled your kernel or in your case the stock configuration from your install. Check under Network devices, Ethernet 10 -
100 bit and make sure that Ethernet and 3com cards are checked. If they are not you will have to recompile your kernel to use the NIC. Then select your
card as module and save the new configuration.
From /usr/src/linux #make modules modules_install
This will compile the modules and install the module in /lib/module/'uname-r'net
Next #depmod -a will update the dependency file.
When your kernel finishes some preliminary stuff while booting it looks in /etc/modules for a list of modules to load, the 3c59x module should be listed
in there. You can edit this directly.
Next the kernel will look at /etc/modules.conf to find any options for the
modulesDon't edit this file directly, instead add the lines to
/etc/modules/aliases
and the changes will be incorporated when you run #update-modules, after which
you again need to #depmod -a.
If you are setting up an ethernet interface you need an entry in
/etc/network/interfaces.
This should look like
#cable modem
iface eth0 inet dhcp
#local network - eth1
iface eth1 inet static
address 10.0.0.1
netmask 255.0.0.0
network 10.0.0.0
This way the interface should come up when you boot. If you are already running
just #ifup
Good Luck
Sean
XKEYBOARD in X 3.3.6
Hello all, I was just upgrading a few libraries for cups and xpp when I developed some odd problems. Now, my backspace key functions as delete and the number pad works as numbers whether or not the Number Lock is on. I have a normal 104 key IBM keyboard. I was unable fix this with XF86Setup but when it started up it had a warning that it was unable to read information from the keyboard. It also said this usually happens when the XKEYBOARD extension is not enabled or the x-server does not support it. The xkeyboard extension is installed: #xdpyinfo -ext XKEYBOARD | tail -2 XKEYBOARD version 1.0 opcode: 136, base event: 84, base error: 136 The XF86config file has the following in the keyboard section: Section Keyboard ProtocolStandard XkbRulesxfree86 XkbModelpc104 XkbLayout us EndSection This is puzzling because I didn't change the configuration when this stopped working properly. Any help would be appreciated. Sean
Re: Setting up eth1 interface
Hello all, This is just to thank all those who offered advice. I finally managed to bring up the eth1 interface. I tried all the suggestions, aliases with a single tulip driver, aliases with 2 tulip drivers, compiled the tulip driver into the kernel and passed ether arguments with lilo. Obviously, the last thing I tried, adding a tulip module when tulip was already compiled in the kernel, worked. As a theoretical question, why can't the tulip driver that is compiled into the kernal recognize both cards? From http://www.securityportal.com, I understand there are some security concerns with having a kernel load modules, so shouldn't you be able to support 2+ cards with a monolithic kernel? Anyway, all is working. Thanks again. On to setting up samba. Sean
Setting up eth1 interface
Hello All, I have been trying to set up a small local network with a linux box as a gateway and my wife's win98 laptop. I am running potato with a fresh 2.2.17 kernel from kernel.org. Currently, a D-link DE-530TX is working well with a tulip driver loaded as a module to connect to my cable modem. The second NIC is a linksys LNE-100TX ver. 4.0, which also uses the tulip driver. However, I cannot get the eth1 interface to initialize. #ifconfig eth1 10.0.0.1 netmask 255.0.0.0 up SIOCSIFADDR: No such device eth1: unknown interface: No such device SIOCSIFNETMASK: No such device eth1: unknown interface: No such device In my /etc/network/interfaces file there is no entry for eth1. eth0 is : iface eth0 inet dhcp so I tried adding : iface eth1 inet Now with #ifup eth1, I get the error /etc/network/interfaces: too few parameters for iface line So, I think that I am almost there I just cannot find any information on what options should be on that line. Or am I not really supposed to be editing that file directly? Any help would be appreciated. Thanks in advance. Sean [EMAIL PROTECTED]
Re: Setting up eth1 interface
Thanks for the really quick replies. Bud Rogers wrote: You probably need to add static to that line. And you will need to add at least address and netmask entries for that interface. Man interfaces for details. iface eth1 inet static address 192.168.1.1 netmask 255.255.255.0 I added these lines and the static option ( thanks for the man reference ). However, I still get the same error when I use #ifup eth1. Leen Besselink wrote: Are you sure the module loaded ? sounds like some kind of driver problem. 'lsmod' will tell you more about that, also you could take a look at the output of 'dmesg'. Maybe that will tell you what went wrong. Hope this helps. I am as sure as I can be with my experience. That is, I have full web access and am sending this email over the eth0 card with that module. I did #lsmod Module Size Used by loop7808 0 (unused) tulip 30680 1 sound 57356 0 (unused) soundlow 344 0 [sound] No errors were found when I looked at dmesg. tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED] eth0: Digital DC21041 Tulip rev 33 at 0xc400, 00:80:C8:6C:61:3C, IRQ 5. eth0: 21041 Media table, default media 0800 (Autosense). eth0: 21041 media #0, 10baseT. eth0: 21041 media #4, 10baseT-FD. eth0: 21143 10baseT link beat good. eth0: 21143 10baseT link beat good. However, there were some errors that flew by at boot that are not there. From what I saw they were modprobe errors complaining about my lp module. How can I see the complete log of what flashes by at boot? I looked at the man dmesg, but the -n switch just returned no messages at all. I had some trouble with modules but I thought that had been resolved with a fresh install this morning and the recompiled kernel from fresh sources. ( I have been fighting with this problem on and off for over a month, but I will fix it today if the coffee holds out) By the way, I have a gnome ( with helix gnome ) desktop. Currently, using Mozilla for mail since my local mail also isn't yet working. Is there a way to directly send standard output to the gnome clipboard instead of dmesg dmesg.txt and then cutting from there? Thanks Sean
re: setting up eth1 interface
Still no luck, Leen Besselink wrote: a good idea could be is make a modules alias for each card (I think it goes in /etc/modutils/aliases): alias eth0 de4x5 alias eth1 3c59x or whatever you need. This could also help... (then just do: modprobe -v eth0 modprobe -v eth1 ) Hope this helps, Lennie. - New things are always on the horizon. added some aliases to /etc/modutils/aliases, ran update-modules and the right lines appeared in modules.conf, then depmod -a ###network modules alias eth0 tulip alias eth1 tulip #options tulip io=0x400,0x800 The options line is now commented out since neither card would work with that line. modprobe -v eth1 was silent, no errors or messages in /var/log/messages still when I try to bring up eth1 I get the following message #ifconfig eth1 10.0.0.1 netmask 255.0.0.0 up SIOCSIFADDR: No such device eth1: unknown interface: No such device SIOCSIFNETMASK: No such device eth1: unknown interface: No such device I don't know what else to try, except compiling the tulip driver into the kernel. Would that make a difference? I tried compiling the tulip.c from Linksys but it wouldn't compile. Struggling on, any help appreciated. Sean
