Network not found

English Network/Internet
#1

first the issues: I initially could not even boot into OpenSUSE 12.1 but with an added option of “nomodeset” resolved that however even through during bootup the hardware for both my wired and wireless network cards are detected and cleared once I have logged in and attempt to configure them. I can chose between the tabs for wired and wireless but selecting config the dialog boxes are grayed out. When I tried to use any network commands at the command line I was repeated met with command not found. I used a standard install and the cards where in the auto config. can you point me in the right direction here or is this for what to look for next.

System considerations: My system is dual booted but on separate drives with windows 7 32bit on sda and openSUSE 12.1 on sdb all network hardware and software work fine in windows.

#2

So you can’t use both Network Manager and manually configure your network devices. If you have a wired connection, it is often best to use it to get your wireless working. If you go to YaST / Network Devices / Network Settings, what are you greeted with? Can you tell us more about your computer hardware and if you know the exact type of network device you are trying to use? How are you getting online right now?

Thank You,

#3

I am dual booted and the windows side works fine so I log out and go into windows to get here, I will get what I can shortly and return. I will also attempt a wired connection before returning and see what happens.

#4

You have the networking set to be handled by the networkmanager. Hence the network connection should be made from the desktop. But…when your machine stays in place forever, you could change the networking in the general tab to the traditional method, ifup. This would allow you to configure the wireless. But the config will stay greyed out until you make the switch as described.

#5

Yast provides the following network info:

SysFS ID: /class/net/lo
Hardware Class: network interface
Model: “Loopback network interface”
Device File: lo
Link detected: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown
67: None 00.0: 10701 Ethernet
[Created at net.124]
Unique ID: usDW.ndpeucax6V1
Parent ID: rBUF._LiPOPOWg1B
SysFS ID: /class/net/eth0
SysFS Device Link:
/devices/pci0000:00/0000:00:1e.0/0000:01:0c.0
Hardware Class: network interface
Model: “Ethernet network interface”
Driver: “e1000”
Driver Modules: “e1000”
Device File: eth0
HW Address: 00:0d:56:9d:be:46
Link detected: no
Config Status: cfg=no, avail=yes, need=no,
active=unknown
Attached to: #31 (Ethernet controller)
68: None 00.0: 1070a WLAN
[Created at net.124]
Unique ID: AYEt.QXn1l67RSa1
Parent ID: y9sn.s_MB2x+swO4
SysFS ID: /class/net/wlan0
SysFS Device Link: /devices/pci0000:00/0000:00:1e.0/0000:01:09.0
Hardware Class: network interface
Model: “WLAN network interface”
Driver: “rtl8180”
Driver Modules: “rtl8180”
Device File: wlan0
HW Address: 00:17:3f:d3:ed:cc
Link detected: no
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #30 (WLAN controller)
The machine is an old Dell Optiplex 270 Intel 3ghzSysFS ID: /class/net/lo

Hardware Class: network interface

Model: “Loopback network interface”

Device File: lo

Link detected: yes

Config Status: cfg=no, avail=yes, need=no, active=unknown

67: None 00.0: 10701 Ethernet
[Created at net.124]
Unique ID: usDW.ndpeucax6V1
Parent ID: rBUF._LiPOPOWg1B

SysFS ID: /class/net/eth0

SysFS Device Link:
/devices/pci0000:00/0000:00:1e.0/0000:01:0c.0

Hardware Class: network interface

Model: “Ethernet network interface”

Driver: “e1000”

Driver Modules: “e1000”

Device File: eth0

HW Address: 00:0d:56:9d:be:46

Link detected: no

Config Status: cfg=no, avail=yes, need=no,
active=unknown
Attached to: #31 (Ethernet controller)

68: None 00.0: 1070a WLAN
[Created at net.124]
Unique ID: AYEt.QXn1l67RSa1
Parent ID: y9sn.s_MB2x+swO4

SysFS ID: /class/net/wlan0

SysFS Device Link: /devices/pci0000:00/0000:00:1e.0/0000:01:09.0

Hardware Class: network interface

Model: “WLAN network interface”

Driver: “rtl8180”

Driver Modules: “rtl8180”

Device File: wlan0

HW Address: 00:17:3f:d3:ed:cc
Link detected: no

Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #30 (WLAN controller)

The machine is an old Dell optiplex 270 Intel 3.0Ghz Dual Core processor with 3 Gb Ram and a total of 1.6Tb storage the Nic’s are an optiplex GX270 as Eth0 and a Belkin Wlan as Eth1

#6

I have tried both methods unsuccessfully and ifup does nothing to change the status of the cards yet these very same cards work fine in windows. I need this as a study tool I am not unfamiliar with networks and systems but need to network operational to be of benefit to me first. As I have not stated it in earlier posts I am logged in as root and while the hardware shows and the software sees the cards nothing allows me to config them even at the command line level. This said I have not scripted any files, could this be an issue or am I headed into something i don’t need there.

#7

forgot to mention NetworkManager locks up my system requiring a hard boot, but I am trying to access it from XTerm is that causing the lock up. I see no general tab in the network tools gui though.

#8

I forgot to mention that attempting to launch NetworkManager from command line does not work and trying it in XTerm locks my system solid requiring a hard reboot, but I see no general tab in network tools within the gui. Maybe I have the wrong info about configuring the cards. If I just did it straight from the command line as root what directory should i be in and what commands with the options should I be using. The reference I have is 10 years old and not that great for examples at the command line. What I normally deal with is already installed and configured often running for a while, then I am using trace and route as well as ipconfig and netdiag or net, even telnet to diagnose things. What am I missing here since am not familiar with the initial setup.

#9

Guess I said something which made everyone run away thinking I am an idiot, no I am not but I am very rusty but in a hurry, just give me a quick run through of what HAS to be done and I will leave you elitists alone.

#10

Can someone take a moment and just give me a quick run down of what MUST be done and in what order. Brief reminder using suse 12.1 and dual booted with windows 7 and network works fine in windows so cards are good. I want to resolve this quickly to have some background in it before starting my course and be able to work things out so I can study at home once the course is ongoing.

#11

Guess I said something which made everyone run away thinking I am an idiot, no I am not but I am very rusty but in a hurry, just give me a quick run through of what HAS to be done and I will leave you elitists alone.

Sometimes it can take some time for other who may be able to help to come along. We all live on different parts of the planet with other responsibilities and priorities. We’re all just users and our time is voluntary, although most of us get satisfaction from being able to assist where we can. The other thing is, so far there is not a lot of real info to go on.

As I have not stated it in earlier posts I am logged in as root and while the hardware shows and the software sees the cards nothing allows me to config them even at the command line level.

Don’t log in to the desktop as root. Log in as a regular user. Let’s start from the top:

  1. Which desktop are you using - KDE, Gnome, …?

  2. Open a terminal window, and type

/sbin/lspci -nnk|grep Net -A3

This should return info about your network hardware.

  1. Lets look at whether you have configured the YaST>>Network Devices>>Network Settings to use NetworkManager. Open a terminal and execute the following command
 cat /etc/sysconfig/network/config |grep NETWORK
  1. Enter the following command to tell us whether NetworkManager is running
/sbin/rcnetwork status

Report back. There will probably be more questions or advice from this…

#12

On 09/25/2012 09:46 AM, sjguy1962 wrote:
> Can someone take a moment and just give me a quick run down of what MUST
> be done and in what order.

well, i took a win7 loaded netbook, and all i found that MUST be done
was plug in a cord from my netbook ethernet port to my router’s ethernet
port and then boot from the install media and run it openSUSE!

openSUSE found and configured the network and used it during the install
process to download and install the very latest code available…

then i clicked on the Network Manager icon in the task bar, clicked to
“Enable wireless” then “Configure Wireless” and told openSUSE the
ID/Pass needed for connecting wirelessly, and i was finished in no time
at all…

and, i never ever logged into the desktop environment as root even once
(not since about 1999)

skeptical? plug in the network wire and boot from a Live CD, and go
surfing…no problem (yes, if wireless and not connecting to a open AP
you too must supply the ID/Pass…other than that, there is nothing to
do–if your hardware is meets internet standards and is therefore
usable by openSUSE (or Linux in general)

oh, and have you been through this or the other documentation:
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.nm.html

–
dd http://goo.gl/PUjnL
http://tinyurl.com/DD-Caveat http://tinyurl.com/DD-Hardware
http://tinyurl.com/DD-Software

#13

On 09/25/2012 09:36 AM, sjguy1962 wrote:

> you elitists

WOW!

THAT is a great way to make new friends with the VOLUNTEER helpers here!

i wish i had seen it before i took my time to try to be helpful.

–
dd