search

seemoo-lab / nexmon

The C-based Firmware Patching Framework for Broadcom/Cypress WiFi Chips that enables Monitor Mode, Frame Injection and much more
GNU General Public License v3.0
2.43k stars 453 forks source link

install question #624

Open liuchengzhi314159 opened 2 months ago

liuchengzhi314159 commented 2 months ago

I hope to use PI4 to study some thing。 first i used 2022-01-28-raspios-bullseye-arm64 with linux-kernel 5.10.xx-V8+.but when i cd patches/bcm43455c0/7 45 189/nexmon and
make it ,it say no have /lib/module/5.10.xx-V8+/bulid,after i apt upgrade.my kernel name is 6.1.xx-V8+. I have exchanges some image. Now ,only 2024-07-04-raspios-bullseye-arm64.img has /lib/module/6.1.xx-v8+/build.but its kernel name is linux-kernel 6.1, I think it must make somethings wrong.however,I can make brcmfmac43455-sdio.bin.but when i 'sudo make install-firmware ',it say : Makefile:4 /firmwares/bcm43455c0/7 45 189/definitions.mk :No such file or diretory make: *** No rule to make target '/firmwares/bcm43455c0/7 45 189/definitions.mk‘ .stop. i don't know what happened.

jlinktu commented 2 months ago

You forgot to source setup_env.sh in the repository's root directory.

liuchengzhi314159 commented 2 months ago

？？I m sorry。i did it!

i downloaded nexmon on windows.and copy to my PI4 and unzip nexmon-master.zip.then i did it step by step by the guide. i"m sure i

source setup_env.sh

At 2024-08-13 18:30:53, "Jakob Link" @.***> wrote:

You forgot to source setup_env.sh in the repository's root directory.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

jlinktu commented 2 months ago

You have to do this every time you generate a new shell environment, e.g. when opening a new emulated terminal, switching to a fresh terminal emulator tab, ... Alternatively, you can put the source command in whatever file gets sourced by your shell when created, e.g.~/.bashrc (when putting it there, remember to source that file in open shells or simply restart them).

liuchengzhi314159 commented 2 months ago

im sorry.. how can i put the source command into /.bashrc ?

At 2024-08-13 20:42:40, "Jakob Link" @.***> wrote:

You have to do this every time you generate a new shell environment, e.g. when opening a new emulated terminal, switching to a fresh terminal emulator tab, ... Alternatively, you can put the source command in whatever file gets sourced by your shell when created, e.g. ~/.bashrc (when putting it there, remember to source that file in open shells or simply restart them).

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

jlinktu commented 2 months ago

Please use the online search service of your choice to figure that out.

liuchengzhi314159 commented 2 months ago

Sorry, the problem is still not solved. I followed the instructions step by step in the same terminal and still have the problem in issue, known to be unsolvable

At 2024-08-14 15:51:22, "Jakob Link" @.***> wrote:

Please use the online search service of your choice to figure that out.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>