Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
if the nic driver is installed then ping 127.0.0.1 should have given you replies - I believe.
research the spec for your board on their site and find out which nic is installed - then you can get the driver. You may have to call the oem and ask their tech support if you can't find out - otherwise it should be on their site.
hmm... it's unlikely that the card is installed right if pinging loopback isn't doing anything. strange that mandrake's autodetection didn't pick up any of your hardware... oh well. now that i think about it, probably since there are a range of hardware problems you're having, you should
a) open a terminal and su to root.
b) type "lsmod"
c) hopefully a whole list of stuff will appear. just copy and paste that whole list and post it to this forum. that's a list of all the modules (for simplicity's sake, think modules=drivers) running on the machine. linux module names are not always immediately obvious, so they might not mean much to a newbie, but it would help us all enormously to get an idea of at least what hardware your kernel thinks is on the machine so we have somewhere to start when telling it what really is there.
yeah, i don't immediately recognize a network or a sound card driver on that list (though it's entirely possible you're just using one i haven't worked with before...) very weird that it figured out that you need appletalk and ipx but didn't bother to load a nic driver--did you specifically tell it about your network protocols at install? it doesn't really matter, i was just curious.
at this point, a good and diligent person would go to whatever lengths necessary to research his machine and figure out what chipset the nic and the sound card on the motherboard are using.
however.... you might be able to get by with being impatient/lazy and just start modprobing a bunch of common modules and seeing if any work (i confess that i usually do do this...) . likely suspects for the nic are "3c59x" and "3c509" (this is an onboard nic, right? most of them use 3com chipsets, i've found, though that might be a dell-specific thing, as dell is all we have at work.) for an onboard soundcard, "i810_audio" is pretty common. to try to load them, type (for example) "modprobe 3c59x" at a command prompt. if it works, it'll pause for a minute and then look like nothing happened, but the new module will show up next time you run lsmod. it should bitch and refuse to load the module if it can't find the hardware to go with it. if none of these modules work, i guess you could keep trying others, but to be honest, you might be stuck having to do some research... hope this helps.
incidentally, to any other readers out there, i am actually a newbie in disguise, and i'm really stretching the limits of my knowledge here, just doing stuff that's worked for me in the past. i have no idea if any of this is the proper way to go about it, and i encourage anyone to jump vigorously down my throat if i'm giving bad advice.
[slapping forehead] wait, is your trident sound card still physically in the pci slot? if so, i think the motherboard will ignore the onboard and assume you want to use the pci card. try typing "modprobe trident" and see what happens. you might not even have to use the onboard at all.
I've got an old Mac SE/30 I keep for nostalgic purposes ... but my cut of Linux went on an old Compaq 4814
My Graphics card works great now ... I used the Trident over the S3 on-board... so that part has been taken care of. I'm trying to get my sound and network setup up properly now ... I'm sorry I must not have mentioned the graphics card fix before .... my apoligies. the Trident works perfectly ... Does Linux handle grpahic differently than let's say a windows machine? I noticed it looks nice a crisp on my system way better than on my ViewSonic which is hooked up to my Sony Vaio WinXP Pro machine. I am not sure if it's a better monitor on the Linux Box or just better?
I think it did detect the netowrk card though ... but configuring it has me lost
I'll try posting with a new topic in networking but I feel I'm so close I don't want to ruin my groove. If you tire of my newbieisms I'll understand I just hate having to retype all this... lol anyhow I managed to get this for you... it's a lspci and a result of the ifdown and ifup commands .... (my router's i.p. had been changed for obvious reasons)
[the_bug@localhost the_bug]$ su root
Password:
[root@localhost the_bug]# fdown eth0
bash: fdown: command not found
[root@localhost the_bug]# ifdown eth0
[root@localhost the_bug]# ping [ my router ip here ]
connect: Network is unreachable
[root@localhost the_bug]# ifup eth0
Determining IP information for eth0... done.
/sbin/ifup: line 433: 9859 Hangup /etc/init.d/tmdns reload >/d ev/null 2>&1
[root@localhost the_bug]# ping [ my router ip here ]
connect: Network is unreachable
[root@localhost the_bug]# lspci
00:00.0 Host bridge: Intel Corp. 430TX - 82439TX MTXC (rev 01)
00:01.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 01)
00:01.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:01.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:01.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 01)
00:02.0 VGA compatible controller: S3 Inc. 86c775/86c785 [Trio 64V2/DX or /GX] (
00:03.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip
00:05.0 VGA compatible controller: Trident Microsystems 3DImage 9750 (rev f3)
well the logic behind posting a new topi with "nic installation problem" [or something like that] is that more people who know about networking etc will see it and prolly respond.
anyway - we should be able to crack it -
when you if down and then if up - check to see if it's pulling an ip from the router [I presume it's set to dhcp] by typing:
ifconfig
what ip are you getting?
do you have any firewalls installed? if so - shut 'em dune thar.
do you have the cable plugged in [sorry to ask but you never know!] - if so are the lights on the router and nic on?
P.S. cables hooked up -- lights on .... I think we're very close ... not knowing anything bout Linux and looking at the ifconfig ... I presume it sees some type of network?
alas, no, a 169 ip address is an error message. i really don't know what is causing it. however, at work, (and we use exclusively windows boxes for everything but the servers) 169's are usually the result of broken jacks or invalid mac addresses submitted to the dhcp. what's your router setup? is it set to give an ip to any card that asks, or just to approved mac's?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
yeah, i don't immediately recognize a network or a sound card driver on that list (though it's entirely possible you're just using one i haven't worked with before...) very weird that it figured out that you need appletalk and ipx but didn't bother to load a nic driver--did you specifically tell it about your network protocols at install? it doesn't really matter, i was just curious. 
research... hope this helps.
