David Given
2012-11-13 19:58:35 UTC
I have an old Sony Vaio with an ipw2100 wifi chipset. I installed Haiku
a4 on it and it all seemed to work fine. Unfortunately, after running
the script to download the wifi firmware bundle, it has now stopped booting.
It usually hangs immediately after changing screen mode, showing a
corrupted boot splash screen, although sometimes I get a frozen mouse
pointer instead.
Turning debug output on usually shows a whole bunch of Radeon messages,
although *very occasionally* I'll see messages describing initialisation
of the wireless hardware interleaved. (This smells like the system is
freezing before the debug log gets flushed to the screen. Is there a way
to make this synchronous?)
Right now I can see that it's called ifmedia_add a bunch of times for
various different slightly different modes, and the last message shown is:
ifmedia_add: Adding Entry...
(The previous call was for type = IEEE 802.11 Wireless Ethernet, Mode =
11b, Subtype = DS/5.5Mbps, although this can vary.)
This all happens regardless of whether the physical kill-switch for the
wireless hardware is on or off.
It boots fine in safe mode.
I'm *sure* I remember this happening in a3... any ideas?
a4 on it and it all seemed to work fine. Unfortunately, after running
the script to download the wifi firmware bundle, it has now stopped booting.
It usually hangs immediately after changing screen mode, showing a
corrupted boot splash screen, although sometimes I get a frozen mouse
pointer instead.
Turning debug output on usually shows a whole bunch of Radeon messages,
although *very occasionally* I'll see messages describing initialisation
of the wireless hardware interleaved. (This smells like the system is
freezing before the debug log gets flushed to the screen. Is there a way
to make this synchronous?)
Right now I can see that it's called ifmedia_add a bunch of times for
various different slightly different modes, and the last message shown is:
ifmedia_add: Adding Entry...
(The previous call was for type = IEEE 802.11 Wireless Ethernet, Mode =
11b, Subtype = DS/5.5Mbps, although this can vary.)
This all happens regardless of whether the physical kill-switch for the
wireless hardware is on or off.
It boots fine in safe mode.
I'm *sure* I remember this happening in a3... any ideas?
--
ââââ ïœïœïŒ ïœïœïœïœïœïœïœïŒïœïœïœ âââââ http://www.cowlark.com âââââ
â "Of course, on a sufficiently small planet, 40 km/hr is, in fact,
â sufficient to punt the elastic spherical cow into low orbit." ---
â Brooks Moses on r.a.sf.c
ââââ ïœïœïŒ ïœïœïœïœïœïœïœïŒïœïœïœ âââââ http://www.cowlark.com âââââ
â "Of course, on a sufficiently small planet, 40 km/hr is, in fact,
â sufficient to punt the elastic spherical cow into low orbit." ---
â Brooks Moses on r.a.sf.c