[SOLVED] Live USB fail to boot

Booting Arch netinstall and core from a USB fails on waht appears to be "booting the kernel"
After that the screen is flood with what looks like a dump.
The last 5 lines are something like (i quickly copied them down) and each line is preceded by a bunch of numbers:
do_one_initcall +0x35/0x170
? quick_tc86c001_idet +0x22/0x22
kernel_init +0xae/0x13a
? start_kernel +0x35d/0x35d
kernel_thread_helper +0x6/0x10
_ *blinking*
It hangs there and doesn't go away until I reset the machine
iso was torrented but I did a md5 check anyway and then created it using Universal USB installer. It works fine on my laptop.
Hardware
Mother board: Gigabyte GA-Z77-D3H
BIOS: BIOS Date: 02/21/12 15:12:36 Ver: 04.06.05
Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~5.9GHz
Card name: NVIDIA GeForce GTX 560 Ti
NIC:Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
Last edited by glethro (2012-06-17 03:23:54)

glethro wrote:I will leave this as solved as the kernel panic is no longer happening.. But archbot doesn't seem to work either. When in the configure step it shows a fstab file with an entry only for tmp. I booted this and it created the entire file system as read only. I reinstalled and used my own fstab file and was still left with a read-only system.
I successfully installed archlinux using archboot... concerning your fstab issue, I just haven't look this file in the configure step and everything worked fine... did you try editing this file manually without using the archboot installer ?

Similar Messages

  • [Solved] Archboot "2k12-R4" USB fails to boot

    i mounted the iso and copied it to a fat32 formatted usb
    when i boot i chose uefi: usb disk
    then i get an error message :  "No loader found. Configuration files in \loader\entries\*.conf are needed."
    i have a SSD formatted with GPT and a UEFI motherboard (Latest BIOS version)
    Last edited by Heema (2012-10-31 20:51:04)

    srs5694 wrote:Chances are your USB drive is not mounted read-only, but that you need root access to write to it. I don't know what sort of system you're using to access the drive, but logging in as root or using "sudo" before each command (as in "sudo nano /boot/efi/EFI/boot/refind.conf" to edit the file with nano) should work.
    I'm running things in a recent Fedora 17 installation, mostly as root.
    If the drive really is mounted read-only, you should be able to fix it by using an explicit "rw" mount option, as in:
    mount -o remount,rw /dev/sda1 /boot/efi
    Omit the "remount," part if it's not currently mounted, and change the mount point as necessary.
    Turns out it WAS mounted as read-only. I had to repartition the whole stick as FAT32, then make a FAT32 filesystem on it. I had used it for other things prior to this. Now I can write to it.
    Earlier today someone posted his method of getting stuff to work with a UEFI bios, and I'm working my way through it. I've learned quite a bit already. I'm stuck at one point, though, and will soon post on that thread ( https://bbs.archlinux.org/viewtopic.php?id=151773 ) what I've done so far.
    Finally, you can do this from another OS, if you're more comfortable with something else.
    You mean like I've been doing with Fedora? If not something like Fedora, what did you have in mind?
    Thanks for your help!
    Alan

  • [SOLVED] "Filesystem check failed" during boot process

    I was using XFCE on my netbook recently and clicked "shutdown".  It logged out to the command prompt and nothing happened.  Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update...  And moments later it suddenly started the shutdown process.
    Now, whenever I boot up, I see the message below.  I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
    Can anyone suggest what I might need to do to fix the problem?
    rootfs: clean, 11026/246512 files, 477083/984576 blocks
    home: clean, 4386/527280 files, 237183/2105344 blocks
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    ************* FILESYSTEM CHECK FAILED ************
    * Please repair manually and reboot. Note that the root
    * file system is currently mounted read-only. To remount
    * it read-write type: mount -n -o remount,rw /
    * when you exit the maintenance shell the system will
    * reboot automatically.
    Give root password for maintenance
    (or type Control-D to continue):
    Last edited by esuhl (2012-03-27 01:20:07)

    Thank you all for your replies :-)
    hadrons123 wrote:What happens when you do try the suggestion given by it?
    I don't exactly know how I should "repair manually"...  I thought a filesystem check in GParted would have been enough...
    lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
    DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
    Thanks.  I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition.  The check completed, but the problem persists...  I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
    fsck from util-linux 2.20.1
    e2fsck 1.41.14 (22-Dec-2010)
    usr was not cleanly unmounted, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
    Gcool wrote:
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
    I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it?  Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...?  Anyway, the partition details from /etc/fstab are below.
    <file system> <dir> <type> <options> <dump> <pass>
    tmpfs /tmp tmpfs nodev,nosuid 0 0
    /dev/sda1 / ext2 defaults,noatime 0 1
    /dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
    /dev/sdb2 /usr ext2 defaults,noatime 0 1
    I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
    Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
    If I type "umount /dev/sdb2" at the prompt, I get the following error:
    umount: /usr: device is busy.
    (In some cases useful info about processes that use
    the device is found by lsof(8) or fuser(1))
    I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
    I also booted into GParted, but there is no option to "unmount" /dev/sdb2.  There is a "mount" option in the menu, but it is greyed out.  If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
    umount: /dev/sdb2: not mounted
    DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
    No (as shown above).  I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

  • [SOLVED] QEMU-KVM fails to boot if passed q35 machine type

    As I understand it, qemu still uses the PII3X as the default machine type.  I had been using -machine type=q35,accel=kvm for a few weeks to learn more about qemu and KVM.  With this code I could boot a win7 VM and I confirmed the ICH9 chipset appeared in the device manager.
    After a system update I am no longer able to pass that command.  I am using the linux-0.2 image located here.
    If I enter this code, the system boots normally:
    qemu-system-x86_64 -enable-kvm -boot order=c linux-0.2.img
    This however does not work and the bios complains that there is no bootable media found (after waiting for pxe):
    qemu-system-x86_64 -enable-kvm -boot order=c -M q35 linux-0.2.img
    qemu is 1.7.0-2 (built 02/19/14 but this is the only package in pacman's cache)
    seabios is 1.7.3.1-2 (built 09/21/13)
    I actually tried this on two different machines with the same result.  What can I do next to troubleshoot?  Thanks.
    Last edited by gizzard (2014-04-13 15:55:25)

    R00KIE wrote:
    The iso should boot, yes. I did try using -M q35 with a WinXP image I have here and it started to boot (I get blue screens and automatic reboots since lots of things change with -M q35).
    One different thing I have however is the specification of the interface type for disks. Try using "-drive file=/path/to/image,if=scsi" or "-drive file=/path/to/image,if=virtio", that seems to make it work for me, it still might make Win7 complain though.
    I think I'm getting closer thanks to your help.  Adding the if variable allows the debian image to boot using the q35 machine type.  Here are results of some trials (command and result):
    1. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 debian-live-7.4-amd64-standard.iso
    - boots fine
    user@debian:~$ lspci | grep ACPI
    00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
    2. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm debian-live-7.4-amd64-standard.iso
    - fails to boot
    3. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=ide
    - fails to boot
    4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=scsi
    - boots fine
    user@debian:~$ lspci | grep AHCI
    00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
    user@debian:~$ lspci | grep SCSI
    00:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
    4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=virtio
    - boots fine
    user@debian:~$ lspci | grep AHCI
    00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
    user@debian:~$ lspci | grep SCSI
    00:03.0 SCSI storage controller: Red Hat, Inc Virtio block device
    I will try these options with the win7 VM and report back.  I may need to recreate it from scratch, so it might take a little while.

  • [SOLVED] Disk check failed at boot.

    Hello,
    I've got a problem with arch booting. It looks like my cpu doesn't like being left alone fat night. I powered it on today and what I get iss disk check failed error and reboot message. I've tried fsck-ing all partitions and everything seems to be allright. What's more I can mount everything when press ctrl+z when arch tries to reboot and system loading goes on. Any tips? What should I post?
    Last edited by muchzill4 (2010-02-05 10:02:48)

    You have some messed up file systems. As if you didn't know.=O)
    Have you changed fstab? Switched disks around? Try using uuid in fstab instead of '/dev/sdxx'.
    Check this thread http://bbs.archlinux.org/viewtopic.php?id=89857
    and use
    ls -l /dev/disk/by-uuid

  • [SOLVED] Custom Kernel failed to boot

    Hello everyone, this is my first time compiling my own kernel,  I was afraid of breaking the base system so I followed the guides on the wiki
    http://wiki.archlinux.org/index.php/Ker … n_with_ABS
    http://wiki.archlinux.org/index.php/Cus … n_with_ABS
    :: Running Hook [filesystems]
    :: Loading root filesystem module...
    ERROR: Failed to parse block device name for '/dev/sda4'
    ERROR: root fs cannot be detected. Try using the rootfstype= kernel paramter.
    ERROR: Unable to create/detect root device '/dev/sda4'
    I have tried to make an intrid by makeinitcpio -k <my kernel version> -g kernel-SLAB.img but that didn't really do anything.
    So I'm just wondering where I have done wrong, the kernel error messages are pertty cryptic so I have no idea, I would really appreciate any help I can get right now.
    Here's a list of the files that I have used or related to this problem. Thanks all!
    *PKGBUILD
    http://www.ualberta.ca/~blu2/kernel26/PKGBUILD
    *kernel config file
    http://www.ualberta.ca/~blu2/kernel26/config
    *GRUB menu.lst
    http://www.ualberta.ca/~blu2/kernel26/menu.lst
    *mkinitcpio conf
    http://www.ualberta.ca/~blu2/kernel26/mkinitcpio.conf
    *RC.conf
    http://www.ualberta.ca/~blu2/kernel26/rc.conf
    Update, HELP NEEDED
    To be on the safe side, I decided not to apply any EXTRA patch at all, so I used the kernel26 from /var/abs/core/base/kernel26, ONLY changing the package name and the features I wanted, (I changed the generic m686 MARCH to MK8 (amd semperon processor) and KEPT everything else as is to the .config file in /usr/src/linux-2.6.23.12-ARCH/.config
    The package compiled fine but again, but I can't boot properly, giving the same error as previous attempts. The mkinitcpio generated an image that I can boot with the original kernel that came with Arch, but not the kernel I compiled.
    I noticed that during boot, when loading udev, for the original kernel, there's a lot of messages showing modules being detected etc., but for my compiled kernel, there's only one message loading the PS2 keyboard, and nothing else, the HOOK filesystem was ran immediately after that. Is there anyway to capture those initial boot messages? Thanks!
    I'm not sure what I am doing wrong. Any help is appreciated.
    Update
    Kernel sucessfully compiled with the help of fwojciec, thank you.
    Last edited by blu3ness (2008-01-15 05:42:38)

    I can only really tell you how I do it -- I'm not exactly an expert with in-depth knowledge of how kernel works  
    The way I compile the kernel is by adapting the PKGBUILD for the current kernel from the ABS.  I use the script from this thread (http://bbs.archlinux.org/viewtopic.php?id=34815) to rename the kernel and add "make menuconfig" command to the PKGBUILD; I also manually add some patches.  If you want to use this script be careful: is a bit old and last time I've tried it changed "kernel26" to kernel26-[myname] in few some source addresses which obviously was not good but also not really difficult to fix. 
    When I compile the kernel like this I can just do "mkinitcpio -p kernel26-[myname]" and this generates the image without any problems.
    Sorry -- that's the best answer I can give you.  Perhaps somebody else will have ideas what needs to be done using your method to get the kernel to work.  Maybe just looking at the script will give you some ideas...

  • [solved] netfs/sshfs failing on boot

    ok I seem to have a very weird problem and I can not for the life of me figure out a solution.
    I have ssh setup with rsa authentication, I am mounting the sshfs share in fstab according to the wiki.
    [email protected]:torrents/ /mnt/desktop fuse defaults,users,port=22000,reconnect,allow_other 0 0
    On boot netfs fails with the error
    Connection reset by peer.
    But if I let kde finish loading and start a terminal and type in
    /etc/rc.d/netfs start
    it mounts just fine. This is where I don't understand why it will not mount when booting. Because I can not replicate the error once the machine is fully booted. I even tried the sleep 20 trick in netfs.
    my daemon array looks like this.
    DAEMONS=(syslog-ng acpid cpufreq crond hal !net-profiles net-auto-wireless rpcbind nfs-common oss fam sshd ntpd !avahi-daemon netfs)
    Any idea is worth a shot so please amuse me
    Solution: Delete the /root/.ssh/known_hosts file and then re-authenticate the host machine for root user locally. My known_hosts had two entries and the first entry was not available on the network. I assume this is the reason why netfs was failing. The rsa key of the only working host was the exact same before and after in the known_hosts file.
    Last edited by jacko (2009-12-29 16:16:56)

    After booting "swapon -s" give me:
    Filename Type Size Used Priority
    /dev/sda3 partition 8388604 0 -1
    So I assume that the swap partition is actually mounted and activated. However, resuming from hibernation always results in output which says "clearing orphan nodes." I know it has something to do with the swap because I was able to get resume to work by activating swap after I manually mounted swap after booting. I can't remember the exact process I used, whether it be through systemctl or swapon. I will see if I can get figure it out again.

  • Netboot live install fails to boot

    Hi,
    I'm having massive amounts of trouble trying to get a netboot live install to work. The target has GRUB legacy on its HDD. Following https://releng.archlinux.org/pxeboot/ ,
    I copied ipxe.lkrn to /boot/, added a section to menu.lst.
    Reboot, select that new option; it loads correctly ipxe and I get to the graphical menu ( like http://jadelinux.com/images/archimg/1.png ). I select Release64, then any mirror (tried 3), and then I see vmlinuz and archiso.img getting downloaded correctly (I presume), then
    Booting the kernel.
    :: running hook [xyz]
    ... (more hooks)
    :: running hook [archiso_pxe_common]
    IP-Config: eth0 hardware address 00:14..... mtu 1500 DHCP RARP
    And then nothing.
    Fun facts :
    - from either the graphical or text menu, pressing [tab] to try adding kernel options doesn't work, i.e. I can't edit the command before booting ! Swapping keyboards doesn't help
    - from either graph or text menu, pressing Esc gets me to a "boot: " prompt, but I can't enter kernel options from there !
    - from another computer running wireshark, connected to the same hub, the last traffic I see is some (unanswered ?) DHCP requests from the machine stuck at "IP-Config ..." So I thought maybe my router doesn't like these repeat / redundant dhcp query... I tried manually releasing the IP just before that "IP-Config : eth0 ...." line. The only difference I see is that the DHCP query now succeeds ( I see the new assigned IP in the router's table), but the netboot process still doesn't continue !
    Any ideas ?

    If you haven't put too much work into your install yet, I would just reinstall. You can also boot into a live cd, chroot, and reinstall the kernel (pacman -S kernel26).

  • [SOLVED] gdm randomly fails on boot

    Hello everybody,
    I'm new to arch and it took me some time to get everything going, but now it works almost without issues. One not really critical, but very annoying thing is the following:
    Sometimes when booting the system (pure systemd setup), gdm will not start (i. e. no graphical login appears). Instead, I'm directed to tty1, have to log in and do systemctl stop/start gdm.service. I have absolutely no idea why it is working sometimes and sometimes not - it seems like a random phenomenon... Here are the Xorg.log files of the situation when everything's working and when it's not:
    working: http://pastie.org/private/szwlmvl8pcbcaoe0xurba
    failing: http://pastie.org/private/webtcyiyktdwkeke8rb9kq
    The output is not very conclusive, in my opinion. What other logfiles could be helpful?
    Thanks for your help in advance!
    Last edited by michaels (2012-10-24 20:47:19)

    1) to push this one a little...
    2) to give some more information: Checking the output of journalctl thoroughly, I found out that in the not-working case the gdm error messages (GDM display: display lasted xxx seconds / maximum number of X display failures reached) appear between messages from the kernel. Those indicate that the system is still busy loading kernel modules (device drivers for sound and chipset, in particular). Maybe some modules which are needed for the X server to run properly aren't loaded when systemd attempts to start gdm? Then, how to apply a timeout or, even better, a proper dependency to gdm.service unit?
    journal failing: http://pastie.org/private/0k6fjkoievd7k90ytnqdq
    journal working (truncated after gdm started successfully): http://pastie.org/private/orbvisc9hbjgmosxplmtra
    I also tried to upgrade gdm from [testing] with all its dependencies, but this does not work at all.

  • [Solved]USB Flash Installation Media fails on booting kernel

    I've been trying to install Arch on my desktop however the live USB keeps failing to load. The process of loading modules freezes at random points. I've tried acpi=off and mem=2048M, as well as enabled various debugging flags. It doesn't freeze at the same spot on different tries. I  tried loading from RAM and dd'ing the drive, I'm sure the drive works because my laptop can boot off of it. I've ran out of options, can anyone help?
    http://i60.tinypic.com/2rca6bp.jpg
    http://i62.tinypic.com/6z9fsl.jpg
    EDIT: Nevermind nomodeset worked....
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
    Last edited by Pentlander (2014-03-28 01:52:25)

    @DSpider: Please stop FUD about archisolabel and related message. I suggest to learn how boot things really works.
    Reaching such message is because some of these things fails:
    1) User does not setup a filesystem label when copy ISO contents to booteable media (usb drives). In that case, if users insist in not using label, there is a boot option archisodevice=...
    2) Broken/incompatible/unsupported hardware/firmware on Linux and sometimes with udev built-ins (cdrom_id, ...). -> Needed modules not loaded or loaded but not working for boot medium.
    Again, archboot work in a really different way than archiso. It just work on initramfs (rootfs), so there is no need to detect and mount boot media then switch_root.
    So please finish with these false alarms. I already read several of your messages in different places on this forum, repeating the same thing over and over again.
    PS1: Archiso will continue using the great label-system.
    PS2: memdisk is the most discourage method to boot especially in x86_32.

  • [SOLVED] USB Installation Media Boot Problems

    Hi all,
    I'm having trouble creating a live USB stick that my new (to me) HP Elitebook
    2730p laptop can boot successfully. Here is what I've tried so far:
    1. dd with the latest stable Arch installation media
    In other words:
    # dd if=/path/to/archlinux*.iso of=/dev/sdb
    Result: I can boot with the USB stick on my old Dell laptop (which is running
    Arch) without issue, but can't with the new HP. The BIOS will freeze if the USB
    stick is inserted, and will only unfreeze after I remove it.
    2. dd with a recent Arch installation media snapshot
    The snapshot is ``archlinux-2012.06.05_04-00-01-core-x86_64.iso''. I
    install the image to the USB stick with the same dd method above,
    and I get the same behavior: works fine on the old Dell, but freezes the BIOS of
    the new HP.
    3. dd with an old lubuntu iso
    This time, I used an old lubuntu iso
    (lubuntu-11.10-desktop-amd64.iso) with dd. This method
    worked without a problem -- both my old Dell and my new HP would boot it without
    complaint.
    3. unetbootin with the latest stable Arch installation media
    Creating the USB stick with unetbootin allows me to boot the stick with the new
    HP, but the boot fails to the ramfs prompt after ``Waiting 30 seconds for device
    /dev/disk/by-label/ ...'' (notice how there's nothing after ``by-label/'').
    Adding ``vmalloc=448M'' to the end of the unetbootin boot entry makes no
    difference.
    4. Image Writer for Windows
    The ``USB Installation Media'' wiki page suggests using ``Image Writer for
    Windows'' to create a bootable USB stick. I tried this method using Windows 7
    Professional, and the result was the same as attempts 1 and 2: the USB stick
    freezes the HP's BIOS.
    Other notes
    I've checked the md5sums of all the isos I've tried
    I've updated the BIOS on the HP laptop
    I've used the same USB stick for each of the above situations
    The new HP laptop does not have an optical drive, and I don't own an
    external one
    In attempts 1, 2, and 4, I noticed that cfdisk shows that the partition
    that contains the installation files has both the ``Bootable'' and ``NC'' flags
    set. The cfdisk man page says that the latter flag stands for ``Not Compatible
    with DOS or OS/2''. I can actually remove this flag by using the ``Maximize''
    option in cfdisk, which actually makes the USB stick bootable by the HP
    computer's BIOS, but the boot eventually fails to the ``ramfs prompt
    thingy'' after saying ``ERROR: '/dev/disk/by-label/ARCH_201108' found, but the
    filesystem type is unknown''
    In attempt 3 (the lubuntu one), I noticed that cfdisk shows a bit of free
    space in front of the partition that contains the lubuntu files. The ``NC'' flag
    is not present when I run cdisk.
    My current theory is this: I believe my new HP's BIOS is unhappy with the
    ``isohybrid-nature'' of the Arch installation media. Is there any way I can
    confirm this, or obtain ``non-isohybrid'' Arch media?
    As you might imagine, this has been pretty frustrating. Any help would be
    greatly appreciated!
    Daniel
    Last edited by bebeababa (2012-06-10 15:04:43)

    bebeababa wrote:
    DSpider wrote:
    Adding ``vmalloc=448M'' to the end of the unetbootin boot entry makes no difference.
    Duh. That's for booting it from RAM (with MEMDISK) in case it doesn't map the entire file, which for some reason it didn't for the i686 iso on my computer. I probably should've specified it when I wrote the article. I'll add it tomorrow morning.
    Speaking of which, have you tried it?
    https://wiki.archlinux.org/index.php/US … O_from_RAM
    Because you only seem to be using dd ("Image Writer" is the same) and Unetbootin (which had various problems since forever). The correct syntax for dd is:
    $ sudo dd if=archlinux.iso of=/dev/sd[x]
    Warning: Make sure to use /dev/sdx and NOT /dev/sdx1. This is a very common error!
    https://wiki.archlinux.org/index.php/US … _USB_drive
    Haven't tried the ``Boot the entire ISO from RAM'' method yet. I'll give that a shot next.
    The ``Boot the entire ISO from RAM'' method worked like a charm! Thanks,
    DSpider!
    Marking thread [SOLVED].

  • [SOLVED] apache daemon fails to start on boot, but rc.d restart works?

    I installed apache from the official repos and followed the instructions in the wiki for configuring it. I checked to make sure the http user exists, and I /etc/hosts looks good (to me). Upon boot, the daemon fails to start and I can't load local web pages, but running "rc.d restart httpd" works just fine. Since I'd rather not start it manually every time I boot, is there a way to fix this? Also, httpd is the last daemon in my DAEMONS array.
    /etc/httpd/conf/httpd.conf:
    # This is the main Apache HTTP server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "/var/log/httpd/foo_log"
    # with ServerRoot set to "/etc/httpd" will be interpreted by the
    # server as "/etc/httpd//var/log/httpd/foo_log".
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path. If you point
    # ServerRoot at a non-local disk, be sure to point the LockFile directive
    # at a local disk. If you wish to share the same ServerRoot for multiple
    # httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "/etc/httpd"
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 127.0.0.1:80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule authn_file_module modules/mod_authn_file.so
    LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_anon_module modules/mod_authn_anon.so
    LoadModule authn_dbd_module modules/mod_authn_dbd.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_owner_module modules/mod_authz_owner.so
    LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    LoadModule auth_digest_module modules/mod_auth_digest.so
    LoadModule file_cache_module modules/mod_file_cache.so
    LoadModule cache_module modules/mod_cache.so
    LoadModule disk_cache_module modules/mod_disk_cache.so
    LoadModule mem_cache_module modules/mod_mem_cache.so
    LoadModule dbd_module modules/mod_dbd.so
    LoadModule dumpio_module modules/mod_dumpio.so
    LoadModule reqtimeout_module modules/mod_reqtimeout.so
    LoadModule ext_filter_module modules/mod_ext_filter.so
    LoadModule include_module modules/mod_include.so
    LoadModule filter_module modules/mod_filter.so
    LoadModule substitute_module modules/mod_substitute.so
    LoadModule deflate_module modules/mod_deflate.so
    LoadModule ldap_module modules/mod_ldap.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule log_forensic_module modules/mod_log_forensic.so
    LoadModule logio_module modules/mod_logio.so
    LoadModule env_module modules/mod_env.so
    LoadModule mime_magic_module modules/mod_mime_magic.so
    LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule expires_module modules/mod_expires.so
    LoadModule headers_module modules/mod_headers.so
    LoadModule ident_module modules/mod_ident.so
    LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule setenvif_module modules/mod_setenvif.so
    LoadModule version_module modules/mod_version.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
    LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    LoadModule ssl_module modules/mod_ssl.so
    LoadModule mime_module modules/mod_mime.so
    LoadModule dav_module modules/mod_dav.so
    LoadModule status_module modules/mod_status.so
    LoadModule autoindex_module modules/mod_autoindex.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule info_module modules/mod_info.so
    LoadModule suexec_module modules/mod_suexec.so
    LoadModule cgi_module modules/mod_cgi.so
    LoadModule cgid_module modules/mod_cgid.so
    LoadModule dav_fs_module modules/mod_dav_fs.so
    LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule speling_module modules/mod_speling.so
    LoadModule userdir_module modules/mod_userdir.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule rewrite_module modules/mod_rewrite.so
    #php
    LoadModule php5_module modules/libphp5.so
    <IfModule !mpm_netware_module>
    <IfModule !mpm_winnt_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User http
    Group http
    </IfModule>
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents. e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName www.example.com:80
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "/srv/http"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features.
    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "/srv/http">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    # Options FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Order allow,deny
    Allow from all
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
    DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
    </FilesMatch>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "/var/log/httpd/error_log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
    # You need to enable mod_logio.c to use %I and %O
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "/var/log/httpd/access_log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "/var/log/httpd/access_log" combined
    </IfModule>
    <IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock /var/run/httpd/cgisock
    </IfModule>
    # "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/srv/http/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
    </Directory>
    # DefaultType: the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value. If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    <IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    # MaxRanges: Maximum number of Ranges in a request before
    # returning the entire resource, or one of the special
    # values 'default', 'none' or 'unlimited'.
    # Default setting is to accept 200 Ranges.
    #MaxRanges unlimited
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall is used to deliver
    # files. This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    Include conf/extra/httpd-autoindex.conf
    # Language settings
    Include conf/extra/httpd-languages.conf
    # User home directories
    Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    Include conf/extra/httpd-default.conf
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    #PHP
    Include conf/extra/php5_module.conf
    # Note: The following must must be present to support
    # starting without SSL on platforms with no /dev/random equivalent
    # but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    /etc/hosts
    # /etc/hosts: static lookup table for host names
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost laptop
    ::1 localhost.localdomain localhost
    # End of file
    Per the wiki, I also tried commenting out the line that reads
    LoadModule unique_id_module modules/mod_unique_id.so
    Either way, it still fails on boot.
    Last edited by pythonscript (2012-06-10 21:14:44)

    The SIGTERM are from reboots, yes. I'm not absolutely sure that the process isn't running; I just know that I can't access http://localhost immediately upon reboot. I have to restart the httpd daemon, which works fine. How would I be able to tell if it's just hung?
    I checked everything.log, and I don't see anything that leaps off the page to me.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Successfully made thread 1930 of process 1908 (/usr/bin/pulseaudio) owned by '120' RT at priority 5.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Supervising 2 threads of 1 processes of 1 users.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Successfully made thread 1931 of process 1908 (/usr/bin/pulseaudio) owned by '120' RT at priority 5.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Supervising 3 threads of 1 processes of 1 users.
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.gnome.SessionManager method=RegisterClient
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: RegisterClient 106d33cade29b1ba713392593689729000000018320001
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: Adding new client 106d33cade29b1ba713392593689729000000018320001 to session
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): uid = 120
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): pid = 1842
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmStore: Adding object id /org/gnome/SessionManager/Client2 to store
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client2
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): App gnome-settings-daemon.desktop registered
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase INITIALIZATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase WINDOW_MANAGER
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase WINDOW_MANAGER
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase PANEL
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase PANEL
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase DESKTOP
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase DESKTOP
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase APPLICATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting app '/org/gnome/SessionManager/App1'
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): Starting app: /org/gnome/SessionManager/App1
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmAutostartApp: starting gnome-shell.desktop: command=gnome-shell --gdm-mode startup-id=106d33cade29b1ba713392593689681600000018320000
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmAutostartApp: started pid:1936
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase APPLICATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase RUNNING
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmPresence: adding idle watch
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GSIdleMonitor: creating new alarm for positive transition wait=600000
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GSIdleMonitor: creating new alarm for negative transition wait=599999
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost kernel: [ 29.003352] wlan0: no IPv6 routers present
    Jun 9 17:29:31 localhost NetworkManager[765]: <warn> could not commit DNS changes: (0) Could not replace /etc/resolv.conf: Operation not permitted
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Activation (wlan0) successful, device activated.
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: accept_ice_connection()
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: auth_ice_connection()
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Setting up new connection
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: New client '0x7f9ff0004e60 []'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmStore: Adding object id /org/gnome/SessionManager/Client3 to store
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client3
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Initializing client 0x7f9ff0004e60 []
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 []' received RegisterClient(106d33cade29b1ba713392593689681600000018320000)
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmManager: Adding new client 106d33cade29b1ba713392593689681600000018320000 to session
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Sending RegisterClientReply to '0x7f9ff0004e60 [106d33cade29b1ba713392593689681600000018320000]'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Set properties from client '0x7f9ff0004e60 [106d33cade29b1ba713392593689681600000018320000]'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Program = 'gnome-shell'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: UserID = 'gdm'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: RestartStyleHint = 0
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: ProcessID = '1936'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: CurrentDirectory = '/var/lib/gdm'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: _GSM_Priority = 20
    Jun 9 17:29:31 localhost dhcpcd[1640]: eth0: sending IPv6 Router Solicitation
    Jun 9 17:29:31 localhost dhcpcd[1640]: eth0: no IPv6 Routers available
    Jun 9 17:29:33 localhost dhcpcd[1677]: wlan0: sending IPv6 Router Solicitation
    Jun 9 17:29:33 localhost dhcpcd[1677]: wlan0: no IPv6 Routers available
    Jun 9 17:29:33 localhost NetworkManager[765]: <warn> error monitoring device for netlink events: error processing netlink message: Object busy
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:35 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:35 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> (eth0): IP6 addrconf timed out or failed.
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> (wlan0): IP6 addrconf timed out or failed.
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: handling signal 15
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: Found 1 callbacks
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x41c9e0
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Got callback for signal 15
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Logout called
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: requesting logout
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase RUNNING
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase QUERY_END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: sending query-end-session to clients (logout mode: forceful)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: sending QueryEndSession signal to :1.8
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: sending QueryEndSession signal to :1.2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Caught signal 15, shutting down normally.
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: Done handling signals
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received SaveYourselfDone(success = True)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: sms_error_handler (0x1491c70, FALSE, 3, 9, 32771, 0)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: query end session complete
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase QUERY_END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received SaveYourselfDone(success = True)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: sms_error_handler (0x1491c70, FALSE, 3, c, 32771, 0)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect for app 'at-spi-registryd.desktop'
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: unable to find application for client - not restarting
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1428a40
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Using ConsoleKit for session tracking
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase EXIT
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: xsmp_stop ('0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]')
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received CloseConnection
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: in shutdown, not restarting application
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x7f9ff0004e60
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: xsmp_finalize (0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000])
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: in shutdown, not restarting application
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1428ac0
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: last client disconnected - exiting
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase EXIT
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Unreffing manager
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disposing manager
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1473070
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1473150
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/App2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/App1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gdm-simple-slave[1728]: WARNING: Child process 1832 was already dead.
    Jun 9 17:29:43 localhost gnome-session[1970]: EggSMClient-WARNING: Desktop file '/home/ak5791/.config/autostart/dropbox.desktop' has malformed Icon key 'dropbox.png'(should not include extension)
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2022 of process 2022 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 4 threads of 2 processes of 2 users.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2023 of process 2022 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 5 threads of 2 processes of 2 users.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2024 of process 2022 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 6 threads of 2 processes of 2 users.
    Jun 9 17:29:44 localhost dbus[739]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper)
    Jun 9 17:29:44 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Jun 9 17:29:44 localhost dbus[739]: [system] Activating service name='org.freedesktop.colord-sane' (using servicehelper)
    Jun 9 17:29:45 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.colord-sane'
    Jun 9 22:29:46 localhost rtkit-daemon[1910]: Successfully made thread 2079 of process 2079 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jun 9 22:29:46 localhost rtkit-daemon[1910]: Supervising 7 threads of 3 processes of 2 users.
    Jun 9 17:29:46 localhost pulseaudio[2079]: [pulseaudio] pid.c: Daemon already running.
    Jun 9 17:29:48 localhost dbus[739]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
    Jun 9 17:29:48 localhost udisksd[2110]: udisks daemon version 1.94.0 starting
    Jun 9 17:29:48 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.UDisks2'
    Jun 9 17:29:48 localhost udisksd[2110]: Acquired the name org.freedesktop.UDisks2 on the system message bus
    Jun 9 17:29:48 localhost kernel: [ 46.319778] gnome-shell-cal[2103] trap int3 ip:7ff3f55b85e1 sp:7fff94941890 error:0
    Jun 9 17:30:19 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:40:53 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:47:15 localhost kernel: [ 1092.983585] usb 8-1.4.1: new high-speed USB device number 8 using ehci_hcd
    Jun 9 22:47:15 localhost mtp-probe: checking bus 8, device 8: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1/8-1.4/8-1.4.1"
    Jun 9 22:47:15 localhost mtp-probe: bus: 8, device: 8 was not an MTP device
    Jun 9 22:47:15 localhost kernel: [ 1093.132002] usbcore: registered new interface driver uas
    Jun 9 22:47:15 localhost kernel: [ 1093.135601] Initializing USB Mass Storage driver...
    Jun 9 22:47:15 localhost kernel: [ 1093.135785] scsi6 : usb-storage 8-1.4.1:1.0
    Jun 9 22:47:15 localhost kernel: [ 1093.135905] usbcore: registered new interface driver usb-storage
    Jun 9 22:47:15 localhost kernel: [ 1093.135913] USB Mass Storage support registered.
    Jun 9 22:47:16 localhost kernel: [ 1094.137579] scsi 6:0:0:0: Direct-Access Kingston DT 101 G2 1.00 PQ: 0 ANSI: 2
    Jun 9 22:47:16 localhost kernel: [ 1094.140133] sd 6:0:0:0: [sdb] 15636304 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Jun 9 22:47:16 localhost kernel: [ 1094.140631] sd 6:0:0:0: [sdb] Write Protect is off
    Jun 9 22:47:16 localhost kernel: [ 1094.140634] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
    Jun 9 22:47:16 localhost kernel: [ 1094.141128] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.141132] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.144916] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.144921] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.146680] sdb: sdb1
    Jun 9 22:47:16 localhost kernel: [ 1094.151407] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.151411] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.151414] sd 6:0:0:0: [sdb] Attached SCSI removable disk
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Version 2012.1.15 external FUSE 29
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Mounted /dev/sdb1 (Read-Write, label "kingstonGB", NTFS 3.1)
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177,uhelper=udisks2
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Global ownership and permissions enforced, configuration type 7
    Jun 9 22:47:17 localhost udisksd[2110]: Mounted /dev/sdb1 at /run/media/ak5791/kingstonGB on behalf of uid 1000
    Jun 9 22:47:28 localhost dbus[739]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper)
    Jun 9 22:47:28 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.UDisks'
    Jun 9 22:47:46 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:57:59 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 23:01:02 localhost /USR/SBIN/CROND[5529]: (root) CMD (run-parts /etc/cron.hourly)
    Jun 9 23:21:02 localhost -- MARK --
    All I notice is that my system's time is having a few problems, since you'll notice that events occur at 22:00 and change, then 17:00 and change, then back to 22:00 and change afterwards. Could this be the problem? I've had the CMOS batteries peg out on me suddenly in the last few weeks. I would hope this sytem is not also suffering a similar fate. Nothing else was happening on my system except for the standard processes from /etc/rc.conf and other standard ones, since I've just been rebooting, checking the logs, then posting here.

  • [SOLVED] Arch Linux Duke (2007) Fails to Boot

    Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
    I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch.  It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
    After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
    A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
    RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
    RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
    If you have read this far, you are a trooper.  Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
    :: Loading udev events                [Pass]
    :: Mount root Read-only
    :: Checking file systems
    This is where it stops.
    The next thing I see is:
    /dev/sda6
    The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
        E2fsck –b 8193 <device>
    I then get a sort of character based splash screen that says
    **********FILE SYSTEM CHECK FAILED ****************************
    *   Please repair manually and reboot. Note that the root file system
    *   is currently mounted read-only. To remount it read-write, type:
    *   mount –n –o remount,rw /.  When you exit the maintenance
    *   shell, the system will reboot automatically
    Give root password for maintenance
    At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
    /dev/sda6 on / type ext3 (rw)
    This is exactly the root partition that the start up complains about. It is clearly there.  I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
    At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
    Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
    # mknod “/dev/root2” b 3 6   
    (“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
    Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
    All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
    I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
    By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
    image = /boot/vmlinuz26
       root = /dev/sda6
       label = ArchLinux-Duke
       initrd = /boot/kernel26.img
       read-only
    I am stumped. Thanks in advance for any and all pointers you may be able to offer.
    Last edited by mac57 (2014-06-02 17:42:21)

    Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
    At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
    So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
    Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next.  This is my guess anyway.
    I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the  Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
    It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
    Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

  • Trouble Booting to Ubuntu Live USB on T440

    Hey,
    I am having trouble booting to a Ubuntu Live USB on my T440. I turn on the laptop, press enter to interrupt the normal boot, and press F12 to select another boot option. But after selecting the appropritate USB, the screen goes black for a couple of seconds and then returns to the boot selection. It will not boot from the Ubuntu USB, only to the preinstalled Windows 8.
    Other guides have recommended disabling Secure Boot (I have done this, it has not worked); others suggest enabling Secure Boot but changing to Legacy Boot (this didn't work for me either).
    Once I can successfully boot to the USB, I will be installing Ubuntu, replacing Windows all together. I don't need help with that; just getting the computer to boot from the USB would be great.
    Thanks.
    Solved!
    Go to Solution.

    Fixed. My boot USB was made with Ubuntu's Startup Disk Creator (on my other Ubuntu system). On a hunch, I made another boot USB using Linux Pen Drive on the Windows 8 machine. That one worked. I presume it was related to the format of the USB (the working one being FAT32).
    So if anyone wants to easily install a Linux distibution on a T440, make your boot USB on a Windows machine.

  • Arch boot using live-usb freezes on "Triggering uevents.."

    I have been trying to install Arch on my new machine but am having issues getting it to work. I have in the past successfully installed the OS on my laptop, but for some reason it just simply will not work with my desktop.
    Relevant Hardware:
    MSI Z87 Gaming Motherboard (UEFI)
    Intel i5 4690k
    I do know, however, that the bios on my laptop is not of the UEFI type which could be the underlying issue here. To make the live-usb I do exactly as the guide states and use USB-Writer. I have also tried Universal-USB-installer and Rufus in an effort to get a working live-usb but all have the same issue in that they appear to freeze at the same spot.
    An interesting note: I am able to successfully boot from my live-usb on my laptop (the very same that fails on my desktop). Therefore, I must be missing something specific to a piece of hardware my machine has or the fact that it uses UEFI. I was able to successfully create a gparted bootable usb to partition my drive, but the Arch image does not work so easily for some reason.
    Any ideas?
    Last edited by sherrellbc (2014-11-27 03:51:34)

    On the beginner page here: https://wiki.archlinux.org/index.php/be … t_problems
    It gives a few troubleshooting ideas, specifically if your boot freezes.I just wanted to add here that I added "acpi=off" at the end of the string as the guide states and it boots now. I had tried this earlier but did some tweaking in my bios settings regarding boot settings so I am not sure if this alone did this trick.
    Last edited by sherrellbc (2014-11-27 04:29:10)

Maybe you are looking for

  • Obiee 11g error

    Hi All, I am using obiee 11g for a demo project.When i a run the a report just with 2 columns from 1 from dimension and 1 from fact.It is throwing an error.the error message is Query Failed: [nQSError: 14025] No fact table exists at the requested lev

  • Can't connect to network (wireless)

    Hello, I have a Dell Vostro 1500 with an Intel pro 3985 wireless card. The driver that comes with the latest kernel is installed. Running lsmod shows iwl3945. ifconfig wlan0: wlan0 Link encap:Ethernet HWaddr 00:1C:BF:99:B1:DE UP BROADCAST MULTICAST M

  • Best option for Webcam for quality video

    I'm looking to put together a few short movies for my family. It's a bucket list thing so I've got a Mac mini & I'm trying to work out the best webcam to buy. I was about to buy the C920 but then realised the limited capability. I also have all the a

  • How do I fix an "OSStatus error -19160"?

    How do I fix an "OSStatus error -19160" in QuckTime?

  • Applet not running on Firefox10

    Hi, I am facing an issue with Firefox10 where I am trying to run a jnlp program which downloads certain jar files and after downloading shows me the screen (applet). On Firefox15, I am able to run the same but on Firefox10, I am facing certain issues