Re: please review alsaconf patch
Roland,
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?
This patch may also work for the AMD7930, and I would be gratefull if
someone with an AMD7930 could test it.
Thanks,
Martin
On Sun, Oct 30, 2005 at 07:40:49PM +0100, Roland Stigge wrote:
Hi Martin,
you wrote:
I created the patch below to make alsaconf work with the DBRI and
CS4231 chips. But I'm not sure if this will work for the AMD7930
chip. The patch tries to find a SUNW,AMD7930* directory in this
case, but I don't know if that exists. Can somebody with an AMD7930
sound chip confirm/deny this?
Other feedback (like better approaches) is welcome too. I'll submit
it to Takashi once the AMD7930 issue is resolved.
I tried with my CS4231 and that didn't work. Loading the module
snd-sun-cs4231 manually works fine.
Maybe the following debug output is of interest:
# /sbin/modprobe -a -l | grep 'snd-sun-'
/lib/modules/2.6.12-1-sparc64/kernel/sound/sparc/snd-sun-cs4231.ko
/lib/modules/2.6.12-1-sparc64/kernel/sound/sparc/snd-sun-amd7930.ko
/proc/openprom# find /proc/openprom -follow -type d -name SUNW,*
/proc/openprom/packages/SUNW,builtin-drivers
/proc/openprom/SUNW,[EMAIL PROTECTED],0
/proc/openprom/[EMAIL PROTECTED],460/SUNW,[EMAIL PROTECTED]
/proc/openprom/[EMAIL PROTECTED],448/SUNW,[EMAIL PROTECTED],0
(On A SunBlade 1000.)
So there's no 'SUNW,CS4231*' which results in the whole patch giving no
output.
Is this problem related to the above
bye,
Roland
---
--- alsaconf.orig 2005-10-25 16:00:11.0 +0100
+++ alsaconf2005-10-31 13:02:07.0 +
@@ -696,6 +696,40 @@
echo PowerMac $i $FOUND
done
fi
+
+#
+# Sparc
+#
+if grep -q Sparc $PROCFS/cpuinfo; then
+ 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`
+ fi
+ if test -n $audio; then
+ compat=`cat $audio/compatible`
+ compat=${compat#SUNW,}
+ fi
+ # Go through all cards we have
+ /sbin/modprobe -a -l | grep 'snd-sun-' | \
+ while read i; do
+ i=${i##*/}
+ i=${i%%.o}
+ i=${i%%.ko}
+ sdev=`echo ${i#snd-sun-} | tr [a-z] [A-Z]`
+
+ if test $sdev = $compat; then
+ echo $sdev $i $FOUND
+ elif test -r $PROCFS/openprom; then
+ find $PROCFS/openprom -follow -type d -name SUNW,${sdev}* \
+ -exec echo $sdev $i \; 2/dev/null $FOUND
+ else
+ echo $sdev $i $FOUND
+ fi
+ done
+fi
}
#
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: please review alsaconf patch
On Monday 31 October 2005 14:11, Martin Habets wrote: + /sbin/modprobe -a -l | grep 'snd-sun-' | \ Hmmm. Is -a -l correct for modprobe? -l is supposed to list modules, -a to insert (load) them... I doubt that the intention here is to try to actually load all modules available on the system, so why -a? Or am I missing something? From the manpage, -l takes a wildcard, thus why not just use modprobe -l snd-sun-* ? Also from the manpage it looks like both the -a and the -l options are deprecated and using something like find /lib/modules/$(uname -r)/kernel/ -name snd-sun-* is suggested instead. Cheers, FJP pgpbrvS2bIeMn.pgp Description: PGP signature
Re: booting a sunblade 100
On Tue, Oct 25, 2005 at 07:24:45PM +0200, Riccardo Tortorici wrote: It seems the current D-I for SPARC is broken for Sunblades. I had exactly your problem on a Sunblade 150 64bits. Try to install it via netboot with the image you can find here: http://people.debian.org/~stappers/d-i/images/daily/sparc64/netboot/ I tried the 2.6 one and it works. There are some issues regarding the frame buffer (first char truncated). Actually I'm working on a kernel customization in order to fix it. I hope it will work on your sunblade as well. Hi All, Many thanks for all of the replies. Booting via tftp definately works. I have yet to get the installer to complete (it always hangs halfway through), but I'm devoting some time to it when there's a pause in work. I've dumped the blade 150 (since it's having some other problems) and am now concentrating on a 100. -- Sincerely, Matt Dunford Unix Systems Administrator DOE Joint Genome Institute url: http://www.jgi.doe.gov email: [EMAIL PROTECTED] phone: 925-296-5844 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Free Sparcserver 670 in DC area
If anyone in the DC area is feeling adventuresome and would like to try getting Debian to work on a Sparcserver 670, drop me a line. I have one with quad 40mhz processors and about half a gig of ram. Its yours if you pick it up. The 600 series were the first of the Sun 4m machines, supporting sbus, mbus and the vme bus. If you feel really adventuresome, I have a variety of boards for it and some working Seagate IPI hard disks as well. Let me know. Its headed for the landfill if no one wants it.
Re: Type5 keyboard with kernel version 2.6.x
On Sat, 29 Oct 2005 19:54:22 +0200, Christian Tusche [EMAIL PROTECTED] wrote: I'm running debian-testing on my Ultra60 together with a 2.6.12 kernel. I wonder how to get the type5 keyboard to work with xorg. What is the right keyboard layout to select? Since for the 2.6.x series kernel the keycodes get translated to a PC-style keyboard, i am using the pc104 layout. This gives basic functionality, however the function block on the left as well as the volume keys produces no keysyms. The sun rules will not work at all, because they rely on untranslated keycodes. Is there any other layout, which supports the type5 keyboard on the 2.6 kernel? Thanks. Christian Christian, I feel better that I am not the only one with this problem. Hmmm... You are using 2.6.12 kernel. I am using 2.4. Let me upgrade and see what happens... 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 This gives basic functionality I cannot get anything usable in X (using X.org) with either kernel. Could you post your xorg.conf file? Thanks, Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
