LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 04-23-2006, 01:43 PM   #1
sirius57
Member
 
Registered: Jun 2004
Distribution: Fedora core 1, puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora
Posts: 462

Rep: Reputation: 30
How to start networking and web browsing?


I did a fresh install of Fedora core 1, however I want to start networking using samba server and browse the internet. I disabled the firewall to make sure that was not the problem. To browse the network, I tried to set up an ethernet connection, however, a dialog said I needed to install the Lisa Daemon lan browser. I did a Fedora install on an older box, so I am not sure what I missed this time. The network configuration utility has no devices listed and in server setting services, network is checked and smb is unchecked. Do I need to add devices?
 
Old 04-24-2006, 07:02 AM   #2
Simon Bridge
Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 197Reputation: 197
FC1 is legacy.
You should install at least FC4.
(Running fedora pretty much requires you upgrade every 12-16 months.)
But for an older box, you may prefer a lighter distro.

Browser:
You browse the internet using mozilla - right there on the panel. If it isn't, then it is on your disk, you need to install it. That is the browser.

Ethernet Connection:
There are two main utilities in fedora - the Network Device Control (NDC) and the Internet Configuration Wizard (ICW). NDC is for existing services (like an onboard ethernet card) - the device will be called eth0, highlight it and click "activate" to start it up.

However, you will probably need to configure it for your network. NDC is good for that too. Just click "configure" and select your card. Walk through the tabs and set appropriate things for your network.

ICW is for adding new network devices - like when you add a pci ethernet nic or a modem. Though these things are often autodetected when you boot.

Both these are in main menue > system tools

So - first check for "eth0" in NDC. If it isn't there, you need to add the device in ICW. If no device is detected - make sure it is turned on in bios (for onboard nic) or properly seated (for pci nic). (Check lspci to see if the nic is detected.)

SAMBA:
main menue > desktop > system settings > server settings > SAMBA
/etc/init.d/samba start
Though I take it the machine is to be a client to a windows server? Or is it supposed to be a server?

Beyond that, I cannot really say. You havn't told us enough about your system. You havn't said how you expected to connect to the internet. Nor have you told us anything about your network.
 
Old 04-24-2006, 08:04 PM   #3
sirius57
Member
 
Registered: Jun 2004
Distribution: Fedora core 1, puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora
Posts: 462

Original Poster
Rep: Reputation: 30
I found the utilities and I am posting my shell:

[jeff@localhost jeff]$ /sbin/ipconfig
bash: /sbin/ipconfig: No such file or directory
[jeff@localhost jeff]$ /sbin/ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1513 errors:0 dropped:0 overruns:0 frame:0
TX packets:1513 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1154260 (1.1 Mb) TX bytes:1154260 (1.1 Mb)

[jeff@localhost jeff]$ /sbin/route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 * 255.255.0.0 U 0 0 0 lo
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
[jeff@localhost jeff]$ ping
Usage: ping [-LRUbdfnqrvVaA] [-c count] [-i interval] [-w deadline]
[-p pattern] [-s packetsize] [-t ttl] [-I interface or address]
[-M mtu discovery hint] [-S sndbuf]
[ -T timestamp option ] [ -Q tos ] [hop1 ...] destination
[jeff@localhost jeff]$ ping 192.168.1.1
connect: Network is unreachable

Also, this is a new box. The board came with a cd for audio and network drivers, since they are integrated on the board. I have an Asus A8V-E SE motherboard. I am sharing an internet connection through a linksys router. The driver docs list 3 types on install, kernel, load the module or a temporary load after compiling the driver. So far I copied the driver directory from the cd to my home directory. There is a file called install.sh and sk98lin.tar.bz2. They are assuming I know how to extract the package, then modprobe sk98lin to start the ethernet. This sounds elementry, but do I install by clicking on the install.sh?
 
Old 04-24-2006, 08:57 PM   #4
InEeDhElPlInUx
Member
 
Registered: Sep 2003
Posts: 107

Rep: Reputation: 15
try
./install.sh

Follow prompts and you should be alright...post back if not.
 
Old 04-25-2006, 02:02 AM   #5
Simon Bridge
Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 197Reputation: 197
Quote:
The board came with a cd for audio and network drivers, since they are integrated on the board.
You probably don't need the CDs - fedora has good support for what you want. Unless your hardware is very weird, you will be fine.
Quote:
I am sharing an internet connection through a linksys router.
Ahah! In that case - configure eth0 to use DHCP, plug the cat5 cable into any ethernet port on the router, then activate the connection. Did you find the Network Device Control dialog?
Quote:
The driver docs list 3 types on install, kernel, load the module or a temporary load after compiling the driver. So far I copied the driver directory from the cd to my home directory.
nonononono! Stop that - it is probably done already.

right-click on the desktop and select "open terminal".
at the prompt enter: lspci | grep Ethernet (post the command and result here)
take note of what sort of card it says you have then
enter: lsmod
look through the list for an entry that seems to correspond to your card.

This is what happens for me:
Code:
$ /sbin/lspci | grep Ethernet
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
$ /sbin/lsmod
[snip]
iptable_filter          3137  1
ip_tables              12313  2 iptable_mangle,iptable_filter
x_tables               12741  8 xt_limit,xt_tcpudp,ipt_LOG,ipt_MASQUERADE,ipt_TOS,ipt_REJECT,xt_state,ip_tables
ipv6                  249089  10
8139cp                 22465  0
usb_storage            68513  0
scsi_mod              132301  2 sd_mod,usb_storage
ohci_hcd               21725  0
ehci_hcd               31949  0
[snip]
You see my card is of type 8139... something, so the module must have those numbers in it (in green).

Of course - if eth0 shows up in Network Device Control, then the driver must be loaded already - it remains to configure it for dhcp and activate it.

If it is not there, you will need to install the driver from the CD.
You want the module install.
you use the "cd" command in the terminal to take you to the same directory as the install.sh file (this is an executable script file similar to a DOS batch (*.bat) file) and enter "./install.sh" like the man said.

note: enter ls to see the content of a directory. the blue names are subdirectories. enter: cd <directory-name> to change to that directory.

Last edited by Simon Bridge; 04-25-2006 at 02:09 AM.
 
Old 04-25-2006, 09:51 PM   #6
sirius57
Member
 
Registered: Jun 2004
Distribution: Fedora core 1, puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora
Posts: 462

Original Poster
Rep: Reputation: 30
Ok, I have alot to post from my shell. I have posted the results and the readme file to explain what I did and to help me where I went wrong. Here are the nic results:

[jeff@localhost jeff]$ lsmod
bash: lsmod: command not found
[jeff@localhost jeff]$ ismod
bash: ismod: command not found
[jeff@localhost jeff]$ Lsmod
bash: Lsmod: command not found
[jeff@localhost jeff]$ /sbin/lspci | grep Ethernet
05:00.0 Ethernet controller: Galileo Technology Ltd.: Unknown device 4362 (rev 1
9)
[jeff@localhost jeff]$ /sbin/lspci
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0238
00:00.1 Host bridge: VIA Technologies, Inc.: Unknown device 1238
00:00.2 Host bridge: VIA Technologies, Inc.: Unknown device 2238
00:00.3 Host bridge: VIA Technologies, Inc.: Unknown device 3238
00:00.4 Host bridge: VIA Technologies, Inc.: Unknown device 4238
00:00.5 PIC: VIA Technologies, Inc.: Unknown device 5238
00:00.7 Host bridge: VIA Technologies, Inc.: Unknown device 7238
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device b188
00:02.0 PCI bridge: VIA Technologies, Inc.: Unknown device a238
00:03.0 PCI bridge: VIA Technologies, Inc.: Unknown device c238
00:03.1 PCI bridge: VIA Technologies, Inc.: Unknown device d238
00:03.2 PCI bridge: VIA Technologies, Inc.: Unknown device e238
00:03.3 PCI bridge: VIA Technologies, Inc.: Unknown device f238
00:0f.0 RAID bus controller: VIA Technologies, Inc.: Unknown device 3149 (rev 80 )
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/ C/VT8235 PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. USB (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3227
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 A udio Controller (rev 60)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
02:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0161 (rev a1)
05:00.0 Ethernet controller: Galileo Technology Ltd.: Unknown device 4362 (rev 1 9)

I did run the script as mentioned in this thread. I was unable to modprobe any modules. The following is the readme file from the cd. At the end, I listed how far in the readme I was able to go. I tried to keep it as short as I could.

Installation Instructions for sk98lin Driver

This file contains
1 Overview
2 Required Files and Tools
3 Prerequisites
4 Preparing the Driver Installation Package
5 Driver Installation
5.1 User Installation Mode
5.2 Expert Installation Mode
5.3 Patch Generation Mode
6 Patch Generation and Recompilation of the Kernel
6.1 Downloading and Unpacking the Linux Kernel
6.2 Generating the Driver Patch
6.3 Applying the Driver Patch
6.4 Configuring the Linux Kernel
6.5 Compiling the Linux Kernel
6.6 Installing the Compiled Linux Kernel
7 Manual Module Loading
8 Unloading the Module
9 Driver Parameters
10 Troubleshooting
================================================================================


1 Overview
===========

This document describes the installation of the sk98lin driver
on your Linux system. It describes how the installation script works
and how it can be used to either install the sk98lin driver or to
create a Linux kernel patch.

Applying the Linux kernel patch requires an installed Linux kernel
which can be compiled and which is used along with the applied
sk98lin driver. Therefore, unpacking, patching, configuring
and compiling a Linux kernel is also explained in this document.

This document does not describe the sk98lin driver and its
parameters. For more information refer to 'sk98lin.txt' or
the sk98lin.4 man page.
***


2 Required Files and Tools
===========================

To install the sk98lin driver the following files
and tools on your Linux system are required:

- Linux kernel source available in directory /usr/src/linux

- Compiler tools (e.g. gcc)
***


3 Prerequisites
================

The prerequisites for compilation, loading and patch creation of the
sk98lin driver are:

- Any device using the sk98lin kernel module needs to be closed.

- The old sk98lin kernel module needs to be unloaded.
Per default the installation script will do this automatically
(if "user mode" installation is selected).
If you want to shutdown and unload the old sk98lin kernel module
manually, run the script in "expert installation" mode.

- Your system has to be equipped with a supported network card.
Without a card the full driver functionality cannot be checked.

- The kernel source and kernel version have to be consistent.
For instance, it might be, that you run kernel version 2.4.20, but
the header files the kernel module will be compiled with refer to
kernel version 2.4.21. If you don't have the same kernel version,
install the sources and compile a new kernel. It's not possible to
mix different kernel versions!
***


4 Preparing the Driver Installation Package
============================================

Before the sk98lin driver installation script can be invoked, the
installation package needs to be unpacked:

1. Login as 'root'.
2. Unpack the driver installation package using the command

# tar xfvj install-???.tar.bz2
or
# bunzip2 -c install-???.tar.bz2 | tar xfv -
***

5 Driver Installation
======================

1. After the driver installation package is unpacked, type the following
commands to start the sk98lin driver build process:

# cd DriverInstall
# ./install.sh

2. Select the driver installation mode (see following subchapters).
3. Wait for the driver build process to finish.
Depending on the installation mode you selected, the driver is either
compiled and installed or a kernel patch is generated.
***

5.1 User Installation Mode
---------------------------

Selecting this installation mode the driver sources shipped
with the install package are compiled and the resulting driver
module object file is installed to a suitable location (usually somewhere
below directory /lib/modules/...).

No source files of the driver are installed into a kernel directory.
Only the driver module object file and the man page of the driver are
installed onto your system permanently.

The term "user installation" reflects the fact that the build
process runs automatically without any user interaction. In case
of installation problems, the driver installation script autonomously
tries to solve the problem (if this is possible).

After compilation has finished, the initial system state and
configuration is recovered and all (possibly) backed-up system
files are restored from the initial configuration.
***

5.2 Expert Installation Mode
-----------------------------

Selecting this installation mode the driver sources are also compiled
and the resulting driver module object file is installed to a suitable
location (Similiar to the "user installation" mode).

No source files of the driver are installed into a kernel directory.
Only the driver module object file and the man page of the driver are
installed onto your system permanently.

In contrast to the "user installation" it is the user's responsiblity
to provide a consistent Linux system with correctly installed Linux
kernel sources. In case of problems at installation time, no attempts
to solve the problem are performed.

In case of problems or warnings, the installation stops and an error
message is displayed. Then it is up to the user to correct the
error and to restart the installation.
***

5.3 Patch Generation Mode
--------------------------

Selecting this installation mode, a driver patch is created which can
be applied to your Linux kernel (instead of compiling and installing
the driver on your machine).

Usually, a patch is applied when a recompilation of the Linux
kernel is intended and the latest driver sources need to be
installed permanently in the appropriate driver directory of
the Linux kernel.

NOTE: You still have to compile your patched Linux kernel in
order to effectively use the latest driver sources shipped
with this installation package!
***


6 Patch Generation and Recompilation of the Kernel
===================================================

If a new patch has been created using the sk98lin driver installation
script,
- it needs to be applied against the Linux kernel sources
and
- the Linux kernel has to be recompiled in order to use the
sk98lin driver.
***

6.1 Downloading and Unpacking the Linux Kernel
-----------------------------------------------

Before the sk98lin driver installation script is used to generate
a driver patch, a Linux kernel needs to be installed. If you already have
installed a Linux kernel in the directory /usr/src, you can skip this
paragraph and immediately continue with the paragraph describing
how to apply the patch against the Linux kernel.

To patch the Linux Kernel, proceed as follows:

1. Login as 'root'.

2. Download the original Linux source code named linux-a.b.c.tar.bz
from ftp.kernel.org into the directory /usr/src

3. Go to the directory /usr/src and remove all symbolic links to old
Linux sources using the commands:

# cd /usr/src
# rm linux

4. Unpack the original Linux source code using the command:

# tar xvjf linux-a.b.c.tar.bz

After the sources have been installed, they can be found in a
directory named /usr/src/linux-a.b.c or /usr/src/linux.

5. If the symbolic link to the target kernel source directory
(/usr/src/linux) does not exist, create it manually with the
following commands:

# cd /usr/src
# ln -s linux.a.b.c linux
***

6.2 Generating the Driver Patch
--------------------------------

1. Run the the sk98lin driver installation script.
2. Choose "gererate patch".
3. Follow the instructions of the install script.
***

6.3 Applying the Driver Patch
------------------------------

To apply the generated Patch into the kernel use the following
commands:

# cd /usr/src/linux
# cat /patch-location/sk98lin__vX.XX_a_b_c_patch | patch -p1
***

6.4 Configuring the Linux Kernel
---------------------------------

1. Go to the directory /usr/src/linux:

# cd /usr/src/linux

2. Depending on your current environment mode (console or graphical),
you have to invoke different Kernel configuration commands:

- In the console mode, execute the command:

# make menuconfig

- In the graphical mode, execute the command:

# make xconfig

- In the graphical mode with kernel 2.6, execute the command:

# make gconfig

This builds a few programs and displays the kernel
configuration menu. In this menu you can modify several options
of the kernel configuration.

3. Select the options you want to compile into the new kernel.

- For kernel 2.4.x family:
a. Select the menu "Network Device Support".
b. Select "Ethernet (1000 Mbit)".

- For kernel 2.6.x family:
a. Select the menu "device drivers"
b. Select the menu "Network Device Support".
c. Select "Ethernet (1000 Mbit)".

4. Select how to use the driver in the Linux kernel.

- To compile the driver as a module, mark
"Marvell Yukon Chipset/SysKonnect SK-98xx Support" with (M).

- To integrate the driver permanently into the kernel, mark
"Marvell Yukon Chipset/SysKonnect SK-98xx Support" with (*).

5. Select if you want to use Rx polling (NAPI).

- To enable Rx polling of the driver, mark
"Use Rx polling (NAPI)" with (*).

- To disable Rx polling of the driver, do not mark
"Use Rx polling (NAPI)".

6. Select "Exit".

7. Select the menu "Loadable module support".

8. Select "Enable loadable module support".

9. Select "Kernel module loader".

10. Configure other options depending on your needs (e.g. SCSI).

11. To quit the configuration, select "Exit".

12. When the message "Do you wish to save your new kernel configuration"
is displayed, select "Yes".
***

6.5 Compiling the Linux Kernel
-------------------------------

After the Linux configuration has been finished, it can be compiled.

1. Create all dependencies (unnecessary for kernel 2.6.x):

# make dep

2. Build the Linux kernel binary:

# make clean bzImage.

3. Build all modules and install them below /lib/modules:

# make modules
# make modules_install
***

6.6 Installing the Compiled Linux Kernel
-----------------------------------------

When the compilation of the Linux kernel has been finished it needs
to be installed to the boot directory. In addition to this, the boot
loader (LILO, GRUB etc.) needs to be notified about the new Linux kernel.

1. Install the new kernel by copying it into your boot directory
by executing the commands (e.g. on Intel/x86 machines):

# cp arch/i386/boot/bzImage /boot/vmlinuz-new
# cp System.map /boot/System.map-new.

2. Edit the boot loader configuration file to boot the new kernel.
For details refer to man page and documentation of your boot loader
(LILO, GRUB).

3. Reboot your system with the new kernel.
***


7 Manual Module Loading
========================

After booting the Linux kernel and compiling the driver as a loadable
kernel module (LKM), the driver needs to be loaded.

1. Enter "modprobe sk98lin".

2. If any Marvell Yukon(TM) based adapter is installed in your computer
and you have a mounted /proc file system, execute the command:

# ls /proc/net/sk98lin/

This should produce an output line of the following format:
eth0 eth1 ...
which indicates that your adapter(s) has/have been found and initialized.

NOTE: For further information (e.g. the driver parameters) refer to
the sk98lin.txt file.
***


8 Unloading the Module
=======================

Unloading of the sk98lin driver is only possible if it has been
compiled as loadable kernel module. Before the driver module can be unloaded,
all interfaces of the driver module need to be stopped using the following
sequence of commands:

1. Execute the command "ifconfig YOUR_DEVICE down":

# ifconfig eth0 down
# ifconfig eth1 down
# ifconfig ... down

2. Execute the command "rmmod sk98lin".
***


9 Driver Parameters
====================

When loading the driver as a kernel module, additional parameters
can be passed to the driver for configuration.

Those parameters can be passed in two ways: You can either

- state them on the modprobe command line
or
- set them in the file /etc/modules.conf (old name:
/etc/conf.modules), in order to force the kernel module loader
to pass them to the driver at load-time.

NOTE: For further information about the driver parameters and their
possible values refer to the sk98lin.txt file.
***


10 Troubleshooting
===================

If any problems occur during the installation process, check the
following list:


Problem: The SK-98xx adapter cannot be found by the driver.
Solution: In /proc/pci search for the following entry:
'Ethernet controller: SysKonnect SK-98xx ...'
If this entry exists, the SK-98xx or SK-98xx V2.0 adapter has
been found by the system and should be operational.
If this entry does not exist or if the file '/proc/pci' is not
found, there may be a hardware problem or the PCI support may
not be enabled in your kernel.
The adapter can be checked using the diagnostics program which
is available on the SysKonnect web site:
www.syskonnect.com


Problem: Programs such as 'ifconfig' or 'route' cannot be found or the
error message 'Operation not permitted' is displayed.
Reason: You are not logged in as user 'root'.
Solution: Logout and login as 'root' or change to 'root' via 'su'.


Problem: The driver can be started, but if an ip address is assigned
to an adapter no link up indication appears although it is
connected to the network. It is also not possible to receive
or transmit any packets; e.g. 'ping' does not work.
Reason: The adapter does not receive any interrupts from the Linux
system. This can happen when using the APIC (Advanced
Programmable Interrupt Controller) of an SMP compiled kernel
on a UP envrionment.
Solution: Use the Linux kernel parameters 'noapic' or 'nolapic' when
booting your kernel. This can be done by adding those kernel
parameters to the boot manager kernel selection menu (either
/boot/grub/menu.lst (GRUB) or /etc/lilo.conf (LILO)).
When you build a kernel, deselect option CONFIG_X86_LOCAL_APIC.


Problem: The driver can be started, the adapter is connected to the
network and a link up indication is displayed, but you cannot
receive or transmit any packets; e.g. 'ping' does not work.
Reason: There is an incorrect route in your routing table or the
remote host is unreachable.
Solution: Check the routing table with the command 'route' and read the
manual help pages dealing with routes (enter 'man route').
Check the connection to the remote host system.


Problem: At driver start, the following error message is displayed:
"eth0: -- ERROR --
Class: internal Software error
Nr: 0xcc
Msg: SkGeInitPort() cannot init running ports"
Reason: You are using a driver compiled for single processor machines
on a multiprocessor machine with SMP (Symmetric MultiProcessor)
kernel.
Solution: Configure your kernel appropriately and recompile the kernel.
***


***End of Readme File***

I got as far as 6.5, but paragraph 3 failed in building the modules and installing them. I have the kernel 2.4 and I chose patch generation mode in 5.3. I also configured the linux kernel in 6.4. I do not want to build a new kernel, just modprobe the ethernet patch each time the box is booted up.
 
Old 04-26-2006, 01:23 AM   #7
Simon Bridge
Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 197Reputation: 197
Quote:
Originally Posted by sirius57
Ok, I have alot to post from my shell. I have posted the results and the readme file to explain what I did and to help me where I went wrong.
good, information wants to be free
Quote:
Here are the nic results:
Code:
[jeff@localhost jeff]$ lsmod
bash: lsmod: command not found
try: /sbin/lsmod
(in general - if you don't find a command, try locate <command> or apropos <command> as well as man <command> or info <command>. This will give you clues.
Quote:
[jeff@localhost jeff]$ /sbin/lspci | grep Ethernet
05:00.0 Ethernet controller: Galileo Technology Ltd.: Unknown device 4362 (rev 19)
Unknown huh - unusual and not good. "unknown" usually means there is no driver for the device ... but you have a sk98lin driver source tarball which is supposed to run this?
Quote:
I did run the script as mentioned in this thread. I was unable to modprobe any modules. The following is the readme file from the cd. At the end, I listed how far I got
[snip]
Quote:
I got as far as 6.5, but paragraph 3 failed in building the modules and installing them. I have the kernel 2.4 and I chose patch generation mode in 5.3. I also configured the linux kernel in 6.4. I do not want to build a new kernel, just modprobe the ethernet patch each time the box is booted up.
... OK this won't work. The patch is a diff file which must be applied to a kernel, then the kernel recompiled. Usually this has to be a vanilla kernel rather than a distro kernel, and the patch has to be for your exact kernel version given in uname -r.

What you want to do is google for sk98lin drivers pre-packaged for your kernel.
(Or disable the onboard ethernet and use a pci ethernet nic instead...)

I'll go see what I can find, and get back to you.
 
Old 04-26-2006, 01:26 AM   #8
Simon Bridge
Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 197Reputation: 197
Ahah!
http://www.redhat.com/archives/rhl-l.../msg02148.html

You ignore the provided drivers: Fedora has the driver already. The trouble is that kudzu dosn't realise this. Here's what you need to do:
Code:
echo "alias eth0 sk98lin" >> /etc/modules.conf
then reboot.
 
Old 04-26-2006, 09:05 PM   #9
sirius57
Member
 
Registered: Jun 2004
Distribution: Fedora core 1, puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora
Posts: 462

Original Poster
Rep: Reputation: 30
I made progress. After typing in the line as root and rebooting, the lights on the nic and the port on the router lit up. In the network configuration panel, I entered the sk98 ethernet adapter. However, it will not allow me to activate the card. Message: 'sk98lin device does not seem to be present, delaying initialization.' The lights are on, so I am assuming the driver is present. Is there something else that needs to be adjusted? The box was rebooted after using the network configuration panel.

Last edited by sirius57; 04-26-2006 at 09:08 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Text Web Browsing? Mulsiphix Linux - Newbie 7 01-18-2006 01:33 PM
Wireless Networking (Browsing) Problems Nolewatcher Fedora 2 07-09-2005 09:23 PM
Web-browsing via ssh jamesinhamburg Linux - General 3 04-30-2005 09:12 AM
XMMS and web browsing-- but not together hindenbergbaby Linux - Software 6 12-27-2003 10:27 AM
Web browsing... ade Linux - General 3 01-11-2003 07:58 AM


All times are GMT -5. The time now is 11:45 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration