Browsing this Thread:
1 Anonymous Users
|
Re: nVidia driver
|
||||
|---|---|---|---|---|
|
Not too shy to talk
 
|
Quote:
Yes it was the Video BIOS cache. Must remember to get a coffee first thing in the morning before posting to any message boards! :zzz: Cheers, Chris
Posted on: 2005/1/28 23:41
|
|||
|
||||
|
Re: nVidia driver
|
||||
|---|---|---|---|---|
|
Just popping in
 
|
Surly it was a Video BIOS ROM cache... Two possiblities: System BIOS cacheable and Video BIOS cacheable.
Posted on: 2005/1/28 23:24
|
|||
|
Bye, H0V
--------------------------- Using FC3 and AROS for fun! ...
|
||||
|
||||
|
Re: nVidia driver
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
Quote:
Er... Actually just checked - it was Video Bios Shadow. Cheers, Chris
Posted on: 2005/1/28 23:20
|
|||
|
||||
|
Re: nVidia driver
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
Quote:
Woah... Caching Video Ram just sounds wrong!!! 
Posted on: 2005/1/28 20:58
|
|||
|
||||
|
Re: nVidia driver
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
Thanks for the info.
I solved the problem in the end - I turned off cache video ram in the bios and all works well now. Now if I could just get grub installed...  Cheers, Chris
Posted on: 2005/1/28 17:19
|
|||
|
||||
|
Re: nVidia driver
|
||||
|---|---|---|---|---|
|
Home away from home
|
It could have to do with the debug output issue, for which I STILL have not commited any fix.
The problem is that on normal non-debug built there's still debug output which in x86 native goes to VGA textmode screen. The stuff one says at the beginning during boot. Now when the gfx driver kicks in, those debug output should be halted. As it messes around in video ram and there might be important things in there (not just gfx data). Like linked list nodes of allocated bitmap memory (is the case with nvidia driver). That can cause crashe if such nodes get trashed. For those who build AROS from source a quick fix is to simply disable the debug output which goes to vga text mode screen by changing arch/i386-pc/exec/rawputchar.c and disabling/commenting out the "Putc()" call in there. Regarding which gfx cards work: Here I have a FX5700 which works. Before I used to have a GeForce 2 MX 400, which also worked.
Posted on: 2005/1/25 2:42
|
|||
|
||||
|
Re: nVidia driver
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
Quote:
MSI K7T Turbo motherboard Athlon 1.2Ghz 256Mb Ram 40Gb HD Sparklehorse GeForce 2 MX 32Mb WinTV Express (would this affect it? in fact both my machines have WinTV) VESA mode works fine in all resolutions. Cheers, Chris
Posted on: 2005/1/25 2:41
|
|||
|
||||
|
Re: nVidia driver
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
That's odd I have a GeForce 2 MX machine here which runs AROS fine... can you list more detailed system specs... also have you tried the VESA mode?
Posted on: 2005/1/25 2:34
|
|||
|
||||
|
nVidia driver
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
Hi,
I've tried booting the stable AROS-MAX and the nightly builds with the nVidia driver selected on: One PC with a GeForce 2MX (32mb) One PC with an FX5200 (128mb) and they both freeze with a corrupted screen with the mouse pointer in the corner (but totally corrupted - no indication of Wanderer loaded). The PC with the GeForce 2MX will be dedicated to AROS, so if this card doesn't work, is there an nVidia card that is guaranteed to work I could get? Thanks, Chris
Posted on: 2005/1/25 1:58
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
