Hi,
I just did a fresh install of the 3.0 i386 distribution (due
to
circumstances..)
on my amd64 machine. This combination "used to
work" like a charm
under 2.0, 2.02 and 3.0BETA, but now I'm (out of the blue)
experiencing
similar quircks as Anne:
Starting X a second time (as in typing startx, leaving X and
typing startx
again) results in a hard hang - including the front power
switch
becoming unresponsive. The last log entries in my
XFree86.0.log are:
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Loading /usr/X11R6/lib/modules/libi2c.a
(II) Module i2c: vendor="The XFree86 Project"
compiled for 4.5.0, module version = 1.2.0
ABI class: XFree86 Video Driver, version 0.8
(II) RADEON(0): I2C bus "DDC" initialized.
(II) RADEON(0): I2C device "DDC:ddc2" registered
at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 2, Detected Type: 3
(II) RADEON(0): I2C device "DDC:ddc2" registered
at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered
at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered
at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 3, Detected Type: 0
(II) RADEON(0): DDC Type: 4, Detected Type: 0
(constantly syncing the fs helps in getting these at all)
Normally my suggestion would be to follow up on this issue
on a different
mailing list, however, another *athlon* system, also with a
new, stock 3.0
install, does NOT have this problem (the videocard is a
different ATI
one, but
I could try to swap to see if it makes any difference)
relevant parts of the dmesg output:
NetBSD 3.0 (GENERIC) #0: Mon Dec 19 01:04:02 UTC 2005
builds works.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/i
386/200512182024Z-obj/home/builds/ab/netbsd-3-0-RELEASE/src/
sys/arch/i386/compile/GENERIC
total memory = 1023 MB
avail memory = 993 MB
BIOS32 rev. 0 found at 0xfb8b0
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD Unknown K7 (Athlon) (686-class), 2010.14 MHz, id
0xfc0
cpu0: features
78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR&
gt;
cpu0: features 78bfbff<PGE,MCA,CMOV,PAT,PSE36,MPC,MMX>
cpu0: features 78bfbff<FXSR,SSE,SSE2>
cpu0: "AMD Athlon(tm) 64 Processor 3000+"
vga1 at pci1 dev 0 function 0: ATI Technologies Radeon 7500
(rev. 0x00)
and
NetBSD 3.0 (GENERIC) #0: Mon Dec 19 01:04:02 UTC 2005
buildsworks.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/i
386/200512182024Z-obj/home/builds/ab/netbsd-3-0-RELEASE/src/
sys/arch/i386/compile/GENERIC
total memory = 511 MB
avail memory = 492 MB
BIOS32 rev. 0 found at 0xf1960
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD Athlon XP 2400+ (686-class), 1990.32 MHz, id 0x681
cpu0: features
c3c3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR
>
cpu0: features
c3c3fbff<PGE,MCA,CMOV,PAT,PSE36,MMXX,MMX>
cpu0: features c3c3fbff<FXSR,SSE,3DNOW2,3DNOW>
cpu0: "AMD Athlon(TM) XP 2400+"
cpu0: I-cache 64 KB 64B/line 2-way, D-cache 64 KB 64B/line
2-way
cpu0: L2 cache 256 KB 64B/line 16-way
cpu0: ITLB 16 4 KB entries fully associative, 8 4 MB entries
fully
associative
cpu0: DTLB 32 4 KB entries fully associative, 8 4 MB entries
4-way
cpu0: 8 page colors
vga1 at pci1 dev 0 function 0: ATI Technologies Radeon
7000/VE (rev. 0x00)
Anyone else with an AMD64 cpu and ATI video card
experiencing similar
problems? or am I on the wrong track here?
regards, Theo
|
Hi,
I just did some swapping of videocards, and found that the
problem
is NOT AMD64 specific, and that I can faithfully reproduce
hangs on
both machines with both videocards.
Normally I have my TFT connected using a DVI cable AND using
an
analogue cable through a KVM to the same cards' vga output.
This
set-up allows me to quickly switch between machines, while
still having
the benefits of the digital interface when I need them
(switching between
digital and anologue inputs through the monitors' control
pannel /all/ the
time is a nuisance)
As it turns out, having both video-card outputs connected
at the same
time is what causes the crashes, and in this respect it does
not matter if
monitors are TFT or CRT or if they are switched on at all,
and the exact
point where X dies (fiddling with I2C and DDCs) makes me
quite certain
that (al least my) problems are radeon driver related.
As I basically have a mono-head set up, I don't know if
these problems
also occur when configuring a proper dual head/Xinerama
system.
I guess it's back to google again...
regards, Theo
theo borm wrote:
> Hi,
>
> I just did a fresh install of the 3.0 i386 distribution
(due to
> circumstances..)
> on my amd64 machine. This combination "used to
work" like a charm
> under 2.0, 2.02 and 3.0BETA, but now I'm (out of the
blue) experiencing
> similar quircks as Anne:
>
> Starting X a second time (as in typing startx, leaving
X and typing
> startx
> again) results in a hard hang - including the front
power switch
> becoming unresponsive.
> Anyone else with an AMD64 cpu and ATI video card
experiencing similar
> problems? or am I on the wrong track here?
>
> regards, Theo
|