Jump to content

dkebler

Members
  • Posts

    10
  • Joined

  • Last visited

  1. ok so I try to load the module manually and get modprobe --first-time drm_mipi_dsi modprobe: ERROR: could not insert 'drm_mipi_dsi': Module already in kernel so it's already in the kernel so WHY is the DSI device not recognized and loaded (its not listed with lsmod) IF it's auto detected in order to load well the cable to the lcd is connected and it was working with android.
  2. Still trying to get this to work. I did see that the kernel config has enabled it. So apparently that kernel module is loaded. `CONFIG_DRM_MIPI_DSI=y` but `CONFIG_DRM_PANEL_DSI_CM=m` is a loadable module The two DSI modules that that be loaded are apparently `cat /lib/modules/$(uname -r)/modules.builtin | grep dsi` kernel/drivers/gpu/drm/drm_mipi_dsi.ko kernel/drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.ko ` so I added those to /etc/modules dw_mipi_dsi drm_mipi_dsi but on reboot they are not listed by lsmod.| grep dsi So am I barking up the right tree? How come these built-in modules won't load in this way?
  3. I've got jammy running but I have a dsi display for the board and I'd like that to work (well the tp port too) with jammy. Looking at armbian config I see no setting for it. I know the display works fine as if I load an aryufan android image it works as it is set to use DSI by default. Does this kernel know about the DSI port? Do I have to build a custom kernel? If not then what boot env line will get it going?
  4. I tried flashing the spi u-boot, 2020 arufan version. Honestly not sure it took as I saw nothing on the monitor so had no idea if it was successful but now jammy server/cli version boots
  5. maybe one of the armbian dev's can help us troubleshoot/track down the issue. @admin
  6. yup, it's stuck at the exact same place . `booting using the ftd blob...` I used 5.18 (latest) so this hasn't been resolved with 5.18 jammy edge. These are likely CI generated and only us who actually have boards know this isn't booting. focal versions and dietpit versions are booting so only the jammy versions are the problem. Not sure how we can resolve this. I don't know enough to track down the problem., Thoughts?
  7. Nevermind, 😙 kept trying reformatted stick again and it worked. So for those having this issue make sure to format your stick to MBR not GPT and then make a FAT32 partition.
  8. Getting stuck out of the gate (of course never goes as documented🤣) https://puhoy.github.io/posts/armbian_on_espressobin/ While attempting to flash the required uboot update I keep getting a "permission" type error I've tried with usb stick and sd card, formated ext4, formatted fat and various permutations including simple filename....all give the same error even though usb and mmc commands say the media is there This is a v5. I have an identical one I set up a few years ago with ubuntu 18 but I did not have to flash this new uboot. Any thoughts? Do one of the jumpers have to be set in order to flash? Marvell>> usb info 1: Hub, USB Revision 3.0 - U-Boot XHCI Host Controller - Class: Hub - PacketSize: 9 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 1: Hub, USB Revision 2.0 - u-boot EHCI Host Controller - Class: Hub - PacketSize: 64 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 2: Mass Storage, USB Revision 2.0 - SanDisk Corporation Staples Relay SNDK7E38850327C07602 - Class: (from Interface) Mass Storage - PacketSize: 64 Configurations: 1 - Vendor: 0x0781 Product 0x5202 Version 0.32 Configuration: 1 - Interfaces: 1 Bus Powered 200mA Interface: 0 - Alternate Setting 0, Endpoints: 2 - Class Mass Storage, Transp. SCSI, Bulk only - Endpoint 1 In Bulk MaxPacket 512 - Endpoint 1 Out Bulk MaxPacket 512 Marvell>> bubt flash-image-DDR3-2g_2cs_7-1000_800.bin spi usb Burning U-BOOT image "flash-image-DDR3-2g_2cs_7-1000_800.bin" from "usb" to "spi" USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found ** File not found flash-image-DDR3-2g_2cs_7-1000_800.bin ** Error: Failed to read file flash-image-DDR3-2g_2cs_7-1000_800.bin from usb exit not allowed from main input shell. Marvell>> mmc info Device: sdhci@d0000 Manufacturer ID: 3 OEM: 5344 Name: SU08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.4 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes Marvell>> bubt flash-image-DDR3-2g_2cs_7-1000_800.bin spi mmc Burning U-BOOT image "flash-image-DDR3-2g_2cs_7-1000_800.bin" from "mmc" to "spi" Card did not respond to voltage select! mmc_init: -95, time 42 MMC Device 1 not found No SD/MMC/eMMC card found Error: Failed to read file flash-image-DDR3-2g_2cs_7-1000_800.bin from mmc exit not allowed from main input shell.
  9. Looking at master branch for that tag that would be no as there is no patch/kernel/sunxi-dev folder in the master for that tag https://github.com/armbian/build/tree/v2021.05/patch/kernel so does this patch have to be moved into the sunxi-current to be included in the release (or manual) builds from master branch? So if I want build to inlcude this which branch/tag should I use? It's not clear to me. Or...when might this patch eventaully make it into the master branch latest tag? I've never built a kernel or complete image for armbian so I'm kinda stabbing in the dark when it comes to repo structure and where commits get put and when and why. Any tips welcome.
  10. so has this patch been incorporated into any of the most recent builds?? https://github.com/armbian/build/commit/d49be78b702d7779f78d2655126a56e7f2ea7426 I just downloaded (7/10/21) Armbian_21.05.1_Pinebook-a64_focal_current_5.10.34_xfce_desktop.img.xz and it has the same issue so I am guessing no? In which case if I build it myself it should be incorporated? i.e. the build is based on latest source?
×
×
  • Create New...