On Sun, 2005-10-23 at 18:12 -0400, Doug McGarrett wrote:
Doug McGarrett wrote:
At 01:56 PM 10/22/2005 -0400, Ken Schneider wrote:
/snip/
//snip//
What I have done so far:
I found out how to get into yast graphical mode, from a console. I don't know how to do it from the desktop. At any rate, I followed your instructions as nearly as possible.
Yast found the network card by itself. I didn't have to look in the lower area. (I looked anyway, and my "card" isn't there.) It automatically selected DHCP and it found the ip address of the router by itself for the default gateway. The following available command is not "next" but "OK". There does not seem to be a "finish" command. I forget what came next, but somehow I got back to the yast main window and closed it.
At this point I tried to ping the router itself (should work, but did not) and tried to ping an outside source which I can ping from Windows or the other Linux machine.
This is more than likely the route of the problem, here. You ought to be able to ping the router if your network card is properly configured.
Somewhere it said that the network starts at boot, so I will reboot into Suse and see if the network starts, and I'll report back either way.
Someone asked about the results of ifconfig and lsmod. Unfortunately, I do not have any way of forwarding those, since I can't save them to NTFS, and I can't send them direct from Suse--no network! Can I somehow save them to a .txt file in XP, from which I could copy and paste to this mailer?
When you're in Linux open a console shell (konsole) issue the command su - enter the root user password at the password prompt issue the command ifconfig using your mouse locate the line on the console screen where you involed the ifconfig command, and place it at the beginning of that line, left click and highlight everything until you reach the end of the output from the command. Right click in the highlighted area and choose copy. Paste the output into an e-mail. Repeat for lsmod. Frankly at this point I think you have either a driver problem, or a hardware problem.
Whoever it was also asked for the type of Ethernet hardware--its Broadcom NetXtreme Gigabit Ethernet, part of the MOBO, but Yast seems to be able to find it OK.
I rebooted Suse. No joy, no network.
Here's what I have done further. I now have the Linspire mail program on line, so I have 2 computers working. But I do NOT have networking on the Suse box. I was able to ping the ethernet hardware with a loopback code-- 127.0.0.1--and that worked OK. (I have also figured out how to get to YaST from the desktop, and how to add its icon there.)
If anyone needs to know what ifconfig or lsmod have to say, you'll have to tell me what to look for. I could probably type in the ifconfig output, but I sure can't type in the page-and-a-quarter of codes and numbers from lsmod.
See above, if you actually need to do this.
A little better description of the ethernet hardware: Yast says it's Broadcom NetXtreme BCM5702X Gigabit Ethernet.
The result I get when I try to ping the router is "Network is unreachable"
If no-one can come up with a solution, I'll reinstall and hope for the best. I'd rather not do that, because if it still doesn't work, where am I?
You shouldn't have to re-install. I've had some problems with nic's under 9.1. They'd work and then they wouldn't find the network. I found that deleting the nic in Yast, closing the NIC YaST component and then going back into it, and installing a new nic (actually the old one) worked. One other thing comes to mind here. Are you sure of your cables and other hardware? swap ports on your router, and switch cables from the box that works to the box that doesn't work. Does the box that works still work?
My thanx to those who have answered so far, and any other suggestions would be appreciated. Just please remember that I am not all that familiar--I'm not much familiar at all--with Linux/Unix.
This Linux machine, BTW, is going thru the same router.
Mike