Detecting Acer Aspire Hardware on Debian 5.0.5
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
Let's see what we can do.
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
deb http://ftp.egr.msu.edu/debian lenny main
just add contrib and non-free to it like
deb http://ftp.egr.msu.edu/debian lenny main contrib non-free
you will need root privilege to edit the file.
The b43-fwcutter is something else you will probably need to use to extract the firmware for the broadcom card.
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."
Then you must not be getting root somehow. Do this.
Open a konsole/terminal and issue the command
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
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
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.
When I try to run apt-get update, it gives me a bunch of diagnostics:
I think you are getting these errors because you do not have a functioning internet connection. You'll need this to download additional software.
I appreciate your wireless isn't working, but can you use an ethernet connection until you get it working?
Most distros will automatically establish a wired connection with DHCP if the ethernet cable from your PC is plugged into your router before you boot.
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.
So, does your wired ethernet work?
I will try booting the PC with the ethernet connected and report back.
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
If it is a matter of downloading ISOs which would I need? I am currently running Debian Lenny with KDE on my Acer Aspire
Here is my complete lspci readout:
with the machine power up, the ethernet cable plugged into the computer and the router run from root
you should get something like, but with your system specs instead of xxx
eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx Mask:xxx.xxx.xxx.xxx
inet6 addr: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:66794 errors:0 dropped:0 overruns:0 frame:0
TX packets:16105 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:13413067 (12.7 MiB) TX bytes:1994873 (1.9 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:303 errors:0 dropped:0 overruns:0 frame:0
TX packets:303 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:20826 (20.3 KiB) TX bytes:20826 (20.3 KiB)
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.
your hardwire card seems to be supported by the kernel look at
look at this thread too
I remember when the boy had some issues awhile back with the pci card definitions needing updated before his card would be recognized. look at this
there is a link post 5 that gives better instructions on how to update them.
a google search on this
Broadcom Device 1692 linux
will help shed some light on your problem
When I try to run ifconfig on eth0, it doesn't recognize eth0 at all. Also, I am unclear on what to do with Tigon3.
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.
Don't give up. We are rooting for you.:D
|All times are GMT -5. The time now is 12:04 AM.|