| View previous topic :: View next topic |
| Author |
Message |
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
 Posted: Thu Jul 14, 2005 2:58 am Post subject: vesafb-tng and x86_64 |
 |
|
Sorry if this has been posted before...
Any way to get it working?
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
 |
Headrush
Watchman
Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World
|
| Posted: Thu Jul 14, 2005 3:22 am Post subject: |
|
|
| No. Just use vesa, not that much diifferent and only seen for seconds at startup anyways. |
|
| Back to top |
|
|
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
| Posted: Thu Jul 14, 2005 3:34 am Post subject: |
|
|
alright. I just like the options granted by tng.
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
|
Headrush
Watchman
Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World
|
| Posted: Thu Jul 14, 2005 3:49 am Post subject: |
|
|
| Cinder6 wrote: | | alright. I just like the options granted by tng. |
I never understood the fascination with the need for a 75MHz refresh rate over a 60MHz refresh rate for a bootup splash screen. 
It's a fairly static image anyways and not like a rapidly changing first person shooter!
Of course I say that, yet found the need to have the graphic GRUB boot loader with animations.  |
|
| Back to top |
|
|
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
| Posted: Thu Jul 14, 2005 3:54 am Post subject: |
|
|
Well, I sometimes work off the terminal...
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
| Posted: Fri Jul 22, 2005 4:36 pm Post subject: |
|
|
| Cinder6 wrote: | | Well, I sometimes work off the terminal... |
That and the fact that when I exit X my screen is all screwy. |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Sat Jul 23, 2005 9:05 am Post subject: |
|
|
i always wondered what happens if you actually DO compile vfb-tng on AMD64 
i have a 32bit system, so i could never test it,
but if someone is really brave, try this:
go to drivers/video/Kconfig file in kernel source patched with vfb-tng and replace
| Code: |
config FB_VESA_TNG
bool "vesafb-tng"
depends on !X86_64
select FB_MODE_HELPERS
|
with
| Code: |
config FB_VESA_TNG
bool "vesafb-tng"
select FB_MODE_HELPERS
|
basically removing the dependency on NOT x86_64,
now you at least can choose it and try to compile 
_________________
Retired gentoo user |
|
| Back to top |
|
|
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
| Posted: Sat Jul 23, 2005 5:20 pm Post subject: |
|
|
hehe, alright, Tiger. sounds fun. if it works, maybe you could put it in nitro6!
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Sat Jul 23, 2005 5:39 pm Post subject: |
|
|
_________________
Retired gentoo user |
|
| Back to top |
|
|
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
| Posted: Sun Jul 24, 2005 7:37 pm Post subject: |
|
|
okay, I just tried compiling it, and it was a no go. got this error:
| Code: | * ERROR: Failed to compile the "bzImage" target...
* -- Grepping log... --
CC arch/x86_64/kernel/msr.o
LD arch/x86_64/kernel/cpuid.o
CC arch/x86_64/kernel/apic.o
CC kernel/fork.o
CC arch/x86_64/kernel/nmi.o
arch/x86_64/kernel/nmi.c:310: warning: initialization from incompatible pointer type
--
LD arch/x86_64/kernel/built-in.o
CC kernel/resource.o
CC mm/bootmem.o
CC mm/filemap.o
CC kernel/sysctl.o
kernel/sysctl.c:229: warning: 'one' defined but not used
--
CC drivers/block/scsi_ioctl.o
CC fs/partitions/mac.o
CC fs/partitions/ldm.o
CC drivers/block/noop-iosched.o
CC drivers/block/as-iosched.o
drivers/block/as-iosched.c:167: warning: initialization from incompatible pointer type
--
CC drivers/pci/access.o
CC fs/xfs/xfs_attr.o
CC drivers/pci/bus.o
CC drivers/pci/probe.o
drivers/pci/probe.c: In function `pci_read_bases':
drivers/pci/probe.c:166: warning: large integer implicitly truncated to unsigned type
drivers/pci/probe.c:216: warning: large integer implicitly truncated to unsigned type
--
LD fs/xfs/built-in.o
LD fs/built-in.o
CC drivers/video/console/bitblit.o
CC sound/sound_core.o
sound/sound_core.c: In function `sound_insert_unit':
sound/sound_core.c:178: warning: passing arg 1 of `class_simple_device_add' from incompatible pointer type
sound/sound_core.c: In function `cleanup_soundcore':
sound/sound_core.c:565: warning: passing arg 1 of `class_simple_destroy' from incompatible pointer type
sound/sound_core.c: In function `init_soundcore':
sound/sound_core.c:575: warning: assignment from incompatible pointer type
--
CC sound/core/pcm_memory.o
CC drivers/video/softcursor.o
CC sound/core/rawmidi.o
CC drivers/video/vesafb-tng.o
In file included from drivers/video/vesafb-tng.c:27:
include/video/vesa.h:16: error: field `regs' has incomplete type
drivers/video/vesafb-tng.c: In function `vesa_setpalette':
drivers/video/vesafb-tng.c:138: warning: unused variable `entry'
drivers/video/vesafb-tng.c:139: warning: unused variable `mytask'
drivers/video/vesafb-tng.c: In function `vesafb_read_proc_vbe_info':
drivers/video/vesafb-tng.c:588: warning: cast to pointer from integer of different size
drivers/video/vesafb-tng.c:589: warning: cast to pointer from integer of different size
drivers/video/vesafb-tng.c:590: warning: cast to pointer from integer of different size
drivers/video/vesafb-tng.c:591: warning: cast to pointer from integer of different size
drivers/video/vesafb-tng.c: In function `vesafb_vbe_init':
drivers/video/vesafb-tng.c:629: warning: cast to pointer from integer of different size
drivers/video/vesafb-tng.c:630: warning: cast to pointer from integer of different size
drivers/video/vesafb-tng.c:630: warning: cast to pointer from integer of different size
drivers/video/vesafb-tng.c:631: warning: cast to pointer from integer of different size
drivers/video/vesafb-tng.c:637: warning: cast to pointer from integer of different size
drivers/video/vesafb-tng.c:646: warning: cast to pointer from integer of different size
make[2]: *** [drivers/video/vesafb-tng.o] Error 1
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
CC sound/core/rtctimer.o
CC sound/core/timer.o
CC sound/core/sound.o
sound/core/sound.c: In function `snd_register_device':
sound/core/sound.c:234: warning: passing arg 1 of `class_simple_device_add' from incompatible pointer type
--
LD sound/synth/built-in.o
LD sound/built-in.o
* Gentoo Linux Genkernel; Version 3.2.10
* Running with options: --no-clean --no-mrproper --menuconfig all
* ERROR: Failed to compile the "bzImage" target...
* -- End log... -- |
Oh well, didn't have high hopes for it, anyways 
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
| Posted: Sun Jul 24, 2005 11:36 pm Post subject: |
|
|
| n00b question but who writes these drivers? Maybe we can send a petition to who mever wrote the original driver to update it for x86_64? |
|
| Back to top |
|
|
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
| Posted: Sun Jul 24, 2005 11:43 pm Post subject: |
|
|
Honestly, I don't know who wrote vesafb-tng off the top of my head, but we could easily look at the top of the source code (authors usually write their names and contact info).
I wouldn't be surprised if s/he is working on it, though. However, it might give him/her some encouragement if a bunch of people start asking about it.
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
|
Deranger
Veteran
Joined: 26 Aug 2004
Posts: 1215
|
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
| Posted: Mon Jul 25, 2005 4:06 am Post subject: |
|
|
he left contact info, I guess you all know what we must do now.  |
|
| Back to top |
|
|
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
| Posted: Mon Jul 25, 2005 4:22 am Post subject: |
|
|
Yes. ATTACK!
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
|
kreedcarmoch
n00b
Joined: 09 Apr 2005
Posts: 51
Location: San Antonio, Texas
|
| Posted: Mon Jul 25, 2005 6:34 am Post subject: |
|
|
| Troubleshooting wrote: | | The patch will not work on 64-bit systems (x86_64 and ia64), because the vm86 mode is not supported for OSes running in 64-bit mode. If you happen to own a 64-bit box, you're limited to plain vesafb. You may still use vesafb-tng's predecessor - the vesafb-rrc patch, though. (it should work with all 2.6.x kernels). |
|
|
| Back to top |
|
|
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
| Posted: Mon Jul 25, 2005 7:09 am Post subject: |
|
|
What is vm86? Anyone I can attack?
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Mon Jul 25, 2005 7:32 am Post subject: |
|
|
| kreedcarmoch wrote: | | Troubleshooting wrote: | | The patch will not work on 64-bit systems (x86_64 and ia64), because the vm86 mode is not supported for OSes running in 64-bit mode. If you happen to own a 64-bit box, you're limited to plain vesafb. You may still use vesafb-tng's predecessor - the vesafb-rrc patch, though. (it should work with all 2.6.x kernels). |
|
Hmm, tahts ghay....
especially for you guys
_________________
Retired gentoo user |
|
| Back to top |
|
|
|
Unsupported Software
