Installed Fedora core 6 yesterday.
After a long battle i got that retarded "out of sync" bs fixed finally using system-config-display command and was finally able to start X. Before i go installing ATI's newly released drivers and stuff, i cant connect to the internet even though it detected my network card just fine.
I went into Network and went to Activate it and it sits there saying its trying to get an IP for like 5 min the says it cant get an IP. I also cannot access my router from within linux, usualy in windows useing firefox i type hxxp://gateway/ to access my 2wire router/modem, i havent had any probs with this router in xp/vista or on my 360 as far as connecting to it so linux should be able to work with it too. But now i am stumped, is there a simple way i can resolve this problem i dont really wanna reinstall linux again or something that drastic.
Also should i be worried about this error message during boot-up "FATAL acpi_cpufreq not found".

My system info just incase.
ATi x1900 allinwonder
Athlon64 3700+
2gb ocz platinum
AsRock 939dualsata2

I don't know but it sounds like the kernel may not have the right driver for your card.
Did you check dmesg to see if any info was given that might pertain to the network or the ethernet card?

I would suggest you find out what kind of ethernet card you are using and google to find what are the possible drivers for it, then check whether these are being loaded into the kernel.

If they are not there, the worse case scenario is probably that you will have to re-compile the kernel to get them added.

-mark

Do a /sbin/lspci -v and give us what it says about your Network card eth0.
I have a 2Wire router also and I had to call 2Wire support and get some help on setting up wireless. It was about setting up a bridge.
2Wire also requires a WEP key with wireless.

Jim

it looks like it may have the wrong driver installed, i downloaded the proper driver from ULi, burned it to a cd in windows and booted back to fedora, read the readme file and i wasn't able to find the directory it was talking about.
I copied the readme text here. Ill go back to fedora and type that /sbin/lspci -v and report back.

------------------------------------------------------------------------------------
ULi M5263 10/100M Ethernet Controller Driver for kernel 2.6.x
------------------------------------------------------------------------------------

Copyright (c) 2004-2005, ULi Electronics Inc.


------------------
CONTENTS
------------------
1. ULi M5263 10/100M Ethernet Controller Core
2. File Signature
3. Installation Guide
4. Revision History
5. Disclaimer


1. ULi M5263 10/100M Ethernet Controller Core
=============================================
You can use command
/sbin/lspci -n
or
cat /proc/pci | grep 5263
to determine whether ULi M5263 Ethernet controller exists in your
system. If yes, simply follow the steps below to install the driver.

This driver is dedicated to support ULi M5263 10/100M Ethernet
Controller under Linux platform.

Any improper use of this module, such as combining it with different
hardware and/or software environment, may produce unpredicable results.
The author of the driver and its property owner do not have
responsibility for any property lose or damage.


2. File Signature
====================
/driver/uli526x.c source codec c file
readme.txt this file
====================
/sample/Kconfig.in configuration sample file
/sample/Makefile.in sample makefile

3.Installation Guide
====================
To install the driver, you should reconfigure and recompile your Linux
kernel as follows:

Make sure your kernel version number is 2.6.x.

Copy uli526x.c to /usr/src/linux-2.6.x/drivers/net/tulip/, and modify the
following file in this directory. (Make a backup of them.)

1.Kconfig.in
add the following lines to Kconfig.in file.(refer to the Kconfig.in file we provide to you)

config ULI526X
tristate "ULi M526x controller support"
depends on NET_TULIP && PCI
select CRC32
---help---
This driver is for ULi M5261/M5263 10/100M Ethernet Controller
(<http://www.uli.com.tw/>).

To compile this driver as a module, choose M here.

2.Makefile
add the following lines to Makefile.(refer to the Makefile we provide to you)

obj-$(CONFIG_ULI526X) += uli526x.o
------------------------------------
Install as a kernel module
------------------------------------

Step 1:
Change directory to /usr/src/linux-2.6.x
Use the command "make menuconfig" or "make xconfig", and make
sure "ULi M526x controller support" is set as module.

Example:
Select "Device Drivers"
Select "Networking support"
Select "Ethernet (10 or 100Mbit)"
Select "Tulip family network device support"
Unselect "DECchip Tulip (dc2114x) PCI support"
Select "ULi M526x controller support" as "m"

Step 2:
Select "Loadable module support", and unselect "Set version information
on all module symbols"

Before exit, save your configration.


Step 3:
make modules
make modules_install

Step 4:
rmmod tulip
modprobe uli526x

Then, you can bind any protocol into M5263 driver and use it.

------------------------------------------
Install as a part of linux kernel
------------------------------------------

Step 1:
Change directory to /usr/src/linux-2.6.x
Use the command "make menuconfig" or "make xconfig", and make
sure "ULi M526x controller support" is set as kernel.

Example:
Select "Device Drivers"
Select "Networking support"
Select "Ethernet (10 or 100Mbit)"
Select "Tulip family network device support"
Unselect "DECchip Tulip (dc2114x) PCI support"
Select "ULi M526x controller support" as "y"


Step 2:
Select "Loadable module support", and unselect "Set version information
on all module symbols"

Before exit, save your configration.


Step 3:
make
cp arch/i386/boot/bzImage /boot

Step 4:
If you use grub to boot your linux, then
1) Modify the file /etc/grub.conf by adding
title 2.6.x
root (hd0,2)
kernel /boot/bzImage ro root=/dev/hd1
The disk partition where your linux resides in,
for example: /dev/hda1
2) Reboot and select the kernel 2.6.x

Then, you can bind any protocol into M5263 driver and use it.

ok, here we go, took me a while to find a blank floppy to save the text to.

00:00.0 Host bridge: ALi Corporation M1695 K8 Northbridge [PCI Express and HyperTransport]
Flags: bus master, fast devsel, latency 0
Capabilities: [40] HyperTransport: Slave or Primary Interface
Capabilities: [5c] HyperTransport: MSI Mapping
Capabilities: [68] HyperTransport: UnitID Clumping
Capabilities: [74] HyperTransport: Interrupt Discovery and Configuration
Capabilities: [7c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable-

00:01.0 PCI bridge: ALi Corporation PCI Express Root Port (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000a000-0000cfff
Memory behind bridge: ff200000-ff2fffff
Prefetchable memory behind bridge: aff00000-cfefffff
Capabilities: [40] Power Management version 2
Capabilities: [48] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable-
Capabilities: [58] Express Root Port (Slot+) IRQ 0
Capabilities: [7c] HyperTransport: MSI Mapping
Capabilities: [88] HyperTransport: Revision ID: 1.05

00:02.0 PCI bridge: ALi Corporation PCI Express Root Port (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Memory behind bridge: ff300000-ff3fffff
Capabilities: [40] Power Management version 2
Capabilities: [48] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable-
Capabilities: [58] Express Root Port (Slot+) IRQ 0
Capabilities: [7c] HyperTransport: MSI Mapping
Capabilities: [88] HyperTransport: Revision ID: 1.05

00:04.0 Host bridge: ALi Corporation M1689 K8 Northbridge [Super K8 Single Chip]
Flags: bus master, fast devsel, latency 0
Memory at d8000000 (32-bit, prefetchable) [size=128M]
Capabilities: [40] HyperTransport: Slave or Primary Interface
Capabilities: [60] HyperTransport: Interrupt Discovery and Configuration
Capabilities: [80] AGP version 3.0

00:05.0 PCI bridge: ALi Corporation AGP8X Controller (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=64
Memory behind bridge: ff400000-ff4fffff

00:06.0 PCI bridge: ALi Corporation M5249 HTT to PCI Bridge (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=32
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: ff500000-ff5fffff

00:07.0 ISA bridge: ALi Corporation M1563 HyperTransport South Bridge (rev 70)
Subsystem: ASRock Incorporation Unknown device 1563
Flags: bus master, medium devsel, latency 0

00:07.1 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
Subsystem: ASRock Incorporation Unknown device 7101
Flags: medium devsel

00:11.0 Ethernet controller: ALi Corporation ULi 1689,1573 integrated ethernet. (rev 40)
Subsystem: ASRock Incorporation Unknown device 5263
Flags: bus master, medium devsel, latency 32, IRQ 23
I/O ports at e800 [size=256]
Memory at ff6ffc00 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2

00:12.0 IDE interface: ALi Corporation M5229 IDE (rev c7) (prog-if 8a [Master SecP PriP])
Subsystem: ASRock Incorporation ASRock 939Dual-SATA2 Motherboard IDE (PATA)
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18
I/O ports at ff00 [size=16]

00:13.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) (prog-if 10 [OHCI])
Subsystem: ASRock Incorporation Unknown device 5237
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 19
Memory at ff6fe000 (32-bit, non-prefetchable) [size=4K]

00:13.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) (prog-if 10 [OHCI])
Subsystem: ASRock Incorporation Unknown device 5237
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 20
Memory at ff6fd000 (32-bit, non-prefetchable) [size=4K]

00:13.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) (prog-if 10 [OHCI])
Subsystem: ASRock Incorporation Unknown device 5237
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 21
Memory at ff6fc000 (32-bit, non-prefetchable) [size=4K]

00:13.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01) (prog-if 20 [EHCI])
Subsystem: ASRock Incorporation Unknown device 5239
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 22
Memory at ff6ff800 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Flags: fast devsel

01:00.0 VGA compatible controller: ATI Technologies Inc R580 [Radeon X1900 XT] Primary (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Unknown device 0412
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at b0000000 (64-bit, prefetchable) [size=256M]
Memory at ff2f0000 (64-bit, non-prefetchable) [size=64K]
I/O ports at c000 [size=256]
Expansion ROM at ff2c0000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint IRQ 0
Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-

01:00.1 Display controller: ATI Technologies Inc R580 [Radeon X1900 XT] Secondary
Subsystem: ATI Technologies Inc Unknown device 0413
Flags: bus master, fast devsel, latency 0
Memory at ff2e0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint IRQ 0

04:06.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
Subsystem: Creative Labs SB Audigy 2 ZS (SB0350)
Flags: bus master, medium devsel, latency 32, IRQ 20
I/O ports at d880 [size=64]
Capabilities: [dc] Power Management version 2

04:06.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04)
Subsystem: Creative Labs SB Audigy MIDI/Game Port
Flags: bus master, medium devsel, latency 32
I/O ports at dc00 [size=8]
Capabilities: [dc] Power Management version 2

04:06.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04) (prog-if 10 [OHCI])
Subsystem: Creative Labs SB Audigy FireWire Port
Flags: bus master, medium devsel, latency 32, IRQ 21
Memory at ff5ff800 (32-bit, non-prefetchable) [size=2K]
Memory at ff5f8000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2

[root@localhost ~]#

sounds like you are nearly fixed

the lspci -v output shows that the ethernet card is the ULi M5263 10/100M,

and you have the proper driver for it, so all you have to do is follow their instructions from that readme you posted and everything should go fine. I would compile the driver as a module, rather than building it in to the kernel directly, but that really is up to you. In either case, just make sure that no other driver gets loaded that might interfere with your new one. They mention removing the tulip driver. Perhaps that's the only one you really need to worry about.

mark

I don't really understand how to install it as a module, last time i actually used linux i installed my drivers from source rpm's or the tarball files. Also the directory it says to go to does not exist (/usr/src/linux-2.6.x/drivers/net/tulip/), for me its just /usr/src/Redhat/ which contains a source and rpms folder and a couple others.

I should be wary of diagnosing from afar, but assuming that I am not completely off-base, your problem is a simple one - at least simple to state. You need a kernel with the uli526x driver. You are going to get this by including it as a loadable modules - the way most drivers are included. To get this, you need to make a few changes to the code files, compile and install the modules. In principle, this should be easy. You'll just follow the standard kernel building process and follow the instructions in the readme. However, little annoyances can arise that will throw a spanner in the works - files might not be in the right place, or on you system, etc. and you will may have to deal with these annoyances.

To make the modules you will have to do some recompiling using the make and gcc tools. Those build tools will presumably be already on your system, and should not be difficult to obtain otherwise.

You need to find out exactly which version of the kernel you are running. Doing
will tell you this. You then need to find the source files for this kernel version. Presumably it is within /usr/src/Redhat. For example, on my (debian) system uname -r gives me 2.6.12, and my sources files are inside /usr/src/linux-2.6.12. I guess you will have to root around to find your's.

Then you have to follow the instructions as laid out in the readme. Copy the files that need to be copied (e.g. copy uli526x.c to "dir_where_source_files_are"/drivers/net/tulip/) and using your favourite editor, makes the changes to the code in these files that they suggest, e.g. the Kconfig.in

Now you are going to be doing some kernel module building. Essentially you are making a new kernel, but just building to loadable module parts, and the kernel itself stays the same. Overall the process feels quite similar. If you have never done this before, just consider it a rite of passage. There will be plenty of guides online to help you. Here is one of the first I found on google that might be of use to you.

Inside "dir_where_source_files_are", you will run a gui to configure your kernel for the build you are about to do. I use
which will bring up a curses gui, as this is a pretty simple interface. There are other ones like make xconfig which do the same thing. All you have to do here is go into the subsections for specifying network drivers and select and deselect options according to the readme instructions.

Then you do the build
and then the install
then you remove the old module and load up the new one, as per instructions, and then restarting the network should get your ethernet card working. Also the next time you reboot, everything should be loaded properly, as the appropriate changes should be made to the module startup files , which should be somewhere inside /etc/, like perhaps /etc/modules.conf (I'm not sure where fedora keeps these files).

maybe this sounds like a hell of a lot of work, just to get your internet working. and in a way, it is. but you are off the beaten track once you are in linux and hardware makers don't lose a lot of sleep worrying about making things easy for their linux users. I guess they figure that linux users will be able to figure it out for themselves. I will personally take that as a compliment.

-mark

managed to get it working, tyvm. Turns out the files where in /etc/bin.