Brand new sheeva install not booting. Systemd[1] error?

This forum is for topics dealing with problems with software specifically in the ARMv5 repo.

Brand new sheeva install not booting. Systemd[1] error?

Postby danielpublic » Thu Dec 18, 2014 2:43 pm

Ok, so I installed anew my sheevaplug through the instructions and software, though I needed to make some changes to runme.php. You guys should really update the instructions, I had a hard time finding the howto fix.

I watched the process do it's thing through: sudo cu -s 115200 -l /dev/ttyUSB0

Boot output:
$this->bbcode_second_pass_code('', 'Connected.
512 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
SDHC found. Card desciption is:
Manufacturer: 0x1b, OEM "SM"
Product name: "00000", revision 1.0
Serial number: 164881900
Manufacturing date: 5/2012
CRC: 0x00, b0 = 0

2818684 bytes read
## Booting image at 00800000 ...
Image Name: Linux-2.6.39.2
Created: 2011-06-26 6:20:32 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2818620 Bytes = 2.7 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.39.2 (kelly@speedy) (gcc version 4.5.3 (PlugComputer G++ 20110530) ) #2 PREEMPT Sun Jun 26 00:20:28 MDT 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=5
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 513240k/513240k available, 11048k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xe0800000 - 0xfe800000 ( 480 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0030000 ( 160 kB)
.text : 0xc0030000 - 0xc055a5d4 (5290 kB)
.data : 0xc055c000 - 0xc0590328 ( 209 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptable hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Console: colour dummy device 80x30
Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
NET: Registered protocol family 16
Kirkwood: MV88F6281-A0, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
Switched to NOHz mode on CPU #0
FS-Cache: Loaded
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
FS-Cache: Netfs 'nfs' registered for caching
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4009, nTxLock = 32077
msgmni has been set to 1002
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 364 at 0x000002d80000
Bad eraseblock 365 at 0x000002da0000
Bad eraseblock 1358 at 0x00000a9c0000
Bad eraseblock 1389 at 0x00000ada0000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address 00:50:43:01:45:b5
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
registered taskstats version 1
rtc-mv rtc-mv: setting system clock to 2029-07-24 03:44:36 UTC (1879559076)
Waiting 5sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address b368
mmcblk0: mmc0:b368 00000 7.51 GiB
mmcblk0: p1 p2
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 160K
systemd[1]: systemd 217 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN )
systemd[1]: Detected architecture 'arm'.

Welcome to Arch Linux ARM!

systemd[1]: Inserted module 'autofs4'
NET: Registered protocol family 10
systemd[1]: Inserted module 'ipv6'
systemd[1]: Set hostname to <alarm>.
systemd[1]: Failed to create root cgroup hierarchy: Invalid argument
systemd[1]: Failed to allocate manager object: Invalid argument

')

Issue:
It doesnt simply boot so that I can login the first time...

Suggestions? :?:
I don't believe it aught to do this on stock new distro...

Thanks in advance!
danielpublic
 
Posts: 3
Joined: Thu Dec 18, 2014 2:28 pm

Re: Brand new sheeva install not booting. Systemd[1] error?

Postby WarheadsSE » Thu Dec 18, 2014 3:58 pm

$this->bbcode_second_pass_quote('', ' ') Image Name: Linux-2.6.39.2
Created: 2011-06-26 6:20:32 UTC
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Brand new sheeva install not booting. Systemd[1] error?

Postby danielpublic » Thu Dec 18, 2014 4:28 pm

Where can I download a more recent kernel?
[edit]I extracted the one in latest release and tried to toss it in there, but.. [/edit]
Can I just toss it in place on my SD-card?
[edit]nope it's to big[/edit]
Last edited by danielpublic on Fri Dec 19, 2014 6:58 am, edited 1 time in total.
danielpublic
 
Posts: 3
Joined: Thu Dec 18, 2014 2:28 pm

Re: Brand new sheeva install not booting. Systemd[1] error?

Postby Socaltom » Fri Dec 19, 2014 1:16 am

I don't have a sheeva plug, but if you downloaded the latest rootfs, shouldn't it have the proper kernel?
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: Brand new sheeva install not booting. Systemd[1] error?

Postby danielpublic » Fri Dec 19, 2014 7:08 am

Hi Tom.

I tried that yesterday, by resizing p1 (just for fun), but it complained about crc error if I remember correctly.
I also looked at the various config-files for the plug-installer to determine if there are any values that correlate to p1.
Might have missed something though.

Anyho, I'm going to first make two partitions by hand and extract the rootfs and put the kernel on p1.
Suppose plan B would be to put the archkernel on the install usbdrive and see if the script determine the size of p1.
danielpublic
 
Posts: 3
Joined: Thu Dec 18, 2014 2:28 pm


Return to ARMv5

Who is online

Users browsing this forum: No registered users and 11 guests