updates for 5.4 [Solved]

[timothyRlamora]

I downloaded all the updates today for sabayon linux 5.4. Now I can't connect to the internet either through wireless or dsl. So I have to wipe my harddrive and start all over again.

[throdon]

are you trolling. you got online somehow to post this why did you not search for related problems or ask a question not just give a statement. these are the quirks of sabayon I just installed onto a 1TB external and updated and now i cant even access anything but grub but i am going to boot up my live USB and do a little homework before I ask a question or state a statment with this tone.

[timothyRlamora]

Sorry about the tone I have a laptop with sabayon 3.4 mini on and that is how I got online . I tried reverting all my network drivers to the old ones but I don't know what the name of my network card or wirleless card. So I download every driver and still no internet. Same with my video card don't know what I have in my computer. Dob't know what sound card how much memeory I have or the size of my harddrives. don't know how to fnd this info.

[Fitzcarraldo]

You can find out which wired network and wireless network cards your machine has got by using the lspci command as root user in a Konsole/Terminal window. For example, on my main laptop:

Code: Select all

# lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
01:00.0 VGA compatible controller: ATI Technologies Inc Redwood [Radeon HD 5600 Series]                                                                                                                                                            
01:00.1 Audio device: ATI Technologies Inc Redwood HDMI Audio [Radeon HD 5600 Series]                                                                                                                                                              
03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
04:00.0 Ethernet controller: Atheros Communications AR8131 Gigabit Ethernet (rev c0)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)

From the above I see that my laptop has:

03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
04:00.0 Ethernet controller: Atheros Communications AR8131 Gigabit Ethernet (rev c0)

What does yours have?

[timothyRlamora]

I have a ralink wirless card and Linksys network card/

[huwie]

I'm having exactly the same problem as the OP. I originally posted in a less appropriate thread; I'll paste what I'd put there:

I'm not sure whether my problem is related; it certainly occurred only after a slew of updates. I installed Sabayon for the first time today. At first eth0 was working perfectly, but after all the updates it just died.

According to ifconfig, eth0 is up and running, but it simply refuses to connect to my router. I've tried clicking auto eth0 in the network manager panel applet and for about 30 seconds or so it says "setting network address" but then just fails.

Any advice greatly appreciated! Please note that I'm not an expert - I'm not afraid of bash but I don't know much about how to use it either.

I'm quickly trying to gather info to help you all help me. I'll edit this post as I gather info.

Edit: Gah! Apparently the solution is to frantically click auto eth0 in the network manager applet a few times in between reboots. Tch. Computers, eh? What goes on inside those enigmatic metal cases?

So that's two threads I've managed to make a fool of myself in. I'll try to make less of a twit of myself from now on!

[huwie]

I spoke too soon. As I dual boot the PC is rebooted a lot, and it's become apparent that a working connection is actually the exception to the rule. I'm not sure how to troubleshoot this, but I did spot the following in /var/log/messages:

Code: Select all

Jan 17 15:36:14 sabayon dhclient: Listening on LPF/eth0/00:19:d1:71:76:b0
Jan 17 15:36:14 sabayon dhclient: Sending on   LPF/eth0/00:19:d1:71:76:b0
Jan 17 15:36:15 sabayon dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 17 15:36:22 sabayon dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 17 15:36:34 sabayon dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jan 17 15:36:39 sabayon dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Jan 17 15:36:48 sabayon dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Jan 17 15:36:58 sabayon dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Jan 17 15:36:59 sabayon NetworkManager[6569]: <warn> (eth0): DHCPv4 request timed out.
Jan 17 15:36:59 sabayon NetworkManager[6569]: <info> (eth0): canceled DHCP transaction, DHCP client pid 7633
Jan 17 15:36:59 sabayon NetworkManager[6569]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) scheduled...
Jan 17 15:36:59 sabayon NetworkManager[6569]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) started...
Jan 17 15:36:59 sabayon NetworkManager[6569]: <info> (eth0): device state change: 7 -> 9 (reason 5)
Jan 17 15:36:59 sabayon NetworkManager[6569]: <info> Marking connection 'System (eth0)' invalid.
Jan 17 15:36:59 sabayon NetworkManager[6569]: <warn> Activation (eth0) failed.
Jan 17 15:36:59 sabayon NetworkManager[6569]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) complete.

So it seems, to my regrettably untrained eye, that for whatever reason NetworkManager is failing to get an address from the router...? What info can I provide to help someone to help me?

By the way, Windows 7 (the other OS I work with) has no problem establishing an ethernet connection, and neither did Linux Mint which was the distro I used before Sabayon.

[Fitzcarraldo]

I notice that users of several other distributions have been reporting similar problems recently. I wonder if it's the upgrade to NetworkManager. I see that the latest version (0.8.2-r2) in the Entropy repository was built from a Sabayon overlay ebuild version of the new version 0.8.2-r2 in the Portage tree. I suggest you file a bug report in the SL Bugzilla citing the symptoms and posting all the console output you've posted here.

If you're up for it, you could try downgrading NetworkManager in order to see whether the problem is indeed with NetworkManager. I'm using version 0.8.1-r6 and it's rock-solid, so you could try merging (installing) that version via Portage as it's not in the Entropy repository any more:

Code: Select all

emerge --sync
layman -s sabayon
emerge -1v =networkmanager-0.8.1-r6

[huwie]

Fitz, thank you very much for your helpful post. As it happens, my connection is currently working; next time it fails I'll do as you advise. I previously had my router set to assign a static IP to my PC; now it's being assigned dynamically and appears to be working (although the same IP is being grabbed anyway, heh).

Yeah, from my research it does appear there's some kind of bug in NetworkManager at the moment, although from what I've seen it hasn't really been confirmed yet. Anything I can do to help in that regard, I assuredly will.

Is this the kind of thing I can expect now that I'm using a bleeding-edge distro?

[Fitzcarraldo]

Is this the kind of thing I can expect now that I'm using a bleeding-edge distro?

Yup, although it's nowhere near as bad as it sounds, as bugs often get fixed quickly by the upstream developers, or by the SL team if it's within their realm, or there is a work-around or alternative package which can be used until the other one stabilises again (my recent problem with Wicd in SL 5.4 E17 is a good example: I switched to ConnMan).

If things broke all the time then I wouldn't still be using this after nearly four years (it used to break a lot more two+ years back and I used to have some horrible battles, especially with comms, but Linux really moves fast in most cases).

If you want 'safe' then you'd need to use the stable branch of a distribution, but then many of the packages would be older versions and not have the latest additions. Personally I prefer a little bit of risk in order to be able to get the latest version of a package, even if it's not fully debugged. I can always re-install an earlier version if necessary (a choice which is not always open to Entropy users as the Entropy repository packages march inexorably forward, although the developers tend to fix breakages very quickly so the impact is low in practice for the majority).