[SOLVED] impossible to boot (UEFI-grub2) after update

Hi,
problem : after update my computer refuses to boot. It doesn't get to the grub2 (actually 1.99) menu, it just says : no boot device found.
My hardware : Asus M8Z77-V LX motherboard with 1 SSD.
In the bios I disabled the bios legacy option to force it to boot with UEFI.
As I hadn't moved to systemd yet, I waited to update a while(2 months).
Last week I updated several pacakges by hand (kernel, vlc, ...) : All updates that according to me didn't involve with systemd.
Then I rebooted and ... problem.
I have tried a whole weekend to solve it by browsing through the wiki's but to no avail.
I can boot with live-cd and access my SSD. All data is there. I can also chroot and do stuff.
The SSD is partitionned in GPT as follows :
sda1 : 1 gb fat 32
sda2 : 20 gb ext4 root
sda3 : 20 gb ext4 var
sda4 : 79 gb ext4 home
I did not do any update of my bios or changed anything on my hardware.
It seems that my bios does not see my SSD as UEFI-bootable device anymore.
When I installed Arch in June on my brand new computer I made a backup with redobackup (partclone) of a working installation.
As a final ressort I put back the image I created then.
But it doesn't work either!
Then I updated my bios but same problem.
My bios can see the fat 32 partition. I know this because to update the bios it looks for attached fat 32 storage and there is shows the partition .
I there anywone who can point me in a good direction?
Thanks a lot in advance.
Last edited by BelgiumArcher (2013-01-08 16:20:43)

I am sorry if I lost your confidence. I can't find any contradictory info in my post.
The Arch Wiki-Grub 2 says that you need to boot in UEFI before you can (re)install grub2.
As my live-cd won't boot in UEFI mode, the only option is that I make a live-usb stick and see if that one will boot in UEFI.
But in the end it is still strange that a software update breaks my Asus UEFI-boot.
I just found another unlucky guy with a simular problem. I'll try his solution tonight.
http://superuser.com/questions/372962/w … ot-manager
http://superuser.com/questions/376470/h … -grub2-efi
I will try the live-usb method and report on it later.

Similar Messages

  • [Solved] 'New' error messages during init after updating initscripts

    After updating to the latest initscripts, I got some error messages during init that I hadn't seen before.  They occurred during one of the UDev steps, and were caused by an attempt to load an IDE module despite the controller being disabled.  The controller shows up in Windows devmgr too, so I guess it's a failing of the mobo or BIOS.
    In any case, I downgraded and found that the errors were nothing new.  I'm just curious if the appearance of the errors during init was by design or a happy accident.
    Last edited by alphaniner (2011-08-01 17:07:30)

    alphaniner wrote:
    karol wrote:If you have the new (i.e. current) initscripts, you should be fine:
    http://projects.archlinux.org/initscrip … 328fbaf2e7
    http://projects.archlinux.org/initscrip … 42dfeca8c2
    I had never noticed the file before yesterday, actually. And I'm up-to-date, yet it's still full of 'em.
    You need to reboot.
    After you do, run
    tail /var/log/boot
    Mine isn't perfect, but I've already sent an e-mail to the dev (it's a matter of just a sed oneliner)
    [karol@black ~]$ tail /var/log/boot
    Tue Aug 2 05:03:01 2011: :: Setting Hostname: black ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:01 2011: :: Setting Locale: pl_PL.UTF-8 ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:01 2011: :: Setting Consoles to UTF-8 mode ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:01 2011: :: Loading Keyboard Map: pl ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:02 2011: :: Loading Console Font: Lat2-Terminus16 ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:02 2011: :: Saving dmesg Log ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:02 2011: INIT: Entering runlevel: 3
    Tue Aug 2 05:03:02 2011: :: Starting Syslog-NG ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:03 2011: :: Starting D-BUS system messagebus ^[[171G [BUSY] ^[[171G [DONE]
    Tue Aug 2 05:03:04 2011: :: Starting acpid ^[[171G [BKGD] :: Starting gpm ^[[171G [BKGD^[[0;1

  • [SOLVED] Intel DRI does not work after update

    Hi,
    after update of kernel from 3.5.6 to 3.6.5 and intel driver and deletion of dri2proto and mesa via pacman -Qdt (there are no more dependencies).. acceleration is no longer working
    $ export LIBGL_DEBUG=verbose; glxinfo | grep renderer
    libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/tls/i965_dri.so
    libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/i965_dri.so
    libGL error: failed to open drm device: Permission denied
    libGL error: failed to load driver: i965
    libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/tls/swrast_dri.so
    libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/swrast_dri.so
    libGL: Can't open configuration file /etc/drirc: No such file or directory.
    OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x301)
    Configuration:
    SandyBridge I5, Intel HD 3000
    Can somebody help?
    Last edited by microcz (2012-11-07 06:15:23)

    OT: A simpler way to check if some packages are installed:
    $ pacman -Q intel-dri libgl foobar
    intel-dri 9.0-1
    libgl 9.0-1
    error: package 'foobar' was not found
    What's the output of 'groups'? Maybe you need to add yourself to 'video' group?
    http://www.linuxquestions.org/questions … nf-794105/
    http://www.mail-archive.com/dri-devel@l … 41313.html

  • [SOLVED] Unable to start vmware 9 after update

    Hello Folks,
    I got one weird issue after update,
    I tried to start vmware, failed as nothing happeded, no error message shown.
    Do you have any clues ?
    ┌─[root@tp]─[/tmp]─[0+4]─[99%=]
    └─# uname -a
    Linux tp 3.6.11-1-ARCH #1 SMP PREEMPT Tue Dec 18 08:57:15 CET 2012 x86_64 GNU/Linux
    ┌─[root@tp]─[/tmp]─[0+4]─[99%=]
    └─# vmware
    ┌─[✗]─[root@tp]─[/tmp]─[0+4]─[99%=]
    └─# vmware-modconfig --console --install-all
    Stopping VMware services:
       VMware Authentication Daemon                                        done
       VM communication interface socket family                            done
       Virtual machine communication interface                             done
       Virtual machine monitor                                             done
       Blocking file system                                                done
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/modconfig-CEZuvv/vmmon-only'
    /usr/bin/make -C /lib/modules/3.6.11-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.6.11-1-ARCH'
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/linux/hostif.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/linux/driver.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/common/memtrack.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/linux/driverLog.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/common/apic.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/common/vmx86.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/common/cpuid.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/common/task.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/common/hashFunc.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/common/comport.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/common/phystrack.o
      CC [M]  /tmp/modconfig-CEZuvv/vmmon-only/vmcore/moduleloop.o
      LD [M]  /tmp/modconfig-CEZuvv/vmmon-only/vmmon.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/modconfig-CEZuvv/vmmon-only/vmmon.mod.o
      LD [M]  /tmp/modconfig-CEZuvv/vmmon-only/vmmon.ko
    make[1]: Leaving directory `/usr/src/linux-3.6.11-1-ARCH'
    /usr/bin/make -C $PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/modconfig-CEZuvv/vmmon-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/modconfig-CEZuvv/vmmon-only'
    cp -f vmmon.ko ./../vmmon.o
    make: Leaving directory `/tmp/modconfig-CEZuvv/vmmon-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/modconfig-CEZuvv/vmnet-only'
    /usr/bin/make -C /lib/modules/3.6.11-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.6.11-1-ARCH'
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/driver.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/hub.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/netif.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/userif.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/bridge.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/filter.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/procfs.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/smac_compat.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/smac.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/vnetEvent.o
      CC [M]  /tmp/modconfig-CEZuvv/vmnet-only/vnetUserListener.o
      LD [M]  /tmp/modconfig-CEZuvv/vmnet-only/vmnet.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/modconfig-CEZuvv/vmnet-only/vmnet.mod.o
      LD [M]  /tmp/modconfig-CEZuvv/vmnet-only/vmnet.ko
    make[1]: Leaving directory `/usr/src/linux-3.6.11-1-ARCH'
    /usr/bin/make -C $PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/modconfig-CEZuvv/vmnet-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/modconfig-CEZuvv/vmnet-only'
    cp -f vmnet.ko ./../vmnet.o
    make: Leaving directory `/tmp/modconfig-CEZuvv/vmnet-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/modconfig-CEZuvv/vmblock-only'
    /usr/bin/make -C /lib/modules/3.6.11-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.6.11-1-ARCH'
      CC [M]  /tmp/modconfig-CEZuvv/vmblock-only/linux/filesystem.o
      CC [M]  /tmp/modconfig-CEZuvv/vmblock-only/linux/file.o
      CC [M]  /tmp/modconfig-CEZuvv/vmblock-only/linux/stubs.o
      CC [M]  /tmp/modconfig-CEZuvv/vmblock-only/linux/block.o
      CC [M]  /tmp/modconfig-CEZuvv/vmblock-only/linux/module.o
      CC [M]  /tmp/modconfig-CEZuvv/vmblock-only/linux/control.o
      CC [M]  /tmp/modconfig-CEZuvv/vmblock-only/linux/super.o
      CC [M]  /tmp/modconfig-CEZuvv/vmblock-only/linux/inode.o
      CC [M]  /tmp/modconfig-CEZuvv/vmblock-only/linux/dentry.o
    /tmp/modconfig-CEZuvv/vmblock-only/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/modconfig-CEZuvv/vmblock-only/linux/inode.c:49:4: warning: (near initialization for ‘RootInodeOps.lookup’) [enabled by default]
    /tmp/modconfig-CEZuvv/vmblock-only/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/modconfig-CEZuvv/vmblock-only/linux/dentry.c:38:4: warning: (near initialization for ‘LinkDentryOps.d_revalidate’) [enabled by default]
    /tmp/modconfig-CEZuvv/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
    /tmp/modconfig-CEZuvv/vmblock-only/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from pointer without a cast [enabled by default]
    /tmp/modconfig-CEZuvv/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’
      LD [M]  /tmp/modconfig-CEZuvv/vmblock-only/vmblock.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/modconfig-CEZuvv/vmblock-only/vmblock.mod.o
      LD [M]  /tmp/modconfig-CEZuvv/vmblock-only/vmblock.ko
    make[1]: Leaving directory `/usr/src/linux-3.6.11-1-ARCH'
    /usr/bin/make -C $PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/modconfig-CEZuvv/vmblock-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/modconfig-CEZuvv/vmblock-only'
    cp -f vmblock.ko ./../vmblock.o
    make: Leaving directory `/tmp/modconfig-CEZuvv/vmblock-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/modconfig-CEZuvv/vmci-only'
    /usr/bin/make -C /lib/modules/3.6.11-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.6.11-1-ARCH'
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/linux/driver.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/linux/vmciKernelIf.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciDriver.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciDatagram.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciResource.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciRoute.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciContext.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciHashtable.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciEvent.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciQueuePair.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciQPair.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/common/vmciDoorbell.o
      CC [M]  /tmp/modconfig-CEZuvv/vmci-only/driverLog.o
      LD [M]  /tmp/modconfig-CEZuvv/vmci-only/vmci.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/modconfig-CEZuvv/vmci-only/vmci.mod.o
      LD [M]  /tmp/modconfig-CEZuvv/vmci-only/vmci.ko
    make[1]: Leaving directory `/usr/src/linux-3.6.11-1-ARCH'
    /usr/bin/make -C $PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/modconfig-CEZuvv/vmci-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/modconfig-CEZuvv/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory `/tmp/modconfig-CEZuvv/vmci-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/modconfig-CEZuvv/vsock-only'
    /usr/bin/make -C /lib/modules/3.6.11-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.6.11-1-ARCH'
      CC [M]  /tmp/modconfig-CEZuvv/vsock-only/linux/af_vsock.o
      CC [M]  /tmp/modconfig-CEZuvv/vsock-only/linux/vsockAddr.o
      CC [M]  /tmp/modconfig-CEZuvv/vsock-only/linux/notifyQState.o
      CC [M]  /tmp/modconfig-CEZuvv/vsock-only/linux/util.o
      CC [M]  /tmp/modconfig-CEZuvv/vsock-only/linux/stats.o
      CC [M]  /tmp/modconfig-CEZuvv/vsock-only/linux/notify.o
      CC [M]  /tmp/modconfig-CEZuvv/vsock-only/driverLog.o
      LD [M]  /tmp/modconfig-CEZuvv/vsock-only/vsock.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/modconfig-CEZuvv/vsock-only/vsock.mod.o
      LD [M]  /tmp/modconfig-CEZuvv/vsock-only/vsock.ko
    make[1]: Leaving directory `/usr/src/linux-3.6.11-1-ARCH'
    /usr/bin/make -C $PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/modconfig-CEZuvv/vsock-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/modconfig-CEZuvv/vsock-only'
    cp -f vsock.ko ./../vsock.o
    make: Leaving directory `/tmp/modconfig-CEZuvv/vsock-only'
    Starting VMware services:
       Virtual machine monitor                                             done
       Virtual machine communication interface                             done
       VM communication interface socket family                            done
       Blocking file system                                                done
       Virtual ethernet                                                   failed
       VMware Authentication Daemon                                        done
    Unable to start services
    ┌─[✗]─[root@tp]─[/tmp]─[0+4]─[99%=]
    └─# vmware
    ┌─[✗]─[root@tp]─[/tmp]─[0+4]─[99%=]
    └─#
    Thanks in advance,
    Liao
    Last edited by liao (2013-01-11 14:10:29)

    after check vmware message under /tmp/vmware-$USER/vmware*.log, found one package is missing - libpng12, after installed it, everything looks good again

  • [SOLVED] Wrong handling with file types after update

    Arch can't "remember" which program to use for certain file type
    Example:
    after update arch try to open everything (mp3, avi, doc, odt, rar.......) with gedit, when I set mplayer for avi, Arch try to open every file with mplayer, I set writer for odt files Arch try to open every file with writer and .....
    And another thing, every file have "text file" icon
    Last edited by Joxy (2008-06-25 16:50:16)

    Take a look here http://bbs.archlinux.org/viewtopic.php?id=50667

  • [Solved] ADF BC - Correlation of Refresh After Update checkbox with Returni

    Hello all,
    As per JDev (10.1.3.3.0) help system Refresh After Update option is used when there is Before Update trigger on a table.
    As far as I know ADF BC framework is using Returing clause of an Update statement to implement Refresh After Update option.
    First of all I created the following objects in Oracle DB 10.2.0.3.0:
    CREATE TABLE TAB1
         ID          NUMBER          PRIMARY KEY,
         EDITED_AT     DATE,
         VALUE          VARCHAR2(64)
    CREATE SEQUENCE S_TAB1
         INCREMENT BY 1
         START WITH 1;
    CREATE TRIGGER T_TAB1_BIE
    BEFORE INSERT OR UPDATE ON TAB1
    FOR EACH ROW
    BEGIN
         IF INSERTING THEN
              SELECT S_TAB1.NEXTVAL INTO :NEW.ID FROM DUAL;
         END IF;
         :NEW.EDITED_AT := SYSDATE;
    END;
    /Taking into consideration aforesaid I tried to do the following in SQL Plus:
    SQL> insert into tab1(value) values('ddd');
    1 row created.
    SQL> commit;
    Commit complete.
    SQL>
    SQL> select * from tab1;
            ID EDITED_AT           VALUE
             1 27.03.2008 17:01:24 ddd
    SQL>
    SQL> declare dt date; val varchar2(64);
      2  begin update tab1 set value = 'ddd' where id = 1 returning edited_at, value into dt, val;
      3  dbms_output.put_line('txt = ' || dt || ', ' || val);
      4  end;
      5  /
    txt = 27.03.2008 17:01:24, ddd
    PL/SQL procedure successfully completed.
    SQL>
    SQL> select * from tab1;
            ID EDITED_AT           VALUE
             1 27.03.2008 17:02:12 ddd
    SQL>As it can be seen Returning clause of an Update statement does not return a new date, i.e. 27.03.2008 17:02:12, that was updated by the trigger, it returns an old one - 27.03.2008 17:01:24.
    Should I change any parameter in Oracle DB or what can I do that ADF BC refreshes values generated by a Before Trigger?

    Yerzhant,
    Something is certainly not right. I don't have a 10.2.0.3.0 instance handy at the moment, but I tried verbatim your example in 11.1.0.6.0, and it works properly.
    I am using this capability all over the place in ADF BC with no problems, database versions from 10gr1 to 11gr1.
    Perhaps time to contact support.
    John

  • [SOLVED] Network Manager systemd unit fails after update

    EDIT: Reinstalling libnm-glib resolved this issue
    After updating to the latest version of NetworkManager (networkmanager-0.9.8.10-3), the systemd unit fails to start. It works fine after downgrading back to the previous version though (networkmanager-0.9.8.10-1). I'm not sure if this is a bug or an error on my end; since the previous package works I've just dowgraded for the time being.  For the update that doesn't work, here is the output of "systemctl status" and the systemd journal:
    >>sudo systemctl daemon-reload
    >> sudo systemctl status NetworkManager
    ● NetworkManager.service - Network Manager
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
    Active: failed (Result: exit-code) since Wed 2014-06-11 15:28:25 EDT; 10s ago
    Process: 24073 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=127)
    Main PID: 24073 (code=exited, status=127)
    Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
    Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
    Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
    >> journalctl -xn
    -- Logs begin at Tue 2014-06-10 12:47:19 EDT, end at Wed 2014-06-11 15:28:36 EDT. --
    Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
    Jun 11 15:28:25 kyle systemd[1]: Starting Network Manager...
    -- Subject: Unit NetworkManager.service has begun with start-up
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit NetworkManager.service has begun starting up.
    Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
    Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
    -- Subject: Unit NetworkManager.service has failed
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit NetworkManager.service has failed.
    -- The result is failed.
    Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
    Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session closed for user root
    Jun 11 15:28:28 kyle dbus[489]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
    Jun 11 15:28:36 kyle sudo[24075]: kyle : TTY=pts/2 ; PWD=/var/cache/pacman/pkg ; USER=root ; COMMAND=/usr/bin/systemctl status NetworkManager
    Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
    Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session closed for user root
    Last edited by T0k3n (2014-07-03 15:18:01)

    Check the changes:
    https://projects.archlinux.org/svntogit … e192881dc5
    https://projects.archlinux.org/svntogit … ee906b6c44
    When posting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
    like this
    It makes the code more readable and - in case of longer listings - more convenient to scroll through.

  • [SOLVED] Only https sites are opening after update

    Today I updated whole system, but after update my browsers (firefox and konqueror) are not able to open http sites. I'm only able to open https sites. Everything was working fine before the update. But I'm able to ping both https and http sites:
    PING www.vpnbook.com (195.60.76.198) 56(84) bytes of data.
    64 bytes from www.vpnbook.com (195.60.76.198): icmp_seq=1 ttl=44 time=489 ms
    64 bytes from www.vpnbook.com (195.60.76.198): icmp_seq=2 ttl=44 time=519 ms
    64 bytes from 195.60.76.198: icmp_seq=3 ttl=44 time=499 ms
    --- www.vpnbook.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2089ms
    rtt min/avg/max/mdev = 489.561/503.014/519.683/12.519 ms
    PING www.google.com (74.125.236.113) 56(84) bytes of data.
    64 bytes from bom03s01-in-f17.1e100.net (74.125.236.113): icmp_seq=1 ttl=50 time=340 ms
    64 bytes from bom03s01-in-f17.1e100.net (74.125.236.113): icmp_seq=2 ttl=50 time=290 ms
    64 bytes from bom03s01-in-f17.1e100.net (74.125.236.113): icmp_seq=3 ttl=50 time=280 ms
    --- www.google.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 1999ms
    rtt min/avg/max/mdev = 280.700/303.871/340.199/26.014 ms
    Last edited by ansh_kumar (2014-04-22 02:51:42)

    Wait I just installed traceroute from https mirror. Here is the output:
    traceroute to 173.194.36.40 (173.194.36.40), 30 hops max, 60 byte packets
    1 10.147.204.2 (10.147.204.2) 675.523 ms 675.639 ms 695.598 ms
    2 10.147.197.18 (10.147.197.18) 897.484 ms 875.211 ms 897.173 ms
    3 10.147.197.61 (10.147.197.61) 936.968 ms 916.711 ms 915.857 ms
    4 10.147.197.1 (10.147.197.1) 915.592 ms 936.590 ms 955.462 ms
    5 10.147.201.65 (10.147.201.65) 955.237 ms 955.521 ms 977.024 ms
    6 10.147.193.53 (10.147.193.53) 977.130 ms 119.199 ms 259.974 ms
    7 218.248.82.210 (218.248.82.210) 261.167 ms 218.248.82.206 (218.248.82.206) 261.732 ms 218.248.82.210 (218.248.82.210) 261.279 ms
    8 72.14.218.242 (72.14.218.242) 262.141 ms 261.980 ms 262.662 ms
    9 66.249.95.106 (66.249.95.106) 262.956 ms 262.671 ms 263.137 ms
    10 209.85.252.143 (209.85.252.143) 262.967 ms 263.329 ms 262.675 ms
    11 209.85.241.189 (209.85.241.189) 263.122 ms 263.349 ms 263.451 ms
    12 bom04s02-in-f8.1e100.net (173.194.36.40) 159.342 ms 159.542 ms 179.665 ms

  • [SOLVED] Archlinux does not boot any more after update

    Hi all,
    yesterday I decided to update my Archlinux system again after postponing the updates for some weeks.
    In general I update anything except kernel stuff, but this did lead to some dependency problems recently,
    so I decided to make a full upgrade now via pacman.
    After restarting the system, the kernel refused to boot. It told me, that it couldn't find my root partition /dev/sdc1 and left
    me in an almost useless recovery shell. The error was:
    ERROR: Unable to determine major/minor number of root device /dev/sdc1
    Has anyone an idea, what might have happened? I had to install Ubuntu into a free partition to post this
    topic. The disks and partitions are okay, I managed to "boot" using the old kernel, but of course the system
    remained useless in that case due to wrong kernel module versions.
    Thanks in advance for any hint, how to proceed.
    Cheers, Zmann
    Last edited by Zmann (2012-06-02 20:56:39)

    Hi all,
    thanks for the quick replies and sorry for the delay (children prioritized :-)
    Yes, I'm using an older SATA controller (more or less 6 years), so the problem might be related to what you posted.
    I was not able to boot the old fallback kernel, same error message. The fallback kernel simply uses a different initrd
    file, perhaps I should think about a more sophisticated approach.
    Nevertheless I already checked the file /etc/mkinitcpio.conf and it did not contain a hook called autodetect. So maybe
    the mkinitcpio won't help anyway? Should I prefer using the suggested LTS kernel instead? I assume, this is done by booting
    using an archlinux CD, then chroot and using pacman? Maybe it's sufficient to chroot from the currently running ubuntu instead?
    Or will the booted kernel have any influence to mkinitcpio or the like?
    Cheers, Zmann

  • [SOLVED] DVB-C card stopped working (after update?)

    edit: Marked as solved because the problem hasn't occurred for years.
    I have a TechnoTrend TT-Budget C-1501 PCI DVB-C card which used to work fine. Today I installed a bunch of updates including new kernel and now the card doesn't work. Current kernel version is 3.9.2-1-ARCH, as reported by uname -r. I don't remember the kernel version which was installed when the card worked but I installed Arch about a month ago and this was the first upgrade.
    dmesg gives the following information:
    $ dmesg | grep -i dvb
    [ 1.663037] saa7146: register extension 'budget_ci dvb'
    [ 1.663232] DVB: registering new adapter (TT-Budget C-1501 PCI)
    [ 1.718876] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:01.0/rc/rc0/input13
    [ 1.719068] rc0: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:01.0/rc/rc0
    [ 1.721746] DVB: TDA10023(-1): tda10023_writereg, writereg error (reg == 0x00, val == 0x33, ret == -121)
    [ 1.771639] DVB: TDA10023(-1): tda10023_readreg: readreg error (reg == 0x1a, ret == -121)
    This problem seems to be relatively common with cards containing the TDA10023 chip but I haven't found a proper solution. Is this just a bug or should I adjust something?
    EDIT: I forgot to mention that the card works on Windows.
    Hardware specs:
    Intel Xeon E3-1230v2 CPU
    16GB of RAM
    ASRock H77 Pro4/MVP motherboard (BIOS/UEFI version seems to be the latest (1.50))
    Geforce GTX 650 Ti
    Last edited by ormu (2015-04-07 16:01:12)

    Weird, now it's working again after "cold" boot... Could the Windows driver load a different firmware which doesn't work properly on Linux? I think I used the card on Windows just before rebooting to Arch...
    $ dmesg | grep -i dvb
    [ 1.651217] saa7146: register extension 'budget_ci dvb'
    [ 1.651361] DVB: registering new adapter (TT-Budget C-1501 PCI)
    [ 1.708299] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:01.0/rc/rc0/input13
    [ 1.708338] rc0: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:01.0/rc/rc0
    [ 1.711359] budget_ci dvb 0000:04:01.0: DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)...

  • [SOLVED] can't boot from ssd after "reset" from recovery usb flash drive

    I have a Twist s230u with the original Hitachi 500GB hdd, running Windows 8.1.  I want to replace the Hitachi 500GB hdd in my Twist s230u with a PNY 240GB SSD that i've purchased.
    While running Windows from the Hitachi HDD drive I followed the "create a recovery drive" procedure to create a recovery usb.  Then I removed the Hitachi HDD from the s230u and installed the PNY 240 SSD in its place.  I booted the s230u from the recovery flash drive that I made.  I selected the "Reset Your PC" option and then the option to wipe all partition/files.  After the Reset completes, I try booting from the SSD but am unable to do so.  I just go back to the F12 boot menu.
    I put the SSD in a drive dock attached to another computer.  Disk Management shows the partitions as follows - 
    I've looked at the partitions on the SSD after the Reset - Disk Management console shows a 1000 MB Recovery partition, a 260MB EFI System partition, and a 221GB primary partition with volume label Windows8_OS.  It is not marked as Boot, Page File, or Crash Dump.
    Diskpart shows an an additional 128MB Reserved partition between the EFI partition and the primary partition.
    I do notice that the 10.6 Lenovo Recovery partition is not present - but I did make sure that I included that partition on the recovery key - though the files on the recovery key only use 8.03 GB for some reason.  Made the key on two different flash media.
    Diskpart also shows the following for the SSD:
    DISKPART> attributes disk
    Current Read-only State : No
    Read-only : No
    Boot Disk : No
    Pagefile Disk : No
    Hibernation File Disk : No
    Crashdump Disk : No
    Clustered Disk : No
    (It also looks like this when I run DISKPART from the recovery media with the SSD inside the internal drive bay of the s230u.)
    When I did the Reset on the SSD in the s230u, and when I tried to boot from it - I had the Secure Boot disabled, the "Legacy Boot first" option set, etc.  
    Can anyone point me in the right direction to be able to boot Windows 8.1 from this SSD in the s230u?  I've been working on this for a couple of days.
    (I also tried cloning the HDD to the SDD using Minitool Partition Wizard, Macrium Reflect, Clonezilla, Acronis, etc - the SSD wouldn't boot after those clone operations either, and I thought maybe I'd have better luck with a reinstall from the USB recovery media.
    (I also tried installing from a Windows 8 iso I burned to a DVD.  I got a product id mismatch message when I tried to install from that, and I was not allowed to proceed.)

    well, I seem to have solved my own problem.  Maybe someone will learn from my mistakes.
    I went into System Setup, went to the Startup tab, and changed the boot setting from "Both" to "UEFI Only".  After doing this I booted from my USB recovery drive, and Reset the PC.  After the Reset, I booted the s230u from the ssd, and I booted into a fresh Windows 8 installation.  
    It seems that the Reset operation could not work properly while the boot setting was "Both" (UEFI and Legacy) and "Legacy First."
    I got a clue when I looked at the contents of the EFI System Partition and there was nothing there except a Temp folder. The EFI System Partition had not been properly written by the Reset operation.  I got some helpful hints on how to see the contents of the EFI System Partition here - http://www.fixedbyvonnie.com/2013/12/how-to-repair-the-efi-bootloader-in-windows-8/#.U-Qz2_ldW7q
    I've also buggered up my original HDD now, so that it won't boot to Windows now.  Now to fix that!  

  • [Solved] NetworkManager-pptp VPN not working after update to 0.9.10

    Hello,
    I have a PPTP VPN set up and it's been working for a long time.  However, after I updated last night to networkmanager-0.9.10, it is no longer able to connect to the remote network.  I can activate the VPN connection, enter my password, but after a short period of time, the connection reports:  "Error: Connection activation failed: the VPN service returned invalid configuration."  As I mentioned before, this VPN was working right before the update and I didn't change the configuration on either my computer or the destination network so I'm pretty sure that this is something to do with the update.  I'm wondering if anybody else has run into this problem and if they've been able to find a solution.  I've been searching all over these forums and the internet for some hours now and I haven't found anything yet.  I'm hoping that somebody might be able to point me in the right direction or maybe know of something that might have changed with the new update.
    Here is my VPN configuration (using NetworkManager-PPTP.  I've also obscured the public IP address):
    [connection]
    id=MyVPN
    uuid=fe6e6265-1a79-4a69-b6d1-8b47e9d4c948
    type=vpn
    permissions=user:greyseal96:;
    autoconnect=false
    timestamp=1408950986
    [vpn]
    service-type=org.freedesktop.NetworkManager.pptp
    gateway=192.168.146.114
    require-mppe=yes
    user=greyseal96
    password-flags=3
    [ipv6]
    method=auto
    [ipv4]
    method=auto
    route1=10.17.0.0/16,10.17.1.1,1
    never-default=true
    Here are my logs during the time that I tried to connect:
    Aug 24 23:44:15 MyArchBox NetworkManager[578]: <info> Starting VPN service 'pptp'...
    Aug 24 23:44:15 MyArchBox NetworkManager[578]: <info> VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 1938
    Aug 24 23:44:15 MyArchBox NetworkManager[578]: <info> VPN service 'pptp' appeared; activating connections
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> VPN connection 'MyVPN' (ConnectInteractive) reply received.
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> VPN plugin state changed: starting (3)
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: ** Message: pppd started with pid 1945
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> VPN connection 'MyVPN' (Connect) reply received.
    Aug 24 23:44:21 MyArchBox pppd[1945]: Plugin /usr/lib/pppd/2.4.6/nm-pptp-pppd-plugin.so loaded.
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: Plugin /usr/lib/pppd/2.4.6/nm-pptp-pppd-plugin.so loaded.
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing
    Aug 24 23:44:21 MyArchBox pppd[1945]: pppd 2.4.6 started by root, uid 0
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection'
    Aug 24 23:44:21 MyArchBox pppd[1945]: Using interface ppp0
    Aug 24 23:44:21 MyArchBox pppd[1945]: Connect: ppp0 <--> /dev/pts/2
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: Using interface ppp0
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: Connect: ppp0 <--> /dev/pts/2
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> (ppp0): new Generic device (driver: 'unknown' ifindex: 10)
    Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> (ppp0): exported as /org/freedesktop/NetworkManager/Devices/9
    Aug 24 23:44:21 MyArchBox pptp[1947]: nm-pptp-service-1938 log[main:pptp.c:333]: The synchronous pptp option is NOT activated
    Aug 24 23:44:21 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 'Start-Control-Connection-Request'
    Aug 24 23:44:21 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_disp:pptp_ctrl.c:758]: Received Start Control Connection Reply
    Aug 24 23:44:21 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_disp:pptp_ctrl.c:792]: Client connection established.
    Aug 24 23:44:22 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 'Outgoing-Call-Request'
    Aug 24 23:44:22 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_disp:pptp_ctrl.c:877]: Received Outgoing Call Reply.
    Aug 24 23:44:22 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_disp:pptp_ctrl.c:916]: Outgoing call established (call ID 0, peer's call ID 50048).
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate'
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (get_credentials): passwd-hook, requesting credentials...
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (get_credentials): got credentials from NetworkManager-pptp
    Aug 24 23:44:25 MyArchBox pppd[1945]: CHAP authentication succeeded
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: CHAP authentication succeeded
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 8 / phase 'network'
    Aug 24 23:44:25 MyArchBox pppd[1945]: MPPE 128-bit stateless compression enabled
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: MPPE 128-bit stateless compression enabled
    Aug 24 23:44:25 MyArchBox pppd[1945]: Cannot determine ethernet address for proxy ARP
    Aug 24 23:44:25 MyArchBox pppd[1945]: local  IP address 10.17.10.3
    Aug 24 23:44:25 MyArchBox pppd[1945]: remote IP address 10.17.10.1
    Aug 24 23:44:25 MyArchBox pppd[1945]: primary   DNS address 10.17.2.22
    Aug 24 23:44:25 MyArchBox pppd[1945]: secondary DNS address 10.17.2.23
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> VPN connection 'MyVPN' (IP4 Config Get) reply received from old-style plugin.
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> VPN Gateway: 192.168.146.114
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Tunnel Device: ppp0
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> IPv4 configuration:
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info>   Internal Address: 10.17.10.3
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info>   Internal Prefix: 32
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info>   Internal Point-to-Point Address: 10.17.10.1
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info>   Maximum Segment Size (MSS): 0
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info>   Static Route: 10.17.0.0/16   Next Hop: 10.17.1.1
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info>   Forbid Default Route: yes
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info>   Internal DNS: 10.17.2.22
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info>   Internal DNS: 10.17.2.23
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info>   DNS Domain: '(none)'
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> No IPv6 configuration
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <error> [1408949065.481618] [platform/nm-linux-platform.c:1716] add_object(): Netlink error adding 10.17.0.0/16 via 10.17.1.1 dev ppp0 metric 1 mss 0 src user: Unspecific failure
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <warn> VPN connection 'MyVPN' did not receive valid IP config information.
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: Cannot determine ethernet address for proxy ARP
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: local  IP address 10.17.10.3
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: remote IP address 10.17.10.1
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: primary   DNS address 10.17.2.22
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: secondary DNS address 10.17.2.23
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 9 / phase 'running'
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): ip-up event
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): sending Ip4Config to NetworkManager-pptp...
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: PPTP service (IP Config Get) reply received.
    Aug 24 23:44:25 MyArchBox pppd[1945]: Terminating on signal 15
    Aug 24 23:44:25 MyArchBox pppd[1945]: Modem hangup
    Aug 24 23:44:25 MyArchBox pptp[1954]: nm-pptp-service-1938 log[callmgr_main:pptp_callmgr.c:245]: Closing connection (unhandled)
    Aug 24 23:44:25 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 12 'Call-Clear-Request'
    Aug 24 23:44:25 MyArchBox pptp[1954]: nm-pptp-service-1938 log[call_callback:pptp_callmgr.c:84]: Closing connection (call state)
    Aug 24 23:44:25 MyArchBox pppd[1945]: Connect time 0.0 minutes.
    Aug 24 23:44:25 MyArchBox pppd[1945]: Sent 0 bytes, received 0 bytes.
    Aug 24 23:44:25 MyArchBox pppd[1945]: MPPE disabled
    Aug 24 23:44:25 MyArchBox pppd[1945]: Connection terminated.
    Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
    Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
    Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
    Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
    Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: inet 10.17.0.0/16 table main
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: priority 0x1 protocol static
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: nexthop via 10.17.1.1 dev 10
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <error> [1408949065.487073] [platform/nm-linux-platform.c:2252] link_change(): Netlink error changing link 10:  <DOWN> mtu 0 (1) driver 'unknown' udi '/sys/devices/virtual/net/ppp0': No such device
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: <error> [1408949065.487153] [platform/nm-linux-platform.c:1777] delete_object(): Netlink error deleting 10.17.10.3/32 lft forever pref forever lifetime 1862-0[4294967295,4294967295] dev ppp0 src kernel: No such device (-31)
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: Terminated ppp daemon with PID 1945.
    Aug 24 23:44:25 MyArchBox kernel: Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev- instead.
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: Terminating on signal 15
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: Modem hangup
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 8 / phase 'network'
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: Connect time 0.0 minutes.
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: Sent 0 bytes, received 0 bytes.
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: MPPE disabled
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 10 / phase 'terminate'
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect'
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: Connection terminated.
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 1 / phase 'dead'
    Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_exit_notify): cleaning up
    Aug 24 23:44:25 MyArchBox pppd[1945]: Exit.
    Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** (nm-pptp-service:1938): WARNING **: pppd exited with error code 16
    Aug 24 23:44:45 MyArchBox NetworkManager[578]: <info> VPN service 'pptp' disappeared
    If you've gotten this far, thank you for taking the time to read through all this!  Any help that you can give would be much appreciated.
    Last edited by greyseal96 (2014-08-27 15:20:02)

    Hmm, not sure about the 3.16 series kernel, but I found that when I upgraded to kernel 3.18 the PPTP VPN also stopped working.  This time, though, it was because, for some reason, there was a change in kernel 3.18 where the firewall kernel modules necessary for the VPN don't get loaded so the firewall won't allow some of the PPTP traffic from the remote side back in.  Since the firewall is stateful, these modules need to be loaded so that the firewall can know that the incoming PPTP traffic from the remote side is part of an existing connection.  Here's what my network manager logs looked like:
    NetworkManager[619]: <info> Starting VPN service 'pptp'...
    NetworkManager[619]: <info> VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 31139
    NetworkManager[619]: <info> VPN service 'pptp' appeared; activating connections
    NetworkManager[619]: <info> VPN connection 'MyVPN' (ConnectInteractive) reply received.
    NetworkManager[619]: <info> VPN plugin state changed: starting (3)
    NetworkManager[619]: ** Message: pppd started with pid 31148
    NetworkManager[619]: <info> VPN connection 'MyVPN' (Connect) reply received.
    pppd[31148]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
    NetworkManager[619]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
    NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing
    pppd[31148]: pppd 2.4.7 started by root, uid 0
    NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection'
    pppd[31148]: Using interface ppp0
    pppd[31148]: Connect: ppp0 <--> /dev/pts/5
    NetworkManager[619]: Using interface ppp0
    NetworkManager[619]: Connect: ppp0 <--> /dev/pts/5
    NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
    NetworkManager[619]: <info> (ppp0): new Generic device (driver: 'unknown' ifindex: 7)
    NetworkManager[619]: <info> (ppp0): exported as /org/freedesktop/NetworkManager/Devices/6
    pptp[31150]: nm-pptp-service-31139 log[main:pptp.c:333]: The synchronous pptp option is NOT activated
    pptp[31157]: nm-pptp-service-31139 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 'Start-Control-Connection-Request'
    pptp[31157]: nm-pptp-service-31139 log[ctrlp_disp:pptp_ctrl.c:758]: Received Start Control Connection Reply
    pptp[31157]: nm-pptp-service-31139 log[ctrlp_disp:pptp_ctrl.c:792]: Client connection established.
    pptp[31157]: nm-pptp-service-31139 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 'Outgoing-Call-Request'
    pptp[31157]: nm-pptp-service-31139 log[ctrlp_disp:pptp_ctrl.c:877]: Received Outgoing Call Reply.
    pptp[31157]: nm-pptp-service-31139 log[ctrlp_disp:pptp_ctrl.c:916]: Outgoing call established (call ID 0, peer's call ID 25344).
    pppd[31148]: LCP: timeout sending Config-Requests <===HERE IS WHERE THE CONNECTION FAILS BECAUSE THE MODULES AREN'T LOADED.
    pppd[31148]: Connection terminated.
    NetworkManager[619]: LCP: timeout sending Config-Requests
    NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect'
    NetworkManager[619]: Connection terminated.
    NetworkManager[619]: <warn> VPN plugin failed: connect-failed (1)
    NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 1 / phase 'dead'
    pppd[31148]: Modem hangup
    pppd[31148]: Exit.
    NetworkManager[619]: <warn> VPN plugin failed: connect-failed (1)
    NetworkManager[619]: Modem hangup
    NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_exit_notify): cleaning up
    NetworkManager[619]: <warn> VPN plugin failed: connect-failed (1)
    NetworkManager[619]: <info> VPN plugin state changed: stopped (6)
    NetworkManager[619]: <info> VPN plugin state change reason: unknown (0)
    NetworkManager[619]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active.
    NetworkManager[619]: ** (nm-pptp-service:31139): WARNING **: pppd exited with error code 16
    NetworkManager[619]: <info> VPN service 'pptp' disappeared
    To fix this, I had to add a file to the /etc/modules-load.d directory to have the modules loaded into the kernel at boot.  I just created a file called netfilter.conf and put the following in it:
    nf_nat_pptp
    nf_conntrack_pptp
    nf_conntrack_proto_gre
    Not sure if this addresses your problem or not, but maybe it's worth a look.

  • [Solved] Can't boot into Arch after deleting some partitons

    About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
    On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
    I can chroot into Arch and did the following -
    grub> find /boot/grub/stage1
    (hd0,5)
    grub> root (hd0,5)
    Filesystem type is ext2fs, partition type 0x83
    grub> setup (hd0)
    Checking if "/boot/grub/stage1" exists... yes
    Checking if "/boot/grub/stage2" exists... yes
    Checking if "/boot/grub/e2fs_stage1_5" exists... yes
    Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
    succeeded
    Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
    ed
    Done.
    grub>
    The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    title Arch uuid
    #root (hd0,5)
    uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
    kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
    intrd /boot/kernel26.img
    title Arch hd
    root (hd0,5)
    kernel /boot/vmlinuz26 root=/dev/sda6
    intrd /boot/kernel26.img
    I have a bootinfo script which gives the following (from the chroot environment) -
    Boot Info Script 0.55 dated February 15th, 2010
    ============================= Boot Info Summary: ==============================
    => Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
    in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
    => No boot loader is installed in the MBR of /dev/sdb
    sda1: _________________________________________________________________________
    File system: swap
    Boot sector type: -
    Boot sector info:
    sda2: _________________________________________________________________________
    File system: Extended Partition
    Boot sector type: -
    Boot sector info:
    sda5: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    sda6: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    mount: /dev/sda6 already mounted or sda6 busy
    sda7: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    sda3: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 10.04.1 LTS
    Boot files/dirs: /etc/fstab
    sda4: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
    sdb1: _________________________________________________________________________
    File system: xfs
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    =========================== Drive/Partition Info: =============================
    Drive: sda ___________________ _____________________________________________________
    Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start End Size Id System
    /dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
    /dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
    /dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
    /dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
    /dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
    /dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
    /dev/sda4 * 63 417,689 417,627 83 Linux
    Drive: sdb ___________________ _____________________________________________________
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    Partition Boot Start End Size Id System
    /dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
    blkid -c /dev/null: ____________________________________________________________
    Device UUID TYPE LABEL
    /dev/loop0 squashfs
    /dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
    /dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
    /dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
    /dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
    /dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
    /dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
    /dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
    /dev/sda: PTTYPE="dos"
    /dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
    /dev/sdb: PTTYPE="dos"
    ============================ "mount | grep ^/dev output: ===========================
    Device Mount_Point Type Options
    /dev/sda12 / ext3 (rw,commit=0)
    =============================== sda3/etc/fstab: ===============================
    # /etc/fstab: static file system information.
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc defaults 0 0
    # /dev/sda1 = swap
    /dev/sda1 none swap sw 0 0
    # /dev/sda3 = root
    #UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
    /dev/sda3 / ext3 relatime,errors=remount-ro 0 1
    # /dev/sda4 = boot
    # UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
    /dev/sda4 /boot ext3 relatime 0 2
    # /dev/sda5 = home
    # UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
    /dev/sda5 /home ext3 relatime 0 2
    #/dev/sda6
    #UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
    /dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
    # /dev/sda7
    # UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
    /dev/sda7 /var ext3 relatime 0 2
    # /dev/sda8
    /dev/sda8 /opt ext3 relatime 0 2
    # /dev/sda10 - Arch
    /dev/sda10 /mnt/arch ext3 relatime 0 2
    # Not sure what this is doing here
    # Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
    # /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
    # /dev/sde1
    # uuid appears to be 644406B3570C1846 -> ../../sde1
    #/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
    #1TB-01
    UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-02
    UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-03
    UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 750GB-02 ext3 Partition
    # UUID giving problems, trying with dev
    # UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    /dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    ============================= sda4/grub/menu.lst: =============================
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ## kopt_2_6_8=root=/dev/hdc1 ro
    ## kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ## lockold=true
    # lockold=false
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery) single
    # altoptions=(recovery mode) single
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ## memtest86=false
    # memtest86=true
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    ## ## End Default Options ##
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-26-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-24-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-23-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-22-generic
    title Ubuntu 10.04.1 LTS, memtest86+
    root (hd0,3)
    kernel /memtest86+.bin
    quiet
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    ============================= sda4/grub/grub.cfg: =============================
    # DO NOT EDIT THIS FILE
    # It is automatically generated by /usr/sbin/grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    set default="0"
    if [ ${prev_saved_entry} ]; then
    set saved_entry=${prev_saved_entry}
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
    fi
    function recordfail {
    set recordfail=1
    if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
    insmod ext2
    set root='(hd0,3)'
    search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
    if loadfont /usr/share/grub/unicode.pf2 ; then
    set gfxmode=640x480
    insmod gfxterm
    insmod vbe
    if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
    fi
    fi
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    set locale_dir=($root)/grub/locale
    set lang=en
    insmod gettext
    if [ ${recordfail} = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    ### END /etc/grub.d/05_debian_theme ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-26-generic ...'
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-24-generic ...'
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-23-generic ...'
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-22-generic ...'
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-22-generic
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin console=ttyS0,115200n8
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Arch Linux (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26.img
    menuentry "Arch Linux Fallback (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26-fallback.img
    #### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    # From Arch grub menu.lst
    # (0) Arch Linux
    #title Arch Linux [/boot/vmlinuz26]
    #root (hd0,0)
    #kernel /vmlinuz26 root=/dev/sda3 ro
    #initrd /kernel26.img
    #Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
    (hdX,Y)/grub/linux.mod).
    #This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
    #An example, booting Arch Linux:
    #set root=(hd0,5)
    #linux /boot/vmlinuz26 root=/dev/sda5
    #initrd /boot/kernel26.img
    #boot
    ###menuentry "Arch1" {
    ###insmod ext2
    ###set root='(hd0,10)'
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    ###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
    ID
    ###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch2" {
    ###insmod ext2
    ###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch3" {
    ###insmod ext2
    ###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ### END /etc/grub.d/40_custom ###
    =================== sda4: Location of files loaded by Grub: ===================
    .0GB: grub/core.img
    .0GB: grub/grub.cfg
    .0GB: grub/menu.lst
    .0GB: grub/stage2
    .0GB: initrd.img-2.6.32-22-generic
    .0GB: initrd.img-2.6.32-23-generic
    .1GB: initrd.img-2.6.32-24-generic
    .1GB: initrd.img-2.6.32-26-generic
    .0GB: vmlinuz26
    .0GB: vmlinuz-2.6.32-22-generic
    .0GB: vmlinuz-2.6.32-23-generic
    .1GB: vmlinuz-2.6.32-24-generic
    .0GB: vmlinuz-2.6.32-26-generic
    =============================== StdErr Messages: ===============================
    No volume groups found
    mdadm: No arrays found in config file or automatically
    [/quote]
    Output of fdisk -l from chroot is -
    [quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0000b084
    Device Boot Start End Blocks Id System
    /dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
    /dev/sda2 25414954 1465144064 719864555+ 5 Extended
    /dev/sda3 6554520 25414829 9430155 83 Linux
    /dev/sda4 * 63 417689 208813+ 83 Linux
    /dev/sda5 25414956 1360287809 667436427 83 Linux
    /dev/sda6 1360287873 1423198349 31455238+ 83 Linux
    /dev/sda7 1423198413 1465144064 20972826 83 Linux
    Partition table entries are not in disk order
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x00025bd3
    Device Boot Start End Blocks Id System
    /dev/sdb1 2048 1953523711 976760832 83 Linux
    I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
    Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
    OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
    List of all partitions:
    No filesystem could mount root, tried:
    Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
    Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
    If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
    If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
    I am really lost as to what is going on, which I'm sure is evident.
    Thanks a lot
    belbo
    Last edited by belbo (2011-08-12 13:31:23)

    Hi. Unfortunately that didn't help.
    So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
    [2011-08-08 23:32] ==> Image generation successful
    [2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
    I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic. 
    Pacman.log relating to the new kernel package below -
    [2011-08-09 00:22] Running 'pacman -Suy'
    [2011-08-09 00:22] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:23] Running 'pacman -Suy'
    [2011-08-09 00:23] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:26] removed python-mygpoclient (1.5-1)
    [2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
    [2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
    [2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
    [2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
    [2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
    [2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
    [2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2011-08-09 00:26] ==> Building image from preset: 'default'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [autodetect]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2011-08-09 00:26] 7079 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] ==> Building image from preset: 'fallback'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2011-08-09 00:26] 23360 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] installed linux (3.0.1-1)
    I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
    It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
    If anybody has other ideas I'd really appreciate it.
    If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
    Any assistance greatly appreciated.
    Thanks
    belbo
    Last edited by belbo (2011-08-08 23:17:49)

  • [SOLVED]nm-applet fails to launch after update

    Hi,
    I've just updated NetworkManager and network-manager-applet:
    [2012-10-31 20:16] upgraded networkmanager (0.9.6.0-2 -> 0.9.6.4-1)
    [2012-10-31 20:16] upgraded network-manager-applet (0.9.6.2-1 -> 0.9.6.4-1)
    After reboot nm-applet fails to launch with the following error:
    ** (nm-applet:6657): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 2 matched rules; type="method_call", sender=":1.48" (uid=1000 pid=6657 comm="nm-applet ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=267 comm="/usr/sbin/NetworkManager --no-daemon ")
    ** Message: applet now removed from the notification area
    ** Message: applet now embedded in the notification area
    ** Message: applet now removed from the notification area
    ** (nm-applet:6657): WARNING **: Failed to register as an agent: (32) Session not found
    When using sudo nm-applet:
    ** Message: applet now removed from the notification area
    ** Message: applet now embedded in the notification area
    ** (nm-applet:6767): WARNING **: Failed to register as an agent: (32) Session not found
    Any idea on what went wrong after the update?
    Thank you in advance!
    EDIT:
    While migrating to systemd, I forgot to replace the ConsoleKit line in /etc/pam.d/slim with:
    session required pam_systemd.so
    ->Problem solved
    Last edited by geekmiki (2012-11-01 00:53:29)

    Related news: https://www.archlinux.org/news/consolek … by-logind/

  • [SOLVED] GDM/Gnome won't start after update

    Today after I run pacman -Suy, GDM/Gnome won't start anymore after reboot. The error message I get after GDM starts is:
    Oh no! Something has gone wrong.
    A problem has occurred and the system can't recover. Please contact a system administrator
    Does anyone have any idea what happened and how can I recover the system?
    Here is the complete log for the update:
    http://bpaste.net/show/209520/
    Here is the journalctl -u gdm log:
    http://sprunge.us/LEOU
    Here is tail -2000 /var/log/messages.log:
    http://sprunge.us/ObWY
    And here is the /var/log/Xorg.0.log:
    http://bpaste.net/show/209549/
    I can't imagine any other log file that might help figure out what happened, let me know if there's anything else.
    Any help is appreciated. Thanks.
    Edit: I stopped gdm, created a ~/.xinitrc and could successfully start Gnome with startx. The problem remains with GDM.
    Edit: The last update solved my problem: http://sprunge.us/RKWA
    Last edited by falmp (2014-04-22 20:38:20)

    I'm not sure my issue is really the same one, but am hoping for some guidance here if possible.  Trying to start GDM gives me the same error message/screen.  After tdm fails I can switch to a console,
    sudo systemctl stop gdm.service
    then
    sudo systemctl start lightdm.service
    and lightdm starts fine.  However, trying to log in to gnome-session gives me the very same error as I had with GDM.  I can log into XFCE just fine.  Attempting to start gnome-ession via startx also gives me the error screen.  Does anyone know how I can diagnose the problem?  Thanks,
    Matt

Maybe you are looking for