Morris wrote:
On 13/02/2017 19:21, Stephen Morris wrote:
I've removed the driver from DKMS in Ubuntu and re-added it, then
run a
DKMS AUTOINSTALL to rebuild and re-install the driver back into the
running kernel and under Ubuntu the modprobe command to active the
driver is not issued either
Morris wrote:
I've removed the driver from DKMS in Ubuntu and re-added it, then
run a
DKMS AUTOINSTALL to rebuild and re-install the driver back into the
running kernel and under Ubuntu the modprobe command to active the
driver is not issued either, but also under Ubuntu is seems that when
the
/2017 19:21, Stephen Morris wrote:
>>>>> I've removed the driver from DKMS in Ubuntu and re-added it, then
>>>>> run a
>>>>> DKMS AUTOINSTALL to rebuild and re-install the driver back into the
>>>>> running kernel and under Ubuntu
run a
DKMS AUTOINSTALL to rebuild and re-install the driver back into the
running kernel and under Ubuntu the modprobe command to active the
driver is not issued either, but also under Ubuntu is seems that when
the rmmod command is issued to remove the driver from the running kernel
which removes wifi a
;>> DKMS AUTOINSTALL to rebuild and re-install the driver back into the
>>> running kernel and under Ubuntu the modprobe command to active the
>>> driver is not issued either, but also under Ubuntu is seems that when
>>> the rmmod command is issued to remove the d
r back into the
>> running kernel and under Ubuntu the modprobe command to active the
>> driver is not issued either, but also under Ubuntu is seems that when
>> the rmmod command is issued to remove the driver from the running kernel
>> which removes wifi access, the dns reso
On 02/13/2017 12:22 PM, Stephen Morris wrote:
> On 13/02/2017 19:21, Stephen Morris wrote:
> I've removed the driver from DKMS in Ubuntu and re-added it, then run a
> DKMS AUTOINSTALL to rebuild and re-install the driver back into the
> running kernel and under Ubuntu the mo
nt and usable
did not have any impact.).
The dkms issue may be an upstream issue as I think dkms under Ubuntu
has the same issue relative to modprobe but I'll need to try the same
test that I did under Fedora, if a kernel upgrade doesn't occur first.
regards,
Steve
I've removed the
s issue may be an upstream issue as I think dkms under Ubuntu has
the same issue relative to modprobe but I'll need to try the same test
that I did under Fedora, if a kernel upgrade doesn't occur first.
regards,
Steve
___
users m
On 02/13/17 11:43, Ed Greshko wrote:
> I have done some checking and have yet to determine why dkms feels the
> need to rebuild the modules.
>
> Does the module loading succeed on subsequent boots?
Well, my knowledge seems "Out of Date".
Even though the additions install process mentions "dkms"
the driver into the
> kernel but it does not issue a modprobe to actually load the driver,
> how do I force dkms to do so, or alternatively am I missing the
> package that would provide that functionality?
This sounds similar to the problem I'm seeing with the vboxvideo driver.
W
modprobe to actually load the driver, how
do I force dkms to do so, or alternatively am I missing the package that
would provide that functionality?
regards,
Steve
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
On 02/28/2014 04:46 PM, Ed Greshko issued this missive:
On 03/01/14 08:43, Rick Stevens wrote:
It wouldn't be. If the device in question is hot-pluggable, then the act
of plugging it in after boot would cause the udev stuff to invoke the
modprobe. Since the device isn't hot-plugg
On 03/01/14 08:43, Rick Stevens wrote:
> It wouldn't be. If the device in question is hot-pluggable, then the act
> of plugging it in after boot would cause the udev stuff to invoke the
> modprobe. Since the device isn't hot-pluggable (it's there when you boot
> the mac
mkinitrd after adding file to these
directories. Lesson learned.
You're welcome.
I don't know where that information may be documented.
It wouldn't be. If the device in question is hot-pluggable, then the act
of plugging it in after boot would cause the udev stuff to invoke the
modp
On 03/01/14 07:14, dennismccl...@earthlink.net wrote:
> Thanks for your help. You were correct that it was a problem with the kernel
> needing to be rebuilt after adding/changing files to the /etc/modules-load.d
> and /etc/modprobe.d directory.
>
> Made a copy of the existing /boot/initramfs-$(un
>>> I need some assistance in troubleshooting problem with passing a modprobe parameter to the lirc_zilog module.>>>>>> I'm running Fedora 19 with the most recent updates:>>>>>> # uname -r>>> 3.12.11-201.fc19.x86_64>>>>
Never mind
options lirc_zilog tx_only=1
is correctSorry, a bit late here.
But the question would still remain.
Does
modprobe lirc_zilog
pick up the options?
If it does, then I think you will need to recreate the initramfs so these
changes are picked up at boot time
On 02/25/14 16:42, dennismccl...@earthlink.net wrote:
> No, what I mean by manual reload is the following command:
>
> modprobe lirc_zilog tx_only=1
I just noticed that you said
# cat /etc/modprobe.d/lirc_zilog.conf
options lirc_zilog tx_only=1
Don't you want simply
options tx_
>> I need some assistance in troubleshooting problem with passing a modprobe
>> parameter to the lirc_zilog module.
>>
>> I'm running Fedora 19 with the most recent updates:
>>
>> # uname -r
>> 3.12.11-201.fc19.x86_64
>>
>> I have a
On 02/25/14 07:56, dennismccl...@earthlink.net wrote:
> I need some assistance in troubleshooting problem with passing a modprobe
> parameter to the lirc_zilog module.
>
> I'm running Fedora 19 with the most recent updates:
>
> # uname -r
> 3.12.11-201.fc19.x86
I need some assistance in troubleshooting problem with passing a modprobe
parameter to the lirc_zilog module.
I'm running Fedora 19 with the most recent updates:
# uname -r
3.12.11-201.fc19.x86_64
I have a file /etc/modprobe.d/lirc_zilog.conf file that contains the following:
# cat
On 08/29/13 09:08, poma wrote:
> On 29.08.2013 00:52, Ed Greshko wrote:
>> On 08/29/13 06:46, Patrick Dupre wrote:
>>> I would like to run modprobe -v i8k at each reboot.
>>> How can I do it automatically?
>> Assuming you're running F18/F19 I suppose you
On 29.08.2013 00:52, Ed Greshko wrote:
> On 08/29/13 06:46, Patrick Dupre wrote:
>> I would like to run modprobe -v i8k at each reboot.
>> How can I do it automatically?
>
> Assuming you're running F18/F19 I suppose you could always go the rc.local
> route.
>
>
Am 29.08.2013 00:46, schrieb Patrick Dupre:
> I would like to run modprobe -v i8k at each reboot.
> How can I do it automatically?
/etc/modules-load.d/ is the way to go for loading modules at boot
http://www.freedesktop.org/software/systemd/man/modules-load.d.html
signatu
On 08/29/13 06:46, Patrick Dupre wrote:
> I would like to run modprobe -v i8k at each reboot.
> How can I do it automatically?
Assuming you're running F18/F19 I suppose you could always go the rc.local
route.
From the rc-local.service file in /lib/systemd/system.
# This unit
Hello,
I would like to run modprobe -v i8k at each reboot.
How can I do it automatically?
Thank.
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de Physico-Chimie de l'Atmos
Nick Urbanik wrote:
> From a rescue disk, I cannot run efibootmgr. The response is always,
> "Fatal: Couldn't open either sysfs or procfs directories for accessing
> EFI variables.
> Try "modprobe efivars" as root"
This means your system is not EFI.
You s
;t open either sysfs or procfs directories for accessing
EFI variables.
Try "modprobe efivars" as root"
Now this has no visible effect. I have been unable to run
efibootmgr. I would really appreciate some ideas on what I can do now
to boot this machine.
--
Nick Urbanik
On 29 March 2011 21:51, Alan Cox wrote:
> On Tue, 29 Mar 2011 18:24:33 +0100
> Aaron Gray wrote:
>
> > I need to get to the command line to do a 'modprobe DAC960' on installing
> > Fedora.
> >
> > Is this possible ?
>
> It should automatically
> I need to get to the command line to do a 'modprobe DAC960' on installing
> Fedora.
>
> Is this possible ?
>
> Many thanks in advance,
>
> Aaron
Aaron,
You could try to add an "module=dac960" or "module=DAC960" in the grub
On 29 March 2011 21:51, Alan Cox wrote:
> On Tue, 29 Mar 2011 18:24:33 +0100
> Aaron Gray wrote:
>
> > I need to get to the command line to do a 'modprobe DAC960' on installing
> > Fedora.
> >
> > Is this possible ?
>
> It should automatically
On Tue, 29 Mar 2011 18:24:33 +0100
Aaron Gray wrote:
> I need to get to the command line to do a 'modprobe DAC960' on installing
> Fedora.
>
> Is this possible ?
It should automatically load the module providing it is on the image. It
could be the autoload is failing
4 Linux kernel. Fedora 14 uses the 2.6 kernel line.
>>
>> Manually running modprobe will not work as there is no "dac960" kernel
>> module for the 2.6 kernel and hardware detection is automatic these days
>> (versus 2.2/2.4 kernels).
> Are you sure ?
> $ uname -r
&
4 Linux kernel. Fedora 14 uses the 2.6 kernel line.
> >
> > Manually running modprobe will not work as there is no "dac960" kernel
> > module for the 2.6 kernel and hardware detection is automatic these days
> > (versus 2.2/2.4 kernels).
>
> Are you sure ?
&
FC4, but post FC4
Kudzu but does not seem to support DAC960 detection any more.
> Aaron, you should try a LiveCD or USB image and try to modprobe your
> module. The Disk Utility (palimpset) should display your card at that
> point.
Okay, that maybe a work around, thanks,
Aaron
--
user
the module still exists. I am too used to modules being
lower case that I didn't perform an case-insensitive search.
Aaron, you should try a LiveCD or USB image and try to modprobe your
module. The Disk Utility (palimpset) should display your card at that point.
--
users mailing lis
Michael Cronenworth cchtml.com> writes:
> ...
> If that is the case, I'm afraid Linux (the kernel, not Fedora) does not
> support your RAID card. A quick Google shows the last driver was
> compatible with the 2.4 Linux kernel. Fedora 14 uses the 2.6 kernel line.
>
>
Aaron Gray on 03/29/2011 02:23 PM wrote:
> FC4 was working. post FC4 is not.
>
>
> FC4 was 2.6.11, looks like it may have been jettisoned later.
Kernel drivers come and go. Sometimes they are completely rewritten (and
renamed). Unfortunately for you it seems support for your card is gone
complet
On 29 March 2011 20:14, Michael Cronenworth wrote:
> Aaron Gray wrote:
> > I need to get to the command line to do a 'modprobe DAC960' on
> > installing Fedora.
> >
> > Is this possible ?
>
> Is the Fedora installer not allowing you to install to hard
Aaron Gray wrote:
> I need to get to the command line to do a 'modprobe DAC960' on
> installing Fedora.
>
> Is this possible ?
Is the Fedora installer not allowing you to install to hard drives
located on your RAID card?
If that is the case, I'm afraid Linux (the k
I need to get to the command line to do a 'modprobe DAC960' on installing
Fedora.
Is this possible ?
Many thanks in advance,
Aaron
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/list
> I don't think most of the options are needed for a rebuild. I've used
> this before things were worked out with the nouveau/Nvidia driver.
> ---
> su -
> mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-backup.img
> dracut /boot/initramfs-$(uname -r).img $(uname -r)
Thanks. I'll st
On Mon, Dec 20, 2010 at 4:11 AM, Tom Horsley wrote:
> On Sun, 19 Dec 2010 21:51:32 -0600
> Richard Shaw wrote:
>
>> More
>> specifically, let dracut rebuilt it.
>
> I know I did it the hard way, except, of course,
> for the difficulty of obtaining the answer to the
> question "What the devil is th
On Sun, 19 Dec 2010 21:51:32 -0600
Richard Shaw wrote:
> More
> specifically, let dracut rebuilt it.
I know I did it the hard way, except, of course,
for the difficulty of obtaining the answer to the
question "What the devil is the command I actually
need to run to let dracut rebuild it?" :-).
T
swer my own question: Yes. (But I still have no idea
> what the official script is :-).
>
> I simply updated the initramfs "by hand" by expanding the
> compressed cpio archive, copying in the additional
> modprobe file and recompressing it.
>
> I now have no kslowdn
I simply updated the initramfs "by hand" by expanding the
compressed cpio archive, copying in the additional
modprobe file and recompressing it.
I now have no kslowdnnn kernel processes running all the
time and accumulating vast cpu, and my mouse is moving
smooth again.
--
users
Searching google for kslowd leads me to suspect I can
help my jerky mouse stop being such a jerk by specifying
the poll=off option to the drm_kms_helper kernel module.
I created a /etc/modprobe.d/drm_kms_helper.conf with
options drm_kms_helper poll=0
in it, but I'm not certain it actually had an
--- On Wed, 7/7/10, Alex wrote:
> From: Alex
> Subject: Generating modprobe files
> To: "Community support for Fedora users"
> Date: Wednesday, July 7, 2010, 5:45 PM
> Hi,
>
> What is the procedure or process to regenerate the
> /etc/modprobe.d
> files,
Hi,
What is the procedure or process to regenerate the /etc/modprobe.d
files, particularly the ones that define the module for the ethernet
drivers?
I'd like to generate the aliases for all the modules that are
currently loaded on the system, so they are loaded automatically on
the next boot.
Th
Noted. Sorry.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
On Sun, 2010-04-11 at 21:12 +0300, Aioanei Rares wrote:
> And please stop top-posting.
And please stop full-quoting... It's wasting everyone's bandwidth and
storage space. Not to mention being a right nuisance to read.
--
[...@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send priv
Hi, I have resolved the problem with modprob -a
thanks for all
2010/4/11 Joseph L. Casale
> >The module hasn't installed properly. Look at the README in the tarball:)
> >Install is left to the op, which he hasn't done as his working dir is
> >still in the compilation dir...
>
> My bad:) All t
>The module hasn't installed properly. Look at the README in the tarball:)
>Install is left to the op, which he hasn't done as his working dir is
>still in the compilation dir...
My bad:) All this html/post craziness left me skimming through this to
quickly. Seems he has copied it over.
Does it w
>Excellent suggestion. That should take care of the problem if the module
>installed correctly.
The module hasn't installed properly. Look at the README in the tarball:)
Install is left to the op, which he hasn't done as his working dir is
still in the compilation dir...
--
users mailing list
u
--- On Sun, 4/11/10, François Patte wrote:
> From: François Patte
> Subject: Re: modprobe problem
> To: "Community support for Fedora users"
> Date: Sunday, April 11, 2010, 10:48 AM
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Le 11/04/2010 19:24
What version of Fedora are you using?
-Inline Attachment Follows-
--
Looks like Fedora 12:
From
/lib/modules/2.6.32.10-90.fc12.i686
Regards,
Antonio
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedora
11xx-2.1.0]# cp
/home/adel/stk11xx-2.1.0/stk11xx.ko
/lib/modules/2.6.32.10-90.fc12.i686/kernel/drivers/media/video/
[r...@localhost stk11xx-2.1.0]# modprobe stk11xx fps=30
FATAL: Module stk11xx not found.
I tryed this, but still fails
And also there is no /etc/m
drivers/media/video/
>>
>> [r...@localhost stk11xx-2.1.0]# modprobe stk11xx fps=30
>> FATAL: Module stk11xx not found.
>>
>>
>> I tryed this, but still fails
>>
>
> And also there is no /etc/modprobe.conf in my fedora
>
> Regards
>
>
>
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 11/04/2010 19:24, Adel ESSAFI a écrit :
> Thanks for replay
>
> [r...@localhost stk11xx-2.1.0]# cp /home/adel/stk11xx-2.1.0/stk11xx.ko
> /lib/modules/2.6.32.10-90.fc12.i686/kernel/drivers/media/video/
> [r...@localhost stk11xx-2
tk11xx-2.1.0]# modprobe stk11xx fps=30
FATAL: Module stk11xx not found.
I tryed this, but still fails
And also there is no /etc/modprobe.conf in my fedora
Regards
2010/4/11 Patrick O'Callaghan mailto:pocallag...@gmail.com>>
On Sun, 2010-04-11 at 19:05 +
2010/4/11 Adel ESSAFI
> Thanks for replay
>
> [r...@localhost stk11xx-2.1.0]# cp /home/adel/stk11xx-2.1.0/stk11xx.ko
> /lib/modules/2.6.32.10-90.fc12.i686/kernel/drivers/media/video/
>
> [r...@localhost stk11xx-2.1.0]# modprobe stk11xx fps=30
> FATAL: Module stk11xx not foun
Thanks for replay
[r...@localhost stk11xx-2.1.0]# cp /home/adel/stk11xx-2.1.0/stk11xx.ko
/lib/modules/2.6.32.10-90.fc12.i686/kernel/drivers/media/video/
[r...@localhost stk11xx-2.1.0]# modprobe stk11xx fps=30
FATAL: Module stk11xx not found.
I tryed this, but still fails
2010/4/11 Patrick
xx-2.1.0]# ls *.ko
> stk11xx.ko
> [r...@localhost stk11xx-2.1.0]# modprobe stk11xx fps=30
> FATAL: Module stk11xx not found.
Is your module in the right place? According to modprobe(8):
modprobe looks in the module directory /lib/modules/‘uname -r‘ for all
the modules and other
file
11xx.ko
> [r...@localhost stk11xx-2.1.0]# modprobe stk11xx fps=30
> FATAL: Module stk11xx not found.
>
>
>
>
> --
>
> PhD candidate in Computer Science
> Address
> 3 avenue lamine, cité ezzahra, Sousse 4000
> Tunisia
> tel: +216 97 246 706
> fax: +216 71
>Dear list
>
>I am trying to install syntex webcam driver, I have compiled the kernel module
>but failed to load him.
>
>Can you help me please
>
>regards
>
>
>
>[r...@localhost stk11xx-2.1.0]# ls *.ko
>stk11xx.ko
>[r...@localhost stk11xx-2.1.0]# modp
Dear list
I am trying to install syntex webcam driver, I have compiled the kernel
module but failed to load him.
Can you help me please
regards
[r...@localhost stk11xx-2.1.0]# ls *.ko
stk11xx.ko
[r...@localhost stk11xx-2.1.0]# modprobe stk11xx fps=30
FATAL: Module stk11xx not found
67 matches
Mail list logo
