I am trying to create a system using TSL3.0 on an embedded system, a
Soekris 4801 with a CF card as the hdd.
I have read a variety of posts and pages by others who have successfully
installed debian, and freebsd on these systems. I would like to use
TSL, however, for its advantages.
I wind up with problems as follows as my TSL system boots in the
embedded system:
TSL-initrd: Found root = /dev/evms/hda1
TSL-initrd: Running evms_activate
TSL-initrd: Mounting /dev/hda1 on /sysroot with no extra options.
mount: you must specify the filesystem type
TSL-initrd: ERROR: The root volume has not been properly mounted. Starting
TSL-initrd: ERROR: a shell. Please mount the root volume manually on the
TSL-initrd: ERROR: /sysroot directory. You can do this with the command:
TSL-initrd: ERROR: mount -o ro /dev/evms/Your_Root_Volume /sysroot
TSL-initrd: ERROR: When you exit the shell, I will attempt to continue
TSL-initrd: ERROR: the boot process.
/bin/dash: can't access tty; job control turned off
and then am not able to mount it as shown by the following:
# mount -o ro /dev/evms/hda1 /sysroot
can't create lock file /etc/mtab~771: Read-only file system (use -n flag
to override)
# mount -no ro /dev/evms/hda1 /sysroot
mount: you must specify the filesystem type
# mount -t ext3 -no ro /dev/evms/hda1 /sysroot
mount: special device /dev/evms/hda1 does not exist
#
I am not sure what to do now and am seeking advice. A full log of the
kernel boot is shown at the end of my note. My reading of the boot
"log" copied from the console suggests that the bios finds the MBR which
finds grub which then boots the kernel which then loads the initrd ...
So, any help would be appreciated. Perhaps my approach as described
below is wrong.
Thanks and regards to anyone helping this confused soul.
I created a new TSL3 system on a workstation and decided to create my CF
card filesystem from that workstation, so I used a CF-reader in the USB
port as the place to connect my CF card.
TSL recognizes the CF card as as sda device when connected to the
workstation.
I fdisk-ed the CF card for one partition marked bootable and with fstype
ext3.
I then mounted the cf-card at /mnt and did the following:
cd /; tar clSf - . | (cd /mnt; tar xpSf -) to copy all from the
/dev/hda1 partition in the workstation to the CF card.
I then cd to mount and add special commands to grub.conf to support the
console as ttyS0 and to ensure that fstab on the cfcard is correct.
grub.conf contains:
# grub.conf generated by viper.
# Note that you do not have to re run grub after making changes to this
file.
default=0
timeout=10
serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1
terminal serial
title Trustix Secure Linux (2.6.14.2-2tr)
root (hd0,0)
kernel /boot/vmlinuz-2.6.14.2-2tr ro root=/dev/hda1
ramdisk_size=8192 console=ttyS0,9600n8
initrd /boot/initrd-2.6.14.2-2tr.img
(note that my mail client has wrapped the kernel line).
fstab contains:
/dev/hda1 / ext3 defaults 1 1
none /proc proc defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
none /sys sysfs defaults 0 0
I also checked to make sure that the CF card contains an entry for
/dev/evms/hda1.
Here's what the console shows on boot:
Linux version 2.6.14.2-2tr ([EMAIL PROTECTED]) (gcc version
3.4.4 (Trust
ix)) #1 Tue Nov 15 11:02:20 GMT 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000008000000 (usable)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
128MB LOWMEM available.
DMI not present.
ACPI: Unable to locate RSDP
Allocating PCI resources starting at 10000000 (gap: 08000000:f7f00000)
Built 1 zonelists
Kernel command line: ro root=/dev/evms/hda1 ramdisk_size=8192
console=ttyS0,9600
n8
No local APIC present or hardware disabled
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Detected 266.663 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 123104k/131072k available (1857k kernel code, 7384k reserved,
567k data,
156k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 534.13 BogoMIPS
(lpj=267066)
Mount-cache hash table entries: 512
mtrr: v2.0 (20020519)
CPU: NSC Unknown stepping 01
Checking 'hlt' instruction... OK.
checking if image is initramfs...it isn't (bad gzip magic numbers);
looks like a
n initrd
Freeing initrd memory: 3184k freed
softlockup thread 0 started up.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.01 entry at 0xf7861, last bus=0
PCI: Using configuration type 1
ACPI: Subsystem revision 20050902
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Real Time Clock Driver v1.12
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: Can't read CTR while initializing i8042.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
mice: PS/2 mouse device common for all mice
logibm.c: Didn't find Logitech busmouse at 0x23c
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
NET: Registered protocol family 9
X.25 for Linux. Version 0.2 for Linux 2.1.15
Using IPI Shortcut mode
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 3184KiB [1 disk] into ram disk... done.
VFS: Mounted root (cramfs filesystem) readonly.
Running /linuxrc from Trustix Secure Linux initial ramdisk
TSL-initrd: Mounting /proc
TSL-initrd: Mounting /sys
TSL-initrd: Mounting tmpfs on /dev/evms
TSL-initrd: Mounting tmpfs on /var/lock
TSL-initrd: Loading modules
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.3
SCSI subsystem initialized
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
Linux agpgart interface v0.101 (c) Dave Jones
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: [EMAIL PROTECTED]
NET: Registered protocol family 10
Disabled Privacy Extensions on device c0326460(lo)
IPv6 over IPv4 tunneling driver
TSL-initrd: Found root = /dev/evms/hda1
TSL-initrd: Running evms_activate
TSL-initrd: Mounting /dev/evms/hda1 on /sysroot with no extra options.
mount: you must specify the filesystem type
TSL-initrd: ERROR: The root volume has not been properly mounted. Starting
TSL-initrd: ERROR: a shell. Please mount the root volume manually on the
TSL-initrd: ERROR: /sysroot directory. You can do this with the command:
TSL-initrd: ERROR: mount -o ro /dev/evms/Your_Root_Volume /sysroot
TSL-initrd: ERROR: When you exit the shell, I will attempt to continue
TSL-initrd: ERROR: the boot process.
/bin/dash: can't access tty; job control turned off
--
+-------------+
Bruce B. Platt
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss
