Unfortunately, I use ndiswrapper to get to my Linksys wireless card. It has always worked with each interation of FC6 and FC7. I currently use it with FC7 test 4.
Every time a new kernal comes out, I run a batch file (oops...script file) to re-run teh ndiswapper stuff. Last night, after I updated to Fedora (2.6.21-1.3194.fc7), I tried to update ndiswrapper andit bombed out with the message below. Note that of teh output below, there were only two new errors: "WARNING: "__spin_lock_init" [/downloads/ndiswrapper-1.44/driver/ndiswrapper.ko] undefined!" and "FATAL: Error inserting ndiswrapper (/lib/modules/2.6.21-1.3194.fc7/misc/ndiswrapper.ko): Unknown symbol in module, or unknown parameter (see dmesg)"...teh other errors are typicsl for each build (at least on my machine). Once I dropped back to Fedora (2.6.21-1.3189.fc7), it works fine.
make -C driver install
make: Entering directory `/downloads/ndiswrapper-1.44/driver'
make -C /lib/modules/2.6.21-1.3194.fc7/build SUBDIRS=/downloads/ndiswrapper-1.44/driver
make: Entering directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'
Building modules, stage 2.
MODPOST 1 modules
WARNING: "__spin_lock_init" [/downloads/ndiswrapper-1.44/driver/ndiswrapper.ko] undefined!
make: Leaving directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'
*** WARNING: This kernel seems to use 4K stack size option (CONFIG_4KSTACKS); many Windows drivers will not work with this option enabled. Disable CONFIG_4KSTACKS option, recompile and install kernel
mkdir -p /lib/modules/2.6.21-1.3194.fc7/misc
install -m 0644 ndiswrapper.ko /lib/modules/2.6.21-1.3194.fc7/misc
/sbin/depmod -a 2.6.21-1.3194.fc7 -b /
make: Leaving directory `/downloads/ndiswrapper-1.44/driver'
make -C utils install
make: Entering directory `/downloads/ndiswrapper-1.44/utils'
install -D -m 755 loadndisdriver /sbin/loadndisdriver
install -D -m 755 ndiswrapper /usr/sbin/ndiswrapper
install -D -m 755 ndiswrapper-buginfo /usr/sbin/ndiswrapper-buginfo
NOTE: Windows driver configuration file format has changed since 1.5. You must re-install Windows drivers if they were installed before.
make: Leaving directory `/downloads/ndiswrapper-1.44/utils'
mkdir -p -m 0755 /usr/share/man/man8
install -m 644 ndiswrapper.8 /usr/share/man/man8
install -m 644 loadndisdriver.8 /usr/share/man/man8
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.21-1.3194.fc7/misc/ndiswrapper.ko): Unknown symbol in module, or unknown parameter (see dmesg)
wlan0 Interface doesn't support scanning.
On 3/11/07, Justin Conover <justin.conover(a)gmail.com> wrote:
> On 2/27/07, Adam Jackson <ajackson(a)redhat.com> wrote:
> > Wow. The people that wrote that BIOS are complete clowns.
> > 1) EDID block with the panel size, but no VESA mode matching that size
> > 2) Detailed timing for the panel mode given in EDID, twice, just for fun
> > 3) EDID is otherwise non-conformant (missing name and range descriptors)
> > xorg-x11-drv-vesa 1.3.0-4.fc7 on its way to rawhide now, should work
> > marginally better. You still won't the native 1680x1050 panel size on
> > account of clown screwup #1, but you should get 1400x1050 at least.
> > Friends don't let friends use vesa,
> > - ajax
Can this be re-opened?
I can't get X on my laptop again.
I just updated a multi-homed machine to the latest rawhide, and I am
seeing a strange behavior:
All packets destined for the loopback interface are being set with the
IP address of the highest order ethernet device, rather than with the LO
In other words, if I have:
and I do a "ping 127.0.0.1", and on another console I do a "tcpdump -n
-i lo", then the TCP dump shows all the ICMP echo request packets as
having come from "192.168.0.1" rather than 127.0.0.1 - even if if force
ping to bind to 127.0.0.1.
If I down eth1, then the packets are marked as having come from
Only when both ethernet devices are down do the packets have 127.0.0.1
as the source address.
Needless to say this plays merry hell with most of the services that are
configured to ignore packets based upon IP address, as many local
packets are being dropped because they don't "smell local".
Has anybody else seen this behavior?
When I try to build a custom kernel from Linus' or Andrew's tree's, I
get the following:
sh /usr/src/linux-2.6/arch/i386/boot/install.sh 2.6.22-rc2-mm1
arch/i386/boot/bzImage System.map "/boot"
WARNING: Couldn't open directory /lib/modules/2.6.22-rc2-mm1: No such
file or directory
FATAL: Could not open /lib/modules/2.6.22-rc2-mm1/modules.dep.temp for
writing: No such file or directory
No modules available for kernel "2.6.22-rc2-mm1".
Since I don't get this problem when compiling under Ubuntu, it seems
it must be a distro problem with a script?
Anyone know why this is failing?
On 5/27/07, Daryll Strauss <daryll.strauss(a)gmail.com> wrote:
> I've been runing all the development kernels on my HP dv9000t (Core 2
> Duo) laptop. (BZ #238365
> As of kernel:
> Suspend worked fine.
> Since the LiveCD was using
> you're in good shape there.
> There was a regression in
> As of that kernel, suspend no longer works. The system appears to
> suspend correctly. The syslog reports the suspend and the power light
> flashes. When I attempt to revive the machine, the machine starts to
> come up. The power light goes solid and I hear the disk wake up. But
> nothing is logged in the syslog and the restore doesn't get any further.
> Hopefully that helps narrow the problem.
> - |Daryll
I really have no idea how to narrow the problem any further.
Only things I can came up with is to install Rawhide live cd on my
laptop and then try to suspend and resume. And then update it with new
kernel and try again...
I can also wait for the official Fedora 7 and fedora 7 live cd and
then try it out...
Any other suggestions?
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
Would you like to add some comments on Bugzilla with
kernel 3201, it displays which is similar to the above
one. Thanks for checking out the sound issue.
You posted in the thread:
Re: [Bug 240081] ICH7 No Sound
dmesg part as follows,
BUG: warning at kernel/softirq.c:144/local_bh_enable()
Note: forwarded message attached.
____________________________________________________________________________________You snooze, you lose. Get messages ASAP with AutoCheck
in the all-new Yahoo! Mail Beta.
I've noticed that gnome-panel, gnome-panel-2.18.0-9.fc7, runs
consistently at the top of top, consuming between 70-90% of the cpu. I
do not see this behavior on FC6.
Does the cpu utilization also include applets running such as
This seems excessive. Do others see similar cpu usage?