Description: WWAN Broadband Wireless Client Manager - Verizon driver for HP Compaq 6515b This package contains the HP Wireless WAN (WWAN) Broadband Wireless Client Manager for Verizon for the supported notebook models and operating system. Compatible devices. Free drivers for HP Compaq 6515b. Found 129 files for Windows 7, Windows 7 64-bit, Windows Vista, Windows Vista 64-bit, Windows XP, Windows XP 64-bit, Windows 2000, Windows XP Media Center, Windows XP Tablet PC. Select driver to download. HP Compaq 6510b Notebook PC Windows 7 Ultimate (32-bit) drivers Driver - AudioADI AD1981HD Audio Driver for Microsoft Windows 7 6.10.1.5240; 6.10.2.5240Driver - GraphicsIntel Video Driver and Control Panel 8.Driver.
On 12:26 PM, derek botha wrote: Hi Sorry if this sounds dumb but im posting this as a lastr resort. I loaded an old laptop with Suse 13.1There is no Suse 13.1. Do you mean openSUSE 13.1?
Code: linux-36ab: # lspci -nnv00:00.0 Host bridge 0600: Advanced Micro Devices, Inc. AMD/ATI RS690 Host Bridge 1002:7910Subsystem: Hewlett-Packard Company Device 103c:30c2Flags: bus master, 66MHz, medium devsel, latency 6400:01.0 PCI bridge 0604: Advanced Micro Devices, Inc. AMD/ATI RS690 PCI to PCI Bridge (Internal gfx) 1002:7912 (prog-if 00 Normal decode)Flags: bus master, 66MHz, medium devsel, latency 64Bus: primary=00, secondary=01, subordinate=01, sec-latency=0I/O behind bridge: 0004fffMemory behind bridge: d0400000-d05fffffPrefetchable memory behind bridge: 00000c7ffffffCapabilities: 44 HyperTransport: MSI Mapping Enable+ Fixed+Capabilities: b0 Subsystem: Hewlett-Packard Company Device 103c:30c2Kernel modules: shpchp00:04.0 PCI bridge 0604: Advanced Micro Devices, Inc. Code: linux-36ab: # lsusbBus 004 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint SensorBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubBus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubBus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubBus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubBus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubAlso, the system is opensuse 13.1 (sorry for the mistake) and im running windows in a dual boot.
In windows the wireless is comming on and is were i checked the device type to be Broadcom.As said in my first post - i believe the problem is that the wireless is not comming on and subseqeuntly not being picked up by the kernel - though i can be dismally wrong in this as well.Let me know if you need any additional information.RegardsPS: Wireless is working when booting into windows. On 02:56 PM, derek botha wrote: Hi lwfinger Find below output for commands as reqeusted: Code: - linux-36ab: # lspci -nnv 00:00.0 Host bridge 0600: Advanced Micro Devices, Inc. AMD/ATI RS690 Host Bridge 1002:7910 Subsystem: Hewlett-Packard Company Device 103c:30c2 Flags: bus master, 66MHz, medium devsel, latency 64 00:01.0 PCI bridge 0604: Advanced Micro Devices, Inc. AMD/ATI RS690 PCI to PCI Bridge (Internal gfx) 1002:7912 (prog-if 00 Normal decode) Flags: bus master, 66MHz, medium devsel, latency 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0004fff Memory behind bridge: d0400000-d05fffff Prefetchable memory behind bridge: 00000c7ffffff Capabilities: 44 HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: b0 Subsystem: Hewlett-Packard Company Device 103c:30c2 Kernel modules: shpchp 00:04.0 PCI bridge 0604: Advanced Micro Devices, Inc. On 02:56 PM, derek botha wrote: Hi lwfinger Find below output for commands as reqeusted: Code: - linux-36ab: # lspci -nnv 00:00.0 Host bridge 0600: Advanced Micro Devices, Inc. AMD/ATI RS690 Host Bridge 1002:7910 Subsystem: Hewlett-Packard Company Device 103c:30c2 Flags: bus master, 66MHz, medium devsel, latency 64 00:01.0 PCI bridge 0604: Advanced Micro Devices, Inc.
AMD/ATI RS690 PCI to PCI Bridge (Internal gfx) 1002:7912 (prog-if 00 Normal decode) Flags: bus master, 66MHz, medium devsel, latency 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0004fff Memory behind bridge: d0400000-d05fffff Prefetchable memory behind bridge: 00000c7ffffff Capabilities: 44 HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: b0 Subsystem: Hewlett-Packard Company Device 103c:30c2 Kernel modules: shpchp 00:04.0 PCI bridge 0604: Advanced Micro Devices, Inc. HTML Code: PCI/VEN14E4&DEV4312&SUBSYS1370103C&REV02And this show again to the broadcom BCM4312 family which should be the B43xxx drivers - but no luck with that yet.Kind regardsI also got another post to install b43-lpphy-installer, but this should be covered in the packman procedure already completed. As said the only difference i can see now it the fact that in windows i can switch the wireless on/off but in openSUSE im not currently able to do so.Last edited by derekbotha; 06-Jul-2014 at 17:59.Reason: additional information. I myself is also out of what can be the cause. The only thing i can see is that windows allows that i can switch the wireless on/off on the touch panel but in openSUSE im not able to do that. (i have tried a few other flavours as well - linux mint, ubuntu).Okay, you need to figure out how to stop the windows driver from completely powering down the wireless device (at shutdown).
FWIW, I have a similar model (6710b) laptop, and I recall the the HP wireless utility was powering my device down initially (at the time I was first installing openSUSE on it). Once that was disabled, I was able to progress with wireless configuration.
Hp Compaq 6515b Wifi Drivers For Windows 7
I should theoretically be able to toggle in openSUSE as well??Kind regardsThere is a 'rfkill' userspace utility which used to query and control various rfkill switches (including those related to the wifi interfaces). However, it will not work here, because clearly the kernel does not detect the wireless device ie it is not effectively present (and this might include hardware which is completely powered down by the system infrastructure for some reason). You'll know when it is powered up properly, because the chipset will then be reported by '/sbin/lspci'.
Hp Compaq 6515b Specs
Well, I don't regularly use Windows, and I don't know which Windows version you are using, but clearly the OS is disabling the hardware at shutdown. You've already posted the chipset details as Windows detects/reports them, now you need to find out how to prevent the disabling from occurring.There is a 'rfkill' userspace utility which used to query and control various rfkill switches (including those related to the wifi interfaces). However, it will not work here, because clearly the kernel does not detect the wireless device ie it is not effectively present (and this might include hardware which is completely powered down by the system infrastructure for some reason). You'll know when it is powered up properly, because the chipset will then be reported by '/sbin/lspci'.Ok it seem lide the hpwmi module is active.