1 [[!meta title="Known issues"]]
5 Problems starting Tails
6 =======================
8 This section lists known problems with specific hardware. To report a problem
9 with different hardware see our [[report guidelines when Tails does not
10 start|doc/first_steps/bug_reporting/tails_does_not_start]].
12 <a id="problematic-usb-sticks"></a>
14 Problematic USB sticks
15 ----------------------
17 The following USB sticks have issues starting Tails. They are configured by the
18 manufacturer as a fixed disk, and not as a removable disk. As a consequence,
19 they require removing the `live-media=removable` boot parameter, which [[is
20 dangerous|doc/first_steps/bug_reporting/tails_does_not_start#entirely]].
22 * SanDisk Cruzer Edge 8GB
23 * SanDisk Cruzer Extreme USB 3.0 16GB and 32GB
24 * SanDisk Cruzer Fit USB 2.0 8GB, 16GB, and 32G
25 * SanDisk Cruzer Force 8GB
26 * SanDisk Cruzer Glide 4GB, 8GB and 16GB
27 * SanDisk Cruzer Switch USB 2.0 8GB and 32GB
28 * SanDisk Cruzer USB 3.0 64GB
29 * SanDisk Cruzer Blade 4GB, 8GB, and 32GB
30 * SanDisk Cruzer Facet
31 * Staples Relay USB 2.0 16GB
33 SanDisk had begun the production of flash drives configured as fixed disk in
34 2012 to meet new requirements for Windows 8 Certification. The flash drives that
35 comply with this certification will have the Windows 8 logo on their packaging.
36 If a flash drive does not have the Windows 8 logo on its packaging, then that
37 drive will function as a removable disk about should work with Tails.
39 See also [[!tails_ticket 6397]].
44 Booting fails with `Not enough memory to load specified image`. Work around by
45 adding the `mem=1500m` [[boot
46 option|/doc/first_steps/startup_options/#boot_menu]].
48 Acer Travelmate 8573T-254G50M
49 -----------------------------
51 Booting from DVD works fine, but does not start on USB sticks created
52 using Tails Installer.
54 This problem might be corrected in Tails 1.1 and newer: please report
55 your test results back to us.
60 Legacy support needs to be enabled in order to start Tails. To enable
61 legacy boot support, enable 'Launch CSM' under boot (menu).
63 This problem might be corrected in Tails 1.1 and newer: please report
64 your test results back to us.
69 You need to update the firmware to its latest version in order to start from a
70 device installed using Tails Installer.
72 Dell Inc. Latitude E6430/0CPWYR
73 -------------------------------
75 Does not start on USB sticks created using Tails Installer.
77 With BIOS versions A03 06/03/2012 (and A09 and A11)
79 Error message: `Invalid partition table!`
81 Workaround (at least with BIOS versions A09 and A11): just hit enter
82 and it will continue with the boot.
84 This problem might be corrected in Tails 1.1 and newer: please report
85 your test results back to us.
87 Dell XPS L702X/03RG89, Samsung RV520, Samsung Series 7 Chronos
88 --------------------------------------------------------------
90 Does not start on USB sticks created using Tails Installer.
92 We were reported that the legacy BIOS shipped on these systems doesn't
93 know how to deal with the GPT partition scheme installed by Tails
96 This problem might be corrected in Tails 1.1 and newer: please report
97 your test results back to us.
99 <http://en.community.dell.com/support-forums/laptop/f/3518/p/19392884/20010995.aspx>
104 The display panel will have the wrong resolution unless `video=LVDS-1:1600x1200
105 nouveau.noaccel=1` is added to the boot command line. This problem might be
106 corrected in Tails 1.1 and newer: please report your test results back
112 Cannot start neither from USB nor from DVD. System crashes with a blank
113 screen and locked up keyboard. This problem might be corrected in
114 Tails 1.1 and newer: please report your test results back to us.
119 With UEFI enabled, when chosing a boot device, select `Boot From EFI File` and
120 then `Filesystem Tails` and `EFI/BOOT/bootx64.efi`.
122 Clevo W258CU, ThinkPad X121e, T420i, T430, T410, T520, W520, T530, E325 and E530
123 --------------------------------------------------------------------------------
125 These machines do not start on USB sticks created using Tails USB
126 Installer, due to a firmware limitation.
128 A workaround for some of these machines is to use the [[manual
129 installation process|doc/first_steps/installation/manual/linux]].
130 Note, however, that this technique does not allow you to set up
133 This problem might be corrected in Tails 1.1 and newer: please report
134 your test results back to us.
141 * Some Mac need [rEFInd](http://sourceforge.net/projects/refind/)
142 installed to boot Tails from a USB stick.
143 * MacBookPro5,5 does not boot with Tails in UEFI mode.
144 * MacBook Air 3,2 (A1369 EMC 2392) freezes when booting Tails in
146 * MacBookPro (early 2011) fails to boot from DVD since Tails 1.1.
147 * Mac Pro Tower (early 2008) fails to boot from a USB stick created by
150 <a id="problematic-virtual-machines"></a>
152 Problematic virtual machines
153 ----------------------------
155 Does not start in some virtualization environments, such as
156 QEMU 0.11.1 and VirtualBox 4.2. This can be corrected by upgrading to
157 QEMU 1.0 or VirtualBox 4.3, or newer.
159 See also [[!tails_ticket 7232]] and [[!tails_ticket 7173]].
161 <a id="chainloading"></a>
163 Chainloading Tails from GRUB
164 ----------------------------
166 To workaround problems in booting Tails on laptops with UEFI support, it is
167 possible to chainload the syslinux on the ISO image from another boot loader
168 that is already working on the laptop, like GRUB. Be careful not to modify at
169 all the options of syslinux in the process.
171 The following commands, run from the GRUB shell, might be helpful:
180 Tails might not erase all the system memory on shutdown
181 -------------------------------------------------------
183 On rare systems (non-PAE with big amounts of memory),
184 Tails does not consistently [[!tails_todo
185 more_efficient_memory_wipe desc="erase all system memory as it
188 After using Tails Installer, the "emergency shutdown" doesn't work
189 ------------------------------------------------------------------
191 Tails Installer messes a bit too much with the USB devices for the
192 "emergency shutdown on media removal" feature to continue working after using
193 it. If you believe this feature is critical for the session you're running, we
194 advice you to reboot Tails.
196 Tails DVD eject failure
197 -----------------------
199 Pressing the DVD eject button does not trigger emergency shutdown.
200 Also, the "normal" (non-emergency) shutdown procedure does not eject
203 (Ticket: [[!tails_todo fix_DVD_eject_at_shutdown]])
205 Stream isolation inconsistency in Claws Mail
206 --------------------------------------------
208 Claws Mail isn't using its dedicated Tor SocksPort for Tor hidden
209 service IMAP/POP/SMTP servers (instead Tor's TransPort is used). This
210 is just a deviation from Tails' design and should have no adverse real
213 Tails fails to completely shutdown or restart
214 ---------------------------------------------
216 When stopping Tails on some hardware, the memory wipe procedure fails to
217 complete: the display gets scrambled, but the computer doesn't
218 completely shutdown or restart. Sometimes the caps-lock button light of
219 the keyboard flashes.
221 <div class="caution">
223 When this happens, there is no guarantee that the memory is wiped entirely.
227 This issue has been reported on the following hardware:
229 - Apple MacBookAir5,1, MacBook Pro 13-inch Mid 2012 9,2, MacBook Pro
230 13-inch Late 2011 8,1, MacBook Pro Retina 13-inch, and
231 MacBookPro10,2, when booting from a USB stick
232 - Hewlett-Packard HP Pavilion dv6 Notebook PC
233 - Lenovo ThinkPad X61, only on emergency shutdown when pulling out the
235 - Toshiba Satellite C855D
236 - Dell Inc. Studio 1458
237 - Fujitsu Lifebook AH531/GFO, only on regular shutdown, emergency
239 - Apple MacBookPro 10,2
241 <a id="fingerprint"></a>
246 <!-- If this section is empty adjust the [[fingerprint documentation|doc/about/fingerprint]]. -->
248 <!-- The fingerprints of the Tor browser and the TBB are different: -->
250 * Browser window resizing is in not reliable: [[!tails_ticket 6377]]
251 and [[!tor_bug 10095]].
256 Boot menu has display issues
257 ----------------------------
259 Since Tails 1.1, one some hardware (ThinkPad X230, MacBookPro8,1),
260 the boot menu is not displayed properly. Tails starts fine, though.
262 Connecting to FTP servers is not possible
263 -----------------------------------------
265 Public FTP servers on the Internet are not reachable using Tails.
266 See [[!tails_todo fix_Internet_FTP_support desc="the corresponding
267 task"]] for more details.
269 YouTube videos are hard to get
270 ------------------------------
272 [[!tails_todo easier_YouTube desc="HTML5 video are not easily seen on YouTube"]]. When the
273 message *This video is currently unavailable* appears, the video can actually be viewed.
274 Right-click on the page, select **NoScript** → **Blocked objects** and
275 **Temporarily allow…** the video.
277 Tails will never support videos which require Flash (those with ads).
279 Tails fails to connect to certain Wi-Fi networks
280 ------------------------------------------------
282 This might be related to the introduction of wireless regulation support
285 VirtualBox guest modules are broken for 64-bit guests
286 -----------------------------------------------------
288 VirtualBox guest modules allow for additional features when using Tails as a
289 VirtualBox guest: shared folders, resizable display, shared clipboard, etc.
291 But due to [a bug in VirtualBox](https://www.virtualbox.org/ticket/11037), the
292 resizable display and shared clipboard
293 only work in Tails if the VirtualBox guest is configured to have a 32-bit
294 processor. The shared folders work both on 32-bit and 64-bit guests.
296 Touchpad configurations
297 -----------------------
299 ### Acer TravelMate B113 - ETPS/2 Elantech Touchpad
301 synclient FingerPress=256;
302 synclient TapButton3=0;
303 synclient Clickpad=1;
304 synclient VertTwoFingerScroll=1;
305 synclient FingerLow=1;
306 synclient FingerHigh=1;
308 TorBrowser takes too long to shutdown
309 -------------------------------------
311 Since Tails 0.22, the browser sometimes takes too long to shutdown
312 ([[!tails_ticket 6480]]). Waiting a few more seconds is usually enough
313 to let it close itself correctly.