On 2014-08-06 17:24, Robert Moskowitz wrote:
Well I built a card to boot, and booted. Looks like I forgot to turn
on capture for the serial console so I did not copy all the firstboot
stuff, but it failed. Video has a few messages displayer, and console
a lot more, but I did not capture that. Console is not accepting any
input; never gets to the login.
It sounds like the serial device isn't being listened on by a
getty.
Take a look here:
http://wiki.redsleeve.org/index.php/QNAP_TS-421#Serial_Console_for_Debugging_Only
and here:
http://wiki.redsleeve.org/index.php/QEMU#Booting_and_configuring_RS
Specifically to the files you might need for different serial
console device nodes.
I can ping the device, so the
ethernet is starting properly; I cannot ssh into the device: 'port 22;
connection refused'.
sshd probably isn't running by default.
Perhaps some of the problems come in that you are building a /boot
directory whereas the Cubieboard Fedora builds (19, 20, and pre-alpha
21) all make a separate uboot partition that has all the boot
information and an empty /boot directory in the root partition.
In which case you don't need anything to do with /boot, as long as
you copy the boot partition across. Chromebooks use a similar thing.
It was a pain to make this card. CP'ing the files I saved back to
firmware required a lot of 'y' to overwrite. there has to be a better
command than cp, but I am not that good to know such things. Even
deleting what was not needed was a bunch of 'rm -fr' commands.
I find tar handy for copying:
tar -cf - /path1 /path2 /path3 | tar -C /target/path -xf -
So attached is the console output for 2nd boot. Please advise what to
try next.
And perhaps a better way to build the card for testing.
It's more complex, but in a nutshell, you'll need your working
uboot partition (you'll have to dd that if you don't have
instructions on how to build one from scratch), and the partition
table to be the same as the working card (although partition
sizes can be different).
Then format the partitions appropriately, and use something
like the tar command above to copy the files. It should
be much quicker.
[kernel boot output]
Welcome to Red Sleeve Enterprise Linux
Starting udev: [ 8.620640] udevd (109): /proc/109/oom_adj is
deprecated, please use /proc/109/oom_score_adj instead.
[ OK ]
Setting hostname redsleeve: [ OK ]
Checking filesystems
Checking all file systems.
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
Entering non-interactive startup
Bringing up loopback interface: [ OK ]
Starting rpcbind: [ OK ]
Starting system message bus: [ OK ]
Setting network parameters... [ OK ]
Starting NetworkManager daemon: [ OK ]
modem-manager: ModemManager (version 0.4.0-3.git20100628.el6)
starting...
modem-manager: Loaded plugin Huawei
Starting NFS statd: modem-manager: Loaded plugin ZTE
modem-manager: Loaded plugin Ericsson MBM
modem-manager: Loaded plugin MotoC
modem-manager: Loaded plugin Gobi
modem-manager: Loaded plugin Option
modem-manager: Loaded plugin Novatel
modem-manager: Loaded plugin Generic
modem-manager: Loaded plugin Longcheer
modem-manager: Loaded plugin Sierra
modem-manager: Loaded plugin AnyData
modem-manager: Loaded plugin Option High-Speed
modem-manager: Loaded plugin SimTech
modem-manager: Loaded plugin Nokia
modem-manager: (tty/ttyS1): port's parent platform driver is not
whitelisted
modem-manager: (tty/ttyS2): port's parent platform driver is not
whitelisted
modem-manager: (tty/ttyS3): port's parent platform driver is not
whitelisted
modem-manager: (tty/ttyS0): port's parent platform driver is not
whitelisted
modem-manager: (net/eth0): port's parent platform driver is not
whitelisted
[ OK ]
Starting RPC idmapd: [ OK ]
Starting HAL daemon: [ OK ]
Retrigger failed udev events[ OK ]
Starting nscd: [ OK ]
dnsdomainname: Unknown host
Starting dnsmasq: [ OK ]
Starting ntpd: [ OK ]
Starting console mouse services: [ OK ]
Yup, as expected, sshd is not starting by default, and there is no
getty listening on the correct serial port for the serial console
login.
For getting the serial console to work, see suggestions above.
For getting sshd to be enabled by default, do:
ln -s /etc/init.d/sshd /etc/rc3.d/S55sshd
ln -s /etc/init.d/sshd /etc/rc5.d/S55sshd
That should get it starting in the appropriate runlevels.
Once you have it booting properly, you can use
chkconfig or ntsysv to enable/disable other services.
Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
