To post a comment
login or create an account
Users of Ubuntu are generally told not to use root prompts, but instead to use sudo to gain necessary authorisation to accomplish adminstrative tasks.
Your steps pass a web-downloaded script directly to a root bash shell. Not something I'd recommend a user do under any circumstances, especially your target audience of home users.
Please could you modify/update your steps to use a more sane set of tasks as non-root.
Alan, I agree, running most things as root is a very poor idea. However, with the exception of the actual download of the bootstrap script, each of the things done in the bootstrap script (adding GPG keys to the apt keyring, adding apt sources.list lines) and each of the things that happen thereafter (installing packages, getting system hardware inventory, running update_firmware) _do_ require root privileges. So yes, it could be re-written:
$ wget -q -O - http://linux.dell.com/repo/firmware/bootstrap.cgi > bootstrap.sh(very carefully read bootstrap.sh)
$ sudo bash bootstrap.sh$ sudo aptitude install firmware-addon-dell$ sudo aptitude install $(sudo bootstrap_firmware -a)$ sudo update_firmware
but I'm not sure that's any prettier.
Good to have these tools in Ubuntu!
However the packages are not perfectly tailored for a deb based system:
With a little polishing though inclusion in hardy should not be a problem and Dell will be even more appreciated from Ubuntu users.
The yum / rpm related files, which look for rpmrc, implement a handy version comparison function that works for BIOS versions as well as RPM versions. It can probably be replaced, which would eliminate those dependencies and messages. Patches welcome. GIT repository at http://linux.dell.com/git/firmware-tools.git/
Good point about the GUI. It's a new feature, so we need to add a .desktop file for it. Thanks for the reminder.
@pabs: thanks for owning a Dell laptop. The BIOS images posted for Dell systems are not open source, though it's been requested many times. Do you not trust the system you have now (for whichever definitions of trust you wish to use)? If so, how would these updates be any different?
It's taken a while to get all the packages building for the Ubuntu versions we do support. I suspect I'll get even more feedback on the packaging now that they're available, and I simply haven't taken the time to build the packages for Debian. I have every reason to believe they will build there. And yes, I would love to see these included in Debian and Ubuntu both, just as they are included in Fedora.
As for duplicating apt/dpkg and yum/rpm, no, in fact we don't do that at all. We use dpkg/rpm packaging to provide the tools and payload files in an easily-consumable format, and apt/yum for package management. The goal is to fit cleanly into these existing tools, absolutely not duplicate them.
Good to see you have Debian packages too, even though you didn't mention it. Will you be including firmware-tools and firmware-addon-dell in Debian?
I'd like to be able to trust Dell's firmware, since I have a Dell Laptop, but I cannot do that unless you provide source code for verification.
It's not perfect, since users may not know your key in the first place, but it's better than piping from wget to bash!
Error here when running the first command:
~$ sudo wget -q -O - http://linux.dell.com/repo/firmware/bootstrap.cgi | bashbash: line 221: /etc/apt/sources.list.d/dell-software-temp-bootstrap.list: Permission deniedDownloading GPG key: http://linux.dell.com/repo/GPG-KEY-libsmbios Importing key.gpg: no writable keyring found: eofgpg: error reading `GPG-KEY': general errorgpg: import from `GPG-KEY' failed: general errorGPG-KEY import failed. Either there was a problem downloading the key, or you do not have sufficient permissions to import the key.
@Tom - no, I hadn't heard of that, I'll have a look. imbrandon showed me how the Adobe flashplayer-plugin is being handled, which might be useful, we're still discussing.
@holotone: the bash script must be run with sudo privilages too, which in your command line it isn't. It's easiest if you just:
$ sudo bash
and then run all the commands, or if you like, you can do the wget, write it to a file, and then start a 'sudo bash' in which you execute the other steps. See above in the comments here for why you need everything from the bash step onward to be run as the root user.
Kevin, it's supposed to update daily, but that cronjob isn't quite working smoothly. I'll investigate further.
imneat: yours is the second report of this, I haven't seen it myself yet. Perhaps others have ideas?
Victor: that's one of the nice things about firmware-tools: it uses the exact same BIOS flashing mechanism as all other Dell systems use. firmware-tools merely puts the BIOS image in memory, and sets an NVRAM flag - nothing more. When you reboot the system, BIOS, during POST, sees the NVRAM flag, re-assembles and checksums the image, then performs the actual flash. This assures that no other OS functions can interfere, because there is no OS running at the time.
We did have some very early systems with a broken (advertised, but non-functional) flash implementation, but we know which those are, and the tool specifically excludes posting BIOS images for them.
There are a few exceptions. Some of the newest systems, in particular some Vostro and Inspiron systems, don't have this capability. We're investigating ways to provide the same functionality.
Many thanks for doing this! I'm trying this out with my M1210 now :-).
error: Unable to open /usr/lib/rpm/rpmrc for reading: No such file or directory.
I get that error using Kubuntu Feisty
Matt, I applied the update yesterday per the instructions, and for me the Synaptic update notification still appears, even after running the update several times. I see a couple other people reported this happening too
However, my test machine already had the latest BIOS update in place at the time. Is it possible that this happens when updating the BIOS for the first time on a machine that's already been updated? I haven't had time to test myself yet.