Re: both nics down after F14 kernel update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Antonio Olivares <olivares14031@xxxxxxxxx>:

>

Kevin, Kevin and Antonio,

Thanks for your suggestions. I have booted in turn from each of my  
2.6.35 kernels, .6, .9 and .10 with no change. For unknown reasons I  
am now able to bring up the port with the cable connnection to my  
router, but can not get out from there. I am currently typing on my  
netbook, cabled into the same router; it's getting out fine. Also,  
Ubuntu gets out fine.

WTF??

I see no other messages in the tail of /var/log/messages other than  
the two telling me that one port is up and the other is not. Well, I  
knew that anyway. lspci is below.

---------- start lspci ----------------

00:00.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP55 LPC Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP55 SMBus (rev a3)
00:02.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2)
00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1)
00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3)
00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3)
00:05.2 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3)
00:06.0 PCI bridge: nVidia Corporation MCP55 PCI bridge (rev a2)
00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
00:0a.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
00:0b.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
00:0c.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
00:0d.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
00:0e.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
00:0f.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8  
[Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8  
[Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8  
[Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8  
[Athlon64/Opteron] Miscellaneous Control
01:06.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI]
05:00.0 PCI bridge: NEC Corporation uPD720400 PCI Express - PCI/PCI-X  
Bridge (rev 07)
05:00.1 PCI bridge: NEC Corporation uPD720400 PCI Express - PCI/PCI-X  
Bridge (rev 07)
08:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 4770 [RV740]
08:00.1 Audio device: ATI Technologies Inc RV710/730

---------------- end lspci ---------------

I don't know what modules ought to be loaded and consequently don't  
know whether they ARE loaded.

If any of this prompts any further ideas please accept my thanks in  
advance. It is now Christmas Eve and I am going to bugger off and play  
with friends and kids for a couple of days. Many thanks and best wishes!

Dave

>
> --- On Thu, 12/23/10, Dave Stevens <geek@xxxxxxxxxxxx> wrote:
>
>> From: Dave Stevens <geek@xxxxxxxxxxxx>
>> Subject: both nics down after F14 kernel update
>> To: "Community support for Fedora users" <users@xxxxxxxxxxxxxxxxxxxxxxx>
>> Date: Thursday, December 23, 2010, 6:20 PM
>> Hi,
>>
>> This afternoon I downloaded a kernel update for F14 and
>> rebooted. I 
>> found I had no network access and could not manually bring
>> up the 
>> interfaces using ifconfig. After considerable thrashing I
>> booted off a 
>> nearby Ubuntu 10.10 and the network access is ok. So I take
>> it that 
>> that conclusively establishes the issue as in software. A
>> Tyan S2932 
>> mobo with eth0 and eth1 onboard. Anyone else seeing this?
>> Ideas about 
>> debugging?
>>
>> Dave
>>
>>
>> --
>
> Did you try
> $ su -
> passwd:
> # dhclient eth0
> or
> # dhclient eth1
>
> and then check if connected with
> # ifconfig -a
>
> other option is to see if corresponding *.ko kernel modules are  
> loaded or not? lsmod and look for kernel module, if not loaded,  
> modprobe them as root user and see if that works?
>
> Regards,
>
> Antonio
>
>
>
> --
> users mailing list
> users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>



-- 
"It is no measure of health to be well adjusted to a profoundly sick society."
   Krishnamurti

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux