Jump to content

Search the Community

Showing results for tags 'bananapim3'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 6 results

  1. I am trying to build an old debian stretch image for checking my BananaPi M3 boards. I had it and Jessie running fine for years, but buster is causing issues with soft boot and reboots failing. So wanted to check the boards integrity with stretch. I have tried git checkout -b v20.02 remotes/origin/v20.02 which I thought was around the right time but I am just getting Buster being offered. I am using Ububtu Jammy for building.
  2. Hello ! I have a Banana Pi M3 that has 0 output on every pin. I measured 0 output using an oscilloscope. I have been on all of the forums I can think of and I got no answer. How can I make the pins of this damned board work like the ones from a Raspberry Pi ? How does one define a pin ? What does defining a pin means ? Because the pins look dead to me. How do I make them start ? How do I make them to output something... anything ? I am a total and complete noob and I have no idea of the kernel voodoo that has to be done. I am using ARMBIAN 5.83 stable Debian GNU/Linux 9 (stretch) 4.19.38-sunxi
  3. Hi to everyone, I'm new at armbian forum, but following the project since some month. As far as I can tell all contributors make a great job to enable a stable debian based distribution to many as possible arm-based boards. Thanks a lot for this great job. I bought one of the first available Banana Pi M3-boards in Germany, because I wanted (and did it already very successfully) to set up a small server for email, music storage, mythtv-backend, read out my central heating.... Until now I use a stripped down image based on the provided Ubuntu 16.04 image from http://www.banana-pi.org/m3-download.html As you all know the "support" and further development of the OEM is more or less not there, and the provided image is based on kernel 3.4 (and not updated for ages). Until now it was more-or-less a "beauty mistake" for me, but not a real problem. But some weeks ago the mythtv-project released a new version, and installing this new version needs more-or-less a newer version of ubuntu (or debian in general). So now I have 2 possibility: 1. Buy a better supported board 2. Get the latest armbian running on this board Solution 1 seems to be the simplest way, but I don't want to go this way until 2nd is not completely impossible. But I have not the knowledge to make way 2 by myself. I know Banana Pi M3 is very very unloved in the community, but as far as I understand https://linux-sunxi.org/Linux_mainlining_effort and https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=359b5a1e1c2d81af6d68de509e11d08ab4c150dc great success was made to implement this board into kernel 4.14. So I want to make a promise to give a donation of 100€ to the armbian project if this board will be supported by armbian until X-mas 2017. Main goals which have to work: - Boot into CLI debian Stretch - onboard USB host - onboard I2C - onboard Ethernet Networking - actual mainline Kernel (4.14?) - support for this board on regular level (.conf) instead of actual level (.csc) Not needed (but of course not "forbidden") - Graphical support - Sound - USB OTG Please be so kind and tell what you think about this idea. Thanks Robert
  4. Is there a build for the BPI M3 at all or is the M2 compatible ?
  5. I use "Semi_Armbian_5.07_M3", how can I mount blank SD? When I boot from eMMC with blank SD inside - System will not start (First boot A83T is from SD) , When I plug when the systen is already running - is not recognized. Do we need 'redirector' on SD-Bootsector? (like PC+ Floppy Disk) ? After inserting the SD: root@BananaPiM3:~# 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: 0x000ac9e8 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 * 204800 729087 524288 256M c W95 FAT32 (LBA) /dev/mmcblk0p2 729088 15269887 14540800 7G 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 root@BananaPiM3:~# cat /proc/partitions major minor #blocks name 179 0 7634944 mmcblk0 179 1 262144 mmcblk0p1 179 2 7270400 mmcblk0p2 179 32 4096 mmcblk0boot1 179 16 4096 mmcblk0boot0 root@BananaPiM3:~# blkid -c /dev/null /dev/mmcblk0: PTUUID="000ac9e8" PTTYPE="dos" /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="BPI-BOOT" UUID="4621-6220" TYPE="vfat" PARTUUID="000ac9e8-01" /dev/mmcblk0p2: LABEL="BPI-ROOT" UUID="c551b64c-2f93-4c4c-b35b-5b1680f8a207" TYPE="ext4" PARTUUID="000ac9e8-02" Great eW #tkaiser have you this (Semi_Armbian_5.07_M3) like minimal? Without X? Thx. (ich putze nich gerne )
  6. I have a little problem: my fstab: root@osirisBpiM3:~ # cat /etc/fstab /dev/mmcblk0p2 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,rw,nosuid 0 0 /var/swap none swap sw 0 0 //192.168.0.11/media /mnt/openelec/media cifs iocharset=utf8,credentials=/root/.smbcredentials,uid=1000 0 0 //192.168.0.11/media2 /mnt/openelec/media2 cifs iocharset=utf8,credentials=/root/.smbcredentials,uid=1000 0 0 //192.168.0.11/big850gig /mnt/openelec/big850gig cifs iocharset=utf8,credentials=/root/.smbcredentials,uid=1000 0 0 //192.168.0.2/C$ /mnt/sophie/c cifs iocharset=utf8,credentials=/root/.smbcredentialssophie,uid=1000 0 0 //192.168.0.2/D$ /mnt/sophie/d cifs iocharset=utf8,credentials=/root/.smbcredentialssophie,uid=1000 0 0 //192.168.0.2/E$ /mnt/sophie/e cifs iocharset=utf8,credentials=/root/.smbcredentialssophie,uid=1000 0 0 I can mount my disks without problems from command or with 'mount -a', but ... after boot - nothing . The parameters 'ntlm' or 'ntmlv2' in fstab does not help root@osirisBpiM3:~ # dmesg | grep CIFS [ 19.723100] CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3 [ 20.030750] CIFS VFS: Error connecting to socket. Aborting operation [ 20.030765] CIFS VFS: Error connecting to socket. Aborting operation [ 20.030820] CIFS VFS: Error connecting to socket. Aborting operation [ 20.058421] CIFS VFS: cifs_mount failed w/return code = -111 [ 20.058445] CIFS VFS: cifs_mount failed w/return code = -111 [ 20.090249] CIFS VFS: cifs_mount failed w/return code = -111 [ 20.730759] CIFS VFS: cifs_mount failed w/return code = -112 [ 20.730766] CIFS VFS: cifs_mount failed w/return code = -112 [ 20.731042] CIFS VFS: cifs_mount failed w/return code = -112 root@osirisBpiM3:~ # cat /proc/fs/cifs/DebugData Display Internal CIFS Data Structures for Debugging --------------------------------------------------- CIFS Version 1.78 Features: Active VFS Requests: 0 Servers: 1) Name: 192.168.0.2 Domain: DOM Uses: 3 OS: Windows 7 Ultimate 7601 Service Pack 1 NOS: Windows 7 Ultimate 6.1 Capability: 0x1e3fc SMB session status: 1 TCP status: 4 Local Users To Server: 1 SecMode: 0x3 Req On Wire: 0 Shares: 1) \\192.168.0.2\E$ Mounts: 1 Type: NTFS DevInfo: 0x20 Attributes: 0xc700ff PathComponentMax: 255 Status: 0x1 type: DISK DISCONNECTED 2) \\192.168.0.2\D$ Mounts: 1 Type: NTFS DevInfo: 0x20 Attributes: 0xc700ff PathComponentMax: 255 Status: 0x1 type: DISK DISCONNECTED 3) \\192.168.0.2\C$ Mounts: 1 Type: NTFS DevInfo: 0x20 Attributes: 0xc700ff PathComponentMax: 255 Status: 0x1 type: DISK DISCONNECTED MIDs: 2) Name: 192.168.0.11 Domain: WORKGROUP Uses: 3 OS: Unix NOS: Samba 3.6.25 Capability: 0x80f3fd SMB session status: 1 TCP status: 4 Local Users To Server: 1 SecMode: 0x2 Req On Wire: 0 Shares: 1) \\192.168.0.11\big850gig Mounts: 1 Type: NTFS DevInfo: 0x20 Attributes: 0x1000f PathComponentMax: 255 Status: 0x1 type: DISK DISCONNECTED 2) \\192.168.0.11\media2 Mounts: 1 Type: NTFS DevInfo: 0x20 Attributes: 0x1000f PathComponentMax: 255 Status: 0x1 type: DISK DISCONNECTED 3) \\192.168.0.11\media Mounts: 1 Type: NTFS DevInfo: 0x20 Attributes: 0x1000f PathComponentMax: 255 Status: 0x1 type: DISK DISCONNECTED Any idea? Sorrry @tkaiser it is the moronic 3.4.39-BPI-M3-Kernel from sinovoip Great
×
×
  • Create New...