On Tuesday 15 Nov 2005 20:32, Andy Ross wrote: > Lee Elliott wrote: > > I get exactly the same problem on my lap-top (it's the only > > one of my systems with Windows installed). I noticed while > > watching the console messages scroll by, that the driver > > module for the sound card fails to load during the first > > boot after running windows but subsequent re-boots are fine. > > I would submit this to the ALSA folks as a bug report. Most > likely it's an issue with the initialization code for your > sound hardware -- it can properly handle the cold boot state, > but not the state that windows leaves it in following a warm > boot. > > Be sure to include the output of "lspci -vvv" so they know > what hardware you have. > > Andy
I think it might not be a cold/warm start problem because I'm pretty sure that one of the things I tried, when I first found the problem, was to try powering-down before re-booting back into linux but it didn't cure it, iirc. It suggested to me that something was set in nv ram somewhere, which was causing the problem. A curious aspect of this problem is that _failing_ to load the driver seems to fix it - perhaps the sound h/w resets any nv ram settings itself if it finds it hasn't got a driver loaded. The lap-top is an old P3-750 Viao - 8MB neomagic video so no use at all for FG. Even running atlas on it results in 100% cpu utilisation because of the s/w rendering. I can't see the Alsa team putting too much effort in fixing this problem on such old h/w and it only really gets used as a rendering node, or playing the occasional PC game. LeeE _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
