Installing additional firmware

33 views
Skip to first unread message

Achim Patzner

unread,
May 28, 2016, 2:38:15 PM5/28/16
to qubes-users
Hi!

Is it only me or are there some more people who seriously hate having to add firmware for virtual machines? Is there a better way than moving the image into some trustworthy machine, extending it and moving it back to dom0? I’ve been doing this for the sixth time now and I’m getting a bit tired by it. I guess we should petition for adding at least firmware for everything Realtek with USB (and maybe Ralink and Intel) to the standard Qubes installation.


Achim

Andrew David Wong

unread,
May 28, 2016, 9:31:12 PM5/28/16
to Achim Patzner, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I'm not sure I understand. Is this some kind of special procedure
required by your particular needs? I don't think I've ever had a need
to install firmware in VMs in that sense. Or, if I did, I was able to
do so via a package manager like yum or dnf.

It's possible that I'm simply ignorant about this topic. (But if
that's true, it's also possible that I'm representative of the
majority of Qubes users, in which case there may not be a pressing
need to accommodate this.)

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXSkZVAAoJENtN07w5UDAwBdYP/3IYzMwMYEDFVCw0faQB89T2
QbzJIU19/Hg8RuaITSLdF4bONkJUkyEm2qIGpcmcyDd1G0DoIY0na1aCGqLUJyv2
RATvnPEB75PCXmbPMgIydN6jHy0zzNJ9p9mpxe3XbnS0vjaLWdjxHBPo6udBIgAq
9uXaAiKfZGAHeB9dbaWHWftvkq4/+DW8NZ1pfCqc7zYGxRVvjp+0njYzYHPuU9SF
hTMHCHbZA3nxjcCW3WnkIZ0e4pWb5SLYdvFeQ6gSu6ZAPOyxNeqoj6maprJrn0i/
yUMk5U4ygBUZJVfUVi0Bng29oZbcAnyuEOrZC0VV5a39cgSPIpuH0NipXTOWzy6p
1nzLNQJfNw1aXCT23JnmOHfEjEm8+winkfvbs4NjjGv4H/OpFrOjGCRGU1L5usfS
v3AiyjyzWEm3iSBAT9FgEre6uK8i3OP9FIIPRhzBZChgWjoKpc7ouijcHfUYptx7
uqtYF7TgzptZ3rjQWnERJJO/a6UCib7ZVCoYfxkR7xtQwzMkSYHftYXz683KNZa/
h2TUjICfgm8HYtUJ1jDj6R5lfB7oFW50m0pH070moNxafY+eA5vvP0OhUlclmGRH
nPw8QMmtYZzoknUplhykkB6HIobrCGc6UV+HmyJe5TqD/tMgoLOw2nzm9qit7oMF
qNRfkN8qpC751n/slFtT
=0LIU
-----END PGP SIGNATURE-----

Achim Patzner

unread,
May 29, 2016, 9:14:28 AM5/29/16
to qubes...@googlegroups.com
Am 29.05.2016 um 03:31 schrieb Andrew David Wong:
> On 2016-05-28 11:38, Achim Patzner wrote:
> > Hi!
>
> > Is it only me or are there some more people who seriously hate
> > having to add firmware for virtual machines?
>
> I'm not sure I understand.

My mistake. I wanted to write _modules_ and constantly wrote "firmware".
"You should not post at 3 in the morning after 27 hours of work", I guess.

> Is this some kind of special procedure required by your particular needs?

Yes. For some reasons I'm running around with a collection of USB WLAN
devices and I have to install the appropriate drivers (and firmware) for
them whenever I update the kernel. I wouldn't really mind it so much if
they were really exotic hardware but most of them are Ralink and Realtek
based "IT-groceries" found at every corner. This is annoying me quite a bit.


Achim

Andrew David Wong

unread,
May 29, 2016, 5:11:18 PM5/29/16
to Achim Patzner, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ah, I see. Is the Fedora template upgrade procedure applicable? Maybe
it would be easier to make room by bind mounting a temp directory over
/usr/lib/modules as described here:

https://www.qubes-os.org/doc/fedora-template-upgrade-21/

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXS1rxAAoJENtN07w5UDAwNVQQAJ1gp//jJ2HH6QGb7t91aRX3
MfCAP+S3tZ4vTWkCgxr/iQlxEgGrQ689XJwZk3jZFoZq8ofmqEAX3SNsoxEMCL3M
YiFvRBip57EdMqW84r9V4hdqBmAEBjQcYsg78QNQXYbB2nP8q8fV6665CEJZPoJy
NcDIbv3dnVFKVcADtXqtR0ssvQbQzoNkGqvkgQQK1NduyZl4AI/PTbhAF/qSa5//
ocm0k/rdyBxda/9ZuVg5M2MdFJMyVq7h8v0ApAXV4cIudu3ki9n/9A+ZrlRImQdM
ksfQW3i91BOMQ4dvo8KyF9u7/evR01y0/eHeg9d/DLdFafVfa4EeQM3n8cH5Ehqz
tZdhY48WTYDSx1aze6gnQcBAHqCUmNMM8L34j+5gyGVr77eeSdkKR9e4WK+ktXTI
rFrOWYC+RsJRpWTy5Na8Y0RWNOmYYE+FoCZUfKgUFV75UwvW8I4/gU+SVvOwZkHm
27d+vzND/ysrm2m/xsGPru3JWtj4Y2EyD6goRGsbEe8VPDQhcohQz9Kb7AZExAHg
BjGGHSDxJYi49hfVcg7zQWo4sC8kazssHYf4sNMy0pefuYd9ruUbHSF1VsUvZUvC
bVUQw20TRiqyYxREzHofCLMXlUEUP1Vp3EsTZuWCiwlmMWvhI9Ep9yN3bZtwaBOa
Geuvsx1H2c4BtMHRNpMw
=NwnS
-----END PGP SIGNATURE-----

Achim Patzner

unread,
May 30, 2016, 4:26:20 PM5/30/16
to qubes...@googlegroups.com
Am 29.05.2016 um 23:11 schrieb Andrew David Wong:
> > I'm running around with a collection of USB
> > WLAN devices and I have to install the appropriate drivers (and
> > firmware) for them whenever I update the kernel. I wouldn't really
> > mind it so much if they were really exotic hardware but most of
> > them are Ralink and Realtek based "IT-groceries" found at every
> > corner. This is annoying me quite a bit.
>
> Ah, I see. Is the Fedora template upgrade procedure applicable? Maybe
> it would be easier to make room by bind mounting a temp directory over
> /usr/lib/modules

Which would be a local patch again. I'd like to fix the pain for many
users (who enjoy buying cheap hardware for some unknown reason) ending
up with one of the common off-the-shelf-at-the-grocery-shop devices. "I
wanted to buy some condoms but grabbed a WLAN adapter instead". For some
unknown reason Realtek has released dozens of nearly the same devices
with completely different drivers and nobody consolidated all the
RTL8192[ABCDE][C|U|E] drivers into one. I don't think adding a handfull
of additional drivers would hurt that much and installing the
proprietary firmware (if necessary) isn't that much of a PITA if the
driver module has been included.


Achim
Reply all
Reply to author
Forward
0 new messages