Re: Alcor installation and kernels etc
Paul Slootman wrote,
:On Wed 25 Mar 1998, Tan Wee Yeh wrote:
:
:> I also tried to compile the kernel for the system but failed
:> in all attempts... 2.0.33 compiles but hangs the system...
:> the gzipped version unzips but stays there. The development
:
:Did you build the gzipped version with "make boot" ? Simply gzipping the
:vmlinux in the base directory doesn't work, as I found out :-) Use
:"make boot", and then use the arch/alpha/boot/vmlinux.gz image.
Ouch.. I gzipped the binary :PP. Anyway, I tried the
compilation again after installing gcc2.90.26 (egcs). Now,
it won't link properly:(. The errors occur in the linking
as shown below.
ld -static -Ttext 0xfffffc0000310000 -N \
arch/alpha/kernel/head.o init/main.o init/version.o \
arch/alpha/kernel/kernel.o arch/alpha/mm/mm.o \
kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o net/network.a \
fs/filesystems.a drivers/block/block.a drivers/char/char.a \
drivers/net/net.a drivers/scsi/scsi.a drivers/pci/pci.a \
/usr/src/kernel-source-2.0.33/arch/alpha/math-emu/math-emu.a \
/usr/src/kernel-source-2.0.33/arch/alpha/lib/lib.a \
/usr/src/kernel-source-2.0.33/lib/lib.a \
/usr/src/kernel-source-2.0.33/arch/alpha/lib/lib.a \
-o vmlinux
Errors seem to be located around the msdosfs supports since
taking them out works... Compiling the fatfs as modules
gives problems when loading:
prata# insmod fat.o
fat.o: unresolved symbol load_nls
fat.o: unresolved symbol load_nls_default
fat.o: unresolved symbol unload_nls
fat.o: unresolved symbol utf8_wcstombs
Any ideas??
Also, the problem with the alignment traps only occur when I
up the tulip cards. There are 2 devices here, eth0 and
eth1... the system default eth0 has no problem (possibly due
to that the card is not connected). Once I up eth1, the
kernel messages starts appearing...
:> kernels (2.1.85 and 2.1.90) wouldn't compile at all. I
:
:AFAIK that's a compiler problem, I couldn't compile 2.1.87 either at
:first, but with the snapshot built by Guenther (I think?) it compiles
:all the way through. I haven't tried out the latest "official" gcc yet,
:however.
That's what I tried after reading one of the Feb articles
from the list archive. Unfortunately, the error remains:
gcc -D__KERNEL__ -I/usr/src/linux-2.1.87/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -D__SMP__ -pipe
-mno-fp-regs -ffixed-8 -c -o init/main.o init/main.c
In file included from init/main.c:17:
/usr/src/linux-2.1.87/include/linux/sched.h:107: parse error
before `tasklist_lock'
/usr/src/linux-2.1.87/include/linux/sched.h:107: warning:
type defaults to `int' in declaration of `tasklist_lock'
/usr/src/linux-2.1.87/include/linux/sched.h:107: warning:
data definition has no type or storage class
In file included from init/main.c:17:
/usr/src/linux-2.1.87/include/linux/sched.h:598: parse error
before `waitqueue_lock'
/usr/src/linux-2.1.87/include/linux/sched.h:598: warning:
type defaults to `int' in declaration of `waitqueue_lock'
/usr/src/linux-2.1.87/include/linux/sched.h:598: warning:
data definition has no type or storage class
/usr/src/linux-2.1.87/include/linux/sched.h: In function
`add_wait_queue':
/usr/src/linux-2.1.87/include/linux/sched.h:604: warning:
implicit declaration of function `write_lock_irqsave'
/usr/src/linux-2.1.87/include/linux/sched.h:606: warning:
implicit declaration of function `write_unlock_irqrestore'
make: *** [init/main.o] Error 1
The same error occured with 2.1.90.
:I have an XLT with a Matrox Millenium, and it works fine. Very fast.
:I use 3.3.1 from hamm and X works fine (as long as you don't try > 16bpp).
Why's that?? Any experience with 3.3.2 (w/ matrox II
support? I'm quite keen on getting it.. maybe this Saturday
:PP.
Just me,
Wire ...
--
Tan Wee Yeh wytan@post1.com tanweeye@iscs.nus.sg
For PGP public key : finger -l tanweeye@fingerhost.nus.sg
PGP fingerprint = EC A6 98 25 5B D9 38 40 74 BC 0C C9 0F 81 BE 92
--
--
To UNSUBSCRIBE, email to debian-alpha-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: