I just gota new computer, installed a new OpenSUSE 13.2 x86_64, but can’t connect to anything, not even the modem. I am clueless of where to begin. Can anyone help?
Computer is Intel Core i3-4150CPU @3.50 Mhz.
Kinfocenter shows only one interface detected: lo (loopback).
There’s a built-in network interface, and I have a cable plugged in between it and the modem.
Linux is not seeing the ethernet interface at all.
If you need more info just tell me what to do, (please be explicit). Thanks!
You say “Linux is not seeing …” but that is rather vague. Did you look with YaST > Network Devices > Network Settings if it is listed there?
I could not agree more to the statement that the original post is rather vague.
“Installed a new system”. Wow. What did the installer tell you about the network during the Installation? I really like those people who are doing things that they are not aware of.
Obviously the NIC was not recognized at install time. This should have been rectified already then.
Now YAST is a good place to look onto the NIC.
I do not expect, however, a NIC to be found there.
What I expect is that you will have to look for a suitable NIC Driver.
Or perhaps tell us the make and model of the computer you purchased. You might also ask your vendor what network interface card (NIC) is installed in your computer. You might also try doing a search for computer name computer model specifications.
Open a terminal window and run the following command
/sbin/lspci -nnk | grep '\02' -A3
It should return details about ‘02’ class (network) chipsets.
If it doesn’t, you can run a more general query with
/sbin/lspci -nnk
but that will return a lot of information about all devices connected to the PCI bus that we don’t need to concern ourselves with here.
You can cut and paste the output to a text file, and save to a memory stick. Then share the output with us via a computer with internet connectivity.
Well, of course it rather vague! What part of “I’m clueless and don’t now where to begin” was too cryptic for you? It’s awful arrogant and snobby to expect an admittedly clueless person to give you technical details up front without first teling him how. You should try being less hostile to newbies that don’t have your technical prowess.
I just looked for “network settings” in ‘YaST>Network devices’, but it isn’t shown. There IS a ‘Network Services (xinetd)’ shown there, however that’s not what we need, is it?
Please run the command I gave you and post the output (via a memory stick if need be).
Alternatively type the following in a terminal window
/usr/sbin/hwinfo --netcard > output.txt
then save output.txt to a memory stick.
Intel (R) Core ™ i3-4150 CPU @ 3.50GHz
I sent a text to the seller requesting info on what nic is installed, awaiting an answer.
No need to get frustrated.
When people say “Linux is not seeing …” that is by definition a useless remark. As long as computers/operating systems are not human, one should not expect human actions from it.
Thus I assume that in fact “you” saw something, or you expected to see something that you didn’t then see. We want to know what it was that triggered you in concluding that the system “did not see” the device.
Even if you say, you have no clue, there must be something that made you typing “Linux is not seeing …”. And we want to know what that is, because we do not look over your shoulder and are not clairvoyant.
Thanks for the non-judgmental response. I really do appreciate any help that doesn’t include needless criticism. I tried both comands when I finally got some electric here, and this is what I got:
Nothing.
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: hsw_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 04)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 04)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 04)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d4)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 04)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation C220 Series Chipset Family H81 Express LPC Controller [8086:8c5c] (rev 04)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 04)
Subsystem: Dell Device [1028:0612]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 04)
Subsystem: Dell Device [1028:0612]
Kernel modules: i2c_i801
Sorry for the delays in answering, I’ve been without electric here for over 24 hours, with only 1 brief connection, now a second. Let’s hope it stays on for a while.
That comand returned nothing at all.
(Omiting the ‘–netcard’ part it shows a ton of hardware info.)
There’s a port on the back where I pluged in the network cable, so the hardware is there. Linuc just isn’t detecting it.
Okay, well that output does not show any network device present. (At the very least, I would have expected to see a chipset enumerated representing it.)
You’re clearly wasting my time and bandwidth by splitting hairs over questions of semantics and rhetoric. Other people are being helpful. You’re not.
The next suggestion I have is to check the BIOS (or UEFI BIOS) configuration and make sure that the NIC is enabled perhaps. Is this a dual boot machine? If Windows is also installed, is the network interface working there?
That’s my entire point. I have a network cable plugged in to the port, which I can see on the back of the box. In previous installs of OpenSUSE on my old computer the nic was always detected and configured during the install sequnce. But now, on this new box, it doesn’t detect the interface at all - it just doesn’t see it! I’ve never experienced anything like this before, so naturally I have no clue of how to rectify this problem. What now?
That might be your point, but we’re not in front of your machine, and so there is a process of discovery needed to try to nail down the cause. 
In previous installs of OpenSUSE on my old computer the nic was always detected and configured during the install sequnce. But now, on this new box, it doesn’t detect the interface at all - it just doesn’t see it! I’ve never experienced anything like this before, so naturally I have no clue of how to rectify this problem. What now?
Well that’s the way it is for most of us most of the time. Hardware is detected and recognised by the kernel. However, I think that it may be disabled (or possibly defective), hence my suggestions and questions in my last post. Please read it and respond accordingly.
BIOS: WOW! it’s amazing how much **** is now configurable in this BIOS, it’s got more settings than you can shake a stick at! It took a while to find anything, but I finally did. You’re right! I found a setting where te NIC was disabled, and that was the problem. It’s working now THANK YOU, THANK YOU, THANK YOU!!! Ifyou didn’t mention it I wouldn’t have thought there’d be a BIOS setting where it could be disabled. Deano_ferrari, you’re a wizard and a true star! Kudos to you for having the patience to help me as I needed it! I hope others learn to follow your fine example!
I’m planning on triple-booting this one, since I have Windblows 8.1 and 10, as well as OpenSUSE 13.2. But as of now I only have Linux installed temporarily. Now that the NIC is working I’ll feel more comfortable tackling the multi-boot and reinstall. Thanks again!
Glad to have been of help. I’m no wizard - just a regular user with a bit of experience and logic who tries to help where I can - the same as the countless other volunteers who participate here to share their knowledge and experience.
Ok, this would be your processor (CPU = Central Processing Unit). From what I see in your printout, this might be a Dell computer? There might be a sticker on the outside of the computer that will show the manufacturer and model, for example Dell OptiPlex 3020, or perhaps on your sales receipt. With any luck it might also list the NIC and it’s MAC address, but lets not push our luck
If I were to make a premature, unfounded guess, it would be that it is an onboard Intel network card. In my limited experience, it can be a ‘hit or miss’ as to whether there is an open source driver for Intel equipment (Intel is not really open source friendly). In some cases, I’ve found it’s easier just to buy a network card that I know works with Linux or BSD.
As Henk said, don’t become frustrated. The answer is out there
Never mind, I see you’ve resolved the problem. Congratulations !
On 05/05/2015 06:16 AM, hcvv wrote:
>
> rwbehne1;2708401 Wrote:
>> Well, of course it rather vague! …
> No need to get frustrated.
>
> When people say “Linux is not seeing …” that is by definition a useless
> remark. As long as computers/operating systems are not human, one should
> not expect human actions from it.
>
For new people why don’t you just accept that “linux is not seeing…”
== “linux does not detect…”. That is how I interpreted rwbehne1’s
statement.
Things are not always just black and white!
Ken