[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

ATI RS350 chipset



I just put together a system with a Gigabyte GA-8TRS350MT board; this
has what it calls the ATI RS350 chipset.  It's a pretty nice board
and (so I thought) not particularly new, but it seems to be a bit
ahead of current kernel support.  I figured I'd post a note in case
anything is searching

Here's an lspci:

00:00.0 Host bridge: ATI Technologies Inc: Unknown device 7833
00:01.0 PCI bridge: ATI Technologies Inc: Unknown device 7838
00:13.0 USB Controller: ATI Technologies Inc: Unknown device 4367 (rev 01)
00:13.1 USB Controller: ATI Technologies Inc: Unknown device 4368 (rev 01)
00:13.2 USB Controller: ATI Technologies Inc: Unknown device 4365 (rev 01)
00:14.0 SMBus: ATI Technologies Inc: Unknown device 4363 (rev 03)
00:14.1 IDE interface: ATI Technologies Inc: Unknown device 4369 (rev 01)
00:14.2 IDE interface: ATI Technologies Inc: Unknown device 436e (rev 01)
00:14.3 ISA bridge: ATI Technologies Inc: Unknown device 436c (rev 01)
00:14.4 PCI bridge: ATI Technologies Inc: Unknown device 4362 (rev 01)
00:14.5 Multimedia audio controller: ATI Technologies Inc: Unknown device 4361 (rev 03)
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 9100 PRO IGP
02:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

I checked the curent PCI ID list on sourceforge and these aren't
listed; I'd add them myself but I have no idea what to call them.

FC2 (which I currently have rolled out on 200 machines) didn't install
it all.  FC3 did install, but the IDE was dog slow and required a
little kernel patch for chipset recognition.  kernel-2.6.10-1.1056_FC4
added support for that.  (This is bug 142647.)

Graphics seem to work under FC3 well enough.  I haven't tried 3D stuff
yet.  I can switch to text consoles but when I do a shutdown (with X
running) the screen goes completely dark until the machine reboots.

USB support works for mice but when I use a plain USB2 memory thingy
(any of several models I have laying around) things don't work so
well.  Upon inserting the device (with this morning's
kernel-2.6.10-1.1063_FC4) I see:

usb 3-3: new low speed USB device using ohci_hcd and address 2
ohci_hcd 0000:00:13.1: Unlink after no-IRQ?  Different ACPI or APIC settings may help.

which is a bit more helpful than earlier kernels.  lsusb at this point
hangs.  Booting with noapic doesn't help; then I get this:

usb 3-3: new full speed USB device using ohci_hcd and address 2
usb 3-3: device descriptor read/64, error -110
usb 3-3: device descriptor read/64, error -110
usb 3-3: new full speed USB device using ohci_hcd and address 3
usb 3-3: device descriptor read/64, error -110
usb 3-3: device descriptor read/64, error -110
usb 3-4: new low speed USB device using ohci_hcd and address 4

and lsusb still hangs.  acpi=off gives the same.  This is not yet in
bugzilla; I'll keep experimenting and file a complete bug once I've
trolled through the BIOS settings.

I haven't tried sound yet.

If anyone has any suggestions, I'd sure appreciate them.

 - J<


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]