Unanswered topics | Active topics


Board index » »

All times are UTC-06:00



Post new topic  Reply to topic  Page 1 of 1
  [ 7 posts ] 
  Previous topic | Next topic 
Author Message
astrofos
PostPosted: Sat Feb 02, 2008 3:49 am 
Offline

Joined: Thu Mar 01, 2007 9:26 am
Posts: 13
Location: Greece
Hello I am trying to revive my Efika and setup debian linux.

My efika has attached:
*) hard disk
*) serial cable
*) ethernet cable

It does not have a video card. I am using minicom to operate the board and TFTP to boot the kernel.
Code:
boot eth:192.168.178.21 di_efika console=ttyPSC0
After the debian installer finishes successfully I try to boot with the following command:
Code:
boot eth:192.168.178.21 kernel_efika root=/dev/sda2 console=ttyPSC0
then I get to this point:
Code:
INIT: Entering runlevel: 2
Starting system log daemon: syslogd.
Starting kernel log daemon: klogd.
Starting portmap daemon...Already running..
Starting MTA: exim4.
Starting internet superserver: inetd.
Starting NFS common utilities: statd.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: crond.
after wich nothing happens.
Top
   
Reply with quote  
markos
PostPosted: Sat Feb 02, 2008 6:52 am 
Offline

Joined: Wed Oct 13, 2004 7:26 am
Posts: 348
Quote:
Hello I am trying to revive my Efika and setup debian linux.

My efika has attached:
*) hard disk
*) serial cable
*) ethernet cable

It does not have a video card. I am using minicom to operate the board and TFTP to boot the kernel.
Code:
boot eth:192.168.178.21 di_efika console=ttyPSC0
After the debian installer finishes successfully I try to boot with the following command:
Code:
boot eth:192.168.178.21 kernel_efika root=/dev/sda2 console=ttyPSC0
then I get to this point:
Code:
INIT: Entering runlevel: 2
Starting system log daemon: syslogd.
Starting kernel log daemon: klogd.
Starting portmap daemon...Already running..
Starting MTA: exim4.
Starting internet superserver: inetd.
Starting NFS common utilities: statd.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: crond.
after wich nothing happens.
do you by any chance have mingetty or fbgetty or sth similar installed? In order to be able to login to your system from a serial console mgetty or agetty is required. Apart from that, the system seems to boot fine and I can't think of another reason.

Konstantinos
Top
   
Reply with quote  
astrofos
 Post subject:
PostPosted: Sat Feb 02, 2008 7:08 am 
Offline

Joined: Thu Mar 01, 2007 9:26 am
Posts: 13
Location: Greece
Hi markos
Quote:
do you by any chance have mingetty or fbgetty or sth similar installed? In order to be able to login to your system from a serial console mgetty or agetty is required.
I just followed all the steps from the debian installer. I haven't done anything manually. This is the second time I am trying debian and I recall that this also happened and the first time. If I remember correctly then, I was told to use a video card because it was loading X by default? The problem is that now I don't have a compatible video card available.
Top
   
Reply with quote  
markos
 Post subject:
PostPosted: Sat Feb 02, 2008 8:24 am 
Offline

Joined: Wed Oct 13, 2004 7:26 am
Posts: 348
Quote:
Hi markos
Quote:
do you by any chance have mingetty or fbgetty or sth similar installed? In order to be able to login to your system from a serial console mgetty or agetty is required.
I just followed all the steps from the debian installer. I haven't done anything manually. This is the second time I am trying debian and I recall that this also happened and the first time. If I remember correctly then, I was told to use a video card because it was loading X by default? The problem is that now I don't have a compatible video card available.
Well, you could boot with "init=/bin/sh" option in the OF boot arguments, get access to the system and thus change/set the getty, stop X, etc. and then restart to a properly configured system. I've done it many times in similar situations.

Konstantinos
Top
   
Reply with quote  
astrofos
 Post subject:
PostPosted: Mon Feb 04, 2008 7:46 am 
Offline

Joined: Thu Mar 01, 2007 9:26 am
Posts: 13
Location: Greece
Quote:
Well, you could boot with "init=/bin/sh" option in the OF boot arguments, get access to the system and thus change/set the getty, stop X, etc. and then restart to a properly configured system.
That almost worked, I got access to a shell although with read only access to files. What do I have to do to get write access?
Top
   
Reply with quote  
markos
 Post subject:
PostPosted: Mon Feb 04, 2008 8:56 am 
Offline

Joined: Wed Oct 13, 2004 7:26 am
Posts: 348
Quote:
Quote:
Well, you could boot with "init=/bin/sh" option in the OF boot arguments, get access to the system and thus change/set the getty, stop X, etc. and then restart to a properly configured system.
That almost worked, I got access to a shell although with read only access to files. What do I have to do to get write access?
mount -o rw,remount /
Top
   
Reply with quote  
astrofos
 Post subject:
PostPosted: Tue Feb 05, 2008 2:49 am 
Offline

Joined: Thu Mar 01, 2007 9:26 am
Posts: 13
Location: Greece
thank you! my efika now works perfectly :D
Top
   
Reply with quote  
Display posts from previous:  Sort by  
Post new topic  Reply to topic  Page 1 of 1
  [ 7 posts ] 

Board index » »

All times are UTC-06:00

Who is online

Users browsing this forum: No registered users and 13 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
PowerDeveloper.org: Copyright © 2004-2012, Genesi USA, Inc. The Power Architecture and Power.org wordmarks and the Power and Power.org logos and related marks are trademarks and service marks licensed by Power.org.
All other names and trademarks used are property of their respective owners. Privacy Policy
Powered by phpBB® Forum Software © phpBB Group