On 08/07/2014 02:52 PM, Gordan Bobic wrote:
On 08/07/2014 06:21 PM, Robert Moskowitz wrote:
So with some care, I have a card booted into Redsleeve, but access only
from the console.
Monitor is showing some startup messages, but no login prompt. Mouse is
active and input works, but nothing seems to be listening.
Network is up, but not sshd:
# service sshd status
sshd: unrecognized service
yum install openssh-server
# yum install openssh-server
rsel6 | 3.8 kB 00:00
rsel6/primary_db | 3.1 MB 00:43
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package openssh-server.armv5tel 0:5.3p1-52.el6.2 will be installed
--> Processing Dependency: openssh = 5.3p1-52.el6.2 for package:
openssh-server-5.3p1-52.el6.2.armv5tel
--> Finished Dependency Resolution
Error: Package: openssh-server-5.3p1-52.el6.2.armv5tel (rsel6)
Requires: openssh = 5.3p1-52.el6.2
Installed: openssh-5.3p1-84.1.el6.armv5tel (installed)
openssh = 5.3p1-84.1.el6
Available: openssh-5.3p1-52.el6.2.armv5tel (rsel6)
openssh = 5.3p1-52.el6.2
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Did I get a wrong tar? Not the armv7, but armv5? Oops?
But not having sshd in minimal? Strange, but then if I am mismatched
on armv then that might explain it.
I did do those ln commands:
ln -s /run/media/rgm/rootfs/etc/init.d/sshd
/run/media/rgm/rootfs/etc/rc3.d/S55sshd
ln -s /run/media/rgm/rootfs/etc/init.d/sshd
/run/media/rgm/rootfs/etc/rc5.d/S55sshd
but no sshd.
Probably not installed in the minimal rootfs. See above.
The uboot partition is not mounted (your comment about Chromebook using
a uboot is not supprising as I have been told it also uses the Allwinner
A20 soc and thus SunXi).
Samsung Chromebook uses the Samsung Exynos SoC, not the Allwinner.
uboot partition is not mountable, this is normal.
There was a thread on fedora-arm or cubieboard lists, and I just must
have switched which chromebook. Never mind.
and the label I gave the rootfs partition does not seem to be
recognized:
# df -h
Filesystem Size Used Avail Use% Mounted on
UUID=33de6a91-2289-4ec7-9703-2b03a9d51725
13G 1.8G 11G 15% /
tmpfs 494M 152K 493M 1% /dev/shm
You will need to disect the uboot image and work out what it is
picking the rootfs by. Since you are getting a bootable system,
whatever it is using seems to be working.
Scary stuff, for me.
I need a good way to create the partitions on the card that line up
properly on 'cylinder boundaries':
# fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 15.6 GB, 15560867840 bytes
4 heads, 16 sectors/track, 474880 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000cd80a
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 33 16416 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/mmcblk0p2 16417 49184 1048576 82 Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/mmcblk0p3 49185 465184 13312000 83 Linux
Partition 3 does not end on cylinder boundary.
I used gparted on my F20 notebook. I need some 'nice' command lines to
lay down the partitions and format them. No experience on this, pointers
to some cookbook instructions would be appreciated.
Chromebook instructions:
http://wiki.redsleeve.org/index.php/Chromebook
I did look at it, I will again.
My preference is for gdisk, mainly because of 20 years experience with
fdisk, and gdisk is very similar, whereas parted is both fundamentally
different and lacking some of the functionality.
Perhaps what I am looking for.
Attached is the firstboot console capture:
[...]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: mount: special device
UUID=2cb94397-dc57-4276-bd81-0f30170f8cc1 does not exist
[FAILED]
Check your fstab and make sure the UUID specified there matches the
one on the relevant file system this is referring to.
ooh, most likely wrong. Afterall, the fstab is from a F19 build and
this is a 'clean' separate build so of course it will have different UUIDs.
Red Sleeve Enterprise Linux release 6.1 (Leap)
Kernel 3.4.61.sun7i+ on an armv7l
redsleeve login: root
Password:
Looks good! :)
First solid step.
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
