On Thu, 17 Nov 2005, Paolo Andretta wrote:
> A part the HW-RAID-1 problem (, now I have noticied another "little" problem;
> I can install the TSL 3.0 (used 20050708 and 20051021);
> Create SW Raid-1 volumes;
> Install the system;
> All Ok.
>
> The problem born when using swup --upgrade the kernel was updated.
> Next reboot fail: seems that the system can't access to modules.
>
> Tried rebuild the initrd
> Tried install manually the new kernel
> Tried follow on screen instructions (remount / volume)
> Tried hints from evms.sf.net:
> mount -o remount,rw /
> /usr/sbin/evms_activate
>
> I think can be an evms related problem, but I am not expert on evms, so
> ...
> Same problem a week ago with kernel 2.6.14-1 and today with kernel
> 2.6.14.1-2 (smp and "standard")
>
> I have tried a similar installation under vmware: no problem.
> I haven't tested using a CD that have the last kernel 2.6.14.* because
> last iso that there is (or that I have found), is the 20051021 that have
> the working 2.6.13.4-1.
>
> N.B.: booting with the 2.6.13.4-1 works.
Updates:
- Same problem if I use a single disk, so it isn't a problem related to RAID ...
- No differences if manual or automatic partitioning disk ...
- Recompiling kernel and modules give no differences ...
Question: In the past, I have noticied that when there was packages
updated also the .iso images was updated. In this case there was at last 2
kernel upgrades, but the iso still is the 20051021. There is a reason?
Or can I find it in a no "standard" site?
My idea was testing also a new iso that have the 2.6.14.* kernel to see if
the problem is still present on a fresh boot or only updating the kernel.
Thanks.
--
Saluti,
Paolo
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss
