Re: Type5 keyboard with kernel version 2.6.x
On Mon, 2005-10-31 15:50:24 -0600, Marc Mandel [EMAIL PROTECTED] wrote: OK. I upgraded from 2.4.x to 2.6.12 and now my keyboard is dorked both inside of and outside of X.org You're probably loading a new key mapping during bootup. Don't do that, or load the one for PC105 keyboards. MfG, JBG -- Jan-Benedict Glaw [EMAIL PROTECTED]. +49-172-7608481 _ O _ Eine Freie Meinung in einem Freien Kopf| Gegen Zensur | Gegen Krieg _ _ O für einen Freien Staat voll Freier Bürger | im Internet! | im Irak! O O O ret = do_actions((curr | FREE_SPEECH) ~(NEW_COPYRIGHT_LAW | DRM | TCPA)); signature.asc Description: Digital signature
Re: please review alsaconf patch
Hi,
Martin Habets wrote:
Thanks for the info. I guess you must have an audio device on the
ebus then, and I failed to check for that in my original patch.
Could you try the patch attached in stead of the original one, please?
Unfortunately, it didn't work out-of-the-box. With a bit of polishing I
could at least make it run (see attached incremental patch to your changes).
Some comments to the respective changes:
(1) $PROCFS was not defined, so I set it manually. I didn't know where
you intended it to come from so I just set it in the beginning of the
patch to /proc.
(2) I guess you meant mounting openpromfs in case /proc/openprom exists?
Therefore instead of ||.
(3) Under /proc/openprom/[EMAIL PROTECTED],470/[EMAIL PROTECTED], I have a
directory
called [EMAIL PROTECTED],20. Therefore, I needed to search for audio*
instead of audio.
(4) The file compatible contains: 'SUNW,CS4231' (with single
quotes). I needed to remove them.
Now, alsaconf detects the device fine. (Also consider FJP's comments on
using modprobe.)
However, there are some issues left with my CS4231: On bootup, the
modules are not loaded automatically (even hotplug doesn't care about
them). So I need to put snd-sun-cs4231 into /etc/modules. Further,
when I want to play something (e.g., with xmms), I often (unpredictably)
get (white?) noise. Retrying helps every 3rd or 4th time. Maybe
alignment or endianess issues. But these are different issues and not
related to alsaconf I think. If noone else has experienced this yet, I
will need to dive into the driver myself later.
Thanks for now.
bye,
Roland
--- alsaconf.orig 2005-11-01 12:39:37.0 +0100
+++ alsaconf 2005-11-01 12:38:53.0 +0100
@@ -588,16 +588,19 @@
#
# Sparc
#
+PROCFS=/proc
if grep -q Sparc $PROCFS/cpuinfo; then
- test -r $PROCFS/openprom || /bin/mount -t openpromfs none $PROCFS/openprom /dev/null 21
+ test -r $PROCFS/openprom /bin/mount -t openpromfs none $PROCFS/openprom /dev/null 21
# Check for an audio device
audio=
compat=
if test -r $PROCFS/openprom; then
- audio=`find $PROCFS/openprom -follow -type d -name audio -print`
+ audio=`find $PROCFS/openprom -follow -type d -name audio* -print`
fi
if test -n $audio; then
compat=`cat $audio/compatible`
+ compat=${compat#\'}
+ compat=${compat%\'}
compat=${compat#SUNW,}
fi
# Go through all cards we have
Re: Type5 keyboard with kernel version 2.6.x
On Tue, 1 Nov 2005 11:04:50 +0100, Jan-Benedict Glaw [EMAIL PROTECTED] wrote: On Mon, 2005-10-31 15:50:24 -0600, Marc Mandel [EMAIL PROTECTED] wrote: OK. I upgraded from 2.4.x to 2.6.12 and now my keyboard is dorked both inside of and outside of X.org You're probably loading a new key mapping during bootup. Don't do that, or load the one for PC105 keyboards. MfG, JBG My first thought was How the heck do I do that? Well, a little google searching and I found the following link: http://www.debian.org/releases/stable/sparc/release-notes/ch-information.en.html In the spirit that this may be useful to someone else, here is the relevent portion: 5.2.1 Keyboard configuration The most invasive change in the 2.6 kernels is a fundamental change of the input layer. This change makes all keyboards look like normal PC keyboards. This means that if you currently have a different type of keyboard selected (e.g. a USB-MAC or Sun keyboard), you will very likely end up with a non-working keyboard after rebooting with the new 2.6 kernel. If you can SSH into the box from another system, you can resolve this issue by running dpkg-reconfigure console-data, choosing the option Select keymap from full list and selecting a pc keyboard. If your console keyboard is affected, you will probably also need to reconfigure your keyboard for the X Window System. You can do this either by running dpkg-reconfigure xserver-xfree86 or by editing /etc/X11/XF86Config-4 directly. Don't forget to read the documentation referred to in Things to do before rebooting, Section 4.6. Note that if you are using a USB keyboard, this may be configured as either a normal PC keyboard or as a USB-MAC keyboard. In the first case you will not be affected by this issue. So, now I am running 2.6.x kernel with a working console. Still no working xorg... yet... Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Type5 keyboard with kernel version 2.6.x
On Tue, 01 Nov 2005 11:09:55 -0600, Marc Mandel [EMAIL PROTECTED] wrote: On Tue, 1 Nov 2005 11:04:50 +0100, Jan-Benedict Glaw [EMAIL PROTECTED] wrote: On Mon, 2005-10-31 15:50:24 -0600, Marc Mandel [EMAIL PROTECTED] wrote: OK. I upgraded from 2.4.x to 2.6.12 and now my keyboard is dorked both inside of and outside of X.org You're probably loading a new key mapping during bootup. Don't do that, or load the one for PC105 keyboards. MfG, JBG My first thought was How the heck do I do that? Well, a little google searching and I found the following link: http://www.debian.org/releases/stable/sparc/release-notes/ch-information.en.html In the spirit that this may be useful to someone else, here is the relevent portion: stuff deleted So, now I am running 2.6.x kernel with a working console. Still no working xorg... yet... Marc X.org would not work due to mouse problems. I edit xorg.conf and changed mouse from /dev/sunmouse to /dev/psaux and it is working... Thanks to Christian (for your initial post) and Jan-Benedict for your help. Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bttv and SPARC
[EMAIL PROTECTED] wrote: Hi all. I would like to know if bttv is supposed to work under sparc (Ultra 10). pci_iommu: alloc_streaming_cluster of npages(260) failed! I confirm that my TV tuner works with the 2.6.14 kernel. It seems that the problem was that the fast allocator in the sparc64 PCI IOMMU code had a hard limit of 256 pages. (according to the kernel changelog). I experienced a hard lockup and an oops; still needs some investigation. Nov 1 14:09:18 solaris kernel: spitfire_data_access_exception: SFSR[00801009] SFAR[0004], going. Nov 1 14:09:18 solaris kernel: \|/ \|/ Nov 1 14:09:18 solaris kernel: @'/ .. \`@ Nov 1 14:09:18 solaris kernel: /_| \__/ |_\ Nov 1 14:09:18 solaris kernel: \__U_/ Nov 1 14:09:18 solaris kernel: sh(2613): Dax [#1] Nov 1 14:09:18 solaris kernel: TSTATE: 009911009607 TPC: 004babd0 TNPC: 004babd4 Y: Not tainted Nov 1 14:09:18 solaris kernel: TPC: proc_lookup+0x30/0xc0 Nov 1 14:09:18 solaris kernel: g0: f80007a86fe1 g1: 0006 g2: g3: fff8 Nov 1 14:09:18 solaris kernel: g4: f8001319c800 g5: 6f6e6600 g6: f80007a84000 g7: 006b Nov 1 14:09:18 solaris kernel: o0: fff8 o1: f80016ff6d61 o2: o3: 0a433ef2 Nov 1 14:09:18 solaris kernel: o4: f8001226cefc o5: f8001226cea0 sp: f80007a87051 ret_pc: 004babf0 Nov 1 14:09:18 solaris kernel: RPC: proc_lookup+0x50/0xc0 Nov 1 14:09:18 solaris kernel: l0: c000 l1: f8001226d5e0 l2: 00702c00 l3: 0006 Nov 1 14:09:18 solaris kernel: l4: f80007e3900a l5: l6: l7: 701d1000 Nov 1 14:09:18 solaris kernel: i0: f80007e54328 i1: f8001226ce48 i2: f80007a87d68 i3: Nov 1 14:09:18 solaris kernel: i4: i5: i6: f80007a87111 i7: 004916a0 Nov 1 14:09:18 solaris kernel: I7: do_lookup+0x140/0x180 Nov 1 14:09:18 solaris kernel: Caller[004916a0]: do_lookup+0x140/0x180 Nov 1 14:09:18 solaris kernel: Caller[00491820]: __link_path_walk+0x140/0xe60 Nov 1 14:09:18 solaris kernel: Caller[00492598]: link_path_walk+0x58/0x140 Nov 1 14:09:18 solaris kernel: Caller[00493c90]: open_namei+0x70/0x660 Nov 1 14:09:18 solaris kernel: Caller[00481e60]: filp_open+0x40/0xa0 Nov 1 14:09:18 solaris kernel: Caller[00481f58]: do_sys_open+0x38/0xe0 Nov 1 14:09:18 solaris kernel: Caller[00407194]: linux_sparc_syscall32+0x34/0x40 Nov 1 14:09:18 solaris kernel: Caller[70136bcc]: 0x70136bcc Nov 1 14:09:18 solaris kernel: Instruction DUMP: e05c2048 22c4001e b0103ffe c4142004 c206602c 80a08001 124a d4142004 952ab030 ... Nov 1 19:02:24 solaris kernel: Badness in pci_map_sg at arch/sparc64/kernel/pci_iommu.c:633 Nov 1 19:02:24 solaris kernel: Call Trace: Nov 1 19:02:24 solaris kernel: [1021d99c] videobuf_iolock+0x9c/0x160 [video_buf] Nov 1 19:02:24 solaris kernel: [102264b4] bttv_prepare_buffer+0xf4/0x1c0 [bttv] Nov 1 19:02:24 solaris kernel: [1022b4a4] bttv_do_ioctl+0x1084/0x1ea0 [bttv] Nov 1 19:02:24 solaris kernel: [101ee168] video_usercopy+0xc8/0x2a0 [videodev] Nov 1 19:02:24 solaris kernel: [0049585c] do_ioctl+0x5c/0x80 Nov 1 19:02:24 solaris kernel: [004958ec] vfs_ioctl+0x6c/0x340 Nov 1 19:02:24 solaris kernel: [00495be8] sys_ioctl+0x28/0x60 Nov 1 19:02:24 solaris kernel: [004ad904] compat_sys_ioctl+0xe4/0x3c0 Nov 1 19:02:24 solaris kernel: [00407194] linux_sparc_syscall32+0x34/0x40 Nov 1 19:02:24 solaris kernel: [00047db0] 0x47db0 Nov 1 19:02:24 solaris kernel: videobuf_dma_pci_map: pci_map_sg failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
