udev failing to produce device node, I think

[AS]

Additional info for you, here: 

http://www.pclinuxos.com/forum/index.php/topic,104499.0.html

AS

[wedgetail]

AS
I am taking your advice on this make experimenting, I need to study a bit more.  I believe the nGene in pclinuxos is only for single channel cards, my card is dual channels.  The make I rushed into was for dual channel operation, ie I need to set up two adapters for full operation (not that this is needed for it to work as single channel I don't think)

I will come back and ask when I consider making again.   

[wedgetail]

Approaching ngene and make slightly different. After having downloaded linux source files, actually this was in the kernel 3.2.15 which I am playing with a bit, it occurred to me to explore a bit around ngene.

/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/Kconfig
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/Makefile
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene-cards.c
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene-core.c
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene-dvb.c
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene-i2c.c
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene.h

[root@KDE-mini-kernel3x gert]#

I made a copy of those files in a new directory /btest and decided to run make, thinking well these files were used to build the ngene module in pclinuxos, so this should be a safe bet  

One of the the shortest make runs of the few I have made.

make: *** No targets.  Stop.

Looking at the Makefile

#
# Makefile for the nGene device driver
#

ngene-objs := ngene-core.o ngene-i2c.o ngene-cards.o ngene-dvb.o


obj-$(CONFIG_DVB_NGENE) += ngene.o

ccflags-y += -Idrivers/media/dvb/dvb-core/
ccflags-y += -Idrivers/media/dvb/frontends/
ccflags-y += -Idrivers/media/common/tuners/

# For the staging CI driver cxd2099
ccflags-y += -Idrivers/staging/media/cxd2099/

This file does seem a bit short of directives?  Though the ngene module is available so it must have been compiled?

Questions?
1.. How is this makefile to be used?
2.. How do I compile ngene module

[AS]

You need to recompile the whole kernel ...

Did you modified the driver source code ?

AS

[wedgetail]

No I have not changed any source code. I thought I would do a quick module make and compare with the original before I started tinkering with ngene. (If I got identical result I was intending to do some minor tinkering in the source code for ngene just to see what I can get away with  )

From what you are saying, I understand that whilst ngene is a loadable kernel module, it is built differently to one that I would build from those files in the ngene source directory?  

This link, which I accidentally came accros, gave me idea of trying to build loadable module from the existing files of ngene.

https://www.linux.com/learn/linux-career-center/23685-the-kernel-newbie-corner-your-first-loadable-kernel-module

Hmmm, if ngene was built at the time of the full kernel build how does this impact on trying to build another ngene module standalone?

[AS]

No I have not changed any source code. I thought I would do a quick module make and compare with the original before I started tinkering with ngene. (If I got identical result I was intending to do some minor tinkering in the source code for ngene just to see what I can get away with  )

If you didn't changed the source code, even if you build the module, you will get the same module as already provided from kernel-3.2.15 kernel package. So ? 

From what you are saying, I understand that whilst ngene is a loadable kernel module, it is built differently to one that I would build from those files in the ngene source directory?  

Most the the kernel's modules source code is written so that you can build it as a module or incorporated inside the kernel itself, depending on some external parameter ...

This link, which I accidentally came accros, gave me idea of trying to build loadable module from the existing files of ngene.

https://www.linux.com/learn/linux-career-center/23685-the-kernel-newbie-corner-your-first-loadable-kernel-module

Hmmm, if ngene was built at the time of the full kernel build how does this impact on trying to build another ngene module standalone?

Sorry, may be I misunderstood because you asked previously where to find the source code ... and indeed it is in the kernel source tree ... Are we speaking of the same source code ?

AS

[wedgetail]

I previously downloaded the kernel tree source code when I finally understood what you were hinting at (have done it on a couple of systems, but let us just assume I am using my kernel-3.2.15-pclos1 system.  Here I then go looking for ngene and find below, which to me looked like it would be possible to run a make.

I copied these files to a new directory   /btest (which I also had done with the simple exercise in the link previously posted)

/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/Kconfig
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/Makefile
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene-cards.c
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene-core.c
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene-dvb.c
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene-i2c.c
/usr/src/linux-3.2.15-pclos1/drivers/media/dvb/ngene/ngene.h
[root@KDE-mini-kernel3x gert]#

My intention was to prove that the ngene.ko I made would be the same as the one already in the kernel I am using.  This was to give me confidence that I might have understood correctly how to make a loadable ngene driver module from the driver source code existing in pclinuxos ( and not external code which may or may not have worked).

I am assuming that ngene is a loadable module, ie not built into the kernel, since I have to modprobe to get it installed.  I have better ask am I right on this point? ie ngene is not in the kernel (lost my confidence)    (If ngene was in the kernel I would have expected lsmod |grep negene to show some lines after a reboot?)

------

By searching the term  CONFIG_DVB_NGENE and looking in the Kconfig for ngene a few more bricks fell into place.  Now I believe I understand what you meant by saying

You need to recompile the whole kernel ...

The existing Makefile is simply not suitable for my intention.

The ngene module is built as part of a kernel build.  So if I want to do a separate ngene build my system now having a full kernel tree will have all the required files but I will have to figure out how to construct a  Makefile to serve this situation?  ZZZzzz......

[AS]

How about to do a step at once ? i.e. build a new kernel at first:

Code: [Select]

cd /usr/src/linux-3.2.15-pclos1
make mrproper
make oldconfig
make menuconfig
make

do not install it right now ... you could overwrite your current kernel installation 

[wedgetail]

Well that kept me awake   I think I had a bit of luck as I managed to think a bit before I launched into this in blind faith. Realising that your instructions could just be copied to konsole line by line.

A concern I had was, where does it all go?  I assumed that there was a lot more to know about these simple lines, googled a bit on mrproper which gave me some very helpful insight.

The build took a very long time I thought, around 40 min plus, that surprised me a bit.  I was very tempted to hit the panick button after 10-15 minutes, my coffee was cold by then.  I was expecting around 5 minutes with my machine.

No errors, but I did see a number of warnings go through. Any logs to be found after such and exercise?

BUT
When I ran make menuconfig I may have done something wrong, I was carefully exploring the items in the gui panel that popped up, entering into one level by SELECT and getting out unscathed by using ESC button however on the second selection something about CPU .... when I used ESC the make took off before I could blink.

I am tempted to run make mrproper and then carry on from here  

While the build was running I studied loosely

http://www.linuxchix.org/content/courses/kernel_hacking/lesson3

After the run I read a most interesting README file,

/usr/src/linux-3.2.15-pclos1/README

Time to put the kettle on again and do some thinking.  

[AS]

Well that kept me awake  

Welcome aboard! 

[wedgetail]

Used the CLEANUP by running the instructions again.  

[root@KDE-mini-kernel3x linux-3.2.15-pclos1]# make oldconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
#
# using defaults found in /boot/config-3.2.15-pclos1
#
#
# configuration written to .config
#
[root@KDE-mini-kernel3x linux-3.2.15-pclos1]#

[root@KDE-mini-kernel3x linux-3.2.15-pclos1]# make menuconfig
  HOSTCC  scripts/kconfig/lxdialog/checklist.o
  HOSTCC  scripts/kconfig/lxdialog/inputbox.o
  HOSTCC  scripts/kconfig/lxdialog/menubox.o
  HOSTCC  scripts/kconfig/lxdialog/textbox.o
  HOSTCC  scripts/kconfig/lxdialog/util.o
  HOSTCC  scripts/kconfig/lxdialog/yesno.o
  HOSTCC  scripts/kconfig/mconf.o
  HOSTLD  scripts/kconfig/mconf
scripts/kconfig/mconf Kconfig


*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.


[root@KDE-mini-kernel3x linux-3.2.15-pclos1]#

   here I used exit immediately and got back to the prompt line

[root@KDE-mini-kernel3x linux-3.2.15-pclos1]#

[root@KDE-mini-kernel3x linux-3.2.15-pclos1]# make >/home/gert/kernel-3.2.15-build-exercise.glk 2>&1
40 minutes plus?? later
[root@KDE-mini-kernel3x linux-3.2.15-pclos1]#

Since I redirected output to a file, I then followed the build in another konsole by tailin in real time the file I collected the output in.

tail -f /home/gert/kernel-3.2.15-build-exercise.glk

I received just over 104 warnings for about 15,400 lines of build.

Do I need to worry about the warnings?

Edit:
I am lost,  where is the new kernel?    
Errrh, temporary confusion has lifted after a long walk, at the moment reading this

/usr/src/linux-3.2.15-pclos1/README

Also when I discovered a lot of files hanging around file.c with the name files.o wherever I looked in the sources tree. Hope this is the correct term.
 
Since I probably need the make install step before I have my new kernel, I am settling back more relaxed.  Actually in the sources tree there seem to be a lot of interesting information files so I am going to look a bit closer.  Fascinating.

[AS]

I received just over 104 warnings for about 15,400 lines of build.
Do I need to worry about the warnings?

No, unless they refers to your own code. If the kernel's devs leave the code with that warning, you can safely assume they are just warnings without a real impact on the final result.

Edit:
I am lost,  where is the new kernel?    

Relax, you don't even need to know where it is, a couple of commands will take care about:

Code: [Select]

make modules_install
make install

Be sure to have an alternate kernel already installed and working, possibly a different one from 3.2.15, just in case you shall overwrite it.
It is rather normal that the first installation will not work as expected ... it is part of the learning process ...

AS

[wedgetail]

I have just inserted a stanza in GRUB to take me back to the  3.2.14-pclos7.bfs, booted up to test and all seemed well.

Relax, you don't even need to know where it is, .....

Must admit I expected that, hmmmm  

[root@KDE-mini-kernel3x linux-3.2.15-pclos1]# make modules_install
.................
.................
  INSTALL /lib/firmware/keyspan_pda/keyspan_pda.fw
  INSTALL /lib/firmware/keyspan_pda/xircom_pgs.fw
  INSTALL /lib/firmware/cpia2/stv0672_vp4.bin
  INSTALL /lib/firmware/yam/1200.bin
  INSTALL /lib/firmware/yam/9600.bin
  DEPMOD  3.2.15-pclos1
[root@KDE-mini-kernel3x linux-3.2.15-pclos1]# make install
sh /usr/src/linux-3.2.15-pclos1/arch/x86/boot/install.sh 3.2.15-pclos1 arch/x86/boot/bzImage \
                System.map "/boot"
[root@KDE-mini-kernel3x linux-3.2.15-pclos1]#

The moment of great interest has come  

Edit:

I rebooted and noticed two things. Approximately halfway through re-boot lines rolling nicely, then a flash and suddenly my text was much smaller. I think it was shortly after I just figured the the new kernel was being installed that I jumped a bit.  A little bit later something about proprietary driver could not be found/used and nouveau would be used instead.

When clicking on OK boot caried on and now all appears normal when writing this.  I will go to PCC and see if I can find the normal nVidia I use.   

[wedgetail]

I think I have a problem with the graphics driver, the system appears normal, PCC says it is the normal driver I use for nVidia.  Re-configured and during the process was told there was a proprietary driver, did I want to use this. I said yes and finished and rebooted.

Got the message about Xorg could not find the proprietary driver.  I will have a look tomorrow. Too late here. ZZZzzz.....

Edit:
Having gone through the graphics configuration using XFdrake, and accepting the use of a proprietary driver found.  Then when booting:

The proprietary driver for your graphics card can not be found, the system is now using the free software driver (nouveau)

Reason: The proprietary kernel driver not found for nvidia X.org driver

[wedgetail]

This is an interesting sidetrack and I am not sure if it is worth following up on it at this stage. Quite some months ago I remember seing some problems with nvidia drivers but I don't remember if I was having problems.  I know I continued using the nVidia driver as it seemed to give speed and great presentation.

Will google a bit.