| View previous topic :: View next topic |
| Author |
Message |
catkfr
Guru
Joined: 02 Aug 2004
Posts: 300
|
 Posted: Wed Aug 04, 2004 10:46 am Post subject: |
 |
|
I'm quite new with linux but really wanted to get this patch to work with gentoo-dev-sources-2.6.7-r11. I saw that other people managed to do this but I thought that for other newbies like me this could help.
In order to apply the vesafb patch, you should first apply the following patch (yes, I know it is ridiculously simple!)
http://www.mit.edu/~mserrano/prevesafb-tng-gentoo-2.6.7-r11.patch
so dowload this patch and the vesa-tng-0.9-rc2-2.6.7-gentoo.patch
cd /usr/src/linux
patch -p1 < <path-to-prevesafb-patch>/prevesafb-tng-gentoo-2.6.7-r11.patch
then apply the vesafb patch and it should work.
Hope this helps |
|
| Back to top |
|
 |
catkfr
Guru
Joined: 02 Aug 2004
Posts: 300
|
| Posted: Wed Aug 04, 2004 1:01 pm Post subject: problems with 1400x1050 on laptop |
|
|
I can't get 1400x1050 to work properly on my laptop (Dell Inspiron 8200) with a Geforce 440 Go. The other resolutions work fine but when I try this resolution, the screen doesn't work properly, as if the bottom left of the screen was at the wrong place (slightly higher and to the right of the corner of the screen). In the end, the text wraps and the lines finish on the left side of the screen and a few charcters are missiong and the screen is a bit corrupted (the column between the end of the lines and the beginning of the lines) and if I launch bootsplash, then the colors go wrong as well. I tried all the options in the documentation without any success. The mode that doesn't work 1400x1050-16 appears in the modes in /proc/fb0/.
For now, I'm running perfectly in 1280x1024-16. Any ideas? |
|
| Back to top |
|
|
snekiepete
Guru
Joined: 07 May 2003
Posts: 306
Location: WISCONSIN
|
| Posted: Wed Aug 04, 2004 2:51 pm Post subject: |
|
|
Not sure if I can shed any light or not, my line in grub:
video=vesafb:ywrap,mtrr,1400x1050-32@85.
one thing that I noticed affected the fb was compiled in fonts, if I had none or one other than the 8x16 I would get some funkiness? possibly you could check that.... |
|
| Back to top |
|
|
catkfr
Guru
Joined: 02 Aug 2004
Posts: 300
|
| Posted: Wed Aug 04, 2004 4:02 pm Post subject: |
|
|
| Thanks for the info snekiepete but unfortunately, that didn't do it for me: no change at all (good or bad) |
|
| Back to top |
|
|
MadEgg
l33t
Joined: 06 Jun 2002
Posts: 678
Location: Netherlands
|
| Posted: Wed Aug 04, 2004 5:12 pm Post subject: |
|
|
catkfr, thx for the hint but it doesn't work for me...
| Code: |
bash-2.05b# patch -p1 < /root/prevesafb-tng-gentoo-2.6.7-r11.patch
patching file drivers/video/vesafb.c
bash-2.05b# patch -p1 < /root/vesafb-tng-0.9-rc3-r3-2.6.8-rc1.patch
patching file arch/i386/boot/video.S
patching file Documentation/fb/vesafb.txt
patching file drivers/video/fbmem.c
Hunk #3 succeeded at 1439 (offset -42 lines).
patching file drivers/video/Kconfig
patching file drivers/video/Makefile
Hunk #1 succeeded at 44 (offset 1 line).
patching file drivers/video/vesafb.c
Hunk #2 FAILED at 59.
Hunk #6 FAILED at 231.
Hunk #7 succeeded at 463 (offset 3 lines).
Hunk #8 succeeded at 490 (offset 3 lines).
Hunk #9 succeeded at 511 (offset 3 lines).
Hunk #10 succeeded at 800 (offset 3 lines).
Hunk #11 succeeded at 834 (offset 3 lines).
Hunk #12 FAILED at 864.
Hunk #13 succeeded at 1143 (offset 2 lines).
3 out of 13 hunks FAILED -- saving rejects to file drivers/video/vesafb.c.rej
The next patch would create the file drivers/video/vesafb-thread.c,
which already exists! Assume -R? [n] n
Apply anyway? [n] y
patching file drivers/video/vesafb-thread.c
Patch attempted to create file drivers/video/vesafb-thread.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file drivers/video/vesafb-thread.c.rej
The next patch would create the file include/video/vesa.h,
which already exists! Assume -R? [n] y
patching file include/video/vesa.h
|
I still get a lot of failed 'hunks'... This is on gentoo-dev-sources-2.6.7-r11 so what am I doing wrong?
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
| Back to top |
|
|
catkfr
Guru
Joined: 02 Aug 2004
Posts: 300
|
| Posted: Wed Aug 04, 2004 5:30 pm Post subject: |
|
|
| the patch you are using is not for this kernel version. Use vesafb-tng-0.9-rc2-2.6.7-gentoo |
|
| Back to top |
|
|
MadEgg
l33t
Joined: 06 Jun 2002
Posts: 678
Location: Netherlands
|
| Posted: Wed Aug 04, 2004 6:26 pm Post subject: |
|
|
Ow dohh... I'm so stupid 
Anyway, the older patch works a lot better, but it complains about a vesafb-thread.c and a vesa.h file that would be created by the patch, but they already exist. Hmm, I'll see what happens if I just remove those 2 files before I apply the patch.
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
| Back to top |
|
|
MadEgg
l33t
Joined: 06 Jun 2002
Posts: 678
Location: Netherlands
|
| Posted: Wed Aug 04, 2004 7:25 pm Post subject: |
|
|
Hmmzz.. apparently those existing files were the remnants of some other patch or something.
I re-emerged gentoo-dev-sources and now both the patches applied fine.
I removed the vga=0x518 from my bootline and added ,1024x768-32@85 to the video option.
I do get a 1024x768 console with the appropriate bootsplash and stuff. The refresh rate is still 60Hz though 
I checked dmesg and vesafb is telling me that my card(GF6800 Ultra) is VBE 3.0 compatible(as it should be imo  ) so that should not be a problem.
My two monitors can handle 85Hz at that resolution as well so I don't see what's the problem...
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
| Back to top |
|
|
MadEgg
l33t
Joined: 06 Jun 2002
Posts: 678
Location: Netherlands
|
| Posted: Thu Aug 05, 2004 11:36 pm Post subject: |
|
|
Anyone?
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
| Back to top |
|
|
ketjow
Guru
Joined: 01 Apr 2004
Posts: 382
Location: Krakow, Poland
|
| Posted: Fri Aug 06, 2004 11:58 pm Post subject: |
|
|
Check, if your monitor doesn't send bad information about his max. refresh-rates. After typing dmesg, find something that looks like this: | Code: | vesafb: monitor limits: vf = 60 Hz, hf = 65 kHz, clk = 110 MHz
|
If this is the case, just add something like:
| Code: | | maxvf:85,maxhf:100,maxclk:170 |
to your video option.
By the way - Great patch! Works fine, although much slower than the "classic" vesafb (delay when switching consoles). Is this normal? |
|
| Back to top |
|
|
MadEgg
l33t
Joined: 06 Jun 2002
Posts: 678
Location: Netherlands
|
| Posted: Sat Aug 07, 2004 10:09 am Post subject: |
|
|
Hmmz. My monitor doesn't send any edid-information at all(tad strange for a 2 year old monitor but anyway).
I checked dmesg anyway, it said this:
| Code: |
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
|
I added 'maxvf=160,maxhf=96,maxclk=200' to my video parameter.
The result was this:
| Code: |
vesafb: monitor limits: vf = 0 Hz, hf = 160 kHz, clk = 200 MHz
|
I then went diggin through the sourcecode. I found a bug in there which assigns the value of maxvf to the variable maxhf on line 534(or 533, maybe I added a new empty line in before). I fixed that and rebooted.
Result:
| Code: |
vesafb: monitor limits: vf = 160 Hz, hf = 96 kHz, clk = 0 MHz
|
Still no nice refresh rate. Pixelclock has become 0 somehow.
Went digging through the sourcecode again. I found out the reason it became 0 could be found on line 767(766?), probably because mon_limits is not set.
I hacked the default value from 0 into the max pixelclock from my monitor, 200 MHz, so I entered 200000000 at line 767(766?) instead of 0.
Result after reboot:
| Code: |
vesafb: monitor limits: vf = 160 Hz, hf = 96 kHz, clk = 200 MHz
|
Seems allright. But still no nice refresh rate, still at 60Hz.
The entire vesafb part of dmesg as of now:
| Code: |
bash-2.05b$ dmesg | grep vesafb
Kernel command line: root=/dev/hda5 video=vesafb:ywrap,mtrr,noedid,maxvf:160,maxhf:96,maxclk:200,vram:16,1024x768-16@85 splash=silent
vesafb: NVIDIA Corporation, nv40 Board - p201-12 , Chip Rev (OEM: NVIDIA)
vesafb: VBE version: 3.0
vesafb: protected mode interface info at c000:cd50
vesafb: pmi: set display start = c00ccd86, set palette = c00ccdf0
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
vesafb: monitor limits: vf = 160 Hz, hf = 96 kHz, clk = 200 MHz
vesafb: total memory: 16777216
vesafb: scrolling: ywrap using protected mode interface, yres_virtual=8192
vesafb: framebuffer at 0xc0000000, mapped to 0xf8809000, size 16384k
bash-2.05b$
|
Maybe I should bug-report this to spock instead of posting here? Anyway, suggestions are welcome!
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
| Back to top |
|
|
ketjow
Guru
Joined: 01 Apr 2004
Posts: 382
Location: Krakow, Poland
|
| Posted: Sat Aug 07, 2004 10:50 am Post subject: |
|
|
| strange.. Worked fine for me, except that the monitor gave bad max*-values. I looked for the errors, you've found, but couldn't localize them. When did you download the patch? Kernel 2.6.8?? |
|
| Back to top |
|
|
MadEgg
l33t
Joined: 06 Jun 2002
Posts: 678
Location: Netherlands
|
| Posted: Sat Aug 07, 2004 12:40 pm Post subject: |
|
|
No, the file I've got is: vesafb-tng-0.9-rc2-2.6.7-gentoo.patch
For my 2.6.7-gentoo-r11 kernel.
I'd like to switch to another kernel, I've used love-sources till about 2.6.5 but then they started breaking everything in every other release so I decided to switch to gentoo-sources. Don't like this one either because qingy doesn't seem to want to work with it, it deadlocks my whole machine when I start it.
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
| Back to top |
|
|
ketjow
Guru
Joined: 01 Apr 2004
Posts: 382
Location: Krakow, Poland
|
|
| Back to top |
|
|
MadEgg
l33t
Joined: 06 Jun 2002
Posts: 678
Location: Netherlands
|
| Posted: Sat Aug 07, 2004 3:42 pm Post subject: |
|
|
I just tried that. The maxvf->maxhf bug was fixed, but the maxclk still gets set to 0.
When I hardcode it to 200000000 and even when I set the minvf to 85, I still get a console at 60 Hz...
I'll try this with a monitor that does supply EDID info later tonight, see if I can actually get it to work at all...
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
| Back to top |
|
|
MadEgg
l33t
Joined: 06 Jun 2002
Posts: 678
Location: Netherlands
|
| Posted: Sun Aug 08, 2004 3:43 pm Post subject: |
|
|
Nope. The monitor does supply EDID, it gets detected correctly by the vesafb driver but the refresh rate is still 60 Hz.
Can't figure out why
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
| Back to top |
|
|
raid517
l33t
Joined: 06 Mar 2003
Posts: 946
|
| Posted: Sun Aug 08, 2004 8:17 pm Post subject: |
|
|
Erm... how exactly do I use this patch? Kill me for being a total n00b if you will, but I have never patched anything in my life. Could someone tell me, or maybe the author could add it to his guide?
GJ |
|
| Back to top |
|
|
MadEgg
l33t
Joined: 06 Jun 2002
Posts: 678
Location: Netherlands
|
| Posted: Sun Aug 08, 2004 11:13 pm Post subject: |
|
|
Err... both on the start post of this thread and on his webpage it is quite clearly described how to apply the patch as far as I can see...
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
| Back to top |
|
|
MaxDamage
l33t
Joined: 03 Jan 2004
Posts: 650
Location: Oviedo, Spain
|
| Posted: Sun Sep 05, 2004 10:32 am Post subject: |
|
|
I'm using gentoo-dev-sources-2.6.8-r3, wich have vesafb-tng patch applied by default. I own an ATI Radeon 9600 Pro and use the binary drivers.
Well the problem is the same that MadEgg explained. Works well... at 60Hz! No way of getting more. My question is: Doesn't the video modes we are trying to use be defined in /etc/fb.conf? I have no video mode "1024x768-16@85" in that file (is untouched, as gentoo install writed it). Or people got it to work without having the specific video mode defined in fb.conf?
The Radeon 9600 should be VBE 3.0 complaint, so I dont know why fails. I'm missing something?
_________________
La PDA de tungsteno |
|
| Back to top |
|
|
MaxDamage
l33t
Joined: 03 Jan 2004
Posts: 650
Location: Oviedo, Spain
|
| Posted: Sun Sep 05, 2004 11:05 am Post subject: |
|
|
Ok, look what a curious thing:
| Code: | vesafb: ATI Technologies Inc., V350, 01.00 (OEM: ATI RADEON 9600 PRO)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:5757
vesafb: pmi: set display start = c00c57eb, set palette = c00c5837
vesafb: pmi: ports = c010 c016 c054 c038 c03c c05c c000 c004 c0b0 c0b2 c0b4
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: scrolling: redraw
vesafb: framebuffer at 0xc0000000, mapped to 0xe0808000, size 16384k |
So, it recognices my Radeon 9600 as only VBE 2.0 complaint  Google says it's 3.0. What can I do?
_________________
La PDA de tungsteno |
|
| Back to top |
|
|
sarge
n00b
Joined: 30 Aug 2004
Posts: 27
|
| Posted: Mon Sep 06, 2004 6:04 am Post subject: |
|
|
| MaxDamage wrote: | Ok, look what a curious thing:
| Code: | vesafb: ATI Technologies Inc., V350, 01.00 (OEM: ATI RADEON 9600 PRO)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:5757
vesafb: pmi: set display start = c00c57eb, set palette = c00c5837
vesafb: pmi: ports = c010 c016 c054 c038 c03c c05c c000 c004 c0b0 c0b2 c0b4
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: scrolling: redraw
vesafb: framebuffer at 0xc0000000, mapped to 0xe0808000, size 16384k |
So, it recognices my Radeon 9600 as only VBE 2.0 complaint Google says it's 3.0. What can I do? |
Reflash modified bios. Try google for atiflash and radedit tools. |
|
| Back to top |
|
|
MaxDamage
l33t
Joined: 03 Jan 2004
Posts: 650
Location: Oviedo, Spain
|
| Posted: Mon Sep 06, 2004 8:18 am Post subject: |
|
|
| sarge wrote: | | Reflash modified bios. Try google for atiflash and radedit tools. |
Could you be more specific? Don't know what I've to change in the BIOS.
_________________
La PDA de tungsteno |
|
| Back to top |
|
|
sarge
n00b
Joined: 30 Aug 2004
Posts: 27
|
| Posted: Mon Sep 06, 2004 10:58 am Post subject: |
|
|
Sure..
1. save original bios with atiflash 0 -s bios.bin
2. run radedit , load bios.bin , change default refresh rates and save it (newbios.bin)
3. upload modified bios to VGA : atiflash 0 -p newbios.bin
4. power off and on
I said try google coz i did it 1,5 year ago on my R9700 and since then there r new versions of this tools for sure. |
|
| Back to top |
|
|
chapazzo
n00b
Joined: 15 Sep 2004
Posts: 11
|
| Posted: Thu Sep 16, 2004 2:35 am Post subject: |
|
|
Sup. I bought a nvidia GF4MX440 (before I had a GF2MX400, no refresh probs), and now the framebuffer is locked at 60hz. No kernel parameter, no fbset, no setting can change it. This card is VBE 3.0, and the monitor reports the modes correctly, but I can't change the refresh :/
Does anything similar happened with any other card? Hope someone can help me in this.
System info: Linux 2.6.7 (vanilla, from kernel.org), vesafb-tng-0.9-rc2-2.6.7. dmesg reports as if nothing wrong happened (no errors). |
|
| Back to top |
|
|
grzewho
l33t
Joined: 31 Dec 2002
Posts: 626
Location: /home/g
|
| Posted: Thu Sep 16, 2004 11:42 am Post subject: |
|
|
| ketjow wrote: | | Works fine, although much slower than the "classic" vesafb (delay when switching consoles). Is this normal? |
yeah, I`d like to know that too !
_________________
| Code: | | USE="freedom -software_patents" emerge --deep --update world |
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Documentation, Tips & Tricks
