root ./debian/rules binary)
>
> There's little point in that as gdb won't be able to deal with the X
> server modules anyway. You'll either have to use the LoaderPrintSymbol()
> trick or build with
>
> #define DoLoadableServer NO
>
> in xc/config/cf/host.d
eal with the X
server modules anyway. You'll either have to use the LoaderPrintSymbol()
trick or build with
#define DoLoadableServer NO
in xc/config/cf/host.def. Then you can rebuild parts of the tree with
makeg as appropriate.
> but when I gdb't xserver-xfree86 the machine froze...
Are
. I recompiled your package with debug symbols
(export CFLAGS=-g ; export CPPFLAGS=-g ; fakeroot ./debian/rules binary)
but when I gdb't xserver-xfree86 the machine froze... (and as I always
have to put the notebook to sleep to see something on console this is
really tidious work...though I kept
On Wed, 2004-03-10 at 16:43, Soeren Sonnenburg wrote:
>
> The newer xserver from this years february bail out with signal 11 when
> no monitor is connected.
Please try to get a backtrace.
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast
Hi.
I just wanted to report this regression bug:
The newer xserver from this years february bail out with signal 11 when
no monitor is connected. However it works nicely with
xserver-xfree86-dri-trunk_2003.10.05-2_powerpc.deb (some resolution is
chosen for the external display).
Regards,
Soeren
On Mon, 08 Mar 2004 the mental interface of
Michel Dänzer told:
> On Sun, 2004-03-07 at 20:17, Elimar Riesebieter wrote:
> > It is running on my Albook (Radeon 9600) but the log tells:
> > Symbol drmGetClient from module \
> > /usr/X11R6/lib/modules-dri-trunk/drivers/radeon_drv.o is unresolved!
>
On Sun, 2004-03-07 at 20:17, Elimar Riesebieter wrote:
> It is running on my Albook (Radeon 9600) but the log tells:
> Symbol drmGetClient from module \
> /usr/X11R6/lib/modules-dri-trunk/drivers/radeon_drv.o is unresolved!
Harmless cosmetic side effect of the DRI not being supported on Radeon
950
It is running on my Albook (Radeon 9600) but the log tells:
Symbol drmGetClient from module \
/usr/X11R6/lib/modules-dri-trunk/drivers/radeon_drv.o is unresolved!
Any Hints?
Ciao
Elimar
--
Obviously the human brain works like a computer.
Since there are no stupid computers humans can't be
On Sat, 8 Feb 2003, Vincent Bernat wrote:
> > However, now I have GLX working, but resuming after suspend still doesn't:
> > the colors are all off, and the mouse pointer is corrupted.
>
> Not sure, but you may want to create /dev/apm_bios. Search the
> archives for the correct procedure to do th
OoO En cette nuit nuageuse du samedi 08 février 2003, vers 00:06, ERDI
Gergo <[EMAIL PROTECTED]> disait:
> No, thanks, that was the solution (I assumed make-kpkg used the same
> compiler).
> However, now I have GLX working, but resuming after suspend still doesn't:
> the colors are all off, and th
On 7 Feb 2003, Michel [ISO-8859-1] Dänzer wrote:
> Have you built the DRM with the same compiler as the kernel?
No, thanks, that was the solution (I assumed make-kpkg used the same
compiler).
However, now I have GLX working, but resuming after suspend still doesn't:
the colors are all off, and th
On Fre, 2003-02-07 at 21:05, ERDI Gergo wrote:
>
> Hoping to get resume/suspend working on my iBook2.2 if DRI/DRM works, I
> got the following error messages from the 2002.02.07. snapshot:
>
> Skipping
> "/usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.a:m_debug_clip.o": No
> symbols foun
Hi,
Hoping to get resume/suspend working on my iBook2.2 if DRI/DRM works, I
got the following error messages from the 2002.02.07. snapshot:
Skipping
"/usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.a:m_debug_clip.o": No
symbols found
Skipping
"/usr/X11R6/lib/modules-dri-trunk/extensions/
On Die, 2002-12-10 at 11:06, Vincent Bernat wrote:
> OoO Vers la fin de l'après-midi du lundi 09 décembre 2002, vers 16:18,
> "Kevin B. McCarty" <[EMAIL PROTECTED]> disait:
>
> > One other thing, for other people who may be having a problem -- with the
> > latest xserver package, it seems that loa
OoO Vers la fin de l'après-midi du lundi 09 décembre 2002, vers 16:18,
"Kevin B. McCarty" <[EMAIL PROTECTED]> disait:
> One other thing, for other people who may be having a problem -- with the
> latest xserver package, it seems that loading the freetype module kills X
> for some reason. So I lea
On Mon, 9 Dec 2002, Michel [ISO-8859-1] Dänzer wrote:
> On Mon, 2002-12-09 at 15:33, Kevin B. McCarty wrote:
> > Thank you Jesus Clemente! Your XF86Config-4 file works wonderfully!
> > I did have to make one minor change: changing the line
> > Driver: "ati"
> > to
> > Driver: "radeon"
> >
One other thing, for other people who may be having a problem -- with the
latest xserver package, it seems that loading the freetype module kills X
for some reason. So I leave out that module in /etc/X11/XF86Config-4 and
instead install xfs -- once again I have truetype fonts.
Regards,
--
Kevi
On Mon, 9 Dec 2002, Michel [ISO-8859-1] Dänzer wrote:
> On Mon, 2002-12-09 at 15:33, Kevin B. McCarty wrote:
> > Thank you Jesus Clemente! Your XF86Config-4 file works wonderfully!
> > I did have to make one minor change: changing the line
> > Driver: "ati"
> > to
> > Driver: "radeon"
> >
On Mon, 2002-12-09 at 15:33, Kevin B. McCarty wrote:
> Thank you Jesus Clemente! Your XF86Config-4 file works wonderfully!
> I did have to make one minor change: changing the line
> Driver: "ati"
> to
> Driver: "radeon"
>
> in order to make this work with the 2002.12.05-1 version of t
On Mon, Dec 09, 2002 at 09:33:49AM -0500, Kevin B. McCarty wrote:
> Thank you Jesus Clemente! Your XF86Config-4 file works wonderfully!
Ergh...
Climent. My surname is Climent ;)
J
--
Jesus Climent | Unix SysAdm | Helsinki, Finland | pumuki.hispalinux.es
GPG: 1024D/86946D69 BB64 2339 1CAA 7064
Thank you Jesus Clemente! Your XF86Config-4 file works wonderfully!
I did have to make one minor change: changing the line
Driver: "ati"
to
Driver: "radeon"
in order to make this work with the 2002.12.05-1 version of the DRI
xserver.
--
Kevin McCartyPhysics Depa
On Sat, Dec 07, 2002 at 09:24:35PM -0500, Kevin B. McCarty wrote:
> Hi,
> I just installed the latest xserver-xfree86-dri-trunk (version
> 2002.11.06-2) on my iBook2, upgrading from 2002.10.02-2. My version of
> xserver-xfree86 (the stock Debian package) is 4.2.1-4. I am writing
&g
On Mon, 9 Dec 2002, Kevin B. McCarty wrote:
> I've just tried with the latest package, the 2002.12.05-1 version, but
> that does not start up at all, not even producing a garbled display. So I
> am still sticking with 2002.10.06-2 for now :-(
sorry, I meant
As suggested by Vincent Bernat, I've tried starting the 2002.11.06-2
version of xserver-xfree86-dri-trunk using just "X". This produced the
same stippled background overlaid by diagonal bands of color that I saw
earlier, but (unlike with calling startx) did not crash right
OoO En ce milieu de nuit étoilée du dimanche 08 décembre 2002, vers
03:24, "Kevin B. McCarty" <[EMAIL PROTECTED]> disait:
> I just installed the latest xserver-xfree86-dri-trunk (version
> 2002.11.06-2) on my iBook2, upgrading from 2002.10.02-2. My version of
> xserver-
Hi,
I just installed the latest xserver-xfree86-dri-trunk (version
2002.11.06-2) on my iBook2, upgrading from 2002.10.02-2. My version of
xserver-xfree86 (the stock Debian package) is 4.2.1-4. I am writing
because my X server worked perfectly, until the upgrade caused startx to
fail. For an
> I upgraded yesterday from:
>xserver-xfree86-dri-trunk_2002.10.02-2
> to:
>xserver-xfree86-dri-trunk_2002.11.06-1
>
> Since then I was getting random X shutdown. It seems to be triggered by
> AA font display rendering.
> Since I have downgraded, everything is f
I have made a full upgrade when upgrading xserver-xfree86-dri-trunk.
So everything if fresh from unstable.
~$ apt-cache policy xlibs
xlibs:
Installed: 4.2.1-3
Candidate: 4.2.1-3
Version Table:
*** 4.2.1-3 0
500 ftp://ftp.us.debian.org sid/main Packages
100 /var/lib/dpkg
On Fre, 2002-11-15 at 17:46, christophe barbe wrote:
> I upgraded yesterday from:
>xserver-xfree86-dri-trunk_2002.10.02-2
> to:
>xserver-xfree86-dri-trunk_2002.11.06-1
>
> Since then I was getting random X shutdown. It seems to be triggered by
> AA font display rend
I upgraded yesterday from:
xserver-xfree86-dri-trunk_2002.10.02-2
to:
xserver-xfree86-dri-trunk_2002.11.06-1
Since then I was getting random X shutdown. It seems to be triggered by
AA font display rendering.
Since I have downgraded, everything is fine.
Unfortunately there is nothing in the
On Jan 19 2002, Branden Robinson wrote:
> On Sat, Jan 19, 2002 at 05:06:27AM -0200, Rogério Brito wrote:
> > BTW, Branden, if you're reading this, could you make the debconf
> > for xserver-xfree86 ask the user if he wants a font server
> > running? In my computers (whic
On Sat, Jan 19, 2002 at 05:06:27AM -0200, Rogério Brito wrote:
> BTW, Branden, if you're reading this, could you make the
> debconf for xserver-xfree86 ask the user if he wants a font
> server running? In my computers (which are quite limited in
> RAM), I u
r is
> able to determine the primary adapter on some machines, but not on
> others, for no obvious reason.
Oh, now it makes sense. Thank you very much, Michel. (And it
was actually a good thing that Branden is asking this
information in recent debconfs).
BTW,
On Fri, 2002-01-18 at 05:55, Branden Robinson wrote:
> On Fri, Jan 18, 2002 at 12:23:50AM -0500, Michael D. Crawford wrote:
> > That's what I did, and it seems to work, but the instructions should say
> > not to specify a bus ID if you don't have PCI video, such as for all the
> > macs that just h
On Fri, 2002-01-18 at 19:11, Rogério Brito wrote:
> On Jan 17 2002, Branden Robinson wrote:
> > I'm not sure, but I think you probably need the BusID unless you're
> > using the fbdev driver.
>
> Indeed, it took me ages to make a 9500/180MP with an imstt
> card work with xfree86 -- I h
On Jan 17 2002, Branden Robinson wrote:
> I'm not sure, but I think you probably need the BusID unless you're
> using the fbdev driver.
Indeed, it took me ages to make a 9500/180MP with an imstt
card work with xfree86 -- I had to specify the pci slot where
the card was. Oth
fbdev driver.
> I didn't want it to overwrite my config file, but it did, and
> importantly, it didn't save the old settings.
It did; it backed them up.
> When I upgraded xserver-xfree86, it came up with the configuration
> automatically. I didn't ask it to. The only quest
idn't do it right?
I didn't want it to overwrite my config file, but it did, and
importantly, it didn't save the old settings.
When I upgraded xserver-xfree86, it came up with the configuration
automatically. I didn't ask it to. The only question it asked was
about the bus ID
6Config-4 settings. When I restarted X, it went back to 640x480. I
> > > had to run, I think it was dpkg-reconfigure xserver-xfree86 to get my
> > > proper video back.
> >
> > It doesn't overwrite your config file unless you tell it to. Or do you
> > mean yo
o run, I think it was dpkg-reconfigure xserver-xfree86 to get my
> > proper video back.
>
> It doesn't overwrite your config file unless you tell it to. Or do you
> mean you wanted it to, but it didn't do it right?
And when it writes a new one, it saves the old one wi
ything
> about it when I did the "lspci" command.
Don't specify a bus ID then?
> The other problem is that the new configuration nuked my existing
> XF86Config-4 settings. When I restarted X, it went back to 640x480. I
> had to run, I think it was dpkg-reconfigure xs
> I updated from sid on my powermac 8500 a couple days ago. I had two
> problems with the configuration of an updated package, I'm pretty sure
> it was the xserver-xfree86 package. I have 4.1.0-13 now (PowerPC).
>
> I'm reporting this to the Debian-PowerPC list becaus
I updated from sid on my powermac 8500 a couple days ago. I had two
problems with the configuration of an updated package, I'm pretty sure
it was the xserver-xfree86 package. I have 4.1.0-13 now (PowerPC).
I'm reporting this to the Debian-PowerPC list because the first problem
was s
On Fri, Sep 21, 2001 at 05:48:00PM +0200, Michael Schmitz wrote:
> > > > The patch is rather hackish (there's no way to easily find a free PCI
> > > > resource region in 2.2 kernels) and might not make it through BenH's or
> > > > Alan's 'no brute force hacks' filter. If the Debian kernel package
>
> > > The patch is rather hackish (there's no way to easily find a free PCI
> > > resource region in 2.2 kernels) and might not make it through BenH's or
> > > Alan's 'no brute force hacks' filter. If the Debian kernel package
> > > maintainer accepts it, fine.
> >
> > Ok, I filed a bug against ker
On Thu, Sep 20, 2001 at 03:33:41PM -0400, Adam Di Carlo wrote:
> > I'd rather make a set of 2.4 install disks available than include
> > patches like this in our 2.2 kernel.
>
> It's certainly possible to change the boot-floppies over to 2.4
> kernels, but I doubt the wisdom of that. I recently t
On Thu, Sep 20, 2001 at 03:33:41PM -0400, Adam Di Carlo wrote:
>
> It's certainly possible to change the boot-floppies over to 2.4
> kernels, but I doubt the wisdom of that. I recently tried to run the
> kernel-image-2.4-powerpc (2.4.8-1) and it wouldn't even boot my
> machine (hung after the RTC
Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> On Thu, Sep 20, 2001 at 11:18:29AM -0400, Adam Di Carlo wrote:
> > Michael Schmitz <[EMAIL PROTECTED]> writes:
> >
> > > The patch is rather hackish (there's no way to easily find a free PCI
> > > resource region in 2.2 kernels) and might not make i
On Thu, Sep 20, 2001 at 11:18:29AM -0400, Adam Di Carlo wrote:
> Michael Schmitz <[EMAIL PROTECTED]> writes:
>
> > The patch is rather hackish (there's no way to easily find a free PCI
> > resource region in 2.2 kernels) and might not make it through BenH's or
> > Alan's 'no brute force hacks' fil
Michael Schmitz <[EMAIL PROTECTED]> writes:
> The patch is rather hackish (there's no way to easily find a free PCI
> resource region in 2.2 kernels) and might not make it through BenH's or
> Alan's 'no brute force hacks' filter. If the Debian kernel package
> maintainer accepts it, fine.
Ok, I
> > > I'll try your kernel patch -- should I also perhaps try the 2.4 kernel?
> >
> > Try the 2.4 kernel first. If that doesn't fix it, my patch won't either.
>
> Sorry, I went ahead and stuck with kernel 2.2.19 with your patch.
>
> Your patch fixed it. Should I file a bug against the pmac to a
Michael Schmitz <[EMAIL PROTECTED]> writes:
> > > should have read X -probeonly (where did that go?), sorry.
> >
> > That crashes it as well. I just tested with xserver-xfree86 4.1.0-5
> > and -6, same results.
> >
> > I'll try your kernel
> > should have read X -probeonly (where did that go?), sorry.
>
> That crashes it as well. I just tested with xserver-xfree86 4.1.0-5
> and -6, same results.
>
> I'll try your kernel patch -- should I also perhaps try the 2.4 kernel?
Try the 2.4 kernel first. If tha
hat crashes it as well. I just tested with xserver-xfree86 4.1.0-5
and -6, same results.
I'll try your kernel patch -- should I also perhaps try the 2.4 kernel?
--
...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/>
> > Please send the full X server log (the section about PCI device
> > probing/fixup might prove interesting)
>
> I can't, due to the kernel crash which occurs when running this.
Sorry, I forgot how bad this can be... Does it also panic with X
> Should I file a bug on kernel-image-2.2.19-pmac
> > I can't, due to the kernel crash which occurs when running this.
>
> Sorry, I forgot how bad this can be... Does it also panic with X
should have read X -probeonly (where did that go?), sorry.
Michael
Michael Schmitz <[EMAIL PROTECTED]> writes:
> Wallstreet and 2.2 kernel
Yes, 2.2.19-pmac stock kernel.
>, and you boot using BootX I suppose?
No, booting with a hacked miboot floppy, believe it or not. I don't
have MacOS installed.
> Please send the full X server log (the section about PCI de
> Distribution: pure 'testing'
> Version: 4.1.0-2
> Kernel: kernel-image-2.2.19-pmac 2.2.19-2
>
> Installing the new xserver-xfree86 4.1.0-2 from unstable causes an
> error:
>
> (WW) ATI: PCI/AGP Mach64 in slot 0:17:0 could not be detected!
>
Please CC me on any replies, I am not subscribed to this list.
Hardware: PowerBook G3 (Wall Street)
Distribution: pure 'testing'
Version: 4.1.0-2
Kernel: kernel-image-2.2.19-pmac 2.2.19-2
Installing the new xserver-xfree86 4.1.0-2 from unstable causes an
error:
(WW)
Hi all, sorry for my noise.
The title was wrong and it was on kernel 2.4.4 (not 2.2.4!)
and I found the kerenl-patch-2.4.4-powerpc after posting the
former mail. It worked fine!
> First, Xfree 4.0(xserver-xfree8 4.0.3-3 etc.) seems not to
> work correctly. I used fbdev but it displaied somethin
On Tue, Dec 12, 2000 at 08:04:22AM -0500, Adam C Powell IV wrote:
> BTW, anyone know why the woody GNOME stuff isn't being autobuilt? I've built
> from source and gtkhtml is the only thing I can't get to work, some sources
> have
> built fine for two months but don't have ppc .debs. (Some have m
Phil Fraering wrote:
> Hi. I noticed when I last did an update that the version
> of xserver-xfree86 is still 4.0.1-10 in the binary version,
> but that the source archive is 4.0.1-11; also, Branden mentioned
> that he's compiling 4.0.1-12.
>
> Did you mean to say 11? I sus
Hi. I noticed when I last did an update that the version
of xserver-xfree86 is still 4.0.1-10 in the binary version,
but that the source archive is 4.0.1-11; also, Branden mentioned
that he's compiling 4.0.1-12.
Did you mean to say 11? I suspect that 4.0.1-12 will probably be
ready bef
Phil Fraering wrote:
>
> Hi. After some travails and ups and downs, I think I finally have
> the right kernel. I'm sort-of ready for the next step... does anyone
> know what the _last_ revision of xserver-xfree86 was that was
> actually compiling for the PowerPC (and was rec
Hi. After some travails and ups and downs, I think I finally have
the right kernel. I'm sort-of ready for the next step... does anyone
know what the _last_ revision of xserver-xfree86 was that was
actually compiling for the PowerPC (and was recognizing the
video chip in the iBook) and wh
65 matches
Mail list logo
