ssic-linux-users

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

[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] 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

[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...>]

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...>]

> - 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] 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

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

Hello again Scott,

Scott Walters escreveu:

> 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.

Ok, I just made some testing to grab the kernel boot messages. This will 
be a very long post, so I'm already asking the other subscribed users to 
  forgive me.

Boot 2.6.11-ssi-686-smp with the regular options:

<firstTry>
Linux version 2.6.11-ssi-686-smp (john@carbon) (gcc version 3.3.5 
(Debian 1:3.3.5-13)) #1 SMP Fri Jan 1 22:51:25 UTC 2010
BIOS-provided physical RAM map:
  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
  BIOS-e820: 0000000000100000 - 0000000037ee0000 (usable)
  BIOS-e820: 0000000037ee0000 - 0000000037ee3000 (ACPI NVS)
  BIOS-e820: 0000000037ee3000 - 0000000037ef0000 (ACPI data)
  BIOS-e820: 0000000037ef0000 - 0000000037f00000 (reserved)
  BIOS-e820: 0000000038000000 - 0000000040000000 (reserved)
  BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
894MB LOWMEM available.
found SMP MP-table at 000f3ac0
DMI 2.4 present.
Using APIC driver default
ACPI: PM-Timer IO Port: 0x1008
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:15 APIC version 16
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: BIOS IRQ0 pin2 override ignored.
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
Enabling APIC mode:  Flat.  Using 1 I/O APICs
ACPI: HPET id: 0x10de8201 base: 0xfeff0000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 40000000 (gap: 40000000:b0000000)
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro console=ttyS0,9660
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 897148k/916352k available (3677k kernel code, 18664k reserved, 
2235k data, 272k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
hpet0: at MMIO 0xfeff0000, IRQs 2, 8, 31
hpet0: 0ns tick, 3 32-bit timers
Using HPET for base-timer
Using HPET for gettimeofday
Detected 2009.646 MHz processor.
Using hpet for high-res timesource
kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights 
Reserved
kdb_cmd[0]: bpa panic_hook
Instruction(i) BP #0 at 0xc0127600 (panic_hook)
     is enabled globally adjust 1
kdb_cmd[1]: defcmd archkdb "" "First line arch debugging"
kdb_cmd[7]: defcmd archkdbcpu "" "archkdb with only tasks on cpus"
kdb_cmd[13]: defcmd archkdbshort "" "archkdb with less detailed backtrace"
kdb_cmd[19]: defcmd archkdbcommon "" "Common arch debugging"
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
VProc hash table entries: 32768 (order: 6, 262144 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
CPU0: AMD Sempron(tm) Processor LE-1150 stepping 01
Total of 1 processors activated (3973.12 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 pin1=0 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...  failed.
...trying to set up timer as Virtual Wire IRQ... failed.
...trying to set up timer as ExtINT IRQ... failed :(.
Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with 
apic=debug and send a report.  Then try booting with the 'noapic' option
Instruction(i) breakpoint #0 at 0xc0127600 (adjusted)
0xc0127600 panic_hook:         int3

Entering kdb (current=0xc1aa3aa0, pid 2) on processor 0 due to 
Breakpoint @ 0xc0127600
[0]kdb>
</firstTry>

Booting the same kernel, with apic=debug

<secondTry>
Linux version 2.6.11-ssi-686-smp (john@carbon) (gcc version 3.3.5 
(Debian 1:3.3.5-13)) #1 SMP Fri Jan 1 22:51:25 UTC 2010
BIOS-provided physical RAM map:
  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
  BIOS-e820: 0000000000100000 - 0000000037ee0000 (usable)
  BIOS-e820: 0000000037ee0000 - 0000000037ee3000 (ACPI NVS)
  BIOS-e820: 0000000037ee3000 - 0000000037ef0000 (ACPI data)
  BIOS-e820: 0000000037ef0000 - 0000000037f00000 (reserved)
  BIOS-e820: 0000000038000000 - 0000000040000000 (reserved)
  BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
894MB LOWMEM available.
found SMP MP-table at 000f3ac0
DMI 2.4 present.
Unknown genapic `apic=debug' specified.
Using APIC driver default
ACPI: PM-Timer IO Port: 0x1008
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:15 APIC version 16
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: BIOS IRQ0 pin2 override ignored.
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
Enabling APIC mode:  Flat.  Using 1 I/O APICs
ACPI: HPET id: 0x10de8201 base: 0xfeff0000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 40000000 (gap: 40000000:b0000000)
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro apic=debug console=ttyS0,9600
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 897148k/916352k available (3677k kernel code, 18664k reserved, 
2235k data, 272k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
hpet0: at MMIO 0xfeff0000, IRQs 2, 8, 31
hpet0: 0ns tick, 3 32-bit timers
Using HPET for base-timer
Using HPET for gettimeofday
Detected 2009.707 MHz processor.
Using hpet for high-res timesource
kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights 
Reserved
kdb_cmd[0]: bpa panic_hook
Instruction(i) BP #0 at 0xc0127600 (panic_hook)
     is enabled globally adjust 1
kdb_cmd[1]: defcmd archkdb "" "First line arch debugging"
kdb_cmd[7]: defcmd archkdbcpu "" "archkdb with only tasks on cpus"
kdb_cmd[13]: defcmd archkdbshort "" "archkdb with less detailed backtrace"
kdb_cmd[19]: defcmd archkdbcommon "" "Common arch debugging"
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
VProc hash table entries: 32768 (order: 6, 262144 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
CPU0: AMD Sempron(tm) Processor LE-1150 stepping 01
Getting VERSION: 80050010
Getting VERSION: 80050010
Getting ID: 0
Getting LVT0: 700
Getting LVT1: 400
enabled ExtINT on CPU#0
ESR value before enabling vector: 0x00000004  after: 0x00000000
Total of 1 processors activated (3973.12 BogoMIPS).
ENABLING IO-APIC IRQs
Synchronizing Arb IDs.
..TIMER: vector=0x31 pin1=0 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...  failed.
...trying to set up timer as Virtual Wire IRQ... failed.
...trying to set up timer as ExtINT IRQ... failed :(.
Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with 
apic=debug and send a report.  Then try booting with the 'noapic' option
Instruction(i) breakpoint #0 at 0xc0127600 (adjusted)
0xc0127600 panic_hook:         int3

Entering kdb (current=0xc1aa3aa0, pid 2) on processor 0 due to 
Breakpoint @ 0xc0127600
[0]kdb>
</secondTry>

Booting the same kernel, with "noapic" option:

<thirdTry>
Linux version 2.6.11-ssi-686-smp (john@carbon) (gcc version 3.3.5 
(Debian 1:3.3.5-13)) #1 SMP Fri Jan 1 22:51:25 UTC 2010
BIOS-provided physical RAM map:
  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
  BIOS-e820: 0000000000100000 - 0000000037ee0000 (usable)
  BIOS-e820: 0000000037ee0000 - 0000000037ee3000 (ACPI NVS)
  BIOS-e820: 0000000037ee3000 - 0000000037ef0000 (ACPI data)
  BIOS-e820: 0000000037ef0000 - 0000000037f00000 (reserved)
  BIOS-e820: 0000000038000000 - 0000000040000000 (reserved)
  BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
894MB LOWMEM available.
found SMP MP-table at 000f3ac0
DMI 2.4 present.
Using APIC driver default
ACPI: PM-Timer IO Port: 0x1008
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:15 APIC version 16
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: Skipping IOAPIC probe due to 'noapic' option.
ACPI: HPET id: 0x10de8201 base: 0xfeff0000
Using ACPI for processor (LAPIC) configuration information
Intel MultiProcessor Specification v1.4
     Virtual Wire compatibility mode.
OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
I/O APIC #4 Version 17 at 0xFEC00000.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Processors: 1
Allocating PCI resources starting at 40000000 (gap: 40000000:b0000000)
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro noapic console=ttyS0,9600
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 897148k/916352k available (3677k kernel code, 18664k reserved, 
2235k data, 272k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
hpet0: at MMIO 0xfeff0000, IRQs 2, 8, 31
hpet0: 0ns tick, 3 32-bit timers
Using HPET for base-timer
Using HPET for gettimeofday
Detected 2009.646 MHz processor.
Using hpet for high-res timesource
kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights 
Reserved
kdb_cmd[0]: bpa panic_hook
Instruction(i) BP #0 at 0xc0127600 (panic_hook)
     is enabled globally adjust 1
kdb_cmd[1]: defcmd archkdb "" "First line arch debugging"
kdb_cmd[7]: defcmd archkdbcpu "" "archkdb with only tasks on cpus"
kdb_cmd[13]: defcmd archkdbshort "" "archkdb with less detailed backtrace"
kdb_cmd[19]: defcmd archkdbcommon "" "Common arch debugging"
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
VProc hash table entries: 32768 (order: 6, 262144 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: setting ELCR to 0200 (from 8c20)
CPU0: AMD Sempron(tm) Processor LE-1150 stepping 01
Total of 1 processors activated (3973.12 BogoMIPS).
Brought up 1 CPUs
checking if image is initramfs...it isn't (bad gzip magic numbers); 
looks like an initrd
Freeing initrd memory: 1204k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 3.00 entry at 0xfa7a0, last bus=4
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20050211
     ACPI-0352: *** Error: Looking up [\_PR_.CPU0] in namespace, 
AE_NOT_FOUND
search_node f7ed9f00 start_node f7ed9f00 return_node 00000000
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: Transparent bridge - 0000:00:04.0
ACPI: PCI Interrupt Link [LNK1] (IRQs 5 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK2] (IRQs *5 7 9 10 11 14 15)
ACPI: PCI Interrupt Link [LNK3] (IRQs 5 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK4] (IRQs 5 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK5] (IRQs 5 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK6] (IRQs 5 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK7] (IRQs 5 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK8] (IRQs 5 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LIGP] (IRQs 5 7 9 10 *11 14 15)
ACPI: PCI Interrupt Link [LP2P] (IRQs 5 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs *5 7 9 10 11 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 5 7 9 10 11 14 *15)
ACPI: PCI Interrupt Link [LAZA] (IRQs 5 7 9 *10 11 14 15)
ACPI: PCI Interrupt Link [LPMU] (IRQs 5 7 9 10 *11 14 15)
ACPI: PCI Interrupt Link [LSMB] (IRQs 5 7 9 10 *11 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 5 7 9 *10 11 14 15)
ACPI: PCI Interrupt Link [LIDE] (IRQs 5 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSID] (IRQs 5 7 9 10 *11 14 15)
ACPI: PCI Interrupt Link [LFID] (IRQs 5 7 9 *10 11 14 15)
ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled.
ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
ACPI: PCI Interrupt Link [APC5] (IRQs 16) *0, disabled.
ACPI: PCI Interrupt Link [APC6] (IRQs 16) *0, disabled.
ACPI: PCI Interrupt Link [APC7] (IRQs 16) *0, disabled.
ACPI: PCI Interrupt Link [APC8] (IRQs 16) *0, disabled.
ACPI: PCI Interrupt Link [AIGP] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APMU] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [AAZA] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APSI] (IRQs 23) *0, disabled.
ACPI: PCI Interrupt Link [APSJ] (IRQs 23) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 13 devices
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
** PCI interrupts are no longer routed automatically.  If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device().  As a temporary
** workaround, the "pci=routeirq" argument restores the old
** behavior.  If this argument makes the device work again,
** please email the output of "lspci" to bjo...@hp...
** so I can fix the driver.
pnp: 00:00: ioport range 0x1000-0x107f could not be reserved
pnp: 00:00: ioport range 0x1080-0x10ff has been reserved
pnp: 00:00: ioport range 0x1400-0x147f has been reserved
pnp: 00:00: ioport range 0x1480-0x14ff could not be reserved
pnp: 00:00: ioport range 0x1800-0x187f has been reserved
pnp: 00:00: ioport range 0x1880-0x18ff has been reserved
pnp: 00:00: ioport range 0x2000-0x207f has been reserved
pnp: 00:00: ioport range 0x2080-0x20ff has been reserved
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1285185009.071:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
CFS server token hash table entries: 131072 (order: 7, 524288 bytes)
SSI Token Message hash table entries: 4096 (order: 3, 32768 bytes)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: Fan [FAN] (on)
     ACPI-0352: *** Error: Looking up [\_PR_.CPU0] in namespace, 
AE_NOT_FOUND
search_node f7ed9f00 start_node f7ed9f00 return_node 00000000
ACPI: Thermal Zone [THRM] (19 C)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
hpet_acpi_add: no address or irqs in _CRS
Linux agpgart interface v0.100 (c) Dave Jones
[drm] Initialized drm 1.0.0 20040925
ACPI: PS/2 Keyboard Controller [PS2K] at I/O 0x60, 0x64, irq 1
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 76 ports, IRQ sharing enabled
ÿttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hda: SAMSUNG SP0411N, ATA DISK drive
hdb: HL-DT-STDVDRRW GWA-4161B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 1024KiB
hda: 78242976 sectors (40060 MB) w/2048KiB Cache, CHS=16383/255/63
  hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 >
hdb: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
IPVS: Registered protocols (TCP, UDP, AH, ESP)
IPVS: Connection hash table configured (size=65536, memory=512Kbytes)
IPVS: ipvs loaded.
IPVS: [wlc] scheduler registered.
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
ACPI wakeup devices:
HUB0 XVR0 XVR1 XVR2 UAR1 USB0 USB2 AZAD MMAC
ACPI: (supports S0 S3 S4 S5)
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 1204KiB [1 disk] into ram disk... |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\done.
Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(1,0)
Instruction(i) breakpoint #0 at 0xc0127600 (adjusted)
0xc0127600 panic_hook:         int3

Entering kdb (current=0xc1aa3aa0, pid 2) on processor 0 due to 
Breakpoint @ 0xc0127600
[0]kdb>
</thirdTry>


That it. I'll give a try to Fedore 3 now.

Thanks in advance,
Alceu

Re: [SSI-users] initial setup for newbies

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

Hi Alceu,

Reading through all of that, the situation seems to be this:

APIC isn't supported and doesn't work.

Without APIC, it can't set up interrupts for the PCI controller.

Without the PCI controller, it can't find the harddrive controller or
harddrives.

The Fedora version of OpenSSI will attempt to install and boot exactly
the same kernel.  The kernel will fail in exactly the same way if run
on the same hardware.

Short of back-porting fixes from a newer version of Linux (if you can
figure out the closest working version) to the OpenSSI kernel, I don't
have any suggestions here.

I've had good luck with ASUS motherboards with AMD CPUs but I think
you previously said that you already had a bank of machines you wanted
to cluster.

Wish I had better news for ya.

Regards,
-scott