[ solved ] Do I have a modinfo problem?

[wedgetail]

I am in the process of trying to find out why MiniMe on an:

Code: [Select]

[root@localhost gert]# lspci -v -s 01:00
01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) (prog-if 00 [VGA controller])
Can not use the native resolution, I have to fall back to something like 800x600 for a 1920x1080 wide screen LCD

In the process I have returned to my nvidia fitted pc and was checking:

Code: [Select]

[root@localhost gert]# lsmod |grep nvidia
nvidia               9601218  40
i2c_core               16500  11 nvidia,tda1004x,saa7134_dvb,tuner_simple,tda9887,tda8290,tuner,saa7134,v4l2_common,videodev,tveeprom
[root@localhost gert]# modinfo nvidia
modinfo: could not find module nvidia
[root@localhost gert]#
My shaky understanding is that if you have a module then you can find out more about it with modinfo, but not this time?

What does it mean?  Do I have a problem?

The system seems to run fine?

[AS]

try:
modinfo nvidia-current

 

AS

[muungwana]

whats the output of this command?

find /lib/modules/`uname -r` -iname *nvidia*

ps:
copy and paste it on the terminal

[wedgetail]

muungwana
Thanks, I will return the details tomorrow as it is well pat midnight here and I will not be switching back tonight/today/tomorrow ?? 

I have just returned to the original problem desktop machine to see if I can get something from AndrzejL's post on ATI

MiniMe seems to have picked the correct 1920x1080 resolution but the screen window is about 20% smaller so everything is sitting out left in space where I can not see it and the panel has dropped under the screen too 

[wedgetail]

muungwana
Here is the output of:

Code: [Select]

[gert@localhost ~]$ find /lib/modules/`uname -r` -iname *nvidia*
/lib/modules/2.6.38.6-pclos1.bfs/kernel/drivers/char/drm/nvidia96xx.ko.gz
/lib/modules/2.6.38.6-pclos1.bfs/kernel/drivers/char/drm/nvidia173.ko.gz
/lib/modules/2.6.38.6-pclos1.bfs/kernel/drivers/char/drm/nvidia-current.ko.gz
/lib/modules/2.6.38.6-pclos1.bfs/kernel/drivers/video/nvidia
/lib/modules/2.6.38.6-pclos1.bfs/kernel/drivers/video/nvidia/nvidiafb.ko.gz
/lib/modules/2.6.38.6-pclos1.bfs/kernel/drivers/video/backlight/mbp_nvidia_bl.ko.gz
[gert@localhost ~]$ modinfo nvidia-current

I love above command line input, find and I do not agree, great trouble getting it to work it seems, it is so bad that I hardly ever consider using it. Perhaps one day.    Though this was not what I was after.

as
Yes this was the info I was after. What is the secret?  I was assuming that lsmod |grep nvidia would have caught that one too??

Code: [Select]

[gert@localhost ~]$ modinfo nvidia-current
filename:       /lib/modules/2.6.38.6-pclos1.bfs/kernel/drivers/char/drm/nvidia-current.ko.gz
alias:          char-major-195-*
supported:      external
license:        NVIDIA
alias:          pci:v000010DEd00000E00sv*sd*bc04sc80i00*
alias:          pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
alias:          pci:v000010DEd*sv*sd*bc03sc02i00*
alias:          pci:v000010DEd*sv*sd*bc03sc00i00*
depends:        i2c-core
vermagic:       2.6.38.6-pclos1.bfs SMP preempt mod_unload modversions 686
parm:           NVreg_EnableVia4x:int
parm:           NVreg_EnableALiAGP:int
parm:           NVreg_ReqAGPRate:int
parm:           NVreg_EnableAGPSBA:int
parm:           NVreg_EnableAGPFW:int
parm:           NVreg_Mobile:int
parm:           NVreg_ResmanDebugLevel:int
parm:           NVreg_RmLogonRC:int
parm:           NVreg_ModifyDeviceFiles:int
parm:           NVreg_DeviceFileUID:int
parm:           NVreg_DeviceFileGID:int
parm:           NVreg_DeviceFileMode:int
parm:           NVreg_RemapLimit:int
parm:           NVreg_UpdateMemoryTypes:int
parm:           NVreg_InitializeSystemMemoryAllocations:int
parm:           NVreg_UseVBios:int
parm:           NVreg_RMEdgeIntrCheck:int
parm:           NVreg_UsePageAttributeTable:int
parm:           NVreg_EnableMSI:int
parm:           NVreg_MapRegistersEarly:int
parm:           NVreg_RegisterForACPIEvents:int
parm:           NVreg_RegistryDwords:charp
parm:           NVreg_RmMsg:charp
parm:           NVreg_NvAGP:int
[gert@localhost ~]$

To make it easier on me, the MiniMe OS system on the older machine which I got to work delightfully, blew a fuse over night. (I think it was just to show me who is boss (gee I miss it already).  Shut down normally, then starting up this morning the process got past Installing root file system and then it seemed like a page or more of assembly code, quite fascinating. The system must have plowed into a snowdrift or something, I could not move it apart from the big switch.
Tried a couple of times, same result, later when starting kde 3.5.10 on the same drive, I recovered a fair bit of my hp printer work I was carrying out here, bet you my neck hair was standing out stiff at the thought of having lost that. Have copy now, pheeewww,  

I will see, late I will probably have a look at the problem, looks too juicy to just scrap. I believe to I have an Ace up my sleeve when I get time, the systdm does not know about that yet,  .

The hp inkjet printing problems is really getting up my nose so I am diverting my attention to help out here on higher priority.  This time I am not letting it go past until I have a clear understanding of what is going on.

Of course I count on you two amongst others when I have the back against the wall (again)  

[AS]

as
Yes this was the info I was after. What is the secret?  I was assuming that lsmod |grep nvidia would have caught that one too??

the module has filename "nvidia-current.ko.gz" but it's "registered" in kernel, (thus exposed from lsmod) with the name "nvidia", it's the "same" module.

[muungwana]

I usually add "*" around any string i am searching for because the result will contain the string i typed and all related strings.

Below command would have given you the output you were looking for and inform you that the module use a different module name

lsmod |grep *nvidia*

find command is a great tool and with everything else, extra easy to use if you know how to use it correctly  , i asked you run it because i wanted to see what kernel modules you have, you should see that you dont have "nvidia" module but "nvidia173.ko.gz" and "nvidia-current.ko.gz"

[Just17]

Below command would have given you the output you were looking for and inform you that the module use a different module name

lsmod |grep *nvidia*

Code: [Select]

[user@Dell ~]$ lsmod | grep *nvidia*
[user@Dell ~]$

    

Code: [Select]

[user@Dell ~]$ lsmod | grep nvidia
nvidia               9607598  38
i2c_core               16500  10 i2c_i801,nvidia,tda18218,af9013,dvb_usb_af9015,dvb_usb,em28xx,v4l2_common,videodev,tveeprom
[user@Dell ~]$
 

[wedgetail]

Just19
  I second that, I tried something similar just before going to bed. Shook my head and my linux confidence again took a dive.

as & muungwana
I appreciate your explanations. I learnt something.