Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 34

Thread: No Wireless - Broadcom 4311

  1. #21
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: No Wireless - Broadcom 4311

    The STA driver will support your device (you can tell by typing "modinfo wl" and searching through the alias strings for one matching your card's PCI ID, which is 14e4:4311). Because nothing looks out of the ordinary to me on your IRQ table, I think trying the STA driver would be worth it.

    You should be able to deactivate b43 and put the STA driver (whose modules is named "wl" for reasons that I've never understood) in its place by typing these commands (no need for now to modify your blacklist files; you can do that later if this turns out to be a permanent solution):
    Code:
    sudo rmmod b43
    sudo rmmod ssb
    sudo rmmod wl
    sudo modprobe wl
    At this point, if you haven't received any error messages, the device just might come up and work. If not, please let me know the output at this point of:
    Code:
    dmesg | tail -25
    lshw -C Network

  2. #22
    Join Date
    Jun 2008
    Beans
    47

    Re: No Wireless - Broadcom 4311

    Mmmm....The first two went fine but the third didn't.

    sudo rmmod wl

    ERROR: Module wl does not exist in /proc/modules

    According to modinfo wl

    filename: /lib/modules/2.6.38-8-generic/kernel/net/wireless/wl.ko

    Should this file be somewhere else?

    Also, when I ran lsmod | grep b43\|ssb\|wl it returned nothing.
    Last edited by KemKev; August 16th, 2011 at 03:43 PM. Reason: Added lsmod output.

  3. #23
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: No Wireless - Broadcom 4311

    Sorry, I should have warned you about that. The error message about wl not being in /proc/modules simply means that wl wasn't loaded initially--which is fine (I only had you attempt to remove it just in case it was already loaded, since generally it needs to be unloaded and reloaded again to make it claim the hardware). So you can ignore that error and continue on with the other commands. Please try again and let me know how it goes.

    Sorry I forgot to mention that that message might have come up.

  4. #24
    Join Date
    Jun 2008
    Beans
    47

    Re: No Wireless - Broadcom 4311

    No problem at all. Should I activate the STA driver? I did do the sudo modprobe wl but nothing happened. I will post the output of the commands you requested when I get home.

    Here goes:

    Code:
    lsmod | grep wl
    wl                   2642531  0 
    lib80211               14570  1 wl
    Just wanted to confirm wl was loaded. Orange light still static.

    Code:
    dmesg | tail -25
    [  596.466756] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
    [  596.466760] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  596.466764] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
    [  596.466768] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  596.466771] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
    [  596.466775] cfg80211: 2474000 KHz - 2494000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  596.466779] cfg80211: World regulatory domain updated:
    [  596.466784] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [  596.466788] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [  596.466792] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [  596.466796] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [  596.466800] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [  596.466804] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [  599.820351] usb 1-2: USB disconnect, address 2
    [  599.824236] zd1211rw 1-2:1.0: error ioread32(CR_REG1): -19
    [  607.430430] forcedeth 0000:00:14.0: eth0: link up
    [  607.431013] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [  617.928039] eth0: no IPv6 routers present
    [ 1226.397323] wl 0000:03:00.0: can't find IRQ for PCI INT A; probably buggy MP table
    [ 1226.397336] wl 0000:03:00.0: setting latency timer to 64
    [ 1226.399672] malloc in abgphy done
    [ 1226.399800] eth%d: 5.100.82.38 driver failed with code 21
    [ 1317.206235] wl 0000:03:00.0: setting latency timer to 64
    [ 1317.208609] malloc in abgphy done
    [ 1317.208745] eth%d: 5.100.82.38 driver failed with code 21
    Code:
    sudo lshw -C Network
      *-network UNCLAIMED     
           description: Network controller
           product: BCM4311 802.11b/g WLAN
           vendor: Broadcom Corporation
           physical id: 0
           bus info: pci@0000:03:00.0
           version: 01
           width: 32 bits
           clock: 33MHz
           capabilities: pm msi pciexpress bus_master cap_list
           configuration: latency=0
           resources: memory:b6000000-b6003fff
    Last edited by KemKev; August 17th, 2011 at 12:08 AM.

  5. #25
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: No Wireless - Broadcom 4311

    "sudo modprobe wl" shouldn't produce any output unless there's an error, so no problems there. From your dmesg output it looks like the wl module was indeed inserted properly and claimed the hardware. Unfortunately, it also complains about IRQ routing problems ("[ 1226.397323] wl 0000:03:00.0: can't find IRQ for PCI INT A; probably buggy MP table"), which brings us back to where we started. I was hoping the STA driver might be able to handle the IRQ issue better than b43, but it seems not.

    Which kernel parameters were you booting with before that caused the light to turn green briefly? We didn't really dig deeper there before, but that may give the key to this whole issue. It would be useful to see the output of these commands after the light has flashed green:
    Code:
    dmesg
    lshw -C Network
    Finally, this may be a lot of work, but I'd love to see your BIOS screens myself to check whether there are any options that might be useful but that don't have obvious labels (or if there's anything that mentions something along the lines of "plug and play"). If it's not too much trouble to take some pictures of the BIOS screens, that would be great. But don't worry about this if you don't have a camera.

  6. #26
    Join Date
    Jun 2008
    Beans
    47

    Re: No Wireless - Broadcom 4311

    Thanks for the imput. I will give those a go after work later. However, I have concluded that this version of the OS and the Pavilion dv6110ca have very little in common, which is weird considering everything - wireless, integrated webcam, etc. - worked fine before this upgrade.

    As an aside, when the bluelight flashed with previous attempts, the lshw -C Network output was similar to that in my first post. I will repost later to confirm. In the meantime, would you happen to know if there is a later firmware upgrade available?
    Last edited by KemKev; August 17th, 2011 at 03:02 PM.

  7. #27
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: No Wireless - Broadcom 4311

    I doubt the b43 firmware would have anything to do with the IRQ issues, but you can find a list of supported firmware at http://linuxwireless.org/en/users/Dr...st_of_firmware You would need to use the b43-fwcutter tool to extract it and copy into the /lib/firmware directory manually. There's also reverse-engineered firmware available, which you can read about at http://lwn.net/Articles/314313/ but I'm not sure what the status of that endeavor is.

    Everything worked fine for you in an earlier Ubuntu release? I don't think I knew that. Which version did you last have installed?

  8. #28
    Join Date
    Jun 2008
    Beans
    47

    Re: No Wireless - Broadcom 4311

    Quote Originally Posted by pytheas22 View Post
    Everything worked fine for you in an earlier Ubuntu release? I don't think I knew that. Which version did you last have installed?
    Ubuntu 10.10

  9. #29
    Join Date
    Apr 2008
    Beans
    2

    Re: No Wireless - Broadcom 4311

    I'm having the same problem now, but I'm running 10.10. I've tried the recommended steps here with no luck. I'm very interested to see the resolution to this, and hopefully can use the same information to get my 4311 to work.

    My question is to see if there's a way to start from the beginning of the setup without reinstalling Ubuntu from scratch. In effect, what "should" the setup look like? I'm concerned that I've changed so much that all of the settings and drivers are radically different than how they start upon a fresh install.

    Oh, and i'm very new to Ubuntu, if you can't tell.

  10. #30
    Join Date
    Jun 2008
    Beans
    47

    Re: No Wireless - Broadcom 4311

    Quote Originally Posted by pytheas22 View Post
    "sudo modprobe wl" shouldn't produce any output unless there's an error, so no problems there. From your dmesg output it looks like the wl module was indeed inserted properly and claimed the hardware. Unfortunately, it also complains about IRQ routing problems ("[ 1226.397323] wl 0000:03:00.0: can't find IRQ for PCI INT A; probably buggy MP table"), which brings us back to where we started. I was hoping the STA driver might be able to handle the IRQ issue better than b43, but it seems not.

    Which kernel parameters were you booting with before that caused the light to turn green briefly? We didn't really dig deeper there before, but that may give the key to this whole issue. It would be useful to see the output of these commands after the light has flashed green:
    Code:
    dmesg
    lshw -C Network
    Finally, this may be a lot of work, but I'd love to see your BIOS screens myself to check whether there are any options that might be useful but that don't have obvious labels (or if there's anything that mentions something along the lines of "plug and play"). If it's not too much trouble to take some pictures of the BIOS screens, that would be great. But don't worry about this if you don't have a camera.
    When I use either the "pci=routeirq" or the "noapic" option, the blue light flashes before returning to static orange. Here are the respective outputs with the "pci=routeirq" option enabled.

    Code:
    lshw -C Network
    
    *-network               
           description: Network controller
           product: BCM4311 802.11b/g WLAN
           vendor: Broadcom Corporation
           physical id: 0
           bus info: pci@0000:03:00.0
           version: 01
           width: 32 bits
           clock: 33MHz
           capabilities: pm msi pciexpress bus_master cap_list
           configuration: driver=b43-pci-bridge latency=0
           resources: irq:0 memory:b6000000-b6003fff
      *-network:0 DISABLED
           description: Wireless interface
           physical id: 1
           logical name: wlan0
           serial: 00:1a:73:02:6b:bd
           capabilities: ethernet physical wireless
           configuration: broadcast=yes driver=b43 driverversion=2.6.38-8-generic firmware=410.2160 link=no multicast=yes wireless=IEEE 802.11bg
    Code:
    dmesg
    
    in
    [   75.808685]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [   75.808689] ata3.00: status: { DRDY }
    [   75.808692] ata3.00: failed command: READ FPDMA QUEUED
    [   75.808700] ata3.00: cmd 60/30:d0:20:a4:75/00:00:24:00:00/40 tag 26 ncq 24576 in
    [   75.808702]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [   75.808706] ata3.00: status: { DRDY }
    [   75.808709] ata3.00: failed command: READ FPDMA QUEUED
    [   75.808717] ata3.00: cmd 60/30:d8:38:a5:75/00:00:24:00:00/40 tag 27 ncq 24576 in
    [   75.808719]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [   75.808723] ata3.00: status: { DRDY }
    [   75.808726] ata3.00: failed command: READ FPDMA QUEUED
    [   75.808734] ata3.00: cmd 60/20:e0:80:a5:75/00:00:24:00:00/40 tag 28 ncq 16384 in
    [   75.808736]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [   75.808740] ata3.00: status: { DRDY }
    [   75.808743] ata3.00: failed command: READ FPDMA QUEUED
    [   75.808751] ata3.00: cmd 60/58:e8:78:a7:75/00:00:24:00:00/40 tag 29 ncq 45056 in
    [   75.808753]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [   75.808757] ata3.00: status: { DRDY }
    [   75.808761] ata3.00: failed command: READ FPDMA QUEUED
    [   75.808769] ata3.00: cmd 60/d0:f0:18:a8:75/01:00:24:00:00/40 tag 30 ncq 237568 in
    [   75.808771]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [   75.808774] ata3.00: status: { DRDY }
    [   75.808781] ata3: hard resetting link
    [   75.808785] ata3: nv: skipping hardreset on occupied port
    [   76.276031] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [   76.329096] ata3.00: configured for UDMA/133
    [   76.329102] ata3.00: device reported invalid CHS sector 0
    [   76.329106] ata3.00: device reported invalid CHS sector 0
    [   76.329110] ata3.00: device reported invalid CHS sector 0
    [   76.329113] ata3.00: device reported invalid CHS sector 0
    [   76.329117] ata3.00: device reported invalid CHS sector 0
    [   76.329120] ata3.00: device reported invalid CHS sector 0
    [   76.329124] ata3.00: device reported invalid CHS sector 0
    [   76.329127] ata3.00: device reported invalid CHS sector 0
    [   76.329131] ata3.00: device reported invalid CHS sector 0
    [   76.329134] ata3.00: device reported invalid CHS sector 0
    [   76.329138] ata3.00: device reported invalid CHS sector 0
    [   76.329141] ata3.00: device reported invalid CHS sector 0
    [   76.329145] ata3.00: device reported invalid CHS sector 0
    [   76.329148] ata3.00: device reported invalid CHS sector 0
    [   76.329152] ata3.00: device reported invalid CHS sector 0
    [   76.329155] ata3.00: device reported invalid CHS sector 0
    [   76.329159] ata3.00: device reported invalid CHS sector 0
    [   76.329162] ata3.00: device reported invalid CHS sector 0
    [   76.329166] ata3.00: device reported invalid CHS sector 0
    [   76.329169] ata3.00: device reported invalid CHS sector 0
    [   76.329173] ata3.00: device reported invalid CHS sector 0
    [   76.329176] ata3.00: device reported invalid CHS sector 0
    [   76.329179] ata3.00: device reported invalid CHS sector 0
    [   76.329183] ata3.00: device reported invalid CHS sector 0
    [   76.329186] ata3.00: device reported invalid CHS sector 0
    [   76.329190] ata3.00: device reported invalid CHS sector 0
    [   76.329193] ata3.00: device reported invalid CHS sector 0
    [   76.329197] ata3.00: device reported invalid CHS sector 0
    [   76.329200] ata3.00: device reported invalid CHS sector 0
    [   76.329204] ata3.00: device reported invalid CHS sector 0
    [   76.329207] ata3.00: device reported invalid CHS sector 0
    [   76.329249] ata3: EH complete
    [  111.804142] ata3: EH in SWNCQ mode,QC:qc_active 0x7FEE9FBF sactive 0x7FEE9FBF
    [  111.804149] ata3: SWNCQ:qc_active 0x40401916 defer_bits 0x3FAE86A9 last_issue_tag 0x1e
    [  111.804151]   dhfis 0x401916 dmafis 0x0 sdbfis 0x0
    [  111.804156] ata3: ATA_REG 0x40 ERR_REG 0x0
    [  111.804159] ata3: tag : dhfis dmafis sdbfis sacitve
    [  111.804162] ata3: tag 0x1: 1 0 0 1  
    [  111.804166] ata3: tag 0x2: 1 0 0 1  
    [  111.804169] ata3: tag 0x4: 1 0 0 1  
    [  111.804172] ata3: tag 0x8: 1 0 0 1  
    [  111.804175] ata3: tag 0xb: 1 0 0 1  
    [  111.804178] ata3: tag 0xc: 1 0 0 1  
    [  111.804182] ata3: tag 0x16: 1 0 0 1  
    [  111.804185] ata3: tag 0x1e: 0 0 0 1  
    [  111.804198] ata3.00: exception Emask 0x0 SAct 0x7fee9fbf SErr 0x0 action 0x6 frozen
    [  111.804204] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804214] ata3.00: cmd 60/a0:00:78:10:b8/00:00:24:00:00/40 tag 0 ncq 81920 in
    [  111.804216]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804220] ata3.00: status: { DRDY }
    [  111.804223] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804232] ata3.00: cmd 60/08:08:d8:00:b7/00:00:24:00:00/40 tag 1 ncq 4096 in
    [  111.804234]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804237] ata3.00: status: { DRDY }
    [  111.804241] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804249] ata3.00: cmd 60/08:10:00:32:b6/01:00:24:00:00/40 tag 2 ncq 135168 in
    [  111.804251]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804255] ata3.00: status: { DRDY }
    [  111.804258] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804266] ata3.00: cmd 60/20:18:40:12:b8/00:00:24:00:00/40 tag 3 ncq 16384 in
    [  111.804268]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804272] ata3.00: status: { DRDY }
    [  111.804275] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804283] ata3.00: cmd 60/08:20:e8:01:b7/00:00:24:00:00/40 tag 4 ncq 4096 in
    [  111.804285]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804289] ata3.00: status: { DRDY }
    [  111.804293] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804301] ata3.00: cmd 60/18:28:50:14:b8/00:00:24:00:00/40 tag 5 ncq 12288 in
    [  111.804303]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804306] ata3.00: status: { DRDY }
    [  111.804310] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804318] ata3.00: cmd 60/20:38:98:14:b8/00:00:24:00:00/40 tag 7 ncq 16384 in
    [  111.804320]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804324] ata3.00: status: { DRDY }
    [  111.804327] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804336] ata3.00: cmd 60/a0:40:28:43:b6/00:00:24:00:00/40 tag 8 ncq 81920 in
    [  111.804337]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804341] ata3.00: status: { DRDY }
    [  111.804344] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804353] ata3.00: cmd 60/48:48:00:13:b8/00:00:24:00:00/40 tag 9 ncq 36864 in
    [  111.804354]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804358] ata3.00: status: { DRDY }
    [  111.804361] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804370] ata3.00: cmd 60/18:50:38:19:b8/00:00:24:00:00/40 tag 10 ncq 12288 in
    [  111.804371]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804375] ata3.00: status: { DRDY }
    [  111.804379] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804387] ata3.00: cmd 60/b8:58:e0:2f:b6/00:00:24:00:00/40 tag 11 ncq 94208 in
    [  111.804389]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804393] ata3.00: status: { DRDY }
    [  111.804396] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804404] ata3.00: cmd 60/08:60:88:02:b7/00:00:24:00:00/40 tag 12 ncq 4096 in
    [  111.804406]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804410] ata3.00: status: { DRDY }
    [  111.804413] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804421] ata3.00: cmd 60/30:78:08:16:b8/00:00:24:00:00/40 tag 15 ncq 24576 in
    [  111.804423]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804427] ata3.00: status: { DRDY }
    [  111.804430] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804439] ata3.00: cmd 60/08:88:e0:5b:b7/00:00:24:00:00/40 tag 17 ncq 4096 in
    [  111.804442]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804446] ata3.00: status: { DRDY }
    [  111.804450] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804458] ata3.00: cmd 60/38:90:a8:17:b8/00:00:24:00:00/40 tag 18 ncq 28672 in
    [  111.804459]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804463] ata3.00: status: { DRDY }
    [  111.804466] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804475] ata3.00: cmd 60/58:98:48:16:b8/00:00:24:00:00/40 tag 19 ncq 45056 in
    [  111.804476]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804480] ata3.00: status: { DRDY }
    [  111.804484] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804492] ata3.00: cmd 60/18:a8:b0:11:b8/00:00:24:00:00/40 tag 21 ncq 12288 in
    [  111.804494]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804497] ata3.00: status: { DRDY }
    [  111.804501] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804509] ata3.00: cmd 60/70:b0:80:f2:b6/00:00:24:00:00/40 tag 22 ncq 57344 in
    [  111.804511]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804514] ata3.00: status: { DRDY }
    [  111.804518] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804526] ata3.00: cmd 60/20:b8:b8:8c:b7/00:00:24:00:00/40 tag 23 ncq 16384 in
    [  111.804528]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804532] ata3.00: status: { DRDY }
    [  111.804535] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804543] ata3.00: cmd 60/40:c0:a8:19:b8/00:00:24:00:00/40 tag 24 ncq 32768 in
    [  111.804545]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804549] ata3.00: status: { DRDY }
    [  111.804552] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804560] ata3.00: cmd 60/08:c8:d0:5c:b7/00:00:24:00:00/40 tag 25 ncq 4096 in
    [  111.804562]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804566] ata3.00: status: { DRDY }
    [  111.804570] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804578] ata3.00: cmd 60/00:d0:b8:88:b7/04:00:24:00:00/40 tag 26 ncq 524288 in
    [  111.804580]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804583] ata3.00: status: { DRDY }
    [  111.804587] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804595] ata3.00: cmd 60/00:d8:b8:84:b7/04:00:24:00:00/40 tag 27 ncq 524288 in
    [  111.804597]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804601] ata3.00: status: { DRDY }
    [  111.804604] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804612] ata3.00: cmd 60/30:e0:40:18:b8/00:00:24:00:00/40 tag 28 ncq 24576 in
    [  111.804614]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804618] ata3.00: status: { DRDY }
    [  111.804621] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804629] ata3.00: cmd 60/b0:e8:f8:38:b8/00:00:24:00:00/40 tag 29 ncq 90112 in
    [  111.804631]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804635] ata3.00: status: { DRDY }
    [  111.804638] ata3.00: failed command: READ FPDMA QUEUED
    [  111.804646] ata3.00: cmd 60/38:f0:d0:02:b7/00:00:24:00:00/40 tag 30 ncq 28672 in
    [  111.804648]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  111.804652] ata3.00: status: { DRDY }
    [  111.804659] ata3: hard resetting link
    [  111.804662] ata3: nv: skipping hardreset on occupied port
    [  112.328033] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [  112.376448] ata3.00: configured for UDMA/133
    [  112.376454] ata3.00: device reported invalid CHS sector 0
    [  112.376458] ata3.00: device reported invalid CHS sector 0
    [  112.376462] ata3.00: device reported invalid CHS sector 0
    [  112.376465] ata3.00: device reported invalid CHS sector 0
    [  112.376468] ata3.00: device reported invalid CHS sector 0
    [  112.376471] ata3.00: device reported invalid CHS sector 0
    [  112.376475] ata3.00: device reported invalid CHS sector 0
    [  112.376478] ata3.00: device reported invalid CHS sector 0
    [  112.376481] ata3.00: device reported invalid CHS sector 0
    [  112.376485] ata3.00: device reported invalid CHS sector 0
    [  112.376488] ata3.00: device reported invalid CHS sector 0
    [  112.376491] ata3.00: device reported invalid CHS sector 0
    [  112.376494] ata3.00: device reported invalid CHS sector 0
    [  112.376498] ata3.00: device reported invalid CHS sector 0
    [  112.376501] ata3.00: device reported invalid CHS sector 0
    [  112.376504] ata3.00: device reported invalid CHS sector 0
    [  112.376508] ata3.00: device reported invalid CHS sector 0
    [  112.376511] ata3.00: device reported invalid CHS sector 0
    [  112.376514] ata3.00: device reported invalid CHS sector 0
    [  112.376518] ata3.00: device reported invalid CHS sector 0
    [  112.376521] ata3.00: device reported invalid CHS sector 0
    [  112.376524] ata3.00: device reported invalid CHS sector 0
    [  112.376527] ata3.00: device reported invalid CHS sector 0
    [  112.376531] ata3.00: device reported invalid CHS sector 0
    [  112.376534] ata3.00: device reported invalid CHS sector 0
    [  112.376537] ata3.00: device reported invalid CHS sector 0
    [  112.376571] ata3: EH complete
    [  113.485526] <30>udev[336]: starting version 167
    [  113.553643] Adding 3905532k swap on /dev/sda9.  Priority:-1 extents:1 across:3905532k 
    [  113.581467] lp: driver loaded but no devices found
    [  113.635118] i2c i2c-0: nForce2 SMBus adapter at 0x3040
    [  113.637310] i2c i2c-1: nForce2 SMBus adapter at 0x3000
    [  113.655628] NV_TCO: NV TCO WatchDog Timer Driver v0.01
    [  113.655876] NV_TCO: Watchdog reboot not detected.
    [  113.657184] NV_TCO: initialized (0x1440). heartbeat=30 sec (nowayout=0)
    [  113.657549] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
    [  113.719524] cfg80211: Calling CRDA to update world regulatory domain
    [  113.815519] r852 0000:07:05.3: can't find IRQ for PCI INT C; probably buggy MP table
    [  113.815532] r852 0000:07:05.3: setting latency timer to 64
    [  113.822742] r852: Non dma capable device detected, dma disabled
    [  113.822765] r852: driver loaded succesfully
    [  113.845407] Linux video capture interface: v2.00
    [  113.886743] uvcvideo: Found UVC 1.00 device <unnamed> (05ca:1810)
    [  113.893545] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
    [  113.895131] uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
    [  113.895146] uvcvideo: Failed to initialize the device (-5).
    [  113.895250] usbcore: registered new interface driver uvcvideo
    [  113.895253] USB Video Class driver (v1.0.0)
    [  113.929114] EXT4-fs (sda10): re-mounted. Opts: errors=remount-ro
    [  114.155599] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
    [  114.220234] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220241] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220246] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220250] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220254] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220258] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220261] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220265] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220269] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220273] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220276] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220281] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220284] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220288] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220291] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220296] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220299] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220303] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220307] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220311] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220314] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220318] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220322] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220326] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220329] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220333] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.220337] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
    [  114.220341] cfg80211: 2474000 KHz - 2494000 KHz @  KHz), (600 mBi, 2000 mBm)
    [  114.244138] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
    [  114.245084] Registered led device: b43-phy0::tx
    [  114.245121] Registered led device: b43-phy0::rx
    [  114.245154] Registered led device: b43-phy0::radio
    [  114.245181] Broadcom 43xx driver loaded [ Features: PNL, Firmware-ID: FW13 ]
    [  114.254792] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254800] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254804] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254809] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254812] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254816] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254820] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254824] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254827] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254832] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254835] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254839] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254842] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254847] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254850] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254854] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254858] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254862] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254865] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254869] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254873] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254877] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254880] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254884] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254888] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254892] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254895] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
    [  114.254900] cfg80211: 2474000 KHz - 2494000 KHz @  KHz), (300 mBi, 2000 mBm)
    [  114.254904] cfg80211: World regulatory domain updated:
    [  114.254907] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [  114.254911] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [  114.254915] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [  114.254919] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [  114.254923] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [  114.254927] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [  114.326306] HDA Intel 0000:00:10.1: can't find IRQ for PCI INT B; probably buggy MP table
    [  114.326314] hda_intel: Disable MSI for Nvidia chipset
    [  114.326352] HDA Intel 0000:00:10.1: setting latency timer to 64
    [  114.490567] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
    [  114.640198] Synaptics Touchpad, model: 1, fw: 6.3, id: 0x1a0b1, caps: 0xa04713/0x200000/0x0
    [  114.706400] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input1
    [  115.214192] EXT4-fs (sda11): mounted filesystem with ordered data mode. Opts: (null)
    [  117.380020] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x000f0001
    [  145.888040] ata3: EH in SWNCQ mode,QC:qc_active 0xFF sactive 0xFF
    [  145.888054] ata3: SWNCQ:qc_active 0xFD defer_bits 0x2 last_issue_tag 0x7
    [  145.888056]   dhfis 0x7D dmafis 0x0 sdbfis 0x0
    [  145.888068] ata3: ATA_REG 0x40 ERR_REG 0x0
    [  145.888074] ata3: tag : dhfis dmafis sdbfis sacitve
    [  145.888081] ata3: tag 0x0: 1 0 0 1  
    [  145.888087] ata3: tag 0x2: 1 0 0 1  
    [  145.888092] ata3: tag 0x3: 1 0 0 1  
    [  145.888098] ata3: tag 0x4: 1 0 0 1  
    [  145.888103] ata3: tag 0x5: 1 0 0 1  
    [  145.888109] ata3: tag 0x6: 1 0 0 1  
    [  145.888117] ata3: tag 0x7: 0 0 0 1  
    [  145.888133] ata3.00: NCQ disabled due to excessive errors
    [  145.888139] ata3.00: exception Emask 0x0 SAct 0xff SErr 0x0 action 0x6 frozen
    [  145.888151] ata3.00: failed command: READ FPDMA QUEUED
    [  145.888166] ata3.00: cmd 60/10:00:30:38:e4/00:00:24:00:00/40 tag 0 ncq 8192 in
    [  145.888168]          res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
    [  145.888186] ata3.00: status: { DRDY }
    [  145.888194] ata3.00: failed command: READ FPDMA QUEUED
    [  145.888207] ata3.00: cmd 60/08:08:00:b8:e6/00:00:24:00:00/40 tag 1 ncq 4096 in
    [  145.888209]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  145.888227] ata3.00: status: { DRDY }
    [  145.888234] ata3.00: failed command: READ FPDMA QUEUED
    [  145.888247] ata3.00: cmd 60/38:10:60:39:e4/00:00:24:00:00/40 tag 2 ncq 28672 in
    [  145.888248]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  145.888266] ata3.00: status: { DRDY }
    [  145.888273] ata3.00: failed command: READ FPDMA QUEUED
    [  145.888286] ata3.00: cmd 60/08:18:20:38:e4/00:00:24:00:00/40 tag 3 ncq 4096 in
    [  145.888288]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  145.888306] ata3.00: status: { DRDY }
    [  145.888313] ata3.00: failed command: READ FPDMA QUEUED
    [  145.888326] ata3.00: cmd 60/08:20:10:08:e5/00:00:24:00:00/40 tag 4 ncq 4096 in
    [  145.888328]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  145.888345] ata3.00: status: { DRDY }
    [  145.888352] ata3.00: failed command: READ FPDMA QUEUED
    [  145.888365] ata3.00: cmd 60/08:28:98:88:e5/00:00:24:00:00/40 tag 5 ncq 4096 in
    [  145.888367]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  145.888385] ata3.00: status: { DRDY }
    [  145.888392] ata3.00: failed command: READ FPDMA QUEUED
    [  145.888404] ata3.00: cmd 60/08:30:50:a1:e5/00:00:24:00:00/40 tag 6 ncq 4096 in
    [  145.888406]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  145.888424] ata3.00: status: { DRDY }
    [  145.888431] ata3.00: failed command: READ FPDMA QUEUED
    [  145.888444] ata3.00: cmd 60/08:38:00:29:e6/00:00:24:00:00/40 tag 7 ncq 4096 in
    [  145.888446]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [  145.888464] ata3.00: status: { DRDY }
    [  145.888475] ata3: hard resetting link
    [  145.888478] ata3: nv: skipping hardreset on occupied port
    [  146.412034] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [  146.465230] ata3.00: configured for UDMA/133
    [  146.465237] ata3.00: device reported invalid CHS sector 0
    [  146.465241] ata3.00: device reported invalid CHS sector 0
    [  146.465244] ata3.00: device reported invalid CHS sector 0
    [  146.465248] ata3.00: device reported invalid CHS sector 0
    [  146.465251] ata3.00: device reported invalid CHS sector 0
    [  146.465255] ata3.00: device reported invalid CHS sector 0
    [  146.465258] ata3.00: device reported invalid CHS sector 0
    [  146.465262] ata3.00: device reported invalid CHS sector 0
    [  146.465279] ata3: EH complete
    [  147.149338] vesafb: framebuffer at 0xc0000000, mapped to 0xf9180000, using 3072k, total 3072k
    [  147.149345] vesafb: mode is 1024x768x32, linelength=4096, pages=0
    [  147.149349] vesafb: scrolling: redraw
    [  147.149353] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    [  147.150954] Console: switching to colour frame buffer device 128x48
    [  147.177235] ppdev: user-space parallel port driver
    [  147.204338] fb0: VESA VGA frame buffer device
    [  147.213934] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
    [  147.296574] b43-phy0 ERROR: Cannot request IRQ-0
    [  147.708118] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
    [  147.782002] b43-phy0 ERROR: Cannot request IRQ-0
    [  149.130111] EXT4-fs (sda10): re-mounted. Opts: errors=remount-ro,commit=0
    [  149.134598] EXT4-fs (sda8): re-mounted. Opts: commit=0
    [  149.214100] EXT4-fs (sda11): re-mounted. Opts: commit=0
    [  151.630584] EXT4-fs (sda10): re-mounted. Opts: errors=remount-ro,commit=0
    [  151.637250] EXT4-fs (sda8): re-mounted. Opts: commit=0
    [  151.641991] EXT4-fs (sda11): re-mounted. Opts: commit=0
    [  157.648024] eth0: no IPv6 routers present
    Relevant BIOS screens below:
    Attached Images Attached Images
    Last edited by KemKev; August 19th, 2011 at 02:58 AM. Reason: Added BIOS screenprints

Page 3 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •