On 28.10.2012, at 22:27, Peter Czanik <pczanik@fang.fa.gau.hu> wrote:
On 10/28/2012 10:02 PM, Alexander Graf wrote:
On 28.10.2012, at 21:56, Peter Czanik <pczanik@fang.fa.gau.hu> wrote:
On 10/28/2012 09:52 PM, Alexander Graf wrote:
On 28.10.2012, at 22:28, Peter Czanik <pczanik@fang.fa.gau.hu> wrote:
On 10/28/2012 08:59 PM, Alexander Graf wrote:
On 28.10.2012, at 20:53, Peter Czanik wrote:
> Hello, > > On 10/27/2012 12:31 PM, Dirk Müller wrote: >> We've personally tested some of the variations, but not all of them. We'd like >> to get more feedback about it. > Finally I have my EFIKA MX smarttop unpacked. Of course I gave it a try with http://download.opensuse.org/ports/armv7hl/distribution/12.2-untested/applia... > My problem is, that no matter what's in boot.scr, the last message I see coming from the serial port is: > [...] > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > And nothing more. Does anybody has a workaround/fix for it? Oh? That sounds bad. Can you try to manually call
setenv bootargs console=ttymxc0,115200
before the boot script gets executed?a Just tested, it did not seem to change anything :-( I also tried to rewrite boot.scr based on what comes with the original Ubuntu image, but still the same... Odd. Do you have a JTAG around and could dump log_buf of the running machine? No, just the serial dongle... Phew. I wonder what's going wrong really. It's either a broken default cmdline or a really early kernel oops or I was being stupid and made the console driver a module again ;).
It could be, as even explicitly setting console and root in bootargs does not seem to help...
I also tried now the kernel/initrd from Ubuntu, but for some reason it can't find init (asks to add init= to boot arguments...). Is it because of systemd? Systemd still provides the same binary name. It's probably because the kernel is searching at the wrong partition.
Are you using mmcblk0p2?
Or rather can't find it even if it's there. Looking a bit more at boot messages with the Ubuntu kernel reveals, that the device should be there:
[...] [ 3.505966] mmc0: new high speed SDHC card at address 1234 [ 3.511954] mmcblk0: mmc0:1234 SA04G 3.68 GiB [ 3.516624] mmcblk0: p1 p2 [ 3.522175] pmic_rtc pmic_rtc.1: setting system clock to 2012-10-28 21:17:23 UTC (1351459043) [ 3.530827] Freeing init memory: 148K Loading, please wait... [ 3.652396] udev[520]: starting version 163 Begin: Loading essential drivers ... [ 4.815158] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. mount: mounting /dev/mmcblk0p2 on /root failed: No such device
Could you try an ls -la /dev in the ubuntu emergency initrd shell? But really, we should rather try to get this to work with our kernel. Does the Factory image work? Alex
Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg.
BusyBox v1.15.3 (Ubuntu 1:1.15.3-1ubuntu5) built-in shell (ash) Enter 'help' for a list of built-in commands.
(initramfs)
Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org