Hi all,

I was wondering if anyone can help me with configuring my NIC. I'm trying to configure it to use Blueyonder Broadband (http://www.blueyonder.co.uk), which assigns IP address' dynamically, however I've been unable to configure the network card yet.

Distribution Slackware 9.1
Kernel 2.4.24

I modified /etc/rc.d/rc.inet1 as shown below

-------------/etc/rc.d/rc.inet1-------------
# Edit these values to set up your first Ethernet card (eth0):
#IPADDR="127.0.0.1" # REPLACE with YOUR IP address!
#NETMASK="255.255.255.0" # REPLACE with YOUR netmask!
# Or, uncomment the following lines to set up eth0 using DHCP:
USE_DHCP=yes
# If your provider requires a DHCP hostname, uncomment and edit below:
#DHCP_HOSTNAME="CCHOSTNUM-A"

# Edit the next line to point to your gateway:
GATEWAY="82.38.192.1" # REPLACE with YOUR gateway!

# You shouldn't need to edit anything below here.
---------------End--------------------------

I then try running rc.inet1 manually and get the following output...

-------------------rc.inet1-----------------
[root@fisher:/etc/rc.d]# rc.inet1
SIOCADDRT: File exists
Attempting to configure eth0 by contacting a DHCP server...
SIOCADDRT: Network is unreachable
---------------End--------------------------

Which to me indicates that eth0 isn't configured properly, so I tried configuring it...

-------------------ifconfig------------------
[root@fisher:/etc/rc.d]# ifconfig eth0
eth0: error fetching interface information: Device not found

---------------End--------------------------

So I think that the NIC isn't being detected, but I don't know why.

Detailed below is some output...

[root@fisher:/home/neil]# lspci -v
----------relevant section------------------
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7120
Flags: bus master, medium devsel, latency 32, IRQ 23
I/O ports at d800 [size=256]
Memory at dffefe00 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>
----------relevant section------------------

This is just a guess, but could it be that my kernel doesn't support the hardware??

Any help would be much appreciated.

Thanks in advance

slack---line

Did you check your distros hardware compatability list or the Linux Hardware Compatibility HOWTO to see if it is supported?

try /sbin/modprobe tulip

Hi peeps,

Thanks for the replies...

fancypiper

I coudn't find anything detailed on the Hardware Compatability that looks anywhere near similar to the ethernet card I have.

keefaz

Nothing found.

This makes me suspect I need to load a module, but I could be wrong (I'll probably end up doing a kernel recompile as I want to get 2.6.* working (probs with ALSA, but thats a who different issue)).

Any more hints/ideas are more than welcome,

slack---line

try "dmesg | grep eth" to see what that says, post that. i assume you are running hotplug?
post lsmod output also

before delving into all of this, did you try netconfig?

cd /usr/src/linux
make menuconfig
go to device drivers > Networking support > enable Dummy net driver support (module)
go to Ethernet (10 or 100Mbit)
> enable EISA, VLB, PCI and on board controllers
>enable VIA Rhine support (module)

I have a on board controller for etho too, here is my lspci output (my card works well) :
00:13.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11)
Subsystem: DFI Inc: Unknown device 100a
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at e400 [size=256]
Memory at e7001000 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: <available only to root>

Hooray, I'm now writing this message under Linux.

My kernel was missing the key support for the NIC. I just included the tulip module and stuck a load of others in as loadable modules (had no idea which was which), but I shall try and suss out which is the correct one (not too hard at all).

Thank you all for your help and suggestions,

slack---line

You could look under the hood or use some bash commands......
What's this bash command stuff?
# Bash shell commands
Command Reference NHF
O'Reilly Directory of Linux Commands
# Handy bash commands I might use or ask a newbie to use:
# Find CPU specifications
cat /proc/cpuinfo
# Find running kernel version
uname -r
# What compiler version do I have installed
gcc -v
gcc --version
# What is the running kernel and compiler installed
cat /proc/version
# Find X server version
X -showconfig
# What pci cards are installed and what irq/port is used
cat /proc/pci
# What kernel modules are loaded
lsmod
# Memory and swap information
cat /proc/meminfo
free
An article: Tips for Optimizing Linux Memory
# How are the hard drives partitioned
fdisk -l
# How much free/used drive space
df -h
# Show disk usage by current directory and all subdirectories
du | less
# What takes up so much space on your box
# Run from the directory in question and the largest chunk shows up last
find $1 -type d | xargs du -sm | sort -g
# What is the distribution
cat /etc/.product
cat /etc/.issue
cat /etc/issue
cat /etc/issue.net
sysinfo
# For finding or locating files
find
locate
which
whereis
# Use dmesg to view the kernel ring buffer (error messages)
dmesg | less
# Watch error messages as they happen (sysklog needed)
as root, tail -f /var/log/messages (shows last 10 lines, use a number in front of f for more lines)
# What processes are running
ps -A
# Find a process by name
ps -ef | grep -i <plain text>
For example, XCDroast
ps -ef xcdroast
# See current environment list, or pipe to file
env | more
env > environmentvariablelist.txt
# Show current userid and assigned groups
id
# See all command aliases for the current user
alias
# See rpms installed on current system
rpmquery --all | less
rpmquery --all > <filename>
rpmquery --all | grep -i <plaintext>
Autospec for tarballs
RPM tools
# What directory am I using
pwd
# Get ls colors in less
ls --color=always | less -R
Look at man <command> or info <command> for the flags I used and for other options you can use for bash commands.

why indicate rpm things, our favorite distro is slackware

#see packages installed in system
ls /var/log/packages | less
ls /var/log/packages > <filename>
ls /var/log/packages | grep -i <plaintext>

# find a program installed by a package
grep -i program /var/log/packages/*

PKG TOOLS

Hehehe,

thanks for the tips fancypiper, I know a fair bit of bash already (I maintaina small server at work for people to sue for genetic analysis, but that was set up when I was learning and I learnt that hard way that RedHat is not a patch on slackware ;-), but there are a few tricks there that I've not come across, thanks.

I never touch RPM's they're evil!!!!!


Thanks to all who have replied,

slack---line

You mean you can't use rpm in slack? I can in Gentoo..

What else do I need to add to my Slack stuff? (Apparently I ignore the name of the forums...)
# Slackware
The Official Guide To Slackware Linux
#see packages installed in system
ls /var/log/packages | less
ls /var/log/packages > <filename>
ls /var/log/packages | grep -i <plaintext>
Slackware Linux Packages
# find a program installed by a package
grep -i <program> /var/log/packages/*

we can do all but slackware pkg is just more efficient