Results 1 to 8 of 8
Is there anyone who had the problem that the computer is making a kind of "beeping" noise when i'm connected to a wireless connection but doesn't make any sounds when ...
- 01-27-2007 #1Just Joined!
- Join Date
- Oct 2006
- Location
- Sweden
- Posts
- 53
Hardware problem
Is there anyone who had the problem that the computer is making a kind of "beeping" noise when i'm connected to a wireless connection but doesn't make any sounds when i'm plugged in with the networkcable?
This is my problem and I have no idea what's wrong but some things I have done as a debugging:
First of all, the sound is not a quick "beep" and then stop, it's closer to a constant ringing, so quick beeps with a little paus in between. So you don't think that its saying "beep" once and no more :P
The problem is only in linux, when I use my wireless in windows everything is fine and also windows wired connection is quite. So I booted into debian and directly disabled the wireless, no weird sounds. Put my ear against the keyboard and unplugged the network-cable, directly network-manager started to search for other networks and the same second the sound started.
Keept my ear against the keyboard and plugged the network-cable back in, and the sound disappeared directly so it has something to do with the wireless connection. Since it works in windows xp it should not be a hardware problem with the network card so i'm blaming the wireless driver.
I have a intel pro wireless 2200BG and using the ipw2200 driver and 2.6.18-3-686 linux-kernel on a debian etch system. My computer is a Latitude x1.
Is there anyone who has heard of this problem before because i'm going nuts from the sound, its to loud and to irritating to just ignore?
Can it be some kind of conflict between the driver and the kernel or anything close to that?
edit: Is there anyone who knows about a GUI for the networkcard to make configurations? And by that I don't mean to configure wireless network connection, I mean to configure the networkcard?
- 01-27-2007 #2
You can see if the system acknowledge is some way the problem.
Check the output of
And ofCode:dmesg
to see if you can find any clues.Code:cat /var/log/syslog
Also, you can perhaps force the system to load the ipw2200 with some specific parameters.
For example, create a file /etc/modprobe.d/ipw2200 with this content :
as the default hardware cryptography is sometimes buggy.Code:options ipw2200 hwcrypto=0
Then reload the module."To express yourself in freedom, you must die to everything of yesterday. From the 'old', you derive security; from the 'new', you gain the flow."
-Bruce Lee
- 01-27-2007 #3Just Joined!
- Join Date
- Oct 2006
- Location
- Sweden
- Posts
- 53
Ok, I will check this out for clues!
Originally Posted by antidrugue
A hardware bug sounds exactly like the thing I need to eliminateAlso, you can perhaps force the system to load the ipw2200 with some specific parameters.
For example, create a file /etc/modprobe.d/ipw2200 with this content :
as the default hardware cryptography is sometimes buggy.Code:options ipw2200 hwcrypto=0
by doingThen reload the module.
i have had som problems with modprobe when I was using ndiswrapper so I want to be sure that this is what I am suppose to do.Code:modprobe ipw2200 ?
Will try this now, thank you.
- 01-28-2007 #4will unload it.Code:
modprobe -r ipw2200
will load it.Code:modprobe ipw2200
As always, check the man pages for more :
Code:man modprobe
"To express yourself in freedom, you must die to everything of yesterday. From the 'old', you derive security; from the 'new', you gain the flow."
-Bruce Lee
- 01-28-2007 #5Just Joined!
- Join Date
- Oct 2006
- Location
- Sweden
- Posts
- 53
Yep, I did find that.
Originally Posted by antidrugue
Yes, i figured that I could find it there so I did check the man pages, stupid of me to ask.As always, check the man pages for more :
Code:man modprobe
Reloading the module did not do any difference. Consider the following:
My computer is a latitude x1, which means that I have no fans or other moving parts except the harddrive, so the only thing that is able to cause the noise is the harddrive. My question is, how can the harddrive make weird noises when I'm using a wireless connection and not when I use the wired?
I just got a new harddrive from dell so the problem is not the hardware i presume (had the same trouble with the last harddrive aswell) and only in linux that time to.
Does anyone know of a graphical tool to make network-card changes? There is some sort of conflict that I can't seem to find.
"dmesg" and "cat /var/log/syslog" didn't give me anything, it just said that the network-card is found and in use and so on..
edit: i'm going to try to find something similar from intel who made the card. If anyone else has ideas, your are more then welcome.
I've tried with something called "mii-diag" but that only monitored my wired connection, it did not recognize my eth2 (which is the one used for wireless)
- 01-28-2007 #6What do you mean you had the same problem with the old hard drive ? The exact same noise ? And a new hard drive solved it ?
Originally Posted by bnei
While you are at it, you can as well upgrade your BIOS to the latest Latitude X1 System Bios version A06 from Dell. It is a simple thing to try, and it just might help."To express yourself in freedom, you must die to everything of yesterday. From the 'old', you derive security; from the 'new', you gain the flow."
-Bruce Lee
- 01-28-2007 #7Just Joined!
- Join Date
- Oct 2006
- Location
- Sweden
- Posts
- 53
I'm sorry if I confused you. My last harddrive had the same problem that I have now, it made a weird sound when I was using a wireless connection but only in debian (not in XP). But the last harddrive got very hot and after a while it started to smell like it was burning so something was wrong with the "arm" on the last harddrive from my understanding. I thought that the noise it made in debian would go away aswell but it didn't so now I don't think it's the harddrives fault.
Originally Posted by antidrugue
Ok, I will do this right away, it might do some good.While you are at it, you can as well upgrade your BIOS to the latest Latitude X1 System Bios version A06 from Dell. It is a simple thing to try, and it just might help.
edit: flashing BIOS didn't help i'm affraid. I don't know what to do about this, I don't think that dell will give me support when I say "i'm using debian", so I don't know were else to turn but here : (
- 01-30-2007 #8Just Joined!
- Join Date
- Oct 2006
- Location
- Sweden
- Posts
- 53
My problem is finally gone and if someone ever has the same problem, here is how to get rid of it.
The problem was that the processor has the ability to make noises when entering some of it's possible states. Depending on operating system and drivers, this function can go nuts and start beeping when it's not suppose to (atleast I don't want it to).
So create a script that does
should make the beeping go away. The script disallows the processor to be able to make the beepsounds (if I understood it correctly).Code:echo 2 > /sys/module/processor/parameters/max_cstate
Thank you all for trying to help me!


Reply With Quote
