#11568 closed bug (fixed)
fails to boot up due to wireless drivers issue
Reported by: | rishabhrawat | Owned by: | korli |
---|---|---|---|
Priority: | high | Milestone: | R1 |
Component: | Drivers/Network/iprowifi4965 | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
Attachments (6)
Change History (24)
by , 10 years ago
Attachment: | IMAG1585.jpg added |
---|
comment:1 by , 10 years ago
As a workaround maybe you could try to use iprowifi4965 from r1alpha4.1 on current nightly? See driver changelog http://cgit.haiku-os.org/haiku/log/src/add-ons/kernel/drivers/network/wlan/iprowifi496.
comment:2 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 10 years ago
Description: | modified (diff) |
---|
follow-up: 7 comment:4 by , 10 years ago
A syslog while blacklisting would be nice. Also the panic message on top of the KDL picture is missing.
And finally, iwn_detach() is called because of a failure earlier in iwn_attach(). The actual failure message should be visible again at the end when you type "syslog". Please provide this message.
follow-up: 6 comment:5 by , 10 years ago
IIRC message
reprints the message printed when entering KDL.
comment:6 by , 10 years ago
Replying to diver:
IIRC
message
reprints the message printed when entering KDL.
Yeah, but iwn should log a normal failure message like "can't find blah" or "can't allocate blah", which only is in the syslog.
by , 10 years ago
Attachment: | 2014-12-06 14.11.47.jpg added |
---|
by , 10 years ago
Attachment: | 2014-12-06 14.11.47.2.jpg added |
---|
syslog part where is detects my wireless hardware
by , 10 years ago
Attachment: | panic message .jpg added |
---|
by , 10 years ago
Attachment: | syslog end message.jpg added |
---|
comment:7 by , 10 years ago
Replying to korli:
A syslog while blacklisting would be nice. Also the panic message on top of the KDL picture is missing.
And finally, iwn_detach() is called because of a failure earlier in iwn_attach(). The actual failure message should be visible again at the end when you type "syslog". Please provide this message.
i am attaching the relevant images, i.e the panic message, the syslog part where it detects my hardware and the end of syslog where it points out the problem
PS> sorry i uploaded a image twice and i don't know how to remove it
comment:8 by , 10 years ago
Blocking: | 7665 added |
---|
comment:9 by , 10 years ago
I'm getting this same KDL on boot if I boot without safe mode enabled under 49058 on a System 76 Gazelle Pro laptop which uses a Centrino Wireless-N 2230.
I can sometimes get Haiku to boot with just safe mode & Use fail-safe video mode but most of the time I have to disable IO-APIC too to get it to boot successfully. I've not tried the most recent alpha release just yet.
If 2230 support hasn't already made it into Haiku, a backport of the FreeBSD 2230 driver to 9-STABLE is here:
by , 10 years ago
Attachment: | r49058-KDL-System76_GazellePro.jpg added |
---|
KDL booting 49058 (GCC2 hybrid x86) on a System76 Gazelle Pro w/ Centrino 2230
comment:10 by , 10 years ago
I can boot alpha4.1 on my Gazelle Pro without any KDL nor having to use safe mode or disabling IO-APIC but unfortunately it doesn't support either of my network interfaces - Centrino 2230 and a RTL8111/8168/8411.
Maybe I can compile FBSD drivers for these under alpha4.1?
comment:11 by , 10 years ago
After blacklisting iprowifi4965, I can boot 49058 provided I use fail-safe video mode. My Gazelle Pro has Intel HD4600 GFX.
comment:12 by , 9 years ago
I believe support for Centrino 2230 was added in hrev49127. Please test and provide a feedback.
comment:15 by , 6 years ago
comment:16 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:17 by , 6 years ago
Blocking: | 7665 removed |
---|
KDL screenshot