This problem troubles me for a long time. The madwifi modules can't be
loaded correctly at startup. I have to rmmod all the madwifi modules,
and modprobe them again, then they work! It's so strange...
Anybody give some hints?
$uname -r
2.6.23-ARCH
My wireless network adapter:
01:04.0 Ethernet co
On Nov 17, 2007 11:54 PM, Eric Belanger <[EMAIL PROTECTED]> wrote:
> but without formatting
> and not taking in account the fact that the package version can be
> different for the 2 archtectures (because of arch specific bug).
I'm not sure what you're referring to here. Can you elaborate?
I simp
2007/11/18, Xavier <[EMAIL PROTECTED]>:
> On Sun, Nov 18, 2007 at 11:42:11AM +0200, Roman Kyrylych wrote:
> > Huh?
> > gcc-libs doesn't depend on gcc
> > python doesn't depend on tk
> > I guess makedepends were counted here, which is wrong.
> >
>
> Ah indeed, the script doesn't make any distinction
On Sun, Nov 18, 2007 at 11:42:11AM +0200, Roman Kyrylych wrote:
> Huh?
> gcc-libs doesn't depend on gcc
> python doesn't depend on tk
> I guess makedepends were counted here, which is wrong.
>
Ah indeed, the script doesn't make any distinction between makedepends and
depends. It probably should j
2007/11/18, Scott Horowitz <[EMAIL PROTECTED]>:
> I posted this script to the pacman-dev list last time, but thought
> maybe it should go here instead. It essentially looks for a number of
> problems with Arch PKGBUILDs, repos, etc. Since the previous posting,
> it now checks for a number of additi
