Unfortunately, that is not an option on this machine.
This is a test bed environment. It has multiple distros on it. If I
let Trustix autopartition, then I lose data.
I thought I had a hard drive problem, so I started doing a bunch of
changes, and am reinstalling portions of the system. It has, or will
have, SuSE 9.2, SuSE 9.3, Trustix 2.2, and I have a partition saved
and waiting for Trustix 3.0.
Interestingly, after changing some HD settings in BIOS and wiping the
partition table on the problem drive, I started getting some
installation errors with SuSE. I ended up having to use the SuSE
"Safe Mode" installation option (does things like apci=off apm=off
barrier=off idewait=50 ..... and a few other settings). Reinstall is
going fine right now.
If I don't run out of time today, then I'll go ahead and check the
Trustix 3 installation with the same Safe Mode settings from SuSE and
see what happens.
I'm beginning to wonder if the kernel is enabling a dma mode or
something similar that isn't really supported on my older hardware,
and that is causing the problem.
Thanks,
Greg
On May 29, 2005, at 4:45 AM, turker-cremis-imap wrote:
Hi,
I had almost exactly the same problem when I used Trustix a few
days ago...
The only solution to the problem was to wipe out every partition on
disk and
let Trustix to auto partition it. If the disk already partitioned
it seems
trustix 3.0RC1 fails to update partition data. It cannot even see
the first
partition and thus cannot boot with initrd.
It works fine though once the partitions are created by Trustix.
My machine is Pentium III 500 MHz Gateway.
Turker Dundar
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gregory S.
Youngblood
Sent: Sunday, 29 May 2005 4:13 PM
To: Trustix List
Subject: TSL 3.0 RC2 Installation stalls at partitioning
I tried to install Trustix 3.0 RC2
(trustix-3.0.200505251226.i586.iso) on an AMD K63-450 based system.
The install stalled with the EVMS progress bar at 20%. [Same thing,
partitioning step stalled, with Trustix 3.0 RC1.]
Here are the details (typed from notes taken during install, so typos
etc. are mine):
ASuS P5A Motherboard, AMD K63-450 processor
Warning message during boot:
Running hotplug
missing module shpcp
dmesg:
warning: unable to open an initial console
shpchp: acpi_chpchprm: \_SB_.PCI0 evaluate _BBN fail=0x5
shpchp:acpi_shpchprm: get_device PCI R007 HID fail 0x5
log:
ViperLog: Staring Module { partition }
Running Module in Gather Mode { partition}
Command Line { /usr/bin/env python /usr/viper/viper_partition/trustix-
partition-utilit.py --installer --gather --root=/tmp/target 2> /var/
tm/viper/logs/partition-gather-stderr.log }
<4> hdc: dma_intr: status 0x51 {DriveReady SeekComplete Error}
<4> hdc: dma_intr: error 0x84 {DriveStatus Error BadCRC}
<4> ide: failed opcode was: unknown
partition-gather-stderr.log:
EVMS Command Line Interpreter 2.5.2
DosSegMgr: Warning: Using an alternate geometry (Cylinders, Heads,
Sectors) for drive hdc.
The kernel reported drive geometry is: C=59554, H=16, S=63
The partition records report a geometry of C=59554, H=255, S=63
Using the alternate reported by the partition records.
====
The hard drives in this system are :
WDC AC26400B 6gig (hda)
Maxtor 53073H6 (hdc)
Maxtor 52049H4 (hdd)
hdb is an ATAPI 40x CD-Rom drive (with (U)DMA disabled, something
about blacklisted device).
All three HD report Cache flushing not supported.
I should also point out that this machine has previously had Trustix
2.1, SuSE 9.2, and SuSE 9.3 installed on it. And, I just installed
Trustix 2.2 on it after 3.0 failed. I had a very similar problem with
Trustix 3.0 RC1 previously. At one point I allowed it to
autopartition (3.0 RC1) to see if it would install, and it did, but
it would not boot.
If you need more detail, please let me know.
Thanks,
Greg
.
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss
