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.
You can move this to the Debian subforum if you see fit, but here's my problem.
(I'm running Debian Lenny, 5.0.5)
Aside from the microphone, webcam and speakers not working (which I would also like to have recognized at some point; at least the speakers, anyway)
Through someone helping me grep and lpsci, I have determined that the eth0 is Broadcom Device 1692 and the WiFi card is Broadcom Device 4537.
I have tried to get thru installing NdisWrapper but always run into the same problem. I'm able to run this line
Code:
aptitude install module-assistant wireless-tools
fine without any problems (do I need to download anything and put it on the PC I've got Debian running on?).. but as soon as I get to the next section, the terminal freezes up and gives me a diagnostic:
Code:
Installation of the ndiswrapper-source source failed.
Ignoring this package. Maybe you need to add something to sources.list, maybe the contrib and non-free archives.
So, how do I go about installing the right drivers and getting ndiswrapper set up?
First, have you checked to see if the Broadcom cards have any native support? Mostly they don't but you never know. Google should help with that.
You should be able to fix the installation error by editing your /etc/apt/sources.list and adding contrib and non-free to your repos. You should have a line that looks something like
First, have you checked to see if the Broadcom cards have any native support? Mostly they don't but you never know. Google should help with that.
You should be able to fix the installation error by editing your /etc/apt/sources.list and adding contrib and non-free to your repos. You should have a line that looks something like
The b43-fwcutter is something else you will probably need to use to extract the firmware for the broadcom card.
Even as root it is telling me "Permission denied" when I try to access /etc/apt/sources.list
And when I try to edit sources.list in KWrite and save changes it says "Access denied. Could not write to /etc/apt/sources.list.part."
Last edited by ColtraneFan89; 08-17-2010 at 08:13 PM.
Then you must not be getting root somehow. Do this.
Open a konsole/terminal and issue the command
su
enter your root password
you should now have a # prompt instead of a $ prompt
issue the command
apt-get install nano
and install that simple text editor. When that completes issue the command
nano /etc/apt/sources.list
you should end up in a very plain jane text editor with the contents of your sources files up. Make your changes and press ctrl+x (i think) and save your file.
then issue the command
apt-get update
that will reload the available repositories then you should be able to install what you want to.
Note: apt-get and aptitude are mostly interchangeable.
Mostly you can ignore those messages. They are telling you that for some reason the Debian Security site won't resolve. That seems to happen to me frequently too.
You can comment out, by adding a # to the beginning of line, the cd-rom access. You should not need it any more. I would not remove it yet but commenting it out will speed things up a bit.
And as tredegar says you do need a working ethernet connection for this to work. You may however be able to get to the same place by downloading all the disk-iso's and going that route but I would hold off on that until you have exhausted the ethernet way first.
I tried connecting the router to the computer and restarting, nothing. I tried connecting the computer to the modem directly via Ethernet and still nothing. When I use the ethernet connection from the router to the computer
It says:
Code:
An error occurred while loading http://www.kde.org/:
Unknown host www.kde.org
The router works fine on the other computers in the house (including the one I am typing on at present).
If it is a matter of downloading ISOs which would I need? I am currently running Debian Lenny with KDE on my Acer Aspire
you should get at least 2 network interfaces. The lo interface is just local to your machine. The other one should show your ip address. if you only have one then the system is not recognizing it being there. That usually means that a module(driver) needs to be loaded. If the interface is there but it does not have an ip address then you will need to configure your networking. Post what you get so we can see how to proceed.
you should get at least 2 network interfaces. The lo interface is just local to your machine. The other one should show your ip address. if you only have one then the system is not recognizing it being there. That usually means that a module(driver) needs to be loaded. If the interface is there but it does not have an ip address then you will need to configure your networking. Post what you get so we can see how to proceed.
Tigon3 seems to be the module(driver) for your card. It should be automatically detected and loaded on boot. That appears to not be happening. So the question is why not.
Look at the log files in /var/log mostly syslog, messages, dmesg, and boot if you have it. Examine them carefully and see if you can find a boot message that sheds some light on why the module is not getting loaded. Open a terminal (may need root) and run
cat /var/log/dmesg | grep broadcom
That should help narrow down your search. You can change the file name (dmesg) and the search keyword (boradcom) to different files and keywords to help find what you are looking for. If you get to many results and it scrolls off the screen you can append | less to the command and then you can scroll through it. | is a pipe, it is on the backslash key.
The reason that ifconfig does not work on eth0 for you is because the device eth0 is not in the system. When we get the module to load eth0 will show up when you run ifconfig.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.