Cannot get internet working using Intel DP35DP Motherboard
I've never had so many problems just connecting to the internet! For years, I've maintained a Windows LAN and kept computers running fairly well long past their prime. I've always considered myself more than computer literate. Heck, I've just built a computer last night with no problems... except...
I just can't connect to the internet.
I'm ready to toss the whole thing out the window. Especially with Ubuntu, the computer is nigh useless unless I can get the ethernet adapter working. Everything else works beautifully! Just can't connect.
Here is my specific build:
Intel Core 2 Duo Processor E6850
Intel DP35DP Motherboard
e-GeForce 8500 GT Graphics Card
Nspire 750W battery
G.Skill DDR2 1GB x 2 (Dual Channel)
Frankensteined DVD drive and 250GB SATA HDD
This is on a home LAN using a Linksys Wireless-G Broadband Router WRT54GS and DSL Actiontec Modem GT701. Both hardware firewalls are off. Other computer in the LAN connects just fine using wireless connection. I'm attempting a wired connection. I've tried using DHCP as well as giving it a static IP, but neither did anything.
I've tried downloading and installing the Gigabit Network Adapter Base Driver for Linux* with 2.4.18 to 2.6.x kernels (e1000-
man:
cannot write to /var/cache/
e1000.
and the install stops cold. I tried to continue the installation instructions with the command "modprobe e1000", but then I get no feedback. I recognize that some commands don't give any feedback, so I continue to the next: "ifconfig ethx <ip address>" which I entered with the ip address that this computer will have on my LAN. In response I get:
SOICSIFADDR: No such device
ethx: ERROR while getting interface flags: No such device
I've got too little experience with Linux, much less Ubuntu, to try to move forward with this method, so I tried popping in an old D-link ethernet PCI card. Still nothing.
Thinking that my motherboard might be just too new for Feisty Fawn, I tried installing Gutsy Gibbon, but that yielded identical results. I know it's not the cable, because I used this exact same cable to connect on my other desktop PC just two weeks ago (when it blew capacitors on it's motherboard, but that's another story).
Am I just missing something simple? I don't think I've ever been this frustrated with computers before now. I thought that building the dang thing would be the hard part, not connecting to the internet!
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- FrozenFlame22
- Solved:
- Last query:
- Last reply: