On Sun, June 3, 2012 4:15 pm, Andreas Färber wrote:
> Am 03.06.2012 10:10, schrieb Alexander Graf:
>>
>> On 03.06.2012, at 06:35, Andreas Färber wrote:
>>
>>> On the armStoneA8 board, using NBoot V14 and U-Boot, I'm trying to
boot the downstream 3.3.7 kernel (BSP V1.1) from SD with a LimeJeOS
rootfs on
>>> SD. I had to reconfigure the kernel with CONFIG_LBDAF to mount the
ext3[*] rootfs r/w. This is what I get now:
>>>
>>> [...]
>>> mmc0: new high speed SDHC card at address b368
>>> IPv6 over IPv4 tunneling driver
>>> mmcblk0: mmc0:b368 NCard 7.48 GiB
>>> NET: Registered protocol family 17
>>> can: controller area network core (rev 20090105 abi 8)
>>> mmcblk0: p1
>>> NET: Registered protocol family 29
>>> can: raw protocol (rev 20090105)
>>> can: broadcast manager protocol (rev 20090105 t)
>>> Registering the dns_resolver key type
>>> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev
2 s3c-rtc s3c64xx-rtc: setting system clock to 2000-01-01 00:00:00 UTC
(946684800)
>>> kjournald starting. Commit interval 5 seconds
>>> EXT3-fs (mmcblk0p1): using internal journal
>>> EXT3-fs (mmcblk0p1): recovery complete
>>> EXT3-fs (mmcblk0p1): mounted filesystem with ordered data mode VFS:
Mounted root (ext3 filesystem) on device 179:1.
>>> Freeing init memory: 148K
>>> Failed to mount /dev: No such device
>>>
>>> Our rootfs definitely contains /dev, so what is this complaining about?
>>
>> Please make sure that you have support for tmpfs and (if running w/o
initrd) devtmpfs in the kernel :).
>
> Thanks, found two devtmpfs options through search in menuconfig.
>
> Now I'm finally getting into the system but am seeing some failures
(reformatted for readability):
>
> Starting System Logging Service...
> Starting LSB: Purge old kernels...
> Starting LSB: Configure the localfs depending network interfaces...
Starting Login Service...
> Starting Permit User Sessions...
> Started Console System Startup Logging [ OK ]
Started LSB: Framebuffer setup [ OK ]
Failed to start System Logging Service [FAILED]
See 'systemctl status syslog.service' for details.
> Started LSB: Purge old kernels [ OK ]
Started Permit User Sessions [ OK ]
Starting Serial Getty on ttySAC0...
> Started Serial Getty on ttySAC0 [ OK ]
Starting Getty on tty1...
> Started Getty on tty1 [ OK ]
Starting D-Bus System Message Bus...
> Started D-Bus System Message Bus [ OK ]
Starting System Logging Service...
> Failed to start System Logging Service [FAILED]
See 'systemctl status syslog.service' for details.
> Starting System Logging Service...
> Started Login Service [ OK ]
Failed to start System Logging Service [FAILED]
See 'systemctl status syslog.service' for details.
> Starting System Logging Service...
> Failed to start System Logging Service [FAILED]
See 'systemctl status syslog.service' for details.
> Starting System Logging Service...
> Failed to start System Logging Service [FAILED]
See 'systemctl status syslog.service' for details.
> Starting System Logging Service...
> Failed to start System Logging Service [FAILED]
See 'systemctl status syslog.service' for details.
> Starting System Logging Service...
> Failed to start System Logging Service [FAILED]
See 'systemctl status syslog.service' for details.
>
>
> linux:~ # systemctl
> Failed to get D-Bus connection: No connection to service manager.
>
> But D-Bus seemed to have started "[ OK ]" above.
>
> linux:~ # pstree
> systemdââ¬âagetty
> ââconsole-kit-daeâââ64*[{console-kit-dae}]
> ââcron
> ââdbus-daemon
> ââdhcpcd
> ââloginâââbashâââpstree
> ââpolkitdâââ{polkitd}
> ââsshd
> ââsystemd-journal
> ââsystemd-logind
> ââudevdâââ2*[udevd]
>
> What could be going wrong here? More kernel options needed?
I've build a kernel for this board in :home:worldcitizen:armv7l
kernel-armstonea8 .
The config is also there.
I've tested it quite some time ago. I don't know if I saw these errors.
I use the kernel supplied by F&S Elektronik Systeme GmbH.
>
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF:
Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg --
Regards,
Joop.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
