[SOLVED] Two Archlinux logos show up during boot

Hi! I recently installed Archlinux on my HP Mini 110 netbook via a usb core image. I can see an Archlinux logo at the top of the screen during boot using the usb stick, but this is not the case in my installation. When booting up my netbook, I can see two Archlinux logos side by side. As far as I can remember, this does not happen at the first time I boot my machine with a fresh install. At that time, I was using vga=773 kernel boot option at my menu.lst, but my laptop monitor does not support this and grub asks me for a new parameter instead. I'm sorry but I really don't remember clearly how it happened, as it did not bother me at first, but it's getting quite annoying that you see something wrong everytime I boot up.
The right way:
A
boot messages
scrolling on
the
screen
What shows up in my case:
AA
boot messages
scrolling on
the
screen
I have already corrected the vga option to suit my laptop monitor's specification (1024x576 is vga=866) but the problem still persists. I have also tried other vga options, both supported and unsupported by my laptop monitor, to no avail. Does this have something to do with intramfs, or do I have to recreate the logo? As far as I can remember, I mkinicpio a couple of times: once during installation, and once during post-installation configuration.
Last edited by avendael (2010-04-13 03:26:34)

dcc24 wrote:
skottish wrote:Intel's hyperthreaded CPUs sometimes report 'cores' that are not physical. It varies from model to model.
That would explain the difference between 2 and 4, but 3?
Do your physical cores seem like they are working properly? I really don't understand much about how it works, but this is the first that I've heard of an odd number of cores on a multi-core system being reported.

Similar Messages

  • [solved] Hard disk security parameters freeze during boot

    Hi fellow archers!
    Currently I am trying to pin point a problem I have. I have an old PC of mine setup as some kind of experimental playground. My problem is that the security options of my driver become frozen during powering up this PC. It is a fresh and empty Arch installation with just sshd running and no services has been installed that should set the drive security-freeze. I am trying to figure out who is locking it, my current suspicion is the mainboard/BIOS itself, but I need to be sure, that there is no script during executing Arch boot setting the freeze parameter. -- Oh if someone one if the ASUS A8N32-SLI is doing such nasty stuff, it would be great to know.
    Thanks in advance for your feedback
    Last edited by jpk (2011-10-15 13:19:20)

    Hi, it's not really a fix for the problem, but I now know what happens. It is really the mainboard BIOS who freezes the security state of my hdds. So what I did was to build a power switch for my hdd. During boot I switch the power and linux will detect the sata drive (haven't tested it with IDE drives) and I can work with it.

  • Apple logo takes a while to show up during boot up

    I noticed that when I restarted my MacBook today, the Apple logo takes a while (20-30 seconds) to just show up before the spinning gear shows up.
    I'm not sure what caused this. Any ideas? Thanks.
    Things I've tried
    1. Repair disk permissions
    2. Verify disk
    3. Reset PRAM
    4. Boot into Safe Mode
    5. Make sure Mac OS X 10.6.5 is the startup disk

    It sounds normal for me. My iMac always does that. But my sample size is a bit low; I think I have only rebooted it five or six times since I first received it in August.
    Are you using Boot Camp? If not, rebooting is rarely necessary. Try using sleep mode instead of shutting down. Waking up from sleep mode is really fast.

  • [SOLVED] Imapd does not start (only during boot process)

    I'm running a courier-imap server.
    A few days ago I noticed I did not receive any mails anymore. Then I found my imapd daemon was not running anymore.
    I then stopped the daemon process together with the xinetd daemon (which lets me connect to my imap server via my local network).
    I restart from a terminal both daemons (imapd an xinetd) and ... everything is up and running ! Note that I have to stop xinetd too because only stopping imapd and restarting doesn't help.
    I reboot my PC ... again no imapd anymore. During the boot process I do not get any error message though ...
    I'm completely puzzled
    The problem started when I upgraded to the linux 3.0.1 kernel ...
    Last edited by Strider (2011-08-14 07:59:41)

    I managed to get the problem solved by removing and re-installing the courier-imap package. Don't know why that solved it though ...
    Last edited by Strider (2011-08-14 07:59:05)

  • [SOLVED] Borked systemd setup -- dbus errors during boot; can't login

    I have error messages very similar to this post. Unfortunately, as the author states, he never persisted in solving it but instead re-installed from scratch. I'd rather not do that.
    For reference, I have a pure systemd setup -- no rc.conf file, no initscripts package, etc.
    At boot I get the "Welcome to Arch!" messages followed by the various [OK] lines and then I get blindingly fast repeating lines about dbus not starting and attempting to restart it too quickly. If I walk away for about 1-2min, I finally see a login screen, but after entering my username/password, it just sits there and does nothing.
    As for suspects... I had systemd working fine.
    -- I updated some packages (not more than a few days worth and I'd have to check the list)
    -- I also took care of manual updates to some .pacnew files I periodically check for. In this group were some biggies: group, shadow, and passwd. I did recall the odd bit about uuidd changing from uid 995 to 68, but in reading about that since then, it doesn't seem to be a big deal.
    I've been booting in by appending
    systemd.unit=emergency.target
    to the kernel line, but my exploration hasn't been all that helpful. `journalctl since=date` reveals the errors, but I don't get much information about why dbus is having issues starting.
    emergency.target also doesn't seem to be that helpful since I can't do anything with a read-only system. I'd love some suggestions about what, specifically, to check for before I reboot from Windows back into Arch and record more careful notes, probably by jotting notes onto a flash drive. Any places to start? For reference, I've done:
    -- systemctl status dbus: lists as inactive (dead) and simply shows the errors I see at boot (failed to start)
    -- systemctl list-units
    -- systemctl list-unit-files
    -- journalctl and looking around for instances of fail or failed or dbus
    If I start systemd-logind.service or dbus.service, it displays a status message about running fsck and then takes me to a login prompt automatically. Then I can type in my username and password and then there's nothing after that. No prompt, just an apparent hang.
    Thanks for any suggestions -- I'll take them and then collect more detailed results and report back.
    Thanks!
    Last edited by jwhendy (2012-11-08 16:07:33)

    As I wondered, I think it's a problem with passwd. I don't have a dbus entry and must have missed it when I was copying things around between my version and the .pacnew. Downloading an install disc now since I can't seem to change it from the recovery console due to mounting root read-only.
    I'd love to know of a way to boot that avoids starting dbus and other things that might break while still having read/write access to root. Will mark solved once I update /etc/passwd and reboot.

  • Just switched from Lion to Mountain Lion - Now terminal shows up during boot up and when shutting down. How do I stop this?

    Just switched from Lion to Mountain Lion - Now, when I start my machine, the terminal shows up and runs through it's thing and then the normal screen shows up. This also happens when I shut down as well - the terminal shows up again. I have a MAC running Mountain Lion at work and this doesn't happen so I'm assuming this is not normal.
    While my machine still runs, it's annoying and I fear this will lead to problems if I don't address the situation. How do I ge this to stop? Any help would be greatly appreciated.

    They are being sent to the All Mail folder.  The inbox is pretty much unaffected.
    I don't want to hide the All Mail folder and forget about it.  I am after the messages gone forever.  Especially from the All Mail folder.
    I'm the kind of person who uses email like sms.  I use it to contact people annd delete 95% of the messages after reading.  I don't want them archived.  I don't want them stored in the All Mail folder.  I want them totally gone.
    And yes it seems Mail is downloading all my messages over and over.  So my question is how to stop the messages being stored/archived and to instead be totally deleted.
    In the gmail settings I found:
    Auto-Expunge off - Wait for the client to update the server.
    When a message is marked as deleted and expunged from the last visible IMAP folder:  Immediately delete the message forever.  Instead of archiving it like I had set before.  I'm not 100% sure if that'll fix the issue I am having.  I'm sure you'll be able to tell me if I am on the right track.
    And thanks for the quick reply.

  • My iPad Mini iOS7 is showing only Apple Logo which happened during software update. I tried to restore using iTunes but it asking me to response from iPad. But my ipad only shows apple logo. How can i response? How to solve this problem?

    My iPad Mini iOS7 is showing only Apple Logo which happened during software update. I tried to restore using iTunes but it asking me to response from iPad. But my ipad only shows apple logo. How can i response? How to solve this problem?

    FORCE IPAD INTO RECOVERY MODE
    1. Turn off iPad
    2. Turn on computer and launch iTunes (make sure you have the latest version of iTune)
    3. Plug USB cable into computer's USB port
    4. Hold Home button down and plug the other end of cable into docking port.
    DO NOT RELEASE BUTTON until you see picture of iTunes and plug
    5. Release Home button.
    ON COMPUTER
    6. iTunes has detected iPad in recovery mode. You must restore this iPad before it can be used with iTunes.
    7. Select "Restore iPad"...
    Note:
    1. Data will be lost if you do not have backup
    2. You must follow step 1 to step 4 VERY CLOSELY.
    3. Repeat the process if necessary.

  • During boot Yosemite shows a grey screen with the Apple logo and a progress bar - is this normal?

    During boot Yosemite shows a grey screen with the Apple logo and a progress bar - is this normal?

    Same here after upgrade yesterday. 
    I can get OS utilities up using CMD R or holding the shift key (eventually), but if I simply then reinstall the OS will it not loose everything on my drive? I do have it backed up on Time Machine? What a nightmare - Apple Support does suck.  I am not paying £25 for them to call me to tell me how to fix a bug in their OS software upgrade.  Any help
    Also does anyone know if it is possible to use time machine to go back to Snow Leopard? I have wasted much of the day on this now
    Cheers
    Simon

  • How can I get the arch logo in console/terminal during boot?

    Hello
    I just installed arch as my first linux, and I would like to get the arch logo in the top left corner during boot, like on the following screenshot:
    http://i4.photobucket.com/albums/y132/s … h_boot.png
    uname  -a:
    Linux 3.6.6.1-ARCH #1
    syslinux bootloader
    How can I do that?
    Thanks a lot and greetings

    I'm not sure what's the situation now, but you may not get the logo - neither the penguin nor Arch logo:
    * https://bbs.archlinux.org/viewtopic.php?id=120516
    * https://bbs.archlinux.org/viewtopic.php?id=122778
    * https://bbs.archlinux.org/viewtopic.php?id=124730

  • I am getting frequent lock-ups and blue screens during boot up. The lock ups occur during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button. Ideas?

    I am getting frequent lock-ups and blue screens during boot up on my Mac Pro.  The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
    I had the Mac Defender malware and I have used apple jack but still having issues.

    I am getting frequent lock-ups and blue screens during boot up on my Mac Pro.  The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
    I had the Mac Defender malware and I have used apple jack but still having issues.

  • [SOLVED][Duplicate]Garbage output during boot

    During boot you can see something like "666666666666" constantly printed amoung other messages:
    http://i.imgur.com/2YOShSMl.jpg
    This continues even after we are booted and ready to login into the system:
    http://i.imgur.com/THZWZT4l.jpg
    The first time I've noticed this was about half a year ago. It didn't really bothered me, because kdm still worked and you could successfully log into system.
    Yesterday, however, I tried install arch on my new ssd and bumped into this problem even during booting from usb drive with installation iso.
    Any ideas what could this be? I'm not even sure where to look for the root of the problem.
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
    Last edited by konart (2013-06-07 17:30:39)

    Could it possibly be the Logitech G710+ ?
    UPD:
    Oh, I see now: https://bbs.archlinux.org/viewtopic.php?id=153752 Thanks for your directions
    Last edited by konart (2013-06-06 10:34:08)

  • Hard disk not detected during booting or also it does not show in boot menu.

    hard disk not detected during booting or also it does not show in boot menu please tell

    you may have a failed hard drive or bad cables, i would check first to see if the hard drive is powering on. if it doesn't try a different power connection, and if it still doesn't start spinning i would say that it is bad and get a new hard drive. If
    it does start spinning and just isn't being recognized, try a different sata port if you have the option or a different sata cable all together.

  • Deep Sleep - Is it normal to show a grey progress bar during boot?

    I've just downloaded the Deep Sleep widget from Axionic Labs. So far, it works wonderfully.
    I really like the idea of Deep Sleep. No power consumption, quick boot and same state it was before Deep Sleeping.
    However, I noticed that when I power my MBP on (after Deep Sleeping) it shows the grey boot screen with a grey bar below being filled. Actually, it's several small grey bars being filled.
    Is it normal to show those grey bars when your MBP is booting after a deep sleep?
    Here's a photo that I took of it: http://img198.imageshack.us/img198/2039/dsc00787uz.jpg

    davidcmc wrote:
    Here's a photo that I took of it:
    ...and here's Apple's own photo of it, taken from this linked kbase article:
    ...so, yes, it's normal.

  • [SOLVED] How to get NetworkManager start on background during boot?

    NetworkManager has always taken relatively long time to start during boot, presumably waiting for wlan to connect.
    $ systemd-analyze blame
    7.682s NetworkManager.service
    Previously I was able to get it to start on background by removing /etc/systemd/system/multi-user.target.wants/NetworkManager.service
    This prevented multi-user.target from waiting for NM to start and it would continue to connect on background while my boot finishes.
    However, after upgrade to networkmanager-0.9.10.0-2 that doesn't seem work any more.
    If I remove the .service file from multi-user.target.wants/, NetworkManager doesn't start during boot at all.
    enabling NetworkManager.service creates these symlinks:
    # systemctl enable NetworkManager
    Created symlink from /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service to /usr/lib/systemd/system/NetworkManager.service.
    Created symlink from /etc/systemd/system/multi-user.target.wants/NetworkManager.service to /usr/lib/systemd/system/NetworkManager.service.
    Created symlink from /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service to /usr/lib/systemd/system/NetworkManager-dispatcher.service.
    looks like enabling any other basic systemd unit links the .service file to multi-user.target.wants/ as well..
    How can I enable NetworkManager.service during boot without multi-user.target.wants/, and get it to start on background again?
    any ideas appreciated :)
    Last edited by ooo (2014-08-03 12:13:28)

    Okay, looks like this can be resolved by simply changing the NetworkManager.service type from dbus to forking.
    $ systemd-analyze blame
    173ms NetworkManager.service
    Here's the modified service file if anyone's interested:
    place it in /etc/systemd/system/NetworkManager.service
    [Unit]
    Description=Network Manager
    Wants=network.target
    Before=network.target
    [Service]
    Type=forking
    PIDFile=/var/run/NetworkManager.pid
    BusName=org.freedesktop.NetworkManager
    ExecStart=/usr/bin/NetworkManager --pid-file=/var/run/NetworkManager.pid
    # NM doesn't want systemd to kill its children for it
    KillMode=process
    [Install]
    WantedBy=multi-user.target
    Alias=dbus-org.freedesktop.NetworkManager.service
    Also=NetworkManager-dispatcher.service
    You need to disable NetworkManager.service before creating the file and enable it after so that systemd links the file from /etc/systemd instead of /usr/lib/systemd,
    there may be simpler way but I can't be bothered to go through systemd manuals any more.
    Note that this will probably break any systemd .service that actually requires network, although that was the case with my previous workaround as well.
    I won't guarantee this will work for you and won't set your machine on fire. If you have issues, simply remove the file and re-enable to go back to default

  • [solved]How to unlock LUKS using keyfile on usbdrive during boot?

    Hi all,
    I would like some advise for booting encrypted partitions using kefiles on a flashdrive. I'm setting up a Intel Atom based homeserver, and and want my data to be encrypted in case the server gets stolen. To save some encryption overhead I prefer to leave root unencrypted and only encrypt /home, and if this works, later on /var, /tmp and swap as well. My plan is to have a keyfile on a flash thumbdrive, and only have the thumbdrive plugged in while booting.
    I have read the dm-crypt wiki page, but it assumes an encrypted root, and this approach won't work in my situation, where only non-root mountpoints are encrypted. If i put 'ASK' in /etc/crypttab I get prompted for the passphrase and the LUKS container unlocks and mounts fine. I can also unlock the LUKS container manually using the keyfile that I created. However when I put the path to the keyfile in /etc/crypttab instead of 'ASK', and let the usbdrive automount using an udev rule the unlock at boot fails. It seems that my udev rule is only executed when I plug in a drive after booting, not when it is already plugged in during boot. How would I accomplish this? Mount it with fstab and automatically unmount it after booting, or some entirely different way?
    my /etc/fstab:
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    /dev/sda1 / ext4 defaults 0 1
    /dev/sda2 swap swap defaults 0 0
    /dev/mapper/home /home ext4 defaults 0 1
    /etc/crypttab:
    home /dev/sda3 /media/usbhd-sdc1/keyfiles/arch_server_-_home.key
    /etc/udev/rules.d/01.usbdrive_automount.rules (sdb is a second, currently unused harddisk):
    KERNEL=="sd[b-z]", NAME:="%k", SYMLINK+="usbhd-%k", GROUP:="users", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", SYMLINK+="usbhd-%k", GROUP:="users", NAME:="%k"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", PROGRAM=="/sbin/blkid -t %N", RESULT=="vfat", RUN+="/bin/mount -t vfat -o rw,noauto,flush,dirsync,noexec,nodev,noatime,dmask=000,fmask=111 /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
    ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
    <edit>
    Okay I have found a solution. The trick was to make sure the usbstick gets mounted first, so the keyfile is available for the unlocking/mounting during boot. To do so I have added 'usb' to the hooks line in /etc/mkinitcpio.conf and recompiled the initramfs as described in the wiki link above.
    Next I changed my /etc/udev/rules.d/01.usbdrive_automount.rules a little so that the mountpoint of the usbdrive stays after unplugging it:
    KERNEL=="sd[b-z]", NAME:="%k", SYMLINK+="usbhd-%k", GROUP:="users", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", SYMLINK+="usbhd-%k", GROUP:="users", NAME:="%k"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", PROGRAM=="/sbin/blkid -t %N", RESULT=="vfat", RUN+="/bin/mount -t vfat -o rw,noauto,flush,dirsync,noexec,nodev,noatime,dmask=000,fmask=111 /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k", OPTIONS="last_rule"
    #ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
    #ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
    /etc/fstab:
    The usbdrive is put above the encrypted partition to make it get mounted first:
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    /dev/sdc1 /media/usbhd-sdc1 ext2 defaults 0 0
    /dev/sda1 / ext4 defaults 0 1
    /dev/sda2 swap swap defaults 0 0
    /dev/mapper/home /home ext4 defaults 0 1
    /etc/crypttab:
    home /dev/sda3 /media/usbhd-sdc1/keyfiles/arch_server_-_luks.key
    So now I plug in the flashdrive, turn on the server, unplug the flashdrive and udev automatically unmounts the flashdrive while leaving the mountpoint /media/usbhd-sdc1 for the next boot.
    </edit>
    Last edited by rwd (2009-12-04 19:36:14)

    graysky wrote:@ratcheer - You can try now if it's a major pain in the balls by enabling [testing] and using the updated linux package.
    If you do enable testing make sure you aren't like myself: I'm not competent enough to enable testing..
    Edit:
    To elaborate a bit.  If you enable testing and then just do a "pacman -Syu" then you are going to pull in all sorts of packages you may not want and it may be complicated to get rid of later.  To avoid this I would enable testing, do this:
    sudo pacman -Syy
    sudo pacman -S testing/linux
    So it would pull in the absolute minimum that I wanted from testing.  Then I would disable the testing repository and pacman -Syy again.  That would convert the new linux package and packages it requires to manual packages.  E.g. they would be shown under "pacman -Qm"
    Because once you start pulling packages in from testing it is almost a one-way street.  As I instructed above, that is my gross understanding.  I don't use testing at all, it is supposed to be used if you are actively testing Arch and providing feedback while doing so.
    Last edited by headkase (2012-10-03 01:51:51)

Maybe you are looking for