On 01/21/2016 03:49 PM, Rick Stevens wrote:
On 01/21/2016 03:09 PM, thibaut noah wrote:
Thanks for the enlightment.
I manage to get the driver from the modules.gz archive and i made a new
initframs using dracut --add-drivers but modprobe still cannot find it,
possible that the module will indeed not work :/
The error is saying :
could not insert 'rr272x_1x' : Exec format error
The driver was built incorrectly for this version of the system. Just
why, I don't know. It did get put into the correct directory or
modprobe/insmod wouldn't find it at all.
Did i miss something? the driver is a .ko file
Just because it's a .ko file doesn't mean it's compatible with a 4.x
kernel. Odds are that it isn't. You should browse High Point's web
site and see if there IS a version of that driver that's 4.x compatible.
Sorry I can't be of more help.
I just looked at High Point's website and they have driver source
compatible with kernels up to 4.0.4. Dunno which kernel you're running.
My F23 box is running 4.3.3-300, my F22 is running 4.2.8-200. They're
both too new for that driver.
2016-01-21 18:53 GMT+01:00 Rick Stevens <ricks@xxxxxxxxxxxxxx
<mailto:ricks@xxxxxxxxxxxxxx>>:
On 01/21/2016 04:02 AM, thibaut noah wrote:
updating this, i did some testing on the sh file and i found
where the
issue is coming from.
There is two for loops (at least two that concerns me) and the
code
inside is never executed.
Condition is :
for dir in [23].*;do
[ -d $dir/kernel/fs ] || continue
I'm a bit lost here, what is this 23 number? it cannot be fedora
number
as this driver is the open source version of the fedora 17
driver.
Pretty sure if i modify the condition with a correct one
everything
should work properly
F17? Well, that's probably the issue. What you're seeing is an
attempt
to walk down the various /lib/modules/2.* and /lib/modules/3.* trees
to install the driver. If you're on F22 or F23, you probably don't
HAVE
2.* or 3.* kernel trees. You have 4.x kernel trees.
You could try changing that line from:
for dir in [23].*; do
To:
for dir in [234].*; do
That would include the 4.x kernel trees. I don't know if the
module will
work, though as it seems to be written for quite old kernels. YMMV
2016-01-21 12:21 GMT+01:00 thibaut noah <thibaut.noah@xxxxxxxxx
<mailto:thibaut.noah@xxxxxxxxx>
<mailto:thibaut.noah@xxxxxxxxx <mailto:thibaut.noah@xxxxxxxxx>>>:
Hello guys, got this weird error trying to install my raid
driver :
Start to install the driver rr272x_1x.ko of rr272x_1x.
Finish installing the kernel module rr272x_1x.ko.
Loading rr272x_1x driver module rr272x_1x
modprobe: FATAL: Module rr272x_1x not found.
Checked with lsmod driver does not appear tough the
installation is
finished (checked the sh file, modprobe is running at the
end).
After a little read of the sh file i can confirm that the
driver is
in /etc/rc.modules (it appears to be with sd_mod and that's
all).
chmod on rc.modules in the sh file is successfull (chmod
755).
The failing part seems to be this :
elif [ "${MODULE}" = "rr272x_1x" -o "${MODULE}" =
"rr274x_3x" -o
"${MODULE}" = "rr276x" -o "${MODULE}" = "rr278x" ] ; then
( cd /lib/modules/
for dir in [23].*; do
[ -d $dir/kernel/fs ] || continue
if [ -f /boot/initrd-$dir.img ]; then
mv /boot/initrd-$dir.img /boot/initrd-$dir.img.bak
# do not include mvsas in initrd, as the udev and so will
load the
driver
mkinitrd --builtin=mvsas /boot/initrd-$dir.img $dir
elif [ -f /boot/initramfs-$dir.img ]; then
mv /boot/initramfs-$dir.img /boot/initramfs-$dir.img.bak
# do not include mvsas in initramfs, as the udev and so
will load
the driver
dracut /boot/initramfs-$dir.img $dir
fi
done
Can someone give me a hint on how to do what needs to be
done? I'm
not familiar with drivers on unix systems so i'm a bit
lost, full sh
file is attached if needed, thanks.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Polygon: A dead parrot (With apologies to John Cleese) -
----------------------------------------------------------------------
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
