-   Linux - Software (
-   -   RedHat kickstart post fglrx rpm install not working (

dizowned 02-23-2010 06:51 AM

RedHat kickstart post fglrx rpm install not working
As the title says, I'm building a kickstart for a RedHat installation.
I'm trying to incorporate the firegl driver rpm installation and its halfway working, not completly. What I've tried so far is to place the rpm in the --nochroot and in the normal chroot enviornment and neither one works. In the --nochroot, install it with rpm --root /mnt/sysimage/
and in the normal post i just do an rpm -ivh. In either case the fglrx folder is built within /lib/modules, however everything thats supposed to be installed never makes it to the newly installed root. I'm thinking that its actually getting installed to the installation / as opposed to the new /. I'm rebuilding another kickstart to verify this but until then, any suggestions or insight would be much appreciated. Thanks All.

kbp 02-24-2010 04:42 PM

I usually install all packages in the %post section without any issues... maybe the rpm is doing something strange ? .. can you do an 'rpm -qp --scripts <firegl_rpm_name.rpm>'

Where did you get the rpm from ?


dizowned 02-26-2010 04:43 AM

Thanks for the reply, I figured it out and you are kind of right about the rpm doing something strange. Part of the rpm post is to have a custom fglrx module built via script. The way the sh script looks for the kernel headers causes it to look in
/usr/src/linux/include for the headers. In the latest kernel releases they no longer use /usr/src/linux/include. Usually they just use /usr/src/redhat/kernel-version/... and /lib/modules/kernel-version/... , The fglrx bin that will build you custom rpm's for different distro's builds in a way for the rpm to find your kernel headers based on uname queries. The problem with doing this during installation is that one of the conditionals in the includes if-else routines comes up true, which causes the /usr/src/linux/include to be used as opposed to the real /lib/modules/kernel-version/build/include. It's either something weird that happens do to the chroot env your operating in, or maybe its something totally different.
The only work around I've found is to extract the rpm, pull the post script and have the sh script run with hard coded settings as part of the post, which then of course defeats the whole point of having an rpm...

kbp 02-26-2010 07:21 AM

You could convert it to a dkms rpm... I had to do a few drivers like that recently. It works really well, dkms checks on boot whether the module matches the running kernel and if not compiles and inserts on the fly during boot



All times are GMT -5. The time now is 04:01 AM.