Eu instalei o ubuntu touch no meu nexus 7 2013 recentemente, e enfrentei problemas ao instalar o driver para o adaptador usb Moxa Uport. Na verdade, o driver precisa ser compilado e é por isso que eu preciso de cabeçalhos Linux para ser instalado.
Eu descobri que:
apt-get install linux-headers-'uname -r'
precisa escrever algo em / lib / modules e esse caminho pertence a / dev / loop1, que é montado como readonly. Eu sou capaz de remontá-lo para rw, mas em uma única tentativa de escrever lá, ele cai de volta para readonly.
nada sobre loop1 ou / lib / modules em / etc / fstab
comando:
mount | grep loop1
saída:
/dev/loop1 on /android/system type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /etc/ubuntu-touch-session.d/android.conf type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /lib/udev/rules.d/70-android.rules type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /usr/share/powerd/device_configs/config-default.xml type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /lib/modules type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /var/lib/lxc/android/rootfs/system type ext4 (ro,relatime,data=ordered)
comando:
blockdev --report |grep loop1
saída:
ro 256 512 4096 0 126427136 /dev/loop1
então:
blockdev --setrw /dev/loop1
blockdev --report |grep loop1
saída:
rw 256 512 4096 0 126427136 /dev/loop1
comando:
mount -o remount,rw /dev/loop1
mount | grep loop1
saída:
/dev/loop1 on /android/system type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /etc/ubuntu-touch-session.d/android.conf type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /lib/udev/rules.d/70-android.rules type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /usr/share/powerd/device_configs/config-default.xml type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /lib/modules type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /var/lib/lxc/android/rootfs/system type ext4 (rw,relatime,data=ordered)
estranho, apenas / var / lib / lxc / android / rootfs / system foi definido como rw
então:
mount -o remount,rw /lib/modules
mount | grep loop1
saída:
/dev/loop1 on /android/system type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /etc/ubuntu-touch-session.d/android.conf type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /lib/udev/rules.d/70-android.rules type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /usr/share/powerd/device_configs/config-default.xml type ext4 (ro,relatime,data=ordered)
/dev/loop1 on /lib/modules type ext4 (rw,relatime,data=ordered)
/dev/loop1 on /var/lib/lxc/android/rootfs/system type ext4 (rw,relatime,data=ordered)
mas:
mkdir /lib/modules/rrr
saída:
mkdir: cannot create directory Б─≤/lib/modules/rrrБ─≥: Read-only file system
dmesg:
[ 8280.681213] EXT4-fs (loop1): previous I/O error to superblock detected
[ 8280.681579] Buffer I/O error on device loop1, logical block 0
[ 8280.682006] lost page write due to I/O error on loop1
[ 8280.682037] EXT4-fs error (device loop1): ext4_journal_start_sb:328: Detected aborted journal
[ 8280.682891] EXT4-fs (loop1): Remounting filesystem read-only
[ 8280.683135] EXT4-fs (loop1): previous I/O error to superblock detected
[ 8280.683593] Buffer I/O error on device loop1, logical block 0
Eu acho que a razão é a razão de:
apt-get install linux-headers-'uname -r'
falha com:
Unpacking linux-headers-3.4.0-5-flo (3.4.0-5.19~15.04.1) ...
dpkg: error processing archive /var/cache/apt/archives/linux-headers-3.4.0-5-flo_3.4.0-5.19~15.04.1_armhf.deb (--unpack):
error creating symbolic link './lib/modules/3.4.0-5-flo/build': Read-only file system
Errors were encountered while processing:
/var/cache/apt/archives/linux-headers-3.4.0-5-flo_3.4.0-5.19~15.04.1_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Então, fiquei preso nisso, poderia agradar a alguém que me ajudasse?
Atenciosamente, Victor