Burning the Arch Linux ISO to a DVD. NOTE: If you plan on installing Arch Linux on a VM, you may skip this step and boot directly into the ISO image. Now that we have downloaded the Arch Linux ISO, we will burn it to the DVD. There is a variety of software, many free, that allow you to do this, such as Brasero, AnyBurn, or the non-free. Reason: Are any command-line tools to arrange files into volumes to fit on a disk (like GAFFitter or cdrkit's dirsplit) packaged for Arch Linux? (Discuss in Talk:Optical disc drive#) Warning: The quality of optical drives and the discs themselves varies greatly. Generally, using a slow burn speed is. Anarchy Linux, compared to other Linux distributions like Manjaro and Antergos because it is actually NOT a Linux distribution. Anarchy Linux is a free and open source package containing a set of automated scripts designed to facilitate the easier installation and configuration setup of Arch Linux. Arch Linux ISO Once you have downloaded the Arch Linux ISO, it is recommended that you verify it’s SHA1 checksum. If the checksum you get is different from the one on the ISO file you have may have been tampered with, and should not be used.

• Linux Gui Development
• List Of Linux Gui
• Arch Linux Architect

This document is a guide for installing Arch Linux from the live system booted with the official installation image. Before installing, it would be advised to view the FAQ. For conventions used in this document, see Help:Reading. In particular, code examples may contain placeholders (formatted in italics) that must be replaced manually.

For more detailed instructions, see the respective ArchWiki articles or the various programs' man pages, both linked from this guide. For interactive help, the IRC channel and the forums are also available.

Arch Linux should run on any x86_64-compatible machine with a minimum of 512 MiB RAM. A basic installation with all packages from the base group should take less than 800 MiB of disk space. As the installation process needs to retrieve packages from a remote repository, this guide assumes a working internet connection is available.

• 1Pre-installation
  • 1.7Partition the disks
• 2Installation
• 3Configure the system

Pre-installation

The installation media and their GnuPG signatures can be acquired from the Download page.

Verify signature

It is recommended to verify the image signature before use, especially when downloading from an HTTP mirror, where downloads are generally prone to be intercepted to serve malicious images.

On a system with GnuPG installed, do this by downloading the PGP signature (under Checksums) to the ISO directory, and verifying it with:

Alternatively, from an existing Arch Linux installation run:

• The signature itself could be manipulated if it is downloaded from a mirror site, instead of from archlinux.org as above. In this case, ensure that the public key, which is used to decode the signature, is signed by another, trustworthy key. The gpg command will output the fingerprint of the public key.
• Another method to verify the authenticity of the signature is to ensure that the public key's fingerprint is identical to the key fingerprint of the Arch Linux developer who signed the ISO-file. See Wikipedia:Public-key cryptography for more information on the public-key process to authenticate keys.

Boot the live environment

The live environment can be booted from a USB flash drive, an optical disc or a network with PXE. For alternative means of installation, see Category:Installation process.

• Pointing the current boot device to a drive containing the Arch installation media is typically achieved by pressing a key during the POST phase, as indicated on the splash screen. Refer to your motherboard's manual for details.
• When the Arch menu appears, select Boot Arch Linux and press Enter to enter the installation environment.
• See README.bootparams for a list of boot parameters, and packages.x86_64 for a list of included packages.
• You will be logged in on the first virtual console as the root user, and presented with a Zsh shell prompt.

To switch to a different console—for example, to view this guide with ELinks alongside the installation—use the Alt+arrowshortcut. To edit configuration files, nano, vi and vim are available.

Set the keyboard layout

The default console keymap is US. Available layouts can be listed with:

To modify the layout, append a corresponding file name to loadkeys(1), omitting path and file extension. For example, to set a German keyboard layout:

Console fonts are located in /usr/share/kbd/consolefonts/ and can likewise be set with setfont(8).

Verify the boot mode

If UEFI mode is enabled on an UEFI motherboard, Archiso will boot Arch Linux accordingly via systemd-boot. To verify this, list the efivars directory:

If the directory does not exist, the system may be booted in BIOS or CSM mode. Refer to your motherboard's manual for details.

Connect to the internet

To set up a network connection, go through the following steps:

• Ensure your network interface is listed and enabled, for example with ip-link(8):
• Connect to the network. Plug in the Ethernet cable or connect to the wireless LAN.
• Configure your network connection:
  • Dynamic IP address: use DHCP.

  Note: The installation image enables dhcpcd (dhcpcd@interface.service) for wired network devices on boot.

• The connection may be verified with ping:

Update the system clock

Use timedatectl(1) to ensure the system clock is accurate:

To check the service status, use timedatectl status.

Partition the disks

When recognized by the live system, disks are assigned to a block device such as /dev/sda or /dev/nvme0n1. To identify these devices, use lsblk or fdisk.

Results ending in rom, loop or airoot may be ignored.

The following partitions are required for a chosen device:

• One partition for the root directory /.
• If UEFI is enabled, an EFI system partition.

If you want to create any stacked block devices for LVM, system encryption or RAID, do it now.

Example layouts

See also Partitioning#Example layouts.

• Use fdisk or parted to modify partition tables, for example fdisk /dev/sdX.
• Swap space can be set on a swap file for file systems supporting it.

Format the partitions

Once the partitions have been created, each must be formatted with an appropriate file system. For example, if the root partition is on /dev/sdX1 and will contain the ext4 file system, run:

If you created a partition for swap, initialize it with mkswap:

See File systems#Create a file system for details.

Mount the file systems

Mount the file system on the root partition to /mnt, for example:

Create any remaining mount points (such as /mnt/efi) and mount their corresponding partitions.

genfstab will later detect mounted file systems and swap space.

Installation

Select the mirrors

Packages to be installed must be downloaded from mirror servers, which are defined in /etc/pacman.d/mirrorlist. On the live system, all mirrors are enabled, and sorted by their synchronization status and speed at the time the installation image was created.

The higher a mirror is placed in the list, the more priority it is given when downloading a package. You may want to edit the file accordingly, and move the geographically closest mirrors to the top of the list, although other criteria should be taken into account.

This file will later be copied to the new system by pacstrap, so it is worth getting right.

Install the base packages

Use the pacstrap script to install the base package group:

This group does not include all tools from the live installation, such as btrfs-progs or specific wireless firmware; see packages.x86_64 for comparison.

To install packages and other groups such as base-devel, append the names to pacstrap (space separated) or to individual pacman commands after the #Chroot step.

Configure the system

Fstab

Generate an fstab file (use -U or -L to define by UUID or labels, respectively):

Check the resulting file in /mnt/etc/fstab afterwards, and edit it in case of errors.

Chroot

Change root into the new system:

Time zone

Set the time zone:

Run hwclock(8) to generate /etc/adjtime:

This command assumes the hardware clock is set to UTC. See System time#Time standard for details.

Localization

Uncomment en_US.UTF-8 UTF-8 and other needed locales in /etc/locale.gen, and generate them with:

Create the locale.conf(5) file, and set the LANGvariable accordingly:

If you set the keyboard layout, make the changes persistent in vconsole.conf(5):

Network configuration

Create the hostname file:

Add matching entries to hosts(5):

If the system has a permanent IP address, it should be used instead of 127.0.1.1.

Complete the network configuration for the newly installed environment.

Initramfs

Creating a new initramfs is usually not required, because mkinitcpio was run on installation of the linux package with pacstrap.

For LVM, system encryption or RAID, modify mkinitcpio.conf(5) and recreate the initramfs image:

Root password

Set the root password:

Boot loader

Choose and install a Linux-capable boot loader. If you have an Intel or AMD CPU, enable microcode updates in addition.

Reboot

Exit the chroot environment by typing exit or pressing Ctrl+d.

Optionally manually unmount all the partitions with umount -R /mnt: this allows noticing any 'busy' partitions, and finding the cause with fuser(1).

Finally, restart the machine by typing reboot: any partitions still mounted will be automatically unmounted by systemd. Remember to remove the installation media and then login into the new system with the root account.

Post-installation

See General recommendations for system management directions and post-installation tutorials (like setting up a graphical user interface, sound or a touchpad).

For a list of applications that may be of interest, see List of applications.

From Wikipedia:

In computing, an optical disc drive (ODD) is a disk drive that uses laser light or electromagnetic waves within or near the visible light spectrum as part of the process of reading or writing data to or from optical discs. Some drives can only read from discs, but recent drives are commonly both readers and recorders, also called burners or writers. Compact discs, DVDs, and Blu-ray discs are common types of optical media which can be read and recorded by such drives. Optical drive is the generic name; drives are usually described as 'CD' 'DVD', or 'Blu-ray', followed by 'drive', 'writer', etc.

• 1Burning
  • 1.2Making an ISO image from existing files on hard disk
  • 1.14Multi-session
  • 1.17Burning a BIN/CUE
• 2Playback
• 3Ripping
  • 3.1Audio CD
  • 3.2DVD-Video
• 4Troubleshooting
  • 4.6GUI program log indicates problems with backend program

Burning

This article or section needs expansion.

The burning process of optical disc drives consists of creating or obtaining an image and writing it to an optical medium. The image may in principle be any data file. If you want to mount the resulting medium, then it is usually an ISO 9660 file system image file. Audio and multi-media CDs are often burned from a .bin file, under control of a .toc file or a .cue file which tell the desired track layout.

Install burning utilities

This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.

If you want to use programs with graphical user interface, then follow #Burning CD/DVD/BD with a GUI.

The programs listed here are command line oriented. They are the back ends which are used by most free GUI programs for CD, DVD, and BD. GUI users might get to them when it comes to troubleshooting or to scripting of burn activities.

You need at least one program for creation of file system images and one program that is able to burn data onto your desired media type.

Available programs for ISO 9660 image creation are:

• mkisofs(8) from cdrtools
• xorriso(1) and xorrisofs(1) from libisoburn

The traditional choice is mkisofs.

Available programs for burning to media are:

• cdrdao(1) from cdrdao (CD only, TOC/CUE/BIN only)
• cdrecord(1) from cdrtools
• cdrskin(1) from libburn
• growisofs(1) from dvd+rw-tools (DVD and BD only)
• xorriso(1) and xorrecord(1) from libisoburn

The traditional choices are cdrecord for CD and growisofs for DVD and Blu-ray Disk. For writing TOC/CUE/BIN files to CD, install cdrdao.

The free GUI programs for CD, DVD, and BD burning depend on at least one of the above packages.

xorrisofs supports the mkisofs options which are shown in this document.

cdrskin supports the shown cdrecord options; xorrecord also supports those which do not deal with audio CD.

Making an ISO image from existing files on hard disk

The simplest way to create an ISO image is to first copy the needed files to one directory, for example: ./for_iso.

Then generate the image file with mkisofs:

Each of those options are explained in the following sections.

Basic options

-V

Specifies the name (that is assigned to) of the file system. The ISO 9660 standard specs impose the limitations of 32-character string length, as well as limiting the characters allowed to sets of: 'A' to 'Z', '0' to '9', and '_'. This volume label will probably show up as mount point if the medium is mounted automatically.

-J

Enables Joliet extension, which allocates special space to store file names in Unicode (up to 64 UTF-16 characters for each file).

-joliet-long

Increases maximum length of file names from 64 to 103 UTF-16 characters in Joliet table. Non-compliant to Joliet specs and not commonly supported.

-r

Enables Rock Ridge extension, which adds POSIX file system semantics to an image, including support of long 255-character filenames and Unix-style file permissions.

-o

Sets the file path for the resulting ISO image.

graft-points

It is also possible to let mkisofs to collect files and directories from various paths

-graft-points

Enables the recognition of pathspecs which consist of a target address in the ISO file system (e.g. /photos) and a source address on hard disk (e.g. /home/user/photos). Both are separated by a '=' character.

So this example puts the disk directory /home/user/photos, /home/user/mail and /home/user/holidays/photos, respectively in the ISO image as /photos, /mail and /photos/holidays.

Programs mkisofs and xorrisofs accept the same options. For secure backups, consider using xorrisofs with option --for_backup, which records eventual ACLs and stores an MD5 checksum for each data file.

See the mkisofs(8) and xorrisofs(1) man pages for more info about their options.

Mounting an ISO image

You can mount an ISO image if you want to browse its files.To mount the ISO image, we can use:

Do not forget to unmount the image when your inspection of the image is done:

See also Mounting images as user for mounting without root privileges.

Converting img/ccd to an ISO image

To convert an img/ccd image, you can use ccd2iso:

Learning the name of your optical drive

For the remainder of this section the name of your recording device is assumed to be /dev/sr0.

Check this by

which should report Vendor_info and Identification fields of the drive.

If no drive is found, check whether any /dev/sr* exist and whether they offer read/write permission (wr-) to you or your group.If no /dev/sr* exists then try loading module sr_mod manually.

Reading the volume label of a CD or DVD

If you want to get the name/label of the media, use dd:

Creating an ISO image from a CD, DVD, or BD

In order to only copy actual data from the disc and not the empty blocks filling it up, first retrieve its block/sector count and size (2048 most of the time):

Windows 7 repair usb bootable. or alternatively:

Then use dd to copy the data using the obtained values:

If the original medium was bootable, then the copy will be a bootable image. You may use it as a pseudo CD for a virtual machine or burn it onto an optical media which should then become bootable. [1]

Erasing CD-RW and DVD-RW

Used CD-RW media need to be erased before you can write over the previously recorded data. This is done by

There are two options for blanking: blank=fast and blank=all. Full blanking lasts as long as a full write run. It overwrites the payload data on the CD. Nevertheless this should not be considered as securely making those data unreadable. For that purpose, several full write runs with random data are advised.

Alternative commands are:

To erase the DVD-RW use the dvd+rw-format utility from dvd+rw-tools:

Alternative commands are:

Such fastly blanked DVD-RW are not suitable for multi-session and cannot take input streams of unpredicted length. For that purpose one has to use one of:

The other media types are either write-once (CD-R, DVD-R, DVD+R, BD-R) or are overwritable without the need for erasing (DVD-RAM, DVD+RW, BD-RE).

Formatting DVD-RW

Formatted DVD-RW media can be overwritten without previous erasure. So consider to apply once in their life time

Unlike DVD-RAM, DVD+RW, and BD-RE, formatted DVD-RW cannot be used as (slow) hard disk directly, but rather need the mediation of driver pktcdvd. See man pktsetup.

Formatting BD-RE and BD-R

BD-RE need formatting before first use. This is done automatically by the burn programs when they detect the unformatted state. Nevertheless the size of the payload area can be influenced by expert versions of the format commands shown above for DVD-RW.

BD-R can be used unformatted or formatted. Unformatted they are written with full nominal speed and offer maximum storage capacity. Formatted they get checkread during write operations and bad blocks get replaced by blocks from the Spare Area. This reduces write speed to a half or less of nominal speed. The default sized Spare Area reduces the storage capacity by 768 MiB.

growisofs formats BD-R by default. The others do not. growisofs can be kept from formatting. cdrskin and xorriso can write with full nominal speed on formatted BD-RE or BD-R:

Burning an ISO image to CD, DVD, or BD

To burn a readily prepared ISO image file isoimage.iso onto an optical medium, run for CD:

and for DVD or BD:

• Make sure that the medium is not mounted when you begin to write to it. Mounting may happen automatically if the medium contains a readable file system. In the best case, it will prevent the burn programs from using the burner device. In the worst case, there will be misburns because read operations disturbed the drive. So if in doubt, do:
• growisofs has a small bug with blank BD-R media. It issues an error message after the burning is complete. Programs like k3b then believe the whole burn run failed. To prevent this, either
  • format the blank BD-R by dvd+rw-format /dev/sr0 before submitting it to growisofs
  • or use growisofs option -use-the-force-luke=spare:none

Verifying the burnt ISO image

You can verify the integrity of the burnt medium to make sure it contains no errors. Always eject the medium and reinsert it before verifying. It will guarantee that not any kernel cache will be used to read the data.

First calculate the MD5 checksum of the original ISO image:

Next calculate the MD5 checksum of the ISO file system on the medium.Although some media types deliver exactly the same amount of data as have been submitted to the burn program, many others append trailing garbage when being read. So you should restrict reading to the size of the ISO image file.

Both runs should yield the same MD5 checksum (here: e5643e18e05f5646046bb2e4236986d8). If they do not, you will probably also get an I/O error message from the dd run. dmesg might then tell about SCSI errors and block numbers, if you are interested.

ISO 9660 and burning on-the-fly

It is not necessary to store an emerging ISO file system on hard disk before writing it to optical media. Only very old CD drives at very old computers could suffer failed burns due to empty drive buffer.

If you omit option -o from mkisofs then it writes the ISO image to standard output. This can be piped into the standard input of burn programs.

Option -waiti is not really needed here. It prevents cdrecord from writing to the medium before mkisofs starts its output. This would allow mkisofs to read the medium without disturbing an already started burn run. See next section about multi-session.

On DVD and BD, you may let growisofs operate mkisofs for you and burn its output on-the-fly:

Multi-session

ISO 9660 multi-session means that a medium with readable file system is still writable at its first unused block address, and that a new ISO directory tree gets written to this unused part. The new tree is accompanied by the content blocks of newly added or overwritten data files. The blocks of data files, which shall stay as in the old ISO tree, will not be written again.

Linux and many other operating systems will mount the directory tree in the last session on the medium. This youngest tree will normally show the files of the older sessions, too.

Multi-session by cdrecord

CD-R and CD-RW stay writable (aka 'appendable') if cdrecord option -multi was used

Then the medium can be inquired for the parameters of the next session

By help of these parameters and of the readable medium in the drive you can produce the add-on ISO session

Finally append the session to the medium and keep it appendable again

Programs cdrskin and xorrecord do this too with DVD-R, DVD+R, BD-R and unformatted DVD-RW. Program cdrecord does multi-session with at least DVD-R and DVD-RW. They all do with CD-R and CD-RW, of course.

Most re-usable media types do not record a session history that would be recognizable for a mounting kernel. But with ISO 9660 it is possible to achieve the multi-session effect even on those media. Free download for printing pictures.

growisofs and xorriso can do this and hide most of the complexity.

Multi-session by growisofs

By default, growisofs uses mkisofs as a backend for creating ISO images forwards most of its program arguments to . See above examples of mkisofs. It bans option -o and deprecates option -C. By default it uses the mkisofs. You may specify to use one of the others compatible backend program by setting environment variable MKISOFS:

The wish to begin with a new ISO file system on the optical medium is expressed by option -Z

The wish to append more files as new session to an existing ISO file system is expressed by option -M

For details see the growisofs(1) manual and the manuals of mkisofs and xorrisofs.

Multi-session by xorriso

xorriso learns the wish to begin with a new ISO file system from the blank state of the medium. So it is appropriate to blank it if it contains data. The command -blank as_needed applies to all kinds of re-usable media and even to ISO images in data files on hard disk. It does not cause error if applied to a blank write-once medium.

On non-blank writable media xorriso appends the newly given disk files if command -dev is used rather than -outdev. Of course, no command -blank should be given here

For details see the xorriso(1) man page and especially its examples.

BD Defect Management

BD-RE and formatted BD-R media are normally written with enabled Defect Management. This feature reads the written blocks while they are still stored in the drive buffer. In case of poor read quality the blocks get written again or redirected to the Spare Area where the data get stored in replacement blocks.

This checkreading reduces write speed to at most half of the nominal speed of drive and BD medium. Sometimes it is even worse. Heavy use of the Spare Area causes long delays during read operations. So Defect Management is not always desirable.

cdrecord does not format BD-R. It has no means to prevent Defect Management on BD-RE media, though.

growisofs formats BD-R by default. The Defect Management can be prevented by option -use-the-force-luke=spare:none. It has no means to prevent Defect Management on BD-RE media, though.

cdrskin, xorriso and xorrecord do not format BD-R by default. They do with cdrskin blank=format_if_needed, resp. xorriso -format as_needed, resp. xorrecord blank=format_overwrite. These three programs can disable Defect Management with BD-RE and already formatted BD-R by cdrskin stream_recording=on, resp. xorriso -stream_recording on, resp. xorrecord stream_recording=on.

Burning an audio CD

Create your audio tracks and store them as uncompressed, 16-bit, stereo WAV files. To convert MP3 to WAV, ensure lame is installed, cd to the directory with your MP3 files, and run:

Linux Gui Development

In case you get an error when trying to burn WAV files converted with LAME, try decoding with mpg123:

To convert AAC to WAV ensure faad2 is installed and run:

Name the audio files in a manner that will cause them to be listed in the desired track order when listed alphabetically, such as 01.wav, 02.wav, 03.wav, etc. Use the following command to simulate burning the WAV files as an audio CD:

If everything worked, you can remove the dummy flag to actually burn the CD.

To test the new audio CD, use MPlayer:

Burning a BIN/CUE

To burn a BIN/CUE image run:

TOC/CUE/BIN for mixed-mode disks

ISO images only store a single data track. If you want to create an image of a mixed-mode disk (data track with multiple audio tracks) then you need to make a TOC/BIN pair:

Some software only likes CUE/BIN pair, you can make a CUE sheet with toc2cue (part of cdrdao):

Burn backend problems

If you are experiencing problems, you may ask for advise at mailing list cdwrite@other.debian.org, or try to write to the one of support mail addresses if some are listed near the end of the program's man page.

Tell the command lines you tried, the medium type (e.g. CD-R, DVD+RW, ..), and the symptoms of failure (program messages, disappointed user expectation, ..). You will possibly get asked to obtain the newest release or development version of the affected program and to make test runs. But the answer might as well be, that your drive dislikes the particular medium.

Burning CD/DVD/BD with a GUI

There are several applications available to burn CDs in a graphical environment.

See also Wikipedia:Comparison of disc authoring software.

• AcetoneISO — All-in-one ISO tool (supports BIN, MDF, NRG, IMG, DAA, DMG, CDI, B5I, BWI, PDI and ISO).

http://sourceforge.net/projects/acetoneiso acetoneiso2

• BashBurn — Lightweight terminal based menu frontend for CD/DVD burning tools.

http://bashburn.dose.se/ bashburn

• Brasero — Disc burning application for the GNOME desktop that is designed to be as simple as possible.

https://wiki.gnome.org/Apps/Brasero brasero

• cdw — Ncurses frontend to cdrecord, mkisofs, growisofs, dvd+rw-mediainfo, dvd+rw-format and xorriso.

http://cdw.sourceforge.net/ cdw^AUR

• Graveman — GTK-based CD/DVD burning application. It requires configuration to point to correct devices.

http://graveman.tuxfamily.org/ graveman^AUR

• isomaster — ISO image editor.

http://littlesvr.ca/isomaster isomaster^AUR

• K3b — Feature-rich and easy to handle CD burning and ripping application based on KDElibs.

http://www.k3b.org/ k3b

• SimpleBurn — Minimalistic GTK application for burning and extracting CDs and DVDs.

https://simpleburn.tuxfamily.org/ simpleburn^AUR

• X-CD-Roast — Lightweight cdrtools front-end for CD and DVD writing.

http://www.xcdroast.org/ xcdroast^AUR

• Xfburn — Simple front-end to the libburnia libraries with support for CD/DVD(-RW), ISO images, and BurnFree.

http://goodies.xfce.org/projects/applications/xfburn xfburn

• xorriso-tcltk — Graphical front-end to ISO and CD/DVD/BD burn tool xorriso

https://www.gnu.org/software/xorriso/ libisoburn

Playback

CD

Playback of audio CDs requires the libcdio package. To enable KDE Applications like Dolphin to read audio CDs install audiocd-kio.

DVD

If you wish to play encrypted DVDs, you must install the libdvd* packages:

Additionally, you must install player software. Popular DVD players are MPlayer, xine and VLC. See the video players list and the specific instructions for MPlayer.

Ripping

Ripping is the process of copying audio or video content to a hard disk, typically from removable media or media streams.

Audio CD

Console

• abcde — Comprehensive command-line tool for ripping audio CDs.

https://abcde.einval.com/ abcde

• cdda2wav — CD-audio extraction program with paranoia support.

http://www.cdda2wav.de/ cdrtools

• cdparanoia — Compact Disc Digital Audio (CDDA) Digital Audio Extraction (DAE) tool.

https://xiph.org/paranoia/index.html cdparanoia

• ripright — Minimal CD ripper modeled on autorip.

http://www.mcternan.me.uk/ripright/ ripright^AUR

• ripit — Command-line ripper that supports MusicBrainz, freeddb and various codecs.

http://www.ripit.pl/ ripit^AUR

• shnsplit — Splits .wav and .flac files according to a CUE sheet and encodes the resulting pieces. A useful companion to ABCDE.

http://www.etree.org/shnutils/shntool/ shntool

• whipper — CD ripper aiming for accuracy over speed. Uses cdparanoia, MusicBrainz, AccurateRip.

https://github.com/JoeLametta/whipper whipper

Graphical

• Asunder — GTK-based CD ripping program.

http://littlesvr.ca/asunder/ asunder

• Audex — Audio grabber tool for CD-ROM drives based on KDE.

https://www.linux-apps.com/content/show.php?content=77125 audex

• fre:ac — Audio converter and CD ripper with support for various popular formats and encoders.

List Of Linux Gui

https://freac.org/ freac^AUR

• Goobox — CD player and ripper for GNOME.

https://people.gnome.org/~paobac/goobox/ goobox

• Grip — Fast and light CD ripper within the GNOME project that resembles Audiograbber.

https://sourceforge.net/projects/grip/ grip^AUR.

• K3b — Feature-rich and easy to handle CD/DVD burning and ripping application based on KDElibs.

http://www.k3b.org/ k3b

• KAudioCreator — KDE program for ripping and encoding Audio-CDs.

https://www.kde.org/applications/multimedia/kaudiocreator/ kaudiocreator

• ripperX — GTK program to rip CD audio tracks and encode them to the Ogg, MP3, or FLAC formats.

https://sourceforge.net/projects/ripperx/ ripperx^AUR

• rubyripper — Audiodisk ripper that tries to deliver a secure rip through multiple rippings of the same track and corrections of any differences.

https://code.google.com/archive/p/rubyripper/ rubyripper^AUR

• Sound Juicer — CD ripper for GNOME.

https://wiki.gnome.org/Apps/SoundJuicer sound-juicer

• soundKonverter — Front-end to various audio converters.

https://www.linux-apps.com/content/show.php?content=29024 soundkonverter

• XCFA — Tool to extract the content of audio CDs and convert files to various formats.

http://www.xcfa.tuxfamily.org/ xcfa^AUR

DVD-Video

See also Wikipedia:Comparison of DVD ripper software.

Often, the process of ripping a DVD can be broken down into two subtasks:

1. Data extraction — Copying the audio and/or video data to a hard disk,
2. Transcoding — Converting the extracted data into a suitable format.

Some utilities perform both tasks, whilst others focus on one aspect or the other.

Console

• dvdbackup — Tool for pure data extraction which does not transcode. It is useful for creating exact copies of encrypted DVDs in conjunction with libdvdcss or for decrypting video for other utilities unable to read encrypted DVDs.

http://dvdbackup.sourceforge.net/ dvdbackup

• FFmpeg — Complete and free Internet live audio and video broadcasting solution for Linux/Unix, capable to do a direct rip in any format (audio/video) from a DVD-Video ISO image, just select the input as the ISO image and proceed with the desired options. It also allows to downmixing, shrinking, spliting, selecting streams among other features.

http://ffmpeg.org/ ffmpeg

• HandBrake CLI — Simple yet powerful video transcoder ideal for batch mkv/x264 ripping.

http://handbrake.fr/ handbrake-cli

• MEncoder — Free command line video decoding, encoding and filtering tool. It supports ripping and transcoding DVD-Video.

http://www.mplayerhq.hu/ mencoder

• subtitleripper — Convert DVD subtitles into text format.

http://joonet.de/subtitleripper/ subtitleripper^AUR

• Transcode — Video/DVD ripper and encoder with the CLI.

https://bitbucket.org/france/transcode-tcforge transcode

Graphical

• dvd::rip — Front-end to transcode, used to extract DVD's to the hard disk and transcode or extract and transcode on-the-fly.

https://www.exit1.org/dvdrip/ dvdrip^AUR

• HandBrake — Simple yet powerful video transcoder ideal for batch mkv/x264 ripping. GTK version.

http://handbrake.fr/ handbrake

• K3b — Feature-rich and easy to handle CD/DVD burning and ripping application based on KDElibs.

http://www.k3b.org/ k3b

• OGMRip — An application and a set of libraries for ripping and encoding DVD into AVI, OGM, MP4, or Matroska files using a wide variety of codecs. It relies on mplayer, mencoder, ogmtools, mkvtoolnix, mp4box, oggenc, lame, and faac to perform its tasks.

http://ogmrip.sourceforge.net/ ogmrip^AUR

DVD-Audio

• Python Audio Tools — Includes dvda2track, which is easy to use command line tool to extract DVD-Audio tracks to uncompressed wav files.

http://audiotools.sourceforge.net/ audiotools^AUR

Troubleshooting

Brasero fails to normalize audio CD

If you try to burn it may stop at the first step called Normalization.

As a workaround you can disable the normalization plugin using the Edit > Plugins menu

VLC: Error '.. could not open the disc /dev/dvd'

If you get an error like

it may be because there is no device node /dev/dvd on your system. Udev no longer creates /dev/dvd and instead uses /dev/sr0. To fix this, edit the VLC configuration file (~/.config/vlc/vlcrc):

DVD drive is noisy

If playing DVD videos causes the system to be very loud, it may be because the disk is spinning faster than it needs to. To temporarily change the speed of the drive, run:

Sometimes:

Arch Linux Architect

Any speed that is supported by the drive can be used, or 0 for the maximum speed.

Playback does not work with new computer (new DVD-Drive)

If playback does not work and you have a new computer (new DVD-Drive) the reason might be that the region code is not set. You can read and set the region code with the regionset^AUR package.

None of the above programs are able to rip/encode a DVD to my hard disk!

Make sure the region of your DVD reader is set correctly; otherwise, you will get loads of inexplicable CSS-related errors. Use the regionset^AUR package to do so.

GUI program log indicates problems with backend program

If you use a GUI program and experience problems which the program's log blames on some backend program, then try to reproduce the problem by the logged backend program arguments.Whether you succeed with reproducing or not, you may report the logged lines and your own findings to the places mentioned in #Burn backend problems section.

Special case: medium error / write error

Here are some typical messages about the drive disliking the medium. This can only be solved by using a different drive or a different medium. A different program will hardly help.

Brasero with backend growisofs:

Brasero with backend libburn:

AHCI

If your new DVD drive is detected but you cannot mount disks, check wether your BIOS uses AHCI and add the module to the kernel image.

Edit /etc/mkinitcpio.conf and add ahci to the MODULES array (see mkinitcpio for details):

Regenerate the initramfs so that it includes the newly added module.

BD-R DL 50GB errors on trying to burn second layer

Using growisofs from dvd+rw-tools for burning 50GB BD-R DL discs might result in a fatal error and damaged media, such as:

This happened at the 25GB boundary when starting to write the second layer. Using cdrecord from cdrtools works with no problems. Tested with a 'HL-DT-ST BD-RE WH16NS40' LG burner, and Verbatim BD-R DL 6x discs (#96911). FS#47797

Disc tray autocloses

If after ejecting a cd, either by using the eject command, or pushing the drive button, the drive disc tray autocloses before being able to remove the disc, try the following command:

If that solves the problem, make the change permanent:

See also

• In the United States, backup of physically obtained media is allowed under these conditions: About Piracy - RIAA.