mgx0

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. hey there, I'm playing with T9 player based on RK3328, 4/64GB, DTD file is from hexdump from his latest post. But I'm experiencing kernel panics most probably related to emmc. when I run "yes > ./test.txt" it goes crazy in few minutes and ends up with this in ssh session I get this Message from syslogd@plex at Jun 1 13:01:11 ... kernel:[ 236.370456] Internal error: Oops - bad mode: 0 [#1] SMP Message from syslogd@plex at Jun 1 13:01:11 ... kernel:[ 236.370548] Process lsb_release (pid: 2595, stack limit = 0xffffffc0f0230000) Message from syslogd@plex at Jun 1 13:01:11 ... kernel:[ 236.372255] Internal error: Oops - bad mode: 0 [#2] SMP Message from syslogd@plex at Jun 1 13:01:11 ... kernel:[ 236.372314] Process telegraf (pid: 929, stack limit = 0xffffffc0f0270000) Message from syslogd@plex at Jun 1 13:01:11 ... kernel:[ 236.585493] Internal error: Oops - bad mode: 0 [#3] SMP Message from syslogd@plex at Jun 1 13:01:11 ... kernel:[ 236.695864] Process yes (pid: 2477, stack limit = 0xffffffc0f02b4000) Segmentation fault on screen it's quite lot of text, says BUG: spinlock lockup suspected on CPU#0 using ARMBIAN 5.82 user-built Debian GNU/Linux 9 (stretch) 4.4.154-rk3328-tv, this LABEL Armbian LINUX /Image INITRD /uInitrd FDT /dtb/rockchip/rk3328-t9.dtb APPEND root=LABEL=ROOT_EMMC rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 I read somewhere about lowering eMMC frequency from 200MHz to 150MHz, is this possible somehow, please? update: ek3328-evb.dtb is running more stable, no crashes during excessive IO on disk. ek3328-evb.dtb has no keyboard/mouse, that is not an issue for me. And it crashed too in few hours. Kept the CPU temperature a LOT lower and crashed a lot later than using the ek3328-t9.dtb file
  2. yeah now it does not complain about anything. had to replace mmcblk1 with mmcblk2 in install.sh and also in /boot/create-mbr-linux.sh now it's installing ... EDIT: AAAAND booted! thanks a lot for your hard work!
  3. thanks for the reply the problem is that there is no mmcblk2p1 and mmcblk2p2, which the install.sh script tries to mount. there are four partitions on eMMC: /dev/mmcblk2boot1 /dev/mmcblk2boot2 /dev/mmcblk2rpmb and /dev/mmcblk2 (this should be actually the physical disk) $PART_BOOT and $PART_ROOT variables are set to /dev/mmcblk1p0 and mmcblk1p2. which one has to be changed to mmcblk2? and what to do with /dev/mmcblk2boot1 /dev/mmcblk2boot2 and /dev/mmcblk2rpmb ? or does the /dev/mmcblk2 need to be repartitioned? i mean create new /dev/mmcblk2p1 and /dev/mmcblk2p2 ... did anybody need to do that on T9? EDIT: CRAP! I'm not reading the instructions again! I'm sorry for confusion are lines in bold (which were not executed) the cause of what I see? I'll do that this evening. sorry again, my fault 1. Download, unzip and burn the image to SD card. 2. Start Armbian on the TV box and perform the initial setup of the system. 3. If the system works correctly and you are satisfied, run the utility "ddbr" and create a full backup of eMMC (this is a prerequisite). 4. Rename the file "/boot/mvr9-uboot.img" in "/boot/uboot.img". 5. Run as user "root" script "/boot/create-mbr-linux.sh" 6. To run the script "/root/install.sh"
  4. So, ethernet is working fine, ddbr has done a backup of mmcblk2, performance is a bit below S905X. So the machine is good, I just need to remove that Android crap and put something useful onto it :-) I could repartition mmcblk2 in two partitions, update install.sh script and run it, but I'm not that good in knowing linux on these particular devices. I don't want to brick my device any idea what to do with mmcblk2 please? How to proceed with installing onto emmc?
  5. hit some problem when trying to install the latest image to eMMC. following is terminal output from armbian booted off SD card (with dtb file from hexdump) root@rk3328:~# mount | grep mmcblk /dev/mmcblk0p2 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro) /dev/mmcblk0p2 on /var/log.hdd type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) root@rk3328:~# ls -la /dev/mmcblk* brw-rw---- 1 root disk 179, 0 Apr 27 15:23 /dev/mmcblk0 brw-rw---- 1 k 179, 1 Apr 27 15:23 /dev/mmcblk0p1 brw-rw---- 1 root disk 179, 2 Apr 27 15:23 /dev/mmcblk0p2 brw-rw---- 1 root disk 179, 32 Apr 27 15:23 /dev/mmcblk2 brw-rw---- 1 root disk 179, 64 Apr 27 15:23 /dev/mmcblk2boot0 brw-rw---- 1 root disk 179, 96 Apr 27 15:23 /dev/mmcblk2boot1 brw-rw---- 1 root disk 179, 128 Apr 27 15:23 /dev/mmcblk2rpmb install.sh sets the destination to mmcblk1pX because mmcblk0pX is mounted from SD card. this is truncated output from install.sh (see mmcblk1p1 does not exist) root@rk3328:~# ./install.sh Start copy system for eMMC. /dev/mmcblk0p1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro 0 0 Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24) mkfs.vfat: unable to open /dev/mmcblk1p1: No such file or directory done. mount: special device /dev/mmcblk1p1 does not exist Cppying BOOT...done. Edit init config...done. umount: /ddbr/install: not mounted Formatting ROOT partition... The file /dev/mmcblk1p2 does not exist and no size was specified. e2fsck 1.43.4 (31-Jan-2017) e2fsck: No such file or directory while trying to open /dev/mmcblk1p2 Possibly non-existent device? done. Copying ROOTFS. mount: special device /dev/mmcblk1p2 does not exist Copy BIN Create DEV Copy ETC tar: etc/fstab: time stamp 2019-04-27 15:27:57 is 124.421815093 s in the future Copy HOME Copy LIB tar: lib/firmware/cxgb3: time stamp 2019-04-27 15:25:54 is 1.11954926 s in the future tar: lib/firmware/bnx2: time stamp 2019-04-27 15:25:54 is 0.988122802 s in the future tar: lib/firmware/kaweth: time stamp 2019-04-27 15:25:54 is 0.708338343 s in the future tar: lib/firmware/dpaa2/mc: time stamp 2019-04-27 15:25:54 is 0.420168176 s in the future tar: lib/firmware/rkwifi/bcmdhd: time stamp 2019-04-27 15:25:54 is 0.20225176 s in the future tar: lib/udev/rules.d: time stamp 2019-04-27 15:27:23 is 20.601957435 s in the future Create MEDIA Create MNT Copy OPT Create PROC Copy ROOT Create RUN Copy SBIN tar: sbin: time stamp 2019-04-27 15:27:27 is 23.46567281 s in the future Copy SELINUX Copy SRV Create SYS Create TMP Copy USR I am leaving it to finish but I don't expect to have some effect. looks like the eMMC is on /dev/mmcblk2 and it's not mountable does anybody have an idea what is going on please? ddbr performs fine, it can copy the mmcblk2 drive
  6. yeah thanks a lot man, good stuff. I got it running, starts fine. I'll keep investigating and I'll get back with the details
  7. As I said, stupid question, sorry. I have fount it until my post has been approved, so I could not edit it. Sorry again
  8. Hi, I just got my T9 box RK3328 and am looking for Armbian_5.82_Rk3328-tv_Ubuntu_bionic_default_4.4.154_desktop_20190427.img.xz a stupid question: where the hell can I download that image, please? 😂 google did not help, all links go to this forum ... sorry for that, please respond thanks