Page MenuHomeFreeBSD

Amazon EC2: Disable floppy devices (fdc0, fd0,) and parallel port device (pp0)
AcceptedPublic

Authored by james.wright_digital-chaos.com on Dec 8 2018, 5:00 AM.
Referenced Files
Unknown Object (File)
Sat, Apr 20, 1:56 PM
Unknown Object (File)
Fri, Apr 19, 9:30 AM
Unknown Object (File)
Fri, Apr 12, 9:01 AM
Unknown Object (File)
Wed, Apr 10, 10:10 AM
Unknown Object (File)
Mar 2 2024, 12:30 PM
Unknown Object (File)
Feb 2 2024, 11:25 PM
Unknown Object (File)
Jan 25 2024, 7:58 AM
Unknown Object (File)
Dec 27 2023, 10:39 AM
Subscribers

Details

Reviewers
cperciva
lwhsu
imp
Group Reviewers
Contributor Reviews (src)
Summary

Disable the floppy devices (fdc0, fd0) and parallel port device (ppc0) on Amazon EC2 instances. They are not present on these machines and output an error on boot (see below);

# dmesg | grep fdc
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: does not respond
device_attach: fdc0 attach returned 6
fdc0: No FDOUT register!
# dmesg | grep ppc
ppc0: cannot reserve I/O port range

Bugzilla PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233861

Test Plan

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Updated file path in diff for Phabricator Diffusion browsing

lwhsu added a subscriber: lwhsu.

@cperciva I think this patch is good, can you check it? Thanks!

This revision is now accepted and ready to land.Jun 25 2020, 1:28 PM

Which instance type are you seeing this on? I haven't been able to reproduce it.

Which instance type are you seeing this on? I haven't been able to reproduce it.

I think it may have been a t2.micro at the time but not 100% sure now. Everything I have is running on t3a instances now and I can't reproduce it on these types either, so I think it may have just been an issue on the older generations.

Ah, on t2.micro I see warnings about fdc (but not about ppc). Normally I aim to minimize the difference between EC2 and "stock" FreeBSD, but I guess there's no harm in making this change even if it only affects older instance types.