[JohnWill]

I just downloaded SUSE Linux 10.0 and installed it under Microsoft Virtual PC 2004. The install seemed to go well, however the one hurdle I can't seem to cross is it detected the emulated NIC during the install, but I get an error when it boots, and it says it failed to detect an interface. Naturally, I installed Win98 in another virtual machine and it found the NIC with no issues.

Anyone got any idea how I get to the network configuration and try to figure out what's going on?

Note: Linux newcomer here, if that's not apparent!

[lynch]

Drill down through Menu> System> Configuration> Yast> Network Devices.
lynch

[JohnWill]

I did that, and re-ran the configuration and once again,it appears to like what it sees, but networking still doesn't work.

[saikee]

Can't afford MS virtual PC and would not know an emulated nic.

However if there is a physical nic and it should be named eth0 (or eth1) in Suse then in terminal mode either one of these two commands may kickstart the nic

ifconfig eth0
dhcpcd eth0

If a IP address is assigned from the response to the first command then the network should run. The quick return with nothing also mean success for the second command.

I assume you use DHCP.

PS John, It is an honour to have you here. Thanks for sending the Linux-related newbies here from other parts of the forum.

[JohnWill]

I'm one of the Linux newbies!

I'll give those a try, the GUI configuration didn't do it.

[jiml8]

Need to take a look at your startup scripts and how your system config is recognized.

Frankly, I had thought that virtual PC wouldn't handle Linux; guess microsoft has improved it.

Anyhow, as saikee said, run ifconfig and see what happens. also report the output here.

Then, as root browse to the directory /etc/rc.d/init.d and see if you have a script called network. If so, then run "./network start" (without the quotes) and see what happens.

Also, try running lspci to see what things your virtual system sees as connected to the pci bus.

[saikee]

Yast only tests the nic but shows very little in reporting. I think in the Red Hat and Mandrake GUI they show a list of the detected nics and you can highlight the card and then select "activate". That way the card's status is shown clearly before and after the activation.

[JohnWill]

There are a number of people apparently running various version of Linux under Virtual PC successfully, I'm just not one of them yet.

Hmm... I get a Device not found when i do a ifconfig eth0, that's not good.

I went into the YaST2 console and I brought up the Network Card, it thinks it's a DECchip 21140, which is correct. It goes through it's list of actions until it gets to SUSEconfig, hangs there a while, then completes. However, the network doesn't work after it's done. The only thing I can ping is the local host name and localhost.

When I try to edit, I get a message that says:

The resolver configuration file (/etc/resolv.conf) has been temporarily modified by dhcpcd. You have two options:

1. Modify the current (changed) version of the file.
2. Press 'Accept' now and continue editing the other (nonresolver) data. You could return to this dialog later when the above service has terminated.

One curious issue, in the Name Server list, the first one has the correct 192.168.0.1 address in light grey, almost like it's teasing me. I claims to be using the "tulip" driver for the Ethernet.

[jiml8]

what does lspci say?

what does ifconfig say? Not ifconfig eth0, but ifconfig with no options?

[lynch]

Are you connected to a router or directly to a modem? Is this computer sharing it's internet connection with the regular lan/switched network?(assuming that's the case.) Are you using dhcp?
lynch

[JohnWill]

Apparently the problem is that the initialization doesn't recognize the emulated hardware. I watched the init go by,
and when it tried to initialize the NIC, it said there was no response. I suspect that I need to somehow manually
configure the NIC without the hardware probe to get this to work. Here's the responses to the two commands, since
I have no way to get them onto the other machine, I took a picture.

To answer the other question, yes I'm using DHCP, that's how it's configured. Since Virtual PC does internal NAT,
I don't even know the IP address to use if I wanted to assign it manually.

One problem, although I apparently detects the floppy, I couldn't figure out how to access it, it didn't appear in
My Computer, and copying to /dev/fd0 didn't seem to be doing the trick. That's why I resorted to the picture.

[jiml8]

Actually that ifconfig response says your eth0 is up and running, and has obtained an address via DHCP. I presume you are connected to a firewall/router - in fact, from other posts of your I am certain of that. The lspci shows you as having only a basic system available. Do you really have a DEC nic? Must be an old one.

Why you got a device not found when you did an ifconfig eth0 is a mystery to me; asking ifconfig to list all interfaces shows it bigger'n life.

What symptoms, exactly, are you experiencing? Your network does appear to be up.

What do you get when, as root, you type in "route" (no quotes)?

[JohnWill]

I don't know what happened there, since now it is displayed. I do know that I saw it come up with an error during the boot, and that error is missing now, at least I don't see it.

I'm running this under Virtual PC, I thought I made that clear. This is an emulated DEC card, not real hardware. I've moved the virtual machine to this computer so it's easier to get screen shots. For some reason, it gets eth1, not eth0 as it's hardware, but it appears to have the same issue.

I have made real progress however! I manually entered a gateway address for my router, and now I can access the router's setup screens, even though I still don't have any DNS capability. I think I just need to figure out how to enter the DNS addresses and I'll probably be on my way.

[JohnWill]

Here's my current results from a route and an ifconfig

[jiml8]

I knew you were running virtual PC; I just see no reason why the NIC would be emulated. On VMWare it isn't - you see the actual hardware. VMWare emulates the display and the HD controller; for everything else you get the real hardware. At least, when the host is Linux you get the real hardware; don't know about the Windows version of VMWare.

In any case you have a problem in your interface definitions. In your earlier screenshot, the interface was eth0 and in this latest one it is eth1. That by itself is sufficient to cause your problems. A lot of your software will be looking for a specific interface, and if that interface is eth0 while the currently active interface is eth1, that will mess you up.

Take a look at /etc/sysconfig/network-scripts and see if there are startup scripts for both eth0 and eth1 present there. If so, you need to figure out which to use and make your system start consistently.

Your routing table has a potential issue; you need to make sure that loopback is mapped to 127.0.0.1 in /etc/hosts and /etc/networks (it should be, but then things aren't working right).

What is link-local?

Is your gateway really 192.168.131.254? This is the address of your router, of course, and most commonly it would be xxx.xxx.xxx.1 for a gateway. Doesn't have to be, of course, but this is probably the default and unless you changed it this could be your problem. Actually, this routing table makes me think that perhaps your Windows system is using ICS to allow Virtual PC to communicate with the internet; this would explain some things such as the emulated NIC. Is this the case?

VMWare, BTW, allows the virtual machine direct access to the NIC - at least, when the host is Linux.

For your reference, here is my linux routing table:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.247.0 * 255.255.255.0 U 0 0 0 vmnet8
192.168.0.0 * 255.255.255.0 U 10 0 0 eth0
192.168.40.0 * 255.255.255.0 U 0 0 0 vmnet1
default 192.168.0.1 0.0.0.0 UG 10 0 0 eth0

and here is the Windows routing table for the Win2K machine that presently is running in VMWare:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0c 29 54 91 7a ...... AMD PCNET Family Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.103 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.103 192.168.0.103 1
192.168.0.103 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.255 255.255.255.255 192.168.0.103 192.168.0.103 1
224.0.0.0 224.0.0.0 192.168.0.103 192.168.0.103 1
255.255.255.255 255.255.255.255 192.168.0.103 192.168.0.103 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None