Jurij Smakov <[EMAIL PROTECTED]> writes:
> Thanks for testing. Can you try tweaking you X configuration file as
> described in http://forums.gentoo.org/viewtopic-t-288023.html, and see
> if it helps in any way with the mouse problem?
The only difference between the mouse section given there and mine is
that the one I'm using under 2.6.8 has the extra lines:
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
I'll try taking them out for next time I boot, but the gentoo config
seems to be with x.org, not the debian stable server. The kernel
mouse messages look the same as for 2.6.8. It's a USB mouse, of
course.
> Garbled screen in console sounds like framebuffer problems.
Yes, it's after it (I assume) switches to the framebuffer, as I should
have made clear.
> What videocard are you using?
It's (I assume) the normal one for blade 100. lspci says
:00:13.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
I should have thought to paste them before, but the relevant (?)
kernel messages for 2.6.12 are:
atyfb: 3D RAGE XL (Mach64 GR, PCI-33MHz) [0x4752 rev 0x27]
atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 230 MH z PLL, 83 Mhz MCLK, 63 MHz
XCLK
Console: switching to colour frame buffer device 160x64
atyfb: fb0: ATY Mach64 frame buffer device on PCI
and 2.6.11:
atyfb: 3D RAGE XL (Mach64 GR, PCI-33MHz) [0x4752 rev 0x27]
atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 230 MH z PLL, 83 Mhz MCLK, 63 MHz
XCLK
atyfb: setting up CRTC
atyfb: set primary CRT to 1280x1024 NN composite N
atyfb: CRTC_H_TOTAL_DISP: 9f00d2
atyfb: CRTC_H_SYNC_STRT_WID: 3201a3
atyfb: CRTC_V_TOTAL_DISP: 3ff0429
atyfb: CRTC_V_SYNC_STRT_WID: 230400
atyfb: CRTC_OFF_PITCH: 2800
atyfb: CRTC_VLINE_CRNT_VLINE: 0
atyfb: CRTC_GEN_CNTL: b000200
atyfb: atyfb_set_par
atyfb: Set Visible Mode to 1280x1024-8
atyfb: Virtual resolution 1280x6521, pixclock_in_ps 7444 (calculated 7444)
atyfb: Dot clock: 134 MHz
atyfb: Horizontal sync: 79 kHz
atyfb: Vertical refresh:74 Hz
atyfb: x style: 134.2504 1280 1313 1457 1688 1024 1025 1028 1066
atyfb: fb style: 7444 231 1280 33 144 38 1024 1 3
debug atyfb: Mach64 non-shadow register values:
debug atyfb: 0x2000: 009F00D2 003201A3 03FF0429 00230400
debug atyfb: 0x2010: 018B 2800 0840 0B002200
debug atyfb: 0x2020: 002A0776 02400731
debug atyfb: 0x2030: 00110202 C001
debug atyfb: 0x2040:
debug atyfb: 0x2050:
debug atyfb: 0x2060: FF0F
debug atyfb: 0x2070: 01003200 0005
debug atyfb: 0x2080: 0001
debug atyfb: 0x2090: 00803000 0100
debug atyfb: 0x20A0: 7B23A040 0104 E5000C81
debug atyfb: 0x20B0: 10151A3B 0001 0001
debug atyfb: 0x20C0: 00FF 86010182
debug atyfb: 0x20D0: 0100 00080179 00C2
debug atyfb: 0x20E0: 27004752 0040001C
debug atyfb: 0x20F0: 8021 037FFCF8
debug atyfb: Mach64 PLL register values:
debug atyfb: 0x00: ADD541E4 8A030094 8E9E6501 80 1B
debug atyfb: 0x10: 06CF4000 50B6AC10 408024FD 00 02
debug atyfb: 0x20: 06AC06AC 1424FD00 00255500 00 00
debug atyfb: 0x30: 00 00
Console: switching to colour frame buffer device 160x64
atyfb: fb0: ATY Mach64 frame buffer device on PCI
2.6.8 (which is OK) says this. Is the different MCLK the problem?
atyfb: 3D RAGE (XL) [0x4752 rev 0x27] 8M SDRAM, 29.498928 MHz XTAL, 230 MHz
PLL, 100 Mhz MCLK
fb0: ATY Mach64 frame buffer device on PCI
> Did you try disabling the framebuffer?
How? I'm afraid I don't understand framebuffer stuff and doc on
kernel parameters is rather deficient... I probably wouldn't care
much about the console anyway if the mouse was working.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
