headers
Sungjong Woo | 1 Jan 2003 08:32
Picon

Bug#174915: xf86PciInfo.h does not have appropriate data for my card, even though XFree86 found valid card configuration.

Package: XFree86
Version: 4.1.0.1

I am sending this e-mail once again since I didn't include Package
information before.

When I ran /usr/bin/x11/xf86cfg, it gave me this error message.
------------------------------------------------------------------------
 XFree86 found a valid card configuration.
 Unfortunately the appropriate data has not been added to xf86PciInfo.h.
 Please forward 'scanpci -v' output to XFree86 support team.
-------------------------------------------------------------------------
The whole log file of running xf86cfg is attached 'XFree86.8.log'.

'scanpci -v' output is also attached as a file named 'scanpciresult'.

When I ran 'starx', it failed to show me xwindow. It said 'No device
detected', even though I thought I put a proper module for the device.
The attached file, 'XFree86.0.log' is the log file for running 'startx'.

The device I am using is ATI Rage 128 Pro (as is shown on the video card).
The monitor I am using is SAMSUNG SyncMaster 750s. Horizontal frequency
range is 30-70kHz and vertical frequency is 50-160kHz, which I found from
manufacturer's homepage.

I am using Debian GNU/Linux 3.0r1, kernel 2.2.20.

Thank you,
Sungjong Woo
(Continue reading)

Permalink | Reply | 1 comment |
headers
Chris Tillman | 1 Jan 2003 18:49

Fwd: Possible bug in installation

This message appeared on debian-boot. 
Skip, please check for responses on debian-x.

----- Forwarded message from Skip Queen <papanohair <at> mindspring.com> -----

Date: 01 Jan 2003 00:54:43 -0500
From: Skip Queen <papanohair <at> mindspring.com>
X-Mailer: Ximian Evolution 1.0.8-3mdk
To: debian-boot <at> lists.debian.org
Subject: Possible bug in installation

I have tried to install Debian Woody 3.0 a total of six times and each
time the same thing happens.  My video is all screwed up.  XWindows does
not work.  When I pick up video card (i810) it won't work at all.  If I
pick VESA it will "sort of" work - i.e., not the resolution I pick so
things "float" across the screen and the resolution will not go above
800X600.  Someone told me there was a bug in the kernel.  I have had no
problem with my system using either Mandrake, Redhat, SuSE or Knoppix -
only Debian (Woody).  Can you help!  Thanks!

--

-- 
To UNSUBSCRIBE, email to debian-boot-request <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

----- End forwarded message -----
Permalink | Reply | 0 comments |
headers
Debian Bug Tracking System | 1 Jan 2003 19:33
Picon

Bug#174685: marked as done (xserver-xfree86: quake3 unable to receive some DGA mouse events)

Your message dated Wed, 1 Jan 2003 13:29:10 -0500
with message-id <20030101182910.GR8801 <at> deadbeast.net>
and subject line Bug#174685: xserver-xfree86: quake3 unable to receive some DGA mouse events
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 30 Dec 2002 06:08:42 +0000
From nveber <at> pyre.virge.net Mon Dec 30 00:08:39 2002
Return-path: <nveber <at> pyre.virge.net>
Received: from (pyre.virge.net) [24.157.37.105] (postfix)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 18St6K-0001qR-00; Mon, 30 Dec 2002 00:08:36 -0600
Received: by pyre.virge.net (Postfix, from userid 1000)
	id DA3991873DE; Mon, 30 Dec 2002 01:08:34 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Norbert Veber <nveber <at> pyre.virge.net>
To: Debian Bug Tracking System <submit <at> bugs.debian.org>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Branden Robinson | 1 Jan 2003 19:35
Picon
Favicon

Bug#170510: X server build problem fix

On Tue, Dec 31, 2002 at 01:24:01AM +0900, ISHIKAWA Mutsumi wrote:
> Hi,
> 
>  Here is a patch for #170508, #170510.

Thanks so much for this patch.  I knew the bug could be fixed this way
but I was hoping someone would fix the external dependencies instead.

Oh well, that's upstream's problem, I guess.

Thanks again.

--

-- 
G. Branden Robinson                |       Psychology is really biology.
Debian GNU/Linux                   |       Biology is really chemistry.
branden <at> debian.org                 |       Chemistry is really physics.
http://people.debian.org/~branden/ |       Physics is really math.
Permalink | Reply | 4 comments |
headers
Debian Bug Tracking System | 1 Jan 2003 20:03
Picon

Processed: tagging 174282

Processing commands for control <at> bugs.debian.org:

> tag 174282 + upstream
Bug#174282: xlibs: Xpm needs LONG64 on Alpha 
There were no tags set.
Tags added: upstream

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)
Permalink | Reply | 0 comments |
headers
Debian Bug Tracking System | 1 Jan 2003 20:03
Picon

Bug#174915: marked as done (xf86PciInfo.h does not have appropriate data for my card, even though XFree86 found valid card configuration.)

Your message dated Wed, 1 Jan 2003 13:50:44 -0500
with message-id <20030101185044.GW8801 <at> deadbeast.net>
and subject line Bug#174915: xf86PciInfo.h does not have appropriate data for my card, even though XFree86 found valid card configuration.
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 1 Jan 2003 13:22:49 +0000
From cjwatson <at> flatline.org.uk Wed Jan 01 07:22:49 2003
Return-path: <cjwatson <at> flatline.org.uk>
Received: from lutetium.btinternet.com [194.73.73.116] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 18Tipc-00026D-00; Wed, 01 Jan 2003 07:22:48 -0600
Received: from host217-36-6-112.in-addr.btopenworld.com ([217.36.6.112] helo=riva.lab.dotat.at)
	by lutetium.btinternet.com with esmtp (Exim 3.22 #16)
	id 18TipY-0005qi-00
	for submit <at> bugs.debian.org; Wed, 01 Jan 2003 13:22:44 +0000
Received: from cjwatson by riva.lab.dotat.at with local (Exim 3.35 #1 (Debian))
	for submit <at> bugs.debian.org
	id 18TipX-0001Am-00; Wed, 01 Jan 2003 13:22:43 +0000
(Continue reading)

Permalink | Reply | 0 comments |
headers
Branden Robinson | 1 Jan 2003 20:07
Picon
Favicon

Bug#172962: IPv6 support (more info)

On Mon, Dec 16, 2002 at 07:39:16PM +0100, Fabio Massimo Di Nitto wrote:
> I hope this will make some things more clear about the IPv6 status.
[...]
> At this point in time I would suggest to proceed with inclusion and be
> ready to merge with 4.3.0, test and send upstream. More than rejecting the
> patches I do not see any other simple solution in a short term. Of course
> we can just wait and see but of course the final decision is up to
> Branden.

I will not have Debian's XFree86 packages break protocol compatibility
with upstream XFree86.

I am on the fence regarding these patches until I know whether they do
so or not.

In any case, getting these patches aired upstream (XFree86, not
necessarily X.Org) is a very, very good idea, because people much
savvier with X protocol design and implementation details can thus get a
good, critical look at it.

--

-- 
G. Branden Robinson                |       The key to being a Southern
Debian GNU/Linux                   |       Baptist: It ain't a sin if you
branden <at> debian.org                 |       don't get caught.
http://people.debian.org/~branden/ |       -- Anthony Davidson
Permalink | Reply | 5 comments |
headers
Branden Robinson | 1 Jan 2003 20:57
Picon
Favicon

Bug#168178: [savage] runs out of MTRRs on unknown chipset (0x8c2e) rev 5

On Wed, Dec 11, 2002 at 11:42:23PM +0100, Juliusz Chroboczek wrote:
> This is fixed in upstream CVS.  It is due to the 4.2 version of the
> Savage driver mis-detecting the video memory size.
> 
> A workaround is to set the size in your XF86Config-4 explicitly using
> the VideoRam keyword.  A proper solution is to remove the code that
> (mistakenly) probes for the memory size using the VESA BIOS in
> SavagePreInit in savage_driver.c.

I have a fix pending for 4.2.1-5:

  * patch #000_stolen_from_HEAD_savage_driver: new
    + Fixed memory leaks in S3 Savage driver (Egbert Eich).
    + Savage driver updates (#5203, Tim Roberts).
    + [...] xf86SetOperatingState() call cleanups in most drivers
      (Marc La France).
    + Savage driver updates.
        - Support for ProSavage DDR (PCI ID 0x8D04)
        - TV output fixes
        - support for -pixmap24 flag
        - XAA fixes to cure lockups
        (#5412, Tim Roberts).
    + Fix Mono8x8 code in savage driver, needed ROP_NEEDS_SOURCE, also
      add NO_PLANEMASK to ScreenToScreen as code doesn't handle that case
      (Alan Hourihane).
    + Remove "Option VideoRam" from savage driver, there's no need for
      it, and utilize the entities given VideoRam size (Alan Hourihane).

--

-- 
G. Branden Robinson                |    A committee is a life form with six
(Continue reading)

Permalink | Reply | 0 comments |
headers
ISHIKAWA Mutsumi | 1 Jan 2003 21:17
Picon

Bug#170510: X server build problem fix

>>>>> In <20030101183545.GU8801 <at> deadbeast.net> 
>>>>>	Branden Robinson <branden <at> debian.org> wrote:

>> On Tue, Dec 31, 2002 at 01:24:01AM +0900, ISHIKAWA Mutsumi wrote:
>> > Hi,
>> > 
>> >  Here is a patch for #170508, #170510.
>>
>> Thanks so much for this patch.  I knew the bug could be fixed this way
>> but I was hoping someone would fix the external dependencies instead.

 Compiling XFree86 with this patch does not refer X11/* headers
out of the source tree. Of cause Build-Depends: xlibs-dev is not
needed. I've tested the build under clean installed chroot sid tree.
The chroot system tree does not have X11 headers.

 This fix is not enough for these bug reports?

 I'm confising about `external dependencues'.

 I believed that "`external dependencues` said in the reports
means xfree86 build depends xfree86 generated files. So,
we should add xfree86 Build-Depends: xlibs-dev or so....."

--

-- 
ISHIKAWA Mutsumi
 <ishikawa <at> netvillage.co.jp>, <ishikawa <at> linux.or.jp>, <ishikawa <at> debian.org>
Permalink | Reply | 3 comments |
headers
Fabio Massimo Di Nitto | 1 Jan 2003 22:59

Bug#172962: IPv6 support (more info)


On Wed, 1 Jan 2003, Branden Robinson wrote:

> On Mon, Dec 16, 2002 at 07:39:16PM +0100, Fabio Massimo Di Nitto wrote:
> > I hope this will make some things more clear about the IPv6 status.
> [...]
> > At this point in time I would suggest to proceed with inclusion and be
> > ready to merge with 4.3.0, test and send upstream. More than rejecting the
> > patches I do not see any other simple solution in a short term. Of course
> > we can just wait and see but of course the final decision is up to
> > Branden.
>
> I will not have Debian's XFree86 packages break protocol compatibility
> with upstream XFree86.

Of course this is a very very good argument perfectly understandable.

>
> I am on the fence regarding these patches until I know whether they do
> so or not.

fair enough...

>
> In any case, getting these patches aired upstream (XFree86, not
> necessarily X.Org) is a very, very good idea, because people much
> savvier with X protocol design and implementation details can thus get a
> good, critical look at it.
>
(Continue reading)

Permalink | Reply | 4 comments |

Gmane