[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

booting on t1000

I've installed both squeeze and wheezy on sun t1000. With each installation, I have two odd issues:

I must manually intervene to make SILO boot the system:

Boot device: disk0  File and args:
SILO Version 1.4.14
boot: boot:

the system will just sit there seemingly forever if i do not press <enter> or enter Linux<enter>

What's causing SILO to not timeout and continue booting?

I've tried booting with and without the :3 appendage to my disk0 alias. that doesnt seem to be part of the issue. i've also tried setting timeout=0 in my silo.conf, but that didnt change anything either.

{0} ok printenv boot-device
boot-device =           disk0 disk1 net
{0} ok devalias disk0
disk0                    /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0:3
{0} ok devalias disk1
disk1                    /pci@7c0/pci@0/pci@8/scsi@2/disk@1,0:3

root@t1000:~# cat /boot/silo.conf

root@t1000:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs           66G  1.5G   61G   3% /
udev             10M     0   10M   0% /dev
tmpfs           808M  312K  808M   1% /run
/dev/md1         66G  1.5G   61G   3% /
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           2.0G     0  2.0G   0% /run/shm
/dev/sda1       183M   33M  141M  19% /boot
/dev/sdb1       183M   33M  141M  19% /bootm

The other problem is that the console seems to lock after I get a warning message:
[....] Starting MD monitoring service: mdadm --monitor. ok
[....] Starting deferred execution scheduler: atd. ok
[  154.046571] tg3 0001:03:04.0: eth0: Link is up at 100 Mbps, full duplex
[ 154.364365] tg3 0001:03:04.0: eth0: Flow control is on for TX and on for RX [....] Starting periodic command scheduler: cron[ 154.390176] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
. ok
[....] Starting OpenBSD Secure Shell server: sshd. ok
[....] Starting MTA: exim4. ok

I get no login prompt, pressing any keys including <enter> doesn't seem to affect the console. SSH works fine, though.

any ideas on either issue ?


Jeremy Kister

Reply to: