Redhat 9.0 also has the snd.o unresolved symbol schedule_work issue
I work for HP and I just downloaded the new RH 9.0 iso's from our internal source yesterday. After upgrading from RH 8.0 and the 2.4.18 kernel I tried to update my Alsa drivers to work with the new 2.4.20 kernel and found that althought the Alsa 0.9.2 drivers had compiled and installed without trouble the would not load. Instead I am getting the error unresolved symbol schedule_work.
Now I know that there have been numerous similar complaints on the user mailing list, but since nobody seems to be privinding and answer and since I saw no mention of this error on the development list I thought that I would send out this mail to both lists and see if I could get a little bit more of a response.
I have a Yamahaa Waveforce 192XG, a 1.2Ghz Duron, 128MB of ram, and a ECS K7S5A motherboard. But since this appears to be a layer other then the hardware driver layer and has been reported with to be affecting numerous cards, I really don't think that my hardware config will be of much importance.
Jason Corekin
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
Quoted 6 lines · Jason Corekin
I work for HP and I just downloaded the new RH 9.0 iso's from our internal source yesterday. After upgrading from RH 8.0 and the 2.4.18 kernel I tried to update my Alsa drivers to work with the new 2.4.20 kernel and found that althought the Alsa 0.9.2 drivers had compiled and installed without trouble the would not load. Instead I am getting the error unresolved symbol
schedule_work.
please, check the kernel includes./usr/include/linux MUST be the link to the include directory of the kernel. it was in the process of migration from 2.4.<20 to 2.4.>20. some distributions have /usr/include/linux as a directory. and, when compiling the fresh kernel, one can get strange things with unresolved symbols etc (old headers + new kernel).
so,/usr/include/linux must be the link to /usr/src/linux/include/linux, if kernel sources were unpacked to the /usr/src/linux. and, also, You need to recompile drivers.
maybe, the described approach can help.
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
Good news I have Alsa 0.9.2 working on RedHat 9.0 working with kernel
version 2.4.20. The catch is that I had to replace the RedHat kernel with the stock kernel from www.kernel.org. So the problem has to be in the changes that RedHat made to their kernel. I have to give credit to Kmberry and Lance A. Brown, for pointing out that RedHat plays around with the kernel before releasing it
The only thing that I have not yet tried to do is to rework the
symlinks to make sure that the Alsa code knows where to find the right kernel dependencies. Since I do not know if there is any thing that I am now missing from not running on the RedHat kernel or not it would be nice to at least have some modules compatible with their kernel, but I'm not too worried about it.
I hope this helps.
Jason Corekin
Quoted 32 lines · Jason Corekin
I work for HP and I just downloaded the new RH 9.0 iso's from our internal source yesterday. After upgrading from RH 8.0 and the 2.4.18 kernel I tried to update my Alsa drivers to work with the new 2.4.20 kernel and found that althought the Alsa 0.9.2 drivers had compiled and installed without trouble the would not load. Instead I am getting the error unresolved symbol
schedule_work.Now I know that there have been numerous similar complaints on the user mailing list, but since nobody seems to be privinding and answer and since I saw no mention of this error on the development list I thought that I would send out this mail to both lists and see if I could get a little bit more of a response.
I have a Yamahaa Waveforce 192XG, a 1.2Ghz Duron, 128MB of ram, and a ECS K7S5A motherboard. But since this appears to be a layer other then the hardware driver layer and has been reported with to be affecting numerous cards, I really don't think that my hardware config will be of much importance.
Jason Corekin
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Alsa-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Signature · 9 lines
Jason Corekin <[email protected]> ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
This is most likely (AFAIK) because redhat ships their kernel with NPTL (Native POSIX Thread Library).
Quoted 1 line
From the release notes:
Red Hat Linux 9 includes the Native POSIX Thread Library (NPTL), a new implementation of POSIX threads for Linux. This library provides performance improvements and increased scalability for i686 or better processors.
This thread library is designed to be binary compatible with the old LinuxThreads implementation; however, applications that rely on the places where the LinuxThreads implementation deviates from the POSIX standard will need to be fixed. Notable differences include:
- Signal handling has changed from per-thread signal handling to POSIX process signal handling.
- getpid() returns the same value in all threads.
- Thread handlers registered with pthread_atfork are not run if vfork() is used - no manager thread
--------------------------
I could be wrong but this is where I think the problem is...
Quoted 51 lines · Jason Corekin
Good news I have Alsa 0.9.2 working on RedHat 9.0 working with kernel
version 2.4.20. The catch is that I had to replace the RedHat kernel with the stock kernel from www.kernel.org. So the problem has to be in the changes that RedHat made to their kernel. I have to give credit to Kmberry and Lance A. Brown, for pointing out that RedHat plays around with the kernel before releasing it
The only thing that I have not yet tried to do is to rework the
symlinks to make sure that the Alsa code knows where to find the right kernel dependencies. Since I do not know if there is any thing that I am now missing from not running on the RedHat kernel or not it would be nice to at least have some modules compatible with their kernel, but I'm not too worried about it.
I hope this helps.Jason Corekin
Quoted 32 lines · Jason Corekin
I work for HP and I just downloaded the new RH 9.0 iso's from our internal source yesterday. After upgrading from RH 8.0 and the 2.4.18 kernel I tried to update my Alsa drivers to work with the new 2.4.20 kernel and found that althought the Alsa 0.9.2 drivers had compiled and installed without trouble the would not load. Instead I am getting the error unresolved symbol
schedule_work.Now I know that there have been numerous similar complaints on the user mailing list, but since nobody seems to be privinding and answer and since I saw no mention of this error on the development list I thought that I would send out this mail to both lists and see if I could get a little bit more of a response.
I have a Yamahaa Waveforce 192XG, a 1.2Ghz Duron, 128MB of ram, and a ECS K7S5A motherboard. But since this appears to be a layer other then the hardware driver layer and has been reported with to be affecting numerous cards, I really don't think that my hardware config will be of much importance.
Jason Corekin
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Alsa-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Signature · 20 lines
Edward Muller Interlix - President Web Hosting - PC Service & Support Custom Programming - Network Service & Support Phone: 417-862-0573 Cell: 417-844-2435 Fax: 417-862-0572 http://www.interlix.com ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
Sounds like a real possibility, but I do not know nearly enough about how the ALSA drivers work to agree or disagree.
Quoted 85 lines
This is most likely (AFAIK) because redhat ships their kernel with NPTL (Native POSIX Thread Library).
Quoted 1 line
From the release notes:
Red Hat Linux 9 includes the Native POSIX Thread Library (NPTL), a new implementation of POSIX threads for Linux. This library provides performance improvements and increased scalability for i686 or better processors.
This thread library is designed to be binary compatible with the old LinuxThreads implementation; however, applications that rely on the places where the LinuxThreads implementation deviates from the POSIX standard will need to be fixed. Notable differences include:
- Signal handling has changed from per-thread signal handling to POSIX process signal handling.
-
getpid()returns the same value in all threads.- Thread handlers registered with
pthread_atforkare not run ifvfork()is used - no manager thread--------------------------
I could be wrong but this is where I think the problem is...
Quoted 32 lines · Jason Corekin
Good news I have Alsa 0.9.2 working on RedHat 9.0 working with kernel
version 2.4.20. The catch is that I had to replace the RedHat kernel with the stock kernel from www.kernel.org. So the problem has to be in the changes that RedHat made to their kernel. I have to give credit to Kmberry and Lance A. Brown, for pointing out that RedHat plays around with the kernel before releasing it
The only thing that I have not yet tried to do is to rework the
symlinks to make sure that the Alsa code knows where to find the right kernel dependencies. Since I do not know if there is any thing that I am now missing from not running on the RedHat kernel or not it would be nice to at least have some modules compatible with their kernel, but I'm not too worried about it.
I hope this helps.Jason Corekin
Quoted 1 line · Jason Corekin
I work for HP and I just downloaded the new RH 9.0 iso's from our
internal source yesterday. After upgrading from RH 8.0 and the 2.4.18 kernel I tried to update my Alsa drivers to work with the new 2.4.20 kernel and found that althought the Alsa 0.9.2 drivers had compiled and installed without trouble the would not load. Instead I am getting the error unresolved symbol
schedule_work.Quoted 2 lines
Now I know that there have been numerous similar complaints on the
user mailing list, but since nobody seems to be privinding and answer and since I saw no mention of this error on the development list I thought that I would send out this mail to both lists and see if I could get a little bit more of a response.
Quoted 1 line
Quoted 19 lines
Quoted 1 line
I have a Yamahaa Waveforce 192XG, a 1.2Ghz Duron, 128MB of ram, and
a ECS K7S5A motherboard. But since this appears to be a layer other then the hardware driver layer and has been reported with to be affecting numerous cards, I really don't think that my hardware config will be of much importance.
Quoted 14 lines
Jason Corekin
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Alsa-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel--
Edward MullerInterlix - President
Quoted 8 lines
Web Hosting - PC Service & Support
Custom Programming - Network Service & SupportPhone: 417-862-0573
Cell: 417-844-2435
Fax: 417-862-0572
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/