linuxconsole-dev

Re: G550DH + G450DH Framebuffer succes & directfb question.

[Svetoslav S. <sv...@gm...>]

Hi all,

first of all , i've yet ound time to play with ruby-2.6.5,
so here are my experiancies with ruby-2.6.3

> On Thursday 13 May 2004 10:56, Mark Hurenkamp wrote:
> > I managed to find a couple of matrox cards (G550 dual head AGP and a
> G450
> > dualhead PCI card), and decided to give it a go with ruby.
> > I did not succeed in setting up a working dualhead X environment yet
> > (although Xinerama works), but with framebuffer i have everything
> workingnow on kernel 2.6.5, even with modular matroxfb & fbcon drivers.
There are
> > still a few issues (I think Helge also mentioned some of them before):


i could get it running with fbdev X driver, and i think mga +fb 
on a G550DH, but i needed Aivils hack for VT_SHIFT & 2 Xserver binaries

> > 
> >     * upon loading of the matroxfb drivers, all framebuffers show a
> garbled
> >       screen.
same here

> >     * when loading fbcon, the garbled screen cleans up (mostly), but on
> the
> >       main console I see a big white rectangle. On none of the consoles
> I
> >       can see the login prompt, but it appears after pressing enter key
> :-)

same here
> >     * when switching virtual console on the main console with F1-F6
> keys,
> >       the framebuffer setup is somehow messed up and so the main console
> is
> >       also shown on the second head. Rerunning the matroxset commands
> does

i'm not sure i've seen this

> >       not help, but after rerunning my 'reset_matrox' script which also
> >       uses fbset to setup the framebuffers, everything works again.

 
> Unfortunately i do not understand how hard is fb support,
> when i add fbcon. Each fb low level driver slightly differs.
> Seems, matrox fb is spiteful.

it's very, very spiteful :(

it's just that the maintainer doesn't like the new API,
and doesn't care much about the in kernel driver
and ....
he still ships his own matroxfb driver, which reverts the API 
change almost completely 
:(

but IMO this is the only (?i386?) hardware 
with some support for multi-head fbdev

best,

svetljo

-- 
NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/dsl

Re: Help request - Xfree 4.2.0, Mandrake 8.2, bruby 2.4.25

[Svetoslav S. <sv...@gm...>]

> Hello list,

Hi Daniel,

> 
> I've been experimenting with the Backstreet Ruby patch and I feel that I
> almost have it working, but I'm having difficulty getting X running on my
> second or third graphics card. I'm hoping someone on the list can kindly
> give me some help. (please?!)
> 
> Setup:
>  - Duron 1.6
>  - VIA KT4AV Motherboard
>  - 512MB
>  - 3 * PCI Sapphire ATI Radeon 7000 32MB (0:5:0, 0:6:0, 0:7:0)
>  - Mandrake 8.2

don't you know that MDK-8.2 suport is discontinued :-)
kidding, but update might help a bit

>  - 1 standard PS2 keyboard
>  - 1 USB keyboard
>  - 2 USB mice
> 
> The kernel works just fine (I think). I downloaded a clean 2.4.25, patched
> it, mkinitrd'd, grub'd, no problems. USB is compiled as modules, because
> the
> Mandrake init scripts seem to like it like that.
> 
> X server is installed from XFree86-concurrent-server-4.2.0-10mdk.i586.rpm
> and I'm not using /proc/bus/pci/hackvideo

using the concurrent X server is equal to using the hack,
not sure if this is the problem thought
 
> I can start 'X0' as :0 on the first PCI card with either keyboard (vt7 or
> vt17), and either mouse (/dev/input/mouse0 or mouse1), so it seems the
> inputs are all in /dev/input (devfs) correctly.
> 
> 
> So here's the problem... After stopping X0 (no X server running at all
> now),
> I cannot get X1 to start on the second PCI card, using:
> 
> 	startx -- /usr/X11R6.bin/X1 :1 -xf86config /etc/X11/XF86Config-4-X1
> -layout
> X1 vt17 > tmp.log 2>&1
> 
> The console display I'm on goes blank (but monitor isn't entering power
> saving mode), no LEDs function on the keyboard, and as far as I can tell
> Linux hangs. There's no /var/log/XFree.1.log after rebooting to single
> user
> mode / rc3, and the last messages I can see in my tmp.log read :
> 
>   (WW) RADEON: No matching Device section for instance (BusID PCI 0:5:0)
> found
>   (WW) RADEON: No matching Device section for instance (BusID PCI 0:7:0)
> found
> 

you should first get all cards working in single mode,
or/and Xinerama

Xinerama would be probably easier with XFdrake

but ...
your XFree version is tooooooo old :(
(it shouldn't metter if you are configuring under bruby or normal kernel)

when you get them working in Xinerama drop a line :-)

> The file XF86Config-4-X1 contains:
> 
>   Section "Device"
>     Identifier	"ATI Radeon 2"
>     VendorName	""
>     BoardName	""
>     Driver	"radeon"
>     Option	"DPMS" "off"
>     BusID	"PCI:0:6:0"
>   EndSection
> 
>   Section "Screen"
>     Identifier "screen2"
>     Device "ATI Radeon 2"
>     Montior "monitor2"
>     ...
>   EndSection
> 
>   Section "ServerLayout"
>     Identifier "X1"
>     Screen "screen2"
>     InputDevice "USB Mouse 2" "CorePointer"
>     InputDevice "Keyboard2" "CoreKeyboard"
>     Option "SingleCard" "true"
>     #Option "PrefBusID" "0:6:0" # does this work?
>   EndSection
> 
> 
> I tried using -prefbusid, but the XFree-concurrent I've got doesn't seem
> to
> recognise it?

nope, 
it's unsupported, both commandline parameter & config file
options PrefBusID & SingleCard are unsuported by it

that's why for a bit newer mdk versions
there are both -prefbusid & concurrent Xservers,
and for latest only prefbusid(as the hack is equal to concurrent)
well there are no "official" packages for MDK-10,
but in case of interest i have some Xorg packages
(if i didn't messed up smth, there should be -prefbusid Xserver
 for any MDK that ships with XFree-4.3)

> So, please, can someone suggest where I might be going wrong?!
> 

sorry to say it,
but i can not help a lot without working Xinerama or all
cards in single mode :(

i really think a XFree update could help,
which probably means distro update too 

best,

svetljo

-- 
NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/dsl

Help request - Xfree 4.2.0, Mandrake 8.2, bruby 2.4.25

[Daniel L. <dan...@ya...>]

Hello list,

I've been experimenting with the Backstreet Ruby patch and I feel that I
almost have it working, but I'm having difficulty getting X running on my
second or third graphics card. I'm hoping someone on the list can kindly
give me some help. (please?!)

Setup:
 - Duron 1.6
 - VIA KT4AV Motherboard
 - 512MB
 - 3 * PCI Sapphire ATI Radeon 7000 32MB (0:5:0, 0:6:0, 0:7:0)
 - Mandrake 8.2
 - 1 standard PS2 keyboard
 - 1 USB keyboard
 - 2 USB mice

The kernel works just fine (I think). I downloaded a clean 2.4.25, patched
it, mkinitrd'd, grub'd, no problems. USB is compiled as modules, because the
Mandrake init scripts seem to like it like that.

X server is installed from XFree86-concurrent-server-4.2.0-10mdk.i586.rpm
and I'm not using /proc/bus/pci/hackvideo

I can start 'X0' as :0 on the first PCI card with either keyboard (vt7 or
vt17), and either mouse (/dev/input/mouse0 or mouse1), so it seems the
inputs are all in /dev/input (devfs) correctly.


So here's the problem... After stopping X0 (no X server running at all now),
I cannot get X1 to start on the second PCI card, using:

	startx -- /usr/X11R6.bin/X1 :1 -xf86config /etc/X11/XF86Config-4-X1 -layout
X1 vt17 > tmp.log 2>&1

The console display I'm on goes blank (but monitor isn't entering power
saving mode), no LEDs function on the keyboard, and as far as I can tell
Linux hangs. There's no /var/log/XFree.1.log after rebooting to single user
mode / rc3, and the last messages I can see in my tmp.log read :

  (WW) RADEON: No matching Device section for instance (BusID PCI 0:5:0)
found
  (WW) RADEON: No matching Device section for instance (BusID PCI 0:7:0)
found

The file XF86Config-4-X1 contains:

  Section "Device"
    Identifier	"ATI Radeon 2"
    VendorName	""
    BoardName	""
    Driver	"radeon"
    Option	"DPMS" "off"
    BusID	"PCI:0:6:0"
  EndSection

  Section "Screen"
    Identifier "screen2"
    Device "ATI Radeon 2"
    Montior "monitor2"
    ...
  EndSection

  Section "ServerLayout"
    Identifier "X1"
    Screen "screen2"
    InputDevice "USB Mouse 2" "CorePointer"
    InputDevice "Keyboard2" "CoreKeyboard"
    Option "SingleCard" "true"
    #Option "PrefBusID" "0:6:0" # does this work?
  EndSection


I tried using -prefbusid, but the XFree-concurrent I've got doesn't seem to
recognise it?

So, please, can someone suggest where I might be going wrong?!

Many thanks for any help offered,

Dan
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.686 / Virus Database: 447 - Release Date: 14/05/2004

Kernel summit/Desktop summit.

[James S. <jsi...@in...>]

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. 

Re: Why does decvte.c exists?

[James S. <jsi...@in...>]

> > the question goes to mainly to James Simmons (jsi...@in...).
> > 
> > The chance of getting the multihead feature into mainline
> > would be higher if the VTE was the same in the ruby tree.
> > 
> > Maintainability is better if the terminal emulator
> > is in its separate source file but why didn't you used
> > the original Linux implementation?
> 
> If anytime ruby-tree will be merged with Linus-tree, then ruby code will be
> splited into small pieces. Rather decvte.c stay out of Linus-tree.

In the mainstream kernel printk via the console driver and the tty layer 
are interwoven. Also the console driver is on top of the tty layer. My 
goal for 2.7.X is to create a very light weight printk that could work 
without the VT tty layer. 
 

Re: Kernel summit 2004: graphics/console issues

[James S. <jsi...@in...>]

Hi folks!!!

   I have been following that list and also been in discussion in those 
threads. This year I will be going to the Kernel Summit to discuss the 
graphics issue as well as present ruby there. 

> Hi,
> 
> I found the following post on the directfb mailing list, which I
> think may be interesting reading material for linuxconsole subscribers
> as well.
> I read a few messages in the posted threads, which address the multihead,
> multi-framebuffer and multi-console issues, and how to deal with them.
> 
> Mark.
> 
> -------- Original Message --------
> Subject: [directfb-dev] kernel summit 2004
> From: Torgeir Veimo <to...@po...>
> Date: Mon, May 17, 2004 13:37
> To: dir...@di...
> 
> Are any directfb developers going to the kernel-summit this year?
> 
> Seem that gfx kernle driver architecture is an upcoming issue. Threads at
> 
> http://thunker.thunk.org/pipermail/ksummit-2004-discuss/2004-April/thread.htmlhttp://thunker.thunk.org/pipermail/ksummit-2004-discuss/2004-May/thread.html
> 
> 

Is the wacom input driver known to work with linux-ruby ?

[<ce...@ri...>]

Hi all,

I use a kernel version 2.6.5 patched with ruby and have troubles making my=
=20
wacom tablet useable.
Every click or touch event throws in XFree logs several lines like that:
wacom: relative event received (0)!!!
wacom: relative event received (1)!!!

Before looking further in the wacom driver configuration and code, I'd like=
 to=20
know if anyone knows if there wouldn't be an incompatibility between the ru=
by=20
patch (because of the changes in the input layer) and the wacom driver.

TIA
C=E9dric

Re: G550DH + G450DH Framebuffer succes & directfb question.

[Aivils <ai...@un...>]

On Thursday 13 May 2004 10:56, Mark Hurenkamp wrote:
> I managed to find a couple of matrox cards (G550 dual head AGP and a G450
> dualhead PCI card), and decided to give it a go with ruby.
> I did not succeed in setting up a working dualhead X environment yet
> (although Xinerama works), but with framebuffer i have everything workingnow on kernel 2.6.5, even with modular matroxfb & fbcon drivers. There are
> still a few issues (I think Helge also mentioned some of them before):
> 
>     * upon loading of the matroxfb drivers, all framebuffers show a garbled
>       screen.
>     * when loading fbcon, the garbled screen cleans up (mostly), but on the
>       main console I see a big white rectangle. On none of the consoles I
>       can see the login prompt, but it appears after pressing enter key :-)
>     * when switching virtual console on the main console with F1-F6 keys,
>       the framebuffer setup is somehow messed up and so the main console is
>       also shown on the second head. Rerunning the matroxset commands does
>       not help, but after rerunning my 'reset_matrox' script which also
>       uses fbset to setup the framebuffers, everything works again.

Unfortunately i do not understand how hard is fb support,
when i add fbcon. Each fb low level driver slightly differs.
Seems, matrox fb is spiteful.

> Since the framebuffers are working so well, I decided to try some DirectFB
> applications (would like to run freevo or mythtv on my TV and try
> the XDirectFB server), however, they don't seem to like ruby because I keep
> getting the following error with every application I try to start:
> 
> (!) DirectFB/FBDev/vt: FBIOGET_CON2FBMAP failed!
>     --> Inappropriate ioctl for device
> 
> Is there anything I can do to further investigate? Perhaps I can patch
> ruby to add a dummy IOCTL or patch directfb in some way that the IOCTL is
> not needed anymore?
> Should I take this to the directfb mailinglist, or is it a ruby problem?

pure ruby problem.

> The message reminds me of the old con2fbmap tool, which we don't need
> anymore since ruby takes care of console to fb mapping :-)

con2fbmap is to match complicated for current linux-ruby. In abstract
user may use con2fbmap on 3 head (or more) system, when 1st user
uses 2 heads and 2nd user uses 1 head.
Current i agree more simple solution , when each user uses 1 video card
(or head - matrox case), 1 keyboard.
I will revert back original linux con2fb code. Then con2fbmap does dummy
IOCTL, compatible with linus-tree :)

How sane is moving con2fb[ ] array to VT structure ?
Existence of con2fb[ ] breaks all automatic created links between
TTY and fbdev.

Aivils

Kernel summit 2004: graphics/console issues

[Mark H. <Mar...@xs...>]

Hi,

I found the following post on the directfb mailing list, which I
think may be interesting reading material for linuxconsole subscribers
as well.
I read a few messages in the posted threads, which address the multihead,
multi-framebuffer and multi-console issues, and how to deal with them.

Mark.

-------- Original Message --------
Subject: [directfb-dev] kernel summit 2004
From: Torgeir Veimo <to...@po...>
Date: Mon, May 17, 2004 13:37
To: dir...@di...

Are any directfb developers going to the kernel-summit this year?

Seem that gfx kernle driver architecture is an upcoming issue. Threads at

http://thunker.thunk.org/pipermail/ksummit-2004-discuss/2004-April/thread.htmlhttp://thunker.thunk.org/pipermail/ksummit-2004-discuss/2004-May/thread.html

-- 
Torgeir Veimo <to...@po...>



-- 
Info:  To unsubscribe send a mail to ec...@di... with
"unsubscribe directfb-dev" as subject.

Re: Patched Xfree86 4.3.0 in Debian

[Kjetil K. <kj...@kj...>]

On mandag 17. mai 2004, 09:45, Aivils wrote:
> > s/PrefBusID/IsolateDevice/g
> > right?
>
> Yep.

Cool! And thanks!

> > Then, I wondered about the HOWTO: Probably, we should now add some
> > Debian-specific notes, now that people most likely can just use
> > Sarge or Sid and get the X servers they need, but must use slightly
> > different options than the rest of the world.
>
> If end-user will start muptiple local xf86, then "IsolateDevice" is
> not enough. Each xf86 open /dev/ttyXX , which one current is allowed
> under Linus-tree kernel. Secondary xf86 become active when user press
> Alt-F8 and primary xf86 goes spleep until user activate /dev/tty7.
>
> Multiple current /dev/ttyXX exist only in linux-ruby.

Yes, of course. Debian's approach to that is that you can create 
kernel-patch-packages, which the user can trivially apply if s/he 
chooses to build a kernel themself. For example, that's how Reiser4 is 
supported in Debian: 
http://packages.debian.org/unstable/devel/kernel-patch-2.6-reiser4

I know Andreas has been thinking about making such a kernel-patch 
package for ruby (and suggested I could do it, he'd sponsor it, but I 
do not feel quite up to the task... :-) ). It would be really cool to 
have the xf86 patches and the kernel-patch package. Meanwhile, there 
are a lot more good tools available to compile a kernel, and people do 
that more routinely, than to compile xf86, so it is a real advancement. 
So, I just use Linus tree with (backstreet) ruby patches now. 


> > Unless you guys find Branden's
> > changes reasonable, and adopt and recommend the above patch to
> > others that want to get this stuff running, in which case the HOWTO
> > could be changed to reflect the new names. So, what do you think
> > about that?
>
> While single current TTY only allowed Branden have not a raw material
> about what write how-to.

Uhm, I must admit I didn't fully parse that... :-) 

BTW, the linuxconsole-dev archives on Sourceforge seems dead... Nothing 
has been archived since March, that's why I thought the list was 
quiet...

Cheers,

Kjetil
-- 
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
kj...@kj...  web...@sk...  ed...@le...
Homepage: http://www.kjetil.kjernsmo.net/        OpenPGP KeyID: 6A6A0BBC

Re: Patched Xfree86 4.3.0 in Debian

[Aivils <ai...@un...>]

On Tuesday 11 May 2004 23:18, Kjetil Kjernsmo wrote:
> Hi all!
> 
> Long time, no see! Seems to have been quiet around here lately...?
> 
> Well, I bring some good news (and I need a little advice): Some of you
> might allready know, thanks to some great work by Andreas Schuldei and
> others, the patches to X most of us need to run multi-head setups have
> been applied to the Debian packages, they have been in the unstable
> release for 11 days now, and today, they are going into Sarge. Unless
> it breaks the system of somebody who aren't using it, it will be in
> Sarge when it some day is released as Stable! Which means, it will be
> accessible to many more users. Cool, eh? The first version it can be
> found in is 4.3.0.dfsg.1-1.
> 
> There has been some changes to the patch however. It has been reviewed
> by Branden Robinson in particular and the rest of the Debian X Strike
> Force team. Branden felt that "PrefBusID" wasn't very descriptive of
> what it really does, so it is in Debian known as "IsolateDevice". They
> have also written some documentation to it and made some other minor
> changes if I understand it correctly. In addition to "IsolateDevice",
> it also has a "SingleCard" layout option.
> 
> If I have understood the branches in the repository, the diff is
> available at
> http://necrotic.deadbeast.net/xsf/XFree86/branches-4.3.0-sid/debian/patches/080_pci_isolate_device_feature.diff
> and I thought you guys might want to review it.
> 
> I haven't tried the new packages out myself yet, I plan to do it Real
> Soon Now[tm]. But before I venture off into the somewhat unknown, I
> just wanted to ask those who understand the patch: To reconfigure my X
> servers to use the new Debian packages, all I have to do is
> s/PrefBusID/IsolateDevice/g
> right?

Yep.

> Then, I wondered about the HOWTO: Probably, we should now add some
> Debian-specific notes, now that people most likely can just use Sarge
> or Sid and get the X servers they need, but must use slightly different
> options than the rest of the world.

If end-user will start muptiple local xf86, then "IsolateDevice" is not
enough. Each xf86 open /dev/ttyXX , which one current is allowed under
Linus-tree kernel. Secondary xf86 become active when user press
Alt-F8 and primary xf86 goes spleep until user activate /dev/tty7.

Multiple current /dev/ttyXX exist only in linux-ruby.

> Unless you guys find Branden's 
> changes reasonable, and adopt and recommend the above patch to others
> that want to get this stuff running, in which case the HOWTO could be
> changed to reflect the new names. So, what do you think about that?

While single current TTY only allowed Branden have not a raw material
about what write how-to.

Aivils

Re: G550DH + G450DH Framebuffer succes & directfb question.

[Helge H. <hel...@ai...>]

Mark Hurenkamp wrote:

>Hi,
>
>
>I managed to find a couple of matrox cards (G550 dual head AGP and a G450
>dualhead PCI card), and decided to give it a go with ruby.
>I did not succeed in setting up a working dualhead X environment yet
>(although Xinerama works), but with framebuffer i have everything workingnow on kernel 2.6.5, even with modular matroxfb & fbcon drivers.
>
Did you try modular only, or did you also try compiled-in framebuffer?
I have not been able to run 2.6.3 or later, because of a divide error when
initializing the framebuffers.  I'll try modular now, to see if that 
improves
anything.

> There are
>still a few issues (I think Helge also mentioned some of them before):
>
>    * upon loading of the matroxfb drivers, all framebuffers show a garbled
>      screen.
>  
>
Fortunately, a minor problem. They are usually loaded only once.

>    * when loading fbcon, the garbled screen cleans up (mostly), but on the
>      main console I see a big white rectangle. On none of the consoles I
>      can see the login prompt, but it appears after pressing enter key :-)
>  
>
The fbcons works, they merely start out with some garbage.

>    * when switching virtual console on the main console with F1-F6 keys,
>      the framebuffer setup is somehow messed up and so the main console is
>      also shown on the second head. Rerunning the matroxset commands does
>      not help, but after rerunning my 'reset_matrox' script which also
>      uses fbset to setup the framebuffers, everything works again.
>  
>
Now this is irritating.  It seems to be tied to changing resolution or
video mode. Changing resolution in X messes up the same way.

>Since the framebuffers are working so well, I decided to try some DirectFB
>applications (would like to run freevo or mythtv on my TV and try
>the XDirectFB server), however, they don't seem to like ruby because I keep
>getting the following error with every application I try to start:
>
>(!) DirectFB/FBDev/vt: FBIOGET_CON2FBMAP failed!
>    --> Inappropriate ioctl for device
>
>Is there anything I can do to further investigate? Perhaps I can patch
>  
>
Try on each console, maybe this fails only on some consoles?

>ruby to add a dummy IOCTL or patch directfb in some way that the IOCTL is
>not needed anymore?
>Should I take this to the directfb mailinglist, or is it a ruby problem?
>
>The message reminds me of the old con2fbmap tool, which we don't need
>anymore since ruby takes care of console to fb mapping :-)
>
>
>Well, I'm very impressed with ruby's current state on matroxfb, so
>good work guys!
>
>Mark.
>
>
>P.S.
>Did any of you have any success setting up dual independent (accelerated) X
>servers on the G550? I'm very interested to see your XF86Config!
>
>  
>
I haven't researched this more, but I once ran two accelerated
servers simultaneously.  (Both on the same screen though, but
that's a minor point - clever use of xinerama and or "screen 1"
should make it possible to get on separate screens)

The G550 with two accelerated X servers is fine as long as
you use ordinary 2D.   Run a 3D program on one server and
the other mostly freeze waiting for the 3D stuff to stop.
Two 3D programs simultaneously on separate xservers fail,
the second one simply segfaults.  All this may change with
newer xservers or newer DRI. My attempt was a few months ago.

Helge Hafting

G550DH + G450DH Framebuffer succes & directfb question.

[Mark H. <Mar...@xs...>]

Hi,


I managed to find a couple of matrox cards (G550 dual head AGP and a G450
dualhead PCI card), and decided to give it a go with ruby.
I did not succeed in setting up a working dualhead X environment yet
(although Xinerama works), but with framebuffer i have everything workingnow on kernel 2.6.5, even with modular matroxfb & fbcon drivers. There are
still a few issues (I think Helge also mentioned some of them before):

    * upon loading of the matroxfb drivers, all framebuffers show a garbled
      screen.
    * when loading fbcon, the garbled screen cleans up (mostly), but on the
      main console I see a big white rectangle. On none of the consoles I
      can see the login prompt, but it appears after pressing enter key :-)
    * when switching virtual console on the main console with F1-F6 keys,
      the framebuffer setup is somehow messed up and so the main console is
      also shown on the second head. Rerunning the matroxset commands does
      not help, but after rerunning my 'reset_matrox' script which also
      uses fbset to setup the framebuffers, everything works again.

Since the framebuffers are working so well, I decided to try some DirectFB
applications (would like to run freevo or mythtv on my TV and try
the XDirectFB server), however, they don't seem to like ruby because I keep
getting the following error with every application I try to start:

(!) DirectFB/FBDev/vt: FBIOGET_CON2FBMAP failed!
    --> Inappropriate ioctl for device

Is there anything I can do to further investigate? Perhaps I can patch
ruby to add a dummy IOCTL or patch directfb in some way that the IOCTL is
not needed anymore?
Should I take this to the directfb mailinglist, or is it a ruby problem?

The message reminds me of the old con2fbmap tool, which we don't need
anymore since ruby takes care of console to fb mapping :-)


Well, I'm very impressed with ruby's current state on matroxfb, so
good work guys!

Mark.


P.S.
Did any of you have any success setting up dual independent (accelerated) X
servers on the G550? I'm very interested to see your XF86Config!

Re: Pointers and Suggestions?

[Mark H. <Mar...@xs...>]

> I have it working right now, only thing I did differently that I can
> think of is that I tried a
> startx -- -layout PCI-Console
> first to confirm the PCI card was OK...closed that, then started AGP
> then second PCI session. I also removed a keyboard1 input reference....

I also had some problems getting my Asus 7100 Deluxe & my XFX GF4 440MX up
and running simultaneously, and noticed that when I had run in Xinerama
mode earlier, the problem would go away.Now I run a "X -- -layout Xinerama -probeonly" before I start kdm (thus
initialising the PCI card), and things work perfectly :-)

Mark.

Pointers and Suggestions?

[James v. Z. <ja...@dv...>]

here's my intended target application:

4 head "serverstation"
big P4, 2Gb DDR
1 x GF AGP, video-in, video-out
3 x GF PCI

VMware 4.5 ( up and running )
AGP  = X login, video + media use
PCI1 = automatic login to restricted account and launch windoz 2003
server in a full-screen VMware session.
PCI2 = automatic login to restricted account and launch windoz XP Pro in
a full-screen VMware session.
PCI3 = X login, administrative use, miscellaneous virtual machines.

Currently using a 2800+Athlon, 1Gb for testing. It has an AGP dual head
+ one TNT2 CPI

- Can one patch 2.6.5-ruby kernel source to 2.6.6-ruby, or must the cvs
be patched, and then applied to 2.6.6 source ? -

I have successfully compiled 2.6.5-ruby and created a prefbusid version
of XFree86-4.3.0-55 rpm by adding the patch and prep entries to the
source rpm's .spec file

That's been installed on two test boxes using 
rpm -Uvh XFree86-4.3.0-55.i686.rpm --force
replacing the stock executables in the fedora core installations.

I am happy to compile RH9, FC1, and FC2 (when released and I have) rpm
packages

I've then looked at editing /etc/X11/XF86Config

I have successfully started two X servers, and had VMware sessions
running full screen in both, which says to me that this is eventually
going to work pretty much exactly as I want it to.

Catch is the startup does not seem to be consistent. As often than not,
X is crashing when I start the second X session. I had it working fine
one day, the next it wouldn't work. Yesterday I had it working briefly.

Symptom seems to be more frequently occuring that I try to start the
second server first time and a connection is rejected. If I try again, I
lose the console. 

I have it working right now, only thing I did differently that I can
think of is that I tried a
startx -- -layout PCI-Console
first to confirm the PCI card was OK...closed that, then started AGP
then second PCI session. I also removed a keyboard1 input reference....

Since it hasn't been consistent yet, I thought I ask for some pointers
and suggestions...

from here, I'd be wanting two login at runlevel5, with no X gripes, and
then the restricted users, auto login and custom .xinitrc   ?

This is the XF86Config from one box, intended 1xAGP dual head login,
1xPCI login:

Two examples of; one configuration has the AGP dual-head configured as
Xinemera, the other as another screen ( and hence desktop etc...)
Second login is configured for a PCI TNT2, using nVidia drivers...

###########################################################
This seemed more ruby friendly?? by a fraction??
###########################################################

# XFree86 4 configuration created by redhat-config-xfree86

Section "ServerLayout"
Identifier     "AGP-Console"
Screen         "Screen AGP 0" 0 0
# Screen         "Screen AGP 1" RightOf "Screen AGP 0"
InputDevice    "Mouse0" "CorePointer"
InputDevice    "Keyboard0" "CoreKeyboard"
Option        "SingleCard" "true"
EndSection

Section "ServerLayout"
Identifier     "PCI-Console"
Screen         "Screen PCI"
InputDevice    "Mouse1" "CorePointer"
InputDevice    "Keyboard0" "CoreKeyboard"
Option        "SingleCard" "true"
EndSection

Section "Files"
RgbPath      "/usr/X11R6/lib/X11/rgb"
FontPath     "unix/:7100"
EndSection

Section "Module"
Load  "dbe"
    # Load the glx module.
Load  "glx"
Load  "extmod"
Load  "type1"
Load  "freetype"
EndSection

Section "ServerFlags"

    # Uncomment this to cause a core dump at the spot where a signal is
    # received.  This may leave the console in an unusable state, but
may
    # provide a better stack trace in the core dump to aid in debugging
    #NoTrapSignals
    # Uncomment this to disable the <Crtl><Alt><BS> server abort
sequence
    # This allows clients to receive this key event.
    #DontZap
    # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode
switching
    # sequences.  This allows clients to receive these key events.
    #DontZoom
    # This  allows  the  server  to start up even if the
    # mouse device can't be opened/initialised.
Option     "allowmouseopenfail"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver      "Keyboard"
Option     "AutoRepeat" "250 30"
Option     "XkbRules" "xfree86"
Option     "XkbModel" "pc105"
Option     "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver      "mouse"
Option     "Protocol" "IMPS/2"
Option     "Device" "/dev/input/mouse0"
Option     "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier  "Mouse1"
Driver      "mouse"
Option     "Protocol" "IMPS/2"
Option     "Device" "/dev/input/mouse1"
Option     "ZAxisMapping" "4 5"
EndSection

Section "Monitor"

    # be sure to replace these values with values appropriate for your
    # monitor!
    # 3840x2400 @ 12Hz for IBM's T221 FlatPanel
    # Modeline "3840x2400" 148.0 3840 3944 4328 4816 2400 2401 2404 2418
Identifier   "MyMonitor"
VendorName   "IBM"
ModelName    "IBM P201"
HorizSync    30.0 - 107.0
VertRefresh  50.0 - 160.0
EndSection

Section "Device"

    # update this with the PCI id of your card.  Consult the output
    # of the 'lspci' command. The  BusID is usually optional when
    # only using one graphics card.
    # sample twinview setup
    # Option     "TwinView"
    # be sure to replace the HorizSync and VertRefresh with correct
values
    # for your monitor!  
    Option     "TwinView"
    Option     "SecondMonitorHorizSync" "30-70"
    Option     "SecondMonitorVertRefresh" "50-160"
    Option     "TwinViewOrientation" "RightOf"
    Option     "MetaModes" "1920x1440,1280x1024" 
    # "1600x1200,1280x1024" "1280x1024,1280x1024" "1024x768,1024x768"
"800x600,800x600"
Identifier  "NV AGP 0"
Driver      "nvidia"
VendorName  "nvidia"
BoardName   "G-Force2 Dual Head"
Option     "ConnectedMonitor" "crt,crt"
BusID       "PCI:3:0:0"
EndSection

#Section "Device"
#
#    # update this with the PCI id of your card.  Consult the output
#    # of the 'lspci' command. The  BusID is usually optional when
#    # only using one graphics card.
#    # sample twinview setup
#    # Option     "TwinView"
#    # be sure to replace the HorizSync and VertRefresh with correct
values
#    # for your monitor!  
#    # Option     "TwinView"
#    # Option     "SecondMonitorHorizSync" "30-107"
#    # Option     "SecondMonitorVertRefresh" "50-160"
#    # Option     "TwinViewOrientation" "RightOf"
#    # Option     "MetaModes" "1920x1440,1280x1024"
# Identifier  "NV AGP 1"
# Driver      "nvidia"
# VendorName  "nvidia"
# BoardName   "G-Force2 Dual Head"
# Option     "ConnectedMonitor" "crt,crt"
# BusID       "PCI:3:0:0"
# Screen      1
#EndSection

Section "Device"

    # update this with the PCI id of your card.  Consult the output
    # of the 'lspci' command.  The BusID is usually optional when
    # only using one graphics card.
Identifier  "NV PCI"
Driver      "nvidia"
VendorName  "nvidia"
BusID       "PCI:1:9:0"
EndSection

Section "Screen"
Identifier "Screen AGP 0"
Device     "NV AGP 0"
Monitor    "MyMonitor"
DefaultDepth     24
SubSection "Display"
Depth     8
Modes    "1920x1440" "1600x1200" "1280x1024" "1024x768" "800x600"
"640x400"
EndSubSection
SubSection "Display"
Depth     16
Modes    "1920x1440" "1600x1200" "1280x1024" "1024x768" "800x600"
"640x480"
EndSubSection
SubSection "Display"
Depth     24
Modes    "1920x1440" "1600x1200" "1400x1050" "1280x1024" "1280x960"
"1152x864" "1024x768" "800x600" "640x480" "640x400"
EndSubSection
EndSection

#Section "Screen"
# Identifier "Screen AGP 1"
# Device     "NV AGP 1"
# Monitor    "MyMonitor"
# DefaultDepth     24
# SubSection "Display"
# Depth     8
# Modes    "1280x1024" "1024x768" "800x600" "640x400"
# EndSubSection
# SubSection "Display"
# Depth     16
# Modes    "1280x1024" "1024x768" "800x600" "640x480"
# EndSubSection
# SubSection "Display"
# Depth     24
# Modes    "1280x1024" "1280x960" "1152x864" "1024x768" "800x600"
"640x480" "640x400"
# EndSubSection
#EndSection

Section "Screen"
Identifier "Screen PCI"
Device     "NV PCI"
Monitor    "MyMonitor"
DefaultDepth     24
SubSection "Display"
Depth     8
Modes    "1400x1050" "1280x1024" "1024x768" "800x600" "640x400"
EndSubSection
SubSection "Display"
Depth     16
Modes    "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth     24
Modes    "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Group        0
Mode         0666
EndSection


##############################################################
This is what I'd rather be using if I can make it work, unless I hook
two identical monitors up.
WORKING NOW.
################################################################


# XFree86 4 configuration created by redhat-config-xfree86

Section "ServerLayout"
Identifier     "AGP-Console"
Screen         "Screen AGP 0" 0 0
Screen         "Screen AGP 1" RightOf "Screen AGP 0"
InputDevice    "Mouse0" "CorePointer"
InputDevice    "Keyboard0" "CoreKeyboard"
Option        "SingleCard" "true"
EndSection

Section "ServerLayout"
Identifier     "PCI-Console"
Screen         "Screen PCI"
InputDevice    "Mouse1" "CorePointer"
InputDevice    "Keyboard0" "CoreKeyboard"
Option        "SingleCard" "true"
EndSection

Section "Files"
RgbPath      "/usr/X11R6/lib/X11/rgb"
FontPath     "unix/:7100"
EndSection

Section "Module"
Load  "dbe"
    # Load the glx module.
Load  "glx"
Load  "extmod"
Load  "type1"
Load  "freetype"
EndSection

Section "ServerFlags"

    # Uncomment this to cause a core dump at the spot where a signal is
    # received.  This may leave the console in an unusable state, but
may
    # provide a better stack trace in the core dump to aid in debugging
    #NoTrapSignals
    # Uncomment this to disable the <Crtl><Alt><BS> server abort
sequence
    # This allows clients to receive this key event.
    #DontZap
    # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode
switching
    # sequences.  This allows clients to receive these key events.
    #DontZoom
    # This  allows  the  server  to start up even if the
    # mouse device can't be opened/initialised.
Option     "allowmouseopenfail"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver      "Keyboard"
Option     "AutoRepeat" "250 30"
Option     "XkbRules" "xfree86"
Option     "XkbModel" "pc105"
Option     "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver      "mouse"
Option     "Protocol" "IMPS/2"
Option     "Device" "/dev/input/mouse0"
Option     "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier  "Mouse1"
Driver      "mouse"
Option     "Protocol" "IMPS/2"
Option     "Device" "/dev/input/mouse1"
Option     "ZAxisMapping" "4 5"
EndSection

Section "Monitor"

    # be sure to replace these values with values appropriate for your
    # monitor!
    # 3840x2400 @ 12Hz for IBM's T221 FlatPanel
    # Modeline "3840x2400" 148.0 3840 3944 4328 4816 2400 2401 2404 2418
Identifier   "MyMonitor"
VendorName   "IBM"
ModelName    "IBM P201"
HorizSync    30.0 - 107.0
VertRefresh  50.0 - 160.0
EndSection

Section "Device"

    # update this with the PCI id of your card.  Consult the output
    # of the 'lspci' command. The  BusID is usually optional when
    # only using one graphics card.
    # sample twinview setup
    # Option     "TwinView"
    # be sure to replace the HorizSync and VertRefresh with correct
values
    # for your monitor!  
    # Option     "TwinView"
    # Option     "SecondMonitorHorizSync" "30-70"
    # Option     "SecondMonitorVertRefresh" "50-160"
    # Option     "TwinViewOrientation" "RightOf"
    # Option     "MetaModes" "1920x1440,1280x1024"
Identifier  "NV AGP 0"
Driver      "nvidia"
VendorName  "nvidia"
BoardName   "G-Force2 Dual Head"
Option     "ConnectedMonitor" "crt,crt"
BusID       "PCI:3:0:0"
EndSection

Section "Device"

    # update this with the PCI id of your card.  Consult the output
    # of the 'lspci' command. The  BusID is usually optional when
    # only using one graphics card.
    # sample twinview setup
    # Option     "TwinView"
    # be sure to replace the HorizSync and VertRefresh with correct
values
    # for your monitor!  
    # Option     "TwinView"
    # Option     "SecondMonitorHorizSync" "30-107"
    # Option     "SecondMonitorVertRefresh" "50-160"
    # Option     "TwinViewOrientation" "RightOf"
    # Option     "MetaModes" "1920x1440,1280x1024"
Identifier  "NV AGP 1"
Driver      "nvidia"
VendorName  "nvidia"
BoardName   "G-Force2 Dual Head"
Option     "ConnectedMonitor" "crt,crt"
BusID       "PCI:3:0:0"
Screen      1
EndSection

Section "Device"

    # update this with the PCI id of your card.  Consult the output
    # of the 'lspci' command.  The BusID is usually optional when
    # only using one graphics card.
Identifier  "NV PCI"
Driver      "nvidia"
VendorName  "nvidia"
BusID       "PCI:1:9:0"
EndSection

Section "Screen"
Identifier "Screen AGP 0"
Device     "NV AGP 0"
Monitor    "MyMonitor"
DefaultDepth     24
SubSection "Display"
Depth     8
Modes    "1920x1440" "1600x1200" "1280x1024" "1024x768" "800x600"
"640x400"
EndSubSection
SubSection "Display"
Depth     16
Modes    "1920x1440" "1600x1200" "1280x1024" "1024x768" "800x600"
"640x480"
EndSubSection
SubSection "Display"
Depth     24
Modes    "1920x1440" "1600x1200" "1400x1050" "1280x1024" "1280x960"
"1152x864" "1024x768" "800x600" "640x480" "640x400"
EndSubSection
EndSection

Section "Screen"
Identifier "Screen AGP 1"
Device     "NV AGP 1"
Monitor    "MyMonitor"
DefaultDepth     24
SubSection "Display"
Depth     8
Modes    "1280x1024" "1024x768" "800x600" "640x400"
EndSubSection
SubSection "Display"
Depth     16
Modes    "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth     24
Modes    "1280x1024" "1280x960" "1152x864" "1024x768" "800x600"
"640x480" "640x400"
EndSubSection
EndSection

Section "Screen"
Identifier "Screen PCI"
Device     "NV PCI"
Monitor    "MyMonitor"
DefaultDepth     24
SubSection "Display"
Depth     8
Modes    "1400x1050" "1280x1024" "1024x768" "800x600" "640x400"
EndSubSection
SubSection "Display"
Depth     16
Modes    "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth     24
Modes    "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Group        0
Mode         0666
EndSection

Patched Xfree86 4.3.0 in Debian

[Kjetil K. <kj...@kj...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all!

Long time, no see! Seems to have been quiet around here lately...?

Well, I bring some good news (and I need a little advice): Some of you=20
might allready know, thanks to some great work by Andreas Schuldei and=20
others, the patches to X most of us need to run multi-head setups have=20
been applied to the Debian packages, they have been in the unstable=20
release for 11 days now, and today, they are going into Sarge. Unless=20
it breaks the system of somebody who aren't using it, it will be in=20
Sarge when it some day is released as Stable! Which means, it will be=20
accessible to many more users. Cool, eh? The first version it can be=20
found in is 4.3.0.dfsg.1-1.

There has been some changes to the patch however. It has been reviewed=20
by Branden Robinson in particular and the rest of the Debian X Strike=20
=46orce team. Branden felt that "PrefBusID" wasn't very descriptive of=20
what it really does, so it is in Debian known as "IsolateDevice". They=20
have also written some documentation to it and made some other minor=20
changes if I understand it correctly. In addition to "IsolateDevice",=20
it also has a "SingleCard" layout option.=20

If I have understood the branches in the repository, the diff is=20
available at
http://necrotic.deadbeast.net/xsf/XFree86/branches-4.3.0-sid/debian/patches=
/080_pci_isolate_device_feature.diff
and I thought you guys might want to review it.=20

I haven't tried the new packages out myself yet, I plan to do it Real=20
Soon Now[tm]. But before I venture off into the somewhat unknown, I=20
just wanted to ask those who understand the patch: To reconfigure my X=20
servers to use the new Debian packages, all I have to do is=20
s/PrefBusID/IsolateDevice/g
right?

Then, I wondered about the HOWTO: Probably, we should now add some=20
Debian-specific notes, now that people most likely can just use Sarge=20
or Sid and get the X servers they need, but must use slightly different=20
options than the rest of the world. Unless you guys find Branden's=20
changes reasonable, and adopt and recommend the above patch to others=20
that want to get this stuff running, in which case the HOWTO could be=20
changed to reflect the new names. So, what do you think about that?=20

Cheers,

Kjetil
=2D --=20
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
kj...@kj...  web...@sk...  ed...@le...
Homepage: http://www.kjetil.kjernsmo.net/        OpenPGP KeyID: 6A6A0BBC
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAoTVLlE/Gp2pqC7wRAtQhAKCnfp+eQdfgd1YhdahxW4HcZDCpmACfYgul
NWvQzlRwzWKt9FkYCMooQu4=3D
=3DSmOY
=2D----END PGP SIGNATURE-----

Re: ruby-2.6.6

[Zoltan B. <zb...@fr...>]

Zoltan Boszormenyi =EDrta:
> Hi,
>=20
> here are changes against the linuxconsole CVS to be against
> linux-2.6.6.
>=20
> Best regards,
> Zolt=E1n B=F6sz=F6rm=E9nyi

I forgot something. The attached patch is part of a larger
patch against drivers/char/vt.c that is in linux-2.6.6
that has to be reverted so ruby-2.6.5 apply cleanly.
This part of the patch changes locking in con_open()
and con_close() (they became vt_open()/vt_close() in -ruby)
that I don't see where it should fit. Everything that was
in linux-2.6.6 is reapplied in the previous patch-set.
I may have forgotten something else, too.

Best regards,
Zolt=E1n B=F6sz=F6rm=E9nyi

ruby-2.6.6

[Zoltan B. <zb...@fr...>]

Hi,

here are changes against the linuxconsole CVS to be against
linux-2.6.6.

Best regards,
Zolt=E1n B=F6sz=F6rm=E9nyi

y u stopped replying my mail?

[Yoshie D. <fyn...@mb...>]

malodor covert untinged seyyid highboy eerie decoder optometry betrothed 
mulet revamp chimneypot bufflehead invective katrina balldress tractation 

Re: ruby 2.6.3 died with "divide error", ruby 2.6.5 has the same problem

[Helge H. <hel...@ai...>]

On Fri, May 07, 2004 at 10:09:57AM +0300, Aivils wrote:
> On Friday 07 May 2004 00:24, Helge Hafting wrote:
> > On Fri, Feb 27, 2004 at 05:30:36PM +0000, James Simmons wrote:
> > > 
> > > I just looked at the code. The only way the could happen is if 
> > > info->var.bits_per_pixel equals zero. Need to check the initialization to 
> > > see if it sets this.
> > >  
> > Did you find anything? I tried ruby-2.6.5, and got almost
> > exactly the same oops again.  I get the penguins and a message
> > about switchin to framebuffer, then this.  Only the first
> > lines are different from the 2.6.3 case:
> > 
> > divide error: 9999 [#1]
> > EIP at cfb_imageblit+0x262/0x5c0
> > trace:
> > buffered_runqueue
> > fbcon_putc
> > gotoxay
> > clear_region
> > hide_softcursor
> > update_screen
> > vt_map_display
> > fbcon_add
> > cache_alloc_refill
> > fbcon_event_notify
> > notifier_call_chain
> > register_framebuffer
> > matroxfb_db_regit
> > matroxfb_db_register
> > matroxfb_xrtx2_probe
> > matroxfb_register_driver
> > matroxfb_crtc2_init
> > do_initcalls
> > init
> > init
> > kernel_thread_helper
> > Kernel panic: attempted to kill init!
> > 
> > At this stage I only see the first framebuffer.  I don't know how far
> > the second get, because userland has to run "matroxset" before it 
> > gets routed to an actual screen.
> > 
> > The first framebuffer seems to work, it displays the penguins and
> > the oops flawlessly.  Could it be something wrong in initializing the
> > second fb?  Might a well-placed printk or something help?
> 
> I can help only with randomly-placed printk :)
> First try this patch
> --- ruby-CVS-20040430/drivers/video/console/fbcon.c     2004-04-30 09:45:06.000000000 +0300
> +++ ruby-test/drivers/video/console/fbcon.c     2004-05-07 09:41:49.000000000 +0300
> @@ -499,7 +499,7 @@ static const char *fbcon_startup(struct
>         vc->vc_can_do_color = info->var.bits_per_pixel != 1;
> 
>         /* We trust the mode the driver supplies. */
> -       if (!done && info->fbops->fb_set_par)
> +       if (info->fbops->fb_set_par)
>                 info->fbops->fb_set_par(info);

Thanks for the tip.  I tried it, but it looks like the problem
is something else because I got exactly the same oops this time.
Something with the matrox second fb driver perhaps?  I guess few
people actually use that.

Helge Hafting

Re: ruby 2.6.3 died with "divide error", ruby 2.6.5 has the same problem

[Aivils <ai...@un...>]

On Friday 07 May 2004 00:24, Helge Hafting wrote:
> On Fri, Feb 27, 2004 at 05:30:36PM +0000, James Simmons wrote:
> > 
> > I just looked at the code. The only way the could happen is if 
> > info->var.bits_per_pixel equals zero. Need to check the initialization to 
> > see if it sets this.
> >  
> Did you find anything? I tried ruby-2.6.5, and got almost
> exactly the same oops again.  I get the penguins and a message
> about switchin to framebuffer, then this.  Only the first
> lines are different from the 2.6.3 case:
> 
> divide error: 9999 [#1]
> EIP at cfb_imageblit+0x262/0x5c0
> trace:
> buffered_runqueue
> fbcon_putc
> gotoxay
> clear_region
> hide_softcursor
> update_screen
> vt_map_display
> fbcon_add
> cache_alloc_refill
> fbcon_event_notify
> notifier_call_chain
> register_framebuffer
> matroxfb_db_regit
> matroxfb_db_register
> matroxfb_xrtx2_probe
> matroxfb_register_driver
> matroxfb_crtc2_init
> do_initcalls
> init
> init
> kernel_thread_helper
> Kernel panic: attempted to kill init!
> 
> At this stage I only see the first framebuffer.  I don't know how far
> the second get, because userland has to run "matroxset" before it 
> gets routed to an actual screen.
> 
> The first framebuffer seems to work, it displays the penguins and
> the oops flawlessly.  Could it be something wrong in initializing the
> second fb?  Might a well-placed printk or something help?

I can help only with randomly-placed printk :)
First try this patch
--- ruby-CVS-20040430/drivers/video/console/fbcon.c     2004-04-30 09:45:06.000000000 +0300
+++ ruby-test/drivers/video/console/fbcon.c     2004-05-07 09:41:49.000000000 +0300
@@ -499,7 +499,7 @@ static const char *fbcon_startup(struct
        vc->vc_can_do_color = info->var.bits_per_pixel != 1;

        /* We trust the mode the driver supplies. */
-       if (!done && info->fbops->fb_set_par)
+       if (info->fbops->fb_set_par)
                info->fbops->fb_set_par(info);

        DPRINTK("mode:   %s\n", info->fix.id);


I add this !done because my ati-rage3d dies as secondary fb. May be matrox
does all vice-versa, because more sane is calling fb_set_par().

fbcon_strartup() already have printk
        DPRINTK("res:    %dx%d-%d\n", info->var.xres,
                info->var.yres,
                info->var.bits_per_pixel);
Seems You cannot see that on the screen. Oops push out important text.

Aivils

Re: ruby 2.6.3 died with "divide error", ruby 2.6.5 has the same problem

[Helge H. <hel...@ai...>]

On Fri, Feb 27, 2004 at 05:30:36PM +0000, James Simmons wrote:
> 
> I just looked at the code. The only way the could happen is if 
> info->var.bits_per_pixel equals zero. Need to check the initialization to 
> see if it sets this.
>  
Did you find anything? I tried ruby-2.6.5, and got almost
exactly the same oops again.  I get the penguins and a message
about switchin to framebuffer, then this.  Only the first
lines are different from the 2.6.3 case:

divide error: 9999 [#1]
EIP at cfb_imageblit+0x262/0x5c0
trace:
buffered_runqueue
fbcon_putc
gotoxay
clear_region
hide_softcursor
update_screen
vt_map_display
fbcon_add
cache_alloc_refill
fbcon_event_notify
notifier_call_chain
register_framebuffer
matroxfb_db_regit
matroxfb_db_register
matroxfb_xrtx2_probe
matroxfb_register_driver
matroxfb_crtc2_init
do_initcalls
init
init
kernel_thread_helper
Kernel panic: attempted to kill init!

At this stage I only see the first framebuffer.  I don't know how far
the second get, because userland has to run "matroxset" before it 
gets routed to an actual screen.

The first framebuffer seems to work, it displays the penguins and
the oops flawlessly.  Could it be something wrong in initializing the
second fb?  Might a well-placed printk or something help?

Helge Hafting

Rest of the 2.6.3 ruby report, with a very similiar trace.
> > Configuration: matrox G550 dualhead, everything compiled-in (fbcon & 
> > framebuffer) no modules, smp, no preempt.
> > 
> > (Some stuff omitted, but I have a digital photo of it
> > if it matters.)
> > 
> > The framebuffers came up fine, then I got this:
> > Console: switching to colour MATROX 160x64 vc:1-16
> > divide error: 0000 [#1]
> > CPU:1
> > EIP: 060:[<c02afccb>] Not tainted
> > EFLAGS: 00010246
> > EIP is at cfb_imageblit+0x27b/0x610
> > eax:00000020 ebx:00000000 ecx: 00000020 edx: 00000000
> > esi:00000000 edi:00000000 ebp: 00000000 esp: c13dfd84
> > ds:007b es:007b ss:0068
> > Process swapper (pid:1 ...
> > stack: ...
> > Call trace:
> > move_buf_aligned
> > accel_putc
> > fbcon_putc
> > hide_softcursor
> > update_screen
> > vt_map_display
> > fbcon_add
> > cache_alloc_refill
> > fbcon_event_notify
> > notifier_call_chain
> > register_framebuffer
> > matroxfb_db_regit
> > matroxfb_db_register
> > fbcon_add
> > matroxfb_crtc2_probe
> > matroxfb_register_driver
> > matroxfb_crtc2_init
> > do_initcalls
> > init_workqueues
> > init
> > init
> > kernel_thread_helper
> > Code: f7 f7 85 d2 0f 85 ab 01 00 00 85 ed 0f 85 a3 01 00 00 8b 54
> > <0>Kernel panic: Attempted to kill init!
> > <0>Rebooting in 300 seconds
> > 
> > I checked out ruby from cvs yesterday, and copied it into
> > a 2.6.3 source tree.
> > 
> > Helge Hafting
> > 
> > 
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > Linuxconsole-dev mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev
> > 

Re: Why does decvte.c exists?

[Aivils <ai...@un...>]

On Monday 03 May 2004 06:03, lin...@li... wrote:
> the question goes to mainly to James Simmons (jsi...@in...).
> 
> The chance of getting the multihead feature into mainline
> would be higher if the VTE was the same in the ruby tree.
> 
> Maintainability is better if the terminal emulator
> is in its separate source file but why didn't you used
> the original Linux implementation?

If anytime ruby-tree will be merged with Linus-tree, then ruby code will be
splited into small pieces. Rather decvte.c stay out of Linus-tree.

Ta accelerate merging anybody (master of business administration) should
manipulate with mind of Linus-tree maintainers. Merging is politic question
primarily and technical question secondary. Of course ready for use code
may help add this nice feature. Basic knowlege of programming may help.
Feel free to change standpoint of Linux community :)

I am new under Linux. I have not religious attitude towards TTY. I never
work on teletypewriter terminal and i work very limited time on VT100 or
similar terminals. Anyway i am (up to date) minicomputer fan.

Also clean solution of multiple local xf86 is possible right now.
/dev/eventXX drivers for xf86 are complete long time ago. Since SEP-2003
secondary keyboard may be unbounded from TTY via EVIOCGRAB
ioctl() . Current only keyboard's LEDs will not work. But developers may
complete EVIOCGRAB with less effort (2 lines).

Aivils Stoss

Why does decvte.c exists?

[Zoltan B. <zb...@fr...>]

Hi,

the question goes to mainly to James Simmons (jsi...@in...).

The chance of getting the multihead feature into mainline
would be higher if the VTE was the same in the ruby tree.

Maintainability is better if the terminal emulator
is in its separate source file but why didn't you used
the original Linux implementation?

Best regards,
Zolt=E1n B=F6sz=F6rm=E9nyi

Re: 2.6.5-ruby sofirq bug solved

[Zoltan B. <zb...@fr...>]

Aivils i'rta:
> Hi All!
>=20
> 	Thanks all unwearying testers, which help puzzle-headed developer!
> Solution is very simple:

Thanks. Would you please apply his one as well?
I had some whitespace fixes in drivers/pci/proc.c
and made the locking similar to linux-2.6.6-pre2.

Best regards,
Zolta'n B=F6sz=F6rm=E9nyi