Re: Installation stops after logs, and drops to a shell.

2006-06-20 Thread Steve Langasek
Hi Robert,

On Fri, Jun 16, 2006 at 05:18:37PM -0400, Robert Oram wrote:
> Hello all,
>First off, is this the proper forum to help troubleshoot installer 
> issues, and list the problems it has?  Or is there another list devoted 
> to the alpha installer alone?  I would love to help make the installer 
> better by testing and reporting problems, since I cannot do the coding.

No, there is no list specific to the installer for alpha; there are two
lists of relevance, debian-alpha for architecture-specific problems and
debian-boot for problems not specific to alpha.

The problem you describe doesn't sound like it's an alpha-specific problem,
so I would recommend filing an installation report (which gets forwarded to
the debian-boot list) describing your experience in detail, so that the
maintainers of the relevant installer components can take a look at the
problem... and kick it back to me if they find it's an alpha problem after
all. :)

For this, please make sure you're using the most recent daily builds, to
rule out transient issues that have already been fixed.

>My next issue now may be just an unfinished component or ignorance 
> on my part.  The installs seem to complete, it asks me where to put the 
> log files, then it dumps me to a mini-shell.  And thats it.  What am I 
> supposed to do there?

Really shouldn't happen at all, so I can't suggest an answer here. :)

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature


Re: Xorg upgrade: 6.9.x to 7.0.x

2006-06-20 Thread Steve Langasek
On Tue, Jun 20, 2006 at 09:00:37AM -0500, Bob Tracy wrote:
> Steve Langasek wrote:
> > No idea about the rest, but since int10 is a PC BIOS interface and you don't
> > have one of those, you'll probably want to add

> > Option  "NoINT10" "true"

> > as a start, as an option in your video "Device" section.  Maybe that's
> > enough to clear up the rest of your problems too, with luck.

> No joy in Mudville this day...  The above option made no discernable
> difference other than a mention in the logfile that it was set.  Let me
> see if some combination of TFM and the driver author might provide a
> clue as to what's happening.  There's also the matter of the "INTA"
> jumper on the card that I could try setting to "disable".

> Does "NoINT10 == true" imply I should disable the "int10" and "vbe"
> modules in my "xorg.conf" file?  TFM claims "vbe" needs "int10" to
> work.

Sorry, dunno; I've had both of these modules loaded in my config for a while
even with NoINT10 disabled, but then, my video also stopped working
correctly after upgrade to 7.0...

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Xorg upgrade: 6.9.x to 7.0.x

2006-06-20 Thread Bob Tracy
Steve Langasek wrote:
> No idea about the rest, but since int10 is a PC BIOS interface and you don't
> have one of those, you'll probably want to add
> 
> Option  "NoINT10" "true"
> 
> as a start, as an option in your video "Device" section.  Maybe that's
> enough to clear up the rest of your problems too, with luck.

No joy in Mudville this day...  The above option made no discernable
difference other than a mention in the logfile that it was set.  Let me
see if some combination of TFM and the driver author might provide a
clue as to what's happening.  There's also the matter of the "INTA"
jumper on the card that I could try setting to "disable".

Does "NoINT10 == true" imply I should disable the "int10" and "vbe"
modules in my "xorg.conf" file?  TFM claims "vbe" needs "int10" to
work.

-- 
---
Bob Tracy   WTO + WIPO = DMCA? http://www.anti-dmca.org
[EMAIL PROTECTED]
---


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]