Ehud Gavron wrote:
Do you mean:
1. Reboot in 2.6.21...
2. Associate or not, do whatever you normally do, wait till it either
WON'T WORK or CRASHES
3. Reboot in FC6 (2.6.20-1.2948.fc6)
4. Send log file lines starting with bcm..
Reboot in 2.6.21 and let it run until if loses
Ok, so I was bored... and installed the 2.6.21 kernel.
I then patch -p1 combined_2.6.21.patch
make
make modules_install
make install
sync reboot -f
The bcm43xx modules reports associated... scanning... associated... with
another message in the middle, about once every half second without
Ehud Gavron wrote:
Ok, so I was bored... and installed the 2.6.21 kernel.
I then patch -p1 combined_2.6.21.patch
make
make modules_install
make install
sync reboot -f
The bcm43xx modules reports associated... scanning... associated... with
another message in the middle, about once
Just to be precise, I repeated everything. Here it is in gory detail,
except that I don't know how to capture the panic attack info because
the system is stuck and I think a camera screenshot would be lame ;)
tar -zxvf linux-2.6.21.tar.gz
mv linux-2.6.21 /usr/src
ln -s /usr/src/linux-2.6.21
Ehud Gavron wrote:
Just to be precise, I repeated everything. Here it is in gory detail,
except that I don't know how to capture the panic attack info because
the system is stuck and I think a camera screenshot would be lame ;)
tar -zxvf linux-2.6.21.tar.gz
mv linux-2.6.21 /usr/src
ln -s
Ehud Gavron wrote:
Just to be precise, I repeated everything. Here it is in gory detail,
except that I don't know how to capture the panic attack info because
the system is stuck and I think a camera screenshot would be lame ;)
Do you have the option of using netconsole to capture the
