From: James S. <jsi...@in...> - 2004-05-18 18:57:11
|
Hi folks!!! For July 19 and 20th I will be attending the Desktop Summit as well as the kernel summit. The kernel summit is unfortunely by invitation only :-( but the desktop one is open to the public. To the people that have worked hard on this project let me know if you want to go to the desktop summit. If you don't have the money I will work something out for you. I plan to give a demo of Ruby there!!!! So in the next few weeks I'm going to set up a box to send to the conference. My goals for the demo are to have a 4 desktop system. I like to get KDE running on one desktop and Gnome on another. Then the other 2 heads would be a Embedded JVM running and a regular console. |
From: Helge H. <hel...@ai...> - 2004-05-19 08:52:56
|
James Simmons wrote: >Hi folks!!! > > For July 19 and 20th I will be attending the Desktop Summit as >well as the kernel summit. The kernel summit is unfortunely by >invitation only :-( but the desktop one is open to the public. To the >people that have worked hard on this project let me know if you want to go >to the desktop summit. If you don't have the money I will work something >out for you. I plan to give a demo of Ruby there!!!! So in the next few >weeks I'm going to set up a box to send to the conference. > >My goals for the demo are to have a 4 desktop system. I like to get KDE >running on one desktop and Gnome on another. Then the other 2 heads would >be a Embedded JVM running and a regular console. > Ideally set up so the session type (gnome, kde, regular,...) is decided by login name rather than console number? Ability to use any console for anything is great, it avoids the problem of everybody wanting the "best" screen at home. :-) Will you tell them about Zoltán Böszörményi's double 3D setup too? :-) Helge Hafting |
From: James S. <jsi...@in...> - 2004-05-19 19:38:46
|
> >well as the kernel summit. The kernel summit is unfortunely by > >invitation only :-( but the desktop one is open to the public. To the > >people that have worked hard on this project let me know if you want to go > >to the desktop summit. If you don't have the money I will work something > >out for you. I plan to give a demo of Ruby there!!!! So in the next few > >weeks I'm going to set up a box to send to the conference. > > > >My goals for the demo are to have a 4 desktop system. I like to get KDE > >running on one desktop and Gnome on another. Then the other 2 heads would > >be a Embedded JVM running and a regular console. > > > Ideally set up so the session type (gnome, kde, regular,...) is > decided by login name rather than console number? Ability > to use any console for anything is great, it avoids the problem > of everybody wanting the "best" screen at home. :-) > > Will you tell them about Zoltán Böszörményi's double 3D setup too? :-) Yes. |
From: Zoltan B. <zb...@fr...> - 2004-05-20 17:44:21
|
James Simmons =EDrta: >>Will you tell them about Zolt=E1n B=F6sz=F6rm=E9nyi's double 3D setup t= oo? :-) >=20 >=20 > Yes. Great! :-) Do you need more details about the machine setup? I suppose you put your presentation somewhere after Desktop summit. Will you post the link to this list, too? BTW I will try to do the same under x86_64 FC2 soon. Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi |
From: Aivils <ai...@un...> - 2004-05-24 07:01:43
|
On Tuesday 18 May 2004 21:57, James Simmons wrote: > > Hi folks!!! > > For July 19 and 20th I will be attending the Desktop Summit as > well as the kernel summit. The kernel summit is unfortunely by > invitation only :-( but the desktop one is open to the public. To the > people that have worked hard on this project let me know if you want to go > to the desktop summit. If you don't have the money I will work something > out for you. These summits befall over sea! > I plan to give a demo of Ruby there!!!! So in the next few > weeks I'm going to set up a box to send to the conference. Current CVS contain ugly VGA driver (?) bug - tty1 cursor lost positon after vt switch. I have no idea where that bug lives. You must patch or hide with fbdev. gpm - Your tree breaks (/dev/vc/0) . /dev/vcs* - I don't know how to use it, rather that is broken. > My goals for the demo are to have a 4 desktop system. 4 desktop system, seems, well tested is Nvidia adapters only, with closed source drivers. I agree usage of easy sytems, where each user have soundcard too. Sound setup is hard, because each program use own sound driver. > I like to get KDE > running on one desktop and Gnome on another. gdm allow choose session. Most psyhodelic is full screen vmware session with lovely M$ inside. > Then the other 2 heads would > be a Embedded JVM running and a regular console. xf86 stops VGA output. looks like PC legacy ports used for VGA stoping. This feature does not distrub starting number of xf86 and i never try locate it. Of course ruby needs for good "marketing manager" , which tell anybody about benefits of ruby. Aivils |
From: Aivils <ai...@un...> - 2004-05-26 06:27:51
|
Hi All! CVS now contains linux-ruby against 2.6.6. FBIOGET_CON2FBMAP, FBIOSET_CON2FBMAP ioctl() uses dummy call. Aivils Stoss |
From: Helge H. <hel...@ai...> - 2004-05-27 12:38:25
|
Aivils wrote: >Hi All! > > CVS now contains linux-ruby against 2.6.6. > >FBIOGET_CON2FBMAP, FBIOSET_CON2FBMAP ioctl() uses >dummy call. > > Thanks for the good work - ruby-2.6.6 works for me. There is a small problem where I get 998 messages in /var/log/messages during startup. This slows startup down with abouit half a minute, but doesn't seem to have other problems: One run: May 26 22:57:27 monster kernel: Badness in vc_resize at drivers/char/vt.c:1095 May 26 22:57:27 monster kernel: Call Trace: May 26 22:57:27 monster kernel: [<c0208ad4>] vc_resize+0x3b4/0x3c0 May 26 22:57:27 monster kernel: [<c0128678>] notifier_call_chain+0x18/0x40 May 26 22:57:27 monster kernel: [<c0283999>] fb_resize_vt+0x59/0x70 May 26 22:57:27 monster kernel: [<c0283b17>] fb_ioctl+0x167/0x340 May 26 22:57:27 monster kernel: [<c0134391>] unlock_page+0x11/0x60 May 26 22:57:27 monster kernel: [<c014aaa9>] exclusive_swap_page+0x39/0x90 May 26 22:57:27 monster kernel: [<c0134391>] unlock_page+0x11/0x60 May 26 22:57:27 monster kernel: [<c014109d>] do_wp_page+0x7d/0x2f0 May 26 22:57:27 monster kernel: [<c014613d>] __pte_chain_free+0x4d/0x50 May 26 22:57:27 monster kernel: [<c015f5dc>] sys_ioctl+0xec/0x25a May 26 22:57:27 monster kernel: [<c0106cff>] syscall_call+0x7/0xb May 26 22:57:28 monster kernel: The next one appeared twice: May 26 22:57:28 monster kernel: Badness in set_origin at drivers/char/vt.c:503 May 26 22:57:28 monster kernel: Call Trace: May 26 22:57:28 monster kernel: [<c020767c>] set_origin+0x9c/0xb0 May 26 22:57:28 monster kernel: [<c0208970>] vc_resize+0x250/0x3c0 May 26 22:57:28 monster kernel: [<c0128678>] notifier_call_chain+0x18/0x40 May 26 22:57:28 monster kernel: [<c0283999>] fb_resize_vt+0x59/0x70 May 26 22:57:28 monster kernel: [<c0283b17>] fb_ioctl+0x167/0x340 May 26 22:57:28 monster kernel: [<c0134391>] unlock_page+0x11/0x60 May 26 22:57:28 monster kernel: [<c014aaa9>] exclusive_swap_page+0x39/0x90 May 26 22:57:28 monster kernel: [<c0134391>] unlock_page+0x11/0x60 May 26 22:57:28 monster kernel: [<c014109d>] do_wp_page+0x7d/0x2f0 May 26 22:57:28 monster kernel: [<c014613d>] __pte_chain_free+0x4d/0x50 May 26 22:57:28 monster kernel: [<c015f5dc>] sys_ioctl+0xec/0x25a May 26 22:57:28 monster kernel: [<c0106cff>] syscall_call+0x7/0xb May 26 22:57:28 monster kernel: May 26 22:57:28 monster kernel: Badness in set_palette at drivers/char/vt.c:291 May 26 22:57:28 monster kernel: Call Trace: May 26 22:57:28 monster kernel: [<c0206e18>] set_palette+0x78/0x80 May 26 22:57:28 monster kernel: [<c0207936>] update_screen+0x36/0x80 May 26 22:57:28 monster kernel: [<c0208a25>] vc_resize+0x305/0x3c0 May 26 22:57:28 monster kernel: [<c0283999>] fb_resize_vt+0x59/0x70 May 26 22:57:28 monster kernel: [<c0283b17>] fb_ioctl+0x167/0x340 May 26 22:57:28 monster kernel: [<c0134391>] unlock_page+0x11/0x60 May 26 22:57:28 monster kernel: [<c014aaa9>] exclusive_swap_page+0x39/0x90 May 26 22:57:28 monster kernel: [<c0134391>] unlock_page+0x11/0x60 May 26 22:57:28 monster kernel: [<c014109d>] do_wp_page+0x7d/0x2f0 May 26 22:57:28 monster kernel: [<c014613d>] __pte_chain_free+0x4d/0x50 May 26 22:57:28 monster kernel: [<c015f5dc>] sys_ioctl+0xec/0x25a May 26 22:57:28 monster kernel: [<c0106cff>] syscall_call+0x7/0xb Then I got 31 of these: May 26 22:57:28 monster kernel: Badness in vc_resize at drivers/char/vt.c:1095 May 26 22:57:28 monster kernel: Call Trace: May 26 22:57:28 monster kernel: [<c0208ad4>] vc_resize+0x3b4/0x3c0 May 26 22:57:28 monster kernel: [<c0283999>] fb_resize_vt+0x59/0x70 May 26 22:57:28 monster kernel: [<c0283b17>] fb_ioctl+0x167/0x340 May 26 22:57:28 monster kernel: [<c0134391>] unlock_page+0x11/0x60 May 26 22:57:28 monster kernel: [<c014aaa9>] exclusive_swap_page+0x39/0x90 May 26 22:57:28 monster kernel: [<c0134391>] unlock_page+0x11/0x60 May 26 22:57:28 monster kernel: [<c014109d>] do_wp_page+0x7d/0x2f0 May 26 22:57:28 monster kernel: [<c014613d>] __pte_chain_free+0x4d/0x50 May 26 22:57:28 monster kernel: [<c015f5dc>] sys_ioctl+0xec/0x25a May 26 22:57:28 monster kernel: [<c0106cff>] syscall_call+0x7/0xb Then the machine was reset, probably by me. The log then contains a restart followed by about 900 of these vc_restart messages. Could this be a ruby problem, or some sort of framebuffer problem? Helge Hafting |
From: Aivils <ai...@un...> - 2004-05-27 14:26:51
|
On Thursday 27 May 2004 15:40, Helge Hafting wrote: > Aivils wrote: > > >Hi All! > > > > CVS now contains linux-ruby against 2.6.6. > > > >FBIOGET_CON2FBMAP, FBIOSET_CON2FBMAP ioctl() uses > >dummy call. > > > > > Thanks for the good work - ruby-2.6.6 works for me. > There is a small problem where I get 998 messages in > /var/log/messages during startup. > This slows startup down with abouit half a minute, > but doesn't seem to have other problems: > One run: > > May 26 22:57:27 monster kernel: Badness in vc_resize at > drivers/char/vt.c:1095 > May 26 22:57:27 monster kernel: Call Trace: > May 26 22:57:27 monster kernel: [<c0208ad4>] vc_resize+0x3b4/0x3c0 > May 26 22:57:27 monster kernel: [<c0128678>] notifier_call_chain+0x18/0x40 > May 26 22:57:27 monster kernel: [<c0283999>] fb_resize_vt+0x59/0x70 > May 26 22:57:27 monster kernel: [<c0283b17>] fb_ioctl+0x167/0x340 > May 26 22:57:27 monster kernel: [<c0134391>] unlock_page+0x11/0x60 > May 26 22:57:27 monster kernel: [<c014aaa9>] exclusive_swap_page+0x39/0x90 > May 26 22:57:27 monster kernel: [<c0134391>] unlock_page+0x11/0x60 > May 26 22:57:27 monster kernel: [<c014109d>] do_wp_page+0x7d/0x2f0 > May 26 22:57:27 monster kernel: [<c014613d>] __pte_chain_free+0x4d/0x50 > May 26 22:57:27 monster kernel: [<c015f5dc>] sys_ioctl+0xec/0x25a > May 26 22:57:27 monster kernel: [<c0106cff>] syscall_call+0x7/0xb > May 26 22:57:28 monster kernel: > Then the machine was reset, probably by me. > > The log then contains a restart followed by about 900 of these > vc_restart messages. > > Could this be a ruby problem, or some sort of framebuffer problem? ruby needs for tousends of acquire_console_sem();release_console_sem(); pairs. Please try this patch, on succes i upload subject on CVS. diff -Nurp ruby-CVS-20040525/drivers/video/console/fbcon.c ruby-CVS-20040527/drivers/video/console/fbcon.c --- ruby-CVS-20040525/drivers/video/console/fbcon.c 2004-05-24 21:26:48.000000000 +0300 +++ ruby-CVS-20040527/drivers/video/console/fbcon.c 2004-05-27 18:06:46.000000000 +0300 @@ -761,7 +761,9 @@ static void fbcon_set_display(struct vc_ if (!init) { if (vc->vc_cols != nr_cols || vc->vc_rows != nr_rows) + acquire_console_sem(); vc_resize(vc, nr_cols, nr_rows); + release_console_sem(); else if (IS_VISIBLE && vc->vc_mode == KD_TEXT) { accel_clear_margins(vc, info, 0); @@ -1842,7 +1844,9 @@ static int fbcon_do_set_font(struct vc_d && (info->var.yres_virtual % h < info->var.yres % h)) p->vrows--; updatescrollmode(p, vc); + acquire_console_sem(); vc_resize(vc, info->var.xres / w, info->var.yres / h); + release_console_sem(); if (IS_VISIBLE && softback_buf) { int l = fbcon_softback_size / vc->vc_size_row; if (l > 5) diff -Nurp ruby-CVS-20040525/drivers/video/fbmem.c ruby-CVS-20040527/drivers/video/fbmem.c --- ruby-CVS-20040525/drivers/video/fbmem.c 2004-05-24 21:26:48.000000000 +0300 +++ ruby-CVS-20040527/drivers/video/fbmem.c 2004-05-27 18:07:10.000000000 +0300 @@ -1010,8 +1010,11 @@ fb_resize_vt(struct fb_info *info) vc = vt->default_mode; vc->vc_cols = info->var.xres/vc->vc_font.width; vc->vc_rows = info->var.yres/vc->vc_font.height; - for(i = 0; i < vt->vc_count; i++) + for(i = 0; i < vt->vc_count; i++) { + acquire_console_sem(); vc_resize(vt->vc_cons[i], vc->vc_cols, vc->vc_rows); + release_console_sem(); + } return 0; } |
From: Helge H. <hel...@ai...> - 2004-05-28 07:14:47
|
Aivils wrote: >On Thursday 27 May 2004 15:40, Helge Hafting wrote: > > >>Aivils wrote: >> >> >> >>>Hi All! >>> >>> CVS now contains linux-ruby against 2.6.6. >>> >>>FBIOGET_CON2FBMAP, FBIOSET_CON2FBMAP ioctl() uses >>>dummy call. >>> >>> >>> >>> >>Thanks for the good work - ruby-2.6.6 works for me. >>There is a small problem where I get 998 messages in >>/var/log/messages during startup. >>This slows startup down with abouit half a minute, >>but doesn't seem to have other problems: >>One run: >> >>May 26 22:57:27 monster kernel: Badness in vc_resize at >>drivers/char/vt.c:1095 >>May 26 22:57:27 monster kernel: Call Trace: >>May 26 22:57:27 monster kernel: [<c0208ad4>] vc_resize+0x3b4/0x3c0 >>May 26 22:57:27 monster kernel: [<c0128678>] notifier_call_chain+0x18/0x40 >>May 26 22:57:27 monster kernel: [<c0283999>] fb_resize_vt+0x59/0x70 >>May 26 22:57:27 monster kernel: [<c0283b17>] fb_ioctl+0x167/0x340 >>May 26 22:57:27 monster kernel: [<c0134391>] unlock_page+0x11/0x60 >>May 26 22:57:27 monster kernel: [<c014aaa9>] exclusive_swap_page+0x39/0x90 >>May 26 22:57:27 monster kernel: [<c0134391>] unlock_page+0x11/0x60 >>May 26 22:57:27 monster kernel: [<c014109d>] do_wp_page+0x7d/0x2f0 >>May 26 22:57:27 monster kernel: [<c014613d>] __pte_chain_free+0x4d/0x50 >>May 26 22:57:27 monster kernel: [<c015f5dc>] sys_ioctl+0xec/0x25a >>May 26 22:57:27 monster kernel: [<c0106cff>] syscall_call+0x7/0xb >>May 26 22:57:28 monster kernel: >> >> > > > >>Then the machine was reset, probably by me. >> >>The log then contains a restart followed by about 900 of these >>vc_restart messages. >> >>Could this be a ruby problem, or some sort of framebuffer problem? >> >> > >ruby needs for tousends of acquire_console_sem();release_console_sem(); >pairs. > >Please try this patch, on succes i upload subject on CVS. > > I tested it. It doesn't compile as-is. That seemed to be a trivial missing pair of curly braces, so I added them. (See below) Then it compiled, with the following warnings: drivers/video/fbmem.c: In function `fb_resize_vt': drivers/video/fbmem.c:1014: warning: implicit declaration of function `acquire_console_sem' drivers/video/fbmem.c:1016: warning: implicit declaration of function `release_console_sem' Probably a missing header - it linked and gave me a kernel. It hung, though. Could this be the problem, or is it a more difficult deadlock issue with the semaphore? The kernel hung after initializing the framebuffers, before setting up fbcon. So all I got was a screenful of pre-fbcon garbage. It is interesting to note that the first keyboard was dead, it did not react to "numlock" or sysrq sequences. The second keyboard was fine, it reacted to numloc/capslock by turning the LEDs on/off as usual, and I could sync & reboot using sysrq sequences there. My guess is that this looks like some sort of deadlock. Perhaps the console semaphore isn't free, or something else needs it? Do the "printk" that tells us about "160x64 color fbcon takeover" need the semaphore? Only one console locked up. >diff -Nurp ruby-CVS-20040525/drivers/video/console/fbcon.c ruby-CVS-20040527/drivers/video/console/fbcon.c >--- ruby-CVS-20040525/drivers/video/console/fbcon.c 2004-05-24 21:26:48.000000000 +0300 >+++ ruby-CVS-20040527/drivers/video/console/fbcon.c 2004-05-27 18:06:46.000000000 +0300 >@@ -761,7 +761,9 @@ static void fbcon_set_display(struct vc_ > if (!init) { > > if (vc->vc_cols != nr_cols || vc->vc_rows != nr_rows) > > Added a { here >+ acquire_console_sem(); > vc_resize(vc, nr_cols, nr_rows); >+ release_console_sem(); > > Added a } here. Without these braces I got a syntax error on the "else" on the next line. > else if (IS_VISIBLE && > vc->vc_mode == KD_TEXT) { > accel_clear_margins(vc, info, 0); >@@ -1842,7 +1844,9 @@ static int fbcon_do_set_font(struct vc_d > && (info->var.yres_virtual % h < info->var.yres % h)) > p->vrows--; > updatescrollmode(p, vc); >+ acquire_console_sem(); > vc_resize(vc, info->var.xres / w, info->var.yres / h); >+ release_console_sem(); > if (IS_VISIBLE && softback_buf) { > int l = fbcon_softback_size / vc->vc_size_row; > if (l > 5) >diff -Nurp ruby-CVS-20040525/drivers/video/fbmem.c ruby-CVS-20040527/drivers/video/fbmem.c >--- ruby-CVS-20040525/drivers/video/fbmem.c 2004-05-24 21:26:48.000000000 +0300 >+++ ruby-CVS-20040527/drivers/video/fbmem.c 2004-05-27 18:07:10.000000000 +0300 >@@ -1010,8 +1010,11 @@ fb_resize_vt(struct fb_info *info) > vc = vt->default_mode; > vc->vc_cols = info->var.xres/vc->vc_font.width; > vc->vc_rows = info->var.yres/vc->vc_font.height; >- for(i = 0; i < vt->vc_count; i++) >+ for(i = 0; i < vt->vc_count; i++) { >+ acquire_console_sem(); > vc_resize(vt->vc_cons[i], vc->vc_cols, vc->vc_rows); >+ release_console_sem(); >+ } > return 0; > } > > > I hope this bug report can be of help, Helge Hafting |