Re: Invalid module format
On Sat, Feb 24, 2018 at 10:45 AM, Alex Arvelaez wrote: > > On Feb 24, 2018 12:07 AM, Srishti Sharma wrote: > > > > > > > > On Sat, Feb 24, 2018 at 4:59 AM, Tobin C. Harding wrote: > >> > >> On Thu, Feb 22, 2018 at 02:42:23AM +0530, Srishti Sharma wrote: > >> > Hello, > >> > > >> > While trying to load a module from the linux-next branch > >> > >> Do you mean from linux-next tree or from a branch called linux-next in > >> some other tree? (Not that it matters that much :) > >> > >> >, I get the error > >> > that the module format is invalid, this was because the kernel I > compiled > >> > was different from the kernel I was trying to load the module into, > so I > >> > installed the kernel from the same source as the module, and it > booted for > >> > only once right after the installation. When I try to boot into the > same > >> > kernel, my system reboots. What should I do so that I am able to boot > into > >> > it everytime ? > >> > >> What are you trying to achieve? Are you doing testing on linux-next or > >> do you just want to use the module? If you just want to use the module > >> you could build the module for the current running kernel instead of > >> rebuilding the kernel. Copy the module someplace and write a new > >> makefile same as you would if you were developing your own [test] > >> modules. > >> > >> (For the record I happened to be trying to learn about linux-next myself > >> this morning and built a kernel that just goes into a reboot loop > >> without even getting to the grub menu. It boots in a VM though so now > >> I'm playing with the cofig.) > >> > > Something was wrong with the configuration file, so I copied the > configuration of my running kernel and it boots now, but after running > make, the modules don't get generated, so there is something I am missing > in the configuration options again :( > > Are they getting built? did you do make modules_install? > After compilation I got .o files and not .ko , I used make . Regards, Srishti > > Regards, > > Srishti > > > > > >> > >> Hope this helps, > >> Tobin. > > > > > > Regards, > > Alex > ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Invalid module format
On Feb 24, 2018 12:07 AM, Srishti Sharma wrote: > > > > On Sat, Feb 24, 2018 at 4:59 AM, Tobin C. Harding wrote: >> >> On Thu, Feb 22, 2018 at 02:42:23AM +0530, Srishti Sharma wrote: >> > Hello, >> > >> > While trying to load a module from the linux-next branch >> >> Do you mean from linux-next tree or from a branch called linux-next in >> some other tree? (Not that it matters that much :) >> >> >, I get the error >> > that the module format is invalid, this was because the kernel I compiled >> > was different from the kernel I was trying to load the module into, so I >> > installed the kernel from the same source as the module, and it booted for >> > only once right after the installation. When I try to boot into the same >> > kernel, my system reboots. What should I do so that I am able to boot into >> > it everytime ? >> >> What are you trying to achieve? Are you doing testing on linux-next or >> do you just want to use the module? If you just want to use the module >> you could build the module for the current running kernel instead of >> rebuilding the kernel. Copy the module someplace and write a new >> makefile same as you would if you were developing your own [test] >> modules. >> >> (For the record I happened to be trying to learn about linux-next myself >> this morning and built a kernel that just goes into a reboot loop >> without even getting to the grub menu. It boots in a VM though so now >> I'm playing with the cofig.) >> > Something was wrong with the configuration file, so I copied the > configuration of my running kernel and it boots now, but after running make, > the modules don't get generated, so there is something I am missing in the > configuration options again :( Are they getting built? did you do make modules_install? > Regards, > Srishti > > >> >> Hope this helps, >> Tobin. > > Regards, Alex ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Invalid module format
On Sat, Feb 24, 2018 at 4:59 AM, Tobin C. Harding wrote: > On Thu, Feb 22, 2018 at 02:42:23AM +0530, Srishti Sharma wrote: > > Hello, > > > > While trying to load a module from the linux-next branch > > Do you mean from linux-next tree or from a branch called linux-next in > some other tree? (Not that it matters that much :) > > >, I get the error > > that the module format is invalid, this was because the kernel I compiled > > was different from the kernel I was trying to load the module into, so I > > installed the kernel from the same source as the module, and it booted > for > > only once right after the installation. When I try to boot into the same > > kernel, my system reboots. What should I do so that I am able to boot > into > > it everytime ? > > What are you trying to achieve? Are you doing testing on linux-next or > do you just want to use the module? If you just want to use the module > you could build the module for the current running kernel instead of > rebuilding the kernel. Copy the module someplace and write a new > makefile same as you would if you were developing your own [test] > modules. > > (For the record I happened to be trying to learn about linux-next myself > this morning and built a kernel that just goes into a reboot loop > without even getting to the grub menu. It boots in a VM though so now > I'm playing with the cofig.) > > Something was wrong with the configuration file, so I copied the configuration of my running kernel and it boots now, but after running make, the modules don't get generated, so there is something I am missing in the configuration options again :( Regards, Srishti > Hope this helps, > Tobin. > ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Invalid module format
On Sat, 24 Feb 2018 10:29:33 +1100, "Tobin C. Harding" said: > (For the record I happened to be trying to learn about linux-next myself > this morning and built a kernel that just goes into a reboot loop > without even getting to the grub menu. OK, I'll bite - how can the kernel go into a reboot loop that doesn't get to the grub menu? (Hint: How does your system get from the BIOS splash screen to starting the kernel? :) (Though I've seen kernels that flash the screen like they're rebooting but they're actually hung in a loop, and I've heard some great bar stories about kexec/kdump gone horribly astray and re-invoking the current kernel rather than the kexec target kernel) pgpPWYLSpDWRW.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Invalid module format
On Thu, Feb 22, 2018 at 02:42:23AM +0530, Srishti Sharma wrote: > Hello, > > While trying to load a module from the linux-next branch Do you mean from linux-next tree or from a branch called linux-next in some other tree? (Not that it matters that much :) >, I get the error > that the module format is invalid, this was because the kernel I compiled > was different from the kernel I was trying to load the module into, so I > installed the kernel from the same source as the module, and it booted for > only once right after the installation. When I try to boot into the same > kernel, my system reboots. What should I do so that I am able to boot into > it everytime ? What are you trying to achieve? Are you doing testing on linux-next or do you just want to use the module? If you just want to use the module you could build the module for the current running kernel instead of rebuilding the kernel. Copy the module someplace and write a new makefile same as you would if you were developing your own [test] modules. (For the record I happened to be trying to learn about linux-next myself this morning and built a kernel that just goes into a reboot loop without even getting to the grub menu. It boots in a VM though so now I'm playing with the cofig.) Hope this helps, Tobin. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: I'd like to contribute but I don't know how...
On Thu, Feb 22, 2018 at 09:25:39PM +, Alex Arvelaez wrote: > On Thu, Feb 22, 2018 at 04:12:14AM +, Alex Arvelaez wrote: > > On Wed, Feb 21, 2018 at 10:20:07PM -0500, valdis.kletni...@vt.edu wrote: > > > On Thu, 22 Feb 2018 02:33:08 +, Alex Arvelaez said: > > > > Hello, > > > > > > > > I'd like to contribute to the linux kernel eventually but I'm not sure > > > > > > https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html > > > > > > > how, I grabbed a copy of the source code and I found a FIXME that looks > > > > like I could fix: > > > > > > > > /* File: /usr/src/linux/tools/perf/util/string.c > > > > * FIXME: replace this with an expression using log10() when we > > > > * find a suitable implementation, maybe the one in the dvb drivers... > > > > */ > > > > > > Step 0: Verify that the comment still matches the code, *and* that the > > > change > > > is still desired. Hint: Why do they want log10()? What does the current > > > code > > > do? What, if anything, will break if you change it? > > > > I went ahead and used log10() from -lm, everything seems to work > properly from what I can see. I made a patch with my changes should > I send that to the linux-kernel mailing list for feedback? Documentation/process/ is your friend. Tobin ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: sound driver reference
On Fri, 23 Feb 2018 21:11:37 +0530, Muni Sekhar said: > Iâve an audio hardware with eight audio engines and it supports > âPCM/I2S Inputs , PCM/I2S Outputs, ADC (Analogue Line Inputs), DAC > (Analogue Line Outputs), Digital Microphoneâ interfaces. All these > interfaces are implemented on Xilinx FPGA image Well, that's a stumbling block.. First question is, of course, "is this a PCI card, or USB, or something weird that will need its own bus model" > existing sound driver(without platform driver) for reference. Does the > Linux kernel already has sound driver to support this type of > hardware? > Can anyone point me the reference code for this? It's very unlikely there's a "reference code" for an FPGA image (because, by definition, an FPGA is subject to being tweaked and modified). You'll need to talk to whoever created the Xilinx image, and find out whether the ADC and PCM and all the rest are equivalent, or at least similar, to existing drivers. If all those devices try *really* hard to look exactly like every other AC97 device out there, you might get away with just adding your device ID and let a driver claim it. If the ADC is some creeping-horror creation of their own with an API different from any other ADC out there, you're going to be in for a really bad time. pgp7BbDjE5XjV.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
sound driver reference
Hi All, I’ve an audio hardware with eight audio engines and it supports “PCM/I2S Inputs , PCM/I2S Outputs, ADC (Analogue Line Inputs), DAC (Analogue Line Outputs), Digital Microphone” interfaces. All these interfaces are implemented on Xilinx FPGA image and it connects to host CPU(Intel based chip) on PCIe bus in Linux platform. I need to implement a sound driver for this. I’m looking for an existing sound driver(without platform driver) for reference. Does the Linux kernel already has sound driver to support this type of hardware? Can anyone point me the reference code for this? I appreciate any help. -- Thanks, Sekhar ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Year 2038 time set problem
On Fri, 23 Feb 2018 15:13:30 +0530, techi eth said: > Which Linux kernel version have Year 2038 problem solved for Linux running > on 32 Bit system. > > https://en.wikipedia.org/wiki/Year_2038_problem Did you read references 15 through 17 on that page? Also, the answer isn't a strict "Linux v5.91 fixes it" - the problem wasn't fixed in one commit. So for instance, some filesystems had 64 bit timestamps from the very beginning, while there's probably at least one or two that still need work. And if your problem is that you've got some ancient ext2 file system images that you have to keep around for forensic reasons, no kernel version is going to help (And yes, that could happen - as part of my job, I've had to keep disk images around for close to a decade due to ongoing legal action, and I've got users who need to keep research data for 30 years due to grant restrictions). So the *real* question here is - what data/hardware/whatever are you looking at where the 2038 problem is possibly relevant? pgp_o7iFQZnBm.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Year 2038 time set problem
Hi, Which Linux kernel version have Year 2038 problem solved for Linux running on 32 Bit system. https://en.wikipedia.org/wiki/Year_2038_problem ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
