Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Enable Sound - Sunblade 100
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on Sparc
View previous topic :: View next topic  
Author Message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Tue Feb 15, 2005 5:20 am    Post subject: Enable Sound - Sunblade 100 Reply with quote

Hi,

I am trying to enable sound using the onboard sound on my Sunblade 100.

I have had a search & read previous posts but I appear to be missing something because it doesn't appear to be working.

My system...

Linux apollo 2.4.28-sparc-r6 #1 SMP Fri Feb 11 14:39:58 WST 2005 sparc64 sun4u TI UltraSparc IIe (Hummingbird) GNU/Linux


Module Size Used by Not tainted
parport_pc 28200 1 (autoclean)
lp 8920 0 (autoclean)
parport 34304 1 (autoclean) [parport_pc lp]
openpromfs 13784 1 (autoclean)
trident 38776 3
ac97_codec 17208 0 [trident]
soundcore 4836 2 [trident]

I read that version 2.6.x might fix the problem but when I try emerge gentoo-dev-sources

I get the following error message.

!!! All ebuilds that could satisfy "gentoo-dev-sources" have been masked.
!!! One of the following masked packages is required to complete your request:
- sys-kernel/gentoo-dev-sources-2.6.1-r2 (masked by: ~sparc keyword)
- sys-kernel/gentoo-dev-sources-2.6.10-r6 (masked by: ~sparc keyword)
- sys-kernel/gentoo-dev-sources-2.6.10-r7 (masked by: missing keyword)
- sys-kernel/gentoo-dev-sources-2.6.8-r3 (masked by: missing keyword)
- sys-kernel/gentoo-dev-sources-2.6.9-r14 (masked by: missing keyword)
- sys-kernel/gentoo-dev-sources-2.6.9-r9 (masked by: missing keyword)

I'm still quite new to gentoo..

Is there another module that needs to be loaded? Prior to installing Gentoo I had a running version of Aurora (1.0) & the sound worked on that. 2.4 kernel.

TIA
Back to top
View user's profile Send private message
ashu69
n00b
n00b


Joined: 09 Nov 2004
Posts: 45

PostPosted: Tue Feb 15, 2005 9:02 am    Post subject: Reply with quote

I have sound working fine on my Blade150, which ought
to be close enough to the Blade100... Although i have
a ALi M5451 instead of trident.

In general, support for such devices is better in 2.4.x then
in 2.6.x. However, if you are sure that you have choosen
the right driver (and have confirmed that with lspci command),
and you do want 2.6.x, i would suggest going with 2.6.9-r14.
The 2.6.10 series doesn't work with atyfb (you are welcome
to try if you have a non-ati graphics card).

As for the 2.6.x kernel being "masked", that is a very basic
concept in gentoo, have a look at "man emerge". Try
putting "=sys-kernel/gentoo-dev-sources-2.6.9-r14 ~sparc"
in /etc/portage/package.keywords and try
"emerge =gentoo-dev-sources-2.6.9-r14".

HTH
-a
Back to top
View user's profile Send private message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Wed Feb 16, 2005 6:33 am    Post subject: Reply with quote

I am quite happy to keep using a 2.4 kernel.

Output from lspci

0000:00:08.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 01)

When I compiled the kernel the only sound option that I selected was that shown below.

<M> Trident 4DWave DX/NX, SiS 7018 or ALi 5451 PCI Audio Core

Which presumably is responsible for trident.o

I note that you appear to have the same sound-chip. Are you using a different driver?

TIA
Back to top
View user's profile Send private message
ashu69
n00b
n00b


Joined: 09 Nov 2004
Posts: 45

PostPosted: Wed Feb 16, 2005 7:34 am    Post subject: Reply with quote

A ha! We are getting somewhere... My lspci output is the same as yours.
I am using 2.6.9-r14 and here trident and ALI5451 are two *different* drivers.
Code:

egrep -i "trident|5451" .config
# CONFIG_FB_TRIDENT is not set
CONFIG_SND_ALI5451=y
# CONFIG_SND_TRIDENT is not set


I don't remember how it was in 2.4.x. I am probably remembering
some other sound card. I am using the ali5451 ALSA driver with
OSS emulation, and it works flawlessly, YMMV.

HTH
-a
Back to top
View user's profile Send private message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Thu Feb 17, 2005 6:32 am    Post subject: Reply with quote

I'm still struggling with this.

I created the /etc/portage/package.keywords file exactly as suggested.

apollo portage # emerge =gentoo-dev-sources-2.6.9-r14
Calculating dependencies
!!! All ebuilds that could satisfy "=gentoo-dev-sources-2.6.9-r14" have been masked.
!!! One of the following masked packages is required to complete your request:
- sys-kernel/gentoo-dev-sources-2.6.9-r14 (masked by: missing keyword)

For more information, see MASKED PACKAGES section in the emerge man page or
section 2.2 "Software Availability" in the Gentoo Handbook.

:(
Back to top
View user's profile Send private message
ashu69
n00b
n00b


Joined: 09 Nov 2004
Posts: 45

PostPosted: Thu Feb 17, 2005 8:17 am    Post subject: Reply with quote

This is not a good way to do this, but what the heck, emerge
the damned thing using the full ebuild path

emerge /usr/portage/sys-kernel/gentoo-dev-sources/gentoo-dev-sources-2.6.9-r14.ebuild

I do that whenever i am feeling a bit frustated with portage. For things like
libraries and what not (where things depend on other things), this could
create problems, but for a source package, you should be OK.

-a
Back to top
View user's profile Send private message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Sun Feb 20, 2005 10:24 am    Post subject: Reply with quote

That worked. I've downloaded and installed the kernel source.

My first effort to compile it failed with an error message.

For my second pass I used "genkern". It compiled and installed but he modifications to /etc/silo.conf were a bit unclear syntactically.

It pointed it to the new image and rebooted - without an initrd. It mentions hardware detection with initrd enabled.

Anyway the SPARC rebooted with a view error messaged (sigh). When it got the the login prompt (run level 3) I couldn't log in at the console - my USB keyboard didn't work. So I ssh'd in and rebooted back to the previous kernel.

I'll try again on Monday.
Back to top
View user's profile Send private message
ashu69
n00b
n00b


Joined: 09 Nov 2004
Posts: 45

PostPosted: Sun Feb 20, 2005 10:39 am    Post subject: Reply with quote

With 2.6 kernel, i never got keymaps to work with sparc.
Since i have no idea why i need it anyways, i delete it.

I forget what runlevel it runs on, i believe it is the "boot" runlevel.
Hence: rc-update delete keymaps boot

Search in the forums if you are unsure.

I am a bit surprised by your kernel compile failure, that happens
very often with 2.4, never with 2.6. Perhaps you have some conflicting set
of kernel options enabled. Anyhow, you will be happier with 2.6 in the long
run. Enjoy your brand new 2.6 system!

PS: If you ever see system hangs (particularly while accessing cdrom),
boot with ide=nodma. DMA is very flaky on the SunBlades (not sure
whether that is specific to Linux).

-a
Back to top
View user's profile Send private message
hasues
n00b
n00b


Joined: 04 Mar 2004
Posts: 50

PostPosted: Tue Feb 22, 2005 7:48 am    Post subject: Sound on SunBlade 100 Reply with quote

ashu69,
Seeing as your hardware is similar to mine as well, I am curious as to what you are doing differently than me that enables you to use your soundcard? If I try to use mine, it will lock my system. I am using alsa with my system as well, but I have issues using the ioctl-32 piece of ALSA. I have noted there are issues when using this with Sparc, especially when using a 64 bit kernel. Are you using a 64 bit kernel? Secondly, what did you have to do to get sound? I am using 2.6.10, and do you think that has something to do with it? I don't have a problem attempting to downgrade, as I would love to have sound for this workstation.

Haz
_________________
Lettuce, Pickles, hold the mayo!
Back to top
View user's profile Send private message
ashu69
n00b
n00b


Joined: 09 Nov 2004
Posts: 45

PostPosted: Tue Feb 22, 2005 8:39 am    Post subject: Reply with quote

hi hasues,

I am using 2.6.9-r14 instead of 2.6.10 and i am using OSS emulation in
kernel. [So, for example, i disable esd/artsd in KDE.] Here is my kernel .config if it helps you..
Look specifically for sound related options:

http://home.comcast.net/~ashu153/kernel.config

As for lockups, you must use ide=nodma on SunBlades.
I put it in my silo.conf as follows:

Code:

partition=5
root=/dev/hda4
timeout=100
default=k29

image=/image
        label=k29
        append="ide=nodma"


And on the ok prompt, i boot with OK> boot disk0;5
[5 referes to the 5th partition, which is my boot partition. I have to
have a separate boot partition because i am using reiser on my root,
and silo doesn't yet support reiser... but i digress... Your boot partition
can be the same as the root partition if you are using ext3]

You can also boot from the SILO prompt as follows:
Code:

/image root=/dev/hdaXX ide=nodma


As for the 64 bit kernel, that is the only kind on ultrasparc machines (such
as blades), be it Solaris or Linux. So yes, i am using a 64 bit kernel with
32 bit userland, same as everyone else on Linux. [In Solaris, you can have
64 bit userland as well, but i digress again...]

About your 32 bit ioctl problems with ALSA, i don't have any ideas, as i mentioned
earlier, i use OSS emulation and never had any issues.

Hope the above helps, about your lockup problems, i am 99% certain that it
is ide dma related, only in rare cases have i heard of other scenarios (such as
reiserfs related). But then your use of ALSA might be creating its own issues,
i wouldn't know....

I take it that you were able to solve the USB keyboard problem? If so, you are
in the home stretch now :) , just over the next hill lies... a whole new set of
shiny new things.. :D

edit: Hmm... hauses is not the same as w.hill... spaced out on the usb keyboard
thing... :roll:
-a
Back to top
View user's profile Send private message
hasues
n00b
n00b


Joined: 04 Mar 2004
Posts: 50

PostPosted: Tue Feb 22, 2005 12:06 pm    Post subject: A few more questions... Reply with quote

When you say "OSS Emulation" in the kernel...
are you referring to using the OSS kernel drives instead of ALSA?

I imagine I can get this information from your kernel config.

I don't have to use the OK prompt to boot, but okay, I'll take your note.

As far as 32 bit kernels go, I compiled one and my box ran, although it couldn't complete a boot. Maybe it was 64 bit after all, but I know I didn't use the 64 bit compile options. My current one is 64 bit, like you said, that everyone else does.

And yes, I have no problems with the USB keyboard, much less USB memory sticks or anything else.

Thanks for your suggestion though...I will definitely take a look at those parameters for the IDE settings.

Haz
_________________
Lettuce, Pickles, hold the mayo!
Back to top
View user's profile Send private message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Fri Feb 25, 2005 5:21 am    Post subject: Reply with quote

A small advance.


I got frustrated trying to get the 2.6 kernel booting and working. When I tried to enable initrd it locked up.

I tried 2.4.29 instead. I also installed XMMS. Previously I tried to play an audio CD. I noticed in my SunBlade at least that there is no analogue (sound) cable between the DVD player and the motherboard. Does the CD player included with gnome process digital sound?

Once XMMS was installed I tried to play a mp3 file. I got "sound" or should I say loud noise with no discernable pattern and unaffected by moving the volume sliders. The sound appeared both through the built-in speaker and my headphones.

Is there something that needs to be specified when the modules load? From dmesg.

Trident 4DWave/SiS 7018/ALi 5451,Tvia CyberPro 5050 PCI Audio, version 0.14.10h, 11:25:18 Feb 25 2005
trident: ALi Audio Accelerator found at IO 0x1fe02000900, IRQ 7309088
ac97_codec: AC97 codec, id: (Unknown)

I am using the supplied USB keyboard and mouse with my Sun Blade.
Back to top
View user's profile Send private message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Fri Feb 25, 2005 6:32 am    Post subject: Reply with quote

I've just recompiled the 2.6 kernel using ashu69's config file.

It boots but...

I get a number of errors

putfont: PIO_FONT : Function not implement
* Failed to set user font.

AND

SABRE0: Uncorrectable Error, primary error type[DMA Read:Translation Error]
SABRE0: bytemask[00ff] dword_offset[0] was_block(1)
SABRE0: UE AFAR [0000000007efc000]
SABRE0: UE Secondary errors [(none)]
SABRE0: IOMMU Error, type[Invalid Error]
SABRE0: IOMMU TAG(2)[RAW(0000000000c6f800)error(Invalid Error)wr(0)sz(8K)vpg(df000000)]
SABRE0: IOMMU DATA(2)[RAW(0000000

ALSO...

The keyboard doesn't work & I can't login at the console. I have to ssh in to reboot it.
Back to top
View user's profile Send private message
ashu69
n00b
n00b


Joined: 09 Nov 2004
Posts: 45

PostPosted: Fri Feb 25, 2005 7:55 am    Post subject: Reply with quote

@hill: About the keyboard problem... did you remove keymaps from the startup sequence
using
Code:
 rc-update del keymaps
?

About the DMA problems, have you disabled dma, by booting with ide=nodma?
And you did enable the right chipset support? [Mine is ALI15X3, yours is probaby
different..]

I had posted my .config basically for the purpose of matching up the sound
realted entries, not everything.

Another thing you might wanna conside is updating your PROM flash. Mine was
about 2 years old, i like to think that revving it up to the latest one did help at
least with the IDE/PCI stuff.

The PIO_FONT issue is a new one for me. A quick search in the forums
reveals that it is harmless though.

HTH,
-a
Back to top
View user's profile Send private message
hasues
n00b
n00b


Joined: 04 Mar 2004
Posts: 50

PostPosted: Fri Feb 25, 2005 2:37 pm    Post subject: Sound stuff and related Reply with quote

Make sure that you are loading the drivers for your USB controller in /etc/modules.autoload.d/kernel-2.6 (or whatever you are using). Also, make sure you have compiled in support for your drivers for USB keyboards and mice, which I think is part of the event system. I get those errors concerning the font error, but that is because I am not loading frame buffer I believe. If I load frame buffer drivers, I will not get those errors, however my timings are off there and the text is garbled, and since I never intend to use the system without X, I never really worry about it.

I sympathize with your sound issues. I am using Alsa for my SunBlade 100, and the sound quality is horrible when it isn't locking the system. The "ide" setting does not prevent the system from locking up. However, perhaps it is because I am using 2.6.10 and should certain Alsa libs. I don't really know at this point, and when I have a chance to look, I'll see if I can come up with something else. I noticed that in 2.6.10, I do not have the option to load OSS/free drivers.

I received those SABRE errors at one time as well, but it was because I was loading the wrong drivers. Have a look at ashu69's kernel file and configure your kernel from that, that probably will enable you to have the right hardware layout.

Haz
_________________
Lettuce, Pickles, hold the mayo!
Back to top
View user's profile Send private message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Sat Feb 26, 2005 2:37 am    Post subject: Reply with quote

Thanks for all the advice.

I'll fiddle some more when I get back to work on Monday.

I did add the "ide=nodma" clause - it didn't appear to change things.

I hadn't removed keymaps but I will.

When I originally tried to install and OS other than SOLARIS I had heaps of problems trying to boot from CDROM - at whatever speed I recorded them at. In the end I came across someone with similar problems. The recommendation was not to used the latest version of OpenBoot - So I upgraded to 4.5. This solved my install problems (Computer would lock solid after SILO tried to load the kernel previously).

I'll make sure that the USB support for the keyboard is loading correctly.

Have a good weekend.
Back to top
View user's profile Send private message
hasues
n00b
n00b


Joined: 04 Mar 2004
Posts: 50

PostPosted: Sat Feb 26, 2005 8:47 am    Post subject: Reply with quote

I agree. My Sunblade runs indifferently to the "no idedma" statement. I may try another kernel, but even then, if the sound is as bad is it is now, I'd rather add another sound card. On the other hand, I'm using direct ALSA and not OSS emulation through ALSA like ashu69 is. So far if I adjust my clock in KDE or try streaming mp3's from the web, the system locks. If I allow ALSA to use ioctl32 support and try to play sound, it locks.

Haz
_________________
Lettuce, Pickles, hold the mayo!
Back to top
View user's profile Send private message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Mon Feb 28, 2005 9:53 am    Post subject: Reply with quote

Some success - always a good feeling.

I removed "keymaps" - didn't appear to change anything.

I rebooted with the 2.6 kernel. No keyboard. I ssh'd in an manually loaded a few USB modules - the keyboard came to life.

I still see the

putfont: PIO_FONT : Function not implement
* Failed to set user font.

error message.

It is generated by /etc/init.d/consolefont? Can I stop if from running at boot time or is there something that I should either (a) add to the kernel or (b) silo.conf to silence it?

When I try to load the sound driver.

apollo ali5451 # modprobe snd-ali5451.ko
FATAL: Module snd_ali5451.ko not found.

It fail - the file is present though.
Back to top
View user's profile Send private message
hasues
n00b
n00b


Joined: 04 Mar 2004
Posts: 50

PostPosted: Mon Feb 28, 2005 1:18 pm    Post subject: More on progress... Reply with quote

Cool beans on your keyboard stuff...
So take the drivers you had to load, and list each one on a line in /etc/modules.autoload.d/kernel-2.6. Make sure you do that without the .ko extension. You do not have to run consolefont. It seems to me that it is mainly for using framebuffer, which even if you do use it, you don't necessarily have to have it. So I think you can do an rc-update del consolefont. When you use modprobe, again, do not the ".ko" of the modulename you are trying to run. Also, I note that you are trying to load an alsadriver module. Before loading this module, you will need to adjust /etc/modules.d/alsa and configure it according to the documentation in Gentoo's Alsa guide, or at least what is found on the Alsa project webpage documentation. Finally, you shouldn't have to load the alsa modules manually, as there should be a start and stop script located in /etc/init.d/alsasound. DO NOT SET THIS TO START AUTOMATICALLY WITHOUT FIRST TESTING. If you do this, you may make your system unbootable if it locks your system. You will need to test it first. If you want to test it, after modifying /etc/modules.d/alsa, you can:
/etc/init.d/alsasound start

If you then like the way it works and you trust it, then you can:
rc-update add alsasound boot

I have problems with sound locking my system, especially if I attempt to stream audio over the net. Do report your progress please, because if yours works better than mine, I want to compare notes as to what you did differently.

Thanks..

Haz
_________________
Lettuce, Pickles, hold the mayo!
Back to top
View user's profile Send private message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Thu Mar 03, 2005 3:35 am    Post subject: Reply with quote

I notice that a lot of modules.conf files use an "alias' statement. Is this necessary / usual?
Back to top
View user's profile Send private message
w.hill
Tux's lil' helper
Tux's lil' helper


Joined: 23 Jan 2005
Posts: 133
Location: Perth, Western Australia

PostPosted: Thu Mar 03, 2005 10:37 am    Post subject: Reply with quote

I seem to be making a meal of this.

When I emerge alsa-driver after having added ALSA_CARDS="ali5451" to /etc/make.conf I get the following error message.

make[3]: Entering directory `/var/tmp/portage/alsa-driver-1.0.7-r3/work/alsa-driver-1.0.7/acore/ioctl32'
/var/tmp/portage/alsa-driver-1.0.7-r3/work/alsa-driver-1.0.7/include/sndversions.h was updated
sparc-unknown-linux-gnu-gcc -M -D__KERNEL__ -D__isapnp_now__ -DMODULE=1 -I/var/tmp/portage/alsa-driver-1.0.7-r3/work/alsa-driver-1.0.7/include -I/usr/src/linux/include -I/usr/src/linux/include -O2 -m64 -mno-fpu -mcpu=ultrasparc -mcmodel=medlow -ffixed-g4 -fcall-used-g5 -fcall-used-g7 -Wno-sign-compare -D__SMP__ -DCONFIG_SMP -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD -nostdinc -iwithprefix include ioctl32.c pcm32.c rawmidi32.c timer32.c hwdep32.c seq32.c > .depend
cc1: error: -m64 is not supported by this configuration
cc1: error: -mlong-double-64 not allowed with -m64
cc1: error: -mcmodel= is not supported on 32 bit systems
cc1: error: -m64 is not supported by this configuration
cc1: error: -mlong-double-64 not allowed with -m64
cc1: error: -mcmodel= is not supported on 32 bit systems
cc1: error: -m64 is not supported by this configuration
cc1: error: -mlong-double-64 not allowed with -m64
cc1: error: -mcmodel= is not supported on 32 bit systems
cc1: error: -m64 is not supported by this configuration
cc1: error: -mlong-double-64 not allowed with -m64
cc1: error: -mcmodel= is not supported on 32 bit systems
cc1: error: -m64 is not supported by this configuration
cc1: error: -mlong-double-64 not allowed with -m64
cc1: error: -mcmodel= is not supported on 32 bit systems
cc1: error: -m64 is not supported by this configuration
cc1: error: -mlong-double-64 not allowed with -m64
cc1: error: -mcmodel= is not supported on 32 bit systems
make[3]: *** [fastdep] Error 1
make[3]: Leaving directory `/var/tmp/portage/alsa-driver-1.0.7-r3/work/alsa-driver-1.0.7/acore/ioctl32'
make[2]: *** [_sfdep_ioctl32] Error 2
make[2]: Leaving directory `/var/tmp/portage/alsa-driver-1.0.7-r3/work/alsa-driver-1.0.7/acore'
make[1]: *** [dep] Error 1
make[1]: Leaving directory `/var/tmp/portage/alsa-driver-1.0.7-r3/work/alsa-driver-1.0.7'
make: *** [include/sndversions.h] Error 2

!!! ERROR: media-sound/alsa-driver-1.0.7-r3 failed.
!!! Function src_compile, Line 86, Exitcode 2
!!! Make Failed
!!! If you need support, post the topmost build error, NOT this status message.

TIA
Back to top
View user's profile Send private message
hasues
n00b
n00b


Joined: 04 Mar 2004
Posts: 50

PostPosted: Fri Mar 04, 2005 2:08 am    Post subject: Alsa Reply with quote

I didn't do an "emerge", but rather I did a "ebuild".

ebuild /usr/portage/<path to particular e-build> clean

ebuild /usr/portage/<path to particular e-build> unpack

ebuild /usr/portage/<path to particular e-build> compile


when it crashes, I went in the /var/tmp/<package>/work/<package> directory for the Alsa build in question.

Then I did a "sparc64make" in there....

then I did a

ebuild /usr/portage/<path to particular e-build> install



That attempted to make the drivers 64 bit. I don't know how smart this was...perhpas the other guy can talk how he compiled sound as that may be part of my problem.

Haz
_________________
Lettuce, Pickles, hold the mayo!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on Sparc All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum