Arch on zt-180 v2

Install Arch Linux ARM on other devices.

Arch on zt-180 v2

Postby ubis » Mon Nov 05, 2012 6:06 pm

Hello,
i'm trying to boot arch on zt-180 v2, which have 1GHz ARMv6 CPU. Firstly, compiled linux 3.4 arm kernel from kernel.org. Used ArchLinuxARM-oxnas-latest.tar.gz package. Extracted at /dev/mmcblk1p1 (it's NAND).

After extract, used busybox mdev -s command to create files in /dev such as mmcblk0, mmcblk1, tty1... and so on.
Rebooted tablet, some warnings appeared and arch booted fine.

Logged in as root, typed reboot command, tablet rebooted and, can't boot anymore arch... Booting stuck on
$this->bbcode_second_pass_code('', 'Waiting for UDev uevents to be processed [BUSY]')

And the thing is, after reboot logs doesn't change, they were same as first successfull boot. I don't know where the problem is :(

My logs, from successfull boot:

auth.log:
$this->bbcode_second_pass_code('', 'Dec 31 18:00:41 alarm agetty[2475]: /dev/ttyS0: not a character device
Dec 31 18:00:47 alarm login: pam_unix(login:account): account root has password changed in future
Dec 31 18:00:47 alarm login: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Dec 31 18:00:47 alarm login: ROOT LOGIN ON tty1
Dec 31 18:00:51 alarm agetty[2488]: /dev/ttyS0: not a character device
Dec 31 18:01:01 alarm agetty[2489]: /dev/ttyS0: not a character device
Dec 31 18:01:11 alarm agetty[2492]: /dev/ttyS0: not a character device
Dec 31 18:01:21 alarm agetty[2495]: /dev/ttyS0: not a character device
Dec 31 18:01:31 alarm agetty[2496]: /dev/ttyS0: not a character device
Dec 31 18:01:42 alarm agetty[2499]: /dev/ttyS0: not a character device
Dec 31 18:01:52 alarm agetty[2502]: /dev/ttyS0: not a character device
Dec 31 18:02:02 alarm agetty[2503]: /dev/ttyS0: not a character device
Dec 31 18:02:12 alarm agetty[2506]: /dev/ttyS0: not a character device
Dec 31 18:02:22 alarm agetty[2509]: /dev/ttyS0: not a character device
Dec 31 18:02:32 alarm agetty[2510]: /dev/ttyS0: not a character device
Dec 31 18:02:42 alarm agetty[2513]: /dev/ttyS0: not a character device
Dec 31 18:02:52 alarm agetty[2518]: /dev/ttyS0: not a character device
Dec 31 18:02:53 alarm login: pam_unix(login:session): session closed for user root')

boot:
$this->bbcode_second_pass_code('', 'Wed Dec 31 18:00:41 1969: :: Mounting Root Read-Only [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Adjusting system time and setting kernel timezone [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Starting UDev Daemon [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Triggering UDev uevents [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Loading User-specified Modules [BUSY] [FAIL]
Wed Dec 31 18:00:41 1969: :: Waiting for UDev uevents to be processed [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Configuring Virtual Consoles [BUSY] %G [DONE]
Wed Dec 31 18:00:41 1969: :: Bringing up loopback interface [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Unlocking encrypted volumes [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Checking Filesystems [BUSY] /etc/rc.sysinit: line 100: /dev/stdout: Read-only file system
Wed Dec 31 18:00:41 1969: [DONE]
Wed Dec 31 18:00:41 1969: :: Remounting Root and API filesystems [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Mounting Local Filesystems [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Activating Swap [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Configuring Time Zone [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Initializing Random Seed [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Removing Leftover Files [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Setting Hostname: alarm [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Saving dmesg Log [BUSY] install: cannot stat ‘/dev/fd/63’: No such file or directory
Wed Dec 31 18:00:41 1969: [FAIL]
Wed Dec 31 18:00:41 1969: INIT: Entering runlevel: 3
Wed Dec 31 18:00:41 1969: mount: mount point /proc/sys/fs/binfmt_misc does not exist
Wed Dec 31 18:00:41 1969: :: Starting Syslog-NG [BUSY] [DONE]
Wed Dec 31 18:00:41 1969: :: Starting crond daemon [BUSY] [DONE] ')

crond.log :
$this->bbcode_second_pass_code('', 'Dec 31 18:00:40 alarm /usr/sbin/crond[2468]: (CRON) STARTUP (1.4.8)
Dec 31 18:00:40 alarm /usr/sbin/crond[2468]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Dec 31 18:00:41 alarm /usr/sbin/crond[2468]: (CRON) INFO (running with inotify support)')

daemon.log:
$this->bbcode_second_pass_code('', 'Dec 31 18:00:41 alarm systemd-udevd[1349]: starting version 186
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptya1' '/dev/char/2:177.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptya5' '/dev/char/2:181.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../ptyc0' '/dev/char/2:208.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptyb6' '/dev/char/2:198.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptyd5' '/dev/char/2:229.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptyec' '/dev/char/2:252.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptypa' '/dev/char/2:10.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../ptyqd' '/dev/char/2:29.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptyr9' '/dev/char/2:41.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptyu8' '/dev/char/2:88.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../ptyse' '/dev/char/2:62.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptywe' '/dev/char/2:126.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../ptyxd' '/dev/char/2:141.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptyy0' '/dev/char/2:144.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../ptyz2' '/dev/char/2:162.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ptyzf' '/dev/char/2:175.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../tty1' '/dev/char/4:1.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../tty31' '/dev/char/4:31.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../tty58' '/dev/char/4:58.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../tty8' '/dev/char/4:8.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../ttybe' '/dev/char/3:206.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttyab' '/dev/char/3:187.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttydd' '/dev/char/3:237.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttye4' '/dev/char/3:244.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../ttyp8' '/dev/char/3:8.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttype' '/dev/char/3:14.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttyqf' '/dev/char/3:31.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttyrc' '/dev/char/3:44.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../ttyt0' '/dev/char/3:64.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttyuc' '/dev/char/3:92.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttyv3' '/dev/char/3:99.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttyw0' '/dev/char/3:112.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[2065]: symlink '../ttyy1' '/dev/char/3:145.udev-tmp' failed: Read-only file system
Dec 31 18:00:41 alarm systemd-udevd[1530]: symlink '../ttyz2' '/dev/char/3:162.udev-tmp' failed: Read-only file system
Dec 31 18:02:53 alarm init: Switching to runlevel: 6')
ubis
 
Posts: 7
Joined: Mon Nov 05, 2012 5:53 pm

Re: Arch on zt-180 v2

Postby WarheadsSE » Mon Nov 05, 2012 6:39 pm

Do you have devtmpfs enabled on the kernel?
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Arch on zt-180 v2

Postby ubis » Mon Nov 05, 2012 7:52 pm

No. Recompiled and flashed kernel with devtmpfs option. First boot was successfull, and after reboot - no. Freezes at Loading User-specified Modules [BUSY].

BTW in /etc/rc.conf file, my MODULES is empty.
ubis
 
Posts: 7
Joined: Mon Nov 05, 2012 5:53 pm

Re: Arch on zt-180 v2

Postby WarheadsSE » Mon Nov 05, 2012 9:54 pm

Get it to boot once, then depmod -a to confirm all the modules are setup right.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Arch on zt-180 v2

Postby ubis » Tue Nov 06, 2012 12:57 pm

Needed manually create empty files with nano modules.builtin and modules.order in /usr/lib/modules/3.4.0, because depmod -a said, that these files dont exist. After manual file creation, depmod -a returned nothing and files in /usr/lib/modules/3.4.0 were empty. Rebooted and, everything is same... Can't boot anymore. Booting stuck on Loading User-specified Modules as i said before.

Is there any change to debug and fix this problem?


EDIT:
Strange... Tried to use package ArchLinuxARM-mmp-latest.tar.gz for ARMv5 and now succesfully boots arch, even after reboot.
Hmm, can i use it, all functions will work with ARMv5 distro on ARMv6 cpu?
ubis
 
Posts: 7
Joined: Mon Nov 05, 2012 5:53 pm

Re: Arch on zt-180 v2

Postby Kresimir » Sun Jan 20, 2013 7:48 am

Hello!

Please excuse me for jumping into this thread with a not entirely related post.

I've been looking for hints/docs/cookbook/... how to install ArchLinux ARM on my Zenithink "ZTpad C91 upgrade" for several months without notable success.
While searching through ArchLinux ARM forums (and other forums dedicated to tablets) I've noticed you are working on installing ArchLinux on your Zenithink ZT 180 v2 tablet.

Reading your posts lead me to the conclusion you're lightyears in front of me with this, and I believe there must be at least some common points as we have tablets from the same manufacturer.
So I've been wondering if you would be willing to share your experineces and/or sources of information on how to do this and on your progress with your tablet?

Any response will be highly apreciated!
Kresimir
Kresimir
 
Posts: 7
Joined: Sat Jul 21, 2012 7:56 pm


Return to [Please read announcement] Community-Supported Devices

Who is online

Users browsing this forum: No registered users and 31 guests