Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Heh, because I copied and pasted from your post, I replicated your error (corrected now). dpkg does not take the "install" argument like the apt tools, just use the "-i" option alone (for more info see the man page).
Download the following packages from the squeeze-backports repo:
initramfs-tools
firmware-realtek
Then do:
Code:
$ cd Downloads
# dpkg -i linux-image-3* initramfs-tools_0.99* firmware-realtek_0.36*
OK; I'll download the 'initramfs-tools' and the 'firmware'
But I'll have to download from my laptop and carry those packages over to my Desktop and cut and paste them manually
into the Downloads directory-- Let you know what happens tomorrow afternoon.
Well dpkg doesn't do dependency resolution, so if you installed initframfs-tools first and then the other two, all should have been well. Jumping to another distro at the first sign of trouble seems a bit much. Besides you could have upgraded to or just installed wheezy as easily. Anyway good luck with whichever path you choose.
Thought Wheezy wasn't available until May like Tobi told me--
It is available now as the Testing branch of Debian, official release is most likely to happen in May, the number of release critical bugs is down to 7 now.
It is available now as the Testing branch of Debian, official release is most likely to happen in May, the number of release critical bugs is down to 7 now.
That's very good news!
I think the preferred practice for me would be to wait until May, burn a fresh new DVD/CD and than go through a new install.
In the meantime I'll be performing an install of a new (new to me) distribution (UE 3.5) that is Debian and Ubuntu based--
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Why not just install Wheezy now? Installing another distro for a week or two rather than wheezy because the latter has a couple of bugs you will not likely even encounter seems a little odd. You do realise that once the bugs are squashed a simple apt-get update would fix them, don't you?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.