XOpup Interest Group. Puppy Linux for the OLPC XO-1 laptop
Yes, I have those exact messages in my dmesg, but much earlier (I guess those are elapsed seconds in the column down the left of a dmesg output!). I get them at 23.75-23.83 sec.
I think totally apart from user-initiated alsaconf, ALSA is activated by /etc/rc.d/rc.sysinit & /etc/rc.d/services.
I don't have a clue what to do with this.
I googled "puppy alsa cs5535" and it turns up a few items, mostly from a couple of years ago. I have found nothing definitive thus far however.
I think totally apart from user-initiated alsaconf, ALSA is activated by /etc/rc.d/rc.sysinit & /etc/rc.d/services.
I don't have a clue what to do with this.
I googled "puppy alsa cs5535" and it turns up a few items, mostly from a couple of years ago. I have found nothing definitive thus far however.
Aitch,
Thank you for the links, I will check them out.
I don't seem to have an ac97 module, but I do have a snd_ac97_codec module, and it seems to modprobe and modinfo O.K., along with its dependencies.
I did try adding "pfix=irq" to my bootfile, but it did not seem to make any difference.
Thanks for the interest, keep up the suggestions!
Thank you for the links, I will check them out.
I don't seem to have an ac97 module, but I do have a snd_ac97_codec module, and it seems to modprobe and modinfo O.K., along with its dependencies.
I did try adding "pfix=irq" to my bootfile, but it did not seem to make any difference.
Thanks for the interest, keep up the suggestions!
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Regarding audio, the fix might be as simple as re-loading the ALSA driver with extra parameters.
Try this -
or
If no luck, I see some sketchy information on the web to suggest that OLPC support in the snd-cs5535audio driver depends on the cs5535_gpio driver (for AMD CS5535/CS5536 GPIO Geode companion device).
If true, you might need to compile your kernel modules again to include the cs5535_gpio module. In menuconfig, it's found at -
Device Drivers > Character devices > AMD CS5535/CS5536 GPIO (Geode Companion Device)
... and you will probably need to recompile the snd-cs5535audio driver afterwards.
Try this -
Code: Select all
rmmod snd-cs5535audio
modprobe snd-cs5535audio enable=true
Code: Select all
rmmod snd-cs5535audio
modprobe snd-cs5535audio enable=true ac97_quirk=inv_eapd
If true, you might need to compile your kernel modules again to include the cs5535_gpio module. In menuconfig, it's found at -
Device Drivers > Character devices > AMD CS5535/CS5536 GPIO (Geode Companion Device)
... and you will probably need to recompile the snd-cs5535audio driver afterwards.
sound
tempestuous
thanks a lot for the suggestions
cs5535_gpio is included as a module by default in OLPC kernels
modprobe snd-cs5535audio enable=true give "no such option" as well as
modprobe snd-cs5535audio enable=true ac97_quirk=inv_eapd while
modprobe snd-cs5535audio ac97_quirk=inv_eapd goes through but with the same end result
I dumped the alsaconf output to a file and there I see these
in the depmod step
(Parenthesis: this always confuses me in puppy. depmod/modprobe appear to require the full module path and when the default /lib/modules/`uname -r`/ prefix is assumed, fail End Parenthesis)
Then at mixer setup
and finally
The other bit of info is that in Fedora/OLPC there are 2 settings for alsa/oss in modprobe.conf (actually in /etc/modprobe.d/dist-alsa.conf and dist-oss.conf)
and
I tried them both in /etc/modprobe.conf but no luck (though we may need to try a bit more on that since "--ignore-install" is not a recognized option in puppy)
Any suggestion?
Thx again
thanks a lot for the suggestions
cs5535_gpio is included as a module by default in OLPC kernels
modprobe snd-cs5535audio enable=true give "no such option" as well as
modprobe snd-cs5535audio enable=true ac97_quirk=inv_eapd while
modprobe snd-cs5535audio ac97_quirk=inv_eapd goes through but with the same end result
I dumped the alsaconf output to a file and there I see these
Code: Select all
modinfo: could not open kernel/sound/core/snd.ko: No such file or directory
modinfo: could not open kernel/sound/core/snd.ko: No such file or directory
modinfo: could not open kernel/sound/core/snd.ko: No such file or directory
(Parenthesis: this always confuses me in puppy. depmod/modprobe appear to require the full module path and when the default /lib/modules/`uname -r`/ prefix is assumed, fail End Parenthesis)
Then at mixer setup
Code: Select all
Setting default volumes...
amixer: Mixer attach default error: No such device
Code: Select all
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:4154:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4154:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:4154:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:4633:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM default
aplay: main:608: audio open error: No such device
Saving the mixer setup used for this in /etc/asound.state.
/usr/sbin/alsactl: save_state:1502: No soundcards found...
Code: Select all
# ALSA Sound Support
#
# We want to ensure that snd-seq is always loaded for those who want to use
# the sequencer interface, but we can't do this automatically through udev
# at the moment...so we have this rule (just for the moment).
#
# Remove the following line if you don't want the sequencer.
install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-seq
Code: Select all
# OSS Sound Support
# This has been disabled in F11 onwards because it can interfere with the
# PulseAudio sound service (a legacy OSS application can prevent PulseAudio
# applications from playing sound by preventing PulseAudio from (re-)opening
# the sound device). To re-enable support, uncomment the following line:
#
# install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-pcm-oss && /sbin/modprobe snd-seq-device && /sbin/modprobe snd-seq-oss
Any suggestion?
Thx again
Last edited by mavrothal on Sat 08 May 2010, 07:43, edited 1 time in total.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Without me having to read all 23 pages of this thread, can someone tell me exactly what kernel is under discussion here?mavrothal wrote:cs5535_gpio is included as a module by default in OLPC kernels
I see that eowens2 appears to be modifying the Puppy 4.31 kernel, and I know for a fact that the cs5535_gpio module is not included in Puppy 4.31 as standard.
But when you guys do recompile a kernel (whatever kernel version that might be) you should enable the cs5535_gpio module, and rebuild the snd-cs5535audio module at the same time.
THEN it might be worth loading the cs5535_gpio module at boot up ... because the (updated) snd-cs5535audio module may rely on it for OLPC-specific functions.
If the snd kernel module cannot be located, someone has made a major stuff-up ...mavrothal wrote:Code: Select all
modinfo: could not open kernel/sound/core/snd.ko: No such file or directory
and this is clearly not the same situation as exists for eowens2, because I see the snd module listed in eowens2's lsmod output.
Eowens2 and I are not using the same kernels (I think). However, we both use an OLPC modified 2.6.31 kernel patched for Aufs2 (I believe).tempestuous wrote:Without me having to read all 23 pages of this thread, can someone tell me exactly what kernel is under discussion here?mavrothal wrote:cs5535_gpio is included as a module by default in OLPC kernels
I see that eowens2 appears to be modifying the Puppy 4.31 kernel, and I know for a fact that the cs5535_gpio module is not included in Puppy 4.31 as standard.
But when you guys do recompile a kernel (whatever kernel version that might be) you should enable the cs5535_gpio module, and rebuild the snd-cs5535audio module at the same time.
THEN it might be worth loading the cs5535_gpio module at boot up ... because the (updated) snd-cs5535audio module may rely on it for OLPC-specific functions.
If the snd kernel module cannot be located, someone has made a major stuff-up ...mavrothal wrote:Code: Select all
modinfo: could not open kernel/sound/core/snd.ko: No such file or directory
and this is clearly not the same situation as exists for eowens2, because I see the snd module listed in eowens2's lsmod output.
In my case (with the version at hand) I have the entire kernel in initrd/lib/modules and all the aforementioned modules are loaded and present in lsmod output. However, depmode-FULL still complains that can not be found though the module is loaded and alsaconf proceeds normally and reports success.
As you may see in the (added) parenthesis in my previous post the full module path is needed for the modprobe to work.
If modules.dep is in the "kernel/driver/whaterver.ko" format it does not work. If it is in the "/lib/modules/kernel_ver/kernel/driver/whatever.ko" is OK ???
Edit: Crash course in (my) puppy-xo kernels.
Build a kernel.rpm in a Fedora 11 machine.
Install on the XO-1 running Fedora11. Check that everything works on the XO-1 running this kernel.
Modify the puppy initrd.gz by removing the lib/modules/puppy_kernel_ver and replace with the /lib/modules/puppy-xo-kernel_ver from the F11 running XO-1 .
Edit the modules.dep to include the full path (Required. Is this way in the original initrd too. When booted the /lib/modules/kern_ver/modules.dep has the "normal" format)
add "modprobe usb-libusual" in initrd/init (not needed if the full kernel is used in initrd)
Done.
To minimize sfs size and possible conflicts, remove from the puppy_variant.sfs
/lib/modules/puppy_kernel_ver/
/lib/modules/all-firmware/
/lib/firmware/* (and add usb8388.bin in it).
Edit /etc/modprobe.conf with the XO-1 F11 configuration (optional)
Delete unneeded video drivers (optional)
Repack the sfs.
Replace Puppy vmlinuz with the one from the puppy-xo kernel
Your XOpup is ready for testing
Last edited by mavrothal on Wed 12 May 2010, 16:10, edited 2 times in total.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
It actually is! I guess eowens2 did not catch it because it just flies by.tempestuous wrote:If the snd kernel module cannot be located, someone has made a major stuff-up ...mavrothal wrote:Code: Select all
modinfo: could not open kernel/sound/core/snd.ko: No such file or directory
and this is clearly not the same situation as exists for eowens2, because I see the snd module listed in eowens2's lsmod output.
Here is the modinfo and lsmod in my case
Code: Select all
# modinfo snd
filename: /lib/modules/2.6.31_xo1-20100507.1858.1.olpc.7223ce6_PuppyPatched/kernel/sound/core/snd.ko
alias: char-major-116-*
license: GPL
description: Advanced Linux Sound Architecture driver for soundcards.
author: Jaroslav Kysela <perex@perex.cz>
srcversion: DB7976AF0DFD038DB4F46CD
depends:
vermagic: 2.6.31_xo1-20100507.1858.1.olpc.7223ce6_PuppyPatched preempt mod_unload modversions GEODE 4KSTACKS
parm: slots:Module names assigned to the slots. (array of charp)
parm: major:Major # for sound driver. (int)
parm: cards_limit:Count of auto-loadable soundcards. (int)
#
# lsmod
Module Size Used by
snd_cs5535audio 5788 0
snd_ac97_codec 66728 1 snd_cs5535audio
snd_pcm 38380 2 snd_cs5535audio,snd_ac97_codec
snd_timer 11120 1 snd_pcm
snd 28404 4 snd_cs5535audio,snd_ac97_codec,snd_pcm,snd_timer
mousedev 6600 1
usb8xxx 10468 0
libertas 116236 1 usb8xxx
lib80211 2272 1 libertas
serio_raw 2520 0
fuse 36028 0
aufs 103476 459
nls_iso8859_1 2804 0
nls_cp437 4336 0
usbhid 15724 0
usb_storage 21344 1
sr_mod 9916 0
cdrom 23828 1 sr_mod
squashfs 15688 1
ohci_hcd 14964 0
ac97_bus 512 1 snd_ac97_codec
snd_page_alloc 4300 2 snd_cs5535audio,snd_pcm
cs5535_gpio 1560 0
cafe_ccic 12244 0
ehci_hcd 23628 0
psmouse 16448 0
usb_libusual 7228 1 usb_storage
usbcore 83268 7 usb8xxx,usbhid,usb_storage,ohci_hcd,ehci_hcd,usb_libusual
Code: Select all
# depmod-FULL snd
FATAL: modules must be specified using absolute paths.
"snd" is a relative path
# depmod snd
depmod: can't stat 'lib/modules/2.6.31_xo1-20100507.1858.1.olpc.7223ce6_PuppyPatched/snd': No such file or directory
#
Any Idea?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
tempestuous, the kernel is from the olpc repository: git clone git://dev.laptop.org/olpc-2.6 and git checkout origin/olpc-2.6.31. We then patched in aufs2 and squashfs. The stock olpc kernel has snd compiled into the body of the kernel, so on re-compile we configured snd as modular.
Theoretically, we could have begun with the Puppy's kernel and patched in the XO's hardware (I did try this a while), but I get the impression that this is a much harder route...see Mitch Bradley's <wmb@firmworks.com>post in this thread from 17 Jan 2010 http://www.murga-linux.com/puppy/viewto ... &start=210. Mitch is one of the developers at OLPC, whose main area of interest is Open Firmware.
When I add the parameters "enable=true with or without ac97_quirk=inv_eapd" to modprobe snd_cs5535audio, I get "Invalid Argument". When I boot Puppy 4.31 to desktop, open a console and do "lsmod", cs5535_gpio is present, though I am not sure where in the boot process it is loaded.
I think that I am at about the same place as Mavrothal. Here is my output:
# lsmod
Module Size Used by
snd_pcm_oss 34044 0
snd_seq_dummy 2660 0
snd_seq_oss 24044 0
snd_seq_midi_event 6724 1 snd_seq_oss
snd_seq 42080 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 6608 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_mixer_oss 14504 1 snd_pcm_oss
snd_cs5535audio 12740 0
snd_ac97_codec 93820 1 snd_cs5535audio
ac97_bus 1660 1 snd_ac97_codec
usb8xxx 14632 0
snd_pcm 64488 3 snd_pcm_oss,snd_cs5535audio,snd_ac97_codec
libertas 141200 1 usb8xxx
snd_timer 18596 2 snd_seq,snd_pcm
lib80211 6256 1 libertas
snd 51500 9 snd_pcm_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_mixer_oss,snd_cs5535audio,snd_ac97_codec,snd_pcm,snd_timer
snd_page_alloc 8404 2 snd_cs5535audio,snd_pcm
serio_raw 5260 0
cafe_ccic 18720 0
cs5535_gpio 3736 0
psmouse 25560 0
ohci_hcd 20028 0
mousedev 11028 1
fuse 52864 0
aufs 119796 1
nls_iso8859_1 3872 0
usb_storage 33356 1
usbhid 24228 0
usb_libusual 20080 1 usb_storage
squashfs 20440 1
ehci_hcd 30124 0
usbcore 132400 7 usb8xxx,ohci_hcd,usb_storage,usbhid,usb_libusual,ehci_hcd
#
# modinfo snd
filename: /lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/kernel/sound/core/snd.ko
alias: char-major-116-*
license: GPL
description: Advanced Linux Sound Architecture driver for soundcards.
author: Jaroslav Kysela <perex@perex.cz>
srcversion: DB7976AF0DFD038DB4F46CD
depends:
vermagic: 2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY preempt mod_unload modversions GEODE 4KSTACKS
parm: slots:Module names assigned to the slots. (array of charp)
parm: major:Major # for sound driver. (int)
parm: cards_limit:Count of auto-loadable soundcards. (int)
#
# depmod-FULL snd
WARNING: Can't read module snd: No such file or directory
FATAL: grab_module() failed for module snd
#
# depmod snd
depmod: can't stat 'lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/snd': No such file or directory
#
The process of getting a modules.dep into the initrd was puzzling. To construct it I did a depmod -b $DIR <kernel_name> where $DIR is the staging directory that contains lib/modules/<kernel_name>. This does create a modules.dep in the right place with the right modules, with a module listing in the form "kernel/fs/aufs/aufs.ko". But this format of the listing leads to "aufs.ko - no such file or directory". Finally, at my wit's end, I added manually "/lib/modules/<kernel_name>/" as a prefix to each listing in modules.dep, and the modules were found and loaded. Afterwards I found that in a pristine puppy 4.31 initrd, the modules.dep listing is the full pathway.
Also interesting is that the modules.dep in /initrd/pup_ro1 has the full pathway whereas the modules.dep for the .sfs (/initrd/pup_ro2) has the abbreviated pathway (i.e. kernel/fs/aufs/aufs.ko) which contains snd.
I do not understand why initrd can find and load modules, but the fully booted OS has difficulty.
Theoretically, we could have begun with the Puppy's kernel and patched in the XO's hardware (I did try this a while), but I get the impression that this is a much harder route...see Mitch Bradley's <wmb@firmworks.com>post in this thread from 17 Jan 2010 http://www.murga-linux.com/puppy/viewto ... &start=210. Mitch is one of the developers at OLPC, whose main area of interest is Open Firmware.
When I add the parameters "enable=true with or without ac97_quirk=inv_eapd" to modprobe snd_cs5535audio, I get "Invalid Argument". When I boot Puppy 4.31 to desktop, open a console and do "lsmod", cs5535_gpio is present, though I am not sure where in the boot process it is loaded.
I think that I am at about the same place as Mavrothal. Here is my output:
# lsmod
Module Size Used by
snd_pcm_oss 34044 0
snd_seq_dummy 2660 0
snd_seq_oss 24044 0
snd_seq_midi_event 6724 1 snd_seq_oss
snd_seq 42080 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 6608 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_mixer_oss 14504 1 snd_pcm_oss
snd_cs5535audio 12740 0
snd_ac97_codec 93820 1 snd_cs5535audio
ac97_bus 1660 1 snd_ac97_codec
usb8xxx 14632 0
snd_pcm 64488 3 snd_pcm_oss,snd_cs5535audio,snd_ac97_codec
libertas 141200 1 usb8xxx
snd_timer 18596 2 snd_seq,snd_pcm
lib80211 6256 1 libertas
snd 51500 9 snd_pcm_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_mixer_oss,snd_cs5535audio,snd_ac97_codec,snd_pcm,snd_timer
snd_page_alloc 8404 2 snd_cs5535audio,snd_pcm
serio_raw 5260 0
cafe_ccic 18720 0
cs5535_gpio 3736 0
psmouse 25560 0
ohci_hcd 20028 0
mousedev 11028 1
fuse 52864 0
aufs 119796 1
nls_iso8859_1 3872 0
usb_storage 33356 1
usbhid 24228 0
usb_libusual 20080 1 usb_storage
squashfs 20440 1
ehci_hcd 30124 0
usbcore 132400 7 usb8xxx,ohci_hcd,usb_storage,usbhid,usb_libusual,ehci_hcd
#
# modinfo snd
filename: /lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/kernel/sound/core/snd.ko
alias: char-major-116-*
license: GPL
description: Advanced Linux Sound Architecture driver for soundcards.
author: Jaroslav Kysela <perex@perex.cz>
srcversion: DB7976AF0DFD038DB4F46CD
depends:
vermagic: 2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY preempt mod_unload modversions GEODE 4KSTACKS
parm: slots:Module names assigned to the slots. (array of charp)
parm: major:Major # for sound driver. (int)
parm: cards_limit:Count of auto-loadable soundcards. (int)
#
# depmod-FULL snd
WARNING: Can't read module snd: No such file or directory
FATAL: grab_module() failed for module snd
#
# depmod snd
depmod: can't stat 'lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/snd': No such file or directory
#
The process of getting a modules.dep into the initrd was puzzling. To construct it I did a depmod -b $DIR <kernel_name> where $DIR is the staging directory that contains lib/modules/<kernel_name>. This does create a modules.dep in the right place with the right modules, with a module listing in the form "kernel/fs/aufs/aufs.ko". But this format of the listing leads to "aufs.ko - no such file or directory". Finally, at my wit's end, I added manually "/lib/modules/<kernel_name>/" as a prefix to each listing in modules.dep, and the modules were found and loaded. Afterwards I found that in a pristine puppy 4.31 initrd, the modules.dep listing is the full pathway.
Also interesting is that the modules.dep in /initrd/pup_ro1 has the full pathway whereas the modules.dep for the .sfs (/initrd/pup_ro2) has the abbreviated pathway (i.e. kernel/fs/aufs/aufs.ko) which contains snd.
I do not understand why initrd can find and load modules, but the fully booted OS has difficulty.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
When you run "modinfo snd" the location of the snd module is reported as:
/lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/kernel/sound/core/snd.ko
But when you run "depmod-FULL" the system expects it here:
/lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/snd
It looks like you have located the snd module in 2 different locations. I'm not sure whether that applies to the normal filesystem, the initrd, or both. You need to investigate, and sort it out.
The correct location is /lib/modules/<kernelversion>/kernel/sound/core
/lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/kernel/sound/core/snd.ko
But when you run "depmod-FULL" the system expects it here:
/lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/snd
It looks like you have located the snd module in 2 different locations. I'm not sure whether that applies to the normal filesystem, the initrd, or both. You need to investigate, and sort it out.
The correct location is /lib/modules/<kernelversion>/kernel/sound/core
eowens2
I can see we have identical behavior, so I was thinking that might be something in the kernel building that Pupy/depmode can not cope with.
Are you building kernel rpms? Have you ever tried just "make"?
Are you building in a fedora Machine? Have you tried in a Puppy machine?
From the kernel naming I can see that you use the olpc/Makefile, did you ever tried with a puppy makefile? (I'm not sure if this thing exists).
I think I have seen that cross post depmode does not work always, so this might be at the root of this problem.
I can see we have identical behavior, so I was thinking that might be something in the kernel building that Pupy/depmode can not cope with.
Are you building kernel rpms? Have you ever tried just "make"?
Are you building in a fedora Machine? Have you tried in a Puppy machine?
From the kernel naming I can see that you use the olpc/Makefile, did you ever tried with a puppy makefile? (I'm not sure if this thing exists).
I think I have seen that cross post depmode does not work always, so this might be at the root of this problem.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
I did rebuild the kernel in Puppy 4.3.1.mavrothal wrote: Are you building in a fedora Machine? Have you tried in a Puppy machine?
The only difference is that indeed the modules.dep file has the full module paths instead of assuming the /lib/modures/`uname -r`/ default location.
However, ALSAwizard/depmod/depmod-FULL/sound has the ECAXT same behavior, as with the fedora-build kernel.
Wizards,...wizards...
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
It looks strange but actually this is normal for puppytempestuous wrote:When you run "modinfo snd" the location of the snd module is reported as:
/lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/kernel/sound/core/snd.ko
But when you run "depmod-FULL" the system expects it here:
/lib/modules/2.6.31_xo1-20100428.0000.1.olpc.628e024_DIRTY/snd
It looks like you have located the snd module in 2 different locations. I'm not sure whether that applies to the normal filesystem, the initrd, or both. You need to investigate, and sort it out.
The correct location is /lib/modules/<kernelversion>/kernel/sound/core
Tried it in 3 different unmodified puppy versions. In all cases
modinfo reports correctly,
depmod-FULL can not find the module (and asks for full path in someversions)
and the trimmed version of depmod looks always for the module at /lib/mudules/`uname -r`/module_name (and never finds it of course).
There is certainly something wrong, but this has nothing to do with the kernels... Also I do not think it has to do with the missing sound either!
I tried alsaconf from another mini-distro. Went through fine, reported success, no errors in /var/log/messages and yet the mixer could not be found when time for testing arrived ???
Just a general question
did anyone ever got sound from cs5535 with any puppy??? and if yes how?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Mavrothal, I have done most of my puppy work on an HP desktop running Ubuntu 9.04 and compiling with gcc-4.3.
I got interested in depmod, and read several man pages on it, and at least one said that when it is followed by a filename as an argument, the output may not be meaningful.
So I took a Puppy 4.3.1 CD and made a fresh copy of 4.3.1 on a USB stick to run on my desktop. I set up ALSA and got the audible two barks test sound clearly.
Opening a terminal, I typed in "depmod snd" and guess what I got?
# depmod snd
depmod: can't stat 'lib/modules/2.6.30.5/snd': No such file or directory
#
and
# depmod-FULL snd
WARNING: Can't read module snd: No such file or directory
FATAL: grab_module() failed for module snd
So the output of these 2 commands on a functioning system fails to provide support to the idea that on our Xopups the snd modules have been placed in two different locations, making them impossible to find.
Back to the drawing boards!
I got interested in depmod, and read several man pages on it, and at least one said that when it is followed by a filename as an argument, the output may not be meaningful.
So I took a Puppy 4.3.1 CD and made a fresh copy of 4.3.1 on a USB stick to run on my desktop. I set up ALSA and got the audible two barks test sound clearly.
Opening a terminal, I typed in "depmod snd" and guess what I got?
# depmod snd
depmod: can't stat 'lib/modules/2.6.30.5/snd': No such file or directory
#
and
# depmod-FULL snd
WARNING: Can't read module snd: No such file or directory
FATAL: grab_module() failed for module snd
So the output of these 2 commands on a functioning system fails to provide support to the idea that on our Xopups the snd modules have been placed in two different locations, making them impossible to find.
Back to the drawing boards!
cs5535
hmmm,
the only other reference to cs5535audio and puppy I could find is from earlytv back in 2008 and guess what?
everything looked fine but the card could not be found
ref1 ref2 ref3
I'm wondering if earlytv is still around
the only other reference to cs5535audio and puppy I could find is from earlytv back in 2008 and guess what?
everything looked fine but the card could not be found
ref1 ref2 ref3
I'm wondering if earlytv is still around
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Hi Guys
More possibilities....
I've read that the CS5535 was used in a WYSE thinclient
Also experimented in DSL
NOTE:
Best result, IMHO, google groups, - patch
http://groups.google.com/group/linux.ke ... 8570ac9ed4
Else ALSA wiki
http://www.alsa-project.org/main/index.php/Main_Page
HTH
Aitch
More possibilities....
I've read that the CS5535 was used in a WYSE thinclient
Also experimented in DSL
NOTE:
http://www.damnsmalllinux.org/f/topic-3-18-20460-0.htmlI got Puppy linux to boot easy but until Puppy 4.1 the sound wouldnt work at all?
Best result, IMHO, google groups, - patch
http://groups.google.com/group/linux.ke ... 8570ac9ed4
Else ALSA wiki
http://www.alsa-project.org/main/index.php/Main_Page
HTH
Aitch
Not really, but thanks.Aitch wrote:
HTH
Aitch
There is nothing wrong with alsa, the cs5535 driver or the kernel. They all work in Fedora, Debian, Ubuntu and TinyCore (that I have checked). Is in puppy that they fail.
Could be something totally unrelated like the ancient bash version that puppy uses, or some of its recompiled stripped libraries that is misinterpreting some cs5535 output. I do not really know. ...
Any other ideas?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Thanks for the links, Aitch!
The DSL link does suggest that that individual did get some sound with a cs5535 chip with Puppy 4.1. I wish there were more details!
I am 99% certain that the Jaya Kumar patches for the kernel mentioned in the google groups have been incorporated into the base kernel from the OLPC repository that we have furthur patched for Puppy. Sound with the CS5535 chip works fine on the base XO running Sugar, it works fine on the XO with Ubuntu Intrepid. It works well on the XO with Debian Squeeze (I just moved "2barks.au" from puppy over to Squeeze and the doggie performs admirably!).
And I have been wandering around www.alsa-project.org for several days, hoping that something will ring a bell (no pun intended).
Thank you for your interest, and keep the suggestions coming!
The DSL link does suggest that that individual did get some sound with a cs5535 chip with Puppy 4.1. I wish there were more details!
I am 99% certain that the Jaya Kumar patches for the kernel mentioned in the google groups have been incorporated into the base kernel from the OLPC repository that we have furthur patched for Puppy. Sound with the CS5535 chip works fine on the base XO running Sugar, it works fine on the XO with Ubuntu Intrepid. It works well on the XO with Debian Squeeze (I just moved "2barks.au" from puppy over to Squeeze and the doggie performs admirably!).
And I have been wandering around www.alsa-project.org for several days, hoping that something will ring a bell (no pun intended).
Thank you for your interest, and keep the suggestions coming!
2.02/2.13
Sound runs in 2.02/2.13, with ISOs available atmavrothal wrote:Just a general question
did anyone ever got sound from cs5535 with any puppy??? and if yes how?
http://minipc.org/pup/ and http://minipc.org/safepup/.
ADD: It's a proprietary BIOS.
Last edited by raffy on Tue 11 May 2010, 09:49, edited 1 time in total.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Re: 2.02/2.13
Thanks!raffy wrote:Sound runs in 2.02/2.13, with ISOs available atmavrothal wrote:Just a general question
did anyone ever got sound from cs5535 with any puppy??? and if yes how?
http://minipc.org/pup/ and http://minipc.org/safepup/.
Board/firmware (if known)?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==