Re: quik 7300 Auto of scan range
On 13 Jan, this message from Hans Ekbrand echoed through cyberspace:
> On Thu, Jan 12, 2006 at 08:14:47PM -0200, Fábio Rabelo wrote:
>> > > Well then you might not even have to resolve the display issue,
>> > > just install ssh in the chroot and reboot.
>> > Googling around I found this
>> > :http://www.cpu.lu/~mlan/linux/dev/g3upgrade.html
I'm the autho of that page, nice to see it might still be useful.
>> > but I do not
>> > found any command called "nvsetenv" , there are another way to
>> > change OF parameters ? I am almost giving up !
>>
>> All right, within chroot the command nvsetenv works, but I have no
>> idea how to input this parameters !?!
>> man nvsetenv is the most confusing I ever see, tells nothing useful .
>> Someone can help me with this ?
It's very simple:
nvsetenv <var name>
prints the contents of the OF variable <var name>, while
nvsetenv <var name> <value>
writes <value> into the OF variable <var name>.
> I use nvsetenv in the following way to set the variables "boot-device"
> and "boot-command" to get quik working:
>
> nvsetenv boot-device ata/ATA-Disk@0:0
Don't use that one in the 7300. It's for machines with IDE disks.
> nvsetenv boot-command "begin ['] boot catch 1000 ms cr again"
This one can help since the internal SCSI disk of th 7300 may take too
much time to spin up. But as far as we know, this is not Fabio's
problem.
> I think the code you refered to would into the "nvramrc" variable and
> thus be entered like this:
>
> nvsetenv nvramrc "dev /bandit/gc/via-cuda
> ' write value &W
> : -&We &W swap - execute ;
> : P1 4D8 -&We false 548 -&We ;
> &W FC + ' P1 BLpatch
> : P2 0C 2 ms ;
> &W E0 + ' P2 BLpatch device-end"
>
[snip'ed remaining explanation]
Be careful, this would replace the current contents of nvramrc. But
there should be other patches already in there.
You better copy your current nvramrc to a file:
nvsetenv nvramrc > of-patches
then edit that file of-patches, adding what I describe on my page, and
finally setting it again:
nvsetenv nvramrc "`cat of-patches`"
Now, all this OF patching only helps you get OF's diplay onto your
monitor. It should not have any impact on what Linux does to your
display.
To get this sorted out, tell us more:
- what monitor are you using? Apple? Third party?
- if third party, what adapter? With video mode switches? How are the
switches configured?
- did you install a display manager, that would be started
automatically, i.e. your system would boot to an X-Windows interface
instead of only text mode?
- if yes, what configuration file did you provide for X?
You could try with this config file for X:
http://www.cpu.lu/~mlan/linux/dev/XF86Config.control
Again, verify that your monitor is recognized by the hardware as a
Multisync monitor (either it's a Multisync from Apple, or the adapter is
configured to represent one), and that it supports the mode I'v chosen
(1152x864).
When reporting back to us, please also post relevant error messages from
the logs.
Cheers
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
Reply to: