linuxconsole-dev

Re: Keyboard generating events

[Andreas S. <an...@sc...>]

* Kjetil Kjernsmo (kj...@kj...) [031106 21:16]:
> My girlfriend just experienced that her keyboard and mouse locked up 
> hard after a few hours' use. It could have been something like that I 
> experienced too, but I did not investigate at that time. Locked hard 
> means that the secondary mouse generates no events, and the LEDs on the 
> keyboard can't be toggled. 

this is something that i experience, too.

i assumed it was my usb hardware which was slighly broken, so i
looked for ways to work around it. your usb setup doesnt seem to
be too stable either, perhaps it is the same problem? however,
here it is mostly the two mice and my keyboard dis- and reappearing.

the problem with reappearing is that the xserver does not reclaim
its hw automatically once it was gone. It does that only on
special events, e.g. when you switch from the console to X.

the Xserver in debian-experimental is able to regrab its hardware
with help of the input.agent from
http://people.debian.org/~warp/evdev/ , since it can react to
events received from a pipe, which the input.agent writes to.

the drawback with the event interface configuration is that it
seems to have problems with mouse keypresses (the pressbutton
event is generated at the same time as the releasebutton event,
making dragging and marking things under X impossible). I still
want to debug this so this is fully usable. the author of the x
event interface can not explain this and never saw this
phenomenon.

Keyboard generating events

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

Uhm,,,! 

Well, I'm apparently not quite there yet... 

My girlfriend just experienced that her keyboard and mouse locked up 
hard after a few hours' use. It could have been something like that I 
experienced too, but I did not investigate at that time. Locked hard 
means that the secondary mouse generates no events, and the LEDs on the 
keyboard can't be toggled. 

Now, I find that /dev/input/event2 is spewing out events persistently, 
even though no keys are hit. Well, it could be something else than the 
secondary keyboard, but it fits rather well with being this keyboard, 
right? Output from /proc/bus/input/devices:

I: Bus=0003 Vendor=0d3d Product=0001 Version=0001
N: Name="Tangtop Generic USBPS2"
P: Phys=usb-00:04.2-2/input0
H: Handlers=kbd event2
B: EV=120003
B: KEY=10000 7f ffe00000 7ff ffbeffdf ffffffff ffffffff fffffffe
B: LED=1f

On one hand, I've never seen this behaviour when using the keyboard on 
other ports, so perhaps it could be the driver, but OTOH, it is strange 
if the driver would generate keyboard events.... The scroll lock button 
sits in a somewhat awkward position, perhaps that could do it...? But 
then, I can't turn it off...

Any ideas? 

Also, is it some way I can reset the keyboard without rebooting the box?

Best,

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: Mouse and keyboard troubles with USB -> PS/2 adapter

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

On Thursday 06 November 2003 08:56, Aivils Stoss wrote:
> >Yup, the funny thing now is that my non-bruby 2.4.22 kernel detects
> > both the mouse and keyboad on this device:
> >input: USB HID v1.00 Keyboard [Tangtop Generic USBPS2] on usb1:2.0
> >input: USB HID v1.00 Mouse [Tangtop Generic USBPS2] on usb1:2.1
> >whereas the bruby kernel only detects the keyboard.
>
> Thank You for notifying! USB HID is out of my scopespace because of
> optimization of development. Unknown "bcollins" goodman already port
> back USB HID from 2.5.72 to 2.4.22, but this one escape from my
> attention.

OK, thanks for tracking it down!


> Now ready:
> http://startx.times.lv/bruby-2.4.22-20031105.diff.bz2
>
> fixed USB HID.
>
> You can report:
> Works Tangtop device?

Yihaaaaaaaa! It does! Thanks a lot, and thanks to bcollins! :-) 

> Show /proc/bus/input/devices each Tangtop unit?

Yes!

Full logs at 
http://dev.kjernsmo.net/tmp/multi-user-logs-working1/

> Show /proc/bus/input/devices different Phys for each Tangtop unit?

Yes!

P: Phys=usb-00:04.2-2/input0
P: Phys=usb-00:04.2-2/input1


> Works 2 PS/2 mice via Tangtop?
> Works 2 PS/2 keyboards via Tangtop?

No and no. BUT, it may be possible to tweak it. 

Basically, when I connect both mice or keyboards to the Tangtop, dmesg 
says things like:
keyboard.c [Tangtop Generic USBPS2] vc:1-16
input: USB HID v1.00 Keyboard [Tangtop Generic USBPS2] on usb-00:04.2-2
usb.c: hid driver claimed interface dfe5a300
keyboard.c [Tangtop Generic USBPS2] vc:17-17
input: USB HID v1.00 Mouse [Tangtop Generic USBPS2] on usb-00:04.2-2
usb.c: hid driver claimed interface dfe5a318

This is when I connected both keyboards to the Tangtop, logs at 
http://dev.kjernsmo.net/tmp/multi-user-logs-keybdtt1/

Here, the keyboard that is called "Mouse" is connected to the green plug 
on the tangtop. Conversely, when I connected both mice, one of them was 
called "Keyboard" and was connected to the purple plug. Indeed, the one 
that was connected to the "wrong" plug didn't work for me.

However, it isn't necessarily hopeless, because I saw in /proc/bus/
console/*/* that there were two keyboards detected, something that 
looks above that could be the case too. So I guess tweaking it could 
make it work without any programming. 

Unfortunately, the keyboard froze hard while I was exploring that, for 
some unknown reason, so the only file I caught was the usb/devices, 
included on my website. 


My preferred config works now, however, so I am myself very happy! I 
have just a couple of very minor things left (such as connecting an 
extension cable). Thanks to all who helped! 

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

Understanding "normal" and "paranormal" xf86 starting

[Aivils S. <Aiv...@un...>]

>you are misunderstanding "normal" multihead.  what it means is that you
>have two independant screens (you can run different apps, WM's, etc on
>them, but you can't drag windows between them) with a shared set of
>input devices.  xinerama binds the two independant screens into one
>large, logical screen.  there is no way, without patches, to have
>separate independant screens with their own independant input devices.
>
>Alex
>
>--------------------------------------------------------
>
>Hi!
>Thanx for the answer.
>I understand from you that this only be possible with patched kernel
>and xfree86.
>The text from Tomas Winischhofer site i was thinking about with mode
>"Normal" was the \
>following.
>
>"XFree86 supports two different dual-head modes: "Normal", where you
>get two \
>independent screens (and two X sessions), and "Xinerama" where these
>two screens are \
>virtually one. Please see the documentation on Xfree86.org for more
>information..."
>
>The Normal mode is exactly what i'm looking for if it's possible.
>What is unsure is if i'm able to start different window managers in the
>independent \
>screens and if can force the keyboard and mouse to only operate on one
>of them.
>
>I've already got a pci graphics card on the shelf so maby i'll try to
>start patching \
>things up trying it the hard way.
>
>Fredrik

My comments.

To start two separate screens for _one_ user no needs for kernel or
xf86 pathces!
Instead use standard xf86 where XF86Config file contains "ServerLayout"
with two screens. Do not use xinerama.
To start programs on first screen use parameter -display
xterm -display :0.0
To start programs on second screen
xterm -display :0.1

set up Your xf86 starting scripts according this.

That all.
Please read
http://www.winischhofer.net/linuxsisvga.shtml#mergedfbmode

Aivils Stoss

Re: Mouse and keyboard troubles with USB -> PS/2 adapter

[Aivils S. <Aiv...@un...>]

>Yup, the funny thing now is that my non-bruby 2.4.22 kernel detects both
>the mouse and keyboad on this device:
>input: USB HID v1.00 Keyboard [Tangtop Generic USBPS2] on usb1:2.0
>input: USB HID v1.00 Mouse [Tangtop Generic USBPS2] on usb1:2.1
>whereas the bruby kernel only detects the keyboard.

Thank You for notifying! USB HID is out of my scopespace because of
optimization of development. Unknown "bcollins" goodman already port back
USB HID from 2.5.72 to 2.4.22, but this one escape from my attention.

Now ready:
http://startx.times.lv/bruby-2.4.22-20031105.diff.bz2

fixed USB HID.

You can report:
Works Tangtop device?
Show /proc/bus/input/devices each Tangtop unit?
Show /proc/bus/input/devices different Phys for each Tangtop unit?
Works 2 PS/2 mice via Tangtop?
Works 2 PS/2 keyboards via Tangtop?

Aivils Stoss

Re: 2.6.0-test6 ruby success with matrox G550, and some questions

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

I tried booting ruby-2.6-test9 with the single console patch
and framebuffer console again.

ruby without the patch hangs as soon as it switch away
from vga.

runy with the patch gets further.  The framebuffer shows
only garbage, similar to ruby with framebuffer but without
fbcon.  (Plain 2.6.0-test9 shows text on the framebuffer
console.) So there are more problems than just the
number of framebuffers on a G550.

I can't see printk's, but I see from disk lights that
the scsi bus does the usual lengthy initialization.
The kernel hangs shortly after that.  I know it hangs
because the keyboards stop reacting to numlock/capslock.
(No LED reaction, and no sysrq either.)

Helge Hafting

Fwd: decoded oopses (Re: Any more documentation on 2.6.0 ?)

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

--- Weitergeleitete Nachricht / Forwarded Message ---
Date: Wed, 5 Nov 2003 17:29:43 +0100 (MET)
From: "Svetoslav Slavtchev" <sv...@gm...>
To: Aiv...@un...
Subject: decoded oopses (Re: Any more documentation on 2.6.0 ?)

> 
> > modprobe matroxfb - register both heads.
> > modprobe fbcon
> > 
> > fbcon must be last. nnnfb in any order.
> > I have interest about dmesg form serial console on matrox
> > G550 (single,multi fbcon). After modprobe matroxfb should nothing
> > happen. After modprobe fbcon - die. i need oops report.
> 
> loading fbcon -> OOPSES.fbcon.txt
> + typing         -> OOPSES.fbcon1.txt
> 
> 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! +++

-- 
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! +++

Fwd: fbcon modular + matroxfb (Re: Any more documentation on 2.6.0 ?)

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

--- Weitergeleitete Nachricht / Forwarded Message ---
Date: Wed, 5 Nov 2003 17:17:25 +0100 (MET)
From: "Svetoslav Slavtchev" <sv...@gm...>
To: Aiv...@un...
Subject: fbcon modular + matroxfb (Re: Any more documentation on 2.6.0 ?)

> Hi Aivils,
> 
> first mail with what i captured over serial console,
> decoded wil folow in short
> the PC is still up, so ...
> 
> > 
> > >Aivils, i got the same lock up with G550
> > >using ruby single && multi fb console
> > >
> > >and with Geforce4 + radeon 7500
> > >i'm sure the problem is in the Geforce fb driver
> > >and that it is initialized before the radeon (radeon is my primary
> head)
> > >
> > >do you think i can get some debug info if i try to swap the order
> > >in fbmem.c or all fb's are initialized at the same time and changing
> the
> > >order
> > 
> > This kernel - single thread, mostly. Init in strong fbmem.c order.
> > 
> > >can not help( i think it's the second, but let's ask :-) )
> > 
> > since test9 fbcon is modular. modular fbcon works badly.
> > modprobe radeonfb
> > modprobe rivafb
> > modprobe fbcon
> 
> rivafb is brocken for me,
> and when it tries to initialize it it freezes
> (rivafb reports 2Mb memmory and the card has 64Mb)
> 
> > or
> > modprobe matroxfb - register both heads.
> > modprobe fbcon
> > 
> > fbcon must be last. nnnfb in any order.
> > I have interest about dmesg form serial console on matrox
> > G550 (single,multi fbcon). After modprobe matroxfb should nothing
> > happen. After modprobe fbcon - die. i need oops report.
> 
> that's what i tried 
> load matroxfb_base - no problem, fb0 registered
> load matroxfb_crtc2 - noproblem , fb1 registered
> 
> loading fbcon -> modprobe segfault + oopses
> 
> typing later on, more oopses
> 
> it mentions devide error ?
> 
> Ok, 
> enough talking :-)
> 
> let's attach
> 
> 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! +++

-- 
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! +++

Re: 2.6.0-test6 ruby success with matrox G550, and some questions

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

Svetoslav Slavtchev wrote:
> Hi,
> 
> i think i almost got it :-)
> 
> almost, cause my main monitor died in the weekend 
> and i used a switch, and the accelerated head gives
> pretty strange output 
> 
> Helge please correct me if i'm wrong somewhere,
> or if smth differs from your setup
>  
Some tips:
The framebuffer driver is supposed to start the second head
in 640x480, but the accelerated driver seems to set it to
1280x1024 while setting the first head to that resolution.
Quitting X seems to reset this as "old" settings are restored.
Try using the same resolution on both heads.
Also, the framebuffer drivers claim to support only 16 or 32
bit color on the second head.  So don't bother trying
8 or 24 bit.
 
OpenGL seems to work only with 16bit, so that's what I use.
16-bit color and the same resolution on both screens.
I happen to have two identical monitors, others should
set up the accelerated driver with timings that both
monitors can handle.  I believe the second head uses 
the same timing as the first.  Other setups may be
possible - this is the "easy" one.

>>>How did you got it running?
>>
>>I used this machine single-headed for a long time.
>>All I did was to create a second config file (xf86config-4) 
>>for fbdev, and use matroxset-0.3 from Petrs site to
>>set up which framebuffer connects to what output.
>>
>>I can set up a guest account on the machine, if you
>>want to look more at the setup.  
>>
>>
>>>i'm tring with no success quite a long time.
>>
>>>which version of XFree ?
>>
>>debian packaged xserver-xfree86-dri-trunk from
>>http://people.debian.org/~daenzer/dri-trunk-sid/
>>because I want accelerated opengl on at least one screen.
>  
> that was my first problem, i used the matrox drivers
> which obviously doesn't play nice with linux-2.6
> i got all kind of agp errors and tring to activate "UseFBDev" 
> caused lock ups
> switching to the plain mga drivers fixed the problem,
> but also the distored screen :( i'll have to play more with it
> 
The matrox drivers (beta 3) were fine in single-screen setup,
I haven't tried them with two screens.  I gave up on them
because the dri-trunk driver was better at doing opengl.
If agp cause trouble, consider forcing agp 1x until
everything else works.  And turn off any kind of
overclocking.  (Experiment with such things after
your setup works...)
I use agp 2x, as my old motherboard (bx) isn't supposed
to support more than that.  I can specify agp4x, but then
I have to change the bios from agp=1/1 cpuclk to
agp=2/3 cpucl, where the cpu clock is 100MHz.
This don't buy anything though, so I use the supported agp 2x
and use agp=1/1 cpuclk.

Just write down whatever bios settings you have, and test
if some really slow settings work better.  
> 
>>I got xdm working too.
>>>From my /etc/X11/xdm/Xservers:
>>
>>:0 local /usr/X11R6/bin/X :0 vt7  -deferglyphs 16 -nolisten tcp
>>:1 local /usr/X11R6/bin/X :1 vt17 -deferglyphs 16 -nolisten tcp
>>-xf86config xf86config-4
>>
>>The first server use the standard XF86Config-4
>>This runs the servers, but I had to modify /etc/X11/xdm/Xsetup
>>too to actually make the second framebuffer visible.  Whenever the
>>accelerated server starts, it configures the G550 to show the same
>>screen on both outputs.  Fortunately, xdm then runs the Xsetup script,
>>so that's where I put the following lines:
>>/usr/local/bin/matroxset -f /dev/fb/1 -m 0
>>/usr/local/bin/matroxset -f /dev/fb/0 -m 2
>>/usr/local/bin/matroxset -f /dev/fb/1 -m 1
> 
> 
> that's basicly the script swapped from the matroset tarball, correct ?
Yes, except that I was surprised that the first screen was the
second output.  It was easy enough to find out though.
The xfree driver for g550 really ought to have options for
what output port to use.  (first, second, both.. use the same numbers
as for matroxset.) I currently have to re-run those lines
whenever X changes resolution.  I.e. when my girlfriend starts
tuxracer on the accelerated screen.  Any resolution change
shows /dev/fb/0 on both screeens, but only the correct one
changes resolution.  Looks weird, and I have to
run matroxset blind to get my own screen back.
> 
>>1. line: disconnect /dev/fb/1 from whatever output it uses (in case it was
>>using&blocking  output 2)
>>2. line: connect /dev/fb/0 to output 2, which is the vga connector
>>3. line: connect /dev/fb/1 to output 1, which is the DVI connector with a
>>VGA converter.
>>The output numbers are really bits, so connecting a framebuffer to output
>>3 shows
>>it on both screens.  There's also a third output, bitnumber 4, but there
>>is no such plug.
>>Perhaps the video out?  "matroxset" seems undocumented.
>>
>>This setup means both servers get a screen.  A minor inconvenience is the
>>way
>>both screens blink whenever one of the xdm's are reset. 
>>
>>
>>>which matrox drivers?
>>
>>I believe I'm using the mga_drv.o (and fbdev_drv.o) that comes with
>>xserver-xfree86-dri-trunk.
>>>From /var/log/XFree86.0.log:
>>(II) LoadModule: "mga"
>>(II) Loading /usr/X11R6/lib/modules-dri-trunk/drivers/mga_drv.o
>>(II) Module mga: vendor="The XFree86 Project"
>>        compiled for 4.3.99.12, module version = 1.1.1
>>        Module class: XFree86 Video Driver
>>        ABI class: XFree86 Video Driver, version 0.7
>>
>>>From /var/log/XFree86.1.log:
>>(II) LoadModule: "fbdev"
>>(II) Loading /usr/X11R6/lib/modules-dri-trunk/drivers/fbdev_drv.o
>>(II) Module fbdev: vendor="The XFree86 Project"
>>        compiled for 4.3.0, module version = 0.1.0
>>        ABI class: XFree86 Video Driver, version 0.6
>>
>>>From /etc/X11/XF86Config-4  (accelerated)
>>Section "Device"
>>        Identifier      "Matrox G550"
>>        Driver          "mga"
>>        BusID           "PCI:01:00:0"
>>        Option          "UseFBDev"              "true"
> 
> 
> without "UseFBDev here i get the "mga" screen of both fb's
> and if i run matroxset after "mga" is started ," mga" goes blank
> or distored, if i start the "fb" i get lock up
> 
> with "UseFBDev activated everything works,
> running matroxset doesn't affect "mga"
> (there might be short blanking but i couldn't see as
> i used the switch with only one monitor )
> starting "fb" works OK  
> 
It is only the unaccelerated screen that blinks for me,
because that is the only one that is turned off for a moment.
The accelerated screen is on all the time with that script,
assuming it was on from the beginning, so no blinking there.

> 
>>        Option          "HWcursor" "off"   #avoid cursor corruption
>>        Option          "AGPMode" "2"      #Faster 3D...
>>        Option          "DRIReinit"        #Possibly several servers with
>>DRI
>>EndSection
>>
>>The last option because someone on the net got DRI working on two
>>matrox cards, (PCI+AGP) but only one at a time, unfortunately.
>>
>>>From /etc/X11/xf86config-4 (fbdev)
>>Section "Device"
>>        Identifier      "Matrox G550"
>>        Driver          "fbdev"
>>#       BusID           "PCI:01:00:1"
>>        Option          "UseFBDev"              "true"
>>        Option          "fbdev"                 "/dev/fb/1"
>>
>>        Option          "HWcursor" "off"   #avoid cursor corruption       
>>
>>EndSection
>>
>>Using BusID here doesn't work.  The two files are otherwise
>>identical except that they specify different mice.
> 
> 
> 
> So, in a recap :-)
> (for the howto )
> 
> 1.)
> don't use matrox's closed source driver (mga_hall_drv)
> it doesn't support linux-2.6 && the new FB API
> do use the original XFree driver
> 
> 2.)
> do activate 
> Option "useFBDev" "true" 
> for the accelerated head 
> (? does this option affect "fbdev" unaccelerated head ? )
> 
> 3.)
> get matroxset, build it and install it
> install also the swapped script from the tarball
> 
> 4.)
> convince xdm/kdm/gdm to run swapped  at every X server
> start/restart
> for xdm/kdm Xsetup
> ?for gdm ? wrapper? is there smth like Xsetup used by gdm ?
>  
This seems fine.

I don't know what to do with gdm/kdm, other than
read the docs and see if they have a similiar file that
runs as root after X server initialization before presenting
the login screen.  It has to be at that moment,
after the accelerated server initialization that
scrambles the output setup, and before the
login screen or you won't see it!

xdm seems to work fine for this purpose though.
I can restart the fbdev X server anythime without affecting
the accelerated one.  When running matroxset "blind" fails I
simply press ctrl+alt+backspace, killing the fbdev server
and then xdm restarts it and runs the script for me.
I haven't tried this with the accelerated server yet.  It will
at least blink the wrong screen as it briefly take over
both outputs.

Setting up some hotkey for the matroxset script is
highly advisable - I haven't bothered figuring it out
yet though.  This may depend on the window manager used.

The framebuffer driver works surprisingly well.  Browsing,
word processing and 2D games performs fine even with
this unaccelerated driver on 500MHz dual cpus.  It is still
fine with tuxracer running on the other screen using 100%
of one cpu. 

Helge Hafting

Re: Mouse and keyboard troubles with USB -> PS/2 adapter

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

Hi!

I'm following up on myself, I've done a few small things.

Mainly, I compiled the USB stuff, UHCI, HID etc into the kernel, rather 
as modules. 

On Monday 03 November 2003 15:27, Kjetil Kjernsmo wrote:

> The current status is (on the surface) that X starts OK on both
> screens, but only the main PS/2 keyboard works. There's no output
> from the devices in /dev/input/ except event1, which is the PS/2
> keyboard. The primary mouse (on the PS/2 port) is dead, not even
> giving output to /dev/psaux 

Now, the primary mouse works and it sends output to both 
/dev/input/mouse0 and /dev/psaux. So it actually looks like it helped to 
not use modules for this... 


> and the secondary keyboard and mouse are also quite dead...

They still are.

> A new set of logs and config files (aka "More about my system than
> would be good for anybody's sanity) is to be found at
> http://dev.kjernsmo.net/tmp/multi-user-logs3/

Now supplemented with something new, see below.

> There are a couple of lines in the bruby-kernel dmesg that looks
> somewhat suspecious...:
> usb-uhci.c: interrupt, status 2, frame# 658
> hid-core.c: ctrl urb status -75 received

Googling and reading source (!), I find the following info:
The error is apparently this:
-EOVERFLOW		The amount of data returned by the endpoint was
			greater than either the max packet size of the
			endpoint or the remaining buffer size.  "Babble".

The question is then who does it, the mouse or the keyboard? The 
keyboard seems to be initialized allready, so perhaps it is the mouse? 
Is HID then giving up breath and giving up on both the keyboard and the 
mouse? 

I figured, since I'm seeing this in the backstreet ruby kernel, and not 
in the vanilla (that is, debian-patched) kernel, am I actually getting 
bitten by a bug....? Well, I went back and enabled CONFIG_USB_DEBUG=y
(and I have CONFIG_INPUT_EVBUG=m, but I haven't enabled the general 
kernel debugging). 

I've including this evening's kern.log in 
http://dev.kjernsmo.net/tmp/multi-user-logs3/kern.log
and the new config is there too, but note that the rest is from the 
previous boot.... 

These are the messages that looks relevant to USB/HID problems.....: 

Nov  3 20:27:09 owl kernel: usb.c: hub driver claimed interface dfe9fe40
Nov  3 20:27:09 owl kernel: host/usb-uhci.c: v1.275:USB Universal Host 
Controller Interface driver
Nov  3 20:27:09 owl kernel: usb.c: registered new driver hiddev
Nov  3 20:27:09 owl kernel: usb.c: registered new driver hid
Nov  3 20:27:09 owl kernel: hid-core.c: v1.31:USB HID core driver
Nov  3 20:27:09 owl kernel: mice: PS/2 mouse device common for all mice
Nov  3 20:27:09 owl kernel: input: ImExPS/2 Logitech Explorer Mouse on 
isa0060/serio1
Nov  3 20:27:09 owl kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Nov  3 20:27:09 owl kernel: keyboard.c AT Set 2 keyboard vc:1-16
Nov  3 20:27:09 owl kernel: input: AT Set 2 keyboard on isa0060/serio0
Nov  3 20:27:09 owl kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Nov  3 20:27:09 owl kernel: hub.c: port 2, portstatus 301, change 2, 1.5 
Mb/s
Nov  3 20:27:09 owl kernel: hub.c: port 2, portstatus 301, change 2, 1.5 
Mb/s
Nov  3 20:27:09 owl last message repeated 2 times
Nov  3 20:27:09 owl kernel: hub.c: port 2, portstatus 303, change 0, 1.5 
Mb/s
Nov  3 20:27:09 owl kernel: hub.c: new USB device 00:04.2-2, assigned 
address 2
Nov  3 20:27:09 owl kernel: usb.c: kmalloc IF dfe5a3c0, numif 2
Nov  3 20:27:09 owl kernel: usb.c: skipped 1 class/vendor specific 
interface descriptors
Nov  3 20:27:09 owl kernel: usb.c: skipped 1 class/vendor specific 
interface descriptors
Nov  3 20:27:09 owl kernel: usb.c: new device strings: Mfr=1, Product=2, 
SerialNumber=0
Nov  3 20:27:09 owl kernel: usb.c: USB device number 2 default language 
ID 0x409
Nov  3 20:27:09 owl kernel: Manufacturer: Tangtop
Nov  3 20:27:09 owl kernel: Product: Generic USBPS2
Nov  3 20:27:09 owl kernel: keyboard.c Tangtop Generic USBPS2 vc:17-17
Nov  3 20:27:09 owl kernel: input: USB HID v1.00 Keyboard [Tangtop 
Generic USBPS2] on usb-00:04.2-2
Nov  3 20:27:09 owl kernel: usb.c: hid driver claimed interface dfe5a3c0
Nov  3 20:27:09 owl kernel: host/usb-uhci.c: interrupt, status 2, frame# 
827
Nov  3 20:27:09 owl kernel: hid-core.c: ctrl urb status -75 received

If I am to go waaaaay beyond what I should put my nose into, the warning 
is something about size, and that's kmalloc too, so perhaps kmalloc IF 
dfe5a3c0, numif 2 has something to do with it, since that's the 
problematic interface... Or perhaps I'm just doing what the docs I 
pasted above says, babbling... :-) 

Just poking... :-) 

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: 2.6.0-test6 ruby success with matrox G550, and some questions

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

Hi,

i think i almost got it :-)

almost, cause my main monitor died in the weekend 
and i used a switch, and the accelerated head gives
pretty strange output 

Helge please correct me if i'm wrong somewhere,
or if smth differs from your setup
 
> > How did you got it running?
> I used this machine single-headed for a long time.
> All I did was to create a second config file (xf86config-4) 
> for fbdev, and use matroxset-0.3 from Petrs site to
> set up which framebuffer connects to what output.
> 
> I can set up a guest account on the machine, if you
> want to look more at the setup.  
> 
> > i'm tring with no success quite a long time.
> 
> > 
> > which version of XFree ?
> debian packaged xserver-xfree86-dri-trunk from
> http://people.debian.org/~daenzer/dri-trunk-sid/
> because I want accelerated opengl on at least one screen.

that was my first problem, i used the matrox drivers
which obviously doesn't play nice with linux-2.6
i got all kind of agp errors and tring to activate "UseFBDev" 
caused lock ups
switching to the plain mga drivers fixed the problem,
but also the distored screen :( i'll have to play more with it


> I got xdm working too.
> >From my /etc/X11/xdm/Xservers:
> 
> :0 local /usr/X11R6/bin/X :0 vt7  -deferglyphs 16 -nolisten tcp
> :1 local /usr/X11R6/bin/X :1 vt17 -deferglyphs 16 -nolisten tcp
> -xf86config xf86config-4
> 
> The first server use the standard XF86Config-4
> This runs the servers, but I had to modify /etc/X11/xdm/Xsetup
> too to actually make the second framebuffer visible.  Whenever the
> accelerated server starts, it configures the G550 to show the same
> screen on both outputs.  Fortunately, xdm then runs the Xsetup script,
> so that's where I put the following lines:
> /usr/local/bin/matroxset -f /dev/fb/1 -m 0
> /usr/local/bin/matroxset -f /dev/fb/0 -m 2
> /usr/local/bin/matroxset -f /dev/fb/1 -m 1

that's basicly the script swapped from the matroset tarball, correct ?

> 1. line: disconnect /dev/fb/1 from whatever output it uses (in case it was
> using&blocking  output 2)
> 2. line: connect /dev/fb/0 to output 2, which is the vga connector
> 3. line: connect /dev/fb/1 to output 1, which is the DVI connector with a
> VGA converter.
> The output numbers are really bits, so connecting a framebuffer to output
> 3 shows
> it on both screens.  There's also a third output, bitnumber 4, but there
> is no such plug.
> Perhaps the video out?  "matroxset" seems undocumented.
> 
> This setup means both servers get a screen.  A minor inconvenience is the
> way
> both screens blink whenever one of the xdm's are reset. 
> 
> > which matrox drivers?
> I believe I'm using the mga_drv.o (and fbdev_drv.o) that comes with
> xserver-xfree86-dri-trunk.
> >From /var/log/XFree86.0.log:
> (II) LoadModule: "mga"
> (II) Loading /usr/X11R6/lib/modules-dri-trunk/drivers/mga_drv.o
> (II) Module mga: vendor="The XFree86 Project"
>         compiled for 4.3.99.12, module version = 1.1.1
>         Module class: XFree86 Video Driver
>         ABI class: XFree86 Video Driver, version 0.7
> 
> >From /var/log/XFree86.1.log:
> (II) LoadModule: "fbdev"
> (II) Loading /usr/X11R6/lib/modules-dri-trunk/drivers/fbdev_drv.o
> (II) Module fbdev: vendor="The XFree86 Project"
>         compiled for 4.3.0, module version = 0.1.0
>         ABI class: XFree86 Video Driver, version 0.6
> 
> >From /etc/X11/XF86Config-4  (accelerated)
> Section "Device"
>         Identifier      "Matrox G550"
>         Driver          "mga"
>         BusID           "PCI:01:00:0"
>         Option          "UseFBDev"              "true"

without "UseFBDev here i get the "mga" screen of both fb's
and if i run matroxset after "mga" is started ," mga" goes blank
or distored, if i start the "fb" i get lock up

with "UseFBDev activated everything works,
running matroxset doesn't affect "mga"
(there might be short blanking but i couldn't see as
i used the switch with only one monitor )
starting "fb" works OK  

>         Option          "HWcursor" "off"   #avoid cursor corruption
>         Option          "AGPMode" "2"      #Faster 3D...
>         Option          "DRIReinit"        #Possibly several servers with
> DRI
> EndSection
> 
> The last option because someone on the net got DRI working on two
> matrox cards, (PCI+AGP) but only one at a time, unfortunately.
> 
> >From /etc/X11/xf86config-4 (fbdev)
> Section "Device"
>         Identifier      "Matrox G550"
>         Driver          "fbdev"
> #       BusID           "PCI:01:00:1"
>         Option          "UseFBDev"              "true"
>         Option          "fbdev"                 "/dev/fb/1"
> 
>         Option          "HWcursor" "off"   #avoid cursor corruption       
> 
> EndSection
> 
> Using BusID here doesn't work.  The two files are otherwise
> identical except that they specify different mice.


So, in a recap :-)
(for the howto )

1.)
don't use matrox's closed source driver (mga_hall_drv)
it doesn't support linux-2.6 && the new FB API
do use the original XFree driver

2.)
do activate 
Option "useFBDev" "true" 
for the accelerated head 
(? does this option affect "fbdev" unaccelerated head ? )

3.)
get matroxset, build it and install it
install also the swapped script from the tarball

4.)
convince xdm/kdm/gdm to run swapped  at every X server
start/restart
for xdm/kdm Xsetup
?for gdm ? wrapper? is there smth like Xsetup used by gdm ?
 

best,

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! +++

Re: Mouse and keyboard troubles with USB -> PS/2 adapter

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

Hi!

Svetoslav has been helping me a lot off-list, but touched by your 
attention, I guess I can bring it back on... :-)

On Monday 03 November 2003 10:53, Aivils Stoss wrote:
> >usb_control/bulk_msg: timeout
>
> google show similar results for "Tangtop Generic USBPS2" under Linux.
> hid-core.c, hid-input.c, which is important, is quite old
> FEB/AUG-2002. USB input derived from Johan Deneux , which go away
> from USB backport since SEP-2002 :-(
>
> >Scary, huh?
>
> Very.

I've upgraded to 2.4.22, Marcelo's tree, and patched with the latest 
bruby patch now, and I haven't seen this message since. (The patch 
didn't apply cleanly to the debian kernel-source, but nevermind).

I guess this fixed that problem.

The current status is (on the surface) that X starts OK on both screens, 
but only the main PS/2 keyboard works. There's no output from the 
devices in /dev/input/ except event1, which is the PS/2 keyboard. The 
primary mouse (on the PS/2 port) is dead, not even giving output to 
/dev/psaux (and haven't for a few different configurations...), and the 
secondary keyboard and mouse are also quite dead...

A new set of logs and config files (aka "More about my system than would 
be good for anybody's sanity) is to be found at 
http://dev.kjernsmo.net/tmp/multi-user-logs3/

> > keyboard.c Tangtop Generic USBPS2 VT1 first VC 8
>
> Correct. dmesg is helpful.

Yup, the funny thing now is that my non-bruby 2.4.22 kernel detects both 
the mouse and keyboad on this device:
input: USB HID v1.00 Keyboard [Tangtop Generic USBPS2] on usb1:2.0
input: USB HID v1.00 Mouse [Tangtop Generic USBPS2] on usb1:2.1
whereas the bruby kernel only detects the keyboard. 

That is, in dmesg I see
keyboard.c Tangtop Generic USBPS2 vc:17-17
input: USB HID v1.00 Keyboard [Tangtop Generic USBPS2] on usb-00:04.2-2

(so, I'm now starting the second X-server with vt17, OK?)

One of the recent things I've done, following Svetoslav's advice, is to 
add
above hid usbcore
to modules.conf (or rather /etc/modutils/local, that's how I understand 
the Debian Way... :-) ).  I was for a while seriously confused, as 
KEYBDEV was not available in the kernel, but HID wanted it... :-)

Allthough the above looks like the keyboard it least should be loaded, 
there is little to be seen in 
http://dev.kjernsmo.net/tmp/multi-user-logs3/proc.bus.usb.devices
Mmmm, I much prefer the way it looks in /proc/bus/usb/devices of my 
currently running non-bruby kernel:
P:  Vendor=0d3d ProdID=0001 Rev= 0.01
S:  Manufacturer=Tangtop
S:  Product=Generic USBPS2
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=hid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=hid
E:  Ad=82(I) Atr=03(Int.) MxPS=   5 Ivl=10ms

Currently, /dev/input/mouse0 is my USB mouse with the non-bruby-kernel. 

There are a couple of lines in the bruby-kernel dmesg that looks 
somewhat suspecious...:
usb-uhci.c: interrupt, status 2, frame# 658
hid-core.c: ctrl urb status -75 received
I can't see that in my non-bruby kernel dmesg (ok, since I'm talking so 
much about it, I've dumped that too on my website)... 

I think I'm getting close now... :-) Help for the final bit would be 
greatly appreciated!

Best,

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: Mouse and keyboard troubles with USB -> PS/2 adapter (Kjetil Kjernsmo)

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

Hi Aivils,

> >I've been slightly confused about the connection between the numbering
> >on virtual terminals, tty's, and how they relate to the number I put at
> >the end of the line in the Xserver file... vt[n] you know... :-) So,
> >you can see in
> >http://dev.kjernsmo.net/tmp/multi-user-logs1/XFree86.1.log
> >that I've used vt16. I've used vt9 and vt8 too, without success. I have
> >vt8 now, as from my current understanding, it should be correct, since
> >dmesg says:
> > keyboard.c Tangtop Generic USBPS2 VT1 first VC 8
> 
> Correct. dmesg is helpful.
> 
> >There is a weird thing that may have some relevance, that happens if I
> >go cat /proc/bus/usb/devices... It takes a long time to get anything,
> >and at the end of http://dev.kjernsmo.net/tmp/multi-user-logs1/dmesg
> >you see lines like:
> >usb_control/bulk_msg: timeout
> 
> google show similar results for "Tangtop Generic USBPS2" under Linux.
> hid-core.c, hid-input.c, which is important, is quite old FEB/AUG-2002.
> USB input derived from Johan Deneux , which go away from USB backport
> since SEP-2002 :-(
> 
> >Scary, huh?
> 
> Very.
 
sorry for not keeping you informed, 
(i hit "reply" && not" reply all" some days ago,
and we continued the discussion privately :( )

it seems like a usb/acpi problems coming from
too old kernel, which were fixed by updating to 2.4.22
i'm waiting for his conformation that it works under bruby,
he tested it under vanilla-2.4.22 & everything was OK

best,

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! +++

Re:problem with x authorization

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

> When I start my 2nd X, I ought to be able to run KDE
> or Gnome to have a second user on the machine. But, I
> get error messages that the X server isn't allowing my
> client(KDE) to connnect, thus my 2nd X server is
> useless.
> 
> How do I fix this?

please check xfree list for similar errors and this
 http://linuxgazette.net/issue53/lg_answer53.html#tag/13

you might also try adding "-ac" to the XFree parameters list in Xservers/
gdm.conf

> Also, I'm expirementing with virtual displays using
> the 'Virtual' keyword in my X config to make my screen
> larger. Do you know how to control where the viewport
> on the screen will initially appear when X starts?

sorry, but no idea 

best,

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! +++

Re: Mouse and keyboard troubles with USB -> PS/2 adapter (Kjetil Kjernsmo)

[Aivils S. <Aiv...@un...>]

>I've been slightly confused about the connection between the numbering
>on virtual terminals, tty's, and how they relate to the number I put at
>the end of the line in the Xserver file... vt[n] you know... :-) So,
>you can see in
>http://dev.kjernsmo.net/tmp/multi-user-logs1/XFree86.1.log
>that I've used vt16. I've used vt9 and vt8 too, without success. I have
>vt8 now, as from my current understanding, it should be correct, since
>dmesg says:
> keyboard.c Tangtop Generic USBPS2 VT1 first VC 8

Correct. dmesg is helpful.

>There is a weird thing that may have some relevance, that happens if I
>go cat /proc/bus/usb/devices... It takes a long time to get anything,
>and at the end of http://dev.kjernsmo.net/tmp/multi-user-logs1/dmesg
>you see lines like:
>usb_control/bulk_msg: timeout

google show similar results for "Tangtop Generic USBPS2" under Linux.
hid-core.c, hid-input.c, which is important, is quite old FEB/AUG-2002.
USB input derived from Johan Deneux , which go away from USB backport
since SEP-2002 :-(

>Scary, huh?

Very.

Aivils

Mouse and keyboard troubles with USB -> PS/2 adapter

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

Hello again!

Well, I'm not quite finished yet... :-) 

Yesterday, I got out and bought the USB -> PS/2 adapter (labelled 
Tangtop Generic USBPS2), and I've been trying to get it to work since 
then. Current status is that the primary keyboard is on the normal 
PS/2-port, the primary mouse is on the mouse's usual PS/2, and the 
secondary keyboard and mouse on an USB port using this gadget. That's 
the configuration I intend to be permanent. 

Unfortunately, it is only the primary keyboard that works. Not the 
primary mouse, nor the secondary stuff. 

The strange thing is that /dev/psaux, /dev/input/mouse0 and 
/dev/input/event0, the devices where one should expect stuff to be on, 
they all work... E.g. cat /dev/input/mouse0 yields output if I touch 
the secondary mouse. Yeah, this change is reflected in the X 
config... :-)

Output of /proc/bus/input/devices is
isa0060/serio0/input0
usb-00:04.2-2/input0

I now boot with dumbcon=3 (don't think I need it, though, no multimedia 
keys).

In the interest of bandwidth conservation, I've dropped the config files 
and the logs to http://dev.kjernsmo.net/tmp/multi-user-logs1/ instead 
of attaching them. 

I've been slightly confused about the connection between the numbering 
on virtual terminals, tty's, and how they relate to the number I put at 
the end of the line in the Xserver file... vt[n] you know... :-) So, 
you can see in 
http://dev.kjernsmo.net/tmp/multi-user-logs1/XFree86.1.log
that I've used vt16. I've used vt9 and vt8 too, without success. I have 
vt8 now, as from my current understanding, it should be correct, since 
dmesg says:
 keyboard.c Tangtop Generic USBPS2 VT1 first VC 8


There is a weird thing that may have some relevance, that happens if I 
go cat /proc/bus/usb/devices... It takes a long time to get anything, 
and at the end of http://dev.kjernsmo.net/tmp/multi-user-logs1/dmesg
you see lines like:
usb_control/bulk_msg: timeout

Scary, huh?

Well, other than that, I have no idea... As long as the devices give 
some output, I thought things would be OK... (I have not yet taken the 
advice to go for gdm...). Any takers...? :-)

Finally, I just upgraded to Andreas' latest XFree-packages (thanks a 
lot, Andreas!), but I have not changed the config to use the 
PrefBusID-option yet. 

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:problem with x authorization

[dave g. <giv...@ya...>]

When I start my 2nd X, I ought to be able to run KDE
or Gnome to have a second user on the machine. But, I
get error messages that the X server isn't allowing my
client(KDE) to connnect, thus my 2nd X server is
useless.

How do I fix this?

Also, I'm expirementing with virtual displays using
the 'Virtual' keyword in my X config to make my screen
larger. Do you know how to control where the viewport
on the screen will initially appear when X starts?

--- Aivils Stoss <Aiv...@un...> wrote:
> 
> >But, when I start my second X server with the
> startx1
> >command (modified version of startx to start my 2nd
> >server), I get an error message:
> >
> >Xlib: connection to ":1.0" refused by server
> >Xlib: Client is not authorized to connect to
> server.
> 
> IMHO You attemp kill fly with the cannon.
> This project is created actualy for 2 separate X
> servers. If You will start programms from 1st
> desktop
> on 2nd desktop, then You will use Xinerama.
> 
> Even root cannot access X desktop.
> 
> Aivils
> 
> 
> 
>
-------------------------------------------------------
> This SF.net email is sponsored by: The SF.net
> Donation Program.
> Do you like what SourceForge.net is doing for the
> Open
> Source Community?  Make a contribution, and help us
> add new
> features and functionality. Click here:
> http://sourceforge.net/donate/
> _______________________________________________
> Linuxconsole-dev mailing list
> Lin...@li...
>
https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: Local Multi-User X (?) problems

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

Hi there! 

Good news! 

On Thursday 30 October 2003 12:48, Svetoslav Slavtchev wrote:

> > > > BTW, /proc/bus/usb/devices does not exist on my system,
>
> probably your init script doesn't like
> built in support for usb,
> this is the case for mandrake as well
> if usb is built in the kernel, not as modules,
> service usb doesn't start -- it doesn't mount
> usbfs and there might be some issues with
> certain usb drivers
> you probably have to mount it yourself then

Helge's advice worked well! Here is my /proc/bus/usb/devices:

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB UHCI Root Hub
S:  SerialNumber=d000
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=186/900 us (21%), #Int=  2, #Iso=  0
D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB UHCI Root Hub
S:  SerialNumber=d400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=1.5 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=046d ProdID=c00e Rev=11.10
S:  Manufacturer=Logitech
S:  Product=USB-PS/2 Optical Mouse
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=hid
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms
T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#=  3 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=09da ProdID=0006 Rev= 0.01
S:  Manufacturer=A4Tech
S:  Product=USB Optical Mouse
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=hid
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

But now, I've bought the USB to PS/2 converter, so this will change 
soon, I guess!

> please check if putting
> Option "DRI" "false"
> for your second card works OK
> with DRI activated for the first card
> and drop a line
> (i'll add it to the howto if it works)

It works! :-) 

The log says:
(II) MGA(0): [DRI] installation complete

Cool, eh?

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: Local Multi-User X (?) problems

[Andreas S. <an...@sc...>]

* Kjetil Kjernsmo (kj...@kj...) [031030 10:33]:
> > you've written to Andreas,
> > have you asked him which XFree-PrefBusID patch he uses for
> > his XFree binaries ?
> 
> Nope. I'll drop him a note.

i am actually not sure which versin is on my website.  i will
upload the version 3 where one can specify the singlecard option
in the config file.

Re: Local Multi-User X (?) problems

[Aivils S. <Aiv...@un...>]

>>
>> Yup. Since it works now, I'll stick to kdm.
>>
>
>it's higly recomended to switch to gdm,
>as it does obey the specified start/stop order
>and the later is really important to avoid some lock ups
>with certain graphic cards on start/restart/ shut down
>of the X servers, and it does help to retain the VGA console

Bigest sin of kdm is starting of all xf86 come
together. Shutdow oder same as starting order.

gdm instead wait until whole init of current xf86,
then try init next xf86. Shutdown order is reverse.
This two features are important!

May be newest kdm is smarter now.

Aivils Stoss

Re: Local Multi-User X (?) problems

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

On Thursday 30 October 2003 12:48, Svetoslav Slavtchev wrote:
> > Yihaaaa! It works! disabling DRI and using the -prefbusid option
> > did the trick! Thanks a lot!
>
> happy to hear it :-)

Yup! My girlfriend is right now happily editing her documents in OO, and 
all is well! :-) It also looks like I can't use this as an excuse to 
buy more RAM, because it's not yet swapping... 

> so Andreas haven't updated his XFree binaries yet,
> i'll probably have to add it to the howto

It could perhaps be just the DRI that was the problem? 

> > Yes. I think I once read that if you build a kernel for a specific
> > system, and there is something you use all the time, compile it
> > into the kernel, if you use it just occasionally, compile it as a
> > module.
>
> that's probably OK,
> but the question is whether the init scripts
> can live with it

OK!

>
> althougt what happens if you decide to change some hardware,
> filesystem ?

That doesn't happen _that_ often, and besides, when it happens, it was 
probably time to get the latest kernel anyway! :-) A kernel compile 
doesn't take more than 20 minutes, and being an astrophysicist, I'm 
used to processes running for weeks... :-)

> it's more flexible to have most hardware compiled as module's

Yup, undoubtedly.

BTW, my bzipped kernel is currently about 1 MB.  

> > > > BTW, /proc/bus/usb/devices does not exist on my system,
> > >
> > > this is somewhat strange
> > > you must have it
> >
> > OK...
>
> probably your init script doesn't like
> built in support for usb,
> this is the case for mandrake as well
> if usb is built in the kernel, not as modules,
> service usb doesn't start -- it doesn't mount
> usbfs and there might be some issues with
> certain usb drivers
> you probably have to mount it yourself then

OK, I'll try Helge's advice, if it doesn't work, I'll compile it as a 
module. 

> > BTW, here's one point you might want to add something like this in
> > a Troubleshooting section of your HOWTO:
> >
> > Q: e2fsck complains I have a bad superblock after I enabled devfs.
> > In fact, it appears all the superblocks are bad, and I'm scared.
> > What do I do?
> >
> > A: Make sure devfsd is running.
> >
> > :-) This put me off for several days...
>
> it happened to me under debian too :-)
> but i don't think it's a good idea to add this to the howto,
> it's devfs issue and has nothing to do with bruby/ruby-2.6
> and there is a link to the devfs howto

Yeah, well, you have spelled it out clearly, that devfsd is needed, so I 
guess I can only blame myself. But when something like that happens to 
a newbie like me, the system is suddenly unbootable and the first thing 
you think about is "data corruption", a newbie is really put off... :-) 

The problem is, and why it took me so long, was the lack of keywords... 
I didn't realize it was a devfs problem, because I enabled devfs when 
booting the backstreet ruby kernel the first time. Besides, my HD has 
had a lot of problems (a physical problem actually, the IDE cable falls 
out if I just barely touch the chassis :-( ), so I was quite sure it 
was a kernel/hardware problem. It wasn't untill I tried booting my 
non-bruby 2.4.22 kernel with devfs I realized that was relevant. Then 
adding "devfs" to my google search for "e2fsck bad superblock" gave the 
answer immediately. So, I thought it could perhaps fit in an appendix?

Of course, this kind of stuff isn't really what newbies should be doing, 
but then... :-) 

> it's higly recomended to switch to gdm,
> as it does obey the specified start/stop order
> and the later is really important to avoid some lock ups
> with certain graphic cards on start/restart/ shut down
> of the X servers, and it does help to retain the VGA console

OK! I'll probably switch to GDM when I get time to look more into 2.6!


>
> > I guess I might as well ask right now: I was thinking about buying
> > a gadget where I can get two PS/2 ports from a USB-port, like this:
> > http://www.clasohlson.no/images/products/N/hi/A/324024_Xw4.jpg I
> > have no further specs on it, but do you guys think it would "work"?
> > The idea is to use one of those for the second keyboard and mouse.
>
> no idea,
> if it works under non ruby kernel, it should work under
> bruby/ruby-2.6 too
>
> may be searching for this particular adapter "+ linux" on google will
> give you some answers

Yup, there are stuff like that certfied for Linux, (as Aivils pointed 
out). I'll probably go out an buy one tomorrow. I was concerned if it 
could for example just send all its output to e.g. /dev/input/event2, 
and it would be both mouse and keyboard and difficult to tell apart. 
Mmmm, it was a whole lot of wires now... I figured it would be cool if I 
could have something like a Bluetooth box on my desktop with RS232, 
PS/2 and USB connections, and symmetric crypto between that box and a 
bluetooth PCI card in the machine... Anybody know if something like 
that exists? :-) 

> please check if putting
> Option "DRI" "false"
> for your second card works OK
> with DRI activated for the first card
> and drop a line
> (i'll add it to the howto if it works)

Yup, I'll do that once I'm alone on the box! :-) 

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: Local Multi-User X (?) problems

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

On Thu, Oct 30, 2003 at 03:51:10PM +0100, Svetoslav Slavtchev wrote:
> > On Thu, Oct 30, 2003 at 12:48:02PM +0100, Svetoslav Slavtchev wrote:
> > > 

> and how big is your kernel ?
> should you recompile the kernel all the time ?
> 
I do that anyway, I boot & use most of the development kernels.
It is my small contribution to testing them.

My kernels are 2.1MB. Modules wouldn't help much with
memory consumption, because most of them would
be loaded all the time anyway. 


> > > it's more flexible to have most hardware compiled as module's
> > > 
> > Sure - and a lot more hassle if you're running experimental kernels,
> IMO that was the case with 2.5 only
> > devfs, or drivers not yet supported by the distribution.
> ???
Module autoload if you try to access the device.  Except
when using devfs, because then the device node isn't
present until the driver registers.  A good devfsd setup
fixes that - and the distribution may come with a good
devfsd setup.  "New" devices aren't usually there though.
Setting them up isn't fun.  

Modules are great for distribution though.
 
> > > > > > BTW, /proc/bus/usb/devices does not exist on my system,
> > > > >
> > > > > this is somewhat strange
> > > > > you must have it
> > > > 
> > > > OK... 
> > > > 
> > > probably your init script doesn't like
> > > built in support for usb,
> > > this is the case for mandrake as well
> > > if usb is built in the kernel, not as modules,
> > > service usb doesn't start -- it doesn't mount
> > > usbfs and there might be some issues with 
> > > certain usb drivers
> > > you probably have to mount it yourself then
> > > 
> > Put this in /etc/fstab:
> > none                  /proc/bus/usb usbfs   defaults                    0
> > 0
> 
> and you tell me that debian copes with it :-)
> shouldn't it be done automatically ?

It is a fs - something must mount it.  /etc/fstab
is a standard place.  Of course debian
ought to come with it, but I haven't had
debian install a fstab for me for years. (Never
reinstall, only upgrade ...) 

Helge Hafting

Re: 2.6.0-test6 ruby success with matrox G550, and some questions

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

On Tue, Oct 28, 2003 at 02:03:58PM +0200, Aivils Stoss wrote:
> 
> >> Current ruby support straight in kernel compiled fb device
> >> drivers and fbcon. To test Your matrox figure fbcon into
> >> kernel and reboot.
> >2.6.0-test6-ruby dies before the first printk if I do that,
> >while 2.6.0-test6 works.  fbcon on matrox breaks somehow
> >with ruby.  I don't know what to do to debug this
> >further - adding printk's is probably not an option.
> 
> Strange. Normal is 5-10 sec VGA console output until
> fb_console_init is called. After fb_console_init You
> can read printk only on serial console terminal in case
> fbcon is broken.
> 
You are right, there is a few lines of VGA console
output.  I only see half a second if I'm lucky,
because the flat panel screen takes a long time
to switch modes.

2.6test6-ruby with fbcon and 2.6test9-ryby with fbcon
are the same - they die when switching away from vga.
The screen goes black/garbage and then its over.

2.6test6-ruby and 2.6test9-ruby without fbcon
works fine, except that I have no text console.
All I can do if I quit X is to type
blind while looking at a garbage framebuffer.
The garbage change as I type, indicating
prograss but not all that helpful.

2.6test9-ruby with the single console patch
seemed to crash, although it got a little
further.  It managed to corrupt filesystems,
so I believe it got as far as mounting while
the screen was showing garbage.  The keyboard
didn't react to numlock though, so I reset it.
Perhaps I try it again.

Helge Hafting

Re: Local Multi-User X (?) problems

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

> On Thu, Oct 30, 2003 at 12:48:02PM +0100, Svetoslav Slavtchev wrote:
> > 
> > > Yes. I think I once read that if you build a kernel for a specific 
> > > system, and there is something you use all the time, compile it into 
> > > the kernel, if you use it just occasionally, compile it as a module. 
> > 
> > that's probably OK,
> > but the question is whether the init scripts 
> > can live with it
> > 
> Debian seems to cope.  I run a kernel with no module support at all.
> (The module interface changed late in 2.5.xx, modules were unavailable
> for a while anyway.)

i know, but now everything is OK

> > althougt what happens if you decide to change some hardware,
> > filesystem ?
> > 
> Compile a new kernel.  You have to turn the machine off anyway
> to install non-hotplug hardware.  You can precompile filesystems
> that you think you might need in the future.  (Drivers too, but they
> tend to have boring probe timeouts when the hw isn't there.)

well
and how big is your kernel ?
should you recompile the kernel all the time ?

> > it's more flexible to have most hardware compiled as module's
> > 
> Sure - and a lot more hassle if you're running experimental kernels,
IMO that was the case with 2.5 only
> devfs, or drivers not yet supported by the distribution.
???

> > > > > BTW, /proc/bus/usb/devices does not exist on my system,
> > > >
> > > > this is somewhat strange
> > > > you must have it
> > > 
> > > OK... 
> > > 
> > probably your init script doesn't like
> > built in support for usb,
> > this is the case for mandrake as well
> > if usb is built in the kernel, not as modules,
> > service usb doesn't start -- it doesn't mount
> > usbfs and there might be some issues with 
> > certain usb drivers
> > you probably have to mount it yourself then
> > 
> Put this in /etc/fstab:
> none                  /proc/bus/usb usbfs   defaults                    0
> 0

and you tell me that debian copes with it :-)
shouldn't it be done automatically ?


best,

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! +++

Re: Local Multi-User X (?) problems

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

On Thu, Oct 30, 2003 at 12:48:02PM +0100, Svetoslav Slavtchev wrote:
> 
> > Yes. I think I once read that if you build a kernel for a specific 
> > system, and there is something you use all the time, compile it into 
> > the kernel, if you use it just occasionally, compile it as a module. 
> 
> that's probably OK,
> but the question is whether the init scripts 
> can live with it
> 
Debian seems to cope.  I run a kernel with no module support at all.
(The module interface changed late in 2.5.xx, modules were unavailable
for a while anyway.)

> althougt what happens if you decide to change some hardware,
> filesystem ?
> 
Compile a new kernel.  You have to turn the machine off anyway
to install non-hotplug hardware.  You can precompile filesystems
that you think you might need in the future.  (Drivers too, but they
tend to have boring probe timeouts when the hw isn't there.)

> it's more flexible to have most hardware compiled as module's
> 
Sure - and a lot more hassle if you're running experimental kernels,
devfs, or drivers not yet supported by the distribution.

> > > > BTW, /proc/bus/usb/devices does not exist on my system,
> > >
> > > this is somewhat strange
> > > you must have it
> > 
> > OK... 
> > 
> probably your init script doesn't like
> built in support for usb,
> this is the case for mandrake as well
> if usb is built in the kernel, not as modules,
> service usb doesn't start -- it doesn't mount
> usbfs and there might be some issues with 
> certain usb drivers
> you probably have to mount it yourself then
> 
Put this in /etc/fstab:
none                  /proc/bus/usb usbfs   defaults                    0 0


Helge Hafting