[ If you want to make sure that your messages show up in the correct
thread then you have to provide In-Reply-To headers. With your webmail
interface it is probably best to use "Reply-To-All" and then to remove
the email address of the original poster and to shift the list address
from "Cc:" to "To:". ]
On Fri, Apr 13, 2007 at 10:08:58 -0700, Pat Primate wrote:
> Thank you Florian and Kamaraju, I am impressed by the speed and
> helpfulness of the Debian-Users mailing list :) As for my system, I am
> completely up to date (clean install of 4.0r0) and the crash doesn't
> happen in the tty1 terminals, Only inside KDE/X11. I checked the bell
> settings in Konsole (settings ---> bell) and it was set to System bell
> and not visual bell, BUT (the good news) I tried setting the bell
> settings to 'system notification', 'visual bell', and 'none' and all
> three of those settings allow me to use konsole with NO CRASHES :D So
> it seems that the crashes only happen when the bell setting is set to
> 'system bell', but the funny thing is that I don't actually hear the
> bell beep, the crash happens first (even though my sound SEEMS to work
> fine for other things).
I would also go to "K-Menu > Control Center > Sound & Multimedia >
System Bell" and check the settings there. I don't know which other
parts of KDE might want to use the system bell but it cannot hurt to
make sure it is deactivated for all of KDE.
> So here are the attachments you wanted me to add, if you could help me
> figure out where to file a bug report and what info to include I would
> be very grateful :)
It looks like your X setup is OK as far as the graphics card is
concerned (see my remarks below). Maybe the problem is in some weird way
related to the pcspkr module which controls the system bell. You could
try to (un)load the module and see if that makes any difference. The
whole thing might be a very rare coincidence of several factors;
tracking it down might be difficult and not really worth it.
[...]
> 1) lspci | egrep -i 'vga|display|video|graphics
>
> 00:02.0 VGA compatible controller: Intel Corporation Mobile
> 915GM/GMS/910GML Express Graphics Controller (rev 04) 00:02.1 Display
> controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics
> Controller (rev 04)
>
> --------------------------------------
>
> 2) awk '/Section "(Device|Module)"/,/EndSection/' /etc/X11/xorg.conf
>
> Section "Module"
> Load "i2c"
> Load "bitmap"
> Load "ddc"
> Load "dri"
> Load "extmod"
> Load "freetype"
> Load "glx"
> Load "int10"
> Load "vbe"
> EndSection
> Section "Device"
> Identifier "Intel Corporation Mobile 915GM/GMS/910GML
> Express Graphics Controller"
> Driver "i810"
> BusID "PCI:0:2:0"
> EndSection
All is fine as far as I can tell.
> ------------------------------------------------------
>
> 3) patop:/home/pat# egrep '^\((EE|WW)\)' /var/log/Xorg.0.log
>
> (WW) The directory "/usr/X11R6/lib/X11/fonts/misc" does not exist.
[ snip: similar errors for other font directories ]
You can comment out these paths in the "Files" section of your xorg.conf
to make these (harmless) warnings go away.
> (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
I see the same here (Intel Q965 chipset) and I never noticed any problem arising
from it.
> (WW) I810(0): Bad V_BIOS checksum
> (WW) I810(0): Bad V_BIOS checksum
> (WW) I810(0): config file hsync range 43.8857-48.5053kHz not within
> DDC hsync ranges.
> (WW) I810(0): Bad V_BIOS checksum
> (WW) I810(0): Extended BIOS function 0x5f05 failed.
My laptop (Intel 855GM chipset) works without trouble in spite of
similar "Bad V_BIOS" and "Extended BIOS function ..." warnings. I think
these are symptoms of minor glitches of the driver.
You have to adjust the values in the "Monitor" section of xorg.conf if
you want to get rid of the "hsync range" message.
> (WW) AIGLX: 3D driver claims to not support visual 0x23
[ snip: the same for other visuals ]
Same story: I get these warnings too and I never had problems. I guess
these messages will go away once AIGLX support for the Intel chipsets
has matured a bit more.
--
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
