I just want to be able to use my PS4 controllers. I saw that they have gyro,
and it should be supported in the module, but dolphin doesn't seem to
understand it.
On January 12, 2025 9:07:23 AM EST, "tv.debian"
wrote:
>On 12/01/2025 03:54, nsrxnst wrote:
>> does the stock kernel come with this
On 2025-01-12 14:07, tv.debian wrote:
On 12/01/2025 03:54, nsrxnst wrote:
does the stock kernel come with this driver? if not, how can I get it?
Hello,
If you are asking about the controller, Debian kernels are built with
"CONFIG_HID_SONY=m", so the "hid-playstation.ko" should be available
f
On 12/01/2025 03:54, nsrxnst wrote:
does the stock kernel come with this driver? if not, how can I get it?
Hello,
If you are asking about the controller, Debian kernels are built with
"CONFIG_HID_SONY=m", so the "hid-playstation.ko" should be available for
your system and loaded automatically
does the stock kernel come with this driver? if not, how can I get it?
Salut Didier!
didier gaumet writes:
> Le 04/08/2023 à 11:44, Loris Bennett a écrit :
>> Hi,
>> I have a 10 year-old Dell E6230 laptop which I have updated
>> regularly,
>> starting from Squeeze and have now updated to Bookworm. Everything
>> seems to work except for the fact that a module fails
Le 04/08/2023 à 11:44, Loris Bennett a écrit :
Hi,
I have a 10 year-old Dell E6230 laptop which I have updated regularly,
starting from Squeeze and have now updated to Bookworm. Everything
seems to work except for the fact that a module fails to build for the
new kernel:
Error! Bad return s
Hi,
I have a 10 year-old Dell E6230 laptop which I have updated regularly,
starting from Squeeze and have now updated to Bookworm. Everything
seems to work except for the fact that a module fails to build for the
new kernel:
Error! Bad return status for module build on kernel: 6.1.0-10-amd64 (
"blacklist intel_ips" >> /etc/modprobe.d/blacklist.conf
2. add i915 and intel_ips to /etc/modules
echo -e "i915\nintel_ips" >> /etc/modules
I only made the first point and the log flood was over.
Two questions:
1. Could disabling the intel_ips kerne
Hi.
On Sun, Jul 05, 2020 at 11:44:03PM +1000, Zenaan Harkness wrote:
> Is the pciehp / pci express hot plug kernel module to longer included with
> Debian, or is it meant to be compiled in as static?
It's compiled in:
# grep -i HOTPLUG_PCI_PCIE /boot/config-4.1
On Du, 05 iul 20, 23:44:03, Zenaan Harkness wrote:
> Is the pciehp / pci express hot plug kernel module to longer included
> with Debian, or is it meant to be compiled in as static?
>
> Debian sid here on an X220, trying to connect a "Transcend USB 3.0
> ExpressCard Adapter
Is the pciehp / pci express hot plug kernel module to longer included with
Debian, or is it meant to be compiled in as static?
Debian sid here on an X220, trying to connect a "Transcend USB 3.0 ExpressCard
Adapter" to get a USB3 port (2 ports actually).
There are possible hints tha
Hi--
the serpent cipher is unusable at the moment in sid.
Linux pharoah 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64
GNU/Linux
# modprobe serpent
modprobe: ERROR: could not insert 'serpent_sse2_x86_64': Unknown symbol in
module, or unknown parameter (see dmesg)
modprobe: ERROR: cou
Am 24.01.2017 um 17:17 schrieb Jens Sauer:
> Hey list,
>
> During my custom kernel configuration using "make localmodconfig" I noticed
> that
> the "fjes" driver was configured.
> I wondered why this network driver was needed for my laptop, so I have done
> some
> research.
> According this [1]
On Tue, Jan 24, 2017 at 05:17:45PM +0100, Jens Sauer wrote:
> Date: Tue, 24 Jan 2017 17:17:45 +0100
> From: Jens Sauer
> To: debian-user@lists.debian.org
> Subject: Is the "fjes" Kernel Module loaded on every system?
> Can someone confirm if this module is loaded on th
On 2017-01-24 17:17 +0100, Jens Sauer wrote:
> During my custom kernel configuration using "make localmodconfig" I noticed
> that
> the "fjes" driver was configured.
> I wondered why this network driver was needed for my laptop, so I have done
> some
> research.
> According this [1] linux-netdev
On Tue, Jan 24, 2017 at 05:17:45PM +0100, Jens Sauer wrote:
> I am sure that I don't need this driver for my ThinkPad T450s.
> Nevertheless it is loaded because of an ACPI device "PNP0C02" which is linked
> to
> the module [3].
>
> TL;DR
> Can someone confirm if this module is loaded on their har
Hey list,
During my custom kernel configuration using "make localmodconfig" I noticed that
the "fjes" driver was configured.
I wondered why this network driver was needed for my laptop, so I have done some
research.
According this [1] linux-netdev mailing list entry, which introduces the fjes
modu
Hi.
On Mon, 22 Feb 2016 11:01:29 + (UTC)
Mark Johnson wrote:
> Hi all.
>
> My name is Mark, and I try since a few days to implement outbound traffic
> shaping with cgoups and its podsystems (especially - "net_cls", "net_prio")
> and iptables. The problem is to enable cgroups (subs
Hi all.
My name is Mark, and I try since a few days to implement outbound traffic
shaping with cgoups and its podsystems (especially - "net_cls", "net_prio") and
iptables. The problem is to enable cgroups (subsystems "net_cls" and daemons
like "cgrulesengd") Spent many hours looking for educati
Hi,
I am tracking testing, currently my kernel version is 4.1.0-2-amd64.
I have a nifty ACER c720 working almost perfectly, except for the
trackpad, which dmidecode thinks is:
Handle 0x0007, DMI type 41, 11 bytes
Onboard Device
Reference Designation: trackpad
Type: Other
S
possible that Debian 7 does not include any kernel module which
> supports the LSI 3008 chip? I would like to access my disks directly from
> Debian in order to either use RAID 5 with MD or ZFS.
>
The 3008 needs mpt3sas. You will find that in the linux 3.16
kernel, which has b
hat Debian 7 does not include any kernel module which
> supports the LSI 3008 chip? I would like to access my disks directly from
> Debian in order to either use RAID 5 with MD or ZFS.
>
>
lspci -v
Check to see if the controller is listed with a kernel driver...
Hello,
I installed Debian 7.7 (amd64) on a SuperStorage Server from SuperMicro and
noticed that my disks attached to the LSI 3008 (IT mode) chip on the SuperMicro
mainboard are not seen by Debian.
Is it possible that Debian 7 does not include any kernel module which supports
the LSI 3008 chip
for one hour, its clock would be late one hour after resuming the VM.
> The source of
> 'hv_utils' suggests the guest's clock schould be synced after such a resume
> event.
> How can I find out what is happening? I can code C a little bit.
First entry after entering
Hi,
I have installed Debian under client Hyper-V in Windows 8.1 Pro and the time
is not synced
after a resume, the clock just goes one like nothing happened. So if the guest
VM was in a saved
state for one hour, its clock would be late one hour after resuming the VM. The
source of
'hv_utils'
following for my
system:
Linux homebox 3.2.0-4-kirkwood #1 Debian 3.2.46-1 armv5tel GNU/Linux
Can someone point me how to compile just a kernel module on my arm device
for EasyCAP? I have a basic installation of Debian just about 2 months
ago with user land only.
I looked aro
Am 03.07.2013 um 18:34 schrieb Darac Marjal:
On Mon, Jul 01, 2013 at 04:05:13PM +0200, Helmut Wollmersdorfer wrote:
how can I find out the version number of a particular kernel module
without downloading, without installing, without booting, from
https://git.kernel.org/cgit/linux/kernel
On Mon, Jul 01, 2013 at 04:05:13PM +0200, Helmut Wollmersdorfer wrote:
> Hi,
>
> how can I find out the version number of a particular kernel module
> without downloading, without installing, without booting, from
>
Taking, as an example, uinput:
> - the kernel source
On 07/02/2013 02:54 AM, Helmut Wollmersdorfer wrote:
Am 01.07.2013 um 17:52 schrieb Wayne Topa:
On 07/01/2013 10:05 AM, Helmut Wollmersdorfer wrote:
I.e. I would like the version number of a kernel module (e.g. drbd,
megaraid_sas, igb) before deciding to download, compile, or install
Am 01.07.2013 um 17:52 schrieb Wayne Topa:
On 07/01/2013 10:05 AM, Helmut Wollmersdorfer wrote:
I.e. I would like the version number of a kernel module (e.g. drbd,
megaraid_sas, igb) before deciding to download, compile, or install.
# apt-cache search linux-image |grep ^linux
HTH
On 07/01/2013 10:05 AM, Helmut Wollmersdorfer wrote:
Hi,
how can I find out the version number of a particular kernel module
without downloading, without installing, without booting, from
- the kernel source repository
- the debian source package
- the debian binary package
- the running
Hi,
how can I find out the version number of a particular kernel module
without downloading, without installing, without booting, from
- the kernel source repository
- the debian source package
- the debian binary package
- the running kernel, or the loaded modules
I.e. I would like the
problem I am now facing is that I cannot compile that
version of the nvidia kernel module for the 2.6.32-3-amd64 kernel,
because it should be compiled with gcc-4.3, which is not installable
anymore. Is there a workaround to this problem, except of course
downgrading the whole system?
http
version 304.48-1.
The problem I am now facing is that I cannot compile that version of the
nvidia kernel module for the 2.6.32-3-amd64 kernel, because it should be
compiled with gcc-4.3, which is not installable anymore. Is there a
workaround to this problem, except of course downgrading the
problem I am now facing is that I cannot compile that version of the
nvidia kernel module for the 2.6.32-3-amd64 kernel, because it should be
compiled with gcc-4.3, which is not installable anymore. Is there a
workaround to this problem, except of course downgrading the whole system?
Thanks
Hello,
Is there a way to plot/list the time each kernel module was
loaded/registered with the kernel?
I've tried bootchart2 but this doesn't give the list of kernel modules.
I've looked at the output of dmesg but I can't tell which modules are
loaded by udev and which o
predefined location (a network share such as samba/ssh/ftp
or from external device).
> I thought adding a new RAID card module to the installation would be as
> "easy" as adding a closed-source firmware network adapter module such as
> bnx2... but it looks like this is not
On Thu, 2012-08-09 at 07:46 -0700, ML mail wrote:
> Hi,
>
>
> I have a new LSI MegaRAID card which is not recognized by the Debian 6.0
> squeeze installer so I thought I would modify the initrd.gz installation
> image which gets loaded at PXE boot in order to include my self-compiled
> latest
PM
Subject: Re: How to add self-compiled kernel module in debian installation
On Thu, 09 Aug 2012 08:50:47 -0700, ML mail wrote:
> Indeed yes, I managed to compile the megaraid_sas module by using an
> older version of it (looks like the latest source code from LSI has an
> issue with D
using Debian's preseed so going to the server and add a USB
> key is not really an option.
Mmm... then maybe you can add the kernel module to the ISO before you
burn the image into a CD/DVD :-?
> Can't I somehow modify the PXE netinstall initrd.gz image to add there
> dire
x27;s exactly what I
would like to avoid as I want to setup a fully automated installation using
Debian's preseed so going to the server and add a USB key is not really an
option. Can't I somehow modify the PXE netinstall initrd.gz image to add there
directly my self-compiled version of th
SCSI card drivers are not located in the
> initrd.gz image.
>
> Do you know where and how I can get my version of megaraid_sas.ko module
> driver loaded at installation time instead of the default one?
A dirty trick can be placing/copying the kernel module under "/lib/
modules/$(uname
Hi,
I have a new LSI MegaRAID card which is not recognized by the Debian 6.0
squeeze installer so I thought I would modify the initrd.gz installation image
which gets loaded at PXE boot in order to include my self-compiled latest
version of that module (megaraid_sas.ko). I unpacked then the in
> I'm guessing you are not using the Debian packages, because otherwise
> you would have:
>
> ,[ /etc/modprobe.d/nvidia-kernel-common.conf ]
> | alias char-major-195* nvidia
> | options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44
> NVreg_DeviceFileMode=0660
> | # To enable FastWrites a
On Fri, 30 Dec 2011 20:58:57 -0300, David Roguin wrote:
> I have this problem, nouveau it's getting loaded at the beginning of the
> boot sequence, and then when X tries to load the nvidia module it
> crashes saying the graphic card is already being used. If I manually
> remove the nouveau module
On 31/12/11 10:58, David Roguin wrote:
> Hi,
>
> I have this problem, nouveau it's getting loaded at the beginning of
> the boot sequence, and then when X tries to load the nvidia module it
> crashes saying the graphic card is already being used. If I manually
> remove the nouveau module and modpr
On Vi, 30 dec 11, 20:58:57, David Roguin wrote:
> Hi,
>
> I have this problem, nouveau it's getting loaded at the beginning of
> the boot sequence, and then when X tries to load the nvidia module it
> crashes saying the graphic card is already being used. If I manually
> remove the nouveau module
Hi,
I have this problem, nouveau it's getting loaded at the beginning of
the boot sequence, and then when X tries to load the nvidia module it
crashes saying the graphic card is already being used. If I manually
remove the nouveau module and modprobe nvidia, everything works fine.
I've tried remo
On Sun, 11 Dec 2011 16:55:24 +, kuLa wrote:
> On 11/12/11 14:45, Camaleón wrote:
>> On Sat, 10 Dec 2011 11:53:15 +, kuLa wrote:
>>
>>> just yesterday after upgrade on testing strange issue appeared. Gnome3
>>> stopped to start with gnome-shell in favour on Gnome Classic. Some
>>> tests sho
On 11/12/11 14:45, Camaleón wrote:
On Sat, 10 Dec 2011 11:53:15 +, kuLa wrote:
just yesterday after upgrade on testing strange issue appeared. Gnome3
stopped to start with gnome-shell in favour on Gnome Classic. Some tests
showed that popper module is loaded but gnome/gdm3 can't see/recogni
On Sat, 10 Dec 2011 11:53:15 +, kuLa wrote:
> just yesterday after upgrade on testing strange issue appeared. Gnome3
> stopped to start with gnome-shell in favour on Gnome Classic. Some tests
> showed that popper module is loaded but gnome/gdm3 can't see/recognized
> it.
By "proper" module yo
Hi all,
just yesterday after upgrade on testing strange issue appeared.
Gnome3 stopped to start with gnome-shell in favour on Gnome Classic.
Some tests showed that popper module is loaded but gnome/gdm3 can't
see/recognized it.
And now the strange part; restart of gdm3 is bringing me a gnome-she
I switched to custom kernel and came across this thread. I also use
squeeze and this is what I have found.
First of, Debian has the following versions of nvidia-kernel-dkms packages:
squeeze: 195.36.31-6
sid/wheezy: 260.19.44-1
experimental: 270.30-1
The version in squeeze fail on anything above
I switched to custom kernel and came across this thread. I also use
squeeze and this is what I have found.
First of, Debian has the following versions of nvidia-kernel-dkms packages:
squeeze: 195.36.31-6
sid/wheezy: 260.19.44-1
experimental: 270.30-1
The version in squeeze fail on anything above
notice. I am using it right now all I want to do is very very
simple: how do I build just a kernel module from source of a running
kernel.
I do have the source, I just want to make it the debian way until
linux 2.6.40 comes out with this exact driver.
thanks
--
Mathieu
--
To UNSUBSCRIBE, email
g this wireless
> driver.
> I tried the brutal approach of building the entire kernel, see below.
>
> All I am looking for is a simple page where it would describe the
> step to build a specific kernel module on a debian machine.
>
> apt-get source linux-2.6
> cd linux
I am looking for is a simple page where it would describe the
step to build a specific kernel module on a debian machine.
apt-get source linux-2.6
cd linux-2.6-2.6.38
patch -p1 < ~/Downloads/wireless-next-2.6.38.patch
dpkg-buildpackage -rfakeroot -us -uc
But this fails with:
-->
MRH writes:
>On 23/01/11 04:53, Cameron Hutchison wrote:
>> and I had to revert two commits to fix it:
>>
>> 7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to
>> regenerate kernel.release file when make kernelrelease)
>>
>> 01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: "make ke
On 23/01/11 04:53, Cameron Hutchison wrote:
"tv.deb...@googlemail.com" writes:
The problem with extraversion and 2.6.37 is known, it's been reported
here if I remember, look for a message starting with "kernel-package:
2.6.37" in the archives. But since it seems to affect only proprietary
soft
On 22/01/11 23:03, tv.deb...@googlemail.com wrote:
[...]
I have the same setup, I build my kernel (2.6.37 currently) with
kernel-package and both nvidia and VirtualBox 4 work fine (they build
automatically with dkms). I don't use extraversion, only
--append-to-version and --revision.
The problem
"tv.deb...@googlemail.com" writes:
>The problem with extraversion and 2.6.37 is known, it's been reported
>here if I remember, look for a message starting with "kernel-package:
>2.6.37" in the archives. But since it seems to affect only proprietary
>software I guess they'll have to adapt.
Since
On Saturday 22 January 2011 13:24:08 MRH wrote:
> Recently I updated VirtualBox from 3.2 to 4.0 (non OSE version). From
> that moment it stopped working, saying that the kernel driver (vboxdrv)
> is not loaded and suggesting to run /etc/init.d/vboxdrv setup
>
> This fails:
> --
> Stopping V
>On the 22/01/2011 23:20, MRH wrote:
>> On 22/01/11 19:42, Boyd Stephen Smith Jr. wrote:
>> In<4d3b20c8.3080...@o2.pl>, MRH wrote:
>>>CC [M]
>>> /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
>>> In file included from
>>> /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox
On 22/01/11 19:42, Boyd Stephen Smith Jr. wrote:
In<4d3b20c8.3080...@o2.pl>, MRH wrote:
CC [M] /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
In file included from
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
from
/var/lib/dkms/vboxho
In <4d3b20c8.3080...@o2.pl>, MRH wrote:
> CC [M] /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
>In file included from
>/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
> from
>/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/../SUPDrvInternal
Hi,
You're not gonna get much help using non-free software on a tarnished
kernel. That said, when i have problems with VBox i just purge
everything, dkms included, make sure the drivers are actually deleted,
then reinstall, with dkms. Usually does the trick.
HTH,
Nuno
--
Mars 2 Stay!
http://xkc
Recently I updated VirtualBox from 3.2 to 4.0 (non OSE version). From
that moment it stopped working, saying that the kernel driver (vboxdrv)
is not loaded and suggesting to run /etc/init.d/vboxdrv setup
This fails:
--
Stopping VirtualBox kernel modules:done..
Uninstalling old VirtualBo
On 2010-08-20 02:49 +0200, Mark Allums wrote:
> On 8/19/2010 4:25 AM, Sven Joachim wrote:
>> On 2010-08-19 10:25 +0200, David Baron wrote:
>>
>>> Kernels 2.6.33 and on apparently do support Nouveau. I see no option offered
>>> in make menuconfig to compile the module.
>>>
>>> How do I get it ?
>>
On 8/19/2010 4:25 AM, Sven Joachim wrote:
On 2010-08-19 10:25 +0200, David Baron wrote:
Kernels 2.6.33 and on apparently do support Nouveau. I see no option offered
in make menuconfig to compile the module.
How do I get it ?
Device Drivers -> Staging drivers -> Nouveau (nVidia) cards
Sven
On 2010-08-19 10:25 +0200, David Baron wrote:
> Kernels 2.6.33 and on apparently do support Nouveau. I see no option offered
> in make menuconfig to compile the module.
>
> How do I get it ?
Device Drivers -> Staging drivers -> Nouveau (nVidia) cards
Sven
--
To UNSUBSCRIBE, email to debian-u
Kernels 2.6.33 and on apparently do support Nouveau. I see no option offered
in make menuconfig to compile the module.
How do I get it ?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http
On 2010-07-18 21:02 +0200, Greg Madden wrote:
> Thanks, what I don't understand though is why when gcc is installed it does a
> symlink to gcc-4.4, on Squeeze.
Because gcc-4.4 is the default compiler, but the kernel has been
compiled with gcc-4.3 (mainly to avoid regressions that may show up whe
On Sunday 18 July 2010 09:31:46 Sven Joachim wrote:
> On 2010-07-18 19:18 +0200, Greg Madden wrote:
> > to make it work with the stuff from Nvidia's site,
> >
> > 1. Squeeze kernel 2.6.32-5 is configured with gcc 4.3.5
> > 2. gcc that is installed on Squeeze is 4.4.4 & 4.3.5
> > 3. installing gcc c
On 2010-07-18 19:18 +0200, Greg Madden wrote:
> to make it work with the stuff from Nvidia's site,
>
> 1. Squeeze kernel 2.6.32-5 is configured with gcc 4.3.5
> 2. gcc that is installed on Squeeze is 4.4.4 & 4.3.5
> 3. installing gcc creates a symbolic link to version of gcc-4.4.4
> 4. gcc is a
sage about the CC check that failed because the gcc version that
> was used to compile my kernel was not the same as the one used to
> compile the driver and I also see the "compiling kernel module"
> progress bar filling up to 100%. After this, I get the following
> message
essage about the
> CC check that failed because the gcc version that was used to compile my
> kernel was not the same as the one used to compile the driver and I also
> see the "compiling kernel module" progress bar filling up to 100%. After
> this, I get the following message:
&g
On Sun, Jul 18, 2010 at 12:48 PM, Mathieu Malaterre
wrote:
> On Sun, Jul 18, 2010 at 11:22 AM, Jason Filippou
> wrote:
> ...
>> Which steps should I follow to compile the NVIDIA driver into the new kernel?
>
> Are you using squeeze ? If so I would suggest:
>
> http://packages.debian.org/squeeze/n
provided by NVIDIA.
>
> I would recommend to use the Debian packages (nvidia-glx etc.) instead.
>
>> In both cases, I get the ordinary
>> message about the CC check that failed because the gcc version that
>> was used to compile my kernel was not the same as t
d.
> In both cases, I get the ordinary
> message about the CC check that failed because the gcc version that
> was used to compile my kernel was not the same as the one used to
> compile the driver and I also see the "compiling kernel module"
> progress bar filling up
On Sun, Jul 18, 2010 at 11:22 AM, Jason Filippou
wrote:
...
> Which steps should I follow to compile the NVIDIA driver into the new kernel?
Are you using squeeze ? If so I would suggest:
http://packages.debian.org/squeeze/nvidia-kernel-dkms
-> apt-get install nvidia-kernel-dkms
I am using modu
same as the one used to
compile the driver and I also see the "compiling kernel module"
progress bar filling up to 100%. After this, I get the following
message:
"Unable to load the kernel module 'nvidia.ko'. This happens most
frequently when this kernel module was build a
Le 14783ième jour après Epoch,
Alexander Samad écrivait:
> Okay, thats a bit extreme, m-a seems to be able to build a module with
> just the headers.
>
> so all I want to do is rebuild qcserial, patched it to add new id.
> don't need to produce a deb.
>
> what i tried was installed the linux-sourc
y, you
> have to rebuild whole kernel (install kernel-package and see make-kpkg
> manual for details).
>
> On Wed, Jun 23, 2010 at 02:41:45PM +1000, Alexander Samad wrote:
>> I need to make a quick change to a kernel module, I would like to just
>> get the source and make t
Alex,
You can't rebuild single module. If you wanna do it the Debian way, you
have to rebuild whole kernel (install kernel-package and see make-kpkg
manual for details).
On Wed, Jun 23, 2010 at 02:41:45PM +1000, Alexander Samad wrote:
> I need to make a quick change to a kernel module,
I need to make a quick change to a kernel module, I would like to just
get the source and make the change and build.
How can I build ??? I did a google, but couldn't find the debian way
of building with linux-headers..
Alex
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debia
On Sun, Nov 01, 2009 at 12:18:03PM +0100, Klistvud wrote:
> Howdie, fellow Debianites!
>
> Is there a command for passing arguments to a running kernel module on
> the fly, without rmmoding and re-modprobing it?
Yes . /proc/module/$MODULE/parameters
For instance, let's l
Howdie, fellow Debianites!
Is there a command for passing arguments to a running kernel module on
the fly, without rmmoding and re-modprobing it? Echoing new value(s) to
the /proc subtree has long been deprecated now, and the new /sys
interface seems largely to be read-only ... besides
On Tue, Sep 22 2009, sobtwmxt wrote:
> Manoj Srivastava ieee.org> writes:
>
>>
>> As mentioned in another post in this thread, the installed
>> modules are stripped of debugging information. make-kpkg can now
>> create a linux-debug-** package that has detached debug information, to
>
Manoj Srivastava ieee.org> writes:
>
> As mentioned in another post in this thread, the installed
> modules are stripped of debugging information. make-kpkg can now
> create a linux-debug-** package that has detached debug information, to
> be used for debugging, as needed.
>
>
On Mon, Sep 21 2009, sobtwmxt wrote:
> I have built a custom kernel, using make-kpgk, from debian source.
> Using ls -l, there is difference in the size of kernel modules, .ko
> files, at build place and after installation of the package. I
> only looked at 2 unrelated modules, but I think th
Hi,
Does the install software strip extra symbols from the driver?
$ ls -l /lib/modules/2.6.31/kernel/drivers/video/nvidia.ko
-rw-r--r-- 1 root root 9.2M 2009-09-13 03:59
/lib/modules/2.6.31/kernel/drivers/video/nvidia.ko
$ strip nvidia.ko
$ ls -l nvidia.ko
-rw-r--r-- 1 war users 7.9M 2009-0
sobtwmxt wrote:
> Emanoil Kotsev yahoo.com> writes:
>
>>
>> are you using the same filesystem on both (i.e. ext3)?
>>
>
>
> It is ext3 on both.
then may be the disks are different type?
do on both machines as root
fdisk -l /dev/
i.e.
fdisk -l /dev/sda
Disk /dev/sda: 80.0 GB, 8002636185
Emanoil Kotsev yahoo.com> writes:
>
> are you using the same filesystem on both (i.e. ext3)?
>
It is ext3 on both.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
sobtwmxt wrote:
> I have built a custom kernel, using make-kpgk, from debian source.
> Using ls -l, there is difference in the size of kernel modules, .ko
> files, at build place and after installation of the package. I
> only looked at 2 unrelated modules, but I think there will be a
> differe
I have built a custom kernel, using make-kpgk, from debian source.
Using ls -l, there is difference in the size of kernel modules, .ko
files, at build place and after installation of the package. I
only looked at 2 unrelated modules, but I think there will be a
difference in the size of other
I am trying to debug a kernel module (thinkpad_acpi in this case). I
know that because it is in the kernel I cannot just hook up a debugger
or anything without UML or a second machine kind-of-thing which will
probably take too much time for me at the moment.
I tried recompiling the kernel with
On Mon, Apr 27, 2009 at 08:27:04AM +0200, Jeroen Steenbeeke wrote:
> Yup, that did it!
> Booted with the regular 2.6.26-2-amd64 kernel, did m-a a-i -l
> 2.6.26-2-xen-amd64 atl2-source, and then rebooted with the amd64 kernel -
> and the network worked!
> Thanks a lot!
> - Jeroen
>
No problem, gla
Yup, that did it!
Booted with the regular 2.6.26-2-amd64 kernel, did m-a a-i -l
2.6.26-2-xen-amd64 atl2-source, and then rebooted with the amd64 kernel -
and the network worked!
Thanks a lot!
- Jeroen
2009/4/27 Michael Pobega
> On Sun, Apr 26, 2009 at 10:50:05PM +0200, Jeroen Steenbeeke wrote:
>
On Sun, Apr 26, 2009 at 10:50:05PM +0200, Jeroen Steenbeeke wrote:
> Hey everyone,
>
> I am having some problems with my server setup, and I'm starting to go crazy
> trying to figure this out. I want to use my computer to host a couple of Xen
> guests, but no matter what I do, I keep running into
Hey everyone,
I am having some problems with my server setup, and I'm starting to go crazy
trying to figure this out. I want to use my computer to host a couple of Xen
guests, but no matter what I do, I keep running into problems. I've tried 4
different versions of a certain popular Debian based d
1 - 100 of 337 matches
Mail list logo
