linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Justin Madru <jdm64@gawab.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Bryce Harrington <bryce@bryceharrington.org>
Subject: Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]
Date: Sat, 15 Mar 2008 10:35:23 -0700	[thread overview]
Message-ID: <200803151035.23808.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <47DB46F1.80106@gawab.com>

[Adding Bryce to cc list, he may have a copy of intel_reg_dumper already built 
for Ubuntu.  Bryce, please see below for a few more questions, thanks.]

On Friday, March 14, 2008 8:48 pm Justin Madru wrote:
> Jesse Barnes wrote:
> > It would be interesting if you could get register dumps at a couple of
> > different points, using the intel_reg_dumper tool in
> > git://git.freedesktop.org/git/xorg/driver/xf86-video-intel (in
> > src/reg_dumper).
>
> I couldn't get it to compile. What am I suppose to do? I ran autogen.sh
> in the top level dir and it gave the error message:
>
> ./configure: line 20486: syntax error near unexpected token `XINERMA,'
> ./configure: line 20486: `XORG_DRIVER_CHECK_EXT(XINERMA, xineramaproto)'

This usually means you don't have the xorg autoconf macros installed.  Your 
distro probably has some sort of xserver-devel package that may include it.

> Then I also tried to run make and make -f Makefile.in (in the reg_dumper
> dir and top level dir), and it said:
>
> Makefile.in:15 *** missing separator. Stop.
>
> That part of Makefile.in contains:
> @SET_MAKE@
> VPATH = @srcdir@
>
> What am I doing wrong? You'll have to forgive me, I'm not that
> experienced with the cmd line and compiling - I'm trying though.

No problem, building X still isn't quite as easy as it should be, but it's 
only slightly more complicated than the typical './configure;make;make 
install' due to the dependencies between packages.  You can check out the X 
wiki (wiki.x.org), there are some hints on building things there.

> > You'll probably have to modify your boot scripts though.
> > It would be good to get them:
> >   - at startup time before the splash screen
> >   - sometime while the splash screen is running
> >   - after X starts and you see the blank screen
>
> How exactly would I do that? I would think I could just add command at
> the end of 3 files in /etc/init.d. Would that work? It should run my
> command when it starts that script and gets to the end. Or do boot
> scripts exit in the middle of the script, which would prevent my command
> from running?

Hm, I haven't looked at the Ubuntu scripts before.  I know they're using 
upstart, but if they haven't divered too much from the old style init, you 
may be able to modify rc.sysinit to get the boot time register dump.

For the splash screen dump, you'd just have to add the intel_reg_dumper 
command to one of the other init scripts that runs while the splash screen is 
up (maybe the HAL daemon script or something).

Once your screen is blank, it's probably easiest to ssh into your machine and 
capture the dump that way.

Hope that helps, maybe Bryce can give you some more hints on Ubuntu specifics.

> > What's different between your Uni. environment and your home environment?
>
> I'm not sure. I just have a home wireless router (Hawking HWR54G). I
> have no idea what the Uni. router is.
> On both, I connect to an unencrypted network, but at the Uni. it
> redirects to a login page where I have to log on before I can actually
> use the Internet. Is there anyway I could get more information about the
> Uni. router?

Probably, though the messages in your log from your Univ. connection may be 
enough for the networking guys to figure things out.  It's probably best to 
track the wireless thing as a separate issue though, I'd recommend mailing 
linux-wireless@vger.kernel.org with the problem.

Thanks,
Jesse



  reply	other threads:[~2008-03-15 17:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 19:02 [Regression: 2.6.25-rc5: Blank Screen: Intel 945] Justin Madru
2008-03-12 19:36 ` Jesse Barnes
     [not found]   ` <47D8BF6A.9020905@gawab.com>
2008-03-13 17:09     ` Jesse Barnes
2008-03-14  4:22       ` Justin Madru
2008-03-14 17:29         ` Jesse Barnes
2008-03-15  3:48           ` Justin Madru
2008-03-15 17:35             ` Jesse Barnes [this message]
2008-03-15 18:16               ` Bryce Harrington
2008-03-17  1:28               ` Justin Madru
2008-03-18 19:07                 ` Bryce Harrington
2008-03-18 20:00                   ` Jesse Barnes
2008-03-18 20:53                     ` Bryce Harrington
2008-03-18 21:14                     ` Bryce Harrington
2008-03-18 21:17                       ` Jesse Barnes
2008-03-19 23:38                         ` Justin Madru
2008-03-19 23:48                           ` Jesse Barnes
2008-03-20  2:00                             ` Bryce Harrington
2008-03-25  3:07                             ` Justin Madru
2008-03-25 20:08                               ` Jesse Barnes
2008-03-26 18:32                                 ` Justin Madru
2008-03-31 19:24                                 ` Justin Madru
2008-04-01 20:22                                   ` Jesse Barnes
2008-04-09  4:56                                     ` Justin Madru
2008-04-09 15:24                                       ` Jesse Barnes
2008-04-14  3:46                                         ` Justin Madru

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200803151035.23808.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=bryce@bryceharrington.org \
    --cc=jdm64@gawab.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).