Re: [SLE] SuSE 7.1 install on Toshiba Tecra 8000 Laptop
Hello Rob,
Did you ever get your sound working on this Toshiba? I have used the values listed in my BIOS as well and can not get it working.
I am answering your question in the list because
a) it may interest someone else
b) it is not denfinetly solved and perhaps we can discuss it again.
I got sound working on my laptop Toshiba Tecra8000DVD after asking to this
list several times, to SuSE installation support, and reading some of the
papers that are around about this laptop on linux.
Basically, what I added the following config at the end of my
/etc/modules.conf:
### Sound modules for YamahaOPL ###
alias char-major-14 opl3sa2
pre-install opl3sa2 modprobe "-k" ad1848
post-install opl3sa2 modprobe "-k" opl3
options opl3sa2 dma=1 dma2=0 io=0x538 irq=5 mpu_io=0x330 mss_io=0x530
options opl3 io=0x388
These values match with values I have in BIOS setup.
In kernel sound drivers must be active.
also in your /etc/rc.config you turn off your isapnp and alsa:
START_ISAPNP="no"
START_ALSA="no"
So far is ok. However... I can not use my sound car to record anything... and
I always get the following messages (/var/log/messages) everytime I start KDE:
Oct 31 12:14:15 petit kernel: isapnp: Scanning for PnP cards...
Oct 31 12:14:15 petit kernel: isapnp: No Plug & Play device found
Oct 31 12:14:14 petit insmod: insmod: a module named isa-pnp already exists
Oct 31 12:14:15 petit insmod: insmod: insmod char-major-14 failed
Oct 31 12:14:15 petit modprobe: modprobe: Can't locate module sound-slot-0
Oct 31 12:14:15 petit modprobe: modprobe: Can't locate module
sound-service-0-0
Oct 31 12:14:15 petit modprobe: modprobe: Can't locate module sound-slot-0
Oct 31 12:14:15 petit modprobe: modprobe: Can't locate module
sound-service-0-0
Oct 31 12:14:15 petit modprobe: modprobe: Can't locate module sound-slot-1
Oct 31 12:14:15 petit modprobe: modprobe: Can't locate module
sound-service-1-0
Oct 31 12:14:15 petit modprobe: modprobe: Can't locate module sound-slot-1
Oct 31 12:14:15 petit modprobe: modprobe: Can't locate module
sound-service-1-0
Oct 31 12:14:16 petit kernel: ad1848/cs4248 codec driver Copyright (C) by
Hannu Savolainen 1993-1996
Oct 31 12:14:17 petit kernel: opl3sa2: No PnP cards found
Oct 31 12:14:17 petit kernel: opl3sa2: Search for a card at 0x1336.
Oct 31 12:14:17 petit kernel: opl3sa2: chipset version = 0x5
Oct 31 12:14:17 petit kernel: opl3sa2: Found OPL3-SA3 (YMF715E or YMF719E)
Oct 31 12:14:17 petit kernel: <OPL3-SA3> at 0x538
Oct 31 12:14:17 petit kernel:
Pep, I missed the beginning of this thread, so you might have already tried some of the things below, but just in case... Pep Serrano wrote:
So far is ok. However... I can not use my sound car to record anything... and I always get the following messages (/var/log/messages) everytime I start KDE:
(Incidentally, is there more information in /var/log/boot.msg?)
Oct 31 12:14:15 petit kernel: isapnp: Scanning for PnP cards... Oct 31 12:14:15 petit kernel: isapnp: No Plug & Play device found
This is strange. It looks like you have ISA PnP built into the kernel, but that it can't find any PnP cards - yet you clearly have one. Is your BIOS set to say that the OS is a PnP OS, or are you setting the card yourself in the BIOS?
Oct 31 12:14:17 petit kernel: opl3sa2: No PnP cards found Oct 31 12:14:17 petit kernel: opl3sa2: Search for a card at 0x1336.
This is a bug :) It means searching at 1336 decimal (=0x538, as you'd expect). It's harmless, if confusing. I'm not clear whether this is from a built-in oplsa3 driver, or a loaded module. Is opl3sa2 loaded as a module or not?
Oct 31 12:14:17 petit kernel: opl3sa2: Control I/O port 0x538 not free Oct 31 12:14:17 petit kernel: opl3sa2: There was a problem probing one of the ISA PNP cards, continuing
This also appears to be an opl3sa2 or isapnp bug, but I'm still trying to figure out where - I have the same problem. Luckily it's harmless AFAICS. You might be able to get rid of these errors by adding the option "multiple=0" to the opl3sa2 options line (if its a module). This tells the system you only have one sound card (assuming you have!). You could also try adding "isapnp=0" if you have set up the card yourself in the BIOS (ie. you're not depending on the driver to do the PnP setup). If you're using the command line to pass options to the built in driver, isapnp and multiple are the last two arguments in the list (see drivers/sound/opl3sa2.c for the order of the args, then add something like append = "opl3sa2=0x538,<stuff>,0,0" to your lilo.conf). Cheers, -nick
Hello all,
I missed the beginning of this thread, so you might have already tried some of the things below, but just in case... Let's get back again into the subject... I was also absent, sorry...
Pep Serrano wrote:
So far is ok. However... I can not use my sound car to record anything... and I always get the following messages (/var/log/messages) everytime I start KDE:
(Incidentally, is there more information in /var/log/boot.msg?)
No. There are no messages relating sound card in boot.msg
Oct 31 12:14:15 petit kernel: isapnp: Scanning for PnP cards... Oct 31 12:14:15 petit kernel: isapnp: No Plug & Play device found
This is strange. It looks like you have ISA PnP built into the kernel, but that it can't find any PnP cards - yet you clearly have one. Is your BIOS set to say that the OS is a PnP OS, or are you setting the card yourself in the BIOS?
The sound card is set in the BIOS, and I use the same parameters later when configuring my /etc/modules.conf In /etc/rc.config I have START_ISAPNP="NO" because I am not using it... perhaps I am wrong?
Oct 31 12:14:17 petit kernel: opl3sa2: No PnP cards found Oct 31 12:14:17 petit kernel: opl3sa2: Search for a card at 0x1336.
This is a bug :) It means searching at 1336 decimal (=0x538, as you'd expect). It's harmless, if confusing.
I'm not clear whether this is from a built-in oplsa3 driver, or a loaded module. Is opl3sa2 loaded as a module or not?
I do load oplsa3 as a module.
Oct 31 12:14:17 petit kernel: opl3sa2: Control I/O port 0x538 not free Oct 31 12:14:17 petit kernel: opl3sa2: There was a problem probing one of the ISA PNP cards, continuing
This also appears to be an opl3sa2 or isapnp bug, but I'm still trying to figure out where - I have the same problem. Luckily it's harmless AFAICS. You might be able to get rid of these errors by adding the option "multiple=0" to the opl3sa2 options line (if its a module). This tells the system you only have one sound card (assuming you have!). You could also try adding "isapnp=0" if you have set up the card yourself in the BIOS (ie. you're not depending on the driver to do the PnP setup).
Ok, I'll try with multiple=0 and isapnp=0 and I'll tell you how it goes. By the way, did you use pnp to configure your card??? Is it better???
If you're using the command line to pass options to the built in driver, isapnp and multiple are the last two arguments in the list (see drivers/sound/opl3sa2.c for the order of the args, then add something like append = "opl3sa2=0x538,<stuff>,0,0" to your lilo.conf).
I guess I add these arguments in my /etc/modules.conf ? Cheers, Pep.
Hi Pep, Pep Serrano wrote:
The sound card is set in the BIOS, and I use the same parameters later when configuring my /etc/modules.conf In /etc/rc.config I have START_ISAPNP="NO" because I am not using it... perhaps I am wrong?
No, that sounds reasonable - though this will only stop the rc scripts from using the isapnptools to set things up. If you have ISAPnP built into the kernel, then it will still try to set the cards (all this is "as I understand it"!). From what I remember, your boot messages lead me to believe PnP was built in - do you see /proc/isapnp (should show the OPL3-SA2 device and its various optional resource sets)? I don't think PnP can change the BIOS-set values, so this should just give complaints at boot time (no PnP cards found?), assuming you do have it built in. Alternatively, you could tell your BIOS you have a PnP OS and let the built-in PnP set the card as I do.
I do load oplsa3 as a module.
OK.
Ok, I'll try with multiple=0 and isapnp=0 and I'll tell you how it goes. By the way, did you use pnp to configure your card??? Is it better???
Well, it works! I fell over the driver bugs I mentioned, but they seem harmless and easy to avoid - the "multiple=0" stops the error messages in my case. I've told my BIOS that I have a PnP OS (I'm dual boot win95 anyway), and I'm using PnP built into the kernel rather than isapnptools. Curiously, my PnP allocates the card at the 0x100 base address, rather than the priority default of 0x370. I'm still trying to figure out why that might be... but opl3sa2 seems happy to use the card located there.
I guess I add these arguments in my /etc/modules.conf ?
Yes. It's much easier via modules.conf as you can name the individual args. If you use an append line in lilo.conf (for built in drivers) you have to give quite a long string of comma separated args for opl3sa2... easy to get one wrong! Cheers, -nick
Hello back again guys,
I don't know is this thread interest anymore to the list... I leave it up to
you to post replies in the list or to keep chating in private.
You were right... I had PnP support configured in my kernel... And so, I
tried to change my BIOS to use PnP.
Now I have a more nice message in /var/log/messages:
root@petit:/home/pep > tail -30 /var/log/messages | grep opl
Nov 7 09:29:01 petit kernel: opl3sa2: No PnP cards found
Nov 7 09:29:01 petit kernel: opl3sa2: Search for a card at 0x1336.
Nov 7 09:29:01 petit kernel: opl3sa2: chipset version = 0x5
Nov 7 09:29:01 petit kernel: opl3sa2: Found OPL3-SA3 (YMF715E or YMF719E)
Nov 7 09:29:01 petit kernel: opl3sa2: Control I/O port 0x538 not free
Nov 7 09:29:01 petit kernel: opl3sa2: There was a problem probing one of
the ISA PNP cards, continuing
Nov 7 09:29:01 petit kernel: opl3sa2: Control I/O port 0x538 not free
Nov 7 09:29:01 petit kernel: opl3sa2: There was a problem probing one of
the ISA PNP cards, continuing
Nov 7 09:29:01 petit kernel: opl3sa2: Control I/O port 0x538 not free
Nov 7 09:29:01 petit kernel: opl3sa2: There was a problem probing one of
the ISA PNP cards, continuing
root@petit:/home/pep >
So, I think I'll keep using PnP config.
But there are again some questions:
1. Why do I get the first line "Nov 7 09:29:01 petit kernel: opl3sa2: No PnP
cards found" ?
2. And what about the messages "opl3sa2:Control I/O port 0x538 not free" and
"opl3sa2: There was a problem probing one of the ISA PNP cards, continuing" ?
3. Should I activate START_ISAPNP in my /etc/rc.config now???
4. What should I put in my /etc/modules.conf??? So far I had all address
parameters hardcoded... but now they are discovered by PnP... so what should
I put in it???
5. For the moment Pnp support in compiled in the kernel. Is there anything
that stops me from compiling it as a module?
--
Best Regards,
Pep Serrano
Hi Pep, Pep Serrano wrote:
I don't know is this thread interest anymore to the list... I leave it up to you to post replies in the list or to keep chating in private.
I think the "port XXX not free" problem should be of interest to (and be seen by) lots of people - its why *I'm* on this thread!
1. Why do I get the first line "Nov 7 09:29:01 petit kernel: opl3sa2: No PnP cards found" ?
Yes, this is strange. If you look at the driver (drivers/sound/opl3sa2.c) you'll see it means that PnP has failed to allocate the first of multiple cards. I can't explain why PnP can't see your single card. What does /proc/isapnp show? Are you sure the BIOS isn't setting the device any more? Were there earlier messages in the boot sequence from the PnP module itself? It should have said "Yes, I spy a YAMAHA OPL3-SA card here" (or words to that effect).
2. And what about the messages "opl3sa2:Control I/O port 0x538 not free" and "opl3sa2: There was a problem probing one of the ISA PNP cards, continuing" ?
This is the bug I referred to before. I CCd you on the fix I posted to the maintainer. What's happening is that, on failing to find the card with PnP, it's using the parameters you passed to the module to initialize all four (possible) cards - the first works, but the other three fail because (duh!) they're trying to allocate the same resources (same io port etc). The work-round is to disable multiple cards or not pass any parameters; the fix is a small re-code in the driver. The good news is that these messages are harmless.
3. Should I activate START_ISAPNP in my /etc/rc.config now???
No, I don't think so (well... we can experiment with it later perhaps!). That would enable the isapnptools script (using /etc/isapnp.conf) to try to PnP-setup your device, as I understand it. That would just repeat what the kernel tried (and failed) to do.
4. What should I put in my /etc/modules.conf??? So far I had all address parameters hardcoded... but now they are discovered by PnP... so what should I put in it???
My opl3sa is built in, but it looks like you should just be able to load the module and not give it any parameters, since all the base addresses will be allocated by PnP. You might just want to have "multiple=0" to supress the errors above. In my lilo.conf, I used to have a long append line to define parameters to opl3sa, but I've now removed this (and PnP finds the card OK). So your modules.conf should be as you have it, except for "options opl3sa2 multiple=0".
5. For the moment Pnp support in compiled in the kernel. Is there anything that stops me from compiling it as a module?
No, AFAIK you can do that and it should work just the same. The driver code says things like "#if defined CONFIG_ISAPNP || defined CONFIG_ISAPNP_MODULE" round the PnP calls, so it looks like its expecting PnP to be either. Cheers, -nick
Finally I moved back to hardcoding the parameters on the driver. I tried to setup my BIOS to work for PNP and then I removed my driver parameters from /etc/modules.conf At that point I could not load sound drivers anymore. In the other hand, when I setup parameters for the driver... it works. Yet it gives some error messages. As I have pnp support in my kernel (I do use it for USB) I get some confusing message that makes me think it could be detecting the card by means of pnp. Actually, it tries to use pnp but are the parameters set in /etc/modules.conf what makes it work... If I comment out this parameters sound goes silent :-( So far, I have sound working... but just play... I never could reach to record anything. Have you tried sucessfully???
Hi Pep, Pep Serrano wrote:
As I have pnp support in my kernel (I do use it for USB) I get some confusing message that makes me think it could be detecting the card by means of pnp.
Confusing? When my (in-kernel) PnP is starting, it states quite clearly that it's found an OPL3-SA2 card. I usually look in boot.msg. What are you getting? Also, what does /proc/isapnp show (do you have such a file?)?
Actually, it tries to use pnp but are the parameters set in /etc/modules.conf what makes it work... If I comment out this parameters sound goes silent :-(
Hmmm. So it was serious when it said "No PnP cards found". That would explain why the module parameters are being used, and why you get the list of "not free" errors (because it uses them four times, in error).
So far, I have sound working... but just play... I never could reach to record anything. Have you tried sucessfully???
I don't have a microphone. I think recording is a separate problem. We're still trying to solve why PnP can't set the card. I guess if the driver is happy to load from the module parameters you don't *need* PnP and we can try to clear up the boot errors sometime. I can't explain why you then can't record, unless you've given the device the wrong parameters. Have you had this working with other distros or other OSs? If so... presumably you're using the same parameters? :^) Cheers, -nick
Hi again Nick,
Confusing? When my (in-kernel) PnP is starting, it states quite clearly that it's found an OPL3-SA2 card. I usually look in boot.msg. What are you getting? Also, what does /proc/isapnp show (do you have such a file?)?
For the moment I have PnP in kernel (it is also set in the BIOS) and it does not find any sound card (i check messages in /var/log/messages and /var/log/boot.msg. There is just a message that says kernel was unable to find any PNP sound card. By the way, I have no /proc/isapnp... If i do not configure parameters for the driver in modules.conf it does not work. Otherwise there is no sound.
I don't have a microphone. I think recording is a separate problem. We're still trying to solve why PnP can't set the card. I guess if the driver is happy to load from the module parameters you don't *need* PnP and we can try to clear up the boot errors sometime. I can't explain why you then can't record, unless you've given the device the wrong parameters.
Parameters are the right ones from BIOS
But there is a small difference in the MS Sound System address (530 and 534):
[from config in modules.conf]
options opl3sa2 dma=1 dma2=0 io=0x538 irq=5 mpu_io=0x330 mss_io=0x530
multiple=0
[from log]
Nov 7 19:16:10 petit kernel: <OPL3-SA3> at 0x538
Nov 7 19:16:10 petit kernel:
Pep Serrano wrote:
By the way, I have no /proc/isapnp...
Looks like PnP just isn't working. That's worrying, but I doubt whether it's causing the problems with recording, assuming sound works at all.
Parameters are the right ones from BIOS But there is a small difference in the MS Sound System address (530 and 534):
[from config in modules.conf] options opl3sa2 dma=1 dma2=0 io=0x538 irq=5 mpu_io=0x330 mss_io=0x530 multiple=0
These numbers (and their names!) are very confusing. If you've read various HOWTOs and whatnots about opl3sax they sometimes use different names too. In the end - for some clarity! - I wrote to Yamaha, who I must say were very helpful. They pointed me at the tech specification for the device. This explains what the various port settings are (well, they're in there... along with a lot of very complicated stuff!). It's at http://www.yamaha.com/lsi/products/pdf/4MF715E20.pdf (Strictly this is for the SA3, but we think this is a re-badged SA2). I don't know whether that helps.
Isn't it funny???
Exhausting more like! :( Cheers, -nick
participants (2)
-
Nick Battle -
Pep Serrano