Thanks.

From the debug message it looks like this

debug: Looking up symbol __calloc
debug: Symbol __calloc bound to definition in libc.so.3
debug: Looking up symbol mmap_device_memory
debug: Symbol mmap_device_memory bound to definition in libc.so.3
debug: Looking up symbol mmap64
debug: Symbol mmap64 bound to definition in libc.so.3
debug: Looking up symbol xpt_alloc
debug: Symbol xpt_alloc could not be resolved in this scope
ldd:FATAL: Unresolved symbol "xpt_alloc" called from Executable

Regards,
Manas

-----Original Message-----
From: David Sarrazin [mailto:community-noreply@qnx.com] 
Sent: Tuesday, December 15, 2015 10:57 AM
To: Sahoo, Manas R (GE, Intelligent Platforms); ostech-core_os@community.qnx.com
Subject: Re: Starting devb-ahci gives : Unresolved symbol "xpt_alloc" called from Execut able

Sorry, I was unclear. Out the environment variable first on the line.

# DL_DEBUG=all devb-ahci

Sent from my BlackBerry 10 smartphone.
  Original Message
From: Sahoo, Manas R (GE, Intelligent Platforms)
Sent: Tuesday, December 15, 2015 12:25 AM
To: ostech-core_os@community.qnx.com
Reply To: ostech-core_os@community.qnx.com
Subject: RE: Starting devb-ahci gives : Unresolved symbol "xpt_alloc" called from Executable


I see libcam.so, libcam.so.2 & cam-disk.so present in the /proc/boot.

Even though I set DL_DEBUG=all, I see the same error. Please see below.

# devb-ahci DL_DEBUG=all &
[1] 303123
# ldd:FATAL: Unresolved symbol "xpt_alloc" called from Executable


[1] + Done                 devb-ahci DL_DEBUG=all

Regards,
Manas

-----Original Message-----
From: David Sarrazin [mailto:community-noreply@qnx.com]
Sent: Tuesday, December 15, 2015 10:25 AM
To: manas sahoo; ostech-core_os
Subject: Re: Starting devb-ahci gives : Unresolved symbol "xpt_alloc" called from Executable

I think you are missing libcam.so or cam-disk.so.

Set DL_DEBUG=all on the command line, to double check.

Sent from my BlackBerry 10 smartphone.
  Original Message
From: manas sahoo
Sent: Monday, December 14, 2015 11:39 PM
To: ostech-core_os
Reply To: ostech-core_os@community.qnx.com
Subject: Starting devb-ahci gives : Unresolved symbol "xpt_alloc" called from Executable


Hi,

While starting the devb-ahci driver, it does not start and gives the below error. I am stuck here. Need support.

# devb-ahci &
[1] 266255
# ldd:FATAL: Unresolved symbol "xpt_alloc" called from Executable


[1] + Done                 devb-ahci


Regards,
Manas



_______________________________________________

OSTech
https://urldefense.proofpoint.com/v2/url?u=http-3A__community.qnx.com_sf_go_post115306&d=CwIFAg&c=
IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=x4M_FqHWSd9lCjYx6OSUWUXZesy3o-swjtVkHTWouHQ&m=
UurpK1dPpUoPlLHiUu5s2N0DabJoaaTHVg48VMW2Dxw&s=b-AfDaJLMSO7Pz4vAreRL8eNChoHOhd881rhaWHUJhE&e=
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com




_______________________________________________

OSTech
https://urldefense.proofpoint.com/v2/url?u=http-3A__community.qnx.com_sf_go_post115307&d=CwIFAg&c=
IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=x4M_FqHWSd9lCjYx6OSUWUXZesy3o-swjtVkHTWouHQ&m=
UurpK1dPpUoPlLHiUu5s2N0DabJoaaTHVg48VMW2Dxw&s=4jQxkuKXhquO0r6UgTHOZxqqTjjPY3Cmp0DecpB9h9Q&e=
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com




_______________________________________________

OSTech
https://urldefense.proofpoint.com/v2/url?u=http-3A__community.qnx.com_sf_go_post115308&d=CwIFAg&c=
IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=x4M_FqHWSd9lCjYx6OSUWUXZesy3o-swjtVkHTWouHQ&m=-4a_g-
wiqUBwFl3d0pvoKyY0gMGBilv_fJ3Ewp5QTtc&s=c3UsdWgUxLCXFvijKQXucCWkLJWARgyhqJY_KD50ayk&e= 
To cancel your subscription to this discussion, please e-mail...

It looks like there are certain differences between the libraries came with 6.5SP1 and the ones which I have. After 
using the 6.5SP1 libraries the AHCI driver started working. 

Thanks,
Manas

-----Original Message-----
From: David Sarrazin [mailto:community-noreply@qnx.com] 
Sent: Tuesday, December 15, 2015 10:57 AM
To: Sahoo, Manas R (GE, Intelligent Platforms); ostech-core_os@community.qnx.com
Subject: Re: Starting devb-ahci gives : Unresolved symbol "xpt_alloc" called from Execut able

Sorry, I was unclear. Out the environment variable first on the line.

# DL_DEBUG=all devb-ahci

Sent from my BlackBerry 10 smartphone.
  Original Message
From: Sahoo, Manas R (GE, Intelligent Platforms)
Sent: Tuesday, December 15, 2015 12:25 AM
To: ostech-core_os@community.qnx.com
Reply To: ostech-core_os@community.qnx.com
Subject: RE: Starting devb-ahci gives : Unresolved symbol "xpt_alloc" called from Executable


I see libcam.so, libcam.so.2 & cam-disk.so present in the /proc/boot.

Even though I set DL_DEBUG=all, I see the same error. Please see below.

# devb-ahci DL_DEBUG=all &
[1] 303123
# ldd:FATAL: Unresolved symbol "xpt_alloc" called from Executable


[1] + Done                 devb-ahci DL_DEBUG=all

Regards,
Manas

-----Original Message-----
From: David Sarrazin [mailto:community-noreply@qnx.com]
Sent: Tuesday, December 15, 2015 10:25 AM
To: manas sahoo; ostech-core_os
Subject: Re: Starting devb-ahci gives : Unresolved symbol "xpt_alloc" called from Executable

I think you are missing libcam.so or cam-disk.so.

Set DL_DEBUG=all on the command line, to double check.

Sent from my BlackBerry 10 smartphone.
  Original Message
From: manas sahoo
Sent: Monday, December 14, 2015 11:39 PM
To: ostech-core_os
Reply To: ostech-core_os@community.qnx.com
Subject: Starting devb-ahci gives : Unresolved symbol "xpt_alloc" called from Executable


Hi,

While starting the devb-ahci driver, it does not start and gives the below error. I am stuck here. Need support.

# devb-ahci &
[1] 266255
# ldd:FATAL: Unresolved symbol "xpt_alloc" called from Executable


[1] + Done                 devb-ahci


Regards,
Manas



_______________________________________________

OSTech
https://urldefense.proofpoint.com/v2/url?u=http-3A__community.qnx.com_sf_go_post115306&d=CwIFAg&c=
IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=x4M_FqHWSd9lCjYx6OSUWUXZesy3o-swjtVkHTWouHQ&m=
UurpK1dPpUoPlLHiUu5s2N0DabJoaaTHVg48VMW2Dxw&s=b-AfDaJLMSO7Pz4vAreRL8eNChoHOhd881rhaWHUJhE&e=
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com




_______________________________________________

OSTech
https://urldefense.proofpoint.com/v2/url?u=http-3A__community.qnx.com_sf_go_post115307&d=CwIFAg&c=
IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=x4M_FqHWSd9lCjYx6OSUWUXZesy3o-swjtVkHTWouHQ&m=
UurpK1dPpUoPlLHiUu5s2N0DabJoaaTHVg48VMW2Dxw&s=4jQxkuKXhquO0r6UgTHOZxqqTjjPY3Cmp0DecpB9h9Q&e=
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com




_______________________________________________

OSTech
https://urldefense.proofpoint.com/v2/url?u=http-3A__community.qnx.com_sf_go_post115308&d=CwIFAg&c=
IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=x4M_FqHWSd9lCjYx6OSUWUXZesy3o-swjtVkHTWouHQ&m=-4a_g-
wiqUBwFl3d0pvoKyY0gMGBilv_fJ3Ewp5QTtc&s=c3UsdWgUxLCXFvijKQXucCWkLJWARgyhqJY_KD50ayk&e= 
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com




_______________________________________________

OSTech
https://urldefense.proofpoint.com/v2/url?u=http-3A__community.qnx.com_sf_go_post115309&d=CwIFAg&c=
IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=x4M_FqHWSd9lCjYx6OSUWUXZesy3o-swjtVkHTWouHQ&m=-4a_g-
wiqUBwFl3d0pvoKyY0gMGBilv_fJ3Ewp5QTtc&s=i8ucNcmFWfki-JYm6gK5n154y-I57T25Nbkzbrcq0ow&e= 
To cancel your subscription to this discussion, please e-mail...