Hello,
I have two SS5, one as a "pizza box" and a laptop. I have compiled the
2.4.16 and 17pre8 kernels on the both.
On the first station, I have :
bertrand@morgane:/boot$ ls -l vmlinuz-2.4.16
-rwxr-xr-x 1 root root 2134444 Nov 30 10:47 vmlinuz-2.4.16
bertrand@morgane:/boot$ cat /proc/cpuinfo
cpu : Fujitsu MB86904
fpu : Lsi Logic/Meiko L64804 or compatible
promlib : Version 3 Revision 2
prom : 2.15
type : sun4m
ncpus probed : 1
ncpus active : 1
BogoMips : 109.36
MMU type : Fujitsu Swift
contexts : 256
nocache total : 1048576
nocache used : 95744
bertrand@morgane:/boot$ silo -V
SILO version 1.2.4
and on the second :
Root Kepler:[/boot] > ls -l vmlinuz-2.4.17pre8
-rwxr-xr-x 1 root root 1079077 Dec 13 15:11 vmlinuz-2.4.17pre8
Root Kepler:[/boot] > cat /proc/cpuinfo
cpu : Fujitsu MB86904
fpu : Lsi Logic/Meiko L64804 or compatible
promlib : Version 3 Revision 2
prom : 2.15
type : sun4m
ncpus probed : 1
ncpus active : 1
BogoMips : 84.78
MMU type : Fujitsu Swift
invall : 0
invmm : 0
invrnge : 0
invpg : 0
contexts : 256
Root Kepler:[/boot] > silo -V
SILO version 1.2.4
The kernel on the second station seems to be smaller than the first
kernel used on the first station. The bootprom are the same, but when I
try to boot, silo returns on the secon station that the kernel is too
big. I don't understand where is the trouble.
I have tried a uncompressed kernel, but the result is the same.
Thanks in advance,
JKB
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:26 EST