Date: Fri, 22 Jun 2007 10:35:02 -0700
From: Bob McGowan <bob_mcgowan@symantec.com>
To: debian-user@lists.debian.org
Subject: Re: Turning off the %^&* scroll wheel
Message-ID: <467C0846.4090402@symantec.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010709020501050805040601"
This is a cryptographically signed message in MIME format.
--------------ms010709020501050805040601
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Curt Howland wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Friday 22 June 2007, Jonathan Kaye <jdkaye10@yahoo.es> was heard to
> say:
>> The mouse/touchpad is controlled in /etc/X11/xorg.conf. Look for a
>> Section "InputDevice" and if you see something like this:
>> Option "ZAxisMapping" "4 5"
>> then comment it out. That should get rid of the scrollwheel
>> behaviour.
>
> Mr. Kaye, many thanks. Unfortunately, there is no such option in the
> two "mouse" related sections:
>
> ==========
> Section "InputDevice"
> Identifier "Configured Mouse"
> Driver "mouse"
> Option "CorePointer"
> Option "Device" "/dev/input/mice"
> Option "Protocol" "ExplorerPS/2"
> Option "Emulate3Buttons" "true"
> EndSection
>
> Section "InputDevice"
> Identifier "Synaptics Touchpad"
> Driver "synaptics"
> Option "SendCoreEvents" "true"
> Option "Device" "/dev/psaux"
> Option "Protocol" "auto-dev"
> Option "HorizScrollDelta" "0"
> EndSection
> =============
>
> I tried reconfiguring and changing to imps rather than explorerps2, no
> change.
>
> Is there another possibility?
>
--<snipped>--
Which of these two is actually used in the 'ServerLayout' section?
Whichever it is, you could try switching it to the other and see what
happens.
Or if both are there (as they are for my laptop) you could try
commenting one out to see which is actually defining the wheel. Then
edit the conf file to change the 'Option "Protocol"' for that device to
be some other descriptor.
Another thought, based on output from 'gpm -t help', the imps name is
not listed, but imps2 is. But it seems to include some sort of wheel
functionality. So you might try a very basic interface, such as 'ps2'
or 'fups2' (described as being used for 'broken' PS/2 mice).
Though the names are from gpm they should match names used by X11, since
the two have to (and do in my experience) work together.
--
Bob McGowan
--------------ms010709020501050805040601
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJHzCC
AuowggJToAMCAQICEGJ01+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDkwNzIzMjIwM1oX
DTA3MDkwNzIzMjIwM1owSjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEnMCUG
CSqGSIb3DQEJARYYYm9iX21jZ293YW5Ac3ltYW50ZWMuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAreE3QGsl+S8sSMa+47mwvSsRUXRo7nAxCuPyO82co6aKIj3HfHpt
ad6Ct6JWTjWb6RHzkf5H5UvrlBxi1QhlLe5hALcdFNekO5vbtWSNAsQAUfEiPe4b1e7iOCNY
zefbNaEgM4yQX6zSZEhPAdSq4bU4cXbyxmw3lVA48AdhA/M18fCQ4Q/DfRNit72Iy2f3isSE
d8k2YI/Iq1vks9be2+3/5hR2adqfGUKwBP8/JIFsaB0dngifOTlwOOLQyVV4zCiCVlhIK/NI
ZIa6ldIU7Bs9QxauOoF9gIuOP/RaEPMrfrUMPMpJkSyqijAj0zsKBBEeftmIgkE9x1T7UrMN
0QIDAQABozUwMzAjBgNVHREEHDAagRhib2JfbWNnb3dhbkBzeW1hbnRlYy5jb20wDAYDVR0T
AQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQBkb7U/3ygdvn5n2H+1RFgerZkdQf4s5UwGwT4c
bFCynmuyekDmTcwPneekzPuYtVcrJXQRz2FGNyW7bZlZS7IG2Q5sxlc4lRX5O/H5XgzUOW3a
dAInokaS9OUioMv/HJ48cBt0ldLYQmrYPL+gVah6yWbJWxCZhOMgU8b9tU385zCCAuowggJT
oAMCAQICEGJ01+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDkwNzIzMjIwM1oXDTA3MDkw
NzIzMjIwM1owSjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEnMCUGCSqGSIb3
DQEJARYYYm9iX21jZ293YW5Ac3ltYW50ZWMuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAreE3QGsl+S8sSMa+47mwvSsRUXRo7nAxCuPyO82co6aKIj3HfHptad6Ct6JW
TjWb6RHzkf5H5UvrlBxi1QhlLe5hALcdFNekO5vbtWSNAsQAUfEiPe4b1e7iOCNYzefbNaEg
M4yQX6zSZEhPAdSq4bU4cXbyxmw3lVA48AdhA/M18fCQ4Q/DfRNit72Iy2f3isSEd8k2YI/I
q1vks9be2+3/5hR2adqfGUKwBP8/JIFsaB0dngifOTlwOOLQyVV4zCiCVlhIK/NIZIa6ldIU
7Bs9QxauOoF9gIuOP/RaEPMrfrUMPMpJkSyqijAj0zsKBBEeftmIgkE9x1T7UrMN0QIDAQAB
ozUwMzAjBgNVHREEHDAagRhib2JfbWNnb3dhbkBzeW1hbnRlYy5jb20wDAYDVR0TAQH/BAIw
ADANBgkqhkiG9w0BAQUFAAOBgQBkb7U/3ygdvn5n2H+1RFgerZkdQf4s5UwGwT4cbFCynmuy
ekDmTcwPneekzPuYtVcrJXQRz2FGNyW7bZlZS7IG2Q5sxlc4lRX5O/H5XgzUOW3adAInokaS
9OUioMv/HJ48cBt0ldLYQmrYPL+gVah6yWbJWxCZhOMgU8b9tU385zCCAz8wggKooAMCAQIC
AQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENh
cGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAm
BgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1h
aWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNV
BAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQD
EyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEF
AAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B
1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79A
gAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8E
CDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEa
MBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7M
DaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk1
3iSx0x1G/11fZU8xggNkMIIDYAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3
dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl
ZW1haWwgSXNzdWluZyBDQQIQYnTX54sAOPQklBDqZhgPtjAJBgUrDgMCGgUAoIIBwzAYBgkq
hkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNzA2MjIxNzM1MDJaMCMG
CSqGSIb3DQEJBDEWBBS8key7zk9pUSQATvoYFn3JTG9hDjBSBgkqhkiG9w0BCQ8xRTBDMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMc
VGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFs
IEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ01+eLADj0JJQQ6mYYD7YwgYcGCyqGSIb3DQEJEAIL
MXigdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ0
1+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEBBQAEggEAU4lXcJ+dlH+bPp733CLpNVAKJNgX
NQ8bX/loEHa/wJVHsbU70oXX9qY14gTzFeALwodOXiEqR1S5FycqabDcFSn108WSyM82essE
idgLpktWOW5sVB3TuMxKt5fWnkIGEvGzaFkdX4hy91+MNV7JngWXXpvNSF3oe2I3iVpjbMTz
dRa6WzzposHO5CPp4a1JW+P2C2qOUKROX023X2fIogETgIRWAFjnSduDpWOLzrd9IDXn8F9H
dqt6XdwfuEbXYZz8AT/5XhEIituWPzf8FzkKF7ieWMmoGCABOt9MWpl+1lOFyjwEQyy8GtNz
XYs1IZnUG7AtTmg28u9lVMmlkwAAAAAAAA==
--------------ms010709020501050805040601--
Date: Fri, 22 Jun 2007 19:10:13 +0200
From: Malte Forkel <malte.forkel@berlin.de>
To: debian-user@lists.debian.org
Subject: Waking up server during boot prevents NFS mounts after upgrade to
etch
Message-ID: <467C0275.8000708@berlin.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Because my server is not running all the time, clients that want to
mount NFS volumes use a small initscript during boot to wake up the
server if necessary. After upgrading the clients from sarge to etch,
mounting NFS volumes does not work anymore if the server wasn't up already.
The initscript is called /etc/rcS.d/S41wakeupserver during boot, i.e.
after networking and before portmap and mountnfs.sh. It uses ping to
wait until the network is accessible. Then, if ping still fails because
the server does not respond, wakeonlan is used to wake up the server.
Then, again ping is used to wait until the server responds - or the
operation times out.
I understand that in etch, NFS mounts are performed as soon as the
interface becomes available. But disabling asynchronous mounts
(ASYNCMOUNTNFS=no) does not help. It just keeps the clients from waiting
for 90 seconds before giving up on the NFS mounts.
It takes the server about 1 minute to boot. If the server is up before
the client boots, NFS mounts work fine. With or without asynchronous
mounting. So, may be I have some sort of a timing problem?
What has changed from sarge to etch that makes my NFS mounts fail? How
do I have to change my initscript?
Thanks in advance, Malte
Date: Fri, 22 Jun 2007 17:32:38 +0000
From: "Manon Metten" <manon.metten@gmail.com>
To: "debian users" <debian-user@lists.debian.org>
Subject: OT: Say NO to the Microsoft Office format as an ISO standard
Message-ID: <5da176070706221032u4b5172ebj79422b65f6b361e3@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="----=_Part_134182_29569251.1182533558360"
------=_Part_134182_29569251.1182533558360
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi,
This urgent request was posted on users@openoffice.org
<user@openoffice.org>by Hagar de l'Est
< hagar_de_lest@openoffice.org >.
Is not exactly Debian, but I think also of great importance for all of us.
Please sign the petition here: http://www.noooxml.org/petition.
(Cookies have to be enabled for this site.)
Thanks, Manon.
------=_Part_134182_29569251.1182533558360
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<div><div>Hi,<br><br>This urgent request was posted on <a href="mailto:user@openoffice.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">users@openoffice.org</a> by Hagar de l'Est<br><<a href="mailto:hagar_de_lest@openoffice.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
hagar_de_lest@openoffice.org
</a>>.<br>Is not exactly Debian, but I think also of great importance for all of us.<br><br>Please sign the petition here: <a href="http://www.noooxml.org/petition" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.noooxml.org/petition</a>.<br>(Cookies have to be enabled for this site.)
<br><br>Thanks, Manon.<br></div></div><table style="width: 100%;" cellpadding="0" cellspacing="0"><tbody><tr><td><br></td></tr></tbody></table>
------=_Part_134182_29569251.1182533558360--
Date: Fri, 22 Jun 2007 10:33:30 -0500
From: Hugo Vanwoerkom <hvw59601@care2.com>
To: debian-user@lists.debian.org
Subject: Re: [SOLVED] kqemu on Sid
Message-ID: <f5gq4c$3iu$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Hugo Vanwoerkom wrote:
> Hugo Vanwoerkom wrote:
>> David Baron wrote:
>>> On Tuesday 19 June 2007, debian-user-digest-request@lists.debian.org
>>> wrote:
>>>>> Hi,
>>>>>
>>>>>
>>>>> I installed qemu on Sid.
>>>>>
>>>>> But Sid's kqemu is backlevelled: it depends on a non-existing 2.6.18
>>>>> kernel.
>>>>>
>>>>> So I compiled/installed
>>>>> http://fabrice.bellard.free.fr/qemu/kqemu-1.3.0pre11.tar.gz
>>>>> and that went uneventful.
>>>>>
>>>>> *However...* when I try to boot XP with:
>>>>>
>>>>> qemu -m 256 -localtime -hda /hda7/xp.img -cdrom /dev/cdrom -fda
>>>>> /dev/fd0
>>>>>
>>>>> it hangs the whole system absolutely solid: stops all the
>>>>> clocks+applets
>>>>> and needs the red button.
>>>>>
>>>>> Without kqemu it boots XP.
>>>>>
>>>>> Does anybody run qemu with kqemu installed successfully?
>>>> Thanks for the replies.
>>>>
>>>> However you cannot use the kqemu Sid package because that depends
>>>> upon a
>>>> non-existent kernel.
>>>
>>> The source package is also on Sid. Try installing that using m-a (the
>>> Debian way but I have also numerous times used sources from the site
>>> and compiled manually and simply copied the .ko to it correct place),
>>> change that modprobed/kqemu file and try again. I do not have XP
>>> images around to try but qemu runs most everything.
>>>
>>> For an alternative, you might try virtualbox (they have an opensource
>>> version, a free binary and a paid product). Runs some stuff better
>>> then qemu, somewhat different approach. But it does not run everyting
>>> qemu does.
>>>
>>>
>>>
>>
>> I saw that: it is kqemu_1.3.0~pre11.orig.tar.gz. But the kqemu I
>> installed with is kqemu-1.3.0pre11.tar.gz. Seems to me to be the very
>> same thing. I was going to try a different kernel, I am now running
>> Linux debian 2.6.21-1-k7 #1 SMP PREEMPT
>> and I was going to backup to 2.6.18-k7 which no longer is in Sid but I
>> kept the .debs in my repository.
>> It's more a question of "this ought to work" than running XP because I
>> found out what I needed to know by now.
>
> So kqemu-1.3.0pre11 (the latest version) hangs the system solid with
> 2.6.21-1-k7, the Debian stock kernel. But I have modified that kernel
> with 2.6.21-ck2 from here:
> http://members.optusnet.com.au/ckolivas/kernel/
>
> Going back to the plain 2.6.18-4-k7 Debian kernel and reinstalling kqemu
> all errors disappear and XP initiates "normally" (i.e. M$'s version of
> "normal").
>
> So the problem lies either in 2.6.21-1-k7 or in the -ck modification.
>
In neither. The 2.6.21-1-k7 kernel kqemu fails with has been modified by
me to turn *off* paravirtualization. Defined as follows:
Paravirtualization is a way of running multiple instances of
Linux on the same machine, under a hypervisor. This option
changes the kernel so it can modify itself when it is run
under a hypervisor, improving performance significantly.
However, when run without a hypervisor the kernel is
theoretically slower. If in doubt, say N.
The reason I do that is because with PARAVIRT_CONFIG *set* the
installation of the nvidia closed source driver will fail.
So I turned it off and... qemu hangs on execution.
There is an alternative way of using the unmodified
linux-image-2.6.21-1-k7/686 and instead modifying the
linux-kbuild-2.6.21 .deb and installing the nvidia driver by hand and
twiddling some things.
The gory details are here:
http://www.nvnews.net/vbulletin/showthread.php?t=89844
So qemu hangs in kernel 2.6.21 if you turned off paravirtualization and
are using kqemu. End of story.
Have a good day.
Hugo
Date: Fri, 22 Jun 2007 19:34:01 +0200
From: Kum Gabor <kumgabor@kumgabor.hu>
To: debian-user@lists.debian.org
Subject: MP3 to AMR
Message-Id: <200706221934.01874.kumgabor@kumgabor.hu>
Content-Type: text/plain;
charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hello All!
I tried to find the way how to convert MP3 (or WAV) files to AMR (for mobile
phone), but I can't.
Can somebody help me? (I use Etch)
Regards,
Gabor
Date: Fri, 22 Jun 2007 19:37:49 +0200
From: Matus UHLAR - fantomas <uhlar@fantomas.sk>
To: debian-user@lists.debian.org
Subject: Re: Which device did I boot from?
Message-ID: <20070622173749.GA3671@fantomas.sk>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
> Dallas Clement wrote:
> > I'm trying to determine which device I booted Linux from at run-time.
> > I'd like to obtain the boot device's major/minor numbers or at least
> > it's name while executing an init script from initramfs.
why?
On 21.06.07 13:07, Felipe Sateler wrote:
> I don't know if that is available at initramfs, but there is /proc/cmdline,
> which should tell you what device was used (root=/dev/blah)
actually it will say something like root=302, which means that is was device
with major 3 and minot 2 (/dev/hda2).
But it's not the boot device...
--
Matus UHLAR - fantomas, uhlar(at)fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Honk if you love peace and quiet.
Date: Fri, 22 Jun 2007 11:28:10 -0500
From: Hugo Vanwoerkom <hvw59601@care2.com>
To: debian-user@lists.debian.org
Subject: Re: how hot is my xeon?
Message-ID: <f5gtar$f16$2@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
michael wrote:
> On Fri, 2007-06-22 at 16:36 +0200, Pol Hallen wrote:
>>> I've tried unsuccessfully to monitor my dual Xeon box but lm-sensors
>>> doesn't seem to detect anything.
>> Do u have the i2c kernel modules?
>>
>> Pol
>>
>>
>
> michael@ratty:~/Fortran$ sudo lsmod|grep -i i2c
> i2c_dev 8548 0
> i2c_i801 7468 0
> i2c_core 19680 3 i2c_dev,nvidia,i2c_i801
>
>
>
Do you have lm-sensors installed?
What does the 'sensors' command show?
Hugo
Date: Fri, 22 Jun 2007 07:49:56 -0500
From: Dallas Clement <dallas.a.clement@gmail.com>
To: Matus UHLAR - fantomas <uhlar@fantomas.sk>
Cc: debian-user@lists.debian.org
Subject: Re: Which device did I boot from?
Message-Id: <1182516596.4846.23.camel@localhost>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
On Fri, 2007-06-22 at 19:37 +0200, Matus UHLAR - fantomas wrote:
> > Dallas Clement wrote:
> > > I'm trying to determine which device I booted Linux from at run-time.
> > > I'd like to obtain the boot device's major/minor numbers or at least
> > > it's name while executing an init script from initramfs.
>
> why?
>
I'm trying to run a custom Linux install script from initramfs. I want
to avoid the possibility of mistakenly installing Linux over the top of
my boot device. :) Hence, needing to know with certainty which device I
booted Linux from.
I'm trying to boot Linux from a USB drive on a system that may have
other USB, IDE, SCSI drives present, each of which could possibly have
GRUB/Linux already installed.
Ideally I would like to determine the root device without ever having
mounted any other devices.
If I know which is the boot device, I can present a menu of choices
excluding the boot device on which Linux can be installed which would
involve partitioning, formatting, and copying files.
Date: Fri, 22 Jun 2007 20:53:52 +0300
From: ndemou@gmail.com
To: michael <cs@networkingnewsletter.org.uk>
Cc: "debian user" <debian-user@lists.debian.org>
Subject: Re: how hot is my xeon?
Message-ID: <cc703c350706221053q7ed77e3escb478cf15defb862@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 6/22/07, michael <cs@networkingnewsletter.org.uk> wrote:
> [...]... my box gets noisy and I'm trying to see
> if it's temp related
as a precaution: clean all the air intakes, clean all heatsinks that
have a cooler on them
(it's just amazing what a difference cleaning can make)
and you can probably check the temperatures in the BIOS
Date: Fri, 22 Jun 2007 19:55:51 +0200
From: Matus UHLAR - fantomas <uhlar@fantomas.sk>
To: debian-user@lists.debian.org
Subject: Re: Connected to DHCP server but cannot access internet
Message-ID: <20070622175551.GB3671@fantomas.sk>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
> Rehceb Rotkiv wrote:
> > I can suddenly no longer access the internet with my Debian Etch (default
> > kernel + updates). I get "Page not found" in Firefox and ping
> > www.somesite.com says "unknown host". ifdown eth0 && ifup eth0 and the
> > thereby invoked dhclient work as expected, that is I get a valid IP address
> > by the DHCP server etc.
On 21.06.07 14:57, Tod Detre wrote:
> What is in your /etc/resolv.conf? Do the correct name servers appear in
> there?
>
> If you ping an ip address of a server, does it work? What about using an
> IP in firefox?
>
> If the name server is set up correctly in /etc/resolv.conf, but you're
> not getting name resolution, make sure you can get to the nameserver.
> Try pinging it and/or traceroute ( traceroute -p 53 <nameserverip> ).
do you have package 'resolvconf' installed? It should take care of your
resolv.conf file and configure it properly from interface-up-scripts.
--
Matus UHLAR - fantomas, uhlar(at)fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Remember half the people you know are below average.
Date: Fri, 22 Jun 2007 18:43:43 +0100
From: Barry Samuels <barry@beenthere-donethat.org.uk>
To: Debian <debian-user@lists.debian.org>
Subject: (g)mplayer stops
Message-Id: <1182534223l.13851l.0l@dataman1>
Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
I have two machines both running uptodate Debian Testing. They both =20
have Mplayer and mozilla-mplayer installed.
One of them will play video from the web using Iceweasel and the other =20
won't. On the one that won't I see a message saying 'buffering' then a =20
short while later 'stopped'. Restarting produces the same 'stopped' =20
message.
Also on the machine that doesn't play if I start gmplayer or mplayer =20
from a console window the lines displayed are the same as on the =20
machine that does work except for the last line which is:
Option Creating needs a parameter at line 1
and then back to the console prompt.
Any ideas please?
--=20
Barry Samuels
http://www.beenthere-donethat.org.uk
The Unofficial Guide to Great Britain
Date: Fri, 22 Jun 2007 11:24:38 -0500
From: Hugo Vanwoerkom <hvw59601@care2.com>
To: debian-user@lists.debian.org
Subject: Re: hddtemp value
Message-ID: <f5gt49$f16$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Pol Hallen wrote:
> Hi folks :-)
>=20
> Which value hddtemp show? (about my ata disks, between 45-55 C)
>=20
> Is it correct? Or I should worry?
>=20
I use hddtemp and have 3 disks: 2 ATA and 1 USB mounted.
Hddtemp cannot read the USB mounted disk.
Hda is Maxtor 6Y080P0: 28=B0C and is older
Hdc is ST380011A: 39=B0C
The ambient temperature is about 26 degrees, so hda is almost certainly=20
wrong and feeling the disks it would seem hdc is right.
Hugo
Date: Fri, 22 Jun 2007 11:32:32 -0500
From: Hugo Vanwoerkom <hvw59601@care2.com>
To: debian-user@lists.debian.org
Subject: Re: compatible UPS - solved
Message-ID: <f5gtj1$gl0$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
csanyipal wrote:
> On Fri, Jun 22, 2007 at 12:19:13PM +0200, csanyipal wrote:
>
>> Is this UPS supported by Etch?
>>
>> Inform Guard 600A (600VA)/Line Interractive/AVR
>>
>> Any advices will be appreciated!
>
> Sorry for this mail abowe.
> I find this link, which solve my problem:
> http://www.apcupsd.org/
>
And that site says that apcupsd supports an Inform Guard 600A?
Hugo
Date: Fri, 22 Jun 2007 14:05:11 -0400
From: "Andrew J. Barr" <andrew.james.barr@gmail.com>
To: Kum Gabor <kumgabor@kumgabor.hu>
Cc: debian-user@lists.debian.org
Subject: Re: MP3 to AMR
Message-ID: <20070622140511.1b296197@conroe.oakcourt.dyndns.org>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Kum Gabor <kumgabor@kumgabor.hu> wrote:
> Hello All!
>
> I tried to find the way how to convert MP3 (or WAV) files to AMR (for
> mobile phone), but I can't.
> Can somebody help me? (I use Etch)
Do you have the debian-multimedia.org repository installed?
> Regards,
>
> Gabor
>
>
--
Andrew J. Barr
Woke up in my clothes again this morning,
don't know exactly where I am...
Date: Fri, 22 Jun 2007 20:17:25 +0200
From: Kum Gabor <kumgabor@kumgabor.hu>
To: debian-user@lists.debian.org
Subject: Re: MP3 to AMR
Message-Id: <200706222017.25474.kumgabor@kumgabor.hu>
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Friday 22 June 2007 20:05, Andrew J. Barr wrote:
> Kum Gabor <kumgabor@kumgabor.hu> wrote:
> > Hello All!
> >
> > I tried to find the way how to convert MP3 (or WAV) files to AMR (for
> > mobile phone), but I can't.
> > Can somebody help me? (I use Etch)
>
> Do you have the debian-multimedia.org repository installed?
No. Which package I need? And how ro convert!
Special thanks! :-D
G.
Date: Fri, 22 Jun 2007 18:07:36 -0000
From: amhoov@gmail.com
To: debian-user@lists.debian.org
Subject: 2.6 kernel upgrade gives garbled video (w/o X11)
Message-ID: <1182535656.696033.118480@z28g2000prd.googlegroups.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi all,
I recently attempted to upgrade my kernel from 2.4.27 to 2.6.18 on my
Sarge installation. First off, I had to change my sources.list to use
the Etch packages because of a dependency loop involving libc6.
However, I did the kernel installation w/ "apt-get install kernel-
image-2.6-686" and the installation completed successfully w/ my Grub
configurations updated automatically.
When I restarted the machine and selected the 2.6 kernel, the boot
process proceeded fine (and I could read all the text scrolling by).
But when it came time to display the login prompt (terminal only, it's
a server, so there's no X11) the screen got all garbled. Essentially
all I can see is flickering black and white boxes covering the screen.
However, I can login and reboot the machine - I just can't see what
I'm typing.
Anyone have any suggestions on this one? I tried installing the kernel-
image-2.6-386 on a lark, but I still ran into the same problem. I'm
not passing any special kernel parameters on boot to the 2.4 kernel
either. What am I missing?
Thanks,
Aaron
Date: Fri, 22 Jun 2007 18:12:42 -0000
From: "amhoov@gmail.com" <amhoov@gmail.com>
To: debian-user@lists.debian.org
Subject: 2.6 kernel upgrade gives garbled video (w/o X11)
Message-ID: <1182535962.090829.83460@d30g2000prg.googlegroups.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi all,
I recently attempted to upgrade my kernel from 2.4.27 to 2.6.18 on my
Sarge installation. First off, I had to change my sources.list to use
the Etch packages because of a dependency loop involving libc6.
However, I did the kernel installation w/ "apt-get install kernel-
image-2.6-686" and the installation completed successfully w/ my Grub
configurations updated automatically.
When I restarted the machine and selected the 2.6 kernel, the boot
process proceeded fine (and I could read all the text scrolling by).
But when it came time to display the login prompt (terminal only, it's
a server, so there's no X11) the screen got all garbled. Essentially
all I can see is flickering black and white boxes covering the screen.
However, I can login and reboot the machine - I just can't see what
I'm typing.
Anyone have any suggestions on this one? I tried installing the kernel-
image-2.6-386 on a lark, but I still ran into the same problem. I'm
not passing any special kernel parameters on boot to the 2.4 kernel
either. What am I missing?
Thanks,
Aaron
End of debian-user-digest Digest V2007 Issue #1824
**************************************************
Received on Fri Jun 22 15:06:42 2007