ke4nt1

Group: Members
Posts: 2329
Joined: Oct. 2003 |
 |
Posted: Sep. 01 2004,07:10 |
 |
waa waa waa, 
I read somewhere that the esstype line should only be "1" ( one ) if you are using the old 16xx series.. Otherwise , use esstype=0 for the 17xx, 18xx, and 19xx series cards..
Try this... " modprobe sb o=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 esstype=0 " ...if this returns a prompt without errors listed, then try " modprobe opl3 " ...that should fill your 0x388 spot....
If these work for you, than try placing these lines in your "/opt/bootlocal.sh" file..
If running from frugal, or Live CD , make sure to backup before reboot with the "/opt/bootlocal" line in your "/home/dsl/filetool.lst"
Then you'll never have to type these in again..
Please share with us where the esstype=1788 came from. Perhaps you've seen something I'd like to read !
73 ke4nt
|