text:
GRUB2 is the next generation of the GRand Unified Bootloader (GRUB). GRUB2 is derived from PUPA which was a research project to investigate the next generation of GRUB. GRUB2 has been rewritten from scratch to clean up everything and provide modularity and portability [1].
In brief, the bootloader is the first software program that runs when a computer starts. It is responsible for loading and transferring control to the Linux kernel. The kernel, in turn, initializes the rest of the operating system.
Here is some information that needs to be clarified:
- The name GRUB officially refers to version 2 of the software, see [2]. If you are looking for the article on the legacy version, see GRUB Legacy.
From 1.99-6 onwards, GRUB2 supports Btrfs as root (without a separate
/bootfilesystem) compressed with either zlib or LZO.
- For GRUB2 UEFI info, it is recommended to read the UEFI, GPT and UEFI Bootloaders pages before reading this page.
Notes for current GRUB Legacy users
- Upgrade from GRUB Legacy to GRUB2 is the much same as fresh installing GRUB2 which is coveredbelow.
- There are differences in the commands of GRUB and GRUB2. Familiarize yourself with GRUB2 commands before proceeding (e.g. "find" has been replaced with "search").
- GRUB2 is now modular and no longer requires "stage 1.5". As a result, the bootloader itself is limited -- modules are loaded from the hard drive as needed to expand functionality (e.g. for LVM or RAID support).
Device naming has changed between GRUB and GRUB2. Partitions are numbered from 1 instead of 0 while drives are still numbered from 0, and prefixed with partition-table type. For example,
/dev/sda1would be referred to as
(hd0,msdos1)(for MBR) or
(hd0,gpt1)(for GPT) using GRUB2.
Preliminary Requirements for GRUB2
BIOS systems
GUID Partition Table (GPT) specific instructions
GRUB2 in BIOS-GPT configuration requires a BIOS Boot Partition to embed its
core.img in the absence of post-MBR gap in GPT partitioned systems (which is taken over by the GPT Primary Header and Primary Partition table). This partition is used by GRUB2 only in BIOS-GPT setups. No such partition type exists in case of MBR partitioning (at least not for GRUB2). This partition is also not required if the system is UEFI based, as no embedding of bootsectors takes place in that case. Syslinux does not require this partition.
For a BIOS-GPT configuration, create a 1007 KiB partition at the beginning of the disk using cgdisk or GNU Parted with no filesystem. The size of 1007 KiB will allow for the following partition to be correctly alligned at 1024 KiB. If needed, the partition can also be located somewhere else on the disk, but it should be within the first 2 TiB region. Set the partition type to
0xEF02 in gdisk,
EF02 in cgdisk or
set <BOOT_PART_NUM> bios_grub on in GNU Parted.
Master Boot Record (MBR) specific instructions
Usually the post-MBR gap (after the 512 byte MBR region and before the start of the 1st partition) in many MBR (or msdos disklabel) partitioned systems is 31 KiB when DOS compatibility cylinder alignment issues are satisfied in the partition table. However a post-MBR gap of about 1 to 2 MiB is recommended to provide sufficient room for embedding GRUB2's
core.img (FS#24103). It is advisable to use a partitioner which supports 1 MiB partition alignment to obtain this space as well as satisfy other non-512 byte sector issues (which are unrelated to embedding of
MBR partitioning has better support in other operating systems, such as Microsoft Windows (up to Windows 7) and Haiku, than GPT partitioning. If you dual boot another operating system, consider using MBR partitioning.
A MBR disk may be convertible to GPT if there is a small amount of extra space available. See GUID Partition Table#Convert from MBR to GPT
UEFI systems
Create and Mount the UEFI System Partition
Follow Unified Extensible Firmware Interface#EFI System Partition for instructions on creating a UEFI SYSTEM PARTITION. Then mount the UEFI SYSTEM PARTITION at
/boot/efi. If you have mounted the UEFISYS partition in some other mountpoint, replace
/boot/efi in the below instructions with that mountpoint:
# mkdir -p /boot/efi # mount -t vfat <UEFISYS_PART_DEVICE> /boot/efi
Create a <UEFI_SYSTEM_PARTITION>
/EFI directory, if it does not exist:
# mkdir -p /boot/efi/EFI
BIOS systems
Backup Important Data
Although a GRUB(2) installation should run smoothly, it is strongly recommended to keep the GRUB Legacy files before installing grub-bios.
# mv /boot/grub /boot/grub-legacy
Backup the MBR which contains the boot code and partition table (Replace
/dev/sdX with your actual disk path)
# dd if=/dev/sdX of=/path/to/backup/mbr_backup bs=512 count=1
Only 446 bytes of the MBR contain boot code, the next 64 contain the partition table. If you do not want to overwrite your partition table when restoring, it is strongly advised to backup only the MBR boot code:
# dd if=/dev/sdX of=/path/to/backup/bootcode_backup bs=446 count=1
If unable to install GRUB2 correctly, see #Restore GRUB Legacy.
Install grub-bios package
The GRUB(2) packages can be installed with pacman (and will replace grub-legacy or grub, if it is installed):
# pacman -S grub-bios
Install grub-bios boot files
There are 3 ways to install GRUB(2) boot files in BIOS booting:
- #Install to GPT BIOS Boot Partition (recommended with GPT)
- #Install to 440-byte MBR boot code region (recommended with MBR)
- #Install to Partition or Partitionless Disk (not recommended)
#Generate core.img alone (safest method, but requires another BIOS bootloader like grub-legacy orsyslinux to be installed to chainload
Install to 440-byte MBR boot code region
To setup
grub-bios in the 440-byte Master Boot Record boot code region, populate the
/boot/grubdirectory, generate the
/boot/grub/i386-pc/core.img file, embed it in the 31 KiB (minimum size - varies depending on partition alignment) post-MBR gap, and generate the configuration file, run:
# modprobe dm-mod # grub-install --recheck /dev/sda # grub-mkconfig -o /boot/grub/grub.cfg
/dev/sda is the destination of the installation (in this case the MBR of the first SATA disk). If you useLVM for your
/boot, you can install GRUB2 on multiple physical disks.
Install to GPT BIOS Boot Partition
GUID Partition Table disks do not have a reserved "boot track". Therefore you must create a BIOS Boot Partition (0xEF02) to hold the GRUB core image.
Using GNU Parted, you can set this using a command such as the following:
# parted /dev/disk set <partition-number> bios_grub on
If you are using gdisk, set the partition type to
0xEF02. With partitioning programs that require setting the GUID directly, it should be
'21686148-6449-6e6f-744e656564454649' (stored on disk as
"!haHdInotNeedEFI" if interpreted as ASCII).
To setup
grub-bios on a GPT disk, populate the
/boot/grub directory, generate the
/boot/grub/i386-pc/core.img file, and embed it in the BIOS Boot Partition, run:
# modprobe dm-mod # grub-install --target=i386-pc --recheck --debug /dev/sda # mkdir -p /boot/grub/locale # cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
/dev/sda is the destination of the installation.
Install to Partition or Partitionless Disk
To set up
grub-bios to a partition boot sector, to a partitionless disk (also called superfloppy) or to a floppy disk, run (using for example
/dev/sdaX as the
/boot partition):
# modprobe dm-mod # grub-install --target=i386-pc --recheck --debug --force /dev/sdaX # chattr -i /boot/grub/i386-pc/core.img # mkdir -p /boot/grub/locale # cp /usr/share/locale/en@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo # chattr +i /boot/grub/i386-pc/core.img
You need to use the
--force option to allow usage of blocklists and should not use
--grub-setup=/bin/true (which is similar to simply generating
grub-install will give out warnings like which should give you the idea of what might go wrong with this approach:
/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea. /sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.
--force you may get the below error and
grub-setup will not setup its boot code in the partition boot sector:
/sbin/grub-setup: error: will not proceed with blocklists
--force you should get:
Installation finished. No error reported.
The reason why
grub-setup does not by default allow this is because in case of partition or a partitionless disk is that
grub-bios relies on embedded blocklists in the partition bootsector to locate the
/boot/grub/i386-pc/core.img file and the prefix dir
/boot/grub. The sector locations of
core.imgmay change whenever the filesystem in the partition is being altered (files copied, deleted etc.). For more info see https://bugzilla.redhat.com/show_bug.cgi?id=728742 and https://bugzilla.redhat.com/show_bug.cgi?id=730915.
The workaround for this is to set the immutable flag on
/boot/grub/i386-pc/core.img (using chattr command as mentioned above) so that the sector locations of the
core.img file in the disk is not altered. The immutable flag on
/boot/grub/i386-pc/core.img needs to be set only if
grub-bios is installed to a partition boot sector or a partitionless disk, not in case of installation to MBR or simple generation of
core.img without embedding any bootsector (mentioned above).
Generate core.img alone
To populate the
/boot/grub directory and generate a
/boot/grub/i386-pc/core.img file withoutembedding any
grub-bios bootsector code in the MBR, post-MBR region, or the partition bootsector, add
--grub-setup=/bin/true to
# modprobe dm-mod # grub-install --target=i386-pc --grub-setup=/bin/true --recheck --debug /dev/sda # mkdir -p /boot/grub/locale # cp /usr/share/locale/en@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
You can then chainload GRUB2's
core.img from GRUB Legacy or syslinux as a Linux kernel or a multiboot kernel.
Generate GRUB2 BIOS Config file
Finally, generate a configuration for GRUB2 (this is explained in greater detail in the Configuration section):
# grub-mkconfig -o /boot/grub/grub.cfg
If grub(2) complains about "no suitable mode found" while booting, go to #Correct GRUB2 No Suitable Mode Found Error.
grub-mkconfig fails, convert your
/boot/grub/menu.lst file to
/boot/grub/grub.cfg using:
# grub-menulst2cfg /boot/grub/menu.lst /boot/grub/grub.cfg
For example:
default=0 timeout=5 title Arch Linux Stock Kernel root (hd0,0) kernel /vmlinuz-linux root=/dev/sda2 ro initrd /initramfs-linux.img title Arch Linux Stock Kernel Fallback root (hd0,0) kernel /vmlinuz-linux root=/dev/sda2 ro initrd /initramfs-linux-fallback.img
set default='0'; if [ x"$default" = xsaved ]; then load_env; set default="$saved_entry"; fi set timeout=5 menuentry 'Arch Linux Stock Kernel' { set root='(hd0,1)'; set legacy_hdbias='0' legacy_kernel '/vmlinuz-linux' '/vmlinuz-linux' 'root=/dev/sda2' 'ro' legacy_initrd '/initramfs-linux.img' '/initramfs-linux.img' } menuentry 'Arch Linux Stock Kernel Fallback' { set root='(hd0,1)'; set legacy_hdbias='0' legacy_kernel '/vmlinuz-linux' '/vmlinuz-linux' 'root=/dev/sda2' 'ro' legacy_initrd '/initramfs-linux-fallback.img' '/initramfs-linux-fallback.img' }
If you forgot to create a GRUB2
/boot/grub/grub.cfg config file and simply rebooted into GRUB2 Command Shell, type:
sh:grub> insmod legacycfg sh:grub> legacy_configfile ${prefix}/menu.lst
Boot into Arch and re-create the proper GRUB2
/boot/grub/grub.cfg config file.
Multiboot in BIOS
Boot Microsoft Windows installed in BIOS-MBR mode
Find the UUID of the NTFS filesystem of the Windows's SYSTEM PARTITION where the
bootmgr and its files reside. For example, if Windows
bootmgr exists at
For Windows Vista/7/8:
# grub-probe --target=fs_uuid /media/SYSTEM_RESERVED/bootmgr 69B235F6749E84CE
# grub-probe --target=hints_string /media/SYSTEM_RESERVED/bootmgr --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1
Then, add the below code to
/etc/grub.d/40_custom or
/boot/grub/custom.cfg and regenerate
grub.cfg with
grub-mkconfig as explained above to boot Windows (XP, Vista, 7 or 8) installed in BIOS-MBR mode:
For Windows Vista/7/8:
menuentry "Microsoft Windows Vista/7/8 BIOS-MBR" { insmod part_msdos insmod ntfs insmod search_fs_uuid insmod ntldr search --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 69B235F6749E84CE ntldr /bootmgr }
For Windows XP:
menuentry "Microsoft Windows XP" { insmod part_msdos insmod ntfs insmod search_fs_uuid insmod ntldr search --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 69B235F6749E84CE ntldr /ntldr }
/etc/grub.d/40_custom can be used as a template to create
/etc/grub.d/nn_custom. Where nn defines the precendence, indicating the order the script is executed. The order scripts are executed determine the placement in the grub boot menu.
UEFI systems
Hardware-Specific UEFI Examples
It is well know that different motherboard manufactures implement UEFI differently. Users experiencing problems getting Grub/EFI to work properly are encouraged to share detailed steps for hardware-specific cases where UEFI booting does not work as described below. In an effort to keep the parent GRUB article neat and tidy, see the GRUB EFI Examples page for these special cases.
Install grub-uefi package
GRUB(2) UEFI bootloader is available in Arch Linux only from version 1.99~rc1. To install, first detect which UEFI firmware arch you have (either x86_64 or i386).
Depending on that, install the appropriate package
For 64-bit aka x86_64 UEFI firmware:
# pacman -S grub-efi-x86_64
For 32-bit aka i386 UEFI firmware:
# pacman -S grub-efi-i386
Install grub-uefi boot files
Install to UEFI System Partition
The UEFI system partition will need to be mounted at
/boot/efi/ for the GRUB(2) install script to detect it:
# mkdir -p /boot/efi # mount -t vfat /dev/sdXY /boot/efi
Install GRUB UEFI application to
/boot/efi/EFI/arch_grub and its modules to
/boot/grub/x86_64-efi (recommended) using:
# modprobe dm-mod # grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck --debug # mkdir -p /boot/grub/locale # cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
If you want to install grub(2) modules and
grub.cfg at the directory
/boot/efi/EFI/grub and the
grubx64.efi application at
/boot/efi/EFI/arch_grub (ie. all the grub(2) uefi files inside the UEFISYS partition itself) use:
# modprobe dm-mod # grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --boot-directory=/boot/efi/EFI --recheck --debug # mkdir -p /boot/efi/EFI/grub/locale # cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/efi/EFI/grub/locale/en.mo
--efi-directory option mentions the mountpoint of UEFI SYSTEM PARTITION ,
--bootloader-idmentions the name of the directory used to store the
grubx64.efi file and
--boot-directory mentions the directory wherein the actual modules will be installed (and into which
grub.cfg should be created).
The actual paths are:
<efi-directory>/<EFI or efi>/<bootloader-id>/grubx64.efi
<boot-directory>/grub/x86_64-efi/<all modules, grub.efi, core.efi, grub.cfg>
--efi-directory=/boot/efi --boot-directory=/boot/efi/EFI --bootloader-id=grub:
<efi-directory>/<EFI or efi>/<bootloader-id> == <boot-directory>/grub == /boot/efi/EFI/grub
--efi-directory=/boot/efi --boot-directory=/boot/efi/EFI --bootloader-id=arch_grub:
<efi-directory>/<EFI or efi>/<bootloader-id> == /boot/efi/EFI/arch_grub <boot-directory>/grub == /boot/efi/EFI/grub
--efi-directory=/boot/efi --boot-directory=/boot --bootloader-id=arch_grub:
<efi-directory>/<EFI or efi>/<bootloader-id> == /boot/efi/EFI/arch_grub <boot-directory>/grub == /boot/grub
--efi-directory=/boot/efi --boot-directory=/boot --bootloader-id=grub:
<efi-directory>/<EFI or efi>/<bootloader-id> == /boot/efi/EFI/grub <boot-directory>/grub == /boot/grub
<efi-directory>/<EFI or efi>/<bootloader-id>/grubx64.efi is an exact copy of
In all the cases the UEFI SYSTEM PARTITION should be mounted for
grub-install to install
grubx64.efi in it, which will be launched by the firmware (using the
efibootmgr created boot entry in non-Mac systems).
If you notice carefully, there is no <device_path> option (Eg:
/dev/sda) at the end of the
grub-installcommand unlike the case of setting up GRUB(2) for BIOS systems. Any <device_path> provided will be ignored by the install script as UEFI bootloaders do not use MBR or Partition boot sectors at all.
You may now be able to UEFI boot your system by creating a
grub.cfg file by following #Generate GRUB2 UEFI Config file and #Create GRUB2 entry in the Firmware Boot Manager.
Generate GRUB2 UEFI Config file
Finally, generate a configuration for GRUB(2) (this is explained in greater detail in the Configuration section):
# grub-mkconfig -o <boot-directory>/grub/grub.cfg
If you used
# grub-mkconfig -o /boot/grub/grub.cfg
If you used
# grub-mkconfig -o /boot/efi/EFI/grub/grub.cfg
This is independent of the value of
--bootloader-id option.
If GRUB2 complains about "no suitable mode found" while booting, try #Correct GRUB2 No Suitable Mode Found Error.
Create GRUB2 entry in the Firmware Boot Manager
As of grub-efi-x86_64 version 2.00,
grub-install automatically tries to create a menu entry in the boot manager. If it doesn't, then see Beginners' Guide#GRUB for instructions to use
efibootmgr to create a menu entry. However, the problem is likely to be that you haven't booted your CD/USB in UEFI mode, as inUnified Extensible Firmware Interface#Create UEFI bootable USB from ISO.
Create GRUB2 Standalone UEFI Application
It is possible to create a
grubx64_standalone.efi application which has all the modules embeddded in a memdisk within the uefi application, thus removing the need for having a separate directory populated with all the GRUB2 uefi modules and other related files. This is done using the
grub-mkstandalone command which is included in grub-common >= 1:1.99-6 package.
The easiest way to do this would be with the install command already mentioned before, but specifying the modules to include. For example:
# grub-mkstandalone --directory="/usr/lib/grub/x86_64-efi/" --format="x86_64-efi" --compression="xz" \ --output="/boot/efi/EFI/arch_grub/grubx64_standalone.efi" <any extra files you want to include>
grubx64_standalone.efi file expects
grub.cfg to be within its $prefix which is
(memdisk)/boot/grub. The memdisk is embedded within the efi app. The
grub-mkstandlone script allow passing files to be included in the memdisk image to be as the arguments to the script (in <any extra files you want to include>).
If you have the
grub.cfg at
/home/user/Desktop/grub.cfg, then create a temporary
/home/user/Desktop/boot/grub/ directory, copy the
/home/user/Desktop/grub.cfg to
/home/user/Desktop/boot/grub/grub.cfg, cd into
/home/user/Desktop/boot/grub/ and run:
# grub-mkstandalone --directory="/usr/lib/grub/x86_64-efi/" --format="x86_64-efi" --compression="xz" \ --output="/boot/efi/EFI/arch_grub/grubx64_standalone.efi" "boot/grub/grub.cfg"
The reason to cd into
/home/user/Desktop/boot/grub/ and to pass the file path as
boot/grub/grub.cfg (notice the lack of a leading slash - boot/ vs /boot/ ) is because
dir1/dir2/file is included as
(memdisk)/dir1/dir2/file by the
grub-mkstandalone script.
If you pass
/home/user/Desktop/grub.cfg the file will be included as
(memdisk)/home/user/Desktop/grub.cfg. If you pass
/home/user/Desktop/boot/grub/grub.cfgthe file will be included as
(memdisk)/home/user/Desktop/boot/grub/grub.cfg. That is the reason for cd'ing into
/home/user/Desktop/boot/grub/ and passing
boot/grub/grub.cfg, to include the file as
(memdisk)/boot/grub/grub.cfg, which is what
grub.efi expects the file to be.
You need to create an UEFI Boot Manager entry for
/boot/efi/EFI/arch_grub/grubx64_standalone.efi using
efibootmgr. Follow #Create GRUB2 entry in the Firmware Boot Manager.
Multiboot in UEFI
Chainload Microsoft Windows x86_64 UEFI-GPT
Find the UUID of the FAT32 filesystem in the UEFI SYSTEM PARTITION where the Windows UEFI Bootloader files reside. For example, if Windows
bootmgfw.efi exists at
/boot/efi/EFI/Microsoft/Boot/bootmgfw.efi (ignore the upper-lower case differences since that is immaterial in FAT filesystem):
# grub-probe --target=fs_uuid /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi 1ce5-7f28
# grub-probe --target=hints_string /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
Then, add this code to
/etc/grub.d/40_custom to chainload Windows x86_64 (Vista SP1+, 7 or 8) installed in UEFI-GPT mode:
menuentry "Microsoft Windows Vista/7/8 x86_64 UEFI-GPT" { insmod part_gpt insmod fat insmod search_fs_uuid insmod chain search --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 1ce5-7f28 chainloader /efi/Microsoft/Boot/bootmgfw.efi }
Afterwards remake
# grub-mkconfig -o /boot/grub/grub.cfg
You can also choose to automatically generate or manually edit
Automatically generating using grub-mkconfig (Recommended)
The GRUB2
menu.lst equivalent configuration files are
/etc/default/grub and
grub-mkconfig uses these files to generate
grub.cfg. By default the script outputs to stdout. To generate a
grub.cfg file run the command:
# grub-mkconfig -o /boot/grub/grub.cfg
/etc/grub.d/10_linux is set to automatically add menu items for Arch linux that work out of the box, to any generated configuration. Other operating systems may need to be added manually to
/etc/grub.d/40_custom or
Additional arguments
To pass custom additional arguments to the Linux image, you can set the
GRUB_CMDLINE_LINUX variable in
For example, use
GRUB_CMDLINE_LINUX="resume=/dev/sdaX" where
sdaX is your swap partition to enable resume after hibernation.
You can also use
GRUB_CMDLINE_LINUX="resume=/dev/disk/by-uuid/${swap_uuid}", where
${swap_uuid}is the UUID of your swap partition.
Multiple entries are separated by spaces within the double quotes. So, for users who want both resume and systemd it would look like this:
GRUB_CMDLINE_LINUX="resume=/dev/sdaX init=/usr/lib/systemd/systemd"
See Kernel parameters for more info.
Manually creating grub.cfg
A basic GRUB config file uses the following options
(hdX,Y)is the partition
Yon disk
X, partition numbers starting at 1, disk numbers starting at 0
set default=Nis the default boot entry that is chosen after timeout for user action
set timeout=Mis the time
Mto wait in seconds for a user selection before default is booted
menuentry "title" {entry options}is a boot entry titled
set root=(hdX,Y)sets the boot partition, where the kernel and GRUB modules are stored (boot need not be a separate partition, and may simply be a directory under the "root" partition (
An example configuration:
# Config file for GRUB2 - The GNU GRand Unified Bootloader # /boot/grub/grub.cfg # DEVICE NAME CONVERSIONS # # Linux Grub # ------------------------- # /dev/fd0 (fd0) # /dev/sda (hd0) # /dev/sdb2 (hd1,2) # /dev/sda3 (hd0,3) # # Timeout for menu set timeout=5 # Set default boot entry as Entry 0 set default=0 # (0) Arch Linux menuentry "Arch Linux" { set root=(hd0,1) linux /vmlinuz-linux root=/dev/sda3 ro initrd /initramfs-linux.img } ## (1) Windows #menuentry "Windows" { #set root=(hd0,3) #chainloader +1 #}
Using grub-mkconfig
The best way to add other entries is editing the
/etc/grub.d/40_custom or
/boot/grub/custom.cfg . The entries in this file will be automatically added when running
grub-mkconfig.After adding the new lines, run:
# grub-mkconfig -o /boot/grub/grub.cfg
to generate an updated
With GNU/Linux
Assuming that the other distro is on partition
menuentry "Other Linux" { set root=(hd0,2) linux /boot/vmlinuz (add other options here as required) initrd /boot/initrd.img (if the other kernel uses/needs one) }
With FreeBSD
Requires that FreeBSD is installed on a single partition with UFS. Assuming it is installed on
menuentry "FreeBSD" { set root=(hd0,4) chainloader +1 }
With Windows
This assumes that your Windows partition is
sda3. Remember you need to point set root and chainloader to the system reserve partition that windows made when it installed, not the actual partition windows is on. This example works if your system reserve partition is
# (2) Windows XP menuentry "Windows XP" { set root=(hd0,3) chainloader (hd0,3)+1 }
If the Windows bootloader is on an entirely different hard drive than GRUB, it may be necessary to trick Windows into believing that it is the first hard drive. This was possible with
drivemap. Assuming GRUB is on
hd0 and Windows is on
hd2, you need to add the following after
set root:
drivemap -s hd0 hd2
With Windows via EasyBCD and NeoGRUB
Since EasyBCD's NeoGRUB currently does not understand the GRUB2 menu format, chainload to it by replacing the contents of your
C:\NST\menu.lst file with lines similar to the following:
default 0 timeout 1
title Chainload into GRUB v2 root (hd0,7) kernel /boot/grub/i386-pc/core.img
Visual Configuration
In GRUB2 it is possible, by default, to change the look of the menu. Make sure to initialize, if not done already, GRUB2 graphical terminal, gfxterm, with proper video mode, gfxmode, in GRUB2. This can be seen in the section #Correct_GRUB2_No_Suitable_Mode_Found_Error. This video mode is passed by GRUB2 to the linux kernel via 'gfxpayload' so any visual configurations need this mode in order to be in effect.
Setting the framebuffer resolution
GRUB2 can set the framebuffer for both GRUB2 itself and the kernel. The old
vga= way is deprecated. The preferred method is editing
/etc/default/grub as the following sample:
GRUB_GFXMODE=1024x768x32 GRUB_GFXPAYLOAD_LINUX=keep
To generate the changes, run:
# grub-mkconfig -o /boot/grub/grub.cfg
gfxpayload property will make sure the kernel keeps the resolution.
If this method does not work for you, the deprecated
vga= method will still work. Justadd it next to the
"GRUB_CMDLINE_LINUX_DEFAULT=" line in
/etc/default/grubfor eg:
"GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=792" will give you a
1024x768 resolution.
You can choose one of these resolutions:
915resolution hack
Some times for Intel graphic adapters neither
# hwinfo --framebuffer nor
vbeinfo will show you the desired resolution. In this case you can use
915resolution hack. This hack will temporarily modify video BIOS and add needed resolution. See 915resolution's home page
In the following I will proceed with the example for my system. Please adjust the recipe for your needs. First you need to find a video mode which will be modified later. For that, run
915resolution in GRUB2 command shell:
915resolution -l
The output will be something like:
Intel 800/900 Series VBIOS Hack : version 0.5.3 ... Mode 30 : 640x480, 8 bits/pixel ...
Next, our purpose is to overwrite mode 30. (You can choose what ever mode you want.) In the file
/etc/grub.d/00_header just before the
set gfxmode=${GRUB_GFXMODE} line insert:
915resolution 30 1440 900
Here we are overwriting the mode
30 with
1440x900 resolution. Lastly we need to set
GRUB_GFXMODE as described earlier, regenerate GRUB2 configuration file and reboot to test changes:
# grub-mkconfig -o /boot/grub/grub.cfg # reboot
Background image and bitmap fonts
GRUB2 comes with support for background images and bitmap fonts in
pf2 format. The unifont font is included in the grub-common package under the filename
unicode.pf2, or, as only ASCII characters under the name
Image formats supported include tga, png and jpeg, providing the correct modules are loaded. The maximum supported resolution depends on your hardware.
Make sure you have set up the proper framebuffer resolution.
/etc/default/grub like this:
GRUB_BACKGROUND="/boot/grub/myimage" #GRUB_THEME="/path/to/gfxtheme" GRUB_FONT="/path/to/font.pf2"
To generate the changes and add the information into
grub.cfg, run:
grub-mkconfig -o /boot/grub/grub.cfg
If adding the splash image was successful, the user will see
"Found background image..." in the terminal as the command is executed. If this phrase is not seen, the image information was probably not incorporated into the
grub.cfg file.
If the image is not displayed, check:
The path and the filename in
/etc/default/grubare correct.
- The image is of the proper size and format (tga, png, 8-bit jpg).
- The image was saved in the RGB mode, and is not indexed.
The console mode is not enabled in
The command
grub-mkconfigmust be executed to place the background image information into the
Here is an example for configuring Starfield theme which was included in GRUB2 package.
Generate the changes:
grub-mkconfig -o /boot/grub/grub.cfg
If configuring the theme was successful, you'll see
Found theme: /usr/share/grub/themes/starfield/theme.txt in the terminal.Your splash image will usually not be displayed when using a theme.
Menu colors
You can set the menu colors in GRUB2. The available colors for GRUB2 can be found in the GRUB Manual.Here is an example:
GRUB_COLOR_NORMAL="light-blue/black" GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
Generate the changes:
grub-mkconfig -o /boot/grub/grub.cfg
One of the unique features of GRUB2 is hiding/skipping the menu and showing it by holding
Esc when needed. You can also adjust whether you want to see the timeout counter.
/etc/default/grub as you wish. Here is an example where the comments from the beginning of the two lines have been removed to enable the feature, the timeout has been set to five seconds and to be shown to the user:
GRUB_HIDDEN_TIMEOUT=5 GRUB_HIDDEN_TIMEOUT_QUIET=false
and run:
# grub-mkconfig -o /boot/grub/grub.cfg
Disable framebuffer
Users who use NVIDIA proprietary driver might wish to disable GRUB2's framebuffer as it can cause problems with the binary driver.
To disable framebuffer, edit
/etc/default/grub and uncomment the following line:
and run:
grub-mkconfig -o /boot/grub/grub.cfg
Another option if you want to keep the framebuffer in GRUB2 is to revert to text mode just before starting the kernel. To do that modify the variable in
and rebuild the configuration as before.
Other Options
If you use LVM for your
/boot, add the following before menuentry lines:
insmod lvm
and specify your root in the menuentry as:
set root=lvm/lvm_group_name-lvm_logical_boot_partition_name
# (0) Arch Linux menuentry "Arch Linux" { insmod lvm set root=lvm/VolumeGroup-lv_boot # you can only set following two lines linux /vmlinuz-linux root=/dev/mapper/VolumeGroup-root ro initrd /initramfs-linux.img }
GRUB2 provides convenient handling of RAID volumes. You need to add
insmod mdraid which allows you to address the volume natively. For example,
/dev/md0 becomes:
set root=(md0)
whereas a partitioned RAID volume (e.g.
/dev/md0p1) becomes:
set root=(md0,1)
Persistent block device naming
One naming scheme for Persistent block device naming is the use of globally unique UUIDs to detect partitions instead of the "old"
/dev/sd*. Advantages are covered up in the above linked article.
Persistent naming via filesystem UUIDs are used by default in GRUB2.
Whether to use UUIDs is controlled by an option in /etc/default/grub:
# GRUB_DISABLE_LINUX_UUID=true
Either way, do not forget to generate the changes:
# grub-mkconfig -o /boot/grub/grub.cfg
Using Labels
It is possible to use labels, human-readable strings attached to filesystems, by using the
--label option to
search. First of all, label your existing partition:
# tune2fs -L <LABEL> <PARTITION>
Then, add an entry using labels. An example of this:
menuentry "Arch Linux, session texte" { search --label --set=root archroot linux /boot/vmlinuz-linux root=/dev/disk/by-label/archroot ro initrd /boot/initramfs-linux.img }
Recall previous entry
GRUB2 can remember the last entry you booted from and use this as the default entry to boot from next time. This is useful if you have multiple kernels (i.e., the current Arch one and the LTS kernel as a fallback option) or operating systems. To do this, edit
/etc/default/grub and change the setting of
This ensures that GRUB will default to the saved entry. To enable saving the selected entry, add the following line to
If you want to secure GRUB2 so it is not possible for anyone to change boot parameters or use the command line, you can add a user/password combination to GRUB2's configuration files. To do this, run the command
grub-mkpasswd-pbkdf2. Enter a password and confirm it. The output will look like this:
Your PBKDF2 is grub.pbkdf2.sha512.10000.C8ABD3E93C4DFC83138B0C7A3D719BC650E6234310DA069E6FDB0DD4156313DA3D0D9BFFC2846C21D5A2DDA515114CF6378F8A064C94198D0618E70D23717E82.509BFA8A4217EAD0B33C87432524C0B6B64B34FBAD22D3E6E6874D9B101996C5F98AB1746FE7C7199147ECF4ABD8661C222EEEDB7D14A843261FFF2C07B1269A
Then, add the following to
cat << EOF set superusers="username" password_pbkdf2 username <password> EOF
<password> is the string generated by
Regenerate your configuration file. Your GRUB2 command line, boot parameters and all boot entries are now protected.
This can be relaxed and further customized with more users as described in the "Security" part of the GRUB manual.
Root Encryption
To let GRUB2 automatically add the kernel parameters for root encryption,add
cryptdevice=/dev/yourdevice:label to
GRUB_CMDLINE_LINUX in
Example with root mapped to
Also, disable the usage of UUIDs for the rootfs:
Regenerate the configuration.
Boot non-default entry only once
The command
grub-reboot is very helpful to boot another entry than the default only once. GRUB2 loads the entry passed in the first command line argument, when the system is rebooted the next time. Most importantly GRUB2 returns to loading the default entry for all future booting. Changing the configuration file or selecting an entry in the GRUB2 menu is not necessary.
Booting an ISO Directly From GRUB2
/etc/grub.d/40_custom or
/boot/grub/custom.cfg to add an entry for the target ISO. When finished, update the GRUB menu as with the usual
grub-mkconfig -o /boot/grub/grub.cfg (as root).
Arch ISO
Example using x86_64
menuentry "Archlinux-2013.01.04-dual.iso" --class iso { set isofile="/archives/archlinux-2013.01.04-dual.iso" loopback loop (hd0,6)$isofile linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=ARCH_201301 img_dev=/dev/sda6 img_loop=$isofile earlymodules=loop initrd (loop)/arch/boot/x86_64/archiso.img }
Example using i686
menuentry "Archlinux-2013.01.04-dual.iso" --class iso { set isofile="/archives/archlinux-2013.01.04-dual.iso" loopback loop (hd0,6)$isofile linux (loop)/arch/boot/i686/vmlinuz archisolabel=ARCH_201301 img_dev=/dev/sda6 img_loop=$isofile earlymodules=loop initrd (loop)/arch/boot/i686/archiso.img }
Ubuntu ISO
menuentry "ubuntu-12.04-desktop-amd64.iso" { set isofile="/archives/ubuntu-12.04-desktop-amd64.iso" loopback loop (hd0,6)$isofile linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile quiet noeject noprompt splash -- initrd (loop)/casper/initrd.lz }
Other ISOs
Other working configurations from link Source.
Using the command shell
Since the MBR is too small to store all GRUB2 modules, only the menu and a few basic commands reside there. The majority of GRUB2 functionality remains in modules in
/boot/grub, which are inserted as needed. In error conditions (e.g. if the partition layout changes) GRUB2 may fail to boot. When this happens, a command shell may appear.
GRUB2 offers multiple shells/prompts. If there is a problem reading the menu but the bootloader is able to find the disk, you will likely be dropped to the "normal" shell:
If there is a more serious problem (e.g. GRUB cannot find required files), you may instead be dropped to the "rescue" shell:
grub rescue>
The rescue shell is a restricted subset of the normal shell, offering much less functionality. If dumped to the rescue shell, first try inserting the "normal" module, then starting the "normal" shell:
grub rescue> set prefix=(hdX,Y)/boot/grub grub rescue> insmod (hdX,Y)/boot/grub/i386-pc/normal.mod rescue:grub> normal
Pager support
GRUB2 supports pager for reading commands that provide long output (like the help command). This works only in normal shell mode and not in rescue mode. To enable pager, in GRUB2 command shell type:
sh:grub> set pager=1
GUI configuration tools
Following package may be installed from AUR
grub-customizer (requires gettext gksu gtkmm hicolor-icon-theme openssl)
- Customize the bootloader (GRUB2 or BURG)
grub2-editor (requires kdelibs)
- A KDE4 control module for configuring the GRUB2 bootloader
kcm-grub2 (requires kdelibs python2-qt kdebindings-python)
- This Kcm module manages the most common settings of Grub2.
startupmanager (requires gnome-python imagemagick yelp python2 xorg-xrandr)
- GUI app for changing the settings of GRUB, GRUB2, Usplash and Splashy
parttool for hide/unhide
If you have a Windows 9x paradigm with hidden C:\ disks GRUB can hide/unhide it using
parttool. For example, to boot the third C:\ disk of three Windows 9x installations on the CLI enter the CLI and:
parttool hd0,1 hidden+ boot- parttool hd0,2 hidden+ boot- parttool hd0,3 hidden- boot+ set root=hd0,3 chainloader +1 boot
Using the rescue console
See #Using the command shell first. If unable to activate the standard shell, one possible solution is to boot using a live CD or some other rescue disk to correct configuration errors and reinstall GRUB. However, such a boot disk is not always available (nor necessary); the rescue console is surprisingly robust.
The available commands in GRUB rescue include
set, and
unset. This example uses
set modifies variables and
insmod inserts new modules to add functionality.
Before starting, the user must know the location of their
/boot partition (be it a separate partition, or a subdirectory under their root):
grub rescue> set prefix=(hdX,Y)/boot/grub
where X is the physical drive number and Y is the partition number.
To expand console capabilities, insert the
linux module:
grub rescue> insmod (hdX,Y)/boot/grub/linux.mod
This introduces the
linux and
initrd commands, which should be familiar (see #Configuration).
An example, booting Arch Linux:
set root=(hd0,5) linux /boot/vmlinuz-linux root=/dev/sda5 initrd /boot/initramfs-linux.img boot
With a separate boot partition, again change the lines accordingly:
set root=(hd0,5) linux /vmlinuz-linux root=/dev/sda6 initrd /initramfs-linux.img boot
After successfully booting the Arch Linux installation, users can correct
grub.cfg as needed and then reinstall GRUB2.
to reinstall GRUB2 and fix the problem completely, changing
/dev/sda if needed. See #Bootloader installation for details.
Combining the use of UUIDs and basic scripting
If you like the idea of using UUIDs to avoid unreliable BIOS mappings or are struggling with GRUB's syntax, here is an example boot menu item that uses UUIDs and a small script to direct GRUB to the proper disk partitions for your system. All you need to do is replace the UUIDs in the sample with the correct UUIDs for your system. The example applies to a system with a boot and root partition. You will obviously need to modify the GRUB configuration if you have additional partitions:
menuentry "Arch Linux 64" { # Set the UUIDs for your boot and root partition respectively set the_boot_uuid=ece0448f-bb08-486d-9864-ac3271bd8d07 set the_root_uuid=c55da16f-e2af-4603-9e0b-03f5f565ec4a # (Note: This may be the same as your boot partition) # Get the boot/root devices and set them in the root and grub_boot variables search --fs-uuid --set=root $the_root_uuid search --fs-uuid --set=grub_boot $the_boot_uuid # Check to see if boot and root are equal. # If they are, then append /boot to $grub_boot (Since $grub_boot is actually the root partition) if [ $the_boot_uuid == $the_root_uuid] ; then set grub_boot=$grub_boot/boot fi # $grub_boot now points to the correct location, so the following will properly find the kernel and initrd linux ($grub_boot)/vmlinuz-linux root=/dev/disk/by-uuid/$uuid_os_root ro initrd ($grub_boot)/initramfs-linux.img }
Any troubleshooting should be added here.
Intel BIOS not booting GPT
Some Intel BIOS's require at least one bootable MBR partition to be present at boot, causing GPT-partitioned boot setups to be unbootable.
This can be circumvented by using (for instance) fdisk to mark one of the GPT partitions (preferably the 1007KiB partition you've created for GRUB2 already) bootable in the MBR. This can be achieved, using fdisk, by the following commands: Start fdisk against the disk you're installing, for instance "fdisk /dev/sda", then press "a" and select the partition you wish to mark as bootable (probably #1) by pressing the corresponding number, finally press "w" to write the changes to the MBR.
Note that the bootable-marking must be done in fdisk or similar, not in GParted or others, as they will not set the bootable flag in the MBR.
More information is available here
Enable GRUB2 debug messages
set pager=1 set debug=all
Correct GRUB2 No Suitable Mode Found Error
If you get this error when booting any menuentry:
error: no suitable mode found Booting however
Then you need to initialize GRUB2 graphical terminal (
gfxterm) with proper video mode (
gfxmode) in GRUB2. This video mode is passed by GRUB2 to the linux kernel via 'gfxpayload'. In case of UEFI systems, if the GRUB2 video mode is not initialized, no kernel boot messages will be shown in the terminal (atleast until KMS kicks in).
/usr/share/grub/unicode.pf2 to ${GRUB2_PREFIX_DIR} (
/boot/grub/ in case of BIOS and UEFI systems). If GRUB2 UEFI was installed with
--boot-directory=/boot/efi/EFI set, then the directory is
# cp /usr/share/grub/unicode.pf2 ${GRUB2_PREFIX_DIR}
/usr/share/grub/unicode.pf2 does not exist, install bdf-unifont, create the
unifont.pf2 file and then copy it to
# grub-mkfont -o unicode.pf2 /usr/share/fonts/misc/unifont.bdf
Then, in the
grub.cfg file, add the following lines to enable GRUB2 to pass the video mode correctly to the kernel, without of which you will only get a black screen (no output) but booting (actually) proceeds successfully without any system hang.
BIOS systems:
insmod vbe
UEFI systems:
insmod efi_gop insmod efi_uga
After that add the following code (common to both BIOS and UEFI):
insmod font
if loadfont ${prefix}/fonts/unicode.pf2 then insmod gfxterm set gfxmode=auto set gfxpayload=keep terminal_output gfxterm fi
As you can see for gfxterm (graphical terminal) to function properly,
unicode.pf2 font file should exist in
msdos-style error message
grub-setup: warn: This msdos-style partition label has no post-MBR gap; embedding won't be possible! grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged. grub-setup: error: If you really want blocklists, use --force.
This error may occur when you try installing GRUB2 in a VMware container. Read more about it here. It happens when the first partition starts just after the MBR (block 63), without the usual space of 1 MiB (2048 blocks) before the first partition. Read #Master Boot Record (MBR) specific instructions
UEFI GRUB2 drops to shell
If GRUB loads but drops you into the rescue shell with no errors, it may be because of a missing or misplaced
grub.cfg. This will happen if GRUB2 UEFI was installed with
--boot-directory and
grub.cfg is missing OR if the partition number of the boot partition changed (which is hard-coded into the
UEFI GRUB2 not loaded
In some cases the EFI may fail to load GRUB correctly. Provided everything is set up correctly, the output of:
efibootmgr -v
might look something like this:
BootCurrent: 0000 Timeout: 3 seconds BootOrder: 0000,0001,0002 Boot0000* Grub HD(1,800,32000,23532fbb-1bfa-4e46-851a-b494bfe9478c)File(\efi\grub\grub.efi) Boot0001* Shell HD(1,800,32000,23532fbb-1bfa-4e46-851a-b494bfe9478c)File(\EfiShell.efi) Boot0002* Festplatte BIOS(2,0,00)P0: SAMSUNG HD204UI
If everything works correctly, the EFI would now automatically load GRUB.
If the screen only goes black for a second and the next boot option is tried afterwards, according to this post, moving GRUB to the partition root can help. The boot option has to be deleted and recreated afterwards. The entry for GRUB should look like this then:
Boot0000* Grub HD(1,800,32000,23532fbb-1bfa-4e46-851a-b494bfe9478c)File(\grub.efi)
Invalid signature
If trying to boot Windows results in an "invalid signature" error, e.g. after reconfiguring partitions or adding additional hard drives, (re)move GRUB's device configuration and let it reconfigure:
# mv /boot/grub/device.map /boot/grub/device.map-old # grub-mkconfig -o /boot/grub/grub.cfg
grub-mkconfig should now mention all found boot options, including Windows. If it works, remove
Boot freezes
If booting gets stuck without any error message after grub2 loading the kernel and the initial ramdisk, try removing the
add_efi_memmap kernel parameter.
Restore GRUB Legacy
- Move GRUB2 files out of the way:
# mv /boot/grub /boot/grub.nonfunctional
Copy GRUB Legacy back to
# cp -af /boot/grub-legacy /boot/grub
- Replace MBR and next 62 sectors of sda with backed up copy
# dd if=/path/to/backup/first-sectors of=/dev/sdX bs=512 count=1
A safer way is to restore only the MBR boot code use:
# dd if=/path/to/backup/mbr-boot-code of=/dev/sdX bs=446 count=1
- Official GRUB2 Manual - https://www.gnu.org/software/grub/manual/grub.html
- Ubuntu wiki page for GRUB2 - https://help.ubuntu.com/community/Grub2
- GRUB2 wiki page describing steps to compile for UEFI systems -https://help.ubuntu.com/community/UEFIBooting
- Wikipedia's page on BIOS Boot partition


text:
Puppy Linux Discussion Forum
Puppy HOME page :
"THE" alternative forum :
New Forum:
Log in to check your private messages
Log in
The time now is Wed 12 Aug 2020, 15:11
All times are UTC - 4
Forum index
Advanced Topics
Puppy Projects
Karmic Puppy uPup 4.58 w/ GLX/DRI - Latest Woof FEB 16
View previous topic
View next topic
Page 1 of 12
[180 Posts]
Goto page:
Joined: 25 Apr 2008
Posts: 3794
Posted: Thu 03 Dec 2009, 19:15
Post subject:
Karmic Puppy uPup 4.58 w/ GLX/DRI - Latest Woof FEB 16
Subject description: New version on FEB 20 2010 - w/ Cups 1.4.1
New Version 4.58
This is made with the Woof that Barry posted on FEB 16.
Cups is working again--it was at least partially broken in 4.56 and 4.57 but I didn't catch it until testing for 4.58.
The fix for "
Rox Select
" is working. The problem was that a file would stay selected until one clicked in the white space of the Rox window. IMHO that was a serious problem because several times I accidentally deleted the wrong file because the old one stayed selected. There was a fix in /etc/profile but it did not work and it caused a problem with opening Terminal. I used the code instead that aarf posted on page 8 of this thread and it seems to work perfectly.
As per 01micko's discovery,
is present. I know it is doing something because my driver changed from radeonhd to radeon with libdrm-radeon present. I am sure someone understands that.
I am going to write up my
work method and test method
and post it here tonight or tomorrow, just in case it is useful to anyone. I have a test suite now of 4 different video cards, radeon, nvidia, intel and S3 (and all 4 work with glx/dri). Here are the notes ->
The latest
Pwidgets 2.2.4
worked but it caused the problem with the backdrop that was mentioned. I know that is a "good sign" but I prefer to wait to install it by default until it doesn't have that feature.
I will put a link in to Pwidgets in the software links below.
Misson Statement:
To track the Karmic Puppy build in Woof, to find and if possible solve problems, to report back to Barry and maintainers of software, to make a useful Linux desktop with Puppy style and speed and Ubuntu binaries. I hope Karmic Puppy works for you. Thanks for trying it.
Download uPup 4.58
upup458.iso md5sum 3aa69bfae1578b4e42fcec6a8dc876ef
Here is an xdelta update file created and uploaded by pemasu, tested by aarf ->
Download devx
devx_458 md5sum -> f1abc93245792ada6e37eb7c3de33148
Download the upup_devx_458.sfs and place it into /mnt/home. Then check Menu -> System -> System Schedule -> Bootmanager config bootup to make sure the devx will be loaded at startup. I keep devx installed on any semi-permanent installations because there are at least two programs that run better (or at all) when devx is installed (Crossover and xine-ui).
Flashplayer 10.0.45
Flashplayer 10.1pre
Flashplayer 10.1pre Info >
Identifies itself as 10.1 d51 or 10,1,51,45
Seamonkey 2.0.3
(Thanks to 01micko) ->
This was compiled and prepared by 01micko and right away it seemed snappier than the version I got from mozilla.org
01micko's Seamonkey 2.0 page ->
Firefox 3.6
This is not a pet, it is the tar.bz2 file from mozilla. Just download and click to Extract; then open the folder and click firefox. It will update itself daily if you ask it to, Tools -> Check for Updates. It is the latest 1.9.2 gecko, which scores about 25% better on Peacekeeper than the 1.9.1-based versions including 3.5.x in my tests.
Clanbomber 1.05
. Just for fun - full screen game - it has "crocaine" but it overamps you if you do it! ->
Go-OpenOffice 3.1.1 in sfs4 format for Puppy 4.3 and later
md5sum - 63c6a76d95a806c4c8ca9fc802585b35
Info pages on Go-OO ->
Go-Openoffice 3.2
. wolf dog has posted an sfs or Go-OO 3.2 ->
SitHeelSpeak's gcc 4.4.1
devx supplemental ->
Kernel sources
126.96.36.199 ->
SRWare Iron
(Download, Extract, and click Iron to run) ->
ATI Catalyst 9.xx driver
The menu entry is under Utility -> General Utilities.
Menu entry under System -> System status and config.
Foxit PDF Reader for Desktop Linux
This is what I use on Windows for work so I am glad to see it for Linux. To me, it renders significantly better than ePDFView. The menu entry is under Utility -> General Utilities.
CPU Frequency Scaling Tool
(Menu -> Utility - General utilities -> CPU Frequency Scaling Tool) Trio's utility works well from me on my Phenom 9850. Without scaling my cpu idles at 38 and with it at 31.
Pwidgets 2.2.4
. For those who want the widgets it is easy enough to reset the backdrop after starting Pwidgets. There is quite a collection of widgets available now.
Desktop Recorder. Thanks to gposil, Dpup, and aarf. ->
Video cards and drivers
Ideally uPup will
correctly install your video card and also install the glx/dri files.
That can be checked by Menu -> System -> System status and congif -> Hardinfo -> Display and scroll down to see that glx/dri are enabled. One can also check by entering "glxinfo" or "glxgears" at a command prompt. It works that way for me anyway; I am curious to see if it works for anyone else. I personally think that using all of the xorg drivers and installing glx/dri might make things more stable and robust when dealing with newer programs and versions.
If you have an Nvidia video card.
My first test on a different computer failed, but I figured out why. Xorgwizard choose the "nouveau" driver, which I assume is for newer Nvidia cards. So if you have a newer Nvidia card it might work right off. If xorg fails to start it will return you to the prompt (or hit CTRL-C). At the prompt enter
rm /usr/lib/xorg/modules/drivers/nouveau_drv.so
which will erase the nouveau driver, and then enter xorgwizard again and it should choose the "nv" driver that you need. Alternatively, if xorg fails to start, you can enter
and edit your xorg.conf file, replacing driver "nouveau" with driver "nv". Then CTRL-K, X, to quit the e3 editor and "xwin" to restart X. Both of these ways worked for me, and GLX/DRI were started correcly also
If you have an ATI card
that doesn't start correctly, you might try among the "ati," "radeon," and "radeonhd" drivers. It is the "radeonhd" that works for me, which was not in uPup by default.
I have been using
SitHeelSpeak's special devx supplement
, and with that, the regular devx, and the kernel sources, I have been able to
compile and install the latest (9.10) proprietary ATI Catalyst driver,
which works well with my Radeon 3850, and the Catalyst Control Center is working correctly also.
It bugs me to leave out the "nouveau" video driver so the xorgwizard will assign the "nv" driver (which a few people were having to do manually). If this causes you a problem please let me know. I investigated a tiny bit and it seems that "nouveau" is an attempt to get 3D hardware acceleration in an open source driver for nvidia cards. I have had luck in installing/compiling the proprietary 3D hardware acceleration driver Catalyst/fglrx for Ati radeon cards. Perhaps if someone wanted hardware 3D for nvidia they could try to install the Nvidia proprietary driver. For the nouveau driver though ->
Click the file and Extract it, and then place the driver in /usr/lib/xorg/modules/drivers/. After that, Menu -> Shutdown -> Exit to prompt and run xorgwizard at the prompt.
I routinely Save the Network as in the picture below. Your router will have a different name of course.
Last edited by playdayz on Wed 03 Mar 2010, 18:04; edited 138 times in total
Back to top
Joined: 21 Nov 2006
Posts: 11775
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Posted: Thu 03 Dec 2009, 20:00
Post subject:
Altho I am downloading right now and will test later, I have a bit of a problem with the naming.
The latest upup was 476, I use it.
You advertise 432.
There could be a problem when one wants to migrate (if ever possible) to this 432 version.
Any thoughts?
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's
Back to top
Joined: 25 Apr 2008
Posts: 3794
Posted: Thu 03 Dec 2009, 20:27
Post subject:
Hey Beem, My thoughts are that it is confusing. I am not sure the latest uPup is 4.76 though The latest Woof (20091120) generates a uPup numbered 4.32 by default. I just left the number as Barry chose it. 4.76 was one of Barry's wasn't it and then he went back to 4.32? Yes, it could be very confusing, especially as Woof becomes easier and easier to use, more and more people will be making Puplets with it. There might not even be enough numbers between 4 and 5
I am making no claim at all to being in any official sequence. But there might not be an official sequence anymore. I thought that choosing to name the uPup after the edition of Woof might have something to recommend it, but you are right, the number displayed is 4.32. I gather that Barry does not plan to release any more uPups himself but maybe he would have something to say about numbering. ttuuxxx choose 4.50 and 4.60 also. Do you see a way forward?
Back to top
James C
Joined: 26 Mar 2009
Posts: 6735
Location: Kentucky
Posted: Thu 03 Dec 2009, 21:55
Post subject:
Just downloaded and running live at the moment. From a brief test running live this seems much more stable than the other UPup's I tried.No SeaMonkey crashes yet which is a welcome change.
Planning to do a frugal install on my P3 test box tomorrow and I'll give it a good run.Seems pretty solid at first glance though.
Regarding the numbering system, looking back at my old isos Barry K used 4.61, 4.63,4.66,4.71 and 4.76 before reverting to his latest 4.32 with his Upup's. Interesting situation,
Back to top
Joined: 27 Jun 2009
Posts: 238
Posted: Fri 04 Dec 2009, 21:09
Post subject: upup rt73 usb
Subject description: no go
nice color to your pup. and the menus are clean and neat.
when i try to connect wifi using the rt73usb, i get the following
"shared libraries:/ breadline.so.6 cannot open shared object file:
no such file or directory."
i hope you can help, i don't have a glue what this computer stuff
thank you
Back to top
Joined: 05 May 2007
Posts: 11249
Location: Ontario Canada,Sydney Australia
Posted: Sat 05 Dec 2009, 00:14
Post subject:
way to go playdayz
I only made the upup version up just to test it and see if it was stable enough to build a OLPC version on it, I haven't the time since I've been working to devote towards puppy, I'm still doing around 40hrs+ a week for puppy but nothing like 110hrs a week I was doing when I was unemployed
If you want to take over Upup, feel free to. maybe do the next release number 4.51
That way
4 series ends at 4.49 and goes to Ppup
upup 4.51
PPup 4.60 <---Maybe
Pup2.20 <---The one I'm aiming for.
and once one hit's a genuine RC then Series 5 happens.
<-- excellent site
<-- Codec Test Files
<-- excellent HTML5 games
Back to top
Joined: 11 Jul 2008
Posts: 88
Location: Västerås, Sweden
Posted: Sat 05 Dec 2009, 15:42
Post subject:
Hi Playdayz,
I am impressed by your pup.There are some cosmetic problems but for me a major obstacle is that I cannot run it with a wlan connection no other Puppy systems has any problems with. eth0 causes no problems.
Processor AMD Athlon(tm)
Memory 2009MB (67MB used)
Resolution 1280x1024 pixels
X11 Vendor The X.Org Foundation
Wlan0 Wireless zd1211rw usb: Belkin USB2.0 WLAN
Operating System
upup 432plz
# ping yahoo.com
PING yahoo.com (126.96.36.199): 56 data bytes
64 bytes from 18.104.22.168: seq=0 ttl=50 time=169.060 ms
--- yahoo.com ping statistics ---
21 packets transmitted, 5 packets received,
76% packet loss
round-trip min/avg/max = 169.060/187.143/208.729 ms
41 packets transmitted, 3 packets received,
92% packet loss
round-trip min/avg/max = 217.828/223.919/227.953 ms
# ifconfig
wlan0 Link encap:Ethernet HWaddr 00:17:3F:8C:89:DD
inet addr:
Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:768 (768.0 B) TX bytes:2144 (2.0 KiB)
Operating System
Puppy Linux 431
# ping yahoo.com
PING yahoo.com (18.104.22.168): 56 data bytes
64 bytes from 18.104.22.168: seq=0 ttl=43 time=232.794 ms
--- yahoo.com ping statistics ---
16 packets transmitted, 16 packets received,
0% packet loss
round-trip min/avg/max = 230.096/231.548/233.236 ms
# ifconfig
wlan0 Link encap:Ethernet HWaddr 00:17:3F:8C:89:DD
inet addr:
Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2828 (2.7 KiB) TX bytes:7031 (6.8 KiB)
Do you have any clue to why the IP-address is different? Is the adress range limited to 192.168.
.xxx ?
Added comment:
The IP-adress is obtained from a neighbors wlan running unprotected. Using Puppy 431 I can choose between my wlan and the neighbors. But I cannot get upup432 to connect to my wlan. The error output is:
Unable to establish WPA connection
Access point: Not-Associated
Link Quality:0
Output of 'wpa_cli -i wlan status'
wpa_cli: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory
Back to top
Joined: 25 Apr 2008
Posts: 3794
Posted: Sat 05 Dec 2009, 17:25
Post subject:
ecube and timremy, I apologize. I did not say clearly enough that this is a very experimental version. The Puppy is just as it comes from Woof 20091120 with the few changes that I specifically mention.
It should be regarded as alpha software, at the most!
It is definitely not a development of 4.3.1-
-it has very little in common with 4.3.1 under the hood--the numbering is kind of an unfortunate artifact that people are trying to figure out what to do about.
I hope there will eventually be a Puppy based on Ubuntu 9.10 Karmic. The fact that this works at all if due to BarryK's cleverness. If one wants a Puppy that works, one should download the latest official version Puppy 4.3.1.
If one is interested in learning how Puppy works by hacking around on the internals and learning to do it yourself, then this could be a good place to be. It is possible that people reading this thread could solve problems such as the ones you are having and if so then they would post a fix and I will try to implement it in this experimental puppy as it grows up.
Back to top
Joined: 05 May 2007
Posts: 11249
Location: Ontario Canada,Sydney Australia
Posted: Sat 05 Dec 2009, 17:45
Post subject:
ecube wrote:
Hi Playdayz,
Output of 'wpa_cli -i wlan status'
wpa_cli: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory
your missing libreadline.so.6 here's the one from ubuntu Karmic made into a pet, if it works playdayz should included it and also the dev in the compiler.
This is where it comes from and the dev's can be found there also.
I combined both packages and removed the unneeded extras.
1135 Time(s)
<-- excellent site
<-- Codec Test Files
<-- excellent HTML5 games
Back to top
Joined: 25 Apr 2008
Posts: 3794
Posted: Sat 05 Dec 2009, 17:50
Post subject: uPup 20091120 Confguration files
I have posted the changes I made to the default configuration of Karmic Puppy in Woof 20091120 as
This concerns the changes I made to two of the important configuration files as I used Woof 20091120 to build this uPup 20091120 Karmic with extra xservers (video drivers) and GLX/DRI graphics enhancement.
It is just for people who are playing with Woof (I can't imagine anyone else would be interested).
your missing libreadline.so.6 here's the one from ubuntu Karmic made into a pet, if it works playdayz should included it and also the dev in the compiler.
Yes. Thanks ttuuxxx. Ecube, if it works please let us know.
Back to top
Joined: 11 Jul 2008
Posts: 88
Location: Västerås, Sweden
Posted: Sun 06 Dec 2009, 05:35
Post subject:
Thanks Ttuuxxx for your help.
Your pet package silenced the complaint about missing libreadline.so.6. But still no correct internet connection. The error message now reads:
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory.
I have Ubuntu 9.10 (Karmic Koala) installed on the same computer as upup. The wlan connection works flawlessly there.
Playdayz! Are you contemplating building a upup version based on the woof tarball woof-20091202081304REFERENCE.tar.gz?
Regards, Olov
Back to top
Joined: 05 May 2007
Posts: 11249
Location: Ontario Canada,Sydney Australia
Posted: Sun 06 Dec 2009, 06:19
Post subject:
ecube wrote:
Thanks Ttuuxxx for your help.
Your pet package silenced the complaint about missing libreadline.so.6. But still no correct internet connection. The error message now reads:
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory.
I have Ubuntu 9.10 (Karmic Koala) installed on the same computer as upup. The wlan connection works flawlessly there.
Playdayz! Are you contemplating building a upup version based on the woof tarball woof-20091202081304REFERENCE.tar.gz?
Regards, Olov
here install this and see if it works
also open a terminal and type after you installed it
depmod -a
<-- excellent site
<-- Codec Test Files
<-- excellent HTML5 games
Back to top
Joined: 25 May 2005
Posts: 4843
Location: Manila
Posted: Sun 06 Dec 2009, 07:58
Post subject: rt73 (usb)
Actually, this and 4.3.1 have always turned off rt73 (usb), although it works at the start. It's a puzzle, as other 4+ puppies work OK with it.
Puppy user since Oct 2004. Want FreeOffice?
Get the sfs (English only)
Back to top
Joined: 11 Jul 2008
Posts: 88
Location: Västerås, Sweden
Posted: Sun 06 Dec 2009, 11:40
Post subject:
Thanks again for your help Ttuuxxx,
Alas, the error message is the same as before.
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
My interpretation of the error message is that the file
is missing. However, I find no such file in the wpasupplicant pet.
Regards, Olov
Back to top
Joined: 25 Apr 2008
Posts: 3794
Posted: Sun 06 Dec 2009, 15:43
Post subject:
Playdayz! Are you contemplating building a upup version based on the woof tarball woof-20091202081304REFERENCE.tar.gz? http://bkhome.org/blog/?viewDetailed=01232
Yes ecube, I do hope to keep up with the Woof versions and make a uPup for each one, at least for my own usage. I would post it if I saw that some people were interested. Nobody knows what is going to come of woof and how it will all work out. I don't think it will be the same as before, with one official version at a time--well, there may be one official version but it seems like there will be many more unofficial versions. And i still think the true genius of Woof might be in making personal versions, and for that I would see value in exchanging info about Woof and uPup. Giving the new Bones a go should tell me how quickly i could turn around a Woof into a Upup and how transferable the info is from one to the next..
Having Trouble with Wireless???
I I made a build from Bones Woof 2009-1202 Reference. But I am having wireless trouble with it. The Network Wizard, old or new, doesn't find any networks. Fortunately I can configure it manually, which is not much trouble anyway.
Open a terminal (This assumes there is a wireless module running--if not see the Arch page). This is from Archlinux.org
This is easier than it might look. You will only need two or three commands. The three I use are in green. The ESSID is the "name" of your router, which you need to know. And the "key" is the security key, 10 hexadecimal digits, just as usual in the Network Wizard.
1. (Optional, may be required) Some cards require that the kernel interface be activated before you can use the wireless_tools:
# ifconfig wlan0 up
2. (Optional, may be required) See what access points are available:
# iwlist wlan0 scan
3. Depending on the encryption, you need to associate your wireless device with the access point to use and pass the encryption key.
Assuming you want to use the ESSID named MyEssid:
* No encryption
# iwconfig wlan0 essid "MyEssid"
using an hexadecimal key:
# iwconfig wlan0 essid "MyEssid" key 1234567890
using an ascii key:
# iwconfig wlan0 essid "MyEssid" key s:asciikey
You need to edit the /etc/wpa_supplicant.conf file as described in WPA_Supplicant. Then, issue this command:
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
This is assuming your device uses the wext driver. If this does not work, you may need to adjust these options. Check WPA_Supplicant for more information and troubleshooting.
4. Finally, provide an IP address to the network interface. Simple examples are:
# dhcpcd wlan0
for DHCP
Back to top
Display posts from previous:
All Posts
1 Day
7 Days
2 Weeks
1 Month
3 Months
6 Months
1 Year
Sort by:
Post Time
Post Subject
Page 1 of 12
[180 Posts]
Goto page:
View previous topic
View next topic
Forum index
Advanced Topics
Puppy Projects
Jump to:
Select a forum
Forum index
|___ House Training
| |___ Beginners Help ( Start Here)
| |___ Users ( For the regulars )
| | |___ Usuarios de habla Hispana
| | |___ Für deutschsprachige Anhänger
| | |___ Pour les francophones
| |
| |___ HOWTO ( Solutions )
| |___ Bugs ( Submit bugs )
|___ Advanced Topics
| |___ Additional Software (PETs, n' stuff)
| | |___ Package Collections / Repositories
| | |___ Browsers and Internet
| | |___ Business
| | |___ Compiling
| | |___ Desktop
| | |___ Documents
| | |___ Drivers
| | |___ Educational
| | |___ Engineering/Science/Simulation
| | |___ Eye Candy
| | |___ Filesystem
| | |___ Games
| | |___ Graphics
| | |___ Multimedia
| | |___ Network
| | |___ Security/Privacy
| | |___ System
| | |___ Utilities
| | |___ Virtualization
| | |___ Unsorted
| |
| |___ Cutting edge
| | |___ Multi-session live-CD/DVD
| |
| |___ Hardware
| | |___ Audio
| | |___ Networking
| | | |___ Dialup
| | | |___ Ethernet
| | | |___ Wireless
| | |
| | |___ Printers
| | |___ Video
| |
| |___ Puppy Derivatives
| |___ Puppy Projects
| |___ Next Puppy Development
| | |___ 4.x
| | | |___ Bugs (4.x dev)
| | | |___ Usability Issues (4.x dev)
| | |
| | |___ 5.x
| | |___ Bugs (5.x dev)
| | |___ Usability Issues (5.x dev)
| |
| |___ Localization Project
| |___ Documentation Project
|___ Taking the Puppy out for a walk
| |___ Announcements
| |___ Puppy Power
| |___ Suggestions
| |___ Misc
|___ Off-Topic Area
|___ Programming
|___ Security
|___ Truly off-topic conversations
post new topics in this forum
reply to topics in this forum
edit your posts in this forum
delete your posts in this forum
vote in polls in this forum
attach files in this forum
download files in this forum
Powered by
© 2001, 2005 phpBB Group
[ Time: 0.0902s ][ Queries: 13 (0.0180s) ][ GZIP on ]

subset: commoncrawl


text:
Alachua City Hall was constructed in 2007 and is home to the City's administrative offices.
The splashpark at the Hal Brady Recreation Complex is one of the many recreational amenities the City offers.
Alachua is a rural community with strong agrarian roots.
Main Street is at the heart of Alachua's small town charm, inviting residents and visitors to stroll down its historic sidewalks.
Alachua City Hall is illuminated against the evening sky.
Alan Hitchcock Park on Main Street is a common place for local community events and ceremonies.
Main Street is at the heart of Alachua's small town charm, inviting residents and visitors to stroll down its historic sidewalks.
Living in Alachua
Recreation & Culture
Police Department
Public Services
Special Events Calendar
Employment Opportunities
City Guide Book
About Alachua
Civil Rights - Fair Housing - EEO
Business in Alachua
Building Department
Local Business Tax
Planning and Zoning
Vendor Registration
Visiting Alachua
Recreation & Culture
Special Events Calendar
About the City of Alachua
Online Payments
Building Department Payments
Business Licensing Payments
Miscellaneous Receivables Payments
Utility Billing Payments
Stay Connected
Agendas and Minutes
Meet Commissioners
Advisory Boards
Contact Us
Events Calendar
Request City Service
File Complaint
Request Public Records
Rental Opportunities
My Utilities
Pay My Utility Bill
Utility Billing Information
Special Needs Registration
Payment Assistance Programs
Events Calendar
Budget Workshop
August 13, 2018
4:30 p.m.
James A. Lewis Commission Chambers, City Hall
Mailing Address
: P.O. Box 9, Alachua, FL 32616
Physical Address
: 15100 NW 142nd Terrace, Alachua, FL 32615
:(386) 418-6100


text:
Best definition
Mikey D
A young male, orange in skin color, who thinks he is part of a higher homosexual society where he is
king. Lips are always glossed with pink lip gloss and never wears a shirt. Pants are nearly always ripped and his middle finger always makes an appearance in every facebook picture.
Did you see that guy just now? He is totally rockin the Mikey D look.


text:
Check out the list of upcoming OSCON events around the world.
Join today's open source innovators, builders, and pioneers July 25-29 as they gather at the Oregon Convention Center in Portland, Oregon, to share their expertise and experience, explore new ideas, and inspire each other.
Learn first-hand how new developments in open source are shaping the future. Challenge your assumptions, fire up your imagination, and kick your brain into high gear. Rub shoulders with open source rock stars—and have some serious fun with 2000+ people like you.
With over a dozen tracks and hundreds of sessions, you'll find a wealth of leading-edge information on open source languages and platforms, with practical tutorials, inspirational keynote presentations, a jam-packed Expo Hall, fun networking events and activities, and the best "hallway track" around.


text:
- Prams, Buggies, Car seats
- Cots, Cot-beds, Furniture
- Bath Time, Bed Time
- Walkers, Bouncers, Swings, Toys
- Highchairs, Feeding
- Stair gates, Play Pens, Monitors
- Baby Clothing
- Clearance Sale
- Prams, Buggies, Car seats
- Cots, Cot-beds, Furniture
- Bath Time, Bed Time
- Walkers, Bouncers, Swings, Toys
- Highchairs, Feeding
- Stair gates, Play Pens, Monitors
- Baby Clothing
- Clearance Sale
Recent Reviews
Cassey from Sussex
I just want to say a huge thank you Kathy for your help with my order. The service you have provided has been amazing. After months of heart ache finally my 3 month old little boy has a lovely pushchair and I could not be happier.
Thank you again.
Kind regards,
★★★★★ 5/5
Deirdre from Dublin
Hi Kathy ,
Just a quick email to say thanks so much for my order. I will definitely be recommending your store , as the efficiency is second to none.
My carrycot arrived this morning as discussed.
Excellent customer service!
Thanks again.
Kindest regards,
★★★★★ 5/5
Gracie from Sussex
Hi there Kathy and Paul
Just wanted to say a massive thank you to you both for getting the new car seat hood out to me with no issues or fuss I really appreciate it! It's arrived today all in perfect order and shape! Can't thank you guys enough for getting that sorted for us as soon as you did!
Many many thanks
★★★★★ 5/5
Tara from Sussex
Thank you so much for all your help with my order, you went above and beyond to help me get it ASAP and for that I am extremely grateful- looking forward to receiving my order. Will definitely recommend you to my pregnant friends many thanks
★★★★★ 5/5
Judith from Uxbridge
I just wanted to write to you to confirm that the Silver Cross buggy and car seat arrived on Friday.
My step-daughter is absolutely delighted with them.
The parcels arrived safely within the timeframe, it was great that she was able to track them during the delivery process.
Many thanks to you and your team, each person I spoke to on the phone including yourself were very knowledgeable and helpful, the entire customer service experience was excellent.
Thank you to you and please also pass on my gratitude to your colleagues.
I will have no hesitation in recommending you and your company to friends and family in the future.
★★★★★ 5/5
Anna from Lurgan
I've just received my order. The delivery was very quick as I ordered it yesterday. Everything is in good condition so I'm very happy with your service.
Thank you.
★★★★★ 5/5
Example of a customer's payment plan order.
Baby due in 5 months.
Mrs Wright has ordered a Venicci Pram at £700.
Payment plan option was chosen and a 20% (£140) deposit was charged.
We contacted Mrs Wright within 24 hours and agreed a suitable payment structure.
For each of the next 4 months
Mrs Wrights credit card was charged £140.
Total Paid £700
When the Final payment was paid we shipped order out to the customer in time for the baby being born.
Baby Faye.
Mrs Wright was able to view all of her payments made and order details though her online account.
You are in: All categories > Cots, Cot-beds, Furniture > Cot-Beds
Buy your Cot Bed from our extensive range of Cot Beds, Moses Basket, Nursery Furniture, Cots, Beds for your baby, and so much more. Below is our collection of popular brands such as Mj Mark, Baby Elegance, Clair de Lune, Tippitoes, Oslo Sleigh Cot Beds, cots, moses basket and more at the best prices. All of our products are available in our Belfast Kids Store for you to view and try. Online sale & UK/ROI Delivery. We also offer Finance plans.
Products in this category:
Sort by
From £299.99
From £299.99
From £169.99
From £149.99
From £169.99
From £79.99
From £899.99
From £899.99
From £899.99
From £949.99
From £899.99
Back to top


text:
- Prayer and Worship
- Beliefs and Teachings
- Issues and Action
- Media
- Bible
- Catholic Giving
- About USCCB
1For the leader. A psalm of David.
2The heavens declare the glory of God;
the firmament proclaims the works of his hands.a
3Day unto day pours forth speech;
night unto night whispers knowledge.
4*There is no speech, no words;
their voice is not heard;
5A report goes forth through all the earth,
their messages, to the ends of the world.
He has pitched in them a tent for the sun;*
6it comes forth like a bridegroom from his canopy,
and like a hero joyfully runs its course.
7From one end of the heavens it comes forth;
its course runs through to the other;
nothing escapes its heat.
8The law of the LORD is perfect,
refreshing the soul.
The decree of the LORD is trustworthy,
giving wisdom to the simple.b
9The precepts of the LORD are right,
rejoicing the heart.
The command of the LORD is clear,
enlightening the eye.
10The fear of the LORD is pure,
enduring forever.
The statutes of the LORD are true,
all of them just;
11More desirable than gold,
than a hoard of purest gold,
Sweeter also than honey
or drippings from the comb.c
12By them your servant is warned;*
obeying them brings much reward.
13Who can detect trespasses?
Cleanse me from my inadvertent sins.
14Also from arrogant ones restrain your servant;
let them never control me.
Then shall I be blameless,
innocent of grave sin.
15Let the words of my mouth be acceptable,
the thoughts of my heart before you,
LORD, my rock and my redeemer.
* [Psalm 19] The heavenly elements of the world, now beautifully arranged, bespeak the power and wisdom of their creator (Ps 19:2–7). The creator's wisdom is available to human beings in the law (Ps 19:8–11), toward which the psalmist prays to be open (Ps 19:12–14). The themes of light and speech unify the poem.
* [19:4] No speech, no words: the regular functioning of the heavens and the alternation of day and night inform human beings without words of the creator's power and wisdom.
* [19:5] The sun: in other religious literature the sun is a judge and lawgiver since it sees all in its daily course; Ps 19:5b–7 form a transition to the law in Ps 19:8–11. The six synonyms for God's revelation (Ps 19:8–11) are applied to the sun in comparable literature.
* [19:12] Warned: the Hebrew verb means both to shine and to warn, cf. Dn 12:3.
By accepting this message, you will be leaving the website of the
United States Conference of Catholic Bishops. This link is provided
solely for the user's convenience. By providing this link, the United
States Conference of Catholic Bishops assumes no responsibility for,
nor does it necessarily endorse, the website, its content, or
sponsoring organizations.