GA36-MB V1.1-20251025 (Allwinner A33): v0.0.1 works, v0.1.0 a33_panel1 gives black screen and a33_panel2 gives vertical stripes

未關閉
#104 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
c, cpp, linux
領域
embedded-iot

研究方向

Compare the working v0.0.1 H/W Variant A image with the v0.1.0 panel1 and panel2 images for the GA36-MB V1.1-20251025 board with Allwinner A33. Start by checking the display configuration and DTB used by each image; the reporter offers to provide DTB files and additional photos. Done means identifying a compatible display configuration and confirming the screen renders correctly on this hardware.

由索引模型根據 Issue 內容生成。

描述

Hi! First of all, thanks for the project. I got goodluckOS running on my console, and I'm reporting which version worked and which didn't in case it helps other people with the same hardware.

Device

  • Console: Vaboston GA36-R36SCLONE (R36S clone)
  • Board marking: GA36-MB V1.1-20251025
  • SoC: Allwinner A33
  • Original firmware: EmuELEC 4.7 (clone image from the vaboston/GA36-R36SClone repo)

What I tried

  • v0.0.1 [H/W Variant A]: works. The console boots and goodluckOS runs normally.
  • v0.1.0, goodluck_base_a33_panel1.zip: black screen after pressing power.
  • v0.1.0, goodluck_base_a33_panel2.zip: the console boots (blue background), but the middle of the screen shows heavy vertical stripes/garbled image (photo attached).

Expected behavior
The image displays correctly on a GA36-MB V1.1-20251025.

Notes

  • It looks like the board boots, but the display config in v0.1.0 doesn't match this screen. Since v0.0.1 works, I suspect my panel is covered by Variant A but not by the current panel1/panel2 images.
  • Happy to test other builds or provide more info (DTB, photos of the board, etc.) if that helps.

Thanks again!

Image
主要語言
C++
星號
54
分支
8
平均合併
16 天 19 小時
30 天內合併 PR
4

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CodeZombie/goodluckOS 的其他 Issue

查看 CodeZombie/goodluckOS 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。