test May 2007

test@lists.fedoraproject.org

175 participants
290 discussions

Start a nNew thread

rawhide report: 20070529 changes
by Build System 29 May '07

29 May '07

Updated Packages: (none)

1 0

atd[16743]: Open of jobfile failed: Success
by Thomas Hallgren 29 May '07

29 May '07

Hi, When I submit at jobs, I get messages like job 6 at Tue May 29 00:43:00 2007 Warning: at daemon not running but when I do /etc/init.d/atd start, a message like the following appears in /var/log/messages: atd[16743]: Open of jobfile failed: Success $ rpm -q at at-3.1.10-11.fc7 What to do? -- Thomas H

2 1

Newest kernel Fedora (2.6.21-1.3194.fc7) killed ndiswrapper
by Arch Willingham 28 May '07

28 May '07

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. Any idea? Thanks! Arch # /batch/fix_ndis.sh make -C driver install make[1]: 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[2]: 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[2]: 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 echo /lib/modules/2.6.21-1.3194.fc7/misc /lib/modules/2.6.21-1.3194.fc7/misc 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[1]: Leaving directory `/downloads/ndiswrapper-1.44/driver' make -C utils install make[1]: 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[1]: 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. re

4 11

Re: ati x1400 (text mode) F7+
by Justin Conover 28 May '07

28 May '07

On 3/11/07, Justin Conover <justin.conover(a)gmail.com> wrote: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231797 > > 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 > > > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231797 Can this be re-opened? I can't get X on my laptop again.

2 1

Odd behavior on multi-homed machine
by David Hagood 28 May '07

28 May '07

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 device. In other words, if I have: lo: 127.0.0.1 eth0: 10.0.0.1 eth1: 192.168.0.1 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 10.0.0.1. 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?

1 0

yum is installing both i386 and x86_64 for everything
by Neal Becker 28 May '07

28 May '07

I have several x86_64 with current rawhide. If I do yum install blah It will install both blah.i386 and blah.x86_64. I think this has to be fixed.

11 18

Rawhide -- WARNING: Couldn't open directory /lib/modules/2.6.22-rc2-mm1: No such file or directory
by Miles Lane 28 May '07

28 May '07

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? Miles

2 1

Re: suspend/resume madness with Fedora 7 test 4 on HP Compaq nx7300
by Valent Turkovic 28 May '07

28 May '07

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 > <https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238365>) > > As of kernel: > 2.6.21-1.3142 > Suspend worked fine. > > Since the LiveCD was using > 2.6.21-1.3163 > you're in good shape there. > > There was a regression in > kernel-2.6.21-1.3189.fc7 > > 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? Valent. -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241 Skype: valent.turkovic

1 0

Live CD upgrade?
by Adam Pribyl 28 May '07

28 May '07

Does F7 RC2 Live CD allow to do upgrade of existing FC6-F7t4 installs? It only offers me to install by deleting all linux partitions. So upgrade is only available with complete DVD? Adam Pribyl

7 9

NO X with F7 RC2 and ati x1400
by Justin Conover 27 May '07

27 May '07

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241491 I don't have X again with the vesa driver and ati x1400 video card.

2 2

← Newer
1
2
3
4
5
6
7
8
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test May 2007