Re: [9fans] 9load: boot time variables

[Nicolas Victorero Mier <nico@telecable.es>]

Russ Cox wrote:

>Instead of making us read the source code,
>could you explain what it does in email?
>
>  
>
>>And would help people during the install, because
>>sometimes you need *norealmode=, *noe820scan=, installurl=, etc to
>>make it work.
>>    
>>
>
>These are intended to be exceptional cases, not everyday options.
>If you need them to make Plan 9 work on a given machine, tell us.
>Does anyone have a machine that still requires *noe820scan?
>I know no one requires *norealmode, because that's redundant
>with *noe820scan the way things are currently set up.
>
>Russ
>
>  
>
Hello,
About a month ago trying to install Plan 9 on an HP NX7000 laptop, 
allways end up with a "No physical memmory" message, somewhere on the 
wiki said that some BIOS have problems reporting memmory size, and the 
solution is to use *maxmem= in plan9.ini, as the laptop don't have 
floppy, trying that involved extracting the plan9.ini from the img, 
repacking it and then burning a new CD. And that didn't solve the 
problem (it went away with the version from 20051124 :)). I think having 
an easier way to provide that variables at boot time would be nice, even 
just to do some testing when *something* goes wrong.

Btw, the laptop has an ati radeon 9200, and a 1680x1050 TFT, so far i've 
only been able to work at 1280x1024x16, with either 
monitor=vesa/xga/multisync, but more than that resolution it don't 
works, any experience with that, or tips where to learn how to make it 
work better?.
Also in the same laptop, i'm having problems with the usb mouse, 
suddenly it reports an i/o error on the rio screen and ceases to work (i 
have to reboot to have it working again).

Thanks & Greetings

Nico