~mwhudson/help.ubuntu.com/no-install-20.04-i386

directory (at the location mentioned in <a class="xref" href="ch04s02.html#where-files" title="4.2.1. Where to Find Installation Images">Section 4.2.1, “Where to Find Installation Images”</a>).

</p>

<p>

The CD or DVD image you choose should be written directly to the USB stick,

overwriting its current contents. For example, when using an existing

GNU/Linux system, the CD or DVD image file can be written to a USB stick

as follows, after having made sure that the stick is unmounted:

</p>

<code class="prompt">#</code> <strong class="userinput"><code>cp <em class="replaceable"><code>debian.iso</code></em> /dev/<em class="replaceable"><code>sdX</code></em></code></strong>

</pre></div>

<p>

The

win32diskimager</a>

utility can be used under other operating systems to copy the image.

</p>

<tr>

100

<th align="left">Important</th>

101

</tr>

102

103

104

The image must be written to the whole-disk device and not a

105

partition, e.g. /dev/sdb and not /dev/sdb1.

106

Do not use tools like <span class="command"><strong>unetbootin</strong></span> which alter the image.

107

108

</p></td></tr>

109

</table></div>

110

111

<tr>

112

113

<th align="left">Important</th>

114

</tr>

115

116

117

Simply writing the CD or DVD image to USB like this should work fine

118

for most users. The other options below are more complex, mainly for

119

people with specialised needs.

120

121

</p></td></tr>

122

</table></div>

123

<p>

124

125

The hybrid image on the stick does not occupy all the storage space, so

126

it may be worth considering using the free space to hold firmware files

127

or packages or any other files of your choice. This could be useful if

128

you have only one stick or just want to keep everything you need on one

129

device.

130

131

</p>

132

<p>

133

134

Create a second, FAT partition on the stick, mount the partition

135

and copy or unpack the firmware onto it. For example:

136

137

</p>

138

139

# mount /dev/<em class="replaceable"><code>sdX2</code></em> /mnt

140

# cd /mnt

141

# tar zxvf <em class="replaceable"><code>/path/to/</code></em>firmware.tar.gz

142

# cd /

143

# umount /mnt

144

</pre></div>

145

<p>

146

147

</p>

148

<p>

149

150

You might have written the <code class="filename">mini.iso</code> to the USB

151

stick. In this case the second partition doesn't have to be created as,

152

very nicely, it will already be present. Unplugging and replugging the

153

USB stick should make the two partitions visible.

154

155

</p>

156

</div>

157

158

159

<a name="usb-copy-easy"></a>4.3.2. Manually copying files to the USB stick</h3></div></div></div>

160

<p>

161

162

An alternative way to set up your USB stick is to manually copy

163

the installer files, and also a CD image to it.

164

Note that the USB stick should be at least 1 GB in size (smaller

165

setups are possible if you follow <a class="xref" href="ch04s03.html#usb-copy-flexible" title="4.3.3. Manually copying files to the USB stick — the flexible way">Section 4.3.3, “Manually copying files to the USB stick — the flexible way”</a>).

166

167

</p>

168

<p>

169

170

There is an all-in-one file

171

<span class="phrase"><a class="ulink" href="http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-i386/current//images/netboot/boot.img.gz" target="_top">netboot/boot.img.gz</a></span>

172

173

which contains all the installer files (including the kernel)

174

<span class="phrase">as well as <code class="classname">syslinux</code> and its

175

configuration file</span>

176

177

178

</p>

179

<p>

180

181

To use this image simply extract it directly to a partition on your USB

182

stick:

183

184

</p>

185

186

# zcat boot.img.gz > /dev/<em class="replaceable"><code>sdX1</code></em>

187

</pre></div>

188

<p>

189

190

</p>

191

</div>

192

193

194

<a name="usb-copy-flexible"></a>4.3.3. Manually copying files to the USB stick — the flexible way</h3></div></div></div>

195

<p>

196

197

If you like more flexibility or just want to know what's going on, you

198

should use the following method to put the files on your stick. One

199

advantage of using this method is that — if the capacity of your

200

USB stick is large enough — you have the option of copying any

201

ISO image, even a DVD image, to it.

202

203

</p>

204

205

206

<a name="idm846"></a>4.3.3.1. Partitioning the USB stick</h4></div></div></div>

207

<p>

208

209

We will show how to set up the memory stick to use the first partition,

210

instead of the entire device.

211

212

</p>

213

214

<tr>

215

216

217

</tr>

218

219

<p>

220

221

Since most USB sticks come pre-configured with a single FAT16

222

partition, you probably won't have to repartition or reformat the

223

stick. If you have to do that anyway, use <span class="command"><strong>cfdisk</strong></span>

224

or any other partitioning tool to create a FAT16 partition<a href="#ftn.idm852" class="footnote" name="idm852"><sup class="footnote">[2]</sup></a>, install an MBR using:

225

226

</p>

227

228

# install-mbr /dev/<em class="replaceable"><code>sdX</code></em>

229

</pre></div>

230

<p>

231

232

The <span class="command"><strong>install-mbr</strong></span> command is contained in the

233

<code class="classname">mbr</code> Ubuntu package. Then create the filesystem using:

234

235

</p>

236

237

# mkdosfs /dev/<em class="replaceable"><code>sdX1</code></em>

238

</pre></div>

239

<p>

240

241

Take care that you use the correct device name for your USB stick. The

242

<span class="command"><strong>mkdosfs</strong></span> command is contained in the

243

<code class="classname">dosfstools</code> Ubuntu package.

244

245

</p>

246

</td></tr>

247

</table></div>

248

<p>

249

250

In order to start the kernel after booting from the USB stick, we will

251

put a boot loader on the stick. Although any boot loader

252

(e.g. <code class="classname">lilo</code>) should work, it's convenient to use

253

<code class="classname">syslinux</code>, since it uses a FAT16 partition and can

254

be reconfigured by just editing a text file. Any operating system

255

which supports the FAT file system can be used to make changes to the

256

configuration of the boot loader.

257

258

</p>

259

<p>

260

261

To put <code class="classname">syslinux</code> on the FAT16 partition on your USB

262

stick, install the <code class="classname">syslinux</code> and

263

<code class="classname">mtools</code> packages on your system, and do:

264

265

</p>

266

267

# syslinux /dev/<em class="replaceable"><code>sdX1</code></em>

268

</pre></div>

269

<p>

270

271

Again, take care that you use the correct device name. The partition

272

must not be mounted when starting <span class="command"><strong>syslinux</strong></span>. This

273

procedure writes a boot sector to the partition and creates the file

274

<code class="filename">ldlinux.sys</code> which contains the boot loader code.

275

276

</p>

277

</div>

278

279

280

<a name="idm877"></a>4.3.3.2. Adding the installer image</h4></div></div></div>

281

<p>

282

283

Mount the partition

284

(<strong class="userinput"><code>mount /dev/<em class="replaceable"><code>sdX1</code></em> /mnt</code></strong>)

285

and copy the following installer image files to the stick:

286

287

</p>

288

289

290

291

<code class="filename">vmlinuz</code> or <code class="filename">linux</code> (kernel binary)

292

293

</p></li>

294

295

296

<code class="filename">initrd.gz</code> (initial ramdisk image)

297

298

</p></li>

299

</ul></div>

300

<p>

301

302

You can choose between either the text-based or the graphical version

303

of the installer. The latter can be found in the <code class="filename">gtk</code>

304

subdirectory. If you want to rename the files, please note that

305

<code class="classname">syslinux</code> can only process DOS (8.3) file names.

306

307

</p>

308

<p>

309

310

Next you should create a <code class="filename">syslinux.cfg</code> configuration

311

file, which at a bare minimum should contain the following line (change

312

the name of the kernel binary to <span class="quote">“<span class="quote"><code class="filename">linux</code></span>”</span>

313

if you used a <code class="filename">netboot</code> image):

314

315

</p>

316

317

default vmlinuz initrd=initrd.gz

318

</pre></div>

319

<p>

320

321

For the graphical installer you should add <strong class="userinput"><code>vga=788</code></strong> to the

322

line. Other parameters can be appended as desired.

323

324

</p>

325

<p>

326

327

To enable the boot prompt to permit further parameter appending, add a

328

<strong class="userinput"><code>prompt 1</code></strong> line.

329

330

</p>

331

<p>

332

333

If you used an <code class="filename">hd-media</code> image, you should now copy the ISO file of

334

an Ubuntu ISO image<a href="#ftn.idm904" class="footnote" name="idm904"><sup class="footnote">[3]</sup></a> onto the stick. When you are done, unmount the USB memory stick

335

(<strong class="userinput"><code>umount /mnt</code></strong>).

336

337

</p>

338

</div>

339

</div>

340

341

342

343

Don't forget to set the <span class="quote">“<span class="quote">bootable</span>”</span> bootable flag.

344

</p></div>

345

346

You can use either a netinst or a full CD image (see

347

<a class="xref" href="ch04s01.html" title="4.1. Official Ubuntu CD-ROMs">Section 4.1, “Official Ubuntu CD-ROMs”</a>). Be sure to select one that fits.

348

Note that the <span class="quote">“<span class="quote">netboot <code class="filename">mini.iso</code></span>”</span> image is

349

not usable for this purpose.

350

</p></div>

351

</div>

352

</div>

353

354

<hr>

355

356

<tr>

357

358

359

360

361

</td>

362

</tr>

363

<tr>

364

<td width="40%" align="left" valign="top">4.2. Downloading Files from Ubuntu Mirrors </td>

365

366

<td width="40%" align="right" valign="top"> 4.4. Preparing Files for Hard Disk Booting</td>

367

</tr>

368

</table>

369

</div>

370

</body>

371

</html>

Older »