View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002610 | Kali Linux | Kali Package Bug | public | 2015-09-01 17:52 | 2018-01-29 11:54 |
Reporter | pkreuzt | Assigned To | g0tmi1k | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | suspended | ||
Summary | 0002610: Cannot change wireless MAC with Ralink 3070 and Beaglebone Black 3.8.13 kernel | ||||
Description | Beaglebone Black Kali 2 image ships with older 3.8.13 kernel, which has a bug preventing MAC changes on rt2x00 driver. Don't know if this problem could be patched in-kernel or it requires a newer kernel. This image ships with 3.8.13-bone53 which is a very old version from an abandoned repo. For example, the Debian Jessie image for Beaglebone ships with 3.8.13-bone74 and has installable .debs for a lot of newer kernels from http://www.rcn-ee.com/. In my case I'm using 4.1.6-bone15 with good results. In Kali it's impossible to add another kernel without rebuilding the whole image. | ||||
Steps To Reproduce | Try to change default MAC for wireless Ralink device, with macchanger, udev rule or any way. | ||||
Additional Information | The bug in question: http://comments.gmane.org/gmane.linux.kernel.wireless.general/108248 Newer kerneles for BBB: https://github.com/RobertCNelson/linux-stable-rcn-ee | ||||
I know we need to upgrade the kernel, and I intend to, however there was an issue with the script used to build the kernel where it was pulling down it's own cross compiler that was incompatible with kali 1.x. Now that 2.0 is out, I need to revisit it, it's on my todo list. That being said, it does not require building the image from scratch to replace the kernel. Replace the /boot/zImage file with yours, put the dtb files in /boot/dtbs, put the modules in /lib/modules, and the firmware in... /lib/firmware At that point, it should pick your kernel up and use it. If it doesn't, I'd need to see a log file from a serial console booting up to see why it isn't working. |
|
Sorry, I was not clear enough. With "rebuilding the whole image" I meant you cannot install another kernel as a .deb like in Debian, with vmlinuz, initrd and so, so you have to rebuild your own kernel in zImage format and install manually as you said. Also, in Debian is simpler to configure booting kernel (you can have more than one installed through debs) adding a uname_r= line in uEnv.txt, for example: uname_r=4.1.6-bone15 And leave other installed kernels commented out. |
|
These images are a base starting point, and a best effort. They are by no means meant to cover every corner case. You're definitely free to add it in - the scripts are on github, and we do accept pull requests! Keep in mind that I have 29 different machines to take care of, so sometimes things get behind - I'd love to move to using debs for all of the kernels, and the bbb is a perfect candidate for it. If you've got the time to put in to doing it, I'd be more than happy to merge it in! |
|
Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported. Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)? If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup? |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2015-09-01 17:52 | pkreuzt | New Issue | |
2015-09-01 23:03 | steev | Note Added: 0003866 | |
2015-09-02 20:33 | pkreuzt | Note Added: 0003874 | |
2015-09-02 22:26 | steev | Note Added: 0003875 | |
2015-09-03 09:53 | rhertzog | Product Version | kali-dev => |
2018-01-29 11:54 | g0tmi1k | Assigned To | => g0tmi1k |
2018-01-29 11:54 | g0tmi1k | Status | new => closed |
2018-01-29 11:54 | g0tmi1k | Resolution | open => suspended |
2018-01-29 11:54 | g0tmi1k | Note Added: 0008100 |