• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. roberts_lando
    • Profile
    • Following 0
    • Followers 1
    • Topics 25
    • Posts 67
    • Best 2
    • Controversial 1
    • Groups 0

    roberts_lando

    @roberts_lando

    Software engineer for an home and building automation company:
    www.innovation-system.it.

    1
    Reputation
    1034
    Profile views
    67
    Posts
    1
    Followers
    0
    Following
    Joined Last Online
    Email daniel@innovation-system.it Website github.com/robertsLando Location Italy Age 29

    roberts_lando Unfollow Follow

    Best posts made by roberts_lando

    • RE: Bugs In Latest Axons

      Actually what I have done is:

      sudo /sbin/fdisk /dev/mmcblk0
      
      Welcome to fdisk (util-linux 2.29.2).
      Changes will remain in memory only, until you decide to write them.
      Be careful before using the write command.
      
      
      Command (m for help): p
      Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x92824060
      
      Device         Boot   Start      End  Sectors  Size Id Type
      /dev/mmcblk0p1        49152   253951   204800  100M 83 Linux
      /dev/mmcblk0p2       253952  3098623  2844672  1.4G 83 Linux
      /dev/mmcblk0p3      3098624 15269887 12171264  5.8G 83 Linux
      
      Command (m for help): d
      Partition number (1-3, default 3): 3
      
      Partition 3 has been deleted.
      
      Command (m for help): d
      Partition number (1,2, default 2): 2
      
      Partition 2 has been deleted.
      
      Command (m for help): n
      Partition type
         p   primary (1 primary, 0 extended, 3 free)
         e   extended (container for logical partitions)
      Select (default p): 1
      Value out of range.
         p   primary (1 primary, 0 extended, 3 free)
         e   extended (container for logical partitions)
      Select (default p): p
      Partition number (2-4, default 2): 2
      First sector (2048-15269887, default 2048): 253952
      Last sector, +sectors or +size{K,M,G,T,P} (253952-15269887, default 15269887): 15269887
      
      Created a new partition 2 of type 'Linux' and of size 7.2 GiB.
      Partition #2 contains a ext4 signature.
      
      Do you want to remove the signature? [Y]es/[N]o: N
      
      Command (m for help): p
      
      Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x92824060
      
      Device         Boot  Start      End  Sectors  Size Id Type
      /dev/mmcblk0p1       49152   253951   204800  100M 83 Linux
      /dev/mmcblk0p2      253952 15269887 15015936  7.2G 83 Linux
      
      Command (m for help): w
      The partition table has been altered.
      Calling ioctl() to re-read partition table.
      Re-reading the partition table failed.: Device or resource busy
      
      The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
      
      unipi@S105-sn470:~$ sudo reboot
      
      

      Reboot then:

      unipi@S105-sn470:~$ sudo /sbin/resize2fs /dev/mmcblk0p2 
      resize2fs 1.43.4 (31-Jan-2017)
      Filesystem at /dev/mmcblk0p2 is mounted on /; on-line resizing required
      old_desc_blocks = 1, new_desc_blocks = 1
      The filesystem on /dev/mmcblk0p2 is now 1876992 (4k) blocks long.
      

      Now the partition seems to be ok but some thing aren't working as expected.

      posted in Ubuntu Core
      roberts_lando
      roberts_lando
    • Bugs In Latest Axons

      Hi everyone. I have just restored an image that I made some months ago using your backup tool. I have made many different axons starting from this USB backup but the new one arrived seems to have some problems. After I restore the backup from the usb the filesystem is not resized and is stucked at 100% use so I cannot do anything.

      How can I fix this?

      Filesystem                                    Size  Used Avail Use% Mounted on
      udev                                          450M     0  450M   0% /dev
      tmpfs                                         100M  2.9M   97M   3% /run
      /dev/disk/by-path/platform-1c11000.mmc-part2  1.4G  1.3G  476K 100% /
      tmpfs                                         498M     0  498M   0% /dev/shm
      tmpfs                                         5.0M     0  5.0M   0% /run/lock
      tmpfs                                         498M     0  498M   0% /sys/fs/cgroup
      tmpfs                                         150M  2.0M  149M   2% /tmp
      tmpfs                                          50M     0   50M   0% /tftpboot
      /dev/mmcblk0p1                                100M   55M   46M  55% /boot
      tmpfs                                         100M     0  100M   0% /run/user/1000
      

      Also when I try to run a firmware update I get:

      unipi@S105-sn470:~$ /opt/unipi/tools/fwspi -i 0
      Unable to create the arm[0] context
      unipi@S105-sn470:~$ /opt/unipi/tools/fwspi -v --auto
      ARMINIT: Cannot open device /dev/unipispi
      ARMINIT: Cannot open device /dev/unipispi
      ARMINIT: Cannot open device /dev/unipispi
      Firmware autoupdate finished
      unipi@S105-sn470:~$ 
      

      Also I'm not able to start the axon in Service Web Interface mode (by keep pressing the button while starting). It remains stucked. This also happens with all other axons so the problem is not caused by the restore process but affetcts all axons

      Other info:

      unipi@S105-sn470:~$ sudo fdisk -l
      Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x92824060
      
      Device         Boot   Start      End  Sectors  Size Id Type
      /dev/mmcblk0p1        49152   253951   204800  100M 83 Linux
      /dev/mmcblk0p2       253952  3098623  2844672  1.4G 83 Linux
      /dev/mmcblk0p3      3098624 15269887 12171264  5.8G 83 Linux
      
      
      Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      
      
      Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      unipi@S105-sn470:~$ 
      
      
      posted in Ubuntu Core
      roberts_lando
      roberts_lando
    • RE: 1 Wire devices

      @tomas_hora Any news about this?

      posted in Axon series
      roberts_lando
      roberts_lando

    Latest posts made by roberts_lando

    • `cdc_acm` driver not present

      I need to connect an Aeotec Z-stick gen 5 (USB stick for zwave) but it is not recognized by my unipi G-110. Here is the output that confirms the kernel module needed is not present. Could someone help me with this?

      root@G110-sn597:/home/unipi# lsmod | grep cdc_acm
      root@G110-sn597:/home/unipi# modprobe cdc-acm
      modprobe: FATAL: Module cdc-acm not found in directory /lib/modules/5.10.77
      
      posted in Other Peripherals
      roberts_lando
      roberts_lando
    • RE: Patron stucked after some hours

      @Martin-Kudláček After the upgrade with latest firmware the stucked problem is solved but now RS485 ports are no longer working and keep return timeout error.

      Any updates?

      posted in Other Peripherals
      roberts_lando
      roberts_lando
    • RE: Patron stucked after some hours

      @administrators

      posted in Other Peripherals
      roberts_lando
      roberts_lando
    • Patron stucked after some hours

      Hi everyone. I have many Patron units out there, seems that after some hours or at most a day they gets stuck. I have checked the RAM/CPU usage, network status, I/O status and I cannot identify the root cause of the problem. Does anyone know what could be the root cause of this?

      When I say stuck I mean I cannot connect it via ssh or webserver, before getting completely stucked it starts becoming slow. Suggestions?

      posted in Other Peripherals
      roberts_lando
      roberts_lando
    • RE: Bugs In Latest Axons

      @PhilesG The steps (if done correctly) only resize the partition so no data is lost. BTW is something goes wrong it could. I know @Martin-Kudláček also proposed me to create a script to automatically fix the partition problem, I think that would be the safer way

      posted in Ubuntu Core
      roberts_lando
      roberts_lando
    • RE: Unipi G100 Setup static ip on both interfaces eth0 eth1

      I fixed by simply removing gateway and dns-nameservers definitions from the eth1 file.

      If anyone is interested in this the solution to make this working with also the gateway check: https://www.thomas-krenn.com/en/wiki/Two_Default_Gateways_on_One_System

      posted in Other Peripherals
      roberts_lando
      roberts_lando
    • Unipi G100 Setup static ip on both interfaces eth0 eth1

      Hi, I would like to setup both eth interfaces with a static ip. By default the content of /etc/network/interfaces.d/ directory is:

      root@G100-sn26:/etc/network/interfaces.d# ls
      br0  eth0  eth1
      root@G100-sn26:/etc/network/interfaces.d# cat br0 
      
      auto br0
      iface br0 inet dhcp
          bridge_ports eth0 eth1
      
      root@G100-sn26:/etc/network/interfaces.d# cat eth1
      
      allow-hotplug eth1
      iface eth1 inet manual
      
      root@G100-sn26:/etc/network/interfaces.d# cat eth0
      
      allow-hotplug eth0
      iface eth0 inet manual
      
      

      This means that there will be an interface br0 with DHCP enabled and all traffic from both interfaces is bridged from one to the other (like a switch).

      What I would like to do is have both interfaces setted up with a static ip (in 2 differents networks). What I tried is to remove the br0 interface and then setup eth0 like follow:

      root@G100-sn26:/etc/network/interfaces.d# rm br0 
      root@G100-sn26:/etc/network/interfaces.d# cat eth0
      allow-hotplug eth0
      iface eth0 inet static
      address 192.168.1.60
      netmask 255.255.255.0
      gateway 192.168.1.1
      dns-nameservers 8.8.8.8 8.8.4.4
      

      If I restart the network service the eth0 interface is working correctly but now If I do the same with eth1:

      root@G100-sn26:/etc/network/interfaces.d# cat eth1
      allow-hotplug eth1
      iface eth1 inet static
      address 192.168.2.60
      netmask 255.255.255.0
      gateway 192.168.2.1
      dns-nameservers 192.168.2.1
      

      the device stops responding and I have to put it in service mode to restore the default interfaces configuration. How can I do this?

      posted in Other Peripherals
      roberts_lando
      roberts_lando
    • RE: Bugs In Latest Axons

      If anyone got this issue the main problem was caused by the wrong partition table on some new Axons units.

      In order to be able to restore your backups you have to:

      1. Flash a valid image like https://kb.unipi.technology/en:files:software:os-images:00-start?redirect=1#axon_opensource_os
      2. Connect using ssh to the Axon and follow the steps on my previous comment to resize the partitions correctly (remember, once you fix the partition table to reboot and use the resize2fs command to expand the filesystem
      3. Shutdown your axon and restore the backup

      @Martin-Kudláček I hope that next Axons units will have this bug fixed as it becomes very difficult (and time loss) for me do all this steps in multiple axons

      posted in Ubuntu Core
      roberts_lando
      roberts_lando
    • RE: Bugs In Latest Axons

      @Martin-Kudláček I'm using a customized image of the axon, that was my only way to backup/restore multiple devices in a quick way. How can I do it now?

      I really need this or for me it's almost impossible to work with them. I have spent two days tring to figure out what's happened. I have then created a "restore usb" using this image: https://kb.unipi.technology/en:files:software:os-images:00-start?redirect=1#axon_opensource_os

      Starting from that I have installed all the software needed and created a backup of that but I'm not able to restore it anyway in other axons.

      Also there is a bug in all latest models I have received as no one is able to go in service mode, the run led keeps blink every second and the raws leds never switch on. In able to restore that I have to reset them using the image I previously linked here.

      I will do a refund of all axons I bought If I can't find a fix of this

      posted in Ubuntu Core
      roberts_lando
      roberts_lando
    • RE: Bugs In Latest Axons

      Actually what I have done is:

      sudo /sbin/fdisk /dev/mmcblk0
      
      Welcome to fdisk (util-linux 2.29.2).
      Changes will remain in memory only, until you decide to write them.
      Be careful before using the write command.
      
      
      Command (m for help): p
      Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x92824060
      
      Device         Boot   Start      End  Sectors  Size Id Type
      /dev/mmcblk0p1        49152   253951   204800  100M 83 Linux
      /dev/mmcblk0p2       253952  3098623  2844672  1.4G 83 Linux
      /dev/mmcblk0p3      3098624 15269887 12171264  5.8G 83 Linux
      
      Command (m for help): d
      Partition number (1-3, default 3): 3
      
      Partition 3 has been deleted.
      
      Command (m for help): d
      Partition number (1,2, default 2): 2
      
      Partition 2 has been deleted.
      
      Command (m for help): n
      Partition type
         p   primary (1 primary, 0 extended, 3 free)
         e   extended (container for logical partitions)
      Select (default p): 1
      Value out of range.
         p   primary (1 primary, 0 extended, 3 free)
         e   extended (container for logical partitions)
      Select (default p): p
      Partition number (2-4, default 2): 2
      First sector (2048-15269887, default 2048): 253952
      Last sector, +sectors or +size{K,M,G,T,P} (253952-15269887, default 15269887): 15269887
      
      Created a new partition 2 of type 'Linux' and of size 7.2 GiB.
      Partition #2 contains a ext4 signature.
      
      Do you want to remove the signature? [Y]es/[N]o: N
      
      Command (m for help): p
      
      Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x92824060
      
      Device         Boot  Start      End  Sectors  Size Id Type
      /dev/mmcblk0p1       49152   253951   204800  100M 83 Linux
      /dev/mmcblk0p2      253952 15269887 15015936  7.2G 83 Linux
      
      Command (m for help): w
      The partition table has been altered.
      Calling ioctl() to re-read partition table.
      Re-reading the partition table failed.: Device or resource busy
      
      The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
      
      unipi@S105-sn470:~$ sudo reboot
      
      

      Reboot then:

      unipi@S105-sn470:~$ sudo /sbin/resize2fs /dev/mmcblk0p2 
      resize2fs 1.43.4 (31-Jan-2017)
      Filesystem at /dev/mmcblk0p2 is mounted on /; on-line resizing required
      old_desc_blocks = 1, new_desc_blocks = 1
      The filesystem on /dev/mmcblk0p2 is now 1876992 (4k) blocks long.
      

      Now the partition seems to be ok but some thing aren't working as expected.

      posted in Ubuntu Core
      roberts_lando
      roberts_lando