Jump to content

RaptorSDS

Members
  • Posts

    185
  • Joined

  • Last visited

Everything posted by RaptorSDS

  1. nice to hear as far as i know there is no install to nand script there are 3 different wifi chip AP6330 ; BCM4335 and RTL8723BS ; please test in console BCM-> "modprobe dhd" than "ifconfig" dhd is Broadcom Dongle Host Drive RTL-> edit "etc/modprobe/blacklist.conf" add "blacklist dhd" at the end "restart" than "modprobe 8723bs" and "ifconfig" AP -> i have no idea when there is a driver when wlan0 show up than edit "etc/modules-load.d/modules.conf" insert driver module name or insert "modprobe xxx" at "etc/rc.local" maybe helps
  2. @Nikeb both folderss are the same dtb files , you should use the dtb folder (without -30.10) , correct copy and rename single file do not edit uEnv.ini and wait at test around 5-10min , after finish test without postive result than only possible way is serial console and extract boot.img from android , or (with a small chance that it help )take a newer image 20.05 and SSH over Ethernet without hdmi
  3. @Nikeb do not edit uENV.ini at older roms please , neo x8-H plus should be meson8m2-n200-xx.dtb files be aware the first boot maybe around 5-10minutes , when no one of this work than you could only extract android boot.img from your preinstalled Android and ask balbes150 to seperate and convert the dtb from android to armbian ; but i think extract boot.img is only possible with root android and maybe twrp as recovery image , also you can get a serial to usb adapter and solder/connect it to the onboard Serial port than you can also look at linux boot message
  4. the lastest old one is 5.77 with 3.10.108 and a desktop in the name , at 3.10.108 you have the dtb.img rename trick , at 4.19 and 5.xx Kernel you have toedit uENV.ini ; hope now it works
  5. @nikeb first if the autoscript did not install also no sd or usb boot ; secound like my answer to nikron 20.05 you must edit uENV.ini not rename dtb also 20.05 have no HDMI !!!!! maybe start with the 5.xx version (kernel 3.10) -> under OLD balbes150 ROMS
  6. No thats not possible because they use different describe for everything,
  7. @nirkon most all 5.x Kernel version (20.xx and NEXT) are without HDMI !! , its normal to have pixel logo because they only work with Ethernet(SSH) and/or Serial Console (SSH) also 5.x(20.xx ) and 4.x Version (19.xx) version need more time for first startup like 3 till 8 minutes , ( most times goes to timeframe 19.xxx secound and than you have to wait till login show up) ; for 20.xx and 19.xx version only need to edit uENV.ini !!. at the old kernel 3.10 (version 5.xx) you need for hdmi the desktop versions and also have time for first start about 5 -10 minutes, this are the ones that use the rename to dtb.img trick !!
  8. thanks a lot ; i added some Gpio and uart settingd from dts 3.10 to the dts from 5.6 maybe that solve it ;
  9. while searching for the driver i found an entry by Jerome Brunet from the kernel team (Spinics.net) Kernel Patch meson CLK cycle from 2017 where he says that he has got RTL8723bs running on mxiii plus s812 ( but i think with the old 3.10 ) i have already sent him an EMAIL but still no answer if he has activated the card with the new kernel which DTSI /DTS file did you use for the DTB m8s ? i usually try to copy the GPIO pins from the old (3.10) DTS files to the new one the r8723bs.ko file missing in net/wireless respectively drivers/staging folder ( i can not build it from torvald linux no rules in makefile) Translated with www.DeepL.com/Translator (free version)
  10. @balbes150 please can you answer my question , can you insert the rtl8723bs driver in the 20.xx image ? i found that the bin files are inside the image already only the .ko file missing . is it possible to activate the SDIO that the kernel recognize the Wireless card ? or can i copy the old .ko file from 3.10 kernel image ? R8723BS Driver -> 1x at github torvalds tree and 1xanother https://github.com/muhviehstah/r8723bs
  11. do you have ethernet cable connect ? else you can try with modprobe other eth0/wlan driver
  12. thats look like a promising way ; maybe you can make a hardware list with some commands ->Hardware list commands
  13. do you edit the uEnv.ini with the right dtb ( minix8 or MXiii-plus or m8s) , normally it should get till 40.xxx or 80.xxx with many i2c network things CPU core starting and other stuff like on page 15 the secound post from "gmytis" the secound hidden content there should at start 0.xxx some dtb menu like
  14. i think thats normal because your stock ones has a GUI and /usr/bin/sh should be your shell (script) that start the GUI ; now you can go forward and start the new 20.05 or the 19.xx armbian image from usb and than you can interact through your serial terminal with the image when it has no GUI
  15. i think this image has a static ip 192.168.0.100 or 192.168.1.100 maybe a crossover eth connect with a another pc help
  16. Yes this version is without HDMI , you have to use Serial Terminal or Headless Network Terminal ; i think maybe the menson8-minix-neo-x8.dtb is maybe the one for your box; i have normally the M8S clone but the MXIII-plus also work for me
  17. yes after 5.7 image you do not need to copy the dtb file and do not rename it ; only edit UEnv.ini first line name and location of the dtb file
  18. i have tested your 20.05 image 1 run with menson_m8s.dtb its stop(5min waited) at flush journel request by PID 1 2 run with menson_m8s.dtb its stop at GPIO23 request loop and CPU 1,2,3 shutdown and starting loop 3 run with menson_mxplusiii.dtb root login , but no wifi modules 4 run with menson_m8s.dtb now also root login!!! thanks super work please, please can you at the RTL8723bs modules for the few that have this Realtek chip , i did not want use a usb wlan stick because i need both ports is there a different between both dtb files ?
  19. the aml_update.zip is the file that you normaly use to activate linux and multiboot option from Android for bootloader (this updat the bootloader) , the aml_autoscript.zip is the one if you inside bootloader to update bootloader ( the autoscript.zip is part of the update.zip). normaly the right dtb for your device go to /boot/ (<5.5 image) or the path inside uEnv.ini (>5.7 image)
  20. i think non of this image because all are for S9xx ARM CPU and i think Tronsmart MXII are S8xx ARM CPU , mybe balbes150 can post the right link to his image
  21. Mediatek is RALink , thats this driver https://wiki.debian.org/rt2800usb you have to download the driver
  22. if is a realtek or broadcom , plugin maybe restart and than configure wlan1 , maybe setup iprouting and thats all
  23. do you test the other dtb that are inside the dtb folder because older dtb files may not compatible with dtb selector; also do you look inside extracted dbt files did it look the same structure as the dtb that are inside the folder
  24. on old image was the way to copy working dtb to boot Fat partiotion and rename to dtb.img on new image edit the uEnv.ini for selecting proper dtb file it is testing only , one after another until one is working
  25. one error i saw is that dtb file not working for you you need another one
×
×
  • Create New...