You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(9) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(12) |
Feb
(10) |
Mar
|
Apr
(5) |
May
(3) |
Jun
|
Jul
(5) |
Aug
(7) |
Sep
(15) |
Oct
(4) |
Nov
(3) |
Dec
(7) |
| 2003 |
Jan
(5) |
Feb
(30) |
Mar
(5) |
Apr
(13) |
May
(12) |
Jun
(11) |
Jul
(1) |
Aug
(7) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(7) |
| 2004 |
Jan
(4) |
Feb
(9) |
Mar
(16) |
Apr
(42) |
May
(5) |
Jun
(11) |
Jul
(3) |
Aug
(39) |
Sep
(5) |
Oct
(32) |
Nov
(27) |
Dec
|
| 2005 |
Jan
(11) |
Feb
(8) |
Mar
(22) |
Apr
(26) |
May
(9) |
Jun
(10) |
Jul
(7) |
Aug
(43) |
Sep
(23) |
Oct
(18) |
Nov
(15) |
Dec
(15) |
| 2006 |
Jan
(7) |
Feb
(16) |
Mar
(10) |
Apr
(1) |
May
(16) |
Jun
(8) |
Jul
(3) |
Aug
(35) |
Sep
(7) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2007 |
Jan
(2) |
Feb
(30) |
Mar
(6) |
Apr
(7) |
May
(5) |
Jun
|
Jul
(15) |
Aug
(12) |
Sep
(22) |
Oct
(48) |
Nov
(9) |
Dec
(7) |
| 2008 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(4) |
Jun
(1) |
Jul
(5) |
Aug
(4) |
Sep
(4) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
| 2009 |
Jan
(3) |
Feb
|
Mar
|
Apr
(4) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Michael Peddemors <michael@wi...> - 2001-11-20 07:04:53
|
Well I have a lot of them :) Tried working them out myself, and finally gave in and trying the list.. First of all.. I have an issue where I want to support many types of Video cards with a single kernel.. SO I compiled in all of the framebuffer hardwares into the kernel, and also included the generic VESA VGA driver as well, thinking that it would try the other hardwares, and fallback to VESA if it didn't find any other hardwares.. (I am not sure if that is working correctly, but..) Anyways, I have my thinclient booting up and it SEEMS to be in -depth 16 But I also see an entry where the significant bits are only 8 bits... (see below) My problem is that no matter what I seem to do I am getting only 256 color on the X display... Thinclient is calling xdm on the host via X -query <hostname> ThinClient logs attached.. Any ThinClient experts with good configs to help out here? -- "Catch the Magic of Linux..." -------------------------------------------------------- Michael Peddemors - Senior Consultant LinuxAdministration - Internet Services NetworkServices - Programming - Security Wizard IT Services http://www.wizard.ca Linux Support Specialist - http://www.linuxmagic.com -------------------------------------------------------- (604)589-0037 Beautiful British Columbia, Canada |
|
From: Petr Vandrovec <vandrove@vc...> - 2001-11-18 03:15:36
|
On Sat, Nov 17, 2001 at 07:24:37AM +0700, Bill Thompson wrote: > Hi, > > When my system boots, it comes up using vgafb. > How can I change this to use matroxfb? If you have only one VGA device in your box, do not compile vgafb. If you have more than one VGA device, and they are all Matroxes, do not compile vgafb. If you have more than one VGA device, and only some of them are Matroxes, you must make Matrox your secondary device, as vgafb does handle only primary devices. You can also disable vgafb at boottime by using video=vga16:off, but I strongly recommend you to remove vgafb from your kernel completely. Best regards, Petr Vandrovec vandrove@... |
|
From: Bill Thompson <billt@sa...> - 2001-11-17 00:24:40
|
Hi, When my system boots, it comes up using vgafb. How can I change this to use matroxfb? Bill Mandrake 8.1 XFree86 4.1.0-21mdk Matrox G400 w/32MB SDRAM -- "Quando Omni Flunkus Moritati" (When all else fails, play dead!) |
|
From: jakeR <jake@as...> - 2001-11-16 14:12:13
|
hey there, can someone please tell me how to get my fb device working on an IBM X21 notebook? i tried many arguments, but all result in a blank screen. i tried lots of stuff like: video=atyfb:1024x768-8@... video=atyfb,1024x768 and lots of other combinations. also, is this driver faster than the vesa driver? i can get that to work. thanks, jake |
|
From: <R.Young@ir...> - 2001-11-13 19:12:29
|
Dear Wolfram, Thanks for the information. That explains the problem. The advantage of using rivafb over vesafb is that it is a lot faster, but I guess I have no choice. Hope eventually Nvidia will either release their source, or ensure that their drivers work with rivafb, Regards, Roger roger@... On Tue, Nov 13, 2001 at 06:06:03AM -0500, R.Young@... wrote: > > I wonder if you can help with a problem concerning rivafb which is > compiled into the linux kernel (2.4.12). On my system (P3, 733 MHz, > GA660+ graphics card with RIVA TNT2 chipset) this Riva fb driver > appears to be incompatible with the RIVA TNT2 (kernel/GLX) drivers > (v.1.0-1541) supplied by NVIDIA. What happens is that I get a complete > system freeze on attempting to leave X, or to reboot/close down. This > does not occur when rivafb is used in conjunction with the "nv" driver > that is part of XFree86 (v.4.1.0); nor does it occur if I use vesafb > with the NVIDIA kernel/GLX "NVdriver"; but only when rivafb is > combined with NVdriver. Because of the freeze this combination (which > is obviously desireable) is not really viable at the moment... > > I will be very grateful if anyone can assist, The rivafb and the NVdriver are simply not compatible, as they try to access the same piece of hardware independently. Contact Andy Ritger <ARitger@...> for more information (he recommends to use the "standard" vesafb instead). -- Mit freundlichen Gruessen / Yours sincerely Wolfram Schlich * E-Mail: wolfram@... * ICQ: UIN 35713642 Postal: Berghof, D-56626 Andernach-Kell * Phone: +49-(0)2636-941194 |
|
From: Wolfram Schlich <wolfram@sc...> - 2001-11-13 13:13:48
|
On Tue, Nov 13, 2001 at 06:06:03AM -0500, R.Young@... wrote: > > I wonder if you can help with a problem concerning rivafb which is > compiled into the linux kernel (2.4.12). On my system (P3, 733 MHz, > GA660+ graphics card with RIVA TNT2 chipset) this Riva fb driver > appears to be incompatible with the RIVA TNT2 (kernel/GLX) drivers > (v.1.0-1541) supplied by NVIDIA. What happens is that I get a complete > system freeze on attempting to leave X, or to reboot/close down. This > does not occur when rivafb is used in conjunction with the "nv" driver > that is part of XFree86 (v.4.1.0); nor does it occur if I use vesafb > with the NVIDIA kernel/GLX "NVdriver"; but only when rivafb is > combined with NVdriver. Because of the freeze this combination (which > is obviously desireable) is not really viable at the moment... > > I will be very grateful if anyone can assist, The rivafb and the NVdriver are simply not compatible, as they try to access the same piece of hardware independently. Contact Andy Ritger <ARitger@...> for more information (he recommends to use the "standard" vesafb instead). -- Mit freundlichen Gruessen / Yours sincerely Wolfram Schlich * E-Mail: wolfram@... * ICQ: UIN 35713642 Postal: Berghof, D-56626 Andernach-Kell * Phone: +49-(0)2636-941194 |
|
From: <R.Young@ir...> - 2001-11-13 11:06:15
|
Hello everyone, I wonder if you can help with a problem concerning rivafb which is compiled into the linux kernel (2.4.12). On my system (P3, 733 MHz, GA660+ graphics card with RIVA TNT2 chipset) this Riva fb driver appears to be incompatible with the RIVA TNT2 (kernel/GLX) drivers (v.1.0-1541) supplied by NVIDIA. What happens is that I get a complete system freeze on attempting to leave X, or to reboot/close down. This does not occur when rivafb is used in conjunction with the "nv" driver that is part of XFree86 (v.4.1.0); nor does it occur if I use vesafb with the NVIDIA kernel/GLX "NVdriver"; but only when rivafb is combined with NVdriver. Because of the freeze this combination (which is obviously desireable) is not really viable at the moment... I will be very grateful if anyone can assist, Thankyou, Roger Young. roger@... |
|
From: Bernd Oliver Christiansen <bernd@cs...> - 2001-10-22 15:42:43
|
Hello: I'm running XF86_FBDev on a JavaStation Krups (essentially a diskless Sparc) mounting a RedHat 6.2 root file system. While XF86_FBDev basically works, I'm left with some annoyances :-( (1) When I start X, everthing works just fine except that I have a small white border (the color seems to be the one of the Krups' boot screen) around the X desktop. My Monitor is a Sony 420GS. How do I get rid of the border? Does the XF86_FBDev X server look at ModeLine entries in XF86Config's section "Monitor". The sample config file from ultralinux.org has some ModeLine entries, but they are commented out. At this point, I don't have any ModeLine entries. Any suggestions? (2) X comes up with 1024x768 pixels. I'd like to run 1280x1024 pixels. Where is this specified? Is it a mode entry in XF86Config's section "Screen"? Or is it rather a kernel parameter? Would fbset help here? (3) Also, my monitor says it's running at 60Hz. I really would like to have a more ergonomic refresh rate of, say, 75Hz. Again, is this done by a ModeLine entry, a kernel parameter or fbset? Thanks! -Bernd |
|
From: Silver <SilverBanana@gm...> - 2001-10-21 20:45:09
|
Hi! Actually I have a Voodoo5 5500 and I'd like to use framebuffer and it's console driver. Everything works pretty good exept tow things: * The cursor is buggy. It is a not just a little underscore or sth. similar but a large box (about 3*4cm on my 19" screen). * Directly after startup the upper part of the screen is garbled. Any idea how to fix any of these bugs (especcially the cursor bug)? Thanks in advance and sorry for my bad english Silver |
|
From: Frank Neuber <frank.neuber@gm...> - 2001-10-18 09:54:10
|
On 17 Oct 2001, Bruno Clermont wrote: Many thanks Bruno, a bad information is better then nothing. I will check out the XFree86 framebuffer driver. Frank > I switched to a SVGA framebuffer and used XFree86 framebuffer driver... > Slow as hell, but better than nothing, especialy for non-gaming use. > > I tried a vanilla 2.4.9 couple of months later, hoping to see a > difference. It still fade to black and need a reboot. > > I finally stop using the laptop and didn't tried until then. > > On Wed, 2001-10-17 at 09:05, Frank Neuber wrote: > Hi Bruno and all fbdev gurus, > I have exactly the same problem with my COMPAQ Presario laptop. > After loading the module "atyfb" the screen go black and only display some > colored pixels at the bottom line :-(. > The X-Display is then also broken ... > I did my tests wit the 2.4.9 kernel. The patch atyfb-new-20010117.diff > don't work with 2.4.9 kernel. I think the patch is present in this > kernel version. > > lspci: > 01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage P/M > Mobility AGP 2x (rev 64) > > lspci -nvvv > > 01:00.0 Class 0300: 1002:4c4d (rev 64) > Subsystem: 0e11:b11b > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping+ SERR- FastB2B- > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- > Latency: 66 (2000ns min), cache line size 08 > Interrupt: pin A routed to IRQ 5 > Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=16M] > Region 1: I/O ports at 9000 [size=256] > Region 2: Memory at f4200000 (32-bit, non-prefetchable) [size=4K] > Expansion ROM at <unassigned> [disabled] [size=128K] > Capabilities: [50] AGP version 1.0 > Status: RQ=255 SBA+ 64bit- FW- Rate=x1,x2 > Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none> > Capabilities: [5c] Power Management version 1 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > > Did you solve your fbdev problem? > At last I have the same questions: > is it a know problem by you? > if not, are you interested to fix it? > if yes, how can i be usefull? |
|
From: Bruno Clermont <pooh@gn...> - 2001-10-17 21:57:59
|
I switched to a SVGA framebuffer and used XFree86 framebuffer driver...
Slow as hell, but better than nothing, especialy for non-gaming use.
I tried a vanilla 2.4.9 couple of months later, hoping to see a
difference. It still fade to black and need a reboot.
I finally stop using the laptop and didn't tried until then.
On Wed, 2001-10-17 at 09:05, Frank Neuber wrote:
Hi Bruno and all fbdev gurus,
I have exactly the same problem with my COMPAQ Presario laptop.
After loading the module "atyfb" the screen go black and only display some
colored pixels at the bottom line :-(.
The X-Display is then also broken ...
I did my tests wit the 2.4.9 kernel. The patch atyfb-new-20010117.diff
don't work with 2.4.9 kernel. I think the patch is present in this
kernel version.
lspci:
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage P/M
Mobility AGP 2x (rev 64)
lspci -nvvv
01:00.0 Class 0300: 1002:4c4d (rev 64)
Subsystem: 0e11:b11b
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 66 (2000ns min), cache line size 08
Interrupt: pin A routed to IRQ 5
Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=16M]
Region 1: I/O ports at 9000 [size=256]
Region 2: Memory at f4200000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [50] AGP version 1.0
Status: RQ=255 SBA+ 64bit- FW- Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
Capabilities: [5c] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Did you solve your fbdev problem?
At last I have the same questions:
is it a know problem by you?
if not, are you interested to fix it?
if yes, how can i be usefull?
Best regards
Frank
--
_/_/_/_/ _// _/ Frank Neuber
_/ _/_/ _/ frank.neuber@... (private)
_/_/_/ _/ _/ _/
_/ _/ _/_/ neuber@...
_/ _/ // http://www.opensource-systemberatung.de
|
|
From: Frank Neuber <frank.neuber@gm...> - 2001-10-17 14:39:11
|
Hi Bruno and all fbdev gurus,
I have exactly the same problem with my COMPAQ Presario laptop.
After loading the module "atyfb" the screen go black and only display some
colored pixels at the bottom line :-(.
The X-Display is then also broken ...
I did my tests wit the 2.4.9 kernel. The patch atyfb-new-20010117.diff
don't work with 2.4.9 kernel. I think the patch is present in this
kernel version.
lspci:
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage P/M
Mobility AGP 2x (rev 64)
lspci -nvvv
01:00.0 Class 0300: 1002:4c4d (rev 64)
Subsystem: 0e11:b11b
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 66 (2000ns min), cache line size 08
Interrupt: pin A routed to IRQ 5
Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=16M]
Region 1: I/O ports at 9000 [size=256]
Region 2: Memory at f4200000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [50] AGP version 1.0
Status: RQ=255 SBA+ 64bit- FW- Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
Capabilities: [5c] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Did you solve your fbdev problem?
At last I have the same questions:
is it a know problem by you?
if not, are you interested to fix it?
if yes, how can i be usefull?
Best regards
Frank
--
_/_/_/_/ _// _/ Frank Neuber
_/ _/_/ _/ frank.neuber@... (private)
_/_/_/ _/ _/ _/
_/ _/ _/_/ neuber@...
_/ _/ // http://www.opensource-systemberatung.de
|
|
From: Jeff Lessem <Jeff.Lessem@Colorado.EDU> - 2001-10-16 06:27:32
|
I am having some difficulty getting the aty128fb to work with the ATI Rage 128 Mobility LF adapter in my Dell Inspiron 5000e. The display is a 1600x1200 flat panel. Passing video=aty128fb:1600x1200-16bpp@... on the kernel command line causes the screen to crash and the machine to lockup. This occurs as soon as the fb device is initilialized during kernel loading. That 1600x1200 setting is what I use successfully in X. Other things, such as video=aty128fb, or nothing at all also cause the same screen crash and hard lockup. I have this problem through at least 2.4.10. I tried building with the debug option enabled, but aty128fb.c does not compile. Any advice would be greatly appreciated. If there is any information which would be useful that I have not provided, please let me know. -- Thanks, Jeff Lessem. |
|
From: Bakonyi Ferenc <fero@dr...> - 2001-10-09 07:37:34
|
Wolfram Schlich <lists@...> wrote: > hi all, > > i don't get rivafb to (correctly) accept my "video=rivafb:[...]" param > at boot time. perhaps anyone can help me regarding valid modes, e.g. > 1024x768, 16bit, 85Hz). thanks in advance. Try "video=riva:1024x768-16@..." Regards: Ferenc Bakonyi |
|
From: Wolfram Schlich <lists@sc...> - 2001-10-08 20:45:27
|
hi all, i don't get rivafb to (correctly) accept my "video=rivafb:[...]" param at boot time. perhaps anyone can help me regarding valid modes, e.g. 1024x768, 16bit, 85Hz). thanks in advance. -- Mit freundlichen Gruessen / Yours sincerely Wolfram Schlich * E-Mail: wolfram@... * ICQ: UIN 35713642 Postal: Berghof, D-56626 Andernach-Kell * Phone: +49-(0)2636-941194 |