Hello Thanasis!
On Thu, Dec 04, 2003 at 05:50:25PM -0700, Thanasis Kinias wrote:
scripsit Roberto Sanchez:
I'm not sure. Do you have discover or kudzu installed (both are
hardware autodetectors that may try loading/unloading modules to
figure out what you have. Just a thought.
Nope; neither is
scripsit Monique Y. Herman:
> Hrm. Okay, well, I don't know what AFS is (though now I'm thinking I
> should find out), and I don't use sound at the moment, so I probably
> just have to worry about the "couple others" =P
AFS is a distributed file system. My uni uses it (among other things)
to a
On Thu, 04 Dec 2003 at 23:15 GMT, Thanasis Kinias penned:
> scripsit Monique Y. Herman:
>> On Thu, 04 Dec 2003 at 21:46 GMT, Thanasis Kinias penned:
>
>> > OK, I recompiled and enabled that... (Aside: Lots of possible
>> > gotchas switching to 2.6...)
>>
>> Please elaborate!
>
> Well, I didn't
scripsit Roberto Sanchez:
> I'm not sure. Do you have discover or kudzu installed (both are
> hardware autodetectors that may try loading/unloading modules to
> figure out what you have. Just a thought.
Nope; neither is installed. This is a fairly new net install with no
tasksel stuff, either
scripsit Monique Y. Herman:
> On Thu, 04 Dec 2003 at 21:46 GMT, Thanasis Kinias penned:
> > OK, I recompiled and enabled that... (Aside: Lots of possible
> > gotchas switching to 2.6...)
>
> Please elaborate!
Well, I didn't mean to be melodramatic ;)
The biggest one for me is that OpenAFS is
Thanasis Kinias wrote:
scripsit Roberto Sanchez:
They are unsafe to unload because it is possible that unloading them
could cause very serious problems. To unload those, you must have
enabled CONFIG_MODULE_FORCE_UNLOAD (for Forced Module Unloading):
OK, now I'm confused. Why, then, would the k
On Thu, 04 Dec 2003 at 21:46 GMT, Thanasis Kinias penned:
> scripsit Roberto Sanchez:
>
>> Module unloading *must* be specifically enabled in 2.6 kernels.
>> Otherwise, you can only load.
>
> OK, I recompiled and enabled that... (Aside: Lots of possible
> gotchas switching to 2.6...)
Please e
scripsit Roberto Sanchez:
> They are unsafe to unload because it is possible that unloading them
> could cause very serious problems. To unload those, you must have
> enabled CONFIG_MODULE_FORCE_UNLOAD (for Forced Module Unloading):
OK, now I'm confused. Why, then, would the kernel be attempting
Thanasis Kinias wrote:
scripsit Roberto Sanchez:
Module unloading *must* be specifically enabled in 2.6 kernels.
Otherwise, you can only load.
OK, I recompiled and enabled that... (Aside: Lots of possible gotchas
switching to 2.6...)
...and I can now unload _some_ but not all modules. Speci
scripsit Roberto Sanchez:
> Module unloading *must* be specifically enabled in 2.6 kernels.
> Otherwise, you can only load.
OK, I recompiled and enabled that... (Aside: Lots of possible gotchas
switching to 2.6...)
...and I can now unload _some_ but not all modules. Specifically,
ide_probe_m
scripsit Andrew Schulman:
> Are you using the updated modutils for 2.6?
>
> apt-get install module-init-tools
$ apt-cache policy module-init-tools
module-init-tools:
Installés : 0.9.15-pre3-2
Candidat : 0.9.15-pre3-2
Table de version :
*** 0.9.15-pre3-2 0
500 http://ftp.us.debian.
Andrew Schulman wrote:
> I'm using a 2.6 kernel I compiled from the Debian source package, and
> encountering some odd behaviour. I cannot unload modules--I get:
>
> Module foo cannot be unloaded due to unsafe usage in
> include/linux/module.h:483
>
> This results in having a lot of
On Mon, 1 Dec 2003 21:44:48 -0700,
Thanasis Kinias <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
> Also, as a side issue I'm not seeing the vaunted desktop performance
> increases I keep hearing about. On a 2.6 GHz P-IV system (512 MB
> RAM), 2.6 seems if anything a bit more sluggis
> I'm using a 2.6 kernel I compiled from the Debian source package, and
> encountering some odd behaviour. I cannot unload modules--I get:
>
> Module foo cannot be unloaded due to unsafe usage in
> include/linux/module.h:483
>
> This results in having a lot of cruft in the kernel. Is this
Greetings,
I'm using a 2.6 kernel I compiled from the Debian source package, and
encountering some odd behaviour. I cannot unload modules--I get:
Module foo cannot be unloaded due to unsafe usage in
include/linux/module.h:483
This results in having a lot of cruft in the kernel. Is this
15 matches
Mail list logo