On 21/03/13 06:41, Lucas De Marchi wrote:
> Ok... I pushed an alternative fix to have the same behavior as for
> modprobe (except the exit code). As I said "off" and "null" are note
> special, and they weren't in module-init-tools neither. The thing we
> were doing wrong is that in presence of an a
On Fri, Mar 15, 2013 at 12:34 AM, Lucas De Marchi
wrote:
>
> On Mar 14, 2013 4:25 PM, "Alberto Milone"
> wrote:
>>
>> On 14/03/13 23:34, Lucas De Marchi wrote:
>> > Do you realize you are quoting the man page of modutils? It's not
>> > kmod or module-init-tools, which kmod replaced. It's the old
On 14/03/13 23:34, Lucas De Marchi wrote:
> Do you realize you are quoting the man page of modutils? It's not
> kmod or module-init-tools, which kmod replaced. It's the old modutils
> used with Linux 2.4. kmod is a drop-in replacement to m-i-t, but we
> are not putting back the things from moduti
On Thu, Mar 14, 2013 at 7:54 AM, Alberto Milone
wrote:
> On 14/03/13 03:39, Lucas De Marchi wrote:
>> Hi Alberto
>>
>> First of all, please inline your patch next time, so we can comment on it.
>>
>
> Sorry about that.
>
>> On Wed, Mar 13, 2013 at 1:15 PM, Alberto Milone
>> wrote:
>>> Hi all,
>>>
On 14/03/13 03:39, Lucas De Marchi wrote:
> Hi Alberto
>
> First of all, please inline your patch next time, so we can comment on it.
>
Sorry about that.
> On Wed, Mar 13, 2013 at 1:15 PM, Alberto Milone
> wrote:
>> Hi all,
>>
>> I think the problem is that modprobe looks for the module (which
Hi Alberto
First of all, please inline your patch next time, so we can comment on it.
On Wed, Mar 13, 2013 at 1:15 PM, Alberto Milone
wrote:
> Hi all,
>
> I think the problem is that modprobe looks for the module (which in this
> case is aliased as "off") in /sys and raises an error if it doesn'
Hi all,
I think the problem is that modprobe looks for the module (which in this
case is aliased as "off") in /sys and raises an error if it doesn't find
it (there's no such thing as an "off" module in /sys).
In the attached patch I check that the module name is not "off" or
"null" before doing a
Package: kmod
Version: 9-2
Followup-For: Bug #674110
Control: tags -1 - unreproducible moreinfo
I have the same issue, but it is caused by my dislike of firewire on my
previous laptop:
pabs@chianamo ~ $ cat /etc/modprobe.d/pabs-blacklist.conf
# Firewire physical DMA is a security issue
blacklist
On Aug 04, Lucas De Marchi wrote:
> path is NULL but the initstate of the module is BUILTIN. So maybe your
> modules.dep{,bin} is corrupted?
Lucas, another user has found out that this happens when you declare an
alias like "alias nouveau off", which was actually supported by
modutils:
http:/
path is NULL but the initstate of the module is BUILTIN. So maybe your
modules.dep{,bin} is corrupted?
Could you please send me the output of modprobe -
together with your modules.dep{,bin}
files?
Regards,
Lucas De Marchi
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.deb
On 05-23 13:33, Marco d'Itri wrote:
> On May 23, Witold Baryluk wrote:
>
> > I just noticed that modprobe fails during system upgrade, when generting new
> > initrd image. It aborts then and dumps core.
> > This is what I got when run update-initramfs manually:
> Just to be sure, can you try rebu
On May 23, Witold Baryluk wrote:
> I just noticed that modprobe fails during system upgrade, when generting new
> initrd image. It aborts then and dumps core.
> This is what I got when run update-initramfs manually:
Just to be sure, can you try rebuilding the package without the
check_builtin_kv
Package: kmod
Version: 8-2
Severity: normal
I just noticed that modprobe fails during system upgrade, when generting new
initrd image. It aborts then and dumps core.
This is what I got when run update-initramfs manually:
sredniczarny:/home/baryluk# env LC_ALL=C update-initramfs -v -u -k
3.2.0-2
13 matches
Mail list logo
