How to create a new BackTrack iso with kernel 2.6.34

[muts]

I haven't tested out this script extensively - feel free to give it a spin and post results here:

BackTrack ISO Kernel 2.6.34 Upgrade

[joker5bb]

well there is still a huge bug:
Gmane Loom

rt2800usb is badly broken in 2.6.34 (rt3070 chipset for the most part) fixed in 2.6.35-rcx
ath5k needs patch
ath9k gives random ssid & incorrect flags in airodump-ng

airbase-ng is broken on all drivers I tested

compat-wireless fails to compile on this kernel

[Ridgeback111]

Hi, just thought I would add some extra detail.

Updated to 2.6.34 today.

A few things broke:
Both wireless drivers below fail to load firmware.

rt73 usb adapter wireless firmware
phy1 -> rt2x00lib_request_firmware: Error - Failed to request firmware

"dpkg -L rt73-drivers" shows old drivers for 2.6.30 exist, I guess the 2.6.34 are still in work?

ipw2200 internal Dell laptop wireless firmware:
I've rmmod/modprobed ipw2200 and performed cold reboots.
Each time dmesg shows:
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
Inside /lib/firmware-2.6.34/ I have ipw-2.2-bss.fw and a few others.
I even tried making a symbolic link to trick it, but that still fails.

I bet it's a udev problem.

All of this worked great right before the kernel upgrade.

Thanks

[michelinok]

Hi, just thought I would add some extra detail.

Updated to 2.6.34 today.

A few things broke:
Both wireless drivers below fail to load firmware.

rt73 usb adapter wireless firmware
phy1 -> rt2x00lib_request_firmware: Error - Failed to request firmware

"dpkg -L rt73-drivers" shows old drivers for 2.6.30 exist, I guess the 2.6.34 are still in work?

ipw2200 internal Dell laptop wireless firmware:
I've rmmod/modprobed ipw2200 and performed cold reboots.
Each time dmesg shows:
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
Inside /lib/firmware-2.6.34/ I have ipw-2.2-bss.fw and a few others.
I even tried making a symbolic link to trick it, but that still fails.

I bet it's a udev problem.

All of this worked great right before the kernel upgrade.

Thanks

Just copy /lib/firmware/*.* from the live cd to the installed bt4 (boot from the live and copy,i had the same problem,fixed with this workaround).

[lordplagueis]

Just copy /lib/firmware/*.* from the live cd to the installed bt4 (boot from the live and copy,i had the same problem,fixed with this workaround).

thanks you are a life saver I thought my vmware image was the problem

[Ridgeback111]

Copying the original boot iso's /lib/firmware into the /lib/firmware-2.6.34 on my install did the trick!

*Note /lib/firmware is a symbolic link to /lib/firmware-2.6.34 on my boot DVD.

Thank you!

[morning_wood]

ipw2200 internal Dell laptop wireless firmware:
I've rmmod/modprobed ipw2200 and performed cold reboots.
Each time dmesg shows:
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
Inside /lib/firmware-2.6.34/ I have ipw-2.2-bss.fw and a few others.
I even tried making a symbolic link to trick it, but that still fails.

I bet it's a udev problem.

All of this worked great right before the kernel upgrade.

Thanks[/QUOTE]


confirmed

i noted that airdriver-ng gives an error about the driver being compiled on a different GCC as well
note: this is on the "live-cd" R1

[brsick]

I'm having trouble updating the kernel; the error is as follows:

Errors were encoutered while processing:
 /var/cahche/apt/archives/linux-image-2.6.34_2.6.34-10.00.Custom-bt7_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

That is after I run "apt-get update && apt-get dist-upgrade"
I have also tried to force install with "-f"
All the other upgrades seem to install fine except for the kernel; is there something I'm supposed to do manually to install the 2.6.34 kernel?

I have looked at the FAQ, How-To, etc. and haven't found an answer to my particular situation... any help is appreciated.

I am using BT4 Final in VMware.

[erdmaennchen]

Same problem for me, and I've got no idea how to fix it..

[robm999]

brsick:

I was getting the same error while trying to upgrade to 2.6.34 kernel on VMWare. The odd thing is that I did not get this error doing the same thing on Virtualbox.

Anyways, the error, at least in my case, stemmed from it being unable to unpack into /lib/firmware/ for some reason. Checked and for previous kernel there was a directory for /lib/firmware-2.6.30.9 where for the new kernel there was a link /lib/firmware -> firmware-2.6.34 problem was there was not a directory for firmware-2.6.34. I created the directory /lib/firmware-2.6.34 and, so far, all seems to be working correctly.