I was away on business and came home to the big storm with no electric for 6 days. When I finally got online there were 168 updates including a kernel update. i knew the kernel update would ruin Nvidia but it got worse. For networking, I have only loopback. It no longer recognizes eth0. I tried putting on a wifi adapter but that also is not recognized. I dual boot with windows on a separate drive. That also is not recognized and does not appear in my grub menu. I am running 13.1 with updates current as of this morning. I am posting this from an old pc also running 13.1 but not updated for a few weeks. It uses the same router connected via wifi with the adapter I tried to use on the problem pc.
I tried using info in this forum but made no progress. I’ve used both ifup and Network Manager with no results. I have a disk of 13.1 Live that I downloaded soon after it was released. The Nviidia problem is small compared to this. Please give me some advice to get networking (and the windows drive) back.
Sorry for the delay. Power was out. Internet cable was snapped. Plumbing emergencies took precedence. 14 inches of new snow on the ground with more coming. Don’t know how long power will be on.
I have both new and old kernel. Each as default and desktop. Each of those with a failsafe option. None give me any network interface; neither the built-in eth card or plug-in wireless. Had to use old monitor for gui ( a separate nvidia problem).
During boot, I see an error message: FATAL: no ata_generic found. I tried both ifup and Network Manager. Neither sees any network interface but lo.
Rebooted again today and still no option to boot second drive with windows. Now using an old, very slow, pc to get to this forum.
Switched back to ifup and see ethernet controller not configured. Message says “Unable to configure network card because the kernel device (eth0, wlan0) is not present” Says firmware (especially for wlan) might be missing. But no wlan connected.
On 2014-02-13 18:46, Prexy wrote:
> During boot, I see an error message: FATAL: no ata_generic found. I
> tried both ifup and Network Manager. Neither sees any network interface
> but lo.
Check if any partition is full. Use “df -h” to find out.
Guessing that you have a separate /boot partition, it filled, and initrd
was updated incomplete.
fdisk -l shows an asterisk in the boot column for /dev/sda2 (a linux partition) and an asterisk in the boot column of /dev/sdb1 (the windows hd)
df -h shows the sda2 53% full with 8.9G available.
there is a devtempfs listed under sda2 with 1% used. There are 5 more tmpfs with 1% used on each. Each of the tmp has 1G available.
Finally, there is sda3 /home with 26% used.
Sorry I can’t cut & paste but here is the gist of it:
1: lo: <LOOPBACK,UP,LOWER_UP>…state unknown mode DEFAULT… then a bunch of zeros for link/loopback
Which OFFICIAL nvidia did you use? Nvidia website or opensuse?
When I tried this, it said I had neither /proc or /sys which, of course, I do have. I was careful about spacing etc in copying the commands so I don’t know what went wrong. Do I need a reinstall with the Live-CD?
Every tip I tried led me to a dead end. By going chroot, I lost the the interface that the Live-CD found. I ran the Live-CD to see if there was a “repair” option. Seeing none, I gave up and hit “Install.”
The system re-installed but STILL NO NETWORK!! At this point, the only help I was looking for was someone to open a window I could throw this pc out of. I looked at yast - network services and noticed more info on the network interfaces. It gave me a message to edit the controller and I simply changed from static ip to dhcp without much hope. However, that configured the controller to the basic controller used by the Live-CD - enp2s8
That worked to get me a network connection. It may not be the optimal module, but it worked. Configuring the controller did not work before the system re-install.
I thank everyone that tried to help me. I’m sorry that the take-away from this is do a re-install.
On 02/14/2014 12:16 PM, Prexy pecked at the keyboard and wrote:
> Every tip I tried led me to a dead end. By going chroot, I lost the the
> interface that the Live-CD found. I ran the Live-CD to see if there was
> a “repair” option. Seeing none, I gave up and hit “Install.”
>
> The system re-installed but STILL NO NETWORK!! At this point, the only
> help I was looking for was someone to open a window I could throw this
> pc out of. I looked at yast - network services and noticed more info on
> the network interfaces. It gave me a message to edit the controller and
> I simply changed from static ip to dhcp without much hope. However, that
> configured the controller to the basic controller used by the Live-CD -
> enp2s8
>
> That worked to get me a network connection. It may not be the optimal
> module, but it worked. Configuring the controller did not work before
> the system re-install.
>
> I thank everyone that tried to help me. I’m sorry that the take-away
> from this is do a re-install.
I’m sad to say that from my observation over the past few years that is
the way linux is going. Having to do a re-install simply because of an
interface problem is a sad state of affairs. Having to re-install
because of any minor issue is ludicrous.
I too have what I call a minor network issue in that I can’t get Network
Manager to display any wireless networks available in my area. One
update fixed it and another broke it. You would think that with over 20
years of linux experience I should have no trouble, but the fact is
there is so much changing under the hood that I can’t find the problem
to report/fix it. It most likely is a hardware/driver issue.
Glad you got your network up even if in a round-a-bout way.
>
> Prexy;2624124 Wrote:
>> For networking, I have only loopback. It no longer recognizes
>> eth0…
>> I tried using info in this forum but made no progress. I’ve used
both
>> ifup and Network Manager with no results. I have a disk of 13.1
Live
>> that I downloaded soon after it was released. The Nviidia problem
is
>> small compared to this. Please give me some advice to get
networking
>> (and the windows drive) back.
> Right from the start when i started using 13.1 i had no eth0. I only
> had enp2s0
> Due to this :- http://tinyurl.com/p562qf5
>
eth0 has been obsoleted in 13.1, the new name convention (enp2s0)is
used. There was a thread on that back befor 13.1 was released with a
list of all the new names, disk, eth. etc. I lost the link when I lost
my bookmarks.
When I installed 13.1 it came up with eth0 and the new name, and did
not work until I deleted the eth0 link in YaST → network setting. My
device is eno1. I use dhcp,
