From: Svetoslav S. <sv...@gm...> - 2003-11-26 11:17:13
|
> Hi, Svetljo! > > Can You create detailed report about G550. In another case > i drop hope help You. > test sequence with latest CVS > modprobe matroxfb > modprobe matroxfb_2ndhead > modprobe fbcon ooooooops sory compilng the kernel now i use the tarball you sent me + vt3.diff + rc1.patch i haven't seen any changes on the cvs commit ml or do you mean latest bk tree ? svetljo PS last time -- without rc1 diff everything seemd OK with one small problem that after running matroxset (the only way to get independant heads) the second head just stays blank > Aivils > ----- Forwarded by Aivils Stoss/PARVALDE/UNIBANKA/LV on 2003.11.26 09:29 > ----- > > > "Petr > > Vandrovec" To: Aivils Stoss > <Aiv...@un...> > <VANDROVE@vc. cc: > > cvut.cz> Subject: Re: Independ > multiple users on G550 > > On 25 Nov 03 at 16:41, Aivils Stoss wrote: > > I work lot of time on well known linux-ruby project. > > http://linuxconsole.sf.net > > Now i am done with fb layer. fbcon may work with multiple keyboards. > > Each fb device may have his own keyboard. I tested it with 3 > > fb devices voodoo1/voodoo2/voodoo3. Each adapter has independ > > console (range of tty /dev/ttyXX - /dev/ttyYY) and independ > > keyboard. > > In abstract G550 adapter can serve two independ fbdev. > > Unfortunately two members of linuxconsole project cannot start > > fbcon on G550. Both testers report different results of G550 > > manner. I have at least one report about runnig fbcon on > > 1st head of G550. > I have no idea how I can help you... Does driver oops? no oopses > Are not you>violating CRTC2 rules (only 16/32bpp is supported by crtc2)? may be <me sucks> how should i change the settings to valid ones with matroxset/fbset ? </me sucks> >Do you have correctly setup CRTC <-> output mappings by 'matroxset'? yes, it works with X using fbdriver(2 independant heads), after loading the modules swapped from the matroxset tarball is runned, in the case with multiple fb consoles it blanks both heads - the first can be activated/ unblanked by console switch (ctrl-alt-Fx), the second remains blank :( ( multiple fb consoles were tested without starting X, multiple X was used with single fbconsole & 1 dumb console ) <me sucks< why haven't i tried to use X to configure properly crtc2 </me sucks> -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Aivils S. <Aiv...@un...> - 2003-11-26 11:57:01
|
>> Hi, Svetljo! >> >> Can You create detailed report about G550. In another case >> i drop hope help You. >> test sequence with latest CVS >> modprobe matroxfb >> modprobe matroxfb_2ndhead >> modprobe fbcon > >ooooooops > >sory > >compilng the kernel now >i use the tarball you sent me + vt3.diff + rc1.patch > >i haven't seen any changes on the cvs commit ml or do you mean latest bk >tree ? I mean linuxconsole.sf.net. Latest CVS do not need vt3.diff and rc1.patch. Overlapped code removed and fbcon should pop up properly. Aivils |
From: Svetoslav S. <sv...@gm...> - 2003-11-26 12:54:38
|
> > >> Hi, Svetljo! > >> > >> Can You create detailed report about G550. In another case > >> i drop hope help You. > >> test sequence with latest CVS > >> modprobe matroxfb > >> modprobe matroxfb_2ndhead > >> modprobe fbcon > > > >ooooooops > > > >sory > > > >compilng the kernel now > >i use the tarball you sent me + vt3.diff + rc1.patch > > > >i haven't seen any changes on the cvs commit ml or do you mean latest bk > >tree ? > > I mean linuxconsole.sf.net. > Latest CVS do not need vt3.diff and rc1.patch. > Overlapped code removed and fbcon should pop up properly. so i'll have to start over with the compilation :-) could you send me/upload the new code ( i still don't trust sf's cvs) <me sucks EAGAIN> the old kernel , the one i used the last time for testing does work with multiple framebuffer consoles :-) i probably missed smth the previous time :-) yes it works with 2users on the 2 heads :-) but when i start x 1.) on the second head i can not switch to console in the X log "Failed to switch consoles (No such device or address)" 2.) if i switch to console on the first head and then back to X, i get the X(head 1) running on both heads X(head2) continues to work, but as console swicthing doesn't work on X (head 2) i can not activate it,or switch to VC (needs more testing, tmp workaround kill X(head2) and restart it, or do not switch to VC on 1st head) 3.) gdm locks the PC (may be needs some tweaking, testing starting X from fb console works in the already described way) </me sucks> best, svetljo -- GMX Weihnachts-Special: Seychellen-Traumreise zu gewinnen! Rentier entlaufen. Finden Sie Rudolph! Als Belohnung winken tolle Preise. http://www.gmx.net/de/cgi/specialmail/ +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Aivils S. <Aiv...@un...> - 2003-11-26 13:36:37
|
>> I mean linuxconsole.sf.net. >> Latest CVS do not need vt3.diff and rc1.patch. >> Overlapped code removed and fbcon should pop up properly. as well suspicious http://startx.times.lv/ruby-260t9-CVS-20031115.tar.bz2 >so i'll have to start over with the compilation :-) >could you send me/upload the new code ( i still don't trust sf's cvs) > ><me sucks EAGAIN> >the old kernel , the one i used the last time for testing >does work with multiple framebuffer consoles :-) >i probably missed smth the previous time >:-) yes it works with 2users on the 2 heads :-) 2 heads of one matrox or another video adapters? >but when i start x > >1.) >on the second head i can not switch to console >in the X log >"Failed to switch consoles (No such device or address)" Second head uses /dev/vc/17 to /dev/vc/32 , but xf86 will switch Ctrl-Alt-F1 == /dev/vc/1 to neighbour console. You van applay primitive patch --- xc-changed/programs/Xserver/hw/xfree86/common/xf86Events.c 2003-02-20 04:20:52.000000000 +0000 +++ xc-changed/programs/Xserver/hw/xfree86/common/xf86Events.chg.c 2003-11-26 16:28:17.000000000 +0000 @@ -102,7 +102,8 @@ extern void XTestStealMotionData(); EqEnqueue((ev)) #endif - +#define VT_SHIFT 16 + /* * The first of many hacks to get VT switching to work under * Solaris 2.1 for x86. The basic problem is that Solaris is supposed @@ -322,7 +323,7 @@ xf86ProcessActionEvent(ActionEvent actio #if defined(QNX4) xf86Info.vtRequestsPending = vtno; #else - if (ioctl(xf86Info.consoleFd, VT_ACTIVATE, vtno) < 0) + if (ioctl(xf86Info.consoleFd, VT_ACTIVATE, vtno + VT_SHIFT) < 0) ErrorF("Failed to switch consoles (%s)\n", strerror(errno)); #endif } >2.) >if i switch to console on the first head and then back to X, >i get the X(head 1) running on both heads >X(head2) continues to work, but as console swicthing doesn't work >on X (head 2) i can not activate it,or switch to VC >(needs more testing, tmp workaround kill X(head2) and restart it, >or do not switch to VC on 1st head) Matrox driver? >3.) > gdm locks the PC >(may be needs some tweaking, testing > starting X from fb console works in the already described way) Aivils |
From: Svetoslav S. <sv...@gm...> - 2003-11-26 14:02:27
|
> > >> I mean linuxconsole.sf.net. > >> Latest CVS do not need vt3.diff and rc1.patch. > >> Overlapped code removed and fbcon should pop up properly. > > as well suspicious > http://startx.times.lv/ruby-260t9-CVS-20031115.tar.bz2 thanks > >so i'll have to start over with the compilation :-) > >could you send me/upload the new code ( i still don't trust sf's cvs) > > > ><me sucks EAGAIN> > >the old kernel , the one i used the last time for testing > >does work with multiple framebuffer consoles :-) > >i probably missed smth the previous time > >:-) yes it works with 2users on the 2 heads :-) > > 2 heads of one matrox or another video adapters? 2 heads on matrox G550 DH AGP > >but when i start x > > > >1.) > >on the second head i can not switch to console > >in the X log > >"Failed to switch consoles (No such device or address)" > > Second head uses /dev/vc/17 to /dev/vc/32 , but xf86 will > switch Ctrl-Alt-F1 == /dev/vc/1 to neighbour console. > You van applay primitive patch > --- xc-changed/programs/Xserver/hw/xfree86/common/xf86Events.c > 2003-02-20 04:20:52.000000000 +0000 > +++ xc-changed/programs/Xserver/hw/xfree86/common/xf86Events.chg.c > 2003-11-26 16:28:17.000000000 +0000 > @@ -102,7 +102,8 @@ extern void XTestStealMotionData(); > EqEnqueue((ev)) > > #endif > - > +#define VT_SHIFT 16 > + > /* > * The first of many hacks to get VT switching to work under > * Solaris 2.1 for x86. The basic problem is that Solaris is supposed > @@ -322,7 +323,7 @@ xf86ProcessActionEvent(ActionEvent actio > #if defined(QNX4) > xf86Info.vtRequestsPending = vtno; > #else > - if (ioctl(xf86Info.consoleFd, VT_ACTIVATE, vtno) < 0) > + if (ioctl(xf86Info.consoleFd, VT_ACTIVATE, vtno + VT_SHIFT) < 0) > ErrorF("Failed to switch consoles (%s)\n", strerror(errno)); > #endif > } > <stupid question> does this mean that i have to use 2 binaries: one without this patch for first head vc1-vc16 one with this patch for second head vc17-vc32 ? </stupid question> > >2.) > >if i switch to console on the first head and then back to X, > >i get the X(head 1) running on both heads > >X(head2) continues to work, but as console swicthing doesn't work > >on X (head 2) i can not activate it,or switch to VC > >(needs more testing, tmp workaround kill X(head2) and restart it, > >or do not switch to VC on 1st head) > > Matrox driver? original XFree accelerated "mga" driver for Matrox cards have to retest with both X using fbdev driver svetljo -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Svetoslav S. <sv...@gm...> - 2003-11-26 18:44:40
|
> >but when i start x > > > >1.) > >on the second head i can not switch to console > >in the X log > >"Failed to switch consoles (No such device or address)" > > Second head uses /dev/vc/17 to /dev/vc/32 , but xf86 will > switch Ctrl-Alt-F1 == /dev/vc/1 to neighbour console. > You van applay primitive patch > --- xc-changed/programs/Xserver/hw/xfree86/common/xf86Events.c > 2003-02-20 04:20:52.000000000 +0000 > +++ xc-changed/programs/Xserver/hw/xfree86/common/xf86Events.chg.c > 2003-11-26 16:28:17.000000000 +0000 > @@ -102,7 +102,8 @@ extern void XTestStealMotionData(); > EqEnqueue((ev)) > > #endif > - > +#define VT_SHIFT 16 > + > /* > * The first of many hacks to get VT switching to work under > * Solaris 2.1 for x86. The basic problem is that Solaris is supposed > @@ -322,7 +323,7 @@ xf86ProcessActionEvent(ActionEvent actio > #if defined(QNX4) > xf86Info.vtRequestsPending = vtno; > #else > - if (ioctl(xf86Info.consoleFd, VT_ACTIVATE, vtno) < 0) > + if (ioctl(xf86Info.consoleFd, VT_ACTIVATE, vtno + VT_SHIFT) < 0) > ErrorF("Failed to switch consoles (%s)\n", strerror(errno)); > #endif > } that does the trick :-) now we(most likely you as the brain) probably should find a smarter solution smth like : sugestions (order IMO easy to implemet->hard to implement & nice) 1.) startx --- ./usr/X11R6/bin/X... -vt_shift 0 ( or omit) vt7 startx --- ./usr/X11R6/bin/X... -vt_shift 16 vt17 startx --- ./usr/X11R6/bin/X... -vt_shift 32 vt33 2.) Option "SingleCard" "true" Option "VtShift" "0" /* or omit */ ..... Option "SingleCard" "true" Option "VtShift" "16" ..... Option "SingleCard" "true" Option "VtShift" "32" ..... 3.) may be add /proc/bus/console/xx/vc_first and teach XFree to use it while on adding stuff :-) don't you think it would be usefull to expose vc_first,vc_last or vc_range in proc ? 4.) start buging the XFree developers ? may be too early, when the F... will Linus leave 2.6 to Andrew and open 2.7 , and when ruby will be merged ? > > >2.) > >if i switch to console on the first head and then back to X, > >i get the X(head 1) running on both heads > >X(head2) continues to work, but as console swicthing doesn't work > >on X (head 2) i can not activate it,or switch to VC > >(needs more testing, tmp workaround kill X(head2) and restart it, > >or do not switch to VC on 1st head) > > Matrox driver? > both heads with driver "fbdev" is the same -> X(head 1) switch to VC & back -> Problem -->> X(head 1) displayed on both heads ++>> VT switch on head 2 fixes it X(head 2) switch to VC & back -> everything OK ++>> X(head 1) displayed on head 1 ++>> X(head 2) displayed on head 2 order of starting X is not important --------------------------------------------- there is one more ?issue? with the second head the cursor never blinks, it stays all the time turned on a bit strange but everything else is OK best, svetljo -- HoHoHo! Seid Ihr auch alle schön brav gewesen? GMX Weihnachts-Special: Die 1. Adresse für Weihnachts- männer und -frauen! http://www.gmx.net/de/cgi/specialmail +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Aivils S. <Aiv...@un...> - 2003-11-27 08:07:17
|
>3.) >may be add /proc/bus/console/xx/vc_first >and teach XFree to use it /proc is for lazy endusers. For userspace programms more helpful is ioctl. James Simmons already suggest add necessary ioctl-s for TTY. Now is time to play the game. >while on adding stuff :-) >don't you think it would be usefull to expose vc_first,vc_last or vc_range >in proc ? Seems one file /proc/bus/console/info is necessary. >4.) >start buging the XFree developers ? >may be too early, when the F... will Linus leave 2.6 to Andrew >and open 2.7 , and when ruby will be merged ? When linux-ruby enduser count goes over developer count, then You might buging everyone :o) >there is one more ?issue? with the second head >the cursor never blinks, it stays all the time turned on >a bit strange but everything else is OK That is my bug. I cannot decide where i should add cursor timer in fb_info or vt_struct. Current fbcon has single cursor timer used by first head. Aivils |
From: Svetoslav S. <sv...@gm...> - 2003-11-27 11:53:22
|
> > >3.) > >may be add /proc/bus/console/xx/vc_first > >and teach XFree to use it > > /proc is for lazy endusers. For userspace programms > more helpful is ioctl. James Simmons already suggest add > necessary ioctl-s for TTY. Now is time to play the game. and until it's done a small hack for startx ..... -vt_shift 16 vt25 ?-) > >while on adding stuff :-) > >don't you think it would be usefull to expose vc_first,vc_last or > vc_range > >in proc ? > > Seems one file /proc/bus/console/info is necessary. > thanks :-) > >4.) > >start buging the XFree developers ? > >may be too early, when the F... will Linus leave 2.6 to Andrew > >and open 2.7 , and when ruby will be merged ? > > When linux-ruby enduser count goes over developer count, > then You might buging everyone :o) :) which developer count? ruby developers or xfree developers? there are already more users then ruby developers :-) > >there is one more ?issue? with the second head > >the cursor never blinks, it stays all the time turned on > >a bit strange but everything else is OK > > That is my bug. I cannot decide where i should add cursor > timer in fb_info or vt_struct. Current fbcon has single cursor > timer used by first head. OK and one more question can you login as root on secondary head ? i can't :( i can login as two different users on the second head, but trying to login as root always returns "login failed" any ideas? svetljo -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Helge H. <hel...@ai...> - 2003-11-27 12:23:19
|
On Thu, Nov 27, 2003 at 12:53:14PM +0100, Svetoslav Slavtchev wrote: > > >start buging the XFree developers ? > > >may be too early, when the F... will Linus leave 2.6 to Andrew > > >and open 2.7 , and when ruby will be merged ? > > > > When linux-ruby enduser count goes over developer count, > > then You might buging everyone :o) > You can count me and my girlfriend then, and various nephews that comes by to play tuxracer :-) > and one more question > can you login as root on secondary head ? > i can't :( > i can login as two different users on the second head, > but trying to login as root always returns "login failed" > any ideas? > My advice is to take a look at /etc/securetty which limits where root can log in. I lost root logins upon switching to and from devfs due to changing names of the tty devices. Make sure the "extra" consoles are listed. Helge Hafting |
From: Andreas S. <an...@sc...> - 2003-11-27 12:32:53
|
* Helge Hafting (hel...@ai...) [031127 13:24]: > On Thu, Nov 27, 2003 at 12:53:14PM +0100, Svetoslav Slavtchev wrote: > > > >start buging the XFree developers ? > > > >may be too early, when the F... will Linus leave 2.6 to Andrew > > > >and open 2.7 , and when ruby will be merged ? > > > > > > When linux-ruby enduser count goes over developer count, > > > then You might buging everyone :o) > > > You can count me and my girlfriend then, and various > nephews that comes by to play tuxracer :-) no, you dont count, you are to cluefull. your girlfriend does not count either, she was not forced to deal activly with the issues (c: |
From: Svetoslav S. <sv...@gm...> - 2003-11-30 15:24:12
|
> On Thu, Nov 27, 2003 at 12:53:14PM +0100, Svetoslav Slavtchev wrote: > > > >start buging the XFree developers ? > > > >may be too early, when the F... will Linus leave 2.6 to Andrew > > > >and open 2.7 , and when ruby will be merged ? > > > > > > When linux-ruby enduser count goes over developer count, > > > then You might buging everyone :o) > > > You can count me and my girlfriend then, and various > nephews that comes by to play tuxracer :-) > right :-) and there are only two ruby developers Aivils & James there were some guys integrating it in production, /* they got it running, status of integration unknown */ - PC pool in a school in Israel - IT department of Skoda in Cheh republic > > and one more question > > can you login as root on secondary head ? > > i can't :( > > i can login as two different users on the second head, > > but trying to login as root always returns "login failed" > > any ideas? > > > My advice is to take a look at /etc/securetty which > limits where root can log in. I lost root logins upon > switching to and from devfs due to changing names of > the tty devices. Make sure the "extra" consoles > are listed. thanks that worked :-) /* next time i've to read more carefully * i ve searched /ets/security/* but couldn't find * anything, i just googled and find the answer * then re read your mail scratching my head :-) */ best, svetljo -- Neu bei GMX: Preissenkung für MMS-Versand und FreeMMS! Ideal für alle, die gerne MMS verschicken: 25 FreeMMS/Monat mit GMX TopMail. http://www.gmx.net/de/cgi/produktemail +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Helge H. <hel...@ai...> - 2003-11-30 19:52:40
|
On Sun, Nov 30, 2003 at 04:24:04PM +0100, Svetoslav Slavtchev wrote: > > > > > My advice is to take a look at /etc/securetty which > > limits where root can log in. I lost root logins upon > > switching to and from devfs due to changing names of > > the tty devices. Make sure the "extra" consoles > > are listed. > > thanks > > that worked :-) > I updated from CVS 30.nov, and copied the source into 2.6.0-test11 This compiled fine, in several configurations. Booting with framebuffer console compiled-in still oopses, this time the oops was unreadable except for the last line about killing init. So I tried a modular fbcon, with a kernel configured to load modules automatically when needed. This booted in the same way, loaded the fbcon module automatically and crashed just as the compiled-in variant. The readable part of the crash message said something about mdrun exiting with a wrong preempt count. So I moved fbcon.ko where modprobe couldn't find it, and booted again. The machine came up fine, obviously without a console. I moved the module back to its proper place, and loaded it. I immediately got two penguins (it's a dual processor machine) on the screen running accelerated X. This screen has the keyboard connected to the ordinary ps2 keyboard plug (recognized by the bios too). Ruby places this at vt17. Pressing ctrl+alt+F1 here did nothing, no console switch. The other keyboard is connected to the ps2 mouse plug, and seen by X on vt7. Pressing ctrl+alt+F1 switched to a console. X blanked itself. Unfortunately the console appeared at the other screen - so I had matrox console and X running there simultaneously. Psycho circus again. :-( The second screen just sat there. I believe this might work better if I ran the vt7 xfree on the first display, but I have a good reason for not doing so: It is sometimes necessary to access the bios setup, or boot non-ruby versions of linux. In those cases the keyboard connected to the ordinary keyboard plug is the only keyboard, and X happens on the first screen. (/dev/fb0). Moving keyboards or screens around the room isn't very interesting, so this is the layout I want. Life would be so much easier if ruby considered the ordinary pc keyboard as the first one, and one connected to the "mouse" port as the second one. Or if the vt/keyboarddevice/console connections could be specified using kernel parameters. any hope of swapping the keyboards so the console/screen/keyboard/vt combination that works for plain linux simply becomes the "first" set of connected devices using ruby? Is there anything I could do to help find out why fbcon oopses when it is available "too early"? Perhaps it uses resources not yet initialized? Or races somehow? It seems to work when loaded after the normal boot, except that it don't match my screen/keyboard mapping. Helge Hafting |
From: Svetoslav S. <sv...@gm...> - 2003-11-30 21:08:48
|
> On Sun, Nov 30, 2003 at 04:24:04PM +0100, Svetoslav Slavtchev wrote: > > > > > > > My advice is to take a look at /etc/securetty which > > > limits where root can log in. I lost root logins upon > > > switching to and from devfs due to changing names of > > > the tty devices. Make sure the "extra" consoles > > > are listed. > > > > thanks > > > > that worked :-) > > > > > I updated from CVS 30.nov, and copied the source into 2.6.0-test11 > This compiled fine, in several configurations. > > Booting with framebuffer console compiled-in still oopses, > this time the oops was unreadable except for the last line > about killing init. > > So I tried a modular fbcon, with a kernel configured to load > modules automatically when needed. This booted in the same way, > loaded the fbcon module automatically and crashed just as the compiled-in > variant. The readable part of the crash message said something > about mdrun exiting with a wrong preempt count. > no devide errors ? Aivils said that it should be fixed in his last tarball & cvs, but i still get the devide errors and the prevoius patch fixes them /* see attachments */ > So I moved fbcon.ko where modprobe couldn't find it, and > booted again. The machine came up fine, obviously without a > console. I moved the module back to its proper place, > and loaded it. I immediately got two penguins (it's a dual processor > machine) on the screen running accelerated X. This screen > has the keyboard connected to the ordinary ps2 keyboard plug > (recognized by the bios too). i don't get much this part :( you booted with built in matroxfb, but no fbcon, and then loaded fbcon without problems ? > Ruby places this at vt17. > Pressing ctrl+alt+F1 here did nothing, no console switch. you need this Xfree hack http://sourceforge.net/mailarchive/message.php?msg_id=6629651 /* if you were running mdk9.2/ cooker i could send you my binary, * but IIRC you use debian */ > The other keyboard is connected to the ps2 mouse plug, > and seen by X on vt7. Pressing ctrl+alt+F1 switched to a > console. X blanked itself. Unfortunately the console appeared at the > other > screen - so I had matrox console and X running there simultaneously. > Psycho circus again. :-( The second screen just sat there. looks interesting have a snapshot ?-) > I believe this might work better if I ran the vt7 xfree on > the first display, but I have a good reason for not doing so: > It is sometimes necessary to access the bios setup, or boot non-ruby > versions of linux. In those cases the keyboard connected to the > ordinary keyboard plug is the only keyboard, and X happens > on the first screen. (/dev/fb0). Moving keyboards or screens around the > room isn't very interesting, so this is the layout I want. > > Life would be so much easier if ruby considered the ordinary > pc keyboard as the first one, and one connected to the "mouse" port > as the second one. Or if the vt/keyboarddevice/console connections > could be specified using kernel parameters. any hope of swapping the > keyboards so the console/screen/keyboard/vt combination that works > for plain linux simply becomes the "first" set of connected devices > using ruby? just configure hotplug, install input.agent & input.rc /* debian's hotplug pkgs probably already include the input.* scripts * so you'll probably have to merge the ruby input.agent into the debians one */ this way you can configure VT- keyboard mapping & consistent evdev[n] mouse[n] devices /* although udev is probably much better for the evdev & mice */ > Is there anything I could do to help find out why fbcon oopses > when it is available "too early"? Perhaps it uses resources > not yet initialized? Or races somehow? > It seems to work when loaded after the normal boot, except that > it don't match my screen/keyboard mapping. if it is the same issue /* and i think it is */ it was font.width == 0 + a function using xxxx / fonth.width best svetljo PS. i haven't tried yet built in matroxfb/ fbcon PS.2 i use this script to start multiple fbcon's ------------------------------------------------------ #!/bin/bash modprobe matroxfb_base modprobe matroxfb_crtc2 modprobe fbcon # split the heads , we don't want head1 shown on head2 matroxfb_swapped # adjust input devices, we don't have /proc/bus/console/01 # before loading fbcon /etc/hotplug/input.rc start # runlevel 4 is the same as 3 + additianal mingetty's in inittab init 4 --------------------------------------------------- PS.3 attachments 260t9-20031115.txt -- oopses with vanilla ruby-260t9-20031115 AA02-ruby-20031029_matroxfb_fix.patch - fixes the problem, Aivils sent it to me as vt.3.diff , not sure if it hit the list AA03-ruby-fb_resize.patch - another fix by Aivils, the same oopses without the previous patch, Aivils sent it to me as rc1.diff 260t9-20031115-rc1.txt -- oopses without AA02 ,but with AA03 aplied PS.4 the last commit was 14 Nov, so Aivils's tarball contains the same code as cvs Aivils, should ruby-260t9-20031115 really work OK without this patches ? PS.5 the remaining issues /* most likely hardware limitations involved * and XFree "bugs" too */ 1.) X->VT->X on head1 (vt7) X head1 is displayed on both heads, VT switch on head2 fixes it 2.) the mentioned XFree hack should be integrated smarter, currently you need additional binary for each additional fbcon 3.) probably unsolvable/ hardware the need to run swapped from matroxset tarball to separate the displays 4.) related to 3 after swapped, both heads are blank until a VT switch, and on head1 there is a lot of garbage until login + logout actually the garbage is on all vc's except the first one (head 1) but on all vc's usable is only 4/6 of the hight of the screen the top 1/6 is ocupied by the logo, the bottom 1/6 by nothing on vc1 and by garbage on vc2-vc6. Everything becomes normal after a login + logout , but until logout only graphics(e.g. ncurses menuconfig) paint to the entire screen, a ls, ps, whatever will use only the middle 4/6 of the screen hight there is no such problem with head2 /* which misses a blinking cursor, cursor is always on :-) */ -- HoHoHo! Seid Ihr auch alle schön brav gewesen? GMX Weihnachts-Special: Die 1. Adresse für Weihnachts- männer und -frauen! http://www.gmx.net/de/cgi/specialmail +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Helge H. <hel...@ai...> - 2003-12-01 10:04:21
|
Svetoslav Slavtchev wrote: [...] >>So I tried a modular fbcon, with a kernel configured to load >>modules automatically when needed. This booted in the same way, >>loaded the fbcon module automatically and crashed just as the compiled-in >>variant. The readable part of the crash message said something >>about mdrun exiting with a wrong preempt count. > > no devide errors ? > Hard to say what it was, because the screen was partially garbage. The last line was a complaint about the kernel trying to kill init (and therefore giving up). > Aivils said that it should be fixed in his last tarball & cvs, > but i still get the devide errors and the prevoius patch fixes them > /* see attachments */ > > > >>So I moved fbcon.ko where modprobe couldn't find it, and >>booted again. The machine came up fine, obviously without a >>console. I moved the module back to its proper place, >>and loaded it. I immediately got two penguins (it's a dual processor >>machine) on the screen running accelerated X. This screen >>has the keyboard connected to the ordinary ps2 keyboard plug >>(recognized by the bios too). > > > i don't get much this part :( > > you booted with built in matroxfb, but no fbcon, > and then loaded fbcon without problems ? > Yes. I usually compile my kernels with everything built-in because I see no virtue in modules. (They may be fine for distribution kernels, but mu kernel is compiled for my machine specifically. I simply want to avoid all module setup & management,) I made an exception here, by configuring fbcon as a module. The framebuffer driver and everything else still was compiled-in. The part about temporarily moving fbcon.ko where modprobe couldn't find it was just a hack to make the machine boot. The module crashes the kernel if it is loaded "too early", but the module cannot be automatically loaded by the kernel if the kernel cannot find it because I moved the file away from its usual directory. So it seems the framebuffer driver alone works under ruby, even when compiled in. fbcon works too, _if_ it isn't loaded too early. Bringing it up after logging in via xdm were ok. >> Ruby places this at vt17. >>Pressing ctrl+alt+F1 here did nothing, no console switch. > > > you need this Xfree hack > http://sourceforge.net/mailarchive/message.php?msg_id=6629651 > > /* if you were running mdk9.2/ cooker i could send you my binary, > * but IIRC you use debian > */ Thanks for the tip. It'll be useful when I get rid of the crash. > >>The other keyboard is connected to the ps2 mouse plug, >>and seen by X on vt7. Pressing ctrl+alt+F1 switched to a >>console. X blanked itself. Unfortunately the console appeared at the >>other >>screen - so I had matrox console and X running there simultaneously. >>Psycho circus again. :-( The second screen just sat there. > > > looks interesting > have a snapshot ?-) > I don't have one, but it isn't all that hard to imagine. At its best it looks like a ordinary console screen with an xterm overlayed somehow. One keyboard types into the xterm, the other into the console. Of course the two tend to stomp on each other quite a bit, the console scrolling the x desktop away and X repainting a bit here and there now and then. > >>I believe this might work better if I ran the vt7 xfree on >>the first display, but I have a good reason for not doing so: >>It is sometimes necessary to access the bios setup, or boot non-ruby >>versions of linux. In those cases the keyboard connected to the >>ordinary keyboard plug is the only keyboard, and X happens >>on the first screen. (/dev/fb0). Moving keyboards or screens around the >>room isn't very interesting, so this is the layout I want. >> >>Life would be so much easier if ruby considered the ordinary >>pc keyboard as the first one, and one connected to the "mouse" port >>as the second one. Or if the vt/keyboarddevice/console connections >>could be specified using kernel parameters. any hope of swapping the >>keyboards so the console/screen/keyboard/vt combination that works >>for plain linux simply becomes the "first" set of connected devices >>using ruby? > > > just configure hotplug, install input.agent & input.rc > /* debian's hotplug pkgs probably already include the input.* scripts > * so you'll probably have to merge the ruby input.agent into the debians > one > */ > > this way you can configure VT- keyboard mapping > & consistent evdev[n] mouse[n] devices > /* although udev is probably much better for the evdev & mice */ > I'll look at this someday. Do I need modules for this to work? >>Is there anything I could do to help find out why fbcon oopses >>when it is available "too early"? Perhaps it uses resources >>not yet initialized? Or races somehow? >>It seems to work when loaded after the normal boot, except that >>it don't match my screen/keyboard mapping. > > > if it is the same issue /* and i think it is */ > it was font.width == 0 + a function using xxxx / fonth.width > > best > > svetljo > > PS. > i haven't tried yet built in matroxfb/ fbcon I'll try your patches. I like the built-in approach, it is nice to be able to boot with init=/bin/sh and still get a console. The dream is to just boot and get login prompts on both screens with no further setup than running the gettys from /etc/inittab, and perhaps some kernel boot parameters. The big problems with setup scripts is that they run late in the boot process, early oopses or other trouble may prevent them from running, I still want to read the text and be able to use sysrq. I may go for modules and scripts for now, but hope the monolithic approach will work someday. :-) > > PS.2 > i use this script to start multiple fbcon's Thanks > > PS.3 > attachments > > 260t9-20031115.txt -- oopses with vanilla ruby-260t9-20031115 > > AA02-ruby-20031029_matroxfb_fix.patch - fixes the problem, I'll try. > the remaining issues > /* most likely hardware limitations involved > * and XFree "bugs" too > */ > > 1.) X->VT->X on head1 (vt7) > X head1 is displayed on both heads, VT switch on head2 fixes it > I believe this is an issue with the mga accelerated driver. I get similiar problems whenever games change resolution on the accelerated head. I have my window manager set up with a key combination that runs matroxset. It'd be nice not having to do this, but it'll probably be a long time. X simply do more than it should. > 2.) the mentioned XFree hack should be integrated smarter, > currently you need additional binary for each additional fbcon > > 3.) probably unsolvable/ hardware > the need to run swapped from matroxset tarball to > separate the displays I don't see why this should be unsolvable. All matroxset do is to run some ioctl's. Surely the same code could be called from within the framebuffer driver at boot time? I believe this was done because single-monitor setups are common, and the kernel probably can't easily know where that monitor is attached. (Well, it could use DDC...) But people don't buy a G550 to run single-monitor, so having the kernel separate the displays and force the user to think about which connector to use is fine with me. > > 4.) related to 3 > after swapped, both heads are blank until a VT switch, > > and on head1 there is a lot of garbage until login + logout > actually the garbage is on all vc's except the first one (head 1) > but on all vc's usable is only 4/6 of the hight of the screen > the top 1/6 is ocupied by the logo, the bottom 1/6 by nothing > on vc1 and by garbage on vc2-vc6. I believe the garbage is stuff that vgacon left in graphichs memory before handing the console over to the framebuffer. At least this was the explanation when I complained about similiar garbage on a radeon with framebuffer. compiling _without_ vgacon indeed made all the garbage go away, but the option to turn off vgacon recently disappeared from menuconfig. :-( > Everything becomes normal after a login + logout , but until logout > only graphics(e.g. ncurses menuconfig) paint to the entire screen, > a ls, ps, whatever will use only the middle 4/6 of the screen hight > Probably the logo code reserving some of the screen. Odd that it'd reserve the bottom part though. Helge Hafting |
From: Svetoslav S. <sv...@gm...> - 2003-12-01 13:41:39
|
> >>So I moved fbcon.ko where modprobe couldn't find it, and > >>booted again. The machine came up fine, obviously without a > >>console. I moved the module back to its proper place, > >>and loaded it. I immediately got two penguins (it's a dual processor > >>machine) on the screen running accelerated X. This screen > >>has the keyboard connected to the ordinary ps2 keyboard plug > >>(recognized by the bios too). > > > > > > i don't get much this part :( > > > > you booted with built in matroxfb, but no fbcon, > > and then loaded fbcon without problems ? > > > Yes. I usually compile my kernels with everything built-in > because I see no virtue in modules. (They may be fine for > distribution kernels, but mu kernel is compiled for my machine > specifically. I simply want to avoid all module setup & management,) > > I made an exception here, by configuring fbcon as a module. The > framebuffer driver and everything else still was compiled-in. > > The part about temporarily moving fbcon.ko where modprobe couldn't > find it was just a hack to make the machine boot. The module > crashes the kernel if it is loaded "too early", but the module > cannot be automatically loaded by the kernel if the > kernel cannot find it because I moved the file away from > its usual directory. > > So it seems the framebuffer driver alone works under ruby, > even when compiled in. fbcon works too, _if_ it > isn't loaded too early. Bringing it up after > logging in via xdm were ok. hm, timing issues ? fbcon trying to setup consoles before matroxfb initialization is finished ? may be we should experimenent to find the needed timeout, but this is probably dependant on the system or may be /* if it isn't already so */ fbcon should wait for a signal from the framebuffers that they have finished initialization > >>I believe this might work better if I ran the vt7 xfree on > >>the first display, but I have a good reason for not doing so: > >>It is sometimes necessary to access the bios setup, or boot non-ruby > >>versions of linux. In those cases the keyboard connected to the > >>ordinary keyboard plug is the only keyboard, and X happens > >>on the first screen. (/dev/fb0). Moving keyboards or screens around the > >>room isn't very interesting, so this is the layout I want. > >> > >>Life would be so much easier if ruby considered the ordinary > >>pc keyboard as the first one, and one connected to the "mouse" port > >>as the second one. Or if the vt/keyboarddevice/console connections > >>could be specified using kernel parameters. any hope of swapping the > >>keyboards so the console/screen/keyboard/vt combination that works > >>for plain linux simply becomes the "first" set of connected devices > >>using ruby? > > > > > > just configure hotplug, install input.agent & input.rc > > /* debian's hotplug pkgs probably already include the input.* scripts > > * so you'll probably have to merge the ruby input.agent into the > debians > > one > > */ > > > > this way you can configure VT- keyboard mapping > > & consistent evdev[n] mouse[n] devices > > /* although udev is probably much better for the evdev & mice */ > > > I'll look at this someday. Do I need modules for this to work? good question normally hotplug can be used only with modules after it#S available, but the various *.rc scripts simulate a hotpluging event for drivers which are built in or already loaded before hotplug was available theoreticaly it should work, unless some needed functions are ifdef'ed MODULE > > PS. > > i haven't tried yet built in matroxfb/ fbcon > I'll try your patches. > I like the built-in approach, it is nice to be able to > boot with init=/bin/sh and still get a console. well you can have a VGA console built in and load the fb stuff manually or with script later just built fb drivers & fbcon modular and don't load them too early /* no fancy graphics at boot, but a workable VGA console */ > > The dream is to just boot and get login prompts on > both screens with no further setup than running the > gettys from /etc/inittab, and perhaps some kernel boot parameters. > > The big problems with setup scripts is that they run late in the > boot process, early oopses or other trouble may prevent them > >from running, I still want to read the text and be able to use sysrq. > > I may go for modules and scripts for now, but hope the monolithic > approach will work someday. :-) use VGA console and load the framebuffers & fbcon before starting X it would be really nice, but .... i think it's not possible with G550, not sure about G400/450 but it should work with Matrox MMS series or with different cards > > PS.2 > > i use this script to start multiple fbcon's > Thanks > > > > PS.3 > > attachments > > > > 260t9-20031115.txt -- oopses with vanilla ruby-260t9-20031115 > > > > AA02-ruby-20031029_matroxfb_fix.patch - fixes the problem, > I'll try. > > > the remaining issues > > /* most likely hardware limitations involved > > * and XFree "bugs" too > > */ > > > > 1.) X->VT->X on head1 (vt7) > > X head1 is displayed on both heads, VT switch on head2 fixes it > > > I believe this is an issue with the mga accelerated driver. > I get similiar problems whenever games change resolution on > the accelerated head. I have my window manager set up with a key > combination that runs matroxset. It'd be nice not > having to do this, but it'll probably be a long time. > X simply do more than it should. NOPE same with XF driver fbdev for both heads > > 2.) the mentioned XFree hack should be integrated smarter, > > currently you need additional binary for each additional fbcon > > > > 3.) probably unsolvable/ hardware > > the need to run swapped from matroxset tarball to > > separate the displays > I don't see why this should be unsolvable. All matroxset do is > to run some ioctl's. Surely the same code could be called from > within the framebuffer driver at boot time? > > I believe this was done because single-monitor setups are > common, and the kernel probably can't easily know where that > monitor is attached. (Well, it could use DDC...) > > But people don't buy a G550 to run single-monitor, so > having the kernel separate the displays and force the user > to think about which connector to use is fine with me. well may be, it would be nice to have a CONFIG_MATROXFB_SEPARATE_DISPLAYS, but i'm not sure it's doable, and i'm sure Petr is not working on it :( i think that the graphic BIOS initialize them in that way and the fbdriver will have to work around these BIOS settings > > > > 4.) related to 3 > > after swapped, both heads are blank until a VT switch, > > > > and on head1 there is a lot of garbage until login + logout > > actually the garbage is on all vc's except the first one (head 1) > > but on all vc's usable is only 4/6 of the hight of the screen > > the top 1/6 is ocupied by the logo, the bottom 1/6 by nothing > > on vc1 and by garbage on vc2-vc6. > I believe the garbage is stuff that vgacon left in graphichs memory before > handing the console over to the framebuffer. At least this was the > explanation when I complained about similiar garbage on a radeon > with framebuffer. compiling _without_ vgacon indeed made all > the garbage go away, but the option to turn off vgacon recently > disappeared from menuconfig. :-( i actually do have it :-) it disapeared with the option to disable PS2 input && serio you need "Generic Setup -> Remove kernel features (for embedded systems)" enabled to be able to change them i might try disabling it / * not sure when i'll find time for that :( */ svetljo PS how do you setup the fb mode? i'm still using a single monitor with switch @ 640x480, and fbset doesn't seem to work -- Neu bei GMX: Preissenkung für MMS-Versand und FreeMMS! Ideal für alle, die gerne MMS verschicken: 25 FreeMMS/Monat mit GMX TopMail. http://www.gmx.net/de/cgi/produktemail +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Helge H. <hel...@ai...> - 2003-12-01 19:50:25
|
On Mon, Dec 01, 2003 at 02:41:32PM +0100, Svetoslav Slavtchev wrote: > > > > So it seems the framebuffer driver alone works under ruby, > > even when compiled in. fbcon works too, _if_ it > > isn't loaded too early. Bringing it up after > > logging in via xdm were ok. > > hm, timing issues ? > fbcon trying to setup consoles before > matroxfb initialization is finished ? > Or maybe X changes something? It changes the resolution at least. > may be we should experimenent to find the needed timeout, > but this is probably dependant on the system > I believe that is a wrong approach. It should work as fast as possible on any system, without race conditions or arbitrary waiting. > or may be /* if it isn't already so */ > fbcon should wait for a signal from the framebuffers > that they have finished initialization > > well you can have a VGA console built in and load the fb stuff > manually or with script later > just built fb drivers & fbcon modular and don't load them too early > > /* no fancy graphics at boot, but a workable VGA console */ That is indeed an option. Perhaps I'll try that. > > > 1.) X->VT->X on head1 (vt7) > > > X head1 is displayed on both heads, VT switch on head2 fixes it > > > > > I believe this is an issue with the mga accelerated driver. > > I get similiar problems whenever games change resolution on > > the accelerated head. I have my window manager set up with a key > > combination that runs matroxset. It'd be nice not > > having to do this, but it'll probably be a long time. > > X simply do more than it should. > > NOPE > same with XF driver fbdev for both heads > When my pc boots it activates one screen only. The other one is black. That's what the bios do. The other screen starts showing the same as the first one when linux initialize the g550 framebuffers. So it looks like the fb driver do this initially. when it ought to set up one screen per framebuffer. Later X mess with the framebuffer/screen mappings everytime it sets screen resolution. It probably sets resolution when switching to/from console too. I don't know if X itself sets the resolution, or if it calls into the fb driver to do it. X is set up to use the fbdev, who knows _what_ it uses it for. > > > 2.) the mentioned XFree hack should be integrated smarter, > > > currently you need additional binary for each additional fbcon > > > > > > 3.) probably unsolvable/ hardware > > > the need to run swapped from matroxset tarball to > > > separate the displays > > I don't see why this should be unsolvable. All matroxset do is > > to run some ioctl's. Surely the same code could be called from > > within the framebuffer driver at boot time? > > > > I believe this was done because single-monitor setups are > > common, and the kernel probably can't easily know where that > > monitor is attached. (Well, it could use DDC...) > > > > But people don't buy a G550 to run single-monitor, so > > having the kernel separate the displays and force the user > > to think about which connector to use is fine with me. > > well may be, > it would be nice to have a CONFIG_MATROXFB_SEPARATE_DISPLAYS, > but i'm not sure it's doable, and i'm sure Petr is not working on it :( > i think that the graphic BIOS initialize them in that way and the fbdriver > will have to work around these BIOS settings > > > > > > > 4.) related to 3 > > > after swapped, both heads are blank until a VT switch, > > > > > > and on head1 there is a lot of garbage until login + logout > > > actually the garbage is on all vc's except the first one (head 1) > > > but on all vc's usable is only 4/6 of the hight of the screen > > > the top 1/6 is ocupied by the logo, the bottom 1/6 by nothing > > > on vc1 and by garbage on vc2-vc6. > > I believe the garbage is stuff that vgacon left in graphichs memory before > > handing the console over to the framebuffer. At least this was the > > explanation when I complained about similiar garbage on a radeon > > with framebuffer. compiling _without_ vgacon indeed made all > > the garbage go away, but the option to turn off vgacon recently > > disappeared from menuconfig. :-( > > i actually do have it :-) > > it disapeared with the option to disable PS2 input && serio > you need "Generic Setup -> Remove kernel features (for embedded systems)" > enabled to be able to change them > > i might try disabling it > / * not sure when i'll find time for that :( */ > > svetljo > > PS > > how do you setup the fb mode? > i'm still using a single monitor with switch > @ 640x480, and fbset doesn't seem to work kernel boot parameter: video=matroxfb:vesa:0x11A This is supposed to be 1280x1024 16-bit, I'm not sure it works. But X definitely sets the resolution to what it wants, on both screens. Exiting the accelerated server messes up the other screen as X "restores" the video card to previous settings. Helge Hafting |
From: Svetoslav S. <sv...@gm...> - 2003-12-01 20:30:34
|
> On Mon, Dec 01, 2003 at 02:41:32PM +0100, Svetoslav Slavtchev wrote: > > > > > > So it seems the framebuffer driver alone works under ruby, > > > even when compiled in. fbcon works too, _if_ it > > > isn't loaded too early. Bringing it up after > > > logging in via xdm were ok. > > > > hm, timing issues ? > > fbcon trying to setup consoles before > > matroxfb initialization is finished ? > > > Or maybe X changes something? It changes the resolution at least. i have no oopses with modular matroxfb/fbcon with/without starting X so it shouldn't be X > > may be we should experimenent to find the needed timeout, > > but this is probably dependant on the system > > > I believe that is a wrong approach. It should work as fast > as possible on any system, without race conditions or arbitrary waiting. > > > or may be /* if it isn't already so */ > > fbcon should wait for a signal from the framebuffers > > that they have finished initialization > > > > > well you can have a VGA console built in and load the fb stuff > > manually or with script later > > just built fb drivers & fbcon modular and don't load them too early > > > > /* no fancy graphics at boot, but a workable VGA console */ > > That is indeed an option. Perhaps I'll try that. > > > > > 1.) X->VT->X on head1 (vt7) > > > > X head1 is displayed on both heads, VT switch on head2 fixes it > > > > > > > I believe this is an issue with the mga accelerated driver. > > > I get similiar problems whenever games change resolution on > > > the accelerated head. I have my window manager set up with a key > > > combination that runs matroxset. It'd be nice not > > > having to do this, but it'll probably be a long time. > > > X simply do more than it should. > > > > NOPE > > same with XF driver fbdev for both heads > > > When my pc boots it activates one screen only. The other one > is black. That's what the bios do. The other screen starts showing the > same as the first one when linux initialize the g550 framebuffers. > > So it looks like the fb driver do this initially. when it ought to > set up one screen per framebuffer. Later X mess with the > framebuffer/screen mappings everytime it sets screen resolution. > It probably sets resolution when switching to/from console too. > I don't know if X itself sets the resolution, or if it calls > into the fb driver to do it. X is set up to use the fbdev, > who knows _what_ it uses it for. got the answer from Petr :( > > > > 2.) the mentioned XFree hack should be integrated smarter, > > > > currently you need additional binary for each additional fbcon > > > > > > > > 3.) probably unsolvable/ hardware > > > > the need to run swapped from matroxset tarball to > > > > separate the displays > > > I don't see why this should be unsolvable. All matroxset do is > > > to run some ioctl's. Surely the same code could be called from > > > within the framebuffer driver at boot time? > > > > > > I believe this was done because single-monitor setups are > > > common, and the kernel probably can't easily know where that > > > monitor is attached. (Well, it could use DDC...) > > > > > > But people don't buy a G550 to run single-monitor, so > > > having the kernel separate the displays and force the user > > > to think about which connector to use is fine with me. > > > > well may be, > > it would be nice to have a CONFIG_MATROXFB_SEPARATE_DISPLAYS, > > but i'm not sure it's doable, and i'm sure Petr is not working on it :( > > i think that the graphic BIOS initialize them in that way and the > fbdriver > > will have to work around these BIOS settings > > > > > > > > > > 4.) related to 3 > > > > after swapped, both heads are blank until a VT switch, > > > > > > > > and on head1 there is a lot of garbage until login + logout > > > > actually the garbage is on all vc's except the first one (head 1) > > > > but on all vc's usable is only 4/6 of the hight of the screen > > > > the top 1/6 is ocupied by the logo, the bottom 1/6 by nothing > > > > on vc1 and by garbage on vc2-vc6. > > > I believe the garbage is stuff that vgacon left in graphichs memory > before > > > handing the console over to the framebuffer. At least this was the > > > explanation when I complained about similiar garbage on a radeon > > > with framebuffer. compiling _without_ vgacon indeed made all > > > the garbage go away, but the option to turn off vgacon recently > > > disappeared from menuconfig. :-( no garbage with ruby cvs :-) > > i actually do have it :-) > > > > it disapeared with the option to disable PS2 input && serio > > you need "Generic Setup -> Remove kernel features (for embedded > systems)" > > enabled to be able to change them > > > > i might try disabling it > > / * not sure when i'll find time for that :( */ > > > > svetljo > > > > PS > > > > how do you setup the fb mode? > > i'm still using a single monitor with switch > > @ 640x480, and fbset doesn't seem to work > > > kernel boot parameter: video=matroxfb:vesa:0x11A > This is supposed to be 1280x1024 16-bit, I'm not sure > it works. But X definitely sets the resolution to what it > wants, on both screens. Exiting the accelerated server > messes up the other screen as X "restores" the video card > to previous settings. thanks svetljo -- Neu bei GMX: Preissenkung für MMS-Versand und FreeMMS! Ideal für alle, die gerne MMS verschicken: 25 FreeMMS/Monat mit GMX TopMail. http://www.gmx.net/de/cgi/produktemail +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Helge H. <hel...@ai...> - 2003-12-03 15:36:44
|
Svetoslav Slavtchev wrote: > > PS.3 > attachments > > 260t9-20031115.txt -- oopses with vanilla ruby-260t9-20031115 > > AA02-ruby-20031029_matroxfb_fix.patch - fixes the problem, > Aivils sent it to me as vt.3.diff , not sure if it hit the list > > AA03-ruby-fb_resize.patch - another fix by Aivils, > the same oopses without the previous patch, Aivils sent it to me as rc1.diff > 260t9-20031115-rc1.txt -- oopses without AA02 ,but with AA03 aplied > I tried these patches, on top of 2.6.0-test11 The patch to vt.c didn't apply cleanly. The patch tries to move vc_resize(... below the two lines with visual_init(... and update_attr(... But the existing vt.c didn't have the vc_resize(... call at all. It was removed. So I added it back in, in the place the patch wanted it. Booting the resulting kernel (with fbcon compiled in) crashed. An unreadable oops followed immediately after: input: AT Translated Set 2 keyboard on isa0060/serio0 serio: i8042 KBD port at 0x60,0x64 irq 1 registering 0-0050 registering 0-0051 registering 0-0052 registering 0-0053 registering 0-0054 registering 0-0055 registering 0-0056 registering 0-0057 registering 1-0050 registering 1-0051 registering 1-0052 registering 1-0053 registering 1-0054 registering 1-0055 registering 1-0056 registering 1-0057 Here I normally get messages from the md driver initializing, instead I got a semi-garbled message about killing init. Helge Hafting |
From: Svetoslav S. <sv...@gm...> - 2003-12-05 09:43:38
|
Hi, sorry for the late reply and confusion, it seems that Aivils has uploaded the wrong tarball under ruby-260t9-20031115 on his web these patches are needed for this tarball or older ruby, current cvs (and tarball) doesn't need them and it works here if compiled as modules /* except the strange issues with matroxset/fbcon * and mode different from the default 640x480 * :( */ best, svetljo > Svetoslav Slavtchev wrote: > > > > > PS.3 > > attachments > > > > 260t9-20031115.txt -- oopses with vanilla ruby-260t9-20031115 > > > > AA02-ruby-20031029_matroxfb_fix.patch - fixes the problem, > > Aivils sent it to me as vt.3.diff , not sure if it hit the list > > > > AA03-ruby-fb_resize.patch - another fix by Aivils, > > the same oopses without the previous patch, Aivils sent it to me as > rc1.diff > > 260t9-20031115-rc1.txt -- oopses without AA02 ,but with AA03 aplied > > > > I tried these patches, on top of 2.6.0-test11 > The patch to vt.c didn't apply cleanly. The patch tries > to move vc_resize(... below the two lines > with visual_init(... and update_attr(... > > But the existing vt.c didn't have the vc_resize(... call at all. > It was removed. So I added it back in, in the place > the patch wanted it. > > Booting the resulting kernel (with fbcon compiled in) > crashed. An unreadable oops followed immediately after: > > input: AT Translated Set 2 keyboard on isa0060/serio0 > serio: i8042 KBD port at 0x60,0x64 irq 1 > registering 0-0050 > registering 0-0051 > registering 0-0052 > registering 0-0053 > registering 0-0054 > registering 0-0055 > registering 0-0056 > registering 0-0057 > registering 1-0050 > registering 1-0051 > registering 1-0052 > registering 1-0053 > registering 1-0054 > registering 1-0055 > registering 1-0056 > registering 1-0057 > > Here I normally get messages from the md driver initializing, instead I > got a semi-garbled message about killing init. > > Helge Hafting > > > > ------------------------------------------------------- > This SF.net email is sponsored by OSDN's Audience Survey. > Help shape OSDN's sites and tell us what you think. Take this > five minute survey and you could win a $250 Gift Certificate. > http://www.wrgsurveys.com/2003/osdntech03.php?site=8 > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > -- +++ GMX - die erste Adresse für Mail, Message, More +++ Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net |
From: Aivils S. <Aiv...@un...> - 2003-12-01 09:47:43
|
>PS.4 >the last commit was 14 Nov, so Aivils's tarball contains the same code as >cvs > >Aivils, >should ruby-260t9-20031115 really work OK without this patches ? I send bunch of patches to You because i gropingly move in the dark. ruby-260t9-20031115 really works because include all vt.c patches! >PS.5 >the remaining issues >/* most likely hardware limitations involved > * and XFree "bugs" too > */ > >1.) X->VT->X on head1 (vt7) >X head1 is displayed on both heads, VT switch on head2 fixes it > >2.) the mentioned XFree hack should be integrated smarter, >currently you need additional binary for each additional fbcon fbcon should be cleaned at first. >3.) probably unsolvable/ hardware >the need to run swapped from matroxset tarball to >separate the displays > >4.) related to 3 >after swapped, both heads are blank until a VT switch, > >and on head1 there is a lot of garbage until login + logout >actually the garbage is on all vc's except the first one (head 1) >but on all vc's usable is only 4/6 of the hight of the screen >the top 1/6 is ocupied by the logo, the bottom 1/6 by nothing >on vc1 and by garbage on vc2-vc6. >Everything becomes normal after a login + logout , but until logout >only graphics(e.g. ncurses menuconfig) paint to the entire screen, >a ls, ps, whatever will use only the middle 4/6 of the screen hight I read some times code , but do not detect bug :( I have /dev/vc/1 with same issues. >there is no such problem with head2 >/* which misses a blinking cursor, cursor is always on :-) */ Ok. Next snapshot contains vt_struct with cursor timer. Aivils Stoss |
From: Svetoslav S. <sv...@gm...> - 2003-12-01 12:28:26
|
> > >PS.4 > >the last commit was 14 Nov, so Aivils's tarball contains the same code as > >cvs > > > >Aivils, > >should ruby-260t9-20031115 really work OK without this patches ? > > I send bunch of patches to You because i gropingly move in the dark. > ruby-260t9-20031115 really works because include all vt.c patches! ruby-260t9-20031115 without any patches still oopses and no fbcon is shows oopses attached to the previous mail and the vt.3.diff still solves the problem > >PS.5 > >the remaining issues > >/* most likely hardware limitations involved > > * and XFree "bugs" too > > */ > > > >1.) X->VT->X on head1 (vt7) > >X head1 is displayed on both heads, VT switch on head2 fixes it > > > >2.) the mentioned XFree hack should be integrated smarter, > >currently you need additional binary for each additional fbcon > > fbcon should be cleaned at first. you mean: no need for intermediate hacks, let's fix fbcon and add ioctls and then work on final XFree solution/* not hack */ ? > >3.) probably unsolvable/ hardware > >the need to run swapped from matroxset tarball to > >separate the displays > > > >4.) related to 3 > >after swapped, both heads are blank until a VT switch, > > > >and on head1 there is a lot of garbage until login + logout > >actually the garbage is on all vc's except the first one (head 1) > >but on all vc's usable is only 4/6 of the hight of the screen > >the top 1/6 is ocupied by the logo, the bottom 1/6 by nothing > >on vc1 and by garbage on vc2-vc6. > >Everything becomes normal after a login + logout , but until logout > >only graphics(e.g. ncurses menuconfig) paint to the entire screen, > >a ls, ps, whatever will use only the middle 4/6 of the screen hight > > I read some times code , but do not detect bug :( > I have /dev/vc/1 with same issues. are vc2-vc6 perfectly ok with your setup ? > > >there is no such problem with head2 > >/* which misses a blinking cursor, cursor is always on :-) */ > > Ok. Next snapshot contains vt_struct with cursor timer. thanks :-) it's no a important to me bug, but everytime i leave the screen for a minute and look again at it i'm wondering wether the PC is still alive or it has crashed :( svetljo -- Neu bei GMX: Preissenkung für MMS-Versand und FreeMMS! Ideal für alle, die gerne MMS verschicken: 25 FreeMMS/Monat mit GMX TopMail. http://www.gmx.net/de/cgi/produktemail +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Aivils S. <Aiv...@un...> - 2003-12-01 13:00:18
|
>> I send bunch of patches to You because i gropingly move in the dark. >> ruby-260t9-20031115 really works because include all vt.c patches! > >ruby-260t9-20031115 without any patches still oopses and no fbcon is shows >oopses attached to the previous mail >and the vt.3.diff still solves the problem oops. That snapshot contains old version. CVS contains right. Aivils |
From: Aivils S. <Aiv...@un...> - 2003-12-01 14:47:41
|
>> > this way you can configure VT- keyboard mapping >> > & consistent evdev[n] mouse[n] devices >> > /* although udev is probably much better for the evdev & mice */ >> > >> I'll look at this someday. Do I need modules for this to work? > >good question When "foo" device detected, then kernel call /etc/hotplug/input.agent Troubles are non-existing file systems in bootime, /proc and so on. So all Your devices detected in boot time and input.agent has read-only root filesytem and nothing more. This is main reason to use input device drivers modular. Instead modules exists input.rc scripts, which do same. >how do you setup the fb mode? >i'm still using a single monitor with switch >@ 640x480, and fbset doesn't seem to work video=matroxfb:800x600@75 for 1st head. Also i use fbset. Modular fbcon donot resize after fbset resize. Aivils Stoss |
From: Svetoslav S. <sv...@gm...> - 2003-12-01 15:32:57
|
> > >> > this way you can configure VT- keyboard mapping > >> > & consistent evdev[n] mouse[n] devices > >> > /* although udev is probably much better for the evdev & mice */ > >> > > >> I'll look at this someday. Do I need modules for this to work? > > > >good question > > When "foo" device detected, then kernel call /etc/hotplug/input.agent > Troubles are non-existing file systems in bootime, /proc and so on. > So all Your devices detected in boot time and input.agent has read-only > root filesytem and nothing more. This is main reason to use input device > drivers modular. Instead modules exists input.rc scripts, which do same. > > >how do you setup the fb mode? > >i'm still using a single monitor with switch > >@ 640x480, and fbset doesn't seem to work > > video=matroxfb:800x600@75 > > for 1st head. Also i use fbset. Modular fbcon donot resize after > fbset resize. > nice but ------- modpreobe.conf ------------- options matroxfb_base mem=16 vesa=0x117 options matroxfb_crtc2 mem=16 --------------------------------------- matroxfb: Matrox G550 detected matroxfb: MTRR's turned on matroxfb: 1024x768x16bpp (virtual: 1024x65536) matroxfb: framebuffer at 0xD8000000, mapped to 0xe0ca9000, size 16777216 fb0: MATROX frame buffer device fb0: initializing hardware matroxfb_crtc2: secondary head of fb0 was registered as fb1 fbcon_startup: mode: MATROX fbcon_startup: visual: 2 fbcon_startup: res: 1024x0-16 Console: switching to colour MATROX 128x25 vc:1-16 fbcon_startup: mode: MATROX DH fbcon_startup: visual: 2 fbcon_startup: res: 640x480-32 Console: Colour MATROX DH 80x30 vc:17-32 do you see the nice "fbcon_startup: res: 1024x0-16" both heads are off after that /* everything quite normal before loading fbcon */ and --------------------------------------- [root@tux root]# fbset -fb /dev/fb0 1024x768-70 [root@tux root]# fbset -fb /dev/fb0 mode "1024x0-1486" # D: 74.996 MHz, H: 56.473 kHz, V: 1486.134 Hz geometry 1024 0 1024 0 8 timings 13334 144 24 29 3 136 6 accel true rgba 8/0,8/0,8/0,0/0 endmode [root@tux root]# fbset -fb /dev/fb0 800x600-70 [root@tux root]# fbset -fb /dev/fb0 mode "800x0-1237" # D: 44.899 MHz, H: 44.543 kHz, V: 1237.308 Hz geometry 800 0 832 0 8 timings 22272 40 24 15 9 144 12 hsync high accel true rgba 8/0,8/0,8/0,0/0 endmode ------------------------------------------------- any clues, ideas ? svetljo PS. the latest cvs works OK modular, at least in default mode 640x480 -- HoHoHo! Seid Ihr auch alle schön brav gewesen? GMX Weihnachts-Special: Die 1. Adresse für Weihnachts- männer und -frauen! http://www.gmx.net/de/cgi/specialmail +++ GMX - die erste Adresse für Mail, Message, More! +++ |
From: Svetoslav S. <sv...@gm...> - 2003-12-01 16:03:06
|
Hi Petr, Hi all, is this a matroxfb bug ? > > >how do you setup the fb mode? > > >i'm still using a single monitor with switch > > >@ 640x480, and fbset doesn't seem to work > > > > video=matroxfb:800x600@75 > > > > for 1st head. Also i use fbset. Modular fbcon donot resize after > > fbset resize. > > > > nice but > ------- modprobe.conf ------------- > options matroxfb_base mem=16 vesa=0x117 > options matroxfb_crtc2 mem=16 > --------------------------------------- > > matroxfb: Matrox G550 detected > matroxfb: MTRR's turned on > matroxfb: 1024x768x16bpp (virtual: 1024x65536) > matroxfb: framebuffer at 0xD8000000, mapped to 0xe0ca9000, size 16777216 > fb0: MATROX frame buffer device > fb0: initializing hardware > matroxfb_crtc2: secondary head of fb0 was registered as fb1 > fbcon_startup: mode: MATROX > fbcon_startup: visual: 2 > fbcon_startup: res: 1024x0-16 > Console: switching to colour MATROX 128x25 vc:1-16 > fbcon_startup: mode: MATROX DH > fbcon_startup: visual: 2 > fbcon_startup: res: 640x480-32 > Console: Colour MATROX DH 80x30 vc:17-32 > > do you see the nice "fbcon_startup: res: 1024x0-16" > both heads are off after that > /* everything quite normal before loading fbcon */ > > and > --------------------------------------- > [root@tux root]# fbset -fb /dev/fb0 1024x768-70 > [root@tux root]# fbset -fb /dev/fb0 > > mode "1024x0-1486" > # D: 74.996 MHz, H: 56.473 kHz, V: 1486.134 Hz > geometry 1024 0 1024 0 8 > timings 13334 144 24 29 3 136 6 > accel true > rgba 8/0,8/0,8/0,0/0 > endmode > > [root@tux root]# fbset -fb /dev/fb0 800x600-70 > [root@tux root]# fbset -fb /dev/fb0 > > mode "800x0-1237" > # D: 44.899 MHz, H: 44.543 kHz, V: 1237.308 Hz > geometry 800 0 832 0 8 > timings 22272 40 24 15 9 144 12 > hsync high > accel true > rgba 8/0,8/0,8/0,0/0 > endmode > ------------------------------------------------- > > any clues, ideas ? > > > svetljo > > PS. > the latest cvs works OK modular, > at least in default mode 640x480 PS.2 the same happens without loading fbcon when swapped or normal from the matroxset tarball are executed this is without fbcon loaded /* over ssh, quite easy to reproduce with modular matroxfb */ same with vesa=0x118 [root@tux root]# fbset -fb /dev/fb0 mode "1024x768-60" # D: 64.994 MHz, H: 48.359 kHz, V: 59.998 Hz geometry 1024 768 1024 4096 32 timings 15386 160 32 30 4 128 4 accel true rgba 8/16,8/8,8/0,8/24 endmode [root@tux root]# fbset -fb /dev/fb1 mode "640x480-60" # D: 25.176 MHz, H: 31.469 kHz, V: 59.942 Hz geometry 640 480 640 480 32 timings 39721 48 16 33 10 96 2 rgba 8/16,8/8,8/0,8/24 endmode [root@tux root]# matroxfb_swapped [root@tux root]# fbset -fb /dev/fb0 mode "1024x0-1273" # D: 64.994 MHz, H: 48.359 kHz, V: 1272.598 Hz geometry 1024 0 1024 0 32 timings 15386 160 32 30 4 128 4 accel true rgba 8/16,8/8,8/0,8/24 endmode [root@tux root]# fbset -fb /dev/fb1 mode "640x480-60" # D: 25.176 MHz, H: 31.469 kHz, V: 59.942 Hz geometry 640 480 640 480 32 timings 39721 48 16 33 10 96 2 rgba 8/16,8/8,8/0,8/24 endmode [root@tux root]# fbset -fb /dev/fb0 640x480-60 [root@tux root]# fbset -fb /dev/fb0 mode "640x0-699" # D: 25.175 MHz, H: 31.469 kHz, V: 699.305 Hz geometry 640 0 640 0 8 timings 39722 48 16 33 10 96 2 accel true rgba 8/0,8/0,8/0,0/0 endmode best, svetljo -- Neu bei GMX: Preissenkung für MMS-Versand und FreeMMS! Ideal für alle, die gerne MMS verschicken: 25 FreeMMS/Monat mit GMX TopMail. http://www.gmx.net/de/cgi/produktemail +++ GMX - die erste Adresse für Mail, Message, More! +++ |