Bug 15956

Summary: sndconfig has to run twice on NeoMagic MagicMedia 256 ZX
Product: [Retired] Red Hat Linux Reporter: Dan Taylor <daniel_a_taylor>
Component: kernelAssignee: Alan Cox <alan>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: mick_tantasirikorn
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-08-11 16:21:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
lsmod before
none
lsmod after 1
none
lsmod after 2 none

Description Dan Taylor 2000-08-10 21:54:36 UTC
Dell Latitude CSx 
(using the NeoMagic MagicMedia 256 ZX chipset)

After installing by booting to the CD, sndconfig has to be run twice for 
the sound to work (this error was duplicated on multiple installs).

After installing by booting from a floppy(bbot.img), sndconfig only has to 
be run once to get sound working.

Comment 1 Bill Nottingham 2000-08-11 03:04:30 UTC
Odd. What's in /etc/modules.conf after an install
but *before* you run sndconfig?

In the cases where you have to run it twice, what's
the error you get the first time?

Comment 2 Dan Taylor 2000-08-11 14:49:17 UTC
Created attachment 2396 [details]
lsmod before

Comment 3 Dan Taylor 2000-08-11 14:50:15 UTC
In the cases where I have to run the sndconfig twice, there are no error 
messages.  I am able to hear the test sound the first time it is run, but 
afterwards when attempting to #play a sound, it pauses for a second & acts like 
it is playing, but no sound is emitted.  In addition, on this last test case, 
after I ran sndconfig the second time & accepted the changes, the system hard 
locked.  I am including the lsmod data & the /etc/modules.conf data for 
the 'before sndconfig', the 'after 1st sndconfig', & 'after 2nd sndconfig'.  
Note that some of the lsmod data on the last one is different due to the lockup 
& the fact we had to hard boot the machine.



Comment 4 Dan Taylor 2000-08-11 14:52:16 UTC
Created attachment 2397 [details]
lsmod after 1

Comment 5 Dan Taylor 2000-08-11 14:53:45 UTC
Created attachment 2398 [details]
lsmod after 2

Comment 6 Dan Taylor 2000-08-11 15:00:11 UTC
***modules.conf-before***
alias parport_lowlevel parport_pc
alias usb-controller usb-uhci

***modules.conf-after-1***
alias parport_lowlevel parport_pc
alias usb-controller usb-uhci
alias sound-slot-0 nm256

***modules.conf-after-2***
alias parport_lowlevel parport_pc
alias usb-controller usb-uhci
alias sound-slot-0 nm256



Comment 7 Bill Nottingham 2000-08-11 16:21:09 UTC
Ugly. Alan, are you aware of any issues with the nm256 driver?