Bug#369304: Quik uses OF input-device/output-device as console; on oldword this results in no visible outpu

2006-06-24 Thread Holger Levsen
Hi,

On Friday 23 June 2006 18:01, Daniel Dickinson wrote:
> On Fri, Jun 23, 2006 at 11:42:59AM +0200, [EMAIL PROTECTED] wrote:
> > I know. I think the best solution is to have the installer modify the
> > input-device and output-device variables to point to keyboard/screen.
> I was thinking of doing this; I wanted to see if there was an easier way
> first.  I'll be hacking on quik-installer next week to see about doing
> this. 

Another option would be, quik reads those values from /etc/quik.conf and sets 
them, while quik-installer writes quik.conf.

Obviously this requires a version of quik first, that supports this.

> AIUI quik needs boot-device to be eg. /bandit/ohare/mesh/[EMAIL PROTECTED]:0 
> to 
> boot the master boot record anyway (maybe this is model dependant as
> well?).  At least my mac-clone doesn't boot the mbr unless I specify the
> boot-device.

AIUI its OF which needs those settings.

Anyway, also we need to keep in mind that not only that different models 
require different settings, but also they might have scsi or ide discs.

> That's a good idea.  I also need a big scary warning with option to abort
> before modifying boot-device.  I'm thinking that at the most detailed
> debconf priority there could be input fields for the user to specify
> input-device, output-device, and boot-device themselves (with defaults to
> what normally would happen).
> What do you think?

Basically I agree. 

I would like to have sensible/possible choices in the input fields instead of 
free text fields :) 

Also we (d-i team) need to keep in mind, that some users dont want to use quik 
and modify OF values, as they already have a working BootX setup. But this 
surely doesn't belong into this bugreport :)


regards,
Holger


pgpU8hPNPhcZ8.pgp
Description: PGP signature


Bug#369304: Quik uses OF input-device/output-device as console; on oldword this results in no visible outpu

2006-06-23 Thread Daniel Dickinson
On Fri, Jun 23, 2006 at 11:42:59AM +0200, [EMAIL PROTECTED] wrote:

> > quik uses the input-device and output-device of openfirmware as the
> > console.  Unfortunately many old world macs default to a serial console
> > for openfirmware thus the user never sees the quik boot screen, and
> > can't select what image to boot (or MacOS using image=$bye).
> > 
> > The kernel is afflicted with the same problem until the virtual
> > terminals are activated, thus no boot messages are available to the
> > typical oldworld mac user.
> 
> I know. I think the best solution is to have the installer modify the
> input-device and output-device variables to point to keyboard/screen.

I was thinking of doing this; I wanted to see if there was an easier way
first.  I'll be hacking on quik-installer next week to see about doing this.
AIUI quik needs boot-device to be eg. /bandit/ohare/mesh/[EMAIL PROTECTED]:0 to 
boot 
the master boot record anyway (maybe this is model dependant as well?).  At
least my mac-clone doesn't boot the mbr unless I specify the boot-device.

> There are a few cases in which you still want serial console. Some
> models (eg 7200, I'm not sure if there are others) don't have OF support 
> for the onboard framebuffer. Serial console is your only option then. 
> The ANS (Apple Network Server) is likely to be run headless, so serial
> OF console may be the right thing to do there. I think the installer
> should propose a default I/O choice to the user based on the model and
> then modify the OF vars based on the users choice.
 
That's a good idea.  I also need a big scary warning with option to abort
before modifying boot-device.  I'm thinking that at the most detailed debconf 
priority
there could be input fields for the user to specify input-device, output-device,
and boot-device themselves (with defaults to what normally would happen).

What do you think?

-- 
And that's my crabbing done for the day.  Got it out of the way early, 
now I have the rest of the afternoon to sniff fragrant tea-roses or 
strangle cute bunnies or something.   -- Michael Devore



signature.asc
Description: Digital signature


Bug#369304: Quik uses OF input-device/output-device as console; on oldword this results in no visible outpu

2006-06-23 Thread p2
Hi Daniel,

Sorry for the late reply but anyway :)

On Sun, May 28, 2006 at 07:07:12PM -0400, Daniel Dickinson wrote:
> Package: quik
> Version: 2.1-8
> Severity: important
> 
> quik uses the input-device and output-device of openfirmware as the
> console.  Unfortunately many old world macs default to a serial console
> for openfirmware thus the user never sees the quik boot screen, and
> can't select what image to boot (or MacOS using image=$bye).
> 
> The kernel is afflicted with the same problem until the virtual
> terminals are activated, thus no boot messages are available to the
> typical oldworld mac user.

I know. I think the best solution is to have the installer modify the
input-device and output-device variables to point to keyboard/screen.
There are a few cases in which you still want serial console. Some
models (eg 7200, I'm not sure if there are others) don't have OF support 
for the onboard framebuffer. Serial console is your only option then. 
The ANS (Apple Network Server) is likely to be run headless, so serial
OF console may be the right thing to do there. I think the installer
should propose a default I/O choice to the user based on the model and
then modify the OF vars based on the users choice.

Opinions welcome :)

L & L

p2.

-- 
Goa is a state of mind


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



Bug#369304: Quik uses OF input-device/output-device as console; on oldword this results in no visible outpu

2006-05-28 Thread Daniel Dickinson
Package: quik
Version: 2.1-8
Severity: important

quik uses the input-device and output-device of openfirmware as the
console.  Unfortunately many old world macs default to a serial console
for openfirmware thus the user never sees the quik boot screen, and
can't select what image to boot (or MacOS using image=$bye).

The kernel is afflicted with the same problem until the virtual
terminals are activated, thus no boot messages are available to the
typical oldworld mac user.

-- 
And that's my crabbing done for the day.  Got it out of the way early, 
now I have the rest of the afternoon to sniff fragrant tea-roses or 
strangle cute bunnies or something.   -- Michael Devore



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