Salut,
Am ajuns acasa si, fiind in fata calculatorului, pot fi mai explicit.
Initial, kernel-ul era /vmlinuz (symlink la /boot/vmlinuz-2.4.18-sun4u).
Dupa ce am instalat 2.4.24, /vmlinuz a devenit /vmlinuz.old si /vmlinuz
nou este symlink la /boot/vmlinuz-2.4.24-sparc64.
/etc/silo.conf original
timeout=50
partition=1
root=/dev/sda4
read-only
image=/vmlinuz
label=linux
/etc/silo.conf modificat de mine
timeout=50
partition=1
root=/dev/sda4
read-only
image=/vmlinuz
label=2.4.24
image=/vmlinuz.old
label=2.4.18
am rulat silo
=== cut here ===
bobita:~# silo
/etc/silo.conf appears to be valid
bobita:~#
=== and here ===
si, la reboot, selectez 2.4.24, iar el imi booteaza tot 2.4.18-ul...
daca modific in /etc/silo.conf si ii zic
image=/boot/vmlinuz-2.4.24-sparc64 in loc de 2.4.24, zice asa:
=== cut here ===
screen not found.
Can't open input device.
Keyboard not present. Using ttya for input and output.
Sun Ultra 1 SBus (UltraSPARC 167MHz), No Keyboard
OpenBoot 3.5, 128 MB memory installed, Serial #8830465.
Ethernet address 8:0:20:86:be:1, Host ID: 8086be01.
Rebooting with command: boot
Boot device: disk File and args:
SILO boot:
2.4.24 2.4.18
boot: 2.4.24
Cannot find /boot/vmlinuz-2.4.24-sparc64 (Unknown ext2 error)
Image not found.... try again
boot: 2.4.18
Cannot find /vmlinuz.old (Unknown ext2 error)
Image not found.... try again
boot:
=== and here ===
insa pot sa ii zic /vmlinux si booteaza 2.4.18-ul :(
Cam atat...
Sorin CONSTANTINESCU wrote:
> Salut,
>
> Am un Sun ULTRASPARC1 pe care am pus Debian. Din cauza unui bug al
> driverului de HME (cand nu mai am activitate in retea, sun-ul
> crashuieste si intra in OpenPROM), vreau sa fac upgrade de kernel de la
> 2.4.18 la ceva mai recent, poate chiar in 2.6.
>
> Modific silo.conf, adaug un alt "image", rulez silo, rebootez, dar nu
> poate sa imi booteze imaginea noua, eroarea fiind ca nu imi poate gasi
> acel kernel. Mentionez ca amn verificat calea de mai multe ori. In
> schimb, poate sa imi booteze 1/vmlinux chiar daca nu il mai am in lista
> cu imagini.
>
> Am tot cautat pe net cum sa adaug un nou kernel in silo si pasii erau 3:
>
> 1) editare silo.conf
> 2) rulare silo
> 3) reboot
>
> La mine nu merge :( Daca a mai trecut careva prin chestia asta, astept
> un raspuns.
>
> Mersi,
--
Sorin CONSTANTINESCU
[EMAIL PROTECTED]
Linux Registered User #222086
---
Detalii despre listele noastre de mail: http://www.lug.ro/