"I don't know, but I promise you that we will hunt down and punish those held reponsible"Image
I think you've found the rights guys for hunting down and punishing. Isnt that the good old Hussein on that picture...
mimosa wrote:I think you have gremlins.
but i never fed it after midnight, maybe i should trickle some water on it, to validate your suspicion.
First, do you know if Salix is using a different driver for the network connections?
i did not changed any drivers except the video-driver, but i noticed that Salix is not connecting to the internet with a tool like "networkmanager" or "wicd", Salix is using its own "dhcpcd" script to connect, it takes a little bit longer than the networkmanager tool, with the scripts, but it is working fine the dhcp server is answering in 3 seconds or something and the script continues...
Try using the console equivalent of GSlapt and Sourcery, slapt-get and slapt-src to see if they product the strange noise. If so then I would suggest trying wget from the console to download an iso. Try something like this both as a normal user and root:
ah thank you for the hint, meanwhile i have found out that this strange noise is only occuring in sudo or su mode of some (not all) gtk and/or gtk2 programs. Working/downloading with the console does not produce these noises after i have entered "wget
http://sourceforge.net/projects/salix/f ... o/download".
What other applications produce this noise? Only when run ad superuser?
for now i identyfied the tools, gslapt, sourcery and the language selection tool producing noises when started as su or sudo.
- gslapt does not start from console as normal user
- sourcery starts as normal user and is not producing these noises
- the language tool starts as normal user and is producing these noises
no coherent pattern... but it seems to have something to do with connecting to the internet as superuser or in superuser mode with a gtk/gtk2 program.
I apologe for not taking your question more seriously. After doing some checking I've found that
no prob, we probably met before at ICM, so dont mind about my sense of humor
You are absolutely right about my cablemodem and my ISP, they block the VOIP function because i do not pay for it.
Your NIC, unlike your modem is accessible to and can be controlled by your OS, it doesn't seem be possible for your OS to be causing your modem to
for me, the noise sounds like a indexing or searching noise loop and the other OS's (Win7, Arch, Crunchbang) on my computer are not making these noises.
I need to read some tutorials about using wireshark as diagnostic tool since i've installed it (took 15 minutes...), i never dealed with a cablemodem issue, because it is working since 2 years now out of the box without any problems. The disabled VOIP functionality is maybe correlated with these noises...?
Found and installed the tool "cmdiag" with sourcery, here is the output, does anybody know that tool?
Code: Select all
harry[~]$ cmdiag
Console is 79 x 23
This program requires a screen size of at least 125 columns by 43 lines
Please resize your window
harry[~]$ cmdiag
Usage: cmdiag -cm <IP> -cms <string> -ct <IP> -cts <string>
-cm <IP> Cable modem IP address.
-cms <string> Cable modem SNMP community string, this option is mandatory.
-ct <IP> CMTS IP address which the cable modem is connected to, if this is not set some parameters are not to be fetched.
-cts <string> CMTS SNMP community string, you can't omit this if -ct is set.
Example: cmdiag -cm 192.168.0.2 -cms public -ct 192.168.0.1 -cts private
Or: cmdiag -cm 192.168.0.2 -cms public
