vesa driver already for amd64!

Code: 
[bas@gw /usr/ports/misc/vesa-kmod]# make
===>  Building for vesa-kmod-20090921
===> dpms (all)
Warning: Object directory not changed from original /usr/ports/misc/vesa-kmod/work/vesa-20090921/dpms
===> s3 (all)
Warning: Object directory not changed from original /usr/ports/misc/vesa-kmod/work/vesa-20090921/s3
===> vesa (all)
Warning: Object directory not changed from original /usr/ports/misc/vesa-kmod/work/vesa-20090921/vesa
/usr/local/libexec/ccache/cc -O2 -fno-strict-aliasing -pipe  -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc   -I. -I@ -I@/contrib/altq -finline-
limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -mcmodel=kernel 
-mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign 
-fformat-extensions -c vesa.c
vesa.c: In function 'vesa_map_buffer':
vesa.c:858: error: 'PAT_WRITE_COMBINING' undeclared (first use in this function)
vesa.c:858: error: (Each undeclared identifier is reported only once
vesa.c:858: error: for each function it appears in.)
*** Error code 1

Stop in /usr/ports/misc/vesa-kmod/work/vesa-20090921/vesa.
*** Error code 1

Stop in /usr/ports/misc/vesa-kmod/work/vesa-20090921.
*** Error code 1

Stop in /usr/ports/misc/vesa-kmod.

Code: 
[bas@gw /usr/home/bas]# uname -a
FreeBSD gw.*.ru 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Sat Sep 26 17:02:24 PETST 2009     bas@gw.*.ru:/usr/src/sys/amd64/compile/GW  amd64

May be some fixes or i do something wrong?
 
I think r197323 wasn't meant for 7.2 release. I've added
Code: 
.if ${OSVERSION} < 702106
EXTRA_PATCHES+= ${PATCHDIR}/extra-patch-vesa.c
.endif
Can you redownload vesa-kmod.diff and try again?
 
  • Thanks
Reactions: Bas
8.0-release ?

Anyone tried this on 8-RELEASE ?

The syscons stuff doesn't seem to work for me, tried it on i386 and amd64, both the same. I can change resolution via vidcontrol after boot but the flags in loader.conf don't seem to do anything. I can see from dmesg that they're being picked up by sc0 but the res never changes.

Any ideas ?
 
are you correct load the modules vesa.ko and rebuild kernel?
look at the post #1 and use the port from post #11
 
The driver and patches were installed via the port on post #11, kernel was rebuilt with 'options SC_PIXEL_MODE' and I can set 1280x1024x32 (MODE_283) after boot.

vidcontrol -i mode

Code: 
283 (0x11b) 0x0000000f G 1280x1024x32 1  8x16  0xa0000 64k 64k 0xe8000000 8000k

kldstat

Code: 
Id Refs Address    Size     Name
 1    5 0xc0400000 b70ec4   kernel
 2    1 0xc0f71000 6a9c     vesa.ko
 3    2 0xc0f78000 1026c    x86bios.ko

cat /boot/loader.conf

Code: 
module_path="/boot/modules;/boot/kernel"
vesa_load="YES"
hint.sc.0.flags="0x11b0180"

dmesg

Code: 
sc0: <System console> at flags 0x11b0180 on isa0
sc0: VGA <16 virtual consoles, flags=0x11b0380>
 
I've done a bit more fiddling and it looks like an issue with the onboard video card in this Dell GX270 (the i386 PC, see below).

Code: 
vgapci0: <VGA-compatible display> port 0xed98-0xed9f mem 0xe8000000-0xefffffff,0xfeb80000-0xfebfffff irq 16 at device 2.0 on pci0
agp0: <Intel 82865G (865G GMCH) SVGA controller> on vgapci0
agp0: detected 8060k stolen memory
agp0: aperture size is 128M

I've found and fitted an old half-height ATI Rage Pro 128 AGP card and now I get a nice black screen mid-way through boot (yey!).

The black screen isn't related to your stuff as I pretty much can't get any graphical resolutions with this card using yours or the default vesa driver.

The amd64 box is also a Dell (745) which I believe has an intel card too, I'll check when I get to work tomorrow.
 
The flags in loader.conf are meant only for 9.0-CURRENT. They touch dev/syscons/syscons.c that's not part of any module. Look at r197085 and subsequent commits. I think it shouldn't be hard to backport them. IOW, r197085 looks almost exactly like the patch in #10 looked.

FYI, the port is just a fairly old snapshot. Expect things more improved in HEAD.
 
excellent, I applied the vesa-kmod.diff patch and then installed the vesa-kmod port. I loaded the vesa.ko after a reboot and I now have 1024x768 on my freebsd-8.0 system. Thanks so much.
 
What is the status of this being committed to the project's source? Has it been PR'd or reviewed by any FreeBSD committers yet?
 
something odd though, even though I can do "vidcontrol MODE_280" manually, it wont take it in the allscreens_flags in rc.conf nor will it work with the hints line in the loader.conf

Am I missing something?
 
aragon said:
What is the status of this being committed to the project's source? Has it been PR'd or reviewed by any FreeBSD committers yet?
Click to expand...
See #28 post in this thread. Ping delphij@ for MFC in 7.x/8.x.
bigwillyg said:
it wont take it in the allscreens_flags in rc.conf
Click to expand...
Do you have vesa_load=YES in loader.conf? allscreen_flags basically does same thing as vidcontrol MODE_280. It won't change mode to a graphic one unless vesa.ko is loaded.
Code: 
        # set this mode for all virtual screens
        #
        if [ -n "${allscreens_flags}" ]; then
                sc_init
                echo -n ' allscreens'
                for ttyv in /dev/ttyv*; do
                        vidcontrol ${allscreens_flags} < ${ttyv} > ${ttyv} 2>&1
                done
        fi
 
i can't get this to work on my new setup 8.0R-p2 amd64.
i am getting just a black screen on some modes and some other modes even put the monitor in power saving modes.
can someone explain post #41? debug.bootverbose in loader.conf?
 
Hi guys

I decided to test this patch (i used ports version), everything is ok until i will not start Xorg, then when i'm switching between console and X, i'm getting odd colors on console, text which should be white turnes blue etc. When i try to shutdown system my box hangs

Amd64, FreeBSD 8-STABLE, Tyan K8SD PRO, PowerColor RadeonHD 2400 PCI

Regards
 
I tried this today in 8-STABLE. Works awesomely! Complements to the chef. :)

Has anyone figured out how to correctly craft hint.sc.0.flags so that the kernel sets a mode at bootup other than 800x600x32?
 
You must log in or register to reply here.
Back
Top