Hi there!

I have an AMD Duron 600, 320 MB RAM, 2 fixed hard drives, both ATA 100/133. Linux is installed on my second drive, and I loaded the boot loader into the first sectors of the partition, not the hd1 mbr.

Grub figured it all out, and I now have dual boot, Win98 as my option, Linux as my default... all loads, except Linux sees my eth0 card, but cannot make it active. Fedora Core 2 install. eth0 is the only error in bottup (says its not connected - check cable...) It works fine in Windows, so I know there is cable net available.

eth0: 3Com 509B TPO

Thanks for any help! One thing I did notice is that my cmos is assigning the same IRQ for my sound card as my eth0, whether this would make a dif. i dont know? I'll try unplugging it, but I have no conflict in Windows.

Kyle

Is it loading the 3com module for your card?

lsmod will display such information.

If it is loading the module, if not sure post the lsmod output here, have you configured the card? Did it ask to configured at install?

I am still very new to these terms, sorry, i don't have a linux book yet, so really, I have no clue what you are asking LOL

When it boots,

it finds the network adapter, names it appropriately, then tries to make a connection, can't, tells me:

bad cable? [failed]

something to that effect. If i knew the appropriate logs to share with you (their names and locations) I'd post them.

Seems my 98 crumbled in all the process of switching around ethernet cards to get something to work, so I had to reinstall it, now I'll have to do GRUB again? I guess... I dunno, this is all very very complicated compared to Windows, that's for sure.

Thanks

I've experienced the same problems with the 3c905 card. My final solution was disabling Kudzu on bootup. I don't know why, but this always solves the problems for me.

I've also heard that passing 'acpi=off' to the kernel on bootup will solve the problem, but I haven't tested this myself. So, if you can't bear to loose kudzu on boot, then you might want to give this a try.

Hope that helps.

Jared

Hmmm ok

Seems I have a new problem. Linux disappeared, or grubloader got overwritten in the MBR or something. I reinstalled W98 on my c:\ and now grubloaders gone.

I tried booting Disc 1 and typing "linux rescue" and it found the installation, did some mount thing, told me to type chroot /mnt something-or-other, and I did but it didnt fix it.

How to get grubloader back in there?

Then if i do, how do you, do, what you suggested, like exactly how do you disable something at boot up?

Thanks
Kyle

See if this helps; http://www.linuxcompatible.org/thread27844-1.html

Thanks folks!

Managed to get GRUB re-loaded into MBR. See my other thread for solution, thanks to all that helped!

Now...

How do I disable kudzu or set apci=off during boot-up?

Which is the most logical solution?

Linux seems to see my ethernet, calls it what is is (3com XL 309B TPO PCI), on eth0, but.... it does not connect to the net?

also, when I first installed Linux, I made my / and /boot partions of the ext2 file type.... is this correct?

Thanks
Kyle

Thanks again folks!

I am now replying in Linux! Isn't this a beautiful thing when an idiot like me can get a dual boot system up in an evening LOL

To resolve the eth0 not connected to the net, I chose run Interactive boot, and said "N" to using kudzu, and everything seemed to work
nicely.

I guess I'll try disabling it completely as I do not plan on adding any new hardware.

Thanks!!!!!
Kyle

To disable it completely on bootup, you can use 'system-config-services.' Just uncheck the box next to kudzu in the services list (and make sure to save before exiting).

Hello... glad your 3c509 is working better.

Two things for you to be aware of....

1) Even disabling kudzu is not guarenteed to get rid of your problems. We have a large number of 3c905's (same driver) and still can't use them reliably in our FC2 boxes even though we disable kudzu. This is a known problem in the 3c509 module and there is an outstanding Bugzilla issue for it (107389).

https://bugzilla.redhat.com/bugzilla....cgi?id=107389

We don't use the boards in our newly built FC2 boxes because we have had lots of errors, retransmits, funky behavior and slow transmission times. Our few boxes that have 3c905's in them (like some workstation machines) have ongoing networking problems like ill-behaved NFS and failed RCPs and other such obnoxious tendancies. If you can get a non-3com NIC to use for a while you will probably be happier.

The latest grousing about the problem indicates that Fedora Core 3 Test 2 does not have a fix for this problem either. We particularly hate this bug because we have about a dozen really good 3c905 cards that we can't use until it is fixed.

2) The command line (my always-preferred method) way to change the kudzu boot (or in this case, non-boot) behavior is like this:

/sbin/chkconfig --level 345 kudzu off

To display which run-levels kudzu will run at, use:

/sbin/chkconfig --list kudzu

Hope that helps,
Jeff W.

Jeff,

Thanks for the pointer!

Do I leave kudzu disabled on boot-up as seen in the system settings/server settings/services? or recheck it to run on boot up, after i make this shell change?

Thanks
Kyle

Hey kyle,

What jeff posted was just a command-line version of the the same thing that I posted previously (a great thing to know if you're stuck without X and you need to disable/enable a service on boot). So, they accomplish essentially the same task.

Right, same thing. I would encourage you to leave kudzu disabled until the upgrade that fixes the 3c5xx/3c9xx problem is available and installed on your machine. If you add or change other hardware to your system you can run kudzu manually and then reboot.

Thank you!

Now it works for me too!