[SOLVED]grub-mkconfig won't work

Hi!
I'm running grub2, and today grub-mkconfig stopped working: this is the error:
sudo grub-mkconfig -o /boot/grub/grub.cfg
Creazione di grub.cfg...
Trovata immagine linux: /boot/vmlinuz-netbook
Trovata immagine linux: /boot/vmlinuz-3.4.9-1-i686-arch
Trovata immagine initrd: /boot/initramfs-3.4.9-1-i686-arch.img
Found memtest86+ image: /boot/memtest86+/memtest.bin
No volume groups found
Trovato Arch Linux su /dev/sda3
/usr/sbin/grub-mkconfig: line 269: 8481 Errore di segmentazione ${grub_script_check} ${grub_cfg}.new
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.fatto
This is my /etc/default/grub:
GRUB_DEFAULT=saved
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR="Archlinux"
GRUB_CMDLINE_LINUX_DEFAULT="quiet rootfstype=ext4 add_efi_memmap logo.nologo fastboot raid=noautodetect libahci.ignore_sss=1 loglevel=3 pcie_aspm=force i915.i915_enable_rc6=3 i915.lvds_downclock=1 ipv6.disable=1 resume=swap:/dev/sda3:0x5d0000 "
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=false
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
GRUB_BACKGROUND="/usr/share/grub/background.png"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
I only set a swapfile to be used by tuxonice, then add the proper line there, in /etc/default/grub.
May be i made some mistakes? I tried to remove the resume= parameter, but it won't work anyway...
Thank you!
Last edited by nierro (2012-08-23 22:32:46)

The resume parameter is different from the normal resume= because i'm using a swap file
Btw, this is the error message without resume parameter, in english:
LC_ALL=C sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-netbook
Found linux image: /boot/vmlinuz-3.4.9-1-i686-arch
Found initrd image: /boot/initramfs-3.4.9-1-i686-arch.img
Found memtest86+ image: /boot/memtest86+/memtest.bin
No volume groups found
Found Arch Linux on /dev/sda3
error: syntax error.
error: Incorrect command.
error: syntax error.
/usr/sbin/grub-mkconfig: line 269: 5859 Segmentation fault ${grub_script_check} ${grub_cfg}.new
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.done
Last edited by nierro (2012-08-23 22:01:33)

Similar Messages

  • [SOLVED] GRUB DEFAULT settings not working

    Hi to everyone,
    after a system update the default settings for grub is not working. It still booting automatically to first occurrence...
    This is what grub-customizer sees:
    so I can imagine everything is set ok. What could I check more?
    Last edited by Tid91 (2014-03-07 17:58:27)

    Hi,
    Check /boot/grub/grub.cfg, and in your case you should set:
    set default="4"
    Take in mind it's zero-based.
    Beware, you should be doing this modifying /etc/default/grub and rebuilding your config file with grub-mkconfig; see the wiki for more details on how to do it.

  • [Solved] grub-mkconfig not picking up new kernel

    Hi,
    I compiled the linux-lts kernel from source today, woohoo! First time compiling from source.  Fun!
    I followed the Kernels/Compilation/Traditional - Archwiki.  No problems at all in the Build Configuration and Compilation & Installation steps.  The issue is that when I try to add the new kernel to grub.cfg
    # grub-mkconfig -o /boot/grub.d/grub.cfg
    it does not pick up my new kernel.  Here's the contents of /boot:
    % ll /boot ~
    total 27444
    drwxr-xr-x 3 root root 4096 Aug 31 17:13 .
    drwxr-xr-x 18 root root 4096 Jul 18 16:09 ..
    lrwxrwxrwx 1 root root 26 Aug 31 17:13 System.map -> /boot/System.map-linux-lts
    -rw-r--r-- 1 root root 2455967 Aug 31 17:13 System.map-linux-lts
    drwxr-xr-x 2 root root 4096 Aug 31 17:26 grub
    -rw-r--r-- 1 root root 11152827 Aug 30 18:10 initramfs-linux-fallback.img
    -rw-r--r-- 1 root root 3332339 Aug 31 17:10 initramfs-linux-lts.img
    -rw-r--r-- 1 root root 3364808 Aug 15 11:37 initramfs-linux.img
    -rw-r--r-- 1 root root 3792336 Aug 31 17:04 vmlinux-linux-lts
    -rw-r--r-- 1 root root 3982880 Aug 13 22:43 vmlinuz-linux
    Here's the output of grub-mkconfig:
    # grub-mkconfig -o /boot/grub/grub.cfg ~
    Generating grub configuration file ...
    Found linux image: /boot/vmlinuz-linux
    Found initrd image: /boot/initramfs-linux.img
    Found fallback initramfs image: /boot/initramfs-linux-fallback.img
    done
    I've tried a bit of googling, checking journalctl, but haven't come up with anything, I've also retraced my steps in the wiki process about 3-4 times.  I'm hoping someones bumped into this before, maybe I'm missing something obvious?
    Thanks for your time!
    Last edited by oktorok (2014-09-01 07:19:04)

    lullllzlzl.  Oh man, I'm not even going to deprecate myself here, or make excuses. To be perfectly honest, I'm glad it was a typo and not a real issue.  I can't thank you enough for pointing this out.  Gladly marked solved.

  • [Solved] history -c won't work

    i was try to clear bash history with :
    history -c
    but it won't work , actually when i close terminal and reopen it history still exist :-??
    Last edited by Milad (2012-05-06 15:17:57)

    Gcool wrote:Doesn't "history -c" just clear the history saved in RAM (not what's actually saved in ~/.bash_history)? Someone please correct me if I'm wrong here (not 100% sure of this).
    The command will not work from a terminal emulator.  You still have bash running when you close the terminal emulator.  All you are clearing is that terminal instance's history.  To completely clear the history file with the command 'history -c', you need to run it from the login shell.
    You could use this to clear the history file:
    $ > ~/.bash_history

  • [SOLVED] UEFI shell won't work on Thinkpad Edge E520

    Hi there,
    I have installed the x86_64 UEFI Shell 2.0 on my Thinkpad Edge E520 which is already booting in UEFI mode using refind-efi for some time now. The same shell is running just fine on my desktop system.
    But - on the Thinkpad it doesn't run. The shell is installed as /boot/efi/shellx64.efi and when I start the laptop, refind appears and shows me the shell icon (amoung others). But when I choose the shell from refind I get a black screen with this writing:
    Starting shellx64.efi
    Using load options ' '
    ASSERT_EFI_ERROR (Status = Device Error)
    ASSERT c:\dev\edk2tip\Build\Shell\RELEASE_VS2005\X64\ShellPkg\Application\Shell\Shell\DEBUG\AutoGen.c (431): !EFI_ERROR (Status)_
    I don't know if the text is going on after the last underline. If yes I cannot see it because the text is running out of the screen.
    The funny thing is - exactly the same setup is working pretty nice on my Asrock ITX board but not on the Lenovo Thinkpad Edge E520.
    Any ideas? Just say, if you need further information.
    Last edited by swordfish (2013-02-10 11:44:27)

    Okay, found the - somewhat obvious - solution myself. The UEFI Bios on my Thinkpad is an "old" UEFI 2.0. So, Shell 2.0 won't work on this system (as I could have read in the wiki ).
    Now, I have installed Shell 1.0 and I can enter the shell from refind .
    Last edited by swordfish (2013-02-10 11:45:03)

  • [(somewhat) SOLVED] Dnsmasq simply won't work - crashed?

    Hi there,
    I'm having a problem with dnsmasq (v2.54 [<- how is this possible anyway? I just reinstalled it, pacman calls it "2.53-1", 'dnsmasq --version' calls it '2.54'…]). I'm just trying to use it as a DNS cache, nothing special.
    It seems to be started (with the "log dns queries" option enabled) without problems, but without any queries too (even though there should have been some at this time):
    Jun 7 20:39:04 dnsmasq[1717]: started, version 2.54 cachesize 150
    Jun 7 20:39:04 dnsmasq[1717]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
    Jun 7 20:39:04 dnsmasq[1717]: reading /etc/resolv.conf
    Jun 7 20:39:04 dnsmasq[1717]: ignoring nameserver 127.0.0.1 - local interface
    Jun 7 20:39:04 dnsmasq[1717]: read /etc/hosts - 1 addresses
    Jun 7 20:39:15 dnsmasq[1717]: reading /etc/resolv.conf
    Jun 7 20:39:15 dnsmasq[1717]: reading /etc/resolv.conf
    Jun 7 20:39:15 dnsmasq[1717]: ignoring nameserver 127.0.0.1 - local interface
    I learned "ignoring nameserver 127.0.0.1 - local interface" is not a bug but a feature (makes sense of course).
    As far as I can tell in this short (but complete) log, there is nothing wrong here.
    Still, it is not used:
    dig google.de:
    ;; Query time: 2 msec
    ;; SERVER: 192.168.178.1#53(192.168.178.1)
    dig google.de again:
    ;; Query time: 2 msec
    ;; SERVER: 192.168.178.1#53(192.168.178.1)
    Here's my not exactly spectacular resolv.conf:
    # Generated by dhcpcd from eth0
    nameserver 127.0.0.1
    nameserver 192.168.178.1
    # /etc/resolv.conf.tail can replace this line
    /etc/hosts (if needed at all):
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost
    # End of file
    Nothing fancy here either.
    I've made two more observations:
    1. A few days ago I switched from a "normal" network setup (using 'eth0="dhcp"' in rc.conf) to 'net-auto-wired' using netcfg.
    Browsing using a domain name like 'google.de' has become very slow since then, i.e. connecting to a new website takes a few seconds; following a few links on that (now dns-resolved) website is fast. Browsing using IP addresses is fast as usual.
    2. I cannot restart dnsmasq.
    sudo /etc/rc.d/dnsmasq restart:
    :: Stopping DNS/DHCP daemon [DONE]
    :: Starting DNS/DHCP daemon [FAIL]
    Nothing else (not in the logs either). What I can observe in my process list is that a second dnsmasq process is started even though the original process is NOT stopped. After a few seconds, the second, newly created dnsmasq process disappears.
    "killall dnsmasq" simply does nothing. It's like pushing Return in my console. No message, no effect, no nothing.
    These 2 observations lead me to my assumption, that dnsmasq crashes at some point; an application tries to give its DNS queries to it -> nothing happens -> the applications uses the second entry in my resolv.conf which is my router.
    I have no idea whether this assumption is true nor why trying to SIGKILL it doesn't end dnsmasq's miseral life.
    I'm stuck here. Can anybody help me?
    Thanks a lot.
    Last edited by EdgarButan (2010-06-08 16:59:52)

    Alright, I seem to be able to kill dnsmasq with "kill -9 PID".
    "killall" nor the process list of KDE worked which has never occured to me.
    This topic is now a duplicate of the other one, let's call it "SOLVED".

  • [SOLVED] Gnome Mplayer Won't Work

    I have Gnome mplayer and gecko player installed on my maching with the mplayer-mt Aur package.  Gnome-mplayer won't play any files and just says "Stopped" on the bottom.  Can't figure it out, I've tried re-installing it and the regular mplayer package too without any luck.  Anybody know what the problem might be?
    Thx
    Last edited by leberyo (2010-09-24 19:35:43)

    anonymous_user wrote:
    Did you try deleting the config for gnome-mplayer?
    rm -r ~/.config/gnome-mplayer
    Also try running gnome-mplayer from a terminal and post its output when trying to play a file.
    Deleting the gnome-mplayer folder did the job.  It works now thanks.
    The only thing is, if I change any settings whatsoever in gnome-mplayer preferences, it stops again.  I guess I'll just stick to all the stock settings...

  • [Solved] Pulse Audio won't work on newly installed system with Gnome

    About a year ago I got a new computer and more or less retired my old one with my first arch install. Recently, I decided I would set it up as a Linux system for my sister. I first updated the computer, which broke it royally (since it was last updated before the /bin symlinking happened) but I eventually got it fixed. However, after doing that, Pulse Audio wouldn't work, then I broke X and decided to do a full reinstall.
    Now, on this clean install, Pulse is again not working. I have set up Gnome and gdm to work, and everything works great except Pulse.  The wiki says that Pulse with Gnome 3 requires no extra setup, so I have not edited conf files at all. I have, however, installed "pulseaudio-alsa", which created this conf file:
    # Use PulseAudio by default
    pcm.!default {
    type pulse
    fallback "sysdefault"
    hint {
    show on
    description "Default ALSA Output (currently PulseAudio Sound Server)"
    ctl.!default {
    type pulse
    fallback "sysdefault"
    # vim:set ft=alsaconf:
    which seems fairly standard. Anyway, I tried removing it and had the same problems. When I have Pulse Audio running and try to play sound, I get the error:
    ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
    Playback open error: -16,Device or resource busy
    which is obviously trying for ALSA, or from mplayer:
    AO: [pulse] Init failed: Connection refused
    Running "pacmd list" nets me:
    Daemon not responding.
    and pavucontrol gives me:
    Fatal Error: Unable to connect to PulseAudio: OK
    when I try to start it.
    No pulseaudio commands seem to work (e.g. pulseaudio -k). They don't raise any errors, but also it doesn't have any effect on the server.
    The only asound conf file is "/etc/asound.conf", clearing ~/.config/pulse does not fix the issue.
    Journalctl does not seem to give anything interesting (Stale PID is the only message when starting Pulse), though admittedly I'm just vgrepping all of journalctl since I don't know how to narrow it down more, nor does the output from pulseaudio -vvvv. There are a lot of errors in pulseaudio -vvvv, but they all appear to be related to loading devices that don't exist, and so I assume not a problem, I can post it if necessary. Sometimes when I kill Pulse the process refuses to go away and I have to reboot in order to clear the process out, but I don't think that's related.
    If I kill Pulse or keep it from starting on boot, I can play sound, but only through ALSA, and while I didn't have the problem I expected (I can still play multiple things simultaneously) there's still the issue that the volume buttons in Gnome will no longer work and that the volume levels ALSA reports are basically nonsense to a human being.
    I basically just blurbed everything I thought of/found on the wiki or forums, and I'm not really sure where to go from here. It's a fairly old computer, so that could be related, and I'd be willing to dump Pulse if Gnome could integrate well with ALSA, but obviously fixing Pulse would be the preferred option.
    Any suggestions on where to look next? I've run out of ideas.
    Thanks.
    Last edited by HuFlungDu (2014-01-07 19:52:11)

    Wonder if you have a conflict between two audio cards ... for example, I have a friend with some PulseAudio problems caused by conflict between the HDMI audio from his graphics card and his onboard sound. Something would switch PulseAudio to the wrong card and it would just quit after getting itself into a twist. Unsolved, I'm afraid, but have a look at commands such as:
    aplay -l
    pactl list sinks
    pactl stat
    (Latter two will need PulseAudio coaxed into life first)
    and of course, the Arch wiki.
    If there is a conflict, blacklisting kernel modules might also be needed.

  • [SOLVED] pacman upgrade won't work because of unresolved dependency

    Hey all,
    I tried a pacman -Syyu today and it found some things and said:
    :: The following packages should be upgraded first :
        pacman
    :: Do you want to cancel the current operation
    :: and upgrade these packages now? [Y/n] y
    resolving dependencies...
    looking for inter-conflicts...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: gcc: requires gcc-libs=4.6.2-6
    I have gcc-libs=4.6.2-7 and I apparently need 4.6.2-6 but I can't change anything without pacman, and pacman won't change anything without updating itself first, and it can't because of this unmet dependency, so there's a stalemate.
    Any ideas what to do?
    Last edited by jdoggsc (2012-02-13 21:00:47)

    Awebb wrote:What's a repost?
    http://www.urbandictionary.com/define.php?term=repost

  • [SOLVED] X environment won't work

    Hey guys so I am having trouble trying to get my x environment to work. When I type startx it goes to a black screen and then show white and black zig-zag lines and the black ones are pixalated. I checked my log (Greg EE /var/log/Xorg.0.log) and this is what it says
    [332.566] Current operating system: Linux (none) 3.5.3-1-ARCH #1 SMP PREEMPT sun aug 26 09:14:51 CEST 2012 x86_64
             (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [332.593] (II) loading extension MIT-SCREEN-SAVER
    [332.603] (EE) failed to load module "nvidia" (module does not exist, 0)
    [332.603] (EE) failed to load module "nv" (module does not exist, 0)
    [332.604] (EE) failed to load module "vesa" ( module does not exist, 0)
    [332.604] (EE) failed to load module "fbdev" (module does not exist, 0)
    [334.875] (EE) AIGLX error: dlopen of /usr/lib/Xorg/modules/dri/nouveau_dri.so failed (/usr/lib/Xorg/modules/dri/nouveau_dri.so: cannot open shared object file: No such file or directory)
    [334.875] (EE) AIGLX: reverting to software rendering
    I have a gtx 560 graphics card and I installed the nouveau driver for it. It says failed to load NVIDIA so I was wondering if I should just use the NVIDIA driver instead of nouveau even though it is recommended that you use nouveau first until you get it setup. I don't think I messed anything up because all I did was install the needed packages. Any help will be awesome thank you.
    Last edited by bdawg (2012-09-25 00:18:51)

    bdawg wrote:I have a gtx 560 graphics card and I installed the nouveau driver for it. It says failed to load NVIDIA so I was wondering if I should just use the NVIDIA driver instead of nouveau even though it is recommended that you use nouveau first until you get it setup.
    It means that you still have the xorg.conf file that nvidia-xconfig created, for the nvidia driver.
    Delete or move any xorg.conf ("/etc/X11/xorg.conf" or "/etc/xorg.conf") and use the "/etc/X11/xorg.conf.d/10-monitor.conf" file with your equivalent of:
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "DELL"
    ModelName "U2311H"
    HorizSync 30.0 - 83.0
    VertRefresh 56.0 - 76.0
    Option "DPMS"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nouveau"
    VendorName "NVIDIA Corporation"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    PS: While explicitly specifying the "Driver" part may be omitted with open-source drivers (or so I've heard), I find that it's easier to switch to nvidia, if I ever want to, instead of automatically generating that awful xorg.conf.

  • [solved]Quod Libet won't work

    Hi,
    I have reinstalled my archbox yesterday. Then I installed quod libet, but it don't start.
    The start in a terminal gives me this:
    [jean@arch ~]$ quodlibet
    Traceback (most recent call last):
    File "/usr/bin/quodlibet", line 299, in <module>
    util.gtk_init()
    File "/usr/share/quodlibet/util/__init__.py", line 44, in gtk_init
    import gtk
    ImportError: No module named gtk
    What can I do ? Is there any packages missing?
    Thanks for any help.
    Jean-Paul
    Last edited by jean-paul (2007-05-14 18:43:42)

    Yeah, thats realy funny.
    Thanks for help, it works well.
    Fortuna will great again.
    Jean-Paul

  • [SOLVED] lxdm autologin won't work since last upgrade

    Hi,
    Since last upgrade, lxdm won't autologin anymore.
    I had a lxdm.conf.pacnew file wich added only a commented line that I added into the conf file, wich does look like this :
    [base]
    ## uncomment and set autologin username to enable autologin
    #autologin=dgod
    autologin=Olaff
    ## uncomment and set timeout to enable timeout autologin,
    ## the value should >=5
    # timeout=10
    ## default session or desktop used when no systemwide config
    session=/usr/bin/startlxde
    #session=/usr/bin/openbox-session
    ## uncomment and set to set numlock on your keyboard
    # numlock=0
    ## set this if you don't want to put xauth file at ~/.Xauthority
    # xauth_path=/tmp
    # not ask password for users who have empty password
    # skip_password=1
    ## greeter used to welcome the user
    greeter=/usr/lib/lxdm/lxdm-greeter-gtk
    [server]
    ## arg used to start xserver, not fully function
    arg=/usr/bin/X -background vt1
    # uncomment this if you really want xserver listen to tcp
    # tcp_listen=1
    # uncoment this if you want reset the xserver after logou
    # reset=1
    [display]
    ## gtk theme used by greeter
    gtk_theme=Clearlooks
    ## background of the greeter
    # bg=/usr/share/backgrounds/default.png
    ## if show bottom pane
    bottom_pane=1
    ## if show language select control
    lang=1
    ## if show keyboard layout select control
    keyboard=0
    ## the theme of greeter
    theme=Industrial
    [input]
    [userlist]
    ## if disable the user list control at greeter
    disable=0
    ## whitelist user
    white=
    ## blacklist user
    black=
    Since there were no uncommented lines added, I assumed it would make no difference.
    Edit :
    Now, the system goes to the login screen instead of autologin.
    lxdm brings me to my session if I log in however.
    Last edited by OlaffTheGreat (2013-09-21 18:00:09)

    Here is my current /etc/lxdm/lxdm.conf file.  Hope something in here can help you out. 
    [base]
    ## uncomment and set autologin username to enable autologin
    autologin=andy
    ## uncomment and set timeout to enable timeout autologin,
    ## the value should >=5
    # timeout=10
    ## default session or desktop used when no systemwide config
    session=/usr/bin/startlxde
    ## uncomment and set to set numlock on your keyboard
    numlock=1
    ## set this if you don't want to put xauth file at ~/.Xauthority
    # xauth_path=/tmp
    # not ask password for users who have empty password
    # skip_password=1
    ## greeter used to welcome the user
    #greeter=/usr/lib/lxdm/lxdm-greeter-gtk
    [server]
    ## arg used to start xserver, not fully function
    #arg=/usr/bin/X -background vt1
    # uncomment this if you really want xserver listen to tcp
    # tcp_listen=1
    # uncoment this if you want reset the xserver after logou
    # reset=1
    [display]
    ## gtk theme used by greeter
    gtk_theme=Clearlooks
    ## background of the greeter
    # bg=/usr/share/backgrounds/default.png
    ## if show bottom pane
    bottom_pane=1
    ## if show language select control
    lang=
    ## if show keyboard layout select control
    keyboard=0
    ## the theme of greeter
    theme=Industrial
    [input]
    [userlist]
    ## if disable the user list control at greeter
    disable=1
    ## whitelist user
    white=
    ## blacklist user
    black=
    Not sure why OlaffTheGreat uses LXDM, but I use it because you get it for free as part of the LXDE group, and I'm too lazy to change it.  My security is the 30 to 40 character passphrase I need to unlock my encrypted drives.  Then having to type in an 8 character easily guessed user password is beyond annoying.
    I just checked my pacman cache files and it looks like the upgrade to 0.4-1-25 is when I first got the error (currently listed as 9 days ago which would be about right).  I upgraded, booted and got the login screen that I was not supposed to.  I had just merged the pacnew file so it was fresh in my head and made the changes I described.  Booted again and got the autologin and I didn't think another thing about it until I saw this post earlier today.  Upgraded again this weekend to 0.4-1-27 with no problems.

  • [solved] remove grub timeout doesn't work

    i am trying to remove the grub timeout by editing /etc/default/grub and setting grub_timeout to 0, but it doesn't work, is there anything else i should change?
    p.s. should i run grub-mkconfig?
    Last edited by aldoiljazi (2013-09-18 07:35:11)

    okay i run 'sudo grub-mkconfig'
    this is my /etc/default/grub
    GRUB_DEFAULT=0
    GRUB_TIMEOUT=0
    GRUB_DISTRIBUTOR="Arch"
    GRUB_CMDLINE_LINUX_DEFAULT="quiet"
    GRUB_CMDLINE_LINUX=""
    # Preload both GPT and MBR modules so that they are not missed
    GRUB_PRELOAD_MODULES="part_gpt part_msdos"
    # Uncomment to enable Hidden Menu, and optionally hide the timeout count
    #GRUB_HIDDEN_TIMEOUT=5
    #GRUB_HIDDEN_TIMEOUT_QUIET=true
    # Uncomment to use basic console
    GRUB_TERMINAL_INPUT=console
    # Uncomment to disable graphical terminal
    #GRUB_TERMINAL_OUTPUT=console
    # The resolution used on graphical terminal
    # note that you can use only modes which your graphic card supports via VBE
    # you can see them in real GRUB with the command `vbeinfo'
    GRUB_GFXMODE=auto
    # Uncomment to allow the kernel use the same resolution used by grub
    GRUB_GFXPAYLOAD_LINUX=keep
    # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
    # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
    #GRUB_DISABLE_LINUX_UUID=true
    # Uncomment to disable generation of recovery mode menu entries
    GRUB_DISABLE_RECOVERY=true
    # Uncomment and set to the desired menu colors. Used by normal and wallpaper
    # modes only. Entries specified as foreground/background.
    #GRUB_COLOR_NORMAL="light-blue/black"
    #GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
    # Uncomment one of them for the gfx desired, a image background or a gfxtheme
    #GRUB_BACKGROUND="/path/to/wallpaper"
    #GRUB_THEME="/path/to/gfxtheme"
    # Uncomment to get a beep at GRUB start
    #GRUB_INIT_TUNE="480 440 1"
    #GRUB_SAVEDEFAULT="true"
    and this is my /boot/grub/grub.cfg
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 6b44daaa-610c-4f23-a632-569d091e4d43
    else
    search --no-floppy --fs-uuid --set=root 6b44daaa-610c-4f23-a632-569d091e4d43
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    set timeout=5
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-6b44daaa-610c-4f23-a632-569d091e4d43' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 6b44daaa-610c-4f23-a632-569d091e4d43
    else
    search --no-floppy --fs-uuid --set=root 6b44daaa-610c-4f23-a632-569d091e4d43
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=6b44daaa-610c-4f23-a632-569d091e4d43 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    p.s. i didn't think you needed those, because i thought they had default values.
    edit: i guess i need 'grub-mkconfig -o /boot/grub/grub.cfg '
    Last edited by aldoiljazi (2013-09-18 07:31:39)

  • [Solved] Grub not displaying menu, error messages from grub-mkconfig

    Hi I'm new
    I have (or rather, am trying to setup) a dual boot with Windows 8.1 and Arch, with each OS on separate SSDs.
    Windows 8.1 already installed, Arch installation (seems to have) has gone smoothly. However, when I remove the installation usb, and try to boot, I get a command line prompt:
    grub >_
    ...instead of a menu. I tried typing 'boot', but got 'you need to load the kernel first'. So I cannot access my arch installation without chrooting (or knowing how to compile the kernel in the command line, which I could not find after a lot of searching)
    I followed the documentation in the Beginner's Guide and the GRUB page for installing and configuring GRUB. This is UEFI (grub2), not BIOS (grub legacy).
    pacman -S grub efibootmgr
    grub-install --target=x86S64-efi --efi-directory=/boot --bootloader-id=arch_grub --recheck
    No error messages. I also installed os-prober for kicks. When I went to generate the config file (as recommended for beginners), I got a torrent of what I interpreted to be error messages, not just copacetic output:
    grub-mkconfig -o /boot/grub/grub.cfg
    resulted in:
    click this link for error messages
    (sorry about the image. I had to shutdown and reboot into my windows partition, since I still can't arch it up. If any/all of you have a better way to reproduce output and feel it pertinent, I'm all ears)
    so upon exiting chroot and rebooting, grub boots up to the above effect; no menu is displayed. And I am sad panda.
    Background Information:
    Partition scheme:
    /dev/sda1 - BIOS boot partition (I didn't read carefully, lol)
    /dev/sda2 - EFI System Partition - mounted to /mnt/boot when chrooting in
    /dev/sda3 - Root partition - mounted to /mnt/ when chrooting in
    /dev/sda4 - Home partition - mounted to /mnt/home when chrooting in
    The installation and configuration described above was done in chroot with the above partition scheme
    I originally had issues booting into UEFI mode with the arch iso (written to a usb stick for the initial install). The boot would hang at 'triggering uevents'. I ultimately fixed this by pressing 'e' in the bootloader menu (also grub, I believe) and prepended
    linux /boot/vmlinux-linux root=UUID=978e3e81-8048-4ae1-8a06-aa727458e8ff nomodeset nouveau.modeset=0
    It then (successfully triggered uevents? and) booted normally
    ALSO:
    This is a custom built pc.
    Hardware:
    intel i7 4930K
    ASUS Sabertooth X79 mobo
    ASUS GTX 780 Ti gpu
    ballistix sport DDR3 RAM (4 x 8 GB)
    3 x 128 GB SSD (ADATA P900)
    1 x 2 TB HDD (Toshiba, 7200 rpm)
    Hey, if you made it to the bottom of this post, I really appreciate you taking the time out of your day. Thank you!
    Last edited by Otsdarva (2014-06-09 03:22:25)

    I realized that since I was not using EFISTUB, I could not mount the ESP to /boot; it had to be /boot/efi. A quick remount-reinstall of grub, then rerunning grub-mkconfig solved the issue.
    Also, regarding WonderWoofy's suggestion: I learned by trying gummiboot that for whatever reason the kernel hadn't compiled properly when I ran
    pacstrap /mnt base base-devel
    Fixed via
    pacman -S linux
    Thanks for your help, everybody!

  • [SOLVED] Fresh Install, won't boot past grub

    I did a fresh install of Arch (GPT partitioning table) with a 8 GB root directory, 138 GB home directory, 4 GB swap, and a 1007 KB bios boot partition. Everything went well, I got through the installation with no problems, but when I rebooted the computer. It showed this after the grub menu: https://lh6.googleusercontent.com/-UM-3 … 2014-06-22
    So now my question is, was I supposed to do anything extra during the installation process? Or is this a hardware problem? Linux Mint, Ubuntu, Lubuntu, and Zorin OS works fine so I'm assuming I need to do something extra during installation...
    Last edited by ryukiri (2014-07-03 21:44:44)

    Trilby wrote:
    ryukiri wrote:That only tells me how to make it a boot option...I assume I need to be chrooted from the install CD to do this.
    You can do it one of two ways: boot the install cd/usb, mount all the partitions as in the original installation process, then chroot.  From there you can just use pacman to install packages as it it were a normal system: `pacman -S linux-lts`.
    There is, however, no need for the chroot.  The alternative, and somewhat simpler, approach would be to boot the install media and mount the partitions as above, then use the pacstrap tool just like you did when installing the 'base' group: `pacstrap -i /mnt linux-lts`.
    I think it is safer to arch-chroot because you still need to be chrooted to generate your grub.cfg "grub-mkconfig -o /boot/grub/grub.cfg"
    Last edited by ugjka (2014-07-03 08:24:30)

Maybe you are looking for