Jump to content

nepo

Members
  • Posts

    30
  • Joined

  • Last visited

Posts posted by nepo

  1. hi

     

    Unfortunately no solutions for my udev-problem, but a small workaround to implement my external hard disks.

     

    Mount with fstab and nofail option fstab

    Quote

    External devices

    External devices that are to be mounted when present but ignored if absent may require the nofail option. This prevents errors being reported at boot. For example:

    /etc/fstab

    /dev/sdg1 /media/backup jfs nofail,x-systemd.device-timeout=1 0 2

    The nofail option is best combined with the x-systemd.device-timeout option. This is because the default device timeout is 90 seconds, so a disconnected external device with only nofail will make your boot take 90 seconds longer, unless you reconfigure the timeout as shown. Make sure not to set the timeout to 0, as this translates to infinite timeout.

     

    In my case

    UUID=xxxxxxxxxxxx	/mnt/mountpoint	ext4	nofail,x-systemd.device-timeout=1,rw,auto,users       0 0

    To unmount correctly if unplugged I use an udev-rule

    orangepi@orangepiplus2e:~$ cat /etc/udev/rules.d/90-USB_festplatten.rules 
    ACTION=="remove", KERNEL=="sd?1", ENV{ID_SERIAL_SHORT}=="33Q8K5YEF", RUN+="/bin/umount  /mnt/mountpoint"

    bye

  2. hi

    I have upgraded my SD-version Armbian_5.65_Orangepiplus2e_Ubuntu_xenial_default_3.4.11 to mainline aka 4.14.70 Armbian 5.60

     

    et voila the system mount my harddisk. It seems not to be  a problem with the mainline-kernel.

     

    So, Where are the differences ?

    xenial vs bionic or/and  Armbian 5.60 vs Armbian_5.65

     

    bye

  3. hi

    orangepi 2e+ with ARMBIAN 5.65 stable Ubuntu 18.04.1 LTS 4.14.84-sunxi

    syslog

    I want to mount my external hard disks with

    cat /etc/udev/rules.d/91-intenso.rules 
    KERNEL=="sd?1", SUBSYSTEMS=="usb", ATTRS{serial}=="31700000000000007023", SYMLINK+="Intenso", ACTION=="add", RUN+="/bin/mount /dev/Intenso /mnt/Intenso"

    Normally no problem, tested with Armbian_5.65_Orangepiplus2e_Ubuntu_xenial_default_3.4.113 and Workstation PC Linux 4.15.0-43-generic #46~16.04.1-Ubuntu.

    With my current version, I have a problem. The udev-rule is/seem ok 

    Spoiler

    orangepi@orangepiplus2e:~$ sudo udevadm test /sys/class/block/sdb1
    calling: test
    version 237
    Load module index
    Parsed configuration file /lib/systemd/network/99-default.link
    Created link configuration context.
    Reading rules file: /etc/udev/rules.d/10-wifi-disable-powermanagement.rules
    Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
    Reading rules file: /lib/udev/rules.d/50-firmware.rules
    Reading rules file: /lib/udev/rules.d/50-udev-default.rules
    Reading rules file: /lib/udev/rules.d/55-dm.rules
    Reading rules file: /lib/udev/rules.d/60-block.rules
    Reading rules file: /lib/udev/rules.d/60-bridge-network-interface.rules
    Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
    Reading rules file: /lib/udev/rules.d/60-crda.rules
    Reading rules file: /lib/udev/rules.d/60-drm.rules
    Reading rules file: /lib/udev/rules.d/60-evdev.rules
    Reading rules file: /lib/udev/rules.d/60-gnupg2.rules
    Reading rules file: /lib/udev/rules.d/60-input-id.rules
    Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules
    Reading rules file: /lib/udev/rules.d/60-persistent-input.rules
    Reading rules file: /lib/udev/rules.d/60-persistent-storage-dm.rules
    Reading rules file: /lib/udev/rules.d/60-persistent-storage-tape.rules
    Reading rules file: /lib/udev/rules.d/60-persistent-storage.rules
    Reading rules file: /lib/udev/rules.d/60-persistent-v4l.rules
    Reading rules file: /lib/udev/rules.d/60-sensor.rules
    Reading rules file: /lib/udev/rules.d/60-serial.rules
    Reading rules file: /lib/udev/rules.d/60-sunxi-tools.rules
    Reading rules file: /lib/udev/rules.d/60-vlan-network-interface.rules
    Reading rules file: /lib/udev/rules.d/61-persistent-storage-android.rules
    Reading rules file: /lib/udev/rules.d/64-btrfs-dm.rules
    Reading rules file: /lib/udev/rules.d/64-btrfs.rules
    Reading rules file: /lib/udev/rules.d/70-joystick.rules
    Reading rules file: /lib/udev/rules.d/70-mouse.rules
    Reading rules file: /lib/udev/rules.d/70-power-switch.rules
    Reading rules file: /lib/udev/rules.d/70-touchpad.rules
    Reading rules file: /lib/udev/rules.d/70-uaccess.rules
    Reading rules file: /lib/udev/rules.d/71-axp-power-button.rules
    Reading rules file: /lib/udev/rules.d/71-power-switch-proliant.rules
    Reading rules file: /lib/udev/rules.d/71-seat.rules
    Reading rules file: /lib/udev/rules.d/73-seat-late.rules
    Reading rules file: /lib/udev/rules.d/73-special-net-names.rules
    Reading rules file: /lib/udev/rules.d/73-usb-net-by-mac.rules
    Reading rules file: /lib/udev/rules.d/75-net-description.rules
    Reading rules file: /lib/udev/rules.d/75-probe_mtd.rules
    Reading rules file: /lib/udev/rules.d/78-graphics-card.rules
    Reading rules file: /lib/udev/rules.d/78-sound-card.rules
    Reading rules file: /lib/udev/rules.d/80-debian-compat.rules
    Reading rules file: /lib/udev/rules.d/80-drivers.rules
    Reading rules file: /lib/udev/rules.d/80-ifupdown.rules
    Reading rules file: /lib/udev/rules.d/80-net-setup-link.rules
    Reading rules file: /lib/udev/rules.d/84-nm-drivers.rules
    Reading rules file: /lib/udev/rules.d/85-hdparm.rules
    Reading rules file: /lib/udev/rules.d/85-nm-unmanaged.rules
    Reading rules file: /lib/udev/rules.d/85-regulatory.rules
    Reading rules file: /lib/udev/rules.d/90-alsa-restore.rules
    Reading rules file: /lib/udev/rules.d/90-console-setup.rules
    Reading rules file: /etc/udev/rules.d/91-intenso.rules
    Reading rules file: /lib/udev/rules.d/95-dm-notify.rules
    Reading rules file: /lib/udev/rules.d/99-systemd.rules
    rules contain 24576 bytes tokens (2048 * 12 bytes), 14122 bytes strings
    1935 strings (25186 bytes), 1249 de-duplicated (11751 bytes), 687 trie nodes used
    GROUP 6 /lib/udev/rules.d/50-udev-default.rules:56
    LINK 'disk/by-id/ata-TOSHIBA_MG03ACA300_33Q8K5YEF-part1' /lib/udev/rules.d/60-persistent-storage.rules:53
    LINK 'disk/by-path/platform-1c1c000.usb-usb-0:1.2:1.0-scsi-0:0:0:0-part1' /lib/udev/rules.d/60-persistent-storage.rules:76
    IMPORT builtin 'blkid' /lib/udev/rules.d/60-persistent-storage.rules:90
    probe /dev/sdb1 raid offset=0
    LINK 'disk/by-uuid/21cbd081-a7b7-4fb3-a6a9-bf2e08aee280' /lib/udev/rules.d/60-persistent-storage.rules:93
    LINK 'disk/by-label/Intenso_3TB' /lib/udev/rules.d/60-persistent-storage.rules:94
    LINK 'disk/by-id/wwn-0x50000394aba82e19-part1' /lib/udev/rules.d/60-persistent-storage.rules:98
    LINK 'Intenso' /etc/udev/rules.d/91-intenso.rules:1
    RUN '/bin/mount /dev/Intenso /mnt/Intenso' /etc/udev/rules.d/91-intenso.rules:1
    handling device node '/dev/sdb1', devnum=b8:17, mode=0660, uid=0, gid=6
    preserve permissions /dev/sdb1, 060660, uid=0, gid=6
    preserve already existing symlink '/dev/block/8:17' to '../sdb1'
    found 'b8:17' claiming '/run/udev/links/\x2fIntenso'
    creating link '/dev/Intenso' to '/dev/sdb1'
    preserve already existing symlink '/dev/Intenso' to 'sdb1'
    found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fata-TOSHIBA_MG03ACA300_33Q8K5YEF-part1'
    creating link '/dev/disk/by-id/ata-TOSHIBA_MG03ACA300_33Q8K5YEF-part1' to '/dev/sdb1'
    preserve already existing symlink '/dev/disk/by-id/ata-TOSHIBA_MG03ACA300_33Q8K5YEF-part1' to '../../sdb1'
    found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fwwn-0x50000394aba82e19-part1'
    creating link '/dev/disk/by-id/wwn-0x50000394aba82e19-part1' to '/dev/sdb1'
    preserve already existing symlink '/dev/disk/by-id/wwn-0x50000394aba82e19-part1' to '../../sdb1'
    found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-label\x2fIntenso_3TB'
    creating link '/dev/disk/by-label/Intenso_3TB' to '/dev/sdb1'
    preserve already existing symlink '/dev/disk/by-label/Intenso_3TB' to '../../sdb1'
    found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-path\x2fplatform-1c1c000.usb-usb-0:1.2:1.0-scsi-0:0:0:0-part1'
    creating link '/dev/disk/by-path/platform-1c1c000.usb-usb-0:1.2:1.0-scsi-0:0:0:0-part1' to '/dev/sdb1'
    preserve already existing symlink '/dev/disk/by-path/platform-1c1c000.usb-usb-0:1.2:1.0-scsi-0:0:0:0-part1' to '../../sdb1'
    found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-uuid\x2f21cbd081-a7b7-4fb3-a6a9-bf2e08aee280'
    creating link '/dev/disk/by-uuid/21cbd081-a7b7-4fb3-a6a9-bf2e08aee280' to '/dev/sdb1'
    preserve already existing symlink '/dev/disk/by-uuid/21cbd081-a7b7-4fb3-a6a9-bf2e08aee280' to '../../sdb1'
    Unload module index
    Unloaded link configuration context.

     

    LINK 'Intenso' /etc/udev/rules.d/91-intenso.rules:1
    RUN '/bin/mount /dev/Intenso /mnt/Intenso' /etc/udev/rules.d/91-intenso.rules:1

     

    But

    orangepi@orangepiplus2e:~$ ls /mnt/Intenso/
    orangepi@orangepiplus2e:~$ 

    But If I mount manually

    orangepi@orangepiplus2e:~$ sudo mount /dev/Intenso /mnt/Intenso/
    orangepi@orangepiplus2e:~$ ls /mnt/Intenso/
    Filme  FRITZ  lost+found  Musik  recup_dir.86  Serien

    Where is my fault ?

     

    Bye nepo

  4. hi

    Orangepi plus 2e; Armbian 5,38 with Ubuntu xenial 16.4

     

    Normally my OrangePi works pretty fine, but today I tested lirc. I activated lirc by armbian-config, changed something in /etc/lirc/hardware.conf 

    Spoiler

    /etc/lirc/hardware.conf

     

    REMOTE_MODULES="sunxi_cir"

    REMOTE_DEVICE="/dev/lirc0"

    REMOTE_LIRCD_CONF=""

    REMOTE_LIRCD_ARGS=""

     

    #Enable lircd

    START_LIRCD="true"

     

    #Try to load appropriate kernel modules

    LOAD_MODULES="true"

    DRIVER="default"

    DEVICE="/dev/lirc0"

    MODULES="sunxi-cir"

     

    # Default configuration files for your hardware if any

    LIRCMD_CONF=""

     

    #to leave this set to "false"

    FORCE_NONINTERACTIVE_RECONFIGURATION="false"

    START_LIRCMD=""

    and now my Orangepi don't started correctly - Stopping with

    Starting Kernel ...

    What I can Do ? I can start my system with a SD-card, and mount the hole emmc-content.  It is possible to diable lirc only by remove/edit a (config-)file ?

     

    Bye nepo

  5. hi

    I have tested and read a lot of tutorials, but nothing works - I can't used rtcwake for wakeevents!

    Quote

    e.g.

    orangepi@orangepiplus2e:~$ sudo rtcwake -m off -d /dev/rtc1 -s 300
    [sudo] password for orangepi:
    rtcwake: assuming RTC uses UTC ...
    rtcwake: cannot open /sys/class/rtc/rtc1/device/power/wakeup: No such file or directory
    rtcwake: /dev/rtc1 not enabled for wakeup events

    but the rtc-modul ds3231 works

    Spoiler

    orangepi@orangepiplus2e:~$ sudo i2cdetect -y 0
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    00:          -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --                         

    orangepi@orangepiplus2e:~$ dmesg |grep rtc
    [    3.786757] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0
    [    3.786763] sun6i-rtc 1f00000.rtc: RTC enabled
    [    8.372324] [drm] Cannot find any crtc or sizes
    [    9.440407] [drm] Cannot find any crtc or sizes
    [   14.920990] rtc-ds1307 0-0068: registered as rtc1

     

    orangepi@orangepiplus2e:~$ sudo hwclock -D -r -f /dev/rtc1
    hwclock from util-linux 2.29.2
    Using the /dev interface to the clock.
    Assuming hardware clock is kept in UTC time.
    Waiting for clock tick...
    /dev/rtc1 does not have interrupt functions. Waiting in loop for time from /dev/rtc1 to change
    ...got clock tick
    Time read from Hardware Clock: 2018/04/15 13:58:56
    Hw clock time : 2018/04/15 13:58:56 = 1523800736 seconds since 1969
    Time since last adjustment is 1523800736 seconds
    Calculated Hardware Clock drift is 0.000000 seconds
    2018-04-15 15:58:55.297307+0200

     

    armbianmonitor -u

     

    Can I use my Orange Pi +2e with DS3231 to wake up ?  Anybody has success ?

    And why I have not a /proc/driver/rtc ?

    Quote

    cat /proc/driver/rtc
    cat: /proc/driver/rtc: No such file or directory

    With my Raspberry 3 and rtc-ds3231 it exist.

     

    Bye nepo!

  6. Hi Igor

     

    Thank you for this tutorial - and it works

    Spoiler

    orangepi@orangepiplus2e:~$ sudo i2cdetect -y 0
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    00:          -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --                         

     

    orangepi@orangepiplus2e:~$ timedatectl
          Local time: So 2018-04-08 18:03:35 CEST
      Universal time: So 2018-04-08 16:03:35 UTC
            RTC time: So 2018-04-08 16:03:34
           Time zone: Europe/Berlin (CEST, +0200)
     Network time on: yes
    NTP synchronized: yes
     RTC in local TZ: no
    orangepi@orangepiplus2e:~$ sudo hwclock -w
    [sudo] password for orangepi:
    orangepi@orangepiplus2e:~$ timedatectl
          Local time: So 2018-04-08 18:04:04 CEST
      Universal time: So 2018-04-08 16:04:04 UTC
            RTC time: So 2018-04-08 16:04:03
           Time zone: Europe/Berlin (CEST, +0200)
     Network time on: yes
    NTP synchronized: yes
     RTC in local TZ: no

     

    I want to use rtcwake, but

    Quote

    sudo rtcwake -n -m off -t $(date -d '20180408 18:45' +%s)
    rtcwake: wakeup from "off" using /dev/rtc0 at Mon Jun  9 01:11:54 1930 ;)

    logical:

    lrwxrwxrwx 1 root root          9 Feb 11  2016 rtc -> /dev/rtc1
    crw------- 1 root root   254,   0 Feb 11  2016 rtc0
    crw------- 1 root root   254,   1 Feb 11  2016 rtc1

    but

    sudo rtcwake -n -d /dev/rtc1 -m off -t $(date -d '20180408 18:45' +%s)
    rtcwake: cannot open /sys/class/rtc/rtc1/device/power/wakeup: No such file or directory
    rtcwake: /dev/rtc1 not enabled for wakeup events

     

    What must I do to use rtcwake ?

     

    Bye nepo!

  7. hi

    orangepi+2e : ARMBIAN 5.32 user-built Debian GNU/Linux 8 (jessie) 4.13.2-sunxi (no changes)

    armbianmonitor -u

     

    Perhaps I've the the same problem:

     

    Spoiler

    cpufreq-info
    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to cpufreq@vger.kernel.org, please.
    analyzing CPU 0:
      no or unknown cpufreq driver is active on this CPU
      maximum transition latency: 0.00 ms.
    analyzing CPU 1:
      ...
     
    orangepi@orangepiplus2e:~$ sudo service cpufrequtils status
    * cpufrequtils.service - LSB: set CPUFreq kernel parameters
       Loaded: loaded (/etc/init.d/cpufrequtils)
       Active: active (exited) since Fr 2017-09-15 17:03:24 CEST; 11min ago
      Process: 757 ExecStart=/etc/init.d/cpufrequtils start (code=exited, status=0/SUCCESS)

    Sep 15 17:03:24 orangepiplus2e cpufrequtils[757]: CPUFreq Utilities: Setting ondemand CPUFreq governor...disabled, governor not available...done.
    Sep 15 17:03:25 orangepiplus2e systemd[1]: Started LSB: set CPUFreq kernel parameters.
    orangepi@orangepiplus2e:~$
    dmesg |grep -i cpu
    [    0.000000] Booting Linux on physical CPU 0x0
    [    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=50c5387d
    [    0.000000] CPU: div instructions available: patching division code
    [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
    [    0.000000] percpu: Embedded 17 pages/cpu @eed9e000 s39948 r8192 d21492 u69632
    [    0.000000] pcpu-alloc: s39948 r8192 d21492 u69632 alloc=17*4096
    [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
    [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [    0.001091] CPU: Testing write buffer coherency: ok
    [    0.001399] /cpus/cpu@0 missing clock-frequency property
    [    0.001415] /cpus/cpu@1 missing clock-frequency property
    [    0.001430] /cpus/cpu@2 missing clock-frequency property
    [    0.001447] /cpus/cpu@3 missing clock-frequency property
    [    0.001456] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
    [    0.002479] smp: Bringing up secondary CPUs ...
    [    0.013073] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
    [    0.023724] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
    [    0.034335] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
    [    0.034400] smp: Brought up 1 node, 4 CPUs
    [    0.034412] CPU: All CPU(s) started in HYP mode.
    [    0.034414] CPU: Virtualization extensions available.
    [    0.449247] cpuidle: using governor ladder
    [    0.449376] cpuidle: using governor menu
    [    3.890777] ledtrig-cpu: registered to indicate activity on CPUs
    [    7.046077] cpu cpu0: failed to get clock: -2
    [    7.046105] cpufreq-dt: probe of cpufreq-dt failed with error -2

     

    I've tried to load the cpufreq driver

    orangepi@orangepiplus2e:~$ cat /etc/modules
    #8189fs
    arm_big_little
    arm_big_little_dt
    

    But nothing happens.

     

    On 10.9.2017 at 9:35 AM, Igor said:

    Everything is fine.

     

    What does it mean ? No risk for my Pi ?

     

    ciao nepo

  8. hi

     

    Services rpimonitor and rpimonitor-helper.service runs

    but no information in /tmp/disktemp nor /tmp/externaltemp (the files exists), also by editing to the orig. conf-files.

    sudo hdparm /dev/sda
    
    /dev/sda:
     multcount     = 16 (on)
     readonly      =  0 (off)
     readahead     = 256 (on)
     geometry      = 60801/255/63, sectors = 976773168, start = 0
    
    sudo hdparm -I /dev/sda1
    
    /dev/sda1:
    
    ATA device, with non-removable media
    	Model Number:       TOSHIBA MQ01UBD050                      
    	Serial Number:      54R5TCLYT
    	Firmware Revision:  AX001U  
    	Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6
    Standards:
    	Supported: 8 7 6 5 
    	Likely used: 8
    Configuration:
    	Logical		max	current
    	cylinders	16383	16383
    	heads		16	16
    	sectors/track	63	63
    	--
    	CHS current addressable sectors:   16514064
    	LBA    user addressable sectors:  268435455
    	LBA48  user addressable sectors:  976773168
    	Logical  Sector size:                   512 bytes
    	Physical Sector size:                  4096 bytes
    	Logical Sector-0 offset:                  0 bytes
    	device size with M = 1024*1024:      476940 MBytes
    	device size with M = 1000*1000:      500107 MBytes (500 GB)
    	cache/buffer size  = 8192 KBytes
    	Form Factor: 2.5 inch
    	Nominal Media Rotation Rate: 5400
    Capabilities:
    	LBA, IORDY(can be disabled)
    	Queue depth: 32
    	Standby timer values: spec'd by Standard, no device specific minimum
    	R/W multiple sector transfer: Max = 16	Current = 16
    	Advanced power management level: 254
    	DMA: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5 
    	     Cycle time: min=120ns recommended=120ns
    	PIO: pio0 pio1 pio2 pio3 pio4 
    	     Cycle time: no flow control=120ns  IORDY flow control=120ns
    Commands/features:
    	Enabled	Supported:
    	   *	SMART feature set
    	    	Security Mode feature set
    	   *	Power Management feature set
    	   *	Write cache
    	   *	Look-ahead
    	   *	Host Protected Area feature set
    	   *	WRITE_BUFFER command
    	   *	READ_BUFFER command
    	   *	NOP cmd
    	   *	DOWNLOAD_MICROCODE
    	   *	Advanced Power Management feature set
    	    	SET_MAX security extension
    	   *	48-bit Address feature set
    	   *	Device Configuration Overlay feature set
    	   *	Mandatory FLUSH_CACHE
    	   *	FLUSH_CACHE_EXT
    	   *	SMART error logging
    	   *	SMART self-test
    	   *	General Purpose Logging feature set
    	   *	WRITE_{DMA|MULTIPLE}_FUA_EXT
    	   *	64-bit World wide name
    	   *	IDLE_IMMEDIATE with UNLOAD
    	   *	WRITE_UNCORRECTABLE_EXT command
    	   *	{READ,WRITE}_DMA_EXT_GPL commands
    	   *	Segmented DOWNLOAD_MICROCODE
    	   *	Gen1 signaling speed (1.5Gb/s)
    	   *	Gen2 signaling speed (3.0Gb/s)
    	   *	Native Command Queueing (NCQ)
    	   *	Host-initiated interface power management
    	   *	Phy event counters
    	   *	Idle-Unload when NCQ is active
    	    	DMA Setup Auto-Activate optimization
    	    	Device-initiated interface power management
    	   *	Software settings preservation
    	   *	SMART Command Transport (SCT) feature set
    	   *	SCT Write Same (AC2)
    	   *	SCT Error Recovery Control (AC3)
    	   *	SCT Features Control (AC4)
    	   *	SCT Data Tables (AC5)
    Security: 
    	Master password revision code = 65534
    		supported
    	not	enabled
    	not	locked
    	not	frozen
    	not	expired: security count
    		supported: enhanced erase
    	112min for SECURITY ERASE UNIT. 112min for ENHANCED SECURITY ERASE UNIT. 
    Logical Unit WWN Device Identifier: 0000000000000000
    	NAA		: 0
    	IEEE OUI	: 000000
    	Unique ID	: 000000000
    Checksum: correct

     

     

  9. Hi

    orange pi +2e with

    Distribution: Ubuntu 16.04.2 LTS

    Kernel version: Linux 3.4.113-sun8i armv7l

    rpimonitor installed with sudo armbianmonitor -r

     

    I use Rpimonitor to control temperature, upgradable packages and cpu frequency, nice tool !

    Unfortunately it looks that rpimonitor has access to my external external hard drives, so no spin off .

    I change rpimonitor config files

    sudo nano /etc/rpimonitor/data.conf
    
    #include=/etc/rpimonitor/template/sdcard.conf
    
    and
    
    sudo nano /etc/rpimonitor/template/Allwinner_H3_Extended_Mainline.conf
    
    #dynamic.7.name=externaltemp
    #dynamic.7.source=/tmp/externaltemp
    #dynamic.7.regexp=(.*)
    #dynamic.7.postprocess=sprintf("%.1f", $1/1000)
    #dynamic.7.rrd=GAUGE
    
    #dynamic.8.name=disktemp
    #dynamic.8.source=/tmp/disktemp
    #dynamic.8.regexp=(.*)
    #dynamic.8.postprocess=sprintf("%.1f", $1/1000)
    #dynamic.8.rrd=GAUGE

     

    But no success

    Only if I stoped rpimonitor service, my hard disks spin off.

     

    Can anybody help

     

    Bye nepo

     

    @edit: With only armbianmonitor -m no problems

  10. hi again

    new image compile without rc_core.

    compile media_built and install -> no errors

    reboot and plugin the stick -> no kernel Panic :D

     

    But:

    dmesg

    new high-speed USB device number 3 using ehci-platform
    [ 2512.085372] usb 4-1: New USB device found, idVendor=15f4, idProduct=0131
    [ 2512.085389] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 2512.085399] usb 4-1: Product: dvbt2
    [ 2512.085410] usb 4-1: Manufacturer: astrometadvbt2
    [ 2512.109067] media: exports duplicate symbol __media_device_register (owned by kernel)
    [ 2512.205549] media: exports duplicate symbol __media_device_register (owned by kernel)

    dmesg | grep -i dvb only and no adapter in /dev/

    4.520298] usb 4-1: Product: dvbt2
    [    4.520303] usb 4-1: Manufacturer: astrometadvbt2
    [ 2512.085399] usb 4-1: Product: dvbt2
    [ 2512.085410] usb 4-1: Manufacturer: astrometadvbt2

    armbianmonitor

    lsmod

    Module                  Size  Used by
    bluetooth             263753  0 
    cfg80211              192770  0 
    rfkill                 10928  3 bluetooth,cfg80211
    realtek                 2818  1 
    evdev                   9979  0 
    ir_lirc_codec           4502  0 
    lirc_dev                8387  1 ir_lirc_codec
    sun4i_codec            28243  3 
    sun8i_codec_analog     13766  1 
    sunxi_cir               3825  0 
    snd_soc_core          115473  2 sun4i_codec,sun8i_codec_analog
    snd_pcm_dmaengine       4221  1 snd_soc_core
    snd_pcm                70145  2 snd_pcm_dmaengine,snd_soc_core
    sun8i_ths               3134  0 
    uio_pdrv_genirq         3354  0 
    cpufreq_dt              3522  0 
    uio                     8012  1 uio_pdrv_genirq
    gpio_keys               8517  0 
    thermal_sys            43232  2 cpufreq_dt,sun8i_ths
    8189fs                826413  0 
    fuse                   70718  1 

    so I look at this page and try

    orangepi@orangepiplus2e:~/media_build$ sudo make unload 
    [sudo] password for orangepi: 
    make -C /home/orangepi/media_build/v4l unload
    make[1]: Entering directory '/home/orangepi/media_build/v4l'
    scripts/rmmod.pl unload
    found 575 modules
    /sbin/rmmod ir_lirc_codec
    Pulseaudio is running with UUID(s): 
    /sbin/rmmod lirc_dev
    make[1]: Leaving directory '/home/orangepi/media_build/v4l'orangepi@orangepiplus2e:~/media_build$ sudo modprobe -a rtl2832_sdr videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core mn88473 rtl2832 dvb_usb_rtl28xxu
    modprobe: ERROR: could not insert 'rtl2832_sdr': Exec format error
    modprobe: ERROR: could not insert 'videobuf2_v4l2': Exec format error
    modprobe: ERROR: could not insert 'videobuf2_core': Exec format error
    modprobe: ERROR: could not insert 'mn88473': Exec format error
    modprobe: ERROR: could not insert 'rtl2832': Exec format error
    modprobe: ERROR: could not insert 'dvb_usb_rtl28xxu': Exec format error

    reboot

    The same problem. Also I try (found no *.ko.gz files)

    sudo make reload
    sudo depmod -a

    Nothing !

    What can i do else

  11. hi

    I don't want to give up, also next attempt.

    Fresh image Armbian_5.27_Orangepiplus2e_Debian_jessie_dev_4.10.3 (april 5) with no kernel config

    Install media-build with

    git clone git://linuxtv.org/media_build.git
    cd media_build 
    ./build

    No errors!

    reboot and sudo make unload, plug in usb-stick

     

    Kernel Panic

    usb 4-1: new high-speed USB device number 2 using ehci-platform
    [10756.489835] usb 4-1: New USB device found, idVendor=15f4, idProduct=0131
    [10756.489851] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [10756.489861] usb 4-1: Product: dvbt2
    [10756.489872] usb 4-1: Manufacturer: astrometadvbt2
    [10756.523013] Unable to handle kernel NULL pointer dereference at virtual address 00000080
    [10756.531707] pgd = ecdf4000
    [10756.534598] [00000080] *pgd=00000000
    [10756.548898] Internal error: Oops: 805 [#1] SMP THUMB2
    [10756.564493] Modules linked in: dvb_usb_rtl28xxu(O+) ir_xmp_decoder(O) cfg80211 bluetooth rfkill evdev realtek sun8i_codec_analog sunxi_cir sun4i_codec snd_soc_core snd_pcm_dmaengine snd_pcm sun8i_ths gpio_keys cpufreq_dt thermal_sys uio_pdrv_genirq uio 8189fs [last unloaded: lirc_dev]
    [10756.632763] CPU: 0 PID: 5294 Comm: systemd-udevd Tainted: G           O    4.10.3-sun8i #7
    [10756.662661] Hardware name: Allwinner sun8i Family
    [10756.678351] task: ed5e3900 task.stack: edece000
    [10756.693727] PC is at rtl28xxu_identify_state+0x37/0x68 [dvb_usb_rtl28xxu]
    [10756.711399] LR is at rtl28xxu_ctrl_msg+0xb6/0xcc [dvb_usb_rtl28xxu]
    [10756.728414] pc : [<bfa6215c>]    lr : [<bfa6210f>]    psr: 00070033
                   sp : edecfcc0  ip : 00000000  fp : ed64be00
    [10756.761072] r10: bfa64064  r9 : ed64be00  r8 : bfa64b7c
    [10756.776655] r7 : ece6d000  r6 : 00000000  r5 : ecc6c000  r4 : 00000000
    [10756.793479] r3 : 00000002  r2 : 00000000  r1 : 00000000  r0 : 00000000
    [10756.810074] Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment none
    [10756.827485] Control: 50c5387d  Table: 6cdf406a  DAC: 00000051
    [10756.843230] Process systemd-udevd (pid: 5294, stack limit = 0xedece210)
    [10756.859858] Stack: (0xedecfcc0 to 0xeded0000)
    [10756.874058] fcc0: bfa640b8 06000020 00000000 00000000 bfa640b8 ecc6c000 ece6d070 c05ae8a3
    [10756.901816] fce0: eda6ca00 00000000 00000000 00000000 00000001 ece6d070 ece6d0e4 00000004
    [10756.929671] fd00: 400e0013 bfa64b7c 00000000 c04d2091 0000000a ed64be20 00000000 ece6d070
    [10756.957617] fd20: ece6d000 bfa64b7c ed64be00 bfa64064 ffffffed c05500ab c054ffed ed64be20
    [10756.985657] fd40: c0b9bc50 00000000 00000000 bfa64b7c 0000002e ed965a24 00000124 c04cb46b
    [10757.013735] fd60: 00000000 ed64be20 bfa64b7c ed64be54 c04cb4e1 bfa64c00 ed965a00 c04cb545
    [10757.042541] fd80: 00000001 00000000 bfa64b7c c04ca2c5 ee594158 ed8d5ab4 00000000 bfa64b7c
    [10757.071946] fda0: ecdd6900 00000000 c0b43418 c04cad4b bfa64688 bfa64b7c c0b43418 bfa64b7c
    [10757.101332] fdc0: c0b43418 c054ffed bfa64b7c c04cbab9 bfa64688 bfa64b48 c0b43418 c054f3bd
    [10757.130721] fde0: ffffe000 bfa64c00 bfa68001 00000000 00000001 c01016b7 8040003f 014000c0
    [10757.160426] fe00: ecc6c018 bfa64c48 00000000 c0b25b2c 8040003e 00000001 ee401e40 edecfe38
    [10757.190668] fe20: 00000001 ee401e40 edecfe38 00000001 ee401e40 edecfe50 bfa64c00 bfa64c00
    [10757.221303] fe40: bfa64c00 bfa64c00 00000001 ed662500 00000001 c0198fb9 ed965a00 edecff54
    [10757.252474] fe60: bfa64c00 edecff54 bfa64c00 00000001 ed965a00 c0173011 bfa64c0c 00007fff
    [10757.284414] fe80: bfa64c00 c01712b9 00000000 bfa64c00 bfa64c48 edecff54 bfa64c0c f17b3c38
    [10757.316720] fea0: bfa64c0c c0702e0c c08946c0 c0894724 c08946cc bfa64dbc 00000000 00006c88
    [10757.349271] fec0: 00000000 edecff48 00006c88 00000000 00000000 00000000 00000000 00000000
    [10757.382033] fee0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    [10757.414801] ff00: 00000000 00000000 7fffffff 00000000 f17ad000 b6e3d63c 0000017b c0106024
    [10757.444261] ff20: edece000 00000000 00000000 c01734c9 7fffffff 00000000 00000003 00000000
    [10757.466896] ff40: 00000000 f17ad000 00006c88 00000000 00000000 f17ad000 00006c88 f17b3738
    [10757.489527] ff60: f17b35e4 f17b17e8 00002e04 00003894 00000000 00000000 00000000 00001f90
    [10757.512156] ff80: 00000020 00000021 00000017 00000000 00000010 00000000 7f68c058 7f680b0c
    [10757.534782] ffa0: b0411d00 c0105e61 7f68c058 7f680b0c 00000007 b6e3d63c 00000000 b6e3e0a4
    [10757.557413] ffc0: 7f68c058 7f680b0c b0411d00 0000017b 00020000 7f680b0c 7f692448 00000000
    [10757.580044] ffe0: be9ef8e8 be9ef8d8 b6e378ff b6d89572 800e0030 00000007 ffffffff ffffffff
    [10757.602723] [<bfa6215c>] (rtl28xxu_identify_state [dvb_usb_rtl28xxu]) from [<c05ae8a3>] (dvb_usbv2_probe+0xb7/0x838)
    [10757.627812] [<c05ae8a3>] (dvb_usbv2_probe) from [<c05500ab>] (usb_probe_interface+0xbf/0x1bc)
    [10757.650865] [<c05500ab>] (usb_probe_interface) from [<c04cb46b>] (driver_probe_device+0x16b/0x1e0)
    [10757.674383] [<c04cb46b>] (driver_probe_device) from [<c04cb545>] (__driver_attach+0x65/0x68)
    [10757.697392] [<c04cb545>] (__driver_attach) from [<c04ca2c5>] (bus_for_each_dev+0x39/0x58)
    [10757.720155] [<c04ca2c5>] (bus_for_each_dev) from [<c04cad4b>] (bus_add_driver+0xab/0x164)
    [10757.742940] [<c04cad4b>] (bus_add_driver) from [<c04cbab9>] (driver_register+0x31/0x84)
    [10757.765568] [<c04cbab9>] (driver_register) from [<c054f3bd>] (usb_register_driver+0x51/0xdc)
    [10757.789677] [<c054f3bd>] (usb_register_driver) from [<c01016b7>] (do_one_initcall+0x2f/0xfc)
    [10757.812826] [<c01016b7>] (do_one_initcall) from [<c0198fb9>] (do_init_module+0x45/0x314)
    [10757.835625] [<c0198fb9>] (do_init_module) from [<c0173011>] (load_module+0x1461/0x17ac)
    [10757.858355] [<c0173011>] (load_module) from [<c01734c9>] (SyS_finit_module+0x65/0x70)
    [10757.880927] [<c01734c9>] (SyS_finit_module) from [<c0105e61>] (ret_fast_syscall+0x1/0x4c)
    [10757.903873] Code: d004 4604 b958 2302 (f886) 3080 
    [10757.916134] ---[ end trace 4885c4e9b24281a6 ]---

    dmesq dvb and whole dmesg.txt and armhwinfo.log

    orangepi@orangepiplus2e:~/media_build$ dmesg |grep -i dvb
    [10756.489861] usb 4-1: Product: dvbt2
    [10756.489872] usb 4-1: Manufacturer: astrometadvbt2
    [10756.564493] Modules linked in: dvb_usb_rtl28xxu(O+) ir_xmp_decoder(O) cfg80211 bluetooth rfkill evdev realtek sun8i_codec_analog sunxi_cir sun4i_codec snd_soc_core snd_pcm_dmaengine snd_pcm sun8i_ths gpio_keys cpufreq_dt thermal_sys uio_pdrv_genirq uio 8189fs [last unloaded: lirc_dev]
    [10756.693727] PC is at rtl28xxu_identify_state+0x37/0x68 [dvb_usb_rtl28xxu]
    [10756.711399] LR is at rtl28xxu_ctrl_msg+0xb6/0xcc [dvb_usb_rtl28xxu]
    [10757.602723] [<bfa6215c>] (rtl28xxu_identify_state [dvb_usb_rtl28xxu]) from [<c05ae8a3>] (dvb_usbv2_probe+0xb7/0x838)
    [10757.627812] [<c05ae8a3>] (dvb_usbv2_probe) from [<c05500ab>] (usb_probe_interface+0xbf/0x1bc)

    No modul for mn88743 and

    ls /dev/dvb
    ls: cannot access '/dev/dvb': No such file or directory

     

    make reload

    orangepi@orangepiplus2e:~/media_build$ sudo make reload
    rmmod: ERROR: Module dvb_usb_rtl28xxu is in use
    .
    .
    insmod: ERROR: could not load module ./dvb_usb_az6027.ko: No such file or directory
    insmod: ERROR: could not load module ./dvb_usb_opera.ko: No such file or directory
    insmod: ERROR: could not load module ./dvb_usb_digitv.ko: No such file or directory
    insmod: ERROR: could not load module ./dvb_usb_dw2102.ko: No such file or directory
    insmod: ERROR: could not insert module ./cpia2.ko: Cannot allocate memory
    insmod: ERROR: could not load module ./sony_btf_mpx.ko: No such file or directory
    insmod: ERROR: could not load module ./dvb_usb_ttusb2.ko: No such file or directory
    insmod: ERROR: could not insert module ./saa7115.ko: Cannot allocate memory
    insmod: ERROR: could not insert module ./cx25840.ko: Cannot allocate memory
    insmod: ERROR: could not insert module ./tvp5150.ko: Cannot allocate memory
    insmod: ERROR: could not insert module ./adv7842.ko: Cannot allocate memory
    insmod: ERROR: could not insert module ./smiapp.ko: Cannot allocate memory
    insmod: ERROR: could not insert module ./cx2341x.ko: Cannot allocate memory
    insmod: ERROR: could not insert module ./tvaudio.ko: Cannot allocate memory
    insmod: ERROR: could not load module ./dvb_usb_technisat_usb2.ko: No such file or directory
    insmod: ERROR: could not load module ./dvb_usb_mxl111sf.ko: No such file or directory
    .
    .
    .
    insmod: ERROR: could not load module ./dvb_usb_a800.ko: No such file or directory
    insmod: ERROR: could not insert module ./mt9t031.ko: Cannot allocate memory
    insmod: ERROR: could not insert module ./ov5642.ko: Cannot allocate memory
    insmod: ERROR: could not load module ./go7007_usb.ko: No such file or directory
    insmod: ERROR: could not load module ./cx231xx_alsa.ko: No such file or directory
    insmod: ERROR: could not load module ./dvb_usb_dibusb_mc.ko: No such file or directory
    insmod: ERROR: could not insert module ./mt9m001.ko: Cannot allocate memory
    insmod: ERROR: could not load module ./xilinx_tpg.ko: No such file or directory
    .
    .

    What I can do ???

    Please help and

    Ciao nepo

  12. 6 minutes ago, jernej said:

    BTW, just curious, does the issue, present in 4.9 and newer kernels, affect all DVB dongles?

    I don't know.  I didn't use T230C , because dvb-c support is bad, in 4.10 as well as 4.4 (RPI), so I could not tested really, I read some post about it., with my Astrometa-Dongle and 4.4.5 perfect, recordings (mpeg2) with ProjectX no error ... and with 4.10.3 only problems - live and recordings.

     

    24 minutes ago, jernej said:

    Tell me if you want to go this way, but I can't promise you anything

    I will go every way :D, but I can't go myself (noob)

  13. 57 minutes ago, jernej said:

    Tough luck. 4.8 kernel should be usable for you just enough, because in this version USB support was introduced for H3, but I'm not sure how to make Armbian image with it.

     

    Probably the best way would be to do kernel bisect to pinpoint bad commit between 4.8 and 4.9, but this is tedious work and it should be done on HW supported by SW, e.g. LibreELEC on RPi or something similar. Once bad commit is found, it could be analyzed and fixed. Fix could be then included in Armbian.

    Thanks for help, but I understand nothing. :blink:

    At moment, I try another thing. Perhaps (hopefully) I make a mistake by compiling the image. In this post idandavidi used a t230c stick and funnily I have such stick somewhere. 

     

    So, I'm not sure, idandavidi used kernel 3.4 like me and my orangepi don't recognize the stick t230. I believe, that means i make a mistake by building the image.

    Perhaps anybody can find the error dmesq_t230c.txt   linux-sun8i-default.config

     

    Ciao

  14. hi

    thanks for answer!

    I'm a noob, but my RPI runs with kernel 4.4.50-v7+ and I remember I could compile the v4l driver I will test it again.

     

    usb 1-1.3: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...
    usb 1-1.3: DVB: registering adapter 0 frontend 1 (Panasonic MN88473)...

    I need only dvb-c -> mn88473

    It is possible to compile without rtl2832 ?

     

    edit: v4l compile with kernel 4.4.50 link 

  15. Hi

    I want to install a tv-server (vdr) on my orangepi with a usb-dvb-stick from astrometa. I read this post and try to reproduce it. I build my own image ARMBIAN 5.27 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i (linux-sun8i-default.config )and install v4l driver with no errors.

    Unfortunately it don't work.  The system don't recognize the stick (see file orangepi_Astrometa.txt and dmesq_media_build.txt ). Useful for comparison my raspberrypi with the stick (raspberry_Astrometa.txt) .

     

    Can anybody help?

     

    Ciao nepo

  16. I will try it.

    Change configuration.sh

    Quote

    ARMBIAN_MAINLINE_KERNEL_VERSION='4.10'
    MAINLINE_KERNEL_BRANCH=tag:v$(wget -qO- https://www.kernel.org/finger_banner | awk '{print $NF}' | grep -oE "^${ARMBIAN_MAINLINE_KERNEL_VERSION//./\\.}\.?[[:digit:]]*" | tail -1)

    in

    Quote

    ARMBIAN_MAINLINE_KERNEL_VERSION='4.8'

    'KERNELBRANCH='branch:orange-pi-4.8'

    Right ?

    And like this post

    Quote

    When you go back with version, patches might break. You will need to deal with that ... check output/debug/patching.log for details and fix patches. In case patches are not important for you, disable them.

    No other way.

      How I can disable patches - in configuration files or during the process of compile (configure kernel)

  17. hello again :D

     

    I tested this image Armbian_5.27_Orangepiplus2e_Debian_jessie_dev_4.10.3, everything ok only the Tv-Output.

     

    I have the same problem to fit this description :

    That build was the first one that used the new 4.9.0 kernel. I noticed a somewhat rare, intermittent video corruption when watching 1080i h.264 TV channels - usually a flash of green artifacts. Those video artifacts appear once in 5-10 minutes (sometimes more frequent). (I use it as tvserver with RPI3 (Raspian Jessie and Kodi) as client.

    So I want to try another kernel.

    I read this post and I insert in my compile.sh

    KERNELTAG="v4.4.58"

    Of course, nothing happen, still the same kernel 4.10.3. so I read your documentation about patches , kernel configs and ..., but I understand nothing (not at all)  :(. I'm "only" a user - copy and paste try and error.

    Can I build a kernel e.g. v4.4.50 (like my raspi) and if how I can do that ?

     

    Tschau nepo

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines