Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Maybe I should post this in the slack section, I don't know.
Long story short: I garbled up a Wine install, couldn't get rid of it, and through laziness, chance and misfortune, it took me nearly a year to get around to re-installing Slack on my (fairly) new computer.
During this time, Slack has updated from v9 to 10, so I grabbed and burned new discs.
The installation goes off with the only hitch being a bad re-writable that needs to be laid to rest. I have now successfully made a dual-boot computer.
I pick a WM... and open Mozilla. No internet connection. Upon reflection, I had found it rather odd that during boot, Slack didn't automatically try to find an internet connection like it did the other times I installed.
Now, my hardware has changed, but I know that shouldn't be a problem. The only thing I did differently when I installed, was that I didn't have it find the network card before typing Setup at the prompt. (I didn't do it because I thought it was saying "do this if you need to install slack over the network, which I wasn't doing)
Will reinstalling and setting up the network card before typing setup fix my problem? Is there a way to set it up now that Slackware's been installed?
Thanks in advance,
Last edited by ElvenAssassin; 04-24-2005 at 07:20 PM.
just recently.. say 2 days ago.. iv gotten around to [succesfully ] setting up slack 10.0
in most distros iv tried the network card was automatically found and configured, not in slack.
ya i remember seeing what your talking about.. before typing 'setup' theres an option to type 'network' to setup and configure your NIC. i dont think that if you reisntall and select that option before isntalling, will change much. i think that if your network card still isnt auto-detected now it wont if you do what your possibly suggesting.
when i installed slack i did choose the 'network' option and it searched through a list of included drivers to see if they are for my NIC and it didnt find one. so i had to download the driver for my NIC and load it [which is surprisingly easy--besides the problem im having, which i previously made a thread here for anyone who could help me with that ].
so the question is... what NIC do you have? can u get a linux driver for it?
edit: you might want to check out this link..although actually i think it wont help much till you get a driver for the nic.
mine was a 3Com, which is a globally popular company and it didnt even auto-detect my card... the one you mentioned doesnt ring a bell, and im sure that it wouldnt be auto-detected either [not saying im a networking guru, but..]
so start searching yahoo, google, internet, [or even inside your pc case?] for your motherboard model and a link to your NIC linux driver download. i got mine from the asus site and would bet if your card is somewhat new, which u said it is, that youll be in luck if you search there. there should be a 'download' page for your mb. on the asus site and can probably find it there
sorry.. im still a newbie to linux, so cant help you further. if you cant find a linux driver for your nic.. i dont know what to say or what you should do. is there another linux driver that would be compatible with that card? you probably thought about this and it isnt the case.. but does your old mb have a non-onboard nic?
I did some more poking around, this time at Marvell's website (even though a search through Google was fruitless), and I might? have something... so thanks a bunch for directing me on how to go about trying to install drivers.
also, when you said 'install' (referring to the driver).. maybe im wrong, and quite possibly.. but.. (at least for mine) the command that i read to do to setup my nic was a command to 'load' the driver.. so you load the driver to control the nic, and not 'install'. so each time the computer is booted the driver for the nic must be loaded.. which is what my other thread [which i linked to earlier] that i started was regarding. im having a problem which hopefully is being resolved, that each time i turned on the computer, my nic wasnt recognized.. so i had to load the driver again.. and im looking for a way to have the driver automatically loaded at boot to avoid this.