Was happy with initial install of F17, 64 bit, Gnome 3.4. Worked ok
outta the box.
However, after adding some software and updating to 3.4 kernel, I have
no [wired 1gb] network access.
Also, I don't have the icon/applet to turn it on.
--
Please advise.
Thanks
nat
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Tue, 2012-06-19 at 11:11 -0400, Natalie Gross wrote:
> Was happy with initial install of F17, 64 bit, Gnome 3.4. Worked ok
> outta the box.
> However, after adding some software and updating to 3.4 kernel, I have
> no [wired 1gb] network access.
> Also, I don't have the icon/applet to turn it on.


Please check /var/log/messages for any errors, as root:.

# egrep -i 'error' /var/log/messages

You can also try restarting the networkmanager service, as root:

# systemctl restart NetworkManager.service
--
Thanks,
Warm regards,
Ankur: "FranciscoD"

Please only print if necessary.

Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG

http://fedoraproject.org/wiki/User:Ankursinha
http://dodoincfedora.wordpress.com/
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Wed, Jun 20, 2012 at 1:34 AM, Ankur Sinha <sanjay.ankur@gmail.com> wrote:
> On Tue, 2012-06-19 at 11:11 -0400, Natalie Gross wrote:
>> Was happy with initial install of F17, 64 bit, Gnome 3.4. Worked ok
>> outta the box.
>> However, after adding some software and updating to 3.4 kernel, I have
>> no [wired 1gb] network access.
>> Also, I don't have the icon/applet to turn it on.
>
>
> Please check /var/log/messages for any errors, as root:.
>
> # egrep -i 'error' /var/log/messages
>
> You can also try restarting the networkmanager service, as root:
>
> # systemctl restart NetworkManager.service
> --
> Thanks,
> Warm regards,
> Ankur: "FranciscoD"
>
Many errors regarding NetworkManager: (Please note: This machine does
NOT have wifi. It is a 1gb wired interface.)
---------------------------------------
Jun 18 23:06:25 Phenom9600 NetworkManager[783]: <warn> error
requesting auth for
org.freedesktop.NetworkManager.enable-disable-wifi: (0)
GDBus.Errorrg.freedesktop.PolicyKit1.Error.Faile d: Action
org.freedesktop.NetworkManager.enable-disable-wifi is not registered
Jun 18 23:06:25 Phenom9600 NetworkManager[783]: <warn> error
requesting auth for
org.freedesktop.NetworkManager.enable-disable-wwan: (0)
GDBus.Errorrg.freedesktop.PolicyKit1.Error.Faile d: Action
org.freedesktop.NetworkManager.enable-disable-wwan is not registered
Jun 18 23:06:25 Phenom9600 NetworkManager[783]: <warn> error
requesting auth for
org.freedesktop.NetworkManager.enable-disable-wimax: (0)
GDBus.Errorrg.freedesktop.PolicyKit1.Error.Faile d: Action
org.freedesktop.NetworkManager.enable-disable-wimax is not registered
Jun 18 23:06:25 Phenom9600 NetworkManager[783]: <warn> error
requesting auth for org.freedesktop.NetworkManager.network-control:
(0) GDBus.Errorrg.freedesktop.PolicyKit1.Error.Faile d: Action
org.freedesktop.NetworkManager.network-control is not registered
Jun 18 23:06:25 Phenom9600 NetworkManager[783]: <warn> error
requesting auth for
org.freedesktop.NetworkManager.wifi.share.protecte d: (0)
GDBus.Errorrg.freedesktop.PolicyKit1.Error.Faile d: Action
org.freedesktop.NetworkManager.wifi.share.protecte d is not registered
Jun 18 23:06:25 Phenom9600 NetworkManager[783]: <warn> error
requesting auth for org.freedesktop.NetworkManager.wifi.share.open:
(0) GDBus.Errorrg.freedesktop.PolicyKit1.Error.Faile d: Action
org.freedesktop.NetworkManager.wifi.share.open is not registered
Jun 18 23:06:25 Phenom9600 NetworkManager[783]: <warn> error
requesting auth for
org.freedesktop.NetworkManager.settings.modify.sys tem: (0)
GDBus.Errorrg.freedesktop.PolicyKit1.Error.Faile d: Action
org.freedesktop.NetworkManager.settings.modify.sys tem is not
registered
Jun 18 23:06:25 Phenom9600 NetworkManager[783]: <warn> error
requesting auth for
org.freedesktop.NetworkManager.settings.modify.own : (0)
GDBus.Errorrg.freedesktop.PolicyKit1.Error.Faile d: Action
org.freedesktop.NetworkManager.settings.modify.own is not registered
Jun 18 23:06:25 Phenom9600 NetworkManager[783]: <warn> error
requesting auth for
org.freedesktop.NetworkManager.settings.modify.hos tname: (0)
GDBus.Errorrg.freedesktop.PolicyKit1.Error.Faile d: Action
org.freedesktop.NetworkManager.settings.modify.hos tname is not
registered
....
Jun 20 06:14:30 Phenom9600 network[1767]: Bringing up interface p6p1:
ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device p6p1 does
not seem to be present, delaying initialization.
--------------------------------------

Also, status network.service gives me this:
-------------------------------------------------------------
network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: failed (Result: exit-code) since Wed, 20 Jun 2012 09:09:09
-0400; 1min 5s ago
Process: 1793 ExecStart=/etc/rc.d/init.d/network start (code=exited,
status=1/FAILURE)
CGroup: name=systemd:/system/network.service
� 1980 /sbin/dhclient -H Phenom9600 -1 -q -lf /var/lib/dh...

Jun 20 09:09:06 Phenom9600 network[1793]: Bringing up loopback interface: [...]
Jun 20 09:09:06 Phenom9600 network[1793]: Bringing up interface em1:
Jun 20 09:09:06 Phenom9600 dhclient[1913]: DHCPREQUEST on em1 to 255.255.255...)
Jun 20 09:09:06 Phenom9600 dhclient[1913]: DHCPACK from 192.168.1.1 (xid=0x7...)
Jun 20 09:09:08 Phenom9600 dhclient[1913]: bound to 192.168.1.13 -- renewal ....
Jun 20 09:09:08 Phenom9600 network[1793]: Determining IP information for em1....
Jun 20 09:09:09 Phenom9600 network[1793]: [ OK ]
Jun 20 09:09:09 Phenom9600 network[1793]: Bringing up interface p6p1: ERROR....
Jun 20 09:09:09 Phenom9600 network[1793]: [FAILED]
-------------------------------------------------------------

Thank you.
nat
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Wed, 2012-06-20 at 09:41 -0400, Natalie Gross wrote:

> Jun 20 09:09:06 Phenom9600 network[1793]: Bringing up loopback interface: [...]
> Jun 20 09:09:06 Phenom9600 network[1793]: Bringing up interface em1:
> Jun 20 09:09:06 Phenom9600 dhclient[1913]: DHCPREQUEST on em1 to 255.255.255...)
> Jun 20 09:09:06 Phenom9600 dhclient[1913]: DHCPACK from 192.168.1.1 (xid=0x7...)
> Jun 20 09:09:08 Phenom9600 dhclient[1913]: bound to 192.168.1.13 -- renewal ....
> Jun 20 09:09:08 Phenom9600 network[1793]: Determining IP information for em1....
> Jun 20 09:09:09 Phenom9600 network[1793]: [ OK ]
> Jun 20 09:09:09 Phenom9600 network[1793]: Bringing up interface p6p1: ERROR....
> Jun 20 09:09:09 Phenom9600 network[1793]: [FAILED]

This looks like you have a /etc/sysconfig/network-scripts/ifcfg-p6p1
script but your Ethernet device is actually em1. Looks like em1 is
getting set up OK. Try moving aside the ifcfg-p6p1 script and see if
that makes the failure go away, e.g.

# cd /etc/sysconfig/network-scripts
# mv ifcfg-p6p1 sav.ifconfig-p6p1

(that way you can bring it back later if you have to)

--Greg


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Wed, Jun 20, 2012 at 12:35 PM, Greg Woods <woods@ucar.edu> wrote:
> On Wed, 2012-06-20 at 09:41 -0400, Natalie Gross wrote:
>
>> Jun 20 09:09:06 Phenom9600 network[1793]: Bringing up loopback interface: *[...]
>> Jun 20 09:09:06 Phenom9600 network[1793]: Bringing up interface em1:
>> Jun 20 09:09:06 Phenom9600 dhclient[1913]: DHCPREQUEST on em1 to 255.255.255...)
>> Jun 20 09:09:06 Phenom9600 dhclient[1913]: DHCPACK from 192.168.1.1 (xid=0x7...)
>> Jun 20 09:09:08 Phenom9600 dhclient[1913]: bound to 192.168.1.13 -- renewal ....
>> Jun 20 09:09:08 Phenom9600 network[1793]: Determining IP information for em1....
>> Jun 20 09:09:09 Phenom9600 network[1793]: [ *OK *]
>> Jun 20 09:09:09 Phenom9600 network[1793]: Bringing up interface p6p1: *ERROR....
>> Jun 20 09:09:09 Phenom9600 network[1793]: [FAILED]
>
> This looks like you have a /etc/sysconfig/network-scripts/ifcfg-p6p1
> script but your Ethernet device is actually em1. Looks like em1 is
> getting set up OK. Try moving aside the ifcfg-p6p1 script and see if
> that makes the failure go away, e.g.
>
> # cd /etc/sysconfig/network-scripts
> # mv ifcfg-p6p1 sav.ifconfig-p6p1
>
> (that way you can bring it back later if you have to)
>
> --Greg

Yes! Now it works if I bring it up manually via systemctl restart
network.service.
But it (network) does not start automatically at boot. And I don't
have that network icon/applet on the bar to start it with a mouse
click.

Thanks,
--nat
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Wed, 2012-06-20 at 13:09 -0400, Natalie Gross wrote:
> Now it works if I bring it up manually via systemctl restart
> network.service.
> But it (network) does not start automatically at boot. And I don't
> have that network icon/applet on the bar to start it with a mouse
> click.

There are two different services involved. There is NetworkManager
(which is where the panel icon comes from) and network. You should only
run one of them. If you want to run the network service, which is more
command-line and config-file oriented, then just do:

# systemctl disable NetworkManager.service
# systemctl enable network.service

The latter command is the one that will get the network service started
at boot time.

Fedora out of the box wants you to run NetworkManager, in which case you
would use the NetworkManager GUI to configure your devices and don't
enable or start the "network" service. The simpler (and some say more
reliable) network service may be fine if you have only one device and no
WiFi and don't need to change your device configuration very often.

--Greg



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Thu, Jun 21, 2012 at 3:51 PM, Greg Woods <woods@ucar.edu> wrote:
> On Wed, 2012-06-20 at 13:09 -0400, Natalie Gross wrote:
>> *Now it works if I bring it up manually via systemctl restart
>> network.service.
>> But it (network) does not start automatically at boot. And I don't
>> have that network icon/applet on the bar to start it with a mouse
>> click.
>
> There are two different services involved. There is NetworkManager
> (which is where the panel icon comes from) and network. You should only
> run one of them. If you want to run the network service, which is more
> command-line and config-file oriented, then just do:
>
> # systemctl disable NetworkManager.service
> # systemctl enable network.service
>
> The latter command is the one that will get the network service started
> at boot time.
>
> Fedora out of the box wants you to run NetworkManager, in which case you
> would use the NetworkManager GUI to configure your devices and don't
> enable or start the "network" service. The simpler (and some say more
> reliable) network service may be fine if you have only one device and no
> WiFi and don't need to change your device configuration very often.
>
> --Greg
>
I would rather use NetworkManager. (I also have a wifi card, currently
not used.)
But attempting to enable or restart NetworkManager.service results in
an error "No such file or directory."
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Mon, Jun 25, 2012 at 8:41 PM, Natalie Gross <nat101l@gmail.com> wrote:
> On Thu, Jun 21, 2012 at 3:51 PM, Greg Woods <woods@ucar.edu> wrote:
>> On Wed, 2012-06-20 at 13:09 -0400, Natalie Gross wrote:
>>> *Now it works if I bring it up manually via systemctl restart
>>> network.service.
>>> But it (network) does not start automatically at boot. And I don't
>>> have that network icon/applet on the bar to start it with a mouse
>>> click.
>>
>> There are two different services involved. There is NetworkManager
>> (which is where the panel icon comes from) and network. You should only
>> run one of them. If you want to run the network service, which is more
>> command-line and config-file oriented, then just do:
>>
>> # systemctl disable NetworkManager.service
>> # systemctl enable network.service
>>
>> The latter command is the one that will get the network service started
>> at boot time.
>>
>> Fedora out of the box wants you to run NetworkManager, in which case you
>> would use the NetworkManager GUI to configure your devices and don't
>> enable or start the "network" service. The simpler (and some say more
>> reliable) network service may be fine if you have only one device and no
>> WiFi and don't need to change your device configuration very often.
>>
>> --Greg
>>
> I would rather use NetworkManager. (I also have a wifi card, currently
> not used.)
> But attempting to enable or restart NetworkManager.service results in
> an error "No such file or directory."

The latest update (including kernel) has solved the problem!
network.service now starts automatically.
-nat
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org