Jump to content

Search the Community

Showing results for tags 'orangepizero2w'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Volunteering opportunities
  • Part time jobs

Categories

  • Official giveaways
  • Community giveaways

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

  1. Hi, How to enable i2c on PI8(SDA) and PI7(SCL)? I'm newbie in linux and not really understand what am I actually doing so I tried to make it with chatgpt but still not working. root@orangepizero2w:/# sudo i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- It can't see any device, but there should be one on the 0x21. Could somebody help me out with this? dmesg | grep i2c [ 0.739582] i2c_dev: i2c /dev entries driver [ 0.739878] mv64xxx_i2c 7081400.i2c: can't get pinctrl, bus recovery not supp orted [ 0.740303] i2c 0-0036: Fixed dependency cycle(s) with /soc/pinctrl@300b000 [ 1.340117] sun50i-h616-pinctrl 300b000.pinctrl: unsupported function i2c0 on pin PI8 [ 1.340132] sun50i-h616-pinctrl 300b000.pinctrl: unsupported function i2c0 on pin PI7 [ 1.340141] mv64xxx_i2c 5002000.i2c: there is not valid maps for state defaul t [ 1.340264] sun50i-h616-pinctrl 300b000.pinctrl: unsupported function i2c0 on pin PI8 [ 1.340279] sun50i-h616-pinctrl 300b000.pinctrl: unsupported function i2c0 on pin PI7 [ 1.340287] mv64xxx_i2c 5002000.i2c: there is not valid maps for state defaul t [ 1.341370] axp20x-i2c 0-0036: AXP20x variant AXP313a found [ 1.342890] axp20x-i2c 0-0036: AXP20X driver loaded [ 269.046993] i2c i2c-2: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 271.094978] i2c i2c-2: mv64xxx: I2C bus locked, block: 1, time_left: 0 Tried to edit device tree via armbian-config (now it is probably kinda messy): armbianEnv.txt: verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun50i-h618 overlays=i2c0 i2c1 i2c2 i2c3 uart5 param_uart1_rtscts=1 param_uart2_rtscts=2 param_uart2_rtscts=3 param_uart2_rtscts=4 param_uart2_rtscts=5 rootdev=UUID=88b03ed8-436d-4226-bf01-975ceef8cc1b rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
  2. Hi everyone! I wonder if modifying the "fbdev" driver to use Mali GPU to improve gaming performance is possible. I enabled `gpu` dtb, but according to "glxinfo -B" it uses "Device: llvmpipe, Accelerated: no". I'm curious if this can be improved somehow. BTW I found this old commit for Odroid C2: link
  3. I've seen this question asked quite frequently here and all the posts end before there is a solution. I think it's time we had a crystal clear discussion on how it can be done. Not just for my curiosity, but for the people who've asked before and for the people who will ask in the future. The reason: Many hats/shields designed for RaspberryPi would otherwise be compatible with OrangePi if Armbian/u-boot didn't direct the debug output to UART0. UART0 is the most commonly used serial connection for hats/shields designed for RaspberryPi. OrangePi has multiple UART gpio so it would make sense for the O.S. (Armbian) to use the one that least impacts the users ability to actually use their hardware. Debug output is important but not so much so that the user cannot easily disable it.
  4. I'm trying to enable GPU support for watching youtube on orange pi 2 zero w model. But there is no Mali driver and even kernel package How can I enable this?
  5. Hello, I have recently setup Armbian on my Orange Pi Zero 2W for a project I am working on. Everything works great so far but one thing I have noticed is that permissions feel much reduced to my user account. I require sudo to do basically everything from create a file in the home folder to use apt. This feels very different from the feel of the Raspbian install on like a Raspberry Pi. Is there any way I can change the user permissions so I won't have to use sudo for everything? Its been a bigger problem for a project I'm using Clion for where files are synced between my laptop to the pi using SFTP and Rsync but I constantly get errors about unable to create or transfer files and folders due to permission errors causing me to need to delete the remote changes and manually copy them over with sudo. I understand that doing this compromises security and is riskier but I'm fine with that. Any and all help would be great
  6. Hello Armbian community, Firstly, thank you for the amazing work that you do. Having Armbian has made the setup process so simple, and I really appreciate that I'm completely new to the world of SBCs and Armbian (but not Linux), and this issue had me stumped for a long time. I wanted to share the solution for those who are in the same position as me, as I only found this on Raspberry Pi resources. Sorry if this has already been covered elsewhere in the forums - my searches didn't show any answers from here, and additionally, I keep getting time-locked (forced to wait 30sec) for every forum search. The model of OPI I have is the Orange Pi Zero 2W 4G RAM. I installed the Armbian Bookworm image (Armbian_24.2.6_Orangepizero2w_bookworm_current_6.6.28_minimal.img.xz). The SD card I'm using is a 32GB SanDisk card that is A1 speed. That was a lucky purchase considering I knew nothing of SD cards when I bought it - I just got the cheap thing, lmao. The Problem & its Symptoms The issue I initially had was that when I would try to SSH into my OPI, it would hang for a really long time after inputting user credentials before spitting out something or other about a broken pipe (in other words, timed out because of no user input). I could ping the OPI and it would return the appropriate results: PING 192.168.1.154 (192.168.1.154) 56(84) bytes of data. 64 bytes from 192.168.1.154: icmp_seq=1 ttl=64 time=127 ms 64 bytes from 192.168.1.154: icmp_seq=2 ttl=64 time=4.15 ms 64 bytes from 192.168.1.154: icmp_seq=3 ttl=64 time=2.13 ms 64 bytes from 192.168.1.154: icmp_seq=4 ttl=64 time=3.97 ms 64 bytes from 192.168.1.154: icmp_seq=5 ttl=64 time=5.19 ms 64 bytes from 192.168.1.154: icmp_seq=6 ttl=64 time=2.80 ms ^C --- 192.168.1.154 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5007ms rtt min/avg/max/mdev = 2.133/24.182/126.853/45.926 ms Unlike a lot of other posts on the forum where the host was unreachable, it wasn't a problem in this instance. I made sure to run `# systemctl enable --now ssh` for the SSH service when setting up for the first time. When I'd try to SSH in, `systemctl status ssh` would say the session was open for my client. Unfortunately, on the client side that was never reflected, but it did show that there wasn't any other kind of network problem at play. The same problem happened without any firewall enabled, so that was not the problem either. I reinstalled the OS 3 times, all times using Balena Etcher, though the first time I did it directly from the .img file rather than the .xz archive. The issue was still not fixed after all those times. There was the option to reset the OpenSSH host keys but I thought every reinstall I did effectively did that anyway, so I didn't bother. :> After a bit of searching elsewhere, I discovered this: https://raspberrypi.stackexchange.com/questions/143142/has-anyone-solved-raspberry-pi-zero-w-ssh-client-loop-send-disconnect-broken Basically, "...open-ssh has relatively recently begun using quality-of-service (QoS) metrics to try to optimize its performance based on the expected behavior of the connection, and its default is to assume a reliability that the Pi Zero W's tiny wifi simply can't deliver; as a result it gets caught waiting for lost packets rather than retrying." The Solution As outlined in the linked post: 1. Open /etc/ssh/sshd_conf with your editor of choice 2. Append `IPQoS 0x00` to the file (append meaning add at the end). This disables the quality of service metrics 3. Restart SSH service (`# systemctl restart ssh`) I can now SSH into the OPI nicely. Yay! ___ ____ _ _____ ______ __ / _ \| _ \(_) |__ /___ _ __ ___|___ \ \ / / | | | | |_) | | / // _ \ '__/ _ \ __) \ \ /\ / / | |_| | __/| | / /| __/ | | (_) / __/ \ V V / \___/|_| |_| /____\___|_| \___/_____| \_/\_/ Welcome to Armbian 24.2.6 Bookworm with Linux 6.6.28-current-sunxi64 No end-user support: community creations System load: 2% Up time: 19:30 Memory usage: 4% of 3.84G IP: 192.168.1.154 CPU temp: 46°C Usage of /: 7% of 29G [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ] Last login: Thu May 9 18:06:47 2024 from 192.168.1.104 orangepi@orangepizero2w:~$ I hope this helps anyone who comes across it, and that it wasn't something extremely obvious that I just missed... ^^; But also, maybe it could be fixed in new Armbian images (if possible)? This could stump other newbies if left as is.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines