PDA

View Full Version : HOWTO: Use b43 driver with 14e4:4315 (Broadcom bcm4312 rev 01)



Pages : 1 [2] 3 4

amigec
December 26th, 2009, 10:42 PM
I dont know where is problem, I blacklisted b43 driver from loading on startup because sometimes it wont boot. When it boot I typed modprobe b43 to load driver. Driver loaded successfully and I can connect to my AP, I have IP adress but i cant access Internet. When I want to put card in monitor mode, it stops working after 10 seconds and dmesg | grep b43 says DMA error, then my system freeze. I tryed reset wlan module 3 times, I think I'll buy another wireless card.
EDIT: dmesg | grep b43 says
[ 812.821913] b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000400, 0x00000000, 0x00000000
[ 812.821922] b43-phy0: Controller RESET (DMA error) ...
[ 813.044260] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[ 818.577347] b43-phy0: Controller restarted

Can I load some other firmware version? Maybe this is too old.

Kevinlittleton
December 26th, 2009, 11:51 PM
Hi guys, I'm a total newbie to Ubuntu and Linux and I have a problem with my wireless connection.

When I first installed Ubunutu 9.1 I had to play around with installing a driver for the wifi card. I went with Broadcom STA wireless card which is properitery. It worked for a few days but now it won't connect to a network. It will ask for the network key but after that it does nothing.

I tried to disable and reinstall and now it's giving me this:

Please have a look at the log file for details: /var/log/jockey.log

Any ideas?

amigec
December 27th, 2009, 01:41 AM
Here is something promising but I dont know how to patch that, can someone help me?
http://lists.opensuse.org/opensuse-kernel/2009-12/msg00047.html

focwiz
December 27th, 2009, 05:00 AM
I'm afraid my wireless is a mess. I've tried many solutions (lately, the one at the beginning of this thread) with no result.

I Recently upgraded to 9.1. Wireless worked for a bit, but after a restart it vanished.

I Installed bcml.kernel, fw-cutter, etc.

Broadcom STA shows up under Admin>Drivers>Hardware Drivers, it reads:

"This driver is not activated"

I try and activate with no result. No other drivers show up.



Glidd,

Have you tried activating the STA driver while connected to the internet (wired)? That's what I had to do to activate it.

Kevin

chenxiaolong
December 28th, 2009, 09:27 PM
Kevinlittleton, could you attach the /var/log/jockey.log file to a new post? I have no way to access your computer to get the file :).

emas80
December 29th, 2009, 07:42 PM
Here is something promising but I dont know how to patch that, can someone help me?
http://lists.opensuse.org/opensuse-kernel/2009-12/msg00047.html

Hi, thank you, you find probably the cause of this problem!

The bad news is that the problem is not (totally) solved.
http://lists.berlios.de/pipermail/bcm43xx-dev/2009-December/006536.html

That is the mailing list of driver's developer, they found the problem months ago and they finally half-fixed creating a patch that should be applied to driver's source code.

I said half-fixed because they really don't know what is causing the DMA problem, but, if you search througth the mailing list, you can discover that they isolated it and they could reproduce it (and solve! after a sequence of operations like reboot, loading wl driver, cold reboot.. ecc. ecc.. I got the wifi working by doing these apparently *random* things).

By now, the only way to get the card working is, as I wrote, to patch the source with that code, and then loading b43 module in PIO mode, slower than DMA mode (I don't really know what's the difference). The patch won't be included in 2.6.33 kernel, maybe in 2.6.34 kernel.

Maybe later this night I will try to do that stuff.

chenxiaolong
December 29th, 2009, 08:39 PM
That's very good info you found! :D Could you post back with your results?

emas80
December 30th, 2009, 02:21 AM
Hi all!

I successfully patched b43 driver sources with info found on b43 developer's mailing list!
I'm writing using wireless connection :cool:.
I loaded (and surfed with!) the new driver three times, and this time I booted directly with which will be my new default configuration and it seems to work.

To make the wifi card working, you should be able to recompile a linux kernel, and you should know what a kernel module is. Please take attention, read twice, and ALWAYS make backup before to modify something - if you don't know what you are doing, ask before doing damage to your system, someone will help.

I'm currently using b43 open source driver (shipped with linux "vanilla" kernel), with b43-fwcutter Ubuntu firmware.

Here are my instructions to get things done:


Patch driver's source files. I made a .tar with my driver's source file directory (<your kernel sources>/drivers/net/wireless/b43): in my .tar, there are source files *already patched* (that are to be compiled) together with a patch/ directory containing original files and all the patches. You can see patch-rejected results, changes have been merged by hand, I hope I didn't make too many mistakes.:)Take attention: I used vanilla kernel 2.6.32.2, currently Ubuntu kernel is 2.6.31-17, I'm really sorry but the patch, as far as I read on the mailing list, should be applied to 2.6.32 kernel. I didn't even try Ubuntu kernel, I like to have last vanilla kernel, and also I read on linuxwireless.org (http://linuxwireless.org/en/users/Drivers/b43) that my Broadcom card *should* function with this kernel (it didn't). I don't know if the patch applies also to previous kernel, by reading the site probably NOT, but you can just try, remember ALWAYS to backup EVERYTHING that is supposed to be modified.
Recompile the kernel - really safe - if you know what you are doing. Or ... why don't recompile only the module?!? Please take attention, this procedure is not difficult, but if you don't know what you are doing you can damage your running kernel, so TAKE THIS AT YOUR OWN RISK - and don't try this at work :)! There is a simple instruction, go in your kernel source directory and type

make modules SUBDIRS=drivers/net/wireless/b43 This will recompile just b43 module, so in drivers/net/wireless/b43 directory you should found a shiny new b43 module. If you now type
modinfo drivers/net/wireless/b43/b43.ko you should have a little different result than giving a simple
modinfo b43 (if you have a b43 module). Yes, the last line show a new parameter, a "pio" parameter, in the recompiled driver.
If you recompiled the kernel, all is fine, just go to next step, kernel modules are already at the right place. Else, you should copy the new b43.ko in current kernel module directory. The fastest way is to simply copy the new file in /lib/modules/<your kernel>/kernel/drivers/net/wireless/b43, AFTER previous file was renamed (remember: BACKUP). After a reboot, the new module should be loaded instead of the old one - don't reboot right now, there is a last step.
I said there is a new parameter, "pio" parameter. This param forces pio mode instead of dma mode, causing no more dma errors. Great! We should pass the new parameter to the new kernel module, when the module is loaded. In Ubuntu-boot, you can accomplish that by creating a new file, let's call b43.conf, in /etc/modprobe.d/ directory. While booting, Ubuntu will read that dir and will execute commands (= pass to kernel) contained in all found files. Our file will contain only a simple instruction:
options b43 pio=1. Take attention: after you created this file, whatever kernel you will use, "pio" parameter WILL ALWAYS be passed to b43 module. If the module cannot understand the parameter, simply it won't be loaded, causing an error message being displayed. e.g. If you boot with a kernel with an "old" (different?) version of b43 - 2.6.31-17. Remember the dir in which you "copied" b43.ko? Only that kernel will load b43 module, you should empty b43.conf file to make other kernel's b43 modules loading - other kernels modules are still intact in ther /lib/modules/<other kernel>/kernel/drivers/net/wireless/b43 directories!
That's all. After a reboot your wifi should be activated and you could see wifi networks surrounding you. No more DMA problem. I read that probably the connection should be slower than DMA-normal one, but a slow connection is better than no connection. B43 guys have been busy for over 1 month on this problem, I hope they will solve it soon.

Hope it helps, remember to ask for help if something is not clear.
I really thank Larry Finger and Michael Buesch, the work is definitely THEIR work, and of all b43 developer guys.

Bye!

Emanuele

chenxiaolong
December 30th, 2009, 04:45 AM
Great news, emas80!!! :D:D:D May I paraphrase your HowTo in my first post (of course I'm going to credit you)? I'll also make a script for beginners if that's okay with you. I'll try recompiling the module with the patch tomorrow. I'm really tired right now (I've been trying to control my Lego Mindstorms NXT with a WiiMote, but NXT does not go well with Linux).

goslings
December 30th, 2009, 10:50 AM
Brillant :):)
Every time i've upgraded Ubuntu the B43 NEVER works out of the box;
This solution above worked for me - Why o why is in not part of the upgrade facility ?!?!?!


For those of you who use karmic, compat-wireless need not be compiled.

sudo apt-get install linux-backports-modules-karmic linux-backports-modules-wireless-karmic-generic b43-fwcutter
is enough.
Then do

sudo modprobe -r wl
sudo modprobe b43
and you're done. If it works and you want to make the change permanent :
First, blacklist the wl module

echo blacklist wl | sudo tee -a /etc/modprobe.d/blacklist.conf

Then

gksudo gedit /etc/modules
and add

b43
to the end of the file

goslings
December 30th, 2009, 11:01 AM
Ah - not quite - not permanent after reboot
also noticed that
"sudo modprobe -r wl"
"sudo modprobe b43"
failed with

WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
FATAL: Module wl not found.

WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.

I'll scan earlier in the post - but if anyone any ideas ...
thanks
Ian

emas80
December 30th, 2009, 11:25 AM
Hi,
This morning, I booted my note and wifi is still working! Great!

Yes you can do whatever you think is good to share it, I spent two days looking for a solution and I really hope my work will help who is stuck with dma problem.
Unfortunately, your good how-to didn't work for me, not even with older kernel release, maybe because of my particular wifi card, as I read on linuxwireless.org.
I will write to b43 developer mailing list, telling their patch is working for me.

Lego Mindstorms.. I'm really going to try "playing" with them, sooner or later.. :-)

emas80
December 30th, 2009, 11:45 AM
Hi, what do you mean with "not permanent"?
Here is my explanation for errors you reported:


Ah - not quite - not permanent after reboot
also noticed that
"sudo modprobe -r wl"
"sudo modprobe b43"
failed with
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.


This is only a warning :), it tells you that ndiswrapper should be renamed to ndiswrapper.conf, otherwise future releases could ignore its content.
In Ubuntu, while booting kernel, all files in /etc/modprobe.d/ are read and "executed", and this is used to blacklist some modules, or to pass parameters to loaded modules.
You can see the content of the files in that directory to better understand what they are useful for.



FATAL: Module wl not found.
This tells that no wl module was found as loaded, didn't you add it to blacklist :)? If so, obviously it has not been loaded!

What's the output of following command
lsmod | grep b43 after a reboot? Is b43 module loaded?
ifconfig or
iwconfig?

Why do you have a "ndiswrapper" configuration file? Maybe in the past you tried to use ndiswrapper to make your card working?
You shouldn't "mix" various howto's together, because you get confused, and your system gets confused too :).
I didn't try ndiswrapper, I don't know how to make it works, or how to remove it, maybe you can google for it, or someone could help you reinstalling or removing it.

goslings
December 30th, 2009, 02:53 PM
Hi, what do you mean with "not permanent"?
i.e after a reboot it looses all wireless


What's the output of following command
lsmod | grep b43 after a reboot? Is b43 module loaded?
ifconfig or
iwconfig?


Nothing from lsmod | grep b43
op from iconfig:

eth0 Link encap:Ethernet HWaddr 00:0c:6e:12:71:f6
inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20c:6eff:fe12:71f6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3559 errors:0 dropped:0 overruns:0 frame:0
TX packets:2824 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3927342 (3.9 MB) TX bytes:564320 (564.3 KB)
Interrupt:17 Base address:0x9800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)


op from iwconfig
lo no wireless extensions.
eth0 no wireless extensions.

Seems not to being made permanent
thanks for your help
Ian

goslings
December 30th, 2009, 03:36 PM
got rid of ndiswrapper
lspci | grep BCM report

00:0e.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

chenxiaolong
December 30th, 2009, 03:46 PM
Emas80, I was able to create a working patch from by using diff between your patched files and my original files. I just did a test run on a copy of the original and it patched without errors. I'm writing a script right now and I'll edit my first post later on. Again, thanks for your help and testing.:D

emas80
December 30th, 2009, 11:15 PM
got rid of ndiswrapper
lspci | grep BCM report

00:0e.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
Hi, so you are now in situation where you installed b43 module, b43 firmware and blacklisted wl module.
You said that wifi worked after following the procedure some posts ago, but after rebooting it stopped working. Probably this is because b43 module is not loaded, so if you try
sudo modprobe b43 it should work, or at least ifconfig/iwconfig should show the new interface.
If this is the case, please check that in /etc/modules the line about b43 module is present, and that no line about specifically "ssb" or "b43" is present in /etc/modprobe.d/blacklist.conf. When b43 module is loaded, it should load also ssb module, so if some error messages about module loading are shown try loading before ssb module and then b43.
Eventually type dmesg after module loading to look for log messages, or check kernel.log file to look for kernel error while loading modules (System->Administration->Log file viewer).

Which kernel are you using? I suppose the last Ubuntu kernel, 2.6.31-17.
Please go to this site (http://linuxwireless.org/en/users/Drivers/b43) to discover if your card could really work well with this revision of kernel, probably it does with no (known) problem but it is better to be sure.
I think that your card doesn't work after each upgrading because of some module conflict, the same conflict preventing you to use the card after a reboot, new Ubuntu revision = new kernel revision, if you use b43 module driver sources are in the kernel and the firmware is needed, other modules like nvidia or fglrx are "registered" with dkms so their sources are installed (look in /usr/src/) and the module is recompiled while booting if it is not found for running kernel.

chenxiaolong
December 31st, 2009, 12:33 AM
Emas80, are you using the 2.6.32.2 kernel from the Ubuntu kernel PPA? I'm a little confused when you said kernel source directory. Is it /usr/src/linux-source-2.6.32 or is it /usr/src/linux-headers-2.6.32-*-generic? Thank you.

goslings
December 31st, 2009, 12:52 AM
Hi Thanks for your help Emas80
uname -r report
2.6.3.16-generic (upgrade from 9.04 via update manager)

lspci | grep BC
00:0e.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

according to site you suggested
14e4:4306 supported BCM4306 b43legacy?
but below this states supported chipsets
bcm4306 (Rev. 2 uses b43legacy, Rev. 3 uses b43)

so as per 9.04 as this is a REV 3 use b43-should be way forward
All working over wireless - as of now - before a reboot
See what happens on the other side
thanks again
Ian

goslings
December 31st, 2009, 01:17 AM
See what happens on the other side
thanks again
Ian

grrr - No wireless after reboot
network icon just has enable networking and no wireless
edit connection has 1 wired and strangle two wireless
BTvoyager - used 6hrs ago
BTvoyager - used 1 yr ago

This is the kern.log file since the reboot - long sorry
Hope there is some clues in here to the initiated


Dec 30 23:50:31 goslinux kernel: Kernel logging (proc) stopped.
Dec 30 23:51:21 goslinux kernel: imklog 4.2.0, log source = /var/run/rsyslog/kmsg started.
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Initializing cgroup subsys cpuset
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Initializing cgroup subsys cpu
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Linux version 2.6.31-16-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 (Ubuntu 2.6.31-16.53-generic)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] KERNEL supported cpus:
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Intel GenuineIntel
Dec 30 23:51:24 goslinux kernel: [ 0.000000] AMD AuthenticAMD
Dec 30 23:51:24 goslinux kernel: [ 0.000000] NSC Geode by NSC
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Cyrix CyrixInstead
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Centaur CentaurHauls
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Transmeta GenuineTMx86
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Transmeta TransmetaCPU
Dec 30 23:51:24 goslinux kernel: [ 0.000000] UMC UMC UMC UMC
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-provided physical RAM map:
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 000000003fffc000 (usable)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-e820: 000000003fffc000 - 000000003ffff000 (ACPI data)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-e820: 000000003ffff000 - 0000000040000000 (ACPI NVS)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] DMI 2.3 present.
Dec 30 23:51:24 goslinux kernel: [ 0.000000] last_pfn = 0x3fffc max_arch_pfn = 0x100000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] MTRR default type: uncachable
Dec 30 23:51:24 goslinux kernel: [ 0.000000] MTRR fixed ranges enabled:
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 00000-9FFFF write-back
Dec 30 23:51:24 goslinux kernel: [ 0.000000] A0000-BFFFF uncachable
Dec 30 23:51:24 goslinux kernel: [ 0.000000] C0000-C7FFF write-protect
Dec 30 23:51:24 goslinux kernel: [ 0.000000] C8000-EFFFF uncachable
Dec 30 23:51:24 goslinux kernel: [ 0.000000] F0000-FFFFF write-protect
Dec 30 23:51:24 goslinux kernel: [ 0.000000] MTRR variable ranges enabled:
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 0 base 000000000 mask FC0000000 write-back
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 1 base 0E8000000 mask FFC000000 write-combining
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 2 disabled
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 3 disabled
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 4 disabled
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 5 disabled
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 6 disabled
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 7 disabled
Dec 30 23:51:24 goslinux kernel: [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Dec 30 23:51:24 goslinux kernel: [ 0.000000] e820 update range: 0000000000002000 - 0000000000006000 (usable) ==> (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Scanning 1 areas for low memory corruption
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified physical RAM map:
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 0000000000000000 - 0000000000002000 (usable)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 0000000000002000 - 0000000000006000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 0000000000006000 - 000000000009fc00 (usable)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 000000000009fc00 - 00000000000a0000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 0000000000100000 - 000000003fffc000 (usable)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 000000003fffc000 - 000000003ffff000 (ACPI data)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 000000003ffff000 - 0000000040000000 (ACPI NVS)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 00000000fec00000 - 00000000fec01000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] modified: 00000000ffff0000 - 0000000100000000 (reserved)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] initial memory mapped : 0 - 00c00000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] init_memory_mapping: 0000000000000000-00000000377fe000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Using x86 segment limits to approximate NX protection
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 0000000000 - 0000400000 page 4k
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 0000400000 - 0037400000 page 2M
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 0037400000 - 00377fe000 page 4k
Dec 30 23:51:24 goslinux kernel: [ 0.000000] kernel direct mapping tables up to 377fe000 @ 7000-c000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] RAMDISK: 37816000 - 37fef821
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Allocated new RAMDISK: 008ad000 - 01086821
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Move RAMDISK from 0000000037816000 - 0000000037fef820 to 008ad000 - 01086820
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: RSDP 000f64e0 00014 (v00 ASUS )
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: RSDT 3fffc000 00030 (v01 ASUS P4S533VL 42302E31 MSFT 31313031)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: FACP 3fffc0c0 00074 (v01 ASUS P4S533VL 42302E31 MSFT 31313031)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: DSDT 3fffc134 026B9 (v01 ASUS P4S533VL 00001000 MSFT 0100000B)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: FACS 3ffff000 00040
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: BOOT 3fffc030 00028 (v01 ASUS P4S533VL 42302E31 MSFT 31313031)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: APIC 3fffc058 00068 (v01 ASUS P4S533VL 42302E31 MSFT 31313031)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 135MB HIGHMEM available.
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 887MB LOWMEM available.
Dec 30 23:51:24 goslinux kernel: [ 0.000000] mapped low ram: 0 - 377fe000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] low ram: 0 - 377fe000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] node 0 low ram: 00000000 - 377fe000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] node 0 bootmap 00008000 - 0000ef00
Dec 30 23:51:24 goslinux kernel: [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 00377fe000]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] #3 [0000100000 - 00008a80a0] TEXT DATA BSS ==> [0000100000 - 00008a80a0]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] #4 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] #5 [00008a9000 - 00008ac16c] BRK ==> [00008a9000 - 00008ac16c]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] #6 [0000007000 - 0000008000] PGTABLE ==> [0000007000 - 0000008000]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] #7 [00008ad000 - 0001086821] NEW RAMDISK ==> [00008ad000 - 0001086821]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] #8 [0000008000 - 000000f000] BOOTMAP ==> [0000008000 - 000000f000]
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Zone PFN ranges:
Dec 30 23:51:24 goslinux kernel: [ 0.000000] DMA 0x00000000 -> 0x00001000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Normal 0x00001000 -> 0x000377fe
Dec 30 23:51:24 goslinux kernel: [ 0.000000] HighMem 0x000377fe -> 0x0003fffc
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Movable zone start PFN for each node
Dec 30 23:51:24 goslinux kernel: [ 0.000000] early_node_map[3] active PFN ranges
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 0: 0x00000000 -> 0x00000002
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 0: 0x00000006 -> 0x0000009f
Dec 30 23:51:24 goslinux kernel: [ 0.000000] 0: 0x00000100 -> 0x0003fffc
Dec 30 23:51:24 goslinux kernel: [ 0.000000] On node 0 totalpages: 262039
Dec 30 23:51:24 goslinux kernel: [ 0.000000] free_area_init_node: node 0, pgdat c0784940, node_mem_map c1087000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] DMA zone: 32 pages used for memmap
Dec 30 23:51:24 goslinux kernel: [ 0.000000] DMA zone: 0 pages reserved
Dec 30 23:51:24 goslinux kernel: [ 0.000000] DMA zone: 3963 pages, LIFO batch:0
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Normal zone: 1744 pages used for memmap
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Normal zone: 221486 pages, LIFO batch:31
Dec 30 23:51:24 goslinux kernel: [ 0.000000] HighMem zone: 272 pages used for memmap
Dec 30 23:51:24 goslinux kernel: [ 0.000000] HighMem zone: 34542 pages, LIFO batch:7
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Using APIC driver default
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: PM-Timer IO Port: 0xe408
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Dec 30 23:51:24 goslinux kernel: [ 0.000000] IOAPIC[0]: apic_id 2, version 128, address 0xfec00000, GSI 0-23
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: IRQ0 used by override.
Dec 30 23:51:24 goslinux kernel: [ 0.000000] ACPI: IRQ2 used by override.
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Using ACPI (MADT) for SMP configuration information
Dec 30 23:51:24 goslinux kernel: [ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
Dec 30 23:51:24 goslinux kernel: [ 0.000000] nr_irqs_gsi: 24
Dec 30 23:51:24 goslinux kernel: [ 0.000000] PM: Registered nosave memory: 0000000000002000 - 0000000000006000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Allocating PCI resources starting at 40000000 (gap: 40000000:bec00000)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
Dec 30 23:51:24 goslinux kernel: [ 0.000000] PERCPU: Embedded 14 pages at c188c000, static data 35612 bytes
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 259991
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Kernel command line: root=UUID=37e33de3-a10e-485e-902e-8db860896b49 ro vga=795 quiet
Dec 30 23:51:24 goslinux kernel: [ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Enabling fast FPU save and restore... done.
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Enabling unmasked SIMD FPU exception support... done.
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Initializing CPU#0
Dec 30 23:51:24 goslinux kernel: [ 0.000000] allocated 5242800 bytes of page_cgroup
Dec 30 23:51:24 goslinux kernel: [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Initializing HighMem for node 0 (000377fe:0003fffc)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Memory: 1017640k/1048560k available (4566k kernel code, 30164k reserved, 2142k data, 540k init, 139256k highmem)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] virtual kernel memory layout:
Dec 30 23:51:24 goslinux kernel: [ 0.000000] fixmap : 0xfff1d000 - 0xfffff000 ( 904 kB)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] .init : 0xc078e000 - 0xc0815000 ( 540 kB)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] .data : 0xc0575bb4 - 0xc078d3c8 (2142 kB)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] .text : 0xc0100000 - 0xc0575bb4 (4566 kB)
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
Dec 30 23:51:24 goslinux kernel: [ 0.000000] SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Dec 30 23:51:24 goslinux kernel: [ 0.000000] NR_IRQS:2304 nr_irqs:424
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Fast TSC calibration using PIT
Dec 30 23:51:24 goslinux kernel: [ 0.000000] Detected 3059.046 MHz processor.
Dec 30 23:51:24 goslinux kernel: [ 0.000046] Console: colour dummy device 80x25
Dec 30 23:51:24 goslinux kernel: [ 0.000051] console [tty0] enabled
Dec 30 23:51:24 goslinux kernel: [ 0.000105] Calibrating delay loop (skipped), value calculated using timer frequency.. 6118.09 BogoMIPS (lpj=12236184)
Dec 30 23:51:24 goslinux kernel: [ 0.000138] Security Framework initialized
Dec 30 23:51:24 goslinux kernel: [ 0.000169] AppArmor: AppArmor initialized
Dec 30 23:51:24 goslinux kernel: [ 0.000179] Mount-cache hash table entries: 512
Dec 30 23:51:24 goslinux kernel: [ 0.000381] Initializing cgroup subsys ns
Dec 30 23:51:24 goslinux kernel: [ 0.000388] Initializing cgroup subsys cpuacct
Dec 30 23:51:24 goslinux kernel: [ 0.000393] Initializing cgroup subsys memory
Dec 30 23:51:24 goslinux kernel: [ 0.000403] Initializing cgroup subsys freezer
Dec 30 23:51:24 goslinux kernel: [ 0.000407] Initializing cgroup subsys net_cls
Dec 30 23:51:24 goslinux kernel: [ 0.000428] CPU: Trace cache: 12K uops, L1 D cache: 8K
Dec 30 23:51:24 goslinux kernel: [ 0.000432] CPU: L2 cache: 512K
Dec 30 23:51:24 goslinux kernel: [ 0.000435] CPU: Physical Processor ID: 0
Dec 30 23:51:24 goslinux kernel: [ 0.000437] CPU: Processor Core ID: 0
Dec 30 23:51:24 goslinux kernel: [ 0.000442] mce: CPU supports 4 MCE banks
Dec 30 23:51:24 goslinux kernel: [ 0.000455] CPU0: Thermal monitoring enabled (TM1)
Dec 30 23:51:24 goslinux kernel: [ 0.000470] Performance Counters: no PMU driver, software counters only.
Dec 30 23:51:24 goslinux kernel: [ 0.000479] Checking 'hlt' instruction... OK.
Dec 30 23:51:24 goslinux kernel: [ 0.018975] ACPI: Core revision 20090521
Dec 30 23:51:24 goslinux kernel: [ 0.024497] alloc irq_desc for 20 on node 0
Dec 30 23:51:24 goslinux kernel: [ 0.024500] alloc kstat_irqs on node 0
Dec 30 23:51:24 goslinux kernel: [ 0.024635] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Dec 30 23:51:24 goslinux kernel: [ 0.064325] CPU0: Intel(R) Pentium(R) 4 CPU 3.06GHz stepping 07
Dec 30 23:51:24 goslinux kernel: [ 0.068001] Booting processor 1 APIC 0x1 ip 0x6000
Dec 30 23:51:24 goslinux kernel: [ 0.004000] Initializing CPU#1
Dec 30 23:51:24 goslinux kernel: [ 0.004000] Calibrating delay using timer specific routine.. 6118.24 BogoMIPS (lpj=12236486)
Dec 30 23:51:24 goslinux kernel: [ 0.004000] CPU: Trace cache: 12K uops, L1 D cache: 8K
Dec 30 23:51:24 goslinux kernel: [ 0.004000] CPU: L2 cache: 512K
Dec 30 23:51:24 goslinux kernel: [ 0.004000] CPU: Physical Processor ID: 0
Dec 30 23:51:24 goslinux kernel: [ 0.004000] CPU: Processor Core ID: 0
Dec 30 23:51:24 goslinux kernel: [ 0.004000] mce: CPU supports 4 MCE banks
Dec 30 23:51:24 goslinux kernel: [ 0.004000] CPU1: Thermal monitoring enabled (TM1)
Dec 30 23:51:24 goslinux kernel: [ 0.004000] x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
Dec 30 23:51:24 goslinux kernel: [ 0.152870] CPU1: Intel(R) Pentium(R) 4 CPU 3.06GHz stepping 07
Dec 30 23:51:24 goslinux kernel: [ 0.152893] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Dec 30 23:51:24 goslinux kernel: [ 0.156050] Brought up 2 CPUs
Dec 30 23:51:24 goslinux kernel: [ 0.156056] Total of 2 processors activated (12236.33 BogoMIPS).
Dec 30 23:51:24 goslinux kernel: [ 0.156100] CPU0 attaching sched-domain:
Dec 30 23:51:24 goslinux kernel: [ 0.156105] domain 0: span 0-1 level SIBLING
Dec 30 23:51:24 goslinux kernel: [ 0.156109] groups: 0 1
Dec 30 23:51:24 goslinux kernel: [ 0.156117] CPU1 attaching sched-domain:
Dec 30 23:51:24 goslinux kernel: [ 0.156120] domain 0: span 0-1 level SIBLING
Dec 30 23:51:24 goslinux kernel: [ 0.156124] groups: 1 0
Dec 30 23:51:24 goslinux kernel: [ 0.156233] Booting paravirtualized kernel on bare hardware
Dec 30 23:51:24 goslinux kernel: [ 0.156266] regulator: core version 0.5
Dec 30 23:51:24 goslinux kernel: [ 0.156266] Time: 23:50:49 Date: 12/30/09
Dec 30 23:51:24 goslinux kernel: [ 0.156266] NET: Registered protocol family 16
Dec 30 23:51:24 goslinux kernel: [ 0.156298] EISA bus registered
Dec 30 23:51:24 goslinux kernel: [ 0.156311] ACPI: bus type pci registered
Dec 30 23:51:24 goslinux kernel: [ 0.157834] PCI: PCI BIOS revision 2.10 entry at 0xf2520, last bus=1
Dec 30 23:51:24 goslinux kernel: [ 0.157837] PCI: Using configuration type 1 for base access
Dec 30 23:51:24 goslinux kernel: [ 0.160942] bio: create slab <bio-0> at 0
Dec 30 23:51:24 goslinux kernel: [ 0.160942] ACPI: EC: Look up EC in DSDT
Dec 30 23:51:24 goslinux kernel: [ 0.167868] ACPI: Interpreter enabled
Dec 30 23:51:24 goslinux kernel: [ 0.167876] ACPI: (supports S0 S1 S3 S4 S5)
Dec 30 23:51:24 goslinux kernel: [ 0.168022] ACPI: Using IOAPIC for interrupt routing
Dec 30 23:51:24 goslinux kernel: [ 0.181925] ACPI: No dock devices found.
Dec 30 23:51:24 goslinux kernel: [ 0.182061] ACPI: PCI Root Bridge [PCI0] (0000:00)
Dec 30 23:51:24 goslinux kernel: [ 0.182124] pci 0000:00:00.0: reg 10 32bit mmio: [0xe8000000-0xebffffff]
Dec 30 23:51:24 goslinux kernel: [ 0.182302] pci 0000:00:02.0: Enabling SiS 96x SMBus
Dec 30 23:51:24 goslinux kernel: [ 0.182360] pci 0000:00:02.1: reg 20 io port: [0xe600-0xe61f]
Dec 30 23:51:24 goslinux kernel: [ 0.182412] pci 0000:00:02.5: reg 10 io port: [0xd800-0xd807]
Dec 30 23:51:24 goslinux kernel: [ 0.182422] pci 0000:00:02.5: reg 14 io port: [0xd400-0xd403]
Dec 30 23:51:24 goslinux kernel: [ 0.182431] pci 0000:00:02.5: reg 18 io port: [0xd000-0xd007]
Dec 30 23:51:24 goslinux kernel: [ 0.182440] pci 0000:00:02.5: reg 1c io port: [0xb800-0xb803]
Dec 30 23:51:24 goslinux kernel: [ 0.182449] pci 0000:00:02.5: reg 20 io port: [0xb400-0xb40f]
Dec 30 23:51:24 goslinux kernel: [ 0.182510] pci 0000:00:02.6: reg 10 io port: [0xb000-0xb0ff]
Dec 30 23:51:24 goslinux kernel: [ 0.182520] pci 0000:00:02.6: reg 14 io port: [0xa800-0xa87f]
Dec 30 23:51:24 goslinux kernel: [ 0.182575] pci 0000:00:02.6: supports D1 D2
Dec 30 23:51:24 goslinux kernel: [ 0.182578] pci 0000:00:02.6: PME# supported from D3hot D3cold
Dec 30 23:51:24 goslinux kernel: [ 0.182584] pci 0000:00:02.6: PME# disabled
Dec 30 23:51:24 goslinux kernel: [ 0.182629] pci 0000:00:02.7: reg 10 io port: [0xa400-0xa4ff]
Dec 30 23:51:24 goslinux kernel: [ 0.182638] pci 0000:00:02.7: reg 14 io port: [0xa000-0xa07f]
Dec 30 23:51:24 goslinux kernel: [ 0.182694] pci 0000:00:02.7: supports D1 D2
Dec 30 23:51:24 goslinux kernel: [ 0.182697] pci 0000:00:02.7: PME# supported from D3hot D3cold
Dec 30 23:51:24 goslinux kernel: [ 0.182702] pci 0000:00:02.7: PME# disabled
Dec 30 23:51:24 goslinux kernel: [ 0.182746] pci 0000:00:03.0: reg 10 32bit mmio: [0xe6800000-0xe6800fff]
Dec 30 23:51:24 goslinux kernel: [ 0.182805] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Dec 30 23:51:24 goslinux kernel: [ 0.182811] pci 0000:00:03.0: PME# disabled
Dec 30 23:51:24 goslinux kernel: [ 0.182856] pci 0000:00:03.1: reg 10 32bit mmio: [0xe6000000-0xe6000fff]
Dec 30 23:51:24 goslinux kernel: [ 0.182916] pci 0000:00:03.1: PME# supported from D0 D3hot D3cold
Dec 30 23:51:24 goslinux kernel: [ 0.182921] pci 0000:00:03.1: PME# disabled
Dec 30 23:51:24 goslinux kernel: [ 0.182965] pci 0000:00:03.2: reg 10 32bit mmio: [0xe5800000-0xe5800fff]
Dec 30 23:51:24 goslinux kernel: [ 0.183024] pci 0000:00:03.2: PME# supported from D0 D3hot D3cold
Dec 30 23:51:24 goslinux kernel: [ 0.183030] pci 0000:00:03.2: PME# disabled
Dec 30 23:51:24 goslinux kernel: [ 0.183073] pci 0000:00:03.3: reg 10 32bit mmio: [0xe5000000-0xe5000fff]
Dec 30 23:51:24 goslinux kernel: [ 0.183133] pci 0000:00:03.3: PME# supported from D0 D3hot D3cold
Dec 30 23:51:24 goslinux kernel: [ 0.183139] pci 0000:00:03.3: PME# disabled
Dec 30 23:51:24 goslinux kernel: [ 0.183194] pci 0000:00:0e.0: reg 10 32bit mmio: [0xe4800000-0xe4801fff]
Dec 30 23:51:24 goslinux kernel: [ 0.183278] pci 0000:00:0f.0: reg 10 32bit mmio: [0xe4000000-0xe40003ff]
Dec 30 23:51:24 goslinux kernel: [ 0.183339] pci 0000:00:0f.0: supports D1 D2
Dec 30 23:51:24 goslinux kernel: [ 0.183387] pci 0000:00:10.0: reg 10 32bit mmio: [0x000000-0x000fff]
Dec 30 23:51:24 goslinux kernel: [ 0.183412] pci 0000:00:10.0: supports D1 D2
Dec 30 23:51:24 goslinux kernel: [ 0.183415] pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot D3cold
Dec 30 23:51:24 goslinux kernel: [ 0.183420] pci 0000:00:10.0: PME# disabled
Dec 30 23:51:24 goslinux kernel: [ 0.183467] pci 0000:00:12.0: reg 10 io port: [0x9800-0x98ff]
Dec 30 23:51:24 goslinux kernel: [ 0.183477] pci 0000:00:12.0: reg 14 32bit mmio: [0xe3800000-0xe38000ff]
Dec 30 23:51:24 goslinux kernel: [ 0.183532] pci 0000:00:12.0: supports D1 D2
Dec 30 23:51:24 goslinux kernel: [ 0.183535] pci 0000:00:12.0: PME# supported from D1 D2 D3hot D3cold
Dec 30 23:51:24 goslinux kernel: [ 0.183541] pci 0000:00:12.0: PME# disabled
Dec 30 23:51:24 goslinux kernel: [ 0.183585] pci 0000:00:13.0: reg 10 32bit mmio: [0xe3000000-0xe3000fff]
Dec 30 23:51:24 goslinux kernel: [ 0.183645] pci 0000:00:13.0: supports D1 D2
Dec 30 23:51:24 goslinux kernel: [ 0.183648] pci 0000:00:13.0: PME# supported from D0 D1 D2 D3hot D3cold
Dec 30 23:51:24 goslinux kernel: [ 0.183654] pci 0000:00:13.0: PME# disabled
Dec 30 23:51:24 goslinux kernel: [ 0.183727] pci 0000:01:00.0: reg 10 32bit mmio: [0xe7000000-0xe7ffffff]
Dec 30 23:51:24 goslinux kernel: [ 0.183736] pci 0000:01:00.0: reg 14 32bit mmio: [0xf0000000-0xf7ffffff]
Dec 30 23:51:24 goslinux kernel: [ 0.183744] pci 0000:01:00.0: reg 18 32bit mmio: [0xef800000-0xef87ffff]
Dec 30 23:51:24 goslinux kernel: [ 0.183765] pci 0000:01:00.0: reg 30 32bit mmio: [0xef7e0000-0xef7fffff]
Dec 30 23:51:24 goslinux kernel: [ 0.183844] pci 0000:00:01.0: bridge 32bit mmio: [0xe7000000-0xe7ffffff]
Dec 30 23:51:24 goslinux kernel: [ 0.183850] pci 0000:00:01.0: bridge 32bit mmio pref: [0xef700000-0xfebfffff]
Dec 30 23:51:24 goslinux kernel: [ 0.183882] pci_bus 0000:00: on NUMA node 0
Dec 30 23:51:24 goslinux kernel: [ 0.183888] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Dec 30 23:51:24 goslinux kernel: [ 0.184063] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
Dec 30 23:51:24 goslinux kernel: [ 0.276095] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Dec 30 23:51:24 goslinux kernel: [ 0.276230] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 *4 5 6 7 10 11 12 14 15)
Dec 30 23:51:24 goslinux kernel: [ 0.276359] ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 11 12 14 15)
Dec 30 23:51:24 goslinux kernel: [ 0.276489] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Dec 30 23:51:24 goslinux kernel: [ 0.276618] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *9
Dec 30 23:51:24 goslinux kernel: [ 0.276747] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *9
Dec 30 23:51:24 goslinux kernel: [ 0.276873] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *9
Dec 30 23:51:24 goslinux kernel: [ 0.277003] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *9
Dec 30 23:51:24 goslinux kernel: [ 0.277272] SCSI subsystem initialized
Dec 30 23:51:24 goslinux kernel: [ 0.277345] libata version 3.00 loaded.
Dec 30 23:51:24 goslinux kernel: [ 0.277345] usbcore: registered new interface driver usbfs
Dec 30 23:51:24 goslinux kernel: [ 0.277345] usbcore: registered new interface driver hub
Dec 30 23:51:24 goslinux kernel: [ 0.277345] usbcore: registered new device driver usb
Dec 30 23:51:24 goslinux kernel: [ 0.277345] ACPI: WMI: Mapper loaded
Dec 30 23:51:24 goslinux kernel: [ 0.277345] PCI: Using ACPI for IRQ routing
Dec 30 23:51:24 goslinux kernel: [ 0.288013] Bluetooth: Core ver 2.15
Dec 30 23:51:24 goslinux kernel: [ 0.288045] NET: Registered protocol family 31
Dec 30 23:51:24 goslinux kernel: [ 0.288045] Bluetooth: HCI device and connection manager initialized
Dec 30 23:51:24 goslinux kernel: [ 0.288045] Bluetooth: HCI socket layer initialized
Dec 30 23:51:24 goslinux kernel: [ 0.288045] NetLabel: Initializing
Dec 30 23:51:24 goslinux kernel: [ 0.288045] NetLabel: domain hash size = 128
Dec 30 23:51:24 goslinux kernel: [ 0.288045] NetLabel: protocols = UNLABELED CIPSOv4
Dec 30 23:51:24 goslinux kernel: [ 0.288053] NetLabel: unlabeled traffic allowed by default
Dec 30 23:51:24 goslinux kernel: [ 0.300021] pnp: PnP ACPI init
Dec 30 23:51:24 goslinux kernel: [ 0.300056] ACPI: bus type pnp registered
Dec 30 23:51:24 goslinux kernel: [ 0.305606] pnp: PnP ACPI: found 15 devices
Dec 30 23:51:24 goslinux kernel: [ 0.305610] ACPI: ACPI bus type pnp unregistered
Dec 30 23:51:24 goslinux kernel: [ 0.305615] PnPBIOS: Disabled by ACPI PNP
Dec 30 23:51:24 goslinux kernel: [ 0.305631] system 00:00: iomem range 0x0-0x9ffff could not be reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305636] system 00:00: iomem range 0xf0000-0xfffff could not be reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305640] system 00:00: iomem range 0x100000-0x3fffffff could not be reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305645] system 00:00: iomem range 0xfec00000-0xfecfffff could not be reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305649] system 00:00: iomem range 0xfee00000-0xfeefffff could not be reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305659] system 00:02: ioport range 0xe400-0xe47f has been reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305663] system 00:02: ioport range 0xe480-0xe4ff has been reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305667] system 00:02: ioport range 0xe600-0xe61f has been reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305670] system 00:02: ioport range 0x480-0x48f has been reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305674] system 00:02: iomem range 0xffee0000-0xffefffff has been reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305683] system 00:03: iomem range 0xfffe0000-0xffffffff could not be reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305692] system 00:04: ioport range 0x4d0-0x4d1 has been reserved
Dec 30 23:51:24 goslinux kernel: [ 0.305705] system 00:0d: ioport range 0x295-0x296 has been reserved
Dec 30 23:51:24 goslinux kernel: [ 0.340443] AppArmor: AppArmor Filesystem Enabled
Dec 30 23:51:24 goslinux kernel: [ 0.340493] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
Dec 30 23:51:24 goslinux kernel: [ 0.340497] pci 0000:00:01.0: IO window: disabled
Dec 30 23:51:24 goslinux kernel: [ 0.340504] pci 0000:00:01.0: MEM window: 0xe7000000-0xe7ffffff
Dec 30 23:51:24 goslinux kernel: [ 0.340510] pci 0000:00:01.0: PREFETCH window: 0xef700000-0xfebfffff
Dec 30 23:51:24 goslinux kernel: [ 0.340517] pci 0000:00:10.0: CardBus bridge, secondary bus 0000:02
Dec 30 23:51:24 goslinux kernel: [ 0.340520] pci 0000:00:10.0: IO window: 0x001000-0x0010ff
Dec 30 23:51:24 goslinux kernel: [ 0.340526] pci 0000:00:10.0: IO window: 0x001400-0x0014ff
Dec 30 23:51:24 goslinux kernel: [ 0.340532] pci 0000:00:10.0: PREFETCH window: 0x40000000-0x43ffffff
Dec 30 23:51:24 goslinux kernel: [ 0.340538] pci 0000:00:10.0: MEM window: 0x44000000-0x47ffffff
Dec 30 23:51:24 goslinux kernel: [ 0.340555] pci 0000:00:01.0: setting latency timer to 64
Dec 30 23:51:24 goslinux kernel: [ 0.340575] alloc irq_desc for 19 on node -1
Dec 30 23:51:24 goslinux kernel: [ 0.340578] alloc kstat_irqs on node -1
Dec 30 23:51:24 goslinux kernel: [ 0.340586] pci 0000:00:10.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Dec 30 23:51:24 goslinux kernel: [ 0.340595] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
Dec 30 23:51:24 goslinux kernel: [ 0.340599] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
Dec 30 23:51:24 goslinux kernel: [ 0.340602] pci_bus 0000:01: resource 1 mem: [0xe7000000-0xe7ffffff]
Dec 30 23:51:24 goslinux kernel: [ 0.340606] pci_bus 0000:01: resource 2 pref mem [0xef700000-0xfebfffff]
Dec 30 23:51:24 goslinux kernel: [ 0.340609] pci_bus 0000:02: resource 0 io: [0x1000-0x10ff]
Dec 30 23:51:24 goslinux kernel: [ 0.340612] pci_bus 0000:02: resource 1 io: [0x1400-0x14ff]
Dec 30 23:51:24 goslinux kernel: [ 0.340616] pci_bus 0000:02: resource 2 pref mem [0x40000000-0x43ffffff]
Dec 30 23:51:24 goslinux kernel: [ 0.340619] pci_bus 0000:02: resource 3 mem: [0x44000000-0x47ffffff]
Dec 30 23:51:24 goslinux kernel: [ 0.340673] NET: Registered protocol family 2
Dec 30 23:51:24 goslinux kernel: [ 0.340812] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
Dec 30 23:51:24 goslinux kernel: [ 0.341334] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
Dec 30 23:51:24 goslinux kernel: [ 0.342487] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
Dec 30 23:51:24 goslinux kernel: [ 0.343245] TCP: Hash tables configured (established 131072 bind 65536)
Dec 30 23:51:24 goslinux kernel: [ 0.343251] TCP reno registered
Dec 30 23:51:24 goslinux kernel: [ 0.343444] NET: Registered protocol family 1
Dec 30 23:51:24 goslinux kernel: [ 0.343573] Trying to unpack rootfs image as initramfs...
Dec 30 23:51:24 goslinux kernel: [ 0.581926] Freeing initrd memory: 8038k freed
Dec 30 23:51:24 goslinux kernel: [ 0.592800] Simple Boot Flag at 0x3a set to 0x1
Dec 30 23:51:24 goslinux kernel: [ 0.592954] cpufreq-nforce2: No nForce2 chipset.
Dec 30 23:51:24 goslinux kernel: [ 0.592992] Scanning for low memory corruption every 60 seconds
Dec 30 23:51:24 goslinux kernel: [ 0.593145] audit: initializing netlink socket (disabled)
Dec 30 23:51:24 goslinux kernel: [ 0.593171] type=2000 audit(1262217049.592:1): initialized
Dec 30 23:51:24 goslinux kernel: [ 0.600550] highmem bounce pool size: 64 pages
Dec 30 23:51:24 goslinux kernel: [ 0.600558] HugeTLB registered 4 MB page size, pre-allocated 0 pages
Dec 30 23:51:24 goslinux kernel: [ 0.602486] VFS: Disk quotas dquot_6.5.2
Dec 30 23:51:24 goslinux kernel: [ 0.602577] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Dec 30 23:51:24 goslinux kernel: [ 0.603325] fuse init (API version 7.12)
Dec 30 23:51:24 goslinux kernel: [ 0.603436] msgmni has been set to 1731
Dec 30 23:51:24 goslinux kernel: [ 0.603799] alg: No test for stdrng (krng)
Dec 30 23:51:24 goslinux kernel: [ 0.603821] io scheduler noop registered
Dec 30 23:51:24 goslinux kernel: [ 0.603824] io scheduler anticipatory registered
Dec 30 23:51:24 goslinux kernel: [ 0.603827] io scheduler deadline registered
Dec 30 23:51:24 goslinux kernel: [ 0.603898] io scheduler cfq registered (default)
Dec 30 23:51:24 goslinux kernel: [ 0.603990] pci 0000:01:00.0: Boot video device
Dec 30 23:51:24 goslinux kernel: [ 0.604125] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Dec 30 23:51:24 goslinux kernel: [ 0.604158] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Dec 30 23:51:24 goslinux kernel: [ 0.604332] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
Dec 30 23:51:24 goslinux kernel: [ 0.604338] ACPI: Power Button [PWRF]
Dec 30 23:51:24 goslinux kernel: [ 0.604403] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
Dec 30 23:51:24 goslinux kernel: [ 0.604407] ACPI: Power Button [PWRB]
Dec 30 23:51:24 goslinux kernel: [ 0.604583] ACPI: Invalid PBLK length [5]
Dec 30 23:51:24 goslinux kernel: [ 0.604631] processor LNXCPU:00: registered as cooling_device0
Dec 30 23:51:24 goslinux kernel: [ 0.604691] processor LNXCPU:01: registered as cooling_device1
Dec 30 23:51:24 goslinux kernel: [ 0.615359] isapnp: Scanning for PnP cards...
Dec 30 23:51:24 goslinux kernel: [ 0.840937] Switched to high resolution mode on CPU 1
Dec 30 23:51:24 goslinux kernel: [ 0.844006] Switched to high resolution mode on CPU 0
Dec 30 23:51:24 goslinux kernel: [ 0.969050] isapnp: No Plug & Play device found
Dec 30 23:51:24 goslinux kernel: [ 0.970618] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Dec 30 23:51:24 goslinux kernel: [ 0.971071] alloc irq_desc for 18 on node -1
Dec 30 23:51:24 goslinux kernel: [ 0.971075] alloc kstat_irqs on node -1
Dec 30 23:51:24 goslinux kernel: [ 0.971085] serial 0000:00:02.6: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Dec 30 23:51:24 goslinux kernel: [ 0.971094] serial 0000:00:02.6: PCI INT C disabled
Dec 30 23:51:24 goslinux kernel: [ 0.972432] brd: module loaded
Dec 30 23:51:24 goslinux kernel: [ 0.973077] loop: module loaded
Dec 30 23:51:24 goslinux kernel: [ 0.973202] input: Macintosh mouse button emulation as /devices/virtual/input/input2
Dec 30 23:51:24 goslinux kernel: [ 0.974091] pata_sis 0000:00:02.5: version 0.5.2
Dec 30 23:51:24 goslinux kernel: [ 0.974109] alloc irq_desc for 16 on node -1
Dec 30 23:51:24 goslinux kernel: [ 0.974112] alloc kstat_irqs on node -1
Dec 30 23:51:24 goslinux kernel: [ 0.974121] pata_sis 0000:00:02.5: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 30 23:51:24 goslinux kernel: [ 0.974421] scsi0 : pata_sis
Dec 30 23:51:24 goslinux kernel: [ 0.974570] scsi1 : pata_sis
Dec 30 23:51:24 goslinux kernel: [ 0.975304] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xb400 irq 14
Dec 30 23:51:24 goslinux kernel: [ 0.975308] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xb408 irq 15
Dec 30 23:51:24 goslinux kernel: [ 0.975824] Fixed MDIO Bus: probed
Dec 30 23:51:24 goslinux kernel: [ 0.975871] PPP generic driver version 2.4.2
Dec 30 23:51:24 goslinux kernel: [ 0.976045] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Dec 30 23:51:24 goslinux kernel: [ 0.976083] alloc irq_desc for 23 on node -1
Dec 30 23:51:24 goslinux kernel: [ 0.976086] alloc kstat_irqs on node -1
Dec 30 23:51:24 goslinux kernel: [ 0.976094] ehci_hcd 0000:00:03.3: PCI INT D -> GSI 23 (level, low) -> IRQ 23
Dec 30 23:51:24 goslinux kernel: [ 0.976118] ehci_hcd 0000:00:03.3: EHCI Host Controller
Dec 30 23:51:24 goslinux kernel: [ 0.976192] ehci_hcd 0000:00:03.3: new USB bus registered, assigned bus number 1
Dec 30 23:51:24 goslinux kernel: [ 0.976231] ehci_hcd 0000:00:03.3: cache line size of 128 is not supported
Dec 30 23:51:24 goslinux kernel: [ 0.976251] ehci_hcd 0000:00:03.3: irq 23, io mem 0xe5000000
Dec 30 23:51:24 goslinux kernel: [ 0.985013] ehci_hcd 0000:00:03.3: USB 2.0 started, EHCI 1.00
Dec 30 23:51:24 goslinux kernel: [ 0.985120] usb usb1: configuration #1 chosen from 1 choice
Dec 30 23:51:24 goslinux kernel: [ 0.985165] hub 1-0:1.0: USB hub found
Dec 30 23:51:24 goslinux kernel: [ 0.985178] hub 1-0:1.0: 6 ports detected
Dec 30 23:51:24 goslinux kernel: [ 0.985272] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Dec 30 23:51:24 goslinux kernel: [ 0.985304] ohci_hcd 0000:00:03.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Dec 30 23:51:24 goslinux kernel: [ 0.985322] ohci_hcd 0000:00:03.0: OHCI Host Controller
Dec 30 23:51:24 goslinux kernel: [ 0.985372] ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 2
Dec 30 23:51:24 goslinux kernel: [ 0.985392] ohci_hcd 0000:00:03.0: irq 20, io mem 0xe6800000
Dec 30 23:51:24 goslinux kernel: [ 1.042085] usb usb2: configuration #1 chosen from 1 choice
Dec 30 23:51:24 goslinux kernel: [ 1.042122] hub 2-0:1.0: USB hub found
Dec 30 23:51:24 goslinux kernel: [ 1.042133] hub 2-0:1.0: 2 ports detected
Dec 30 23:51:24 goslinux kernel: [ 1.042212] alloc irq_desc for 21 on node -1
Dec 30 23:51:24 goslinux kernel: [ 1.042216] alloc kstat_irqs on node -1
Dec 30 23:51:24 goslinux kernel: [ 1.042223] ohci_hcd 0000:00:03.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
Dec 30 23:51:24 goslinux kernel: [ 1.042236] ohci_hcd 0000:00:03.1: OHCI Host Controller
Dec 30 23:51:24 goslinux kernel: [ 1.042281] ohci_hcd 0000:00:03.1: new USB bus registered, assigned bus number 3
Dec 30 23:51:24 goslinux kernel: [ 1.042306] ohci_hcd 0000:00:03.1: irq 21, io mem 0xe6000000
Dec 30 23:51:24 goslinux kernel: [ 1.098087] usb usb3: configuration #1 chosen from 1 choice
Dec 30 23:51:24 goslinux kernel: [ 1.098126] hub 3-0:1.0: USB hub found
Dec 30 23:51:24 goslinux kernel: [ 1.098138] hub 3-0:1.0: 2 ports detected
Dec 30 23:51:24 goslinux kernel: [ 1.098207] alloc irq_desc for 22 on node -1
Dec 30 23:51:24 goslinux kernel: [ 1.098211] alloc kstat_irqs on node -1
Dec 30 23:51:24 goslinux kernel: [ 1.098217] ohci_hcd 0000:00:03.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
Dec 30 23:51:24 goslinux kernel: [ 1.098232] ohci_hcd 0000:00:03.2: OHCI Host Controller
Dec 30 23:51:24 goslinux kernel: [ 1.098276] ohci_hcd 0000:00:03.2: new USB bus registered, assigned bus number 4
Dec 30 23:51:24 goslinux kernel: [ 1.098301] ohci_hcd 0000:00:03.2: irq 22, io mem 0xe5800000
Dec 30 23:51:24 goslinux kernel: [ 1.137142] ata1.00: ATA-6: WDC WD1600BB-22DAA0, 65.13G65, max UDMA/100
Dec 30 23:51:24 goslinux kernel: [ 1.137147] ata1.00: 312581808 sectors, multi 16: LBA48
Dec 30 23:51:24 goslinux kernel: [ 1.153172] ata1.00: configured for UDMA/100
Dec 30 23:51:24 goslinux kernel: [ 1.153341] scsi 0:0:0:0: Direct-Access ATA WDC WD1600BB-22D 65.1 PQ: 0 ANSI: 5
Dec 30 23:51:24 goslinux kernel: [ 1.153546] sd 0:0:0:0: Attached scsi generic sg0 type 0
Dec 30 23:51:24 goslinux kernel: [ 1.153606] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
Dec 30 23:51:24 goslinux kernel: [ 1.153681] sd 0:0:0:0: [sda] Write Protect is off
Dec 30 23:51:24 goslinux kernel: [ 1.153685] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Dec 30 23:51:24 goslinux kernel: [ 1.153724] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 30 23:51:24 goslinux kernel: [ 1.154131] usb usb4: configuration #1 chosen from 1 choice
Dec 30 23:51:24 goslinux kernel: [ 1.154179] hub 4-0:1.0: USB hub found
Dec 30 23:51:24 goslinux kernel: [ 1.154196] hub 4-0:1.0: 2 ports detected
Dec 30 23:51:24 goslinux kernel: [ 1.154294] uhci_hcd: USB Universal Host Controller Interface driver
Dec 30 23:51:24 goslinux kernel: [ 1.154455] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
Dec 30 23:51:24 goslinux kernel: [ 1.154810] serio: i8042 KBD port at 0x60,0x64 irq 1
Dec 30 23:51:24 goslinux kernel: [ 1.154820] serio: i8042 AUX port at 0x60,0x64 irq 12
Dec 30 23:51:24 goslinux kernel: [ 1.154935] mice: PS/2 mouse device common for all mice
Dec 30 23:51:24 goslinux kernel: [ 1.155079] rtc_cmos 00:06: RTC can wake from S4
Dec 30 23:51:24 goslinux kernel: [ 1.155142] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
Dec 30 23:51:24 goslinux kernel: [ 1.155170] rtc0: alarms up to one month, 242 bytes nvram
Dec 30 23:51:24 goslinux kernel: [ 1.155345] device-mapper: uevent: version 1.0.3
Dec 30 23:51:24 goslinux kernel: [ 1.155558] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
Dec 30 23:51:24 goslinux kernel: [ 1.155725] sda:
Dec 30 23:51:24 goslinux kernel: [ 1.155855] device-mapper: multipath: version 1.1.0 loaded
Dec 30 23:51:24 goslinux kernel: [ 1.155862] device-mapper: multipath round-robin: version 1.0.0 loaded
Dec 30 23:51:24 goslinux kernel: [ 1.156116] EISA: Probing bus 0 at eisa.0
Dec 30 23:51:24 goslinux kernel: [ 1.156126] Cannot allocate resource for EISA slot 1
Dec 30 23:51:24 goslinux kernel: [ 1.156156] EISA: Detected 0 cards.
Dec 30 23:51:24 goslinux kernel: [ 1.156328] cpuidle: using governor ladder
Dec 30 23:51:24 goslinux kernel: [ 1.156331] cpuidle: using governor menu
Dec 30 23:51:24 goslinux kernel: [ 1.157118] TCP cubic registered
Dec 30 23:51:24 goslinux kernel: [ 1.157285] NET: Registered protocol family 10
Dec 30 23:51:24 goslinux kernel: [ 1.157925] lo: Disabled Privacy Extensions
Dec 30 23:51:24 goslinux kernel: [ 1.158405] NET: Registered protocol family 17
Dec 30 23:51:24 goslinux kernel: [ 1.158435] Bluetooth: L2CAP ver 2.13
Dec 30 23:51:24 goslinux kernel: [ 1.158437] Bluetooth: L2CAP socket layer initialized
Dec 30 23:51:24 goslinux kernel: [ 1.158441] Bluetooth: SCO (Voice Link) ver 0.6
Dec 30 23:51:24 goslinux kernel: [ 1.158443] Bluetooth: SCO socket layer initialized
Dec 30 23:51:24 goslinux kernel: [ 1.158526] Bluetooth: RFCOMM TTY layer initialized
Dec 30 23:51:24 goslinux kernel: [ 1.158533] Bluetooth: RFCOMM socket layer initialized
Dec 30 23:51:24 goslinux kernel: [ 1.158537] Bluetooth: RFCOMM ver 1.11
Dec 30 23:51:24 goslinux kernel: [ 1.158594] Using IPI No-Shortcut mode
Dec 30 23:51:24 goslinux kernel: [ 1.158705] PM: Resume from disk failed.
Dec 30 23:51:24 goslinux kernel: [ 1.158724] registered taskstats version 1
Dec 30 23:51:24 goslinux kernel: [ 1.158868] Magic number: 5:521:859
Dec 30 23:51:24 goslinux kernel: [ 1.158968] rtc_cmos 00:06: setting system clock to 2009-12-30 23:50:50 UTC (1262217050)
Dec 30 23:51:24 goslinux kernel: [ 1.158973] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Dec 30 23:51:24 goslinux kernel: [ 1.158975] EDD information not available.
Dec 30 23:51:24 goslinux kernel: [ 1.175781] sda1 sda2 <
Dec 30 23:51:24 goslinux kernel: [ 1.180183] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
Dec 30 23:51:24 goslinux kernel: [ 1.187536] sda5 sda6 sda7 > sda3
Dec 30 23:51:24 goslinux kernel: [ 1.211613] sd 0:0:0:0: [sda] Attached SCSI disk
Dec 30 23:51:24 goslinux kernel: [ 1.324256] ata2.00: ATAPI: SONY DVD RW DW-U12A, 2.0b, max UDMA/33
Dec 30 23:51:24 goslinux kernel: [ 1.324297] ata2.01: ATAPI: Pioneer DVD-ROM ATAPIModel DVD-120, 1.20, max UDMA/66
Dec 30 23:51:24 goslinux kernel: [ 1.324330] ata2.01: limited to UDMA/33 due to 40-wire cable
Dec 30 23:51:24 goslinux kernel: [ 1.340274] ata2.00: configured for UDMA/33
Dec 30 23:51:24 goslinux kernel: [ 1.356305] ata2.01: configured for UDMA/33
Dec 30 23:51:24 goslinux kernel: [ 1.359120] scsi 1:0:0:0: CD-ROM SONY DVD RW DW-U12A 2.0b PQ: 0 ANSI: 5
Dec 30 23:51:24 goslinux kernel: [ 1.362918] sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
Dec 30 23:51:24 goslinux kernel: [ 1.362924] Uniform CD-ROM driver Revision: 3.20
Dec 30 23:51:24 goslinux kernel: [ 1.363063] sr 1:0:0:0: Attached scsi CD-ROM sr0
Dec 30 23:51:24 goslinux kernel: [ 1.363144] sr 1:0:0:0: Attached scsi generic sg1 type 5
Dec 30 23:51:24 goslinux kernel: [ 1.363787] scsi 1:0:1:0: CD-ROM PIONEER DVD-ROM DVD-120R 1.20 PQ: 0 ANSI: 5
Dec 30 23:51:24 goslinux kernel: [ 1.367157] sr1: scsi3-mmc drive: 40x/40x cd/rw xa/form2 cdda tray
Dec 30 23:51:24 goslinux kernel: [ 1.367275] sr 1:0:1:0: Attached scsi CD-ROM sr1
Dec 30 23:51:24 goslinux kernel: [ 1.367339] sr 1:0:1:0: Attached scsi generic sg2 type 5
Dec 30 23:51:24 goslinux kernel: [ 1.367382] Freeing unused kernel memory: 540k freed
Dec 30 23:51:24 goslinux kernel: [ 1.368152] Write protecting the kernel text: 4568k
Dec 30 23:51:24 goslinux kernel: [ 1.368219] Write protecting the kernel read-only data: 1836k
Dec 30 23:51:24 goslinux kernel: [ 1.542428] Linux agpgart interface v0.103
Dec 30 23:51:24 goslinux kernel: [ 1.548266] agpgart-sis 0000:00:00.0: SiS chipset [1039/0651]
Dec 30 23:51:24 goslinux kernel: [ 1.573117] agpgart-sis 0000:00:00.0: AGP aperture is 64M @ 0xe8000000
Dec 30 23:51:24 goslinux kernel: [ 1.595273] <6>8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
Dec 30 23:51:24 goslinux kernel: [ 1.595333] 8139cp 0000:00:12.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
Dec 30 23:51:24 goslinux kernel: [ 1.600736] 8139too Fast Ethernet driver 0.9.28
Dec 30 23:51:24 goslinux kernel: [ 1.600841] alloc irq_desc for 17 on node -1
Dec 30 23:51:24 goslinux kernel: [ 1.600846] alloc kstat_irqs on node -1
Dec 30 23:51:24 goslinux kernel: [ 1.600861] 8139too 0000:00:12.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Dec 30 23:51:24 goslinux kernel: [ 1.602830] eth0: RealTek RTL8139 at 0x9800, 00:0c:6e:12:71:f6, IRQ 17
Dec 30 23:51:24 goslinux kernel: [ 1.696809] Floppy drive(s): fd0 is 1.44M
Dec 30 23:51:24 goslinux kernel: [ 1.757077] ohci1394 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Dec 30 23:51:24 goslinux kernel: [ 1.760633] reset set in interrupt, calling f80db170
Dec 30 23:51:24 goslinux kernel: [ 1.760670] floppy0: no floppy controllers found
Dec 30 23:51:24 goslinux kernel: [ 1.815036] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[18] MMIO=[e3000000-e30007ff] Max Packet=[2048] IR/IT contexts=[4/4]
Dec 30 23:51:24 goslinux kernel: [ 2.761336] vesafb: framebuffer at 0xf0000000, mapped to 0xf8180000, using 10240k, total 131072k
Dec 30 23:51:24 goslinux kernel: [ 2.761342] vesafb: mode is 1280x1024x32, linelength=5120, pages=0
Dec 30 23:51:24 goslinux kernel: [ 2.761344] vesafb: protected mode interface info at c000:f060
Dec 30 23:51:24 goslinux kernel: [ 2.761348] vesafb: pmi: set display start = c00cf0a5, set palette = c00cf12a
Dec 30 23:51:24 goslinux kernel: [ 2.761351] vesafb: pmi: ports = b4c3 b503 ba03 c003 c103 c403 c503 c603 c703 c803 c903 cc03 ce03 cf03 d003 d103 d203 d303 d403 d503 da03 ff03
Dec 30 23:51:24 goslinux kernel: [ 2.761380] vesafb: scrolling: redraw
Dec 30 23:51:24 goslinux kernel: [ 2.761385] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Dec 30 23:51:24 goslinux kernel: [ 2.761464] fb0: VESA VGA frame buffer device
Dec 30 23:51:24 goslinux kernel: [ 2.770280] Console: switching to colour frame buffer device 160x64
Dec 30 23:51:24 goslinux kernel: [ 3.100704] xor: automatically using best checksumming function: pIII_sse
Dec 30 23:51:24 goslinux kernel: [ 3.101257] ieee1394: Host added: ID:BUS[0-00:1023] GUID[0800460301543ecf]
Dec 30 23:51:24 goslinux kernel: [ 3.120008] pIII_sse : 3879.000 MB/sec
Dec 30 23:51:24 goslinux kernel: [ 3.120012] xor: using function: pIII_sse (3879.000 MB/sec)
Dec 30 23:51:24 goslinux kernel: [ 3.123261] device-mapper: dm-raid45: initialized v0.2594b
Dec 30 23:51:24 goslinux kernel: [ 3.402738] PM: Starting manual resume from disk
Dec 30 23:51:24 goslinux kernel: [ 3.402744] PM: Resume from partition 8:5
Dec 30 23:51:24 goslinux kernel: [ 3.402746] PM: Checking hibernation image.
Dec 30 23:51:24 goslinux kernel: [ 3.402972] PM: Resume from disk failed.
Dec 30 23:51:24 goslinux kernel: [ 3.428347] kjournald starting. Commit interval 5 seconds
Dec 30 23:51:24 goslinux kernel: [ 3.428366] EXT3-fs: mounted filesystem with writeback data mode.
Dec 30 23:51:24 goslinux kernel: [ 4.219229] type=1505 audit(1262217053.557:2): operation="profile_load" pid=415 name=/usr/share/gdm/guest-session/Xsession
Dec 30 23:51:24 goslinux kernel: [ 4.233368] type=1505 audit(1262217053.573:3): operation="profile_load" pid=416 name=/sbin/dhclient3
Dec 30 23:51:24 goslinux kernel: [ 4.233916] type=1505 audit(1262217053.573:4): operation="profile_load" pid=416 name=/usr/lib/NetworkManager/nm-dhcp-client.action
Dec 30 23:51:24 goslinux kernel: [ 4.234219] type=1505 audit(1262217053.573:5): operation="profile_load" pid=416 name=/usr/lib/connman/scripts/dhclient-script
Dec 30 23:51:24 goslinux kernel: [ 4.277625] type=1505 audit(1262217053.618:6): operation="profile_load" pid=417 name=/usr/bin/evince
Dec 30 23:51:24 goslinux kernel: [ 4.286926] type=1505 audit(1262217053.626:7): operation="profile_load" pid=417 name=/usr/bin/evince-previewer
Dec 30 23:51:24 goslinux kernel: [ 4.292398] type=1505 audit(1262217053.630:8): operation="profile_load" pid=417 name=/usr/bin/evince-thumbnailer
Dec 30 23:51:24 goslinux kernel: [ 4.316992] type=1505 audit(1262217053.654:9): operation="profile_load" pid=418 name=/usr/lib/cups/backend/cups-pdf
Dec 30 23:51:24 goslinux kernel: [ 4.317642] type=1505 audit(1262217053.658:10): operation="profile_load" pid=418 name=/usr/sbin/cupsd
Dec 30 23:51:24 goslinux kernel: [ 28.277388] udev: starting version 147
Dec 30 23:51:24 goslinux kernel: [ 28.288084] Adding 1020088k swap on /dev/sda5. Priority:-1 extents:1 across:1020088k
Dec 30 23:51:24 goslinux kernel: [ 28.318325] sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0xe600
Dec 30 23:51:24 goslinux kernel: [ 28.343124] lp: driver loaded but no devices found
Dec 30 23:51:24 goslinux kernel: [ 28.387017] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Dec 30 23:51:24 goslinux kernel: [ 28.399873] yenta_cardbus 0000:00:10.0: CardBus bridge found [104d:8139]
Dec 30 23:51:24 goslinux kernel: [ 28.527595] yenta_cardbus 0000:00:10.0: ISA IRQ mask 0x06b8, PCI irq 19
Dec 30 23:51:24 goslinux kernel: [ 28.527603] yenta_cardbus 0000:00:10.0: Socket status: 30000006
Dec 30 23:51:24 goslinux kernel: [ 28.629621] Linux video capture interface: v2.00
Dec 30 23:51:24 goslinux kernel: [ 28.750430] parport_pc 00:0a: reported by Plug and Play ACPI
Dec 30 23:51:24 goslinux kernel: [ 28.750507] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Dec 30 23:51:24 goslinux kernel: [ 28.775927] saa7130/34: v4l2 driver version 0.2.15 loaded
Dec 30 23:51:24 goslinux kernel: [ 28.779528] Floppy drive(s): fd0 is 1.44M
Dec 30 23:51:24 goslinux kernel: [ 28.805840] reset set in interrupt, calling f815e170
Dec 30 23:51:24 goslinux kernel: [ 28.805873] floppy0: no floppy controllers found
Dec 30 23:51:24 goslinux kernel: [ 28.826208] ppdev: user-space parallel port driver
Dec 30 23:51:24 goslinux kernel: [ 28.833436] ip_tables: (C) 2000-2006 Netfilter Core Team
Dec 30 23:51:24 goslinux kernel: [ 28.845420] lp0: using parport0 (interrupt-driven).
Dec 30 23:51:24 goslinux kernel: [ 28.867100] b43-pci-bridge 0000:00:0e.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Dec 30 23:51:24 goslinux kernel: [ 28.870686] ssb: Sonics Silicon Backplane found on PCI device 0000:00:0e.0
Dec 30 23:51:24 goslinux kernel: [ 28.871207] saa7134 0000:00:0f.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Dec 30 23:51:24 goslinux kernel: [ 28.871222] saa7134[0]: found at 0000:00:0f.0, rev: 1, irq: 18, latency: 32, mmio: 0xe4000000
Dec 30 23:51:24 goslinux kernel: [ 28.871238] saa7134[0]: subsystem: 1043:4830, board: ASUS TV-FM 7134 [card=16,autodetected]
Dec 30 23:51:24 goslinux kernel: [ 28.871276] saa7134[0]: board init: gpio is 0
Dec 30 23:51:24 goslinux kernel: [ 28.871287] IRQ 18/saa7134[0]: IRQF_DISABLED is not guaranteed on shared IRQs
Dec 30 23:51:24 goslinux kernel: [ 28.889401] cfg80211: Calling CRDA to update world regulatory domain
Dec 30 23:51:24 goslinux kernel: [ 28.932671] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
Dec 30 23:51:24 goslinux kernel: [ 29.026897] saa7134[0]: i2c eeprom 00: 43 10 30 48 ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.026925] saa7134[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.026951] saa7134[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.026974] saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.026998] saa7134[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027021] saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027045] saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027069] saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027092] saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027116] saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027139] saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027163] saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027186] saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027209] saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027232] saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027255] saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 30 23:51:24 goslinux kernel: [ 29.027285] i2c-adapter i2c-1: Invalid 7-bit address 0x7a
Dec 30 23:51:24 goslinux kernel: [ 29.070656] phy0: Selected rate control algorithm 'minstrel'
Dec 30 23:51:24 goslinux kernel: [ 29.071764] Registered led device: b43-phy0::tx
Dec 30 23:51:24 goslinux kernel: [ 29.071789] Registered led device: b43-phy0::rx
Dec 30 23:51:24 goslinux kernel: [ 29.071814] Registered led device: b43-phy0::radio
Dec 30 23:51:24 goslinux kernel: [ 29.071905] Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
Dec 30 23:51:24 goslinux kernel: [ 29.080146] tuner 1-0043: chip found @ 0x86 (saa7134[0])
Dec 30 23:51:24 goslinux kernel: [ 29.088670] tda9887 1-0043: creating new instance
Dec 30 23:51:24 goslinux kernel: [ 29.088677] tda9887 1-0043: tda988[5/6/7] found
Dec 30 23:51:24 goslinux kernel: [ 29.098100] psmouse serio1: ID: 10 00 64
Dec 30 23:51:24 goslinux kernel: [ 29.120014] All bytes are equal. It is not a TEA5767
Dec 30 23:51:24 goslinux kernel: [ 29.120151] tuner 1-0060: chip found @ 0xc0 (saa7134[0])
Dec 30 23:51:24 goslinux kernel: [ 29.136028] tuner-simple 1-0060: creating new instance
Dec 30 23:51:24 goslinux kernel: [ 29.136035] tuner-simple 1-0060: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3))
Dec 30 23:51:24 goslinux kernel: [ 29.148386] udev: renamed network interface wlan0 to eth1
Dec 30 23:51:24 goslinux kernel: [ 29.165970] cfg80211: World regulatory domain updated:
Dec 30 23:51:24 goslinux kernel: [ 29.165976] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec 30 23:51:24 goslinux kernel: [ 29.165980] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 30 23:51:24 goslinux kernel: [ 29.165984] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec 30 23:51:24 goslinux kernel: [ 29.165987] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec 30 23:51:24 goslinux kernel: [ 29.165991] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 30 23:51:24 goslinux kernel: [ 29.165994] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 30 23:51:24 goslinux kernel: [ 29.166740] logips2pp: Detected unknown logitech mouse model 14
Dec 30 23:51:24 goslinux kernel: [ 29.196349] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x240-0x247
Dec 30 23:51:24 goslinux kernel: [ 29.198146] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean.
Dec 30 23:51:24 goslinux kernel: [ 29.198888] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
Dec 30 23:51:24 goslinux kernel: [ 29.199544] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7:
Dec 30 23:51:24 goslinux kernel: [ 29.200209] saa7134[0]: registered device video0 [v4l2]
Dec 30 23:51:24 goslinux kernel: [ 29.200225] clean.
Dec 30 23:51:24 goslinux kernel: [ 29.200266] saa7134[0]: registered device vbi0
Dec 30 23:51:24 goslinux kernel: [ 29.200324] saa7134[0]: registered device radio0
Dec 30 23:51:24 goslinux kernel: [ 29.200605] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
Dec 30 23:51:24 goslinux kernel: [ 29.202058] Intel ICH 0000:00:02.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Dec 30 23:51:24 goslinux kernel: [ 29.209240] saa7134 ALSA driver for DMA sound loaded
Dec 30 23:51:24 goslinux kernel: [ 29.209264] IRQ 18/saa7134[0]: IRQF_DISABLED is not guaranteed on shared IRQs
Dec 30 23:51:24 goslinux kernel: [ 29.209324] saa7134[0]/alsa: saa7134[0] at 0xe4000000 irq 18 registered as card -2
Dec 30 23:51:24 goslinux kernel: [ 29.636721] input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input4
Dec 30 23:51:24 goslinux kernel: [ 29.953050] EXT3 FS on sda3, internal journal
Dec 30 23:51:24 goslinux kernel: [ 30.024030] intel8x0_measure_ac97_clock: measured 55413 usecs (2665 samples)
Dec 30 23:51:24 goslinux kernel: [ 30.024035] intel8x0: clocking to 48000
Dec 30 23:51:24 goslinux kernel: [ 32.144390] kjournald starting. Commit interval 5 seconds
Dec 30 23:51:24 goslinux kernel: [ 32.144620] EXT3 FS on sda6, internal journal
Dec 30 23:51:24 goslinux kernel: [ 32.144629] EXT3-fs: mounted filesystem with writeback data mode.
Dec 30 23:51:24 goslinux kernel: [ 32.562938] __ratelimit: 6 callbacks suppressed
Dec 30 23:51:24 goslinux kernel: [ 32.562943] type=1505 audit(1262217081.901:13): operation="profile_replace" pid=1058 name=/usr/share/gdm/guest-session/Xsession
Dec 30 23:51:24 goslinux kernel: [ 32.566793] type=1505 audit(1262217081.905:14): operation="profile_replace" pid=1059 name=/sbin/dhclient3
Dec 30 23:51:24 goslinux kernel: [ 32.567362] type=1505 audit(1262217081.905:15): operation="profile_replace" pid=1059 name=/usr/lib/NetworkManager/nm-dhcp-client.action
Dec 30 23:51:24 goslinux kernel: [ 32.567663] type=1505 audit(1262217081.905:16): operation="profile_replace" pid=1059 name=/usr/lib/connman/scripts/dhclient-script
Dec 30 23:51:24 goslinux kernel: [ 32.576401] type=1505 audit(1262217081.917:17): operation="profile_replace" pid=1060 name=/usr/bin/evince
Dec 30 23:51:24 goslinux kernel: [ 32.586462] type=1505 audit(1262217081.925:18): operation="profile_replace" pid=1060 name=/usr/bin/evince-previewer
Dec 30 23:51:24 goslinux kernel: [ 32.592692] type=1505 audit(1262217081.933:19): operation="profile_replace" pid=1060 name=/usr/bin/evince-thumbnailer
Dec 30 23:51:24 goslinux kernel: [ 32.601231] type=1505 audit(1262217081.941:20): operation="profile_replace" pid=1061 name=/usr/lib/cups/backend/cups-pdf
Dec 30 23:51:24 goslinux kernel: [ 32.602295] type=1505 audit(1262217081.941:21): operation="profile_replace" pid=1061 name=/usr/sbin/cupsd
Dec 30 23:51:24 goslinux kernel: [ 32.606254] type=1505 audit(1262217081.945:22): operation="profile_replace" pid=1062 name=/usr/sbin/mysqld-akonadi
Dec 30 23:51:25 goslinux kernel: [ 35.766113] b43-pci-bridge 0000:00:0e.0: PCI INT A disabled
Dec 30 23:51:25 goslinux kernel: [ 35.866466] eth0: link down
Dec 30 23:51:25 goslinux kernel: [ 35.866741] ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 30 23:51:28 goslinux kernel: [ 39.300896] CPU0 attaching NULL sched-domain.
Dec 30 23:51:28 goslinux kernel: [ 39.300906] CPU1 attaching NULL sched-domain.
Dec 30 23:51:28 goslinux kernel: [ 39.313090] CPU0 attaching sched-domain:
Dec 30 23:51:28 goslinux kernel: [ 39.313096] domain 0: span 0-1 level SIBLING
Dec 30 23:51:28 goslinux kernel: [ 39.313101] groups: 0 1
Dec 30 23:51:28 goslinux kernel: [ 39.313110] CPU1 attaching sched-domain:
Dec 30 23:51:28 goslinux kernel: [ 39.313113] domain 0: span 0-1 level SIBLING
Dec 30 23:51:28 goslinux kernel: [ 39.313116] groups: 1 0
Dec 30 23:53:52 goslinux kernel: [ 183.356821] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Dec 30 23:53:52 goslinux kernel: [ 183.356978] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Dec 30 23:54:03 goslinux kernel: [ 194.156010] eth0: no IPv6 routers present

chenxiaolong
December 31st, 2009, 05:03 AM
Goslings, does your wireless work if you run sudo modprobe b43? If it does, you can add modprobe b43 right above the exit 0 line in /etc/rc.local.

Also (to everyone), I've updated my original post with the links to my script. You can change them however you want, but please let me know what changes you made.

TironN
December 31st, 2009, 10:00 AM
I've been trying to get this b43 stuff working for ages now!
Trying your kernel script now, hopefully this and your help I will be able to have everything going!

goslings
December 31st, 2009, 01:45 PM
Does this not mean i would have enter root passwd every time
+It worked in 9.04 without workarounds
I love the odd tinker with Ubuntu, but there are limits, every time it is a pain with wireless


Goslings, does your wireless work if you run sudo modprobe b43? If it does, you can add modprobe b43 right above the exit 0 line in /etc/rc.local.

chenxiaolong
December 31st, 2009, 03:15 PM
Goslings: No, you will not have to enter your root password every time it boots because all the lines in /etc/rc.local are run as root. So, no password :D.

TironN
December 31st, 2009, 03:50 PM
Hey I'm using a dell mini 9 so its not Amd 64 or i386. Its i686.
So do I use the amd or i386 .debs for this?

chenxiaolong
December 31st, 2009, 04:01 PM
i386.

By the way, debs for what?

DarkAngel88
December 31st, 2009, 04:58 PM
Multiple problems with your script. The script downloads the amd files if uname -m == i686. Had to do the download manually. Also, problem at line 239 in your script, missing a "esac" or something similar (tried changing the first case from "if uname -m == i386" to "if uname -m == i686"). In that particular case, the new kernel wasn't installed at all as it downloads and tries to install the amd version of the kernel into a Intel Atom cpu, you get the idea I'm pretty sure ;)

Also, your script should check if "patch" is installed prior to execute the patch command. In my case (fresh system), "patch" wasn't installed and the b43 sources weren't patched at all.

Other than that, thanks for the script. Will continue to see if this fixes my issue!

chenxiaolong
December 31st, 2009, 05:35 PM
Ahh, I see. Thanks for the info. I was using the amd64 version of Ubuntu so the script worked fine for me. Also, I used "if [ "$(uname -m) == "i386" ]" because I thought Ubuntu x86 was i386 based; the LiveCD and the kernel debs end with i386. Oh well, I fixed the scripts.

goslings
December 31st, 2009, 05:48 PM
Goslings: No, you will not have to enter your root password every time it boots because all the lines in /etc/rc.local are run as root. So, no password :D.

cheers works thanks very much
Would like to find out why have to do this tweak,
but that is for another year

Happy New Year

The Glidd
January 1st, 2010, 12:27 AM
Glidd,

Have you tried activating the STA driver while connected to the internet (wired)? That's what I had to do to activate it.

Kevin


I tried that without any result. I did put this into the terminal:

modprobe b43

And at least now I'm getting an option for wireless networks under network manager. Simultaneously, the Broadcom B43 showed up under Hardware Drivers. When I activate it though, (it says it's activated) nothing happens, either in network manager or with the wireless.

Did I blacklist or something somewhere in this process?

TironN
January 1st, 2010, 10:16 AM
So I ran your shell scripts and the final result is this:

after a restart running 'sudo modprobe b43' I get:


FATAL: Error inserting b43 (/lib/modules/2.6.32-02063202-generic/updates/drivers/net/wireless/b43/b43.ko): Invalid module format


Whats going on here? Also dmesg has no DMA errors, lshw -c network is saying its using the b43 driver and modinfo b43 has this: "parm: pio:enable(1) / disable(0) PIO mode (int)" at the bottom

Thanks, Fergus

The Glidd
January 1st, 2010, 04:28 PM
I tried that without any result. I did put this into the terminal:

modprobe b43

And at least now I'm getting an option for wireless networks under network manager. Simultaneously, the Broadcom B43 showed up under Hardware Drivers. When I activate it though, (it says it's activated) nothing happens, either in network manager or with the wireless.

Did I blacklist or something somewhere in this process?


Also, I just had a few moments of wireless signals being detected. Network Manager even said I was connected to my router (just like old times!) No pages loaded, though. After a restart, no networks are being detected.

Also, under System > Administration > Hardware Drivers, both STA and b43 show up. If I try and activate STA I get this:

Sorry, installation of this driver failed.

Please have a look at the log file for details: /var/log/jockey.log

And then if I go and activate b43, the dialog at the bottom of the Hardware Driver info screen says:

A different version of this driver is in use.

Then I activate with the only change being that network manager has an option for wireless which didn't exist when I tried to install STA.

goslings
January 2nd, 2010, 11:53 AM
cheers works thanks very much
chenxiaolong

Just whem I I though was all solved ....
Now on every boot up network wireless asks for wireless passwd
and sudo modprobe b43 just hangs

Luv Linux but for a couple of months after EVERY upgrade I always have problem

chenxiaolong
January 2nd, 2010, 04:18 PM
Wow, a lot of problems :(.

TironN: Could you post the output of dmesg | tail after running sudo modprobe b43. This will give me a look at why b43 isn't loading.

The Glidd: You definitely don't want to try and activate the STA driver and the b43 driver together. They fight for control over the wireless card and as a result, nothing works. Since you've been having problems, I suggest you to use the STA driver because it's stable (although proprietary). Here's how:

1. sudo rmmod b43 ssb wl
Unloads the two wireless drivers.

2. sudo apt-get --purge remove b43-fwcutter bcmwl-kernel-source

3. Check the files in /etc/modprobe.d and make sure that there ISN'T

blacklist wl

in any of the files. Also make sure that there IS

blacklist b43
blacklist bcm43xx
blacklist ssb
blacklist b43legacy

in one of the files. You can create a new one if you want to be more organized (file has to end in .conf).

4. Open /etc/modules as root and check the file and make sure that there isn't a line with

b43

and that there is a line with

wl

5. sudo apt-get install bcmwl-kernel-source
Reinstall bcmwl-kernel-source

Goslings: Could you post the output of modinfo b43?

goslings
January 2nd, 2010, 07:23 PM
Wow, a lot of problems :(.

Goslings: Could you post the output of modinfo b43?

It seems to be working again after a reboot (using Kino a lot at the moment)



ian@goslinux:~$ modinfo b43
filename: /lib/modules/2.6.31-16-generic/updates/cw/b43.ko
firmware: FW13
license: GPL
author: Gábor Stefanik
author: Michael Buesch
author: Stefano Brivio
author: Martin Langer
description: Broadcom B43 wireless driver
srcversion: 3C72AF37EF2A8FE86721372
alias: pcmcia:m02D0c0476f*fn*pfn*pa*pb*pc*pd*
alias: pcmcia:m02D0c0448f*fn*pfn*pa*pb*pc*pd*
alias: ssb:v4243id0812rev10*
alias: ssb:v4243id0812rev0F*
alias: ssb:v4243id0812rev0D*
alias: ssb:v4243id0812rev0B*
alias: ssb:v4243id0812rev0A*
alias: ssb:v4243id0812rev09*
alias: ssb:v4243id0812rev07*
alias: ssb:v4243id0812rev06*
alias: ssb:v4243id0812rev05*
depends: pcmcia,ssb,mac80211,led-class,cfg80211,pcmcia_core
vermagic: 2.6.31-16-generic SMP mod_unload modversions 586
parm: bad_frames_preempt:enable(1) / disable(0) Bad Frames Preemption (int)
parm: fwpostfix:Postfix for the .fw files to load. (string)
parm: hwpctl:Enable hardware-side power control (default off) (int)
parm: nohwcrypt:Disable hardware encryption. (int)
parm: hwtkip:Enable hardware tkip. (int)
parm: qos:Enable QOS support (default on) (int)
parm: btcoex:Enable Bluetooth coexistence (default on) (int)
parm: verbose:Log message verbosity: 0=error, 1=warn, 2=info(default), 3=debug (int)

emas80
January 3rd, 2010, 12:02 PM
Hi! And happy new year :-)
Sorry I was away during the last days


Emas80, are you using the 2.6.32.2 kernel from the Ubuntu kernel PPA? I'm a little confused when you said kernel source directory. Is it /usr/src/linux-source-2.6.32 or is it /usr/src/linux-headers-2.6.32-*-generic? Thank you.

I'm not using Ubuntu kernel, I downloaded kernel sources directly from www.kernel.org (http://www.kernel.org), so when I untarred the file, usually in /usr/src/, it created a dir called linux-2.6.32.2. Ubuntu kernels instead when untarred create directory called linux-source-2.6.xxxx.
I think that that patches should apply with no many problems on Ubuntu version of 2.6.32 kernel.

emas80
January 3rd, 2010, 12:35 PM
Just whem I I though was all solved ....
Now on every boot up network wireless asks for wireless passwd
and sudo modprobe b43 just hangs

Luv Linux but for a couple of months after EVERY upgrade I always have problem

Hi, your modinfos looks right, if wifi keeps asking for password, your card is detected and driver is already loaded, maybe this is causing the hangs on modprobe b43.
About the password, I'm not sure, maybe it lost the "remember pwd", or the connect automatically, or couldn't connect because some sort of problem occurred.. I had the same problem on Windows, with another notebook, sometime wifi is not detected on boot time and I should connect manually, and I should try many times before it worked.
But I think that looking at the output of dmesg when this error occurs (e.g. just after boot) should help us identifying the problem,
After a correct boot with wifi found, enabled and connected my last dmesg lines are

[ 988.371533] wlan0: deauthenticating from 00:1d:6a:ec:18:45 by local choice (reason=3)
[ 988.373729] wlan0: direct probe to AP 00:1d:6a:ec:18:45 (try 1)
[ 988.376187] wlan0: direct probe responded
[ 988.376197] wlan0: authenticate with AP 00:1d:6a:ec:18:45 (try 1)
[ 988.378502] wlan0: authenticated
[ 988.378553] wlan0: associate with AP 00:1d:6a:ec:18:45 (try 1)
[ 988.382002] wlan0: RX AssocResp from 00:1d:6a:ec:18:45 (capab=0x431 status=0 aid=1)
[ 988.382033] wlan0: associated
[ 988.384550] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 988.385491] cfg80211: Calling CRDA for country: IT
[ 988.389714] cfg80211: Received country IE:
[ 988.389721] cfg80211: Regulatory domain: IT
[ 988.389725] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 988.389733] (2402000 KHz - 2494000 KHz @ 40000 KHz), (10000 mBi, 10000 mBm)
[ 988.389737] cfg80211: CRDA thinks this should applied:
[ 988.389741] cfg80211: Regulatory domain: IT
[ 988.389745] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 988.389751] (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 988.389757] (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 988.389763] (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 988.389769] (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
[ 988.389773] cfg80211: We intersect both of these and get:
[ 988.389777] cfg80211: Regulatory domain: 98
[ 988.389781] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 988.389787] (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 988.389797] cfg80211: Disabling channel 2484 MHz on phy0 due to Country IE
[ 988.389804] cfg80211: Current regulatory domain updated by AP to: IT
[ 988.389808] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 988.389814] (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 998.601110] wlan0: no IPv6 routers presentI agree with you about Ubuntu problems after EACH upgrade, maybe Ubuntu is too user friendly so everyone (me too!) upgrades without reading the changelogs and readmes, and just after everything stops working they realizes that developers changed that and added those, so *maybe this could possibly cause some problems on people who use <yes, it is really your card/pc here>*.
I have been using Ubuntu for 3 years, and I made the last 3 upgrades over one month after they released the OS, after browsed forums and discovered possible problems and workarounds. I work with my pc and I really cannot stay without my video card because someone changed something that WAS ALREADY WORKING PRETTY WELL and *forgot* to test it with my hardware. Yes I know it is not easy, and it's quite impossible, I'm a software engineer too :-) .
I've always fixed everything is important to me (I gave up with hibernate, after EACH kernel revision it works, if before didn't, or it stops working, if before it did), so I can go on with this, and I've no time to try Gentoo, but one day I will :-)

The Glidd
January 3rd, 2010, 03:05 PM
Wow, a lot of problems :(.
The Glidd: You definitely don't want to try and activate the STA driver and the b43 driver together. They fight for control over the wireless card and as a result, nothing works. Since you've been having problems, I suggest you to use the STA driver because it's stable (although proprietary). Here's how:

1. sudo rmmod b43 ssb wl
Unloads the two wireless drivers.

2. sudo apt-get --purge remove b43-fwcutter bcmwl-kernel-source

3. Check the files in /etc/modprobe.d and make sure that there ISN'T

blacklist wl

in any of the files. Also make sure that there IS

blacklist b43
blacklist bcm43xx
blacklist ssb
blacklist b43legacy

in one of the files. You can create a new one if you want to be more organized (file has to end in .conf).

4. Open /etc/modules as root and check the file and make sure that there isn't a line with


b43

and that there is a line with

wl

5. sudo apt-get install bcmwl-kernel-source
Reinstall bcmwl-kernel-source

Thanks, I'm following each of these as we speak. Incidentally, the wireless inexplicably tried to connect last night. It won't accept my WPA password, though. So I'm proceeding with the above, anyway.

1. sudo rmmod b43 ssb wl
Unloads the two wireless drivers.

-I get: ERROR: Module wl does not exist in /proc/modules

2. sudo apt-get --purge remove b43-fwcutter bcmwl-kernel-source

-ok

3. Check the files in /etc/modprobe.d and make sure that there ISN'T

blacklist wl

in any of the files. Also make sure that there IS

blacklist b43
blacklist bcm43xx
blacklist ssb
blacklist b43legacy

in one of the files. You can create a new one if you want to be more organized (file has to end in .conf).

i get:

alsa-base.conf blacklist-framebuffer.conf blacklist-wl.conf
blacklist-ath_pci.conf blacklist-modem.conf libpisock9.conf
blacklist.conf blacklist-oss.conf oss-compat.conf
blacklist-firewire.conf blacklist-watchdog.conf

The ones in aqua blue appear as such in the terminal.

4. Open /etc/modules as root and check the file and make sure that there isn't a line with


b43

and that there is a line with

wl

- sorry, I don't know how open that as root, exactly. I'm still fairly new to ubuntu!

5. sudo apt-get install bcmwl-kernel-source
Reinstall bcmwl-kernel-source

-ok, I'll restart now.

Upon restart, there's no option for wireless under network manager. Broadcom STA shows up under hardware drivers (no b43!) but when I try to activate, I get:

Sorry, installation of this driver failed.

Please have a look at the log file for details: /var/log/jockey.log

I don't know how to look at this log file. When I put this into terminal, it tell me I don't have permission.

I have a hunch this has something to do with what's blacklisted above, but I have no idea how to resolve this!

chenxiaolong
January 3rd, 2010, 06:58 PM
Can you post the contents of /var/log/jockey.log?

You can open the file by running:

sudo cat /var/log/jockey.log

Whenever you run a command with sudo *command*, the command runs with root privileges; it means Super User DOes *command* :D.

EDIT: About the blacklists: What I meant by that step was to open each of the files in /etc/modprobe.d to check for the lines. An easier was to open the folder as root, where you can double click the files to open them:

gksu nautilus /etc/modprobe.d

GKSU is the graphical version of sudo, which is better for running graphical programs.

Good luck. I hope this works for you.

The Glidd
January 4th, 2010, 01:31 AM
Wow, a lot of problems :(.

TironN: Could you post the output of dmesg | tail after running sudo modprobe b43. This will give me a look at why b43 isn't loading.

The Glidd: You definitely don't want to try and activate the STA driver and the b43 driver together. They fight for control over the wireless card and as a result, nothing works. Since you've been having problems, I suggest you to use the STA driver because it's stable (although proprietary). Here's how:

1. sudo rmmod b43 ssb wl
Unloads the two wireless drivers.

2. sudo apt-get --purge remove b43-fwcutter bcmwl-kernel-source

3. Check the files in /etc/modprobe.d and make sure that there ISN'T

blacklist wl

in any of the files. Also make sure that there IS

blacklist b43
blacklist bcm43xx
blacklist ssb
blacklist b43legacy

in one of the files. You can create a new one if you want to be more organized (file has to end in .conf).

4. Open /etc/modules as root and check the file and make sure that there isn't a line with

b43

and that there is a line with

wl

5. sudo apt-get install bcmwl-kernel-source
Reinstall bcmwl-kernel-source

Goslings: Could you post the output of modinfo b43?

Here are the contents of the log file:

2010-01-03 19:15:30,215 DEBUG: reading modalias file /usr/share/jockey/modaliases/disable-upstream-nvidia
2010-01-03 19:15:30,248 DEBUG: reading modalias file /usr/share/jockey/modaliases/fglrx-modules.alias.override
2010-01-03 19:15:30,249 DEBUG: reading modalias file /usr/share/jockey/modaliases/nvidia-173
2010-01-03 19:15:30,252 DEBUG: reading modalias file /usr/share/jockey/modaliases/nvidia-185
2010-01-03 19:15:30,255 DEBUG: reading modalias file /usr/share/jockey/modaliases/nvidia-71
2010-01-03 19:15:30,256 DEBUG: reading modalias file /usr/share/jockey/modaliases/nvidia-96
2010-01-03 19:15:30,258 WARNING: Could not open DriverDB cache /var/cache/jockey/driverdb-OpenPrintingDriverDB.cache: [Errno 2] No such file or directory: '/var/cache/jockey/driverdb-OpenPrintingDriverDB.cache'
2010-01-03 19:15:30,258 DEBUG: loading custom handler /usr/share/jockey/handlers/sl_modem.py
2010-01-03 19:15:31,553 DEBUG: Instantiated Handler subclass __builtin__.SlModem from name SlModem
2010-01-03 19:15:31,560 DEBUG: Software modem not available
2010-01-03 19:15:31,561 DEBUG: loading custom handler /usr/share/jockey/handlers/dvb_usb_firmware.py
2010-01-03 19:15:31,572 DEBUG: Instantiated Handler subclass __builtin__.DvbUsbFirmwareHandler from name DvbUsbFirmwareHandler
2010-01-03 19:15:31,572 DEBUG: Firmware for DVB cards not available
2010-01-03 19:15:31,572 DEBUG: loading custom handler /usr/share/jockey/handlers/broadcom_wl.py
2010-01-03 19:15:31,582 DEBUG: Instantiated Handler subclass __builtin__.BroadcomWLHandler from name BroadcomWLHandler
2010-01-03 19:15:31,582 DEBUG: Broadcom STA wireless driver availability undetermined, adding to pool
2010-01-03 19:15:31,582 DEBUG: loading custom handler /usr/share/jockey/handlers/nvidia.py
2010-01-03 19:15:31,587 WARNING: modinfo for module nvidia failed: ERROR: modinfo: could not find module nvidia

2010-01-03 19:15:31,588 DEBUG: Instantiated Handler subclass __builtin__.NvidiaDriver from name NvidiaDriver
2010-01-03 19:15:31,589 DEBUG: NVIDIA accelerated graphics driver availability undetermined, adding to pool
2010-01-03 19:15:31,589 DEBUG: loading custom handler /usr/share/jockey/handlers/madwifi.py
2010-01-03 19:15:31,593 WARNING: modinfo for module ath_pci failed: ERROR: modinfo: could not find module ath_pci

2010-01-03 19:15:31,594 DEBUG: Instantiated Handler subclass __builtin__.MadwifiHandler from name MadwifiHandler
2010-01-03 19:15:31,594 DEBUG: Alternate Atheros "madwifi" driver availability undetermined, adding to pool
2010-01-03 19:15:31,594 DEBUG: loading custom handler /usr/share/jockey/handlers/b43.py
2010-01-03 19:15:31,604 DEBUG: Instantiated Handler subclass __builtin__.B43LegacyHandler from name B43LegacyHandler
2010-01-03 19:15:31,604 DEBUG: Broadcom B43legacy wireless driver availability undetermined, adding to pool
2010-01-03 19:15:31,607 DEBUG: Instantiated Handler subclass __builtin__.B43Handler from name B43Handler
2010-01-03 19:15:31,607 DEBUG: Broadcom B43 wireless driver availability undetermined, adding to pool
2010-01-03 19:15:31,607 DEBUG: loading custom handler /usr/share/jockey/handlers/fglrx.py
2010-01-03 19:15:31,611 WARNING: modinfo for module fglrx failed: ERROR: modinfo: could not find module fglrx

2010-01-03 19:15:31,613 DEBUG: Instantiated Handler subclass __builtin__.FglrxDriver from name FglrxDriver
2010-01-03 19:15:31,619 DEBUG: ATI/AMD proprietary FGLRX graphics driver availability undetermined, adding to pool
2010-01-03 19:15:31,619 DEBUG: all custom handlers loaded
2010-01-03 19:15:31,620 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002A43sv00001028sd000002AAbc03sc8 0i00')
2010-01-03 19:15:31,839 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0019v0000p0005e0000-e0,5,kramlsfw0,')
2010-01-03 19:15:31,979 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:31,979 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002929sv00001028sd000002AAbc01sc0 6i01')
2010-01-03 19:15:31,982 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002448sv00000000sd00000000bc06sc0 4i01')
2010-01-03 19:15:31,985 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0800:')
2010-01-03 19:15:31,985 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0303:')
2010-01-03 19:15:31,985 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002937sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:31,988 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0019v0000p0001e0000-e0,1,k74,ramlsfw')
2010-01-03 19:15:31,989 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:31,989 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'platform:Fixed MDIO bus')
2010-01-03 19:15:31,989 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00')
2010-01-03 19:15:32,013 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002930sv00001028sd000002AAbc0Csc0 5i00')
2010-01-03 19:15:32,016 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'i2c_i801', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,016 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0017v0001p0001e0100-e0,1,2,k110,111,112,r0,1,amlsfw')
2010-01-03 19:15:32,016 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,017 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0C01:')
2010-01-03 19:15:32,017 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'platform:dcdbas')
2010-01-03 19:15:32,017 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v000011ABd00004354sv00001028sd000002AAbc02sc0 0i00')
2010-01-03 19:15:32,043 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'sky2', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,043 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'platform:eisa')
2010-01-03 19:15:32,044 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002919sv00001028sd000002AAbc06sc0 1i00')
2010-01-03 19:15:32,046 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'iTCO_wdt', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,047 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002A40sv00001028sd000002AAbc06sc0 0i00')
2010-01-03 19:15:32,049 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'intel_agp', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,049 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:LNXVIDEO:')
2010-01-03 19:15:32,049 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0000:')
2010-01-03 19:15:32,049 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002A42sv00001028sd000002AAbc03sc0 0i00')
2010-01-03 19:15:32,052 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'i915', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,052 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0F13:')
2010-01-03 19:15:32,052 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:LNXTHERM:')
2010-01-03 19:15:32,052 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:LNXSYSTM:')
2010-01-03 19:15:32,053 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0C02:')
2010-01-03 19:15:32,053 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'usb:v05CAp180Ad8730dcEFdsc02dp01ic0Eisc02ip00')
2010-01-03 19:15:32,053 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d0000293Csv00001028sd000002AAbc0Csc0 3i20')
2010-01-03 19:15:32,056 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d0000293Asv00001028sd000002AAbc0Csc0 3i20')
2010-01-03 19:15:32,058 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0011v0001p0001eAB41-e0,1,4,11,14,k71,72,73,74,75,76,77,79,7A,7B,7C,7D, 7E,7F,80,8C,8D,8E,8F,94,98,9B,9C,9D,9E,9F,A2,A3,A4 ,A5,A6,AC,AD,B7,B8,B9,BF,C1,CD,D4,D7,D9,E0,E1,E2,E 3,EC,EE,ram4,l0,1,2,sfw')
2010-01-03 19:15:32,058 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,058 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0019v0000p0003e0000-e0,1,k8E,ramlsfw')
2010-01-03 19:15:32,059 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,059 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0000v0000p0000e0000-e0,5,kramlsfw2,')
2010-01-03 19:15:32,059 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,059 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0011v0002p0008e7321-e0,1,2,3,k110,111,112,145,14A,r0,1,a0,1,18,mlsfw')
2010-01-03 19:15:32,059 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'joydev', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,059 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'joydev', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,060 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,060 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002939sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,062 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'dmi:bvnDellInc.:bvrA07:bd05/13/2009:svnDellInc.:)nInspiron1545:)vr:rvnDellInc.:rn 0G848F:rvr:cvnDellInc.:ct8:cvr:')
2010-01-03 19:15:32,077 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'dell_wmi', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,077 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'dell_laptop', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,077 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0200:')
2010-01-03 19:15:32,077 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0019v0000p0006e0000-e0,1,kE0,E1,E3,F0,F1,F2,F3,F4,F5,ramlsfw')
2010-01-03 19:15:32,078 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,078 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00')
2010-01-03 19:15:32,078 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'usb:v0BDAp0158d5888dc00dsc00dp00ic08isc06ip50')
2010-01-03 19:15:32,083 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'usb_storage', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,083 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0103:)NP0C01:')
2010-01-03 19:15:32,083 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0000v0000p0000e0000-e0,5,kramlsfw4,')
2010-01-03 19:15:32,084 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,084 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0C04:')
2010-01-03 19:15:32,084 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002936sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,086 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002938sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,089 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002935sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,091 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d0000293Esv00001028sd000002AAbc04sc0 3i00')
2010-01-03 19:15:32,094 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'snd_hda_intel', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,094 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0011v0002p0008e0000-e0,1,2,k110,111,112,r0,1,amlsfw')
2010-01-03 19:15:32,094 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,094 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:)NP0B00:')
2010-01-03 19:15:32,095 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'usb:v05CAp180Ad8730dcEFdsc02dp01ic0Eisc01ip00')
2010-01-03 19:15:32,095 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'uvcvideo', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,095 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v000014E4d00004315sv00001028sd0000000Cbc02sc8 0i00')
2010-01-03 19:15:32,147 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted
2010-01-03 19:15:32,147 DEBUG: got handler kmod:wl([BroadcomWLHandler, nonfree, disabled] Broadcom STA wireless driver)
2010-01-03 19:15:32,147 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'ssb', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,147 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted
2010-01-03 19:15:32,147 DEBUG: got handler kmod:wl([BroadcomWLHandler, nonfree, disabled] Broadcom STA wireless driver)
2010-01-03 19:15:32,148 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'platform:)cspkr')
2010-01-03 19:15:32,148 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'pcspkr', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,148 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'snd_pcsp', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,148 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'serio:ty01pr00id00ex00')
2010-01-03 19:15:32,158 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'serio_raw', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,158 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'psmouse', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,158 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0001v111Dp76B2e0001-e0,12,kramls1,2,fw')
2010-01-03 19:15:32,159 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,159 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'pci:v00008086d00002934sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,162 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0019v0000p0000e0000-e0,1,k94,95,A1,E0,E1,EC,EE,1AF,ramlsfw')
2010-01-03 19:15:32,162 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,162 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'input:b0003v05CAp180Ae8730-e0,1,kD4,ramlsfw')
2010-01-03 19:15:32,162 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-01-03 19:15:32,162 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97fe80c> about HardwareID('modalias', 'acpi:PNP0100:')
2010-01-03 19:15:32,163 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002A43sv00001028sd000002AAbc03sc8 0i00')
2010-01-03 19:15:32,163 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0019v0000p0005e0000-e0,5,kramlsfw0,')
2010-01-03 19:15:32,163 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002929sv00001028sd000002AAbc01sc0 6i01')
2010-01-03 19:15:32,163 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002448sv00000000sd00000000bc06sc0 4i01')
2010-01-03 19:15:32,163 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0800:')
2010-01-03 19:15:32,163 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0303:')
2010-01-03 19:15:32,163 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002937sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,163 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0019v0000p0001e0000-e0,1,k74,ramlsfw')
2010-01-03 19:15:32,163 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'platform:Fixed MDIO bus')
2010-01-03 19:15:32,164 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00')
2010-01-03 19:15:32,164 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002930sv00001028sd000002AAbc0Csc0 5i00')
2010-01-03 19:15:32,164 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0017v0001p0001e0100-e0,1,2,k110,111,112,r0,1,amlsfw')
2010-01-03 19:15:32,164 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0C01:')
2010-01-03 19:15:32,164 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'platform:dcdbas')
2010-01-03 19:15:32,164 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v000011ABd00004354sv00001028sd000002AAbc02sc0 0i00')
2010-01-03 19:15:32,164 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'platform:eisa')
2010-01-03 19:15:32,164 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002919sv00001028sd000002AAbc06sc0 1i00')
2010-01-03 19:15:32,164 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002A40sv00001028sd000002AAbc06sc0 0i00')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:LNXVIDEO:')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0000:')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002A42sv00001028sd000002AAbc03sc0 0i00')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0F13:')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:LNXTHERM:')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:LNXSYSTM:')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0C02:')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'usb:v05CAp180Ad8730dcEFdsc02dp01ic0Eisc02ip00')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d0000293Csv00001028sd000002AAbc0Csc0 3i20')
2010-01-03 19:15:32,165 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d0000293Asv00001028sd000002AAbc0Csc0 3i20')
2010-01-03 19:15:32,166 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0011v0001p0001eAB41-e0,1,4,11,14,k71,72,73,74,75,76,77,79,7A,7B,7C,7D, 7E,7F,80,8C,8D,8E,8F,94,98,9B,9C,9D,9E,9F,A2,A3,A4 ,A5,A6,AC,AD,B7,B8,B9,BF,C1,CD,D4,D7,D9,E0,E1,E2,E 3,EC,EE,ram4,l0,1,2,sfw')
2010-01-03 19:15:32,166 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0019v0000p0003e0000-e0,1,k8E,ramlsfw')
2010-01-03 19:15:32,166 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0000v0000p0000e0000-e0,5,kramlsfw2,')
2010-01-03 19:15:32,166 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0011v0002p0008e7321-e0,1,2,3,k110,111,112,145,14A,r0,1,a0,1,18,mlsfw')
2010-01-03 19:15:32,166 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002939sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,166 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'dmi:bvnDellInc.:bvrA07:bd05/13/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn 0G848F:rvr:cvnDellInc.:ct8:cvr:')
2010-01-03 19:15:32,166 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0200:')
2010-01-03 19:15:32,166 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0019v0000p0006e0000-e0,1,kE0,E1,E3,F0,F1,F2,F3,F4,F5,ramlsfw')
2010-01-03 19:15:32,166 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00')
2010-01-03 19:15:32,167 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'usb:v0BDAp0158d5888dc00dsc00dp00ic08isc06ip50')
2010-01-03 19:15:32,167 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0103:PNP0C01:')
2010-01-03 19:15:32,167 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0000v0000p0000e0000-e0,5,kramlsfw4,')
2010-01-03 19:15:32,167 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0C04:')
2010-01-03 19:15:32,167 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002936sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,167 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002938sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,167 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002935sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,167 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d0000293Esv00001028sd000002AAbc04sc0 3i00')
2010-01-03 19:15:32,167 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0011v0002p0008e0000-e0,1,2,k110,111,112,r0,1,amlsfw')
2010-01-03 19:15:32,168 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0B00:')
2010-01-03 19:15:32,168 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'usb:v05CAp180Ad8730dcEFdsc02dp01ic0Eisc01ip00')
2010-01-03 19:15:32,168 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v000014E4d00004315sv00001028sd0000000Cbc02sc8 0i00')
2010-01-03 19:15:32,168 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'platform:pcspkr')
2010-01-03 19:15:32,168 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'serio:ty01pr00id00ex00')
2010-01-03 19:15:32,168 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0001v111Dp76B2e0001-e0,12,kramls1,2,fw')
2010-01-03 19:15:32,168 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'pci:v00008086d00002934sv00001028sd000002AAbc0Csc0 3i00')
2010-01-03 19:15:32,168 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0019v0000p0000e0000-e0,1,k94,95,A1,E0,E1,EC,EE,1AF,ramlsfw')
2010-01-03 19:15:32,169 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'input:b0003v05CAp180Ae8730-e0,1,kD4,ramlsfw')
2010-01-03 19:15:32,169 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x9b45fac> about HardwareID('modalias', 'acpi:PNP0100:')
2010-01-03 19:15:32,217 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted
2010-01-03 19:15:32,378 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted
2010-01-03 19:15:32,409 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted
2010-01-03 19:15:34,948 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted
2010-01-03 19:15:39,331 WARNING: /sys/module/wl/drivers does not exist, cannot rebind wl driver
2010-01-03 19:15:39,342 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted
2010-01-03 19:15:45,906 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted
2010-01-03 19:15:45,919 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted
2010-01-03 19:15:45,942 DEBUG: BroadcomWLHandler enabled(): kmod disabled, bcm43xx: blacklisted, b43: blacklisted, b43legacy: blacklisted

And I just opened up Nautilus:

Here are the contents of modprobe.d:

blacklist-wl
alsa-base.conf
blacklist.conf
blacklist-ath_pci.conf
blacklist-bcm43.conf
blacklist-firewire.conf
blacklist-framebuffer.conf
blacklist-modem.conf
blacklist-oss.conf (has an arrow shooting off the icon)
blacklist-watchdog.conf
libpisock9.conf
oss-compat.conf (has an arrow shooting off the icon)

Thanks!

k3Rn
January 4th, 2010, 03:24 AM
Hi chenxiaolong,

i've been trying hard to get the b43 driver to work on my dell mini 10 - =/
what a mess!

I now manually installed the 2.6.32 kernel (2.6.32-02063202-generic).

Your b43_compile script prompts some errors.

Here is the output of your script:



b43 Kernel Source Patcher: The exciting part 2!
-------------------------------------------------
Remember, you must me booted in your 2.6.32.2 kernel before you continue.
Do you want to continue?
(yes/no):
yes
The b43 driver will be unloaded before the script continues.

ERROR: Module b43 does not exist in /proc/modules
[: 120: !=: unexpected operator
Compiling the modules needed for compiling the kernel module b43 (hmmm...needs rewording :D). [Might need password for sudo]
scripts/kconfig/conf -s arch/x86/Kconfig
***
*** You have not yet configured your kernel!
*** (missing kernel config file ".config")
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `modules_prepare'. Stop.

Now for what we've been waiting for...the b43 compilation!!! YAY!!! [Also might need password for sudo]


ERROR: Kernel configuration is invalid.
include/linux/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.


WARNING: Symbol version dump /usr/src/linux-source-2.6.32/Module.symvers
is missing; modules will have no dependencies and modversions.

Building modules, stage 2.
/usr/src/linux-source-2.6.32/scripts/Makefile.modpost:42: include/config/auto.conf: No such file or directory
make[1]: *** No rule to make target `include/config/auto.conf'. Stop.
make: *** [modules] Error 2
Please enter your password if asked.
The commands being run are:
--------------------------------------
sudo mkdir /lib/modules/2.6.32-02063202-generic/updates/drivers > /dev/null
sudo mkdir /lib/modules/2.6.32-02063202-generic/updates/drivers/net > /dev/null
sudo mkdir /lib/modules/2.6.32-02063202-generic/updates/drivers/net/wireless > /dev/null
sudo mkdir /lib/modules/2.6.32-02063202-generic/updates/drivers/net/wireless/b43 > /dev/null
mkdir: cannot create directory `/lib/modules/2.6.32-02063202-generic/updates/drivers': No such file or directory
mkdir: cannot create directory `/lib/modules/2.6.32-02063202-generic/updates/drivers/net': No such file or directory
mkdir: cannot create directory `/lib/modules/2.6.32-02063202-generic/updates/drivers/net/wireless': No such file or directory
mkdir: cannot create directory `/lib/modules/2.6.32-02063202-generic/updates/drivers/net/wireless/b43': No such file or directory

Please enter your password is asked (again :( ).
The command being run is: "sudo depmod -a"

Enabling PIO Mode
options b43 pio=1

Loading b43 module... (ARGH, PASSWORDS!!!)
FATAL: Error inserting b43 (/lib/modules/2.6.32-02063202-generic/kernel/drivers/net/wireless/b43/b43.ko): Unknown symbol in module, or unknown parameter (see dmesg)

YAY!!! EVERYTHING IS DONE!!! :D:D:D
Now, just check the files in "/etc/modprobe.d/" and make sure they don't contain:

blacklist b43
blacklist ssb

Now that was easy wasn't it? :) Enjoy your wireless!
Output of modprobe b43:



k3rn@kernkraft:~$ sudo modprobe b43
FATAL: Error inserting b43 (/lib/modules/2.6.32-02063202-generic/kernel/drivers/net/wireless/b43/b43.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Here the dmesg output:



733.221499] b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 733.221521] b43-phy0: Controller RESET (DMA error) ...
[ 733.221534] Controller restarted
[ 733.464455] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 738.985499] b43-phy0: Controller restarted
[ 738.986504] b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 738.986539] b43-phy0: Controller RESET (DMA error) ...
[ 739.216428] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 744.733448] b43-phy0:
[ 744.733460] b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 744.733481] b43-phy0: Controller RESET (DMA error) ...
[ 744.733494] Controller restarted
[ 744.972443] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 750.489450] b43-phy0:
[ 750.489461] b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 750.489482] b43-phy0: Controller RESET (DMA error) ...
[ 750.489495] Controller restarted
[ 750.645367] b43-pci-bridge 0000:03:00.0: PCI INT A disabled
[ 754.773778] b43-pci-bridge 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 754.773814] b43-pci-bridge 0000:03:00.0: setting latency timer to 64
[ 754.840602] ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
[ 754.867234] b43: Unknown parameter `pio'
[ 754.915106] b43: Unknown parameter `pio'
[ 1352.172081] b43: Unknown parameter `pio'
[ 2107.124385] b43-pci-bridge 0000:03:00.0: PCI INT A disabled
[ 2111.811660] b43-pci-bridge 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 2111.811942] b43-pci-bridge 0000:03:00.0: setting latency timer to 64
[ 2111.876795] ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
[ 2111.901145] b43: Unknown parameter `pio'
[ 2111.933204] b43: Unknown parameter `pio'
I hope you can help me to get it to work - in the end.

Greetings,
Markus

chenxiaolong
January 4th, 2010, 03:36 AM
Delete the blacklist-wl file in /etc/modprobe.d (as root). Then restart and try again. If it still doesn't work, try plugging in your wired internet, then reactivating the STA Driver in the Hardware Drivers.

howcanireachthesekids
January 4th, 2010, 12:10 PM
Chienxialong, first of all i want to thank you for taking your time to make this guide that i am sure it helped many Broadcom users.
I would like to ask you some questions if you could possibly help me with this issue.
I have a HP Pavilion DV6-1020el laptop which uses Broadcom BCM4312 (rev 01) card.


It is 14e4:4315. I have installed Ubuntu 9.04 using the option "Inside Windows" and given it a 17 GB harddisk.


So the driver wl is loaded to get my card working.But as you know, this driver does not support monitor mode. I want to try monitor mode with injection, which i herd works with 14e4:4315.
I think i know what to do.I should blacklist the wl driver and get b43 driver to work.But to do this i am a little stuck.I am not that good with Linux.
So i am asking you, which options of your guide should i use ?
Can you guide me with specifics into getting my card ( which is the same as yours)
to work in monitor mode with injection.I want to learn about WEP cracking for EDUCATIONAL PURPOSES ONLY !!!!
Also, if i would be using Ubuntu 9.10 on full hard disk installation, which part of your guide should i use ?
and do i need internet connection to make the card work ? because the only way i can get internet is by wireless but since the card would not work in 9.10 ( i have tried it ) i dont think i can get internet other ways. i can just download the neccessary files and put them in USB.
or will try connecting in 9.10 via using the wireless in my nokia E71 using bluetooth connection with the laptop then...



Thank you in advance.

chenxiaolong
January 4th, 2010, 03:17 PM
Yesssss, snow day, no school!

Anyway,

howcanireachthesekids: Unfortunately, you need kernel 2.6.32, which can only be installed on Ubuntu 9.10, not Ubuntu 9.04. The wireless doesn't work by default in Ubuntu 9.10 because the Ubuntu developers decided not to include the wl driver for the standard install, unlike Ubuntu 8.04-9.04. You should install Ubuntu 9.10 first, then come back to this thread. I'll give you some steps later because I'll still trying to fix this problem. There's no fool-proof solution yet :(.

K3rn: could you try running these commands:



cd /usr/src/linux-source-2.6.32 #Change to source directory
sudo make oldconfig #Use the default (I think) settings for make
sudo make prepare #Prepares make to compile kernel
sudo make modules_prepare #Prepares make to compile kernel modules
sudo make modules SUBDIRS=drivers/net/wireless/b43 #Compiles b43
sudo rmmod b43 ssb wl #Unload in-use modules
cd /lib/modules/`uname -r`/kernel/drivers/net/wireless/b43 #Change to b43 directory of current kernel
sudo mv b43.ko b43.ko.backup #Backup current b43 module
sudo cp /usr/src/linux-source-2.6.32/drivers/net/wireless/b43/b43.ko ./ #Copies new b43 driver to the kernel modules directory (where the drivers are)
sudo modprobe ssb # 0R REBOOT
sudo modprobe b43 pio=1 # OR REBOOT


Hope that helps

howcanireachthesekids
January 4th, 2010, 03:26 PM
Yesssss, snow day, no school!

Anyway,

howcanireachthesekids: Unfortunately, you need kernel 2.6.32, which can only be installed on Ubuntu 9.10, not Ubuntu 9.04. The wireless doesn't work by default in Ubuntu 9.10 because the Ubuntu developers decided not to include the wl driver for the standard install, unlike Ubuntu 8.04-9.04. You should install Ubuntu 9.10 first, then come back to this thread. I'll give you some steps later because I'll still trying to fix this problem. There's no fool-proof solution yet :(.


Well i appreciate your quick reply :)
Ok i will install Ubuntu 9.10 with kernel 2.6.32 on fresh installation in the entire HDD. I will try to get internet access to download any necessary packages/files via ethernet cable or somehow using my Nokia E71 with bluetooth connection and the laptop.
Then what do you suggest ? Which guide steps ?

Thanks

k3Rn
January 4th, 2010, 11:25 PM
Hi chenxiaolong,

thank you for the fast reply.

I did run the commands, here is the complete log/output:



k3rn@kernkraft:~$ cd /usr/src/linux-source-2.6.3
linux-source-2.6.31/ linux-source-2.6.32/
k3rn@kernkraft:~$ cd /usr/src/linux-source-2.6.32
k3rn@kernkraft:/usr/src/linux-source-2.6.32$ sudo make oldconfig
[sudo] password for k3rn:
scripts/kconfig/conf -o arch/x86/Kconfig
#
# using defaults found in /boot/config-2.6.32-02063202-generic
#
#
# configuration written to .config
#
k3rn@kernkraft:/usr/src/linux-source-2.6.32$ sudo make prepare
scripts/kconfig/conf -s arch/x86/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CC kernel/bounds.s
GEN include/linux/bounds.h
CC arch/x86/kernel/asm-offsets.s
GEN include/asm/asm-offsets.h
CALL scripts/checksyscalls.sh
k3rn@kernkraft:/usr/src/linux-source-2.6.32$ sudo make modules_prepare
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CALL scripts/checksyscalls.sh
HOSTCC scripts/genksyms/genksyms.o
SHIPPED scripts/genksyms/lex.c
SHIPPED scripts/genksyms/parse.h
SHIPPED scripts/genksyms/keywords.c
HOSTCC scripts/genksyms/lex.o
SHIPPED scripts/genksyms/parse.c
HOSTCC scripts/genksyms/parse.o
HOSTLD scripts/genksyms/genksyms
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
scripts/mod/modpost.c: In function ‘get_markers’:
scripts/mod/modpost.c:1562: warning: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result
scripts/mod/modpost.c: In function ‘add_marker’:
scripts/mod/modpost.c:1982: warning: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/selinux/mdp/mdp
HOSTCC scripts/kallsyms
scripts/kallsyms.c: In function ‘read_symbol’:
scripts/kallsyms.c:112: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result
HOSTCC scripts/conmakehash

---

k3rn@kernkraft:/usr/src/linux-source-2.6.32$ ls drivers/net/wireless/b43
b43.h dma.c lo.h pcmcia.h phy_g.h pio.h sysfs.h tables_nphy.h
b43_kernel_2.6.32.2.patch dma.h main.c phy_a.c phy_lp.c rfkill.c tables.c wa.c
b43_kernel_2.6.32.2.patch.1 Kconfig main.h phy_a.h phy_lp.h rfkill.h tables.h wa.h
b43_kernel_2.6.32.2.patch.2 leds.c Makefile phy_common.c phy_n.c sdio.c tables_lpphy.c xmit.c
debugfs.c leds.h modules.order phy_common.h phy_n.h sdio.h tables_lpphy.h xmit.h
debugfs.h lo.c pcmcia.c phy_g.c pio.c sysfs.c tables_nphy.c
k3rn@kernkraft:/usr/src/linux-source-2.6.32$ sudo make modules SUBDIRS=drivers/net/wireless/b43

WARNING: Symbol version dump /usr/src/linux-source-2.6.32/Module.symvers
is missing; modules will have no dependencies and modversions.

CC [M] drivers/net/wireless/b43/main.o
CC [M] drivers/net/wireless/b43/tables.o
CC [M] drivers/net/wireless/b43/phy_common.o
CC [M] drivers/net/wireless/b43/phy_g.o
CC [M] drivers/net/wireless/b43/phy_a.o
CC [M] drivers/net/wireless/b43/phy_lp.o
drivers/net/wireless/b43/phy_lp.c:382: warning: ‘lpphy_restore_dig_flt_state’ defined but not used
drivers/net/wireless/b43/phy_lp.c:890: warning: ‘lpphy_disable_rx_gain_override’ defined but not used
CC [M] drivers/net/wireless/b43/tables_lpphy.o
CC [M] drivers/net/wireless/b43/sysfs.o
CC [M] drivers/net/wireless/b43/xmit.o
CC [M] drivers/net/wireless/b43/lo.o
CC [M] drivers/net/wireless/b43/wa.o
CC [M] drivers/net/wireless/b43/dma.o
CC [M] drivers/net/wireless/b43/pio.o
CC [M] drivers/net/wireless/b43/rfkill.o
CC [M] drivers/net/wireless/b43/leds.o
LD [M] drivers/net/wireless/b43/b43.o
Building modules, stage 2.
MODPOST 1 modules
CC drivers/net/wireless/b43/b43.mod.o
LD [M] drivers/net/wireless/b43/b43.ko
k3rn@kernkraft:/usr/src/linux-source-2.6.32$ sudo rmmod b43 ssb wl
ERROR: Module b43 does not exist in /proc/modules
ERROR: Module wl does not exist in /proc/modules
When trying to load the b43 module i get the following error now:



sudo modprobe b43 pio=1
[sudo] password for k3rn:
FATAL: Error inserting b43 (/lib/modules/2.6.32-02063202-generic/kernel/drivers/net/wireless/b43/b43.ko): Invalid module format


dmesg prompts:


b43: no symbol version for module_layout


I don't know what to try else - please have a second look at it.

Thank you in advance!

The Glidd
January 5th, 2010, 03:41 AM
Delete the blacklist-wl file in /etc/modprobe.d (as root). Then restart and try again. If it still doesn't work, try plugging in your wired internet, then reactivating the STA Driver in the Hardware Drivers.

I deleted the blacklist-wl file in /etc/modprobe.d using nautilus. When I return via nautilus, there's no blacklist-wl anywhere to be seen. I then tried to activate the STA driver (while wired) and restarted. Then I get:

This driver is activated but not currently in use.

There's no wireless dialog to speak of in network manager.

TironN
January 6th, 2010, 05:36 AM
Ok. After a mod probe dmesg gives me:


[ 659.512320] b43: no symbol version for module_layout


dmesg prompts:

Code:
b43: no symbol version for module_layout
I don't know what to try else - please have a second look at it.

Thank you in advance!

Same as me!

emas80
January 6th, 2010, 11:17 AM
To TironN (http://ubuntuforums.org/member.php?u=934510) and k3Rn (http://ubuntuforums.org/member.php?u=936978):
Which kernel are you using? It seems that is trying to insert a wrong module in running kernel, or something is missing with inserted module.
What's the result of

uname -a and
modinfo b43 ?

The first command prints kernel actual version, while the second prints information about current b43 module version.

Maybe I just found this solution from another post:

Just copy the file Module.symversion from /lib/modules/your-kernel-name into the kernel source location (=/usr/src/linux-source-2.6.32).

I don't know why this file is missing, but k3Rn (http://ubuntuforums.org/member.php?u=936978) do you remember the warning about "Symbol version dump missing" when running chenxiaolong (http://ubuntuforums.org/member.php?u=724117)'s script? I think that is related.

If it still doesn't work, I think that recompiling (and of course installing) all the kernel, and not only modules, should work, fixing all these little problems.

howcanireachthesekids
January 7th, 2010, 08:31 AM
bump, i need help :(

k3Rn
January 7th, 2010, 10:56 PM
@emas80: i couldn't find any modules.symversion file in my system.

for now i give up on this topic, i don't have enough time at the moment.

i'll keep track on this thread here and will try it again with a fresh ubuntu install when i find the time.

anyway thank you guys for the help so far - i'll be back sometime :)

greetz,

k3rn

gfa
January 8th, 2010, 08:07 AM
[SOLVED] View next post :)

Hi chenxiaolong... I've run your commands, and got the same errors as K3rn... As I can see in his last message, he has no time to help you, but I really would like to get B43 in 2.6.32 so if you have any idea I could test ;)

After rebooting in new kernel, applying the patch and trying to insert the new kernel module I get:



FATAL: Error inserting b43 (/lib/modules/2.6.32-02063203-generic/updates/drivers/net/wireless/b43/b43.ko): Invalid module format

In dmesg I get:


b43: no symbol version for module_layout

I have tried stripping symbols in kernel, but then I get another error stating there're no symbols :S

Any help will be great :)

Thanks
gFa




K3rn: could you try running these commands:



cd /usr/src/linux-source-2.6.32 #Change to source directory
sudo make oldconfig #Use the default (I think) settings for make
sudo make prepare #Prepares make to compile kernel
sudo make modules_prepare #Prepares make to compile kernel modules
sudo make modules SUBDIRS=drivers/net/wireless/b43 #Compiles b43
sudo rmmod b43 ssb wl #Unload in-use modules
cd /lib/modules/`uname -r`/kernel/drivers/net/wireless/b43 #Change to b43 directory of current kernel
sudo mv b43.ko b43.ko.backup #Backup current b43 module
sudo cp /usr/src/linux-source-2.6.32/drivers/net/wireless/b43/b43.ko ./ #Copies new b43 driver to the kernel modules directory (where the drivers are)
sudo modprobe ssb # 0R REBOOT
sudo modprobe b43 pio=1 # OR REBOOT


Hope that helps

gfa
January 8th, 2010, 09:30 AM
I have successfully compiled b43 module, just needed one more command:


cd /usr/src/linux-source-2.6.32 #Change to source directory
sudo cp /usr/src/linux-headers-`uname -r`/Module.symvers ./ #Copy symbols dependencies
sudo make oldconfig #Use the default (I think) settings for make
sudo make prepare #Prepares make to compile kernel
sudo make modules_prepare #Prepares make to compile kernel modules
sudo make modules SUBDIRS=drivers/net/wireless/b43 #Compiles b43
sudo rmmod b43 ssb wl #Unload in-use modules
cd /lib/modules/`uname -r`/kernel/drivers/net/wireless/b43 #Change to b43 directory of current kernel
sudo mv b43.ko b43.ko.backup #Backup current b43 module
sudo cp /usr/src/linux-source-2.6.32/drivers/net/wireless/b43/b43.ko ./ #Copies new b43 driver to the kernel modules directory (where the drivers are)
sudo depmod -a # Refresh modules
sudo modprobe ssb # 0R REBOOT
sudo modprobe b43 pio=1 # OR REBOOT

Now, I can insert the module... but my system freezes after few seconds (about 10 secs), any clue?

Thanks
gFa

TironN
January 8th, 2010, 11:51 AM
I have successfully compiled b43 module, just needed one more command:


cd /usr/src/linux-source-2.6.32 #Change to source directory
sudo cp /usr/src/linux-headers-`uname -r`/Module.symvers ./ #Copy symbols dependencies
sudo make oldconfig #Use the default (I think) settings for make
sudo make prepare #Prepares make to compile kernel
sudo make modules_prepare #Prepares make to compile kernel modules
sudo make modules SUBDIRS=drivers/net/wireless/b43 #Compiles b43
sudo rmmod b43 ssb wl #Unload in-use modules
cd /lib/modules/`uname -r`/kernel/drivers/net/wireless/b43 #Change to b43 directory of current kernel
sudo mv b43.ko b43.ko.backup #Backup current b43 module
sudo cp /usr/src/linux-source-2.6.32/drivers/net/wireless/b43/b43.ko ./ #Copies new b43 driver to the kernel modules directory (where the drivers are)
sudo depmod -a # Refresh modules
sudo modprobe ssb # 0R REBOOT
sudo modprobe b43 pio=1 # OR REBOOTNow, I can insert the module... but my system freezes after few seconds (about 10 secs), any clue?

Thanks
gFa

I was getting the same errors and did the same thing (the header version) and got the same system freeze. It got so bad I have done a fresh installation (off a nikon camera no less (I'm overseas)) so hopefully it will work now!

chenxiaolong
January 8th, 2010, 09:54 PM
Thanks for the information about the symbols dependencies. I've added that to the script and I reattached the script on my first post.

Sorry for the long wait. I've been studying for my midterms (I'm only a High School freshman. I have to take midterms :(). Anyway, I'll try and figure out why it freezes after ten seconds. If you want to remove the driver, you can always boot into an older kernel and delete /lib/modules/YOUR_KERNEL/updates/drivers/net/wireless/b43/b43.ko.

gfa
January 8th, 2010, 11:16 PM
Thank you... If you need some kind of log or something like that, I could try again... i'm still using karmic default kernel (2.6.31) as primary but I can reboot to test whenever you need...

By the way, I downloaded the latests packages from Kernel PPA, version:

2.6.32-02063203

I think they're different than the one that downloads your script, does this affect?



Thanks for the information about the symbols dependencies. I've added that to the script and I reattached the script on my first post.

Sorry for the long wait. I've been studying for my midterms (I'm only a High School freshman. I have to take midterms :(). Anyway, I'll try and figure out why it freezes after ten seconds. If you want to remove the driver, you can always boot into an older kernel and delete /lib/modules/YOUR_KERNEL/updates/drivers/net/wireless/b43/b43.ko.

chenxiaolong
January 8th, 2010, 11:24 PM
Actually, it does. The script is written for kernel 2.6.32.2, but you have kernel 2.6.32.3. I'll upload a new script in addition to the one for 2.6.32.2. I didn't know that kernel 2.6.32.3 is out already :confused::D.

gfa
January 8th, 2010, 11:27 PM
Actually, it does. The script is written for kernel 2.6.32.2, but you have kernel 2.6.32.3. I'll upload a new script in addition to the one for 2.6.32.2. I didn't know that kernel 2.6.32.3 is out already :confused::D.

Maybe this is the freezes cause :o

I think I'll wait until you submit the new patch instead of downloading the old kernel packages...

Thanks
gFa

chenxiaolong
January 9th, 2010, 12:04 AM
I just uploaded it.

gfa
January 9th, 2010, 12:09 AM
I just uploaded it.

I don't see any diff between the old and the newest patch file :S

chenxiaolong
January 9th, 2010, 12:58 AM
The patch file will be the same until 2.6.33 because the coding in the 2.6.32 "series" is the same. I just fixed the script so it would recognize that you're running kernel 2.6.32.3.

gfa
January 9th, 2010, 01:01 AM
The patch file will be the same until 2.6.33 because the coding in the 2.6.32 "series" is the same. I just fixed the script so it would recognize that you're running kernel 2.6.32.3.

Yes :) what I wanted to say is that as the patch is the same and installed manually the new kernel I still have the freezes... As long as I get into my home I will try again and post the logs here...

chenxiaolong
January 9th, 2010, 01:51 AM
Crap. Double crap. Triple crap. I just noticed that I've been using the wl driver the whole time and not b43 :(:(. I'm such an idiot. I just tried loading the b43 driver under the new kernel 2.6.32.3 and I'm getting the same 10-seconds-waiting-then-kernel-panic error. I'm going to try compiling the b43 driver from the wireless-testing git tree. It already has the files prepatched, so that eliminates some work.

I would be glad if emas80 could give some help on this. He's the only one who's got it working so far.

gfa
January 9th, 2010, 01:54 AM
Crap. Double crap. Triple crap. I just noticed that I've been using the wl driver the whole time and not b43 :(:(. I'm such an idiot...

LOL :S

Good luck
gFa

emas80
January 9th, 2010, 12:26 PM
Crap. Double crap. Triple crap. I just noticed that I've been using the wl driver the whole time and not b43. I'm such an idiot. I just tried loading the b43 driver under the new kernel 2.6.32.3 and I'm getting the same 10-seconds-waiting-then-kernel-panic error. I'm going to try compiling the b43 driver from the wireless-testing git tree. It already has the files prepatched, so that eliminates some work.

I would be glad if emas80 could give some help on this. He's the only one who's got it working so far.

LOL :)

So you are saying that using patched-kernel.org (and not Ubuntu) kernel 2.6.32.3 instead of 2.6.32.2 locks the system in kernel panic?
I had a kernel panic too, the very first time I booted Ubuntu 9.10 with its 2.6.31 kernel, when I checked wireless card driver (I really don't remember which one, if wl or b43) in Admnistration>Hardware drivers. I didn't care, because I was at work, I was full of to-dos and I had a wired connection, I simply rebooted and then nothing strange happened since then, simply my wifi was not working. So I think now that kernel panic was caused by this driver ;)

But, by the way, I really don't know what to do.. :(
A kernel panic is a bad thing.. I just suggest to check log files (system>log file viewer) for error messages, maybe there is something useful..
All that I did was patch with the right patch the right kernel. I usually recompile my own kernel, after downloading the last version from kernel.org, I'm a little maniac with this ;).
So my system was totally "clean", headers compiled and installed, kernel compiled and installed and running, modules compiled and installed, all in right directories, dkms autorecompiled correctly (and still now checks on every boot) nvidia and virtualbox modules.. This is just to say that I did the things in the way the things are to be done, a coherent way, I KNOW what I was doing.
I'm not telling YOU don't know :D, I'm trying to describe my totally clean situation.

What I don't undestand is...
Which kernel are you using? Is the kernel recompiled? Has it been totally recompiled and installed together with its kernel headers? I don't totally agree with copying that "Module.symvers" file, just because in my ignorance I don't know what "Module.symvers" file is (I can wonder it, but I'm not totally sure), and I'm not sure about things I ignore ;).
In particular,


sudo cp /usr/src/linux-headers-`uname -r`/Module.symvers
what's "uname -r"? I hope that it is 2.6.32 (but I frankly don't believe so.. ;)) , because else you are copying a file from current running kernel to a complete different one!
Maybe it could work, maybe not..
What that I know, is that there is a kernel panic, and a possibly mix of modules from possible different kernels...
So, chenxiaolong (http://ubuntuforums.org/member.php?u=724117), what's your current situation?
What's the changelog between 2.6.32.2 and 2.6.32.3?
I'm really NOT going to install new kernel (until 2.6.33 revision comes out ;)) I need my notebook for my job and now, after Christmas' holidays are over, I have no time to recompile and rechecks everything, right now everything works and I'm happy with this.

llamafier
January 10th, 2010, 07:45 PM
This thread looks very promising in solving my issues with b43. I tried using the 2.6.32 script to update the kernel and it seems to be attempting to install the amd64 version on accident. I've tried manually updating to the newer kernel but I always mess it up somehow.

I have an HP Mini 311 with an Atom processor so that would require the i386 kernel right?

Thanks for making that script chenxiaolong it got me very excited, even though it hasn't worked yet. :D

hypergeek14
January 11th, 2010, 11:48 AM
Perhaps the all-knowing chenxiaolong can help me with my b43 problem?

http://ubuntuforums.org/showthread.php?t=1373877

saewelo
January 15th, 2010, 06:20 PM
This bit worked for me
----------------------------------------------------------------------------------------------
This is the new, updated information for Karmic. The steps are much easier in Karmic than in Jaunty. The steps for Jaunty are at the bottom of the post for reference and for people who still use Karmic.

1. Open up Terminal.

2. Install the "linux-backports-modules-karmic" (newer wireless drivers from compat-wireless) package and the "b43-fwcutter" package (wireless firmware). During installation, if it asks you to fetch the firmware automatically, make sure you select yes.

Code:
sudo apt-get install linux-backports-modules-karmic b43-fwcutter
3. Blacklist the ssb module.

Code:
echo "blacklist ssb" | sudo tee -a /etc/modprobe.d/blacklist-ssb.conf
4. Blacklist the wl module.

Code:
echo "blacklist wl" | sudo tee -a /etc/modprobe.d/blacklist-wl.conf
5. Reboot

6. Enjoy your wireless!!!

----------------------------------------------------------------------------------------------------------------
Compaq Mini 110C-1100

chenxiaolong
January 15th, 2010, 10:38 PM
I am soo sorry for the late response. VBulletin didn't send email notifications for any of my fifty some subscribed threads :(. Anyway, I'm back now :).

Emas80: I am actually running the Ubuntu version of the 2.6.32.3 kernel from the Ubuntu Kernel PPA. I am not running a self compiled version of the 2.6.32.3 kernel. I do have the headers and the kernel source installed. The modules.symvers file contains information about the symbol versions for the kernel modules. I really have no idea what symbols (in this case) are. About "uname -r": It's actually a command that tells you what kernel version you are booted into and are running. When you use " ` " in a script or a command, it runs the command inside the " ` " and replaces " `blahblah` " with the output of the command "blahblah." It essentially does the same thing as "$(blahblah)." Here's the changelog of kernel 2.6.32.3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.3/CHANGES. It doesn't fix anything for b43, except a error on the PPC platform.
I'll try compiling a kernel from kernel.org and hopefully it will finally work :D.

llamafier: I'm sorry my script installed the amd64 version of the kernel on your computer. You can remove the kernel using Synaptic or apt-get. Could you post the output of the command "uname -a" so I can improve the detection of my script (I don't have a computer running Ubuntu i386)? Also, my script doesn't work quite right yet :( because the Ubuntu version of the kernel isn't cooperating with the new, patched b43 driver. I'll let you know when I get it working :D.

saewelo: I suggest that you do NOT use that method as it will eventually cause a DMA error, which will cause the wireless card to stop working until you manually take out the wireless card and touch all the pins (pretty annoying).


Anyway, I'll be compiling the latest kernel from http://kernel.org and I'll let you guys know how it goes :D.

Chen Xiao-Long

Alacrity
January 16th, 2010, 02:01 AM
chenxiaolong,

Could you please list the 50 subsribed threads? Your b43 thread subscribers will all want to subsribe to their thread facilitor's recommended threads.

Alacrity

chenxiaolong
January 16th, 2010, 03:03 AM
Well, I haven't subscribed to many useful software threads. Most of them are threads on hardware issues (because I've had past experience). I'll list some threads you guys might find useful:

http://ubuntuforums.org/showthread.php?t=1352270
http://ubuntuforums.org/showthread.php?t=1317801
http://ubuntuforums.org/showthread.php?t=1361657
http://ubuntuforums.org/showthread.php?t=1009404
http://ubuntuforums.org/showthread.php?t=1361108
http://ubuntuforums.org/showthread.php?t=1360732
http://ubuntuforums.org/showthread.php?t=1362237
http://ubuntuforums.org/showthread.php?t=1361594
http://ubuntuforums.org/showthread.php?t=1318953
http://ubuntuforums.org/showthread.php?t=1347483
http://ubuntuforums.org/showthread.php?t=1352964
http://ubuntuforums.org/showthread.php?t=1350865
http://ubuntuforums.org/showthread.php?t=978212
http://ubuntuforums.org/showthread.php?t=1352665
http://ubuntuforums.org/showthread.php?t=1215686
http://ubuntuforums.org/showthread.php?t=1338775
http://ubuntuforums.org/showthread.php?t=1311826
http://ubuntuforums.org/showthread.php?t=1308235
http://ubuntuforums.org/showthread.php?t=1052602

And I modified the Gnometris code for my brother a while ago so he could get a high score:

http://ubuntuforums.org/showthread.php?t=1064445

chenxiaolong
January 16th, 2010, 03:15 AM
Also, could someone tell me how to cross compile a kernel for i386 (from amd64) or point out a link to a HowTo? Google isn't very helpful :( I'm planning on creating a PPA at Launchpad for a prepatched version of the latest kernel at http://kernel.org for an easy install.

gfa
January 16th, 2010, 10:09 AM
I have just downloaded new Lucid Lynx alpha2 and b43 driver for 14e4:4315 works great!!!! =) I could even change to monitor mode :o

I will try again using Kernels PPA's for Karmic as this Lucid release is still in early dev and I use this notebook as main system.

By the way, the kernel version in Lucid was 2.6.32.10...

chenxiaolong
January 16th, 2010, 02:33 PM
Thanks for the information! It's nice to know that the next Ubuntu release will support the wireless card natively :D:D.

llamafier
January 16th, 2010, 04:17 PM
llamafier: I'm sorry my script installed the amd64 version of the kernel on your computer. You can remove the kernel using Synaptic or apt-get. Could you post the output of the command "uname -a" so I can improve the detection of my script (I don't have a computer running Ubuntu i386)? Also, my script doesn't work quite right yet :( because the Ubuntu version of the kernel isn't cooperating with the new, patched b43 driver. I'll let you know when I get it working :D.

Here is the output of uname -a


Linux myhostname 2.6.32-7-generic #10-Ubuntu SMP Sun Dec 6 13:43:20 UTC 2009 i686 GNU/Linux

(this was from Ubuntu 10.04 Alpha 1, but I think the part you needed to see should be the same right?)



I tried 10.04 Alpha 1 since it had the newer kernel, but I couldn't get the wireless working. I think there was issues in the b43 package.

Looks like that was fixed in Alpha 2 unless I just screwed something up before. Thanks for pointing that out gfa! I'm gonna give it a try now. :D

chenxiaolong
January 17th, 2010, 02:59 AM
Does anyone know a free reliable web hosting company (free only; I'm 14; can't make money yet :()? I have the kernel with the b43 patch packaged as debs (amd64 version -- native compile; i386 version -- chroot 32bit compile). I just need a reliable web host for an apt repository. My server is running on a ADSL connection, which is waaaay too slow for more than one user.

Also: If you ever need to compile anything, use Distcc. It can use any computer in your network to help compiling whatever you need to compile :D.

rivensky
January 17th, 2010, 06:50 AM
I had to register just so I could tell you THANK YOU! I'm still a Linux n00b and just wiped Vista off my Dell XPS laptop and was not happy to find my wireless wasn't working. Problem solved! And so easy! Thanks again!

Indolence
January 17th, 2010, 12:47 PM
The b43 driver in lucid lynx alpha2 gives me dma errors


Does anyone know a free reliable web hosting company (free only; I'm 14; can't make money yet :()? I have the kernel with the b43 patch packaged as debs (amd64 version -- native compile; i386 version -- chroot 32bit compile). I just need a reliable web host for an apt repository. My server is running on a ADSL connection, which is waaaay too slow for more than one user.

Also: If you ever need to compile anything, use Distcc. It can use any computer in your network to help compiling whatever you need to compile :D.

zymic.com maybe?

chenxiaolong
January 17th, 2010, 03:04 PM
Indolence: Unfortunately, zymic doesn't allow a file hosting site (apparently, an apt repository falls under this category).

voxsim
January 17th, 2010, 08:47 PM
Hello everyone,

I read this thread beacause and i download the b43_kernel_2.6.32.3.sh script, first i run the third option beacause i have the kernel 2.6.31-18 on Ubuntu 9.10, after i run the first option of this script and finally i have to run the second option, but this don't work :(

When i type


sudo sh b43_kernel_2.6.32.3.sh /usr/src/linux-source-2.6.32

i have this result



/usr/src/linux-source-2.6.32
The path you set isn't valid (or you typed it wrong). (Man, I have to type the path again, darn it :D) It has to be the full path name.


I modified the script and i added an "echo $@" and seems the if[$@=="/*"] don't work, please help me :P

voxsim
January 18th, 2010, 12:28 AM
I already try only third option of kernel script and i finally read XD


You must now boot into the new 2.6.32.3 kernel to build the b43 driver.
After reboot, you will need to run part 2 of this script.
You can get it at http://software.6368.co.cc/linux/b43/patches/b43_compile_2.6.32.3.sh
The link is also in my first post on my b43 HowTo thread on UbuntuForums

I have to reboot now?? Awwwwwwww. Oh, well. (After all, it's Linux. Who cares about rebooting :D)

Excuse me for my first post :P but when i reboot in grub i didn't see the new kernel, but i see only the kernel 2.6.31-18

Indolence
January 18th, 2010, 11:11 AM
Indolence: Unfortunately, zymic doesn't allow a file hosting site (apparently, an apt repository falls under this category).

Well... I rent a part of a webserver. If you can get yourself a domain name (for which you can change the name servers/dns servers) I can give you some space for free. The server is running everything you're likely to need, php, mysql, etc.

chenxiaolong
January 18th, 2010, 03:30 PM
Indolence: I've already found a host that suits my needs: cxr.cc. Thanks anyway though :D.

Emas80:

I just recompiled the newest stable kernel (2.6.32.3) from kernel.org and the b43 driver loads fine, but it won't connect to any networks.

Did you compile your kernel using the Ubuntu/Debian way or the traditional way?

I compiled mine by running:

sudo su
cd /usr/src
wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.3.tar.bz2
tar jxvf linux-2.6.32.3.tar.bz2
cd linux-2.6.32.3
cp /boot/config-`uname -r` ./.config
make oldconfig
make-kpkg clean
CONCURRENCY_LEVEL=3 fakeroot make-kpkg --initrd --append-to-version=-cxl kernel_image kernel_headers modules_image
dpkg -i ../linux-*.deb

Is that basically what you did? The kernel I compiled can boot perfectly fine and can load any of my other modules (wl,nvidia,virtualbox,etc) and b43, but b43 won't connect to any networks. Dmesg doesn't give any errors either.:( By the way, this is my first time compiling a kernel.

Thanks.

voxsim
January 18th, 2010, 09:41 PM
chenxiaolong (http://ubuntuforums.org/member.php?u=724117): Did you enable your wireless drivers in the kernel?

http://ubuntuforums.org/showthread.php?t=311158

chenxiaolong
January 18th, 2010, 11:48 PM
I actually followed that thread to compile the kernel. I read that post about 10 times before I started compiling. Yet, I still missed it.


THIS#IS# NOT THE#1ST# ## ## TIME I'VE MADE
## ## ## ## ## ## ### ## #### #### ####
## ## ## ## ## ## #### ## #### #### ####
## ## ## A ## MISTAKE# ## ## ## ## ## ##
## ## ######### ## ## ## ####
## ## ## ## ## ## ## ### #### #### ####
######## ## ## ## ## ## ## #### #### ####

EDIT: Darn, the ascii didn't turn out right

hypergeek14
January 19th, 2010, 08:07 AM
2. Install the "linux-backports-modules-karmic" (newer wireless drivers from compat-wireless) package and the "b43-fwcutter" package (wireless firmware). During installation, if it asks you to fetch the firmware automatically, make sure you select yes.

Code:
sudo apt-get install linux-backports-modules-karmic b43-fwcutter

It turned out that I did in fact not have linux-backports-modules-karmic installed, but sadly installing it has not changed my situation. Any further help?

Hiro2k
January 20th, 2010, 12:41 AM
Any updates? I got as far as you guys and when the system would freeze there would be no errors in the syslog. The last line mentioned loading the firmware so I tried using the newer 4.174.64.19 firmware like it says over at http://linuxwireless.org/en/users/Drivers/b43#device_firmware, but that also failed.

I have clue what else to try :(

chenxiaolong
January 20th, 2010, 09:45 PM
I have no time to try anything. I have midterms all week.

chenxiaolong
January 21st, 2010, 08:15 PM
The b43 driver is already enabled because I'm using the Ubuntu version of ".config" to compile. I have no idea why b43 loads but won't connect. Any suggestions?

MarioHaddad
January 21st, 2010, 11:35 PM
good luck with the Midterms !!

i just reinstalled Ubuntu 9.10 ( havent even booted it yet !! :D ) i've went through all 34 pages of this thread but still have a couple of questions...

1) will your script 100% work ? ( i'll manually update the kernel to 2.6.32.3 )
2) is the b43 driver the same thing as that b43-fwcutter? ( if i apt-get that does that mean i'll have the b43 driver ? )
3) should i or should i not install the broadcom STA driver ? ( that worked on previous installs of 9.10 but without monitor mode)
4) is your 2 part script all i need to get it working ? or do i have to download something before running it other than the kernel ?
5) might it need me to hard reset my network card ? :\

THANK YOU :D

chenxiaolong
January 22nd, 2010, 01:07 AM
Thanks !!

1) No, it causes a kernel panic. I have no idea why, but I'm trying to figure it out.
2) B43 is not the same thing as b43-fwcutter. B43 is already installed on every Ubuntu installation. B43-fwcutter downloads the firmware, which tells the b43 driver how to send and receive signals from your wireless card.
3) If you want wireless internet, then yes. You can always uninstall it (or disable it).
4) Yes. The second part of my script should (in theory) get it working; but it doesn't. The driver loads fine, but it crashes after 10 seconds.
5) No. The purpose of the script was to enable PIO mode because DMA mode causes the card to need a hard reset.

I'll let you know when (yes, when, not if) I get it working :D.

chenxiaolong
January 22nd, 2010, 04:00 AM
I just compiled the lastest kernel: 2.6.32.4 --> still has the same kernel panic problem, except now it panics right after loading the module. Crap. I'm going to try to compile the latest kernel from the Lucid git tree as someone reported success in the Lucid Alpha 2 release. Other than that, I'm running out of ideas. AHHHH!!!

chenxiaolong
January 22nd, 2010, 04:43 AM
OMWG (oh my windoze god), I'm about to rip my hair out ](*,)](*,)! Compiling the Lucid kernel from its git tree didn't work either. It makes a kernel panic as soon as the module loads, just like kernel 2.6.32.4. By the way, the latest Lucid kernel in the git tree is 2.6.32.11. I've compiled a total of 17 kernels with different versions and configurations ](*,). I really have no idea of what I should do. It causes a kernel panic in every single kernel I've compiled. In the 2.6.33-RC kernels, everything was screwed up. My ATI modules, wl module, and b43 module didn't load. I'm really, really confused about why this is happening :confused::confused::confused:. Tomorrow, I'm going to try compiling the Lucid kernel debs under Lucid Alpha 2 and install them under Karmic. I could bet money that there's a very simple command or changing of a configuration file that will make this magically work :D.

Where is the great Emas80? We need your steps on compiling the kernel and your .config file for your kernel :).

Oh yeah, one more thing: After some research online, I found out that make-kpkg is not the recommended way of compiling the kernel in Karmic.

Hiro2k
January 22nd, 2010, 06:04 PM
You are using the newest firmware and fwcutter like the Linux Wireless page says to right?


You are using the b43 driver with an LP-PHY card (e.g. BCM4312)

Follow these instructions if you are using the b43 driver from linux-2.6.32 and newer or compat-wireless-2.6, or from any current GIT tree, and have a device with a low-power PHY.

Use the current Git version of b43-fwcutter.
Download, extract the b43-fwcutter tarball and build it:

git clone http://git.bu3sch.de/git/b43-tools.git
cd b43-tools/fwcutter
make
cd ..

Use version 4.174.64.19 of Broadcom's proprietary driver. (The tarball is mislabeled as "4.178.10.4", but it is actually 4.174.64.19.)
Download and extract the firmware from this driver tarball:

export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2
tar xjf broadcom-wl-4.178.10.4.tar.bz2
cd broadcom-wl-4.178.10.4/linux
sudo ../../fwcutter/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.o

Note that you must adjust the FIRMWARE_INSTALL_DIR path to your distribution. The standard place where firmware is installed to is /lib/firmware. However some distributions put firmware in a different place.

I'm 100% sure that you won't get it working without that firmware. I tried it using the precompiled 2.6.32 kernels but it never worked. I didn't try compiling my own kernel in Ubuntu and switched to gentoo for some odd reason. I managed to get it work in gentoo! :D So there is hope.

But I don't know how much of a difference there is between the two kernel sources, of it had anything to do with my success.

chenxiaolong
January 23rd, 2010, 04:58 AM
Well, I knew there was going to be a simple solution. I wasn't using that new firmware. DARN IT!!! Thanks you so much for the information :D. I'll try this tomorrow and see how it goes :D.

(I feel embarrassed when someone types a really long post or a post with really useful information and all I have to say is Thank You :))

Hiro2k
January 23rd, 2010, 06:08 AM
I thought I'd share this in case anyone ran into this little problem.

airodump-ng wlan0
ioctl(SIOCSIWMODE) failed: Device or resource busy

ARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead. Make
sure RFMON is enabled: run 'airmon-ng start wlan0 <#>'
Sysfs injection support was not found either.


First you have to use
airmon-ng start wlan0 <channel> which creates an interface called mon0. And then you use that interface for all the rest of the stuff.
airodump-ng mon0

MarioHaddad
January 23rd, 2010, 03:17 PM
hey.. is there an easy way to get kernel 2.32.X on ubuntu 9.10 running 2.31.14-17 ? i tried downloading and configuring the kernel then compiling, but i dont know what all the settings do in the config and i managed to screw up ubuntu :P so i formatted the drive and got a fresh install :D

i need 2.32 to be able to follow the guide from linux wireless right ?...

THANKS !! :popcorn:

single29
January 23rd, 2010, 03:53 PM
It is backports caused the problem. I have fixed it. type these commands in terminal you should be able to have it fixed in minutes.

root@ubuntu:apt-get remove linux-ubuntu-modules-2.6.31-17-generic \
linux-backports-modules-2.6.31-17-generic
root@ubuntu:apt-get install --reinstall bcmwl-kernel-source

Then click on your network manager icon in your launch panel you should see all available wireless services.

hypergeek14
January 25th, 2010, 02:02 PM
I can't say why, but the first script that upgrades my kernel has never worked. Can someone tell/link me how to do it manually?

chenxiaolong
January 25th, 2010, 03:03 PM
All the Ubuntu Kernel's are at the PPA: http://kernel.ubuntu.com/~kernel-ppa/mainline/

MarioHaddad
January 25th, 2010, 07:28 PM
i just had to try it................... -.-"...

got my self a DMA error :| crap :|:(

EDIT: fixed it without removing the card !!... dont know what exactly did it but here's what i did :
1) disconnected power cord and took out the battery
2) pressed the power button with the lid OPENED for 30+ seconds,
3) then pressed the wifi catcher on the left of my 1537 studio With the power button for 30 seconds.
4) kept pressing the power button like crazy on and off
5) returned the battery and wen into bios, turned off everything about wireless including that WPAN+WLAN thingy... but left bluetooth on.. save settings
6) restarted
7) turned everything in the bios about wireless back on :D

and voila !! it worked :P just a little something for whoever gets a DMA error and doesnt want to take the card out manually...

k3Rn
January 26th, 2010, 05:27 AM
omg - so frustrating, spend couple of hours again!

you scripts just don't work probperly. tryed to execute the commands by hand, but errors over errors.

i hope you once redo em properly (especially for i386 systems).

p.s.: when i did the commands from script 1 by hand (i need the i386 kernel, the script would download amd64) - i can boot into 2.6.32-02063203-generic.
but compiling the patch give me various errors. i posted the output on pastbin: http://pastebin.com/f379bf961

Ferdemidu
January 26th, 2010, 12:32 PM
Dear chenxiaolong,
I'm just a beginner with Ubuntu.
My problem is that I do not know how to follow after the Part1 of your script.
I have my machine with two operating systems, Windows 7 an Ubuntu 9.10 and I have GRUB 1 to select from each one.
My kernel is 2.6.31-17-generic-pae
I don't know how to reboot from the new 2.6.32.2 because I don't know how to put it in the GRUB
Could you help me?

Regards,

Ferdemidu


Unfortunately, only patching the b43 driver will not work because it causes a kernel panic after ten seconds. You have to compile a new kernel with the b43 module patched. But..........that's not so bad. I already patched and compiled it for you :D. I'm just trying to find a free reliable web hosting company to host an apt repository for the patched kernels. I can't afford any paid webhosts--I'm only 14. Please PM any suggestions to me (doesn't need PHP or MySQL, just hosting).


----------------------

2.6.32.3 Script

New Script for kernel 2.6.32.3 (b43_compile_2.6.32.3.sh & b43_kernel_2.6.32.3.sh): Attached below; also at my website: http://software.6368.co.cc/linux/b43/patches.

----------------------

2.6.32.2 Script

Script Update 4 (b43_kernel_2.6.32.2.sh): Backs up and renames /usr/src/linux-source-2.6.32 so there is a clean copy of the source to work with.

Script Update 3 (b43_compile_2.6.32.2.sh): Fixed error about modules.symversions.

Script Update 2 (b43_kernel_2.6.32.2.sh): Fixed kernel download part (i386 --> i686); added checking for "patch" package.

Script Update 1 (b43_compile_2.6.32.2.sh): Included the enabling of PIO mode; stupid mistake on my part.

---------------------

Great news for everyone!! The b43 driver can now be run in Ubuntu 9.10 Karmic WITHOUT any DMA errors!!:D I created a script this time that will install it for you. :D I couldn't have done it without emas80 (page 26), O-Hatta (http://www.incentivespro.com/forum/viewtopic.php?t=222), and of course, the b43 developers (http://lists.opensuse.org/opensuse-kernel/2009-12/msg00047.html).

Unfortunately, it only works on kernel 2.6.32. BUT, the first shell script that I created will automatically download and install kernel 2.6.32.2 from the Ubuntu Kernel PPA and patch the b43 driver to get rid of the DMA problems. If you compiled the 2.6.32 kernel or downloaded it from a third party source, the script also works, but you will have to run it with a parameter (see below). Also, if you already have the 2.6.32.* kernel installed from the Ubuntu Kernel PPA, you can just run the script normally. This script can be run as root or as your regular user. It uses sudo commands, so running the script as root might save you from typing your password a million times. Now lets put this paragraph into action :).

PART 1 (described above) of the script can be downloaded here (also attached to this post as b43_kernel_2.6.32.2.sh): http://software.6368.co.cc/linux/b43/patches/b43_kernel_2.6.32.2.sh

IF YOU WANT TO USE THE 2.6.32.2 KERNEL, USE "2.6.32.2" INSTEAD OF "2.6.32.3", INCLUDING LINKS.

Cases:

1. You are using a 2.6.31 kernel (default in Ubuntu 9.10 Karmic)
Run sudo sh b43_kernel_2.6.32.3.sh

2. You are running a third party or self-compiled version of kernel 2.6.32
Run sudo sh b43_kernel_2.6.32.3.sh /path/to/kernel/sources

3. You already have kernel 2.6.32 installed from the Ubuntu Kernel PPA
Run sudo sh b43_kernel_2.6.32.3.sh

Part 1 of the script makes sure that you are using the 2.6.32 kernel and patches the b43 script for compilation during part 2 of the script. If you were running kernel 2.6.31* and the script installed 2.6.32, you MUST boot into the new kernel for b43 to compile (a.k.a. just reboot). Part 2 will prepare the kernel sources to compile the b43 driver and then compile and install b43. After running the script, you will have to make sure that there IS a "b43" line in /etc/modules and make sure that there ISN"T a "blacklist b43" or "blacklist ssb" line in any of the files in "/etc/modprobe.d." You run the second script basically like the same way above.

PART 2 (described above) of the script can be downloaded here (also attached to this post as b43_compile_2.6.32.3.sh): http://software.6368.co.cc/linux/b43/patches/b43_compile_2.6.32.3.sh

Cases:

1. You are (now) running kernel 2.6.32 from the Ubuntu Kernel PPA
Run sudo sh b43_compile_2.6.32.3.sh

2. You are running a third party or self-compiled version of kernel 2.6.32
Run sudo sh b43_compile_2.6.32.3.sh /path/to/kernel/sources

Again, after running part 2 of the script, you will need to make sure that in "/etc/modules," there IS a "b43" line and that there ISN'T a "blacklist b43" or "blacklist ssb" line in any of the files in "/etc/modprobe.d."

Then reboot and enjoy your wireless!! :D

Notes:

The patch file from my website (also attached to this post) is NOT the same as the patch at http://lists.opensuse.org/opensuse-kernel/2009-12/msg00047.html, although the patch results ARE the same. Emas80 took the time to read the patch file line-by-line and patch the files manually. I downloaded his patched version of the b43 source files (page 26 of this thread) and ran the diff command between my unmodified b43 source and his patched source, saving the output to a new patch. The new patch is at http://software.6368.co.cc/linux/b43/patches/b43_kernel_2.6.32.3.patch.

If you have any doubts about my scripts, you can open them up and check it. I commented (in the script) what every command does. If there's any typos or problems please PM me so I can fix them. They should be okay; I tested the scripts on my computer.

Again, thanks to anyone who helped me with the script and the developers of the b43 driver.

----------------------------------------------------------------------------------------------
This is the new, updated information for Karmic. The steps are much easier in Karmic than in Jaunty. The steps for Jaunty are at the bottom of the post for reference and for people who still use Karmic.

1. Open up Terminal.

2. Install the "linux-backports-modules-karmic" (newer wireless drivers from compat-wireless) package and the "b43-fwcutter" package (wireless firmware). During installation, if it asks you to fetch the firmware automatically, make sure you select yes.


sudo apt-get install linux-backports-modules-karmic b43-fwcutter

3. Blacklist the ssb module.


echo "blacklist ssb" | sudo tee -a /etc/modprobe.d/blacklist-ssb.conf

4. Blacklist the wl module.


echo "blacklist wl" | sudo tee -a /etc/modprobe.d/blacklist-wl.conf

5. Reboot

6. Enjoy your wireless!!!

[COLOR=red]----------------------------------------------------------------------------------------------------------------

First of all, I want to thank lwfinger at openSUSE forums for making the b43 driver work with the 14e4:4315

The post looks verrrrry long right? Well it's not. All the commands are "copy-n-paste-able" and I recommend that you do copy and paste them so you don't make any mistakes.

So first of all, you need to download the latest compat-wireless from

You can't use wget for this because they have a hotlink prevention system. So just download the file from that website and SAVE IT TO YOUR HOME DIRECTORY.

Then open the terminal and run this command to extract the archive


tar xjf compat-wireless-2.6.tar.bz2

In order for the package to compile, you need to install the kernel headers, if not already installed. Run this in the terminal


sudo apt-get install linux-headers-$(uname -r)

Then change to the compat-wireless directory:


cd compat-wireless

Then compile the source files:


sudo make

Then install the files:


sudo make install

Then unload the drivers


sudo make unload

Then install b43-fwcutter:
VERY IMPORTANT!!: Do NOT choose yes when it asks if you want to automatically fetch the firmware.


sudo apt-get install b43-fwcutter

Download the Broadcom firmware files


wget http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2

Extract the archive


tar xjf broadcom-wl-4.150.10.5.tar.bz2

Change to the driver directory


cd broadcom-wl-4.150.10.5/driver

Install the firmware


b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta_mimo.o

Then blacklist the proprietary driver


echo blacklist wl | sudo tee -a /etc/modprobe.d/blacklist.conf

And finally..............RESTART!!!




I hope this worked for you. It worked for me.

By the way, I'm turning 14 on September 26, so wish me a happy birthday :)

chenxiaolong
January 26th, 2010, 09:23 PM
Awesome new, everyone: B43 FINALLY WORKS!!! Really, it works now. No crashes. No DMA errors. No kernel panics. And best of all, very easy to get working :D. I'll update my first post with more info after I do my homework. Time ~ 1 hour (for homework). Time ~ 20 minutes (to get working).

leorolla
January 27th, 2010, 02:09 PM
They should release Lucid Alpha2 with Wubi, so we can make disposable fresh installations to make tests all the time.

One suggestion: keep the 1st post more clear, separating what is the state-or-art and what is just history.

MarioHaddad
January 27th, 2010, 09:38 PM
awesome ! :D tried it ! works !! :D atleast the normal surfing mode.. but when i tried ifconfig down then iwconfig wlan0 mode monitor... it said something about busy.. dont really remember... is there another way im missing ?

chenxiaolong
January 27th, 2010, 09:39 PM
I'll separate the first post to make it more clear.

jensbodal
January 27th, 2010, 09:49 PM
Was going to say I ran into an error when running the 'make' command but I didn't install all 3 kernel debs.

jensbodal
January 27th, 2010, 10:13 PM
Hey I tried your directions and followed them to the T... I didn't receive any errors but after I rebooted my computer nothing changed. Wireless still not working, or even showing up for that matter. I tried the drivers from the hardware manager and the Broadcom STA shows up, but I cannot install those drivers as it just says installation of driver fails...

chenxiaolong
January 27th, 2010, 10:35 PM
You have to install all three debs (for your system architecture). The kernel-headers packages allow you to compile kernel modules.

jensbodal
January 27th, 2010, 11:11 PM
Would just installing the ubuntu 10.0.04 beta do the same thing? I had this card working with Ubuntu 8.04 like 2 years ago and was able to run Aircrack just fine, but I cannot seem to find any guide or tip that works for me.

leorolla
January 27th, 2010, 11:31 PM
....then add these lines to /etc/rc.local (thanks to Muti for this information)


modprobe -r b43
sleep 3
modprobe b43...

Mine isn't working... and I did it with a nearly fresh wubi install (though I had installed and uninstalled kernel 2.32.10 and had been playing with ndiswrapper as well).

Did you test it on fresh installs?

I will try the above trick and report tomorrow.

leorolla
January 27th, 2010, 11:34 PM
Would just installing the ubuntu 10.0.04 beta do the same thing? I had this card working with Ubuntu 8.04 like 2 years ago and was able to run Aircrack just fine, but I cannot seem to find any guide or tip that works for me.

You had this card working with a different driver... whose well-functioning Ubuntu unfortunately keeps breaking.

leorolla
January 28th, 2010, 12:14 AM
Firmware missing?

Driver was not even present:

leorolla@ubuntu:~$ sudo lshw -C network
[sudo] password for leorolla:
*-network UNCLAIMED
description: Network controller
product: BCM4312 802.11b/g
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: latency=0
resources: memory:55100000-55103fff
*-network
description: Ethernet interface
product: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller
vendor: Attansic Technology Corp.
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: b0
serial: 00:23:5a:57:47:ed
capacity: 100MB/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=ATL1E driverversion=1.0.0.7-NAPI firmware=L1e latency=0 link=no multicast=yes port=twisted pair
resources: irq:28 memory:53000000-5303ffff ioport:1000(size=128)
Then I did:

leorolla@ubuntu:~$ lsmod
Module Size Used by
binfmt_misc 6587 1
ppdev 5259 0
joydev 8736 0
snd_hda_codec_realtek 202637 1
snd_hda_intel 21530 2
snd_hda_codec 74209 2 snd_hda_codec_realtek,snd_hda_intel
iptable_filter 2271 0
ip_tables 10219 1 iptable_filter
x_tables 14299 1 ip_tables
snd_hwdep 5412 1 snd_hda_codec
snd_pcm_oss 35304 0
snd_mixer_oss 13774 1 snd_pcm_oss
snd_pcm 70894 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 1338 0
snd_seq_oss 27055 0
snd_seq_midi 4557 0
snd_rawmidi 19084 1 snd_seq_midi
snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
snd_seq 47231 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 19333 2 snd_pcm,snd_seq
snd_seq_device 5762 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
uvcvideo 57402 0
videodev 34361 1 uvcvideo
v4l1_compat 13251 2 uvcvideo,videodev
snd 54416 16 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec, snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_se q_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
lp 7124 0
led_class 2864 0
parport 32603 2 ppdev,lp
soundcore 6620 1 snd
psmouse 62398 0
serio_raw 3978 0
snd_page_alloc 7340 2 snd_hda_intel,snd_pcm
nls_iso8859_1 3249 1
nls_cp437 4919 1
vfat 8901 1
fat 47919 1 vfat
fbcon 35102 72
tileblit 2031 1 fbcon
font 7589 1 fbcon
bitblit 4675 1 fbcon
softcursor 1189 1 bitblit
i915 282634 3
drm_kms_helper 27478 1 i915
usbhid 36048 0
drm 156437 4 i915,drm_kms_helper
i2c_algo_bit 4964 1 i915
intel_agp 24246 2 i915
atl1e 28866 0
agpgart 31703 2 drm,intel_agp
video 17491 1 i915
output 1871 1 video

leorolla@ubuntu:~$ sudo modprobe b43

Now the icon at the panel says "device not ready". Doesn't see any network. New output:

leorolla@ubuntu:~$ sudo lshw -C network
*-network
description: Network controller
product: BCM4312 802.11b/g
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=b43-pci-bridge latency=0
resources: irq:16 memory:55100000-55103fff
*-network
description: Ethernet interface
product: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller
vendor: Attansic Technology Corp.
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: b0
serial: 00:23:5a:57:47:ed
capacity: 100MB/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=ATL1E driverversion=1.0.0.7-NAPI firmware=L1e latency=0 link=no multicast=yes port=twisted pair
resources: irq:28 memory:53000000-5303ffff ioport:1000(size=128)
*-network DISABLED
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:24:2b:a2:1a:e7
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=b43 driverversion=2.6.32-11-generic firmware=N/A link=yes multicast=yes wireless=IEEE 802.11bg
My suspect of firmware is due to:

leorolla@ubuntu:~$ dmesg | grep b43
[ 113.461069] b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 113.461094] b43-pci-bridge 0000:01:00.0: setting latency timer to 64
[ 113.579322] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[ 113.692501] Registered led device: b43-phy0::tx
[ 113.692623] Registered led device: b43-phy0::rx
[ 113.699752] Registered led device: b43-phy0::radio
[ 113.765173] b43 ssb0:0: firmware: requesting b43/ucode15.fw
[ 113.804840] b43 ssb0:0: firmware: requesting b43-open/ucode15.fw
[ 113.818433] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
[ 113.818459] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
[ 113.818479] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
[ 113.864130] b43 ssb0:0: firmware: requesting b43/ucode15.fw
[ 113.870022] b43 ssb0:0: firmware: requesting b43-open/ucode15.fw
[ 113.879531] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
[ 113.879546] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
[ 113.879556] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.When you tested this solution, had you previosly installed the firmwares from some other driver etc, or was it in a fresh install?

chenxiaolong
January 28th, 2010, 12:22 AM
Quote http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp:


You are using the b43 driver with an LP-PHY card (e.g. BCM4312)

Follow these instructions if you are using the b43 driver from linux-2.6.32 and newer or compat-wireless-2.6, or from any current GIT tree, and have a device with a low-power PHY.

Use the current Git version of b43-fwcutter.
Download, extract the b43-fwcutter tarball and build it:

git clone http://git.bu3sch.de/git/b43-tools.git
cd b43-tools/fwcutter
make
cd ..

Use version 4.174.64.19 of Broadcom's proprietary driver. (The tarball is mislabeled as "4.178.10.4", but it is actually 4.174.64.19.)
Download and extract the firmware from this driver tarball:

export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2
tar xjf broadcom-wl-4.178.10.4.tar.bz2
cd broadcom-wl-4.178.10.4/linux
sudo ../../fwcutter/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.o

jensbodal
January 28th, 2010, 07:15 AM
You had this card working with a different driver... whose well-functioning Ubuntu unfortunately keeps breaking.

I'm not sure what you mean by this but I read in another post that someone had used the latest Ubuntu install and said that the driver works fine in there. Are you saying that the Ubuntu versions keep changing/breaking the driver?

Do you think just clearing my current install and trying 10.04 will do anything?

leorolla
January 28th, 2010, 12:57 PM
I'm not sure what you mean by this but I read in another post that someone had used the latest Ubuntu install and said that the driver works fine in there. Are you saying that the Ubuntu versions keep changing/breaking the driver?

Yes. Ubuntu autmoatically loads the correct proprietary driver and you wireless just works out of the box. This was true in 8.04, 8.10, 9.04 but suddenly not quint with 9.10.
A few months ago you had to update your installation (with wired connection of course) to get it working. Since a few weeks ago even that was again not working. I don't know if has been fixed again, I'm getting sick of it.


Do you think just clearing my current install and trying 10.04 will do anything?

Maybe. But I guess it is safer to install it to a USB stick, just to check if it works.


Quote http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp (http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp:)

You are using the b43 driver with an LP-PHY card (e.g. BCM4312)

Follow these instructions if you are using the b43 driver from linux-2.6.32 and newer or compat-wireless-2.6, or from any current GIT tree, and have a device with a low-power PHY.

Use the current Git version of b43-fwcutter.
Download, extract the b43-fwcutter tarball and build it:

git clone http://git.bu3sch.de/git/b43-tools.git
cd b43-tools/fwcutter
make
cd ..

Use version 4.174.64.19 of Broadcom's proprietary driver. (The tarball is mislabeled as "4.178.10.4", but it is actually 4.174.64.19.)
Download and extract the firmware from this driver tarball:

export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2
tar xjf broadcom-wl-4.178.10.4.tar.bz2
cd broadcom-wl-4.178.10.4/linux
sudo ../../fwcutter/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.o

So, in summary, you mean something like this?


cd ~/Desktop
wget http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-image-2.6.32-11-generic_2.6.32-11.15_i386.deb
wget http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-11-generic_2.6.32-11.15_i386.deb
wget http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-11_2.6.32-11.15_all.deb
sudo dpkg -i linux*2.6.*.deb
sudo reboot
cd ~/Desktop
git clone http://git.bu3sch.de/git/b43-tools.git
cd b43-tools/fwcutter
make
cd ..
export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2
tar xjf broadcom-wl-4.178.10.4.tar.bz2
cd broadcom-wl-4.178.10.4/linux
sudo ../../fwcutter/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.o
sudo reboot
cd ~/Desktop
wget http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2010-01-26.tar.bz2
tar jxvf compat-wireless-2010-01-26.tar.bz2
cd compat-wireless-2010-01-26
make
sudo make install
sudo make unload
sudo depmod
sudo depmod -a
echo "options b43 pio=1" | sudo tee -a "/etc/modprobe.d/b43-thingy.conf"
sudo reboot

leorolla
January 28th, 2010, 06:05 PM
It works!!!

:KS:KS:KS:KS:KS

I also had to check for the blacklist and remove b43.

So I guess you should add:
- the firmware installation,
- un-blacklisting of b43,
- blacklisting of the other drivers,
and you will finally have your HowTo :P

DarkAngel88
January 28th, 2010, 09:13 PM
It works!!!

:KS:KS:KS:KS:KS

I also had to check for the blacklist and remove b43.

So I guess you should add:
- the firmware installation,
- un-blacklisting of b43,
- blacklisting of the other drivers,
and you will finally have your HowTo :P

What he said!! Thanks dude! Adding "modprobe b43 into /etc/rc.local" did the work for me!

chenxiaolong
January 28th, 2010, 09:50 PM
leorolla: Sure thing. Anything to make the guide easier :D.

DarkAngel88: I'm glad you got it working :D.

Also, I'll update the first post whenever a new kernel comes out and I'll let you guys know whether it works or not :P:P.

Oly0909
January 29th, 2010, 01:38 AM
OK. I'm trying to get this card working under BackTrack 4 Final Release. As soon as I start, I get this:

root@bt:~/kernel2632# sudo dpkg -i linux*2.6.*.deb

Selecting previously deselected package linux-headers-2.6.32-11.

(Reading database ... 225594 files and directories currently installed.)

Unpacking linux-headers-2.6.32-11 (from linux-headers-2.6.32-11_2.6.32-11.15_all
.deb) ...

Selecting previously deselected package linux-headers-2.6.32-11-generic.

Unpacking linux-headers-2.6.32-11-generic (from linux-headers-2.6.32-11-generic_2.6.32-11.15_i386.deb) ...

Selecting previously deselected package linux-image-2.6.32-11-generic.

Unpacking linux-image-2.6.32-11-generic (from linux-image-2.6.32-11-generic_2.6.32-11.15_i386.deb) ...

Done.

Setting up linux-headers-2.6.32-11 (2.6.32-11.15) ...

dpkg: dependency problems prevent configuration of linux-headers-2.6.32-11-generic:

linux-headers-2.6.32-11-generic depends on libc6 (>= 2.8); however:

Version of libc6 on system is 2.8~20080505-0ubuntu9.
dpkg:
error processing linux-headers-2.6.32-11-generic (--install):

dependency problems - leaving unconfigured

dpkg: dependency problems prevent configuration of linux-image-2.6.32-11-generic:

linux-image-2.6.32-11-generic depends on wireless-crda; however:

Package wireless-crda is not installed.

dpkg: error processing linux-image-2.6.32-11-generic (--install):

dependency problems - leaving unconfigured

Errors were encountered while processing:

linux-headers-2.6.32-11-generic

linux-image-2.6.32-11-generic

I'm totaly new to linux. Can somebody help me?

DarkAngel88
January 29th, 2010, 02:37 AM
chenxiaolong: good idea about the regular updates about new kernels.

Also, am I the only one with the issue that sometimes, my laptop simply won't go beyond the grub menu? I mean, it seems to hang *sometimes* just after the grub menu. A reboot sometimes fixes the issue but still, pretty weird. Hangs after the "b43-pci-bridge" thing... One solution is to blacklist b43 and use STA instead. We all know here that this is not the solution we want... now I'm wondering if anyone knows another solution to this issue.

eric512
January 29th, 2010, 10:19 AM
Finally got Kismet working on my Dell 1537 with the new tutorial on the first page.

Had to use the firmware instructions for the 4.174.64.19 firmware.

Airodump and Kismet both run with mon0,

but both die after about 2-3 mins.

I have to modprobe -r to restart the mon0.

Then it dies again after 2-3 mins.

Getting very close............

nbcmayhem
January 29th, 2010, 04:42 PM
i just got this running under fedora with current kernel. no drops so far. (dell mini 10 2nd gen)
but i only get 1mb/s and some weird jumping between transferrates from time to time.

i'll wait til 2.6.32.xx is pushed through the pipes and compile compat-wl again, maybe that's causing odd behavior.

is there a newer driver then broadcom's 4.178.10.4 ? let me know

chenxiaolong
January 29th, 2010, 09:48 PM
DarkAngel88: Well, we can't expect too much from a beta kernel :D. I rather reboot once or twice than to use the STA driver :D.

Eric512: I have that problem sometimes, but not too frequently. I'm guessing that it will be fixed in the coming kernels and compat-wireless releases.

Nbcmayhem: I have no idea why it's that slow. I know it's a wireless-g card, but I get about 1.7-2.0 megabytes per second using the b43 driver. PIO mode is also slower than DMA, but it shouldn't be half the speed :(. By the way, the 4.178.10.4 package is NOT a driver. It has the firmware files that tell the b43 driver (and wl driver) how to communicate with the Broadcom cards.

EDIT: Sorry Oly0909, I didn't see your post :(. You will have to compile your own kernel or use a kernel from the Debian experimental repository (sorry, no link. I have no idea how to access the experimental repo online). The kernels mentioned in this post are for Ubuntu ONLY.

leorolla
January 29th, 2010, 11:20 PM
I have one problem with this kernel:
I'm running on battery and it's totally unaware of it. It even thinks my laptop only runs on AC power.
Should I file a bug to the devs? How is it?

chenxiaolong
January 29th, 2010, 11:24 PM
Try booting with the option "acpi=force". If that doesn't work, then, yes, file a bug report.

leorolla
January 30th, 2010, 12:07 AM
Try booting with the option "acpi=force". If that doesn't work, then, yes, file a bug report.

I'm more newbie than you think. How do you "boot with the option xyz" ?

chenxiaolong
January 30th, 2010, 04:22 AM
That's okay, Ubuntu is "Linux for [all] humanity" :D. Anyway, when you start up the computer and get to the list of kernels (it says Grub at the top), press "E"; go to the second line (or the longest line) and add "acpi=force" to the end; then, press escape and "Control X" boot. Hopefully that will work :P.

hypergeek14
January 30th, 2010, 04:49 AM
I must say the latest update is working perfectly. Thanks all!

chenxiaolong
January 31st, 2010, 03:26 AM
Well, I really didn't do much except creating a HowTo article. We really should be thanking Larry Finger at the OpenSUSE forums for making the b43 code :D.

nbcmayhem
February 2nd, 2010, 01:04 AM
still only 1mbit transferrate and i can't connect to ttls networks. bummer.

chenxiaolong
February 2nd, 2010, 01:08 AM
The 1MB transfer rate will remain until the developers fix DMA mode for this card or improve PIO mode. I have no idea what TTLS is, so I can't help you there :D.

nbcmayhem
February 2nd, 2010, 01:52 PM
http://en.wikipedia.org/wiki/Extensible_Authentication_Protocol#EAP-TTLS

leorolla
February 2nd, 2010, 06:04 PM
I haven't tested the transfer rate.

Does it also work with 2.6.32-12?

With 2.6.32-11 I have the power problem.

chenxiaolong
February 3rd, 2010, 12:51 AM
I'll try kernel 2.6.32.12 tomorow and let you guys know.

Xantar
February 3rd, 2010, 02:20 AM
I followed this HOW TO step by step. Unfortunately my wireless card is still not working.

Any trouble shooting tips to assist me? I've tried both the ndiswrapper how to and this to no avail.

leorolla
February 3rd, 2010, 03:01 AM
I followed this HOW TO step by step. Unfortunately my wireless card is still not working.

Any trouble shooting tips to assist me? I've tried both the ndiswrapper how to and this to no avail.

Show us:


lsmod
dmesg
grep b43 /etc/modprobe.d/*
grep wl /etc/modprobe.d/*
grep ndiswrapper /etc/modprobe.d/*
uname -r
apt-cache policy ndiswrapper-common
apt-cache policy bcmwl-kernel-source
sudo lshw -C network

Xantar
February 3rd, 2010, 03:28 AM
lsmod

Module Size Used by
aes_i586 7268 471
aes_generic 26863 1 aes_i586
b44 25647 0
mii 4349 1 b44
ssb 37914 1 b44
ndiswrapper 185354 0
mac80211 205832 0
cfg80211 127190 1 mac80211
binfmt_misc 6587 1
ppdev 5259 0
snd_hda_codec_idt 51397 1
snd_hda_intel 21530 2
snd_hda_codec 74209 2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep 5412 1 snd_hda_codec
snd_pcm_oss 35304 0
snd_mixer_oss 13774 1 snd_pcm_oss
dm_crypt 11307 0
snd_pcm 70894 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 1338 0
snd_seq_oss 27055 0
snd_seq_midi 4557 0
snd_rawmidi 19084 1 snd_seq_midi
snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
snd_seq 47231 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 19333 2 snd_pcm,snd_seq
joydev 8736 0
nls_iso8859_1 3249 1
nls_cp437 4919 1
iptable_filter 2271 0
ip_tables 10219 1 iptable_filter
ricoh_mmc 2992 0
snd_seq_device 5762 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
x_tables 14299 1 ip_tables
snd 54416 16 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_ hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_os s,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
sdhci_pci 5470 0
vfat 8901 1
soundcore 6620 1 snd
sdhci 15462 1 sdhci_pci
snd_page_alloc 7340 2 snd_hda_intel,snd_pcm
led_class 2864 1 sdhci
psmouse 62398 0
fat 47919 1 vfat
dell_wmi 1697 0
serio_raw 3978 0
dell_laptop 6688 0
dcdbas 5550 1 dell_laptop
lp 7124 0
parport 32603 2 ppdev,lp
ohci1394 27174 0
usbhid 36048 0
video 17491 0
output 1871 1 video
ieee1394 81465 1 ohci1394
e1000e 120970 0
intel_agp 24246 0
agpgart 31703 1 intel_agp


dmesg


[ 0.564891] pci 0000:00:1c.3: PCI bridge, secondary bus 0000:0e
[ 0.564894] pci 0000:00:1c.3: IO window: 0xc000-0xcfff
[ 0.564901] pci 0000:00:1c.3: MEM window: 0xf1c00000-0xf1efffff
[ 0.564906] pci 0000:00:1c.3: PREFETCH window: 0x000000f0000000-0x000000f01fffff
[ 0.564913] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:03
[ 0.564915] pci 0000:00:1e.0: IO window: disabled
[ 0.564921] pci 0000:00:1e.0: MEM window: 0xf1b00000-0xf1bfffff
[ 0.564926] pci 0000:00:1e.0: PREFETCH window: disabled
[ 0.564945] alloc irq_desc for 16 on node -1
[ 0.564948] alloc kstat_irqs on node -1
[ 0.564955] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.564960] pci 0000:00:01.0: setting latency timer to 64
[ 0.564969] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.564975] pci 0000:00:1c.0: setting latency timer to 64
[ 0.564985] alloc irq_desc for 17 on node -1
[ 0.564987] alloc kstat_irqs on node -1
[ 0.564990] pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 0.564995] pci 0000:00:1c.1: setting latency timer to 64
[ 0.565006] alloc irq_desc for 18 on node -1
[ 0.565007] alloc kstat_irqs on node -1
[ 0.565011] pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 0.565016] pci 0000:00:1c.2: setting latency timer to 64
[ 0.565026] alloc irq_desc for 19 on node -1
[ 0.565028] alloc kstat_irqs on node -1
[ 0.565031] pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
[ 0.565037] pci 0000:00:1c.3: setting latency timer to 64
[ 0.565045] pci 0000:00:1e.0: setting latency timer to 64
[ 0.565050] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 0.565052] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
[ 0.565055] pci_bus 0000:01: resource 0 io: [0xd000-0xdfff]
[ 0.565057] pci_bus 0000:01: resource 1 mem: [0xf2000000-0xf6efffff]
[ 0.565060] pci_bus 0000:01: resource 2 pref mem [0xe0000000-0xefffffff]
[ 0.565062] pci_bus 0000:0b: resource 0 io: [0x2000-0x2fff]
[ 0.565065] pci_bus 0000:0b: resource 1 mem: [0x80000000-0x801fffff]
[ 0.565067] pci_bus 0000:0b: resource 2 pref mem [0x80200000-0x803fffff]
[ 0.565069] pci_bus 0000:0c: resource 0 io: [0x3000-0x3fff]
[ 0.565072] pci_bus 0000:0c: resource 1 mem: [0xf1f00000-0xf1ffffff]
[ 0.565074] pci_bus 0000:0c: resource 2 pref mem [0x80400000-0x805fffff]
[ 0.565077] pci_bus 0000:0d: resource 0 io: [0x4000-0x4fff]
[ 0.565079] pci_bus 0000:0d: resource 1 mem: [0x80600000-0x807fffff]
[ 0.565081] pci_bus 0000:0d: resource 2 pref mem [0x80800000-0x809fffff]
[ 0.565084] pci_bus 0000:0e: resource 0 io: [0xc000-0xcfff]
[ 0.565086] pci_bus 0000:0e: resource 1 mem: [0xf1c00000-0xf1efffff]
[ 0.565089] pci_bus 0000:0e: resource 2 pref mem [0xf0000000-0xf01fffff]
[ 0.565091] pci_bus 0000:03: resource 1 mem: [0xf1b00000-0xf1bfffff]
[ 0.565093] pci_bus 0000:03: resource 3 io: [0x00-0xffff]
[ 0.565096] pci_bus 0000:03: resource 4 mem: [0x000000-0xffffffff]
[ 0.565139] NET: Registered protocol family 2
[ 0.565242] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.565546] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.566043] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.566271] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.566273] TCP reno registered
[ 0.566339] NET: Registered protocol family 1
[ 0.566523] pci 0000:01:00.0: Boot video device
[ 0.566712] cpufreq-nforce2: No nForce2 chipset.
[ 0.566737] Scanning for low memory corruption every 60 seconds
[ 0.566840] audit: initializing netlink socket (disabled)
[ 0.566849] type=2000 audit(1265141428.563:1): initialized
[ 0.576481] highmem bounce pool size: 64 pages
[ 0.576486] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[ 0.577899] VFS: Disk quotas dquot_6.5.2
[ 0.577952] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.578480] fuse init (API version 7.13)
[ 0.578561] msgmni has been set to 1705
[ 0.578753] alg: No test for stdrng (krng)
[ 0.578763] io scheduler noop registered
[ 0.578765] io scheduler anticipatory registered
[ 0.578767] io scheduler deadline registered
[ 0.578805] io scheduler cfq registered (default)
[ 0.578943] alloc irq_desc for 24 on node -1
[ 0.578945] alloc kstat_irqs on node -1
[ 0.578953] pcieport 0000:00:01.0: irq 24 for MSI/MSI-X
[ 0.578959] pcieport 0000:00:01.0: setting latency timer to 64
[ 0.579087] alloc irq_desc for 25 on node -1
[ 0.579089] alloc kstat_irqs on node -1
[ 0.579097] pcieport 0000:00:1c.0: irq 25 for MSI/MSI-X
[ 0.579108] pcieport 0000:00:1c.0: setting latency timer to 64
[ 0.579255] alloc irq_desc for 26 on node -1
[ 0.579257] alloc kstat_irqs on node -1
[ 0.579265] pcieport 0000:00:1c.1: irq 26 for MSI/MSI-X
[ 0.579276] pcieport 0000:00:1c.1: setting latency timer to 64
[ 0.579427] alloc irq_desc for 27 on node -1
[ 0.579428] alloc kstat_irqs on node -1
[ 0.579437] pcieport 0000:00:1c.2: irq 27 for MSI/MSI-X
[ 0.579447] pcieport 0000:00:1c.2: setting latency timer to 64
[ 0.579596] alloc irq_desc for 28 on node -1
[ 0.579598] alloc kstat_irqs on node -1
[ 0.579607] pcieport 0000:00:1c.3: irq 28 for MSI/MSI-X
[ 0.579632] pcieport 0000:00:1c.3: setting latency timer to 64
[ 0.579732] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.579870] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.579990] ACPI: AC Adapter [AC] (on-line)
[ 0.580063] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
[ 0.581708] ACPI: Lid Switch [LID]
[ 0.581749] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 0.581756] ACPI: Power Button [PBTN]
[ 0.581797] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[ 0.581800] ACPI: Sleep Button [SBTN]
[ 0.582515] ACPI: SSDT 7f450999 00281 (v01 PmRef BspIst 00003000 INTL 20050624)
[ 0.582981] ACPI: SSDT 7f450df1 005C6 (v01 PmRef BspCst 00003001 INTL 20050624)
[ 0.583316] Monitor-Mwait will be used to enter C-1 state
[ 0.583339] Monitor-Mwait will be used to enter C-2 state
[ 0.583361] Monitor-Mwait will be used to enter C-3 state
[ 0.583367] Marking TSC unstable due to TSC halts in idle
[ 0.583422] processor LNXCPU:00: registered as cooling_device0
[ 0.583838] ACPI: SSDT 7f450c1a 001D7 (v01 PmRef ApIst 00003000 INTL 20050624)
[ 0.584175] ACPI: SSDT 7f4513b7 0008D (v01 PmRef ApCst 00003000 INTL 20050624)
[ 0.584498] Switching to clocksource hpet
[ 0.584826] processor LNXCPU:01: registered as cooling_device1
[ 0.616909] thermal LNXTHERM:01: registered as thermal_zone0
[ 0.616917] ACPI: Thermal Zone [THM] (51 C)
[ 0.616961] ACPI: Battery Slot [BAT0] (battery present)
[ 0.616970] ACPI: Battery Slot [BAT1] (battery absent)
[ 0.617075] isapnp: Scanning for PnP cards...
[ 0.621244] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.621396] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 0.621779] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 0.622779] brd: module loaded
[ 0.623216] loop: module loaded
[ 0.623283] input: Macintosh mouse button emulation as /devices/virtual/input/input3
[ 0.623364] ahci 0000:00:1f.2: version 3.0
[ 0.623377] ahci 0000:00:1f.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19
[ 0.623408] alloc irq_desc for 29 on node -1
[ 0.623410] alloc kstat_irqs on node -1
[ 0.623419] ahci 0000:00:1f.2: irq 29 for MSI/MSI-X
[ 0.623464] ahci: SSS flag set, parallel bus scan disabled
[ 0.623501] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0x33 impl RAID mode
[ 0.623504] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pmp pio slum part ccc ems sxs
[ 0.623510] ahci 0000:00:1f.2: setting latency timer to 64
[ 0.648052] scsi0 : ahci
[ 0.648120] scsi1 : ahci
[ 0.648169] scsi2 : ahci
[ 0.648220] scsi3 : ahci
[ 0.648270] scsi4 : ahci
[ 0.648321] scsi5 : ahci
[ 0.648735] ata1: SATA max UDMA/133 abar m2048@0xfed1c800 port 0xfed1c900 irq 29
[ 0.648739] ata2: SATA max UDMA/133 abar m2048@0xfed1c800 port 0xfed1c980 irq 29
[ 0.648741] ata3: DUMMY
[ 0.648742] ata4: DUMMY
[ 0.648745] ata5: SATA max UDMA/133 abar m2048@0xfed1c800 port 0xfed1cb00 irq 29
[ 0.648748] ata6: SATA max UDMA/133 abar m2048@0xfed1c800 port 0xfed1cb80 irq 29
[ 0.649602] Fixed MDIO Bus: probed
[ 0.649633] PPP generic driver version 2.4.2
[ 0.649664] tun: Universal TUN/TAP device driver, 1.6
[ 0.649666] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 0.649747] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.649765] alloc irq_desc for 22 on node -1
[ 0.649767] alloc kstat_irqs on node -1
[ 0.649771] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 0.649781] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[ 0.649785] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[ 0.649822] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
[ 0.649849] ehci_hcd 0000:00:1a.7: debug port 1
[ 0.653751] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[ 0.653778] ehci_hcd 0000:00:1a.7: irq 22, io mem 0xfed1c400
[ 0.672013] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 0.672090] usb usb1: configuration #1 chosen from 1 choice
[ 0.672119] hub 1-0:1.0: USB hub found
[ 0.672125] hub 1-0:1.0: 6 ports detected
[ 0.672183] alloc irq_desc for 20 on node -1
[ 0.672184] alloc kstat_irqs on node -1
[ 0.672189] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 0.672198] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 0.672201] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 0.672231] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[ 0.672256] ehci_hcd 0000:00:1d.7: debug port 1
[ 0.676153] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 0.676165] ehci_hcd 0000:00:1d.7: irq 20, io mem 0xfed1c000
[ 0.692012] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 0.692088] usb usb2: configuration #1 chosen from 1 choice
[ 0.692112] hub 2-0:1.0: USB hub found
[ 0.692117] hub 2-0:1.0: 6 ports detected
[ 0.692171] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.692187] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.692205] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 0.692211] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[ 0.692215] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 0.692242] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[ 0.692268] uhci_hcd 0000:00:1a.0: irq 20, io base 0x00006f60
[ 0.692347] usb usb3: configuration #1 chosen from 1 choice
[ 0.692372] hub 3-0:1.0: USB hub found
[ 0.692377] hub 3-0:1.0: 2 ports detected
[ 0.692420] alloc irq_desc for 21 on node -1
[ 0.692422] alloc kstat_irqs on node -1
[ 0.692426] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[ 0.692432] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[ 0.692435] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 0.692462] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[ 0.692494] uhci_hcd 0000:00:1a.1: irq 21, io base 0x00006f80
[ 0.692573] usb usb4: configuration #1 chosen from 1 choice
[ 0.692596] hub 4-0:1.0: USB hub found
[ 0.692602] hub 4-0:1.0: 2 ports detected
[ 0.692644] uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 0.692651] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[ 0.692655] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[ 0.692685] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
[ 0.692710] uhci_hcd 0000:00:1a.2: irq 22, io base 0x00006fa0
[ 0.692791] usb usb5: configuration #1 chosen from 1 choice
[ 0.692814] hub 5-0:1.0: USB hub found
[ 0.692820] hub 5-0:1.0: 2 ports detected
[ 0.692864] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 0.692870] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 0.692874] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 0.692900] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
[ 0.692926] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00006f00
[ 0.693003] usb usb6: configuration #1 chosen from 1 choice
[ 0.693026] hub 6-0:1.0: USB hub found
[ 0.693032] hub 6-0:1.0: 2 ports detected
[ 0.693077] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[ 0.693083] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 0.693087] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 0.693114] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
[ 0.693139] uhci_hcd 0000:00:1d.1: irq 21, io base 0x00006f20
[ 0.693223] usb usb7: configuration #1 chosen from 1 choice
[ 0.693246] hub 7-0:1.0: USB hub found
[ 0.693252] hub 7-0:1.0: 2 ports detected
[ 0.693296] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 0.693302] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 0.693306] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 0.693337] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
[ 0.693361] uhci_hcd 0000:00:1d.2: irq 22, io base 0x00006f40
[ 0.693441] usb usb8: configuration #1 chosen from 1 choice
[ 0.693464] hub 8-0:1.0: USB hub found
[ 0.693470] hub 8-0:1.0: 2 ports detected
[ 0.693562] PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 0.694138] i8042.c: Warning: Keylock active.
[ 0.697332] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.697337] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.697441] mice: PS/2 mouse device common for all mice
[ 0.697566] rtc_cmos 00:03: RTC can wake from S4
[ 0.697600] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 0.697629] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 0.697718] device-mapper: uevent: version 1.0.3
[ 0.697804] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[ 0.697871] device-mapper: multipath: version 1.1.0 loaded
[ 0.697874] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 0.697970] EISA: Probing bus 0 at eisa.0
[ 0.697973] EISA: Cannot allocate resource for mainboard
[ 0.697975] Cannot allocate resource for EISA slot 1
[ 0.697977] Cannot allocate resource for EISA slot 2
[ 0.697979] Cannot allocate resource for EISA slot 3
[ 0.697980] Cannot allocate resource for EISA slot 4
[ 0.697997] EISA: Detected 0 cards.
[ 0.698134] cpuidle: using governor ladder
[ 0.698241] cpuidle: using governor menu
[ 0.698662] TCP cubic registered
[ 0.698800] NET: Registered protocol family 10
[ 0.699226] lo: Disabled Privacy Extensions
[ 0.699541] NET: Registered protocol family 17
[ 0.700258] Using IPI No-Shortcut mode
[ 0.700314] PM: Resume from disk failed.
[ 0.700324] registered taskstats version 1
[ 0.701117] Magic number: 14:860:193
[ 0.701151] acpi device:1f: hash matches
[ 0.701190] rtc_cmos 00:03: setting system clock to 2010-02-02 20:10:28 UTC (1265141428)
[ 0.701193] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 0.701194] EDD information not available.
[ 0.702688] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
[ 0.973243] isapnp: No Plug & Play device found
[ 1.140069] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.141298] ata1.00: ATA-7: ST9160823ASG, 3.ADE, max UDMA/133
[ 1.141302] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 1.142842] ata1.00: configured for UDMA/133
[ 1.156192] scsi 0:0:0:0: Direct-Access ATA ST9160823ASG 3.AD PQ: 0 ANSI: 5
[ 1.156309] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.156329] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[ 1.156369] sd 0:0:0:0: [sda] Write Protect is off
[ 1.156372] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.156392] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.156508] sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
[ 1.205276] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.384063] usb 5-1: new full speed USB device using uhci_hcd and address 2
[ 1.561843] usb 5-1: configuration #0 chosen from 1 choice
[ 1.561847] usb 5-1: config 0 descriptor??
[ 1.808098] usb 6-2: new low speed USB device using uhci_hcd and address 2
[ 1.982069] usb 6-2: configuration #1 chosen from 1 choice
[ 2.044070] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.046083] ata2.00: ATAPI: MATSHITA DVD+/-RW UJ862A, 1.02, max UDMA/33
[ 2.048448] ata2.00: configured for UDMA/33
[ 2.065949] scsi 1:0:0:0: CD-ROM MATSHITA DVD+-RW UJ862A 1.02 PQ: 0 ANSI: 5
[ 2.069760] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 2.069764] Uniform CD-ROM driver Revision: 3.20
[ 2.069851] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 2.069903] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 2.388107] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.724070] ata6: SATA link down (SStatus 0 SControl 300)
[ 2.740132] Freeing unused kernel memory: 660k freed
[ 2.740483] Write protecting the kernel text: 4780k
[ 2.740534] Write protecting the kernel read-only data: 1916k
[ 2.867578] Linux agpgart interface v0.103
[ 2.891182] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[ 2.891185] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 2.891232] e1000e 0000:00:19.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 2.891241] e1000e 0000:00:19.0: setting latency timer to 64
[ 2.891337] alloc irq_desc for 30 on node -1
[ 2.891339] alloc kstat_irqs on node -1
[ 2.891351] e1000e 0000:00:19.0: irq 30 for MSI/MSI-X
[ 2.935962] b43-pci-bridge 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 2.935979] b43-pci-bridge 0000:0c:00.0: setting latency timer to 64
[ 2.976930] usbcore: registered new interface driver hiddev
[ 2.989352] ohci1394 0000:03:01.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 2.992574] input: Logitech USB Mouse as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0/input/input5
[ 2.992656] generic-usb 0003:046D:C00C.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB Mouse] on usb-0000:00:1d.0-2/input0
[ 2.992676] usbcore: registered new interface driver usbhid
[ 2.992679] usbhid: v2.6:USB HID core driver
[ 3.006051] acpi device:35: registered as cooling_device2
[ 3.007182] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:33/LNXVIDEO:00/input/input6
[ 3.007216] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
[ 3.020347] ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0
[ 3.033547] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:21:70:b8:fa:7a
[ 3.033550] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 3.033577] 0000:00:19.0: eth0: MAC: 7, PHY: 8, PBA No: 1004ff-0ff
[ 3.050063] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[f1bff800-f1bfffff] Max Packet=[2048] IR/IT contexts=[4/4]
[ 4.188268] PM: Starting manual resume from disk
[ 4.188272] PM: Resume from partition 8:5
[ 4.188274] PM: Checking hibernation image.
[ 4.188440] PM: Error -22 checking image file
[ 4.188441] PM: Resume from disk failed.
[ 4.225035] kjournald starting. Commit interval 5 seconds
[ 4.225043] EXT3-fs: mounted filesystem with writeback data mode.
[ 4.324173] ieee1394: Host added: ID:BUS[0-00:1023] GUID[444fc00012494de1]
[ 4.824367] type=1505 audit(1265141432.622:2): operation="profile_load" pid=489 name="/usr/share/gdm/guest-session/Xsession"
[ 4.831655] type=1505 audit(1265141432.626:3): operation="profile_load" pid=490 name="/sbin/dhclient3"
[ 4.832315] type=1505 audit(1265141432.630:4): operation="profile_load" pid=490 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
[ 4.832651] type=1505 audit(1265141432.630:5): operation="profile_load" pid=490 name="/usr/lib/connman/scripts/dhclient-script"
[ 4.913448] type=1505 audit(1265141432.710:6): operation="profile_load" pid=491 name="/usr/bin/evince"
[ 4.922876] type=1505 audit(1265141432.718:7): operation="profile_load" pid=491 name="/usr/bin/evince-previewer"
[ 4.928527] type=1505 audit(1265141432.726:8): operation="profile_load" pid=491 name="/usr/bin/evince-thumbnailer"
[ 4.941640] type=1505 audit(1265141432.738:9): operation="profile_load" pid=493 name="/usr/lib/cups/backend/cups-pdf"
[ 4.942381] type=1505 audit(1265141432.738:10): operation="profile_load" pid=493 name="/usr/sbin/cupsd"
[ 5.904963] Adding 4104568k swap on /dev/sda5. Priority:-1 extents:1 across:4104568k
[ 6.273162] EXT3 FS on sda3, internal journal
[ 6.398169] udev: starting version 147
[ 8.918762] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[ 8.990002] input: Dell WMI hotkeys as /devices/virtual/input/input7
[ 9.191472] lp: driver loaded but no devices found
[ 9.406085] sdhci: Secure Digital Host Controller Interface driver
[ 9.406088] sdhci: Copyright(c) Pierre Ossman
[ 9.489219] sdhci-pci 0000:03:01.1: SDHCI controller found [1180:0822] (rev 21)
[ 9.489238] sdhci-pci 0000:03:01.1: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 9.491310] Registered led device: mmc0::
[ 9.492380] mmc0: SDHCI controller on PCI [0000:03:01.1] using DMA
[ 9.492397] sdhci-pci 0000:03:01.2: SDHCI controller found [1180:0843] (rev 11)
[ 9.492411] sdhci-pci 0000:03:01.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 9.493416] mmc1: Hardware doesn't specify base clock frequency.
[ 9.493425] sdhci-pci 0000:03:01.2: PCI INT C disabled
[ 9.839343] input: DualPoint Stick as /devices/platform/i8042/serio1/input/input8
[ 9.856334] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input9
[ 10.012308] Disabling lock debugging due to kernel taint
[ 10.019566] ricoh-mmc: Ricoh MMC Controller disabling driver
[ 10.019569] ricoh-mmc: Copyright(c) Philip Langdale
[ 10.019597] ricoh-mmc: Ricoh MMC controller found at 0000:03:01.2 [1180:0843] (rev 11)
[ 10.019613] ricoh-mmc: Controller is now disabled.
[ 10.020145] ndiswrapper version 1.55 loaded (smp=yes, preempt=no)
[ 10.049081] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 10.227872] usbcore: registered new interface driver ndiswrapper
[ 10.363752] cfg80211: Calling CRDA to update world regulatory domain
[ 10.448633] b43: Unknown parameter `pio'
[ 10.601798] cfg80211: World regulatory domain updated:
[ 10.601801] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 10.601804] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 10.601806] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 10.601808] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 10.601810] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 10.601812] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 11.657036] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 11.657077] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 12.082597] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10
[ 12.181272] __ratelimit: 3 callbacks suppressed
[ 12.181275] type=1505 audit(1265159439.978:12): operation="profile_replace" pid=1087 name="/usr/share/gdm/guest-session/Xsession"
[ 12.182731] type=1505 audit(1265159439.978:13): operation="profile_replace" pid=1088 name="/sbin/dhclient3"
[ 12.183383] type=1505 audit(1265159439.978:14): operation="profile_replace" pid=1088 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
[ 12.183745] type=1505 audit(1265159439.978:15): operation="profile_replace" pid=1088 name="/usr/lib/connman/scripts/dhclient-script"
[ 12.187866] type=1505 audit(1265159439.982:16): operation="profile_replace" pid=1089 name="/usr/bin/evince"
[ 12.198073] type=1505 audit(1265159439.994:17): operation="profile_replace" pid=1089 name="/usr/bin/evince-previewer"
[ 12.204436] type=1505 audit(1265159440.002:18): operation="profile_replace" pid=1089 name="/usr/bin/evince-thumbnailer"
[ 12.214255] type=1505 audit(1265159440.010:19): operation="profile_replace" pid=1091 name="/usr/lib/cups/backend/cups-pdf"
[ 12.215042] type=1505 audit(1265159440.010:20): operation="profile_replace" pid=1091 name="/usr/sbin/cupsd"
[ 12.217577] type=1505 audit(1265159440.014:21): operation="profile_replace" pid=1092 name="/usr/sbin/tcpdump"
[ 12.977204] e1000e 0000:00:19.0: irq 30 for MSI/MSI-X
[ 13.033113] e1000e 0000:00:19.0: irq 30 for MSI/MSI-X
[ 13.033370] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 13.100011] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x00df0700
[ 13.100314] input: HDA Intel Mic at Sep Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 13.100441] input: HDA Intel Mic at Ext Right Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 13.100551] input: HDA Intel Line Out at Sep Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[ 13.100659] input: HDA Intel HP Out at Ext Right Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
[ 14.661795] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[ 14.661799] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[ 14.661987] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 15.240250] ppdev: user-space parallel port driver
[ 18.267127] dell-wmi: Unknown key ffd0 pressed
[ 18.658033] b43-pci-bridge 0000:0c:00.0: PCI INT A disabled
[ 19.577828] dell-wmi: Unknown key ffd0 pressed
[ 20.851736] dell-wmi: Unknown key ffd1 pressed
[ 21.724524] cfg80211: Calling CRDA to update world regulatory domain
[ 21.729558] cfg80211: World regulatory domain updated:
[ 21.729561] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 21.729564] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 21.729566] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 21.729569] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 21.729571] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 21.729573] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 21.772486] b43-pci-bridge 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 21.772505] b43-pci-bridge 0000:0c:00.0: setting latency timer to 64
[ 21.840301] ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0
[ 21.846105] b43: Unknown parameter `pio'
[ 21.901130] b43-pci-bridge 0000:0c:00.0: PCI INT A disabled
[ 21.902855] usbcore: deregistering interface driver ndiswrapper
[ 21.911526] ndiswrapper version 1.55 loaded (smp=yes, preempt=no)
[ 21.920386] usbcore: registered new interface driver ndiswrapper
[ 21.926726] b43-pci-bridge 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 21.926747] b43-pci-bridge 0000:0c:00.0: setting latency timer to 64
[ 21.996293] ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0
[ 24.784203] eth0: no IPv6 routers present
[ 40.165794] padlock: VIA PadLock not detected.
[ 2403.632017] CE: hpet increasing min_delta_ns to 15000 nsec
[ 2565.688296] CE: hpet increasing min_delta_ns to 22500 nsec
[ 2565.752095] CE: hpet increasing min_delta_ns to 33750 nsec
[ 3456.452215] psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 5
[ 3456.453562] psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 3456.461118] psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 - driver resynched.
[ 3457.168219] psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 5
[ 3457.169417] psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 3457.176263] psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 - driver resynched.



/etc/modprobe.d/b43-thingy.conf:options b43 pio=1
/etc/modprobe.d/blacklist:blacklist b43
/etc/modprobe.d/blacklist.conf:# replaced by b43 and ssb.



/etc/modprobe.d/blacklist:blacklist wl
/etc/modprobe.d/blacklist:blacklist wl
/etc/modprobe.d/blacklist:blacklist wl
/etc/modprobe.d/blacklist~:blacklist wl
/etc/modprobe.d/blacklist~:blacklist wl
/etc/modprobe.d/blacklist-watchdog.conf:blacklist twl4030_wdt
/etc/modprobe.d/ndiswrapper:alias wlan0 ndiswrapper
/etc/modprobe.d/wedontneednonossdrivers.conf:blacklist wl



/etc/modprobe.d/ndiswrapper:alias wlan0 ndiswrapper



2.6.32-11-generic



ndiswrapper-common:
Installed: 1.54-2ubuntu1
Candidate: 1.54-2ubuntu1
Version table:
*** 1.54-2ubuntu1 0
500 http://us.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status



ndiswrapper-common:
Installed: 1.54-2ubuntu1
Candidate: 1.54-2ubuntu1
Version table:
*** 1.54-2ubuntu1 0
500 http://us.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
xantar@xantar-laptop:~$ apt-cache policy bcmwl-kernel-source
bcmwl-kernel-source:
Installed: (none)
Candidate: 5.10.91.9+bdcom-0ubuntu4
Version table:
5.10.91.9+bdcom-0ubuntu4 0
500 http://us.archive.ubuntu.com karmic/restricted Packages




*-network
description: Ethernet interface
product: 82567LM Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 03
serial: 00:21:70:b8:fa:7a
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=1.0.2-k2 duplex=full firmware=1.7-7 ip=192.168.1.108 latency=0 link=yes multicast=yes port=twisted pair speed=100MB/s
resources: irq:30 memory:f6fe0000-f6ffffff memory:f6fdb000-f6fdbfff ioport:efe0(size=32)
*-network
description: Network controller
product: BCM4312 802.11b/g
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:0c:00.0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=b43-pci-bridge latency=0
resources: irq:17 memory:f1ffc000-f1ffffff

leorolla
February 3rd, 2010, 10:42 AM
Check:

cat /etc/modules
There should be a line with "b43".

Backup:

cp /etc/modprobe.d/ndiswrapper ~
Now


sudo gedit /etc/modprobe.d/blacklistand remove the line


blacklist b43
Remove ndiswrapper:

sudo rm /etc/modprobe.d/ndiswrapper
sudo apt-get purge ndiswrapper-commonReboot and see if it works.

Xantar
February 3rd, 2010, 06:18 PM
cat /etc/modulesContains



lp
ndiswrapper
ndiswrapper
b43



sudo gedit /etc/modprobe.d/blacklistProduces



blacklist bcm43xx
blacklist wl
blackist bcm43xx
blacklist wl
blacklist bcm43xx
blacklist b43
blacklist bcm43xx
blacklist wlAren't the multiple blacklists redundant? Anyway, removed b43 and

After


sudo apt-get purge ndiswrapper-commonIt said


dpkg: warning: while removing ndiswrapper-common, directory '/etc/ndiswrapper' not empty so not removed.And afterward still nothing.

Under Network Connections the Wireless tab is completely empty (although I am right next to a wireless router + others around campus)

and the antenna next to the speaker and the mail icon in the upper right produces only the options

Wired Netork

Anything else I can try?

EDIT -

Also


cat /etc/modules

Still contains



lp
ndiswrapper
ndiswrapper
b43

chenxiaolong
February 3rd, 2010, 10:04 PM
Did you reboot after making the changes? I know it's a stupid question, but I forget to reboot all the time :D.

Also, about the 2.6.32.12 kernel: I don't have time to test it yet. I have to use Premier Pro CS4 for my world history project, so I've been using Windoze lately ](*,)](*,)](*,):D.

Xantar
February 3rd, 2010, 10:48 PM
Hehe yes I reboot after every set of instructions to check. Unfortunately still nothing :(

I have this laptop on loan from school. It had a Windows partition on it already. I added another partition because when I give the computer back I want to be able to just delete the partition and it'd be like I never had it (hopefully). I decided on Ubuntu because I wanted more practice in a Unix command line because one of my classes this semester has us SSH into our school's Solaris server. Everything went well except for the wireless card :C

chenxiaolong
February 3rd, 2010, 11:07 PM
If you need stability with your wireless connection for your classes, then I recommend that you use the Broadcom STA driver simply because:

1) Easy to install
2) No connection drops
3) Stable

The b43 driver is still in development with this wireless card and you never know if it will work or not.

From the output of "dmesg" a few posts ago, it looks like you didn't install the new kernel (2.6.32.11) and/or you didn't compile and install compat-wireless (indicated by "Unknown parameter: pio," which only occurs with the current/non-beta version of b43). Make sure you're running and booted into the latest kernel mentioned on my first post and make sure that you run "sudo depmod" & "sudo depmod -a" after you compile and install compat-wireless.

Anyway, good luck with this!

leorolla
February 3rd, 2010, 11:31 PM
cd /etc
cp -r ndiswrapper ~ # backup that you probably will never need
sudo rm -r ndiswrapper
sudo gedit modules # then remove lines containing ndiswrapper
sudo reboot # but close important programs before!
As Chen said, maybe you didn't really compile the latest compat. It takes ages to compile... Did you really do the HowTo steps one-by-one in the right order?

tcrowter
February 4th, 2010, 08:04 AM
I have a problem - I have got to the part about installing the new kernel - the links are down, but I can find a similar file in the index of that link you posted. I was scared to do ANYTHING differently (whenever I do, it goes wrong) from the instructions, so I thought I would post and ask:

Would it still work if I used different kernel image and headers to the ones linked to?

and how come the links are suddenly down - yesterday they worked for me :-s

Thanks very much for the guide -- I felt really close to getting there yesterday, but it seemed my Ubuntu installation was too cluttered with all my attempts - I decided to reinstall from scratch and JUST try your method, as it seems to work for everyone else.

leorolla
February 4th, 2010, 03:59 PM
I have a problem - I have got to the part about installing the new kernel - the links are down, but I can find a similar file in the index of that link you posted. I was scared to do ANYTHING differently (whenever I do, it goes wrong) from the instructions, so I thought I would post and ask:

Would it still work if I used different kernel image and headers to the ones linked to?

and how come the links are suddenly down - yesterday they worked for me :-s

Thanks very much for the guide -- I felt really close to getting there yesterday, but it seemed my Ubuntu installation was too cluttered with all my attempts - I decided to reinstall from scratch and JUST try your method, as it seems to work for everyone else.

Weird that 2.6.32-11 was just vaporized from repositories.

Try with these and tell us if it works.
http://mirrors.kernel.org///ubuntu/pool/main/l/linux/linux-image-2.6.32-12-generic_2.6.32-12.16_i386.deb
http://mirrors.kernel.org///ubuntu/pool/main/l/linux/linux-headers-2.6.32-12_2.6.32-12.16_all.deb
http://mirrors.kernel.org///ubuntu/pool/main/l/linux/linux-headers-2.6.32-12-generic_2.6.32-12.16_i386.deb

Note that I am assuming you have an ordinary 32-bit installation.

tcrowter
February 4th, 2010, 07:34 PM
Weird that 2.6.32-11 was just vaporized from repositories.

Try with these and tell us if it works.
http://mirrors.kernel.org///ubuntu/pool/main/l/linux/linux-image-2.6.32-12-generic_2.6.32-12.16_i386.deb
http://mirrors.kernel.org///ubuntu/pool/main/l/linux/linux-headers-2.6.32-12_2.6.32-12.16_all.deb
http://mirrors.kernel.org///ubuntu/pool/main/l/linux/linux-headers-2.6.32-12-generic_2.6.32-12.16_i386.deb

Note that I am assuming you have an ordinary 32-bit installation.

Sorry, I have a 64-bit laptop. Hate to be difficult.

Thanks for your quick reply!

leorolla
February 4th, 2010, 08:31 PM
Sorry, I have a 64-bit laptop. Hate to be difficult.

Thanks for your quick reply!

Try these then:
http://mirrors.kernel.org/ubuntu/pool/main/l/linux-meta/linux-image-generic_2.6.32.12.12_amd64.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-12-generic_2.6.32-12.16_amd64.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-12_2.6.32-12.16_all.deb

I have tested on a fresh install and it seems* to work.

Actually after installing the firmware, it seemed* to be working even without compiling and installing compat.

So if it doesn't work for you, you may want to try installing Ubuntu 32 bits just to be sure that this is not a 64-bit-specific isssue.

* the network here is refusing to give me an IP, but it is not because of my drivers.

chenxiaolong
February 4th, 2010, 09:47 PM
Ubuntu does not keep minor revisions of development (ing?) packages in the repository, which is why the 2.6.32.11 files are gone. I think it's safe to try out kernel 2.6.32.12 from leorolla's post. I'll update my first post with the links.

leorolla: The default b43 module that comes with the 2.6.32.12 works, but you will eventually get the DMA error because it's not patched with the PIO mode patch, which is included in compat-wireless.

Also, it's definitely not a 64 bit issue. I've been running 64 bit the whole time (mainly because I have 8GB of RAM and it would be really slow to run 32 bit Ubuntu :D).

tcrowter
February 4th, 2010, 10:03 PM
Try these then:
http://mirrors.kernel.org/ubuntu/pool/main/l/linux-meta/linux-image-generic_2.6.32.12.12_amd64.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-12-generic_2.6.32-12.16_amd64.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-12_2.6.32-12.16_all.deb

I have tested on a fresh install and it seems* to work.

Actually after installing the firmware, it seemed* to be working even without compiling and installing compat.

So if it doesn't work for you, you may want to try installing Ubuntu 32 bits just to be sure that this is not a 64-bit-specific isssue.

* the network here is refusing to give me an IP, but it is not because of my drivers.

I'll download those onto a fresh installation, thanks :)


Ubuntu does not keep minor revisions of development (ing?) packages in the repository, which is why the 2.6.32.11 files are gone. I think it's safe to try out kernel 2.6.32.12 from leorolla's post. I'll update my first post with the links.

leorolla: The default b43 module that comes with the 2.6.32.12 works, but you will eventually get the DMA error because it's not patched with the PIO mode patch, which is included in compat-wireless.

Also, it's definitely not a 64 bit issue. I've been running 64 bit the whole time (mainly because I have 8GB of RAM and it would be really slow to run 32 bit Ubuntu :D).

Is the DMA error serious? I'll try and follow the instructions through as well as I can - most linux instructions never seem to work for me -- there's always some technicality!

Thanks for your help, I'll get back to you when I find out the results.

chenxiaolong
February 4th, 2010, 10:59 PM
I don't know what you consider serious, but if you get that error (shown in dmesg), then you won't be able to use the wireless card until you physically take out the card, touch the pins, and put it back in.

tcrowter
February 4th, 2010, 11:54 PM
I don't know what you consider serious, but if you get that error (shown in dmesg), then you won't be able to use the wireless card until you physically take out the card, touch the pins, and put it back in.

I decided to follow through the instructions - I noticed my wifi was working when I installed the new kernel, but I went right ahead, and now it seems I have no wireless interfaces. Anything I can do to fix it?

chenxiaolong
February 5th, 2010, 04:09 AM
Can you post the output of "dmesg"? I need it to see what's happening when your computer boots.

leorolla
February 5th, 2010, 04:13 AM
What the heck is the DMA error?

Mine seemed to be working fine after the kernel and fwcutter.

I haven't installed compat yet.

chenxiaolong
February 5th, 2010, 04:24 AM
What the heck is the DMA error?

I have no idea.


Mine seemed to be working fine after the kernel and fwcutter.

You'll find out after downloading a large file.

tcrowter
February 5th, 2010, 07:41 AM
Can you post the output of "dmesg"? I need it to see what's happening when your computer boots.

Okay, I only just got your message(s) - after my last post I ran dmesg on a hunch, and then added those lines mentioned in the first post, and now it works!

The only problem is with the GUI I'm trying out, but that's separate from this thread.

Thanks VERY much for your help!

drumin90
February 5th, 2010, 09:26 AM
Hello, thanks for the tutorial. I can now succesfully get my BCM4312 into monitor mode but it brings up another problem. My wireless card can detect netowrks but absolutely cannot connect to any of them. Any ideas?

tcrowter
February 5th, 2010, 06:29 PM
Sorry to be difficult again, but I now have another issue, which has popped up since restarting. When I click on the network applet, the 'Enable Wireless' option is greyed out. When I 'modprobe -r b43', the option disappears. When I 'modprobe b43', the option returns, but still ghosted.

EDIT: Sorry, this turned out to be a separate issue.

Sorry for posting so much!

chenxiaolong
February 5th, 2010, 10:39 PM
tcrowter: That's okay. Do you still have the problem? I you do, can you start a new thread on it, so I can help you there?

drumin90: Can you post the output of "uname -a"? That command tells me what kernel you are booted into. The pre-2.6.32-11 kernels have this error.

drumin90
February 6th, 2010, 03:34 AM
Output from uname -a:


2.6.32-12-generic #16-Ubuntu SMP Wed Jan 27 18:34:19 UTC 2010 i686 GNU/Linux

The netbook can see wireless networks fine, it just cannot connect to any of them.

Thank you for the help
-drumin90

tcrowter
February 6th, 2010, 10:12 AM
tcrowter: That's okay. Do you still have the problem? I you do, can you start a new thread on it, so I can help you there?


It turned out to be related to the network manager applet, which I replaced with the Wicd Network Manager, which works okay. The only problem now is related to the GUI I'm using for aircrack, which I'm asking about on the aircrack-ng forum.

Thanks!

chenxiaolong
February 6th, 2010, 03:38 PM
drumin90: Hmmmm... I'm also running kernel 2.6.32-12 with compat-wireless-2010-02-01 with no problems. I don't know what might be causing this :(.

drumin90
February 6th, 2010, 04:58 PM
OK. Well if this helps at all, the NIC is the LP version. (14e4:14315) I assume this is ok since that is the same as in the title of this post. Also, in your tutorial, before setting up the new kernel, for installing b43-fwcutter, should I just use the standard Ubuntu command to install b43-fwcutter or should I do the option listed for the LP cards?

chenxiaolong
February 6th, 2010, 06:11 PM
You should use the option for LP cards.

drumin90
February 6th, 2010, 06:25 PM
Ok I figured. So should I only do that or should I go through the entire tutorial again and redo all of the steps?

chenxiaolong
February 6th, 2010, 07:52 PM
You can backup and remove the current firmware so you can redo the steps on installing the LP firmware. You don't need to do everything over again.

To backup the firmware


sudo rmmod b43 ssb
sudo mv /lib/firmware/b43 /lib/firmware/b43.backup

drumin90
February 6th, 2010, 07:56 PM
So basically backup the old firmware, and then follow the steps for the LP cards? And should I completely remove the current b43-fwcutter first?

chenxiaolong
February 7th, 2010, 02:47 AM
Sorry for the slow response. So, you should remove the current b43-fwcutter package, backup the firmware, and follow the firmware for LP cards.

Good luck. I hope this works out for you :D.

drumin90
February 7th, 2010, 07:21 PM
Ok thank you for all the help. I will most likely do all of this after the game today and report the results back to here. Thanks again for everything.

tcrowter
February 7th, 2010, 10:03 PM
It turned out to be related to the network manager applet, which I replaced with the Wicd Network Manager, which works okay. The only problem now is related to the GUI I'm using for aircrack, which I'm asking about on the aircrack-ng forum.

Thanks!

I hate to keep coming back and annoying you all with my problems, but here I am.

Sorry in advance.

Okay, so using the Wicd Network Manager, I can see all the APs fine. When I try and connect to my own with what is definitely the correct password, the program keeps saying it is getting an IP address. I checked with my router, and DHCP is working fine, and it does for all my other devices.

I'm now unsure what is causing this issue! Please help!

Thanks muchly in advance.

drumin90
February 7th, 2010, 10:34 PM
I hate to keep coming back and annoying you all with my problems, but here I am.

Sorry in advance.

Okay, so using the Wicd Network Manager, I can see all the APs fine. When I try and connect to my own with what is definitely the correct password, the program keeps saying it is getting an IP address. I checked with my router, and DHCP is working fine, and it does for all my other devices.

I'm now unsure what is causing this issue! Please help!

Thanks muchly in advance.


This actually sounds like the same problem I am having. BTW, reinstalling fwcutter and the firmware decribed for LP cards did not work for me. I'm still having the same issue. I try to connect to my router with the correct wpa key and it continually tries to connect. After about a minute or so, it asks me for my wpa key again. It never actually makes a connection to the router though.

If it helps at all, I tried using aircrack to see if it could establish a connection that way. It originally found the router when using airodump the first time (for finding the bssid) but could not even see the router when using airodump for dumping on the target or in aireplay.

Thanks again for all the help.

chenxiaolong
February 7th, 2010, 10:58 PM
I'll try everything out myself today to make sure that everything is working. I've been using Vista (Premier Pro CS4) for a school project and was also messing around with my parent's digital keyboard & PropellerHeads Reason 4 :D. Anyway, I'm going back to Linux now to see what exactly the problem is.

I'll post my results whether I get it working or not (hopefully it will work fine......).

leorolla
February 7th, 2010, 11:30 PM
I hate to keep coming back and annoying you all with my problems, but here I am.

Sorry in advance.

Okay, so using the Wicd Network Manager, I can see all the APs fine. When I try and connect to my own with what is definitely the correct password, the program keeps saying it is getting an IP address. I checked with my router, and DHCP is working fine, and it does for all my other devices.

I'm now unsure what is causing this issue! Please help!

Thanks muchly in advance.

Sometimes I have this problem. Once it went away just by itself.

I noticed that when it happens, it's independent of Compat, BCM, or Ndiswrapper. It is even independent of the OS, and with other OSes I don't get an IP either.

When googling, I found out that it may be a problem with our hardware:
http://www.google.com/search?q=acer+aspire+one+dhcp+problems+wireless&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:official&client=firefox-a

When you had this DHCP problem, did you try with other releases like Jaunty, and with Windows?

drumin90
February 7th, 2010, 11:33 PM
I'll try everything out myself today to make sure that everything is working. I've been using Vista (Premier Pro CS4) for a school project and was also messing around with my parent's digital keyboard & PropellerHeads Reason 4 :D. Anyway, I'm going back to Linux now to see what exactly the problem is.

I'll post my results whether I get it working or not (hopefully it will work fine......).


Way off topic: Propellarhead Reason 4 is amazing. Great piece of software.

Back on topic, as far as I know, this wireless card works fine in windows.

chenxiaolong
February 8th, 2010, 03:25 AM
BAD NEWS: B43 won't connect in either 2.6.32-12.17 or 2.6.33-RC7.

BUT, I found some interesting info from dmesg:


[ 1526.290758] wlan0: direct probe to 00:21:27:46:94:da (try 1)
[ 1526.500123] wlan0: direct probe to 00:21:27:46:94:da (try 2)
[ 1526.690129] wlan0: direct probe to 00:21:27:46:94:da (try 3)
[ 1526.890156] wlan0: direct probe to 00:21:27:46:94:da timed out
[ 1537.723698] wlan0: direct probe to 00:21:27:46:94:da (try 1)
[ 1537.728609] wlan0: direct probe responded
[ 1537.760066] wlan0: authenticate with 00:21:27:46:94:da (try 1)
[ 1537.762726] wlan0: authenticated
[ 1537.762986] wlan0: associate with 00:21:27:46:94:da (try 1)
[ 1537.766827] wlan0: RX AssocResp from 00:21:27:46:94:da (capab=0x431 status=0 aid=1)
[ 1537.766833] wlan0: associated
[ 1537.769207] cfg80211: Calling CRDA for country: US
[ 1537.773261] cfg80211: Received country IE:
[ 1537.773266] cfg80211: Regulatory domain: US
[ 1537.773269] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1537.773274] (2402000 KHz - 2472000 KHz @ 40000 KHz), (10000 mBi, 2700 mBm)
[ 1537.773277] cfg80211: CRDA thinks this should applied:
[ 1537.773280] cfg80211: Regulatory domain: US
[ 1537.773282] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1537.773287] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 1537.773291] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 1537.773295] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1537.773300] (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1537.773304] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 1537.773307] cfg80211: We intersect both of these and get:
[ 1537.773309] cfg80211: Regulatory domain: 98
[ 1537.773312] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1537.773316] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 1537.773323] cfg80211: Disabling channel 2467 MHz on phy0 due to Country IE
[ 1537.773327] cfg80211: Disabling channel 2472 MHz on phy0 due to Country IE
[ 1537.773330] cfg80211: Disabling channel 2484 MHz on phy0 due to Country IE
[ 1537.773334] cfg80211: Current regulatory domain updated by AP to: US
[ 1537.773337] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1537.773341] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 1542.540162] No probe response from AP 00:21:27:46:94:da after 500ms, disconnecting.
[ 1543.673914] wlan0: direct probe to 00:21:27:46:94:da (try 1)
[ 1543.874452] wlan0: direct probe to 00:21:27:46:94:da (try 2)
[ 1544.070049] wlan0: direct probe to 00:21:27:46:94:da (try 3)
[ 1544.270056] wlan0: direct probe to 00:21:27:46:94:da timed out
chenxiaolong@d6657k1:~$


Would cfg80211 be blocking a attempt to connect? I'll try connecting to another router and a neighbor's router and see how it goes.

chenxiaolong
February 8th, 2010, 03:33 AM
Hmm... I tried connecting to my other router after the first one failed and, of course, it failed to connect. But interestingly, dmesg didn't show any errors or debug messages. Afterwards, I tried to connect again, but neither network-manager nor "sudo iwlist scan" could show any networks ](*,).

chenxiaolong
February 8th, 2010, 03:38 AM
Could you guys try loading b43 with this: ? It seems to be working for one of my routers.


sudo rmmod b43
sudo modprobe b43 pio=1 nohwcrypt=1 verbose=3

drumin90
February 8th, 2010, 06:22 AM
Could you guys try loading b43 with this: ? It seems to be working for one of my routers.


sudo rmmod b43
sudo modprobe b43 pio=1 nohwcrypt=1 verbose=3

It didnt work for my router. Airodump was able to see the router this time however, so it seems to have gotten closer. As far as connecting, it still just times out every time.

tcrowter
February 9th, 2010, 11:06 AM
Could you guys try loading b43 with this: ? It seems to be working for one of my routers.


sudo rmmod b43
sudo modprobe b43 pio=1 nohwcrypt=1 verbose=3


I can see my AP, but when connecting it just times out when fetching an IP address.

chenxiaolong
February 9th, 2010, 10:12 PM
I wonder if it's because compat-wireless never got installed properly: .


chenxiaolong@d6657k1:/lib/modules/2.6.32-12-generic/updates$ find
./drivers
./drivers/misc
./drivers/misc/eeprom
./drivers/bluetooth
./drivers/bluetooth/btsdio.ko
./drivers/bluetooth/btusb.ko
./drivers/bluetooth/bluecard_cs.ko
./drivers/bluetooth/bt3c_cs.ko
./drivers/bluetooth/btmrvl.ko
./drivers/bluetooth/btmrvl_sdio.ko
./drivers/bluetooth/bcm203x.ko
./drivers/bluetooth/bpa10x.ko
./drivers/bluetooth/bfusb.ko
./drivers/bluetooth/btuart_cs.ko
./drivers/bluetooth/hci_vhci.ko
./drivers/bluetooth/dtl1_cs.ko
./drivers/bluetooth/hci_uart.ko
./drivers/net
./drivers/net/atl1e
./drivers/net/atl1e/atl1e.ko
./drivers/net/atlx
./drivers/net/atlx/atl1.ko
./drivers/net/atlx/atl2.ko
./drivers/net/atl1c
./drivers/net/atl1c/atl1c.ko
./dkms
./dkms/vboxnetadp.ko
./dkms/wl.ko
./dkms/vboxdrv.ko
./dkms/vboxnetflt.ko
./compat
./compat/compat_firmware_class.ko
./compat/compat.ko
./net
./net/bluetooth
./net/bluetooth/bluetooth.ko
./net/bluetooth/bnep
./net/bluetooth/bnep/bnep.ko
./net/bluetooth/hidp
./net/bluetooth/hidp/hidp.ko
./net/bluetooth/rfcomm
./net/bluetooth/rfcomm/rfcomm.ko
./net/bluetooth/sco.ko
./net/bluetooth/cmtp
./net/bluetooth/cmtp/cmtp.ko
./net/bluetooth/l2cap.ko

I'll try compiling compat-wireless, then manually copying b43 and it's dependencies to /lib/modules/2.6.32-12-generic/updates.

drumin90
February 9th, 2010, 11:17 PM
I wonder if it's because compat-wireless never got installed properly: .


chenxiaolong@d6657k1:/lib/modules/2.6.32-12-generic/updates$ find
./drivers
./drivers/misc
./drivers/misc/eeprom
./drivers/bluetooth
./drivers/bluetooth/btsdio.ko
./drivers/bluetooth/btusb.ko
./drivers/bluetooth/bluecard_cs.ko
./drivers/bluetooth/bt3c_cs.ko
./drivers/bluetooth/btmrvl.ko
./drivers/bluetooth/btmrvl_sdio.ko
./drivers/bluetooth/bcm203x.ko
./drivers/bluetooth/bpa10x.ko
./drivers/bluetooth/bfusb.ko
./drivers/bluetooth/btuart_cs.ko
./drivers/bluetooth/hci_vhci.ko
./drivers/bluetooth/dtl1_cs.ko
./drivers/bluetooth/hci_uart.ko
./drivers/net
./drivers/net/atl1e
./drivers/net/atl1e/atl1e.ko
./drivers/net/atlx
./drivers/net/atlx/atl1.ko
./drivers/net/atlx/atl2.ko
./drivers/net/atl1c
./drivers/net/atl1c/atl1c.ko
./dkms
./dkms/vboxnetadp.ko
./dkms/wl.ko
./dkms/vboxdrv.ko
./dkms/vboxnetflt.ko
./compat
./compat/compat_firmware_class.ko
./compat/compat.ko
./net
./net/bluetooth
./net/bluetooth/bluetooth.ko
./net/bluetooth/bnep
./net/bluetooth/bnep/bnep.ko
./net/bluetooth/hidp
./net/bluetooth/hidp/hidp.ko
./net/bluetooth/rfcomm
./net/bluetooth/rfcomm/rfcomm.ko
./net/bluetooth/sco.ko
./net/bluetooth/cmtp
./net/bluetooth/cmtp/cmtp.ko
./net/bluetooth/l2cap.koI'll try compiling compat-wireless, then manually copying b43 and it's dependencies to /lib/modules/2.6.32-12-generic/updates.


When I was compiling compat wireless, there were a few warnings that came up. It would list them as it was compiling. If I remember correctly, none of them had to do with a broadcom driver. I don't know if this would have anything to do with it or not.

leorolla
February 10th, 2010, 07:26 PM
2010-02-07: Not working under any kernel, except 2.6.32-11-generic, which does not exist under the Ubuntu Lucid alpha testing repo anymore

2010-02-07: Changed links for 2.6.32-12.17-generic

2010-02-03: Changed links for 2.6.32-12.16-generic; Untested

2010-01-29: Working kernel: 2.6.32-11-generic; Working compat-wireless: compat-wireless-2010-01-24


Isn't it the case of filing a regression bug?

steven6991
February 14th, 2010, 04:15 PM
Thnx man sooooooooooooooooooooooooooooooooooooooooooooooooo oooooooooooooooooooooooooooooooooooooooooooooooooo ooooo much u rock
u can't imagine how much days i've spend trying to make this driver work!
Thnx you so much keep up the good work
ubuntu

sirsycho
February 15th, 2010, 05:35 AM
I tried with the new linux-2.6.32-13 and the new compat-wireless (2010-02-13) with no luck. I followed the guide in the first post and I can see the wireless networks but continually get prompted for the password after I enter it (it never completely negotiates the connection).

I see there's a new compat-wireless out there (2010-02-14), anyone have any luck with a particular combination... that is still downloadable?

Thanks!

sirsycho
February 15th, 2010, 07:20 AM
well I got it to work once but it stops working after the reboot... here are my steps:

Install Karmic
Full Update - Reboot
Install 2.6.32-13 headers and image - Reboot
Install git-core and follow instructions here: http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp
Reboot
.
.
I can now see wireless networks and join them (do not reboot again yet)
.
.
Install Aircrack-ng via apt-get
airmon-ng start wlan0
airodump-ng mon0 (I now see networks and injection works as well)
Test as much as you like... everything seems to work
.
.
Reboot
.
.
Nothing works anymore, I can no longer see networks and dmesg shows it loading the firmware so I'm not sure what's up.

I've tried: modprobe -r b43 && sleep 3 && modprobe b43

no dice.

any ideas or help would be greatly apprecaited.

Thanks!!

[EDIT] dmesg is now showing the following errors repeatedly



[ 91.008467] b43-phy0: Controller RESET (DMA error) ...
[ 91.236385] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 96.749302] b43-phy0: Controller restarted
[ 96.749844] b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000


I am not running compat-wireless... not yet at least.

Loader009
February 16th, 2010, 02:45 AM
Hello,
I've got a Dell 1555 with the same Wireless NIC.
I'm having the same error as above.
And if I'm trying the tutorial in the first post, I get a "b43-phy0 ERROR: MAC suspend failed" (in PIO mode).

As the error looks to come in all kernels except the 2.6.32-11, so somebody should look at the changelog.
I would, but I'm very new in linux/ubuntu and wouldn't understand or find anything.
Greetings

PS: Sorry for bad english
<--- german

chenxiaolong
February 16th, 2010, 09:53 PM
sirsycho: You have to use compat-wireless for the card to work. The DMA error occurs when the card is in DMA mode, which crashes the card under high bandwidth. The compat-wireless b43 driver supports PIO mode, which doesn't have this error. BUT, the b43 driver from compat-wireless is not working with the newest kernel :(.

Loader009: I get the same error with one of my routers too (in PIO mode). I'll take a look at the kernel changelog to see what happened after kernel 2.6.32-11. The latest compat-wireless package isn't even compiling anymore :(. (By the way, you're english is great!)

I'm going to try compiling the latest compat-wireless (2010-02-16) on development kernel 2.6.32-13 and stable kernel 2.6.32.8 and see how it goes.

sirsycho
February 17th, 2010, 12:02 AM
chenxiaolong: Thanks for the reply. I actually compiled compat-wireless and I don't get the errors anymore but it never completes the handshake, I get prompted for the WPA2-AES password but it just times out. That was with the 2.6.32-13 and compat-wireless 2010-2-14. Oh and for what it's worth... I'm using an Airport Extreme router.

Let us know how your testing goes. If I get a chance I'll try as well tonight.

sirsycho
February 17th, 2010, 05:41 AM
well I tried compat-wireless (2010-02-16) and it wouldn't compile so I switched to (2010-02-15) and still no dice.

I'm still getting the:



[ 48.772629] wlan0: authenticate with 00:25:bc:XX:XX:XX (try 1)
[ 48.972052] wlan0: authenticate with 00:25:bc:XX:XX:XX (try 2)
[ 49.172105] wlan0: authenticate with 00:25:bc:XX:XX:XX (try 3)
[ 49.372102] wlan0: authentication with 00:25:XX:XX:XX:XX timed out


:(

I'm still running 2.6.32-13.

rlelliott
February 17th, 2010, 05:35 PM
Hi guys,

I'm running the fully updated 2.6.32-13 lucid kernel on a Lenovo G550 (4312 14e4:4315) with b43 installed. This card and driver together create a pretty nasty mon mode aircracker, but i am also getting the:



[ 48.772629] wlan0: authenticate with 00:25:bc:XX:XX:XX (try 1)
[ 48.972052] wlan0: authenticate with 00:25:bc:XX:XX:XX (try 2)
[ 49.172105] wlan0: authenticate with 00:25:bc:XX:XX:XX (try 3)
[ 49.372102] wlan0: authentication with 00:25:XX:XX:XX:XX timed out


What i figured out is if you remove the crda package it will not give you this problem. Thing is when you remove that it also removes your kernel!!!! I did it for sh*ts and giggles and it worked great until reboot and no kernel was listed in grub. Does anyone know how to remove crda and still keep the new kernel????

Im using vmware to access the partition in windows 7 to download updates and what not. Had to add rootdelay=10 to make this possible. But it does work.

So for now, linux for "educational purposes". Windows 7 for internet.

ow, and this thread is epic, true story.


also, when injecting, i am able to get about 330-350pps. not bad, def not the best. but injection does work without any patching involved using the svn version of aircrack.

leorolla
February 18th, 2010, 04:37 PM
So for now, linux for "educational purposes". Windows 7 for internet.


I know exactly what this feeling is.

You can try jockey or ndiswrapper.

I am running ndiswrapper. Once I got it working it just continued working forever, no breaks.

Jockey works out of the box for Hardy and Jaunty, for Karmic you need to update/upgrade and then it works fine. But it was broken again a month ago and I don't (want to) know if it has been fixed.

For b43, I congratulate brave people who want to get it working, I even want to help, but right now I will just wait for Lucid and see how it will be then.

Loader009
February 18th, 2010, 05:58 PM
I'm running Lucid beta, w/ 2.6.32-13.18 kernel (updated today from 2.6.32-13) and it don't want to work.
I'll compile the 2.6.32-8 kernel and try it then.
Another thing. Could it be that wireless-crda make broken wifi connection?
Don't know about that package, but I know that earlier was used wireless-regdb instead of wireless-crda.
Greetz

leorolla
February 18th, 2010, 08:48 PM
Maybe you want to try this: http://ubuntuforums.org/showthread.php?t=1410259

Chen, feel free if you want to put this link at the first post, so that the poor victims of Ubuntu unstability can get their wireless working.

Loader009
February 18th, 2010, 11:14 PM
With this you can use nearly every Wireless NIC.
But with that you can't use the Monitor mode, promiscues (or something like this)...

Also I tried the STA driver and everytime the PC hangs. Now the PC hangs if gdm want to have privilegies in Xorg.

This driver can all of this (if it supports the device).
Greetz

leorolla
February 19th, 2010, 04:13 PM
With this you can use nearly every Wireless NIC.
But with that you can't use the Monitor mode, promiscues (or something like this)...

Also I tried the STA driver and everytime the PC hangs. Now the PC hangs if gdm want to have privilegies in Xorg.

This driver can all of this (if it supports the device).
Greetz

What is Monitor mode?

Some people reported not being able to find a Windows driver that works with ndiswrapper, so you can find the linked I have used.

In any case, better with ndiswrapper than having one OS for internet and another OS for other purposes :)

Loader009
February 19th, 2010, 08:56 PM
Monitor Mode -> http://en.wikipedia.org/wiki/Monitor_mode

I've compiled a custom kernel based on the official stable 2.6.32.8 kernel.
Installed and it worked.
Now the driver (b43) works too, but I want to test, if it was only one time.

The STA driver are not open source and I've got problems with it (as already told, ubuntu hangs if the driver is loaded -- found nothing in logs).

ndiswrapper is surely nice but I want "true" WLAN with all WLAN features, include Monitor Mode.
Greetz

chenxiaolong
February 19th, 2010, 09:45 PM
DARN VBULLETIN for not sending me reply emails :o:o. Anyway, I'll see if I can do something about wireless-crda. For now, if you want to remove wireless-cdra, you will have to use videbcontrol (attached to this post) and modify the dependencies line on the linux-image*.deb file. If you don't know what you're doing, then don't do this because when you remove wireless-cdra, it will remove any unmodified (with videbcontrol) kernels.

By the way, videbcontrol works with any deb file.

chenxiaolong
February 19th, 2010, 10:00 PM
I wonder what would happen if I renamed /sbin/crda to /sbin/crda2 and created a script as /sbin/crda that just echoed hi.

rlelliott
February 20th, 2010, 12:48 AM
I downloaded the newest compat-wireless tar and it seems as tho ssb and b43 are broken... :(

As far as ndis goes..... umm if i wanted to use windows drivers i would boot into Win7 and load up Commview for Wifi..

My goal here is to be able to use the b43 driver without any problems.

Crash course in writing drivers? I think so :)

Loader009
February 20th, 2010, 05:10 PM
I don't know if it is the driver or the kernel.
With official stable 2.6.32.8 kernel it works fine. (Compiled with make oldconfig then make-kpkg --initrd)

I don't know how to remove depencies, so I will not test videbcontrol.
I have very little linux knowledge.
Only some basics, some compiling things and the "build kernel" thing is not really what for me. (Because of this I used "make oldconfig")
Greetz

chenxiaolong
February 20th, 2010, 06:27 PM
Are you using PIO mode for the driver? In other words, did you compile compat-wireless and run "echo "options b43 pio=1" | sudo tee -a /etc/modprobe.d/b43.conf"? I know DMA mode works normally on the 2.6.32.* kernels, but it will eventually give the Fatal DMA Error.

Loader009
February 20th, 2010, 08:26 PM
Nope, I'm using the DMA mode.
But as I noticed, the connection is lost randomly (does such a word exist?) and won't connect.
It even doesn't scan (iwlist scan --- no scan result (or something like that)). <- Sounds like that the device crashed ->

Looks like my kernel is crap...

But it works for a few minutes...

Since my rsyslogd is taking much of CPU load, I had to turn it of.
So I haven't (yet) any usefull log.

I'm working on that rsyslog problem but it may take a while.
Greetz

rlelliott
February 20th, 2010, 08:39 PM
BCM 4312 LP Phy compat-wireless stack on (Ubuntu) Linux kernel 2.6.32.14-20 w/ monitor mode & full IPv4 connectivity write up coming soon!!! 10+ cold boots and no breakage with DMA mode!! Thanks goes out to the creator of this thread. Ow and a huge shout out to the compat-wireless team!

chenxiaolong
February 20th, 2010, 09:07 PM
rlelliott: That's great news :D! Could you test to see if the card crashes when downloading a large file, like the Ubuntu CD image? That's usually when the Fatal DMA Error occurs.

Loader009: Most log messages are shown in dmesg (command: dmesg), so you don't need rsyslogd. By the way, randomly is a word :D.

rlelliott
February 20th, 2010, 09:16 PM
Man I haven't slept in weeks and I have no idea what food is for anymore. I'll start the download and let you know what I find. Its so weird, I had to have bcmwl sta driver auto load, then unload the sta driver load the b43.. Full details soon. :)


I know that sound like a pain in the *****, but if you build launchers its no more than a few double clicks to either be in mon mode or connect to the internet. The injection rate is something like 600-750 pps with a tuned svn aircrack and airoscript compile :)


UPDATE: Downloading Ubuntu 9.10 now. If this download is successful without any fatal DMA errors i will start my write up on the process used to get this working. **crosses fingers**

rlelliott
February 20th, 2010, 10:17 PM
alright guys, Im working with a wireless broadband internet connection from sprint.... and im sharing it with my roommates also, sooooooooo it's extremely slow. I have no way to currently test a high speed 10mbit+ wifi connection.. :(

The download is going to take about 2 hrs..

chenxiaolong
February 20th, 2010, 10:29 PM
That's fine. I don't have a very high speed connection either.

rlelliott
February 20th, 2010, 11:31 PM
** UPDATE: ** 640mb downloaded without any errors of any kind. while this finishes i will go ahead and start typing the steps i took to get this working, i will leave out the 20 or more "let's format and try again's".....

Once again thanks go out to chenxiaolong for all the help and hand holding that has been done though out this 46 page thread. your the man. Also lets not forget the hard work that the compat-wireless team has done to get us this far.




If anyone would like to chat while im testing you can reach me @

yahoo: killin1a4

msn: killin1a4@hotmail.com

dmesg so far after 300mb and 3 or 4 svn downloads and compiles is...




[ 1534.932456] wlan0: direct probe to AP 00:1c:df:61:xx:xx (try 1)
[ 1535.132058] wlan0: direct probe to AP 00:1c:df:61:xx:xx (try 2)
[ 1535.134655] wlan0: direct probe responded
[ 1535.134659] wlan0: authenticate with AP 00:1c:df:61:xx:xx (try 1)
[ 1535.136629] wlan0: authenticated
[ 1535.136646] wlan0: associate with AP 00:1c:df:61:xx:xx (try 1)
[ 1535.139284] wlan0: RX AssocResp from 00:1c:df:61:xx:xx (capab=0x411 status=0 aid=3)
[ 1535.139287] wlan0: associated
[ 2157.161282] Skipping EDID probe due to cached edid
[ 2157.197199] Skipping EDID probe due to cached edid
[ 2158.172164] Skipping EDID probe due to cached edid
[ 2158.204123] Skipping EDID probe due to cached edid
[ 2158.240140] Skipping EDID probe due to cached edid
[ 2167.644154] Skipping EDID probe due to cached edid
[ 2167.676140] Skipping EDID probe due to cached edid
[ 2167.716137] Skipping EDID probe due to cached edid
[ 2168.328121] Skipping EDID probe due to cached edid
[ 2173.649090] Skipping EDID probe due to cached edid
[ 2297.984160] Skipping EDID probe due to cached edid
[ 2298.641207] Skipping EDID probe due to cached edid
[ 2298.673186] Skipping EDID probe due to cached edid
[ 2299.704155] Skipping EDID probe due to cached edid
[ 2299.736221] Skipping EDID probe due to cached edid
[ 2299.768146] Skipping EDID probe due to cached edid
[ 2305.420159] Skipping EDID probe due to cached edid
[ 2305.925366] Skipping EDID probe due to cached edid
[ 2335.729124] Skipping EDID probe due to cached edid
[ 2344.284151] Skipping EDID probe due to cached edid
[ 2345.008153] Skipping EDID probe due to cached edid
[ 3900.724033] CE: hpet increasing min_delta_ns to 15000 nsec
[ 4016.949132] Skipping EDID probe due to cached edid
[ 4021.480127] Skipping EDID probe due to cached edid
[ 4060.024128] Skipping EDID probe due to cached edid
[

northd_tech
February 21st, 2010, 12:17 AM
Hi rlelliott,

There has been a rash of recent slowness with ubuntu internet related to IPv6, OpenDNS, etc. (esp. under Karmic 9.10).

You might want to take a look at this/these threads:

http://ubuntuforums.org/showpost.php?p=8849219&postcount=4

rlelliott
February 21st, 2010, 12:39 AM
just a quick summary of what I have done to get the b43 driver and firmware working.

Downloaded last nights "nightly" build of lucid. Installed from usb.

After the system was up I proceeded to install bcmwl kernel source that came with the build under the pool dir.

after i had internet i made sure the build was fully updated and installed kernel image 2.6.32.14-20 with matching headers.

I then followed the directions to the letter to install firmware @

http://wireless.kernel.org/en/users/Drivers/b43#device_firmware_installation

under the

"You are using the b43 driver with an LP-PHY card (e.g. BCM4312)"

section.

I then downloaded the "compat-wireless-2009-10-14" tar file @

http://www.orbit-lab.org/kernel/compat-wireless-2.6/

followed the directions to build and install @

http://wireless.kernel.org/en/users/Download#Building_and_installing

after the install I ran "rmmod wl" to unbind the wl driver from my wireless card. Then ran while still in the compat dir "make unload" to unload anything else pertaining to wireless. I then ran "modprobe b43" to bind the b43 driver to my wireless nic. after that it was smooth sailing.

After the first cold boot the wl driver re-binds to the wifi's nic, so all that needs to be done is to run rmmod wl and the cd to the compat dir and run make unload. bind the b43 driver back with modprobe... this has worked flawlessly without any DMA errors or timeouts. ow and yea and your favorite wireless pen testing programs work like a charm after a quick compile of iw source (this allows programs to control your wifi nic.....

I'll post a full command for command write up soon. If you have questions about this process before i finish the write, just post them here, Im sure either me or the owner if this thread "chenxiaolong" will be able to help you.


I will not pretend to know why this works, but it does. I have even went as far as starting a download and then flipping the hard switch in the front of my Lenovo G550 off and had no hang ups at all. and yes the switch works and turns the led off.



Enjoy!

chenxiaolong
February 21st, 2010, 02:06 AM
rlelliott: Thanks for the guide :D. I'll be doing a complete system format probably tomorrow, so I'll try this out and see how it goes :D.

Again, thank you soo much for the testing.

avilella
February 21st, 2010, 02:38 PM
Great howto! I've added the link to the Lenovo G550/G450/G560 website (http://launchpad.net/~lenovo-g550).

rlelliott
February 21st, 2010, 09:26 PM
I have completed a written guide including term entries and hyper-linked download locations. It can be found @ http://docs.google.com/View?id=dhkq5635_11f3hjxdp6

If any finds any errors in the code posted, please email me @ rlelliott@gmail.com with your findings and fixes.

sirsycho
February 21st, 2010, 11:00 PM
rlelliott: I haven't looked at your full write-up yet but your abbreviated notes worked like a charm ... so far at least :). I've been up for about 3 reboots and just started downloading the current lucid build just to see.

Out of curiosity, have you tried a more recent release of compat-wireless? if so, I'm assuming there were problems? Just trying to avoid testing something you've already tried.

Thanks!!

rlelliott
February 21st, 2010, 11:08 PM
The bleeding edge builds of compat will not build without 2.6.33.xx kernel and headers.

rlelliott
February 22nd, 2010, 01:46 AM
rlelliott: I haven't looked at your full write-up yet but your abbreviated notes worked like a charm ... so far at least :). I've been up for about 3 reboots and just started downloading the current lucid build just to see.

Out of curiosity, have you tried a more recent release of compat-wireless? if so, I'm assuming there were problems? Just trying to avoid testing something you've already tried.

Thanks!!

2 weeks with no sleep and 20+ formats later.... geezz what a task this was.

sirsycho
February 23rd, 2010, 11:26 PM
2 weeks with no sleep and 20+ formats later.... geezz what a task this was.

Indeed... I had all but given up until I saw your post.

I meant to post yesterday but I did want to say that I finally got Lucid (10.04) running in triple boot on my Dell Mini 10v, though it was no trivial task with the Ubiquity installer being quite buggy in the latest daily builds (only when you do manual partitioning or want to put the bootloader on a partition).

If anyone is really interested I can write something up but for those more adventurous... I just did a normal triple boot with 9.10 Karmic and then did an install of 10.04 on top of it without reformatting or installing the bootloader.

You will have to go in and reinstall chameleon (I used Netbook Installer) and may need to repair grub afterward (YMMV with that one). Once you've reinstalled 10.04, you have to do all the steps over again for fixing your bootloaders (chameleon and windows and then linux will work from the chameleon menu).

Basic Triple boot howto here: http://www.youtube.com/user/anguish79#p/u/3/UiI-AxL4RBU

Good luck and thanks again to all who have contributed to this thread.

leorolla
February 24th, 2010, 07:58 PM
Good that it works! This is really nice news.

In the Installation Guide, is there any reason for installing bcmwl-kernel-source beforehand, other than having internet connection for the next steps?

Why can't you just uninstall wl and have b43 being loaded automatically during boot?

MarioHaddad
February 24th, 2010, 08:55 PM
thnx relliott!!!!!... btw i still have the 2.6.32-11-generic kernel files on my laptop... i can upload them if you need them !... btw where is the best place to upload them ?... rapidshare has a limit on the number of downloads right ?... (for FREE.. )

mikeioannina
February 24th, 2010, 09:11 PM
Thanks! I had the wireless working on my Acer Aspire One D250 before two months but after a kernel update it stopped working. I did 5 reformats since then, trying to fix it with many methods, but finally made it work again! I just did everything that the first post says, except i used kernel 2.6.32-14-20. I also had to do this:

then add these lines to /etc/rc.local (thanks to Muti for this information)


modprobe -r b43
sleep 3
modprobe b43

Everything works good, monitor mode works also when connected to my wlan.:D

chenxiaolong
February 24th, 2010, 09:33 PM
MarioHaddad: You can use mediafire.com. There's no download limit (as far as I know).

mikeioannina: Are you running Ubuntu Karmic or Lucid. If you are running Karmic with b43 working, I'll update my first post with the info.

mikeioannina
February 24th, 2010, 10:28 PM
mikeioannina: Are you running Ubuntu Karmic or Lucid. If you are running Karmic with b43 working, I'll update my first post with the info.

I am running Karmic with updated kernel 2.6.32-14-20 and b43 working.

The steps I followed were these. It is from the first post, slightly changed some things:

Download and install the b43 device firmware. Make sure you have the package "git-core" installed then follow the instructions at this link: http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp. It's very easy to follow. They're copy and paste commands.

First of all, download and install the new kernel 2.6.32-14-20:

i386 (32 bit)
---------------
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-image-2.6.32-14-generic_2.6.32-14.20_i386.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-14-generic_2.6.32-14.20_i386.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-14_2.6.32-14.20_all.deb


i386-PAE (32 bit with > 4 GB of RAM)
---------------------------------------------
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-image-2.6.32-14-generic-pae_2.6.32-14.20_i386.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-14-generic-pae_2.6.32-14.20_i386.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-14_2.6.32-14.20_all.deb


amd64 (64 bit)
----------------
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-image-2.6.32-14-generic_2.6.32-14.20_amd64.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-14-generic_2.6.32-14.20_amd64.deb
http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-headers-2.6.32-14_2.6.32-14.20_all.deb

Then run:


sudo dpkg -i linux*2.6.*.deb

in the folder.

Boot into the new kernel by choosing it from the GRUB boot menu.

Then, head on over here: http://linuxwireless.org/download/compat-wireless-2.6/ and download the latest compat-wireless-2010-**-**.tar.gz package to anywhere, preferably an easy to remember location. The package as of now is, compat-wireless-2010-02-24.tar.bz2. I will be using this version for the commands below. Adjust the commands below based on the file you downloaded.

Open up a Terminal and change to the directory you downloaded the file to:


cd /your/path/to/the/directory

Extract the file you downloaded:


tar jxvf compat-wireless-2010-02-24.tar.bz2

Change to the extracted directory:


cd compat-wireless-2010-02-24

Compile the drivers:


make

Install the drivers:


sudo make install

Unload the current drivers: (if you are using the Broadcom STA Driver, run "sudo rmmod wl" first)


sudo make unload

Refresh the drivers/modules for the current kernel:


sudo depmod
sudo depmod -a

Enable PIO mode:


echo "options b43 pio=1" | sudo tee -a "/etc/modprobe.d/b43-thingy.conf"

Remove the package "bcmwl-kernel-source." It's the easiest way to ensure that the b43 driver isn't blacklisted.

Blacklist the wl driver (STA driver):


echo "blacklist wl" | sudo tee "/etc/modprobe.d/blacklist.conf"
echo "blacklist ssb" | sudo tee "/etc/modprobe.d/blacklist.conf"

Add b43 to /etc/modules so it will load at bootup:


echo "b43" | sudo tee -a "/etc/modules"

After reboot, I got errors in dmesg like:


[ 11.788669] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable
[ 11.789575] b43: disagrees about version of symbol ssb_bus_may_powerdown
[ 11.789586] b43: Unknown symbol ssb_bus_may_powerdown
[ 11.790340] b43: disagrees about version of symbol ssb_dma_free_consistent
[ 11.790351] b43: Unknown symbol ssb_dma_free_consistent
[ 11.792008] b43: disagrees about version of symbol ssb_bus_suspend
[ 11.792020] b43: Unknown symbol ssb_bus_suspend
[ 11.793154] b43: disagrees about version of symbol ssb_bus_unregister
[ 11.793166] b43: Unknown symbol ssb_bus_unregister
[ 11.795081] b43: disagrees about version of symbol ssb_bus_resume
[ 11.795093] b43: Unknown symbol ssb_bus_resume
[ 11.795509] b43: disagrees about version of symbol ssb_set_devtypedata
[ 11.795520] b43: Unknown symbol ssb_set_devtypedata
[ 11.796959] b43: disagrees about version of symbol ssb_device_disable
[ 11.796972] b43: Unknown symbol ssb_device_disable
[ 11.797411] b43: disagrees about version of symbol ssb_pmu_set_ldo_voltage
[ 11.797422] b43: Unknown symbol ssb_pmu_set_ldo_voltage
[ 11.798340] b43: disagrees about version of symbol ssb_dma_alloc_consistent
[ 11.798350] b43: Unknown symbol ssb_dma_alloc_consistent
[ 11.799029] b43: disagrees about version of symbol ssb_dma_set_mask
[ 11.799042] b43: Unknown symbol ssb_dma_set_mask
[ 11.801861] b43: disagrees about version of symbol ssb_device_enable
[ 11.801874] b43: Unknown symbol ssb_device_enable
[ 11.802820] b43: disagrees about version of symbol ssb_driver_unregister
[ 11.802833] b43: Unknown symbol ssb_driver_unregister
[ 11.804095] b43: disagrees about version of symbol __ssb_driver_register
[ 11.804109] b43: Unknown symbol __ssb_driver_register
[ 11.821841] b43: Unknown symbol ssb_bus_pcmciabus_register
[ 11.822234] b43: disagrees about version of symbol ssb_bus_powerup
[ 11.822243] b43: Unknown symbol ssb_bus_powerup
[ 11.826522] b43: disagrees about version of symbol ssb_dma_translation
[ 11.826535] b43: Unknown symbol ssb_dma_translation

then added these lines to /etc/rc.local (thanks to Muti for this information)


modprobe -r b43
sleep 3
modprobe b43

And everything works ok after several reboots, the driver loads itself automatically on boot with no problems

chenxiaolong
February 24th, 2010, 11:02 PM
Thanks :D. I'll update my first post with the new info.

MarioHaddad
February 25th, 2010, 01:57 AM
i just tried this with 32.14-20 about 3 times :( this is what i did the last time : freshly installed karmic that comes with 31-14,installed bcmwl-kernel-source from karmic cd ,updated to 31-19, downloaded the firmware as instructed, upgraded to 32.14-20 PAE >= 4GB, followed instructions, but when i finish and reboot, i get nothing.. no wireless... the wifi light on my dell studio doesnt even turn on... i tried adding the 3 lines in the end..... but didnt help... when i try sudo modprobe b43 it just hangs.. its like it goes into an endless loop or something.. i can stop it with CTRL C...
and there isnt a DMA error...
so... :( what can i do ? :(

chenxiaolong
February 25th, 2010, 02:48 AM
Could you post the output of "dmesg | tail" from a separate terminal while "sudo modprobe b43" hangs?

MarioHaddad
February 25th, 2010, 10:44 AM
ok, i got it fixed, dunno why.... when i removed those three lines from rc.local everything worked...

and thats my dmesg,

[ 424.598681] evbug.c: Event. Dev: input5, Type: 0, Code: 0, Value: 0
[ 424.726884] evbug.c: Event. Dev: input5, Type: 4, Code: 4, Value: 38
[ 424.726905] evbug.c: Event. Dev: input5, Type: 1, Code: 38, Value: 1
[ 424.726915] evbug.c: Event. Dev: input5, Type: 0, Code: 0, Value: 0
[ 424.815096] evbug.c: Event. Dev: input5, Type: 4, Code: 4, Value: 38
[ 424.815117] evbug.c: Event. Dev: input5, Type: 1, Code: 38, Value: 0
[ 424.815127] evbug.c: Event. Dev: input5, Type: 0, Code: 0, Value: 0
[ 425.007393] evbug.c: Event. Dev: input5, Type: 4, Code: 4, Value: 28
[ 425.007414] evbug.c: Event. Dev: input5, Type: 1, Code: 28, Value: 1
[ 425.007424] evbug.c: Event. Dev: input5, Type: 0, Code: 0, Value: 0


it just keeps going like this.. i dont know what input5 is..

Bradicus
February 25th, 2010, 01:31 PM
I recently bought a Lenovo S10-3t, and have been having a few issues with getting some of the hardware to work, most importantly the wifi card. It is the bcm4313. It worked fine with the windows install the device came with. Does anyone have any experience with this card? I'm running the netbook remix, which is 9.10 I believe, and I'm not able to see the card. Any info would be appreciated, if I'm leaving anything out that is needed please let me know.

chenxiaolong
February 25th, 2010, 10:17 PM
MarioHaddad: Input5 is the fifth input device you plug in, such as a mouse, keyboard, or tablet.

Bradicus: You might have better luck finding help if you start a new thread, so other people can help you. I don't have this card, so I can't help you very much. Sorry :(.

MarioHaddad
February 25th, 2010, 10:38 PM
MarioHaddad: Input5 is the fifth input device you plug in, such as a mouse, keyboard, or tablet.



im on my laptop with no external devices... u know where i could find a list of connected devices with their numbering ?

chenxiaolong
February 25th, 2010, 11:09 PM
If you want to list your:

PCICMA/Expresscard/PCI cards: "lspci"
USB: "lsusb"
Network hardware: "lshw -C Network"
Input devices: "xinput --list" ---- I think :D

rlelliott
February 25th, 2010, 11:11 PM
chromium is a beast on lucid... that is all

chenxiaolong
February 26th, 2010, 12:39 AM
Way off topic, but I love chromium too.

rlelliott
February 26th, 2010, 12:51 AM
Sorry about going off topic, i just popped in to see what was going on in here.

leorolla
February 26th, 2010, 11:05 AM
Good that it works! This is really nice news.

In the Installation Guide, is there any reason for installing bcmwl-kernel-source beforehand, other than having internet connection for the next steps?

Why can't you just uninstall wl and have b43 being loaded automatically during boot?

I'm wondering if it can be installed directly, without installing first the bcmwl-kernel-source...

rlelliott
February 27th, 2010, 08:36 AM
On a Lenovo G550 R6U, after putting notebook in hibernation, when it came back up, dmesg shows that the the card is having dma errors. I powered down the machine. After sitting for about 20 seconds, powered on the machine. I rmmod wl, then modprobe b43. No DMA errors. I have not tried to load b43 without first loading the wl driver. Has anyone tested this?

dalga999
February 27th, 2010, 10:40 PM
I have been trying to make packet injection work under ubuntu 9.04, in pio mode with no success. I tried it under linux 2.6.32.14.20 and compat-wireless2-24.
Internet works, but packet injection/monitor mode only works for 5-10 seconds then it doesnt work, and connections fail. I need to do modprobe -r b43 and modprobe b43 to make the internet work again. I also upgraded to 9.10 ubuntu, but things didnt change.

I have a question? What is a DMA error, and is there a way to recover from that error?

Thanks

MarioHaddad
February 27th, 2010, 10:51 PM
I have been trying to make packet injection work under ubuntu 9.04, in pio mode with no success. I tried it under linux 2.6.32.14.20 and compat-wireless2-24.
Internet works, but packet injection/monitor mode only works for 5-10 seconds then it doesnt work, and connections fail. I need to do modprobe -r b43 and modprobe b43 to make the internet work again. I also upgraded to 9.10 ubuntu, but things didnt change.

I have a question? What is a DMA error, and is there a way to recover from that error?

Thanks


i dont know what a DMA error is, but these are the ways to recover from it:
1) a simple turn off wait 30 seconds then turn on might work ( worked for me sometimes )
2) if you're on a laptop: turn off. remove power cord, remove battery, while screen opened press the power button for 30 seconds + .... then return everything and turn on. this might work on a desktop by removing power cord and pressing the power button for 30 secs... but didnt try it ;)
3) if none works, you have to TAKE OUT the card, and make contact between all of the pins of the card.. ( using something metal of course ) that should reset it.
4) if none worked, then you're in trouble.....

hope that helps

rlelliott
February 27th, 2010, 11:36 PM
If you follow the guide I have posted, internet and injection works with out a problem using svn aircrack-ng and airoscript.

dalga999
March 2nd, 2010, 05:11 AM
I did not activate the DMA mode because I dont want to risk my laptop right now, I need to be connected to the internet. I tried the instructions on the first page, kernel 2.6.32.14 with compat-wireless and pio mode, the injection do not work on karmic: when I do airodump after airmon, it works for 5 seconds then stops working. I stopped networkmanager before doing it, but nothing changed.

Does it really matter that we use karmic, lucid or other releases? Shouldnt it depend only on the kernel, compat-wireless version and b43 ?

Loader009
March 3rd, 2010, 12:15 AM
I have now installed kubuntu karmic koala (9.10) and getting the DMA error.
I tried the tutorial on the first page and the link... nothing worked neither on lucid nor on karmic...
Any idea?
I also tried the newest and the 2009-10-14 driver, nothing... Don't work either.
Greetz

PS: kernel was/is 2.6.32-14.20

rlelliott
March 3rd, 2010, 02:46 AM
I have now installed kubuntu karmic koala (9.10) and getting the DMA error.
I tried the tutorial on the first page and the link... nothing worked neither on lucid nor on karmic...
Any idea?
I also tried the newest and the 2009-10-14 driver, nothing... Don't work either.
Greetz

PS: kernel was/is 2.6.32-14.20

-----------------------------------------------------------------




You may want to take a look at this ------->>


https://docs.google.com/ViewdocID=0ASbhSfPvr6pZZGhrcTU2MzVfMTFmM2hqeGRwNg&revision=_latest&hgd=1 (https://docs.google.com/View?docID=0ASbhSfPvr6pZZGhrcTU2MzVfMTFmM2hqeGRwNg&revision=_latest&hgd=1)

Loader009
March 3rd, 2010, 01:52 PM
Yes, with "I tried the tutorial on the first page and the link..." I ment your link.
I skipped the installation of bcmwl cause it made me problems from the first day. (The os hangs.)
I haven't tried bcmwl with my actual (kubuntu karmic koala) distribution.

I installed the build-essentials, the compiled and installed compat wireless and then (cause I forgot) I installed b43-fwcutter.
Now I'm getting all the time the DMA error.

Is it because I don't use bcmwl and doesnt rmmod it?
Maybe b43 doesn't load the NIC right and so the DMA error comes?
Greetz

m1lkman
March 5th, 2010, 11:14 AM
Got this to work on Acer Aspire One (D250) with a few hurdles involving grub hacks for booting new kernel and manually having to load the b43 driver.

Unfortunately it's got some quirks. I cant get the b43 to load at startup (as instructed by the guide ). No missing symbol errors in dmesg although I do get a missing parameter error:


m1lkman@shorepoint:~/b43/compat-wireless/compat-wireless-2010-03-04$ dmesg | grep b43
[ 2.071920] b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 2.071950] b43-pci-bridge 0000:01:00.0: setting latency timer to 64
[ 13.765167] b43: Unknown parameter `pio'
[ 14.345117] b43: Unknown parameter `pio'


Not sure what to make of that, anyway, after following the guide and rebooting I was not able to get the b43 driver to load. sudo modprobe, as correctly stated in the guide, does not work nothing.

On a hunch I tried:


sudo insmod /lib/modules/2.6.32-14-generic/kernel/drivers/net/wireless/b43/b43.ko


Couple seconds later, the wireless LED lit up, along with a wlan0 interface, yay!!!

I'm not even sure if this b43.ko was created by me or came with this install as this is a new install, anyways:

The physical radio hardware switch works as well.

"iwlist scan" and the gnome network manager applet both detect and show wireless networks.

Also I can connect to open networks ( but that's it )

Unfortunately, upon trying to connect to my local WEP network I get:


[ 3397.596848] wlan0: associate with AP 00:23:75:02:00:e0 (try 1)
[ 3397.598899] wlan0: RX AssocResp from 00:23:75:02:00:e0 (capab=0x451 status=0 aid=1)
[ 3397.598915] wlan0: associated
[ 3397.624121] wlan0: deauthenticating from 00:23:75:02:00:e0 by local choice (reason=3)


After trying to connect to my local WEP AP. I'm not sure why but if I had to guess, it would be because I need to load some b43 crypto/authentication modules as my local AP uses WEP. I have no clue as to the name of these modules so I cant test it.

If anyone knows what these modules are named that would be great as I can just manually load them and make a script, I don't care if it's hackish. Unless, of course someone has a better solution or explanation as to why the drivers may have failed to load.

chenxiaolong
March 5th, 2010, 10:34 PM
I feel bad writing a short post after you wrote such a long one :(. I also don't want to burst your bubble, but you are still using the stock b43.ko from the kernel, which doesn't support PIO mode (the point of this guide was to have b43 working in PIO mode). The b43.ko from compat-wireless will be in a subfolder in /lib/modules/2.6.32-14-generic/updates (sorry, I don't know the exact folder), not /lib/modules/2.6.32-14-generic/kernel/drivers/net/wireless/b43/b43.ko.

You can find out if it was correctly installed by running:

cd /lib/modules/2.6.32-14-generic/updates
find | grep b43.ko

Good Luck

m1lkman
March 5th, 2010, 11:42 PM
Yeah I gave it a closer look this morning and realized what I actually did. I don't know how basic something like that is but I might as well just give up after that. doh! Screw it, I'll just use my alfa card.

TironN
March 6th, 2010, 12:05 AM
I had given up on this for too long but now I'm back home (you know with good internet and a decent computer at the side), I'm ready to lend my failures to the fray!

chenxiaolong
March 6th, 2010, 03:39 AM
It's nice to see that people haven't given up :D:D. Can anybody test to see if the compat-wireless b43 driver works on kernel 2.6.33? The latest version of compat-wireless should work and the kernel can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33/. Unfortunately, I can't test because I inadvertently deleted my Ubuntu partition while I installed another distro to see if the b43 errors are only in Ubuntu kernels :(.

m1lkman
March 6th, 2010, 08:37 AM
It's nice to see that people haven't given up :D:D. Can anybody test to see if the compat-wireless b43 driver works on kernel 2.6.33? The latest version of compat-wireless should work and the kernel can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33/. Unfortunately, I can't test because I inadvertently deleted my Ubuntu partition while I installed another distro to see if the b43 errors are only in Ubuntu kernels :(.

I got an error when I tried to install that kernel, looks like its due to a broadcom module or something? btw - I'm running a clean install of UNR updated to "Linux version 2.6.31-20-generic"


m1lkman@shorepoint:~/kernel$ sudo dpkg -i linux*2.6.*.deb
Selecting previously deselected package linux-headers-2.6.33-020633.
(Reading database ... 135208 files and directories currently installed.)
Unpacking linux-headers-2.6.33-020633 (from linux-headers-2.6.33-020633_2.6.33-020633_all.deb) ...
Selecting previously deselected package linux-headers-2.6.33-020633-generic.
Unpacking linux-headers-2.6.33-020633-generic (from linux-headers-2.6.33-020633-generic_2.6.33-020633_i386.deb) ...
Selecting previously deselected package linux-image-2.6.33-020633-generic.
Unpacking linux-image-2.6.33-020633-generic (from linux-image-2.6.33-020633-generic_2.6.33-020633_i386.deb) ...
Done.
Setting up linux-headers-2.6.33-020633 (2.6.33-020633) ...
Setting up linux-headers-2.6.33-020633-generic (2.6.33-020633) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms
* Running DKMS auto installation service for kernel 2.6.33-020633-generic
* bcmwl (5.10.91.9+bdcom)... bcmwl (5.10.91.9+bdcom): Installing module.
........(bad exit status: 10)
Build failed. Installation skipped.
[fail]
run-parts: executing /etc/kernel/header_postinst.d/nvidia-common

Setting up linux-image-2.6.33-020633-generic (2.6.33-020633) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.33-020633-generic
Running postinst hook script /usr/sbin/update-grub.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.33-020633-generic
Found initrd image: /boot/initrd.img-2.6.33-020633-generic
Found linux image: /boot/vmlinuz-2.6.31-20-generic
Found initrd image: /boot/initrd.img-2.6.31-20-generic
Found linux image: /boot/vmlinuz-2.6.31-14-generic
Found initrd image: /boot/initrd.img-2.6.31-14-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu 8.10 (8.10) on /dev/sda1
done
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms
* Running DKMS auto installation service for kernel 2.6.33-020633-generic
* bcmwl (5.10.91.9+bdcom)... bcmwl (5.10.91.9+bdcom): Installing module.
.......(bad exit status: 10)
Build failed. Installation skipped.
[fail]
run-parts: executing /etc/kernel/postinst.d/nvidia-common

m1lkman@shorepoint:~/kernel$


Any ideas? Edit: n/m It looks like it worked, I was able to boot it from grub and /proc/version list it as current, should I continue to try and test it or did I screw something up?

rlelliott
March 6th, 2010, 08:49 AM
i downloaded yesterdays daily lucid build. It installed perfectly. bcmwl drivers would not install correctly for me me, but because i have already followed the steps for cutting my firmware, i already had the files on a thumb drive. The first reboot was fine with the stock b43 drivers that came with the build. After a reboot received a fatal dma error almost instantly. I then proceeded to compile the compat-wireless package i have been using with success "compat-wireless-2009-10-14". A few warning durring make but nothing serious or have to do with the b43 drivers i was after. make unload then reboot. rmmod ssb, modprobe b43..... and there we have it, full wireless capabilities. And just so everyone knows the bleeding edge compat package will not compile under 2.6.33.xx :(


But progress IS being made. I now no long have to load the wl driver at boot the unload it and load b43. I am booting strait in. Unloading ssb, and loading b43. I have rebooted 4 or 5 time and it is stiff working!