Re: For those who have no sound in their 32bit chroot
On Fri, 2007-01-26 at 18:08 +1100, Hamish Moffatt wrote: Do you mind posting your /etc/fstab? I want to see if I'm mounting my /x86/dev similarly. # mounts for the i386 chroot /home /var/chroot/i386/home nonebind0 0 /tmp /var/chroot/i386/tmpnonebind0 0 proc /var/chroot/i386/proc procdefaults0 0 /dev /var/chroot/i386/devnonebind0 0 Nothing special. I am using rbind. I wonder if there is a difference between mounting rbind and bind. I will report back about this. What kernel are you using, Hamish? Thanks! -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Hi Þann Föstudagur 26. janúar 2007 17:38 skrifaði Stephen Olander Waters: On Fri, 2007-01-26 at 18:08 +1100, Hamish Moffatt wrote: Do you mind posting your /etc/fstab? I want to see if I'm mounting my /x86/dev similarly. # mounts for the i386 chroot /home /var/chroot/i386/home nonebind0 0 /tmp/var/chroot/i386/tmpnonebind0 0 proc/var/chroot/i386/proc procdefaults0 0 /dev/var/chroot/i386/devnonebind0 0 Nothing special. I am using rbind. I wonder if there is a difference between mounting rbind and bind. I will report back about this. What kernel are you using, Hamish? If I add more to this long discussion. A year ago I needed to set Matlab up in a sarge chroot (because of its libc dependencies). I had some very tricky error message that I spend many hours on until Lennart pointed out to me that it was because of the chroot dev being mounted with bind instead of rbind. My guess is that bind is good enough as long as you don't need device nodes that are in subdirectories. But is there any reason for not using rbind? /Gudjon
Re: For those who have no sound in their 32bit chroot
On Fri, Jan 26, 2007 at 05:47:28PM +0100, Gudjon I. Gudjonsson wrote: If I add more to this long discussion. A year ago I needed to set Matlab up in a sarge chroot (because of its libc dependencies). I had some very tricky error message that I spend many hours on until Lennart pointed out to me that it was because of the chroot dev being mounted with bind instead of rbind. My guess is that bind is good enough as long as you don't need device nodes that are in subdirectories. But is there any reason for not using rbind? As far as I have under stood it the difference is this: If you have mounted: /dev /dev/pts /dev/something else Then bind mount /dev to the chroot will give you: /chroot/dev Doing rbind mount /dev to the chroot will give you: /chroot/dev /chroot/dev/pts /chroot/dev/something So rbind bind mounts everything that is mounted under what you ask for in addition to what you ask for, while bind only does the thing you ask for (and ignores any mounts below it). rbind does NOT however mount anything mounted under the original mount done after the rbind is done. So unfortunately it won't automatically add any new mounts you do for you, so it is of no use for people trying to do things with automount or autofs or the like. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
On Fri, Jan 26, 2007 at 10:38:34AM -0600, Stephen Olander Waters wrote: On Fri, 2007-01-26 at 18:08 +1100, Hamish Moffatt wrote: Do you mind posting your /etc/fstab? I want to see if I'm mounting my /x86/dev similarly. # mounts for the i386 chroot /home /var/chroot/i386/home nonebind0 0 /tmp/var/chroot/i386/tmpnonebind0 0 proc/var/chroot/i386/proc procdefaults0 0 /dev/var/chroot/i386/devnonebind0 0 Nothing special. I am using rbind. I wonder if there is a difference between mounting rbind and bind. I will report back about this. What kernel are you using, Hamish? 2.6.17-1-amd64-k8-smp (I use .17 as 2.6.18-1-amd64 + the latest nvidia driver in unstable causes a kernel oops for me which does not occur with .17.) To confirm that ALSA works correctly, I just used aplay within the chroot successfully. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
On 25 Jan 2007, [EMAIL PROTECTED] wrote: It wouldn't surprise me. E.g., ALSA does not work in a 32-bit chroot, but the old OSS does. ALSA works fine here in a 32-bit chroot. I sometimes use 32-bit mplayer as it has access to win32 codecs. Really??? You're sure it's not falling back on the OSS driver? I can't get ALSA to show up in wine either. I thought the bug that Goswin mentioned was the problem. Would like to hear if it is otherwise. -- Alok Any given program will expand to fill available memory. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
On Wed, Jan 24, 2007 at 04:15:53PM -0600, Stephen Olander Waters wrote: On Thu, 2007-01-25 at 08:14 +1100, Hamish Moffatt wrote: On Wed, Jan 24, 2007 at 08:42:59AM -0600, Stephen Olander Waters wrote: It wouldn't surprise me. E.g., ALSA does not work in a 32-bit chroot, but the old OSS does. ALSA works fine here in a 32-bit chroot. I sometimes use 32-bit mplayer as it has access to win32 codecs. Really??? You're sure it's not falling back on the OSS driver? It says it's using ALSA. Do you mind posting your /etc/fstab? I want to see if I'm mounting my /x86/dev similarly. # mounts for the i386 chroot /home /var/chroot/i386/home nonebind0 0 /tmp/var/chroot/i386/tmpnonebind0 0 proc/var/chroot/i386/proc procdefaults0 0 /dev/var/chroot/i386/devnonebind0 0 Nothing special. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Hi Mattias Gudjon I. Gudjonsson [EMAIL PROTECTED] writes: xoscope is a software oscilloscope that only works on 32 bit machines and comedi is a library to access several IO cards. I ported xoscope amd64 (if anyone is interested) and then it works with comedi but not if I run the 32 bit version in chroot. My guess was that I could solve that pussle by using static /dev in the chroot but obviously that is not an option. As Goswin has pointed out a 32 bit program can not call a 64 bit library. You would need to install the 32 bit version of that library in your chroot. Or is it a kernel module that you are trying to use? Yes, sorry, I sometimes forget to mention relevant information. I was only using the 64 bit kernel modules and 32 bit library in chroot and it did not work. But after porting the application to 64 bit it worked like charm. /Gudjon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Gudjon I. Gudjonsson [EMAIL PROTECTED] writes: Yes, sorry, I sometimes forget to mention relevant information. I was only using the 64 bit kernel modules and 32 bit library in chroot and it did not work. But after porting the application to 64 bit it worked like charm. Then you should be able to debug the application and see wether the device file is actually opened or not. Could it be that this is some data type issue that both the kernel module and the application use a type for communication that has a different size on a 32 bit platform and on a 64 bit platform? This way the 32 bit application would only work with a 32 bit kernel and the 64 bit application only with a 64 bit kernel. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
On Wed, 2007-01-24 at 08:24 -0500, Matthias Julius wrote: Gudjon I. Gudjonsson [EMAIL PROTECTED] writes: Yes, sorry, I sometimes forget to mention relevant information. I was only using the 64 bit kernel modules and 32 bit library in chroot and it did not work. But after porting the application to 64 bit it worked like charm. Then you should be able to debug the application and see wether the device file is actually opened or not. Could it be that this is some data type issue that both the kernel module and the application use a type for communication that has a different size on a 32 bit platform and on a 64 bit platform? This way the 32 bit application would only work with a 32 bit kernel and the 64 bit application only with a 64 bit kernel. It wouldn't surprise me. E.g., ALSA does not work in a 32-bit chroot, but the old OSS does. shrugs -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Stephen Olander Waters [EMAIL PROTECTED] writes: On Wed, 2007-01-24 at 08:24 -0500, Matthias Julius wrote: Gudjon I. Gudjonsson [EMAIL PROTECTED] writes: Yes, sorry, I sometimes forget to mention relevant information. I was only using the 64 bit kernel modules and 32 bit library in chroot and it did not work. But after porting the application to 64 bit it worked like charm. Then you should be able to debug the application and see wether the device file is actually opened or not. Could it be that this is some data type issue that both the kernel module and the application use a type for communication that has a different size on a 32 bit platform and on a 64 bit platform? This way the 32 bit application would only work with a 32 bit kernel and the 64 bit application only with a 64 bit kernel. It wouldn't surprise me. E.g., ALSA does not work in a 32-bit chroot, but the old OSS does. Which is a bug in ALSA. iptables used to be the same way but is fixed now. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
On Wed, Jan 24, 2007 at 08:42:59AM -0600, Stephen Olander Waters wrote: It wouldn't surprise me. E.g., ALSA does not work in a 32-bit chroot, but the old OSS does. ALSA works fine here in a 32-bit chroot. I sometimes use 32-bit mplayer as it has access to win32 codecs. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
On Thu, 2007-01-25 at 08:14 +1100, Hamish Moffatt wrote: On Wed, Jan 24, 2007 at 08:42:59AM -0600, Stephen Olander Waters wrote: It wouldn't surprise me. E.g., ALSA does not work in a 32-bit chroot, but the old OSS does. ALSA works fine here in a 32-bit chroot. I sometimes use 32-bit mplayer as it has access to win32 codecs. Really??? You're sure it's not falling back on the OSS driver? Do you mind posting your /etc/fstab? I want to see if I'm mounting my /x86/dev similarly. Thanks, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Jack Malmostoso [EMAIL PROTECTED] writes: Hi list, I have finally decided to look into my little issue of no sound with chroot applications. The AMD64 howto is down at the moment (or at least I can't reach it) so I am not sure this is written there, anyway: all I had to do was to bind mount my /dev directory. My /etc/fstab looks like this now: # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 /dev/var/chroot/sid-ia32/dev none bind0 0 Well obviously there's more to it, this is just the relevant part ;) I hope this can help somebody. I have sound in flash and mplayer with no other configuration required: please note I use esd in my gnome desktop, not sure if it's relevant or not. Enjoy! You are missing /sys and /dev/pts. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Hi Goswin and all the others # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 /dev/var/chroot/sid-ia32/dev none bind0 0 Well obviously there's more to it, this is just the relevant part ;) I hope this can help somebody. I have sound in flash and mplayer with no other configuration required: please note I use esd in my gnome desktop, not sure if it's relevant or not. Enjoy! You are missing /sys and /dev/pts. MfG Goswin Now there is one thing I don't understand. I do have sound with the following entries in fstab (thanks to a hint from Lennart) # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 /dev/var/chroot/sid-ia32/dev none rbind 0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 rbind makes a difference but I have no no mounting to /sys, perhaps I should add that but according to the debian reference manual it should be done in another way. http://www.debian.org/doc/manuals/reference/ch-tips.en.html#s-chroot chroot # cd /dev; /sbin/MAKEDEV generic; cd - Is this difference documented somewhere or can you explain this? It might explain why my 32 bit xoscope cannot access the 64 bit comedi lib driver. Regards Gudjon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Gudjon I. Gudjonsson [EMAIL PROTECTED] writes: Hi Goswin and all the others # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 /dev/var/chroot/sid-ia32/dev none bind0 0 Well obviously there's more to it, this is just the relevant part ;) I hope this can help somebody. I have sound in flash and mplayer with no other configuration required: please note I use esd in my gnome desktop, not sure if it's relevant or not. Enjoy! You are missing /sys and /dev/pts. MfG Goswin Now there is one thing I don't understand. I do have sound with the following entries in fstab (thanks to a hint from Lennart) # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 /dev/var/chroot/sid-ia32/dev none rbind 0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 rbind makes a difference Yes, with rbind you don't need to mount /dev/pts separately but I have no no mounting to /sys, perhaps I should add that but according to the debian reference manual it should be done in another way. /sys shouldn't be needed for sound. But, for other hardware like USB scanners it might be necessary. http://www.debian.org/doc/manuals/reference/ch-tips.en.html#s-chroot chroot # cd /dev; /sbin/MAKEDEV generic; cd - I wouldn't create a static /dev in a chroot on a system that uses udev. Is this difference documented somewhere or can you explain this? It might explain why my 32 bit xoscope cannot access the 64 bit comedi lib driver. I have no clue about this :) What is xoscope and comedi? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Hi Mattias And thanks for the answer /sys shouldn't be needed for sound. But, for other hardware like USB scanners it might be necessary. http://www.debian.org/doc/manuals/reference/ch-tips.en.html#s-chroot chroot # cd /dev; /sbin/MAKEDEV generic; cd - I wouldn't create a static /dev in a chroot on a system that uses udev. Good to know but could you please point that out for the debian reference manual authors? You seem to have better understanding than I do. Is this difference documented somewhere or can you explain this? It might explain why my 32 bit xoscope cannot access the 64 bit comedi lib driver. I have no clue about this :) What is xoscope and comedi? xoscope is a software oscilloscope that only works on 32 bit machines and comedi is a library to access several IO cards. I ported xoscope amd64 (if anyone is interested) and then it works with comedi but not if I run the 32 bit version in chroot. My guess was that I could solve that pussle by using static /dev in the chroot but obviously that is not an option. Thanks Gudjon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Matthias Julius [EMAIL PROTECTED] writes: Gudjon I. Gudjonsson [EMAIL PROTECTED] writes: Hi Goswin and all the others # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 /dev/var/chroot/sid-ia32/dev none bind0 0 Well obviously there's more to it, this is just the relevant part ;) I hope this can help somebody. I have sound in flash and mplayer with no other configuration required: please note I use esd in my gnome desktop, not sure if it's relevant or not. Enjoy! You are missing /sys and /dev/pts. MfG Goswin Now there is one thing I don't understand. I do have sound with the following entries in fstab (thanks to a hint from Lennart) # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 /dev/var/chroot/sid-ia32/dev none rbind 0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 rbind makes a difference Yes, with rbind you don't need to mount /dev/pts separately Except that the mtab will not reflect the mounted filesystems then iirc and umounting might fail. Better to list the sub-mounts specifically. but I have no no mounting to /sys, perhaps I should add that but according to the debian reference manual it should be done in another way. /sys shouldn't be needed for sound. But, for other hardware like USB scanners it might be necessary. http://www.debian.org/doc/manuals/reference/ch-tips.en.html#s-chroot chroot # cd /dev; /sbin/MAKEDEV generic; cd - I wouldn't create a static /dev in a chroot on a system that uses udev. Unless it is a buildd chroot or something where you do want a minimal /dev. But for a user chroot having it reflect the system is better. Is this difference documented somewhere or can you explain this? It might explain why my 32 bit xoscope cannot access the 64 bit comedi lib driver. Generally 32bit and 64bit can't be mixed in the same address space. You can't dlopen a 64bit lib in a 32bit application for example. I have no clue about this :) What is xoscope and comedi? Matthias MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
Gudjon I. Gudjonsson [EMAIL PROTECTED] writes: xoscope is a software oscilloscope that only works on 32 bit machines and comedi is a library to access several IO cards. I ported xoscope amd64 (if anyone is interested) and then it works with comedi but not if I run the 32 bit version in chroot. My guess was that I could solve that pussle by using static /dev in the chroot but obviously that is not an option. As Goswin has pointed out a 32 bit program can not call a 64 bit library. You would need to install the 32 bit version of that library in your chroot. Or is it a kernel module that you are trying to use? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
