from:"mauro"




Il 25/11/2015 23:56, Lisi Reisz ha scritto:

On Wednesday 25 November 2015 21:12:03 Mauro Condarelli wrote:

Il 25/11/2015 21:28, Lisi Reisz ha scritto:

On Wednesday 25 November 2015 20:14:04 Mauro Condarelli wrote:

Pretty Please,
tell me this isn't true:
The only sensible answer I got from debian list boils down to: "use
proprietary driver".

This is truly sad, especially since I *know* Linux Mint (which is a
debian derivative, through ubuntu parentage) does indeed work
out-of-the-box with *no* configuration at all.

Presumably with a proprietary driver.  Mint makes no claims to be
entirely Free.

You should (!) not presume too much.
I am not used to speak without checking.
Linux Mint uses nouveau for NVidia.

Then why can't you use the same version of nouveau in Debian?

Sometimes I ask myself if I really am an idiot unable to understand what people 
says.
I fail to understand what You are really asking.
I, very obviously, *am* using the same version of nouveau.
Unfortunately drivers do not live in a vacuum and thus *that* nouveau behaves 
differently in the two ecosystems.
I have been unable (to date) to pinpoint significant difference between the two 
systems.
Do You really think I would be here begging for help if I knew what was 
different?
What I am asking is exactly some help to diagnose this debian fault.

Regards
Mauro



If You would have bothered checking lsmod I sent a few days ago you would
have known.

Regards
Mauro


Lisi


A desolate
Mauro

Il 23/11/2015 14:40, Ric Moore ha scritto:

On 11/22/2015 10:44 AM, Mauro Condarelli wrote:

Thanks Ric,
care to share details on how You managed such a marvel?
How did You disable the internal (intel) "video card" (actually inside
the CPU chip)? From BIOS?
What other configuration did You do?

I just disabled the video feature in the bios. Then I loaded the nvidia
driver. Then I used nvidia-settings to use xinerama and to configure
the order of the monitors. When you "save to X configuration file",
save it in your home directory as you are "user" and not able to save
directly to /etc/X11. Open a terminal and "sudo cp xorg.conf /etc/X11"
to put it there. If you have monitors of differing size, the X Server
Display Configuration will allow you to play tricks, like panning to a
smaller screen to be bigger through scrolling. Slick! Ric

Re: Debian seems unable to drive my (4) monitors




Il 25/11/2015 22:35, Ric Moore ha scritto:

On 11/25/2015 03:14 PM, Mauro Condarelli wrote:

Pretty Please,
tell me this isn't true:
The only sensible answer I got from debian list boils down to: "use
proprietary driver".

This is truly sad, especially since I *know* Linux Mint (which is a
debian derivative, through ubuntu parentage) does indeed work
out-of-the-box with *no* configuration at all.


If this is the same box, you can mount the mint drive/partition and look for an 
/etc/X11/xorg.conf file to copy to your Debian install~or~ follow these steps:
http://www.instructables.com/id/How-to-set-up-multiple-monitors-in-linux/?ALLSTEPS

Site is up again.
That is one of the sites I checked before.
Instructions given there do not work for me.
After trying them I doubt they work for anyone nowadays; they're over eight 
years old and a lot changed in Linux/X world since.
What was sound advice is now retrocomputing.
The exercise of deleting misleading old info isn't practiced often, 
unfortunately.



The HUGE reason I recommend the nvidia driver is that you will get much better 
performance IF you want to play openGL games and less tearing as you move windows 
from monitor to monitor. Yeah, I am a selfish shameless pig.   Ric

Also this info isn't very state-of-the-Art.

Regards
Mauro

Re: Debian seems unable to drive my (4) monitors




Il 25/11/2015 22:35, Ric Moore ha scritto:

On 11/25/2015 03:14 PM, Mauro Condarelli wrote:

Pretty Please,
tell me this isn't true:
The only sensible answer I got from debian list boils down to: "use
proprietary driver".

This is truly sad, especially since I *know* Linux Mint (which is a
debian derivative, through ubuntu parentage) does indeed work
out-of-the-box with *no* configuration at all.


If this is the same box, you can mount the mint drive/partition and look for an /etc/X11/xorg.conf file to copy to your Debian install~or~ follow these 

As said multiple times:
Linux Mint works *WITHOUT* any configuration.
*NO* /etc/X11/xorg.conf (no, neither xorg.conf.d is present) I can copy.
That's why I suspect difference lies in compilation switches in either X server 
or kernel itself.


steps:
http://www.instructables.com/id/How-to-set-up-multiple-monitors-in-linux/?ALLSTEPS

Unfortunately the site seems down :(



The HUGE reason I recommend the nvidia driver is that you will get much better 
performance IF you want to play openGL games and less tearing as you move windows 
from monitor to monitor. Yeah, I am a selfish shameless pig.   Ric

I tried that, but it doesn't work either, or, at least, I was not able to make 
it work, despite I tried several configurations (and also no configuration).

Regards
Mauro

Re: Debian seems unable to drive my (4) monitors




Il 25/11/2015 23:07, Catalin Soare ha scritto:



On Nov 25, 2015 11:54 PM, "Mauro Condarelli" mailto:mc5...@mclink.it>> wrote:
>
>
> Il 25/11/2015 22:23, Catalin Soare ha scritto:
>>
>> Hello there,
>>
>> Maybe it is as you said earlier, an option in the kernel. Namely, the no 
multicard support you mentioned earlier, is it possible that was comming from the 
kernel itself or was it noveau?
>>
> Thanks Catalin.
>
> Context of said error is:
> ...
> [ 7.708] (II) Loading sub module "fbdevhw"
> [ 7.708] (II) LoadModule: "fbdevhw"
> [ 7.708] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
> [ 7.709] (II) Module fbdevhw: vendor="X.Org Foundation"
> [ 7.709] compiled for 1.17.2, module version = 0.0.2
> [ 7.709] ABI class: X.Org Video Driver, version 19.0
> [ 7.709] (WW) Falling back to old probe method for vesa
> [ 7.709] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card 
support
> [ 7.709] (II) Loading sub module "dri2"
> [ 7.709] (II) LoadModule: "dri2"
> [ 7.709] (II) Module "dri2" already built-in
> [ 7.709] (--) NOUVEAU(0): Chipset: "NVIDIA NVE4"
> [ 7.709] (II) NOUVEAU(0): Creating default Display subsection in Screen 
section
> "Default Screen Section" for depth/fbbpp 24/32
> [ 7.709] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
> [ 7.709] (==) NOUVEAU(0): RGB weight 888
> ...
>
> I do not know where it comes from (if You want I can post or pastebin the 
whole log again).
> I tried googling, but never found an explanation, only cited in threads 
"solved" by other means.
> VGAarbiter is a kernel module but AFAIK it deals with "legacy VGA devices" which do not 
"allow relocation of such (I/O or memory space) ranges"; it is unclear to me if this applies 
to my case.
>
> I am willing to experiment, but I need help because I have no experience with 
video drivers.
>
> Regards
> Mauro

No need to upload again, I admit I didn't bother to check since apparently 
others have already and I don't have experience with Linux drivers.

Personally, what I would do in this case is save the dmesg for debian 
somewhere; go back to Mint and check dmesg over there too. Also check if Mint 
has blacklisted any modules, such as, for example fbdevhw? Either way, there 
should be something that you will find by matching the 2 OSs.


Thanks.
willdo.
Mauro

Re: Debian seems unable to drive my (4) monitors



Il 25/11/2015 22:23, Catalin Soare ha scritto:

Hello there,

Maybe it is as you said earlier, an option in the kernel. Namely, the no 
multicard support you mentioned earlier, is it possible that was comming from 
the kernel itself or was it noveau?


Thanks Catalin.

Context of said error is:
...
[ 7.708] (II) Loading sub module "fbdevhw"
[ 7.708] (II) LoadModule: "fbdevhw"
[ 7.708] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 7.709] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 7.709] compiled for 1.17.2, module version = 0.0.2
[ 7.709] ABI class: X.Org Video Driver, version 19.0
[ 7.709] (WW) Falling back to old probe method for vesa
[ 7.709] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 7.709] (II) Loading sub module "dri2"
[ 7.709] (II) LoadModule: "dri2"
[ 7.709] (II) Module "dri2" already built-in
[ 7.709] (--) NOUVEAU(0): Chipset: "NVIDIA NVE4"
[ 7.709] (II) NOUVEAU(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
[ 7.709] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 7.709] (==) NOUVEAU(0): RGB weight 888
...

I do not know where it comes from (if You want I can post or pastebin the whole 
log again).
I tried googling, but never found an explanation, only cited in threads 
"solved" by other means.
VGAarbiter is a kernel module but AFAIK it deals with "legacy VGA devices" which do not 
"allow relocation of such (I/O or memory space) ranges"; it is unclear to me if this 
applies to my case.

I am willing to experiment, but I need help because I have no experience with 
video drivers.

Regards
Mauro

Re: Debian seems unable to drive my (4) monitors




Il 25/11/2015 21:28, Lisi Reisz ha scritto:

On Wednesday 25 November 2015 20:14:04 Mauro Condarelli wrote:

Pretty Please,
tell me this isn't true:
The only sensible answer I got from debian list boils down to: "use
proprietary driver".

This is truly sad, especially since I *know* Linux Mint (which is a debian
derivative, through ubuntu parentage) does indeed work out-of-the-box with
*no* configuration at all.

Presumably with a proprietary driver.  Mint makes no claims to be entirely
Free.

You should (!) not presume too much.
I am not used to speak without checking.
Linux Mint uses nouveau for NVidia.
If You would have bothered checking lsmod I sent a few days ago you would have 
known.

Regards
Mauro



Lisi

A desolate
Mauro

Il 23/11/2015 14:40, Ric Moore ha scritto:

On 11/22/2015 10:44 AM, Mauro Condarelli wrote:

Thanks Ric,
care to share details on how You managed such a marvel?
How did You disable the internal (intel) "video card" (actually inside
the CPU chip)? From BIOS?
What other configuration did You do?

I just disabled the video feature in the bios. Then I loaded the nvidia
driver. Then I used nvidia-settings to use xinerama and to configure the
order of the monitors. When you "save to X configuration file", save it
in your home directory as you are "user" and not able to save directly to
/etc/X11. Open a terminal and "sudo cp xorg.conf /etc/X11" to put it
there. If you have monitors of differing size, the X Server Display
Configuration will allow you to play tricks, like panning to a smaller
screen to be bigger through scrolling. Slick! Ric

Re: Debian seems unable to drive my (4) monitors


Pretty Please,
tell me this isn't true:
The only sensible answer I got from debian list boils down to: "use proprietary 
driver".

This is truly sad, especially since I *know* Linux Mint (which is a debian 
derivative, through ubuntu parentage) does indeed work out-of-the-box with *no* 
configuration at all.

A desolate
Mauro

Il 23/11/2015 14:40, Ric Moore ha scritto:

On 11/22/2015 10:44 AM, Mauro Condarelli wrote:

Thanks Ric,
care to share details on how You managed such a marvel?
How did You disable the internal (intel) "video card" (actually inside
the CPU chip)? From BIOS?
What other configuration did You do?


I just disabled the video feature in the bios. Then I loaded the nvidia driver. Then I used nvidia-settings 
to use xinerama and to configure the order of the monitors. When you "save to X configuration 
file", save it in your home directory as you are "user" and not able to save directly to 
/etc/X11. Open a terminal and "sudo cp xorg.conf /etc/X11"
to put it there. If you have monitors of differing size, the X Server Display 
Configuration will allow you to play tricks, like panning to a smaller screen 
to be bigger through scrolling. Slick! Ric

Re: Debian seems unable to drive my (4) monitors

2015-11-23 Thread Mauro Condarelli


That is indeed the case; thanks.

log of the "failing" debian installation is now at: 
http://paste.debian.net/335212/

The only "strange" thing I see is: "[ 7.709] (WW) VGA arbiter: cannot open kernel 
arbiter, no multi-card support"

Is it relevant? If so what does it mean (and how do I fix it)?
I tried googling, but I didn't find a good answer (I understood this is 
connected to VGA text-mode, but ansvers weren't positive).

Any hint welcome.

Do You need a log also for the "working" Linux Mint live CD (USB, actually) 
boot process?

Thanks
Mauro

Il 23/11/2015 08:32, Dominique Dumont ha scritto:

On Monday 23 November 2015 05:19:43 Mauro Condarelli wrote:

In my case there was NO log to /var/log/xorg.0.log.

Since xorg-server (2:1.17.3-1), Xorg log may end up in ~/.local/share/xorg/

Hope this helps

Re: Debian seems unable to drive my (4) monitors


http://paste.debian.net/334935/ Is the lspci/lsmod of working (4 monitors) 
Linux Mint.
http://paste.debian.net/335124/ Is the dmesg/lspci/lsmod of the non-ok debian 
(2 monitors on Nvidia, intel monitors dead and second NVidia monitor 
misbehaving (no background redraw))

In both cases no /var/log/Xorg.#.log was generated.
Apparently you have to request it explicitly in /etc/X11/xorg.conf (or 
equivalent).
In my (current) case I had no configuration, so xorg server was "free to chose".

Thanks in advance for any hint.
Regards
Mauro


Il 23/11/2015 05:37, Felix Miata ha scritto:

Mauro Condarelli composed on 2015-11-23 05:19 (UTC+0100):


No need to make so much fuss about the way I sent logs: I sent them directly 
attaching them in Thunderbird and via paste.debian.net.

I never found any link in any of your emails to paste.debian.net


In my case there was NO log to /var/log/xorg.0.log.

What about /var/log/Xorg.0.log? If none, it indicates your installation
included no Xorg or KDE or Gnome or etc. was installed. What exactly appeared
on the two monitors attached to the same "card"?

Re: Debian seems unable to drive my (4) monitors


Whoa!
No need to make so much fuss about the way I sent logs: I sent them directly 
attaching them in Thunderbird and via paste.debian.net.
In my case there was NO log to /var/log/xorg.0.log.
Can someone suggest how can I understand what's wrong with debian install? ... 
or is the implicit answer to go to Mint?
After zillions of messages discussing what I should, should not, and perhaps would, do 
(not to mention the "meaning of should" to which we should give a cold 
shoulder) is there someone willing to give some hint?
The best I got is "It works fine on my machine" (implying I must be non compos 
mentis).
I have high respect of Debian philosophy and practice, but the list seems to be 
drifting a way a bit too much.
Signal/noise ratio is dangerously approaching usenet standards.

Sorry for the rant, but I'm really tired right now (05:18 AM here and i 
finished coffee supply some hours ago)
g'nite!
Mauro


Il 23/11/2015 02:06, Felix Miata ha scritto:

Gene Heskett composed on 2015-11-22 19:29 (UTC-0500):


Felix Miata wrote:

Xorg.0.log contains bits that can be considerd personal in nature.

How so? I don't recall ever seeing a passwd, or a list of my meds
included in it.
Please explain just what it is in the way of personal info that we are to
expunge before posting.

"can be considered" means opinions are involved, and possibly nothing is
actually risky or personal or needs redaction. I'm not going to catalog what
bits might be among them. One to consider:

hostname

Re:


Mom always said: "don't feed the Troll!"
I should have listened to her...

The truly ridikkulus(!) thing is ranting against "our" behavior he is doing the 
same exact thing, only with more force and arrogance.

Pretty please to everyone:
Let us stop feeding the Troll; he is really getting too fat.

I, for one, won't answer again in this thread.

Regards to everyone
Mauro

Re: Debian seems unable to drive my (4) monitors


Thanks Ric,
care to share details on how You managed such a marvel?
How did You disable the internal (intel) "video card" (actually inside the CPU 
chip)? From BIOS?
What other configuration did You do?

TiA
Mauro

Il 22/11/2015 16:24, Ric Moore ha scritto:

On 11/22/2015 07:03 AM, Richard Owlett wrote:

On 11/22/2015 5:46 AM, Mauro Condarelli wrote:

I have a setup with two video cards (intel HD Graphics 4600 +
NVidia GeForce GTX 770) and four monitors (two for each card).
I can see all monitors under Windows, but I can see (active, of
course) only two under debian (on the same card).
I tried several configurations to no avail and finally I gave up :(


I disabled my onboard video and installed an identical nvidia card in a spare 
PCIe slot. Now I have all four monitors running with the nvidia driver, all 
fully accelerated. Native Linux games can run spread across them and it's a 
mindblast! I can move applications between them with no tearing. Nice. Ric

Re: Debian seems unable to drive my (4) monitors


Hi,
comments below.

Il 22/11/2015 14:09, Felix Miata ha scritto:

Mauro Condarelli composed on 2015-11-22 13:24 (UTC+0100):


I have been able to make them *both* work (using custom xorg.conf), but not *at 
the same time* (under debian)
The working setup (linixmint) does not appear to use any proprietary driver 
(i.e.: it uses nouveau for NVidia).
I attach here full lspci and lsmod output (of *working* setup; i.e. LM) in case 
they give some hint.

I only found your lsmod output.

Useful hints are most often found in Xorg.0.log, which for some people at
least, is better seen in a "pastebin"[1] than an email attachment.

the whole packed is available at: http://paste.debian.net/334935/

I currently am under Win7 (on the same hardware) and I cannot switch.
I will post Xorg.0.log of both machines (BTW I already looked several times at 
the failing one, without any success, but You eyes could be trained better than 
mine, of course) ASAP.

Regards
Mauro

Also, what brand and model is your motherboard? FWIW, most motherboards
disable the onboard video when PCIe slot(s) is/are populated by gfxcard, so
it's nice to know when someone finds one lacking this limitation. Knowing CPU
model might also be useful if the video is in the CPU rather than on a
separate chip on the board.

[1] e.g. http://paste.debian.net/ or your own personal web space

Re: Debian seems unable to drive my (4) monitors


I have been able to make them *both* work (using custom xorg.conf), but not *at 
the same time* (under debian)

The working setup (linixmint) does not appear to use any proprietary driver 
(i.e.: it uses nouveau for NVidia).

I attach here full lspci and lsmod output (of *working* setup; i.e. LM) in case 
they give some hint.

TiA
MAuro


Il 22/11/2015 13:03, Richard Owlett ha scritto:

On 11/22/2015 5:46 AM, Mauro Condarelli wrote:

I have a setup with two video cards (intel HD Graphics 4600 +
NVidia GeForce GTX 770) and four monitors (two for each card).
I can see all monitors under Windows, but I can see (active, of
course) only two under debian (on the same card).
I tried several configurations to no avail and finally I gave up :(

Yesterday I discovered another data point:
Linuxmint (I tested the "live" distribution) can drive all my
monitors, apparently with no configuration at all (no
/etc/X11/xorg.conf or similar).

LMDE (Linux Mint Debian Edition - essentially the same
distribution, but based on Debian instead of Ubuntu) has the same
problems of plain debian.


Which card does *NOT* work? Does it require a non-free driver?
[My Debian machine is a laptop so I never used multiple monitors]





I *suspect* problem comes from different options enabled (kernel
config?), but I have no idea how to debug such a thing.

I did a dump of lspci and lsmod on the working (lm) system and my
next move will be to get a similar dump on the non
working(debian) setup.
Is there anything else I should check?
As said: the working system has no explicit xorg configuration.

Please help me; I would hate to leave debian world (I was here
since the beginnings, coming from slackware to "buzz").

Regards
Mauro






Module  Size  Used by
intel_rapl 20480  0 
iosf_mbi   16384  1 intel_rapl
x86_pkg_temp_thermal16384  0 
intel_powerclamp   20480  0 
coretemp   16384  0 
arc4   16384  2 
joydev 20480  0 
kvm_intel 151552  0 
ath9k 147456  0 
kvm   479232  1 kvm_intel
ath9k_common   32768  1 ath9k
snd_hda_codec_hdmi 53248  2 
snd_hda_codec_realtek81920  1 
snd_hda_codec_generic69632  1 snd_hda_codec_realtek
ath9k_hw  458752  2 ath9k_common,ath9k
dm_crypt   24576  0 
snd_hda_intel  36864  8 snd_hda_codec_hdmi
hid_generic16384  0 
snd_hda_controller 32768  1 snd_hda_intel
pl2303 20480  0 
usbhid 53248  0 
snd_hda_codec 143360  5 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
usbserial  49152  1 pl2303
ath32768  3 ath9k_common,ath9k,ath9k_hw
hid   110592  2 hid_generic,usbhid
mac80211  708608  1 ath9k
snd_hwdep  20480  1 snd_hda_codec
crct10dif_pclmul   16384  0 
crc32_pclmul   16384  0 
snd_pcm   106496  4 
snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
eeepc_wmi  16384  0 
ghash_clmulni_intel16384  0 
asus_wmi   24576  1 eeepc_wmi
aesni_intel   172032  0 
snd_seq_midi   16384  0 
sparse_keymap  16384  1 asus_wmi
snd_seq_midi_event 16384  1 snd_seq_midi
snd_rawmidi32768  1 snd_seq_midi
bnep   20480  2 
aes_x86_64 20480  2 aesni_intel
lrw16384  1 aesni_intel
snd_seq65536  2 snd_seq_midi_event,snd_seq_midi
ath3k  20480  0 
cfg80211  524288  4 ath,ath9k_common,ath9k,mac80211
btusb  40960  0 
gf128mul   16384  1 lrw
rfcomm 69632  8 
snd_seq_device 16384  3 snd_seq,snd_rawmidi,snd_seq_midi
glue_helper16384  1 aesni_intel
mei_me 20480  0 
dm_multipath   24576  0 
bluetooth 491520  23 bnep,ath3k,btusb,rfcomm
snd_timer  32768  2 snd_pcm,snd_seq
ablk_helper16384  1 aesni_intel
scsi_dh16384  1 dm_multipath
mei90112  1 mei_me
soc_button_array   16384  0 
serio_raw  16384  0 
cryptd 20480  3 ghash_clmulni_intel,aesni_intel,ablk_helper
snd86016  25 
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device
mac_hid16384  0 
soundcore  16384  2 snd,snd_hda_codec
lpc_ich24576  0 
shpchp 40960  0 
tpm_infineon   20480  0 
parport_pc 32768  0 
ppdev  20480  0 
lp 20480  0 
parport45056  3 lp,ppdev,parport_pc
binfmt_misc20480  1 
squashfs   49152  1 
overlay45056  1 
nls_iso8859_1

Debian seems unable to drive my (4) monitors


I have a setup with two video cards (intel HD Graphics 4600 + NVidia GeForce 
GTX 770) and four monitors (two for each card).
I can see all monitors under Windows, but I can see (active, of course) only 
two under debian (on the same card).
I tried several configurations to no avail and finally I gave up :(

Yesterday I discovered another data point:
Linuxmint (I tested the "live" distribution) can drive all my monitors, 
apparently with no configuration at all (no /etc/X11/xorg.conf or similar).

LMDE (Linux Mint Debian Edition - essentially the same distribution, but based 
on Debian instead of Ubuntu) has the same problems of plain debian.

I *suspect* problem comes from different options enabled (kernel config?), but 
I have no idea how to debug such a thing.

I did a dump of lspci and lsmod on the working (lm) system and my next move 
will be to get a similar dump on the non working(debian) setup.
Is there anything else I should check?
As said: the working system has no explicit xorg configuration.

Please help me; I would hate to leave debian world (I was here since the beginnings, 
coming from slackware to "buzz").

Regards
Mauro

Re: The word 'should'.

2015-11-21 Thread Mauro Condarelli




Il 21/11/2015 23:45, Lisi Reisz ha scritto:

On Saturday 21 November 2015 17:36:46 Mauro Condarelli wrote:

Unfortunately English is not my mother language, so my command of the
language is lacking (so say the least), please bear with me.

Which might limit your ability to comment on the finer nuances of the meaning
of the language.

Please don't take that as a criticism - my knowledge of Italian is only just
the right side of non-existent - but you aren't in a good position to
comment.

That, may be the case, but I feel like I can distinguish between who is really 
trying to force someone else to behave in a well defined way and who isn't.
Here we are not discussing "nuances", but "annoyance".
BTW this is, again, a lawyer trick: divert the attention from the main subject 
to the irrelevant to score a point.

Anyway (back on subject):
Since everybody here is, more or less, in the computer trade: why don't we 
stick to RFC2119? (http://www.ietf.org/rfc/rfc2119.txt)
It seems pretty explicit on what the meaning of "should" should be. (double 
"should" very intentional)

Have a nice weekend!
Mauro


Lisi

Re: The word 'should'.

2015-11-21 Thread Mauro Condarelli




Il 21/11/2015 18:15, moxalt ha scritto:

On Sat, 21 Nov 2015 14:55:29 +0100, Mauro Condarelli  wrote:
Who's the "Taliban"?
https://en.wikipedia.org/wiki/Taliban

I know, thanks.
That was meant as a rhetoric question; alternately spelled as:
"Who fits better the definition of "Taliban" (thanks for the pointer, in case 
someone needs it ;) ) between the original poster and whoever rebuked him?"

Unfortunately English is not my mother language, so my command of the language 
is lacking (so say the least), please bear with me.

Regards
Mauro

Re: The word 'should'.

2015-11-21 Thread Mauro Condarelli




Il 21/11/2015 14:40, John Hasler ha scritto:

Renaud writes:

No, because you are still trying to impose your own values on others.

There is no attempt to impose anything.  "You should do that" does not
mean "You must do that or I will punish you".  Do you find "You should
recycle" offensive?  How about "You should not injure others?"

... not to mention he is the only one, here, who *consistently insists* to have 
others to change *their* behavior.

The original comment boils down to a semantic: "IMHO it's wrong to..." (reread the 
original post, please), while the other side semantic content is: "You *must not* use the word 
'should', otherwise..." (implying failure to comply means offender is ready to eat babies... 
or something worse).

Who's the "Taliban"?

Almost invariably whoever makes such a fuss about words is really after 
something else (as all lawyers know very well).

Regards
Mauro

Re: Bad interaction between multihead display amd desktops in debian squeeze

2015-11-04 Thread Mauro Condarelli


I am currently on "stretch" (testing).
Same behavior.
I seem unable to activate two cards at the same time.
With no /etc/X11/xorg.config I see the internal (Intel) card (no signal on 
nvidia monitors).
If I add explicit NVidia setup then the other two monitors come to life *after 
login*; gdm3 always displays on the intel monitors; after login the intel 
monitors go dark (but they have syncs).
I can't be more precise at the moment because I'm on Win7.

Il 02/11/2015 16:45, moxalt ha scritto:

On Sun, 1 Nov 2015 21:25:45 +0100, Mauro Condarelli  wrote:


Hi,
I am struggling to make work my new Debian Squezze installation on my
workhorse. Problem is X setup and its interaction with desktops.

I have two VGAs:
* intel embedded in my i7 CPU
* external NVidia GTX770
Each of them drives 2 monitors for a grand total of 4.

I managed to have partial victory in the sense:
I can have dual monitor using *either* intel *or* nvidia
or I can have all four, but then gnome crashes somehow ("Oh no! Something
went wrong...") while X is ok. In the "working" cases xrandr dees only the
two active monitors. I also installed Xfce which works happily with the same
config where Gnome crashes, but shows only the nvidia monitors with mirroring
and xrandr does not work at all.

I am now writing from Win7 (with all monitors correctly working!) and thus I
have no access to actual files.

Can someone point me in the right direction, please?

Use at least Debian 8, for a start.

Bad interaction between multihead display amd desktops in debian squeeze

2015-11-01 Thread Mauro Condarelli


Hi,
I am struggling to make work my new Debian Squezze installation on my workhorse.
Problem is X setup and its interaction with desktops.

I have two VGAs:
* intel embedded in my i7 CPU
* external NVidia GTX770
Each of them drives 2 monitors for a grand total of 4.

I managed to have partial victory in the sense:
I can have dual monitor using *either* intel *or* nvidia
or I can have all four, but then gnome crashes somehow ("Oh no! Something went 
wrong...") while X is ok.
In the "working" cases xrandr dees only the two active monitors.
I also installed Xfce which works happily with the same config where Gnome 
crashes, but shows only the nvidia monitors with mirroring and xrandr does not 
work at all.

I am now writing from Win7 (with all monitors correctly working!) and thus I 
have no access to actual files.

Can someone point me in the right direction, please?

Mauro

Re: debian sid, kernel 3.8 and volume group not found.

2013-05-15 Thread Mauro

On 13 May 2013 01:53, Dick Thomas  wrote:

> have you tried adding the
>
> rootdelay=6
> to your kernel command line?
>
>
It works with rootdelay.
I need it in my desktop while in the laptop there's no need of rootdelay.

Re: debian sid, kernel 3.8 and volume group not found.

2013-05-12 Thread Mauro

I've not tried, I'll do.
But why there's no need to add rootdelay in the other machine?


On 13 May 2013 01:53, Dick Thomas  wrote:

> On 13 May 2013 00:25, Mauro  wrote:
> > It is already installed.
> >
> >
> > On 12 May 2013 15:25, Alan Greenberger  wrote:
> >>
> >> On 2013-05-11, Mauro  wrote:
> >> >
> >> > Yes I've did not mention that the machine where the new kernel does
> not
> >> > work has an amd64 processor.
> >> >
> >> >
> >> > On 11 May 2013 09:53, Anthony Campbell  wrote:
> >> >
> >> >> On 10 May 2013, Mauro wrote:
> >> >> >I have two pc, same distro, debian sid, same software, same
> >> >> configuration.
> >> >> >I'm using the new kernel 3.8.
> >> >> >In one pc the boot is ok, in the other I've volume group xxx not
> >> >> found,
> >> >> >I've noticed also a message like module microcode.ko not found.
> >> >> >Can you help me?
> >> >>
> >> >> I've noticed the same thing. Specifically, microcode does not load on
> >> >> my
> >> >> desktop machine, which has an AMD Athlon 64 processor. I tried with
> the
> >> >> AMD64 kernel as well, without success.
> >> >>
> >> >> On my Thinkpad, with an Intel processor, microcode does work but the
> >> >> tp_smapi module (battery charge control) does not load.
> >> >>
> >> >> I've removed this kernel from both machines.
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Anthony Campbell - a...@acampbell.org.uk
> >> >> http://www.acupuncturecourse.org.uk
> >> >> http://www.smashwords.com/profile.view/acampbell
> >> >> https://itunes.apple.com/ca/artist/anthony-campbell/id73235412
> >> >>
> >>
> >> Maybe install package amd64-microcode ?
> >>
> >>
> >> --
> >> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> >> with a subject of "unsubscribe". Trouble? Contact
> >> listmas...@lists.debian.org
> >> Archive: http://lists.debian.org/slrnkov61e.lib.alanjg@archduke.router
> >>
> >
> have you tried adding the
>
> rootdelay=6
> to your kernel command line?
>
> this is needed in newer kernels when booting
> http://www.debian.org/releases/stable/amd64/release-notes.en.txt
>
> http://about.me/dick.thomas
> http://www.dick-thomas.co.uk
> Blog: www.xpd259.co.uk
> G+:   www.google.com/profiles/xpd259
> gpg key: 98631051
>

Re: debian sid, kernel 3.8 and volume group not found.

2013-05-12 Thread Mauro

It is already installed.


On 12 May 2013 15:25, Alan Greenberger  wrote:

> On 2013-05-11, Mauro  wrote:
> >
> > Yes I've did not mention that the machine where the new kernel does not
> > work has an amd64 processor.
> >
> >
> > On 11 May 2013 09:53, Anthony Campbell  wrote:
> >
> >> On 10 May 2013, Mauro wrote:
> >> >I have two pc, same distro, debian sid, same software, same
> >> configuration.
> >> >I'm using the new kernel 3.8.
> >> >In one pc the boot is ok, in the other I've volume group xxx not
> >> found,
> >> >I've noticed also a message like module microcode.ko not found.
> >> >Can you help me?
> >>
> >> I've noticed the same thing. Specifically, microcode does not load on my
> >> desktop machine, which has an AMD Athlon 64 processor. I tried with the
> >> AMD64 kernel as well, without success.
> >>
> >> On my Thinkpad, with an Intel processor, microcode does work but the
> >> tp_smapi module (battery charge control) does not load.
> >>
> >> I've removed this kernel from both machines.
> >>
> >>
> >>
> >> --
> >> Anthony Campbell - a...@acampbell.org.uk
> >> http://www.acupuncturecourse.org.uk
> >> http://www.smashwords.com/profile.view/acampbell
> >> https://itunes.apple.com/ca/artist/anthony-campbell/id73235412
> >>
>
> Maybe install package amd64-microcode ?
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/slrnkov61e.lib.alanjg@archduke.router
>
>

Re: debian sid, kernel 3.8 and volume group not found.

2013-05-11 Thread Mauro

I've also noticed problems with network.


On 11 May 2013 12:45, Mauro  wrote:

> Yes I've did not mention that the machine where the new kernel does not
> work has an amd64 processor.
>
>
> On 11 May 2013 09:53, Anthony Campbell  wrote:
>
>> On 10 May 2013, Mauro wrote:
>> >I have two pc, same distro, debian sid, same software, same
>> configuration.
>> >I'm using the new kernel 3.8.
>> >In one pc the boot is ok, in the other I've volume group xxx not
>> found,
>> >I've noticed also a message like module microcode.ko not found.
>> >Can you help me?
>>
>> I've noticed the same thing. Specifically, microcode does not load on my
>> desktop machine, which has an AMD Athlon 64 processor. I tried with the
>> AMD64 kernel as well, without success.
>>
>> On my Thinkpad, with an Intel processor, microcode does work but the
>> tp_smapi module (battery charge control) does not load.
>>
>> I've removed this kernel from both machines.
>>
>>
>>
>> --
>> Anthony Campbell - a...@acampbell.org.uk
>> http://www.acupuncturecourse.org.uk
>> http://www.smashwords.com/profile.view/acampbell
>> https://itunes.apple.com/ca/artist/anthony-campbell/id73235412
>>
>>
>>
>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmas...@lists.debian.org
>> Archive: http://lists.debian.org/20130511075356.ga13...@acampbell.org.uk
>>
>>
>

Re: debian sid, kernel 3.8 and volume group not found.

2013-05-11 Thread Mauro

Yes I've did not mention that the machine where the new kernel does not
work has an amd64 processor.


On 11 May 2013 09:53, Anthony Campbell  wrote:

> On 10 May 2013, Mauro wrote:
> >I have two pc, same distro, debian sid, same software, same
> configuration.
> >I'm using the new kernel 3.8.
> >In one pc the boot is ok, in the other I've volume group xxx not
> found,
> >I've noticed also a message like module microcode.ko not found.
> >Can you help me?
>
> I've noticed the same thing. Specifically, microcode does not load on my
> desktop machine, which has an AMD Athlon 64 processor. I tried with the
> AMD64 kernel as well, without success.
>
> On my Thinkpad, with an Intel processor, microcode does work but the
> tp_smapi module (battery charge control) does not load.
>
> I've removed this kernel from both machines.
>
>
>
> --
> Anthony Campbell - a...@acampbell.org.uk
> http://www.acupuncturecourse.org.uk
> http://www.smashwords.com/profile.view/acampbell
> https://itunes.apple.com/ca/artist/anthony-campbell/id73235412
>
>
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/20130511075356.ga13...@acampbell.org.uk
>
>

debian sid, kernel 3.8 and volume group not found.

2013-05-10 Thread Mauro

I have two pc, same distro, debian sid, same software, same configuration.
I'm using the new kernel 3.8.
In one pc the boot is ok, in the other I've volume group xxx not found,
I've noticed also a message like module microcode.ko not found.
Can you help me?

LXC status on Wheezy

2013-02-22 Thread Jeremy MAURO

ebconf/Priority.pm line 24,  line 22.
Use of uninitialized value in numeric ge (>=) at 
/usr/share/perl5/Debconf/Priority.pm line 24,  line 28.

Setting up live-config-sysvinit (3.0.21-1) ...
update-rc.d: warning:  start runlevel arguments (none) do not match live 
Default-Start values (S)

Setting up live-config (3.0.21-1) ...
Setting up live-config-doc (3.0.21-1) ...
Setting up live-tools (3.0.18-1) ...
Setting up sudo (1.8.5p2-1) ...
Usage: live-debconfig
Usage: live-debconfig --debconfig|--debconfig=SCRIPT1,SCRIPT2,SCRIPT3
Usage: live-debconfig --nodebconfig|--nodebconfig=SCRIPT1,SCRIPT2,SCRIPT3
Usage: live-debconfig --debug
debconf: unable to initialize frontend:
debconf: (Can't locate Debconf/FrontEnd/.pm in @INC (@INC contains: 
/etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 
/usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/per

l/5.14 /usr/local/lib/site_perl .) at (eval 26) line 2.)
debconf: falling back to frontend: Noninteractive
Use of uninitialized value in numeric ge (>=) at 
/usr/share/perl5/Debconf/Priority.pm line 24,  line 4.

debconf: unable to initialize frontend:
debconf: (Can't locate Debconf/FrontEnd/.pm in @INC (@INC contains: 
/etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 
/usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/per

l/5.14 /usr/local/lib/site_perl .) at (eval 26) line 2.)
debconf: falling back to frontend: Noninteractive
Shadow passwords are now on.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
'debian' template installed
'myfirstcontainer' created



--
Cordialement,
Jeremy MAURO


Jeremy MAURO (jma...@antidot.net) - Ingénieur Systémes et Réseaux
Antidot - Solutions de recherche d'information
29 avenue Jean Monnet, 13410 LAMBESC (FRANCE)
Tel: (+33) 4 42 63 67 90 / Fax: (+33) 4 42 28 61 03

Re: need lenny.

2012-12-08 Thread Mauro

On 8 December 2012 17:37, Rick Thomas  wrote:
>
> On Dec 8, 2012, at 7:32 AM, Mauro wrote:
>
>>>
>>>
>>> Have you tried aptitude instead of apt-get?
>>>
>>
>> yes, same error.
>
>
> Just a guess, but take a look at backports and see if you can install a more
> modern version of apt or aptitude.
>
> FWIW My lenny box has aptitude version "0.4.11.11-1~lenny2".

now works, perhaps a problem of my dns provider.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0vogqv4-a6fgfwtfvnt9wh6znmsznyhimb5he-0hbp...@mail.gmail.com

Re: need lenny.

2012-12-08 Thread Mauro

On 8 December 2012 16:09, Rick Thomas  wrote:
>
> On Dec 8, 2012, at 5:14 AM, Andrei POPESCU wrote:
>
>> On Sb, 08 dec 12, 12:46:23, Mauro wrote:
>>>
>>> W: Failed to fetch
>>> http://archive.debian.org/debian/dists/lenny/main/binary-amd64/Packages
>>> 302 Moved [IP: 193.62.202.28 80]
>>
>>
>> Hmm, your apt is trying to download the uncompressed Packages file,
>> which is actually not available (anymore?) -- even though mentioned in
>> the Release file -- and doesn't fall back to the compressed Packages
>> files.
>>
>> You should check your apt configurations for any overrides.
>>
>> Kind regards,
>> Andrei
>> --
>> Offtopic discussions among Debian users and developers:
>> http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
>
>
>
> Have you tried aptitude instead of apt-get?
>

yes, same error.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0xyktpev92esyqwzgsah_aba9gpo2v692xrqywctkn...@mail.gmail.com

Re: need lenny.

2012-12-08 Thread Mauro

On 8 December 2012 13:01, Rares Aioanei  wrote:
> On 12/08/12 13:46, Mauro wrote:
>>
>> My sources list:
>>
>> deb http://archive.debian.org/debian/ lenny main contrib non-free
>> deb http://archive.debian.org/backports.org/ lenny-backports main contrib
>> deb http://archive.debian.org/debian-security/ lenny/updates main contrib
>> deb http://archive.debian.org/debian-volatile/ lenny/volatile main contrib
>>
> [...]
> Is there a valid reason for sticking to Lenny? It's unsupported, you know.

I still have some servers with lenny and I need to install some packages.
I knew that archive.debian.org  was established to support old
distributions but it seems does not work.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0XwfYFDKwHwqeQLgOkwKQj+0=qxw_x7+84w+_rgyon...@mail.gmail.com

Re: ntpd crashes.

2012-09-26 Thread Mauro

On 26 September 2012 15:57, lee wrote:
>
> What's in the configuration of your NTP daemon? Perhaps there's
> something wrong with that.

Here is ntp.conf

statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example

# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
# pick a different set every time it starts up. Please consider joining the
# pool:
server 0.debian.pool.ntp.org iburst
server 1.debian.pool.ntp.org iburst
server 2.debian.pool.ntp.org iburst
server 3.debian.pool.ntp.org iburst

restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery

# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust

# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines. Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAE17a0WRo=yk-skgmydwcep5xs_k-jbj1+tkmihen1f7dro...@mail.gmail.com

Re: ntpd crashes.

2012-09-25 Thread Mauro

On 22 September 2012 15:51, Camaleón  wrote:
> El 2012-09-21 a las 22:13 +0200, Mauro escribió:
>
> (resending to the list)
>
>> On 21 September 2012 16:30, Camaleón  wrote:
>> > On Fri, 21 Sep 2012 12:05:01 +0200, Mauro wrote:
>> >
>> >> On 20 September 2012 22:20, Mauro  wrote:
>> >>> On 20 September 2012 16:56, John Hasler  wrote:
>> >>>> Someone who Stefan failed to identify wrote:
>> >>>>> ...ntpd crashes on my server.  Time jumps forward one hour every time
>> >>>>> this has happened.
>> >>>>
>> >>>> I doubt ntpd is crashing.  Most likely something else is jumping the
>> >>>> system clock and ntpd is behaving as designed and exiting when it sees
>> >>>> a one hour error.  Shut down ntpd, set the clock correctly, and wait.
>> >>>> I suspect that eventually you'll see the clock jump even without ntpd
>> >>>> running.
>> >>>
>> >>> Yes that is.
>> >>> I have no cron jobs at all, I only have xen and heartbeat + pacemaker
>> >>> on my two nodes and no processes that set the system clock. The clock
>> >>> jumps ahead of one or two hours and I don't know why. Perhaps some
>> >>> kernel bug?
>> >
>> > ntpd should avoid the clock going that forward and keep it disciplined.
>> >
>> >> It seems not ntp problem but a kernel bug:
>> >>
>> >> http://my.opera.com/marcomarongiu/blog/2010/08/18/debugging-ntp-again-part-4-and-last
>> >
>> > You can try the mentioned work-around and see if that works for you.
>> >
>> > Anyway, if that's the case, you should experience the same with different
>> > ntp daemons and not just with ntpd :-?
>>
>> I've experienced the same problem also with openntp.
>
> That makes more sense.
>
> Anyway, no NTP daemon should crash because of skewed time; one thing is
> that it refushes to sync (which can be fine, and should log this fact
> so the admin can make the proper measures) but a different thing is
> completely killing the service.
>
>> Now I'm back with ntp using the workaround mentioned, hope it works.
>
> Perfect, tell us how it went.

PROBLEM!!
System clock is gone one hour ahead, ntp stops to run with no messages
logs and I now I'm in trouble because I don't know what to do.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0U=bzc_YjSHJ=sglhgvgeswv1rk+kkbrkexxm-grz-...@mail.gmail.com

Re: IA64 or AMD64?

2012-09-21 Thread Mauro

On 20 September 2012 23:04, Stan Hoeppner  wrote:

> You are either:
>
> 1.  Horribly lazy
> 2.  Incompetent

Ok, thank you for answer, have a good day ;-)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0xsuxv5xfr9fzxxyjcahr+ragyqom8z6y2daqjspxb...@mail.gmail.com

Re: ntpd crashes.

2012-09-21 Thread Mauro

On 20 September 2012 22:20, Mauro  wrote:
> On 20 September 2012 16:56, John Hasler  wrote:
>> Someone who Stefan failed to identify wrote:
>>> ...ntpd crashes on my server.  Time jumps forward one hour every time
>>> this has happened.
>>
>> I doubt ntpd is crashing.  Most likely something else is jumping the
>> system clock and ntpd is behaving as designed and exiting when it sees a
>> one hour error.  Shut down ntpd, set the clock correctly, and wait.  I
>> suspect that eventually you'll see the clock jump even without ntpd
>> running.
>> --
>> John Hasler
>
> Yes that is.
> I have no cron jobs at all, I only have xen and heartbeat + pacemaker
> on my two nodes and no processes that set the system clock.
> The clock jumps ahead of one or two hours and I don't know why.
> Perhaps some kernel bug?

It seems not ntp problem but a kernel bug:

http://my.opera.com/marcomarongiu/blog/2010/08/18/debugging-ntp-again-part-4-and-last


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0WcpqaoSK6ZJsT0MTmLHmPyqOH=tjeiv0bzyqx9yu1...@mail.gmail.com

Re: ntpd crashes.

2012-09-20 Thread Mauro

On 20 September 2012 16:56, John Hasler  wrote:
> Someone who Stefan failed to identify wrote:
>> ...ntpd crashes on my server.  Time jumps forward one hour every time
>> this has happened.
>
> I doubt ntpd is crashing.  Most likely something else is jumping the
> system clock and ntpd is behaving as designed and exiting when it sees a
> one hour error.  Shut down ntpd, set the clock correctly, and wait.  I
> suspect that eventually you'll see the clock jump even without ntpd
> running.
> --
> John Hasler

Yes that is.
I have no cron jobs at all, I only have xen and heartbeat + pacemaker
on my two nodes and no processes that set the system clock.
The clock jumps ahead of one or two hours and I don't know why.
Perhaps some kernel bug?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0UfLsG9MjRYstubqqeYwSacaybwjhuMg=G=k2av4cw...@mail.gmail.com

Re: IA64 or AMD64?

2012-09-20 Thread Mauro

On 20 September 2012 09:53, Markus Schönhaber
 wrote:
> 20.09.2012 09:44, Mauro:
>
>> I have a HP proliant DL580 G5 server with 4 Intel(R) Xeon(R) CPU E7330
>>  @ 2.40GHz processors.
>> What architecture port I've to install, IA64 or AMD64?
>
> AMD64.
> IA64 is for Itanium processors. You'd know if you had one.

Ok, thank you, I have only Xeon processors.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0VDG2u=5pmenbrwaag_h31trj667a2gxc6w1jtog1v...@mail.gmail.com

IA64 or AMD64?

2012-09-20 Thread Mauro

Hello.
I have a HP proliant DL580 G5 server with 4 Intel(R) Xeon(R) CPU E7330
 @ 2.40GHz processors.
What architecture port I've to install, IA64 or AMD64?
Thank you.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0Xz1bCHKFMW8jCa=eTTvtZ0Y2_-srZUATHoNGGYWoW=n...@mail.gmail.com

Re: ntpd crashes.

2012-09-18 Thread Mauro

On 18 September 2012 15:51, Stefan Monnier  wrote:
>> with ntpd crashes on my server.  Time jumps forward one hour every time
>> this has happened.  However I'm not convinced it's the hardware causing
>
> Sounds like something is causing the one-hour jump, and that in turns
> causes ntpd to go bonkers.
> As for what causes this jump, I don't know.  Some cron job, maybe?

No I have no cron jobs.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0Vd0h2jMPSco2t9=m1gaa7zqp0nnvrcoggabccadus...@mail.gmail.com

Re: ntpd crashes.

2012-09-18 Thread Mauro

On 17 September 2012 21:47, Bob Proulx  wrote:
> Mauro wrote:
>> I think ntpd crashes are because my server lost time.
>> I have ntpd in two server, now I've seen that in one of these ntp
>> crashes and the time of the server is 1 hour forward.
>> That's why ntp crashes: server time goes 1 hour forward and ntp can't
>> resynchronize so it crashes.
>
> Is it really crashing or is this intended behavior.  The ntpd is
> documented with:
>
>-g Normally, ntpd exits with a message to the system log if the
>   offset exceeds the panic threshold, which is 1000 s by
>   default.  This option allows the time to be set to any value
>   without restriction; however, this can happen only once.  If
>   the threshold is exceeded after that, ntpd will exit with a
>   message to the system log.  This option can be used with the
>   -q and -x options.
>
> Therefore if the time is one hour forward that will be greater than
> the threshold 1000 seconds and ntp will exit.  As described this is so
> that the admin may adjust the time manually to some specific value
> (for whatever reason, testing, whatever) and ntpd will get out of the
> way.
>
> It also says that ntpd will log a message to the system log when this
> condition occurs.

No message logs.

>
> I think it is possible that you have some additional process that is
> setting the clock and this is jumping the time forward one hour and
> because the time is jumped forward one hour that exceeds the ntpd
> panic threshold and therefore ntpd decides that it should get out of
> the way and it intentionally exits.  This intentional behavior is
> quite a bit different from a crash.

I have no additional processes.
Now I'm trying openntp.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0WNw_a=vtptnu3mh4_kd_zx6kays8qorsumyivqfyt...@mail.gmail.com

Re: ntpd crashes.

2012-09-18 Thread Mauro

On 17 September 2012 19:33, Gerald Turner  wrote:
> Mauro  writes:
>> I think ntpd crashes are because my server lost time.
>> I have ntpd in two server, now I've seen that in one of these ntp
>> crashes and the time of the server is 1 hour forward.
>> That's why ntp crashes: server time goes 1 hour forward and ntp can't
>> resynchronize so it crashes.
>> Now I don't know why my server time goes 1 hour forward.
>> Hwclock --debug says that the time is correct, it is set on UTC, so
>> why sometimes it goes forward?
>> Perhaps a problem in the cmos battery?
>
> Hi Mauro, I find this interesting because I have seen the same behavior
> with ntpd crashes on my server.  Time jumps forward one hour every time
> this has happened.  However I'm not convinced it's the hardware causing
> ntpd to crash.  I don't understand why ntpd process exiting silently
> would allow the jump either, I would expect it to drift a few seconds
> over time, but one hour exactly every time?!  Even with monit in place,
> within the two minute window that polling takes place and ntpd has
> crashed, before monit automatically starts ntpd, time is forward an
> hour.

I'm trying openntp now, I hope it works.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0v5ughbzgwxraar4dsmktrv9hagt8dzaewhr9iw+ss...@mail.gmail.com

Re: ntpd crashes.

2012-09-16 Thread Mauro

On 16 September 2012 17:46, Camaleón  wrote:

> Try by appending the "-x" argument at the "/etc/default/ntp" file from
> the server that crashes. If your thoughs are correct, this could mitigate
> the time difference.

I've uninstalled ntp and installed openntp from squeeze backports.
I hope this works.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0w+s79rdjqatwrsyhou2faysmbrl7z-1kvn6e11hsc...@mail.gmail.com

Re: ntpd crashes.

2012-09-15 Thread Mauro

I think ntpd crashes are because my server lost time.
I have ntpd in two server, now I've seen that in one of these ntp
crashes and the time of the server is 1 hour forward.
That's why ntp crashes: server time goes 1 hour forward and ntp can't
resynchronize so it crashes.
Now I don't know why my server time goes 1 hour forward.
Hwclock --debug says that the time is correct, it is set on UTC, so
why sometimes it goes forward?
Perhaps a problem in the cmos battery?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0WWXjsw07n_YN1kjTLyWGHmC=2ctqxbbxkwdgizbt_...@mail.gmail.com

Re: ntpd crashes.

2012-09-11 Thread Mauro

On 11 September 2012 17:32, Camaleón  wrote:
> On Tue, 11 Sep 2012 16:53:43 +0200, Mauro wrote:
>
>> On 11 September 2012 16:48, Camaleón  wrote:
>>> On Tue, 11 Sep 2012 12:54:59 +0200, Mauro wrote:
>>>
>>>> On 11 September 2012 10:58, Chris Davies 
>>>> wrote:
>>>>> Mauro  wrote:
>>>>>> I think the best solution is uninstall ntp and use ntpdate with
>>>>>> cron.
>>>>>
>>>>> Not a particularly good solution for a number of reasons. Mainly,
>>>>> though, you need to be aware that ntpdate is quite likely to jump the
>>>>> clock.
>>>>
>>>> If ntp stops running with apparently no reasons I don't know what else
>>>> I can do. I need to have time synchronized between my servers.
>>>
>>> You can try a different approach: do not run ntpd as daemon but using
>>> cron and see how it goes :-?
>>
>> What's the difference of running ntpdate instead ntp with cron?
>
> Well, AFAIK they're different packages for different purposes, other than
> that, I can't tell. But if you search for a full replacement of "ntp"
> functionalities (client/server) you can look at "openntpd" and "chrony".

openntpd is not in debian squeeze, I'm thinking to replace ntpd with chrony.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0VkBDfFeMU4hkq397VOcVvj0CjE_=qcaqg1aa4ffdg...@mail.gmail.com

Re: ntpd crashes.

2012-09-11 Thread Mauro

On 11 September 2012 13:03, Ralf Mardorf  wrote:
> On Tue, 2012-09-11 at 12:54 +0200, Mauro wrote:
>> On 11 September 2012 10:58, Chris Davies  wrote:
>> > Mauro  wrote:
>> >> I think the best solution is uninstall ntp and use ntpdate with cron.
>> >
>> > Not a particularly good solution for a number of reasons. Mainly, though,
>> > you need to be aware that ntpdate is quite likely to jump the clock.
>>
>> If ntp stops running with apparently no reasons I don't know what else I can 
>> do.
>> I need to have time synchronized between my servers.
>
> I'm a ntpdate and sntp user. I never had issues using ntpdate and sntp
> manually.

sntp is in debian packages?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0va4o88rusg2vecbxdcfve34huttmjuv2pfrlv4hjp...@mail.gmail.com

Re: ntpd crashes.

2012-09-11 Thread Mauro

On 11 September 2012 16:48, Camaleón  wrote:
> On Tue, 11 Sep 2012 12:54:59 +0200, Mauro wrote:
>
>> On 11 September 2012 10:58, Chris Davies 
>> wrote:
>>> Mauro  wrote:
>>>> I think the best solution is uninstall ntp and use ntpdate with cron.
>>>
>>> Not a particularly good solution for a number of reasons. Mainly,
>>> though, you need to be aware that ntpdate is quite likely to jump the
>>> clock.
>>
>> If ntp stops running with apparently no reasons I don't know what else I
>> can do. I need to have time synchronized between my servers.
>
> You can try a different approach: do not run ntpd as daemon but using
> cron and see how it goes :-?

What's the difference of running ntpdate instead ntp with cron?


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0UAchE2ZQfMPgFp0vy5QTgoPjHs=q5_sfkzejszoar...@mail.gmail.com

Re: ntpd crashes.

2012-09-11 Thread Mauro

On 11 September 2012 10:58, Chris Davies  wrote:
> Mauro  wrote:
>> I think the best solution is uninstall ntp and use ntpdate with cron.
>
> Not a particularly good solution for a number of reasons. Mainly, though,
> you need to be aware that ntpdate is quite likely to jump the clock.

If ntp stops running with apparently no reasons I don't know what else I can do.
I need to have time synchronized between my servers.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0xeit6qthg3ewn+uhegu73p71pvc-ns6hqb1dvjerz...@mail.gmail.com

Re: ntpd crashes.

2012-09-10 Thread Mauro

On 11 September 2012 00:08, Gerald Turner  wrote:
> Camaleón  writes:
>
>> On Sat, 08 Sep 2012 13:31:16 +0200, Mauro wrote:
>>
>>> Hello I've two server with debian squeeze and in cluster with
>>> heartbeat+pacemaker.
>>> They run ntpd for time synchronize.
>>> I've noticed some ntpd crashes in random days and random hour.
>>
>> Does restarting the service works?
>>
>>> Logs don't say why.
>>> Can you suggest what can I do to know the reasons for the crash. Thank
>>> you.
>>
>> Mmmm... there's a bug report¹ to request ntpd debugging flag is turned
>> on (which I think is a must) but in the meantime I guess you will have
>> to recompile the package from Debian sources and toggle this parameter
>> on if you want to get an insightful trace.
>>
>> ¹http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643954
>
> I too get random crashes with ntpd in squeeze (1:4.2.6.p2+dfsg-1+b1) on
> a Xen dom0 host.  Frequency is about every two months.  It prompted me
> to install monit² which has nice support for probing NTP protocol and
> restarting the service automatically - not a perfect solution since the
> clock jumps forward an hour during the breakage, upsetting lots of
> software (dovecot and RRD graphs mostly).

Exactly.
I too have Xen dom0 hosts where ntp crashes.
I think the best solution is uninstall ntp and use ntpdate with cron.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0WZG7K1hKWEWdOPyVwXXZmPt18j=6v1wr8w5tqjthp...@mail.gmail.com

Re: debian sid bug?

2012-08-28 Thread Mauro

On 27 August 2012 23:44, Bob Proulx  wrote:
> Ralf Mardorf wrote:
>> At Joe and Bob. Do you use multi arch? It seems to be a problem for
>> multi arch.
>
> I do because multiarch is now a capability of dpkg and I use dpkg.
> But I haven't used it explicitly.  I am running a pure 64-bit amd64
> installation without any explicit ia32 packages installated.
>
> I ran reportbug on libqt4-sql-sqlite and it produced this package tree
> on my system:
>
>   Versions of packages libqt4-sql-sqlite depends on:
>   ii  libc6  2.13-35
>   ii  libgcc11:4.7.1-7
>   ii  libqt4-sql 4:4.8.2+dfsg-1
>   ii  libqtcore4 4:4.8.2+dfsg-1
>   ii  libsqlite3-0   3.7.13-1
>   ii  libstdc++6 4.7.1-7
>   ii  multiarch-support  2.13-35
>
> Notice that the versions above are "+dfsg-1" versions and not "+b1"
> versions.  The original poster was having problems with "+b1" versions
> which have been replaced with the newer "+dfsg-1" versions.
>
> If you are having problems with multiarch it would be informative to
> me if you would explain the problem.  I don't see any 32-bit libs in
> any of the above and so don't see how it would affect things.  I think
> it more likely that an out of date mirror or an out of date package
> list is the problem.
>
> However "+b1" is a binary NMU version and so perhaps someone did a
> binary NMU but inconsistently across the architectures?  That is
> certainly possible.  And would explain why it is working on amd64 just
> fine but broken on another one.
>
> The PTS shows this package very recently uploaded and built.  It may
> not have propagated everywhere yet.  The build failed on ia64.
>
>   http://packages.qa.debian.org/q/qt4-x11.html

I've found the solution here:

http://aptosid.com/index.php?name=PNphpBB2&file=viewtopic&p=15393


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0xs6jmnwjzgyexu9ner2mfrqt-ee2m9ygtfc1dab6+...@mail.gmail.com

debian sid bug?

2012-08-27 Thread Mauro

Hello.
I'm using debian sid.
When I try to update the system I have the error:

dpkg: dependency problems prevent configuration of libqt4-sql-sqlite:amd64:
 libqt4-sql-sqlite:amd64 depends on libqtcore4 (= 4:4.8.2-2+b1); however:
  Version of libqtcore4:amd64 on system is 4:4.8.2+dfsg-1

Is it still an unresolved bug?
Do you have the same problem on debian sid?
Thank you.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0xvrz1bqy1t15uxxzu9bxaqyvunsahgae1-udt5lhx...@mail.gmail.com

Re: continuous reboots in a two nodes cluster with heartbeat and pacemaker.

2012-08-19 Thread Mauro

On 19 August 2012 02:32, Stan Hoeppner  wrote:
> On 8/18/2012 6:36 AM, Mauro wrote:
>
>> I've upgraded ram from 32 to 64G.
>
> Did the reboots occur before doing this?
>
>> I've reinstalled all simms.
>
> DIMMs.  SIMMs haven't been used for over a decade.  But the fact you
> mentioned SIMMs tells me you've been at this game a while.
>
>> The bios reports no ram problems.
>
> It may not.
>
>> Also other server are upgraded to 64G.
>
> Are all the DIMMs fully buffered ECC DDR2-667?  If you added unbuffered
> ECC DDR2-667 DIMMs to go from 32GB to 64GB, the BIOS may no throw any
> errors, but you'd see things like random reboots, random lockups, kernel
> errors, processes crashing, etc.
>
> Do these two machines have all four processors and all four memory
> cartridges installed, or only two of each?
>
>> Bugged ram is on both servers? Strange to me.
>
> It's probably not bad RAM, but it seems possible that you may have used
> unregistered DIMMs when you upgraded to 64GB.  Again, the BIOS may not
> balk at this, and the combo might seem to work until the memory
> subsystem is sufficiently exercised.


Thank you for your replies.
I'll check the DIMMs and tell you.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0xg6+w_gkgev0pj+nmgqtees1+qecenwtdypta0twm...@mail.gmail.com

Re: continuous reboots in a two nodes cluster with heartbeat and pacemaker.

2012-08-18 Thread Mauro

On 17 August 2012 09:53, Stan Hoeppner  wrote:


> I'd be thoroughly inspecting the power circuits feeding those servers at
> this point.  Do you have the machines set to automatically power back on
> after power loss?  If you do, switch that mode so they stay off after AC
> power loss.  That should confirm whether the problem is total loss of AC
> voltage or a severely deep sag.

Is that setting in the bios?


> If the problem is a less severe sag, however, this test won't isolate
> the problem.  For that you must dig into the UPS monitoring interface.
> If you don't have a UPS, you'll have to put a tap on the AC circuit and
> monitor the voltage.  This will require specialized equipment, as it
> must be able to log the sag.  Some of the nicer Fluke meters can log the
> lowest voltage, but probably can't tell you the time of day when the sag
> occurs.  Thus, you'll need to highly trained electrician with the proper
> equipment.
>
> This could also be a thermal issue.  Do you have hardware monitoring
> installed and properly configured?  The 'sensors' package?  Over temp
> conditions will often cause random reboots.  Do the boxes have plenty of
> zero restriction cool airflow?  Less than 25 Celsius intake air temperature?

I have others HP server of the same type, some with linux and others
with windows.
Thay are all in the same room so if it is a temperature problem I
think that also other servers can have the same problem but it is not
the case.
Only mine reboots.

>
> The odds of having defective hardware in two HP servers causing random
> reboots in both machines is extremely low, though possible.  If this is
> the case it's a design flaw, not simply two defective parts.
>
> It's also possible you have the wrong memory installed.  Can you provide
> the specs on all DIMMs installed in both machines?  Did all of the
> memory come preinstalled from HP?  Is it HP memory or aftermarket memory
> from Kingston, Crucial, etc?

I've upgraded ram from 32 to 64G.
I've reinstalled all simms.
The bios reports no ram problems.
Also other server are upgraded to 64G.
Reboots are sometime on node1 and sometime on node2.
Bugged ram is on both servers? Strange to me.
Other server don't reboot.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0vaxxyarztogt6i4xkae-n9cy7d07nkzvpkwdkq50n...@mail.gmail.com

Re: continuous reboots in a two nodes cluster with heartbeat and pacemaker.

2012-08-16 Thread Mauro

On 14 August 2012 08:24, Mauro  wrote:
> On 13 August 2012 22:58, Stan Hoeppner  wrote:
>
>> That being the case I'd suspect something other than server hardware.
>> To be sure, manually remove one node from the cluster and see how long
>> the remaining node runs without rebooting.  If it doesn't reboot at all,
>> that eliminates hardware as the fault point.
>
> good idea, I do it now.

I've done what you have suggested.
It seems that the node reboots without reason.
It is like it is powered off, in fact in the boolog I see that the
journal filesystem is recovered.
It seems very strange to me, perhaps ram bugged?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0V39QMbTnBRGESazYm=f8lrq6c5bp4wk7s6m8etbeb...@mail.gmail.com

ssl-cert-snakeoil certificate.

2012-08-16 Thread Mauro

Hello.
I've installed ssl-cert package and I've found between others a
ssl-cert-snakeoil.pem and ssl-cert.snakeoil.key that I use for my
https servers.
Is that a sort of default certificate?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0wvz68dmpb4kg8cpqy7m+aqcuma9vjuf7jrz210giw...@mail.gmail.com

Re: continuous reboots in a two nodes cluster with heartbeat and pacemaker.

2012-08-13 Thread Mauro

On 13 August 2012 22:58, Stan Hoeppner  wrote:

> That being the case I'd suspect something other than server hardware.
> To be sure, manually remove one node from the cluster and see how long
> the remaining node runs without rebooting.  If it doesn't reboot at all,
> that eliminates hardware as the fault point.

good idea, I do it now.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0VdXgugBaOAdBTR3Pk8GfOS7bVUgsoKJVTdJ=sfwrr...@mail.gmail.com

Re: continuous reboots in a two nodes cluster with heartbeat and pacemaker.

2012-08-13 Thread Mauro

>
> Are these controlled shutdowns?  Or are these hardware crash/reboots
> that are occurring?
>
> If the former you should see syslog entries for the shutdown sequence.
> If the latter, you won't see anything in the logs.  This would suggest
> you've got a hardware problem, and not related to faulty NICs or switches.
>
> What kind of UPS are these machines powered from?  Have you checked the
> UPS and verified they are functioning properly?  If you have a power
> even and the UPS drop the load, the machines will reboot without a hint
> in the logs as to what caused the reboot.
>
> Finally, what servers are theses?  Dell/HP/IBM or whitebox?  Memory
> mismatch or simply bad memory can cause inexplicable reboots.  If the
> machines are decent quality, they BIOS should log such events.

Servers are Hp proliant DL580G5.
I'm afraid that I have hardware problems :-(
The strange thing is that happens alternately in both nodes.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0uuex0io7pcqbo+wo2twnzghassbpwphbymolddrze...@mail.gmail.com

Re: continuous reboots in a two nodes cluster with heartbeat and pacemaker.

2012-08-12 Thread Mauro

On 12 August 2012 20:39, Stan Hoeppner  wrote:
> On 8/12/2012 4:44 AM, Mauro wrote:
>> On 11 August 2012 19:23, Stan Hoeppner  wrote:
>>> On 8/11/2012 8:59 AM, Mauro wrote:
>>>> Hello, I'm experiencing continuous reboots of my two nodes in a
>>>> heartbeat+pacemaker cluster.
>>>> Reboots are random, one day they happen one other day not, sometime
>>>> for 7 days they don't happen, sometimes they happen at night.
>>>> They happen at random days and random time.
>>>> Nodes are connected to a Cisco 3570 switch and a SAN storage system.
>>>> Perhaps there is a misconfiguration in the interfaces?
>>>> Here is my interfaces file:
>>> 
>>>
>>>
>>>> Do you think there are some errors?
>>>
>>> To determine that you need to look at your logs files, not your config
>>> files.  If the nodes are rebooting due to fencing it will be logged
>>> somewhere, as should the underlying network errors that cause the fence
>>> to close.
>>
>> Yes, I look at my logs but the only thing I see is that node 1 fence
>> node 2 or node 2 fence node 1 because one node doesn't see other node,
>> but I don't understard what is the problem, if it is a problem of my
>> NIC or other.
>
> Is there more than one set of these in any dmes files on either host:
>
> Jul 26 00:38:26 [host] kernel: e100 :00:0d.0: eth0: NIC Link is Down
> Jul 26 00:38:28 [host] kernel: e100 :00:0d.0: eth0: NIC Link is Up
> 100 Mbps Full Duplex

No, any link down in any log file :-(
I really don't understand why the reboots :-(

> If so it may indicate a flaky NIC or switch port, possibly a bad patch
> cable.  Is there a switch between the hosts or a cross over cable?

There is a cisco 3570 switch.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0U8D95r2qZT=rmHWQui7J0=p95vqk9ibkmuPDR6Kzgu=g...@mail.gmail.com

Re: continuous reboots in a two nodes cluster with heartbeat and pacemaker.

2012-08-12 Thread Mauro

On 11 August 2012 19:23, Stan Hoeppner  wrote:
> On 8/11/2012 8:59 AM, Mauro wrote:
>> Hello, I'm experiencing continuous reboots of my two nodes in a
>> heartbeat+pacemaker cluster.
>> Reboots are random, one day they happen one other day not, sometime
>> for 7 days they don't happen, sometimes they happen at night.
>> They happen at random days and random time.
>> Nodes are connected to a Cisco 3570 switch and a SAN storage system.
>> Perhaps there is a misconfiguration in the interfaces?
>> Here is my interfaces file:
> 
>
>
>> Do you think there are some errors?
>
> To determine that you need to look at your logs files, not your config
> files.  If the nodes are rebooting due to fencing it will be logged
> somewhere, as should the underlying network errors that cause the fence
> to close.

Yes, I look at my logs but the only thing I see is that node 1 fence
node 2 or node 2 fence node 1 because one node doesn't see other node,
but I don't understard what is the problem, if it is a problem of my
NIC or other.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0X7N3WGOyH=bjtds4K28BYiKoSvpwMY=JQ=3w7mvjn...@mail.gmail.com

continuous reboots in a two nodes cluster with heartbeat and pacemaker.

2012-08-11 Thread Mauro

Hello, I'm experiencing continuous reboots of my two nodes in a
heartbeat+pacemaker cluster.
Reboots are random, one day they happen one other day not, sometime
for 7 days they don't happen, sometimes they happen at night.
They happen at random days and random time.
Nodes are connected to a Cisco 3570 switch and a SAN storage system.
Perhaps there is a misconfiguration in the interfaces?
Here is my interfaces file:

#
# XEN VLAN CONFIGURATION
#

# BACKEND MANAGEMENT VIRTUAL INFRASTRUCTURE - VLAN ID 118 - PH. IFACE eth0

auto eth0.118
iface eth0.118 inet static
address 192.168.244.10
netmask 255.255.255.0
broadcast 192.168.244.255
gateway 192.168.244.1
vlan_raw_device eth0


# DMZ INTERNET VISIT-CAGLIARI - VLAN ID 109 - PH. IFACE eth1

auto eth1.109

auto xenbr.109
iface xenbr.109 inet manual
bridge_ports eth1.109
bridge_maxwait 0

# DMZ INTERNET - VLAN ID 111 - PH. IFACE eth1

auto eth1.111

auto xenbr.111
iface xenbr.111 inet manual
bridge_ports eth1.111
bridge_maxwait 0

# DMZ INTRANET - VLAN ID 112 - PH. IFACE eth1

auto eth1.112

auto xenbr.112
iface xenbr.112 inet manual
bridge_ports eth1.112
bridge_maxwait 0

# BACKEND APPLICATION INTERNET - VLAN ID 113 - PH. IFACE eth2

auto eth2.113

auto xenbr.113
iface xenbr.113 inet manual
bridge_ports eth2.113
bridge_maxwait 0

# BACKEND APPLICATION INTRANET - VLAN ID 114 - PH. IFACE eth2

auto eth2.114

auto xenbr.114
iface xenbr.114 inet manual
bridge_ports eth2.114
bridge_maxwait 0

# BACKEND DATABASE INTERNET - VLAN ID 115 - PH. IFACE eth2

uto eth2.115

auto xenbr.115
iface xenbr.115 inet manual
bridge_ports eth2.115
bridge_maxwait 0

# BACKEND DATABASE INTRANET - VLAN ID 116 - PH. IFACE eth2

auto eth2.116

auto xenbr.116
iface xenbr.116 inet manual
bridge_ports eth2.116
bridge_maxwait 0

# BACKEND AUTHENTICATION/AUTHORIZATION - VLAN ID 117 - PH. IFACE eth2

auto eth2.117

auto xenbr.117
iface xenbr.117 inet manual
bridge_ports eth2.117
bridge_maxwait 0

# BACKEND BACKUP - VLAN ID 119 - PH. IFACE eth3

auto eth3.119

auto xenbr.119
iface xenbr.119 inet manual
bridge_ports eth3.119
bridge_maxwait 0
bridge_fd 0

# LOCAL XEN POOL NETWORKS
#

# LIVE MIGRATION - VLAN ID 2001 - PH. IFACE eth0

auto eth0.2001
auto eth3.2001

iface eth0.2001 inet manual
vlan_raw_device eth0

iface eth3.2001 inet manual
vlan_raw_device eth3

auto bond.2001

iface bond.2001 inet static
address 10.1.0.1
netmask 255.255.255.0
bond-mode active-backup
slaves eth0.2001 eth3.2001
bond-miimon 100

# CLUSTER DOM0 - VLAN ID 2002 - PH. IFACE eth0/3

auto eth0.2002
iface eth0.2002 inet manual
vlan_raw_device eth0

auto eth3.2002
iface eth3.2002 inet manual
vlan_raw_device eth3

auto bond.2002
iface bond.2002 inet static
address 10.2.0.1
netmask 255.255.255.0
bond-mode active-backup
slaves eth0.2002 eth3.2002
bond-miimon 100


# CLUSTER WEB-INTERNET - VLAN ID 2003 - PH. IFACE eth0/3

auto eth0.2003

auto eth3.2003

iface eth0.2003 inet manual
vlan_raw_device eth0

iface eth3.2003 inet manual
vlan_raw_device eth3

auto bond.2003
iface bond.2003 inet manual
bond-mode active-backup
slaves eth0.2003 eth3.2003
bond-miimon 100

auto xenbr.2003
iface xenbr.2003 inet manual
bridge_ports bond.2003
bridge_maxwait 0
bridge_fd 0


# CLUSTER WEB-INTRANET - VLAN ID 2004 - PH. IFACE eth0/3

auto eth0.2004

auto eth3.2004

iface eth0.2004 inet manual
vlan_raw_device eth0

iface eth3.2004 inet manual
vlan_raw_device eth3

auto bond.2004
iface bond.2004 inet manual
bond-mode active-backup
slaves eth0.2004 eth3.2004
bond-miimon 100

auto xenbr.2004
iface xenbr.2004 inet manual
bridge_ports bond.2004
bridge_maxwait 0
bridge_fd 0


# CLUSTER STREAMING - VLAN ID 2005 - PH. IFACE eth0/3

auto eth0.2005

auto eth3.2005

iface eth0.2005 inet manual
vlan_raw_device eth0

iface eth3.2005 inet manual
vlan_raw_device eth3

auto bond.2005
iface bond.2005 inet manual
bond-mode active-backup
slaves eth0.2005 eth3.2005
bond-miimon 100

auto xenbr.2005
iface xenbr.2005 inet manual
bridge_ports bond.2005
bridge_maxwait 0
bridge_fd 0


# CLUSTER MAIL - VLAN ID 2006 - PH. IFACE eth0/3

auto eth0.2006

auto eth3.2006

iface eth0.2006 inet manual
vlan_raw_device eth0

iface eth3.2006 inet manual
vlan_raw_device eth3

auto bond.2006
iface bond.2006 inet manual
bond-mode active-backup
slaves eth0.2006 eth3.2006
bond-miimon 100

auto xenbr.2006
iface xenbr.2006 inet manual
bridge_ports bond.2006
bridge_maxwait 0
bridge_fd 0


# CLUSTER CONTENT FILTER - VLAN ID 2007 - PH. IFACE eth0/3

[SFTP] wierdness

2012-07-27 Thread Jeremy MAURO


Hi everyone,


On my debian box ( Debian: 5.0.10/openssh-server: 1:5.1p1-5) I see the
wierd behavior:
sftp>  ls -l old
-rw-r--r--1 user 100  9798 Jul 16 07:56
20120716_full_delhaizedirect_categories.zip
-rw-r--r--1 user 100  9802 Jul 17 09:57
20120717_full_delhaizedirect_categories.zip

sftp>  ls -l -h old
-rw-r--r--0 1047 100  9.6K Jul 16 09:56
old/20120716_full_delhaizedirect_categories.zip
-rw-r--r--0 1047 100  9.6K Jul 17 11:57
old/20120717_full_delhaizedirect_categories.zip

As you can see there a date difference.



# date
vendredi 27 juillet 2012, 10:26:46 (UTC+0200)
# cat /etc/default/rcS
#
#   Defaults for the boot scripts in /etc/rcS.d
#

# Time files in /tmp are kept in days.
TMPTIME=0
# Set to yes if you want sulogin to be spawned on bootup
SULOGIN=no
# Set to no if you want to be able to login over telnet/rlogin
# before system startup is complete (as soon as inetd is started)
DELAYLOGIN=yes
# Set UTC=yes if your system clock is set to UTC (GMT), and UTC=no if not.
UTC=no
# Set VERBOSE to "no" if you would like a more quiet bootup.
VERBOSE=yes
# Set EDITMOTD to "no" if you don't want /etc/motd to be editted
automatically
EDITMOTD=yes
# Set FSCKFIX to "yes" if you want to add "-y" to the fsck at startup.
FSCKFIX=no

Why do I see the difference with sftp and I don't see any difference
when I am logging with ssh on the server
# ls -l old/
total 29801
-rw-r--r-- 1 user users 9802 jui 17 11:57
20120717_full_delhaizedirect_categories.zip
-rw-r--r-- 1 user users 9797 jui 18 08:22
20120718_full_delhaizedirect_categories.zip
# ls -l -h old/
total 30M
-rw-r--r-- 1 user users 9,6K jui 17 11:57
20120717_full_delhaizedirect_categories.zip
-rw-r--r-- 1 user users 9,6K jui 18 08:22
20120718_full_delhaizedirect_categories.zip



Any idea?



--
Regards,
JM



PS: not able to find a suitable openssh mailing to send the question, sorry.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5012577c.7080...@antidot.net

Re: web conferencing software.

2012-07-14 Thread Mauro

Are you using some web conferencing software?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0XFywS10trfxUCO+vygsoD8a=vgdz6jsxaia68c3hl...@mail.gmail.com

web conferencing software.

2012-07-14 Thread Mauro

I need to install a web conferencing system for my company.
I've read that the best are bigbluebutton and openmeeting.
What is your advice?
Thanks.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0VprQyLTZUyu+AO+1J8Ehb8W4jPc4PeMTO8=dp4bkz...@mail.gmail.com

xen hypervisor security update.

2012-07-04 Thread Mauro

Hello.
In debian squeeze there are several xen security updates:

xen-hypervisor
xen-utils
and so on.

In the debian website there are no information on what are the fixes.
Where can I find them?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cae17a0xs1wss0rapzg8uk154uszn83urb7hx2dejz43d-_n...@mail.gmail.com

Re: failures on boot.

2012-06-21 Thread Mauro

On 16 June 2012 23:42, Roger Leigh  wrote:
>
> However... it certainly shouldn't be giving errors.  It would be useful
> to know where the error occurs (transcript of the boot log from e.g.
> bootlogd) and the contents of /etc/fstab.  Possibly might happen if
> the filesystem is mounted read-only?
>
> If you can replicate the problem and pin it down to a specific
> script, could you file a bug against iniscripts with all the above
> information as requested?

It seems that was a temporary bug from some package.
I've upgraded the system and now the problem is disappeared.
Thank you.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0Wr3b_=xw50-nucwm_ugcpezfnlstisesez+70ksso...@mail.gmail.com

failures on boot.

2012-06-12 Thread Mauro

Hello.
I'm using debian sid.
When I boot the system I have these failures:

cleaning up temporary files /lib/init/bootclean.sh line 22 /tmp/.clean
cannot overwrite existing file
bootclean: failure creating /tmp/.clean
init/rw failed

However the system runs with no problems.
There is someone that have the same problem?
I don't know if it is a temporary bug.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAE17a0UqRLUL1uGrvzCeSFK+iWsyQ12Snm9sMEiq=trfso4...@mail.gmail.com

Re: IBM x3550 M3 with Debian Squeeze not detecting disks on installation

2011-12-30 Thread Mauro Sánchez

2011/12/29 Stan Hoeppner :
> On 12/29/2011 10:39 AM, Mauro Sánchez wrote:
>
>> I have installed debian testing and then installed xen-linux-system
>> and boot from its kernel. Till now everything just works fine. What
>> kind of tests would you suggest me for high load activity with the
>> controller?
>
> Bonnie++, IOzone, FIO, etc.  Anything with a high random IOPS workload.
>  Just running a huge sequential write/read with dd probably won't cause
> any problems to surface.
>
Ok, thanks Stan, I'll use some of those tools to test it.

Mauro.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camcf3yx1q+_asxccrepan0cdnsnpeksybpggzijsordnzsq...@mail.gmail.com

Re: IBM x3550 M3 with Debian Squeeze not detecting disks on installation

2011-12-30 Thread Mauro Sánchez

2011/12/29 Stan Hoeppner :
> On 12/29/2011 9:41 AM, Mauro Sánchez wrote:
>> 2011/12/29 Camaleón :
>>> On Thu, 29 Dec 2011 10:31:28 -0300, Mauro Sánchez wrote:
>>>
>>>> Camaleon, the configuration with one disk uses JBOD. I have tried Debian
>>>> Stable with only one disk, RAID 1, RAID 5 and LVM. None of them worked.
>>>
>>> Did you try to partition and format the disks from Gparted?
>>>
>> Camaleon,
>> I created a partition of 10 GB with Gparted. Then I started to install
>> Squeeze but when is installing the base system it hangs up at 17% with
>> the following errors catched from the dmesg:
>> megasas: RESET -4637 cmd=2a retries=0
>> megasas: waiting for 1 commands to complete
>> megasas: failed to do reset
>> megasas: cannot recover form previous reset failures
>>
>> And other errors of the I/O type.
>
> This is all brand new hardware isn't it?  I've been working under that
> assumption.  If it is used, or refurb stuff, scratch my previous
> statement about the drives, as they could very well have problems, or
> anything else in the chassis for that matter.
>
> New/used/refurb, the first thing I would do, given those errors, is
> check/replace the 8087 cable connecting the 9240 to the drive cage
> backplane.
>
Hello Stan, it's all brand new hardware. So I think it's not a
hardware problem, because I have installed Wheezy on it without any
problem.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camcf3yxb9bzruktoh4keymju1b_8s8rrngwaaajxunm+f3c...@mail.gmail.com

Re: IBM x3550 M3 with Debian Squeeze not detecting disks on installation

2011/12/29 Camaleón :
> On Thu, 29 Dec 2011 12:41:25 -0300, Mauro Sánchez wrote:
>
>> 2011/12/29 Camaleón :
>>> On Thu, 29 Dec 2011 10:31:28 -0300, Mauro Sánchez wrote:
>>>
>>>> Camaleon, the configuration with one disk uses JBOD. I have tried
>>>> Debian Stable with only one disk, RAID 1, RAID 5 and LVM. None of them
>>>> worked.
>>>
>>> Did you try to partition and format the disks from Gparted?
>>>
>> Camaleon,
>> I created a partition of 10 GB with Gparted. Then I started to install
>> Squeeze but when is installing the base system it hangs up at 17% with
>> the following errors catched from the dmesg:
>> megasas: RESET -4637 cmd=2a retries=0
>> megasas: waiting for 1 commands to complete
>> megasas: failed to do reset
>> megasas: cannot recover form previous reset failures
>>
>> And other errors of the I/O type.
>
> Ugh... that sounds like the RAID controller is hanging/resetting very badly
> or the driver is behaving weirdly :-(
>
> It can be then a bug in the megasas kernel module and Google finds *lots*
> of similar errors for that same driver, and curiously, xen kernels:
>
> http://www.google.com/webhp?complete=0&hl=en#hl=en&tbo=1&complete=0&site=webhp&tbs=qdr:y&q=LSI+megasas:+RESET+-4637+cmd%3D2a+retries%3D0&tbo=1&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=e8f1b276e45aa3ef&biw=1280&bih=888
>
> I wouldn't discard this is still happening on wheezy... although the
> installer can succeed, what will happen once the system enters into
> high load? Will the driver experience the same problems?
>
Hello Camaleon.
I have installed debian testing and then installed xen-linux-system
and boot from its kernel. Till now everything just works fine. What
kind of tests would you suggest me for high load activity with the
controller?

> Are you using the NET ISO image to install Debian? If no, I would do a
> final try using it, just to discard bad media and/or DVD read errors.
>
I tried with the net iso and the iso cd, just to be sure it wasn't a
media error. Thanks for asking anyway.

> Greetings,
>
> --
> Camaleón
Greetings,
Mauro.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMCF3ywJvNdoiwK38nLWw=1+uo21W_PkQp3KgUvUhddiE29a=g...@mail.gmail.com

Re: IBM x3550 M3 with Debian Squeeze not detecting disks on installation

2011/12/29 Stan Hoeppner :
> On 12/29/2011 8:39 AM, Mauro Sánchez wrote:
>
>> As I said before, in my opinion, there is a problem with the kernel
>> and the disks. But it's just my opinion based on all the tests I've
>> done.
>
> The problem is with the kernels and modules you are using, and remotely
> possibly teh 9240, not the disk drives.
>
> Is BBWC enabled on this 9240?  Is the cache is write-back mode?  If so
> disabled the cache or change its mode to write-through.
>
Hello Stan.
The disk cache is Disabled and de write mode is write through.
About BBWC I don't know where to check it.

Mauro.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camcf3ywxsm9z7xzwawqqvsdbnpavq1f6vfuud0e_8wmqtyw...@mail.gmail.com

Re: IBM x3550 M3 with Debian Squeeze not detecting disks on installation

2011/12/29 Camaleón :
> On Thu, 29 Dec 2011 10:31:28 -0300, Mauro Sánchez wrote:
>
>> Camaleon, the configuration with one disk uses JBOD. I have tried Debian
>> Stable with only one disk, RAID 1, RAID 5 and LVM. None of them worked.
>
> Did you try to partition and format the disks from Gparted?
>
Camaleon,
I created a partition of 10 GB with Gparted. Then I started to install
Squeeze but when is installing the base system it hangs up at 17% with
the following errors catched from the dmesg:
megasas: RESET -4637 cmd=2a retries=0
megasas: waiting for 1 commands to complete
megasas: failed to do reset
megasas: cannot recover form previous reset failures

And other errors of the I/O type.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camcf3yxgrranj+ykgneu4tfd7ln+ef8ug_flr+we5an+7mo...@mail.gmail.com

Re: IBM x3550 M3 with Debian Squeeze not detecting disks on installation

2011/12/29 Camaleón :
> On Thu, 29 Dec 2011 10:31:28 -0300, Mauro Sánchez wrote:
>
>> Camaleon, the configuration with one disk uses JBOD. I have tried Debian
>> Stable with only one disk, RAID 1, RAID 5 and LVM. None of them worked.
>
> Did you try to partition and format the disks from Gparted?
>
No, that's the last test I have to try.

>> But all of them worked with Debian Testing. I also tried
>> squeeze-custom-amd64-0808, wich is a non-official release with support
>> for newer hardware and that worked ok! It worked because it uses a
>> Kernel 2.6.39 from backports. But the problem was that I have to install
>> xen-linux-system, wich uses kernel 2.6.32, and when I tried to load it
>> the server just restarted.
>
> Uh, how is that? You did not say the server "restarted" but it stalled at
> the installation part when making the partitions and formatting the
> disks... did you finally install Squeeze or -put it in another way- when
> is that "restart" happening?
>
About this restart is when I installed Debian from a custom cd wich
has a kernel 2.6.39
The installation works fine and there is no problem. But after that, I
have to install xen-linux-system wich has a kernel 2.6.32, and when I
reboot and try to boot from that kernel (xen-linux-2.6.32-amd64) the
server reboots.
All the other test with Debian stable hangs in the installation when
it tries to format the partitions.
So, even I will manage to create the partitions with Gparted and
install Debian stable, I will have the problem later with xen. But I
am just guessing here.

>> The conclusion of all this tests is that there is a problem with the
>> kernel and the disks, not the raid controller.
>
> Hum... there is no kernel xen (or I can't see it) from backports.
>
You are right, there aren't.

>> I think is a problem with the disks, because when I used one disk with
>> non raid configuration the installation didn't detect the disk, but the
>> installation of debian testing did detect the disk.
>
> Squeeze's stock kernel should support your raid controller card and hard
> disks as I told you on the Spanish mailing list, I can't see what can be
> failing here.
>
As I said before, in my opinion, there is a problem with the kernel
and the disks. But it's just my opinion based on all the tests I've
done.

>> And when I used RAID 5 or RAID 1, the installation of debian stable did
>> detect the raid controller and let me create the partitions, but it
>> hanged up when it tried to format them after I comitted the changes.
>
> Try with the latest version of Gparted (LiveCD), this can be indeed a
> problem within Squeeze installer (not the kernel) and using Gparted you
> may be able to bypass it.
>
I am about to do it.

>> And with debian testing RAID 5 or RAID 1 worked just fine. Maybe I am
>> wrong, but I think the problem is in the kernel and the disks. I think
>> I would have to use debian testing. Thanks a lot for the help.
>> If anyone has another idea about this, it would be great. Greetings.
>> Mauro.
>
> Wheezy will be freezed on June 2012, there is still a long way until it
> gets released but if you can deal with the usual problems coming from
> testing, well, then go on :-)
>
Ok, I will keep it on mind.

> Greetings,
>
> --
> Camaleón
>
>
Greetings,
Mauro.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camcf3yx8_1rg7sjbg6jlht_z1rmwm69-ss5cbuwrjrocev4...@mail.gmail.com

Re: IBM x3550 M3 with Debian Squeeze not detecting disks on installation