Re: Bug#282435: xfree86 cannot find /dev/psaux after install of kernel-image-2.6.8-1-k7
On Mon, Nov 22, 2004 at 09:46:53PM -0500, xucaen wrote: > Package: kernel-image-2.6.8-1-k7 > Status: install ok installed > Priority: optional > Section: base > Installed-Size: 44108 > Maintainer: Debian kernel team > Architecture: i386 > Source: kernel-image-2.6.8-i386 > Version: 2.6.8-5 > Provides: kernel-image, kernel-image-2.6 > Depends: initrd-tools (>= 0.1.63), coreutils | fileutils (>= 4.0), > module-init-tools (>= 0.9.13) > Suggests: lilo (>= 19.1) | grub, fdutils, kernel-doc-2.6.8 | > kernel-source-2.6.8 > Conflicts: hotplug (<< 0.0.20040105-1) > Description: Linux kernel image for version 2.6.8 on AMD K7. > > Hi, sorry about not providing the required information. I've never > submitted a bug report before. I'm not entirely certain I even need to > send this but the error message I received said I should send the > /var/log/XFree86.0.log to you. I am still researching this out on the > web to find what I need to do to fix this. > Everything is working smoothly. But XFree86 fails to load and > gives me these errors: > > (EE) xf86OpenSerial: Cannot open device /dev/psaux > No such device. > (EE) Configured Mouse: cannot open input device > (EE) PreInit failed for input device "Configured Mouse" > No core pointer > > from what i've been able to gather, /dev/psaux no longer is used by the > new kernel 2.6. I am unable to find steps to take to change my > configuration. I did find a that "modprob mousedev psaux=1" make the > mouse work again. > I found in the kernel 2.6.8 docs that I need to make sure that both > psmouse and mousedev modules are installed. I ran modconf and discovered > that psmouse is installed but there was no mousedev on the list. I have > verified that the new module-init-tools package is installed > Package: module-init-tools > Version: 3.1-pre6-1 > > I am attaching attach /var/log/XFree86.0.log A work around that worked for _me_ on several systems was to insmod mousedev (and possibly also psmouse). I believe there are plenty of others. I am pretty certain it isn't a kernel bug as such. -- Horms
Bug#318413: xlibs: Backslash Key is broken on Japanese Keyboards
{ , "NORM", 1, color="white" },
{ , "NORM", 1, color="white" }
};
};
row {
top= 58;
left= 1;
keys {
{ , "NORM", 1, color="white" },
{ , "NORM", 1, color="white" },
{ , "NORM", 1, color="white" },
{ , "KPAD", 1 }
};
};
row {
top= 77;
left= 1;
keys {
{ , "KP0", 1, color="white" },
{ , "NORM", 1, color="white" }
};
};
}; // End of "Keypad" section
solid "LedPanel" {
top= 25;
left= 375;
priority= 0;
color= "grey10";
shape= "LEDS";
};
indicator "Num Lock" {
top= 40;
left= 379;
priority= 1;
onColor= "green";
offColor= "green30";
shape= "LED";
};
indicator "Caps Lock" {
top= 40;
left= 404;
priority= 2;
onColor= "green";
offColor= "green30";
shape= "LED";
};
indicator "Scroll Lock" {
top= 40;
left= 429;
priority= 3;
onColor= "green";
offColor= "green30";
shape= "LED";
};
text "NumLockLabel" {
top= 28;
left= 378;
priority= 4;
width= 19.8;
height= 10;
XFont= "-*-helvetica-medium-r-normal--*-120-*-*-*-*-iso8859-1";
text= "Num\nLock";
};
text "CapsLockLabel" {
top= 28;
left= 403;
priority= 5;
width= 26.4;
height= 10;
XFont= "-*-helvetica-medium-r-normal--*-120-*-*-*-*-iso8859-1";
text= "Caps\nLock";
};
text "ScrollLockLabel" {
top= 28;
left= 428;
priority= 6;
width= 39.6;
height= 10;
XFont= "-*-helvetica-medium-r-normal--*-120-*-*-*-*-iso8859-1";
text= "Scroll\nLock";
};
};
};
-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12
Locale: LANG=ja_JP.eucJP, LC_CTYPE=ja_JP.eucJP (charmap=EUC-JP) (ignored:
LC_ALL set to ja_JP.eucJP)
Versions of packages xlibs depends on:
ii libice6 6.8.2.dfsg.1-2 Inter-Client Exchange library
ii libsm6 6.8.2.dfsg.1-2 X Window System Session Management
ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li
ii libxext6 6.8.2.dfsg.1-2 X Window System miscellaneous exte
ii libxi6 6.8.2.dfsg.1-2 X Window System Input extension li
ii libxmu6 6.8.2.dfsg.1-2 X Window System miscellaneous util
ii libxmuu1 6.8.2.dfsg.1-2 lightweight X Window System miscel
ii libxp6 4.3.0.dfsg.1-14 X Window System printing extension
ii libxpm4 6.8.2.dfsg.1-2 X pixmap library
ii libxrandr2 6.8.2.dfsg.1-2 X Window System Resize, Rotate and
ii libxt6 6.8.2.dfsg.1-2 X Toolkit Intrinsics
ii libxtrap66.8.2.dfsg.1-2 X Window System protocol-trapping
ii libxtst6 6.8.2.dfsg.1-2 X Window System event recording an
ii xlibs-data 6.8.2.dfsg.1-2 X Window System client data
xlibs recommends no packages.
-- no debconf information
--
Horms
--- ./etc_X11_6.8.2.dfsg.1-2/xkb/keycodes/xfree86 2005-07-12
21:58:36.0 +0300
+++ /etc/X11/xkb/keycodes/xfree86 2005-07-15 14:52:25.0 +0300
@@ -151,7 +151,9 @@
// Keys that are generated on Japanese keyboards
alias = ; // Hankaku_Zenkaku toggle
+ = 120;// Hiragana_Katakana toggle
= 208;// Hiragana_Katakana toggle
+alias = ; // backslash/underscore
= 211;// backslash/underscore
= 129;// Henkan
= 131;// Muhenkan
Bug#318413: xlibs: Backslash Key is broken on Japanese Keyboards
On Fri, Jul 15, 2005 at 09:19:24PM +0200, Mike Hommey wrote: > On Fri, Jul 15, 2005 at 02:58:32PM +0300, Horms <[EMAIL PROTECTED]> wrote: > > Package: xlibs > > Version: 6.8.2.dfsg.1-2 > > Severity: important > > Tags: patch > > > > Hi, > > > > After upgrading xlibs the backslash no longer works on > > my Toshiba Dynabook with a japanese keyboard. This makes > > coding really hard! > > > > The attached patch resolves this problem as well as making the > > Hirugana/Katakana toggle work. Actually, the patch I posted is bogus and doesn't fix anything. The following works for me, but will probably break others. I'm not sure how to make bouth 120 and 208 produce a HKTG, and both KPDC and 211 produce a AB11. I only need the former in each case, but for people who need the latter, my patch falls appart. And if I take the commends out, my keys go to NoSymbol land. > Interestingly, I had the same problem here, which got resolved as soon > as I switched from xserver-xfree86 to xserver-xorg. > > Though the file you patch is the same on my system than your "broken" > one, the backslash key works correctly... it's a bit weird... That is weird. I'm not entirely sure that all Japanese keyboards are created equal, and right now I only have one to test on. I'll be home in about a week and I can test on an IBM keyboard. -- Horms --- ./etc_X11_6.8.2.dfsg.1-2/xkb/keycodes/xfree86 2005-07-12 21:58:36.0 +0300 +++ /etc/X11/xkb/keycodes/xfree86 2005-07-16 13:21:25.0 +0300 @@ -151,8 +151,10 @@ // Keys that are generated on Japanese keyboards alias = ; // Hankaku_Zenkaku toggle - = 208;// Hiragana_Katakana toggle - = 211;// backslash/underscore + = 120;// Hiragana_Katakana toggle +// = 208; // Hiragana_Katakana toggle +alias = ; // backslash/underscore +// = 211; // backslash/underscore = 129;// Henkan = 131;// Muhenkan = 133;// Yen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318413: xlibs: Backslash Key is broken on Japanese Keyboards
On Tue, Jul 19, 2005 at 11:14:12PM +0200, Denis Barbier wrote:
> On Fri, Jul 15, 2005 at 02:58:32PM +0300, Horms wrote:
> > Package: xlibs
> > Version: 6.8.2.dfsg.1-2
> > Severity: important
> > Tags: patch
> >
> > Hi,
> >
> > After upgrading xlibs the backslash no longer works on
> > my Toshiba Dynabook with a japanese keyboard. This makes
> > coding really hard!
> >
> > The attached patch resolves this problem as well as making the
> > Hirugana/Katakana toggle work.
> [...]
> > Versions of packages xlibs depends on:
> > ii libice6 6.8.2.dfsg.1-2 Inter-Client Exchange library
> > ii libsm6 6.8.2.dfsg.1-2 X Window System Session
> > Management
> > ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol
> > client li
>
> There is some mismatch here, your libx11-6 package should have the same
> version number as other X packages.
Good point, I think that was as a result of me desparately
reinstalling old versions in order to debug the problem.
Surprosingly said system seems to work.
> BTW there is indeed a bug in the Japanese layout, the following patch
> has to be applied.
Thanks, very much appreciated.
> --- /etc/X11/xkb/symbols/pc/jp.orig 2005-07-19 23:10:49.949952776 +0200
> +++ /etc/X11/xkb/symbols/pc/jp2005-07-19 23:12:15.366967416 +0200
> @@ -118,7 +118,7 @@
> key { [ colon, asterisk ] };
> key { [ bracketright, braceright ] };
>
> -key { [ backslash, underscore], [ kana_RO ] };
> +key { [ backslash, underscore] };
>
> key { [ Muhenkan ] };
>
--
Horms
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318413: xlibs: Backslash Key is broken on Japanese Keyboards
On Wed, Jul 20, 2005 at 10:07:06PM +0200, Denis Barbier wrote: > On Wed, Jul 20, 2005 at 01:18:26AM +0200, Horms wrote: > [...] > > > > ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol > > > > client li > > > > > > There is some mismatch here, your libx11-6 package should have the same > > > version number as other X packages. > > > > Good point, I think that was as a result of me desparately > > reinstalling old versions in order to debug the problem. > > Surprosingly said system seems to work. > > I am confused, do you mean that this bug can be closed? Now I am confused. What would you like me to test? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318413: xlibs: Backslash Key is broken on Japanese Keyboards
On Wed, Jul 20, 2005 at 11:46:51PM +0200, Denis Barbier wrote: > On Wed, Jul 20, 2005 at 10:35:22PM +0200, Horms wrote: > > On Wed, Jul 20, 2005 at 10:07:06PM +0200, Denis Barbier wrote: > > > On Wed, Jul 20, 2005 at 01:18:26AM +0200, Horms wrote: > > > [...] > > > > > > ii libx11-6 4.3.0.dfsg.1-14 X Window System > > > > > > protocol client li > > > > > > > > > > There is some mismatch here, your libx11-6 package should have the > > > > > same > > > > > version number as other X packages. > > > > > > > > Good point, I think that was as a result of me desparately > > > > reinstalling old versions in order to debug the problem. > > > > Surprosingly said system seems to work. > > > > > > I am confused, do you mean that this bug can be closed? > > > > Now I am confused. What would you like me to test? > > I would like to know if your Japanese keyboard is broken when all X > packages have been upgraded from XFree86 to X.Org, and if my patch > against /etc/X11/xkb/symbols/pc/jp has some good effect. I am pretty sure it doesn't work on my laptop without the modifucation I posted earlier. And I am pretty sure the japanese keys (e.g. Muhenkan) don't work on my IBM spacesaver keyboard even with your patch and mine. I will double check this and get back to you. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: i915 DRI broken after suspend/resume
On Wed, Jul 27, 2005 at 10:45:20AM +0200, David MartÃnez Moreno wrote: > El Martes, 26 de Julio de 2005 05:20, Drew Parsons escribió: > > Intel video driver (855GM etc) support is broken in Debian > > (linux-tree-2.6 v2.6.12-1, xserver-xorg v6.8.2.dfsg.1-4) at the moment. > > That's the i810 Xserver driver using the i915 kernel drm module. > > > > After a suspend/resume cycle, any OpenGL programs fail, e.g. > > > > $ glxgears > > intelWaitIrq: drmI830IrqWait: -16 > > > > A message appears in dmesg: > > > > [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 4229 emitted: > > 4239 > > > > > > This is a known bug, reported at > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=159960 > > and > > https://bugzilla.ubuntu.com/show_bug.cgi?id=7787 > > and > > http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg21138.html > > > > A patch has apparently been made to X.org CVS, so we'd need to check it > > has been applied in Debian's copy of 6.8.2 (Daniel Stone has apparently > > applied it to Ubuntu). > > > > A kernel patch to i915 is also needed (provided by dri.freedesktop.org, > > exact urls mentioned in the Redhat bug report). They seem more like tarballs with new drivers than patches. Which makes it somewhat difficult to isolate the fix. > > I don't know if it's Debian's X.org or 2.6.12 kernel, or both, which > > needs the patches, so I'm not filing a bug till we know. > > Hello, Drew. We know that the i810 Xserver included in X.Org 6.8.2 is > old and > does not support newer chips, so probably the problem will be in the X.Org > packages. We are currently working in the upcoming 6.9 X.Org release that we > hope to solve your problem (and several others). Is there any value in the patches been added to the debian kernel at this stage? And more to the point, is there any information on the status of this change in the upstream (linus) kernel. I heard on the grapevine that the dri/xorg thing is a bit of a mess at the moment, can someone confirm or deny this? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#312255: Problems booting kernel-image-2.6.8-2-k7
new USB bus registered, assigned bus number 4 > hub 4-0:1.0: USB hub found > hub 4-0:1.0: 2 ports detected > usb 1-1: new full speed USB device using address 2 > ACPI: PCI interrupt :00:10.4[C] -> GSI 21 (level, low) -> IRQ 185 > ehci_hcd :00:10.4: VIA Technologies, Inc. USB 2.0 > ehci_hcd :00:10.4: irq 185, pci mem e08a1000 > ehci_hcd :00:10.4: new USB bus registered, assigned bus number 5 > ehci_hcd :00:10.4: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10 > hub 5-0:1.0: USB hub found > hub 5-0:1.0: 8 ports detected > drivers/usb/class/usblp.c: can't set desired altsetting 0 on interface 0 > usblp: probe of 1-1:1.0 failed with error -5 > usbcore: registered new driver usblp > drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver > usb 1-1: USB disconnect, address 2 > via82xx: Assuming DXS channels with 48k fixed sample rate. > Please try dxs_support=1 or dxs_support=4 option > and report if it works on your machine. > ACPI: PCI interrupt :00:11.5[C] -> GSI 22 (level, low) -> IRQ 193 > PCI: Setting latency timer of device :00:11.5 to 64 > codec_read: codec 0 is not valid [0x107e5368] > codec_read: codec 0 is not valid [0x107e5368] > codec_read: codec 0 is not valid [0x107e5368] > codec_read: codec 0 is not valid [0x107e5368] > usb 1-1: new full speed USB device using address 3 > drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 3 if 0 > alt 0 proto 2 vid 0x03F0 pid 0x7304 > Linux agpgart interface v0.100 (c) Dave Jones > agpgart: Detected VIA KT880 chipset > agpgart: Maximum main memory to use for agp memory: 439M > agpgart: AGP aperture is 256M @ 0xe000 > cpci_hotplug: CompactPCI Hot Plug Core version: 0.2 > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > pciehp: PCI Express Hot Plug Controller Driver version: 0.4 > shpchp: shpc_init : shpc_cap_offset == 0 > shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 > Real Time Clock Driver v1.12 > NET: Registered protocol family 17 > eth0: network connection up using port A > speed: 100 > autonegotiation: yes > duplex mode: full > flowctrl:none > irq moderation: disabled > scatter-gather: enabled > lp: driver loaded but no devices found > NET: Registered protocol family 10 > Disabled Privacy Extensions on device c02fc1a0(lo) > IPv6 over IPv4 tunneling driver > [drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies > Inc Radeon RV200 QW [Radeon 7500] > agpgart: Found an AGP 3.5 compliant device at :00:00.0. > agpgart: Device is in legacy mode, falling back to 2.x > agpgart: Putting AGP V2 device at :00:00.0 into 0x mode > agpgart: Putting AGP V2 device at :01:00.0 into 0x mode > eth0: no IPv6 routers present > > > -- System Information: > Debian Release: 3.1 > Architecture: i386 (i686) > Kernel: Linux 2.4.27-2-386 > Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) > > Versions of packages kernel-image-2.6.8-2-k7 depends on: > ii coreutils [fileutils] 5.2.1-2The GNU core utilities > ii initrd-tools 0.1.81.1 tools to create initrd image for > p > ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel > mo > > -- no debconf information > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
