On Saturday 05 June 2010 17:15:10 Martin (KDE) wrote: > Am Samstag, 5. Juni 2010 schrieb Anne Wilson: > > On Saturday 05 June 2010 08:15:26 Anne Wilson wrote: > > >CIFS mount - on the occasion when all 3 NFS mounts were listed I > > >was able > > > > > > to type in the user password. On the times when less that 3 > > > were listed no input was recognised. Coincidence? I don't > > > know. > > > > That part clearly is coincidence, since I've just seen all three > > listed and it still wouldn't accept keyboard input. > > > > It seems I have a solution - but I don't quite understand it, so > > perhaps you could explain. I commented out the fstab cifs line, > > thinking I could add it again later when I've sorted things out. > > There was a long delay in booting, while the nfs mounts were said > > ot have failed. Then I saw 'Mounting other filesystems' succeed. > > When the desktop is fully loaded, dolphin tells me that all the > > nfs mounts AND the samba mount are working! > > I had some similar problems (the long delay on boot). This was caused > by the missing network service but using the networkManager stuff. But > I user a ldap base user configuration and at some stage while the > network is not up other processes tries to fetch user information from > the ldap server. > I think something like that is happening, but the network service appears to be listed several items before the nfs mounts. However, messages has these lines Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> found WiFi radio killswitch rfkill1 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/ieee80211/phy0/rfkill1) (driver <unknown>) Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> WiFi disabled by radio killswitch; disabled by state file Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> WWAN enabled by radio killswitch; enabled by state file Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> WiMAX enabled by radio killswitch; enabled by state file Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> Networking is enabled by state file Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (eth0): carrier is OFF Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2) Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (eth0): now managed Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (eth0): device state change: 1 -> 2 (reason 2) Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (eth0): bringing up device. Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (eth0): preparing device. Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (eth0): deactivating device (reason: 2). Jun 5 07:25:11 tecra-a11 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01). Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlagn' ifindex: 3) Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (wlan0): now managed Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (wlan0): device state change: 1 -> 2 (reason 2) Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (wlan0): bringing up device. Jun 5 07:25:11 tecra-a11 NetworkManager[1277]: <info> (wlan0): deactivating device (reason: 2). being lines 6959-6979 and Jun 5 07:25:13 tecra-a11 kernel: Slow work thread pool: Starting up Jun 5 07:25:13 tecra-a11 kernel: Slow work thread pool: Ready Jun 5 07:25:13 tecra-a11 kernel: FS-Cache: Loaded Jun 5 07:25:13 tecra-a11 kernel: FS-Cache: Netfs 'nfs' registered for caching Jun 5 07:25:13 tecra-a11 kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None Jun 5 07:25:13 tecra-a11 kernel: 0000:00:19.0: eth0: 10/100 speed: disabling TSO Jun 5 07:25:13 tecra-a11 NetworkManager[1277]: <info> (eth0): carrier now ON (device state 2) Jun 5 07:25:13 tecra-a11 NetworkManager[1277]: <info> (eth0): device state change: 2 -> 3 (reason 40) Jun 5 07:25:13 tecra-a11 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jun 5 07:25:13 tecra-a11 NetworkManager[1277]: <info> Activation (eth0) starting connection 'System eth0' Jun 5 07:25:13 tecra-a11 kernel: Slow work thread pool: Starting up Jun 5 07:25:13 tecra-a11 kernel: Slow work thread pool: Ready Jun 5 07:25:13 tecra-a11 kernel: FS-Cache: Loaded Jun 5 07:25:13 tecra-a11 kernel: FS-Cache: Netfs 'nfs' registered for caching Jun 5 07:25:13 tecra-a11 kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None Jun 5 07:25:13 tecra-a11 kernel: 0000:00:19.0: eth0: 10/100 speed: disabling TSO Jun 5 07:25:13 tecra-a11 NetworkManager[1277]: <info> (eth0): carrier now ON (device state 2) Jun 5 07:25:13 tecra-a11 NetworkManager[1277]: <info> (eth0): device state change: 2 -> 3 (reason 40) Jun 5 07:25:13 tecra-a11 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jun 5 07:25:13 tecra-a11 NetworkManager[1277]: <info> Activation (eth0) starting connection 'System eth0' being lines 7002-7026 then Jun 5 07:25:14 tecra-a11 NetworkManager[1277]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. Jun 5 07:25:15 tecra-a11 avahi-daemon[1290]: Registering new address record for fe80::223:18ff:fe50:285a on eth0.*. Jun 5 07:26:13 tecra-a11 kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE Jun 5 07:26:13 tecra-a11 kernel: CIFS VFS: Send error in SessSetup = -13 Jun 5 07:26:13 tecra-a11 kernel: CIFS VFS: cifs_mount failed w/return code = -13 Jun 5 07:34:36 tecra-a11 init: rc main process (1142) killed by TERM signal being lines 7056 - 7061. As you see, things seem to be in the correct order. > Back to your problem: what does your fstab look like the relevant part is 192.168.0.40:/home /mnt/borg2_home nfs4 rsize=8192,wsize=8192,timeo=14,intr 192.168.0.40:/Data1 /mnt/borg2_Data1 nfs4 rsize=8192,wsize=8192,timeo=14,intr 192.168.0.40:/Data2 /mnt/borg2_Data2 nfs4 rsize=8192,wsize=8192,timeo=14,intr 192.168.0.40:/Data3 /mnt/borg2_Data3 nfs4 rsize=8192,wsize=8192,timeo=14,intr # 192.168.0.40:/Data1 /mnt/smbData1 cifs user=anne,gid=users,forcegid,rw > and what does > "chkconfig --list" gives you at the console? Does > chkconfig --list | grep network network 0:off 1:off 2:off 3:off 4:off 5:off 6:off > chkconfig network on > I haven't tried that, since the network is controlled by networkManager. The laptop does sometimes have to be used on other wifi networks. > change anything (if you use wired ethernet connections)? In which > order are the services started (ls in /etc/init.d/rc5.d)? Not sure this is what you want, but I think it is: S23NetworkManager S24avahi-daemon S24nfslock S24rpcgssd S24rpcidmapd S25cups S25netfs Anne -- KDE Community Working Group New to KDE Software? - get help from http://userbase.kde.org -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.fedoraproject.org/pipermail/kde/attachments/20100605/abd1bad4/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://lists.fedoraproject.org/pipermail/kde/attachments/20100605/abd1bad4/attachment-0001.bin
