Can anyone here help me out in configuring a pc with fedora linux 3.

[geckosfeet]

I got a good install but cannot see my ethernet card or modem.

Ultimate goal is to set it up a LAMP system for web development.

[mode13h_net]

1. Do you happen to know the model/manufacturer of your NIC?

By that, I mean your ethernet card -- and your modem as well. With that info you or I could figure out what chipset is on the card and load the appropriate driver for it via insmod or modprobe. I'm assuming they are pci - if not there is a tool/package out there called isa-pnp...

You can also goto the console as root and type 'lspci > lspci.txt' (assuming fc3 has pci-tools installed, which i'm sure it does) and then post that txt file on this thread and that would help too.

on edit: btw, you may want to consider fedora 4. I have very little exp. with red hat (i use solaris, irix, and slackware) but I hear fedora core 3 was really buggy

[geckosfeet]

2. Hey mode. I am looking at cards; nic is an old 3Com Etherlink XL PCI

Lets see,, it says 3C900-Combo, 03-018-002 Rev. A. SN=6MP1312A57. Dated 1996. Whew. The main IC says 3Com and Lucent on it. Didn't Lucent buy this part of 3Com a while back?

Modem looks like conexant chipsset. Don't see a manufacturers name.
AOPEN FM56-PM
P/N 91 AC0001 328
S/N 92910312TCE2

Looks like it was made in 1999.

Old PC, :)

OK,, did the lspci. Sorry I will have to type this: : ethernet controller says 3Com Corp. 3c900 10Mbps Combo (Boomerang).

Communication controller (modem): Conexant HCF 56k Data/Fax/Voice/Spkp Modem (rev 08).

Well I suppose that means that my install had the drivers eh? Just hangs on eth0 when its booting and says it fails.

Yes I see core 4 is out and I have considered it. I just figured I would try and learn some Linux on v3. For where I am at right now I am not sure the bugs make that much difference!

[mode13h_net]

3. Ok, here is a few things to try

I'm sure fedora has the drivers for boomerang/vortex based 3com nic's ... the module you'll want to load is 3c59x . I don't know the names of the start up scripts for fedora - but they will most likely be in something like /etc/rc.d or /etc/rc.x with x being the run mode. You will have to consult some other fedora users or a howto for that. However.. to at least test out the nic - as root type "modprobe 3c59x" .. then "tail /var/log/messages" which will show you the latest syslog. if it shows eth0 coming up and the driver loading then your nic is working.

Remember - if you are using a hub set the nic to half duplex mode using something like 'ethtool eth0 duplex half'.. hubs don't auto negotiate very well. however, its going straight into a cable modem or a switch then you can leave it alone and it will auto-neg and set itself correctly.

Also, I believe fedora using 'dhcpc' for dhcp (which a cable/dsl router/modem usually uses for assigning ip addresses) so an easy way to get an ip if one isnt assigned when 3c59x is loaded, is to type "dhcpc eth0"

The modem might be a different story. Linux is sketchy with winmodems because they sacrificed hardware performance for cost by using your cpu to handle the modem. Almost all recent conexant based chipsets are winmodems and have closed sourced win drivers - It's a difficult subject for a linux beginner to tackle but if you really want to try it then let me know. Otherwise, buy a hardware based chipset modem - they usually run around 80 dollars new, however - last time i checked.

Remember - I'm speculating on most of the bash commands heres, I'm not a redhat user and this is coming solely from my experience with solaris and slackware.

on edit: I found a thread discussing modems for linux...

http://www.democraticunderground.com/discuss/duboard.php?az=view_all&address=240x671

[geckosfeet]

6. OK - eth0 passes boot - don't think it was modem,,, I assuming

a dhcp server configuration using my XP machine as host. No go with XP so I had to assign IP address, netmask etc.

But I got a nice new US Robotics nic while I was at comp usa shopping for a dvd burner.

[FormerDittoHead]

4. Try another NIC to troubleshoot.

I know, I know. Linux should work with that card, linux never has any problems with anything.

But I have an old 3Com here (didn't they go for like $100 back then?) which, to troubleshoot the problem, swapped out for a cheep-o D-Link ($5) and volia. Try Linksys as well - work just fine. Your time isn't worth messing around.

YES, I tried downloading source drivers, compiling, etc etc. Just get another card and test it.

PCI Modem: Is your modem a "WinModem"? 99.999% of PCI card modems are "WINmodems". It SHOULD work, sure, but it's not worth your time, unless you're in prison or something and you have time to kill.

Buy a cheap external modem. Volia. Get hours of your life back and see a movie instead.

[geckosfeet]

5. Time is money,,,

Thanks guys. I am pretty new with linux and really want to get this up and going. Think I am going to try to pick up a new nic - they are cheap enough. Quicker and more productive in the long run.

eth0 will not come up - fails on every boot. A working modem would be a plus but is not required at this point.