[Techtalk] KDE: the saga continues

[Raven Brooke]

nono, you haven't confused me, the log did  : )

I also expected some kind of communication regarding what was causing it 
to bail, that's why the silence after the sound problems seems so odd. 

When starting gnome, the message indicates that modprobe can't find 
sound-service, once, then continues with starting other services. The kde 
startup seems to continue looking for sound stuff then crash.

Is it possible that kde somehow relies on the sound modules in order to 
function?



On Mon, 29 Oct 2001, Rob Stevens wrote:

> Is there anything after this entry in your logfile?  All this is telling me
> is that you have a Via Apollo Chipset with an AC'97 Audio Codec chip.  Below
> what you pasted there might be an entry regarding kfm or other KDE programs.
> Sorry I didn't mean to confuse you, usually there is an entry in the log of
> impending death.
> 
> --
> Rob
> ----- Original Message -----
> From: "Raven Brooke" <rbrooke at maine.rr.com>
> To: <techtalk at linuxchix.org>
> Sent: Tuesday, October 30, 2001 4:37 AM
> Subject: [Techtalk] KDE: the saga continues
> 
> 
> >
> > I looked at the install log, no problems installing any packages in the
> > original 7.2 install (KDE was broken from the very beginning).
> >
> > I also checked the messages log which does indeed show some errors, but I
> > am not sure I see how they are related.
> >
> > Here is the logfile from just before KDE chokes.
> >
> > Oct 29 07:03:03 trinity xinetd[1330]: warning: can't get client address:
> Transport endpoint is not connected
> > Oct 29 07:03:12 trinity kernel: es1371: version v0.30 time 17:36:47 Sep  6
> 2001
> > Oct 29 07:03:12 trinity kernel: PCI: Found IRQ 9 for device 00:14.0
> > Oct 29 07:03:12 trinity kernel: PCI: Sharing IRQ 9 with 00:07.2
> > Oct 29 07:03:12 trinity kernel: PCI: Sharing IRQ 9 with 00:07.3
> > Oct 29 07:03:12 trinity kernel: IRQ routing conflict for 00:14.0, have irq
> 5, want irq 9
> > Oct 29 07:03:12 trinity kernel: es1371: found chip, vendor id 0x1274
> device id 0x1371 revision 0x06
> > Oct 29 07:03:12 trinity kernel: es1371: found es1371 rev 6 at io 0xe000
> irq 5
> > Oct 29 07:03:12 trinity kernel: es1371: features: joystick 0x0
> > Oct 29 07:03:12 trinity kernel: ac97_codec: AC97 Audio codec, id:
> 0x4352:0x5903 (Cirrus Logic CS4297)
> > Oct 29 07:03:12 trinity modprobe: modprobe: Can't locate module
> sound-service-0-0
> > Oct 29 07:03:12 trinity modprobe: modprobe: Can't locate module
> sound-slot-1
> > Oct 29 07:03:12 trinity modprobe: modprobe: Can't locate module
> sound-service-1-0
> > Oct 29 07:03:12 trinity modprobe: modprobe: Can't locate module
> sound-slot-1
> > Oct 29 07:03:12 trinity modprobe: modprobe: Can't locate module
> sound-service-1-0
> >
> >
> > So, could my problem be due to an IRQ conflict? It seems to continue from
> > that point tho, and only fails when it comes to the sound modules .. but
> > why would that cause the window manager to fail?
> >
> > I am more confused than ever now . . .
> >
> >
> > _______________________________________________
> > Techtalk mailing list
> > Techtalk at linuxchix.org
> > http://www.linuxchix.org/mailman/listinfo/techtalk
>