Erich Schulz wrote: > You probably have an IRQ conflict, or an IO conflict. Before you go much > farther, check the value in /proc/ioports and /proc/interrupts, to make > sure that they do not conflict with anything else. > > If that is ok, try and install the module by hand first, as root type: > modprobe eexpress "io=0x300" > Once you have run the command, then check the messages in: > /var/log/messages > > I have found that with one eexpress card that I had, you needed to send a > packet out before it worked, simple fix, just ping one packet in the > startup scripts. > Thank Erich, this was exactly what I needed. I missed the 0x at the beginning of the io :-} Had me scratching my head why I could do it manually but the boot was not working for a while until I spotted the difference. Another question, is there a trick to getting the X-windows sounds going. I can play a sound 'play phone.wav' and I change the plugin in XMMS to the OSS driver and I can play a sound there but I cannot hear the sounds from the windows actions. Ken -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
