Hi, It seems quite odd, but I´m unable to get sound out of my Powermac Running the new SuSE7.3 PPC with improved Sound support.... Well I tried all methods I have been applying to such problems since SuSE 7.0 x86, no avail. If I try 'modprobe dmasound' or 'modprobe dmasound_pmac' Linux says it cant find the module 'dmasound', although I found it under /lib/modules/2.4.12/kernel/sound/dmasound. Same with 'insmod awacs' etc. Since SuSE claims the capabilities of yast 2 I tried a new installation completely using YAST2. Yast 2 detects my souns system as snd0burgundy. But when it comes to the point it should start th sounddriver there is a sort *knack* and the whole System is frozen, no mousemovement no console, no ssh... ..the File mdules.conf is totally scrambled, somtimes rc.config as well. ALSAconf detects my soundchip as 'Awacs' makes some entries in modules.conf but when it wants to start the sound driver .... Same as Yast2 see above. Has anyone got a running soundsyste on a PowerMac G3 B&W ? Do you know what to do? Thanks Thomas
Hi, I am running SuSE 7.1/PPC on my PowerBase 200 machine using the default 2.2.18 kernel, but encountered the following resource conflict when I wanted to activated my network card (Farallon PCI-10, DEC 21041 chipset) yesterday: As soon as the network card is activated, X still starts up, but immediately afterwards crashes the machine completely. This does not happen on the framebuffer console however. I suspect it is due to the resource conflict reported by XFree86 (see log/lspci output below): (WW) ****INVALID IO ALLOCATION**** b: 0x400 e: 0x4ff correcting Is there a way to avoid this conflict? As far as I understood it, there actually is only one IO space on PowerPCs. Various MacOS versions managed to handle this conflict in exactly this configuration for more than 3 years now :-) What I tried so far, but did not help: - changing from the de4x5 driver to the tulip driver (SuSE 2.2.18 sources). - using the SuSE kernel 2.4.2: X refuses to start up immediately following the IO allocation warning. - upgrading to the latest SuSE kernel 2.4.12 or 2.4.16-3: It did not even boot, but froze after the line "Uniform CD-ROM driver ...". The LED light of my SCSI CD writer (Teac CD-R55S) just stayed on forever. Right now, I thus can either choose to use X or my ethernet card... Any help would be appreciated! Thanks, Markus ---------------------------------------------------------------------- XFree86 log: XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) ... (--) PCI: (0:17:0) ATI Mach64 GT rev 65, Mem @ 0x81000000/24, 0xfffff000/12, I/O @ 0x0400/8 (**) FBDev(0): claimed PCI slot 0:17:0 (II) FBDev(0): using default device (WW) ****INVALID IO ALLOCATION**** b: 0x400 e: 0x4ff correcting (**) FBDev(0): Depth 15, (--) framebuffer bpp 16 (==) FBDev(0): RGB weight 555 (==) FBDev(0): Default visual is TrueColor (==) FBDev(0): Using gamma correction (1.0, 1.0, 1.0) (II) FBDev(0): Hardware: ATY Mach64 (vidmem: 4092k) (==) FBDev(0): Option ShadowFB is on (II) FBDev(0): Checking Modes against framebuffer device... (II) FBDev(0): mode "1152x864" ok (II) FBDev(0): Checking Modes against monitor... (--) FBDev(0): Virtual size is 1152x864 (pitch 1152) (**) FBDev(0): Default mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz (==) FBDev(0): DPI set to (75, 75) ---------------------------------------------------------------------- lspci -vv: 00:0b.0 Host bridge: Apple Computer Inc. Bandit PowerPC host bridge (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- Latency: 32, cache line size 08 00:0e.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 21) Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 96 Interrupt: pin A routed to IRQ 25 Region 0: I/O ports at 0400 Region 1: Memory at 80800000 (32-bit, non-prefetchable) [disabled] Expansion ROM at 80840000 [disabled] 00:10.0 Class ff00: Apple Computer Inc. O'Hare I/O (rev 01) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+ Latency: 32, cache line size 08 Region 0: Memory at f3000000 (32-bit, non-prefetchable) 00:11.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 41) (prog-if 00 [VGA]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (2000ns min), cache line size 08 Interrupt: pin A routed to IRQ 22 Region 0: Memory at 81000000 (32-bit, non-prefetchable) Region 1: I/O ports at 0400 [disabled] Region 2: Memory at <ignored> (32-bit, non-prefetchable) ---------------------------------------------------------------------- email: mlischka@physik.tu-muenchen.de Markus Lischka www : http://www.ph.tum.de/~mlischka Physics Department T30 phone: (0 89) 2 89-1 43 30 James-Franck-Str. 1 fax : (0 89) 2 89-1 22 96 D-85747 Garching ----------------------------------------------------------------------
On Wed, Dec 05, Markus Lischka wrote:
Hi,
I am running SuSE 7.1/PPC on my PowerBase 200 machine using the default 2.2.18 kernel, but encountered the following resource conflict when I wanted to activated my network card (Farallon PCI-10, DEC 21041 chipset) yesterday:
As soon as the network card is activated, X still starts up, but immediately afterwards crashes the machine completely. This does not happen on the framebuffer console however. I suspect it is due to the resource conflict reported by XFree86 (see log/lspci output below): (WW) ****INVALID IO ALLOCATION**** b: 0x400 e: 0x4ff correcting
Is there a way to avoid this conflict? As far as I understood it, there actually is only one IO space on PowerPCs. Various MacOS versions managed to handle this conflict in exactly this configuration for more than 3 years now :-)
Can you try the 2.4.2 kernel? It should work with that kernel, known bug in the 2.2 ati kernel driver. Boot the file vmlinux-2.4 and install k_deflt.rpm from CD1/suse/images. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Can you try the 2.4.2 kernel? It should work with that kernel, known bug in the 2.2 ati kernel driver. That's what I actually tried first. The IO port allocation seems to be different to the 2.2.18 kernel with the net effect that X does not start up at all (it somehow still tries to use the IO ports at 0400). FYI, I attach both lspci and XFree output using 2.4.2 below. The good thing is that you cannot crash your machine anymore ;-)
Anyway, I finally managed to boot the 2.4.16 beta kernel from ftp.suse.com. This version indeed manages to properly reassign the IO ports and X starts up :-) What's strange though is that I had to swap the order of my SCSI CD-ROM (NEC CDR-1410A) and my CD-RW (Teac CD-R55S) on the SCSI bus to boot the 2.4.16 kernel. Both configurations were properly terminated, and worked with MacOS 8.x, Linux 2.2.18 or 2.4.2 without any problems. If the CD-ROM is the terminating device on the SCSI bus (my setup for the last three years), the 2.4.16 kernel however just stops the booting sequence with the messages <4>Attached scsi CD-ROM sr0 at scsi1, channel 0, id 3, lun 0 <4>Attached scsi CD-ROM sr1 at scsi1, channel 0, id 4, lun 0 <4>sr0: scsi-1 drive <6>Uniform CD-ROM driver Revision: 3.12 and the LED of the CD-RW stays on forever. Terminating the bus with the CD-RW, everything is fine. I have no idea whatsoever causes this behaviour and whether this is actually related to the Teac CD-RW. Thanks for your help and keep up the good work! Markus ------------------------------------------------------------------------------ lspci -v (using SuSE kernel 2.4.2): 00:0b.0 Host bridge: Apple Computer Inc. Bandit PowerPC host bridge (rev 03) Flags: bus master, medium devsel, latency 32 00:0e.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 21) Flags: bus master, medium devsel, latency 96, IRQ 25 I/O ports at 0400 [size=128] Memory at 80800000 (32-bit, non-prefetchable) [disabled] [size=128] Expansion ROM at 80840000 [disabled] [size=256K] 00:10.0 Class ff00: Apple Computer Inc. O'Hare I/O (rev 01) Flags: bus master, medium devsel, latency 32 Memory at f3000000 (32-bit, non-prefetchable) [size=512K] 00:11.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 41) (prog-if 00 [VGA]) Flags: bus master, stepping, medium devsel, latency 32, IRQ 22 Memory at 81000000 (32-bit, non-prefetchable) [size=16M] I/O ports at <ignored> [disabled] [size=256] Memory at 10000000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at <unassigned> [disabled] [size=128K] ------------------------------------------------------------------------------ XFree86 log (using SuSE kernel 2.4.2): XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) ... (--) PCI: (0:17:0) ATI Mach64 GT rev 65, Mem @ 0x81000000/24, 0x10000000/12, I/O @ 0x0400/8 (**) FBDev(0): claimed PCI slot 0:17:0 (II) FBDev(0): using default device (WW) ****INVALID IO ALLOCATION**** b: 0x400 e: 0x4ff correcting^G (EE) FBDev(0): xf86RegisterResources() found resource conflicts (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found ------------------------------------------------------------------------------ lspci -v (using SuSE kernel 2.4.16-3): 00:0b.0 Host bridge: Apple Computer Inc. Bandit PowerPC host bridge (rev 03) Flags: bus master, medium devsel, latency 32 00:0e.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 21) Flags: bus master, medium devsel, latency 96, IRQ 25 I/O ports at 0400 [size=128] Memory at 80800000 (32-bit, non-prefetchable) [disabled] [size=128] Expansion ROM at 80840000 [disabled] [size=256K] 00:10.0 Class ff00: Apple Computer Inc. O'Hare I/O (rev 01) Flags: bus master, medium devsel, latency 32 Memory at f3000000 (32-bit, non-prefetchable) [size=512K] 00:11.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 41) (prog-if 00 [VGA]) Flags: bus master, stepping, medium devsel, latency 32, IRQ 22 Memory at 81000000 (32-bit, non-prefetchable) [size=16M] I/O ports at 1000 [size=256] Memory at f3080000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at <unassigned> [disabled] [size=128K]
On Wed, Dec 05, Thomas Ruschival wrote:
Hi,
It seems quite odd, but I´m unable to get sound out of my Powermac Running the new SuSE7.3 PPC with improved Sound support.... Well I tried all methods I have been applying to such problems since SuSE 7.0 x86, no avail. If I try 'modprobe dmasound' or 'modprobe dmasound_pmac' Linux says it cant find the module 'dmasound', although I found it under /lib/modules/2.4.12/kernel/sound/dmasound. Same with 'insmod awacs' etc. Since SuSE claims the capabilities of yast 2 I tried a new installation completely using YAST2. Yast 2 detects my souns system as snd0burgundy. But when it comes to the point it should start th sounddriver there is a sort *knack* and the whole System is frozen, no mousemovement no console, no ssh... ..the File mdules.conf is totally scrambled, somtimes rc.config as well. ALSAconf detects my soundchip as 'Awacs' makes some entries in modules.conf but when it wants to start the sound driver .... Same as Yast2 see above.
Has anyone got a running soundsyste on a PowerMac G3 B&W ? Do you know what to do?
I will try to reproduce and fix it, our G4 with G3 motherboard crashed as well. You could use 'modprobe dmasound_pmac' for the time being. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
On Wed, Dec 05, Thomas Ruschival wrote:
Hi,
It seems quite odd, but I´m unable to get sound out of my Powermac Running the new SuSE7.3 PPC with improved Sound support.... Well I tried all methods I have been applying to such problems since SuSE 7.0 x86, no avail. If I try 'modprobe dmasound' or 'modprobe dmasound_pmac' Linux says it cant find the module 'dmasound', although I found it under /lib/modules/2.4.12/kernel/sound/dmasound. Same with 'insmod awacs' etc. Since SuSE claims the capabilities of yast 2 I tried a new installation completely using YAST2. Yast 2 detects my souns system as snd0burgundy. But when it comes to the point it should start th sounddriver there is a sort *knack* and the whole System is frozen, no mousemovement no console, no ssh... ..the File mdules.conf is totally scrambled, somtimes rc.config as well. ALSAconf detects my soundchip as 'Awacs' makes some entries in modules.conf but when it wants to start the sound driver .... Same as Yast2 see above.
Has anyone got a running soundsyste on a PowerMac G3 B&W ? Do you know what to do?
Bug found and fixed. You can either recompile the kernel with this patch for wait for the newer binaries: ftp.suse.com/pub/suse/ppc/kernel/2.4.16/ diff -urN linux_ppc.orig/arch/ppc/kernel/pmac_feature.c linux_ppc/arch/ppc/kernel/pmac_feature.c --- linux_ppc.orig/arch/ppc/kernel/pmac_feature.c Wed Dec 19 18:15:28 2001 +++ linux_ppc/arch/ppc/kernel/pmac_feature.c Sun Jan 6 16:12:59 2002 @@ -525,6 +525,13 @@ struct macio_chip* macio; unsigned long flags; + /* B&W G3 and Yikes don't support that properly (the + * sound appear to never come back after beeing shut down). + */ + if (pmac_mb.model_id == PMAC_TYPE_YOSEMITE || + pmac_mb.model_id == PMAC_TYPE_YIKES) + return 0; + macio = macio_find(node, 0); if (!macio) return -ENODEV; Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
participants (3)
-
Markus Lischka -
Olaf Hering -
Thomas Ruschival