Re: systemd on amd64
On Thu, 2019-08-22 at 13:49:22 +1000, Andrew McGlashan wrote: > > >> >> Any help would be appreciated. > > Check "Devuan Beowulf", > currently under development. > Or even "Devuan ASCII" -- stable. AFAIR Jack had asked for Buster... ASCII is Stretch. - S
Re: systemd on amd64
On Wed, 2019-08-21 at 12:08:07 -0300, Jack Warkentin wrote: > Hi everybody > > I would like to install Buster on my amd64 machine *without* systemd. Is > this possible? If so, how? I have read the entire installation manual and > could not find anything about how to do this. Also. I could find nothing > about it in the debian-amd64 archives. > > I have been using debian since 2002, but at age 81 I am too old to learn a > new way of doing basic maintenance on my machine. > > Any help would be appreciated. Check "Devuan Beowulf", currently under development. - S
Re: Fwd: Fwd: module nvidia not found / amd64 jessie
On Fri, Nov 14, 2014 at 07:35:43AM +, Francesco Pietra wrote: # nvidia-smi -L bash: nvidia-smi: command not found # nvidia-smi bash: nvidia-smi: command not found https://packages.debian.org/search?suite=allsearchon=nameskeywords=nvidia-smi Jessie still has a broken package -3, the issue is supposed to be fixed in -4 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766343 but that didn't migrate due to the freeze... Something that should be resolved soon (the bug is tagged important) - S -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141114083751.gn30...@casco.aei.mpg.de
Re: Wheezy: mcelog not getting notified of ECC errors anymore?
On Mon, Jun 03, 2013 at 02:32:39PM -0500, Karl Schmidt wrote: This is serious - I sure hope you wrote up a bug report? I first wanted to make sure that the serious error isn't on my side. Up to now I seem to be the only one affected... S -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130604070529.gk20...@casco.aei.mpg.de
Wheezy: mcelog not getting notified of ECC errors anymore?
After installing Wheezy (using FAI, so the setup is essentially unaltered), one of my machines doesn't report memory errors via mcelog anymore. Error messages go to syslog instead: Jun 3 09:47:07 testbed kernel: [231899.816038] [Hardware Error]: CPU:0 MC0_STATUS[Over|CE|-|-|AddrV|CECC]: 0xd4674833 Jun 3 09:47:07 testbed kernel: [231899.816282] [Hardware Error]: MC0_ADDR: 0x76d39ec0 Jun 3 09:47:07 testbed kernel: [231899.816377] [Hardware Error]: Data Cache Error: during system linefill. Jun 3 09:47:07 testbed kernel: [231899.816534] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: DRD, part-proc: SRC (no timeout) Jun 3 09:47:07 testbed kernel: [231899.816899] [Hardware Error]: CPU:0 MC2_STATUS[Over|CE|-|-|-|CECC]: 0xd0004863 Jun 3 09:47:07 testbed kernel: [231899.817136] [Hardware Error]: Bus Unit Error: PRF/ECC error in data read from NB: SRC. Jun 3 09:47:07 testbed kernel: [231899.817314] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: PRF, part-proc: SRC (no timeout) Jun 3 09:47:07 testbed kernel: [231899.817677] [Hardware Error]: CPU:0 MC4_STATUS[Over|CE|-|-|AddrV|CECC]: 0xd46740020813 Jun 3 09:47:07 testbed kernel: [231899.817915] [Hardware Error]: MC4_ADDR: 0x7fafc410 Jun 3 09:47:07 testbed kernel: [231899.818009] [Hardware Error]: Northbridge Error (node 0): DRAM ECC error detected on the NB. Jun 3 09:47:07 testbed kernel: [231899.818189] EDAC amd64 MC0: CE ERROR_ADDRESS= 0x7fafc410 Jun 3 09:47:07 testbed kernel: [231899.818289] EDAC MC0: CE page 0x7fafc, offset 0x410, grain 0, syndrome 0xce, row 1, channel 0, label : amd64_edac Jun 3 09:47:07 testbed kernel: [231899.818298] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: SRC (no timeout) Jun 3 09:47:08 testbed kernel: [231900.804029] [Hardware Error]: CPU:1 MC0_STATUS[Over|CE|-|-|AddrV|CECC]: 0xd4674833 Jun 3 09:47:08 testbed kernel: [231900.804278] [Hardware Error]: MC0_ADDR: 0x7a673600 Jun 3 09:47:08 testbed kernel: [231900.804371] [Hardware Error]: Data Cache Error: during system linefill. Jun 3 09:47:08 testbed kernel: [231900.804530] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: DRD, part-proc: SRC (no timeout) Jun 3 09:47:08 testbed kernel: [231900.804894] [Hardware Error]: CPU:1 MC2_STATUS[Over|CE|-|-|-|CECC]: 0xd0004863 Jun 3 09:47:08 testbed kernel: [231900.805130] [Hardware Error]: Bus Unit Error: PRF/ECC error in data read from NB: SRC. Jun 3 09:47:08 testbed kernel: [231900.810632] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: PRF, part-proc: SRC (no timeout) Jun 3 09:52:07 testbed kernel: [232199.816039] [Hardware Error]: CPU:0 MC0_STATUS[Over|CE|-|-|AddrV|CECC]: 0xd4674833 Jun 3 09:52:07 testbed kernel: [232199.816284] [Hardware Error]: MC0_ADDR: 0x0021086ea0c0 Jun 3 09:52:07 testbed kernel: [232199.816378] [Hardware Error]: Data Cache Error: during system linefill. Jun 3 09:52:07 testbed kernel: [232199.816536] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: DRD, part-proc: SRC (no timeout) Jun 3 09:52:07 testbed kernel: [232199.816901] [Hardware Error]: CPU:0 MC2_STATUS[Over|CE|-|-|AddrV|CECC]: 0xd4004813 Jun 3 09:52:07 testbed kernel: [232199.817139] [Hardware Error]: MC2_ADDR: 0x77ef0cc0 Jun 3 09:52:07 testbed kernel: [232199.817232] [Hardware Error]: Bus Unit Error: RD/ECC error in data read from NB: SRC. Jun 3 09:52:07 testbed kernel: [232199.817409] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: SRC (no timeout) Jun 3 09:52:07 testbed kernel: [232199.817771] [Hardware Error]: CPU:0 MC4_STATUS[Over|CE|-|-|AddrV|CECC]: 0xd46740020813 Jun 3 09:52:07 testbed kernel: [232199.818008] [Hardware Error]: MC4_ADDR: 0x7fafc410 Jun 3 09:52:07 testbed kernel: [232199.818101] [Hardware Error]: Northbridge Error (node 0): DRAM ECC error detected on the NB. Jun 3 09:52:07 testbed kernel: [232199.818282] EDAC amd64 MC0: CE ERROR_ADDRESS= 0x7fafc410 Jun 3 09:52:07 testbed kernel: [232199.818382] EDAC MC0: CE page 0x7fafc, offset 0x410, grain 0, syndrome 0xce, row 1, channel 0, label : amd64_edac Jun 3 09:52:07 testbed kernel: [232199.818391] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: SRC (no timeout) Jun 3 09:52:08 testbed kernel: [232200.804035] [Hardware Error]: CPU:1 MC0_STATUS[Over|CE|-|-|AddrV|CECC]: 0xd4674833 Jun 3 09:52:08 testbed kernel: [232200.804283] [Hardware Error]: MC0_ADDR: 0x7a673600 Jun 3 09:52:08 testbed kernel: [232200.804377] [Hardware Error]: Data Cache Error: during system linefill. Jun 3 09:52:08 testbed kernel: [232200.804534] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: DRD, part-proc: SRC (no timeout) Jun 3
Re: making non-free CD and DVD images etc....
On Tue, Apr 29, 2008 at 04:03:19PM +, Michael Fothergill wrote: Dear folks, I am using an amd64 box I just bought in an environment where there is no nearby internet connection. [...] What would be the most efficient way of doing this? What about setting up a Debian mirror, and a NFS root server, for example on a laptop? FAI comes to mind... Or use the netboot CD, and your own transportable mirror if you don't want to learn FAI. Cheers, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sensors
On Fri, Apr 25, 2008 at 03:11:37AM -0700, Francesco Pietra wrote:
Following a suggestion by Romain Delbeau (lm-sensors H8DC8 board), I
contacted Supermicro again. Their prompt answer:
H8QCE uses Winbond W83627HF-AW monitoring chip which currently is not
supported by lm-sensors utility.
Sure, Supermicro knows better than the chip driver which chips are supported by
lm-sensors :(
You have seen some sensors output from a 627 chip, haven't you?
They just might have told you their wiring... and let you find out the rest.
Why they did not provide this information at my first instance is a mystery.
Why they don't know better, is a mystery for me :((
S
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sensors
On Thu, Apr 24, 2008 at 01:37:52AM -0700, Francesco Pietra wrote:
--- On Wed, 4/23/08, Steffen Grunewald [EMAIL PROTECTED] wrote:
Did you search the lm-sensors site with the make of your MB
yet?
At the site http://www.lm-sensors.org/wiki/Devices adm1026 is not listed,
while at site
http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/chips/adm1026 it is
said to be in development. Curiously it is said able to detect three
temperatures, while the motherboard has five temp to detect (four CPUs and
system). I probably did not find the right site, as adm1026 is on my machine
and BIOS detects the five temps..
Please don't look for the individual chips.
Look for your mainboard instead, there might be ready-to-use
sensors.conf files.
Did you check SuperMicro's ftp site?
S
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sensors
On Wed, Apr 23, 2008 at 09:45:58AM -0400, Lennart Sorensen wrote: On Wed, Apr 23, 2008 at 02:13:02AM -0700, Francesco Pietra wrote: Also, is any chance to configure the sensors.conf from data read from BIOS in order to have a correct sampling of temperatures and fan speeds? (without having specific data for the sensors) No. The fan speed should be fairly simple in general. It is usually either correct or it has to be divided by 2 or 4 to make it correct. The maximum and minimums for the alarm state should be set based on the actual speed of your fan when it works normally. For voltages, the sensors I have worked with will read correct for any voltage under 4V, but need an offset and multiplication factor for any voltages over 4V (since they use a resistor network to scale the voltage down into a 0 to 4V range for the sensor). To get an accurate reading really requires knowing which resistor values were used. Of course you also need to know which voltage is supposed to be on each input on the sensor since they could really be used for anything the board maker chooses. There are a few very nice design documents for sensor chips out there (IIRC I grabbed the one for a WD...627HF - did I get the number right?) which shows that there should be a linear dependency of the sensor input reading on the voltage measured, indeed. For negative voltages, and for some positive ones too, there's not only a multiplier/divider but also a bias voltage. Which means that the raw register reading (the one you get in the /proc or /sys filesystem) is always positive, and you've got to fiddle with a and b in register_value = a * voltage + b or, reversed, real_voltage = 1/a * register_value - b/a That's exactly what the conversion formulae are for. If one knows that resistors usually don't come in arbitrary values but follow some rules (look for E series, common values are 6.8 and 10, times a power of ten) it's easy to guess. Note that a single data point (taken from BIOS readings) doesn't allow to determine a and b simultaneously! Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sensors
On Wed, Apr 23, 2008 at 07:37:33AM -0700, Francesco Pietra wrote: Hi: Following your indications below, 1/2 hour after that I sent a request to Supermicro Europe, I got the offsets to apply: Bus Type = I/O Mapping and SMBus Two ADM1026 Analog Devices ADM1026, Slave Address=0x2c (0x58 in 8-Bit format) = Fan1 Fan Speed, Offset 0x38 [...] Now I have to learn how to apply these offsettings when configuring /etc/default/sensors.conf. Not configured, the response of sensors was: Note that these are register offsets, not voltage biases or the like. Since your board seems to have plenty of sensor chips one has to expect that not all inputs are wired (and their readings may be nonsensical). There's the ignore option to fix this. Sometimes the same voltages are fed into different chips. Did you search the lm-sensors site with the make of your MB yet? S -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI Device Addresses
On Fri, Feb 29, 2008 at 12:20:24PM +, Steve Dobson wrote:
As the kernel is assigning disk IDs dynamically is there some way of
forcing given devices to have given SCSI addresses. Our plan is to have
the 16 disks configured into 4 arrays of four disks each. There maybe
times when a disk array is taken off line and the disks pulled. What I
don't want is for the arrays downstream of the pulled array to be
assigned different SCSI addresses and thus come up with the wrong file
system on the mount points.
What about using labels or UUIDs for mounting?
Steffen
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug config
On Wed, Nov 28, 2007 at 12:45:17PM +0100, Michelle Konzack wrote:
update-alternatives --config editor
If I would do this, my customers will kill me.
To use vi, you must be handicaped or a geek.
So I'm handicapped because I prefer vi(m) over ed?
Thanks a lot indeed,
Steffen
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
High Performance Linpack
Hi,
I'm looking for a recent version of HighPerformanceLinpack (you know, the
one that is used to build the top-500 list) and instructions how to
compile and run it under Debian/Etch on amd64 architecture.
I have (C)BLAS and LAM-MPI already installed, but keep getting compile
errors (from deep inside) :-(
Any suggestions?
S
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: High Performance Linpack
On Wed, Mar 21, 2007 at 12:59:36PM +0100, Steffen Grunewald wrote:
Hi,
I'm looking for a recent version of HighPerformanceLinpack (you know, the
one that is used to build the top-500 list) and instructions how to
compile and run it under Debian/Etch on amd64 architecture.
I have (C)BLAS and LAM-MPI already installed, but keep getting compile
errors (from deep inside) :-(
Replying to myself:
I had to install libmpich1.0-dev (and BLAS/ATLAS dev packages), and heavily
twaek the Make.arch file, to get a xhpl binary. But I can only run it on
MPICH, not LAM-MPI. Suggestions?
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom/Serverworks chipsets (was Re: a few simple questions about AMD64 version of Debian)
On Thu, Dec 21, 2006 at 09:14:07AM -0800, Freddie Cash wrote:
Has someone experience with k8 Broadcom/Serverworks chips?
Excellent question. I'd be interested in hearing from people that
have used/tried motherboards using this chipset. It appears to be
the only other choice in server boards if once avoids nForce boards.
You're supposedly talking about HT1000 and the like? SuperMicro's H8SSL
motherboard series is based on this chipset, and there's a 640+ node
cluster based on this board at U Wisconsin Milwaukee (and soon here
too). What do you want to know?
Yes, the HT1000 and similar ServerWords chipsets. These are the only
other non-nForce server chipsets out there (other than Intel, but we
prefer Opterons to Xeons).
How's the Linux support, Debian specifically? We're using Tyan boards for
For Linux support, look at http://lsc-group.phys.uwm.edu and proceed to
the Nemo cluster. They have set up quite a lot of documentation.
While Nemo is running FC4, we @AEI decided to install Debian (Etch) onto
our cluster which is still in an early test phase (only about 1/8 of the
hardware being delivered). Basically, if you build your own kernels (we had
to to have support for Areca RAID controllers, and the Gilgal eth chip on
one of the headnodes [purchased separately]) you're fine. We've been using
FAI to diagnose and install three different types of hardware, and it went
smoothly (OK, three years of FAI experience before...)
all our servers, but have been notified that the S2882 boards we love may
be phased out in 2007, so we're looking for possible replacements. Are
Everything that works will soon be end-of-life.
all the onboard devices detected and usable? Starting with which version
of the kernel? Specifically, the NICs. Also, how is the hardware
management (SMBus, I2C, temperature monitoring, etc)? Is there remote
management (inband or out-of-band) available for the motherboard?
NICs are tg3, kernel 2.6.17 has recent drivers.
For health monitoring, we use IPMI (which conflicts with lm_sensors).
Also IPMI can do remote power on/off/whatever, serial-over-LAN etc.
And, finally, does all of the above work with the 64-bit version of
Debian?
We never tried i386 :-)
S
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom/Serverworks chipsets (was Re: a few simple questions about AMD64 version of Debian)
On Wed, Dec 20, 2006 at 01:47:51PM -0800, Freddie Cash wrote:
On Wednesday 20 December 2006 12:44 pm, Marco Maske wrote:
Has someone experience with k8 Broadcom/Serverworks chips?
Excellent question. I'd be interested in hearing from people that have
used/tried motherboards using this chipset. It appears to be the only
other choice in server boards if once avoids nForce boards.
You're supposedly talking about HT1000 and the like? SuperMicro's H8SSL
motherboard series is based on this chipset, and there's a 640+ node cluster
based on this board at U Wisconsin Milwaukee (and soon here too).
What do you want to know?
S
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Keys too old or compromised ?
On Tue, Nov 21, 2006 at 03:18:23PM -0500, Lennart Sorensen wrote:
On Tue, Nov 21, 2006 at 08:17:29PM +0100, Hans-J. Ullrich wrote:
Dear maintainers,
I just get this message when using apt-get update.
-- snip
W: Es gibt keine ?ffentlichen Schl?ssel f?r die folgenden Schl?ssel-IDs:
A70DAF536070D3A1
W: Es gibt keine ?ffentlichen Schl?ssel f?r die folgenden Schl?ssel-IDs:
A70DAF536070D3A1
W: Es gibt keine ?ffentlichen Schl?ssel f?r die folgenden Schl?ssel-IDs:
A70DAF536070D3A1
gpg --recv-keys 6070d3a1
gpg --armor --export 6070d3a1 | apt-ket add -
The Debian 4.0/etch repositories have got a new key on 2006-11-20.
S
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Keys too old or compromised ?
On Wed, Nov 22, 2006 at 11:05:32AM +0100, Hans wrote: that is exactly what thought. I knew, that thle lifetime of the keys is on its end in these days, but I just wanted to make sure, I update the correct keys and to make sure, the keys are really outdated. Now we all know ! This is not exactly true: apt-key list will tell you that the 2006 signing key will last more than 10 weeks from now. But nevertheless it's a good idea to have a longer-lasting key for the then stable release. S -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sensory data from intel board
On Wed, Nov 15, 2006 at 12:40:36PM -0800, michael wrote:
Hello,
Trying to get sensor to work with an IntelS5000VSA board.
Have etch with kernel 2.6.17 (x86_64) installed.
lm-sensors and sensor-detect recommends to install:
i2c-isa
i2c-ipmi
bmcsensors
I can modprobe i2c-isa, but not i2c-ipmi or bmcsensors.(missing)
Looks like I should install module ipmi_si, but attempting
from modconf or simply modprobing it results in a hang.
Have to reboot to kill it off.
If you use IPMI *don't* use lm-sensors. You're calling for trouble.
modprobe ipmi_{devintf,msghandler,si}, create /dev/ipmi0, and use
ipmitool.
Steffen
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sensory data from intel board
On Thu, Nov 16, 2006 at 10:12:25AM -0800, michael wrote:
On Thu, 16 Nov 2006 09:59:28 -0800, michael wrote
Purged lm-sensors and removed the i2c* modules.
rebooted and loaded ipmi_devintf and ipmi_msghandler okay.
However, trying to modprobe ipmi_si still ends up hanging.
Perhaps the server board doesn't support this module?
or maybe there's a conflict somewhere?
Whats really dumb is that even in the MB BIOS, there's no power management
to even look at the CPU temp. So I have no idea how hot the CPU's
are running.
Okay, I spoke a little too soon.
There was some intel management stuff disabled in the bios by default.
I enabled, rebooted, and now the ipmi_si module loads no problem.
# ipmitool sensor
Gives me the info I was looking for.
Great! You now might be interested in the ipmitool-devel list (hosted
by the ipmitool sourceforge project)
Thanks,
Mike
You're welcome. It's nice if someone else is half a step ahead, isn't it? :-)
Cheers,
Steffen
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Partial Local Repository
On Fri, Nov 17, 2006 at 09:13:14AM +0800, GNU Linux wrote: Hello all, I am planning to create a partial local repository for AMD64 Etch but I don't know the best tool for this. I downloaded and tried the anonftpsync http://www.debian.org/mirror/anonftpsync but until now, it keeps on downloading files. Any other recommended tool to create a partial local repository? I don't want apt-proxy because it requires the local repository server to have an Internet connection. I don't know what partial means; if you want to select etch and amd64, debmirror is your tool of choice. Does it make sense that I'm already downloading the packages for Etch even if it's not yet the stable version? I'm just preparing Etch because it will be the next stable version starting next month. Or shall I just wait until Etch has been finally released as stable? It makes sense since debmirror will clean up obsolete packages. Just run it once per night/week/whatever ... Cheers, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: smartmontools
On Fri, Oct 27, 2006 at 08:27:58AM +, Francesco Pietra wrote: How to activate SMART at booth with amd64 etch raid1? Apparently start_smartd=yes in /etc/default/smartmontools does not work (unlike in non-raid i386 etch pc). Log messages? I suspect you'd have to change your /etc/smartd.conf from AUTODETECT to specific addressing the disks (including the -d ata flag). To check hds i had to command from terminal window: #smartctl -s on -d ata /dev/sda #smartctl -s on -d ata /dev/sdb Which is the way to get SMART activated at boot? smartd tries to start, but with AUTODETECT enabled it probably does NOT detect the disks (since one has to go thru libata for this). This behaviour might change with the next release of smartmontools; please check with their sf.net site. Cheers, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't install -- locks up
On Thu, Aug 17, 2006 at 07:46:47PM -0600, Andrew Robinson wrote: I can't install debian, the installer just keeps locking up / hanging at seeming random parts of the installation. Randomness usually points at random sources, not the ones that are properly under control: external temperature/airflow, bad CPU cooling, or failing capacitors on the board. Also RAM sockets can be involved. MB: 9NPA EPoX nForce 4 Ultra Motherboard this is supposed to be new enough not to suffer yet from failing C's RAM: 3 sticks PC 2700 (1.75 gb) did you run memtest86+ ? the modules might have moved slightly HD: Samsung Sata 2 CPU: AMD X2 dual core 3800+ if cooled properly, AMDs should be OK, check hardware monitor in BIOS whether there are abnormal temperatures or voltages Debian: Etch/testing netinstall from Aug 17, 2006 Selected ftp.debian.us (something like that) mirror Created 2 partitions (1 swap, 1 reiserfs) Setup SMTP Hung on lib6 installation attempt #2: hung on grub-install (hg0) can you compare the uptimes? Not sure what is wrong. RAM timings with motherboard (ram is good though, I didn't upgrade it), bad hardware, bad installer version on that day, etc. I'd blame the installer build last... S -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot install a bootloader
On Tue, Jun 20, 2006 at 11:07:05AM +0200, Dirk Bonenkamp - Bean IT wrote: Hi All, I've trouble installing the bootloader (both grub and lilo fail). I'm using the netinstall cd-image to install. My first idea was a problem with my RAID controller (Adaptec 2020ZCR, running a 4 disc raid 5 array) but it even fails to install a bootloader to a floppy disc. So I think it's a general problem, instead of a hardware problem. It always returns the same error message: The file /boot/grub/stage1 not read correctly. The thing I found out is that the new / filesystem is still mounted under /target, but I guess this is normal while installing...? (never bothered to look, since it always works out fine). I've seen this error message a few times. grub must be installed from a chroot environment (which should be true in your case). grub must find a *correct* mtab to resolve hard disk partitions. (it's a bit tricky since the /proc/mounts trick appears not to work) A leftover device.map may confuse it as well. Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot install a bootloader
On Tue, Jun 20, 2006 at 11:25:18AM +0200, Dirk Bonenkamp - Bean IT wrote: Hi Steffen, Thanks for your reply. Only I'm not sure what to do now... I've chrooted to /target and tried to install grub again, still the same error. The mtab and device.map look correct to me. Could you give me another hint? Run the script by sh -x and look what exactly is being extracted for the (hd*,*) values, and compare with your setup Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: incomplete install
On Wed, May 10, 2006 at 03:35:14AM +0200, thierry wrote: Hi, list: I am trying to install Etch on a laptop. Actually,the install goes well, but nor KDE, nor Gnome will install due to dependencies problems, too numerus to list here. Has anyone experienced the same problem, or am I doing something wrong? With amd64, I'm seeing the same, most apps depending on gnome 2.14 and kde 3.5.2, both of which aren't complete yet. This has been holding up upgrades for about a week now. To me, it looks like the buildds are not keeping up and/or there's a problem with the sid-etch transition. Since I installed sarge long ago, and dist-upgraded to testing from there, I keep having a stable and working system (most of the time at least) Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The future of the amd64 port
On Tue, Apr 11, 2006 at 06:19:51AM -0700, rickh wrote: I should know this, but my choices for sources.list repositories have always been provided by the installation program. Now it seems that I'll have to change it, and I'm not sure what the exact change should be. I'm guessing something like: deb ftp://ftp.us.debian.org/amd64/ testing main contrib non-free deb-src ftp://ftp.us.debian.org/amd64/ testing main contrib non-free ^ this part should read /debian/. And yes, it looks very reasonable. S -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ram
On Fri, Apr 07, 2006 at 09:02:45AM -0400, Lennart Sorensen wrote:
On Fri, Apr 07, 2006 at 06:57:06AM +0200, Francesco Pietra wrote:
In setting up a workstation with
--two amd6a 265 opterons dual core
--Tyan K8WE S2895SA3NRF main board
--two 360GB raid1 hd (raid 1 software by debian)
--ram 2GB (Kingston KVR400D4R3A/2G - DDR 400 Ecc Registered), is any reason
to
prefer two slots of memories 1GB each instead of a single 2GB slot?
The technician here maintains that two slots are needed to have needed two
channels.
Incidentally, the 2GB Kingston is charged in Italy six hundred euros, that
is
more than twice the price in US. This is to recognize that we can
circumvent
the market leader software houses (and be more efficient) but we cannot
avoid
the system in our country which favors handlers against citizen (and
against
scientific research activities). The results of such policy are under the
eyes.
With 2 * 1GB, you get 6.4GB/s memory bandwidth. With 1 * 2GB, you get
3.2GB/s memory bandwidth. I think that is a reason to prefer the
pair 1GB sticks
Socket 939/940 AMD's have dual channel memory controllers to get double
memory bandwidth, but only if you put in at least two sticks of memory
(and into the right slots on the board).
Wouldn't this mean that, in a dual CPU system, one should better use 4 mem
modules?
S
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
