Re: classic & sparc2 install reports
Ben Collins writes:
> > eyra:~# ls -l /lib/modules
> > total 2
> > drwxr-xr-x 10 root root 1024 Apr 8 15:10 2.2.14
> > drwxr-xr-x 2 root root 1024 Apr 8 15:13 2.2.15-pre14
>
> This concerns me. Can you also send me:
>
> ls -l /
eyra:~# ls -l /
total 52
drwxr-xr-x 2 root root 0 Apr 10 17:53 -
drwxr-xr-x 2 root root 2048 Apr 10 08:35 bin
drwxr-xr-x 2 root root 1024 Apr 10 17:39 boot
drwxrwsr-x 2 root cdrom 1024 Mar 31 05:47 cdrom
drwxr-xr-x 3 root root 18432 Apr 10 17:53 dev
drwxr-xr-x 40 root root 3072 Apr 10 17:53 etc
drwxrwsr-x 2 root floppy 1024 Mar 31 05:47 floppy
drwxr-xr-x 3 root root 1024 Apr 10 10:58 home
drwxr-xr-x 2 root root 1024 Mar 31 05:47 initrd
drwxr-xr-x 4 root root 2048 Apr 10 09:03 lib
drwxr-xr-x 2 root root 12288 Apr 8 15:07 lost+found
dr-xr-xr-x 2 root root 1024 Apr 8 17:45 misc
drwxr-xr-x 3 root root 1024 Apr 8 17:45 mnt
dr-xr-xr-x 51 root root 0 Apr 10 17:52 proc
drwxr-xr-x 2 root root 1024 Apr 10 12:15 root
drwxr-xr-x 2 root root 2048 Apr 10 09:43 sbin
drwxrwxrwt 3 root root 1024 Apr 10 17:53 tmp
drwxr-xr-x 2 root root 0 Apr 10 17:53 users
drwxr-xr-x 14 root root 1024 Apr 8 16:14 usr
drwxr-xr-x 14 root root 1024 Apr 8 17:21 var
dr-xr-xr-x 2 root root 1024 Apr 10 11:56 yama
> cat /etc/silo.conf
eyra:~# cat /etc/silo.conf
partition=1
root=/dev/sdb1
timeout=100
image=/boot/vmlinuz
label=linux
read-only
Speaking of silo.conf, I should tell you I have lost a lot of time
after installing the system because silo won't boot (it report an ext2
error) and I can't find why. I finally use the rescue disk to boot and
enter linux root=/dev/hdb1 at the prompt. Then I was dropped into
dselect and can finish the istallation. Only when silo is upgraded and
it tells me that I don't have the link /boot/vmlinuz and whether I
want to create it, that I realise that I don't have this link, but
only a link /vmlinuz --> /boot/vmlinuz-2.2.14sun4cdm and this indeed
explains why silo won't boot before. I have now removed the link
/vmlinuz --> ... as it serves no purpose.
> uname -a
eyra:~# uname -a
Linux eyra 2.2.14 #1 Wed Mar 29 23:06:39 EST 2000 sparc unknown
> > 2) There was a file /boot/vmlinuz-2.2.14sun4cdm and the corresponding
> > system map. I have remove them, the present kernel is the result of
> > using apt-get upgrade.
>
> I doubt you got the kernel by doing an upgrade. The sun4cdm 2.2.14-2
> kernel is a new package name, so you had to specify it directly by doing
> apt-get install (or selecting it from dinstall). Try doing:
>
> apt-get --reinstall install kernel-image-2.2.14-sun4cdm
>
> Then reboot and see what happens (ignore the unresolved syms in the
> modules, it is a non-fatal error).
Well, actually it comes from running dselect just after the install. I
have selected the new kernel image and I know that it is installed since
the system have asked me if I want to go ahead and overwrite
/lib/module/2.2.14. After that I see that the old kernel is still
there so I remove it. Anyhow I just reinstall the
kernel-image-2.2.14-sun4cdm as you said and still get the same error
Warning: /boot/System.map-2-2-14 does not match kernel data
/users/{sun4c_unlockarea} {___f_mmu_unlockarea}
Warning: /boot/System.map-2-2-14 does not match kernel data
/-{sun4c_unlockarea} {___f_mmu_unlockarea}
(these seem to come from the starting of my autofs). Otherwise, I
launch ps, I get
eyra:~# ps
{sun4c_unlockarea} {___f_mmu_unlockarea}
Warning: /boot/System.map-2.2.14 does not match kernel data.
--
PHAM Dinh Tuan | e-mail: Dinh-Tuan.Pham@imag.fr
Laboratoire de Modelisation et Calcul | Tel: +33 4 76 51 44 23
BP 53, 38041 Grenoble cedex 9 (France) | Fax: +33 4 76 63 12 63
-----------------------------------------------------------------------
Reply to: