Jump to content

AaronNGray

Members
  • Posts

    104
  • Joined

  • Last visited

Everything posted by AaronNGray

  1. I have not personally modified armbianEnv.txt, I do not know how to. As I say I think the machine has been messed around with, i.e. it has been hacked.As I say I am trying to work out how to reenable /dev/mmcblk1.
  2. Weird its doing it on all distros and builds have tried so far including Debian. I can only think it must be the boards firmware ?
  3. @djurny No, its not a simple as that, its acutally not on the install on NVMe anymore.
  4. The Gnome desktop Power off menu selection and `sudo shutdown now` both reboot rather than powering down.
  5. At the same time as mmcblk1 disappeared someone had changed the ethernet port over to the secondary port as I could not get into the machine and tried the second port which had been configured to the same static IP address as the primary port was on.
  6. >PLEASE STOP! This is both a time and money nightmare for me. I am giving as much information as I can in order to give feedback in order to get support. What I am posting is not all nonsense ! Okay the Gnome downgrade was incorrect and was based on what ifnformation I could get at the time. Why the issue system put up the postgres tag I really don't know I removed it. It is now repeatedly demostratably kernel dependant. On 6.12.32-current-rockchip64 and 6.12.39-current-rockchip64 the display is failing, 6.12.22-current-rockchip64, and 6.12.17-current-rockchip64 the display is working fine. 6.15.1-edge-rockchip64 is also working fine. No sure about 6.15.7 6.16.0-rc3-edge and 6.16.1-edge are not even booting, with BananaPi-M7. I am going to get kernel output using USB UART for all these boots.
  7. mmcblk1 should be the uSDcard it is on Nobel and Bookworm, it was there before I got hacked as well.
  8. Armbian has become a total nightmare. Things keep breaking and theres no way to get a proper build of a past state anymore, so if I loose a copy of the original image I used for a machine then I am stuck again. Stuck with hardware that will not work again. And this hardware costs a lot of money, and its a lot of time too. Why Armbian was not written with this in mind I really don't know ??? The tree kernel lines supported seem to change randomly and are not in alignment with the linux kernel versions or seem to change randomly just at the wrong times.
  9. Same problem when I put `KERNELBRANCH="tag:6.12.22"` in userpatches/lib.config
  10. Its not working on a cleanly installed repo of Armbian/build ! userpatches/config-test.conf ``` EXPERT="yes" DEST_LANG="en_GB.UTF-8" BOARD="bananapim7" BRANCH="current" KERNEL_VERSION_LEVEL="6.12" KERNELBRANCH="tag:6.12.22" ``` https://paste.armbian.com/zoheruvemi
  11. Thought I got it, but not worked ! ``` cd cache/sources/linux-kernel-worktree/6.12__rockchip64__arm64/ git checkout v6.12.22 --force ```
  12. How do I go about doing that ? It more looks like its to do with the `.github` repo tag contents itself ? But if its not is there a 101 or HOWTO on this please ?
  13. @Werner https://paste.armbian.de/wikedaqena I have ordered a couple of 3.3/5v UART USB adapters. I used to have an old 5V old. Thanks !
  14. with userpatches/config-test.conf ``` EXPERT="yes" DEST_LANG="en_GB.UTF-8" BOARD="bananapim7" BRANCH="current" KERNEL_VERSION_LEVEL="6.12" KERNELSWITCHOBJ="tag:6.12.22" KERNELBRANCH="tag:6.12.22" ``` I am getting the following ``` [🌱] Producing new & caching [ GIT_INFO_KERNEL ] [🌱] Fetching SHA1 of 'tag' 'refs/heads/6.12.22^{}' [ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ] [🌱] SHA1 of tag refs/heads/6.12.22^{} [ '' ] [🌱] Failed to fetch SHA1 of 'tag' 'refs/heads/6.12.22^{}' [ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ] [🌱] Fetching SHA1 of 'tag' 'refs/heads/6.12.22' [ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ] [🌱] SHA1 of tag refs/heads/6.12.22 [ '' ] [🌱] Failed to fetch SHA1 of 'tag' 'refs/heads/6.12.22' [ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ] [🌱] Fetching SHA1 of 'tag' '6.12.22^{}' [ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ] [🌱] SHA1 of tag 6.12.22^{} [ '' ] [🌱] Failed to fetch SHA1 of 'tag' '6.12.22^{}' [ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ] [🌱] Fetching SHA1 of 'tag' '6.12.22' [ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ] [🌱] SHA1 of tag 6.12.22 [ '' ] [🌱] Failed to fetch SHA1 of 'tag' '6.12.22' [ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ] [💥] error! [ Failed to fetch SHA1 of 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git' 'tag' '6.12.22' - make sure it's correct ] ```
  15. I don't think 6.16 has rockchip64 support. The rockchip64 support seems to be in current 6.12.y. I really needed to get 6.12.22 building again but am getting problems getting it to build. How do I build the kernel of my choice ? I thought I could just create a `userpataches/config-test.conf` but thats does not seem to be working with `./compile.sh test EXPERT="yes" Can someone please give me a working example of how to build a particular kernel please, because what I was using no longer seems to work.
  16. The display was working fine on 6.12, but has now stopped. I have tried the other kernels, the vendor has issues with passwords as well for some strange reason its not recognising the set password. I am going to look into the kernel, and kernel patches if I can work out what I am doing, but Armbian with its three fixed kernel versions is a nightmare and always has been. I have had exactly the same issue with BananaPi-M3. The fact Armbian will not build old versions is stupid. I can select older kernels using armbian-config and these work. If armbian/build would allow the user to select the same kernel images as armbian-config can this would go some way to solving this issue.
  17. `ls /dev` is not showing mmcblk1. I have Armbian Ubuntu install that may have been messed around with and is not showing /dev/mmcblk1, where as a fresh uSCDCard install is.
  18. Okay partially solved, its the Linux rockchip64 kernel version. On 6.12.32-current-rockchip64 the display is failing, 6.12.22-current-rockchip64, and 6.12.17-current-rockchip64 the display is working fine. 6.15.1-edge-rockchip64 is also working fine. 6.16.0-rc3-edge is not even booting, with BananaPi-M7. @amazingfate Would it be possible to look into this please.
  19. @laibsch It would be good to get this solved as there are a lot of boards out there and they are expensive kit, also this effects both Armbian Ubuntu as well as Debian. I was hapilly running my own Ubuntu Plucky Armbian Unofficial and had desktop functioning fine on my BananaPi-M7 for several apt-get upgrades. I use ssh mainly as I run it as a server for development purposes, but like to use desktop for dev purposes too. Then suddenly the screen went blank and looked like it was continually trying to start up. On reinstalling Armbian Ubuntu Nobel, then Plucky again I worked out that Gnome had been running as v46, but at some point Ubuntu had reverted to v44. I am not sure if this was the breaking change but it seems to at least be parallel. i.e. it was working and I can demonstrate it working and not working repeatedly. Hi @Cesar R. I will run through your repo mods tomorrow and see if I can replicate. It would be good to get this fixed for both Ubuntu and Debian on BananaPi-M7 and Radxa Rock 5B+ and the other boards for Armbian. As I say theres a lot of boards out there and they are expensive. Maybe some of the board manufacturers would pay towards the fix also ? I am just in it for the solution as I need the boards for dev work.
  20. @Werner - When the Armbian Official Nobel upgrades it has the same issue. Will look at going back to Debian tomorrow.
  21. @Igor@amazingfate Can someone look at this issue please ? I am wondering if this is possibly affecting a large number targets or whether its just BananaPi-M7 / rockchip64 ? I have tried on another monitor also and am getting a black screen. On doing an `apt-get upgrade` on ssh terminal I happened to loose by HDMI display. AFAICT It looks like Ubuntu 'backgraded' gnome v46 (in Nobel release, and also in my older unofficial image) to v44. https://armbian.atlassian.net/jira/software/c/projects/AR/issues/AR-2702?jql=project %3D "AR" ORDER BY created DESC
  22. I am unable to reload or restart sshd now for some reason ?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines