#14820 closed bug (invalid)
regression: won't boot until iprowifi2100 blacklisted
| Reported by: | taos | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers/Network/iprowifi2100 | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
hrev52748 gcc2hybrid
It's no longer possible to boot Haiku on an Acer Travelmate 800 (Centrino, ca. 2003) without blacklisting the iprowifi2100 driver. Without blacklisting, booting stops after the last boot icon (rocket?) lights up. Most of the time my wifi LED starts blinking, then emits continuously, but booting never gets to the desktop.
It was once possible to actually connect wirelessly to a network on this computer.
The attached syslog contains several boot attempts:
Last - booted to desktop with blacklisted iprowifi2100.
Second to last - boot attempt without blacklisting, wifi LED did not light up.
Third to last (and others before) - boot attempt without blacklisting, wifi LED lighted up.
Attachments (16)
Change History (37)
by , 6 years ago
follow-up: 2 comment:1 by , 6 years ago
iprowifi2100 is not mentioned in the syslog at all, so that will be pretty hard to debug.
Try blacklisting your ethernet driver instead and see if that also fixes the problem. There was a similar issue that "solved itself" in which one had to blacklist one driver or the other and then things worked.
comment:2 by , 6 years ago
Replying to waddlesplash:
Try blacklisting your ethernet driver instead and see if that also fixes the problem. There was a similar issue that "solved itself" in which one had to blacklist one driver or the other and then things worked.
Do you think of #14667? As I've already written there, blacklisting my ethernet driver does not let me boot. And the problem didn't resolve itself for me. #14667 also contains a syslog from hrev52547 that still mentions iprowifi2100, the newer syslog only refers to "device 1043: PRO/Wireless LAN 2100 3B Mini PCI Adapter (MIM2000/Centrino)".
comment:3 by , 6 years ago
Could you please drop into KDL after the hang begins (via Alt+PrntScrn+D) and then get backtraces of the net_server and kernel_daemon threads (you can find their IDs by running threads | grep daemon and threads | grep net_server, and then run bt NUM). That should give more insight into what's going wrong.
comment:4 by , 6 years ago
I'll try this as soon as I get my hands on the Acer TM 800 again, probably next weekend or the weekend after.
comment:5 by , 6 years ago
I've attached the backtraces for kernel daemon, net_server, ipw intr handler, and other iprowifi related threads.
by , 6 years ago
| Attachment: | bt_kernel_daemon_net_server.jpg added |
|---|
bt for net_server and kernel daemon
comment:6 by , 6 years ago
Unfortunately all of those things look relatively normal; so I'm not sure what the problem could be.
comment:7 by , 6 years ago
I'm checking a few nightlies to find out when the problem started (I'll add the syslogs and update this comment):
hrev52502 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present, but can't see any wireless networks)
hrev52533 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present, but can't see any wireless networks)
hrev52539 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present, but can't see any wireless networks)
hrev52547 - no problem during first boot (but no /dev/net/iprowifi2100/0), can't boot to desktop after installing the firmwares, stops at blue background, wifi indicator LED blinking
comment:8 by , 6 years ago
hrev52539 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present, but can't see any wireless networks)
hrev52547 - no problem during first boot (but no /dev/net/iprowifi2100/0), can't boot to desktop after installing the firmwares, stops at blue background, wifi indicator LED blinking
Now that is extremely interesting, because there are no changes to the iprowifi2100 driver in that range, and so I think hrev52546 is the only changeset of any potential relevance.
Within that range, this is the only commit which might be suspect, and all error paths added in that commit will print to syslog, save the _user_set_memory_protection one, which is rarely (if ever?) called.
If you can do a custom build, reverting that individual commit and seeing if it fixes something would be very interesting.
comment:9 by , 6 years ago
Where will this change end up? In haiku.hpkg? As far as I remember I haven't been able to successfully build a complete image for quite a long time in haiku. Individual files or (some) packages on the other hand should build fine. However, I won't have time until Friday to start a custom build and check if reverting the mentioned commit solves the issue.
I'll also try to find out when the iprowifi2100 stopped seeing wireless networks (not related to the boot issue).
comment:10 by , 6 years ago
You can just do "jam -q iprowifi2100" and copy the resulting binary to /boot/system/non-packaged/add-ons/kernel/drivers/bin/iprowifi2100 . Not sure if you need to blacklist the original system driver...
comment:11 by , 6 years ago
No, the relevant changes affect only the kernel and not this driver. haiku.hpkg will have to be rebuilt.
comment:13 by , 6 years ago
Just wanted to update haiku before starting to build haiku.hpkg with the reverted commit. I'm on hrev52874 now (updated from hrev52833) and the boot problem is gone. In addition, iprowifi2100 can see a number of wireless networks (except mine, of course). Was there a commit this week that could have fixed something related to the boot issue?
comment:14 by , 6 years ago
I don't think so, but there were a few kernel changes that could be relevant, though that would imply there was some deeper issue they just prevented. Could you try to narrow down that range a bit by bisecting?
comment:15 by , 6 years ago
Okay, now I'm a little puzzled:
hrev52833 - no problem during first boot (but no /dev/net/iprowifi2100/0), can't boot to desktop after installing the firmwares, stops at blue background, wifi indicator LED blinking
hrev52843 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present), wifi indicator LED off, but can't see any wireless networks
hrev52849 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present), wifi indicator LED off, but can't see any wireless networks
hrev52853 - no problem during first boot (but no /dev/net/iprowifi2100/0), can't boot to desktop after installing the firmwares, stops at blue background, wifi indicator LED off
hrev52859 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present), wifi indicator LED off, can see some but not all wireless networks
hrev52860 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present), wifi indicator LED off, can see some but not all wireless networks
comment:16 by , 5 years ago
The problem is still present in hrev53924. I've attached a new syslog (even if there's probably nothing interesting).
by , 5 years ago
| Attachment: | syslog_hrev53924.txt added |
|---|
syslog booting hrev53924 a few times without blacklisting and one time with blacklisted iprowifi2100
comment:19 by , 2 years ago
If someone is still interested:
hrev56238 - no problem during first boot (but no /dev/net/iprowifi2100/0), can't boot to desktop after installing the firmwares, KDL
hrev56630 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present), wifi indicator LED off, can see some but not all wireless networks, after rebooting, wifi indicator LED starts blinking at lit rocket icon, fans spinning (fans turn off again after a couple of minutes), still at rocket after ~ 30 min
by , 2 years ago
| Attachment: | syslog.hrev56630.txt added |
|---|
syslog for hrev56630 (blacklisted and not blacklisted)
follow-up: 21 comment:20 by , 2 years ago
Which KDL is this?
I could potentially drop the FreeBSD driver here in favor of an OpenBSD driver for this hardware, maybe that would be better...
syslog with several boot attempts