RE: xf4 and lombard

RE: xf4 and lombard

[sprenger]

my x-server is working now after using yaboot - thanks !

using a 2.2.17pre15 worked fine, but with a 2.4-test6 kernel the
x-server crashed often especially under heavy load - like compiling
mozilla-m17 !? but even on the console the build would stop three times
with error 132, just had to restart the build - strange .
i just upgraded to 2.4-test7, and the x-server seems to be stable now
(compiling a new mozilla while using the old one - really a heavy load
...). but now i have some garbage (several blue dots) on my screen,
especially on the "gkrellm"-window.
any idea ?

i will try a new rsynced version of the ati-driver during the weekend.

by the way, do you know the standard key-combination to emulate the
second and third mouse button ? with the 2.4-test6 they used to be
"fn-ctrl" and "fn-alt". but when i upgraded to 2.4-test7 i could not
find them anymore.

hope you can help me out again.
/thorsten


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

RE: xf4 and lombard

[Michael Schmitz]

> using a 2.2.17pre15 worked fine, but with a 2.4-test6 kernel the
> x-server crashed often especially under heavy load - like compiling
> mozilla-m17 !? but even on the console the build would stop three times
> with error 132, just had to restart the build - strange .
> i just upgraded to 2.4-test7, and the x-server seems to be stable now
> (compiling a new mozilla while using the old one - really a heavy load
> ...). but now i have some garbage (several blue dots) on my screen,
> especially on the "gkrellm"-window.
> any idea ?

No, I don't do 2.4 (too much work to do in 2.2 yet).

> by the way, do you know the standard key-combination to emulate the
> second and third mouse button ? with the 2.4-test6 they used to be
> "fn-ctrl" and "fn-alt". but when i upgraded to 2.4-test7 i could not
> find them anymore.

Use showkey or xev. My emulation keys are F11 and F12, (108,111) in 2.2,
and as I said above, I don't bother too much with 2.4 as long as Linus
keeps doing these break-all-archs-except-i386 things to the code.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: xf4 and lombard

[Michel Dänzer]

Michael Schmitz wrote:

> I don't bother too much with 2.4 as long as Linus keeps doing these
> break-all-archs-except-i386 things to the code.

Hasn't that happened in 2.2 as well? I guess that's just the way things go in
Linux - if you don't want that, maybe you're more lucky with NetBSD or
something ;)


Michel


--
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and The DRI Project

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: xf4 and lombard

[Michael Schmitz]

> > I don't bother too much with 2.4 as long as Linus keeps doing these
> > break-all-archs-except-i386 things to the code.
>
> Hasn't that happened in 2.2 as well? I guess that's just the way things go in
> Linux - if you don't want that, maybe you're more lucky with NetBSD or
> something ;)

ROTFL. I'm sure it happened with 2.1.199+ (or whatever the last versions
pre 2.2.0 were), and there were still problems with 2.2.x with x < 6 or so
on some archs. I'm just extremely unhappy with far reaching changes being
introduced in 2.4.0-test (I know it's just a fake 2.4, a smoke screen for
the press, but nonetheless).

Wake me as soon as 2.4.10 comes around :-)

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: xf4 and lombard

[Stefan Berndtsson]

sprenger <sprenger@in.tum.de> writes:

> my x-server is working now after using yaboot - thanks !
>
> using a 2.2.17pre15 worked fine, but with a 2.4-test6 kernel the
> x-server crashed often especially under heavy load - like compiling
> mozilla-m17 !? but even on the console the build would stop three times
> with error 132, just had to restart the build - strange .
> i just upgraded to 2.4-test7, and the x-server seems to be stable now
> (compiling a new mozilla while using the old one - really a heavy load
> ...). but now i have some garbage (several blue dots) on my screen,
> especially on the "gkrellm"-window.
> any idea ?
>
> i will try a new rsynced version of the ati-driver during the weekend.

May I just ask.. how the heck did you get xf4 running on lombard? :)

All I manage to get is a black screen and I can't do anything anymore.
The machine is still running, so I can reboot it via network.

It's a lombard/333 running 2.4.0-test6.

xf4 is compiled from sources found on a link from the instructions
at linuxppc.org and the rsynced version of the ati-driver, as of
about 17.00 CET 2000-08-25.

/Stefan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: xf4 and lombard

[Michael Schmitz]

> > i will try a new rsynced version of the ati-driver during the weekend.
>
> May I just ask.. how the heck did you get xf4 running on lombard? :)

Use yaboot to boot the kernel, or hack atyfb to resolve the PCI resource
overlap between MMIO and video RAM (I'll post a new patch for this to
debian-powerpc shortly).

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: xf4 and lombard

[sprenger]

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

> May I just ask.. how the heck did you get xf4 running on lombard? :)
>
> All I manage to get is a black screen and I can't do anything anymore.
> The machine is still running, so I can reboot it via network.
>
> It's a lombard/333 running 2.4.0-test6.
>
> xf4 is compiled from sources found on a link from the instructions
> at linuxppc.org and the rsynced version of the ati-driver, as of
> about 17.00 CET 2000-08-25.
>
use yaboot as said. at the moment i am running  2.4.0-t7 paulus-kernel.
sometimes i have some blue dots on my screen but  the rest is fine.

i have also attached my xf86config-file. the values in the screen
section were floating around in the net - do not ask me where i found
them. as you see i do not use them, the ati-driver determines its own
values and they are much better. comment out the lines with "Xkb..." i
need them because of my german keyboard layout.

it should work now - good luck ;-)
/thorsten


[-- Attachment #2: XF86Config --]
[-- Type: text/plain, Size: 2527 bytes --]



Section "Files"

    RgbPath	"/usr/X11R6/lib/X11/rgb"

    FontPath	"/usr/X11R6/lib/X11/fonts/local/"
    FontPath	"/usr/X11R6/lib/X11/fonts/misc/"
    FontPath	"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
    FontPath	"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
    FontPath	"/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath	"/usr/X11R6/lib/X11/fonts/CID/"
    FontPath	"/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath	"/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath	"/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath	"/usr/X11R6/lib/X11/fonts/latin2/"
    FontPath	"/usr/X11R6/lib/X11/fonts/PEX/"

EndSection


Section "Module"

    Load	"dbe"

    SubSection	"extmod"
	Option	"omit xfree86-dga"
    EndSubSection

    Load	"type1"
    Load	"freetype"

EndSection


Section "ServerFlags"

    Option	"standby time"	"20"
    Option	"suspend time"	"30"
    Option	"off time"	"60"

EndSection


Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"keyboard"

    Option	"AutoRepeat"	"500 5"
    Option	"XkbKeymap"	"macintosh"
    Option	"XkbKeycodes"	"macintosh"
    Option	"XkbTypes"	"default"
    Option	"XkbCompat"	"default"
    Option	"XkbSymbols"	"de(extended)"
    Option	"XkbGeometry"	"macintosh"

EndSection


Section "InputDevice"

    Identifier	"Mouse1"
    Driver	"mouse"

    Option	"Protocol"	"busmouse"
    Option	"Device"	"/dev/adbmouse"

    Option	"Emulate3Buttons"

EndSection


Section "Monitor"

    Identifier	"PowerBookG3"

    HorizSync  1.0 - 300
    VertRefresh  1.0 - 300

#    Mode "1024x768"
#	DotClock	64.966
#	HTimings	1024 1064 1200 1344
#	VTimings	768 771 777 806
#	Flags		"-HSync" "-VSync" "-CSync"
#    EndMode

EndSection


Section "Device"

    Identifier	"ATIMach64"
    BusID	"PCI:0:17:0"
    Driver	"ati"

EndSection


Section "Screen"

    Identifier	"Screen1"
    Device	"ATIMach64"
    Monitor	"PowerBookG3"

    DefaultDepth 24

    SubSection "Display"
        Depth		8
        Modes		"1024x768"
        ViewPort	0 0
        Virtual 	1024 768
    EndSubsection

    SubSection "Display"
	Depth		16
        Modes		"1024x768"
	ViewPort	0 0
	Virtual		1024 768
    EndSubSection

    SubSection "Display"
	Depth		24
	Modes		"1024x768"
	ViewPort	0 0
	Virtual		1024 768
    EndSubSection

    SubSection "Display"
	Depth		32
        Modes		"1024x768"
	ViewPort	0 0
	Virtual		1024 768
    EndSubSection

EndSection


Section "ServerLayout"

    Identifier	"Main Layout"

    Screen	"Screen1"

    InputDevice	"Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Re: xf4 and lombard

[Michel Dänzer]

sprenger wrote:
>
> > May I just ask.. how the heck did you get xf4 running on lombard? :)
> >
> > All I manage to get is a black screen and I can't do anything anymore.
> > The machine is still running, so I can reboot it via network.
> >
> > It's a lombard/333 running 2.4.0-test6.
> >
> > xf4 is compiled from sources found on a link from the instructions
> > at linuxppc.org and the rsynced version of the ati-driver, as of
> > about 17.00 CET 2000-08-25.
> >
> use yaboot as said. at the moment i am running  2.4.0-t7 paulus-kernel.
> sometimes i have some blue dots on my screen but  the rest is fine.
>
> i have also attached my xf86config-file. the values in the screen
> section were floating around in the net - do not ask me where i found
> them. as you see i do not use them, the ati-driver determines its own
> values and they are much better. comment out the lines with "Xkb..." i
> need them because of my german keyboard layout.

Let me comment on a few things:


>     SubSection  "extmod"
>         Option  "omit xfree86-dga"
>     EndSubSection

You normally want to replace this with just

    Load "extmod"

as DGA is deactivated otherwise. This is from an outdated example XF86Config,
way back somewhere at 3.9.x when DGA wasn't working yet.


>     DefaultDepth 24
>
>     SubSection "Display"
>         Depth           32
>         Modes           "1024x768"
>         ViewPort        0 0
>         Virtual         1024 768

These ViewPort and Virtual values are default for the specified mode and as
such not needed.

>     EndSubSection

There is no depth 32 in X 4. 32 bpp is depth 24, fbbpp 32. If you want 32 bpp,
add

    DefaultFbBpp 32

under the DefaultDepth line and

	FbBpp		32

in a Display Subsection for Depth 24. OTOH maybe it's the default anyway
(driver dependent), grep -i bpp /var/log/XFree86.0.log tells for sure.


Michel


--
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and The DRI Project

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: xf4 and lombard

[jeramy b smith]

> May I just ask.. how the heck did you get xf4 running on lombard? :)
>
> All I manage to get is a black screen and I can't do anything anymore.
> The machine is still running, so I can reboot it via network.
>
> It's a lombard/333 running 2.4.0-test6.
>
> xf4 is compiled from sources found on a link from the instructions
> at linuxppc.org and the rsynced version of the ati-driver, as of
> about 17.00 CET 2000-08-25.
>

I have it working. Here is my configuration.
1. Ben's latest precompiled kernel
2. franz's x rpms (from devel.linuxppc.org)
3. The ati moduled compiled from the linuxppc.org tree
4. I took the config file for the pismo at http://linuxppc.org/files/pub/xf4
and edited it for ati instead of r128.
5. I made sure my /etc/X11/X pointed to /usr/X11R6/bin/XFree86 and ran
startx.

voila mes amis!


-jeramy b smith


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

xf4 and lombard

[Thorsten Sprenger]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 593 bytes --]

hi !

i have compiled xfree 4.0.1 with the latest xfree86-pmac tree from
linuxppc.org. as kernel i use the latest pmac-stable and pmac-devel from
linuxcare. when starting the x-server i get a dark screen, final beep and
- after 180 seconds - the system reboots (kernel panic?).

the ati driver doesn't recognize the real amount of videoram, even if i
use the 'VideoRam'-option. i have attached the some parts of my
XF86Config.0.log file (the system i use at the moment is really bad - no
cut'n paste).

does anyone know how to solve this problem ?

thank you very much in advance !
/thorsten


[-- Attachment #2: Type: TEXT/PLAIN, Size: 3458 bytes --]

........
(II) UnloadModule: "scanpci"
(II) Unloading /usr/X11R6/lib/modules/libscanpci.a
(--) PCI: (0:17:0) ATI Mach64 LI rev 220, Mem @ 0x81000000/24, 0x81fff000/12, I/O @ 0x0c00/8
(II) Addressable bus resource ranges are
	[0] -1	0x00000000 - 0xffffffff (0x0) MXB
	[1] -1	0x00000000 - 0x0000ffff (0x10000) IXB
(II) OS-reported resource ranges:
(II) Active PCI resource ranges:
	[0] -1	0x80800000 - 0x8087ffff (0x80000) MXB
	[1] -1	0x80882000 - 0x80882fff (0x1000) MXB
	[2] -1	0x81fff000 - 0x81ffffff (0x1000) MXB(B)
	[3] -1	0x81000000 - 0x81ffffff (0x1000000) MXB(B)
	[4] -1	0x00000c00 - 0x00000cff (0x100) IXB(B)
(II) Active PCI resource ranges after removing overlaps:
	[0] -1	0x80800000 - 0x8087ffff (0x80000) MXB
	[1] -1	0x80882000 - 0x80882fff (0x1000) MXB
	[2] -1	0x81fff000 - 0x81ffffff (0x1000) MXB(B)
	[3] -1	0x81000000 - 0x81ffffff (0x1000000) MXB(B)
	[4] -1	0x00000c00 - 0x00000cff (0x100) IXB(B)
(II) OS-reported resource ranges after removing overlaps with PCI:
(II) All system resource ranges:
	[0] -1	0x80800000 - 0x8087ffff (0x80000) MXB
	[1] -1	0x80882000 - 0x80882fff (0x1000) MXB
	[2] -1	0x81fff000 - 0x81ffffff (0x1000) MXB(B)
	[3] -1	0x81000000 - 0x81ffffff (0x1000000) MXB(B)
	[4] -1	0x00000c00 - 0x00000cff (0x100) IXB(B)
.........
(II) ATI: ATI driver (version 5.3.5) for chipsets: ati, ativga
(--) Chipset ATI Mach64 3D Rage LT Pro (PCI) found
(II) resource ranges after xf86ClaimFixedResources() call:
	[0] -1	0x80800000 - 0x8087ffff (0x80000) MXB
	[1] -1	0x80882000 - 0x80882fff (0x1000) MXB
	[2] -1	0x81fff000 - 0x81ffffff (0x1000) MXB(B)
	[3] -1	0x81000000 - 0x81ffffff (0x1000000) MXB(B)
	[4] -1	0x00000c00 - 0x00000cff (0x100) IXB(B)
Found a Mach64 on a PowerPC
(WW) ****INVALID MEM ALLOCATION**** b: 0x81000000 e: 0x81ffffff correcting\a
own
	[0] -1	0x81fff000 - 0x81ffffff (0x1000) MXB
	[1] -1	0x00000c00 - 0x00000cff (0x100) IXB
(II) window:
	[0] -1	0x00000000 - 0xffffffff (0x0) MXB
(II) resSize:
	[0] -1	0x00000000 - 0xffffffff (0x0) MXB
(II) window fixed:
	[0] -1	0x00000000 - 0xffffffff (0x0) MXB
(II) resource ranges after probing:
	[0] -1	0x01000000 - 0x01ffffff (0x1000000) MXB(B)
	[1] -1	0x80800000 - 0x8087ffff (0x80000) MXB
	[2] -1	0x80882000 - 0x80882fff (0x1000) MXB
	[3] -1	0x81fff000 - 0x81ffffff (0x1000) MXB(B)
	[4] 0	0x000a0000 - 0x000affff (0x10000) MSB
	[5] 0	0x000b0000 - 0x000b7fff (0x8000) MSB
	[6] 0	0x000b8000 - 0x000bffff (0x8000) MSB
	[7] -1	0x00000c00 - 0x00000cff (0x100) IXB(B)
	[8] 0	0x000003b0 - 0x000003bb (0xc) ISB
	[9] 0	0x000003c0 - 0x000003df (0x20) ISB
(II) Setting vga for screen 0.
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a
(II) Module fbdevhw: vendor="The XFree86 Project"
	compiled for 4.0.1, module version = 0.0.1
	ABI class: XFree86 Video Driver, version 0.2
(--) ATI(0): Depth 24, (++) framebuffer bpp 24
(==) ATI(0): RGB weight 888
(==) ATI(0): Default visual is TrueColor
Mapping MMIO @ 0x17ff000 with size 0x1000
testing mmio w/ scratch regs...
SCRATCH_REG0 = 0x0
SCRATCH_REG0 = 0x12345678
SCRATCH_REG1 = 0x0
SCRATCH_REG1 = 0xdeadbeef
Chip Type = 0x0, Rev = 0x0
(--) ATI(0): VideoRam: 7 kByte (OFF)
(==) ATI(0): Using gamma correction (1.0, 1.0, 1.0)
(II) ATI(0): PowerBookG3: Using hsync range of   1.00-300.00 kHz
(II) ATI(0): PowerBookG3: Using vrefresh range of   1.00-300.00 Hz
(II) ATI(0): Maximum clock:  80.00 MHz

Re: xf4 and lombard

[Michael Schmitz]

> i have compiled xfree 4.0.1 with the latest xfree86-pmac tree from
> linuxppc.org. as kernel i use the latest pmac-stable and pmac-devel from
> linuxcare. when starting the x-server i get a dark screen, final beep and
> - after 180 seconds - the system reboots (kernel panic?).

Boot Linux using yaboot and you should be fine.

> the ati driver doesn't recognize the real amount of videoram, even if i
> use the 'VideoRam'-option. i have attached the some parts of my
> XF86Config.0.log file (the system i use at the moment is really bad - no
> cut'n paste).

See atimach64ppc.c and remove the gratituous videoram=2048 assignment
right after the videoram was set from the fb_fix data. In case it's still
in there, I've not rsynced in a while but forgot to tell Ani about that
one.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/