[PlanetCCRMA] problems reverting from edge: sound is gone

Fernando Lopez-Lezcano nando@ccrma.Stanford.EDU
Wed Feb 8 12:23:01 2006


On Wed, 2006-02-08 at 13:37 +0000, mp wrote:
> INTRO:
> I had/have serious problems with sound, occurred after upgrading to
> 2.6.x kernel/Alsa and has been increasing until suddenly recently it
> meant that the machine started crashing. Original bug report filed here:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139927
> 
> More on that below, pasted from a comment in the above mentioned bug.
> 
> ISSUE:
> I tried the FC4 CCRMA kernel and it worked well - sound was better-,
> which made me daring and I wanted to test Molnar's "edge" kernel. I
> enabled the repository and did:
> 
> apt-get install planetccrma-core-edge
> 
>  - but that was no good and sound was completely dead. So I did:
> 
> apt-get remove planetccrma-core-edge
> 
> HOwever, the packaged that was installed as dependencies from the edge
> repo to satisfy the edge kernel remain - only the actual kernel package
> was removed - and the sounds is now dead in the "original" FC4 CCRMA
> kernel too :(
> 
> QUESTION:
> 
> Is there a way that I can revert back to the standard FC4 CCRMA kernel
> via apt-get? 

Hmmm, it should not really be necessary as the original kernel remains,
as you probably know. 

Maybe it is a setting in the mixer state that lingers. You could try
erasing /etc/asound.state and redoing your mixer under the original FC4
kernel. 

> Is there a way that I can manually trace which packages
> were updates/installed as part of the edge upgrade and then manually
> remove tham and return to the state of affairs of the standard FC4 CCRMA
> kernel??  Any help would be greatly appreciated - sound is essential for
> my computer use

You could reinstall the planetccrma-core-edge package and do a:
   rpm -q --requires planetccrma-core-edge
That will tell you what other packages and version the "edge" thingy
requires. 

-- Fernando

> -----------------
> ps: It seems that the original sounds bug has to do with:
> 
> "Short version: (Some?) SBLives on certain motherboards cause bus
> problems (even corruption!) and VIA/Creative point fingers at each other
> as to whose fault it was (here's a hard won link where VIA points at
> Creative
> http://web.archive.org/web/20040202025440/http://www.viaarena.com/?PageID=26 ).
> More links:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0201.3/1079.html
> (kernel mailing list including work arounds later in the thread) and
> here: http://alive.singnet.com.sg/tech/click.htm (talks about the
> different ways the problems manifest and workarounds) and possibly bug
> #53803 too.
> 
> -----------------
> 
> root@paz ~]# lspci
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
> (rev 02)
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
> 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
> (rev 22)
> 00:07.1 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
> 00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 10)
> 00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 10)
> 00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
> 30)
> 00:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
> 08)
> 00:09.1 Input device controller: Creative Labs SB Live! MIDI/Game Port
> (rev 08)
> 00:0b.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
> (rev 43)
> 00:0d.0 USB Controller: NEC Corporation USB (rev 43)
> 00:0d.1 USB Controller: NEC Corporation USB (rev 43)
> 00:0d.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
> 00:13.0 Mass storage controller: Triones Technologies, Inc.
> HPT366/368/370/370A/372/372N (rev 03)
> 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO
> AGP 4x TMDS
>