Bug 17694 - Won't configure ALi M5451 PCI South Bridge Audio
Summary: Won't configure ALi M5451 PCI South Bridge Audio
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: alpha
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-09-19 15:56 UTC by Richard D. Payne
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-10-19 12:02:40 UTC
Embargoed:


Attachments (Terms of Use)
Enable trident sound driver when CONFIG_ALPHA_GENERIC (1.22 KB, patch)
2000-09-21 13:52 UTC, Richard D. Payne
no flags Details | Diff

Description Richard D. Payne 2000-09-19 15:56:09 UTC
sndconfig reports that the ALi M5451 PCI South Bridge Audio is not
supported. However
support is provided by the trident audio driver in 2.2.16 and later. Here's
the entry from
/etc/sysconfig/hwconf

class: AUDIO
bus: PCI
detached: 0
driver: unknown
desc: "Acer Laboratories Inc. [ALi]|M5451 PCI South Bridge Audio"
vendorId: 10b9
deviceId: 5451
subVendorId: 10b9
subDeviceId: 5451
pciType: 1

This sould chip is included on the API UP1100 motherboard.

Comment 1 Richard D. Payne 2000-09-19 15:58:35 UTC
platform should be alpha

Comment 2 Richard D. Payne 2000-09-21 13:52:07 UTC
Created attachment 3483 [details]
Enable trident sound driver when CONFIG_ALPHA_GENERIC

Comment 3 Richard D. Payne 2000-09-21 13:52:55 UTC
I've attached a patch against 2.2.16-24 that enables the trident audio driver
whent he kernel
type is GENERIC, before this would only work is the kernel type was Nautilus.

Comment 4 Bill Nottingham 2000-10-19 05:38:17 UTC
Oops, we mapped the *other* version of the ALI bridge in
the pcitable. Fixed in CVS of kudzu, will be in next build.

Assigning to the kernel for the kernel patch.

Comment 5 Richard D. Payne 2000-10-19 12:02:35 UTC
FWIW, the patch has been accepted for 2.2.18.

Comment 6 Phil Copeland 2001-06-04 16:53:38 UTC
Is this issue still unresolved?


Comment 7 Richard D. Payne 2001-06-04 19:30:43 UTC
detection seems to be fixed with 7.1RC1.


Note You need to log in before you can comment on or make changes to this bug.