On Tue, May 10, 2005 at 12:35:54AM +0200, Nicolas FRANCOIS enlightened
us thusly
> Le Sat, 07 May 2005 17:18:13 -0500 Richard Snow
> <[EMAIL PROTECTED]> a �crit :
>
> > >Yes. It certainly isn't the alsa stuff. I think now it is more a
> question
> > >of graphic card. So I definitly am a szcrumlfbold for calling for
> > >help about sound when it has nothing to do with it. Gasp :-(
>
> Changed my mind again : seems now to be a kernel problem, or a
> hardware problem. Don't think it's a hardware one, having other Linux
> running on the same machine without problem.
>
> I had similar crashes under console, so DRI or XFree is out of the
> way. I experience problems when an application has to use the graphic
> card intensively : I went threw some errors playing graphic games, or
> listing a huge directory... So it may be a graphic card driver, a bus
> driver...
>
> It tried to strace applications doing nasty things to my system, but
> the errors wheren't logged (after the reboot, EVEN after activating
> Magic Keys :-(, so it looks like an instability of the hardware-kernel
> couple...
>
> Can you give me some clues to investigate ? The problem is new to me,
> that system ran succesfully previous versions of LFS, giving me entire
> satisfaction (the system AND LFS ;-).
>
> Thanks for any tip.
OK. Three tips
1. Don't send unzipped .config files around, as they waste
bandwidth, and trip your mail into spam folders (too many
capital letters).
2. Have you tried a framebuffer setup with vesa support? It's a
sort of common denominator system. On the bleeding edge
(LFS-SVN-20050412) expect and _enjoy_ the hardships. That's why
you are there, isn't it :-)?
3. With so much going wrong, start suspecting hardware. Clean
between cooling fins on the all heatsinks. (Unscrew the fan);
Try a memory check with memtest86.
>
> \bye
>
> PS1 : sorry for the cross-post, but I think now it is more a LFS
> problem than a BLFS one. For any reference, the initial thread is on
> BLFS list (under the name "Problem with sound" !
Nobody on LFS is going to advise you on X, DRI or Graphics cards. Isn't
all that stuff blfs?
>
> PS2 : I have a Athlon-XP Barton 2600+, 768Mo RAM, a ATI Radeon 9000
> Pro GC and a KT333 motherboard. LFS-SVN-20050412. And this is my last
> kernel .config :
Sounds very like my box. (Athlon 2600/KT400, 512MB, Athlon 7000 &
LFS-5.something). I never went near DRI, as I don't need it. Vesa
Framebuffer support works for me. I didn't read your .config, but I did
compare it with mine. You seem to have gone for all the hairy options,
and some of the obsolete ones (Have you ISA?? PCMCIA??). You seem to
have compiled everything in whereas I have modules. These you can give
options to.
Are you booting with the acpi=off noapic options? You need them, because
the Via apic hardware is ghastly and broken. cat /proc/interrupts (If
you have /proc) or do the equivelant. Have your interrupts predictable
numbers. Here's my (fairly kosher) set
[EMAIL PROTECTED] ~/Mail]$ cat /proc/interrupts
[EMAIL PROTECTED] ~/Mail]$ cat /proc/interrupts
CPU0
0: 801218 XT-PIC timer
1: 41164 XT-PIC keyboard
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
11: 1001 XT-PIC eth0
12: 19511 XT-PIC PS/2 Mouse
14: 9033 XT-PIC ide0
15: 1 XT-PIC ide1
NMI: 0
ERR: 0
If I allow apic, everything gets irq 10 or 11, 24 irqs are allowed which
many things don't like and life is messy. THINGS DON'T WORK. Something
that would be happy on irq 10 or 11 (e.g. the nic) gets some half-assed
irq number, so it goes around thinking it's a sound card :-/, and the
sound sends everything to the nic :-/.
--
With Best Regards,
Declan Moriarty.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
