ssic-linux-users — User discussion

Re: [SSI-users] setup of OpenSSI 1.9.6 with Debian Sarge with a very old hardware

[Scott W. <sc...@sl...>]

I don't understand the logic behind trying to recompile kernels.  In
the old days of probing ISA cards, the wrong set of actual hardware
and drivers built-in to the kernel could cause crashes on boot, but
that sort of thing is very rare these days.

Boot the OpenSSI kernel and if the machine freezes during boot, post
the last several console lines.

-scott


On 9/14/10, Alceu Rodrigues de Freitas Junior <gla...@ya...> wrote:
> John Hughes escreveu:
>> On Tue, 2010-09-14 at 01:08 -0300, Alceu Rodrigues de Freitas Junior
>> wrote:
>>
>>> I tried latter to compile the kernel 2.6.11-ssi-686-smp in this box,
>>> changing only the processor type and removing the SMP support.
>>>
>>> During the compilation, the machine just hung when compiling the
>>> following line:
>>>
>>> kernel/ptrace.o
>>>
>> sounds like the machine is broken.
>>
>>
>>
>
> I'm not sure about that. I started compiling the regular Debian Sarge
> kernel from the kernel-source package yesterday and after 7 hours it's
> still compiling.
>
> As soon as it finishes, I'll try a second time with OpenSSI source and,
> if it not work, I'll try again but loading the configuration from the
> regular Sarge kernel.
>
> I'll let you know as soon as I finish those tests.
>
> Regards,
> Alceu
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Ssic-linux-users mailing list
> Ssi...@li...
> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users
>

Re: [SSI-users] setup of OpenSSI 1.9.6 with Debian Sarge with a very old hardware

[Alceu R. de F. J. <gla...@ya...>]

John Hughes escreveu:
> On Tue, 2010-09-14 at 01:08 -0300, Alceu Rodrigues de Freitas Junior
> wrote:
> 
>> I tried latter to compile the kernel 2.6.11-ssi-686-smp in this box, 
>> changing only the processor type and removing the SMP support.
>>
>> During the compilation, the machine just hung when compiling the 
>> following line:
>>
>> kernel/ptrace.o
>>
> sounds like the machine is broken.
> 
> 
> 

I'm not sure about that. I started compiling the regular Debian Sarge 
kernel from the kernel-source package yesterday and after 7 hours it's 
still compiling.

As soon as it finishes, I'll try a second time with OpenSSI source and, 
if it not work, I'll try again but loading the configuration from the 
regular Sarge kernel.

I'll let you know as soon as I finish those tests.

Regards,
Alceu

Re: [SSI-users] setup of OpenSSI 1.9.6 with Debian Sarge with a very old hardware

[John H. <jo...@ca...>]

On Tue, 2010-09-14 at 01:08 -0300, Alceu Rodrigues de Freitas Junior
wrote:

> I tried latter to compile the kernel 2.6.11-ssi-686-smp in this box, 
> changing only the processor type and removing the SMP support.
> 
> During the compilation, the machine just hung when compiling the 
> following line:
> 
> kernel/ptrace.o
> 
sounds like the machine is broken.

[SSI-users] setup of OpenSSI 1.9.6 with Debian Sarge with a very old hardware

[Alceu R. de F. J. <gla...@ya...>]

Gentleman,

I tried to install OpenSSI 1.9.6 in Debian Sarge running in the 
following hardware:

jackal@master:~$ cat /proc/cpuinfo
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 5
model        : 4
model name    : Pentium MMX
stepping    : 3
cpu MHz        : 233.825
fdiv_bug    : no
hlt_bug        : no
f00f_bug    : yes
coma_bug    : no
fpu        : yes
fpu_exception    : yes
cpuid level    : 1
wp        : yes
flags        : fpu vme de pse tsc msr mce cx8 mmx
bogomips    : 459.77

jackal@master:~$ lspci
0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5597 
[SiS5582] (rev 02)
0000:00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 
(LPC Bridge) (rev 01)
0000:00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] 
(rev d0)
0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
0000:00:14.0 VGA compatible controller: Silicon Integrated Systems [SiS] 
5597/5598/6326 VGA (rev 65)

The hardware is quite old, so I didn't expect to have issues regarding 
drivers.

Setup in this machine was quite straightforward, without any noise 
besides ipvsadm complain (which was expected, I think).

The only thing that I changed is that I used a Debian Sarge CDROM to 
start the install, then I added the URI below to sources.list:

deb http://archive.debian.org/debian/ Debian-3.1 main contrib

The problem was when I tried to boot with the OpenSSI kernel: after 
initial messages from the kernel, the monitor goes black and the machine 
just restarted alone.

After that I tried adding "noapic" option in the menu.lst file, but the 
result was the same. I tried to boot also by using the rescue option 
with the OpenSSI kernel (grub) but again all I got was a black screen 
and a automatic reboot.

I tried latter to compile the kernel 2.6.11-ssi-686-smp in this box, 
changing only the processor type and removing the SMP support.

During the compilation, the machine just hung when compiling the 
following line:

kernel/ptrace.o

The machine just freezed, I could not boot by using the keyboard (the 
numlock and caps locks just didn't respond after some clicks), I had to 
reboot the machine by using the reset button.

I intend to compile the kernel 2.6.8-4-386 (Debian Sarge Vanilla) just 
to check if it's not a kernel option or a bug, but I would appreciate 
any help about this issue.

Thanks in advance,
Alceu

Re: [SSI-users] initial setup for newbies

[Alceu R. de F. J. <gla...@ya...>]

Hello Scott,

COmments below...

Scott Walters escreveu:
>> - lspci:
>>
>> 0000:00:00.0 RAM memory: nVidia Corporation: Unknown device 03ea (rev a1)
>> 0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 03e0 (rev a2)
>> 0000:00:01.1 SMBus: nVidia Corporation: Unknown device 03eb (rev a2)
>> 0000:00:01.2 RAM memory: nVidia Corporation: Unknown device 03f5 (rev a2)
>> 0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 03f1
>> (rev a3)
>> 0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 03f2
>> (rev a3)
>> 0000:00:04.0 PCI bridge: nVidia Corporation: Unknown device 03f3 (rev a1)
>> 0000:00:05.0 0403: nVidia Corporation: Unknown device 03f0 (rev a2)
>> 0000:00:06.0 IDE interface: nVidia Corporation: Unknown device 03ec (rev a2)
>> 0000:00:07.0 Bridge: nVidia Corporation: Unknown device 03ef (rev a2)
>> 0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)
>> 0000:00:08.1 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)
>> 0000:00:09.0 PCI bridge: nVidia Corporation: Unknown device 03e8 (rev a2)
>> 0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)
>> 0000:00:0c.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)
>> 0000:00:0d.0 VGA compatible controller: nVidia Corporation: Unknown
>> device 03d0 (rev a2)
>> 0000:01:06.0 Ethernet controller: VIA Technologies, Inc. VT6105
>> [Rhine-III] (rev 8b)
> 
> The only thing not unknown is the Ethernet card.  What's up with that?
>  Do you have modules installed in /lib/modules for the OpenSSI kernel
> (eg /lib/modules/2.6.14-ssi-686-smp where "2.6.14-ssi-686-smp" matches
> the name of the initrd and vmlinuz in /boot ) ?

Indeed, I was not able to put the onboard ethernet card to work. Just 
cannot load the appropriated kernel module to do that.

> No, that probably isn't it.  I think the nVidia chipsets are just way too new.

Don't know if this is the real reason. I could not compile the .c file 
from Nvidia website, but the kernel from Sarge look like already have 
such module (just don't know if it is the correct version).

To fix that, I just inserted an offboard ethernet card (Rhine-III) and 
everything worked fine.

> Interesting bits of dmesg would be further down.  Feel free to send
> the full dmesg to me directly.

Ok!

> I discovered that it's harder than I would have guessed to figure out
> if Linux supports any given PCI device by ID.  NetBSD hardcodes those
> in .h files.  I couldn't establish that supported devices on my own
> system were supported from looking at the code.  *sigh*  So trying the
> older machine (or else virtual hardware) is your best bet.

Let me know if you need further info.

Anyway, I tested OpenSSI in a very, very old machine here. Let's call it 
"meth" (shorter version of "Methuselah"):

jackal@master:~$ cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 5
model		: 4
model name	: Pentium MMX
stepping	: 3
cpu MHz		: 233.825
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: yes
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr mce cx8 mmx
bogomips	: 459.77

jackal@master:~$ lspci
0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5597 
[SiS5582] (rev 02)
0000:00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 
(LPC Bridge) (rev 01)
0000:00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] 
(rev d0)
0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
0000:00:14.0 VGA compatible controller: Silicon Integrated Systems [SiS] 
5597/5598/6326 VGA (rev 65)

Setup in this machine was quite straightforward, without any noise 
besides ipvsadm complain (which was expected, I think).

The only thing that I changed is that I used a Debian Sarge CDROM to 
start the install, then I added the URI below to sources.list:

deb http://archive.debian.org/debian/ Debian-3.1 main contrib # updates 
was not available

The problem was when I tried to boot with the OpenSSI kernel: after 
initial messages from the kernel, the monitor goes black and the machine 
just restarted alone.

After that I tried adding "noapic" option in the menu.lst file, but the 
result was the same. I tried to boot also by using the rescue option 
with the OpenSSI kernel (grub) but again all I got was a black screen 
and a automatic reboot.

Should I try to compile the OpenSSI kernel in this box?

I'll try Fedora in both boxes and I'll let you know about the results.

Thanks for helping,
Alceu

Re: [SSI-users] initial setup for newbies

[Scott W. <sc...@sl...>]

> - lspci:
>
> 0000:00:00.0 RAM memory: nVidia Corporation: Unknown device 03ea (rev a1)
> 0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 03e0 (rev a2)
> 0000:00:01.1 SMBus: nVidia Corporation: Unknown device 03eb (rev a2)
> 0000:00:01.2 RAM memory: nVidia Corporation: Unknown device 03f5 (rev a2)
> 0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 03f1
> (rev a3)
> 0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 03f2
> (rev a3)
> 0000:00:04.0 PCI bridge: nVidia Corporation: Unknown device 03f3 (rev a1)
> 0000:00:05.0 0403: nVidia Corporation: Unknown device 03f0 (rev a2)
> 0000:00:06.0 IDE interface: nVidia Corporation: Unknown device 03ec (rev a2)
> 0000:00:07.0 Bridge: nVidia Corporation: Unknown device 03ef (rev a2)
> 0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)
> 0000:00:08.1 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)
> 0000:00:09.0 PCI bridge: nVidia Corporation: Unknown device 03e8 (rev a2)
> 0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)
> 0000:00:0c.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)
> 0000:00:0d.0 VGA compatible controller: nVidia Corporation: Unknown
> device 03d0 (rev a2)
> 0000:01:06.0 Ethernet controller: VIA Technologies, Inc. VT6105
> [Rhine-III] (rev 8b)

The only thing not unknown is the Ethernet card.  What's up with that?
 Do you have modules installed in /lib/modules for the OpenSSI kernel
(eg /lib/modules/2.6.14-ssi-686-smp where "2.6.14-ssi-686-smp" matches
the name of the initrd and vmlinuz in /boot ) ?

No, that probably isn't it.  I think the nVidia chipsets are just way too new.

Interesting bits of dmesg would be further down.  Feel free to send
the full dmesg to me directly.

I discovered that it's harder than I would have guessed to figure out
if Linux supports any given PCI device by ID.  NetBSD hardcodes those
in .h files.  I couldn't establish that supported devices on my own
system were supported from looking at the code.  *sigh*  So trying the
older machine (or else virtual hardware) is your best bet.

Cheers,
-scott

Re: [SSI-users] download of Fedora 3

[MatrixS_Master <mat...@ya...>]

Hello!

Linuxquestions is a bad choice. Try this storage:
Index of /Linux on Riken.JP
I've downloaded FC3 iso here. A very big archive.
Direct link looks like http://ftp.riken.jp/Linux/fedora/core/3/i386/iso/

Kind regards,
Dmitry.


09/09/2010 в 02:43 -0300, Alceu Rodrigues de Freitas Junior:
> Greetings,
> 
> I'm looking for downloading a Fedora 3 CDROM media to give a try 
> installing OpenSSI on it, but I'm not being able to find any repository 
> that contains such media. Even http://www.linuxiso.org seems to still 
> have Fedora 3 medias download.
> 
> Could you guys please provide an method to download Fedora 3? After 
> searching in Google, all results ended in finding only the version 7 as 
> the most old version available for download.
> 
> Thanks in advance,
> Alceu
> 
> 
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
> 
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Ssic-linux-users mailing list
> Ssi...@li...
> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users
> 

Re: [SSI-users] Res: download of Fedora 3

[Mulyadi S. <mul...@gm...>]

On Thu, Sep 9, 2010 at 23:50, Alceu R. de Freitas Jr.
<gla...@ya...> wrote:
> Yup. This is a broken link:
>
> "This Page Cannot Be Displayed
>
> The file (
> ftp://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/3/i386/iso/FC3-i386-disc1.iso


How about this one?
http://archives.fedoraproject.org/pub/archive/fedora/linux/core/3/i386/iso/

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

[SSI-users] Res: download of Fedora 3

[Alceu R. de F. Jr. <gla...@ya...>]

----- Mensagem original ----
> De: Mulyadi Santosa <mul...@gm...>
> Para: Alceu Rodrigues de Freitas Junior <gla...@ya...>
> Cc: ssi...@li...
> Enviadas: Quinta-feira, 9 de Setembro de 2010 3:52:45
> Assunto: Re: [SSI-users] download of Fedora 3
> 
> > I'm looking for downloading a Fedora 3  CDROM media to give a try
> > installing OpenSSI on it, but I'm not being  able to find any repository
> > that contains such media. Even http://www.linuxiso.org seems  to still
> > have Fedora 3 medias download.
> 
> uhm, have you tried  this?
> http://iso.linuxquestions.org/fedora/fedora-core-3/
> 

Yup. This is a broken link:

"This Page Cannot Be Displayed

The file ( 
ftp://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/3/i386/iso/FC3-i386-disc1.iso

) could not be found. The address is either incorrect or obsolete.

If you have questions, or feel this is an error, please contact the local 
Helpdesk and provide the codes shown below.
Notification codes:      (1, FTP_NOT_FOUND, 
ftp://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/3/i386/iso/FC3-i386-disc1.iso)"


      

Re: [SSI-users] download of Fedora 3

[Mulyadi S. <mul...@gm...>]

On Thu, Sep 9, 2010 at 12:43, Alceu Rodrigues de Freitas Junior
<gla...@ya...> wrote:
> Greetings,
>
> I'm looking for downloading a Fedora 3 CDROM media to give a try
> installing OpenSSI on it, but I'm not being able to find any repository
> that contains such media. Even http://www.linuxiso.org seems to still
> have Fedora 3 medias download.

uhm, have you tried this?
http://iso.linuxquestions.org/fedora/fedora-core-3/


-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

[SSI-users] download of Fedora 3

[Alceu R. de F. J. <gla...@ya...>]

Greetings,

I'm looking for downloading a Fedora 3 CDROM media to give a try 
installing OpenSSI on it, but I'm not being able to find any repository 
that contains such media. Even http://www.linuxiso.org seems to still 
have Fedora 3 medias download.

Could you guys please provide an method to download Fedora 3? After 
searching in Google, all results ended in finding only the version 7 as 
the most old version available for download.

Thanks in advance,
Alceu

Re: [SSI-users] initial setup for newbies

[Alceu R. de F. J. <gla...@ya...>]

Hello there Scott,

Scott Walters  :
> Yes, QEMU would be handy for diagnosing problems.  That would rule out
> hardware compat/support problems.
> 
> Not finding the root drive sounds like very probably lack of support
> for your hard drive controller.
> 
> If you want to use your real hardware, you might get an IDE66
> controller off of eBay cheap and install on that.  If you have an
> on-board IDE controller, using that instead of SATA might work too.

This give a another idea... I do have a real old box here. I'll give it
a try with OpenSSI and let you know.

> If you boot a recent kernel (eg, on Knoppix or another live CD) and
> then post the output of `dmesg` and `lspci`, I (or someone) will
> likely be able to tell you whether this is the case that your SATA
> controller isn't supported.

This is easy. Since I still can boot with Debian vanilla kernel, I can
get this data anytime.

To do that, I had to "fix" the /etc/fstab changed by OpenSSI install,
that was like this:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc	/proc	proc	defaults,node=*	0	0
/dev/hda1	/	ext3	defaults,errors=remount-ro,node=1	0	1
/dev/hda9	/home	ext3	defaults,node=1	0	2
/dev/hda8	/tmp	ext3	defaults,node=1	0	2
/dev/hda5	/usr	ext3	defaults,node=1	0	2
/dev/hda6	/var	ext3	defaults,node=1	0	2
/dev/hda7	none	swap	sw,node=1	0	0
/dev/hdb	/media/cdrom0	iso9660	ro,user,noauto,node=1	0 0	/dev/fd0 
/media/floppy0	auto	rw,user,noauto,node=*	0 0

And I changed it to this:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc	/proc	proc	defaults,node=*	0	0
/dev/hda1	/	ext3	defaults,errors=remount-ro	0	1
/dev/hda9	/home	ext3	defaults	0	2
/dev/hda8	/tmp	ext3	defaults	0	2
/dev/hda5	/usr	ext3	defaults	0	2
/dev/hda6	/var	ext3	defaults	0	2
/dev/hda7	none	swap	sw,node=1	0	0
/dev/hdb	/media/cdrom0	iso9660	ro,user,noauto	0	0
/dev/fd0	/media/floppy0	auto	rw,user,noauto	0	0

During my tests with the OpenSSI kernel, it doesn't matter which version
of /etc/fstab I left. Anyway, when I tried to add drivers to the initrd,
I left the OpenSSI fstab version as configured.

Now let's go back to the data requested:

- lspci:

0000:00:00.0 RAM memory: nVidia Corporation: Unknown device 03ea (rev a1)
0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 03e0 (rev a2)
0000:00:01.1 SMBus: nVidia Corporation: Unknown device 03eb (rev a2)
0000:00:01.2 RAM memory: nVidia Corporation: Unknown device 03f5 (rev a2)
0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 03f1 
(rev a3)
0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 03f2 
(rev a3)
0000:00:04.0 PCI bridge: nVidia Corporation: Unknown device 03f3 (rev a1)
0000:00:05.0 0403: nVidia Corporation: Unknown device 03f0 (rev a2)
0000:00:06.0 IDE interface: nVidia Corporation: Unknown device 03ec (rev a2)
0000:00:07.0 Bridge: nVidia Corporation: Unknown device 03ef (rev a2)
0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)
0000:00:08.1 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)
0000:00:09.0 PCI bridge: nVidia Corporation: Unknown device 03e8 (rev a2)
0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)
0000:00:0c.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)
0000:00:0d.0 VGA compatible controller: nVidia Corporation: Unknown 
device 03d0 (rev a2)
0000:01:06.0 Ethernet controller: VIA Technologies, Inc. VT6105 
[Rhine-III] (rev 8b)

- dmesg: dmesg is a bit long to post to the list. Please let me know if 
all the content of it should be posted. Anywhere, I put the parts that I 
thought that were "interesting", but I can check for other parts as well.

...

CPU: After generic identify, caps: 078bfbff ebd3fbff 00000000 00000000
CPU: After vendor identify, caps:  078bfbff ebd3fbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps:        078bfbff ebd3fbff 00000000 00000410
CPU: AMD Sempron(tm) Processor LE-1150 stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000004
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
init IO_APIC IRQs
  IO-APIC (apicid-pin) 4-0, 4-16, 4-17, 4-18, 4-19, 4-20, 4-21, 4-22, 
4-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=-1
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2009.0262 MHz.
..... host bus clock speed is 200.0926 MHz.
checking if image is initramfs...it isn't (ungzip failed); looks like an 
initrd

...

ACPI: Subsystem revision 20040326
     ACPI-0352: *** Error: Looking up [\_PR_.CPU0] in namespace, 
AE_NOT_FOUND
search_node f7abda40 start_node f7abda40 return_node 00000000
     ACPI-1133: *** Error: [NULL NAME], AE_NOT_FOUND

...

number of MP IRQ sources: 15.
number of IO-APIC #4 registers: 24.
testing the IO APIC.......................
IO APIC #4......
.... register #00: 04000000
.......    : physical APIC id: 04
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 00170011
.......     : max redirection entries: 0017
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 04000000
.......     : arbitration: 04
.... IRQ redirection table:


Thanks in advance,
Alceu

Re: [SSI-users] initial setup for newbies

[Scott W. <sc...@sl...>]

Yes, QEMU would be handy for diagnosing problems.  That would rule out
hardware compat/support problems.

Not finding the root drive sounds like very probably lack of support
for your hard drive controller.

If you want to use your real hardware, you might get an IDE66
controller off of eBay cheap and install on that.  If you have an
on-board IDE controller, using that instead of SATA might work too.

If you boot a recent kernel (eg, on Knoppix or another live CD) and
then post the output of `dmesg` and `lspci`, I (or someone) will
likely be able to tell you whether this is the case that your SATA
controller isn't supported.

Cheers,
-scott

Re: [SSI-users] initial setup for newbies

[Alceu R. de F. J. <gla...@ya...>]

John Hughes escreveu:

> QEMU provides simple virtualised hardware, which is often easier to deal 
> with than real hardware.
> 
> For example the QEMU provided NE2000 style NIC works perfectly with 
> OpenSSI, as does the QEMU IDE disk controller.
> 
> (KVM, if it runs on your machine) should give the same benifits.
> 
> For me the other advantage of QEMU is reducing the amount of work 
> necessary to continue from a screw up.
> 

I'm not considering using QEMU because, even if I got it working, I will 
not be able to use it during my tests since I have a Perl program (that 
uses fork to divide processing work) that I would like to test if it can 
be improved without huge changes to it.

Unless using QEMU helps me identifying an error during the procedures 
I'm executing, I do not see many reasons to using it. The hardware that 
I have available for testing does not have multiple processors/cores so 
I could take advantage of them by using hardware emulation.

Please advise if QEMU could be used during my tests. I really don't know 
much about virtualization with QEMU.

Thanks in advance,
Alceu

Re: [SSI-users] initial setup for newbies

[Alceu R. de F. J. <gla...@ya...>]

Hello there,

I'm facing the problems quite the same as you are. Maybe we could help 
each other.

MatrixS_Master escreveu:
> Then I tried to install old Sarge (r7) and OpenSSI v1. My sources.list
> file looks like
> deb http://archive.debian.org/debian-archive/debian sarge main contrib
> deb http://archive.debian.org/debian-archive/debian-volatile/
> sarge/volatile main contrib
> security updates commented out
> in installation process.

I did a different approach: I downloaded two of the three DVD's from 
Debian Sarge and executed a offline setup.

During the setup, Sarge will try to get updates from 
security.debian.org. I had to unplug the box from the Internet (probably 
there is a better approach to avoid that, which I don't know) before 
continuing the setup.

I added both DVD's as source for packages with apt-cdrom add, but did 
NOT select a single package besides the minimal setup.

> After installing a minimal system, I tried
> # echo "deb http://deb.openssi.org/openssi-v1/ ./"
>>> /etc/apt/sources.list
> modify apt preferences
> # apt-get update
> # apt-get dist-upgrade
> # apt-get install openssi

I did the same steps here, but I had to change the sources.list from:

deb http://deb.openssi.org/v2 ./
deb-src http://deb.openssi.org/v2 ./

to:

deb http://deb.openssi.org/openssi-v1.9.6 ./
deb-src http://deb.openssi.org/openssi-v1.9.6 ./

since my box could not locate the repository with the URL given by the 
documentation.

 From the version of sources.list you had used (deb 
http://deb.openssi.org/openssi-v1/ ./) I understand that you had tried 
to use version 1.2 of OpenSSI, which looks like is not being actively 
maintained. Look like the version 1.9.6 is the one to go. But were you 
able to download the packages from OpenSSI repository without changing 
the sources.list?

I did not get a feedback about the URL's available in the documentation, 
if they are correct or not. But for me, the URL's in the don't work at all.

The last try I gave I used kernel 2.6 with Sarge during install, since 
in the previous tests (with kernel 2.4) I got some error messages like 
"kernel does not support IPVS (2.6)", but I still got some warnings  anyway.

After that, I executed:

apt-get update
apt-get dist-upgrade

I got some packages downgrade, but this is expected. But I had to 
executed apt-get update twice, since in the first time I got an error 
message saying that Release file was not available. I got it after 
executing apt-get update a second time.

> I answered to all of questions and program said that's all good. But
> after reboot new kernel not loading. Grub unpacking the kernel image and
> freezes. Kernel dead.

Which error do you get? I always get this one:

kernel panic - not syncing: VFS: Unable to mount root fs on 
unknow-block(1,0)

Before that, my keyboard got's the CAPS-LOCK and SCROLL-LOCK leds 
flashing, which indicates some problem with the kernel to boot.

Then I checked the mailing lists archives for some help. I found some 
tips to create a new initrd image with additional modules, specially 
ext3 module. I did that, editing the configuration of initrd in /etc, 
tried again: same issue. I even mount the initrd (with -o loop option) 
and double checked if the modules of ext3 and my network cards were 
available, and they were.

A new try, I download the kernel source from OpenSSI repository and did 
a kernel compile. I used the config available in /boot to get most of 
the options already set, and changed ONLY the features below:
1 - Added ext3 and cramfs in the kernel image instead of using them as 
modules (this should avoid the need to use initrd modules)
2 - Changed the processor type to fit the processor available in my 
testing machine (a Sempron);
3 - Remove the SMP feature from the kernel, since my box is not SMP.

Finally, I used make-kpkg program to generate a Debian package of the 
new kernel. It did not generate a initrd image.

After that, I still getting the same kernel panic message (related to 
not being able to mount root fs).

Then I tried to boot with the kernel in rescue mode and got this 
additional message:

Instruction(i) breakpint #0 at 0xc011e510 (adjusted)
0xc011e510 panic_hook: int3
Entering kdb(current=0xc19a6aa0, pid 2) due to Breakpoint @0xc011e510

I don't know what I could execute in the prompt "kdb" which as opened. 
Looks like a debugging for the kernel.

> I repeat all steps in fresh system, install kernel-patch-2.4-ipvs and
> run kernel with this parameters:
> kernel /boot/vmlinuz-2.4.22-1.2199.ntpl-ssi-686-smp devfs=mount
> root=/dev/hda1 ro
> Nothing changed. Kernel looks like dead or infinitely waiting for
> somewhat.

I did the same, several times. Sometimes my box hanged because of ACPI 
(which I had disable with noapic option in Grub boot loader) but now I'm 
getting a kernel panic due not locating the root fs to boot. This is the 
  error message I got from the kernel before setting noapic option:

kernel-panic - not syncing: IO-APIC+times doesn't work! Boot with 
apic=debug and send a report. Then try booting with the 'noapic' option

Does OpenSSI needs ACPI working?

> I doubt about this situation. Where is my mistake? Can I install more
> new release and where in root deb.openssi.org I can found it?
> What OS would be preferable? Maybe I need to move to Fedora Core?
> I'm VERY interesting in SSI clustering. I have 5 machines in special 1G
> private network. They used independent and this is not comfortable.

I still trying to isolate the problem, if is a error from the procedure 
I'm executing, a bug in the OpenSSI kernel or a defect in my box 
hardware (which I found difficult to be, since I can get a vanilla 
kernel working without problems).

I would be happy to execute more tests or providing more information 
about the errors.

Regards,
Alceu

Re: [SSI-users] initial setup for newbies

[John H. <jo...@Ca...>]

Alceu Rodrigues de Freitas Junior wrote:
> Anyway, I still have problems with the setup in my machine and I don't 
> think is something related to hardware. Don't see how using QEMU would 
> help with that.
>   
QEMU provides simple virtualised hardware, which is often easier to deal 
with than real hardware.

For example the QEMU provided NE2000 style NIC works perfectly with 
OpenSSI, as does the QEMU IDE disk controller.

(KVM, if it runs on your machine) should give the same benifits.

For me the other advantage of QEMU is reducing the amount of work 
necessary to continue from a screw up.

Re: [SSI-users] initial setup for newbies

[Scott W. <sc...@sl...>]

Hi Dmitry,

My experience is with the development branch of OpenSSI (1.9.x).
Fedora seems to be an easier install target.  Debian changes
constantly.  It will really help if you know how to diagnose problems
in Linux in general.  Installing OpenSSI seems to take people several
tries.  You might want to read through the mailing list archives to
get an idea of the sorts of problems other people have had.  Because
of the older kernel OpenSSI is built on, newer hardware might not be
supported.  Your hard drive controller in particular might not be
supported.  You might have to stick a 66mhz IDE card into a PCI slot,
or find an older, supported SATA card.  Network cards in machines may
or may not be supported.  If the first node (or any other node) can't
figure out what it's MAC address is, it will stop.

Post a log of the install process and then the boot output.  At which
point it stops and what it says before it stops will be helpful in
figuring out what went wrong.

Good luck!
-scott


On 8/25/10, MatrixS_Master <mat...@ya...> wrote:
> Hello all!
>
> My name is Dmitry Soloviov and I'm newbie to OpenSSI. And, like a thread
> starter, got a lot of problems.
> First I tried install OSSI 1.9.6 on my favorite Lenny in VirtualBox VM.
> I've done steps 1-17 from this paper:
> http://deb.openssi.org/openssi/dists/1.9.6-lenny-preview/
> On a last step I've receive a error "mkinitrd failed". Without any error
> description. I've repeat fresh install of Lenny and OpenSSI and nothing
> changed.
>
> Then I tried to install old Sarge (r7) and OpenSSI v1. My sources.list
> file looks like
> deb http://archive.debian.org/debian-archive/debian sarge main contrib
> deb http://archive.debian.org/debian-archive/debian-volatile/
> sarge/volatile main contrib
> security updates commented out
> in installation process.
>
> After installing a minimal system, I tried
> # echo "deb http://deb.openssi.org/openssi-v1/ ./"
>>> /etc/apt/sources.list
> modify apt preferences
> # apt-get update
> # apt-get dist-upgrade
> # apt-get install openssi
>
> I answered to all of questions and program said that's all good. But
> after reboot new kernel not loading. Grub unpacking the kernel image and
> freezes. Kernel dead.
> I repeat all steps in fresh system, install kernel-patch-2.4-ipvs and
> run kernel with this parameters:
> kernel /boot/vmlinuz-2.4.22-1.2199.ntpl-ssi-686-smp devfs=mount
> root=/dev/hda1 ro
> Nothing changed. Kernel looks like dead or infinitely waiting for
> somewhat.
>
> I doubt about this situation. Where is my mistake? Can I install more
> new release and where in root deb.openssi.org I can found it?
> What OS would be preferable? Maybe I need to move to Fedora Core?
> I'm VERY interesting in SSI clustering. I have 5 machines in special 1G
> private network. They used independent and this is not comfortable.
>
> Thanks in advance,
> Dmitry.
>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Ssic-linux-users mailing list
> Ssi...@li...
> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users
>

Re: [SSI-users] use of NFS with OpenSSI 1.9

[Roger T. <rog...@gm...>]

On Wed, Aug 25, 2010 at 10:50 PM, Alceu R. de Freitas Jr. <
gla...@ya...> wrote:

> Greetings,
>
> I was reading the documentation related to NFS for OpenSSI 1.9
> (http://www.openssi.org/cgi-bin/view?page=docs2/1.9/README.nfs-client and
> http://www.openssi.org/cgi-bin/view?page=docs2/1.9/README.nfs-server) and
> saw
> this note:
>
> *** NOTE: NFS client is not yet supported in the new OpenSSI 2.6 kernel ***
>
> This is still the reality?
>

That note was written a long time ago.  OpenSSI supports NFS client.  We
need testing though.


> What should I use for OpenSSI 1.9 as a simple shared filesystem?
>

OpenSSI comes with its own shared filesystem called CFS and is used as the
root filesystem by default.

-Roger

[SSI-users] use of NFS with OpenSSI 1.9

[Alceu R. de F. Jr. <gla...@ya...>]

Greetings,

I was reading the documentation related to NFS for OpenSSI 1.9 
(http://www.openssi.org/cgi-bin/view?page=docs2/1.9/README.nfs-client and 
http://www.openssi.org/cgi-bin/view?page=docs2/1.9/README.nfs-server) and saw 
this note:

*** NOTE: NFS client is not yet supported in the new OpenSSI 2.6 kernel ***

This is still the reality?
What should I use for OpenSSI 1.9 as a simple shared filesystem?

Thanks, 
Alceu Rodrigues de Freitas Junior
--------------------------------------
gla...@ya...
---
A well-used door needs no oil on its hinges.
A swift-flowing stream does not grow stagnant.
Neither sound nor thoughts can travel through a vacuum.
Software rots if not used.
These are great mysteries -- The Tao Of Programming, 5.1



      

Re: [SSI-users] initial setup for newbies

[MatrixS_Master <mat...@ya...>]

Hello all!

My name is Dmitry Soloviov and I'm newbie to OpenSSI. And, like a thread
starter, got a lot of problems.
First I tried install OSSI 1.9.6 on my favorite Lenny in VirtualBox VM.
I've done steps 1-17 from this paper:
http://deb.openssi.org/openssi/dists/1.9.6-lenny-preview/
On a last step I've receive a error "mkinitrd failed". Without any error
description. I've repeat fresh install of Lenny and OpenSSI and nothing
changed.

Then I tried to install old Sarge (r7) and OpenSSI v1. My sources.list
file looks like
deb http://archive.debian.org/debian-archive/debian sarge main contrib
deb http://archive.debian.org/debian-archive/debian-volatile/
sarge/volatile main contrib
security updates commented out
in installation process.

After installing a minimal system, I tried
# echo "deb http://deb.openssi.org/openssi-v1/ ./"
>> /etc/apt/sources.list
modify apt preferences
# apt-get update
# apt-get dist-upgrade
# apt-get install openssi

I answered to all of questions and program said that's all good. But
after reboot new kernel not loading. Grub unpacking the kernel image and
freezes. Kernel dead.
I repeat all steps in fresh system, install kernel-patch-2.4-ipvs and
run kernel with this parameters:
kernel /boot/vmlinuz-2.4.22-1.2199.ntpl-ssi-686-smp devfs=mount
root=/dev/hda1 ro
Nothing changed. Kernel looks like dead or infinitely waiting for
somewhat.

I doubt about this situation. Where is my mistake? Can I install more
new release and where in root deb.openssi.org I can found it?
What OS would be preferable? Maybe I need to move to Fedora Core?
I'm VERY interesting in SSI clustering. I have 5 machines in special 1G
private network. They used independent and this is not comfortable.

Thanks in advance,
Dmitry.

Re: [SSI-users] initial setup for newbies

[Alceu R. de F. J. <gla...@ya...>]

Mulyadi Santosa escreveu:
> Hi..
> 
> On Thu, Aug 19, 2010 at 20:04, Alceu Rodrigues de Freitas Junior
> <gla...@ya...> wrote:
>> I'm not proficient in QEMU. Could you point any good tutorial about it?
> 
> Once I wrote about installing OpenSSI inside Qemu. It's quite old, but
> hopefully it provides you initial clue:
> http://wiki.openssi.org/go/Installation_of_virtual_openSSI_cluster_on_Qemu
> 
> If you want, you could enhance the document...
> 

Thank you, I'll check this out and if possible provide some update/feedback.

Anyway, I still have problems with the setup in my machine and I don't 
think is something related to hardware. Don't see how using QEMU would 
help with that.

I would provide some updates in the instructions provided at 
http://openssi.org/cgi-bin/view?page=docs2/1.9/debian/INSTALL.html but I 
  need some guidance (I believe updating the LaTEX source is preferable).

Regards,
Alceu

Re: [SSI-users] initial setup for newbies

[Mulyadi S. <mul...@gm...>]

Hi..

On Thu, Aug 19, 2010 at 20:04, Alceu Rodrigues de Freitas Junior
<gla...@ya...> wrote:
> I'm not proficient in QEMU. Could you point any good tutorial about it?

Once I wrote about installing OpenSSI inside Qemu. It's quite old, but
hopefully it provides you initial clue:
http://wiki.openssi.org/go/Installation_of_virtual_openSSI_cluster_on_Qemu

If you want, you could enhance the document...

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

Re: [SSI-users] initial setup for newbies

[Alceu R. de F. J. <gla...@ya...>]

John Hughes escreveu:

> The problem is not screwing up hardware, it's being forced to restart 
> from scratch.  If you do your playing in a virtual environment you can 
> do stuff like:
> 
> 1. install debian sarge on a vm
> 2. on the host: cp --sparse=always vm-disk vm-disk-backup
> 3. mess up an install of OpenSSI
> 4. on the host: cp --sparse=always vm-disk-backup vm-disk
> 5. goto 3

You are right. I had to install Debian several times trying to make 
version 1.9.6 work at least in the init node.

I'm not proficient in QEMU. Could you point any good tutorial about it?

I tried several times to install 1.9.6 on Sarge, but I just can't 
install the kernel-image-2.6.11-ssi-686-smp. The error I received is:

Setting up kernel-image-2.6.11-ssi-686-smp (1.9.6.-5) ...
ldd: /cluster/lib/cfstab: No such file or directory
Failed to create initrd image.

Then some more errors regarding dependencies of packages related to openssi.

I tried to locate cfstab in the packages available by using apt-file, 
without results. I'm supposing such file or directory will be created 
dynamically.

I followed the setup manual (which has an error regarding the path of 
OpenSSI deb repositories (should end with a openssi-v1.9.6 instead of 
v2) and didn't installed any additional packages restrict of what 
openssi required. Just

apt-get update
apt-get dist-upgrade
apt-get install openssi

and nothing else. Configuration of apt was executed exactly was it is 
int the manual (except the URL of DEB repository).

I used two DVD images as package repositories and skipped the security 
updates from Debian during initial setup (getting those updates corrupts 
the install).

My doubt is: what I missing here?

Some points:
1 - My hardware is a AMD Sempron LE-1150, so I don't have multiple cores 
or processors in it.
2 - I executed the default install with Debian Sarge, which means the 
setup was executed with kernel 2.4.27-3-386

I event tried latter to install the Debian SMP kernel, but got the same 
error.

Should I install Debian with kernel 2.6 and try again?

Thank you,
Alceu

Re: [SSI-users] 2.6.14-smp kernel headers and sources

[Scott W. <sc...@sl...>]

> /*
>  * Define the maximum clusternode_t value actually supported, i.e. each
>  * subsystem must be able to manage/allocate for nodes 1 -
> NSC_MAX_NODE_VALUE.
>  * Should be a runtime value, but that requires more support not yet
>  * available to a) dynamically size all relevant data structures and b)
>  * make sure root node's value is passed to joining nodes, and
>  * supersedes their own.
>  * When changing this value, please be aware of the limits specified below.
>  * Setting this smaller saves quite a bit of memory.
>  */

> Is there a dynamical way to change the max nodes without having to
> re-compile the kernel again?

Perhaps, but the comment in the chunk of file you included claims
otherwise.  My money is on the comment.

I can't comment on how to successfully edit that file.

As for which CPUs you're targeting, that's a Linux config option.
Linux has an elaborate configuration system.  Read the README that
comes with the (in this case, modified) kernel sources.  You can edit
.config directly, or you can do 'make menuconfig' or 'make xconfig' or
various other things.  But you still want to read that README.  It's
straightforward once you learn the basic process.  I'm used to the BSD
system of kernel config files ;)

Cheers,
-scott

Re: [SSI-users] 2.6.14-smp kernel headers and sources

[Cumberland, L. <lon...@ni...>]

Hi All,

I found the problem.

It turns out that the problem was in the compile source configs in that I had changed the include/cluster/config.h file to increase the max number of nodes from 15 to 125:

(ORIGINAL) ----------------------------------------
#ifndef _CLUSTER_CONFIG_H
#define _CLUSTER_CONFIG_H

#include <linux/param.h>
#include <linux/threads.h>

/*
 * Define the maximum clusternode_t value actually supported, i.e. each
 * subsystem must be able to manage/allocate for nodes 1 - NSC_MAX_NODE_VALUE.
 * Should be a runtime value, but that requires more support not yet
 * available to a) dynamically size all relevant data structures and b)
 * make sure root node's value is passed to joining nodes, and
 * supersedes their own.
 * When changing this value, please be aware of the limits specified below.
 * Setting this smaller saves quite a bit of memory.
 */
/* #define NSC_MAX_NODE_VALUE  125 */ /* default */
#define NSC_MAX_NODE_VALUE  15

/*
 * Define the part of the pid_t reserved for clusternode_t values.
 * Needed regardless of VPROC support in order to generate NSC_NODE_T_RANGE_MAX
 */
#define NODESHIFT       16      /* used by VPROC */
//#define NODESHIFT     23      /* reserve 4 million PIDs per node */

/*
 * Derive the maximum valid clusternode_t value, used ONLY for data-type
 * range checking
 * The PID_MAX defined in threads.h provides a limit to the
 * number of nodes that can be operating at one time.
 */
#if defined(VPROC) || defined(CONFIG_CPID)
#define NSC_NODE_T_RANGE_MAX    (PID_MAX_LIMIT >> NODESHIFT)

#if NSC_MAX_NODE_VALUE > NSC_NODE_T_RANGE_MAX
        #error "NSC_MAX_NODE_VALUE is too large to fit into pid number"
#endif
#endif

#define MAXLOCPID       ((1<<NODESHIFT)-1)  /* number at which pids recycle */
#define LAST_DAEMON_PID 300     /* RESERVED_PIDS */

#define CLUSTER_IFCONFIG_SZ     64
#define CLUSTER_CLMSINFO_SZ     256
#define CLUSTER_ICSROUTE_SZ     64

#endif /* !_CLUSTER_CONFIG_H */
--------------------------------------------------------

When I made the change, the system just crashed out the nodes while booting and I am not really sure why.

The fix, was to set the values back to the default settings like above.

I will try again to make a smaller adjustment to something like 30 nodes or something to see if that works as I had tried 125 and created the crash on the nodes.

Is there a dynamical way to change the max nodes without having to re-compile the kernel again?

Thanks and have a great day,
Lonnie Cumberland, Prof.
Physicist
 
> -----Original Message-----
> From: Cumberland, Lonnie
> Sent: Wednesday, August 18, 2010 12:57 PM
> To: Cumberland, Lonnie; John Hughes; Mulyadi Santosa
> Cc: Openssi users
> Subject: RE: [SSI-users] 2.6.14-smp kernel headers and sources
> 
> Hello All,
> 
> Well, after testing a number of different things, it turns out that the
> main node seems to be running great and even the fuse module is
> working, but that the other nodes are not coming online. They seem to
> get the kernel, boot the kernel and then crash out.
> 
> Thanks and have a great day,
> Lonnie Cumberland, Prof.
> Physicist
> 
> 
> > -----Original Message-----
> > From: Cumberland, Lonnie [mailto:lon...@ni...]
> > Sent: Wednesday, August 18, 2010 10:18 AM
> > To: John Hughes; Mulyadi Santosa
> > Cc: Openssi users
> > Subject: Re: [SSI-users] 2.6.14-smp kernel headers and sources
> >
> > Hello All,
> >
> > Well, there is good news and bad news.
> >
> > The good news is that the compile went well although I did not know
> how
> > to get the "make" commandline switches to SMP and i686 optizimations.
> >
> > The bad news is that even though the kernel seems to boot ok on the
> > main node, the other nodes do not seems to complete the booting
> > properly and crash out after tftp send over the new kernel which I
> put
> > into place via "ssi-ksync".
> >
> > There was a document on the OpenSSI website that said to do:
> >
> > # make oldconfig  		(by using the .config that was previously
> > set up)
> > # make dep        		(the compile reported that this was
> > unnecessary now)
> > # make bzImage    		(this went fine)
> > # make modules    		(this went fine)
> > # make modules_install    	(this went fine)
> >
> > # cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.14_ssi  (this went
> well)
> >
> > # mkinitrd --cfs /boot/initrd-2.6.14_ssi.img  2.6.14__ssi   (PROBLEMS
> > HERE: /usr/sbin/mkinitrd: unrecognized option `--cfs')
> >
> > Instead, I did:
> >
> > # mkinitrd -o /boot/initrd-2.6.14_ssi.img  2.6.14__ssi  (since I did
> > this in the install and it went well)
> >
> > But still the other nodes do not seem to come online.
> >
> > Any ideas on how to fix this?
> >
> > Thanks and have a great day,
> > Lonnie Cumberland, Prof.
> > Physicist
> >
> > > -----Original Message-----
> > > From: John Hughes [mailto:jo...@Ca...]
> > > Sent: Wednesday, August 18, 2010 7:34 AM
> > > To: Mulyadi Santosa
> > > Cc: Cumberland, Lonnie; Openssi users
> > > Subject: Re: [SSI-users] 2.6.14-smp kernel headers and sources
> > >
> > > Mulyadi Santosa wrote:
> > > > On Wed, Aug 18, 2010 at 05:42, Cumberland, Lonnie
> > > > <lon...@ni...> wrote:
> > > >
> > > >> I'll look to see what version I have tomorrow morning.
> > > >>
> > > >> Do I have to remove the whole 4.0 version if that is the problem
> > and
> > > install either 3.4 or 3.5 as you mentioned?
> > > >>
> > > >
> > > > Nope, in Fedora/RHEL, this is usually called gcc-compat or
> compat-
> > gcc
> > > > to refer to the "old" gcc. So for example, if Fedora 5 provides
> gcc
> > > > 3.x and 4.x, the 3.x is installed by gcc-compat. Thus, what you
> > need
> > > > to remove the gcc package (but not the compat one).
> > > >
> > > On Debian just install the gcc-3.4 package.
> > >
> > > apt-get install gcc-3.4
> > >
> >
> >
> > ---------------------------------------------------------------------
> --
> > -------
> > This SF.net email is sponsored by
> >
> > Make an app they can't live without
> > Enter the BlackBerry Developer Challenge
> > http://p.sf.net/sfu/RIM-dev2dev
> > _______________________________________________
> > Ssic-linux-users mailing list
> > Ssi...@li...
> > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users