Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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:
$ cd Downloads
# dpkg -i linux-image-3* initramfs-tools_0.99* firmware-realtek_0.36*
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.
Distribution: Debian Sid AMD64, Raspbian Wheezy, Slackware Current AMD64, various VMs
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?