[solved] GRUB parameters for specific kernel

Is any way for putting options in _specific_ kernel and not using GRUB_CMDLINE_LINUX_DEFAULT? I want to pass
"apparmor=1 security=apparmor"
in linux-apparmor
Thanks a lot,
Last edited by xanb (2015-03-09 11:37:04)

xanb wrote:
mkoskar wrote:Have you looked inside "/etc/grub.d/"?
What about "/etc/grub.d/40_custom"?
This is not exactly what I want: I have already defined the entries. So I don't need to have specific entries (40_custom is for that purpose).
I have "GRUB_DEFAULT='gnulinux-advanced-ef7df8c4-97a9-45d9-a80e-7a16254034b0>gnulinux-linux-advanced-ef7df8c4-97a9-45d9-a80e-7a16254034b0'" in /etc/default/grub. I wonder if I could add CMDLINE only to this entry....
Please post following:
# grep -E '^menuentry' /boot/grub/grub.cfg
$ ls -la /boot/vmlinuz-*
$ ls -la /vmlinuz-*
$ ls -la /boot/kernel-*
$ grep -Ev '^(#|$)' /etc/default/grub
You say you installed "linux-apparmor", I assume it drops kernel in /boot, and then you just regenerate grub which picks it up. Right?
Just go to /boot/grub/grub.cfg and take the whole relevant menuentry and paste it in /etc/grub.d/40_custom, there just modify it to your liking.

Similar Messages

[SOLVED] Grub seems to ignore kernel parameters

Hi,
I have the impression that grub ignores all kernel parameters that I added after installing arch.
The relevant lines in /etc/default/grub look like:
GRUB_CMDLINE_LINUX_DEFAULT="cryptdevice=/dev/sda2:LvmOnLuks root=/dev/mapper/LvmOnLuks-root resume=/dev/LvmOnLuks/swap"
GRUB_CMDLINE_LINUX="acpi_osi= add_efi_memmap i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1"
After generation the kernel line /boot/grub/grub.cfg looks like:
linux /boot/vmlinuz-linux root=UUID=1c05593f-4bfc-4b1f-a0ab-c9ef8f6e97fa rw acpi_osi= add_efi_memmap i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 cryptdevice=/dev/sda2:LvmOnLuks root=/dev/mapper/LvmOnLuks-root resume=/dev/LvmOnLuks/swap
Until this point everything is ok.
But /proc/cmdline give me:
BOOT_IMAGE=/vmlinuz-linux root=UUID=1c05593f-4bfc-4b1f-a0ab-c9ef8f6e97fa rw quiet cryptdevice=/dev/sda2:LvmOnLuks root=/dev/mapper/LvmOnLuks-root
I get the same output from the kernel line in the grubmenu at boottime. But these are the parameters I set at arch installation, not the current ones.
Softwareversions:
linux 3.15.7-1
grub 1:2.02.beta2-4
efibootmgr 0.7.0-1
efivar 0.10-1
I have no idea what the problem could be and I hope I can get help here.
Last edited by don_philipe (2014-08-10 21:57:21)

According to https://wiki.archlinux.org/index.php/AS … _backlight no value is needed for this parameter. The other parameters are also taken from this wiki page https://wiki.archlinux.org/index.php/AS … Parameters.
Edit:
I just tried it without the acpi_osi= parameter, but nothing changed.
Last edited by don_philipe (2014-08-04 16:53:39)

[SOLVED] Grub entry for Arch console-mode

Is there any way to add a grub menuentry to start arch without x?
Last edited by Quatro (2014-08-21 00:14:42)

By menuentry i assume you mean one other than the default for arch.
There is, I believe this may help you. https://wiki.archlinux.org/index.php/GR … b-mkconfig
Currently on phone so its too hard to give exact instructions atm. Internets out -.-

[solved] Grub config file, upgrading kernel

Hi!
I can't see what I've done wrong here, so I'd be really grateful if one of you could help me out. Heres my menu.lst:
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz]
root (hd0,1)
kernel /boot/vmlinuz root=/dev/discs/disc0/part2 ro
# (1) Arch 2.4
title Arch Linux 2.4 [/boot/vmlinuz-2.4]
root (hd0,1)
kernel /boot/vmlinuz-2.4 root=/dev/discs/disc0/part2 ro
# (2) Arch 2.6
title Arch Linux 2.6 [/boot/vmlinuz26]
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/discs/disc0/part2 devfs=nomount ro
Thanks!
From Alan

Have you recently updated your kernel?
in that case, you lack the line
initrd /boot/initrd26.img
after the kernel line.
What is happening? have all kernels suddenly stopped booting? Have you recently fiddled around with the kernel, boot or something? upgraded or otherwise. Or have you only used pacman, and upgraded something else?
Give us some meat on the bones

[SOLVED] Grub error 18 - cannot boot to Windows

Earlier today I tried to install Arch 64bit (I had 32bit earlier) with kdemod to test new KDE4.2. However, after installation I could not boot neither Arch nor Windows. Grub appeared, but every single option gave me an error. I can't remember anymore which error it was, but It doesn't matter anymore. I thought I had made a really stupid and basic mistake while installing, I just didn't know what.
I wanted to test KDE4.2 so much so I installed Kubuntu (yeah, this topic is not related to Arch Linux, I hope that somebody can help me though, move this topic to somewhere else if it doesn't belong here ). Installation was fine, booting to Kubuntu was fine (and upgrading to KDE4.2 was fine), but booting to Windows was not. It gave me a following error:
Error 18: Selected cylinder exceeds maximum supported by BIOS
I googled a bit and found this: http://wiki.linuxquestions.org/wiki/GRUB#Error_18 I reinstalled Kubuntu using /dev/sdb1 as /boot and /dev/sdb2 as / (/dev/sdb3 is windows and /dev/sdb4 is my game partition, ntfs). Before this I had /dev/sdb1 as / and /dev/sdb2 as swap (now I have no swap at all, my 4GB RAM should be enough). The only difference was that at first grub gave me error 15 (I fixed it with Kubuntu LiveCD). After that - no difference.
I need Windows for playing. That's why it's very important that I can use it. [SOLVED] In addition, I should say that /dev/sda is a separated hard drive which is encrypted with Truecrypt. (I said this because I think that Kubuntu tried to install grub on (hd0)...) When I tried to mount this hard drive with Kubuntu, it couldn't do it. I wanted to test mounting on Windows to check if it is just Kubuntu's problem. If not, I'm fucked because this hard drive contains VERY VERY VERY IMPORTANT files. [/SOLVED]
I really need help, please. If somebody can help me, (s)he is my hero.
Last edited by Exitium (2009-01-29 14:42:32)

Oops, I forgot:
menu.lst:
(Yup, a lot of comments, Ubuntu style)
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=504fab5b-7bb6-4b20-af58-83677386de37
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Ubuntu 8.10, kernel 2.6.27-11-generic
uuid 504fab5b-7bb6-4b20-af58-83677386de37
kernel /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro quiet splash
initrd /initrd.img-2.6.27-11-generic
quiet
title Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
uuid 504fab5b-7bb6-4b20-af58-83677386de37
kernel /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro single
initrd /initrd.img-2.6.27-11-generic
title Ubuntu 8.10, memtest86+
uuid 504fab5b-7bb6-4b20-af58-83677386de37
kernel /memtest86+.bin
quiet
title Wintoosa
root (hd1,2)
savedefault
makeactive
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1
fdisk -l
(Note: These results are mainly in Finnish. It could be hard to you to read it... But whatever... I'll translate these only if necessary)
Levy /dev/sda: 640.1 Gt, 640135028736 tavua
255 päätä, 63 sektoria/ura, 77825 sylinteriä
Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
Levyn tunniste: 0xcc5d88e2
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sda1 * 244091 485122 1936074870+ b8 BSDI sivutus
Osion 1 loppu ei ole sylinterin rajalla.
/dev/sda2 176430 394864 1754572509+ 43 Tuntematon
Osion 2 loppu ei ole sylinterin rajalla.
/dev/sda3 177329 413105 1893868925 29 Tuntematon
Osion 3 loppu ei ole sylinterin rajalla.
/dev/sda4 57435 309703 2026342066 5c Priam Edisk
Osion 4 loppu ei ole sylinterin rajalla.
Osiotaulumerkinnät eivät ole levyjärjestyksessä
Levy /dev/sdb: 500.1 Gt, 500107862016 tavua
255 päätä, 63 sektoria/ura, 60801 sylinteriä
Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
Levyn tunniste: 0x0007a52a
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sdb1 1 128 1028128+ 83 Linux
/dev/sdb2 129 13185 104880352+ 83 Linux
/dev/sdb3 13186 26239 104856255 7 HPFS/NTFS
/dev/sdb4 26240 60801 277619265 7 HPFS/NTFS
Last edited by Exitium (2009-01-28 21:05:33)

[SOLVED] Send diff Parameters to diff kernels w/GRUB2 &survive updates

1. Installed LMDE.
2. Loaded the core ARCH and all went well - loaded necessary drivers for my soundcard and video and all is well
3. Discovered early with the first distro installs that the linux kernel does not handle synaptic touchpad devices well during the PM suspend and resume process.
4. The cure is to add atkbd.reset to a command line in the grub file - then update grub and end result - touchpad works great after resume.
5. Now, since grub was already installed I bypassed that during ARCH setup. Went into LMDE and mounted the root for ARCH and then installed OS-prober - ran update-grub and now when my comp starts up I have a grub menu the allows me to choose which distro to choose.
SO QUESTION IS - How do i get grub to send parameters to the kernel for ARCH that are different from parameters being sent to LMDE??
Temporary Solution is to edit the grub.cfg file directly - Just worried about updates to grub erasing my manual adjustments!!!
Permanent Solution you will find at the bottom of this topic post #22.
Last edited by iamk2 (2013-03-27 00:50:07)

[RESOLVED] - How to Send different Parameters to diff. kernels with grub? AND retain these setting automatically even after using update-grub. NOTE this will not prevent any overwrites to your grub.d scripts via pacman. Wonder ho often this actually occurs???
For any one out there that has two or more Linux distro's installed on one PC and uses OS-Prober to locate the 2nd, 3rd, etc.., distro's for the grub2 menu, here is a risk free solution that allows you to send parameters to other kernels as well as your first installed one (or the one you have installed with grub2).
(I say risk free because if your into ARCH, I would believe you have some skill and competence)
1. Edit /etc/grub.d/30_os-prober with root permission
find the code line containing
linux ${LKERNEL} ${LPARAMS}
append ${GRUB_CMDLINE_LINUX_DEFAULT} to the end of this line
It should now look like this:
linux ${LKERNEL} ${LPARAMS} ${GRUB_CMDLINE_LINUX_DEFAULT}
Save the file
2. Open terminal if need be and
sudo update-grub
This will attach the same parameters form your existing GRUB_CMDLINE_LINUX_DEFAULT in the /etc/default grub file to other distro's found by OS-Prober.
3. Now if you wanted to send different parameters to the distro's found by OS-Prober, then instead of
linux ${LKERNEL} ${LPARAMS} ${GRUB_CMDLINE_LINUX_DEFAULT}
make it like something like this
linux ${LKERNEL} ${LPARAMS} ${GRUB_CMDLINE_OS_PROBER_FINDS_DEFAULT}
Then got to your /etc/defaults grub file and insert
GRUB_CMDLINE_OS_PROBER_FINDS_DEFAULT
so that your grub file now looks like this
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash atkbd.reset acpi_osi=\"Linux\""
GRUB_CMDLINE_LINUX="atkbd.reset"
GRUB_CMDLINE_OS-PROBER-FINDS_DEFAULT="your parameters"
Now to send completely different parameters to each and every kernel is a game I wonder about but not interested at this time in solving.
Last edited by iamk2 (2013-03-27 01:55:56)

Calculating Kernel parameters for Oracle 11g R2 db on solaris 10u9

Hi Everyone,
I have query regarding calculating the kernel parameters for deploying oracle 11g R2 db on solaris 10 v 5.10 update 09 machine , we have Ram size of 64gb.
My question is how to calculate shared memory ,shared memory identifiers,semaphores, semaphores identiifiers for creating resource control for the project(user.oracle).
And how to fine out the available semphore values allocated in system..
Thanks in Advance.
Edited by: 898979 on Dec 15, 2011 10:24 PM

Hi;
For those setting mention in installation guide which is already shared previous post.
I suggest also see:
Oracle Database on Unix AIX,HP-UX,Linux,Mac OS X,Solaris,Tru64 Unix Operating Systems Installation and Configuration Requirements Quick Reference (8.0.5 to 11.2) [ID 169706.1]
Regard
Helios

[Solved] Init not found for new kernels

Hello everyone,
I am experiencing this error message when booting using either the linux-3.7.x or linux-ck-3.8.x kernels. I would investigate towards something being wrong with systemd (i.e. the init= line suggested), but the system boots perfectly fine using linux-lts-3.0.56.1.
Relevant information I can think of:
/ is ext4, LVM. The lvm -3 update has not been done yet.
mkinitcpio 0.13.0-1
I am mostly interested in any direction towards what to investigate -- the fact that there is something wrong with the init not being found, but only for certain kernels, perplexes me.
Thanks for any help,
Jan
(My apologies for the quality.)
http://i.imgur.com/Tv276ds.jpg
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by Zuiop (2013-03-06 20:35:51)

/usr is on /.
Here is what lsinitcpio gives me. They all include /usr/bin/init, and in fact the same init related things.
~ /boot for i in initramfs-linux-lts.img initramfs-linux.img initramfs-linux-ck.img ; do
print $i
lsinitcpio $i | grep init
done
initramfs-linux-lts.img
./init
./init_functions
./usr/bin/init
./usr/lib/udev/rules.d/11-dm-initramfs.rules
./etc/initrd-release
initramfs-linux.img
./init
./init_functions
./usr/bin/init
./usr/lib/udev/rules.d/11-dm-initramfs.rules
./etc/initrd-release
initramfs-linux-ck.img
./init
./init_functions
./usr/bin/init
./usr/lib/udev/rules.d/11-dm-initramfs.rules
./etc/initrd-release
Full output (is there a spoiler tag? couldn't find one)
http://paste.kde.org/688802/
Thanks for your continuing help!

[SOLVED]Problematic upgrade to newest kernel 3.10.5-1

Aloha, guys. I've just had a miserably failed upgrade to the latest kernel, probably due to something I had misconfigured and hadn't noticed before.
I was running 3.10 already perfectly before this last update to 3.10.5-1 (x86_64), but as soon as I rebooted after upgrading to the brand spanking new kernel, I got the fsck warning other people mentioned around this forum - corrected already in my syslinux.cfg by replacing ro with rw in the append line.
Both with ro and rw in the append line the boot process hangs (afterall, that fsck warning wouldn't stop the laptop from booting). The problem I'm having is that udev is not starting, meaning that boot hangs with lots of failed udev warnings.
The first one that comes up is "Failed to start udev Coldplug all Devices", and "Failed to start udev Kernel Device Manager" from then on until the boot process just hangs.
I've chrooted and tried rebuilding the initramfs, but it's giving me an "invalid kernel specified: 'boot/vmlinuz-linux'" error.
Right now I'm totally at a loss, as I cannot even begin to troubleshoot it any further. I hadn't kept the older kernel pkg in order to downgrade, but would like to try correcting this before eventually downgrading - as that just temporarily solves my problem.
My mkinitcpio hooks were "base udev autodetect modconf block filesystems keyboard fsck" and I've never had any previous problems with my initramfs. I know I may be missing something basic, or some further information needed to troubleshoot it, so please, please, please, just let me know and I will provide it here.
Any help will be greatly appreciated! Thanks in advance!
Last edited by Onyros (2013-08-07 21:03:54)

This must be something specific about your system - I have three machines running without any problem with kernel 3.10.5-1 - one uses the latest grub 2.00.5086-1, and the other two boot with rEFInd. All three boot fine and are stable.
Did you have any customisation in your mikinitcpio.conf or kernel parameters during boot?
In case it is of interest here is the output in my pacman log for the kernel update section:
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-08-07 13:23] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-08-07 13:23] [ALPM-SCRIPTLET] ==> Image generation successful
Last edited by mcloaked (2013-08-07 13:29:16)

[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!

Comment or attach document for specific cell of data

Dear all,
Is it possible to create comment or attached document for specific cell of data in Webi report?
For example, the sales of certain product & yearmonth is lower than previous month. I want write some comment for that cell of data . Which function should I use? I try the "Discussion" function. But, it's for the whole report not for certain range of data and I can't attached document in there. Please advise.
Thx,
Jeff

Hi Jeff,
This one is the most popular request from most of our customers. But what we always tell the client is that the reports that are created in webintelligence are analytical in nature and it is not cell based. For every refresh of the report, you may get different results based on the parameters and your annotation will not hold good.
We suggest two methods to solve this issue. 1) Discussions - Standard text with the parameters used for refreshing and the observation. This would be a good option if the report is shared with many people.
2) Add a cell to the report, place it at the right place adjacent to the block which you want to observe. Make your comments in different colors. This would be good for reports which need to be presented to some audience.
The below link shows a prototype called Comment It for Crystal Reports. But I don't think this is available for webintelligence.
Comment it [original link is broken]
Thanks
Mohanraj CP
http://blog.mohanraj.org

Security parameters in the kernel do not meet the minimum requirements

Hello,
I am installing Oracle AS Infrastructure.
My overall system checkup was fine but of kernel has following message.
checking for hardnofiles = 65536 found hardnofiles = 1024 Failed
checking for softnofiles = 4096; softnofiles = 1024
Problem:
The security parameters in the kernel do not meet the minimum requirements.
Recommendation: Perform OS System specific instruction to update kernel parameter, namely BIT_SIZE and NON_EXEC_USER_STACK.
After that I have checked /etc/security/limits.conf file values were correct.
But my /proc/sys/net/ipv4/ip_local_port_range
values were 1024 65000 --
they are correct in sysctl.conf file
But any way I have fixed that.
Also /pro/sys/kernel/shmni was 1000, so I make it 4096
Actually in the start of setting up requirements,
I have tried to make changes of kernel through /proc/sys/.....
But after that I have created sysctl.conf file and put all recommended values and restart the system.
So I continue installation.
Is it ok?
Regards,
DN

I have changed to
/etc/security/limits.conf:
* hard nofile 65536 --- I removed this line also
* soft nproc 2047
* hard nproc 16384
* soft nofile 16384
* hard nofile 65536
after that I got the values as below
ulimit -Hn
1024ulimit -Sn
1024I run ulimit -u 1384 -n 65536
ulimit -Hn
65536ulimit -Sn
65536I put the values back and reboot system.
* hard nofile 65536
* soft nproc 2047
* hard nproc 16384
* soft nofile 2048
* hard nofile 65536
Right away from the terminal, its give me values again
ulimit -Hn
1024ulimit -Sn
1024But after some time remotely (SSH) I have checked
abc:~ # ulimit -Hn
65536
abc:~ # ulimit -Sn
2048
dhsappserver1:~ #
DN

Kdump: No crashkernel parameter specified for running kernel

Hi all,
Does someone know how to solve this problem: kdump: No crashkernel parameter specified for running kernel
kdump refuses to start during system start
I did a fresh installation of Oracle Linux 6.3, but OL6.3 seems to be buggy from the very beginning.
Thanks a lot.

Did you enable "kdump" during the installation? By default it is disabled.
Unless you know what kdumps are used for chances are most likely that you really don't need it.
Your problem seems to be described in the OS release notes:
https://oss.oracle.com/ol6/docs/RELEASE-NOTES-U3-en.html
+6. kdump service fails to start with Unbreakable Enterprise Kernel+
When configuring the crash kernel for the UEK, only standard crash kernel settings, e.g. crashkernel=128M@32M, are supported. The new setting used by the RHCK, i.e. crashkernel=auto, is not supported and will cause the kdump service to fail to start.
What is the content of /etc/grub.conf file?
Here is an older similar thread that might be useful:
Kdump Not Starting On 2.6.32-200.13.1.el5uek No crashkernel parameter spec

Define read-only authorization for specific field(s) on a form for 11.5.9

Dear all,
Can you pls let me know how is it possible to define read-only authorization access for specific field(s) per responsibility / user on a form in 11.5.9?
For example I want to protect the item master file by assigning for example to users with responsibility buyer authorization to modify the buyer information but to have read-only only authorization on other sensitive fields such as make/buy flag, expense accounts, etc
Through UI Modeller I have only managed to make specific fields on specific forms invisible, or whole tabs invisible, to specific responsibilities but this does not cover my needs as I want them to be able to view the data of the fields but to not be able to update them

Arun,
Almost but not quite.. The example you've given has the person VO at the top level which includes all the id's (City, State etc). My use case is slightly different.
query 1
     select org_id, OrgName from x;
query 2
     select emp_id, emp_name from y where org_id = x.org_id
query 3
     multi-table join (approx 9 tables) to retrieve depts associated to employee
     where org_id = x.org_id
     and emp_id = y.emp_id
Rather than using LOV's would it be better to create VO's and pass in the bind parameters at run time?

Authorization for specific business scenario or business step in solar01

Dear all,
we have an issue regarding solution manager blueprinting management restricting an access to specific nodes. Our goar is to have several substructures devided by modules like: FI, SD, PS and etc. And each team member according his position in a company should have an access only to his substructure and all the related documentation below that. Saying an access means a change mode not a display access.
Please find the steps have been performed during the configuration of project below:
All the configuration around system landscape has been done properly.
A new project for solution was created in solar_project_admin.
A correct logical componens has been assigned.
All the required users have assigned as a team members of a project.
At the projec. team member tab a box has been checked in for: restrict changes to nodes in project to assigned team members.
A proposed structure of nodes has been created within Tx solar02.
The right team members have assigned to specific node. So that only they suppose to have a change permission within that nodes. All others read only access.
Every user has sap_solar01_all role assigned to him. We have tryed assigning varios roles according to http://help.sap.com/saphelp_sm310/helpdata/en/db/a1033b2a98f46ae10000000a11402f/content.htm
However as a result we are having a change permission allowed for every node within the structure. Like FI responsible member can access to any node from a tree. And he can make a change for SD related documentation.
Please assist regarding this issue.
Kind regards,
P.S.
I found a thread with a similar problem which was solved by activating a checkbox which is already activated in our system and actually doesn't solve that problem for us.
Authorization for specific business scenarios in Solar01/02
Edited by: Artjoms Nikulins on Mar 11, 2010 3:37 PM

Hi
As far my knowldege goes this is not possible to do within same project or making the same.
You can have project specific access given to member but you cannot go module wise authorization.
Ofcourse there satellite system authorization will be different but not in solman.
In addition check this security guide
https://websmp104.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000075728&_OBJECT=011000358700007187872005E
Hope it ans ur query.
Regards
Prakhar
Edited by: Prakhar Saxena on Mar 12, 2010 3:22 AM

[solved] GRUB parameters for specific kernel

Similar Messages

Maybe you are looking for