4.14.80 aarch64?

Overview Forums Sticky Finger’s Kali-Pi 4.14.80 aarch64?

Viewing 14 reply threads
  • Author
    Posts
    • #13552
      rjp421
      Participant

      is 4.14.80 aarch64 the correct “current stable”????

      if not, how can i revert back to 4.14.62? the kalipi- / raspberrypi- packages conflict, when i try to reinstall 4.14.62.

      i have been using 4.14.62 “current stable” on a Pi 3 with no issues.

      the other day, i decided to check for a newer kernel.

      wget’ing current-stable, dowloaded kernel 4.14.80.

      i then checked the https://re4son-kernel.com/re4son-pi-kernel/ to see what had changed, and saw it still shows 4.14.62 as current stable.

      i installed it anyway.

      after rebooting, i let it sit for a couple hours.

      when i looked again, i noticed the wifi connection had stopped working.

      checking dmesg, all i saw was a “Disassociated from AP…”.

      i rebooted it from the console to see if it would fix it. nope…

      using the console, i noticed wlan0 had dissapeared from ifconfig -a.

      dmesg after reboot: https://paste.pound-python.org/show/CWCjVqDKVDQR2PnlHYTR/

      i noticed:
      [ 4.461006] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2

      ls -al /lib/firmware/brcm/: https://paste.pound-python.org/show/gKjwZ2urSKxnjWESjA4f/

      Thanks!

    • #13555
      rjp421
      Participant

      UPDATE:

      with the help of steev from #kali-linux i was able to get wlan0 back.

      
      cd /lib/firmware/brcm
      
      wget https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/master/brcm/brcmfmac43430-sdio.txt
      
      wget https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/master/brcm/brcmfmac43430-sdio.bin
      
      reboot
      

      i assume this should only be a temp fix?

    • #13556
      Re4son
      Keymaster

      Hi rjp421

      You’re right – that package shouldn’t have been up as current. Thanks for letting me know.
      A stable 4.14.88 will be up in a day or two.

      Many thanks,
      Re4son

    • #13558
      rjp421
      Participant

      how do i properly clean up the “kalipi-“/”raspberrypi-” package conflict when trying to downgrade?

      also, the kali-pi-kernel page still shows 4.14.62 as current stable. but it is downloading “next” 4.14.69.

      https://pastebin.com/raw/nUhLck3K

      Thanks!

    • #13559
      rjp421
      Participant

      i just noticed, in the changelog.

      .69 and .62 reversed?

      Package History:

      re4son_kali-pi-tft_kernel_old = re4son_kali-pi-tft_kernel_4.1.21_current
      re4son-kernel_old = re4son-kernel_4.9.80_current
      re4son-kernel_current = re4son-kernel_4.14.69_current
      re4son-kernel_next = re4son-kernel_4.14.62_current

    • #13561
      rjp421
      Participant

      i still cannot figure out how to clean up the new “kalipi-” packages i.e. kalipi-bootloader, which blocks raspberrypi-bootloader etc. in order to downgrade.

      as of a few hours ago, the “current stable” download link still downloads 4.14.69 “next”.

      should i have made a new thread for that?

      this is bad timing, as there was a new NullByte how-to on youtube for rpi and nexmon just released the other day. tons of people are going to be confused af.

    • #13562
      Re4son
      Keymaster

      Hi rjp421,

      Sorry for that. I’m a few hours away from releasing 14.4.89 but you can just continue to use 4.14.80 and rename /boot/kernel8.img, i.e.:

      sudo mount /boot
      mv /boot/kernel8.img /boot/kernel8-alt.img

      reboot and the bootloader will pick the 32bit kernel.

      The only real difference between the new kernel package and the one you’ve got is that the installer does the renaming automatically when executed on armhf.

    • #13564
      rjp421
      Participant

      Awesome!

      looking forward to it 🙂

      Thanks!

    • #13565
      Re4son
      Keymaster

      Still working on it. Best to rename kernel8.img for now

    • #13574
      Re4son
      Keymaster

      Done, sorry for the delay.
      I’ve uploaded the latest 4.14.89 kernel as “Next”:

      https://re4son-kernel.com/download/re4son-kernel-next/

    • #13576
      rjp421
      Participant

      How can i downgrade to current stable?

      root@kali-pi3:/usr/local/src/re4son-kernel_4.14.69-20181010# ./install.sh 
      
      	++++ Install Re4son-Kernel? [Y/n] 
      
      	**** Installing custom Re4son kernel with kali wifi injection patch and TFT support ****
      
      	**** /boot is mounted ****
      
      	**** Installing device tree overlays for various screens ****
      	**** Checking for device-tree-compiler: install ok installed ****
      
      	**** Device tree overlays installed                      ****
      Selecting previously unselected package raspberrypi-bootloader.
      (Reading database ... 218691 files and directories currently installed.)
      Preparing to unpack raspberrypi-bootloader_4.14.69-20181010_armhf.deb ...
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/start.elf to /usr/share/rpikernelhack/start.elf by rpikernelhack'
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/start_cd.elf to /usr/share/rpikernelhack/start_cd.elf by rpikernelhack'
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/start_db.elf to /usr/share/rpikernelhack/start_db.elf by rpikernelhack'
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/start_x.elf to /usr/share/rpikernelhack/start_x.elf by rpikernelhack'
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/fixup.dat to /usr/share/rpikernelhack/fixup.dat by rpikernelhack'
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/fixup_cd.dat to /usr/share/rpikernelhack/fixup_cd.dat by rpikernelhack'
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/fixup_db.dat to /usr/share/rpikernelhack/fixup_db.dat by rpikernelhack'
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/fixup_x.dat to /usr/share/rpikernelhack/fixup_x.dat by rpikernelhack'
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/bootcode.bin to /usr/share/rpikernelhack/bootcode.bin by rpikernelhack'
      dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
      Leaving 'diversion of /boot/LICENCE.broadcom to /usr/share/rpikernelhack/LICENCE.broadcom by rpikernelhack'
      Unpacking raspberrypi-bootloader (4.14.69-20181010) ...
      Replaced by files in installed package kalipi-bootloader (4.14.80-20181125) ...
      dpkg: dependency problems prevent configuration of raspberrypi-bootloader:
       kalipi-bootloader (4.14.80-20181125) breaks raspberrypi-bootloader and is installed.
      
      dpkg: error processing package raspberrypi-bootloader (--install):
       dependency problems - leaving unconfigured
      Errors were encountered while processing:
       raspberrypi-bootloader
      Error completing: dpkg
      root@kali-pi3:/usr/local/src/re4son-kernel_4.14.69-20181010# uname -a
      Linux kali-pi3 4.14.80-Re4son-v7+ #1 SMP Thu Nov 22 17:05:44 AEDT 2018 armv7l GNU/Linux
      root@kali-pi3:/usr/local/src/re4son-kernel_4.14.69-20181010#

      Thanks

    • #13577
      Re4son
      Keymaster

      Just do a manual dpkg -r of the bootloader package then run the installation again

    • #13578
      rjp421
      Participant

      Thanks!

      i am doing something wrong…

      root@kali-pi3:/usr/local/src/re4son-kernel_4.14.69-20181010# dpkg -r kalipi-bootloader
      dpkg: dependency problems prevent removal of kalipi-bootloader:
       libraspberrypi0 depends on kalipi-bootloader (= 4.14.80-20181125).
      
      dpkg: error processing package kalipi-bootloader (--remove):
       dependency problems - not removing
      Errors were encountered while processing:
       kalipi-bootloader
      root@kali-pi3:/usr/local/src/re4son-kernel_4.14.69-20181010# apt -f install
      Reading package lists... Done
      Building dependency tree       
      Reading state information... Done
      Correcting dependencies... Done
      The following packages will be REMOVED:
        raspberrypi-bootloader
      0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
      1 not fully installed or removed.
      After this operation, 12.8 MB disk space will be freed.
      Do you want to continue? [Y/n] 
      (Reading database ... 218694 files and directories currently installed.)
      Removing raspberrypi-bootloader (4.14.69-20181010) ...
      root@kali-pi3:/usr/local/src/re4son-kernel_4.14.69-20181010# dpkg -r kalipi-bootloader
      dpkg: dependency problems prevent removal of kalipi-bootloader:
       libraspberrypi0 depends on kalipi-bootloader (= 4.14.80-20181125).
      
      dpkg: error processing package kalipi-bootloader (--remove):
       dependency problems - not removing
      Errors were encountered while processing:
       kalipi-bootloader
      root@kali-pi3:/usr/local/src/re4son-kernel_4.14.69-20181010# 
    • #13579
      Re4son
      Keymaster

      Oops, sorry. Change that to “apt remove”. That should take care of all dependencies

    • #13580
      rjp421
      Participant

      got it!

      thanks again 🙂

Viewing 14 reply threads
  • You must be logged in to reply to this topic.