List, a testing difficulty.
Installed F14 RC3 XFCE from the CD-sized image released by Kevin on Sept 30. Netbook is Samsung NB30, and dual boots F14 RC3 or XPhome. WiFi is built-in; there is no physical on/off button for it, but a softkey combination, 'Function key' and F9, switch WiFi off and on in Windows XPhome.
Under F14, Network manager does not seem to recognise any WiFi access points and, after adding some, still does not see them to connect to. The 'network icon' in the panel has a 'red cross' against it.
I have also tried F13 XFCE spin (live CD) and F13 does not find the wireless system, either.
If I connect a wired Ethernet cable, the network connects using the wired system. I wonder if the WiFi module is not switching on, or being switched on?
On a different netbook, Acer AspireOne (on which F13 XFCE is installed), while F13 does find the inbuilt wireless system and lights a WiFi LED, the F14 RC3 XFCE liveCD does not find the wireless, and the WiFi LED on the AspireOne does not light.
I'll do some more checks of dmesg to see how far F14 gets in finding the WiFi system. Are there other files I should check?
regards, Ron
Ron Leach wrote:
I'll do some more checks of dmesg to see how far F14 gets in finding the WiFi system. Are there other files I should check?
Here is a dmesg output relating to network:
NET: Registered protocol family 16
=================================================== [ INFO: suspicious rcu_dereference_check() usage. ]
include/linux/cgroup.h:542 invoked rcu_dereference_check() without protection!
other info that might help us debug this:
rcu_scheduler_active = 1, debug_locks = 0 1 lock held by swapper/1: #0: (net_mutex){+.+.+.}, at: [<c073ad19>] register_pernet_subsys+0x17/0x34
stack backtrace: Pid: 1, comm: swapper Not tainted 2.6.35.4-28.fc14.i686 #1 Call Trace: [<c07d07e0>] ? printk+0x25/0x2d [<c0460b75>] lockdep_rcu_dereference+0x7d/0x86 [<c073387a>] sock_update_classid+0x6c/0x8e [<c07338fb>] sk_alloc+0x5f/0x6a [<c0756c1d>] __netlink_create+0x2a/0x90 [<c07584c8>] netlink_kernel_create+0x5f/0x14f [<c07477d0>] rtnetlink_net_init+0x23/0x3b [<c0748b86>] ? rtnetlink_rcv+0x0/0x27 [<c073ab0c>] ops_init+0xda/0xe9 [<c073ac4c>] register_pernet_operations+0x84/0xee [<c073ad25>] register_pernet_subsys+0x23/0x34 [<c0a98e29>] rtnetlink_init+0x42/0xe0 [<c0a9948f>] netlink_proto_init+0xee/0x103 [<c0a993a1>] ? netlink_proto_init+0x0/0x103 [<c040126a>] do_one_initcall+0x62/0x170 [<c0a639c2>] kernel_init+0x1b9/0x23a [<c0a63809>] ? kernel_init+0x0/0x23a [<c0403982>] kernel_thread_helper+0x6/0x10
<snip> NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default <snip> nf_conntrack version 0.5.0 (15708 buckets, 62832 max) CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or sysctl net.netfilter.nf_conntrack_acct=1 to enable it. ip_tables: (C) 2000-2006 Netfilter Core Team TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17
It just doesn't seem to see anything to do with WiFi.
I should add that I've disabled SELinux using SELINUX=DISABLED in its config file. (It was the same before, though.)
regards, Ron
Ron Leach wrote:
Here is a dmesg output relating to network:
<snip>
It just doesn't seem to see anything to do with WiFi.
Here are the Network Manager messages, from /var/log/messages. I think these will wrap round in email format (is there a more useful way to publish this for the list?):
Oct 3 09:34:12 localhost NetworkManager[1089]: <info> NetworkManager (version 0.8.1-6.git20100831.fc14) is starting... Oct 3 09:34:12 localhost NetworkManager[1089]: <info> Read config file /etc/NetworkManager/NetworkManager.conf Oct 3 09:34:13 localhost NetworkManager[1089]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn Oct 3 09:34:13 localhost NetworkManager[1089]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp Oct 3 09:34:13 localhost NetworkManager[1089]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc Oct 3 09:34:13 localhost NetworkManager[1089]: <info> trying to start the modem manager...
Oct 3 09:34:13 localhost modem-manager: ModemManager (version 0.4-4.git20100720.fc14) starting... Oct 3 09:34:13 localhost modem-manager: Loaded plugin Option High-Speed Oct 3 09:34:13 localhost modem-manager: Loaded plugin Ericsson MBM Oct 3 09:34:13 localhost modem-manager: Loaded plugin Novatel Oct 3 09:34:13 localhost modem-manager: Loaded plugin Sierra Oct 3 09:34:13 localhost modem-manager: Loaded plugin ZTE Oct 3 09:34:13 localhost modem-manager: Loaded plugin Nokia Oct 3 09:34:13 localhost modem-manager: Loaded plugin Option Oct 3 09:34:13 localhost modem-manager: Loaded plugin SimTech Oct 3 09:34:13 localhost modem-manager: Loaded plugin Huawei Oct 3 09:34:13 localhost modem-manager: Loaded plugin Longcheer Oct 3 09:34:13 localhost modem-manager: Loaded plugin AnyData Oct 3 09:34:13 localhost modem-manager: Loaded plugin MotoC Oct 3 09:34:13 localhost modem-manager: Loaded plugin Generic Oct 3 09:34:13 localhost modem-manager: Loaded plugin Gobi
Oct 3 09:34:13 localhost NetworkManager[1089]: <info> monitoring kernel firmware directory '/lib/firmware'. Oct 3 09:34:13 localhost NetworkManager[1089]: ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1 Oct 3 09:34:13 localhost NetworkManager[1089]: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Oct 3 09:34:13 localhost NetworkManager[1089]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-wifilinkone ... Oct 3 09:34:13 localhost NetworkManager[1089]: ifcfg-rh: read connection 'wifilinkone' Oct 3 09:34:13 localhost NetworkManager[1089]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-wifilinktwo ... Oct 3 09:34:13 localhost NetworkManager[1089]: ifcfg-rh: read connection 'wifilinktwo' Oct 3 09:34:13 localhost NetworkManager[1089]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Oct 3 09:34:13 localhost NetworkManager[1089]: <info> WiFi enabled by radio killswitch; enabled by state file Oct 3 09:34:13 localhost NetworkManager[1089]: <info> WWAN enabled by radio killswitch; enabled by state file Oct 3 09:34:13 localhost NetworkManager[1089]: <info> WiMAX enabled by radio killswitch; enabled by state file Oct 3 09:34:13 localhost NetworkManager[1089]: <info> Networking is enabled by state file Oct 3 09:34:13 localhost NetworkManager[1089]: <info> (eth0): carrier is OFF Oct 3 09:34:13 localhost NetworkManager[1089]: <info> (eth0): new Ethernet device (driver: 'sky2' ifindex: 2) Oct 3 09:34:13 localhost NetworkManager[1089]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Oct 3 09:34:13 localhost NetworkManager[1089]: <info> (eth0): now managed Oct 3 09:34:13 localhost NetworkManager[1089]: <info> (eth0): device state change: 1 -> 2 (reason 2) Oct 3 09:34:13 localhost NetworkManager[1089]: <info> (eth0): bringing up device. Oct 3 09:34:13 localhost kernel: sky2 0000:09:00.0: eth0: enabling interface Oct 3 09:34:13 localhost NetworkManager[1089]: <info> (eth0): preparing device. Oct 3 09:34:13 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Oct 3 09:34:13 localhost NetworkManager[1089]: <info> (eth0): deactivating device (reason: 2). Oct 3 09:34:13 localhost NetworkManager[1089]: <info> Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0/net/eth0 Oct 3 09:34:13 localhost NetworkManager[1089]: <info> modem-manager is now available Oct 3 09:34:13 localhost NetworkManager[1089]: <warn> bluez error getting default adapter: Launch helper exited with unknown return code 1 Oct 3 09:34:13 localhost NetworkManager[1089]: <info> Trying to start the supplicant...
Oct 3 09:34:21 localhost NetworkManager[1089]: <error> [1286094861.699690] [nm-manager.c:1331] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Oct 3 09:34:21 localhost NetworkManager[1089]: <error> [1286094861.702496] [nm-manager.c:1331] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Oct 3 09:34:21 localhost NetworkManager[1089]: <error> [1286094861.705275] [nm-manager.c:1331] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Oct 3 09:34:47 localhost NetworkManager[1089]: <error> [1286094887.600535] [nm-manager.c:1331] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Oct 3 09:34:47 localhost NetworkManager[1089]: <error> [1286094887.622916] [nm-manager.c:1331] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Oct 3 09:34:47 localhost NetworkManager[1089]: <error> [1286094887.634009] [nm-manager.c:1331] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Oct 3 09:34:47 localhost NetworkManager[1089]: <error> [1286094887.636587] [nm-manager.c:1331] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Oct 3 09:34:47 localhost NetworkManager[1089]: <error> [1286094887.638739] [nm-manager.c:1331] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
The wired LAN cable was not connected (on purpose), and I think that's why Eth0 didn't come up - which is not a problem because it does when I insert the cable.
It does seem to see some WiFi bits - even detecting that it needs a state-based start. The two WiFi nets are the two access points that the machine could reach, and I entered these in the connections list dialog. But the machine doesn't react to them.
There are no further messages for 45 mins or so (when I inserted a USB stick) so there is no other network activity. The WiFi AP was on, and serving other clients.
regards, Ron
On Sun, 03 Oct 2010 10:16:20 +0100 Ron Leach ronleach@tesco.net wrote:
List, a testing difficulty.
Installed F14 RC3 XFCE from the CD-sized image released by Kevin on Sept 30. Netbook is Samsung NB30, and dual boots F14 RC3 or XPhome. WiFi is built-in; there is no physical on/off button for it, but a softkey combination, 'Function key' and F9, switch WiFi off and on in Windows XPhome.
Under F14, Network manager does not seem to recognise any WiFi access points and, after adding some, still does not see them to connect to. The 'network icon' in the panel has a 'red cross' against it.
I have also tried F13 XFCE spin (live CD) and F13 does not find the wireless system, either.
If I connect a wired Ethernet cable, the network connects using the wired system. I wonder if the WiFi module is not switching on, or being switched on?
What wireless card is it?
lspci and/or lsusb should tell you.
On a different netbook, Acer AspireOne (on which F13 XFCE is installed), while F13 does find the inbuilt wireless system and lights a WiFi LED, the F14 RC3 XFCE liveCD does not find the wireless, and the WiFi LED on the AspireOne does not light.
I'll do some more checks of dmesg to see how far F14 gets in finding the WiFi system. Are there other files I should check?
I would first look at lspci/lsusb to figure out what card it is, then go from there. dmesg might also be informative.
kevin
Kevin Fenzi wrote:
On Sun, 03 Oct 2010 10:16:20 +0100 Ron Leach ronleach@tesco.net wrote:
Under F14, Network manager does not seem to recognise any WiFi access points and, after adding some, still does not see them to connect to. The 'network icon' in the panel has a 'red cross' against it.
What wireless card is it?
lspci and/or lsusb should tell you.
Here an extract from lspci -v :
05:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192E Wireless LAN Controller (rev 01) Subsystem: Askey Computer Corp. Device 7160 Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at 2000 [size=256] Memory at f0100000 (32-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number <stripped>
09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller Subsystem: Samsung Electronics Co Ltd Device c073 Flags: bus master, fast devsel, latency 0, IRQ 46 Memory at f0200000 (64-bit, non-prefetchable) [size=16K] I/O ports at 3000 [size=256] Capabilities: [48] Power Management version 3 Capabilities: [5c] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [130] Device Serial Number <stripped> Kernel driver in use: sky2 Kernel modules: sky2
On a different netbook, Acer AspireOne (on which F13 XFCE is installed), while F13 does find the inbuilt wireless system and lights a WiFi LED, the F14 RC3 XFCE liveCD does not find the wireless, and the WiFi LED on the AspireOne does not light.
I'll do some more checks of dmesg to see how far F14 gets in finding the WiFi system. Are there other files I should check?
I would first look at lspci/lsusb to figure out what card it is, then go from there. dmesg might also be informative.
This post is saying that, on another netbook (for comparison), F13 finds the wireless (on an Acer AspireOne netbook), but F14 RC3 does not. So it seems that there's something different between F13 and F14 in respect of wireless support.
I'll post back with details of this other netbook, Acer AspireOne, too.
thanks, Ron
Nathan Thomas wrote:
I also have a Samsung netbook with the same wireless card (RTL8192E). The bad news is that there isn't an in-kernel driver for it yet, but the good news is that Realtek have released an open-source driver out into the wild that works well with my F13 install.
<snip> I had one or two issues getting the kernel module to load on boot in my x86_64 installation, if this happens to you please feel free to email me and I'll let you know what I did to fix it.
Nathan, that's very helpful, thanks; explains why F13 wasn't working, either.
I'll track down a driver and see how far I get,
regards, Ron
Nathan Thomas wrote:
The bad news is that there isn't an in-kernel driver for it yet, but the good news is that Realtek have released an open-source driver out into the wild that works well with my F13 install.
I had one or two issues getting the kernel module to load on boot in my x86_64 installation, if this happens to you please feel free to email me and I'll let you know what I did to fix it.
Nathan, just to say I tracked down a driver and installed it. I didn't find any problems on booting. The README with the driver was pretty good, but I had to also load the kernel source, and the gcc compilers, before I could create the driver - I hit these errors because, on a fairly light XFCE clean install, neither of these were already there (and I hadn't realised that).
On the laptop list I've posted details of what I did, to help others because I think this chipset is common, and there are a lot of newer folk trying these netbooks who may otherwise find installing a driver from source too daunting (it isn't really).
Thanks for your help and for the advice that there was a driver available.
regards, Ron
On 24/10/10 20:13, Ron Leach wrote:
Nathan Thomas wrote:
The bad news is that there isn't an in-kernel driver for it yet, but the good news is that Realtek have released an open-source driver out into the wild that works well with my F13 install.
I had one or two issues getting the kernel module to load on boot in my x86_64 installation, if this happens to you please feel free to email me and I'll let you know what I did to fix it.
Nathan, just to say I tracked down a driver and installed it. I didn't find any problems on booting. The README with the driver was pretty good, but I had to also load the kernel source, and the gcc compilers, before I could create the driver - I hit these errors because, on a fairly light XFCE clean install, neither of these were already there (and I hadn't realised that).
Oops forgot to mention that bit, sorry!
On the laptop list I've posted details of what I did, to help others because I think this chipset is common, and there are a lot of newer folk trying these netbooks who may otherwise find installing a driver from source too daunting (it isn't really).
Thanks for your help and for the advice that there was a driver available.
Glad I was able to help!
Best wishes Nathan
-
Kevin Fenzi -
Nathan Thomas -
Ron Leach