[SOLVED] No display during boot
Sometimes after the reboot my laptop looses display between the messages "Booting the kernel" and "Running early hook (udev)". This happens in 98% cases of reboot. Even if I shutdown the computer and start again, it won't start; I've to keep the laptop shutdown for 5-10 min then my laptop starts nicely. When the computer looses display GPU fans speed begins too increase.
Last edited by ansh_kumar (2014-09-26 12:14:53)
journalctl is unable to log when the problem arrises. In the following log the problem took between 23:31 and 23:59 (no log for the problem)
Sep 24 23:31:50 ansh systemd[1]: Starting Final Step.
Sep 24 23:31:50 ansh systemd[1]: Reached target Final Step.
Sep 24 23:31:50 ansh systemd[1]: Starting Reboot...
Sep 24 23:31:50 ansh systemd[1]: Shutting down.
Sep 24 23:31:50 ansh systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Sep 24 23:31:50 ansh systemd-journal[137]: Journal stopped
-- Reboot --
Sep 24 23:59:25 ansh systemd-journal[138]: Runtime journal is using 8.0M (max allowed 168.3M, trying to leave 252.5M free of 1.6G available â current limit 168.3M).
Sep 24 23:59:25 ansh systemd-journal[138]: Runtime journal is using 8.0M (max allowed 168.3M, trying to leave 252.5M free of 1.6G available â current limit 168.3M).
Sep 24 23:59:25 ansh kernel: Initializing cgroup subsys cpuset
Sep 24 23:59:25 ansh kernel: Initializing cgroup subsys cpu
Sep 24 23:59:25 ansh kernel: Initializing cgroup subsys cpuacct
Sep 24 23:59:25 ansh kernel: Linux version 3.14.18-1-lts (nobody@var-lib-archbuild-extra-x86_64-barthalion) (gcc version 4.9.1 (GCC) ) #1 SMP Sat Sep 6 18:15:52 UTC 2014
Sep 24 23:59:25 ansh kernel: Command line: BOOT_IMAGE=../vmlinuz-linux-lts root=/dev/sda3 rw video=SVIDEO-1:d initrd=../initramfs-linux-lts.img
Sep 24 23:59:25 ansh kernel: e820: BIOS-provided physical RAM map:
And dmesg is only providing the current boot log (nothing about the failed boot).
Adding video=SVIDEO-1:d to command line parameter did not work. How to enable a ssh server. Can you provide a link for a detailed explanation because I know nothing about it.
Laptop specification :
Video Graphics : AMD Radeon HD 7640G + 7670M Dual GPU (1 GB DDR3 dedicated)
Microprocessor : 3 GHz/2.1 GHz AMD Quad-Core A8-4500M
Microprocessor Cache : 4 MB L2 cache
Memory : 4 GB 1600 MHz DDR3
Last edited by ansh_kumar (2014-09-24 18:49:58)
Similar Messages
-
2006 Mac Pro + NEC 3090 - grey screen not displayed during boot
I have a September '06 Mac Pro 1,1 (Woodcrest variant) hooked up to an NEC 3090 30" LCD monitor, running OS X 10.5.7. Previously, I was using an Eizo S2110W 21" LCD; turning the monitor and computer on would cause the following to be displayed (in order):
1. Light grey background with dark grey Apple logo with spinning thing.
2. Solid blue background.
3. Leopard wallpaper.
4. Log-in dialogue.
Since using the NEC, the grey screen is not displayed at all: the display stays blank until the blue screen is displayed, and then the Leopard wallpaper and so on. This is using the 2560x1600 native resolution of the display, and has occurred using both 10.5.6 and 10.5.7.
If I change the resolution to 1280x960 and boot, the grey screen is displayed. If I change it to 1600x1200, I get weird corruption on-screen during the period when the grey screen should be displayed; for some reason, this includes part of the desktop wallpaper I was using before I rebooted.
Resetting the non-volatile RAM using Command-Option-P-R works for the very first time I boot the computer, though the grey screen is displayed at very low resolution. If I reboot from the log-in dialogue immediately afterwards, normal behaviour occurs - i.e. the blank screen.
The upshot of all of the above is that if I want to boot into Windows, or install OS X (e.g. when Snow Leopard comes out), I have to remember to boot into my existing OS X installation, change resolution, reboot whilst remembering also to hold down the ALT/Option key. It would be much easier if I could do away with having to change resolution.
I have tried connecting the monitor to a PPC Mac mini at 1600x1200 (it won't go any higher), using Tiger 10.4.11 (not sure of exact version - the latest). At this resolution, the grey screen is displayed.
Using a '08 MacBook Air (first generation) and the supplied DVI adapter, also at 1600x1200, nothing is displayed on the NEC until I get to the log-in screen. This occurs if the NEC is set to be the primary display or the secondary one - the only difference is where the log-in dialogue is displayed. I am not familiar with dual-screen behaviour, so I can't say whether anything is supposed to be displayed or not (i.e. does the grey appear on both displays?).
I have been in touch with NEC Europe support on this issue, who suggested it might have something to do with the 10.5.7 release. I know this not to be the case, as it was occurring prior to 10.5.7 being released.
Any ideas?Put more of your hardware listed in your profile.
I looked and don't see you list your graphics card anywhere.
Graphic card it came with was either X1900 (watch for heat and dust bunnies and clogged vent);
OEM 7300GT (seems unlikely).
You could have replaced either with 8800GT or ATI 3870.
Require 10.5.2+ ideally 10.5.6+.
Some problems cropped up with 10.5.7. 10.5.7 doesn't work on some (many) 3rd party displays and stay with 10.5.6 if necessary until it is fixed or resolved.
But you say it happens with 10.5.6 also, and was doing so before 10.5.7? which makes your problem somewhat different or unique.
Zapping PRAM or NVRAM reset obviously shouldn't be needed repeatedly. And your graphics card probably needs to be replaced, or test with another card to rule it out. -
MSI R5750 Will not display during boot, crashes on update
Hello,
I recently upgraded my PSU and VGA for my computer and am using a generic LCD monitor (hp L1925). When I installed the VGA, it will not send any video output unless the monitor is first plugged into the motherboard's video. When I plug the monitor into the VGA, everything runs fine, the VGA works well. However, when I try to either install or uninstall drivers, part of the monitor turns black and then loses picture. Live Update has my system at the latest version of BIOS for both the motherboard and VGA. Any ideas?I swapped out the video cable between the monitor and the vga, now everything is working very well. Thanks.
-
Xrandr not enabling external / dual display on boot [SOLVED]
I'm using an HP ProBook 4535s and I want to get a dual display setup working. I've done it before on Ubuntu with this machine and my ASUS external monitor, so I know the hardware supports it.
After I've booted without the external monitor plugged in, if I plug in my VGA-0 and then enter
xrandr --output LVDS --mode 1366x768 --pos 1920x0 --output VGA-0 --mode 1920x1080 --pos 0x0
Then I get perfect resolution on my external monitor, but nothing shows up on my laptop's display. Using arandr also does the job perfectly, but again, it shows nothing on my laptop's display. Additionally, if I try to put a truncated version of the command in xorg.conf, like so,
Section "Monitor"
Identifier "LVDS"
Option "Primary" "true"
Option "PreferredMode" "1366x768"
EndSection
Section "Monitor"
Identifier "VGA-0"
Option "LeftOf" "VGA1"
Option "PreferredMode" "1920x1080"
EndSection
then it starts up the same way (perfect res on external, nothing but backlight on laptop), but it starts in low-graphics mode / seems not to go through any of the commands in .xinitrc. If I try to place the code in .xinitrc, like so,
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# Set up dual display (make sure xorg.conf doesn't run before this...)
#xrandr --output LVDS --mode 1366x768 --pos 1920x0 --output VGA-0 --mode 1920x1080 --pos 0x0
# Start xfce4 Desktop Environment
exec startxfce4
# Placed either above or below startxfce4, I get the error described.
#xrandr --output LVDS --mode 1366x768 --pos 1920x0 --output VGA-0 --mode 1920x1080 --pos 0x0
# Bind keys at startup
exec xbindkeys
# Get rid of the annoying warning bell
exec xset -b
# Below is from ~/.bashrc
Then when I boot with the VGA-0 cable in, *nothing* shows up at all. With any of the above configurations aside from the xorg.conf one, I *must* keep the VGA-0 unplugged during boot to get anything to show. I would like to configure my setup so I can always keep the cable in, even during boot. A dynamic setup would be nice, too, so I don't have to fuss with this when I get new monitors, etc.
Also, if it would help, here's the output of lspci | grep VGA:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G]
Thanks,
sirciny
Last edited by sirciny (2013-06-19 14:31:11)Here's an update: I now have the display spanning both monitors. It shows the right res (1366x768) on the LVDS and the wrong res on the external, and it starts up in low graphics mode. What I did was the following:
1) Install the AMD Radeon HD 6xxxG driver from AMD's website (even though the fglrx is no longer supported in Arch)
2) Copy my Ubuntu partition's xorg.conf to Arch, because Ubuntu's external setup works flawlessly
Of course, the Arch AMD driver is outdated, so I didn't really expect this to work as elegantly as I would like (it still doesn't). Changing it to "intel" in xorg.conf just makes Arch stuck in the TTY when I try to restart X. Here's xorg.conf as it is:
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Module"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "LVDS"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
Option "PreferredMode" "1366x768"
Option "TargetRefresh" "60"
Option "Position" "0 0"
Option "Rotate" "normal"
Option "Disable" "false"
EndSection
Section "Monitor"
Identifier "CRT1"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
Option "PreferredMode" "1920x1080"
Option "TargetRefresh" "60"
Option "Position" "1280 0"
Option "Rotate" "normal"
Option "Disable" "false"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
Option "Monitor-LVDS" "LVDS"
Option "Monitor-CRT1" "CRT1"
BusID "PCI:0:1:0"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Virtual 3286 1080
Depth 24
EndSubSection
EndSection
Last edited by sirciny (2013-06-18 14:40:52) -
[SOLVED] modprobe usage info displayed at boot
This thread seems related to /sbin/modprobe runs at boot before udev [solved]
I'm using mkinitcpio 0.7.2-1 on x86_64, my system is completely up-to-date, but somehow I seem to be still affected by FS#24766: I'm getting modprobe's usage info displayed at boot.
My MODULES array in /etc/mkinitcpio.conf is empty and the file is unmodified.
I have tried reinstalling mkinitcpio with no positive results.
Any ideas? Thanks
Last edited by kynikos (2011-07-31 18:59:41)Eheh, it worked, thanks! I wonder why reinstalling mkinitcpio didn't solve it then... well, nevermind
-
[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) -
[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) -
[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.
-
[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. -
[SOLVED] USB Harddrive via fstab turned off during Boot - Error
Hello^^
I'm trying to mount my external USB Drive.
I put the following line in fstab:
/dev/sdb1 /media/Musik ext4 noauto,user,default 0 1
I only want to start the Harddive occasionally.
The problem is, when the drive is completly turned off during boot I get the following error:
No such file or directory while trying to open /dev/sdb1
Possibly non existend device?
I thought that the noauto Option should prevent fstab from mounting the hdd???
regards
cl10k
PS: Manual mounting works without any problems...
Last edited by cl10k (2011-03-20 22:49:43)Let me give you a hand then. The following I have in my /etc/udev/rules.d/11-media-by-label-auto-mount.rules, and what it does is:
-- pick the name of a drive,
-- create a dedicated /media/mountpoint name (certainly, "mountpoint" is replaced by the name of your drive),
-- mount the drive on boot,
-- unmount the drive on shutdown and delete the /media/mountpoint.
KERNEL!="sd[a-z][0-9]", GOTO="media_by_label_auto_mount_end"
# Import FS infos
IMPORT{program}="/sbin/blkid -o udev -p %N"
# Get a label if present, otherwise specify one
ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
# Global mount options
ACTION=="add", ENV{mount_options}="relatime"
# Filesystem-specific mount options
ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},utf8,gid=100,umask=002"
# Mount the device
ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}", RUN+="/bin/mount -o $env{mount_options} /dev/%k /media/%E{dir_name}"
# Clean up after removal
ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/umount -l /media/%E{dir_name}", RUN+="/bin/rmdir /media/%E{dir_name}"
# Exit
LABEL="media_by_label_auto_mount_end"
Plenty of handy examples you can find in /lib/udev/rules.d/ and modify them so they meet you needs. I hope it clarifies the matter a bit.
Last edited by bohoomil (2011-03-19 16:57:36) -
[SOLVED]net-profiles doesnt work during boot
Hi,
i have got a little problem. Im trying to set up network during boot process. My way is described in arch wiki.
wireless_tools is instaled by base_devel during installation process. other packages that I installed are
pacman -S netcfg wpa_actiond
I set up the network profiles like this (file /etc/network.d/hasek_home)
CONNECTION='wireless'
DESCRIPTION='A simple WPA encrypted wireless connection using a static IP'
INTERFACE='wlan0'
SECURITY='wpa'
ESSID='hasek_home'
KEY='xxxxxxxxxxxxx'
IP='dhcp'
if I typed
netcfg hasek_home
everything works fine (Wi-fi drives is compiled in kernel). So im trying to set starting wi-fi in boot (in /etc/rc.conf)
INTERFACES=(hasek_home)
DAEMONS=(syslog-ng cpufreq acpid crond dbus hal net-profiles @netfs)
buring boot comes this messages
No profile started.
Also like handmade starting
/etc/rc.d/net-profiles restart
net-profiles not running
> No profile started.
Please, what is wrong?
Last edited by ETNyx (2010-06-09 19:03:25)1. Comment out INTERFACES (and in any case, it's not for network names, but for eth0, wlan0 etc)
2. NETWORKS=(hasek_home)
3. Not sure if it helps, but I've never been able to background netfs successfully (remove the @, maybe). I also have net-profiles and netfs before everything except syslog-ng in my daemons array.
Good luck!
Scott -
[SOLVED] efibootmgr not generating boot loader (rEFInd, etc.) entry.
Hello,
The following command runs without problem or any output. It wouldn't create any entry. Also my refind.conf is not being followed. rEFInd is able to detect kernels and boot fine from /boot
efibootmgr -c -g -d /dev/sda -p 1 -w -L "rEFInd" -l '\EFI\refind\refind_x64.efi'
Information
efibootmgr 0.6.0-1
refind-efi 0.6.8-1
Linux 3.8.4-1-ARCH
sudo efibootmgr
BootCurrent: 000A
Timeout: 0 seconds
BootOrder: 0006,0007,0008,0009,000A,000B,000C,000D,000E,000F,0010,0011,0012,0013
Boot0000 Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Startup Interrupt Menu
Boot0004 ME Configuration Menu
Boot0005 Rescue and Recovery
Boot0006* USB CD
Boot0007* USB FDD
Boot0008* ATAPI CD0
Boot0009* ATA HDD2
Boot000A* ATA HDD0
Boot000B* ATA HDD1
Boot000C* USB HDD
Boot000D* PCI LAN
Boot000E* ATAPI CD1
Boot000F* ATAPI CD2
Boot0010 Other CD
Boot0011* ATA HDD3
Boot0012* ATA HDD4
Boot0013 Other HDD
Boot0014* IDER BOOT CDROM
Boot0015* IDER BOOT Floppy
Boot0016* ATA HDD
Boot0017* ATAPI CD:
Boot0018* PCI LAN
ls -R /boot
/boot:
EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
/boot/EFI:
boot refind tools
/boot/EFI/boot:
bootx64.efi icons refind.conf
/boot/EFI/boot/icons:
*** Icons
/boot/EFI/refind:
icons refind.conf refind_x64.efi
/boot/EFI/refind/icons:
*** icons
/boot/EFI/tools:
drivers shells
/boot/EFI/tools/drivers:
ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
/boot/EFI/tools/shells:
Shell.efi Shell_Full.efi
cat /boot/refind_linux.conf
"Boot to X" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=graphical.target"
"Boot to Console" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=multi-user.target"
# refind.conf
# Configuration file for the rEFInd boot menu
# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
timeout 5
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner (built-in or loaded via "banner")
# label - boot option text label in the menu
# singleuser - remove the submenu options to boot Mac OS X in single-user
# or verbose modes; affects ONLY MacOS X
# safemode - remove the submenu option to boot Mac OS X in "safe mode"
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# hints - brief command summary in the menu
# editor - the options editor (+, F2, or Insert on boot options menu)
# all - all of the above
# Default is none of these (all elements active)
#hideui singleuser
#hideui all
# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#icons_dir myicons
# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
#banner hostname.bmp
#banner mybanner.png
# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#font myfont.png
# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#textonly
textonly
# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#textmode 2
textmode 1024
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#resolution 1024 768
#resolution 3
resolution 1024 768
# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
# osx - Mac OS X
# linux - A Linux kernel with EFI stub loader
# elilo - The ELILO boot loader
# grub - The GRUB (Legacy or 2) boot loader
# windows - Microsoft Windows
# Default value: osx
#use_graphics_for osx,linux
# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
# shell - the EFI shell (requires external program; see rEFInd
# documentation for details)
# gptsync - the (dangerous) gptsync.efi utility (requires external
# program; see rEFInd documentation for details)
# apple_recovery - boots the Apple Recovery HD partition, if present
# mok_tool - makes available the Machine Owner Key (MOK) maintenance
# tool, MokManager.efi, used on Secure Boot systems
# about - an "about this program" option
# exit - a tag to exit from rEFInd
# shutdown - shuts down the computer (a bug causes this to reboot
# EFI systems)
# reboot - a tag to reboot the computer
# Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
#showtools shell, mok_tool, about, reboot, exit
showtools shell, mok_tool, about, reboot, exit
# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#scan_driver_dirs EFI/tools/drivers,drivers
scan_driver_dirs /boot/EFI/tools/drivers,drivers
# Which types of boot loaders to search, and in what order to display them:
# internal - internal EFI disk-based boot loaders
# external - external EFI disk-based boot loaders
# optical - EFI optical discs (CD, DVD, etc.)
# hdbios - BIOS disk-based boot loaders
# biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
# cd - BIOS optical-disc boot loaders
# manual - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#scanfor internal,external,optical,manual
scanfor internal,external,optical,manual
# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#scan_delay 5
# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#dont_scan_volumes "Recovery HD"
# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory or the EFI/tools directory.
# You can "blacklist" additional directories with this option, which
# takes a list of directory names as options. You might do this to
# keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
# another boot loader or to exclude a directory that holds drivers
# or non-bootloader utilities provided by a hardware manufacturer. If
# a directory is listed both here and in also_scan_dirs, dont_scan_dirs
# takes precedence. Note that this blacklist applies to ALL the
# filesystems that rEFInd scans, not just the ESP, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell
# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, MokManager.efi is in this blacklist,
# but will show up as a tool if present in certain directories. You
# can control the tools row with the showtools token.
# The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
#dont_scan_files shim.efi,MokManager.efi
# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When uncommented, this option causes
# all files in scanned directories with names that begin with "vmlinuz"
# or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. The drawback to this option is that it can pick up kernels
# that lack EFI stub loader support and other files. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# Default is to NOT scan for kernels without ".efi" extensions.
scan_all_linux_kernels
# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#max_tags 0
# Set the default menu selection. The available arguments match the
# keyboard accelerators available within rEFInd. You may select the
# default loader using:
# - A digit between 1 and 9, in which case the Nth loader in the menu
# will be the default.
# - Any substring that corresponds to a portion of the loader's title
# (usually the OS's name or boot loader's path).
#default_selection 1
default_selection "vmlinuz-linux"
# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#include manual.conf
# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
# volume - identifies the filesystem from which subsequent files
# are loaded. You can specify the volume by label or by
# a number followed by a colon (as in "0:" for the first
# filesystem or "1:" for the second).
# loader - identifies the boot loader file
# initrd - Specifies an initial RAM disk file
# icon - specifies a custom boot loader icon
# ostype - OS type code to determine boot options available by
# pressing Insert. Valid values are "MacOS", "Linux",
# "Windows", and "XOM". Case-sensitive.
# graphics - set to "on" to enable graphics-mode boot (useful
# mainly for MacOS) or "off" for text-mode boot.
# Default is auto-detected from loader filename.
# options - sets options to be passed to the boot loader; use
# quotes if more than one option should be passed or
# if any options use characters that might be changed
# by rEFInd parsing procedures (=, /, #, or tab).
# disabled - use alone or set to "yes" to disable this entry.
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.
# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.
# A sample entry for a Linux 3.3 kernel with its new EFI boot stub
# support on a filesystem called "KERNELS". This entry includes
# Linux-specific boot options and specification of an initial RAM disk.
# Note uses of Linux-style forward slashes, even in the initrd
# specification. Also note that a leading slash is optional in file
# specifications.
menuentry Linux {
icon EFI/refind/icons/os_linux.icns
volume KERNELS
loader bzImage-3.3.0-rc7
initrd initrd-3.3.0.img
options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
disabled
# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
loader /EFI/ubuntu/grubx64.efi
icon /EFI/refined/icons/os_linux.icns
disabled
# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
loader \EFI\elilo\elilo.efi
disabled
# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
loader \EFI\Microsoft\Boot\bootmgfw.efi
disabled
# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
icon \EFI\refind\icons\os_win.icns
loader \EFI\tools\shell.efi
options "fs0:\EFI\tools\launch_windows.nsh"
disabled
# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
icon \EFI\refind\icons\os_mac.icns
volume "OS X boot"
loader \System\Library\CoreServices\boot.efi
disabled
cat /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=7b92a840-4747-43b7-b2cf-02cbf92afce7 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda4
UUID=72f64fd4-a3f1-424c-8fe3-cdf7751a84e0 /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda1
# UUID=5447-7409 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=5447-7409 /boot vfat noatime 0 2
# /dev/sda3
UUID=1e11bea5-41db-4969-a8fa-a461734b71ac none swap defaults 0 0
This is a clean install using April 01 ISO with minimal or no modifications. I have tried to follow wiki as precisely as possible. I am not sure what I am missing. Thanks.
EDIT1: Updated and cleaned the post to better reflect current structure and added /etc/fstab.
EDIT2: @swordfish Removed /boot/EFI/arch.
Last edited by donniezazen (2013-04-04 06:37:07)I used March ISO instead of April ISO and it worked flawlessly. There is some problem with April ISO where efibootmgr and UEFI Shell1/2 fail with ASSERT_EFI_ERROR (status = device error).
I have removed both /boot/EFI/boot and /boot/EFI/arch. I now have two entries one on vmlinuz-linux on 1024 Fat 32 partition which works and second one boot/vmlinuz-linux on 20G / partition which fails and takes me to rootfs. Also refind isn't showing UEFI shells that I have in /boot/EFI/tools/Shells.
ls -R /boot
/boot:
EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
/boot/EFI:
drivers refind tools
/boot/EFI/drivers:
ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
/boot/EFI/refind:
icons refind.conf refind_x64.efi
/boot/EFI/refind/icons:
### Icons
/boot/EFI/tools:
Shell.efi
# refind.conf
# Configuration file for the rEFInd boot menu
# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
timeout 5
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner (built-in or loaded via "banner")
# label - boot option text label in the menu
# singleuser - remove the submenu options to boot Mac OS X in single-user
# or verbose modes; affects ONLY MacOS X
# safemode - remove the submenu option to boot Mac OS X in "safe mode"
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# hints - brief command summary in the menu
# editor - the options editor (+, F2, or Insert on boot options menu)
# all - all of the above
# Default is none of these (all elements active)
#hideui singleuser
#hideui all
# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#icons_dir myicons
# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
#banner hostname.bmp
#banner mybanner.png
# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#font myfont.png
# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#textonly
textonly
# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#textmode 2
textmode 1024
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#resolution 1024 768
#resolution 3
resolution 1024 768
# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
# osx - Mac OS X
# linux - A Linux kernel with EFI stub loader
# elilo - The ELILO boot loader
# grub - The GRUB (Legacy or 2) boot loader
# windows - Microsoft Windows
# Default value: osx
#use_graphics_for osx,linux
# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
# shell - the EFI shell (requires external program; see rEFInd
# documentation for details)
# gptsync - the (dangerous) gptsync.efi utility (requires external
# program; see rEFInd documentation for details)
# apple_recovery - boots the Apple Recovery HD partition, if present
# mok_tool - makes available the Machine Owner Key (MOK) maintenance
# tool, MokManager.efi, used on Secure Boot systems
# about - an "about this program" option
# exit - a tag to exit from rEFInd
# shutdown - shuts down the computer (a bug causes this to reboot
# EFI systems)
# reboot - a tag to reboot the computer
# Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
#showtools shell, mok_tool, about, reboot, exit
showtools shell, about, reboot, exit
# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#scan_driver_dirs EFI/tools/drivers,drivers
scan_driver_dirs EFI/tools/drivers,drivers
# Which types of boot loaders to search, and in what order to display them:
# internal - internal EFI disk-based boot loaders
# external - external EFI disk-based boot loaders
# optical - EFI optical discs (CD, DVD, etc.)
# hdbios - BIOS disk-based boot loaders
# biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
# cd - BIOS optical-disc boot loaders
# manual - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#scanfor internal,external,optical,manual
scanfor internal,external,optical,manual
# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#scan_delay 5
# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#dont_scan_volumes "Recovery HD"
# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory or the EFI/tools directory.
# You can "blacklist" additional directories with this option, which
# takes a list of directory names as options. You might do this to
# keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
# another boot loader or to exclude a directory that holds drivers
# or non-bootloader utilities provided by a hardware manufacturer. If
# a directory is listed both here and in also_scan_dirs, dont_scan_dirs
# takes precedence. Note that this blacklist applies to ALL the
# filesystems that rEFInd scans, not just the ESP, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell
# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, MokManager.efi is in this blacklist,
# but will show up as a tool if present in certain directories. You
# can control the tools row with the showtools token.
# The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
#dont_scan_files shim.efi,MokManager.efi
# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When uncommented, this option causes
# all files in scanned directories with names that begin with "vmlinuz"
# or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. The drawback to this option is that it can pick up kernels
# that lack EFI stub loader support and other files. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# Default is to NOT scan for kernels without ".efi" extensions.
scan_all_linux_kernels
# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#max_tags 0
# Set the default menu selection. The available arguments match the
# keyboard accelerators available within rEFInd. You may select the
# default loader using:
# - A digit between 1 and 9, in which case the Nth loader in the menu
# will be the default.
# - Any substring that corresponds to a portion of the loader's title
# (usually the OS's name or boot loader's path).
#default_selection 1
# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#include manual.conf
# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
# volume - identifies the filesystem from which subsequent files
# are loaded. You can specify the volume by label or by
# a number followed by a colon (as in "0:" for the first
# filesystem or "1:" for the second).
# loader - identifies the boot loader file
# initrd - Specifies an initial RAM disk file
# icon - specifies a custom boot loader icon
# ostype - OS type code to determine boot options available by
# pressing Insert. Valid values are "MacOS", "Linux",
# "Windows", and "XOM". Case-sensitive.
# graphics - set to "on" to enable graphics-mode boot (useful
# mainly for MacOS) or "off" for text-mode boot.
# Default is auto-detected from loader filename.
# options - sets options to be passed to the boot loader; use
# quotes if more than one option should be passed or
# if any options use characters that might be changed
# by rEFInd parsing procedures (=, /, #, or tab).
# disabled - use alone or set to "yes" to disable this entry.
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.
# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.
# A sample entry for a Linux 3.3 kernel with its new EFI boot stub
# support on a filesystem called "KERNELS". This entry includes
# Linux-specific boot options and specification of an initial RAM disk.
# Note uses of Linux-style forward slashes, even in the initrd
# specification. Also note that a leading slash is optional in file
# specifications.
menuentry Linux {
icon EFI/refind/icons/os_linux.icns
volume KERNELS
loader bzImage-3.3.0-rc7
initrd initrd-3.3.0.img
options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
disabled
# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
loader /EFI/ubuntu/grubx64.efi
icon /EFI/refined/icons/os_linux.icns
disabled
# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
loader \EFI\elilo\elilo.efi
disabled
# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
loader \EFI\Microsoft\Boot\bootmgfw.efi
disabled
# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
icon \EFI\refind\icons\os_win.icns
loader \EFI\tools\shell.efi
options "fs0:\EFI\tools\launch_windows.nsh"
disabled
# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
icon \EFI\refind\icons\os_mac.icns
volume "OS X boot"
loader \System\Library\CoreServices\boot.efi
disabled
Thanks for suggesting to try older ISO.
UPDATE:- Most recent ls -R /boot and my refind.conf. Reading over Rod Smith's rEFInd documentation has helped me clean up a little more and set up a good boot manager with automatic kernel detection and shell. I do want to get rid of drivers list that shows itself up along with kernel. Next is to tackle menu entry. Thanks.
Last edited by donniezazen (2013-04-04 06:43:16) -
Hi All,
A few months ago when 1.0.4.14 was released I was quick to update to this version from 1.0.3.10 but very quickly ran into issues.
Bit of background info... I am not doing anything complex with this box, basic IP4 network over all LAN ports, no VLANs, firewall enabled and allowing 2 port access rules to a static IP address. Any static IPs are assigned manual at host level but all other devices receive DHCP IP addresses. I don’t host VPN on this RV180 but I do with another. Routing VPN has no issues. WAN is connected to another switch provided by my ISP who provides DHCP IP Address with their DNS etc. Only LAN ports 1 and 2 are connected, port 1 to my Wireless AP (AP mode passing all requests to the RV180, DHCP etc.), port 2 connects to a 8 port Smart Switch (but all 'Smart' features are currently not in use, so basic switching only). All other settings on the RV180 are on recommended defaults.
Everything is working fine on 1.0.3.10 but I have all kinds of issues after updating to 1.0.4.14. Here are the actions and experiences I had...
1) Backup my RV180 config to txt file.
2) Navigate to the firmware upgrade page and follow steps to complete the upgrade process from 1.0.3.10 to 1.0.4.14. *router does the normal process of upgrading*
3) RV180 reboots to complete but doesn’t come back up even after waiting 5-10 mins. LAN ports enable during boot up (link lights on) but after about 2mins turn off (no link lights). WAN light is on alongside the Power Light.
4) Power cycle even with rest... Same results.
5) Reset the RV180 to default settings. I can sometimes get the unit to boot up and the LAN remains active and powered up. The web UI is VERY slow compared with 1.0.3.10. Internet sometimes works and sometimes doesn't (I would expect it all work without issue on default settings).
6) I repeat this a few times, various resets, powered off waiting periods, etc. but I always have issues. I did manage to get some log file information and the Kernel appears in the Alert, Error and also the Warning logs (please see attached files).
7) I gave up at this point. No major issues like this reported on the internet from a few google searches etc. So I then reset to defaults (1.0.4.14), downgrade to 1.0.3.10 and finally reset to defaults again + restore backup config settings (with some manual changes).
The router has remained like this and seem to be working fine, but I would like any security improvements from 1.0.4.14 firmware on my device.
Anyone able to help, have the same issue or can advise me in any other ways?
I see 1.0.3.10 isn’t displayed as a firmware download on the standard support page for the RV180 now. Only 1.0.2.6 and 1.0.4.14. Do I need to downgrade again to 1.0.2.6 before upgrading to the latest version?
Regards,
~FAZ~Hi,
I recently bought a RV180 router and immediately I encountered the same problem; practically I am not able to access the web GUI.
The PC is directly connected to the router, nothing else is connected; the TCP/IP configuration is as follows:
PC: 192.168.1.100
RV180: 192.168.1.1
GATEWAY: 192.168.1.1
SUBNET MASK: 255.255.255.0
Once the router is turned on, the power LED flashes fastly, the Ethernet LED is on but after few minutes it disappears and the PC detects a disconnection of the Ethernet cable.
The router is not pingable and, as I said, the web interface is not reachable.
I have tried to power cycle the router, to reset it (pressing the reset button for more than 3 second and for more than one minute), to access the rescue mode and download a new firmware through TFTP, but nothing worked.
Few times, after many boot and reset trials,I was able to access the web interface and in one of these occasions I updated the firmware to 1.0.4.14 but once the router is powered off the problem arises again at the next power on.
I have not tried yet to downgrade to an older firmware version.
Can you suggest any solution? thank you. -
"F11 System Recovery" during boot does not work after Cloning hard drive.
Problem: “F11 System Recovery” during boot does not work after Cloning hard drive.
HP Envy m6-1125dx UEFI Notebook Computer with GPT hard drive.
Original Seagate Hard Disk GPT 700GB with Window 8.0_64 upgraded to Windows 8.1_64
Startup Menu (F11 System Menu works properly) only on original hard drive.
Following obtained from Disk Management & diskpart in Command Prompt.
GPT Disk <700GB>
Partition 1 WINRE NTFS Primary 235MB/400MB [Recovery]
Partition 2 EFI System FAT32 (LBA) Primary 108MB/260MB [System]
Partition 3 (NONE) Unformatted Primary 128MB/128MB [Reserve]
Partition 4 Main NTFS Primary 90GB/195GB [Primary “C”]
Partition 5 (NONE) NTFS Primary 372MB/450MB [Recovery]
Partition 6 Data NTFS Primary 7GB/475GB [Primary “E”]
Partition 7 NTFS Primary 26MB/350MB [Recovery]
Partition 8 Recovery NTFS Primary 24GB/26GB [Recovery “D”]
I have Cloned the original hard drive to a new HGST 1TB Hard Drive using four different methods (sector by sector):
Acronis True Image 2015
Acronis Backup for PC
AOMEI Backupper Professional
Macrium Reflect
Each time the cloning process completes successfully and has the same original partition arrangement. The computer works properly except when trying to use the “F11 System Menu” key during boot. It gives the following error message:
“Recovery
Your PC needs to be repaired
A required device isn’t connected or can’t be accessed.
Error code: 0xc0000225
You need to use the recovery tools on your installation media. If you don’t have any installation media (like a disc or USB device), contact your system administrator or PC manufacturer. “
Any suggestions why the F11 System Recovery does not work during boot and how to fix the problem would be appreciated. I have does various disk checking and file checking on both the original and new hard drive with no errors.
Thank you in advanced.Hi,
How did you clone the HDD ? One-for-one or different method ?
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.
Maybe you are looking for
-
My new iMac has recently had OSX Lion installed on it and now when I start the machine it looks like its updating something every time, and the wireless doesn't work. So I restart and everything is OK - until I have to start up again the next time -
-
Game Center: Incorrect Information/Sync/Games
My game center lists games I have never downloaded and never played on any device. Also, my scores for games I do have are not syncing properly. What is going on and how can I stop it?
-
Can Apple TV decode AAC for receivers?
I am interesting in getting an Apple TV, but am concerned about the AAC audio tracks. Since most receivers do not decode AAC, I am wondering if Apple TV decodes AAC for the receiver, so the receiver can play the stereo track. Home theater speakers ar
-
Second Gerneration iPod Nano and USB 1.1
Hello, I have read in other feeds that the second generation Nano is compatable with USB 1.1. Is this correct? If yes, will I need extra charger or something to charge the battery? Thanks, John Heyne
-
RAR: Alerts tables understanding
Hi, After running alert generation role specifying just critical actions flag and a specific risk that includes a few transactions we have identified that the following tables are containing data: VIRSA_CC_ALLASTRUN: Dates and time when alert generat