Menu
▾
▴
linux-fbdev-devel
|
From: Carl W. S. <ch...@re...> - 2001-12-23 23:05:15
|
I just built 2.4.17, and decided to try framebuffer support for my G450. however, I found some bugs. 1. if one doesn't specify a video= option at boot time; the console will hang, and the machine soon locks up. (I know it is locked because my LCD panel attached to the serial port displays no information, and I tried pinging it across the network). 2. if one does boot; and then tries to start X (even XFree86 -configure as root), the system will lock completely. (tho I *did* have one successful startx once; and can't figure out why; since it always failed with a hard lockup otherwise). no X log is generated. it just locks immediately. the time that it did boot sucessfully; I couldn't see anything unusual in the log; tho I'm not an X programmer by any stretch. :) 3. trying to use fbset on the second head of the G450 will fail, like so: root@steel:~# fbset -fb /dev/fb2 '640x480-75' ioctl FBIOPUT_VSCREENINFO: Invalid argument root@steel:~# fbset -fb /dev/fb2 '1280x1024-75' ioctl FBIOPUT_VSCREENINFO: Invalid argument root@steel:~# fbset -fb /dev/fb2 1280x1024-75 ioctl FBIOPUT_VSCREENINFO: Invalid argument the first time you run this, it gives: Warning: Remapping obsolete /dev/fb* minor 64 to 2 nothing that I can see, goes into syslog about these issues. options I'm booting with are: 2.4.17 video=matrox:vesa:0x11A what debugging information should I include? I saved a dmesg and my kernel .config file as well. rather than load the list with them, I put them at: http://copper.redchrome.org/~chrome/2.4.17-dmesg http://copper.redchrome.org/~chrome/2.4.17-config I'm new to this list. How can I help debug this? Carl Soderstrom -- Network Engineer Real-Time Enterprises (952) 943-8700 |
|
From: Petr V. <van...@vc...> - 2001-12-24 01:22:09
|
On Sun, Dec 23, 2001 at 05:05:08PM -0600, Carl Wilhelm Soderstrom wrote: > 1. if one doesn't specify a video= option at boot time; the console will > hang, and the machine soon locks up. (I know it is locked because my > LCD panel attached to the serial port displays no information, and I tried > pinging it across the network). Which option you need to specify to 'video='? You are probably using vesafb together with matroxfb, or matroxfb together with vga16fb. It does not work. And after I looked into your dmesg - are you sure that it does not die due to atyfb? And G450 driver in kernel cannot initialize G450 from scratch (== you must use matrox as primary device, initialized by BIOS). > 2. if one does boot; and then tries to start X (even XFree86 -configure as > root), the system will lock completely. (tho I *did* have one successful > startx once; and can't figure out why; since it always failed with a hard > lockup otherwise). no X log is generated. it just locks immediately. the > time that it did boot sucessfully; I couldn't see anything unusual in the > log; tho I'm not an X programmer by any stretch. :) Make sure that you are not running mga driver from Matrox. Besides of that, it works everywhere else... Make sure that /proc/fb lists only Matrox framebuffers, not something else: ppc:/cdrom# cat /proc/fb 0 MATROX VGA 1 MATROX CRTC2 And of course - are you sure that X do not die because of they are enabling legacy VGA, causing PCI parity error, and thus bringing your box down? > 3. trying to use fbset on the second head of the G450 will fail, like so: > root@steel:~# fbset -fb /dev/fb2 '640x480-75' > ioctl FBIOPUT_VSCREENINFO: Invalid argument > root@steel:~# fbset -fb /dev/fb2 '1280x1024-75' > ioctl FBIOPUT_VSCREENINFO: Invalid argument > root@steel:~# fbset -fb /dev/fb2 1280x1024-75 > ioctl FBIOPUT_VSCREENINFO: Invalid argument Fix your /etc/fbset.modes. Secondary head (as documented) cannot do 8bpp, it can do only 16bpp and 32bpp. > the first time you run this, it gives: > Warning: Remapping obsolete /dev/fb* minor 64 to 2 Fix your /dev/fb* nodes. If you are not running 2.2.x kernels, /dev/fb1 should be 29,1, /dev/fb2 should be 29,2 and so on. > what debugging information should I include? I saved a dmesg and my kernel > .config file as well. rather than load the list with them, I put them at: > http://copper.redchrome.org/~chrome/2.4.17-dmesg > http://copper.redchrome.org/~chrome/2.4.17-config > > I'm new to this list. How can I help debug this? Remove either atyfb + ATI or matroxfb + G450 from your box, and try again... Petr Vandrovec van...@vc... |
|
From: Carl W. S. <ch...@re...> - 2001-12-24 02:58:19
|
> Which option you need to specify to 'video='? You are probably using > vesafb together with matroxfb, or matroxfb together with vga16fb. It > does not work. no, I recompiled my kernel after reading the docs, and turned off vesafb. > And after I looked into your dmesg - are you sure that > it does not die due to atyfb? yeah, that's a possibility. I'll build a new kernel without that. > And G450 driver in kernel cannot initialize > G450 from scratch (== you must use matrox as primary device, initialized > by BIOS). yep. the G450 is the primary display. > Make sure that you are not running mga driver from Matrox. nope. running CVS X 4.1.99.1 (tho the library path is screwed up, so that's why it's loading the 4.1.0 modules. I'll fix that before testing more). > Besides of that, > it works everywhere else... Make sure that /proc/fb lists only Matrox > framebuffers, not something else: > > ppc:/cdrom# cat /proc/fb > 0 MATROX VGA > 1 MATROX CRTC2 > > And of course - are you sure that X do not die because of they are enabling > legacy VGA, causing PCI parity error, and thus bringing your box down? so if I just set it to use the 'fbdev' driver, and not probe (-configure), I've got a better chance of making it work? so why does framebuffer console + MGA X + G400 not cause problems on the machines we have at work? > Fix your /etc/fbset.modes. Secondary head (as documented) cannot do 8bpp, > it can do only 16bpp and 32bpp. hmm, looks like I don't have an /etc/fbset.modes. will look into that. > Fix your /dev/fb* nodes. If you are not running 2.2.x kernels, /dev/fb1 > should be 29,1, /dev/fb2 should be 29,2 and so on. ok. will do. > Remove either atyfb + ATI or matroxfb + G450 from your box, and try again... thanks much! will build another kernel with fewer things, and see what breaks then. Carl Soderstrom -- Network Engineer Real-Time Enterprises (952) 943-8700 |
|
From: Carl W. S. <ch...@re...> - 2001-12-24 07:19:11
|
> > And after I looked into your dmesg - are you sure that > > it does not die due to atyfb? > yeah, that's a possibility. I'll build a new kernel without that. the ATI framebuffer support seems to have been the issue. without that; everything works reasonably fine. this of course leads to the question; why does the addition of an ati framebuffer cause these problems? > > Fix your /etc/fbset.modes. Secondary head (as documented) cannot do 8bpp, > > it can do only 16bpp and 32bpp. > hmm, looks like I don't have an /etc/fbset.modes. will look into > that. I think you meant /etc/fb.modes. yes, I do have that. giving the -depth 16 option in fbset makes it set the display properly. it would be nice to give a more helpful error message in situations like this; but I expect this is a problem that's not entirely trivial to generalize; since it depends on the graphics card's limitations. I did notice one more bug: if one has a framebuffer for the G450's second head, and uses fbset to operate upon it before starting X; the image displayed on that screen once X is started, will be offset to the right by about an inch. if one doesn't use fbset before starting X (this is just plain MGA X, not fbdev); then the image appears in the proper place. is this an issue with X, or the framebuffer? I'm going to suspect X, since it ought to reset things properly before starting; but I know that G450 support in X is pretty shaky in places (DRI is buggy), and unfortunately there isn't an active maintainer that I've seen. :( thanks much for the help! Carl Soderstrom -- Network Engineer Real-Time Enterprises (952) 943-8700 |
|
From: Geert U. <ge...@li...> - 2001-12-24 09:43:45
|
On Mon, 24 Dec 2001, Carl Wilhelm Soderstrom wrote:
> > > And after I looked into your dmesg - are you sure that
> > > it does not die due to atyfb?
> > yeah, that's a possibility. I'll build a new kernel without that.
>
> the ATI framebuffer support seems to have been the issue. without
> that; everything works reasonably fine.
> this of course leads to the question; why does the addition of an
> ati framebuffer cause these problems?
Because you have a RAGE XL, which isn't supported that well yet, and which
doesn't seem to be initialized by the BIOS (cfr. `512K SGRAM', which I doubt
you have).
Unlike matroxfb (on some cards, not G450), atyfb cannot initialize cards from
scratch yet.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Carl W. S. <ch...@re...> - 2001-12-24 16:08:15
|
On Mon, Dec 24, 2001 at 10:43:26AM +0100, Geert Uytterhoeven wrote: > Because you have a RAGE XL, which isn't supported that well yet, and which > doesn't seem to be initialized by the BIOS (cfr. `512K SGRAM', which I doubt > you have). > > Unlike matroxfb (on some cards, not G450), atyfb cannot initialize cards from > scratch yet. aha. I see. well, this is what I get for grabbing the cheapest vid board at the store. :) btw, I read your paper on the Linux 2.2 framebuffer device, Mr. Uytterhoeven; excellent piece. very good introduction to the whole matter. :) Carl Soderstrom -- Network Engineer Real-Time Enterprises (952) 943-8700 |
|
From: Petr V. <van...@vc...> - 2001-12-24 21:51:32
|
On Mon, Dec 24, 2001 at 10:08:07AM -0600, Carl Wilhelm Soderstrom wrote: > On Mon, Dec 24, 2001 at 10:43:26AM +0100, Geert Uytterhoeven wrote: > > Because you have a RAGE XL, which isn't supported that well yet, and which > > doesn't seem to be initialized by the BIOS (cfr. `512K SGRAM', which I doubt > > you have). > > > > Unlike matroxfb (on some cards, not G450), atyfb cannot initialize cards from > > scratch yet. > > aha. I see. well, this is what I get for grabbing the cheapest vid board at > the store. :) In that case: (1) Get kernel 2.4.17 (2) Download ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/mga-2.4.17.gz (3) Apply patch (zcat mga-2.4.17.gz | (cd /usr/src/linux-2.4.17; patch -p1)) (4) Run kernel configuration tool and answer yes for G100-G550 support, G450 dualhead support, and for Matrox /proc interface support. You can answer yes to something else too, but these three are mandatory. (5) Make sure that BIOS uses ATI for its output (6) Reboot and pray (7) You should get nice picture on ATI (either from BIOS, vgacon or atyfb) and nice picture on both G450 heads (though you'll see nothing on them except color dots after bootup; con2fb & matroxset is your friend) (8) If (7) did not happen, send me contents of all /proc/driver/mga/fb*/* you'll find (you should find one 'bios' and one 'pins' for each Matrox video card in your box). And I have no idea why second head picture is on different place when you use fbset before X. Petr Vandrovec van...@vc... |
|
From: Carl W. S. <ch...@re...> - 2002-01-10 05:21:05
|
once a long time ago, Petr Vandrovec was kind enough to write: > In that case: > (1) Get kernel 2.4.17 > (2) Download ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/mga-2.4.17.gz > (3) Apply patch (zcat mga-2.4.17.gz | (cd /usr/src/linux-2.4.17; patch -p1)) > (4) Run kernel configuration tool and answer yes for G100-G550 support, > G450 dualhead support, and for Matrox /proc interface support. You can > answer yes to something else too, but these three are mandatory. > (5) Make sure that BIOS uses ATI for its output > (6) Reboot and pray > (7) You should get nice picture on ATI (either from BIOS, vgacon or atyfb) > and nice picture on both G450 heads (though you'll see nothing on them > except color dots after bootup; con2fb & matroxset is your friend) > (8) If (7) did not happen, send me contents of all > /proc/driver/mga/fb*/* you'll find (you should find one 'bios' and > one 'pins' for each Matrox video card in your box). sorry about the delay. holidays eat into time, and fighting my way back out from under all my mailing lists took longer than I thought. :( I patched my kernel and gave it a try. here's the results of my tests: test #1 settings: PCI (ATI Xpert 98 - Mach64 chip) primary display (as set in the BIOS). no video= options result: nothing readable on any of the 3 heads. ATI - blank; tho there were some white pixels scrolling by on the left side of the screen at boot time. Matrox Head #1 - generally bluish pattern of 'snow' (in regular linear patterns). Matrox Head #2 - purplish pattern of 'wavy lines' rebooted, and did it again to see if result was repeatable. same thing happened. test #2 settings: PCI primary passed video=matrox:vesa:0x11A result: framebuffer console appeared on Matrox Head #1 ATI - completely blank, tho still getting some sort of signal. Matrox Head #1 - got fb console Matrox Head #2 - same wavy purple pattern as in test #1 logged in, and copied the contents of /proc/driver/mga/fb0/ to: www.redchrome.org/misc/bios www.redchrome.org/misc/pins I don't have a con2fb utility, but I do have a con2fbmap utility. tried experimenting with it, but didn't see any results. tried (as root) 'con2fbmap tty1 /dev/fb1' and 'con2fbmap tty1 /dev/fb2'; but didn't see any results. I didn't have a copy of your 'matroxset' program on hand, so I didn't test to see what I could do with that. test #3 settings: AGP primary no video= options result: no working console. :( ATI - no signal Matrox Head #1 - black with vertical white 'pinstripes' Matrox Head #2 - the purple wavy lines again how much does the information about the unreadable framebuffer colors & patterns actually help? can one gain more information knowing that something showed 'black with white pinstripes' rather than 'horizontal purple wavy-line patterns'? Carl Soderstrom -- Network Engineer Real-Time Enterprises (952) 943-8700 |
|
From: Geert U. <ge...@li...> - 2002-01-10 09:59:42
|
On Wed, 9 Jan 2002, Carl Wilhelm Soderstrom wrote:
> I don't have a con2fb utility, but I do have a con2fbmap utility. tried
> experimenting with it, but didn't see any results. tried (as root)
> 'con2fbmap tty1 /dev/fb1' and 'con2fbmap tty1 /dev/fb2'; but didn't see any
> results.
> I didn't have a copy of your 'matroxset' program on hand, so I didn't test
> to see what I could do with that.
Please try the plain numbers instead of the device path names, e.g.
`con2fbmap 1 1'.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
Thanks for helping keep SourceForge clean.
X