Why would cat /sys/class/net/eth0/carrier produce cat: /sys/class/net/eth0/carrier: Invalid Argument using the 'file' command produces "...ERROR: cannot read..." The network cable is connected 11.3 on the same box with the same cable works just fine. hwinfo --network produces the following out put: 24: None 00.0: 10700 Loopback [Created at net.124] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 25: None 00.0: 10701 Ethernet [Created at net.124] Unique ID: usDW.ndpeucax6V1 Parent ID: rBUF.FXdWInzfkAA SysFS ID: /class/net/eth0 SysFS Device Link: /devices/pci0000:00/0000:00:1c.1/0000:02:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "r8169" Driver Modules: "r8169" Device File: eth0 HW Address: 00:22:4d:4c:03:40 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #17 (Ethernet controller) The lspci -vv output is attached. Other files in the directory, such as type and uevent are accessible and can be read???? Help is appreciated. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147