#14546 closed bug (fixed)
R1/beta1 rc1: Some Wifi cards not loading in UEFI boot.
Reported by: | return_0e | Owned by: | waddlesplash |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | Drivers/Network/idualwifi7260 | Version: | R1/Development |
Keywords: | UEFI, wifi | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
I tested both the BIOS and UEFI RC1 images on one of my machines with a Intel Wireless 3165 card and I noticed something odd. The idualwifi7260 driver loads fine when booted in BIOS mode but not in UEFI.
The machine I used is a LattePanda Alpha - https://www.kickstarter.com/projects/139108638/lattepanda-alpha-soul-of-a-macbook-in-a-pocket-siz
Attachments (6)
Change History (18)
by , 6 years ago
Attachment: | syslog-biosboot-normal-wifi added |
---|
by , 6 years ago
Attachment: | syslog-efiboot-no-wifi added |
---|
by , 6 years ago
Attachment: | loaded-drivers-x86_64-biosboot-r1-beta1-rc1.txt added |
---|
by , 6 years ago
Attachment: | loaded-drivers-x86_64-efiboot-r1-beta1-rc1.txt added |
---|
comment:1 by , 6 years ago
Component: | - General → Drivers/Network/idualwifi7260 |
---|---|
Owner: | changed from | to
comment:2 by , 6 years ago
I have the opposite happening on realtekwifi... BIOS is broken but EFI works.
I should probably attach syslogs from the working boot to my ticket for that.
comment:4 by , 6 years ago
rev 52745
KERN: [idualwifi7260] (iwm) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1,0x2) KERN: add_memory_type_range(2067, 0xa2100000, 0x2000, 0) KERN: set MTRRs to: KERN: mtrr: 0: base: 0x8a000000, size: 0x2000000, type: 0 KERN: mtrr: 1: base: 0xa0000000, size: 0x20000000, type: 0 KERN: mtrr: 2: base: 0xc0000000, size: 0x40000000, type: 0 KERN: mtrr: 3: base: 0x90000000, size: 0x10000000, type: 1 KERN: allocate_io_interrupt_vectors: allocated 1 vectors starting from 18 KERN: msi_allocate_vectors: allocated 1 vectors starting from 18 KERN: [idualwifi7260] (iwm) bus_alloc_resource(1, [1], 0x0, 0xffffffff, 0x1,0x2) KERN: msi enabled: 0x0081 KERN: [idualwifi7260] (iwm) iwm_read_firmware: unknown firmware section 512, abort KERN: [idualwifi7260] (iwm) firmware parse error -2147483643, section type 512 KERN: [idualwifi7260] (iwm) iwm_read_firmware: failed -2147483643 KERN: [idualwifi7260] (iwm) Failed to start INIT ucode: -2147483643
comment:5 by , 6 years ago
kim1963, is this on a 32-bit or 64-bit build? If it's on a 32-bit build, please try 64-bit instead.
comment:6 by , 6 years ago
Indeed, this seems to be some sort of bug in the iwm code, it happens on FreeBSD too: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219683
comment:7 by , 6 years ago
I have tried 64 bit hrev52738 build on the same machine (LattePanda Alpha). idualwifi7260 doesn't load when booting on UEFI and I get a similar issue in this ticker such as:
KERN: [idualwifi7260] (iwm) iwm_start_fw: Unable to init nic KERN: [idualwifi7260] (iwm) iwm_start_fw: failed -2147483634 KERN: [idualwifi7260] (iwm) Failed to start INIT ucode: -2147483634
I tested on BIOS boot and idualwifi7260 wifi does scan for networks, but I can't connect to any. It repeats this message after attempting to connect to a wifi network. I'll attach a newer syslog here.
KERN: wlan_control: 9235, 16 KERN: wlan_control: 9235, 17 KERN: wlan_control: 9235, 26 KERN: wlan_control: 9235, 98 KERN: wlan_control: 9235, 15 KERN: wlan_control: 9235, 76
by , 6 years ago
Attachment: | syslog-uefi-boot-x64-hrev52738-no-wifi.txt added |
---|
by , 6 years ago
Attachment: | syslog-bios-boot-x64-hrev52738-wifi-no-connect.txt added |
---|
comment:8 by , 6 years ago
hrev52792 includes some changes to PCI power management in idualwifi7260 that might help here. Please retest.
comment:10 by , 5 years ago
With the changes in hrev53174, I can connect to wifi networks when booting from a BIOS or a UEFI install on x86_64.
I tested an Intel Wireless 8265 AC card with my NUC and a Intel Wireless 3165 using a LattePanda Alpha board and both PCs can connect to open and protected wireless networks. So the idualwifi7260 driver is loaded and functioning correctly, regardless of booting from BIOS/UEFI.
comment:12 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
(iwm) Failed to start INIT ucode: -2147483634
~> error -2147483634
0x8000000e: Device/File/Resource busy