[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#262183: xserver of 4.3.x fails to start on Alpha

retitle 262183 xserver-xfree86: [s3] can't find PCI card on Alpha [regression from 4.2.1]
tag 262183 + moreinfo

On Fri, Jul 30, 2004 at 10:34:50AM +0900, Atsuhito Kohda wrote:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-4
> Priority: important
> Hi,
> recently, after upgrading to 4.3.x, xserver has failed to
> start on my Alpha with a message;
>       Fatal server error:
>       no screens found
> So I downgraded xserver-xfree86 and xserver-common to 4.2.1-16
> and hold them at present (they work fine).
> XFree86.0.log told me that the difference between 4.2.1 and
> 4.3.0 was;
> [4.2.1]
> (II) S3: driver (version 0.3.5 for S3 chipset: 964-0, 964-1, 968,
> 	Trio32/64, Aurora64V+, Trio64V2/DX or /GX
> (II) Primary Device is: PCI 00:09:0
> (--) Assigning device section with no busID to primary device
> (--) Chipset Trio32/64 found
> [4.3.0]
> (II) S3: driver (version 0.3.5 for S3 chipset: 964-0, 964-1, 968,
> 	Trio32/64, Aurora64V+, Trio64V2/DX or /GX
> (II) Primary Device is: ISA
> (EE) No devices detected.
> Fatal server error:
> no screens found
> I'm not sure if this is related to the problem but because my 
> Alpha machine failed to boot with kernel 2.4 nor 2.6 so the kernel
> is yet 2.2.25.
> I'm not good at debugging but if you need more info, please
> let me know.

Yes, please.

Please run the following commands from a shell prompt to gather and deliver
this information to us:

$ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1
$ mailx -s "Re: Bug#262183" 262183@bugs.debian.org < /tmp/output

If you do not have a "mailx" command on your system, you can get by
installing the "mailx" Debian package; for example, with the "aptitude
install mailx" or "apt-get install mailx" commands as root.  Alternatively,
you can also use a mail command that is compatible with mailx's
command-line syntax, such as "mutt".

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name.  The reportbug
program does a lot of automatic information-gathering that helps package
maintainers to understand your system configuration, and also ensures that
your message to the Debian Bug Tracking System is well-formed so that it is
processed correctly by the automated tools that manage the reports.  (If
you've ever gotten a "bounce" message from the Debian Bug Tracking System
that tells you your message couldn't be processed, you might appreciate
this latter feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System in the future.

If you *did* use reportbug to file your report, then you're receiving this
message because the information we expected to see was not present.

If you deliberately deleted this information from the report, please don't
do that in the future, even if it seems like it makes the mail too large.
50 kB (kilobytes) of configuration and log data is typical.  Only if the
included information greatly exceeds this amount (more than 100 kB) should
you consider omitting it; instead, put it up on the World Wide Web
somewhere and provide URLs to it in your report, or in subsequent followup
by mailing <262183@bugs.debian.org>.

Thank you!

G. Branden Robinson                |     The more ridiculous a belief
Debian GNU/Linux                   |     system, the higher the probability
branden@debian.org                 |     of its success.
http://people.debian.org/~branden/ |     -- Wayne R. Bartz

Attachment: signature.asc
Description: Digital signature

Reply to: