Re: [Unattended] Message Signaled Interrupts

2008-04-21 Thread Regis Gras
Nils Olav Fossum wrote: ok, no doubt it is a bug in the network chain somewhere. Contacting Dell should be the next step. They have very good linux people. Meanwhile I will suggest booting the 755's from CD, a corrupted network chain can be a bit hazardous.. Booting from CD has exactly

Re: [Unattended] Message Signaled Interrupts

2008-04-21 Thread Matt Hyclak
On Mon, Apr 21, 2008 at 09:48:59AM +0200, Regis Gras enlightened us: Nils Olav Fossum wrote: ok, no doubt it is a bug in the network chain somewhere. Contacting Dell should be the next step. They have very good linux people. Meanwhile I will suggest booting the 755's from CD, a

Re: [Unattended] Message Signaled Interrupts

2008-04-21 Thread Nyström Anders
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Hyclak Sent: 21. huhtikuuta 2008 14:15 To: unattended-info@lists.sourceforge.net Subject: Re: [Unattended] Message Signaled Interrupts On Mon, Apr 21, 2008 at 09:48:59AM +0200, Regis Gras

Re: [Unattended] Message Signaled Interrupts

2008-04-17 Thread Regis Gras
Nils Olav Fossum wrote: Ok, looks like the -t parameter did not work out... As I am looking thru the kernel config, found this: [ ] Message Signaled Interrupts (MSI and MSI-X) Its not enabled. So, can one of you with this problem enable MSI (CONFIG_PCI_MSI) in the kernel and test if that

Re: [Unattended] Message Signaled Interrupts

2008-04-17 Thread Nils Olav Fossum
Torsdag 17 april 2008 08:30, skrev Regis Gras: Nils Olav Fossum wrote: Ok, looks like the -t parameter did not work out... As I am looking thru the kernel config, found this: [ ] Message Signaled Interrupts (MSI and MSI-X) Its not enabled. So, can one of you with this problem enable

Re: [Unattended] Message Signaled Interrupts

2008-04-16 Thread Matt Hyclak
On Wed, Apr 16, 2008 at 12:00:28PM +0200, Nils Olav Fossum enlightened us: Onsdag 16 april 2008 09:59, skrev Juan Jose Pablos: Regis Gras escribió: Unfortunately, that does'nt work. The last messages are always: Trying DHCP on eth0 udhcpc (V1.9.2) started :00:19.0:eth0: