Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
invalid req i2c
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
Gentree
Watchman
Watchman


Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe

PostPosted: Sun Jun 19, 2005 4:03 pm    Post subject: invalid req i2c Reply with quote

Code:

bash-3.00#em -uDp world

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[blocks B     ] sys-apps/sysvinit (is blocking sys-apps/baselayout-1.9.4-r6)
[ebuild     U ] sys-apps/man-pages-2.02 [2.01]
[ebuild     U ] x11-libs/wxGTK-2.4.2-r3 [2.4.2-r2]
[ebuild     U ] net-mail/mailbase-0.00-r9 [0.00-r8]
[ebuild     U ] x11-libs/startup-notification-0.8 [0.7]
[ebuild     UD] x11-base/opengl-update-2.1.1-r1 [2.2.1]
[ebuild     U ] sys-fs/dosfstools-2.11 [2.10-r1]
[ebuild     U ] app-cdr/gnomebaker-0.3 [0.2-r2]
[ebuild  NS   ] sys-apps/i2c-2.9.1 
[ebuild     U ] media-video/xine-ui-0.99.3-r1 [0.99.3]
[ebuild     U ] media-gfx/gimp-print-5.0.0_beta4 [4.2.7]
[ebuild     U ] net-misc/smb4k-0.5.2 [0.5.1]
[ebuild     U ] dev-util/cvs-1.11.20 [1.11.18]
[ebuild     U ] app-admin/sudo-1.6.7_p5-r4 [1.6.7_p5-r2]
[ebuild     U ] app-cdr/k3b-0.12.1 [0.11.24]




Code:
>>> md5 src_uri ;-) i2c-2.9.1.tar.gz
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     2.6.11-nitro2
 * 2.9.1 is only needed for kernel 2.4.x
 * You need to use the in-kernel I2C drivers for later kernels.

!!! ERROR: sys-apps/i2c-2.9.1 failed.
!!! Function pkg_setup, Line 28, Exitcode 0
!!! Non 2.4.x kernel detected
!!! If you need support, post the topmost build error, NOT this status message.



Code:
bash-3.00#grep -i "i2c" .config
# I2C support
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m
# I2C Algorithms
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
# I2C Hardware Bus support
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELEKTOR is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
CONFIG_I2C_ISA=m
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
# CONFIG_I2C_PCA_ISA is not set
CONFIG_I2C_SENSOR=m
# Other I2C Chip support
CONFIG_I2C_DEBUG_CORE=y
CONFIG_I2C_DEBUG_ALGO=y
CONFIG_I2C_DEBUG_BUS=y
CONFIG_I2C_DEBUG_CHIP=y

from lsmod:
Code:

i2c_viapro              9424  0
i2c_core               25744  1 i2c_viapro


Code:
#equery depends i2c
[ Searching for packages depending on i2c... ]
sys-apps/lm_sensors-2.9.0
!!! aux_get(): ebuild path for 'sys-kernel/nitro-sources-2.6.11-r0' not specified:
!!!            None


Now before bannishing this "unsupported" , I should say I have had this kernel since I came out (at least two months) and this is new and the ebuild has not changed in that time.

so why is this coming out now ?

Is this a result of the aux_get error? Is it safe to stick this in package.provided?

That is a portage question, not a nitro one , so I hope it is legit here.

TIA Gentree. 8)
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86
Back to top
View user's profile Send private message
adaptr
Watchman
Watchman


Joined: 06 Oct 2002
Posts: 6730
Location: Rotterdam, Netherlands

PostPosted: Sun Jun 19, 2005 5:28 pm    Post subject: Reply with quote

You should not need the external i2c package with any 2.6 kernel.
Perhaps the nitro ebuild incorrectly does not provide i2c, or even 2.6.

It's weird.
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen
Back to top
View user's profile Send private message
Gentree
Watchman
Watchman


Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe

PostPosted: Sun Jun 19, 2005 6:03 pm    Post subject: Reply with quote

thanks for the reply but seriously...

I said I have been using this kernel for months , do you think it's likely that neither I nor anyone else has not noticed it is not "providing 2.6". Maybe you did not mean that?

Code:
senson
 * Loading lm_sensors modules...
 *   Loading i2c-viapro...                                                [ ok ]
 *   Loading i2c-voodoo3...                                               [ ok ]
 *   Loading i2c-isa...                                                   [ ok ]
 *   Loading eeprom...                                                    [ ok ]
 *   Loading ddcmon...                                                    [ !! ]

 *   Loading w83627hf...                                                  [ ok ]
 * Initializing sensors...                                                [ ok ]

yep the sensors are detected and loading and working fine in gkrellm.

You will notice the aux_get error in my post. That is either an error/security feature in portage and/or an error in the nitro ebuild and is presumably what is misleading portage into thinking i2c is not accounted for in world.

Hwvr, I have been updating regularily over the past weeks and months and this is new.

My question: why :?:
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86
Back to top
View user's profile Send private message
cdunham
Apprentice
Apprentice


Joined: 06 Jun 2003
Posts: 211
Location: Rhode Island

PostPosted: Mon Jun 20, 2005 12:25 am    Post subject: Reply with quote

I was seeing the same thing using a straight gentoo-sources (~x86).

Code:
# equery d i2c
[ Searching for packages depending on i2c... ]
#


I unmerged previous i2c, lm_sensors, and emerged lm_sensors back in. For some reason, sys-apps/i2c was still in /var/lib/world, but once I took it out of there, it stopped wanting to emerge it.

HTH
_________________
This post more meaningful in a scalar context.
Back to top
View user's profile Send private message
Gentree
Watchman
Watchman


Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe

PostPosted: Mon Jun 20, 2005 8:23 am    Post subject: Reply with quote

Thanks,

well I was able to unmerge it and verify that it was not in /var/lib/portage/world but it is still being called for as

[ebuild N ] sys-apps/i2c-2.9.1

I get the feeling that this is a virtual messing me around.
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86
Back to top
View user's profile Send private message
kallamej
Administrator
Administrator


Joined: 27 Jun 2003
Posts: 4927
Location: Gothenburg, Sweden

PostPosted: Mon Jun 20, 2005 9:50 am    Post subject: Reply with quote

The FAQ https://forums.gentoo.org/viewtopic.php?t=53808 suggests using the --tree and --verbose flags to debug this. Does it give any clue as to what is trying to pull in i2c?
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.freenode.net
Back to top
View user's profile Send private message
Gentree
Watchman
Watchman


Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe

PostPosted: Mon Jun 20, 2005 10:19 am    Post subject: Reply with quote

It's lm_sensors OK. Has there been any changes in portage recently that could explain this?

As I said, this has been installed and running for many months. I think I got this lm_sensors running around Jan this year . The kernel has been the same one for months despite frequent rebuilds , mainly for sound. kernel i2c has always been enabled.

It is possible (though I dont recall) that i2c got emerged at some stage, maybe due to -uD world that slipped that one in without it catching my eye as a conflict.

Code:
[nomerge      ] sys-apps/lm_sensors-2.9.0  -debug -rrdtool
[ebuild  N    ]  sys-apps/i2c-2.9.1  0 kB


I changed profile to 2005.0 around end of March. Is there anything I should be aware of there that could have unexpected effects on this?

TIA.8)
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86
Back to top
View user's profile Send private message
kallamej
Administrator
Administrator


Joined: 27 Jun 2003
Posts: 4927
Location: Gothenburg, Sweden

PostPosted: Mon Jun 20, 2005 10:54 am    Post subject: Reply with quote

That was my suspicion. The question now is why you don't get lm_sensors-2.9.1 listed as an upgrade since it no longer requires i2c as a dependency (<=i2c-2.9-0 is only a stub for 2.6 kernels). Do you have anything relevant to this in /etc/portage/package.*?
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.freenode.net
Back to top
View user's profile Send private message
Gentree
Watchman
Watchman


Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe

PostPosted: Mon Jun 20, 2005 11:24 am    Post subject: Reply with quote

Ah-ha!
Code:
bash-3.00#grep -i "sensors"  /etc/portage/package.*
/etc/portage/package.keywords:sys-apps/lm_sensors ~x86
/etc/portage/package.mask:>sys-apps/lm_sensors-2.9.0
bash-3.00#etcat -v lm_sensors
[ Results for search key           : lm_sensors ]
[ Candidate applications found : 3 ]

 Only printing found installed programs.

*  sys-apps/lm_sensors :
        [   ] 2.8.7 (0)
        [  I] 2.9.0 (2.6.11-nitro2)
        [M~ ] 2.9.1 (0)

and having removed the mask
Code:
[ebuild  NS   ] sys-apps/lm_sensors-2.9.1 
, no i2c deps. Good.

Now I cant remember why I put the line in mask but it was not done recently.

So why did an ebuild that was only a stub start calling for the i2c dep? It was still locked at 2.9.0 it was in the kernel and so was i2c.

What changed to make a working system incorrectly call for this dep. ? If for some reason I wish to keep 2.9.0 the ebuild should still work and rebuild what I have.

Thanks. 8)
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86
Back to top
View user's profile Send private message
kallamej
Administrator
Administrator


Joined: 27 Jun 2003
Posts: 4927
Location: Gothenburg, Sweden

PostPosted: Mon Jun 20, 2005 12:07 pm    Post subject: Reply with quote

Gentree wrote:
So why did an ebuild that was only a stub start calling for the i2c dep? It was still locked at 2.9.0 it was in the kernel and so was i2c.

What changed to make a working system incorrectly call for this dep. ? If for some reason I wish to keep 2.9.0 the ebuild should still work and rebuild what I have.

Umm, lm_sensors was never a stub and older versions always depended on i2c even if the i2c ebuilds didn't install anything on 2.6 kernels. It became a problem for you now because <=lm_sensors-2.9-0 depend on >=sys-apps/i2c-${PV}. The lm_sensors stuff has recently been restructured so filing a bug about changing that to ~sys-apps/i2c-${PV} may not give more than the advice to upgrade to 2.9.1. In fact, lm_sensors-2.9.1 requires >=i2c-2.9.0 for 2.4 kernels so stricter version deps are probably incorrect. The still stable 2.8.7 is not supported upstream.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.freenode.net
Back to top
View user's profile Send private message
Gentree
Watchman
Watchman


Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe

PostPosted: Mon Jun 20, 2005 12:27 pm    Post subject: Reply with quote

Soory, I mis-read your post because the version numbers are so close.

So a new i2c-2.9.1 was recently added and slotted. So my locked lm_sensors-2.9.0 had i2c as a dep and wanted to upgrade it. Because the new i2c is slotted it came up as new. [N]

So it seems that the restructuring makes the old lm ebuild defective and it should now be modified to have its i2c dep locked at <=2.9.0 - at which stage it was still a stub and will work.

Should I file a bug report to this effect?

Thanks for your help in untagling this one. 8)
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86
Back to top
View user's profile Send private message
kallamej
Administrator
Administrator


Joined: 27 Jun 2003
Posts: 4927
Location: Gothenburg, Sweden

PostPosted: Mon Jun 20, 2005 12:44 pm    Post subject: Reply with quote

Gentree wrote:
So it seems that the restructuring makes the old lm ebuild defective and it should now be modified to have its i2c dep locked at <=2.9.0 - at which stage it was still a stub and will work.

Should I file a bug report to this effect?

Devs love bug reports. :)
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.freenode.net
Back to top
View user's profile Send private message
Gentree
Watchman
Watchman


Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe

PostPosted: Mon Jun 20, 2005 1:29 pm    Post subject: Reply with quote

users love bugs in portage. :wink:

Thanks for the help. 8)
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86
Back to top
View user's profile Send private message
SAngeli
l33t
l33t


Joined: 16 Apr 2004
Posts: 904
Location: Italy

PostPosted: Sun Oct 09, 2005 6:17 pm    Post subject: [SOLVED] Reply with quote

Hi,

Today (09-OCT-2005) I had the same issue while ( emerge -uD world ):
Code:
 * 2.9.1 is only needed for kernel 2.4.x
 * You need to use the in-kernel I2C drivers for later kernels.

!!! ERROR: sys-apps/i2c-2.9.1 failed.
!!! Function pkg_setup, Line 28, Exitcode 0
!!! Non 2.4.x kernel detected
!!! If you need support, post the topmost build error, NOT this status message.


What does * 2.9.1 is only needed for kernel 2.4.x mean? It means the following:
- If you have Linux Kernel 2.4.x then you need to install sys-apps/i2c-2.9.1 manually (emerge i2c) and not use the kernel drivers ( [ ] I2C support ).
- If you rather have Linux Kernel >= 2.6.x then you do not need sys-apps/i2c-2.9.1. You then need the in-kernel drivers, (in-line) meaning what the kernel offers. So, you have to enable as module (preferred) or compile into the kernel I2C ( <M> I2C support or <*> I2C support )

After receiving Gentoo IRC assistance, I was able to solve this issue.
Here is step by step howto:

1) check if i2c is present by doing: ~ # emerge -uDtp world
If you get: [ebuild NS ] sys-apps/i2c-2.9.1 then you need to unmerge it
1a) ~ # emerge -C i2c
1b) check again to make sure it is gone: ~ # emerge -uDtp world
2) once you do not have i2c anylonger, check what kind of lm_sensors currently is installed and verify it against portage in gentoo website.
2a) unmerge lm_sensors too so that you do not have any kind of doubts. (OPTIONAL) ~ # emerge -C lm_sensors
2b) verify that lm_sensors is not installed anymore: ~ # emerge -pv lm_sensors
3) Verify that I2C is also not listed in your world ( /var/lib/portage/world ) file
You can either browse or grep world file (one of the two):
~ # cat /var/lib/portage/world |more
~ # cat /var/lib/portage/world | grep lm i2c
4) resume your emerge process (if you were in the middle of it) ~ #emerge --resume
4a) emerge it manually (if you were not in the middle of emerge -uD world) ~ # emerge lm_sensors

This is all I did. I hope this can be of any help to whomever is experiencing this issue.

Take care,
Spiro
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum