From notting at redhat.com Tue May 1 04:07:42 2007 From: notting at redhat.com (Bill Nottingham) Date: Tue, 1 May 2007 00:07:42 -0400 Subject: How to hack module loading to get tifm_core to also load tifm_sd? In-Reply-To: References: Message-ID: <20070501040742.GA11331@nostromo.devel.redhat.com> Miles Lane (miles.lane at gmail.com) said: > I found this bug report which describes my situation as well: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232370 > > I am currently testing F7-Test4. I have > module-init-tools-3.3-0.pre11.1.0.fc7. > Is there something I can do to hack this to do the right thing until > it gets fixed in F7? > modprobe.conf doesn't seem to support it and modprobe.dep is ancient > history. install tifm_core /sbin/modprobe --ignore-install tifm_core && /sbin/modprobe tifm_sd ? If *everything* that has tifm chip uses tifm_sd, then the kernel modules should be fixed... Bill From miles.lane at gmail.com Tue May 1 04:53:13 2007 From: miles.lane at gmail.com (Miles Lane) Date: Mon, 30 Apr 2007 21:53:13 -0700 Subject: How to hack module loading to get tifm_core to also load tifm_sd? In-Reply-To: <20070501040742.GA11331@nostromo.devel.redhat.com> References: <20070501040742.GA11331@nostromo.devel.redhat.com> Message-ID: On 4/30/07, Bill Nottingham wrote: > Miles Lane (miles.lane at gmail.com) said: > > I found this bug report which describes my situation as well: > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232370 > > > > I am currently testing F7-Test4. I have > > module-init-tools-3.3-0.pre11.1.0.fc7. > > Is there something I can do to hack this to do the right thing until > > it gets fixed in F7? > > modprobe.conf doesn't seem to support it and modprobe.dep is ancient > > history. > > install tifm_core /sbin/modprobe --ignore-install tifm_core && /sbin/modprobe tifm_sd > > ? > > If *everything* that has tifm chip uses tifm_sd, then the kernel modules > should be fixed... Thanks for the reply. It is my understanding only SD cards are supported for the TI chip at this time. To me, this means that tifm_sd should always be automatically loaded. Miles From notting at redhat.com Tue May 1 05:04:58 2007 From: notting at redhat.com (Bill Nottingham) Date: Tue, 1 May 2007 01:04:58 -0400 Subject: How to hack module loading to get tifm_core to also load tifm_sd? In-Reply-To: References: <20070501040742.GA11331@nostromo.devel.redhat.com> Message-ID: <20070501050458.GG11331@nostromo.devel.redhat.com> Miles Lane (miles.lane at gmail.com) said: > >If *everything* that has tifm chip uses tifm_sd, then the kernel modules > >should be fixed... > > Thanks for the reply. It is my understanding only SD cards are > supported for the TI chip at this time. To me, this means that > tifm_sd should always be automatically loaded. I note that nothing appears in the module that would cause tifm_core to ever get loaded. How does one know that they need it? Bill From miles.lane at gmail.com Tue May 1 05:03:40 2007 From: miles.lane at gmail.com (Miles Lane) Date: Mon, 30 Apr 2007 22:03:40 -0700 Subject: How to hack module loading to get tifm_core to also load tifm_sd? In-Reply-To: <20070501050458.GG11331@nostromo.devel.redhat.com> References: <20070501040742.GA11331@nostromo.devel.redhat.com> <20070501050458.GG11331@nostromo.devel.redhat.com> Message-ID: On 4/30/07, Bill Nottingham wrote: > Miles Lane (miles.lane at gmail.com) said: > > >If *everything* that has tifm chip uses tifm_sd, then the kernel modules > > >should be fixed... > > > > Thanks for the reply. It is my understanding only SD cards are > > supported for the TI chip at this time. To me, this means that > > tifm_sd should always be automatically loaded. > > I note that nothing appears in the module that would cause > tifm_core to ever get loaded. How does one know that they > need it? Sorry, I don't know. Perhaps the driver developer? From sean.bruno at dsl-only.net Tue May 1 05:15:24 2007 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Mon, 30 Apr 2007 22:15:24 -0700 Subject: FC7T4 Install Failure(SCSI READ ERRORS) Message-ID: <1177996524.3488.14.camel@home-desk> Sorry for the late install folks, I know this is T4 and I should have gotten around to this sooner. It's been a while since I've had some time to use a test release(I'm not sure where FC7T4 bugs go in bugzilla even!). Not sure why I would get these errors on install, and I'm not quite sure if they are from my hard drives or my CDROM. I _assume_ that this is a CDROM drive read failing. I have a Sony DVD Burner, model DRU-800A. The system is a dual-opteron running on the ASUS K8N-DL mobo and runs FC6 x86_64 just fine. Using the x86_64 DVD ISO, I attempted to install. The following errors are the last display on my console after I skip the media check in anaconda. After selecting skip, I see an error message about anaconda being terminated. -- <6> device-mapper: multipath emc: version 0.0.3 loaded <3> SQUASHFS error: sb_bread failed reading block 0x15c5e <3> SQUASHFS error: Unable to read cache block [5716b1d:16f2] <3> SQUASHFS error: Unable to read inode [5716b1d:16f2] <6> sr 3:0:0:0: SCSI error: return code = 0x08000002 <6> sr0: Current: sense key: Hardware Error <6> Additional sense: Logical unit communication CRC error (Ultra-DMA/32) <4> end_request: I/O error, dev sr0, sector 6424656 <3> SQUASHFS error: sb_bread failed reading block 0x1bd4 <3> SQUASHFS error: Unable to read page, block 6f2cfb, size 2566 <6> sr: 3:0:0:0: SCSI error: return code = 0x08000002 <6> sr0: Current: sense key: Hardware Error <6> Additional sense: Logical unit communications CRC error (Ultra-DMA/32) <4> end_request: I/O error, dev sr0, sector 6424656 <6> sr 3:0:0:0: SCSI error: return code = 0x08000002 <6> sr0: Current: sense key: Hardware Error <6> Additional sense: Logical unit communication CRC error (Ultra-DMA/32) <4> end_request: I/O error, dev sr0, sector 6424656 <3> SQUASHFS error: sb_bread failed reading block 0x1bd4 <3> SQUASHFS error: Unable to read page, block 6f2cfb, size 2566 <3> SQUASHFS error: sb_bread failed reading block 0x1bd4 <3> SQUASHFS error: Unable to read page, block 6f2cfb, size 2566 <3> SQUASHFS error: sb_bread failed reading block 0x1bd4 <3> SQUASHFS error: Unable to read page, block 6f2cfb, size 2566 Sean From mschwendt.tmp0701.nospam at arcor.de Tue May 1 08:01:20 2007 From: mschwendt.tmp0701.nospam at arcor.de (Michael Schwendt) Date: Tue, 1 May 2007 10:01:20 +0200 Subject: liferea flakes only for me? In-Reply-To: <11875.1177974799@lwn.net> References: <11875.1177974799@lwn.net> Message-ID: <20070501100120.eaed14e3.mschwendt.tmp0701.nospam@arcor.de> On Mon, 30 Apr 2007 17:13:19 -0600, Jonathan Corbet wrote: > For some time now, I've found rawhide liferea (x86-64) to be broken > almost to the point of uselessness. It runs for something between ten > minutes and a few hours before going into a loop where it no longer > responds to any sort of input events. Instead, it occupies itself with > the vital task of printing > > (gecko:13277): GThread-CRITICAL **: g_cond_timed_wait_posix_impl: assertion `end_time.tv_nsec < G_NSEC_PER_SEC' failed > > over and over again until put out of its misery. Is this reproducible with GtkHTML2 as the internal browser? From mschwendt.tmp0701.nospam at arcor.de Tue May 1 08:05:31 2007 From: mschwendt.tmp0701.nospam at arcor.de (Michael Schwendt) Date: Tue, 1 May 2007 10:05:31 +0200 Subject: liferea flakes only for me? In-Reply-To: References: <11875.1177974799@lwn.net> Message-ID: <20070501100531.9885de3b.mschwendt.tmp0701.nospam@arcor.de> On Mon, 30 Apr 2007 19:33:05 -0400, Konstantin Ryabitsev wrote: > On 4/30/07, Jonathan Corbet wrote: > > I filed this bug a month or two ago > > (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231073) but not > > much seems to be happening there. Releasing F7 with a broken liferea > > seems like a bad idea...but maybe it's only broken for me? Anybody else > > seeing this or have any ideas? > > It's pretty much unusable on x86_64 on FC6 as well. > > icon at rakta:[~]$ dmesg | grep liferea | grep segfault | wc -l > 12 Can you get a stacktrace with the liferea-debuginfo package installed and submit it as a bug report? http://fedoraproject.org/wiki/StackTraces From caf at omen.com Tue May 1 00:47:19 2007 From: caf at omen.com (Chuck Forsberg WA7KGX N2469R) Date: Mon, 30 Apr 2007 17:47:19 -0700 Subject: FC7T4 vncserver problems with -depth 24 Message-ID: <1177980439.3578.7.camel@omen.com> vncserver -depth 24 used to work with 386 Core 6. But not with fc7t4 x86_64. Gnome and many programs give various complaints and/or segfaults. Xterm, xeyes and twm seem to work. Removing the -depth 24 from the vncserver command line allows the clients to work normally. From caf at omen.com Tue May 1 08:37:39 2007 From: caf at omen.com (Chuck Forsberg WA7KGX N2469R) Date: Tue, 01 May 2007 01:37:39 -0700 Subject: fc7t4 3116: Ethernet Still Unreliable Message-ID: <1178008659.3935.7.camel@omen.com> The previously reported problem of a PCI ethernet board losing transmit interrupts is still present in fc7t4 x86_64 kernel 3116. The last good kernel was 2869, to which I have reverted. Interestingly, this bug appears to be machine independent, affecting recent 386 fc6 kernels as well as the fc7 x86_64 kernel. From dtimms at iinet.net.au Tue May 1 09:17:14 2007 From: dtimms at iinet.net.au (David Timms) Date: Tue, 01 May 2007 19:17:14 +1000 Subject: Bug Buddy doesn't work? In-Reply-To: <20070430155707.GC23940@angus.ind.WPI.EDU> References: <20070430155707.GC23940@angus.ind.WPI.EDU> Message-ID: <4637059A.1010403@iinet.net.au> Chuck Anderson wrote: > Gnumeric crashed when I tried to exit and Bug Buddy popped up. > However, submission of the bug report failed: > > Bug Buddy has encountered an error while submitting your report to the > Bugzilla server. Details of the error are included below. > > Failed to parse the xml-rpc response. Response follows: > > Unable to parse XML-RPC Response > > 3 > > > faultStringApplication > failed during request deserialization: > not well-formed (invalid token) at line 23, column 0, byte 1637 at > /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/Parser.pm > line 187 > faultCodeClient > Is that the same as: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238260 DaveT. From buildsys at redhat.com Tue May 1 09:51:26 2007 From: buildsys at redhat.com (buildsys at redhat.com) Date: Tue, 1 May 2007 05:51:26 -0400 Subject: rawhide report: 20070501 changes Message-ID: <200705010951.l419pQVc005646@hs20-bc2-6.build.redhat.com> Updated Packages: NetworkManager-1:0.6.5-2.fc7 ---------------------------- * Wed Apr 25 2007 Christopher Aillon 1:0.6.5-2 - Fix requires macro (237806) anaconda-11.2.0.57-1 -------------------- * Mon Apr 30 2007 Jeremy Katz - 11.2.0.57-1 - fix build * Mon Apr 30 2007 Jeremy Katz - 11.2.0.56-1 - Don't write out ipv6 disabling bits (dcantrell, #237642) - Load pata_pcmcia late (#237674) - Fix release notes to display nicely with the livecd running at 800x600 - Add support for spufs (pnasrat, #237725) - Add libidn for ping (#237745) - Fix selinux context of /root (clumens, #237834) - Fix for mirror errors (dlehman) - Fix splittree (Joel Andres Granados, #233384) - Fix ppc32 netboot (pnasrat, #237988) - Fix %packages for media installs (clumens, #231121, #235881) - Fix rescue mode networking (dcantrell, #238080) - Adjust for unbreaking the yum API - Fix rescue mode traceback (#238261) - Fix for iscsi not being present (#238424) - Fix for upgrades with LVM (clumens, #234938) - Give some feedback while erases are being processed (#238256) anthy-8706-2.fc7 ---------------- * Fri Apr 27 2007 Akira TAGOH - 8706-2 - Fix wrong Provides line. (#237987) libvirt-0.2.2-2.fc7 ------------------- * Sat Apr 21 2007 Daniel P. Berrange - 0.2.2-2.fc7 - Added Requires on dnsmasq for virtual networking pango-1.16.4-1.fc7 ------------------ * Tue Apr 10 2007 Behdad Esfahbod - 1.16.4-1 - Update to 1.16.4. - Enable doc rebuilding to get cross-references right. vim-2:7.0.235-1.fc7 ------------------- * Mon Apr 30 2007 Karsten Hopp 7.0.235-1 - update to patchlevel 235, fixes modeline issues vte-0.16.3-1.fc7 ---------------- * Fri Apr 27 2007 Behdad Esfahbod 0.16.3-1 - Update to 0.16.3 wireless-tools-1:28-2.fc7 ------------------------- * Mon Apr 30 2007 Christopher Aillon - 1:28-2 - Backport a few 64bit alignment fixes from the latest betas. xorg-x11-proto-devel-7.2-9.fc7 ------------------------------ * Thu Apr 26 2007 Adam Jackson 7.2-9 - inputproto 1.4.2 xorg-x11-server-1.3.0.0-3.fc7 ----------------------------- * Mon Apr 30 2007 Adam Jackson 1.3.0.0-3 - xserver-1.3.0-xkb-and-loathing.patch: Ignore (not just block) SIGALRM around calls to Popen()/Pclose(). Fixes a hang in openoffice when opening menus. - Modify BuildRequires to use the virtual protocol Provides. * Wed Apr 25 2007 Adam Jackson 1.3.0.0-2 - xserver-1.3.0-less-randr-fakerama.patch: Disable RANDR's fake Xinerama geometry when there's more than one protocol screen. (#231257) * Mon Apr 23 2007 Adam Jackson 1.3.0.0-1 - xserver 1.3.0. yum-3.1.7-2.fc7 --------------- * Mon Apr 30 2007 Jeremy Katz - 3.1.7-2 - add fix for fastestmirror (#238276) Broken deps for ia64 ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.ia64 requires mkisofs dvd+rw-tools - 7.0-3.fc7.ia64 requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.ia64 requires mkisofs k3b - 1.0-1.fc7.ia64 requires cdrecord libvirt - 0.2.2-2.fc7.ia64 requires dnsmasq nautilus-cd-burner - 2.18.0-2.fc7.ia64 requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.ia64 requires cdrecord xcdroast - 0.98a15-13.ia64 requires cdrecord >= 0:2.0 xcdroast - 0.98a15-13.ia64 requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.ia64 requires mkisofs >= 0:2.0 Broken deps for ppc64 ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.ppc64 requires mkisofs dvd+rw-tools - 7.0-3.fc7.ppc64 requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.ppc64 requires mkisofs k3b - 1.0-1.fc7.ppc64 requires cdrecord nautilus-cd-burner - 2.18.0-2.fc7.ppc64 requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.ppc64 requires cdrecord xcdroast - 0.98a15-13.ppc64 requires cdrecord >= 0:2.0 xcdroast - 0.98a15-13.ppc64 requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.ppc64 requires mkisofs >= 0:2.0 Broken deps for i386 ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.i386 requires mkisofs dvd+rw-tools - 7.0-3.fc7.i386 requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.i386 requires cdrecord k3b - 1.0-1.fc7.i386 requires mkisofs libvirt - 0.2.2-2.fc7.i386 requires dnsmasq nautilus-cd-burner - 2.18.0-2.fc7.i386 requires cdrecord nautilus-cd-burner - 2.18.0-2.fc7.i386 requires mkisofs xcdroast - 0.98a15-13.i386 requires cdrecord >= 0:2.0 xcdroast - 0.98a15-13.i386 requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.i386 requires mkisofs >= 0:2.0 Broken deps for x86_64 ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.x86_64 requires mkisofs dvd+rw-tools - 7.0-3.fc7.x86_64 requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.i386 requires mkisofs k3b - 1.0-1.fc7.i386 requires cdrecord k3b - 1.0-1.fc7.x86_64 requires mkisofs k3b - 1.0-1.fc7.x86_64 requires cdrecord libvirt - 0.2.2-2.fc7.x86_64 requires dnsmasq libvirt - 0.2.2-2.fc7.i386 requires dnsmasq nautilus-cd-burner - 2.18.0-2.fc7.x86_64 requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.x86_64 requires cdrecord nautilus-cd-burner - 2.18.0-2.fc7.i386 requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.i386 requires cdrecord xcdroast - 0.98a15-13.x86_64 requires cdrecord >= 0:2.0 xcdroast - 0.98a15-13.x86_64 requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.x86_64 requires mkisofs >= 0:2.0 Broken deps for ppc ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.ppc requires mkisofs dvd+rw-tools - 7.0-3.fc7.ppc requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.ppc requires mkisofs k3b - 1.0-1.fc7.ppc requires cdrecord nautilus-cd-burner - 2.18.0-2.fc7.ppc requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.ppc requires cdrecord xcdroast - 0.98a15-13.ppc requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.ppc requires mkisofs >= 0:2.0 xcdroast - 0.98a15-13.ppc requires cdrecord >= 0:2.0 From amit.rana at gmail.com Tue May 1 12:32:30 2007 From: amit.rana at gmail.com (Amit Rana) Date: Tue, 1 May 2007 18:02:30 +0530 Subject: f7t4 problems Message-ID: <777ab80a0705010532p1beca6b3h5c4c343e0f3f31f2@mail.gmail.com> Hi, I had been facing lots of problems with f7t4 on my laptop (http://smolt.fedoraproject.org/show?UUID=22c8710a-e702-4bcb-b002-448a3e53805b) All problems are while booting, even the installer did not start in one try. I do not know exactly what is the problem and need help to figure out. Boot process hangs in between and starting it for the second time solves the problem. (sometimes). Today there were some updates (around 13) after installing those when I rebooted my x windows is not starting, its showing me a blank white screen. I did not change "anything", just took latest updates. How can I debug or fix this? For now I have changed init level to 3. I can never boot in one try, I am mentioning below when boot process stops... Switched to high resolution mode on CPU0 it is Freeing initrd memory: 5639k freed Simple Boot flat at 0x7a set to 0x1 ---------------------------- another time it hanged at PCI: setting latency timer of device 0000:00:1c.3 to 64 PCI: setting latency timer of device 0000:00:1e.0 to 64 NET: Registered protocol family 2 ---------------------------- This is a very regular thing. Any advice? Regards, Amit. From n0dalus+redhat at gmail.com Tue May 1 12:51:28 2007 From: n0dalus+redhat at gmail.com (n0dalus) Date: Tue, 1 May 2007 22:21:28 +0930 Subject: sd, sd, who's got the sd In-Reply-To: <4634C3B7.5050102@redhat.com> References: <4634C3B7.5050102@redhat.com> Message-ID: <6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com> On 4/30/07, Will Woods wrote: > > So the solution is: just give the partitions names instead. Then it > doesn't matter if your FC6 root drive is sda1 or sdb1 or hdc1, it's > always LABEL=fc6_root. If you say "mount LABEL=fc6_root /fc6" it will Do > The Right Thing. > > So, in short, it doesn't matter how the two FC7 systems will detect the > new drive, so long as you give it a useful label. > What if the filesystem is not ext3? There are valid reasons to use vfat, ntfs, etc. n0dalus. From lwn-ft at lwn.net Tue May 1 12:55:13 2007 From: lwn-ft at lwn.net (Jonathan Corbet) Date: Tue, 01 May 2007 06:55:13 -0600 Subject: liferea flakes only for me? In-Reply-To: Your message of "Tue, 01 May 2007 10:01:20 +0200." <20070501100120.eaed14e3.mschwendt.tmp0701.nospam@arcor.de> Message-ID: <2830.1178024113@lwn.net> Michael Schwendt wrote: > Is this reproducible with GtkHTML2 as the internal browser? Is that the "open links in Liferea's window" option? If so, I'm trying it now, we'll see. Thanks, jon Jonathan Corbet / LWN.net / corbet at lwn.net From katzj at redhat.com Tue May 1 13:00:00 2007 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 01 May 2007 09:00:00 -0400 Subject: sd, sd, who's got the sd In-Reply-To: <6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com> References: <4634C3B7.5050102@redhat.com> <6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com> Message-ID: <1178024400.13694.29.camel@aglarond.local> On Tue, 2007-05-01 at 22:21 +0930, n0dalus wrote: > On 4/30/07, Will Woods wrote: > > So the solution is: just give the partitions names instead. Then it > > doesn't matter if your FC6 root drive is sda1 or sdb1 or hdc1, it's > > always LABEL=fc6_root. If you say "mount LABEL=fc6_root /fc6" it will Do > > The Right Thing. > > > > So, in short, it doesn't matter how the two FC7 systems will detect the > > new drive, so long as you give it a useful label. > > What if the filesystem is not ext3? There are valid reasons to use > vfat, ntfs, etc. vfat has both a label and a uuid; ntfs at least has a uuid and I would guess a label as well although libblkid doesn't seem to know about it. There's no reason not to use them for mounting those filesystem types either. Jeremy From n0dalus+redhat at gmail.com Tue May 1 13:08:35 2007 From: n0dalus+redhat at gmail.com (n0dalus) Date: Tue, 1 May 2007 22:38:35 +0930 Subject: sd, sd, who's got the sd In-Reply-To: <1178024400.13694.29.camel@aglarond.local> References: <4634C3B7.5050102@redhat.com> <6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com> <1178024400.13694.29.camel@aglarond.local> Message-ID: <6280325c0705010608p69667defo636136943500760a@mail.gmail.com> On 5/1/07, Jeremy Katz wrote: > > vfat has both a label and a uuid; ntfs at least has a uuid and I would > guess a label as well although libblkid doesn't seem to know about it. > There's no reason not to use them for mounting those filesystem types > either. > Good to know. If this is to be the One True Way (TM), we should probably document in the release notes how to find and set labels for different filesystems. n0dalus. From mike at miketc.com Tue May 1 13:17:11 2007 From: mike at miketc.com (Mike Chambers) Date: Tue, 01 May 2007 08:17:11 -0500 Subject: Latest Rawhide kernel doesn't boot In-Reply-To: <1177850273.10817.3.camel@scrappy.miketc.com> References: <1177824841.2208.1.camel@scrappy.miketc.com> <20070429060210.GA23750@redhat.com> <1177850273.10817.3.camel@scrappy.miketc.com> Message-ID: <1178025431.5722.2.camel@scrappy.miketc.com> On Sun, 2007-04-29 at 07:37 -0500, Mike Chambers wrote: > On Sun, 2007-04-29 at 02:02 -0400, Dave Jones wrote: > > On Sun, Apr 29, 2007 at 12:34:01AM -0500, Mike Chambers wrote: > > > It gets to "Starting Time server" and freezes. > > > > > > New kernel = kernel-2.6.21-1.3116.fc7 (freezes) > > > > > > Old Kernel = kernel-2.6.20-1.3104.fc7 (works) > > > > What network card ? > > SiS900 PCI Fast Ethernet (built into motherboard) > > That seems to come up with no error messages. Here is my messages from > the new kernel.. > Apr 29 00:28:46 scrappy kernel: eth0: Media Link On 100mbps full-duplex > > My computer boots via rhgb to setting time/time server and freezes, so above is where it stops logging. Dave, I have sense removed that kernel since it didn't boot, but wanted to follow up on if you knew of a problem or anything? I'll either file a bug, or wait until you put out a newer kernel version to see if it does the same thign and then report it? -- Mike Chambers Madisonville, KY From amit.rana at gmail.com Tue May 1 13:29:33 2007 From: amit.rana at gmail.com (Amit Rana) Date: Tue, 1 May 2007 18:59:33 +0530 Subject: f7t4 problems Message-ID: <777ab80a0705010629n698bfe15gd7f24fed7a0e4701@mail.gmail.com> More information.... Another place where laptop hangs while booting.... Switched to high resolution mode on CPU1 PnP:00:03: ioport range 0x1080-0x10bf has been reserved .....some more messages PnP PnP:00:0b: iomem range 0xfed00000-0xfed003ff could not be reserved I noticed that there two packages related to x xorg-x11-proto-devel-7.2-9.fc7 xorg-x11-server-1.3.0.0-3.fc7 shall I try to uninstall them and install older version and try? From icon at fedoraproject.org Tue May 1 13:37:23 2007 From: icon at fedoraproject.org (Konstantin Ryabitsev) Date: Tue, 1 May 2007 09:37:23 -0400 Subject: liferea flakes only for me? In-Reply-To: <20070501100531.9885de3b.mschwendt.tmp0701.nospam@arcor.de> References: <11875.1177974799@lwn.net> <20070501100531.9885de3b.mschwendt.tmp0701.nospam@arcor.de> Message-ID: On 5/1/07, Michael Schwendt wrote: > > It's pretty much unusable on x86_64 on FC6 as well. > > > > icon at rakta:[~]$ dmesg | grep liferea | grep segfault | wc -l > > 12 > > Can you get a stacktrace with the liferea-debuginfo package installed > and submit it as a bug report? The reason I haven't done that is because FC6 has an older version of liferea (1.0.26), while upstream lists 1.2.x as the stable branch. I was fairly certain their answer would be "please upgrade to the latest stable." -- Konstantin Ryabitsev Montr?al, Qu?bec From mschwendt.tmp0701.nospam at arcor.de Tue May 1 13:53:20 2007 From: mschwendt.tmp0701.nospam at arcor.de (Michael Schwendt) Date: Tue, 1 May 2007 15:53:20 +0200 Subject: liferea flakes only for me? In-Reply-To: References: <11875.1177974799@lwn.net> <20070501100531.9885de3b.mschwendt.tmp0701.nospam@arcor.de> Message-ID: <20070501155320.58d074f0.mschwendt.tmp0701.nospam@arcor.de> On Tue, 1 May 2007 09:37:23 -0400, Konstantin Ryabitsev wrote: > > > It's pretty much unusable on x86_64 on FC6 as well. > > > > > > icon at rakta:[~]$ dmesg | grep liferea | grep segfault | wc -l > > > 12 > > > > Can you get a stacktrace with the liferea-debuginfo package installed > > and submit it as a bug report? > > The reason I haven't done that is because FC6 has an older version of > liferea (1.0.26), while upstream lists 1.2.x as the stable branch. I > was fairly certain their answer would be "please upgrade to the latest > stable." bugzilla.redhat.com because the Fedora package doesn't work for you. From mschwendt.tmp0701.nospam at arcor.de Tue May 1 13:56:06 2007 From: mschwendt.tmp0701.nospam at arcor.de (Michael Schwendt) Date: Tue, 1 May 2007 15:56:06 +0200 Subject: liferea flakes only for me? In-Reply-To: <2830.1178024113@lwn.net> References: <20070501100120.eaed14e3.mschwendt.tmp0701.nospam@arcor.de> <2830.1178024113@lwn.net> Message-ID: <20070501155606.69ceb5eb.mschwendt.tmp0701.nospam@arcor.de> On Tue, 01 May 2007 06:55:13 -0600, Jonathan Corbet wrote: > > Is this reproducible with GtkHTML2 as the internal browser? > > Is that the "open links in Liferea's window" option? If so, I'm trying > it now, we'll see. It's menu "Program > Preferences > Browser" View Headlines With GtkHTML2 <-- instead of "Mozilla". From lwn-ft at lwn.net Tue May 1 14:03:28 2007 From: lwn-ft at lwn.net (Jonathan Corbet) Date: Tue, 01 May 2007 08:03:28 -0600 Subject: liferea flakes only for me? In-Reply-To: Your message of "Tue, 01 May 2007 15:56:06 +0200." <20070501155606.69ceb5eb.mschwendt.tmp0701.nospam@arcor.de> Message-ID: <5021.1178028208@lwn.net> Michael Schwendt wrote: > > > Is this reproducible with GtkHTML2 as the internal browser? > > > > Is that the "open links in Liferea's window" option? If so, I'm trying > > it now, we'll see. > > It's menu "Program > Preferences > Browser" > > View Headlines With GtkHTML2 <-- In my liferea, "Mozilla" is the only option on that pulldown. My system has both gtkhtml2 and gtkhtml3 packages installed...might I be missing something else? Thanks, jon From mschwendt.tmp0701.nospam at arcor.de Tue May 1 14:12:27 2007 From: mschwendt.tmp0701.nospam at arcor.de (Michael Schwendt) Date: Tue, 1 May 2007 16:12:27 +0200 Subject: liferea flakes only for me? In-Reply-To: <5021.1178028208@lwn.net> References: <20070501155606.69ceb5eb.mschwendt.tmp0701.nospam@arcor.de> <5021.1178028208@lwn.net> Message-ID: <20070501161227.87178b45.mschwendt.tmp0701.nospam@arcor.de> On Tue, 01 May 2007 08:03:28 -0600, Jonathan Corbet wrote: > > > > Is this reproducible with GtkHTML2 as the internal browser? > > > > > > Is that the "open links in Liferea's window" option? If so, I'm trying > > > it now, we'll see. > > > > It's menu "Program > Preferences > Browser" > > > > View Headlines With GtkHTML2 <-- > > In my liferea, "Mozilla" is the only option on that pulldown. My system > has both gtkhtml2 and gtkhtml3 packages installed...might I be missing > something else? That's another bug which needs to be examined. Just as in the i386 package, the x86_64 package ought to have both plugins: /usr/lib64/liferea/liblihtmlg.so <-- missing! /usr/lib64/liferea/liblihtmlm.so The one with 'g' is GtkHTML, the one with 'm' Mozilla. From jacliburn at bellsouth.net Tue May 1 14:21:32 2007 From: jacliburn at bellsouth.net (Jay Cliburn) Date: Tue, 01 May 2007 09:21:32 -0500 Subject: Latest Rawhide kernel doesn't boot In-Reply-To: <1178025431.5722.2.camel@scrappy.miketc.com> References: <1177824841.2208.1.camel@scrappy.miketc.com> <20070429060210.GA23750@redhat.com> <1177850273.10817.3.camel@scrappy.miketc.com> <1178025431.5722.2.camel@scrappy.miketc.com> Message-ID: <46374CEC.1040206@bellsouth.net> Mike Chambers wrote: > On Sun, 2007-04-29 at 07:37 -0500, Mike Chambers wrote: >> On Sun, 2007-04-29 at 02:02 -0400, Dave Jones wrote: >>> On Sun, Apr 29, 2007 at 12:34:01AM -0500, Mike Chambers wrote: >>> > It gets to "Starting Time server" and freezes. >>> > >>> > New kernel = kernel-2.6.21-1.3116.fc7 (freezes) >>> > >>> > Old Kernel = kernel-2.6.20-1.3104.fc7 (works) >>> >>> What network card ? >> SiS900 PCI Fast Ethernet (built into motherboard) >> >> That seems to come up with no error messages. Here is my messages from >> the new kernel.. >> > Apr 29 00:28:46 scrappy kernel: eth0: Media Link On 100mbps full-duplex >> My computer boots via rhgb to setting time/time server and freezes, so above is where it stops logging. > > Dave, > > I have sense removed that kernel since it didn't boot, but wanted to > follow up on if you knew of a problem or anything? I'll either file a > bug, or wait until you put out a newer kernel version to see if it does > the same thign and then report it? The sis900 driver had a bug that was patched April 20. Unfortunately, the patch introduced a regression that was then patched April 26 -- one day after 2.6.21 was released. The second patch appears to fix it, according to user reports in the below referenced thread. Details: http://marc.info/?l=linux-netdev&m=117707735821802&w=2 Best, Jay From mike at miketc.com Tue May 1 14:30:40 2007 From: mike at miketc.com (Mike Chambers) Date: Tue, 01 May 2007 09:30:40 -0500 Subject: Latest Rawhide kernel doesn't boot In-Reply-To: <46374CEC.1040206@bellsouth.net> References: <1177824841.2208.1.camel@scrappy.miketc.com> <20070429060210.GA23750@redhat.com> <1177850273.10817.3.camel@scrappy.miketc.com> <1178025431.5722.2.camel@scrappy.miketc.com> <46374CEC.1040206@bellsouth.net> Message-ID: <1178029840.5722.5.camel@scrappy.miketc.com> On Tue, 2007-05-01 at 09:21 -0500, Jay Cliburn wrote: > The sis900 driver had a bug that was patched April 20. Unfortunately, the patch > introduced a regression that was then patched April 26 -- one day after 2.6.21 > was released. The second patch appears to fix it, according to user reports in > the below referenced thread. > > Details: http://marc.info/?l=linux-netdev&m=117707735821802&w=2 Ok,so hopefully the next release by Dave will have the fix. Thanks for the heads up (how did you figure out or find that problem?). -- Mike Chambers Madisonville, KY From jacliburn at bellsouth.net Tue May 1 14:59:24 2007 From: jacliburn at bellsouth.net (Jay Cliburn) Date: Tue, 01 May 2007 09:59:24 -0500 Subject: Latest Rawhide kernel doesn't boot In-Reply-To: <1178029840.5722.5.camel@scrappy.miketc.com> References: <1177824841.2208.1.camel@scrappy.miketc.com> <20070429060210.GA23750@redhat.com> <1177850273.10817.3.camel@scrappy.miketc.com> <1178025431.5722.2.camel@scrappy.miketc.com> <46374CEC.1040206@bellsouth.net> <1178029840.5722.5.camel@scrappy.miketc.com> Message-ID: <463755CC.2050501@bellsouth.net> Mike Chambers wrote: > Thanks for the heads up (how did you figure out or find that problem?). I maintain a kernel network driver, and in that capacity I monitor kernel and netdev mailing list traffic. I remember seeing the sis900 thread. Jay From mike at miketc.com Tue May 1 15:08:26 2007 From: mike at miketc.com (Mike Chambers) Date: Tue, 1 May 2007 10:08:26 -0500 Subject: Latest Rawhide kernel doesn't boot In-Reply-To: <463755CC.2050501@bellsouth.net> References: <1177824841.2208.1.camel@scrappy.miketc.com> <20070429060210.GA23750@redhat.com> <1177850273.10817.3.camel@scrappy.miketc.com> <1178025431.5722.2.camel@scrappy.miketc.com> <46374CEC.1040206@bellsouth.net><1178029840.5722.5.camel@scrappy.miketc.com> <463755CC.2050501@bellsouth.net> Message-ID: ----- Original Message ----- From: "Jay Cliburn" To: "For testers of Fedora Core development releases" Sent: Tuesday, May 01, 2007 9:59 AM Subject: Re: Latest Rawhide kernel doesn't boot > Mike Chambers wrote: > >> Thanks for the heads up (how did you figure out or find that problem?). > > I maintain a kernel network driver, and in that capacity I monitor kernel > and netdev mailing list traffic. I remember seeing the sis900 thread. > Oh, Ok I see. Thanks for the heads up. Mike From cdhouch at gmail.com Tue May 1 15:17:16 2007 From: cdhouch at gmail.com (Caerie Houchins) Date: Tue, 1 May 2007 10:17:16 -0500 Subject: f7t4 problems In-Reply-To: <777ab80a0705010629n698bfe15gd7f24fed7a0e4701@mail.gmail.com> References: <777ab80a0705010629n698bfe15gd7f24fed7a0e4701@mail.gmail.com> Message-ID: On 5/1/07, Amit Rana wrote: > > More information.... > > Another place where laptop hangs while booting.... > > Switched to high resolution mode on CPU1 > PnP:00:03: ioport range 0x1080-0x10bf has been reserved > .....some more messages PnP > PnP:00:0b: iomem range 0xfed00000-0xfed003ff could not be reserved > > I noticed that there two packages related to x > xorg-x11-proto-devel-7.2-9.fc7 > xorg-x11-server-1.3.0.0-3.fc7 > > shall I try to uninstall them and install older version and try? > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > Having the same problem with the video coming up white. It appears to be tied to the intel driver for the video card somehow. Still gathering information. -- Caerie Houchins -------------- next part -------------- An HTML attachment was scrubbed... URL: From fct-cornette at insight.rr.com Tue May 1 15:17:21 2007 From: fct-cornette at insight.rr.com (Jim Cornette) Date: Tue, 01 May 2007 11:17:21 -0400 Subject: f7t4 problems (fakerama RANDR, hope not!) In-Reply-To: <777ab80a0705010629n698bfe15gd7f24fed7a0e4701@mail.gmail.com> References: <777ab80a0705010629n698bfe15gd7f24fed7a0e4701@mail.gmail.com> Message-ID: <46375A01.5090007@insight.rr.com> Amit Rana wrote: > More information.... > > Another place where laptop hangs while booting.... > > Switched to high resolution mode on CPU1 > PnP:00:03: ioport range 0x1080-0x10bf has been reserved > .....some more messages PnP > PnP:00:0b: iomem range 0xfed00000-0xfed003ff could not be reserved > > I noticed that there two packages related to x > xorg-x11-proto-devel-7.2-9.fc7 > xorg-x11-server-1.3.0.0-3.fc7 > > shall I try to uninstall them and install older version and try? > The newer version fixes the problem that I used to have with the 3/4 screen fill with dual head. Are you running dual head or have a video card which can do dual head operation? It could be possible that you needed the fakerama element from the older package. I hope the cause on your end is different from the patch that fixed my dual display system. Jim changelog entry excerpt: - xserver-1.3.0-xkb-and-loathing.patch: Ignore (not just block) SIGALRM around calls to Popen()/Pclose(). Fixes a hang in openoffice when opening menus. - Modify BuildRequires to use the virtual protocol Provides. * Wed Apr 25 2007 Adam Jackson 1.3.0.0-2 - xserver-1.3.0-less-randr-fakerama.patch: Disable RANDR's fake Xinerama geometry when there's more than one protocol screen. (#231257) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231257 -- An effective way to deal with predators is to taste terrible. From per at bothner.com Tue May 1 15:37:01 2007 From: per at bothner.com (Per Bothner) Date: Tue, 01 May 2007 08:37:01 -0700 Subject: F7t4 - intel driver doesn't seem to hot-swap displays In-Reply-To: <1177945482.19526.6.camel@localhost.localdomain> References: <4633AD03.4020504@bothner.com> <1177945482.19526.6.camel@localhost.localdomain> Message-ID: <46375E9D.20502@bothner.com> Adam Jackson wrote: > We don't have automatic plug detection quite wired up yet. And we never > will, for some monitor types, because it would require polling, which is > usually not a price in battery life that people are willing to pay. That makes sense. Having a "detect displays" button like OS X has works ok too. > The new version of the xrandr command line tool should give you enough > rope to hang yourself here. Thanks! With some experimentation and Googling I even managed to get dual-screen working pretty well. (I had edit the "Virtual" Display size in xorg.conf, which is clunky.) Perhaps for F8 we'll have a nice GUI interface for managing multiple displays, but for now this works. -- --Per Bothner per at bothner.com http://per.bothner.com/ From sundaram at fedoraproject.org Tue May 1 15:50:17 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Tue, 01 May 2007 21:20:17 +0530 Subject: sd, sd, who's got the sd In-Reply-To: <6280325c0705010608p69667defo636136943500760a@mail.gmail.com> References: <4634C3B7.5050102@redhat.com> <6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com> <1178024400.13694.29.camel@aglarond.local> <6280325c0705010608p69667defo636136943500760a@mail.gmail.com> Message-ID: <463761B9.7060505@fedoraproject.org> n0dalus wrote: > On 5/1/07, Jeremy Katz wrote: >> >> vfat has both a label and a uuid; ntfs at least has a uuid and I would >> guess a label as well although libblkid doesn't seem to know about it. >> There's no reason not to use them for mounting those filesystem types >> either. >> > > Good to know. If this is to be the One True Way (TM), we should > probably document in the release notes how to find and set labels for > different filesystems. If you want to help, provide the content. Rahul From wwoods at redhat.com Tue May 1 15:59:56 2007 From: wwoods at redhat.com (Will Woods) Date: Tue, 01 May 2007 15:59:56 +0000 Subject: FC7T4 Install Failure(SCSI READ ERRORS) In-Reply-To: <1177996524.3488.14.camel@home-desk> References: <1177996524.3488.14.camel@home-desk> Message-ID: <1178035196.15302.92.camel@metroid.rdu.redhat.com> On Mon, 2007-04-30 at 22:15 -0700, Sean Bruno wrote: > Sorry for the late install folks, I know this is T4 and I should have > gotten around to this sooner. It's been a while since I've had some > time to use a test release(I'm not sure where FC7T4 bugs go in bugzilla > even!). We're always glad to have the help. F7t4 bugs should go under "devel". This was mentioned in the release announcement. > Not sure why I would get these errors on install, and I'm not quite sure > if they are from my hard drives or my CDROM. I _assume_ that this is a > CDROM drive read failing. I have a Sony DVD Burner, model DRU-800A. It's pretty likely. It's amazing how inexact CD/DVD reading and writing really are. If you're having I/O problems with a CD/DVD-based install, the *first* thing you should do is try to burn another one. Even if "it works in another machine", some drives are just picky about what types of media they will read. Or sometimes they get a little overheated and stop reading some types of media but not others. And so on. If you still have trouble with the optical drive, you can create a spare partition, copy the ISO on there, and install from that. -w -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From n0dalus+redhat at gmail.com Tue May 1 16:05:06 2007 From: n0dalus+redhat at gmail.com (n0dalus) Date: Wed, 2 May 2007 01:35:06 +0930 Subject: sd, sd, who's got the sd In-Reply-To: <463761B9.7060505@fedoraproject.org> References: <4634C3B7.5050102@redhat.com> <6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com> <1178024400.13694.29.camel@aglarond.local> <6280325c0705010608p69667defo636136943500760a@mail.gmail.com> <463761B9.7060505@fedoraproject.org> Message-ID: <6280325c0705010905q4e612e72j9b9ce87de1c9d342@mail.gmail.com> On 5/2/07, Rahul Sundaram wrote: > n0dalus wrote: > > Good to know. If this is to be the One True Way (TM), we should > > probably document in the release notes how to find and set labels for > > different filesystems. > > If you want to help, provide the content. > I personally have no idea what commands are involved, and am especially not knowledgeable about any problems that might occur (particularly with regard to changing labels of partitions also used by other operating systems). I want to help, but I don't have the content nor do I feel confident enough in researching the content to the level of understanding I need to write technical documentation for others to rely on. I have given a suggestion, and that can be interpreted as help or not. n0dalus. From bpepple at fedoraproject.org Tue May 1 16:06:05 2007 From: bpepple at fedoraproject.org (Brian Pepple) Date: Tue, 01 May 2007 12:06:05 -0400 Subject: liferea flakes only for me? In-Reply-To: <5021.1178028208@lwn.net> References: <5021.1178028208@lwn.net> Message-ID: <1178035565.5733.4.camel@lincoln> On Tue, 2007-05-01 at 08:03 -0600, Jonathan Corbet wrote: > Michael Schwendt wrote: > > > > > Is this reproducible with GtkHTML2 as the internal browser? > > > > > > Is that the "open links in Liferea's window" option? If so, I'm trying > > > it now, we'll see. > > > > It's menu "Program > Preferences > Browser" > > > > View Headlines With GtkHTML2 <-- > > In my liferea, "Mozilla" is the only option on that pulldown. My system > has both gtkhtml2 and gtkhtml3 packages installed...might I be missing > something else? Upstream Liferea has disabled the gtkhtml plugin for x86_64 builds. /B -- Brian Pepple gpg --keyserver pgp.mit.edu --recv-keys 810CC15E BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at fedoraproject.org Tue May 1 16:10:14 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Tue, 01 May 2007 21:40:14 +0530 Subject: sd, sd, who's got the sd In-Reply-To: <6280325c0705010905q4e612e72j9b9ce87de1c9d342@mail.gmail.com> References: <4634C3B7.5050102@redhat.com> <6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com> <1178024400.13694.29.camel@aglarond.local> <6280325c0705010608p69667defo636136943500760a@mail.gmail.com> <463761B9.7060505@fedoraproject.org> <6280325c0705010905q4e612e72j9b9ce87de1c9d342@mail.gmail.com> Message-ID: <46376666.60402@fedoraproject.org> n0dalus wrote: > On 5/2/07, Rahul Sundaram wrote: >> n0dalus wrote: >> > Good to know. If this is to be the One True Way (TM), we should >> > probably document in the release notes how to find and set labels for >> > different filesystems. >> >> If you want to help, provide the content. >> > > I personally have no idea what commands are involved, and am > especially not knowledgeable about any problems that might occur > (particularly with regard to changing labels of partitions also used > by other operating systems). I want to help, but I don't have the > content nor do I feel confident enough in researching the content to > the level of understanding I need to write technical documentation for > others to rely on. I have given a suggestion, and that can be > interpreted as help or not. Suggestions have already been given twice here on this topic before. What need is someone to step up and contribute. Rahul From cdhouch at gmail.com Tue May 1 16:12:30 2007 From: cdhouch at gmail.com (Caerie Houchins) Date: Tue, 1 May 2007 11:12:30 -0500 Subject: f7t4 problems In-Reply-To: References: <777ab80a0705010629n698bfe15gd7f24fed7a0e4701@mail.gmail.com> Message-ID: On 5/1/07, Caerie Houchins wrote: > > On 5/1/07, Amit Rana wrote: > > > > More information.... > > > > Another place where laptop hangs while booting.... > > > > Switched to high resolution mode on CPU1 > > PnP:00:03: ioport range 0x1080-0x10bf has been reserved > > .....some more messages PnP > > PnP:00:0b: iomem range 0xfed00000-0xfed003ff could not be reserved > > > > I noticed that there two packages related to x > > xorg-x11-proto-devel-7.2-9.fc7 > > xorg-x11-server-1.3.0.0-3.fc7 > > > > shall I try to uninstall them and install older version and try? > > > > -- > > fedora-test-list mailing list > > fedora-test-list at redhat.com > > To unsubscribe: > > https://www.redhat.com/mailman/listinfo/fedora-test-list > > > > Having the same problem with the video coming up white. It appears to be > tied to the intel driver for the video card somehow. Still gathering > information. > > -- > Caerie Houchins > This is definitely an incompatibility with the new xorg-x11-server-Xorg- 1.3.0.0-3.fc7 and the Intel driver found in the i810 x11 driver rpm. The system worked when I set the driver to the standard i810 but looked horrible (to be expected). I downgraded xorg-x11-server-Xorg from 1.30 back to 1.29found on the FC7 T4 DVD and everything appears to be working again. For the record I have the intel i945 graphics card on my Dell laptop. If you have this card and are using the "intel" driver, you probably want to skip the new xorg-x11-server package in rawhide today. -- Caerie Houchins -------------- next part -------------- An HTML attachment was scrubbed... URL: From drago01 at gmail.com Tue May 1 16:17:40 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 18:17:40 +0200 Subject: F7 and iwlwifi using ipw3945 hardware In-Reply-To: <1177715691.3026.1.camel@aglarond.local> References: <46325787.7080106@verizon.net> <1177705101.6286.29.camel@erebor.boston.redhat.com> <1177715691.3026.1.camel@aglarond.local> Message-ID: On 4/28/07, Jeremy Katz wrote: > > On Fri, 2007-04-27 at 23:20 +0200, dragoran dragoran wrote: > > On 4/27/07, Jeremy Katz wrote: > > On Fri, 2007-04-27 at 16:05 -0400, Peter F. Patel-Schneider > > wrote: > > > Is the iwlwifi package going to work in F7? > > > > It's either going to work or we'll pull it. Sadly, the driver > > is not in > > the shape that anyone hoped it would be :( > > > > what about updating to 0.0.14? it has many bugfixes (see changelog) > > Doesn't solve the big problem... I was testing with tip of iwlwifi git > today and still getting the same oops when scanning while associated. > I'm still hoping that we can get the problems worked out, but am less > optimistic than I had previously been iwlwifi 0.0.16 (released today and in cvs already) works much better (no mor oops) and even wpa works fine for me. (i tested with 0.0.15 but 0.0.16 only contains additional fixes so it should work even better) -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean.bruno at dsl-only.net Tue May 1 16:22:56 2007 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Tue, 01 May 2007 09:22:56 -0700 Subject: FC7T4 Install Failure(SCSI READ ERRORS) In-Reply-To: <1178035196.15302.92.camel@metroid.rdu.redhat.com> References: <1177996524.3488.14.camel@home-desk> <1178035196.15302.92.camel@metroid.rdu.redhat.com> Message-ID: <1178036576.3309.5.camel@home-desk> On Tue, 2007-05-01 at 15:59 +0000, Will Woods wrote: > On Mon, 2007-04-30 at 22:15 -0700, Sean Bruno wrote: > > Sorry for the late install folks, I know this is T4 and I should have > > gotten around to this sooner. It's been a while since I've had some > > time to use a test release(I'm not sure where FC7T4 bugs go in bugzilla > > even!). > > We're always glad to have the help. F7t4 bugs should go under "devel". > This was mentioned in the release announcement. Ah...thanks! I'll do that. > > > Not sure why I would get these errors on install, and I'm not quite sure > > if they are from my hard drives or my CDROM. I _assume_ that this is a > > CDROM drive read failing. I have a Sony DVD Burner, model DRU-800A. > > It's pretty likely. It's amazing how inexact CD/DVD reading and writing > really are. If you're having I/O problems with a CD/DVD-based install, > the *first* thing you should do is try to burn another one. Even if "it > works in another machine", some drives are just picky about what types > of media they will read. Or sometimes they get a little overheated and > stop reading some types of media but not others. And so on. > I'm concerned that FC6 doesn't have any issues when installing from DVD, so I'm fairly certain this has been introduced in FC7. Just for fun I went ahead and tried an install of FC6 and it works fine. > If you still have trouble with the optical drive, you can create a spare > partition, copy the ISO on there, and install from that. > I'll give that a whirl. Sean From mschwendt.tmp0701.nospam at arcor.de Tue May 1 16:29:41 2007 From: mschwendt.tmp0701.nospam at arcor.de (Michael Schwendt) Date: Tue, 1 May 2007 18:29:41 +0200 Subject: liferea flakes only for me? In-Reply-To: <1178035565.5733.4.camel@lincoln> References: <5021.1178028208@lwn.net> <1178035565.5733.4.camel@lincoln> Message-ID: <20070501182941.c7308dd1.mschwendt.tmp0701.nospam@arcor.de> On Tue, 01 May 2007 12:06:05 -0400, Brian Pepple wrote: > Upstream Liferea has disabled the gtkhtml plugin for x86_64 builds. :) That would have killed the old plan to split off the mozilla plugin into a sub-package. Hmmm... From wwoods at redhat.com Tue May 1 16:33:53 2007 From: wwoods at redhat.com (Will Woods) Date: Tue, 01 May 2007 12:33:53 -0400 Subject: fc7t4 3116: Ethernet Still Unreliable In-Reply-To: <1178008659.3935.7.camel@omen.com> References: <1178008659.3935.7.camel@omen.com> Message-ID: <1178037233.28491.1.camel@metroid.rdu.redhat.com> On Tue, 2007-05-01 at 01:37 -0700, Chuck Forsberg WA7KGX N2469R wrote: > The previously reported problem of a PCI ethernet board > losing transmit interrupts is still present in fc7t4 > x86_64 kernel 3116. The last good kernel was 2869, to > which I have reverted. It'd help if you mentioned which ethernet card you're talking about, or gave a link to the previous report. Especially if the previous report includes a bugzilla reference. -w -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sean.bruno at dsl-only.net Tue May 1 16:40:03 2007 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Tue, 01 May 2007 09:40:03 -0700 Subject: FC7T4 Install Failure(SCSI READ ERRORS) In-Reply-To: <1178035196.15302.92.camel@metroid.rdu.redhat.com> References: <1177996524.3488.14.camel@home-desk> <1178035196.15302.92.camel@metroid.rdu.redhat.com> Message-ID: <1178037603.3309.7.camel@home-desk> On Tue, 2007-05-01 at 15:59 +0000, Will Woods wrote: > On Mon, 2007-04-30 at 22:15 -0700, Sean Bruno wrote: > > Sorry for the late install folks, I know this is T4 and I should have > > gotten around to this sooner. It's been a while since I've had some > > time to use a test release(I'm not sure where FC7T4 bugs go in bugzilla > > even!). > > We're always glad to have the help. F7t4 bugs should go under "devel". > This was mentioned in the release announcement. > Filed: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238582 Sean From mbarnes at redhat.com Tue May 1 16:41:01 2007 From: mbarnes at redhat.com (Matthew Barnes) Date: Tue, 1 May 2007 12:41:01 -0400 Subject: [SECURITY] Fedora Core 6 Test Update: evolution-data-server-1.8.3-6.fc6 Message-ID: <200705011641.l41Gf1qx024474@int-mx1.corp.redhat.com> --------------------------------------------------------------------- Fedora Test Update Notification FEDORA-2007-484 2007-05-01 --------------------------------------------------------------------- Product : Fedora Core 6 Name : evolution-data-server Version : 1.8.3 Release : 6.fc6 Summary : Backend data server for Evolution Description : The evolution-data-server package provides a unified backend for programs that work with contacts, tasks, and calendar information. It was originally developed for Evolution (hence the name), but is now used by other packages. --------------------------------------------------------------------- Update Information: This update fixes a security vulnerability in APOP authentication. This only affects POP mail accounts. --------------------------------------------------------------------- * Mon Apr 30 2007 Matthew Barnes - 1.8.3-6.fc6 - Revise patch for RH bug #235290 to not break string freeze. * Tue Apr 24 2007 Matthew Barnes - 1.8.3-5.fc6 - Add patch for RH bug #235290 (APOP authentication vulnerability). * Fri Mar 9 2007 Matthew Barnes - 1.8.3-4.fc6 - Add patch for GNOME bug #363102 (local calendar crasher). - Add patch for GNOME bug #415922 (support MS ISA Server 2004). - Patches by Kenny Root and Patrick Ohly. --------------------------------------------------------------------- This update can be downloaded from: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/6/ 8bb3e79deb3808f48e331a97a09446a18bd233ed SRPMS/evolution-data-server-1.8.3-6.fc6.src.rpm 8bb3e79deb3808f48e331a97a09446a18bd233ed noarch/evolution-data-server-1.8.3-6.fc6.src.rpm 25be5a895ed9d66ca713c4b4c86c6c3fb20a1e0f ppc/evolution-data-server-1.8.3-6.fc6.ppc.rpm b52a54b925d5cc4268f4223af01c9c2c81591bf6 ppc/debug/evolution-data-server-debuginfo-1.8.3-6.fc6.ppc.rpm e16b583cff282a56cc1ce808f30c6183f890e744 ppc/evolution-data-server-devel-1.8.3-6.fc6.ppc.rpm b1036b78e26788fe81650603d3daea9488ff8791 x86_64/evolution-data-server-1.8.3-6.fc6.x86_64.rpm 996ec308a56024db2fd9ec01afabd2359d0e1ea5 x86_64/evolution-data-server-devel-1.8.3-6.fc6.x86_64.rpm ac1c0429e55e4123a80ab16d7b3f9f8eb308f1d4 x86_64/debug/evolution-data-server-debuginfo-1.8.3-6.fc6.x86_64.rpm 2b0bcc43ecbd569cc49ffe73411d52801be9187d i386/evolution-data-server-devel-1.8.3-6.fc6.i386.rpm f9ba7643262ca4d6080abb610f0ef764f1f85a5e i386/evolution-data-server-1.8.3-6.fc6.i386.rpm 1db30f34a7e05aba31c6dec5408f935355bf15cd i386/debug/evolution-data-server-debuginfo-1.8.3-6.fc6.i386.rpm This update can be installed with the 'yum' update program. Use 'yum update package-name' at the command line. For more information, refer to 'Managing Software with yum,' available at http://fedora.redhat.com/docs/yum/. --------------------------------------------------------------------- From mbarnes at redhat.com Tue May 1 16:41:36 2007 From: mbarnes at redhat.com (Matthew Barnes) Date: Tue, 1 May 2007 12:41:36 -0400 Subject: [SECURITY] Fedora Core 5 Test Update: evolution-data-server-1.6.3-4.fc5 Message-ID: <200705011641.l41Gfau9024634@int-mx1.corp.redhat.com> --------------------------------------------------------------------- Fedora Test Update Notification FEDORA-2007-485 2007-05-01 --------------------------------------------------------------------- Product : Fedora Core 5 Name : evolution-data-server Version : 1.6.3 Release : 4.fc5 Summary : Backend data server for evolution Description : The evolution-data-server package provides a unified backend for programs that work with contacts, tasks, and calendar information. It was originally developed for Evolution (hence the name), but is now used by other packages. --------------------------------------------------------------------- Update Information: This update fixes a security vulnerability in APOP authentication. This only affects POP mail accounts. --------------------------------------------------------------------- * Mon Apr 30 2007 Matthew Barnes - 1.6.3-4.fc5 - Revise patch for RH bug #235290 to not break string freeze. * Tue Apr 24 2007 Matthew Barnes - 1.6.3-3.fc5 - Add patch for RH bug #235290 (APOP authentication vulnerability). * Tue Mar 6 2007 Matthew Barnes - 1.6.3-2.fc5 - Add patch for GNOME bug #301363 (update timezones). * Thu Aug 3 2006 Matthew Barnes - 1.6.3-1.fc5.2 - Remove patches for Gnome.org bug #309079 (rejected upstream). - One of these patches was causing RH bug #167157. - No longer packaging unused patches. * Mon Jul 31 2006 Matthew Barnes - 1.6.3-1.fc5.1 - Update to 1.6.3 - Dynamically link to BDB. - Add Requires for db4 and BuildRequires for db4-devel. - Add missing Requires and BuildRequires from Rawhide. - Clean up spec file, renumber patches. * Tue May 30 2006 Matthew Barnes - 1.6.2-1.fc5.1 - Update to 1.6.2 - Remove evolution-data-server-1.3.5-nspr_fix.patch (fixed upstream). - Update evolution-data-server-1.2.0-validatehelo.patch and rename it to version 1.6.2. --------------------------------------------------------------------- This update can be downloaded from: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/5/ 8549f9d02fa5f70ddd579afd0aaef08e2058e09b SRPMS/evolution-data-server-1.6.3-4.fc5.src.rpm 8549f9d02fa5f70ddd579afd0aaef08e2058e09b noarch/evolution-data-server-1.6.3-4.fc5.src.rpm 888ef4afa73f0cb693b2bb74796f41940f24b00b ppc/evolution-data-server-1.6.3-4.fc5.ppc.rpm 26359b4d14f0f5c7f5c3d19915fdd83d54bd8bba ppc/evolution-data-server-devel-1.6.3-4.fc5.ppc.rpm 35506272128afc564cb35419ae196523118cf4ce ppc/debug/evolution-data-server-debuginfo-1.6.3-4.fc5.ppc.rpm c46605c94ae7c3795d27c6b40a65ac52f653b17d x86_64/evolution-data-server-1.6.3-4.fc5.x86_64.rpm 5a20be20e0725ecfe3c77495d6fa1782afa765f7 x86_64/debug/evolution-data-server-debuginfo-1.6.3-4.fc5.x86_64.rpm c3e378ab23055358bd8d77a14d3a9a10e3bcf29c x86_64/evolution-data-server-devel-1.6.3-4.fc5.x86_64.rpm d80a856f717de964bbdddbd20642e0f3ad7a5616 i386/debug/evolution-data-server-debuginfo-1.6.3-4.fc5.i386.rpm 7575570d2a344af609a8e7180e1a8edd0b583a52 i386/evolution-data-server-devel-1.6.3-4.fc5.i386.rpm a14357917a79e08a91513764614d62ef0ed7fb67 i386/evolution-data-server-1.6.3-4.fc5.i386.rpm This update can be installed with the 'yum' update program. Use 'yum update package-name' at the command line. For more information, refer to 'Managing Software with yum,' available at http://fedora.redhat.com/docs/yum/. --------------------------------------------------------------------- From bpepple at fedoraproject.org Tue May 1 16:45:11 2007 From: bpepple at fedoraproject.org (Brian Pepple) Date: Tue, 01 May 2007 12:45:11 -0400 Subject: liferea flakes only for me? In-Reply-To: <20070501182941.c7308dd1.mschwendt.tmp0701.nospam@arcor.de> References: <5021.1178028208@lwn.net> <1178035565.5733.4.camel@lincoln> <20070501182941.c7308dd1.mschwendt.tmp0701.nospam@arcor.de> Message-ID: <1178037911.5733.11.camel@lincoln> On Tue, 2007-05-01 at 18:29 +0200, Michael Schwendt wrote: > On Tue, 01 May 2007 12:06:05 -0400, Brian Pepple wrote: > > > Upstream Liferea has disabled the gtkhtml plugin for x86_64 builds. > > :) That would have killed the old plan to split off the mozilla plugin > into a sub-package. Yeah, upstream barely supports x86_64, so I'm actively looking for x86_64 maintainers that want to co-maintain this package since I don't have a x86_64 machine. If anyone is interested please contact me. /B -- Brian Pepple gpg --keyserver pgp.mit.edu --recv-keys 810CC15E BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From das_deniz at yahoo.com Tue May 1 16:55:39 2007 From: das_deniz at yahoo.com (das) Date: Tue, 1 May 2007 09:55:39 -0700 (PDT) Subject: F7 and iwlwifi using ipw3945 hardware In-Reply-To: Message-ID: <364242.72132.qm@web33105.mail.mud.yahoo.com> Wonderful Fedor WiFi Folks (wfwf), I apologize for this sad email - but please help educate us to be better users / bug reporters. I'm sure I'm not the only one confused by the new world of wifi and what f7 is doing and this site: http://intellinuxwireless.org/index.php?p=iwlwifi isn't helping much. Do we have an f7 wifi page write-up somewhere (you know like the quickstart guide for Xen in FC4, FC5 and FC6) the fedoraproject.org wiki title search for "wifi" finds "0 results out of about 7542 pages." there's iwlwifi, "the new way," (which uses a mac80211 driver available in the kernel pkgs now (since what rev?)) vs ipw*, "the old FC6/RHEL5 way" yet we still have ipw2100 and ipw2200 -firmware pkgs? and we don't have/need the ipw3954-firmware pkg but instead we use the new microcode pkg iwlwifi-ucode which we've renamed iwlwifi-firmware ? i was going to try to repackage iwlwifi-0.0.16.tgz for myself - but i don't even know what rpm this corresponds to for us.... did we rename this too? arggg... :) thanks for reading and any feedback. hopefully someone can scribble something up for wifi on the wiki, contrasting old and new drivers, to help take some of the incredible pressure off you all supporting this feature set. das --- dragoran dragoran wrote: > On 4/28/07, Jeremy Katz wrote: > > > > On Fri, 2007-04-27 at 23:20 +0200, dragoran > dragoran wrote: > > > On 4/27/07, Jeremy Katz > wrote: > > > On Fri, 2007-04-27 at 16:05 -0400, Peter > F. Patel-Schneider > > > wrote: > > > > Is the iwlwifi package going to work > in F7? > > > > > > It's either going to work or we'll pull > it. Sadly, the driver > > > is not in > > > the shape that anyone hoped it would be > :( > > > > > > what about updating to 0.0.14? it has many > bugfixes (see changelog) > > > > Doesn't solve the big problem... I was testing > with tip of iwlwifi git > > today and still getting the same oops when > scanning while associated. > > I'm still hoping that we can get the problems > worked out, but am less > > optimistic than I had previously been > > > iwlwifi 0.0.16 (released today and in cvs already) > works much better (no > mor oops) and even wpa works fine for me. > (i tested with 0.0.15 but 0.0.16 only contains > additional fixes so it should > work even better) > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From davej at redhat.com Tue May 1 16:56:21 2007 From: davej at redhat.com (Dave Jones) Date: Tue, 1 May 2007 12:56:21 -0400 Subject: Latest Rawhide kernel doesn't boot In-Reply-To: <1178029840.5722.5.camel@scrappy.miketc.com> References: <1177824841.2208.1.camel@scrappy.miketc.com> <20070429060210.GA23750@redhat.com> <1177850273.10817.3.camel@scrappy.miketc.com> <1178025431.5722.2.camel@scrappy.miketc.com> <46374CEC.1040206@bellsouth.net> <1178029840.5722.5.camel@scrappy.miketc.com> Message-ID: <20070501165621.GD8189@redhat.com> On Tue, May 01, 2007 at 09:30:40AM -0500, Mike Chambers wrote: > On Tue, 2007-05-01 at 09:21 -0500, Jay Cliburn wrote: > > > The sis900 driver had a bug that was patched April 20. Unfortunately, the patch > > introduced a regression that was then patched April 26 -- one day after 2.6.21 > > was released. The second patch appears to fix it, according to user reports in > > the below referenced thread. > > > > Details: http://marc.info/?l=linux-netdev&m=117707735821802&w=2 > > Ok,so hopefully the next release by Dave will have the fix. Fixed in CVS, will be in the next push to rawhide. (or grab it from my people.redhat.com page) Dave -- http://www.codemonkey.org.uk From amit.rana at gmail.com Tue May 1 16:53:20 2007 From: amit.rana at gmail.com (Amit Rana) Date: Tue, 1 May 2007 22:23:20 +0530 Subject: f7t4 problems Message-ID: <777ab80a0705010953s244fa981ted658ba4961aa025@mail.gmail.com> Hi, Thanks for the response. I have moved back to xorg-x11-server-Xorg-1.2.99.905-5.fc7.i386.rpm and now x-windows is working. I will file a bug report. Regards. Amit. From das_deniz at yahoo.com Tue May 1 17:05:39 2007 From: das_deniz at yahoo.com (das) Date: Tue, 1 May 2007 10:05:39 -0700 (PDT) Subject: F7 and iwlwifi using ipw3945 hardware In-Reply-To: <364242.72132.qm@web33105.mail.mud.yahoo.com> Message-ID: <23218.17749.qm@web33108.mail.mud.yahoo.com> ah... --- das wrote: > Wonderful Fedor WiFi Folks (wfwf), > > i was going to try to repackage iwlwifi-0.0.16.tgz > for > myself - but i don't even know what rpm this > corresponds to for us.... did we rename this too? > arggg... :) it's a kernel module just like the mac80211 driver __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From amit.rana at gmail.com Tue May 1 17:12:05 2007 From: amit.rana at gmail.com (Amit Rana) Date: Tue, 1 May 2007 22:42:05 +0530 Subject: # Re: f7t4 problems Message-ID: <777ab80a0705011012h33341cc0oce9b969eddb68b7d@mail.gmail.com> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238585 Bug# 238585 added ------ original msg ------------ Hi, Thanks for the response. I have moved back to xorg-x11-server-Xorg-1.2.99.905-5.fc7.i386.rpm and now x-windows is working. I will file a bug report. Regards. Amit. From amit.rana at gmail.com Tue May 1 17:31:33 2007 From: amit.rana at gmail.com (Amit Rana) Date: Tue, 1 May 2007 23:01:33 +0530 Subject: ipw3945 on f7t4 Message-ID: <777ab80a0705011031y55a11a57k6ee2e2e211f050f5@mail.gmail.com> Kindly advice if this should go to fedora-laptop? Hi, I am unable to get wifi to work on my laptop. configuration: http://smolt.fedoraproject.org/show?UUID=22c8710a-e702-4bcb-b002-448a3e53805b lspci output: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 03:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 03:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01) 03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05) 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) out of ipw3945d ipw3945d - regulatory daemon Copyright (C) 2005-2006 Intel Corporation. All rights reserved. version: 1.7.22 2007-05-01 22:57:40: ERROR: Could not find Intel PRO/Wireless 3945ABG Network Connection /etc/modprobe.conf alias eth1 ipw3945 install ipw3945 /sbin/modprobe --ignore-install ipw3945 associate=1; sleep 0.5; /sbin/ipw3945d --quiet remove ipw3945 /sbin/ipw3945d --kill; /sbin/modprobe -r --ignore-remove ipw3945 alias eth0 b44 alias scsi_hostadapter ata_piix alias snd-card-0 snd-hda-intel options snd-card-0 index=0 options snd-hda-intel index=0 remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel alias wmaster0 ipw3945 I have followed instructions given in various forums and mailing list but not sure what am I doing wrong? Kindly advice. Regards, Amit. From davej at redhat.com Tue May 1 17:35:01 2007 From: davej at redhat.com (Dave Jones) Date: Tue, 1 May 2007 13:35:01 -0400 Subject: ipw3945 on f7t4 In-Reply-To: <777ab80a0705011031y55a11a57k6ee2e2e211f050f5@mail.gmail.com> References: <777ab80a0705011031y55a11a57k6ee2e2e211f050f5@mail.gmail.com> Message-ID: <20070501173501.GA29167@redhat.com> On Tue, May 01, 2007 at 11:01:33PM +0530, Amit Rana wrote: > out of ipw3945d > ipw3945d - regulatory daemon > Copyright (C) 2005-2006 Intel Corporation. All rights reserved. > version: 1.7.22 > 2007-05-01 22:57:40: ERROR: Could not find Intel PRO/Wireless 3945ABG > Network Connection > > /etc/modprobe.conf > alias eth1 ipw3945 The kernel now provides an 'iwlwifi' module which means you don't need ipw3945, or ipw3945d. However it's still having some bugs shaken out of it, so it's not perfect right now. Dave -- http://www.codemonkey.org.uk From caf at omen.com Tue May 1 18:10:35 2007 From: caf at omen.com (Chuck Forsberg WA7KGX N2469R) Date: Tue, 01 May 2007 11:10:35 -0700 Subject: [Fwd: Ethernet problem in 2895 kernel] Message-ID: <1178043035.3935.27.camel@omen.com> Per request, here is the Feb 1 message reporting the problem in the 2895 kernel. I have tried two or three different manufacturers' cards for eth0 with the same result. I do not recall ever seeing this failure with 2869 and older kernels. This bug has been present for the last three months. I wonder if it has propagated to the commercial Linix products. -------------- next part -------------- An embedded message was scrubbed... From: Chuck Forsberg WA7KGX N2469R Subject: Ethernet problem in 2895 kernel Date: Thu, 01 Feb 2007 10:11:21 -0800 Size: 2930 URL: From cebbert at redhat.com Tue May 1 18:23:27 2007 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 01 May 2007 14:23:27 -0400 Subject: [Fwd: Ethernet problem in 2895 kernel] In-Reply-To: <1178043035.3935.27.camel@omen.com> References: <1178043035.3935.27.camel@omen.com> Message-ID: <4637859F.7000505@redhat.com> Chuck Forsberg WA7KGX N2469R wrote: > Per request, here is the Feb 1 message reporting the problem in the > 2895 kernel. I have tried two or three different manufacturers' > cards for eth0 with the same result. > > I do not recall ever seeing this failure with 2869 and older kernels. > > This bug has been present for the last three months. I wonder if it has > propagated to the commercial Linix products. > This is BZ #231687. I asked about this on linux-kernel and netdev last month and nobody replied. From wwoods at redhat.com Tue May 1 18:24:55 2007 From: wwoods at redhat.com (Will Woods) Date: Tue, 01 May 2007 18:24:55 +0000 Subject: [Fwd: Ethernet problem in 2895 kernel] In-Reply-To: <1178043035.3935.27.camel@omen.com> References: <1178043035.3935.27.camel@omen.com> Message-ID: <1178043895.28491.5.camel@metroid.rdu.redhat.com> On Tue, 2007-05-01 at 11:10 -0700, Chuck Forsberg WA7KGX N2469R wrote: > Per request, here is the Feb 1 message reporting the problem in the > 2895 kernel. I have tried two or three different manufacturers' > cards for eth0 with the same result. > > I do not recall ever seeing this failure with 2869 and older kernels. > > This bug has been present for the last three months. I wonder if it has > propagated to the commercial Linix products. This still doesn't say what chipset the devices are. It's fairly hard to track problems when we don't know what driver they're in. You should open a bug in bugzilla (Product "Fedora Core", version "FC6", component "kernel") and add an attachment containing the output of 'lspci'. -w -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From wwoods at redhat.com Tue May 1 18:33:53 2007 From: wwoods at redhat.com (Will Woods) Date: Tue, 01 May 2007 18:33:53 +0000 Subject: [Fwd: Ethernet problem in 2895 kernel] In-Reply-To: <4637859F.7000505@redhat.com> References: <1178043035.3935.27.camel@omen.com> <4637859F.7000505@redhat.com> Message-ID: <1178044433.28491.10.camel@metroid.rdu.redhat.com> On Tue, 2007-05-01 at 14:23 -0400, Chuck Ebbert wrote: > Chuck Forsberg WA7KGX N2469R wrote: > > Per request, here is the Feb 1 message reporting the problem in the > > 2895 kernel. I have tried two or three different manufacturers' > > cards for eth0 with the same result. > > > > I do not recall ever seeing this failure with 2869 and older kernels. > > > > This bug has been present for the last three months. I wonder if it has > > propagated to the commercial Linix products. > > > > This is BZ #231687. That bug is against FC6. Have you tried the kernel mentioned in that bug? (2.6.20-1.2944.fc6) If this is also present in F7, you should probably file another bug, this one against Fedora Core/devel/kernel. Be sure to include lspci output and the contents of /proc/interrupts. -w -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From drago01 at gmail.com Tue May 1 18:48:26 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 20:48:26 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <20070501173501.GA29167@redhat.com> References: <777ab80a0705011031y55a11a57k6ee2e2e211f050f5@mail.gmail.com> <20070501173501.GA29167@redhat.com> Message-ID: On 5/1/07, Dave Jones wrote: > > On Tue, May 01, 2007 at 11:01:33PM +0530, Amit Rana wrote: > > > out of ipw3945d > > ipw3945d - regulatory daemon > > Copyright (C) 2005-2006 Intel Corporation. All rights reserved. > > version: 1.7.22 > > 2007-05-01 22:57:40: ERROR: Could not find Intel PRO/Wireless 3945ABG > > Network Connection > > > > /etc/modprobe.conf > > alias eth1 ipw3945 > > The kernel now provides an 'iwlwifi' module which means you don't need > ipw3945, or ipw3945d. However it's still having some bugs shaken out > of it, so it's not perfect right now. I have tested kernel-2.6.21-1.3122.fc7 from your people page (which has iwlwifi 0.0.16) and it works much better now. wpa works, no oops, keeps the connection, uses the correct rate,scanning works etc ;) the only problem that it has is the handling of the killswitch; which I reported upstream a minute ago. Dave > > -- > http://www.codemonkey.org.uk > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jacliburn at bellsouth.net Tue May 1 18:50:42 2007 From: jacliburn at bellsouth.net (Jay Cliburn) Date: Tue, 01 May 2007 13:50:42 -0500 Subject: [Fwd: Ethernet problem in 2895 kernel] In-Reply-To: <1178043035.3935.27.camel@omen.com> References: <1178043035.3935.27.camel@omen.com> Message-ID: <46378C02.6090904@bellsouth.net> Chuck Forsberg WA7KGX N2469R wrote: > I have tried two or three different manufacturers' > cards for eth0 with the same result. What type cards? You mention your motherboard type below (Asus A8N-E), but you indicate the onboard nic (eth1) isn't giving you problems. Have you tried these PCI add-in nics in different slots? Posting the output of dmesg and lspci would help identify which driver is in play. > > I do not recall ever seeing this failure with 2869 and older kernels. > > This bug has been present for the last three months. I wonder if it has > propagated to the commercial Linix products. > > > ------------------------------------------------------------------------ > > Subject: > Ethernet problem in 2895 kernel > From: > Chuck Forsberg WA7KGX N2469R > Date: > Thu, 01 Feb 2007 10:11:21 -0800 > To: > Fedora-Test-List > > To: > Fedora-Test-List > > > Since updating to the FC6 386 2895 kernel I have has a number > of partial failures of the Ethernet system under heavy load. > System: Asus a8n-e socket 939 with 3 GB RAM running 386 FC6. > Eth0 is a PCI 10/100 NIC, eth1 is the onboard gigabit NIC. > NAT controlled by rc.firewall 2.4. Eth0 connects to the > cable modem, eth1 to the local net. > > Under heavy load, the following error messages appear > and then eth0 stops working, severing the internet connection. > I have not seen this problem prior to the 2895 kernel. > > > Jan 31 22:01:19 omen kernel: NETDEV WATCHDOG: eth0: transmit timed out > Jan 31 22:01:19 omen kernel: eth0: transmit timed out, tx_status 00 > status 8601. > Jan 31 22:01:19 omen kernel: diagnostics: net 0cd8 media 8880 dma > 0000003a fifo 0000 > Jan 31 22:01:19 omen kernel: eth0: Interrupt posted but not delivered -- > IRQ blocked by another device? > Jan 31 22:01:19 omen kernel: Flags; bus-master 1, dirty 80(0) current > 80(0) > Jan 31 22:01:19 omen kernel: Transmit list 00000000 vs. f714b200. > Jan 31 22:01:19 omen kernel: 0: @f714b200 length 80000042 status > 00010042 > Jan 31 22:01:19 omen kernel: 1: @f714b2a0 length 80000052 status > 0c010052 > Jan 31 22:01:19 omen kernel: 2: @f714b340 length 80000043 status > 0c010043 > Jan 31 22:01:19 omen kernel: 3: @f714b3e0 length 80000045 status > 0c010045 > Jan 31 22:01:19 omen kernel: 4: @f714b480 length 80000042 status > 00010042 > Jan 31 22:01:19 omen kernel: 5: @f714b520 length 8000004a status > 0c01004a > Jan 31 22:01:19 omen kernel: 6: @f714b5c0 length 8000004c status > 0c01004c > Jan 31 22:01:19 omen kernel: 7: @f714b660 length 8000004d status > 0c01004d > Jan 31 22:01:19 omen kernel: 8: @f714b700 length 80000052 status > 0c010052 > Jan 31 22:01:19 omen kernel: 9: @f714b7a0 length 80000043 status > 0c010043 > Jan 31 22:01:19 omen kernel: 10: @f714b840 length 80000045 status > 0c010045 > Jan 31 22:01:19 omen kernel: 11: @f714b8e0 length 8000004a status > 0c01004a > Jan 31 22:01:19 omen kernel: 12: @f714b980 length 8000004c status > 0c01004c > Jan 31 22:01:19 omen kernel: 13: @f714ba20 length 8000004c status > 0c01004c > Jan 31 22:01:19 omen kernel: 14: @f714bac0 length 80000052 status > 8c010052 > Jan 31 22:01:19 omen kernel: 15: @f714bb60 length 80000056 status > 8c010056 > > > From gunchev at gmail.com Tue May 1 18:52:04 2007 From: gunchev at gmail.com (Doncho N. Gunchev) Date: Tue, 1 May 2007 21:52:04 +0300 Subject: F7t4 KDE live CD test report Message-ID: <200705012152.04163.gunchev@gmail.com> I installed F7t4 from the KDE live CD, my hardware profile is: ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results: Desktop - everything works fine, except for kpowersave - it crashes, but rpmverify kpowersave shows no problem. It worked fine from the CD and works with the xen kernel (2.6.20, no .21 for xen), but after leaving the laptop on for the night it was not responding. Network - iwlwifi seemed to work untill it connected to the AP (wpa2) and nothing more (no traffic, no ping). b44 worked fine (Ethernet). X11's intel driver was used instead of i810 and worked fine, frozen-bubble and ppracer are playable. There was no need to use 915resolution any more. The same trick (change i810 to intel) does not work with FC6, after resume from ram the display is black or with wrong colors and the mouse is not working. With the live CD my mouse pad was a bit crazy - left was middle button (which I don't have), up was right, down was left, right was nothing and scrolling did not work (moving up/down on the right side of the pad). After installing some more X packages (don't ask me which, many) it worked fine (missing from the live KDE CD, some fonts too). Maybe kudzu did something at some point... Suspend to ram did not work with any kernel. In most cases, when the machine (laptop - ACER aspire 5610) wakes up the disk led stays on and nothing more happens. Just once, after suspending to ram the machine wakes up, but the keyboard does nothing. I have no idea what's the problem, I was able to see the kernel complaining about unknown keys once (volume, brightness...), but no caps-lock/num-lock or anything else. The disk led is constantly on. Hybernation (suspend to disk) works if I kill iwlwifi.ko. I created /etc/pm/hooks/11iwlwifi, which solved the problem: --- cut --- #!/bin/sh exit 0 case "$1" in hibernate|suspend) /sbin/lsmod | grep -q iwlwifi || exit 0 { touch /var/run/iwlwifi && /sbin/modprobe -r iwlwifi ; } \ 2>/dev/null ;; thaw|resume) [ -f /var/run/iwlwifi ] || exit 0 { /sbin/modprobe iwlwifi && rm -f /var/run/iwlwifi \ && /sbin/service NetworkManager restart ; } 2>/dev/null ;; *) ;; esac exit $? --- cut --- Have not tried ipw3945, but I guess it will work as it does in FC6. After updating from kernel 2.6.20-1.3104.fc7 to 2.6.21-1.3116.fc7 the system did not boot. I had to replace 'root=LABEL=/1' with 'root=/dev/VG0/LVroot1' in grub.conf to get it working again. The label is really '/1', but it could not find it. After installing 2.6.20-2925.5.fc7xen the new grub entry was copied from my FC6 (root=/dev/VG0/LVroot instead of /dev/VG0/LVroot1), I have FC6's grub chainloading F7's and F7's is on hda2 (sda2). Nothing else really changed. Should I fill bug reports for these? -- Regards, Doncho From sgrubb at redhat.com Tue May 1 18:55:12 2007 From: sgrubb at redhat.com (Steve Grubb) Date: Tue, 1 May 2007 14:55:12 -0400 Subject: [Fwd: Ethernet problem in 2895 kernel] In-Reply-To: <46378C02.6090904@bellsouth.net> References: <1178043035.3935.27.camel@omen.com> <46378C02.6090904@bellsouth.net> Message-ID: <200705011455.12220.sgrubb@redhat.com> On Tuesday 01 May 2007 14:50, Jay Cliburn wrote: > What type cards? ?You mention your motherboard type below (Asus A8N-E), but > you indicate the onboard nic (eth1) isn't giving you problems. I see the same problem. This is the lspci output: 05:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78) 3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express I think Chuck traced the text that comes out to 3Com, but its been a while. AFAICT, the problem started around the 2834 kernel/Feb 15. -Steve From drago01 at gmail.com Tue May 1 18:59:38 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 20:59:38 +0200 Subject: F7t4 KDE live CD test report In-Reply-To: <200705012152.04163.gunchev@gmail.com> References: <200705012152.04163.gunchev@gmail.com> Message-ID: On 5/1/07, Doncho N. Gunchev wrote: > Network - iwlwifi seemed to work untill it connected to the AP (wpa2) > and > nothing more (no traffic, no ping). b44 worked fine (Ethernet). can you try the kernel from here: http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/ iwlwifi works fine for me using this (and the previous one) the version in the livecd does not even connet to my wpa/wpa2 ap. but no everything seems to work with it, traffic, ping etc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gunchev at gmail.com Tue May 1 19:08:55 2007 From: gunchev at gmail.com (Doncho N. Gunchev) Date: Tue, 1 May 2007 22:08:55 +0300 Subject: F7t4 KDE live CD test report In-Reply-To: References: <200705012152.04163.gunchev@gmail.com> Message-ID: <200705012208.56002.gunchev@gmail.com> On Tuesday 2007-05-01 21:59:38 dragoran dragoran wrote: > On 5/1/07, Doncho N. Gunchev wrote: > > Network - iwlwifi seemed to work untill it connected to the AP (wpa2) > > and > > nothing more (no traffic, no ping). b44 worked fine (Ethernet). > > can you try the kernel from here: > http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/ > iwlwifi works fine for me using this (and the previous one) the version in > the livecd does not even connet to my wpa/wpa2 ap. > but no everything seems to work with it, traffic, ping etc. That's what I'm downloading now... kernel-2.6.21-1.3123.fc7.i686.rpm, thanks for the link ;-) -- Regards, Doncho From Fulko.Hew at sita.aero Tue May 1 19:12:13 2007 From: Fulko.Hew at sita.aero (Fulko.Hew at sita.aero) Date: Tue, 1 May 2007 15:12:13 -0400 Subject: ipw3945 on f7t4 In-Reply-To: Message-ID: fedora-test-list-bounces at redhat.com wrote on 05/01/2007 02:48:26 PM: > The kernel now provides an 'iwlwifi' module which means you don't need > ipw3945, or ipw3945d. However it's still having some bugs shaken out > of it, so it's not perfect right now. > > I have tested kernel-2.6.21-1.3122.fc7 from your people page (which has > iwlwifi 0.0.16) and it works much better now. > wpa works, no oops, keeps the connection, uses the correct rate,scanning works etc ;) > the only problem that it has is the handling of the killswitch; which I > reported upstream a minute ago. Assuming this new kernel gets shipped in the not-to-distant future... can someone _please_ post the steps required to install the appropriate software/firmware to get the 3945 going? This document is strictly confidential and intended only for use by the addressee unless otherwise stated. If you are not the intended recipient, please notify the sender immediately and delete it from your system. From gunchev at gmail.com Tue May 1 19:13:45 2007 From: gunchev at gmail.com (Doncho N. Gunchev) Date: Tue, 1 May 2007 22:13:45 +0300 Subject: F7t4 KDE live CD test report In-Reply-To: <200705012152.04163.gunchev@gmail.com> References: <200705012152.04163.gunchev@gmail.com> Message-ID: <200705012213.45770.gunchev@gmail.com> On Tuesday 2007-05-01 21:52:04 you wrote: > I installed F7t4 from the KDE live CD, my hardware profile is: > ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results: ... > Suspend to ram did not work with any kernel. In most cases, when the ... I think it has something to do with the new IDE /should I say SCSI ;-)/ disk driver. It complains that something is not supported... OT: Now, when hdparm -d 0/1 does nothing, how can I switch DMA on/off for my DVD-Writer and hard disk? -- Regards, Doncho From mike at miketc.com Tue May 1 19:33:54 2007 From: mike at miketc.com (Mike Chambers) Date: Tue, 01 May 2007 14:33:54 -0500 Subject: Latest Rawhide kernel doesn't boot In-Reply-To: <20070501165621.GD8189@redhat.com> References: <1177824841.2208.1.camel@scrappy.miketc.com> <20070429060210.GA23750@redhat.com> <1177850273.10817.3.camel@scrappy.miketc.com> <1178025431.5722.2.camel@scrappy.miketc.com> <46374CEC.1040206@bellsouth.net> <1178029840.5722.5.camel@scrappy.miketc.com> <20070501165621.GD8189@redhat.com> Message-ID: <1178048034.2210.0.camel@scrappy.miketc.com> On Tue, 2007-05-01 at 12:56 -0400, Dave Jones wrote: > On Tue, May 01, 2007 at 09:30:40AM -0500, Mike Chambers wrote: > > On Tue, 2007-05-01 at 09:21 -0500, Jay Cliburn wrote: > > > > > The sis900 driver had a bug that was patched April 20. Unfortunately, the patch > > > introduced a regression that was then patched April 26 -- one day after 2.6.21 > > > was released. The second patch appears to fix it, according to user reports in > > > the below referenced thread. > > > > > > Details: http://marc.info/?l=linux-netdev&m=117707735821802&w=2 > > > > Ok,so hopefully the next release by Dave will have the fix. > > Fixed in CVS, will be in the next push to rawhide. > (or grab it from my people.redhat.com page) Your kernel worked like a champ, thanks for the follow up. -- Mike Chambers Madisonville, KY From jamatos at fc.up.pt Tue May 1 19:34:03 2007 From: jamatos at fc.up.pt (=?iso-8859-1?q?Jos=E9_Matos?=) Date: Tue, 1 May 2007 20:34:03 +0100 Subject: Interrupted upgrade from FC6 to F7 T4 In-Reply-To: <4635B49C.5010207@gmail.com> References: <200704292003.07621.jamatos@fc.up.pt> <200704301012.46040.jamatos@fc.up.pt> <4635B49C.5010207@gmail.com> Message-ID: <200705012034.03405.jamatos@fc.up.pt> On Monday 30 April 2007 10:19:24 dragoran wrote: > yes maybe the anaconda developers have some ideas why this might happend > and how to prevent it from happening again. Filled in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238610 -- Jos? Ab?lio From jacliburn at bellsouth.net Tue May 1 19:39:51 2007 From: jacliburn at bellsouth.net (Jay Cliburn) Date: Tue, 01 May 2007 14:39:51 -0500 Subject: [Fwd: Ethernet problem in 2895 kernel] In-Reply-To: <200705011455.12220.sgrubb@redhat.com> References: <1178043035.3935.27.camel@omen.com> <46378C02.6090904@bellsouth.net> <200705011455.12220.sgrubb@redhat.com> Message-ID: <46379787.9060302@bellsouth.net> Steve Grubb wrote: > On Tuesday 01 May 2007 14:50, Jay Cliburn wrote: >> What type cards? You mention your motherboard type below (Asus A8N-E), but >> you indicate the onboard nic (eth1) isn't giving you problems. > > I see the same problem. This is the lspci output: > > 05:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev > 78) > 3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit > Ethernet PCI Express > > I think Chuck traced the text that comes out to 3Com, but its been a while. > AFAICT, the problem started around the 2834 kernel/Feb 15. > > -Steve > > The only seemingly relevant change I see in the 3c59x driver in the February time frame is this one, although the change appears harmless enough: http://lkml.org/lkml/2007/2/1/183 commit 0d38ff1d3d34ca9ae2a61cf98cf47530f9d51dee Author: Jiri Kosina Date: Mon Feb 5 16:29:48 2007 -0800 NET-3c59x: turn local_save_flags() + local_irq_disable() into local_irq_save drivers/net/3c59x.c::poll_vortex() contains local_irq_disable() after local_save_flags(). Turn it into local_irq_save(). Signed-off-by: Jiri Kosina Signed-off-by: Andrew Morton Signed-off-by: Jeff Garzik diff --git a/drivers/net/3c59x.c b/drivers/net/3c59x.c index 80bdcf8..716a472 100644 --- a/drivers/net/3c59x.c +++ b/drivers/net/3c59x.c @@ -792,8 +792,7 @@ static void poll_vortex(struct net_device *dev) { struct vortex_private *vp = netdev_priv(dev); unsigned long flags; - local_save_flags(flags); - local_irq_disable(); + local_irq_save(flags); (vp->full_bus_master_rx ? boomerang_interrupt:vortex_interrupt)(dev->irq local_irq_restore(flags); } You might try reverting it to see if it helps. Jay From drago01 at gmail.com Tue May 1 19:52:24 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 21:52:24 +0200 Subject: ipw3945 on f7t4 In-Reply-To: References: Message-ID: On 5/1/07, Fulko.Hew at sita.aero wrote: > > > > fedora-test-list-bounces at redhat.com wrote on 05/01/2007 02:48:26 PM: > > > The kernel now provides an 'iwlwifi' module which means you don't need > > ipw3945, or ipw3945d. However it's still having some bugs shaken out > > of it, so it's not perfect right now. > > > > I have tested kernel-2.6.21-1.3122.fc7 from your people page (which has > > iwlwifi 0.0.16) and it works much better now. > > wpa works, no oops, keeps the connection, uses the correct rate,scanning > works etc ;) > > the only problem that it has is the handling of the killswitch; which I > > reported upstream a minute ago. > > Assuming this new kernel gets shipped in the not-to-distant future... it should be pushed to rawhide soon... dave? -------------- next part -------------- An HTML attachment was scrubbed... URL: From selinux at gmail.com Tue May 1 20:01:53 2007 From: selinux at gmail.com (Tom London) Date: Tue, 1 May 2007 13:01:53 -0700 Subject: ipw3945 on f7t4 In-Reply-To: References: Message-ID: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> On 5/1/07, dragoran dragoran wrote: > > > On 5/1/07, Fulko.Hew at sita.aero wrote: > > > > > > fedora-test-list-bounces at redhat.com wrote on 05/01/2007 > 02:48:26 PM: > > > > > The kernel now provides an 'iwlwifi' module which means you don't need > > > ipw3945, or ipw3945d. However it's still having some bugs shaken out > > > of it, so it's not perfect right now. > > > > > > I have tested kernel-2.6.21-1.3122.fc7 from your people page (which has > > > iwlwifi 0.0.16) and it works much better now. > > > wpa works, no oops, keeps the connection, uses the correct rate,scanning > > works etc ;) > > > the only problem that it has is the handling of the killswitch; which I > > > reported upstream a minute ago. > > > > Assuming this new kernel gets shipped in the not-to-distant future... > > > it should be pushed to rawhide soon... dave? > Have problems with this kernel/iwlwifi. Attach snippet from /var/log/messages May 1 12:30:10 localhost kernel: May 1 12:30:10 localhost kernel: ============================================= May 1 12:30:10 localhost NetworkManager: eth0: Device is fully-supported using driver 'iwlwifi'. May 1 12:30:11 localhost kernel: [ INFO: possible recursive locking detected ] May 1 12:30:11 localhost NetworkManager: nm_device_init(): waiting for device's worker thread to start May 1 12:30:11 localhost kernel: 2.6.21-1.3123.fc7PAE #1 May 1 12:30:12 localhost NetworkManager: nm_device_init(): device's worker thread started, continuing. May 1 12:30:12 localhost kernel: --------------------------------------------- tom -- Tom London -------------- next part -------------- May 1 12:30:10 localhost kernel: May 1 12:30:10 localhost kernel: ============================================= May 1 12:30:10 localhost NetworkManager: eth0: Device is fully-supported using driver 'iwlwifi'. May 1 12:30:11 localhost kernel: [ INFO: possible recursive locking detected ] May 1 12:30:11 localhost NetworkManager: nm_device_init(): waiting for device's worker thread to start May 1 12:30:11 localhost kernel: 2.6.21-1.3123.fc7PAE #1 May 1 12:30:12 localhost NetworkManager: nm_device_init(): device's worker thread started, continuing. May 1 12:30:12 localhost kernel: --------------------------------------------- May 1 12:30:12 localhost NetworkManager: Now managing wireless (802.11) device 'eth0'. May 1 12:30:12 localhost kernel: NetworkManager/3037 is trying to acquire lock: May 1 12:30:13 localhost NetworkManager: Deactivating device eth0. May 1 12:30:13 localhost kernel: (&dev->_xmit_lock){-+..}, at: [] ieee80211_set_multicast_list+0x46/0x167 [mac80211] May 1 12:30:13 localhost NetworkManager: Will activate wired connection 'eth1' because it now has a link. May 1 12:30:13 localhost kernel: May 1 12:30:14 localhost NetworkManager: SWITCH: no current connection, found better connection 'eth1'. May 1 12:30:14 localhost kernel: but task is already holding lock: May 1 12:30:14 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason May 1 12:30:14 localhost kernel: (&dev->_xmit_lock){-+..}, at: [] dev_mc_upload+0x14/0x3c May 1 12:30:14 localhost NetworkManager: Will activate connection 'eth1'. May 1 12:30:15 localhost kernel: May 1 12:30:15 localhost NetworkManager: Device eth1 activation scheduled... May 1 12:30:15 localhost kernel: other info that might help us debug this: May 1 12:30:15 localhost NetworkManager: Activation (eth1) started... May 1 12:30:15 localhost kernel: 2 locks held by NetworkManager/3037: May 1 12:30:15 localhost NetworkManager: Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... May 1 12:30:15 localhost kernel: #0: (rtnl_mutex){--..}, at: [] mutex_lock+0x21/0x24 May 1 12:30:15 localhost NetworkManager: Activation (eth1) Stage 1 of 5 (Device Prepare) started... May 1 12:30:15 localhost kernel: #1: (&dev->_xmit_lock){-+..}, at: [] dev_mc_upload+0x14/0x3c May 1 12:30:15 localhost NetworkManager: Old device 'eth1' activating, won't change. May 1 12:30:15 localhost kernel: May 1 12:30:15 localhost NetworkManager: Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... May 1 12:30:15 localhost kernel: stack backtrace: May 1 12:30:15 localhost NetworkManager: Activation (eth1) Stage 1 of 5 (Device Prepare) complete. May 1 12:30:15 localhost kernel: [] show_trace_log_lvl+0x1a/0x2f May 1 12:30:15 localhost NetworkManager: Activation (eth1) Stage 2 of 5 (Device Configure) starting... May 1 12:30:15 localhost kernel: [] show_trace+0x12/0x14 May 1 12:30:15 localhost NetworkManager: Activation (eth1) Stage 2 of 5 (Device Configure) successful. May 1 12:30:15 localhost kernel: [] dump_stack+0x16/0x18 May 1 12:30:15 localhost NetworkManager: Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled. May 1 12:30:15 localhost kernel: [] __lock_acquire+0x11f/0xba4 May 1 12:30:15 localhost NetworkManager: Activation (eth1) Stage 2 of 5 (Device Configure) complete. May 1 12:30:15 localhost kernel: [] lock_acquire+0x56/0x6f May 1 12:30:15 localhost NetworkManager: Activation (eth1) Stage 3 of 5 (IP Configure Start) started... May 1 12:30:15 localhost kernel: [] _spin_lock+0x2b/0x38 May 1 12:30:15 localhost kernel: [] ieee80211_set_multicast_list+0x46/0x167 [mac80211] May 1 12:30:15 localhost kernel: [] __dev_mc_upload+0x20/0x22 May 1 12:30:15 localhost kernel: [] dev_mc_upload+0x27/0x3c May 1 12:30:15 localhost kernel: [] dev_open+0x47/0x66 May 1 12:30:15 localhost kernel: [] dev_change_flags+0x51/0xf1 May 1 12:30:15 localhost kernel: [] rtnl_setlink+0x265/0x37d May 1 12:30:15 localhost kernel: [] rtnetlink_rcv_msg+0x1bb/0x1de May 1 12:30:15 localhost kernel: [] netlink_run_queue+0x65/0xd1 May 1 12:30:15 localhost kernel: [] rtnetlink_rcv+0x29/0x42 May 1 12:30:15 localhost kernel: [] netlink_data_ready+0x15/0x56 May 1 12:30:15 localhost kernel: [] netlink_sendskb+0x1f/0x37 May 1 12:30:15 localhost kernel: [] netlink_unicast+0x1ab/0x1c5 May 1 12:30:15 localhost kernel: [] netlink_sendmsg+0x271/0x27d May 1 12:30:15 localhost kernel: [] sock_sendmsg+0xe7/0x104 May 1 12:30:15 localhost kernel: [] sys_sendmsg+0x151/0x1af May 1 12:30:15 localhost kernel: [] sys_socketcall+0x220/0x241 May 1 12:30:15 localhost kernel: [] syscall_call+0x7/0xb May 1 12:30:15 localhost kernel: ======================= May 1 12:30:15 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready From drago01 at gmail.com Tue May 1 20:08:26 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 22:08:26 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> Message-ID: On 5/1/07, Tom London wrote: > > On 5/1/07, dragoran dragoran wrote: > > > > > > On 5/1/07, Fulko.Hew at sita.aero wrote: > > > > > > > > > fedora-test-list-bounces at redhat.com wrote on 05/01/2007 > > 02:48:26 PM: > > > > > > > The kernel now provides an 'iwlwifi' module which means you don't > need > > > > ipw3945, or ipw3945d. However it's still having some bugs shaken > out > > > > of it, so it's not perfect right now. > > > > > > > > I have tested kernel-2.6.21-1.3122.fc7 from your people page (which > has > > > > iwlwifi 0.0.16) and it works much better now. > > > > wpa works, no oops, keeps the connection, uses the correct > rate,scanning > > > works etc ;) > > > > the only problem that it has is the handling of the killswitch; > which I > > > > reported upstream a minute ago. > > > > > > Assuming this new kernel gets shipped in the not-to-distant future... > > > > > > it should be pushed to rawhide soon... dave? > > > Have problems with this kernel/iwlwifi. Attach snippet from > /var/log/messages > May 1 12:30:10 localhost kernel: > May 1 12:30:10 localhost kernel: > ============================================= > May 1 12:30:10 localhost NetworkManager: eth0: Device is > fully-supported using driver 'iwlwifi'. > May 1 12:30:11 localhost kernel: [ INFO: possible recursive locking > detected ] > May 1 12:30:11 localhost NetworkManager: nm_device_init(): > waiting for device's worker thread to start > May 1 12:30:11 localhost kernel: 2.6.21-1.3123.fc7PAE #1 > May 1 12:30:12 localhost NetworkManager: nm_device_init(): > device's worker thread started, continuing. > May 1 12:30:12 localhost kernel: > --------------------------------------------- does it work? ( I also got this lockdep warning) but its not iwlwifi but mac80211 related (its being worked on upstream) -------------- next part -------------- An HTML attachment was scrubbed... URL: From das_deniz at yahoo.com Tue May 1 20:21:24 2007 From: das_deniz at yahoo.com (das) Date: Tue, 1 May 2007 13:21:24 -0700 (PDT) Subject: ipw3945 on f7t4 In-Reply-To: Message-ID: <930879.75468.qm@web33112.mail.mud.yahoo.com> --- dragoran dragoran wrote: > > does it work? ( I also got this lockdep warning) but > its not iwlwifi but > mac80211 related (its being worked on upstream) iwlwifi 3945 does not work for me with this davej's people kernel - kernel-2.6.21-1.3123.fc7.x86_64 Determining IP information for wmaster0...SIOCSIFFLAGS: Operation not supported rebooting into kernel-2.6.21-1.3115.fc7.x86_64 - and there's no "Operation not supported" it just times out and says 'failed' where's the golden kernel-2.6.21-1.3122.fc7.x86_64 ?? thank you __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From drago01 at gmail.com Tue May 1 20:21:53 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 22:21:53 +0200 Subject: F7t4 KDE live CD test report In-Reply-To: <200705012213.45770.gunchev@gmail.com> References: <200705012152.04163.gunchev@gmail.com> <200705012213.45770.gunchev@gmail.com> Message-ID: On 5/1/07, Doncho N. Gunchev wrote: > > On Tuesday 2007-05-01 21:52:04 you wrote: > > I installed F7t4 from the KDE live CD, my hardware profile is: > > ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results: > ... > > Suspend to ram did not work with any kernel. In most cases, when the > ... > I think it has something to do with the new IDE /should I say SCSI ;-)/ > disk > driver. It complains that something is not supported... > > OT: Now, when hdparm -d 0/1 does nothing, how can I switch DMA on/off for > my > DVD-Writer and hard disk? there is no reason to turn it off the new driver should select and set the best dma mode that your drive/chipset supports; if not its a bug. -- > Regards, > Doncho > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From drago01 at gmail.com Tue May 1 20:26:11 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 22:26:11 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <930879.75468.qm@web33112.mail.mud.yahoo.com> References: <930879.75468.qm@web33112.mail.mud.yahoo.com> Message-ID: On 5/1/07, das wrote: > > > --- dragoran dragoran wrote: > > > > > does it work? ( I also got this lockdep warning) but > > its not iwlwifi but > > mac80211 related (its being worked on upstream) > > iwlwifi 3945 does not work for me with this davej's > people kernel - kernel-2.6.21-1.3123.fc7.x86_64 > > Determining IP information for > wmaster0...SIOCSIFFLAGS: Operation not supported you are using the wrong interface ... do not touch wmaster0 use wlan0 rebooting into kernel-2.6.21-1.3115.fc7.x86_64 - and > there's no "Operation not supported" it just times out > and says 'failed' > > where's the golden kernel-2.6.21-1.3122.fc7.x86_64 ?? the only change between 3122 and 3123 is this one: - Set ARCH_KMALLOC_MINALIGN to 8 on PowerPC (#235392) which has nothing to do with iwlwifi..... -------------- next part -------------- An HTML attachment was scrubbed... URL: From das_deniz at yahoo.com Tue May 1 20:41:13 2007 From: das_deniz at yahoo.com (das) Date: Tue, 1 May 2007 13:41:13 -0700 (PDT) Subject: ipw3945 on f7t4 In-Reply-To: Message-ID: <835719.90165.qm@web33115.mail.mud.yahoo.com> --- dragoran dragoran wrote: > On 5/1/07, das wrote: > > --- dragoran dragoran wrote: > > > > > Determining IP information for > > wmaster0...SIOCSIFFLAGS: Operation not supported > > you are using the wrong interface ... do not touch > wmaster0 use wlan0 i didn't add it / touch it. this is a fairly fresh f7t4 install - boot message and that's a new startup failure message - where as the other kernels would just sit at this point and time out and say 'failed' should i use system-config-network and delete wmaster0 ? > > where's the golden kernel-2.6.21-1.3122.fc7.x86_64 > ?? > > > the only change between 3122 and 3123 is this one: - > Set > ARCH_KMALLOC_MINALIGN to 8 on PowerPC (#235392) > which has nothing to do with iwlwifi..... ok - so i got the same recursive lock and kernel bt as reported earlier - and when i started wpa_supplicant and NetworkManager i got several SELinux troubleshooter msgs... set SELinux to permissive and rebooted - no joy. i was never presented with a drop-down of the wireless ssid's in the area. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From drago01 at gmail.com Tue May 1 20:47:00 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 22:47:00 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <835719.90165.qm@web33115.mail.mud.yahoo.com> References: <835719.90165.qm@web33115.mail.mud.yahoo.com> Message-ID: whats the output of /sbin/iwconfig ? (is there any eth1/wlan0 which has wireless related info) -------------- next part -------------- An HTML attachment was scrubbed... URL: From selinux at gmail.com Tue May 1 20:52:47 2007 From: selinux at gmail.com (Tom London) Date: Tue, 1 May 2007 13:52:47 -0700 Subject: ipw3945 on f7t4 In-Reply-To: References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> Message-ID: <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> On 5/1/07, dragoran dragoran wrote: > does it work? ( I also got this lockdep warning) but its not iwlwifi but > mac80211 related (its being worked on upstream) > Appears to associate to WPA access point, but no apparent network 'success'. That is, ifconfig/iwconfig all report appropriate values, but ping hangs, etc. Initially, it appeared that the routing table was not properly updated (remnants from the wired interface), but not sure. tom -- Tom London From drago01 at gmail.com Tue May 1 21:00:30 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 23:00:30 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> Message-ID: On 5/1/07, Tom London wrote: > > On 5/1/07, dragoran dragoran wrote: > > does it work? ( I also got this lockdep warning) but its not iwlwifi but > > mac80211 related (its being worked on upstream) > > > Appears to associate to WPA access point, but no apparent network > 'success'. That is, ifconfig/iwconfig all report appropriate values, > but ping hangs, etc. what do you mean by hangs? does it not find the host or does it lockup the system? are you using static ip or dhcp? Initially, it appeared that the routing table was not properly updated > (remnants from the wired interface), but not sure. have you done ifdown eth0 (if eth0 is your wired interface) to make sure that is is not the problem? tom > -- > Tom London > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From das_deniz at yahoo.com Tue May 1 21:06:28 2007 From: das_deniz at yahoo.com (das) Date: Tue, 1 May 2007 14:06:28 -0700 (PDT) Subject: ipw3945 on f7t4 In-Reply-To: Message-ID: <254232.63757.qm@web33114.mail.mud.yahoo.com> --- dragoran dragoran wrote: > whats the output of /sbin/iwconfig ? (is there any eth1/wlan0 which has > wireless related info) i've seen Tom's hang too - it's the tail end of this bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234618 $iwconfig wmaster0 no wireless extensions. Warning: Driver for device wlan0 has been compiled with version 22 of Wireless Extension, while this program supports up to version 20. Some things may be broken... wlan0 IEEE 802.11a ESSID:"" Mode:Managed Frequency:5.18 GHz Access Point: Not-Associated Retry min limit:7 RTS thr:off Fragment thr=2346 B Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 but what about this: sudo /sbin/iwlist wlan0 scan Warning: Driver for device wlan0 has been compiled with version 22 of Wireless Extension, while this program supports up to version 20. Some things may be broken... wlan0 Scan completed : Cell 01 - Address: 83:42:00:00:00:00 ESSID:"" Segmentation fault __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From gunchev at gmail.com Tue May 1 21:07:54 2007 From: gunchev at gmail.com (Doncho N. Gunchev) Date: Wed, 2 May 2007 00:07:54 +0300 Subject: F7t4 KDE live CD test report In-Reply-To: References: <200705012152.04163.gunchev@gmail.com> <200705012213.45770.gunchev@gmail.com> Message-ID: <200705020007.54998.gunchev@gmail.com> On Tuesday 2007-05-01 23:21:53 dragoran dragoran wrote: > On 5/1/07, Doncho N. Gunchev wrote: > > On Tuesday 2007-05-01 21:52:04 you wrote: > > > I installed F7t4 from the KDE live CD, my hardware profile is: > > > ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results: > > > > ... > > > > > Suspend to ram did not work with any kernel. In most cases, when the > > > > ... > > I think it has something to do with the new IDE /should I say SCSI ;-)/ > > disk > > driver. It complains that something is not supported... > > > > OT: Now, when hdparm -d 0/1 does nothing, how can I switch DMA on/off for > > my > > DVD-Writer and hard disk? > > there is no reason to turn it off the new driver should select and set the > best dma mode that your drive/chipset supports; if not its a bug. > I know it should (remember when these settings got removed from /etc/sysconfig/*?), that's why I asked 'how?'. My DVD-Writer seems to not use any DMA at all (~1MB/sec vs >4MB/sec in FC6). How do I know if it uses "the best mode", if I can't try any other? -- Regards, Doncho From drago01 at gmail.com Tue May 1 21:14:01 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 23:14:01 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <254232.63757.qm@web33114.mail.mud.yahoo.com> References: <254232.63757.qm@web33114.mail.mud.yahoo.com> Message-ID: On 5/1/07, das wrote: > > > --- dragoran dragoran wrote: > > > whats the output of /sbin/iwconfig ? (is there any eth1/wlan0 which has > > wireless related info) > > i've seen Tom's hang too - it's the tail end of this bug: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234618 > > $iwconfig > > wmaster0 no wireless extensions. > > Warning: Driver for device wlan0 has been compiled with version 22 > of Wireless Extension, while this program supports up to version 20. > Some things may be broken... > > wlan0 IEEE 802.11a ESSID:"" > Mode:Managed Frequency:5.18 GHz Access Point: Not-Associated > Retry min limit:7 RTS thr:off Fragment thr=2346 B > Link Quality:0 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > but what about this: > > sudo /sbin/iwlist wlan0 scan > Warning: Driver for device wlan0 has been compiled with version 22 > of Wireless Extension, while this program supports up to version 20. > Some things may be broken... > > wlan0 Scan completed : > Cell 01 - Address: 83:42:00:00:00:00 > ESSID:"" > Segmentation fault ok this one is interesting... I did not get any segfault (I tested on fc6 running the f7 kernel dunno if this is related)... John any idea? __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From drago01 at gmail.com Tue May 1 21:16:37 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 23:16:37 +0200 Subject: F7t4 KDE live CD test report In-Reply-To: <200705020007.54998.gunchev@gmail.com> References: <200705012152.04163.gunchev@gmail.com> <200705012213.45770.gunchev@gmail.com> <200705020007.54998.gunchev@gmail.com> Message-ID: On 5/1/07, Doncho N. Gunchev wrote: > > On Tuesday 2007-05-01 23:21:53 dragoran dragoran wrote: > > On 5/1/07, Doncho N. Gunchev wrote: > > > On Tuesday 2007-05-01 21:52:04 you wrote: > > > > I installed F7t4 from the KDE live CD, my hardware profile is: > > > > ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results: > > > > > > ... > > > > > > > Suspend to ram did not work with any kernel. In most cases, when > the > > > > > > ... > > > I think it has something to do with the new IDE /should I say SCSI > ;-)/ > > > disk > > > driver. It complains that something is not supported... > > > > > > OT: Now, when hdparm -d 0/1 does nothing, how can I switch DMA on/off > for > > > my > > > DVD-Writer and hard disk? > > > > there is no reason to turn it off the new driver should select and set > the > > best dma mode that your drive/chipset supports; if not its a bug. > > > > I know it should (remember when these settings got removed from > /etc/sysconfig/*?), that's why I asked 'how?'. My DVD-Writer seems > to not use any DMA at all (~1MB/sec vs >4MB/sec in FC6). How do > I know if it uses "the best mode", if I can't try any other? its simple a higher dma mode means higher speed. what does hdparm -i /dev/yourdevice show? (both fc6 and f7 output) ? -- > Regards, > Doncho > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From selinux at gmail.com Tue May 1 21:21:23 2007 From: selinux at gmail.com (Tom London) Date: Tue, 1 May 2007 14:21:23 -0700 Subject: ipw3945 on f7t4 In-Reply-To: References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> Message-ID: <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> On 5/1/07, dragoran dragoran wrote: > > > On 5/1/07, Tom London wrote: > > On 5/1/07, dragoran dragoran wrote: > > > does it work? ( I also got this lockdep warning) but its not iwlwifi but > > > mac80211 related (its being worked on upstream) > > > > > Appears to associate to WPA access point, but no apparent network > > 'success'. That is, ifconfig/iwconfig all report appropriate values, > > but ping hangs, etc. > > what do you mean by hangs? does it not find the host or does it lockup the > system? > are you using static ip or dhcp? > > > Initially, it appeared that the routing table was not properly updated > > (remnants from the wired interface), but not sure. > > have you done ifdown eth0 (if eth0 is your wired interface) to make sure > that is is not the problem? > > > tom Ok, rebooted, this time with the RJ-45 unplugged. System booted fine, NetworkManager popped up the 'unlock keyring' dialog right after login. After entering keyring passphrase, NM associated successfully (yea!), 'route' showed a proper routing table, and a 'traceroute' succeeded. However, network immediately 'dis-associated', and would not associate again. Snippet from /var/log/messages: May 1 14:03:28 localhost NetworkManager: Activation (eth0/wireless): access point 'INSIDE' is encrypted, but NO valid key exists. New key needed. May 1 14:03:28 localhost NetworkManager: Activation (eth0) New wireless user key requested for network 'INSIDE'. May 1 14:03:28 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) complete. May 1 14:03:28 localhost NetworkManager: Activation (eth0) New wireless user key for network 'INSIDE' received. May 1 14:03:28 localhost NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... May 1 14:03:28 localhost NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) started... May 1 14:03:28 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... May 1 14:03:28 localhost NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) complete. May 1 14:03:28 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) starting... Where NM just hangs after the last line. tom -- Tom London From selinux at gmail.com Tue May 1 21:24:24 2007 From: selinux at gmail.com (Tom London) Date: Tue, 1 May 2007 14:24:24 -0700 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> Message-ID: <4c4ba1530705011424q6287ba06s5469d10ddf60db7f@mail.gmail.com> On 5/1/07, Tom London wrote: > On 5/1/07, dragoran dragoran wrote: > > > > > > On 5/1/07, Tom London wrote: > > > On 5/1/07, dragoran dragoran wrote: > > > > does it work? ( I also got this lockdep warning) but its not iwlwifi but > > > > mac80211 related (its being worked on upstream) > > > > > > > Appears to associate to WPA access point, but no apparent network > > > 'success'. That is, ifconfig/iwconfig all report appropriate values, > > > but ping hangs, etc. > > > > what do you mean by hangs? does it not find the host or does it lockup the > > system? > > are you using static ip or dhcp? > > > > > Initially, it appeared that the routing table was not properly updated > > > (remnants from the wired interface), but not sure. > > > > have you done ifdown eth0 (if eth0 is your wired interface) to make sure > > that is is not the problem? > > > > > tom > > Ok, rebooted, this time with the RJ-45 unplugged. > > System booted fine, NetworkManager popped up the 'unlock keyring' > dialog right after login. > > After entering keyring passphrase, NM associated successfully (yea!), > 'route' showed a proper routing table, and a 'traceroute' succeeded. > > However, network immediately 'dis-associated', and would not associate again. > > Snippet from /var/log/messages: > May 1 14:03:28 localhost NetworkManager: Activation > (eth0/wireless): access point 'INSIDE' is encrypted, but NO valid key > exists. New key needed. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > New wireless user key requested for network 'INSIDE'. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 2 of 5 (Device Configure) complete. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > New wireless user key for network 'INSIDE' received. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 1 of 5 (Device Prepare) scheduled... > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 1 of 5 (Device Prepare) started... > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 2 of 5 (Device Configure) scheduled... > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 1 of 5 (Device Prepare) complete. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 2 of 5 (Device Configure) starting... > > Where NM just hangs after the last line. > > tom Here is an interesting snippet from a bit earlier in the log: May 1 14:00:25 localhost wpa_supplicant[3573]: Associated with 00:14:69:3b:af:60 May 1 14:00:25 localhost kernel: iwlwifi: REPLY_ADD_STA failed May 1 14:00:25 localhost wpa_supplicant[3573]: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 1 14:00:25 localhost wpa_supplicant[3573]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys May 1 14:00:26 localhost kernel: iwlwifi: REPLY_ADD_STA failed May 1 14:00:26 localhost wpa_supplicant[3573]: Associated with 00:14:69:3b:af:60 May 1 14:00:36 localhost wpa_supplicant[3573]: Authentication with 00:14:69:3b:af:60 timed out. May 1 14:00:36 localhost NetworkManager: request_and_convert_scan_results(): card took too much time scanning. Get a better one. May 1 14:00:36 localhost wpa_supplicant[3573]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys May 1 14:00:44 localhost NetworkManager: eth0: link timed out. May 1 14:00:44 localhost NetworkManager: SWITCH: found better connection 'eth0/INSIDE' than current connection 'eth0/INSIDE'. same_ssid=1, have_link=0 May 1 14:00:44 localhost NetworkManager: Will activate connection 'eth0/INSIDE'. -- Tom London From selinux at gmail.com Tue May 1 21:26:18 2007 From: selinux at gmail.com (Tom London) Date: Tue, 1 May 2007 14:26:18 -0700 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705011424q6287ba06s5469d10ddf60db7f@mail.gmail.com> References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> <4c4ba1530705011424q6287ba06s5469d10ddf60db7f@mail.gmail.com> Message-ID: <4c4ba1530705011426u16f7dabcrc09e80d51fa5f34f@mail.gmail.com> More spewage: May 1 14:00:46 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) complete. May 1 14:00:46 localhost kernel: iwlwifi: check mac addr 1 | 1May 1 14:00:46 localhost kernel: iwlwifi: check basic rate 2 | 1 May 1 14:00:46 localhost kernel: iwlwifi: check assoc id 3 | 1 May 1 14:00:46 localhost kernel: iwlwifi: check CCK and short slot 4 | 1May 1 14:00:46 localhost kernel: iwlwifi: check CCK & auto detect 5 | 1 May 1 14:00:46 localhost kernel: iwlwifi: check TGG 6 | 1 May 1 14:00:46 localhost kernel: iwlwifi: check antenna 7 1May 1 14:00:46 localhost kernel: iwlwifi: Tuning to channel 3 May 1 14:00:46 localhost kernel: iwlwifi: Error not a valid ipw_rxon_assoc_cmd field valuesMay 1 14:00:46 localhost kernel: iwlwifi: Invalid RXON configuration. Not committing. May 1 14:00:50 localhost wpa_supplicant[3709]: Failed to initiate AP scan. May 1 14:01:02 localhost last message repeated 3 times May 1 14:01:06 localhost NetworkManager: Activation (eth0/wireless): association took too long (>20s), failing activation. -- Tom London From drago01 at gmail.com Tue May 1 21:26:43 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 23:26:43 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> Message-ID: On 5/1/07, Tom London wrote: > > On 5/1/07, dragoran dragoran wrote: > > > > > > On 5/1/07, Tom London wrote: > > > On 5/1/07, dragoran dragoran wrote: > > > > does it work? ( I also got this lockdep warning) but its not iwlwifi > but > > > > mac80211 related (its being worked on upstream) > > > > > > > Appears to associate to WPA access point, but no apparent network > > > 'success'. That is, ifconfig/iwconfig all report appropriate values, > > > but ping hangs, etc. > > > > what do you mean by hangs? does it not find the host or does it lockup > the > > system? > > are you using static ip or dhcp? > > > > > Initially, it appeared that the routing table was not properly updated > > > (remnants from the wired interface), but not sure. > > > > have you done ifdown eth0 (if eth0 is your wired interface) to make sure > > that is is not the problem? > > > > > tom > > Ok, rebooted, this time with the RJ-45 unplugged. > > System booted fine, NetworkManager popped up the 'unlock keyring' > dialog right after login. > > After entering keyring passphrase, NM associated successfully (yea!), > 'route' showed a proper routing table, and a 'traceroute' succeeded. > > However, network immediately 'dis-associated', and would not associate > again. > > Snippet from /var/log/messages: > May 1 14:03:28 localhost NetworkManager: Activation > (eth0/wireless): access point 'INSIDE' is encrypted, but NO valid key > exists. New key needed. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > New wireless user key requested for network 'INSIDE'. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 2 of 5 (Device Configure) complete. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > New wireless user key for network 'INSIDE' received. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 1 of 5 (Device Prepare) scheduled... > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 1 of 5 (Device Prepare) started... > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 2 of 5 (Device Configure) scheduled... > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 1 of 5 (Device Prepare) complete. > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > Stage 2 of 5 (Device Configure) starting... > > Where NM just hangs after the last line. have you tryed wpa_supplicant directly? if you need help how to do this feel free to aks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From selinux at gmail.com Tue May 1 21:33:37 2007 From: selinux at gmail.com (Tom London) Date: Tue, 1 May 2007 14:33:37 -0700 Subject: ipw3945 on f7t4 In-Reply-To: References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> Message-ID: <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> On 5/1/07, dragoran dragoran wrote: > > > > On 5/1/07, Tom London wrote: > > On 5/1/07, dragoran dragoran wrote: > > > > > > > > > On 5/1/07, Tom London wrote: > > > > On 5/1/07, dragoran dragoran wrote: > > > > > does it work? ( I also got this lockdep warning) but its not iwlwifi > but > > > > > mac80211 related (its being worked on upstream) > > > > > > > > > Appears to associate to WPA access point, but no apparent network > > > > 'success'. That is, ifconfig/iwconfig all report appropriate values, > > > > but ping hangs, etc. > > > > > > what do you mean by hangs? does it not find the host or does it lockup > the > > > system? > > > are you using static ip or dhcp? > > > > > > > Initially, it appeared that the routing table was not properly updated > > > > (remnants from the wired interface), but not sure. > > > > > > have you done ifdown eth0 (if eth0 is your wired interface) to make sure > > > that is is not the problem? > > > > > > > tom > > > > Ok, rebooted, this time with the RJ-45 unplugged. > > > > System booted fine, NetworkManager popped up the 'unlock keyring' > > dialog right after login. > > > > After entering keyring passphrase, NM associated successfully (yea!), > > 'route' showed a proper routing table, and a 'traceroute' succeeded. > > > > However, network immediately 'dis-associated', and would not associate > again. > > > > Snippet from /var/log/messages: > > May 1 14:03:28 localhost NetworkManager: Activation > > (eth0/wireless): access point 'INSIDE' is encrypted, but NO valid key > > exists. New key needed. > > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > > New wireless user key requested for network 'INSIDE'. > > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > > Stage 2 of 5 (Device Configure) complete. > > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > > New wireless user key for network 'INSIDE' received. > > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > > Stage 1 of 5 (Device Prepare) scheduled... > > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > > Stage 1 of 5 (Device Prepare) started... > > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > > Stage 2 of 5 (Device Configure) scheduled... > > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > > Stage 1 of 5 (Device Prepare) complete. > > May 1 14:03:28 localhost NetworkManager: Activation (eth0) > > Stage 2 of 5 (Device Configure) starting... > > > > Where NM just hangs after the last line. > > > have you tryed wpa_supplicant directly? > if you need help how to do this feel free to aks. > No, and thanks for the offer of help. It would help if you could provide steps for wpa_supplicant. (Sorry, but I've forgotten....). I'll have to shutdown NetworkManager first, right? Anything else? tom -- Tom London From drago01 at gmail.com Tue May 1 21:41:18 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Tue, 1 May 2007 23:41:18 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> Message-ID: On 5/1/07, Tom London wrote: > No, and thanks for the offer of help. > > It would help if you could provide steps for wpa_supplicant. (Sorry, > but I've forgotten....). > > I'll have to shutdown NetworkManager first, right? Anything else? you need a config file call it whatever you want ex: wpa_supplicant.conf ;) mine looks like this: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid="yourssid" proto=WPA key_mgmt=WPA-PSK scan_ssid=1 pairwise=TKIP group=TKIP psk="yourpassword" } then do (as root) /sbin/service NetworkManager stop /usr/sbin/wpa_supplicant -dd -D wext -i wlan0 -c /yoor/configfile.conf open a second terminal (after it has assiotated) and type (as root) dhclient wlan0 after this the network should be up and running -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom.horsley at att.net Tue May 1 21:54:25 2007 From: tom.horsley at att.net (Tom Horsley) Date: Tue, 1 May 2007 17:54:25 -0400 Subject: sd, sd, who's got the sd In-Reply-To: <1178024400.13694.29.camel@aglarond.local> References: <4634C3B7.5050102@redhat.com> <6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com> <1178024400.13694.29.camel@aglarond.local> Message-ID: <20070501175425.3311ea73@zooty> On Tue, 01 May 2007 09:00:00 -0400 Jeremy Katz wrote: > vfat has both a label and a uuid; ntfs at least has a uuid and I would > guess a label as well although libblkid doesn't seem to know about it. > There's no reason not to use them for mounting those filesystem types > either. How about the reason that there are no linux tools available for setting the label on those filesystems? From wwoods at redhat.com Tue May 1 21:56:42 2007 From: wwoods at redhat.com (Will Woods) Date: Tue, 01 May 2007 21:56:42 +0000 Subject: Fedora QA Meeting 1600UTC, Fri. May 4 Message-ID: <1178056602.28491.37.camel@metroid.rdu.redhat.com> Hi, folks! This week I'd like to have the weekly QA meeting at the usual time (1600UTC, noon EDT) in the usual place (#fedora-meeting on freenode), but on Friday instead of Thursday. A quick agenda: - QA team signup If you want to be counted as a member of the QA team, come down and say hi (or send me mail). - Bugzilla future plans I'll have a proposal on the wiki about how we're going to use Bugzilla for F7 and beyond, and we'll go over that briefly. - Kernel bug triage How can we keep the list of kernel bugs shorter and more manageable so davej and friends can get the important stuff fixed without dying of overwork? This Friday is also (as usual) a Bug Day, so if you have bugs that need attention, come by #fedora-qa and we'll see what can be done. -w -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From selinux at gmail.com Tue May 1 21:59:41 2007 From: selinux at gmail.com (Tom London) Date: Tue, 1 May 2007 14:59:41 -0700 Subject: ipw3945 on f7t4 In-Reply-To: References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> Message-ID: <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> On 5/1/07, dragoran dragoran wrote: > > > On 5/1/07, Tom London wrote: > > No, and thanks for the offer of help. > > > > It would help if you could provide steps for wpa_supplicant. (Sorry, > > but I've forgotten....). > > > > I'll have to shutdown NetworkManager first, right? Anything else? > > you need a config file call it whatever you want ex: wpa_supplicant.conf ;) > mine looks like this: > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > > network={ > ssid="yourssid" > proto=WPA > key_mgmt=WPA-PSK > scan_ssid=1 > pairwise=TKIP > group=TKIP > psk="yourpassword" > } > > then do (as root) > /sbin/service NetworkManager stop > /usr/sbin/wpa_supplicant -dd -D wext -i wlan0 -c /yoor/configfile.conf > open a second terminal (after it has assiotated) and type (as root) > dhclient wlan0 > after this the network should be up and running > Thanks. This seems to work much better. In fact, I'm sending this message on a WPA network. Also, the [INFO possible recursive locking detected ] appears gone. Something funny with NM/kernel interaction? Scans during association? tom -- Tom London From dtimms at iinet.net.au Tue May 1 22:04:03 2007 From: dtimms at iinet.net.au (David Timms) Date: Wed, 02 May 2007 08:04:03 +1000 Subject: sd, sd, who's got the sd - f7 work required before release! In-Reply-To: <46360E59.70908@fedoraproject.org> References: <4634C3B7.5050102@redhat.com> <4635E0FB.20700@iinet.net.au> <4635E33D.80501@gmail.com> <4635E51A.5000907@iinet.net.au> <4635E5D4.5040609@fedoraproject.org> <4635E805.9050708@iinet.net.au> <4635EA69.508@fedoraproject.org> <4635FB01.5020009@iinet.net.au> <4635FF4D.4010700@fedoraproject.org> <46360A70.6010707@iinet.net.au> <46360E59.70908@fedoraproject.org> Message-ID: <4637B953.1050200@iinet.net.au> Rahul Sundaram wrote: > David Timms wrote: >> Rahul Sundaram wrote: > >> I couldn't find the T4 version of the release notes to see if stuff is >> already mentioned - only links to fc6 etc. >> >> Can you point them out ? > > T4 is http://fedoraproject.org/wiki/F7Test4/ReleaseNotes but what you > really need is the current and much more updated version at > http://fedoraproject.org/wiki/Docs/Beats Thanks Rahul, based on the info people have provided in this thread, I probably have enough info to make a relnotes page. I'll post back once I have an initial version to proofread / test. Thanks, DaveT. From drago01 at gmail.com Tue May 1 22:04:36 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Wed, 2 May 2007 00:04:36 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> References: <4c4ba1530705011301n5649d616oad7a2ed460d908a0@mail.gmail.com> <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> Message-ID: On 5/1/07, Tom London wrote: > > On 5/1/07, dragoran dragoran wrote: > > > > > > On 5/1/07, Tom London wrote: > > > No, and thanks for the offer of help. > > > > > > It would help if you could provide steps for wpa_supplicant. (Sorry, > > > but I've forgotten....). > > > > > > I'll have to shutdown NetworkManager first, right? Anything else? > > > > you need a config file call it whatever you want ex: > wpa_supplicant.conf ;) > > mine looks like this: > > ctrl_interface=/var/run/wpa_supplicant > > ctrl_interface_group=wheel > > > > network={ > > ssid="yourssid" > > proto=WPA > > key_mgmt=WPA-PSK > > scan_ssid=1 > > pairwise=TKIP > > group=TKIP > > psk="yourpassword" > > } > > > > then do (as root) > > /sbin/service NetworkManager stop > > /usr/sbin/wpa_supplicant -dd -D wext -i wlan0 -c /yoor/configfile.conf > > open a second terminal (after it has assiotated) and type (as root) > > dhclient wlan0 > > after this the network should be up and running > > > Thanks. > > This seems to work much better. In fact, I'm sending this message on a > WPA network. :) Also, the [INFO possible recursive locking detected ] appears gone. for me it always show up when the interface goes on for the first time... but it does not seem to affect anything Something funny with NM/kernel interaction? Scans during association? dunno...seems to be a problem with nm+iwlwifi (have not tryed yet but will do tomorrow) try open a new terminal and do iwlist scan I tryed this and nothing bad happend.(scan during association) tom > -- > Tom London > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From das_deniz at yahoo.com Tue May 1 22:16:18 2007 From: das_deniz at yahoo.com (das) Date: Tue, 1 May 2007 15:16:18 -0700 (PDT) Subject: ipw3945 on f7t4 In-Reply-To: Message-ID: <379779.84201.qm@web33114.mail.mud.yahoo.com> --- dragoran dragoran wrote: > On 5/1/07, Tom London wrote: > > you need a config file call it whatever you want ex: wpa_supplicant.conf ;) > mine looks like this: > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > > network={ > ssid="yourssid" > proto=WPA > key_mgmt=WPA-PSK > scan_ssid=1 > pairwise=TKIP > group=TKIP > psk="yourpassword" > } > > then do (as root) > /sbin/service NetworkManager stop > /usr/sbin/wpa_supplicant -dd -D wext -i wlan0 -c /yoor/configfile.conf > open a second terminal (after it has assiotated) and type (as root) > dhclient wlan0 > after this the network should be up and running *it is indeed!!!* even for me ;) thank you for getting all the extra stuff out of the way. hum, what to write bugs for... i was looking for iwlist pkg owner - so i could go find a debug pkg and get a backtrace. $ rpm -qf /sbin/iwlist wireless-tools-28-2.fc7.i386 wireless-tools-28-2.fc7.x86_64 why are both these archs installed? - humm 314/1352 pkgs are i386 or i686 (3 of which are i686) 104/1352 pkgs are noarch 933/1352 pkgs are x86_64 and the last is gpg-pubkey-1ac70ce6-41bebeef.(none) metacity-devel-2.18.0-2.fc7.i386 - is the only non-duplicate of the i?86 pkgs, for all the others there is a corresponding x86_64 pkg. is this news to anyone that there are so many 'duplicate' i386 pkgs on a x86_64 machine? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From selinux at gmail.com Tue May 1 22:17:05 2007 From: selinux at gmail.com (Tom London) Date: Tue, 1 May 2007 15:17:05 -0700 Subject: ipw3945 on f7t4 In-Reply-To: References: <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> Message-ID: <4c4ba1530705011517h38a7593bg1cdc4027a56c52a7@mail.gmail.com> On 5/1/07, dragoran dragoran wrote: > for me it always show up when the interface goes on for the first time... > but it does not seem to affect anything > > > Something funny with NM/kernel interaction? Scans during association? > dunno...seems to be a problem with nm+iwlwifi (have not tryed yet but will > do tomorrow) > try open a new terminal and do iwlist scan > I tryed this and nothing bad happend.(scan during association) > > > tom Gee, that wasn't very nice ;) That instantly brought down the link. Here are messages from /var/log/messages: May 1 15:06:50 localhost kernel: iwlwifi: REPLY_ADD_STA failed May 1 15:06:54 localhost last message repeated 3 times May 1 15:07:21 localhost kernel: iwlwifi: check mac addr 1 | 1 May 1 15:07:21 localhost kernel: iwlwifi: check basic rate 2 | 1 May 1 15:07:21 localhost kernel: iwlwifi: check assoc id 3 | 1 May 1 15:07:21 localhost kernel: iwlwifi: check CCK and short slot 4 | 1 May 1 15:07:21 localhost kernel: iwlwifi: check CCK & auto detect 5 | 1 May 1 15:07:21 localhost kernel: iwlwifi: check TGG 6 | 1 May 1 15:07:21 localhost kernel: iwlwifi: check antenna 7 1 May 1 15:07:21 localhost kernel: iwlwifi: Tuning to channel 2 May 1 15:07:21 localhost kernel: iwlwifi: Error not a valid ipw_rxon_assoc_cmd field values May 1 15:07:21 localhost kernel: iwlwifi: Invalid RXON configuration. Not committing. May 1 15:07:21 localhost avahi-daemon[2945]: Interface eth0.IPv6 no longer relevant for mDNS. Had to reboot to make the interface be responsive. tom -- Tom London From gunchev at gmail.com Tue May 1 22:24:55 2007 From: gunchev at gmail.com (Doncho N. Gunchev) Date: Wed, 2 May 2007 01:24:55 +0300 Subject: How to turn on/off DMA In-Reply-To: References: <200705012152.04163.gunchev@gmail.com> <200705020007.54998.gunchev@gmail.com> Message-ID: <200705020124.55400.gunchev@gmail.com> On Wednesday 2007-05-02 00:16:37 dragoran dragoran wrote: > On 5/1/07, Doncho N. Gunchev wrote: > > On Tuesday 2007-05-01 23:21:53 dragoran dragoran wrote: > > > On 5/1/07, Doncho N. Gunchev wrote: > > > > On Tuesday 2007-05-01 21:52:04 you wrote: > > > > > I installed F7t4 from the KDE live CD, my hardware profile is: > > > > > ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results: ... > > > > OT: Now, when hdparm -d 0/1 does nothing, how can I switch DMA on/off > > > > for > > > > > > my > > > > DVD-Writer and hard disk? > > > > > > there is no reason to turn it off the new driver should select and set > > > > the > > > > > best dma mode that your drive/chipset supports; if not its a bug. > > > > I know it should (remember when these settings got removed from > > /etc/sysconfig/*?), that's why I asked 'how?'. My DVD-Writer seems > > to not use any DMA at all (~1MB/sec vs >4MB/sec in FC6). How do > > I know if it uses "the best mode", if I can't try any other? > > its simple a higher dma mode means higher speed. > what does hdparm -i /dev/yourdevice show? > (both fc6 and f7 output) ? > What was not clear in my question, I asked how do I do turn DMA on/off with the new kernels, not why I should not do this? Is there a reason to keep this secret? Here's the info for my DVD-Writer, it has DMA off in FC6 and I'm turning it on in rc.local to get it working faster. I also have to 'killall hald-addon-storage' (or more specificly, the one that monitors my DVD) or the machine (laptop) will die in a few hours (does not matter if I have DMA on, off or if I try to play with /usr/share/hal/fdi/policy/10osvendor/*.fdi. Haven't seen it locking for this reason with F7t4 yet. --- Fedora Core 6 --- # hdparm -i /dev/hdb /dev/hdb: Model=TSSTcorpCD/DVDW TS-L632D, FwRev=AC01, SerialNo= Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=0kB, MaxMultSect=0 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 *udma2 AdvancedPM=no * signifies the current active mode # hdparm /dev/hdb /dev/hdb: IO_support = 0 (default 16-bit) unmaskirq = 0 (off) using_dma = 0 (off) keepsettings = 0 (off) readonly = 0 (off) readahead = 256 (on) HDIO_GETGEO failed: Inappropriate ioctl for device *** There is a difference when hdparm /dev/hdb shows DMA on - when I watch DVD movie it works (and the time taken by the kernel while reading the DVD drops down), when off - it skips frames and looses a/v sync. --- Fedora 7 test 4 --- # ll /dev/dvdrw lrwxrwxrwx 1 root root 4 2 ??? 0,56 /dev/dvdrw -> scd0 # hdparm -i /dev/scd0 /dev/scd0: Model=TSSTcorpCD/DVDW TS-L632D , FwRev=AC01 , SerialNo= Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=0kB, MaxMultSect=0 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 *udma2 AdvancedPM=no * signifies the current active mode # hdparm /dev/scd0 /dev/scd0: IO_support = 0 (default 16-bit) readonly = 0 (off) readahead = 256 (on) HDIO_GETGEO failed: Inappropriate ioctl for device -- Regards, Doncho From tibbs at math.uh.edu Tue May 1 23:32:14 2007 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: 01 May 2007 18:32:14 -0500 Subject: f7t4 problems In-Reply-To: References: <777ab80a0705010629n698bfe15gd7f24fed7a0e4701@mail.gmail.com> Message-ID: >>>>> "CH" == Caerie Houchins writes: CH> This is definitely an incompatibility with the new CH> xorg-x11-server-Xorg- 1.3.0.0-3.fc7 and the Intel driver found in CH> the i810 x11 driver rpm. I talked to ajax on IRC and he indicated that he fixed the bug this morning; the fix should show up soon. - J< From jamatos at fc.up.pt Tue May 1 23:39:41 2007 From: jamatos at fc.up.pt (=?iso-8859-1?q?Jos=E9_Matos?=) Date: Wed, 2 May 2007 00:39:41 +0100 Subject: Latest Rawhide kernel doesn't boot In-Reply-To: <20070501165621.GD8189@redhat.com> References: <1177824841.2208.1.camel@scrappy.miketc.com> <1178029840.5722.5.camel@scrappy.miketc.com> <20070501165621.GD8189@redhat.com> Message-ID: <200705020039.42155.jamatos@fc.up.pt> On Tuesday 01 May 2007 17:56:21 Dave Jones wrote: > Fixed in CVS, will be in the next push to rawhide. > (or grab it from my people.redhat.com page) Just to confirm that it works for me now. Thanks, > ????????Dave -- Jos? Ab?lio From dr.diesel at gmail.com Wed May 2 00:10:12 2007 From: dr.diesel at gmail.com (Dr. Diesel) Date: Tue, 1 May 2007 20:10:12 -0400 Subject: virDomainCreateLinux() failed Message-ID: <2a28d2ab0705011710p778dc94bwdca6cf0e80ddcf11@mail.gmail.com> I've been getting this on 2 separate PCs when creating a fully virtulized i686 Windows machines. Found one bug posted for a xen kernel, but perhaps I need to post this one as well? Any ideas? Have the following installed: virt-manager-0.4.0-1.fc7 2.6.21-1.3116.fc7 qemu-0.9.0 (from source and rpm, same result) qkemu-1.3.0pre11(from source) Unable to complete install: 'virDomainCreateLinux() failed internal error End-of-file while reading PTY startup output' Unable to complete install ' virDomainCreateLinux() failed internal error End-of-file while reading PTY startup output Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 677, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 649, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 666, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 480, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed internal error End-of-file while reading PTY startup output ' Thanks Andy From michel.salim at gmail.com Wed May 2 00:31:59 2007 From: michel.salim at gmail.com (Michel Salim) Date: Tue, 1 May 2007 20:31:59 -0400 Subject: Problems with mounting usb-storage partitions? Message-ID: <883cfe6d0705011731t59e5aa7bn457646633e74123b@mail.gmail.com> I have been having these problems intermittently, and have not been able to ascertain the reason: on a computer with a USB mass storage device attached, logging into the desktop does not result in the drive being automounted by gnome-volume-manager. Symptoms: - After boot is complete, logging on to a console and doing 'dmesg | grep sd' does not list the external drives - After power-cycling one of the external drives, now udev picks *all* the external drives up, and creates device nodes for them - HAL (I'm guessing) does not necessarily sees all the drives. I have two drives, one a WDC MyBook external drive that is reliably mounted with FC6, and the other an Addonics drive cage that I use to mount an old laptop hard drive. All the Addonics partitions are mounted by g-v-m (including the Windows NTFS partition, with ntfs-3g), but I have to manually mount the MyBook's single ext3 partition. What gives? The volume label is "My Book", just in case it's the space that's causing the problem. Will bugzilla this, but would love a comment on whether this is a HAL-only bug, udev-only, both, or even mkinitrd (if usb-storage is not in the initrd again) Regards, -- Michel Salim http://hircus.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From anthony.seward at ieee.org Wed May 2 00:49:32 2007 From: anthony.seward at ieee.org (Anthony Joseph Seward) Date: Tue, 01 May 2007 18:49:32 -0600 Subject: F7t4 - intel driver doesn't seem to hot-swap displays In-Reply-To: <46375E9D.20502@bothner.com> References: <4633AD03.4020504@bothner.com> <1177945482.19526.6.camel@localhost.localdomain> <46375E9D.20502@bothner.com> Message-ID: <1178066972.4606.0.camel@fleuret> On Tue, 2007-05-01 at 08:37 -0700, Per Bothner wrote: > Adam Jackson wrote: > > We don't have automatic plug detection quite wired up yet. And we never > > will, for some monitor types, because it would require polling, which is > > usually not a price in battery life that people are willing to pay. > > That makes sense. Having a "detect displays" button like OS X has > works ok too. > > > The new version of the xrandr command line tool should give you enough > > rope to hang yourself here. > > Thanks! With some experimentation and Googling I even managed to get > dual-screen working pretty well. (I had edit the "Virtual" Display size > in xorg.conf, which is clunky.) Perhaps for F8 we'll have a nice > GUI interface for managing multiple displays, but for now this works. > -- Would you mind making your xorg.conf available? Tony > --Per Bothner > per at bothner.com http://per.bothner.com/ > From stickster at gmail.com Wed May 2 00:49:47 2007 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 01 May 2007 20:49:47 -0400 Subject: sd, sd, who's got the sd In-Reply-To: <20070501175425.3311ea73@zooty> References: <4634C3B7.5050102@redhat.com> <6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com> <1178024400.13694.29.camel@aglarond.local> <20070501175425.3311ea73@zooty> Message-ID: <1178066987.5191.16.camel@localhost.localdomain> On Tue, 2007-05-01 at 17:54 -0400, Tom Horsley wrote: > On Tue, 01 May 2007 09:00:00 -0400 > Jeremy Katz wrote: > > > vfat has both a label and a uuid; ntfs at least has a uuid and I would > > guess a label as well although libblkid doesn't seem to know about it. > > There's no reason not to use them for mounting those filesystem types > > either. > > How about the reason that there are no linux tools available for > setting the label on those filesystems? Hm, I have dosfslabel (from dosfstools) and ntfslabel (from ntfsprogs) on this Fedora box. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://fedoraproject.org/wiki/PaulWFrields irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From jmorris at beau.org Wed May 2 02:38:52 2007 From: jmorris at beau.org (John Morris) Date: Tue, 01 May 2007 21:38:52 -0500 Subject: Fedora 7 Test 4 GNOME based i386 Live CD report In-Reply-To: <1177759564.3656.15.camel@localhost.localdomain> References: <46329DC7.9010500@fedoraproject.org> <1177723446.3656.6.camel@localhost.localdomain> <4632B1F4.8060503@redhat.com> <1177759564.3656.15.camel@localhost.localdomain> Message-ID: <1178073532.3436.62.camel@mjolnir> On Sat, 2007-04-28 at 06:26, Matthias Clasen wrote: > > The prime spin still has Firefox, Evolution and three openoffice.org > > applications which makes sense for RHEL but not for Fedora. I would > > prefer something more home user oriented for Fedora. > > Why on earth do you think firefox, evolution and OOo don't make sense > for Fedora users ? The only reason OOo is not on the livecd is space. Seems like as good a time as any for a good rant..... How about Firefox being trademark encumbered and therefore illegal to redistribute without a special license? RedHat has signed such a license so can redistribute their modified version in RHEL; but the Fedora Foundation had damned well better not be signing any such thing while prancing about tossing packages out far less serious deviations from purity. (openmotif for example. I'm not arguing for patented codecs and closed drivers.) Yea, probably a bit late to fix at the 11th hour, but this issue has been brought up before... way before. Sooner or later either Fedora or Moz Corp has to blink, either they rethink their trademark license or Fedora stops claiming to be 100% pure Free Software and deals with the logical fallout from the policy change. http://lwn.net/Articles/118268/ (Way back in Jan 2005) http://lwn.net/Articles/200857/ (Again back in Sept 06) -- John M. http://www.beau.org/~jmorris This post is 100% M$Free! Geekcode 3.1:GCS C+++ UL++++$ P++ L+++ W++ w--- Y++ b++ 5+++ R tv- e* r From jmorris at beau.org Wed May 2 02:46:04 2007 From: jmorris at beau.org (John Morris) Date: Tue, 01 May 2007 21:46:04 -0500 Subject: x86_64 live CD F7T4 In-Reply-To: <4632B484.1070002@fedoraproject.org> References: <000701c7893e$8062ba40$0a01a8c0@jbsys> <4632B484.1070002@fedoraproject.org> Message-ID: <1178073964.3436.70.camel@mjolnir> On Fri, 2007-04-27 at 21:42, Rahul Sundaram wrote: > Why can't it be burned into a DVD? There are other options like Qemu, > Xen, KVM or VMWare if you don't want to use media. Scratch qemu. With -kernel-kqemu it blows up, without it just locks the vm. This was with Qemu 0.90.0 + kqemu 1.3.0pre11. The grub screen is also totally unreadable. Installs fine on real hardware though, only noticed the usual SELinux problems so far. Well that and suspend doesn't work, but that is also expected. Hope to get a chance to try it on another machine or two in the next couple of days. -- John M. http://www.beau.org/~jmorris This post is 100% M$Free! Geekcode 3.1:GCS C+++ UL++++$ P++ L+++ W++ w--- Y++ b++ 5+++ R tv- e* r From kevin at scrye.com Wed May 2 04:58:03 2007 From: kevin at scrye.com (Kevin Fenzi) Date: Tue, 1 May 2007 22:58:03 -0600 Subject: liferea flakes only for me? In-Reply-To: <1178037911.5733.11.camel@lincoln> References: <5021.1178028208@lwn.net> <1178035565.5733.4.camel@lincoln> <20070501182941.c7308dd1.mschwendt.tmp0701.nospam@arcor.de> <1178037911.5733.11.camel@lincoln> Message-ID: <20070501225803.41e8a7b2@ghistelwchlohm.scrye.com> On Tue, 01 May 2007 12:45:11 -0400 bpepple at fedoraproject.org (Brian Pepple) wrote: > On Tue, 2007-05-01 at 18:29 +0200, Michael Schwendt wrote: > > On Tue, 01 May 2007 12:06:05 -0400, Brian Pepple wrote: > > > > > Upstream Liferea has disabled the gtkhtml plugin for x86_64 > > > builds. > > > > :) That would have killed the old plan to split off the mozilla > > plugin into a sub-package. > > Yeah, upstream barely supports x86_64, so I'm actively looking for > x86_64 maintainers that want to co-maintain this package since I don't > have a x86_64 machine. If anyone is interested please contact me. Well, I use liferea on x86_64 and have also been seeing the crashes. Looking at the upstream list I see this thread: http://sourceforge.net/mailarchive/forum.php?thread_name=1177945223.29795.89.camel%40athena.fprintf.net&forum_name=liferea-devel Which basically says that upstream can't reproduce it, so they have no idea on how to fix it. ;( There is a bug in the sf tracker about it: http://sourceforge.net/tracker/index.php?func=detail&aid=1675822&group_id=87005&atid=581684 I have built the latest one here, and am going to try and grab a stack trace. kevin -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From peter at thecodergeek.com Wed May 2 05:49:40 2007 From: peter at thecodergeek.com (Peter Gordon) Date: Tue, 01 May 2007 22:49:40 -0700 Subject: liferea flakes only for me? In-Reply-To: <1178037911.5733.11.camel@lincoln> References: <5021.1178028208@lwn.net> <1178035565.5733.4.camel@lincoln> <20070501182941.c7308dd1.mschwendt.tmp0701.nospam@arcor.de> <1178037911.5733.11.camel@lincoln> Message-ID: <1178084980.8360.16.camel@tuxhugs> On Tue, 2007-05-01 at 12:45 -0400, Brian Pepple wrote: > Yeah, upstream barely supports x86_64, so I'm actively looking for > x86_64 maintainers that want to co-maintain this package since I don't > have a x86_64 machine. If anyone is interested please contact me. I really like Blam, but (as I discovered soon after picking up its maintainership) since it uses pre-built Atom.Net and RSS.Net libraries (whose upstreams are themselves quite inactive, it seems) and doesn't play well with multilib (as well as being a generally misbehaving application), I've recently been giving up on it a lot and using Liferea instead (Rawhide/x86_64 on an Intel Core2 Duo). If you need some testing/debugging help, just tell me what to do :) - though I won't be able to do anything *too* invasive or time-consuming until this semester of class lets out at the end of the month due to procrastination of projects and whatnot. T_T [As an aside - though I'm happy to continuing maintaining it, does anyone actively use/test Blam stuff that would like to comaintain it with me or take it over fully? Alas, version 1.8.4 has a nasty crasher bug that neither myself or upstream has been able to track down and appropriately squish, so that's why the Fedora package is still at 1.8.3 (plus some backported fixes from 1.8.4).] Thanks. -- Peter Gordon (codergeek42) / FSF & EFF Member GnuPG Public Key ID: 0xFFC19479 / Fingerprint: DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479 Blog: http://thecodergeek.com/blog/ About: http://fedoraproject.org/wiki/PeterGordon -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kevin at scrye.com Wed May 2 06:38:31 2007 From: kevin at scrye.com (Kevin Fenzi) Date: Wed, 2 May 2007 00:38:31 -0600 Subject: liferea flakes only for me? In-Reply-To: <20070501225803.41e8a7b2@ghistelwchlohm.scrye.com> References: <5021.1178028208@lwn.net> <1178035565.5733.4.camel@lincoln> <20070501182941.c7308dd1.mschwendt.tmp0701.nospam@arcor.de> <1178037911.5733.11.camel@lincoln> <20070501225803.41e8a7b2@ghistelwchlohm.scrye.com> Message-ID: <20070502003831.55460000@ghistelwchlohm.scrye.com> I was able to get a pretty useless looking trace when it was off into tight loop land here: (gdb) where #0 0x0000003ab82c71c6 in poll () from /lib64/libc.so.6 #1 0x0000003abca2fe7e in g_free () from /lib64/libglib-2.0.so.0 #2 0x0000003abca3033a in g_main_loop_run () from /lib64/libglib-2.0.so.0 #3 0x0000003ac2b2d0d3 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0 #4 0x000000000043ce08 in main (argc=2, argv=0x7fff63f38308) at main.c:286 Dunno if that helps at all. I was going to add it to the sourceforge bug I listed above, but sourceforge isn't allowing me to login right now for some reason. ;( kevin -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From petr.vyhnalek at gmail.com Wed May 2 06:41:24 2007 From: petr.vyhnalek at gmail.com (p v) Date: Wed, 2 May 2007 08:41:24 +0200 Subject: FC7T4 xen 3ware96502LP SE7520BD2 can't boot Message-ID: <85b9aca60705012341h793a0f70pbde6f998175a218b@mail.gmail.com> Dears, I have folloving server: motherboard - SE7520BD2 RAID controller - 3ware96502LP I test FC7T4. Normal kernel kernel-2.6.20-1.3104.fc7 and kernel-2.6.21-1.3116.fc7 boot OK. But installation with XEN kernel-xen-2.6.20-2925.5.fc7 has problems. It does'n completly boot. It locks in different times, when some daemons starting. It doesn't lock in some place|time. But never boot completly. If you want some more information I am prepared to give it to you. If you suggest me to fill bugzilla bug I will do it. Thank you very much for your cooperation. -- Peter From miles.lane at gmail.com Wed May 2 06:53:46 2007 From: miles.lane at gmail.com (Miles Lane) Date: Wed, 2 May 2007 02:53:46 -0400 Subject: F7T4 -- I tried the Nouveau driver from the LiveCD and hit major problems Message-ID: Hi, I have a NVidia NV31 (GeForce FX 5600). I booted the LiveCD, and it correctly configured the nv driver and set the monitor resolution to 1600x1200. Wanting to test Compiz, I opened System->Administration->Display. >From there, I selected Hardware->Configure and selected nouveau from the list. I was told I needed to log out to get the new driver running X. I logged out and then back in. The result was that the Gnome desktop never got displayed. Rather, I got reoccurring errors stating that something was wrong with the "greeter." I'll reproduce and file a bug with the exact wording. Then, when I tried to switch to a VT, I found it was busted. As far as I can tell, nothing was being rendered on the VT. Rather, the video image from GDM kept getting displayed. Each time I hit Enter, the whole image of GDM would rotate to the right and wrap around onto the left side of the screen. Miles From drago01 at gmail.com Wed May 2 07:06:09 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Wed, 2 May 2007 09:06:09 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705011517h38a7593bg1cdc4027a56c52a7@mail.gmail.com> References: <4c4ba1530705011352v2925b46ev487472d10666af5c@mail.gmail.com> <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> <4c4ba1530705011517h38a7593bg1cdc4027a56c52a7@mail.gmail.com> Message-ID: On 5/2/07, Tom London wrote: > > On 5/1/07, dragoran dragoran wrote: > > for me it always show up when the interface goes on for the first > time... > > but it does not seem to affect anything > > > > > Something funny with NM/kernel interaction? Scans during association? > > dunno...seems to be a problem with nm+iwlwifi (have not tryed yet but > will > > do tomorrow) > > try open a new terminal and do iwlist scan > > I tryed this and nothing bad happend.(scan during association) > > > > > tom > > Gee, that wasn't very nice ;) That instantly brought down the link. > Here are messages from /var/log/messages: > > May 1 15:06:50 localhost kernel: iwlwifi: REPLY_ADD_STA failed > May 1 15:06:54 localhost last message repeated 3 times > May 1 15:07:21 localhost kernel: iwlwifi: check mac addr 1 | 1 > May 1 15:07:21 localhost kernel: iwlwifi: check basic rate 2 | 1 > May 1 15:07:21 localhost kernel: iwlwifi: check assoc id 3 | 1 > May 1 15:07:21 localhost kernel: iwlwifi: check CCK and short slot 4 | 1 > May 1 15:07:21 localhost kernel: iwlwifi: check CCK & auto detect 5 | 1 > May 1 15:07:21 localhost kernel: iwlwifi: check TGG 6 | 1 > May 1 15:07:21 localhost kernel: iwlwifi: check antenna 7 1 > May 1 15:07:21 localhost kernel: iwlwifi: Tuning to channel 2 > May 1 15:07:21 localhost kernel: iwlwifi: Error not a valid > ipw_rxon_assoc_cmd field values > May 1 15:07:21 localhost kernel: iwlwifi: Invalid RXON configuration. > Not committing. > May 1 15:07:21 localhost avahi-daemon[2945]: Interface eth0.IPv6 no > longer relevant for mDNS. > > Had to reboot to make the interface be responsive. try adding this to your /etc/modprobe.conf options iwlwifi disable_hw_scan=1 and repeat the test....does it work? tom > -- > Tom London > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From petr.vyhnalek at gmail.com Wed May 2 07:19:52 2007 From: petr.vyhnalek at gmail.com (p v) Date: Wed, 2 May 2007 09:19:52 +0200 Subject: FC7T4 xen 3ware96502LP SE7520BD2 can't boot In-Reply-To: <85b9aca60705012341h793a0f70pbde6f998175a218b@mail.gmail.com> References: <85b9aca60705012341h793a0f70pbde6f998175a218b@mail.gmail.com> Message-ID: <85b9aca60705020019i43d38bf7r360f61f01e8a7ba3@mail.gmail.com> Now I localize more specific, this problem. Problem is with booting to runlevel 6 -X. When I boot to runlevel 3 and then try to startx. Screen change to graphical - grey dots and cursor cross and the computer is locked - switch to text console CTRL+ALT+F1 doesn=t work. Mouse is locked. On 02/05/07, p v wrote: > Dears, > I have folloving server: > motherboard - SE7520BD2 > RAID controller - 3ware96502LP > > I test FC7T4. > > Normal kernel kernel-2.6.20-1.3104.fc7 and kernel-2.6.21-1.3116.fc7 boot OK. > > But installation with XEN kernel-xen-2.6.20-2925.5.fc7 has problems. > It does'n completly boot. It locks in different times, when some > daemons starting. It doesn't lock in some place|time. But never boot > completly. > > If you want some more information I am prepared to give it to you. If > you suggest me to fill bugzilla bug I will do it. > > > Thank you very much for your cooperation. > > -- > > > Peter > -- Peter From drago01 at gmail.com Wed May 2 07:57:06 2007 From: drago01 at gmail.com (dragoran) Date: Wed, 02 May 2007 09:57:06 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <379779.84201.qm@web33114.mail.mud.yahoo.com> References: <379779.84201.qm@web33114.mail.mud.yahoo.com> Message-ID: <46384452.7060504@gmail.com> das wrote: > --- dragoran dragoran wrote: > > >> On 5/1/07, Tom London wrote: >> >> you need a config file call it whatever you want ex: wpa_supplicant.conf ;) >> mine looks like this: >> ctrl_interface=/var/run/wpa_supplicant >> ctrl_interface_group=wheel >> >> network={ >> ssid="yourssid" >> proto=WPA >> key_mgmt=WPA-PSK >> scan_ssid=1 >> pairwise=TKIP >> group=TKIP >> psk="yourpassword" >> } >> >> then do (as root) >> /sbin/service NetworkManager stop >> /usr/sbin/wpa_supplicant -dd -D wext -i wlan0 -c /yoor/configfile.conf >> open a second terminal (after it has assiotated) and type (as root) >> dhclient wlan0 >> after this the network should be up and running >> > > *it is indeed!!!* > > even for me ;) > > thank you for getting all the extra stuff out of the way. hum, what to write bugs for... > > np ;) you can also add -B to wpa_supplicant so that it runs in the background and you don't have to keep the terminal open. > i was looking for iwlist pkg owner - so i could go find a debug pkg and get a backtrace. > > $ rpm -qf /sbin/iwlist > wireless-tools-28-2.fc7.i386 > wireless-tools-28-2.fc7.x86_64 > > this is weird.... I am also running x86_64 but I don't have the i386 one installed. > why are both these archs installed? - humm > > 314/1352 pkgs are i386 or i686 (3 of which are i686) > 104/1352 pkgs are noarch > 933/1352 pkgs are x86_64 > > and the last is gpg-pubkey-1ac70ce6-41bebeef.(none) > > metacity-devel-2.18.0-2.fc7.i386 - is the only non-duplicate of the i?86 pkgs, for all the others > there is a corresponding x86_64 pkg. > > is this news to anyone that there are so many 'duplicate' i386 pkgs on a x86_64 machine? > > > how have you installed the system? fc6 and yum update? fc6 +anaconda update? fresh install? looks like a anaconda/yum bug to me... From drago01 at gmail.com Wed May 2 08:14:47 2007 From: drago01 at gmail.com (dragoran) Date: Wed, 02 May 2007 10:14:47 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <379779.84201.qm@web33114.mail.mud.yahoo.com> References: <379779.84201.qm@web33114.mail.mud.yahoo.com> Message-ID: <46384877.2090400@gmail.com> das wrote: > --- dragoran dragoran wrote: > > >> On 5/1/07, Tom London wrote: >> >> you need a config file call it whatever you want ex: wpa_supplicant.conf ;) >> mine looks like this: >> ctrl_interface=/var/run/wpa_supplicant >> ctrl_interface_group=wheel >> >> network={ >> ssid="yourssid" >> proto=WPA >> key_mgmt=WPA-PSK >> scan_ssid=1 >> pairwise=TKIP >> group=TKIP >> psk="yourpassword" >> } >> >> then do (as root) >> /sbin/service NetworkManager stop >> /usr/sbin/wpa_supplicant -dd -D wext -i wlan0 -c /yoor/configfile.conf >> open a second terminal (after it has assiotated) and type (as root) >> dhclient wlan0 >> after this the network should be up and running >> > > *it is indeed!!!* > > even for me ;) > > thank you for getting all the extra stuff out of the way. hum, what to write bugs for... > > i was looking for iwlist pkg owner - so i could go find a debug pkg and get a backtrace. > > $ rpm -qf /sbin/iwlist > wireless-tools-28-2.fc7.i386 > wireless-tools-28-2.fc7.x86_64 > > why are both these archs installed? - humm > > 314/1352 pkgs are i386 or i686 (3 of which are i686) > 104/1352 pkgs are noarch > 933/1352 pkgs are x86_64 > > and the last is gpg-pubkey-1ac70ce6-41bebeef.(none) > > metacity-devel-2.18.0-2.fc7.i386 - is the only non-duplicate of the i?86 pkgs, for all the others > there is a corresponding x86_64 pkg. > > is this news to anyone that there are so many 'duplicate' i386 pkgs on a x86_64 machine? > > no this is ok; I asked on IRC they are multilib packages so you have a i386 and a x86_64 one (to be able to run i386 software that links against it) does the scanning still fails? (segfault) From drago01 at gmail.com Wed May 2 08:16:38 2007 From: drago01 at gmail.com (dragoran) Date: Wed, 02 May 2007 10:16:38 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <254232.63757.qm@web33114.mail.mud.yahoo.com> References: <254232.63757.qm@web33114.mail.mud.yahoo.com> Message-ID: <463848E6.9030707@gmail.com> das wrote: > --- dragoran dragoran wrote: > > >> whats the output of /sbin/iwconfig ? (is there any eth1/wlan0 which has >> wireless related info) >> > > i've seen Tom's hang too - it's the tail end of this bug: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234618 > > $iwconfig > > wmaster0 no wireless extensions. > > Warning: Driver for device wlan0 has been compiled with version 22 > of Wireless Extension, while this program supports up to version 20. > Some things may be broken... > > wlan0 IEEE 802.11a ESSID:"" > Mode:Managed Frequency:5.18 GHz Access Point: Not-Associated > Retry min limit:7 RTS thr:off Fragment thr=2346 B > Link Quality:0 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > but what about this: > > sudo /sbin/iwlist wlan0 scan > Warning: Driver for device wlan0 has been compiled with version 22 > of Wireless Extension, while this program supports up to version 20. > Some things may be broken... > > wlan0 Scan completed : > Cell 01 - Address: 83:42:00:00:00:00 > ESSID:"" > Segmentation fault > > can you install the debuginfo package and create a backtrace? From amit.rana at gmail.com Wed May 2 08:23:28 2007 From: amit.rana at gmail.com (Amit Rana) Date: Wed, 2 May 2007 13:53:28 +0530 Subject: problem after updating to libvirt-0.2.2-2.fc7 Message-ID: <777ab80a0705020123p4ee11703y21b4f5504eef93be@mail.gmail.com> Another problem after taking latest update, networking stopped working. I did not change any configuration, system started having some strange 169... ip address. I downgraded to libvirt-0.2.2-1.fc7 and all works well now. is it a bug? From amit.rana at gmail.com Wed May 2 08:29:06 2007 From: amit.rana at gmail.com (Amit Rana) Date: Wed, 2 May 2007 13:59:06 +0530 Subject: problem with iwlwifi Message-ID: <777ab80a0705020129t67960e11i3541bee2fa63a39b@mail.gmail.com> Hi, I was finally able to start my wifi, but soon after my first internet request i.e. ping google.com it stopped responding. It did give result for the first ping but there after it didnt work with constant recursive messages in /var/log/messages [amit at localhost ~]$ uname -ar Linux localhost.localdomain 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:36:44 EDT 2007 i686 i686 i386 GNU/Linux http://smolt.fedoraproject.org/show?UUID=22c8710a-e702-4bcb-b002-448a3e53805b messages: May 2 13:46:30 localhost NetworkManager: Updating allowed wireless network lists. May 2 13:46:31 localhost NetworkManager: SWITCH: no current connection, found better connection 'wlan0'. May 2 13:46:31 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason May 2 13:46:32 localhost NetworkManager: Will activate connection 'wlan0/TJNET'. May 2 13:46:32 localhost NetworkManager: Device wlan0 activation scheduled... May 2 13:46:32 localhost NetworkManager: Activation (wlan0) started... May 2 13:46:33 localhost NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... May 2 13:46:33 localhost NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... May 2 13:46:33 localhost NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... May 2 13:46:34 localhost NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. May 2 13:46:35 localhost NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... May 2 13:46:35 localhost NetworkManager: Activation (wlan0/wireless): access point 'TJNET' is encrypted, but NO valid key exists. New key needed. May 2 13:46:35 localhost NetworkManager: Activation (wlan0) New wireless user key requested for network 'TJNET'. May 2 13:46:35 localhost NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. May 2 13:46:36 localhost NetworkManager: Activation (wlan0) New wireless user key for network 'TJNET' received. May 2 13:46:36 localhost NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... May 2 13:46:36 localhost NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... May 2 13:46:36 localhost NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... May 2 13:46:36 localhost NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. May 2 13:46:36 localhost NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... May 2 13:46:36 localhost NetworkManager: Activation (wlan0/wireless): access point 'TJNET' is encrypted, and a key exists. No new key needed. May 2 13:46:36 localhost NetworkManager: SUP: sending command 'INTERFACE_ADD wlan0 wext /var/run/wpa_supplicant ' May 2 13:46:36 localhost yum-updatesd: error getting update info: Cannot open/read repomd.xml file for repository: development May 2 13:46:36 localhost setroubleshoot: [rpc.ERROR] attempt to open server connection failed: (2, 'No such file or directory') May 2 13:46:36 localhost NetworkManager: SUP: response was 'OK' May 2 13:46:36 localhost NetworkManager: SUP: sending command 'AP_SCAN 1' May 2 13:46:36 localhost NetworkManager: SUP: response was 'OK' May 2 13:46:36 localhost NetworkManager: SUP: sending command 'ADD_NETWORK' May 2 13:46:36 localhost NetworkManager: SUP: response was '0' May 2 13:46:36 localhost NetworkManager: SUP: sending command 'SET_NETWORK 0 ssid 544a4e4554' May 2 13:46:36 localhost NetworkManager: SUP: response was 'OK' May 2 13:46:36 localhost NetworkManager: SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' May 2 13:46:36 localhost NetworkManager: SUP: response was 'OK' May 2 13:46:36 localhost NetworkManager: SUP: sending command 'SET_NETWORK 0 wep_key0 ' May 2 13:46:36 localhost NetworkManager: SUP: response was 'OK' May 2 13:46:36 localhost NetworkManager: SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0' May 2 13:46:36 localhost NetworkManager: SUP: response was 'OK' May 2 13:46:37 localhost NetworkManager: SUP: sending command 'ENABLE_NETWORK 0' May 2 13:46:37 localhost NetworkManager: SUP: response was 'OK' May 2 13:46:37 localhost NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. May 2 13:46:37 localhost kernel: iwlwifi: TODO: Look into long/short preamble change handling. May 2 13:46:37 localhost last message repeated 4 times May 2 13:46:38 localhost bonobo-activation-server (amit-3903): Passing command-line arguments in .server files is deprecated: "/usr/bin/tomboy --panel-applet" May 2 13:46:38 localhost wpa_supplicant[4010]: Trying to associate with 00:15:e9:02:ac:38 (SSID='TJNET' freq=2437 MHz) May 2 13:46:38 localhost kernel: hwcrypto disabled! May 2 13:46:38 localhost kernel: iwlwifi: TODO: Look into long/short preamble change handling. May 2 13:46:38 localhost wpa_supplicant[4010]: Associated with 00:15:e9:02:ac:38 May 2 13:46:38 localhost wpa_supplicant[4010]: CTRL-EVENT-CONNECTED - Connection to 00:15:e9:02:ac:38 completed (auth) [id=0 id_str=] May 2 13:46:38 localhost NetworkManager: Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'TJNET'. May 2 13:46:38 localhost kernel: iwlwifi: REPLY_ADD_STA failed May 2 13:46:38 localhost kernel: iwlwifi: Network RSSI: -52 May 2 13:46:38 localhost NetworkManager: Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. May 2 13:46:38 localhost NetworkManager: Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... May 2 13:46:39 localhost NetworkManager: Activation (wlan0) Beginning DHCP transaction. May 2 13:46:39 localhost NetworkManager: Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. May 2 13:46:39 localhost NetworkManager: DHCP daemon state is now 12 (successfully started) for interface wlan0 May 2 13:46:39 localhost dhclient: wmaster0: unknown hardware address type 801 May 2 13:46:39 localhost NetworkManager: DHCP daemon state is now 1 (starting) for interface wlan0 May 2 13:46:39 localhost dhclient: wmaster0: unknown hardware address type 801 May 2 13:46:39 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 May 2 13:46:39 localhost dhclient: DHCPOFFER from 192.168.0.1 May 2 13:46:39 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 May 2 13:46:39 localhost dhclient: DHCPACK from 192.168.0.1 May 2 13:46:39 localhost NetworkManager: DHCP daemon state is now 2 (bound) for interface wlan0 May 2 13:46:39 localhost NetworkManager: Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled... May 2 13:46:39 localhost NetworkManager: Activation (wlan0) Stage 4 of 5 (IP Configure Get) started... May 2 13:46:39 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.host_name May 2 13:46:39 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.domain_name May 2 13:46:39 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain May 2 13:46:39 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers May 2 13:46:39 localhost NetworkManager: Retrieved the following IP4 configuration from the DHCP daemon: May 2 13:46:39 localhost NetworkManager: address 192.168.0.113 May 2 13:46:39 localhost NetworkManager: netmask 255.255.255.0 May 2 13:46:39 localhost NetworkManager: broadcast 192.168.0.255 May 2 13:46:39 localhost NetworkManager: gateway 192.168.0.1 May 2 13:46:39 localhost NetworkManager: nameserver 208.67.222.222 May 2 13:46:39 localhost NetworkManager: nameserver 192.168.0.1 May 2 13:46:39 localhost NetworkManager: Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... May 2 13:46:39 localhost NetworkManager: Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete. May 2 13:46:39 localhost dhclient: bound to 192.168.0.113 -- renewal in 595395 seconds. May 2 13:46:39 localhost NetworkManager: Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... May 2 13:46:39 localhost avahi-daemon[2752]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.113. May 2 13:46:39 localhost avahi-daemon[2752]: New relevant interface wlan0.IPv4 for mDNS. May 2 13:46:39 localhost avahi-daemon[2752]: Registering new address record for 192.168.0.113 on wlan0.IPv4. May 2 13:46:40 localhost NetworkManager: Activation (wlan0) successful, device activated. May 2 13:46:40 localhost NetworkManager: Activation (wlan0) Finish handler scheduled. May 2 13:46:40 localhost NetworkManager: Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. May 2 13:46:53 localhost kernel: iwlwifi: TODO: Look into long/short preamble change handling. May 2 13:46:53 localhost last message repeated 3 times May 2 13:46:55 localhost kernel: BUG: warning at include/asm/dma-mapping.h:25/dma_map_single() (Not tainted) May 2 13:46:55 localhost kernel: [] show_trace_log_lvl+0x1a/0x2f May 2 13:46:55 localhost kernel: [] show_trace+0x12/0x14 May 2 13:46:55 localhost kernel: [] dump_stack+0x16/0x18 May 2 13:46:55 localhost kernel: [] d_tx+0x7f2/0xd69 [iwlwifi] May 2 13:46:55 localhost kernel: [] __ieee80211_tx+0x20/0xec [mac80211] May 2 13:46:55 localhost kernel: [] ieee80211_master_start_xmit+0x410/0x50e [mac80211] May 2 13:46:55 localhost kernel: [] dev_hard_start_xmit+0x1ce/0x22b May 2 13:46:55 localhost kernel: [] __qdisc_run+0xdb/0x195 May 2 13:46:55 localhost kernel: [] net_tx_action+0xc2/0xeb May 2 13:46:55 localhost kernel: [] __do_softirq+0x6f/0xe2 May 2 13:46:55 localhost kernel: [] do_softirq+0x61/0xd0 May 2 13:46:55 localhost kernel: [] local_bh_enable_ip+0xb9/0xdf May 2 13:46:55 localhost kernel: [] _spin_unlock_bh+0x25/0x28 May 2 13:46:55 localhost kernel: [] ieee80211_scan_completed+0xdf/0x109 [mac80211] May 2 13:46:55 localhost kernel: [] ieee80211_sta_scan_work+0x63/0x199 [mac80211] May 2 13:46:55 localhost kernel: [] run_workqueue+0x89/0x14e May 2 13:46:55 localhost kernel: [] worker_thread+0xf8/0x124 May 2 13:46:55 localhost kernel: [] kthread+0xb3/0xdc May 2 13:46:55 localhost kernel: [] kernel_thread_helper+0x7/0x10 May 2 13:46:55 localhost kernel: ======================= May 2 13:46:58 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:46:58 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:46:59 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:46:59 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:46:59 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:00 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:00 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:00 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:01 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:01 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:01 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:01 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:02 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:02 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:02 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:02 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:03 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:03 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:03 localhost kernel: iwlwifi: Error sending RXON_ASSOC: time out after 500ms. May 2 13:47:03 localhost kernel: iwlwifi: Error setting non-tune configuration (-110). May 2 13:47:04 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:04 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:05 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:05 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:05 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:05 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:06 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:06 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:06 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:06 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:07 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:07 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:07 localhost kernel: iwlwifi: Error sending RXON: time out after 500ms. May 2 13:47:07 localhost kernel: iwlwifi: Error clearing ASSOC_MSK on current configuration (-110). May 2 13:47:08 localhost kernel: iwlwifi: Error sending RXON_ASSOC: time out after 500ms. May 2 13:47:08 localhost kernel: iwlwifi: Error setting non-tune configuration (-110). last 30-40 messages starting from May 2 13:46:55 localhost kernel: BUG: warning at include/asm/dma-mapping.h:25/dma_map_single() (Not tainted) kept on repeating. And I cannot use wifi. How do I reset the connection? If I use NM to disable and then enable it never re-enables, I have to restart. any help? From drago01 at gmail.com Wed May 2 08:43:53 2007 From: drago01 at gmail.com (dragoran) Date: Wed, 02 May 2007 10:43:53 +0200 Subject: problem with iwlwifi In-Reply-To: <777ab80a0705020129t67960e11i3541bee2fa63a39b@mail.gmail.com> References: <777ab80a0705020129t67960e11i3541bee2fa63a39b@mail.gmail.com> Message-ID: <46384F49.8000202@gmail.com> Amit Rana wrote: > Hi, > I was finally able to start my wifi, but soon after my first internet > request i.e. ping google.com it stopped responding. It did give result > for the first ping but there after it didnt work with constant > recursive messages in /var/log/messages > > [amit at localhost ~]$ uname -ar > Linux localhost.localdomain 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 > 10:36:44 EDT 2007 i686 i686 i386 GNU/Linux > > http://smolt.fedoraproject.org/show?UUID=22c8710a-e702-4bcb-b002-448a3e53805b > > > messages: > [...] > > last 30-40 messages starting from > May 2 13:46:55 localhost kernel: BUG: warning at > include/asm/dma-mapping.h:25/dma_map_single() (Not tainted) > kept on repeating. > > And I cannot use wifi. > > How do I reset the connection? If I use NM to disable and then enable > it never re-enables, I have to restart. > > any help? > try the kernel from here: http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/ there has been many important fixes in the newer iwlwifi releases (include for the dma problem you are seeing). it works fine for me with nm + wpa and with wpa_supplicant + wpa. From sundaram at fedoraproject.org Wed May 2 09:26:41 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 02 May 2007 14:56:41 +0530 Subject: F7T4 -- I tried the Nouveau driver from the LiveCD and hit major problems In-Reply-To: References: Message-ID: <46385951.3070506@fedoraproject.org> Miles Lane wrote: > Hi, > > I have a NVidia NV31 (GeForce FX 5600). > I booted the LiveCD, and it correctly configured the nv driver > and set the monitor resolution to 1600x1200. > Wanting to test Compiz, I opened System->Administration->Display. >> From there, I selected Hardware->Configure and selected nouveau from >> the list. Nouveau is nowhere near a state that it could run Compiz. More details at http://fedoraproject.org/wiki/Releases/FeatureNouveau Rahul From buildsys at redhat.com Wed May 2 09:31:32 2007 From: buildsys at redhat.com (buildsys at redhat.com) Date: Wed, 2 May 2007 05:31:32 -0400 Subject: rawhide report: 20070502 changes Message-ID: <200705020931.l429VW1v024203@hs20-bc2-6.build.redhat.com> Updated Packages: audit-1.5.3-1.fc7 ----------------- * Tue May 01 2007 Steve Grubb 1.5.3-1 - Change buffer size to prevent truncation of DAEMON events with large labels - Fix memory leaks in auparse (John Dennis) - Update syscall tables for 2.6.21 kernel - Update capp & lspp rules - New python bindings for libauparse (John Dennis) kdebase-6:3.5.6-6.fc7 --------------------- * Mon Apr 23 2007 Than Ngo - 6:3.5.6-6.fc7 - apply patch KDM to support ConsoleKit, thanks to Kevin Kofler and S.??a??lar Onur, #228111 - ktip, kpersonlizer, kpager, kappfinder in kdebase-extras python-virtinst-0.103.0-3.fc7 ----------------------------- * Tue May 01 2007 Daniel P. Berrange - 0.103.0-3.fc7 - Fixed module import when using --accelerate - Fixed detection of RHEL5 client distro - Fixed default 'network's selection & default URI choice to not be Xen specific - Fixed features XML when using initrd for fullvirt rpm-4.4.2-46.fc7 ---------------- * Tue May 01 2007 Paul Nasrat - 4.4.2-46 - Configurable policy for prefered ELF (#235757) * Mon Apr 23 2007 Paul Nasrat - 4.4.2-45 - Fix debugedit for relative paths (#232222) * Mon Apr 16 2007 Paul Nasrat - 4.4.2-44 - Set default verify flags for %doc (#235353) - Revert to old configure line syslinux-3.36-3.fc7 ------------------- * Tue May 01 2007 Jeremy Katz - 3.36-3 - fix countdown on boot images (#229491) system-config-lvm-1.1.1-1.0.fc7 ------------------------------- * Tue May 01 2007 Stanko Kupcevic 1.1.1-1.0 - Update pam file - Update translation files * Mon Jan 22 2007 Stanko Kupcevic 1.0.22-1.0 - Fixed 223518 (s-c-lvm fails to probe CS5 properly) - Resolves: bz223518 * Mon Dec 18 2006 Stanko Kupcevic 1.0.21-1.0 - Fixed 216569 (some messages not localized) - Fixed 218126 (Can't resize ext3 fs online) - Resolves: bz216569, bz218126 xorg-x11-drv-i810-2.0.0-2.fc7 ----------------------------- * Tue May 01 2007 Adam Jackson 2.0.0-2 - Rebuild for final RANDR 1.2 ABI. Fixes segfault at startup. (#238575) * Mon Apr 23 2007 Adam Jackson 2.0.0-1 - xf86-video-intel 2.0.0. Change the version number to match, why not. - Add a Virtual provides for xorg-x11-drv-intel, since we should probably rename this at some point. Broken deps for ia64 ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.ia64 requires mkisofs dvd+rw-tools - 7.0-3.fc7.ia64 requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.ia64 requires mkisofs k3b - 1.0-1.fc7.ia64 requires cdrecord libvirt - 0.2.2-2.fc7.ia64 requires dnsmasq nautilus-cd-burner - 2.18.0-2.fc7.ia64 requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.ia64 requires cdrecord xcdroast - 0.98a15-13.ia64 requires cdrecord >= 0:2.0 xcdroast - 0.98a15-13.ia64 requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.ia64 requires mkisofs >= 0:2.0 Broken deps for ppc64 ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.ppc64 requires mkisofs dvd+rw-tools - 7.0-3.fc7.ppc64 requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.ppc64 requires mkisofs k3b - 1.0-1.fc7.ppc64 requires cdrecord nautilus-cd-burner - 2.18.0-2.fc7.ppc64 requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.ppc64 requires cdrecord xcdroast - 0.98a15-13.ppc64 requires cdrecord >= 0:2.0 xcdroast - 0.98a15-13.ppc64 requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.ppc64 requires mkisofs >= 0:2.0 Broken deps for i386 ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.i386 requires mkisofs dvd+rw-tools - 7.0-3.fc7.i386 requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.i386 requires cdrecord k3b - 1.0-1.fc7.i386 requires mkisofs libvirt - 0.2.2-2.fc7.i386 requires dnsmasq nautilus-cd-burner - 2.18.0-2.fc7.i386 requires cdrecord nautilus-cd-burner - 2.18.0-2.fc7.i386 requires mkisofs xcdroast - 0.98a15-13.i386 requires cdrecord >= 0:2.0 xcdroast - 0.98a15-13.i386 requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.i386 requires mkisofs >= 0:2.0 Broken deps for x86_64 ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.x86_64 requires mkisofs dvd+rw-tools - 7.0-3.fc7.x86_64 requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.x86_64 requires mkisofs k3b - 1.0-1.fc7.x86_64 requires cdrecord k3b - 1.0-1.fc7.i386 requires mkisofs k3b - 1.0-1.fc7.i386 requires cdrecord libvirt - 0.2.2-2.fc7.x86_64 requires dnsmasq libvirt - 0.2.2-2.fc7.i386 requires dnsmasq nautilus-cd-burner - 2.18.0-2.fc7.x86_64 requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.x86_64 requires cdrecord nautilus-cd-burner - 2.18.0-2.fc7.i386 requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.i386 requires cdrecord xcdroast - 0.98a15-13.x86_64 requires cdrecord >= 0:2.0 xcdroast - 0.98a15-13.x86_64 requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.x86_64 requires mkisofs >= 0:2.0 Broken deps for ppc ---------------------------------------------------------- anaconda-runtime - 11.2.0.57-1.ppc requires mkisofs dvd+rw-tools - 7.0-3.fc7.ppc requires mkisofs >= 0:2.0 k3b - 1.0-1.fc7.ppc requires mkisofs k3b - 1.0-1.fc7.ppc requires cdrecord nautilus-cd-burner - 2.18.0-2.fc7.ppc requires mkisofs nautilus-cd-burner - 2.18.0-2.fc7.ppc requires cdrecord xcdroast - 0.98a15-13.ppc requires cdda2wav >= 0:2.0 xcdroast - 0.98a15-13.ppc requires mkisofs >= 0:2.0 xcdroast - 0.98a15-13.ppc requires cdrecord >= 0:2.0 From sundaram at fedoraproject.org Wed May 2 10:04:04 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 02 May 2007 15:34:04 +0530 Subject: Fedora 7 Test 4 GNOME based i386 Live CD report In-Reply-To: <1178073532.3436.62.camel@mjolnir> References: <46329DC7.9010500@fedoraproject.org> <1177723446.3656.6.camel@localhost.localdomain> <4632B1F4.8060503@redhat.com> <1177759564.3656.15.camel@localhost.localdomain> <1178073532.3436.62.camel@mjolnir> Message-ID: <46386214.7070608@fedoraproject.org> John Morris wrote: > Seems like as good a time as any for a good rant..... > > How about Firefox being trademark encumbered and therefore illegal to > redistribute without a special license? RedHat has signed such a > license so can redistribute their modified version in RHEL; but the > Fedora Foundation had damned well better not be signing any such thing > while prancing about tossing packages out far less serious deviations > from purity. (openmotif for example. I'm not arguing for patented > codecs and closed drivers.) Firefox is not illegal to distribute without a special license. That claim is completely wrong. If you modify Firefox and need to retain the name you need permission or you need to distribute it with a different nam which is the very similar to Fedora on the whole. Your comparison between Firefox and Openmotif shows some all too common confusion between trademark and copyright. I would recommend watching http://www.redhat.com/magazine/007may05/features/ip/ Fedora Foundation does not exist btw. See http://fedoraproject.org/wiki/Foundation. Next time you go on ranting it would better to do some basic fact checking first. Rahul From sundaram at fedoraproject.org Wed May 2 10:04:49 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 02 May 2007 15:34:49 +0530 Subject: x86_64 live CD F7T4 In-Reply-To: <1178073964.3436.70.camel@mjolnir> References: <000701c7893e$8062ba40$0a01a8c0@jbsys> <4632B484.1070002@fedoraproject.org> <1178073964.3436.70.camel@mjolnir> Message-ID: <46386241.5060409@fedoraproject.org> John Morris wrote: > On Fri, 2007-04-27 at 21:42, Rahul Sundaram wrote: > >> Why can't it be burned into a DVD? There are other options like Qemu, >> Xen, KVM or VMWare if you don't want to use media. > > Scratch qemu. With -kernel-kqemu it blows up, without it just locks the > vm. This was with Qemu 0.90.0 + kqemu 1.3.0pre11. The grub screen is > also totally unreadable. > > Installs fine on real hardware though, only noticed the usual SELinux > problems so far. Well that and suspend doesn't work, but that is also > expected. Hope to get a chance to try it on another machine or two in > the next couple of days. Do file bug reports for the SELinux and suspend issues. Rahul From petr.vyhnalek at gmail.com Wed May 2 10:34:50 2007 From: petr.vyhnalek at gmail.com (p v) Date: Wed, 2 May 2007 12:34:50 +0200 Subject: FC7T4 xen 3ware96502LP SE7520BD2 can't boot In-Reply-To: <85b9aca60705020019i43d38bf7r360f61f01e8a7ba3@mail.gmail.com> References: <85b9aca60705012341h793a0f70pbde6f998175a218b@mail.gmail.com> <85b9aca60705020019i43d38bf7r360f61f01e8a7ba3@mail.gmail.com> Message-ID: <85b9aca60705020334y1599a6e8y3993da7d867a7561@mail.gmail.com> I have new information. I tried only runlevel 3. And after some time 2-3 hours, there is message: Message from syslogd@ at Wed May 2 12:23:22 2007 ... fc7Dom0 kernel: journal commit I/O error And computer is locked. I think problem is kernel-XEN and/or 3ware driver. Hardware RAID controller and disks are ok. I used this machine with another operating system. what information is relevanted for debugging? On 02/05/07, p v wrote: > Now I localize more specific, this problem. Problem is with booting to > runlevel 6 -X. When I boot to runlevel 3 and then try to startx. > Screen change to graphical - grey dots and cursor cross and the > computer is locked - switch to text console CTRL+ALT+F1 doesn=t work. > Mouse is locked. > > > On 02/05/07, p v wrote: > > Dears, > > I have folloving server: > > motherboard - SE7520BD2 > > RAID controller - 3ware96502LP > > > > I test FC7T4. > > > > Normal kernel kernel-2.6.20-1.3104.fc7 and kernel-2.6.21-1.3116.fc7 boot OK. > > > > But installation with XEN kernel-xen-2.6.20-2925.5.fc7 has problems. > > It does'n completly boot. It locks in different times, when some > > daemons starting. It doesn't lock in some place|time. But never boot > > completly. > > > > If you want some more information I am prepared to give it to you. If > > you suggest me to fill bugzilla bug I will do it. > > > > > > Thank you very much for your cooperation. > > > > -- > > > > > > Peter > > > > > -- > > > Peter > -- Peter From giallu at gmail.com Wed May 2 11:06:03 2007 From: giallu at gmail.com (Gianluca Sforna) Date: Wed, 2 May 2007 13:06:03 +0200 Subject: Wireless ACX on T4 In-Reply-To: <20070429222753.14dacfd6@niobe> References: <20070429222753.14dacfd6@niobe> Message-ID: On 4/29/07, Roger Grosswiler wrote: > I use a D-Link DWL-G650 which has a TI ACX-Chip (100 or 111 no longer > sure). > > Why are the acx-cards not supported out of the box? Firmware-Problem? I think the situation is worse than that: AFAICT the driver was merged in the -mm branch of the kernel, but it did not make the last "jump" into the mainline kernel due to legal problems in the implementation so, If the situation will not be sorted out, chances are the patch will be dropped. Please be sure to keep Texs Instruments informed about how disappointed you are about their non existent open source support See http://article.gmane.org/gmane.linux.drivers.acx100/1173 and http://article.gmane.org/gmane.linux.drivers.acx100/1165 for more details From sundaram at fedoraproject.org Wed May 2 11:19:39 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 02 May 2007 16:49:39 +0530 Subject: FC7T4 Install Failure(SCSI READ ERRORS) In-Reply-To: <1177996524.3488.14.camel@home-desk> References: <1177996524.3488.14.camel@home-desk> Message-ID: <463873CB.40603@fedoraproject.org> Sean Bruno wrote: > Sorry for the late install folks, I know this is T4 and I should have > gotten around to this sooner. It's been a while since I've had some > time to use a test release(I'm not sure where FC7T4 bugs go in bugzilla > even!). > > Not sure why I would get these errors on install, and I'm not quite sure > if they are from my hard drives or my CDROM. I _assume_ that this is a > CDROM drive read failing. I have a Sony DVD Burner, model DRU-800A. > > The system is a dual-opteron running on the ASUS K8N-DL mobo and runs > FC6 x86_64 just fine. > > Using the x86_64 DVD ISO, I attempted to install. The following errors > are the last display on my console after I skip the media check in > anaconda. After selecting skip, I see an error message about anaconda > being terminated. Don't skip it. Make sure that the ISO file you downloaded matches the sha1sum too. Rahul From amit.rana at gmail.com Wed May 2 12:13:18 2007 From: amit.rana at gmail.com (Amit Rana) Date: Wed, 2 May 2007 17:43:18 +0530 Subject: problem with iwlwifi Message-ID: <777ab80a0705020513r4797ef5fs33a31b4026a942f@mail.gmail.com> Hi, I have installed the new kernel but it didnt boot. It kept on hanging at one of the following message alternatively PCI: setting latency timer of device 0000:00:1c.3 to 64 PCI: setting latency timer of device 0000:00:1e.0 to 64 NET: Registered protocol family 2 ---------------------------- TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) TCP reno registered ------------------------- Anyway this is a common problem which I had been facing since start. First installer didnt start, even rescue disk's boot process hangs. I will create a new thread for this problem, will write again later if I am able to boot with the new kernel. Regards, Amit. From das_deniz at yahoo.com Wed May 2 12:19:24 2007 From: das_deniz at yahoo.com (das) Date: Wed, 2 May 2007 05:19:24 -0700 (PDT) Subject: many non-lib dup binary pkgs of i[36]86 on x86_64 [Was: ipw3945 on f7t4] In-Reply-To: <46384877.2090400@gmail.com> Message-ID: <20070502121924.20542.qmail@web33103.mail.mud.yahoo.com> --- dragoran wrote: > das wrote: > > > > > thank you for getting all the extra stuff out of the way. hum, what to write bugs for... > > > > i was looking for iwlist pkg owner - so i could go find a debug pkg and get a backtrace. > > > > $ rpm -qf /sbin/iwlist > > wireless-tools-28-2.fc7.i386 > > wireless-tools-28-2.fc7.x86_64 > > > > why are both these archs installed? - humm > > > > 314/1352 pkgs are i386 or i686 (3 of which are i686) > > 104/1352 pkgs are noarch > > 933/1352 pkgs are x86_64 > > > > and the last is gpg-pubkey-1ac70ce6-41bebeef.(none) > > > > metacity-devel-2.18.0-2.fc7.i386 - is the only non-duplicate of the i?86 pkgs, for all the > others > > there is a corresponding x86_64 pkg. > > > > is this news to anyone that there are so many 'duplicate' i386 pkgs on a x86_64 machine? > > > > > no this is ok; I asked on IRC they are multilib packages so you have a > i386 and a x86_64 one (to be able to run i386 software that links > against it) created a bugzilla bug for this one against anaconda https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238693 das __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From veillard at redhat.com Wed May 2 12:24:53 2007 From: veillard at redhat.com (Daniel Veillard) Date: Wed, 2 May 2007 08:24:53 -0400 Subject: problem after updating to libvirt-0.2.2-2.fc7 In-Reply-To: <777ab80a0705020123p4ee11703y21b4f5504eef93be@mail.gmail.com> References: <777ab80a0705020123p4ee11703y21b4f5504eef93be@mail.gmail.com> Message-ID: <20070502122453.GH30514@redhat.com> On Wed, May 02, 2007 at 01:53:28PM +0530, Amit Rana wrote: > Another problem after taking latest update, networking stopped working. > > I did not change any configuration, system started having some strange > 169... ip address. > > I downgraded to libvirt-0.2.2-1.fc7 and all works well now. > > is it a bug? Do you have dnsmasq installed on that system ? If no please try to install it and report with libvirt-0.2.2-1.fc7, thanks, Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From drago01 at gmail.com Wed May 2 12:25:08 2007 From: drago01 at gmail.com (dragoran) Date: Wed, 02 May 2007 14:25:08 +0200 Subject: problem with iwlwifi In-Reply-To: <777ab80a0705020513r4797ef5fs33a31b4026a942f@mail.gmail.com> References: <777ab80a0705020513r4797ef5fs33a31b4026a942f@mail.gmail.com> Message-ID: <46388324.8050307@gmail.com> Amit Rana wrote: > Hi, > I have installed the new kernel but it didnt boot. It kept on hanging > at one of the following message alternatively > > > PCI: setting latency timer of device 0000:00:1c.3 to 64 > PCI: setting latency timer of device 0000:00:1e.0 to 64 > NET: Registered protocol family 2 > > ---------------------------- > TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) > TCP reno registered > > ------------------------- > > Anyway this is a common problem which I had been facing since start. > First installer didnt start, even rescue disk's boot process hangs. I > will create a new thread for this problem, will write again later if I > am able to boot with the new kernel. > ok, have you also filled a bug? > Regards, > Amit. > From pfps at verizon.net Wed May 2 12:38:01 2007 From: pfps at verizon.net (Peter F. Patel-Schneider) Date: Wed, 02 May 2007 08:38:01 -0400 Subject: iwlwifi in kernel 2.6.21-1.3125 (was Re: F7t4 KDE live CD test report) In-Reply-To: References: <200705012152.04163.gunchev@gmail.com> Message-ID: <46388629.5090607@verizon.net> dragoran dragoran wrote: > > can you try the kernel from here: > http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/ > iwlwifi works fine for me using this (and the previous one) the > version in the livecd does not even connet to my wpa/wpa2 ap. > but no everything seems to work with it, traffic, ping etc. > The iwlwifi in the kernel from davej is much better, but all is not sweetness and light, at least when running Network Manager. I have attached my observations to this message, but they boil down to two things: 1/ Connection strengths don't seem to be correct. 2/ It is impossible to change wifi networks. Peter F. Patel-Schneider -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: iwlwifi URL: From drago01 at gmail.com Wed May 2 12:48:01 2007 From: drago01 at gmail.com (dragoran) Date: Wed, 02 May 2007 14:48:01 +0200 Subject: iwlwifi in kernel 2.6.21-1.3125 (was Re: F7t4 KDE live CD test report) In-Reply-To: <46388629.5090607@verizon.net> References: <200705012152.04163.gunchev@gmail.com> <46388629.5090607@verizon.net> Message-ID: <46388881.8010904@gmail.com> Peter F. Patel-Schneider wrote: > dragoran dragoran wrote: >> >> can you try the kernel from here: >> http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/ >> iwlwifi works fine for me using this (and the previous one) the >> version in the livecd does not even connet to my wpa/wpa2 ap. >> but no everything seems to work with it, traffic, ping etc. >> > > The iwlwifi in the kernel from davej is much better, but all is not > sweetness and light, at least when running Network Manager. I have > attached my observations to this message, but they boil down to two > things: > > 1/ Connection strengths don't seem to be correct. noticed this too: http://marc.info/?l=linux-wireless&m=117809490027074&w=2 > 2/ It is impossible to change wifi networks. > only with nm (have not tested it yet;lack of aps...) or also when you do it by hand (wpa_supplicant or iwconfig for unencrypted aps) ? and please file a bug with the description you wrote From drago01 at gmail.com Wed May 2 12:55:50 2007 From: drago01 at gmail.com (dragoran) Date: Wed, 02 May 2007 14:55:50 +0200 Subject: How to turn on/off DMA In-Reply-To: <200705020124.55400.gunchev@gmail.com> References: <200705012152.04163.gunchev@gmail.com> <200705020007.54998.gunchev@gmail.com> <200705020124.55400.gunchev@gmail.com> Message-ID: <46388A56.70005@gmail.com> Doncho N. Gunchev wrote: > What was not clear in my question, I asked how do I do turn DMA on/off with > the new kernels, not why I should not do this? Is there a reason to keep this > secret? > I don't know the exact reason; but its as simple as "there is no need to" (libata never allowed this; so it was always the case for sata drives) > Here's the info for my DVD-Writer, it has DMA off in FC6 and I'm turning it on > in rc.local to get it working faster. which is a bug, please fill one (kernel)... > I also have to 'killall > hald-addon-storage' (or more specificly, the one that monitors my DVD) or the > machine (laptop) will die in a few hours (does not matter if I have DMA on, > off or if I try to play with /usr/share/hal/fdi/policy/10osvendor/*.fdi. > also a bug fill it against hal > Haven't seen it locking for this reason with F7t4 yet. > --- Fedora Core 6 --- > # hdparm -i /dev/hdb > > /dev/hdb: > > Model=TSSTcorpCD/DVDW TS-L632D, FwRev=AC01, SerialNo= > Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } > RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 > BuffType=unknown, BuffSize=0kB, MaxMultSect=0 > (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 > IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120} > PIO modes: pio0 pio1 pio2 pio3 pio4 > DMA modes: mdma0 mdma1 mdma2 > UDMA modes: udma0 udma1 *udma2 > AdvancedPM=no > > * signifies the current active mode > > # hdparm /dev/hdb > > /dev/hdb: > IO_support = 0 (default 16-bit) > unmaskirq = 0 (off) > using_dma = 0 (off) > keepsettings = 0 (off) > readonly = 0 (off) > readahead = 256 (on) > HDIO_GETGEO failed: Inappropriate ioctl for device > > *** There is a difference when hdparm /dev/hdb shows DMA on - when I watch DVD > movie it works (and the time taken by the kernel while reading the DVD drops > down), when off - it skips frames and looses a/v sync. > I know that there is a difference between dma on and off ;) > --- Fedora 7 test 4 --- > # ll /dev/dvdrw > lrwxrwxrwx 1 root root 4 2 ??? 0,56 /dev/dvdrw -> scd0 > # hdparm -i /dev/scd0 > > /dev/scd0: > > Model=TSSTcorpCD/DVDW TS-L632D , FwRev=AC01 , SerialNo= > Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } > RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 > BuffType=unknown, BuffSize=0kB, MaxMultSect=0 > (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 > IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120} > PIO modes: pio0 pio1 pio2 pio3 pio4 > DMA modes: mdma0 mdma1 mdma2 > UDMA modes: udma0 udma1 *udma2 > AdvancedPM=no > > * signifies the current active mode > > this seems correct (udma33) > # hdparm /dev/scd0 > > /dev/scd0: > IO_support = 0 (default 16-bit) > readonly = 0 (off) > readahead = 256 (on) > HDIO_GETGEO failed: Inappropriate ioctl for device > > ok hdparm seems not to report the dma flag here.... tested on my box and it seems that it does not do it for harddisks either (SATA) but again if the kernel does not enable the dmamode for you _its a bug_ so please file one against kernel (one for fc6 and one for f7) From gunchev at gmail.com Wed May 2 13:27:46 2007 From: gunchev at gmail.com (Doncho N. Gunchev) Date: Wed, 2 May 2007 16:27:46 +0300 Subject: How to turn on/off DMA In-Reply-To: <46388A56.70005@gmail.com> References: <200705012152.04163.gunchev@gmail.com> <200705020124.55400.gunchev@gmail.com> <46388A56.70005@gmail.com> Message-ID: <200705021627.46130.gunchev@gmail.com> On Wednesday 2007-05-02 15:55:50 dragoran wrote: > Doncho N. Gunchev wrote: > > What was not clear in my question, I asked how do I do turn DMA on/off with > > the new kernels, not why I should not do this? Is there a reason to keep this > > secret? > > > I don't know the exact reason; but its as simple as "there is no need > to" (libata never allowed this; so it was always the case for sata drives) Ok, so there's no way... Thanks. From http://freshmeat.net/projects/hdparm/ : """ > is hdparm useful with sata drives, does > it work with sata drives? SATA drives in the 2.6 kernel are handled by the new "libata" SCSI driver. If you add the "ATA passthru" patch (from Jeff Garzik) to your kernel, then hdparm can work with those drives. Some flags, like "-d", are not supported by libata. Currently, ALL SATA hard drives use DMA, so there is no need for -d. But eventually libata will have to implement ATA PIO (for CF cards..), and at that time it may (or not) begin to support the "-d" flag. """ > > Here's the info for my DVD-Writer, it has DMA off in FC6 and I'm turning it on > > in rc.local to get it working faster. > which is a bug, please fill one (kernel)... > > I also have to 'killall > > hald-addon-storage' (or more specificly, the one that monitors my DVD) or the > > machine (laptop) will die in a few hours (does not matter if I have DMA on, > > off or if I try to play with /usr/share/hal/fdi/policy/10osvendor/*.fdi. > > > also a bug fill it against hal > > Haven't seen it locking for this reason with F7t4 yet. > > --- Fedora Core 6 --- > > # hdparm -i /dev/hdb > > > > /dev/hdb: > > > > Model=TSSTcorpCD/DVDW TS-L632D, FwRev=AC01, SerialNo= > > Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } > > RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 > > BuffType=unknown, BuffSize=0kB, MaxMultSect=0 > > (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 > > IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120} > > PIO modes: pio0 pio1 pio2 pio3 pio4 > > DMA modes: mdma0 mdma1 mdma2 > > UDMA modes: udma0 udma1 *udma2 > > AdvancedPM=no > > > > * signifies the current active mode > > > > # hdparm /dev/hdb > > > > /dev/hdb: > > IO_support = 0 (default 16-bit) > > unmaskirq = 0 (off) > > using_dma = 0 (off) > > keepsettings = 0 (off) > > readonly = 0 (off) > > readahead = 256 (on) > > HDIO_GETGEO failed: Inappropriate ioctl for device > > > > *** There is a difference when hdparm /dev/hdb shows DMA on - when I watch DVD > > movie it works (and the time taken by the kernel while reading the DVD drops > > down), when off - it skips frames and looses a/v sync. > > > I know that there is a difference between dma on and off ;) > > --- Fedora 7 test 4 --- > > # ll /dev/dvdrw > > lrwxrwxrwx 1 root root 4 2 ??? 0,56 /dev/dvdrw -> scd0 > > # hdparm -i /dev/scd0 > > > > /dev/scd0: > > > > Model=TSSTcorpCD/DVDW TS-L632D , FwRev=AC01 , SerialNo= > > Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } > > RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 > > BuffType=unknown, BuffSize=0kB, MaxMultSect=0 > > (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 > > IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120} > > PIO modes: pio0 pio1 pio2 pio3 pio4 > > DMA modes: mdma0 mdma1 mdma2 > > UDMA modes: udma0 udma1 *udma2 > > AdvancedPM=no > > > > * signifies the current active mode > > > > > this seems correct (udma33) > > # hdparm /dev/scd0 > > > > /dev/scd0: > > IO_support = 0 (default 16-bit) > > readonly = 0 (off) > > readahead = 256 (on) > > HDIO_GETGEO failed: Inappropriate ioctl for device > > > > > ok hdparm seems not to report the dma flag here.... tested on my box and > it seems that it does not do it for harddisks either (SATA) > but again if the kernel does not enable the dmamode for you _its a bug_ > so please file one against kernel (one for fc6 and one for f7) > Yep, it reports that DMA is used even when it is not. I will fill the bug reports tonight, after work. I didn't fill a bug report for FC6's kernel because there were enough of this type at that time and there was something about changing the way hal pulls data from the CD... Thanks. -- Regards, Doncho From berrange at redhat.com Wed May 2 13:45:37 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 2 May 2007 14:45:37 +0100 Subject: problem after updating to libvirt-0.2.2-2.fc7 In-Reply-To: <777ab80a0705020123p4ee11703y21b4f5504eef93be@mail.gmail.com> References: <777ab80a0705020123p4ee11703y21b4f5504eef93be@mail.gmail.com> Message-ID: <20070502134537.GD9518@redhat.com> On Wed, May 02, 2007 at 01:53:28PM +0530, Amit Rana wrote: > Another problem after taking latest update, networking stopped working. Networking where ? Host or guest ? > I did not change any configuration, system started having some strange > 169... ip address. Please give complete output of 'ifconfig', 'brctl show' and 'route -n' > I downgraded to libvirt-0.2.2-1.fc7 and all works well now. > > is it a bug? The only change between 0.2.2-1 and 0.2.2-2 was the addition of a single line Requires: dnsmasq. This will cause a DCHP & DNS service to be provided on the virbr0 device used by guest VMs. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From selinux at gmail.com Wed May 2 13:52:18 2007 From: selinux at gmail.com (Tom London) Date: Wed, 2 May 2007 06:52:18 -0700 Subject: ipw3945 on f7t4 In-Reply-To: References: <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> <4c4ba1530705011517h38a7593bg1cdc4027a56c52a7@mail.gmail.com> Message-ID: <4c4ba1530705020652t6b150ec3kab2209fab01bf68@mail.gmail.com> On 5/2/07, dragoran dragoran wrote: > try adding this to your /etc/modprobe.conf > options iwlwifi disable_hw_scan=1 > and repeat the test....does it work? > No joy. With this option set, wpa_supplicant never finds the AP and just hangs. Removing the option, wpa_supplicant negotiates again. tom -- Tom London From pfps at verizon.net Wed May 2 13:54:17 2007 From: pfps at verizon.net (Peter F. Patel-Schneider) Date: Wed, 02 May 2007 09:54:17 -0400 Subject: iwlwifi in kernel 2.6.21-1.3125 (was Re: F7t4 KDE live CD test report) In-Reply-To: <46388881.8010904@gmail.com> References: <200705012152.04163.gunchev@gmail.com> <46388629.5090607@verizon.net> <46388881.8010904@gmail.com> Message-ID: <46389809.9050101@verizon.net> > >> 2/ It is impossible to change wifi networks. >> > only with nm (have not tested it yet;lack of aps...) or also when you > do it by hand (wpa_supplicant or iwconfig for unencrypted aps) ? > > and please file a bug with the description you wrote > How would I change networks without nm? peter From jreiser at BitWagon.com Wed May 2 14:42:40 2007 From: jreiser at BitWagon.com (John Reiser) Date: Wed, 02 May 2007 07:42:40 -0700 Subject: Rescue CD fails to initialize network using IPv4 DHCP Message-ID: <4638A360.8060005@BitWagon.com> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238080 For some weeks the Rescue CD-ROM has failed to initialize the network using IPv4 [only] DHCP. Anaconda team has attacked the problem recently, but the rescue CD still fails on my nVidia CK804 eth0. What is needed to get this working properly? -- From ajackson at redhat.com Wed May 2 14:20:41 2007 From: ajackson at redhat.com (Adam Jackson) Date: Wed, 02 May 2007 10:20:41 -0400 Subject: F7T4 -- I tried the Nouveau driver from the LiveCD and hit major problems In-Reply-To: References: Message-ID: <1178115641.19384.14.camel@localhost.localdomain> On Wed, 2007-05-02 at 02:53 -0400, Miles Lane wrote: > Hi, > > I have a NVidia NV31 (GeForce FX 5600). > I booted the LiveCD, and it correctly configured the nv driver > and set the monitor resolution to 1600x1200. > Wanting to test Compiz, I opened System->Administration->Display. > >From there, I selected Hardware->Configure and selected nouveau from the list. > I was told I needed to log out to get the new driver running X. > I logged out and then back in. Compiz (and accelerated 3d in general) is not enabled in the nouveau driver in F7. Shouldn't have logged you out though, that's weird. I'll check, but please do file a bug so it doesn't get lost. - ajax From katzj at redhat.com Wed May 2 15:35:33 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 02 May 2007 11:35:33 -0400 Subject: x86_64 live CD F7T4 In-Reply-To: <1178073964.3436.70.camel@mjolnir> References: <000701c7893e$8062ba40$0a01a8c0@jbsys> <4632B484.1070002@fedoraproject.org> <1178073964.3436.70.camel@mjolnir> Message-ID: <1178120133.23172.1.camel@aglarond.local> On Tue, 2007-05-01 at 21:46 -0500, John Morris wrote: > On Fri, 2007-04-27 at 21:42, Rahul Sundaram wrote: > > Why can't it be burned into a DVD? There are other options like Qemu, > > Xen, KVM or VMWare if you don't want to use media. > > Scratch qemu. With -kernel-kqemu it blows up, without it just locks the > vm. This was with Qemu 0.90.0 + kqemu 1.3.0pre11. The grub screen is > also totally unreadable. Hitting enter will continue; the problem here is a bug in the video BIOS used by qemu/kvm/etc. Jeremy From drago01 at gmail.com Wed May 2 15:39:38 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Wed, 2 May 2007 17:39:38 +0200 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705020652t6b150ec3kab2209fab01bf68@mail.gmail.com> References: <4c4ba1530705011421r542d0b2brc15c335b78d0dee8@mail.gmail.com> <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> <4c4ba1530705011517h38a7593bg1cdc4027a56c52a7@mail.gmail.com> <4c4ba1530705020652t6b150ec3kab2209fab01bf68@mail.gmail.com> Message-ID: On 5/2/07, Tom London wrote: > On 5/2/07, dragoran dragoran wrote: > > try adding this to your /etc/modprobe.conf > > options iwlwifi disable_hw_scan=1 > > and repeat the test....does it work? > > > No joy. With this option set, wpa_supplicant never finds the AP and just > hangs. > > Removing the option, wpa_supplicant negotiates again. > ok replace the option with debug=0x43fff and attach the complete debug output. > tom > -- > Tom London > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > From selinux at gmail.com Wed May 2 16:13:54 2007 From: selinux at gmail.com (Tom London) Date: Wed, 2 May 2007 09:13:54 -0700 Subject: ipw3945 on f7t4 In-Reply-To: References: <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> <4c4ba1530705011517h38a7593bg1cdc4027a56c52a7@mail.gmail.com> <4c4ba1530705020652t6b150ec3kab2209fab01bf68@mail.gmail.com> Message-ID: <4c4ba1530705020913i77510f72hf05507c306d02518@mail.gmail.com> On 5/2/07, dragoran dragoran wrote: > On 5/2/07, Tom London wrote: > > On 5/2/07, dragoran dragoran wrote: > > > try adding this to your /etc/modprobe.conf > > > options iwlwifi disable_hw_scan=1 > > > and repeat the test....does it work? > > > > > No joy. With this option set, wpa_supplicant never finds the AP and just > > hangs. > > > > Removing the option, wpa_supplicant negotiates again. > > > ok replace the option with debug=0x43fff and attach the complete debug output. Just to be precise, you want me to boot without 'disable_hw_scan=1', with 'debug=0x43fff', run wpa_supplicant/dhclient as above, and when associated, run 'iwlist scan'. Right? tom -- Tom London From guido.ledermann at googlemail.com Wed May 2 16:43:48 2007 From: guido.ledermann at googlemail.com (Guido Ledermann) Date: Wed, 02 May 2007 18:43:48 +0200 Subject: Problems with mounting usb-storage partitions? In-Reply-To: <883cfe6d0705011731t59e5aa7bn457646633e74123b@mail.gmail.com> References: <883cfe6d0705011731t59e5aa7bn457646633e74123b@mail.gmail.com> Message-ID: <4638BFC4.4060601@googlemail.com> Michel Salim schrieb: > I have been having these problems intermittently, and have not been able > to ascertain the reason: on a computer with a USB mass storage device > attached, logging into the desktop does not result in the drive being > automounted by gnome-volume-manager. Hi Michael, I think this is the bug that hits me, too. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238385 Guido From selinux at gmail.com Wed May 2 16:49:54 2007 From: selinux at gmail.com (Tom London) Date: Wed, 2 May 2007 09:49:54 -0700 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705020913i77510f72hf05507c306d02518@mail.gmail.com> References: <4c4ba1530705011433t6008bc46v1dc349d8f755d4be@mail.gmail.com> <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> <4c4ba1530705011517h38a7593bg1cdc4027a56c52a7@mail.gmail.com> <4c4ba1530705020652t6b150ec3kab2209fab01bf68@mail.gmail.com> <4c4ba1530705020913i77510f72hf05507c306d02518@mail.gmail.com> Message-ID: <4c4ba1530705020949j4c67fab5v5bfe64b89612c130@mail.gmail.com> On 5/2/07, Tom London wrote: > On 5/2/07, dragoran dragoran wrote: > > On 5/2/07, Tom London wrote: > > > On 5/2/07, dragoran dragoran wrote: > > > > try adding this to your /etc/modprobe.conf > > > > options iwlwifi disable_hw_scan=1 > > > > and repeat the test....does it work? > > > > > > > No joy. With this option set, wpa_supplicant never finds the AP and just > > > hangs. > > > > > > Removing the option, wpa_supplicant negotiates again. > > > > > ok replace the option with debug=0x43fff and attach the complete debug output. > > Just to be precise, you want me to boot without 'disable_hw_scan=1', > with 'debug=0x43fff', run wpa_supplicant/dhclient as above, and when > associated, run 'iwlist scan'. Right? OK. The bad news: I cannot seem to be able to reproduce this failure. (The good news: I cannot seem to be able to reproduce this failure.) As far as I can tell, the only difference is that today I am running on .3125 (yesterday, I was running on .3123), and I have 'debug=0x43fff' set in modprobe.conf. I'll try starting up NetworkManager and see what happens.... tom -- Tom London From gianluca.cecchi at gmail.com Wed May 2 16:59:35 2007 From: gianluca.cecchi at gmail.com (Gianluca Cecchi) Date: Wed, 2 May 2007 18:59:35 +0200 Subject: rawhide users' actions because of core and extra merge? Message-ID: <561c252c0705020959v17fd629bg571b316f1c1e5c68@mail.gmail.com> just to know if anything is to be manually done by rawhide final users or if the yum repos configuration will be done in a sort of automatic way through updates when mirrors become available after the merge. And also if one is now rsyncing rawhide to better simulate daily installations/upgrades, what kind of action is advisable for both not to saturate mirrors and not to destroy local repository.... thanks, gianluca From josh at wavefood.com Wed May 2 17:08:28 2007 From: josh at wavefood.com (Joshua Andrews) Date: Wed, 02 May 2007 10:08:28 -0700 Subject: fc7t4 - problems with ATA66 module In-Reply-To: <20070430092351.GC22205@devserv.devel.redhat.com> References: <4633F953.4010309@wavefood.com> <20070430092351.GC22205@devserv.devel.redhat.com> Message-ID: <4638C58C.3090009@wavefood.com> Alan Cox wrote: > On Sat, Apr 28, 2007 at 06:48:03PM -0700, Joshua Andrews wrote: > >> Apr 28 18:20:05 et kernel: ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 18 >> (level, low) -> IRQ 19 >> Apr 28 18:20:05 et kernel: pata_hpt366 0000:00:13.0: failed to iomap PCI >> BAR 2 >> > > Is this the only PCI BAR it complains about ? > > Can you open a bug, cc me it and attach a dmesg and lspci -vvxxx from a working > FC (eg FC6). I have some ideas I'd like to check > > I installed Dave Jones 2.6.21-1.3125.fc7 kernel and the problem still exists with "kernel: pata_hpt366 0000:00:13.0: failed to iomap PCI BAR 2". There are no other complaints. -J From selinux at gmail.com Wed May 2 17:08:31 2007 From: selinux at gmail.com (Tom London) Date: Wed, 2 May 2007 10:08:31 -0700 Subject: ipw3945 on f7t4 In-Reply-To: <4c4ba1530705020949j4c67fab5v5bfe64b89612c130@mail.gmail.com> References: <4c4ba1530705011459s118691ebueedbb68146cf506a@mail.gmail.com> <4c4ba1530705011517h38a7593bg1cdc4027a56c52a7@mail.gmail.com> <4c4ba1530705020652t6b150ec3kab2209fab01bf68@mail.gmail.com> <4c4ba1530705020913i77510f72hf05507c306d02518@mail.gmail.com> <4c4ba1530705020949j4c67fab5v5bfe64b89612c130@mail.gmail.com> Message-ID: <4c4ba1530705021008x10abb050we845d302b878c2a4@mail.gmail.com> On 5/2/07, Tom London wrote: > On 5/2/07, Tom London wrote: > > On 5/2/07, dragoran dragoran wrote: > > > On 5/2/07, Tom London wrote: > > > > On 5/2/07, dragoran dragoran wrote: > > > > > try adding this to your /etc/modprobe.conf > > > > > options iwlwifi disable_hw_scan=1 > > > > > and repeat the test....does it work? > > > > > > > > > No joy. With this option set, wpa_supplicant never finds the AP and just > > > > hangs. > > > > > > > > Removing the option, wpa_supplicant negotiates again. > > > > > > > ok replace the option with debug=0x43fff and attach the complete debug output. > > > > Just to be precise, you want me to boot without 'disable_hw_scan=1', > > with 'debug=0x43fff', run wpa_supplicant/dhclient as above, and when > > associated, run 'iwlist scan'. Right? > > OK. The bad news: I cannot seem to be able to reproduce this failure. > (The good news: I cannot seem to be able to reproduce this failure.) > > As far as I can tell, the only difference is that today I am running > on .3125 (yesterday, I was running on .3123), and I have > 'debug=0x43fff' set in modprobe.conf. > > I'll try starting up NetworkManager and see what happens.... > Got it to fail with NetworkManager runing. Below is a snippet from /var/log/messages. I attach output from 'dmesg' tom May 2 09:59:06 localhost kernel: printk: 7 messages suppressed. May 2 09:59:41 localhost kernel: printk: 13 messages suppressed. May 2 10:00:23 localhost wpa_supplicant[4154]: Trying to associate with 00:14:69:3b:af:60 (SSID='INSIDE' freq=2422 MHz) May 2 10:00:23 localhost kernel: iwlwifi: REPLY_ADD_STA failed May 2 10:00:23 localhost wpa_supplicant[4154]: Associated with 00:14:69:3b:af:60 May 2 10:00:23 localhost wpa_supplicant[4154]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys May 2 10:00:26 localhost wpa_supplicant[4154]: Trying to associate with 00:14:6a:5b:3a:80 (SSID='INSIDE' freq=2417 MHz) May 2 10:00:26 localhost kernel: iwlwifi: REPLY_ADD_STA failed May 2 10:00:26 localhost wpa_supplicant[4154]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys May 2 10:00:26 localhost wpa_supplicant[4154]: Associated with 00:14:6a:5b:3a:80 May 2 10:00:27 localhost kernel: iwlwifi: REPLY_ADD_STA failed May 2 10:00:27 localhost wpa_supplicant[4154]: Associated with 00:14:6a:5b:3a:80 May 2 10:00:27 localhost wpa_supplicant[4154]: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 2 10:00:27 localhost wpa_supplicant[4154]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys May 2 10:00:28 localhost kernel: iwlwifi: REPLY_ADD_STA failed May 2 10:00:28 localhost wpa_supplicant[4154]: Associated with 00:14:6a:5b:3a:80 May 2 10:00:34 localhost NetworkManager: request_and_convert_scan_results(): card took too much time scanning. Get a better one. May 2 10:00:38 localhost wpa_supplicant[4154]: Authentication with 00:14:6a:5b:3a:80 timed out. May 2 10:00:38 localhost wpa_supplicant[4154]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys May 2 10:00:46 localhost NetworkManager: eth0: link timed out. May 2 10:00:46 localhost NetworkManager: SWITCH: found better connection 'eth0/INSIDE' than current connection 'eth0/INSIDE'. same_ssid=1, have_link=0 -- Tom London -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.txt.gz Type: application/x-gzip Size: 8418 bytes Desc: not available URL: From davej at redhat.com Wed May 2 17:12:11 2007 From: davej at redhat.com (Dave Jones) Date: Wed, 2 May 2007 13:12:11 -0400 Subject: fc7t4 - problems with ATA66 module In-Reply-To: <4638C58C.3090009@wavefood.com> References: <4633F953.4010309@wavefood.com> <20070430092351.GC22205@devserv.devel.redhat.com> <4638C58C.3090009@wavefood.com> Message-ID: <20070502171211.GC9309@redhat.com> On Wed, May 02, 2007 at 10:08:28AM -0700, Joshua Andrews wrote: > Alan Cox wrote: > > On Sat, Apr 28, 2007 at 06:48:03PM -0700, Joshua Andrews wrote: > > > >> Apr 28 18:20:05 et kernel: ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 18 > >> (level, low) -> IRQ 19 > >> Apr 28 18:20:05 et kernel: pata_hpt366 0000:00:13.0: failed to iomap PCI > >> BAR 2 > >> > > > > Is this the only PCI BAR it complains about ? > > > > Can you open a bug, cc me it and attach a dmesg and lspci -vvxxx from a working > > FC (eg FC6). I have some ideas I'd like to check > > > > > I installed Dave Jones 2.6.21-1.3125.fc7 kernel and the problem still > exists with "kernel: pata_hpt366 0000:00:13.0: failed to iomap PCI BAR > 2". There are no other complaints. As soon as the current build system outage has passed, I'll be pushing through a build with some patches Alan sent me, which should fix this. Dave -- http://www.codemonkey.org.uk From guy at incentre.net Wed May 2 17:23:53 2007 From: guy at incentre.net (Guy Fraser) Date: Wed, 02 May 2007 11:23:53 -0600 Subject: fc7t4: still eating babies? In-Reply-To: <4635EEC0.1080304@redhat.com> References: <9f71cef00704290422t2cd06619j7c2e192415ae17fb@mail.gmail.com> <5256d0b0704290539n3c898d67rc9f585bbca576f4a@mail.gmail.com> <46349C5E.10504@freemail.hu> <20070429095456.78ac4a7e@zooty> <4634A95B.4060008@freemail.hu> <4635EEC0.1080304@redhat.com> Message-ID: <1178126633.2866.330.camel@sigurd.incentre.net> On Mon, 2007-04-30 at 15:27 +0200, Benjamin Kosnik wrote: > > It's clearly a case for "Doctor, it hurts when I do this. - Then don't > > do it." > > There's got to be a sane way to add and remove drives in an existing > Fedora install without borking the system. > Maybe the installer could allow you to edit the labels before it formats and installs. > This is the kind of thing that makes linux installs by non-linux people > hard. Fedora is behaving much differently than other oses here. Grub makes me nuts, I must not talk about for fear of Godwins Law. From gerrytool at gmail.com Wed May 2 17:52:55 2007 From: gerrytool at gmail.com (Gerry Tool) Date: Wed, 2 May 2007 12:52:55 -0500 Subject: F7T4 Gimp Acquire menu doesn't show xsane plugin Message-ID: I have xsane working fine with my Epson Perfection 4490 Photo scanner with iscan installed. [gerry at f7t4 ~]$ rpm -qa *xsane* xsane-0.994-3.fc7 xsane-gimp-0.994-3.fc7 I can scan fine with xsane and save the image, but the Gimp Acquire menu doesn't have an option to scan. This worked in F7T3. Any suggestions, or can anyone else confirm or counter this? Thanks. Gerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From das_deniz at yahoo.com Wed May 2 18:00:32 2007 From: das_deniz at yahoo.com (das) Date: Wed, 2 May 2007 11:00:32 -0700 (PDT) Subject: iwlist backtrace [Was: ipw3945 on f7t4] In-Reply-To: <463848E6.9030707@gmail.com> Message-ID: <636761.58063.qm@web33101.mail.mud.yahoo.com> --- dragoran wrote: > das wrote: > > --- dragoran dragoran wrote: > > > > sudo /sbin/iwlist wlan0 scan > > Warning: Driver for device wlan0 has been compiled with version 22 > > of Wireless Extension, while this program supports up to version 20. > > Some things may be broken... > > > > wlan0 Scan completed : > > Cell 01 - Address: 83:42:00:00:00:00 > > ESSID:"" > > Segmentation fault > > > > > can you install the debuginfo package and create a backtrace? > following the write up here: http://fedoraproject.org/wiki/StackTraces this is what i have for a core / backtrace: Core was generated by `/sbin/iwlist wlan0 scan'. Program terminated with signal 11, Segmentation fault. #0 0x0000000000401c9a in print_scanning_info (skfd=3, ifname=0x7fff8956dc87 "wlan0", args=, count=) at iwlist.c:1101 1101 printf(" Mode:%s\n", (gdb) thread apply all bt full Thread 1 (process 3934): #0 0x0000000000401c9a in print_scanning_info (skfd=3, ifname=0x7fff8956dc87 "wlan0", args=, count=) at iwlist.c:1101 key = {0 '\0' , 40 '(', 110 'n', 111 'o', 110 'n', 101 'e', 41 ')', 0 '\0' } wrq = {ifr_ifrn = {ifrn_name = "wlan0\000\000\000\000\000\000\000\000\000\000"}, u = { name = "\020``\000\000\000\000\000\222\002\000\000\000\000\000", essid = {pointer = 0x606010, length = 658, flags = 0}, nwid = {value = 6316048, fixed = 0 '\0', disabled = 0 '\0', flags = 0}, freq = {m = 6316048, e = 0, i = 0 '\0', flags = 0 '\0'}, sens = {value = 6316048, fixed = 0 '\0', disabled = 0 '\0', flags = 0}, bitrate = {value = 6316048, fixed = 0 '\0', disabled = 0 '\0', flags = 0}, txpower = {value = 6316048, fixed = 0 '\0', disabled = 0 '\0', flags = 0}, rts = {value = 6316048, fixed = 0 '\0', disabled = 0 '\0', flags = 0}, frag = {value = 6316048, fixed = 0 '\0', disabled = 0 '\0', flags = 0}, mode = 6316048, retry = {value = 6316048, fixed = 0 '\0', disabled = 0 '\0', flags = 0}, encoding = {pointer = 0x606010, length = 658, flags = 0}, power = {value = 6316048, fixed = 0 '\0', disabled = 0 '\0', flags = 0}, qual = {qual = 16 '\020', level = 96 '`', noise = 96 '`', updated = 0 '\0'}, ap_addr = {sa_family = 24592, sa_data = "`\000\000\000\000\000\222\002\000\000\000\000\000"}, addr = {sa_family = 24592, sa_data = "`\000\000\000\000\000\222\002\000\000\000\000\000"}, param = {value = 6316048, fixed = 0 '\0', disabled = 0 '\0', flags = 0}, data = {pointer = 0x606010, length = 658, flags = 0}}} buffer = (unsigned char *) 0x7fff8956ce40 "" buflen = 4096 range = {throughput = 0, min_nwid = 0, max_nwid = 0, old_num_channels = 0, old_num_frequency = 0 '\0', event_capa = { 103284816, 1024, 0, 0, 0, 0}, sensitivity = 0, max_qual = {qual = 0 '\0', level = 60 '<', noise = 0 '\0', updated = 82 'R'}, avg_qual = {qual = 0 '\0', level = 0 '\0', noise = 0 '\0', updated = 82 'R'}, num_bitrates = 0 '\0', bitrate = { 0 }, min_rts = 0, max_rts = 2347, min_frag = 256, max_frag = 2346, min_pmp = 0, max_pmp = 0, min_pmt = 0, max_pmt = 0, pmp_flags = 0, pmt_flags = 0, pm_capa = 0, encoding_size = {5, 13, 0, 0, 0, 0, 0, 0}, num_encoding_sizes = 2 '\002', max_encoding_tokens = 4 '\004', encoding_login_index = 0 '\0', txpower_capa = 0, num_txpower = 0 '\0', txpower = {0, 0, 0, 0, 0, 0, 0, 0}, we_version_compiled = 22 '\026', we_version_source = 21 '\025', retry_capa = 4096, retry_flags = 4096, r_time_flags = 0, min_retry = 0, max_retry = 255, min_r_time = 0, max_r_time = 0, ---Type to continue, or q to quit--- num_channels = 0, num_frequency = 0 '\0', freq = {{m = 0, e = 0, i = 0 '\0', flags = 0 '\0'} }, enc_capa = 15} has_range = 1 tv = {tv_sec = 0, tv_usec = 0} timeout = 14550000 __FUNCTION__ = "print_scanning_info" #1 0x0000000000402493 in main (argc=, argv=) at iwlist.c:1641 skfd = 3 dev = 0x7fff8956dc87 "wlan0" cmd = 0x7fff8956dc8d "scan" args = (char **) 0x7fff8956d030 count = 0 iwcmd = (const iwlist_cmd *) 0x404fc0 #2 0x000000351001da24 in __libc_start_main () from /lib64/libc.so.6 No symbol table info available. #3 0x00000000004011b9 in _start () No symbol table info available. (gdb) list 1096 freq, channel, event->u.freq.flags); 1097 printf(" %s\n", buffer); 1098 } 1099 break; 1100 case SIOCGIWMODE: 1101 printf(" Mode:%s\n", 1102 iw_operation_mode[event->u.mode]); 1103 break; 1104 case SIOCGIWNAME: 1105 printf(" Protocol:%-1.16s\n", event->u.name); __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From drago01 at gmail.com Wed May 2 18:07:20 2007 From: drago01 at gmail.com (dragoran dragoran) Date: Wed, 2 May 2007 20:07:20 +0200 Subject: iwlist backtrace [Was: ipw3945 on f7t4] In-Reply-To: <636761.58063.qm@web33101.mail.mud.yahoo.com> References: <463848E6.9030707@gmail.com> <636761.58063.qm@web33101.mail.mud.yahoo.com> Message-ID: On 5/2/07, das wrote: > > > --- dragoran wrote: > > > das wrote: > > > --- dragoran dragoran wrote: > > > > > > sudo /sbin/iwlist wlan0 scan > > > Warning: Driver for device wlan0 has been compiled with version 22 > > > of Wireless Extension, while this program supports up to version 20. > > > Some things may be broken... > > > > > > wlan0 Scan completed : > > > Cell 01 - Address: 83:42:00:00:00:00 > > > ESSID:"" > > > Segmentation fault > > > > > > > > can you install the debuginfo package and create a backtrace? > > > > following the write up here: > > http://fedoraproject.org/wiki/StackTraces > > this is what i have for a core / backtrace: [...] can you fill a bug against wireless tools and attach this backtrace ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From das_deniz at yahoo.com Wed May 2 18:38:32 2007 From: das_deniz at yahoo.com (das) Date: Wed, 2 May 2007 11:38:32 -0700 (PDT) Subject: iwlist backtrace [Was: ipw3945 on f7t4] In-Reply-To: Message-ID: <76016.53705.qm@web33111.mail.mud.yahoo.com> --- dragoran dragoran wrote: > On 5/2/07, das wrote: > > > > this is what i have for a core / backtrace: > > > [...] > can you fill a bug against wireless tools and attach this backtrace ? someone has beat me too it. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238657 sorry for the spam. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From caf at omen.com Wed May 2 18:45:24 2007 From: caf at omen.com (Chuck Forsberg WA7KGX N2469R) Date: Wed, 02 May 2007 11:45:24 -0700 Subject: More details on Ethernet unreliability Message-ID: <1178131524.3597.7.camel@omen.com> Here is an lspci showing devices made with a 386 2869 kernel. 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3) 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2) 05:07.0 Ethernet controller: 3Com Corporation 3cSOHO100-TX Hurricane (rev 30) 05:08.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01) This is with the 3com controller on the third from the top PCI slot. I switched to a different Hurricane controller and installed it in the first slot. Still got the time out failure with x86_64 3104 kernel. I have now replaced the Hurricane controller with a gigabit controller. It has not bombed out yet but hasn't had much uptime. In the meantime Comcast has gone erratic so I haven't received any mail today. From alan at redhat.com Wed May 2 19:04:32 2007 From: alan at redhat.com (Alan Cox) Date: Wed, 2 May 2007 15:04:32 -0400 Subject: fc7t4 - problems with ATA66 module In-Reply-To: <4638C58C.3090009@wavefood.com> References: <4633F953.4010309@wavefood.com> <20070430092351.GC22205@devserv.devel.redhat.com> <4638C58C.3090009@wavefood.com> Message-ID: <20070502190432.GA29011@devserv.devel.redhat.com> On Wed, May 02, 2007 at 10:08:28AM -0700, Joshua Andrews wrote: > I installed Dave Jones 2.6.21-1.3125.fc7 kernel and the problem still > exists with "kernel: pata_hpt366 0000:00:13.0: failed to iomap PCI BAR > 2". There are no other complaints. Fix sent upstream From michel.salim at gmail.com Wed May 2 19:22:13 2007 From: michel.salim at gmail.com (Michel Salim) Date: Wed, 2 May 2007 15:22:13 -0400 Subject: Problems with mounting usb-storage partitions? In-Reply-To: <4638BFC4.4060601@googlemail.com> References: <883cfe6d0705011731t59e5aa7bn457646633e74123b@mail.gmail.com> <4638BFC4.4060601@googlemail.com> Message-ID: <883cfe6d0705021222y19c6df15pbd76c8a34af80170@mail.gmail.com> Aha, thanks. plug and pray madness .. 2007/5/2, Guido Ledermann : > > Michel Salim schrieb: > > I have been having these problems intermittently, and have not been able > > to ascertain the reason: on a computer with a USB mass storage device > > attached, logging into the desktop does not result in the drive being > > automounted by gnome-volume-manager. > > Hi Michael, > > I think this is the bug that hits me, too. > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238385 > > Guido > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > -- Michel Salim http://hircus.wordpress.com/ My theology, briefly, is that the universe was dictated but not signed. -- Christopher Morley -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtimms at iinet.net.au Wed May 2 21:35:16 2007 From: dtimms at iinet.net.au (David Timms) Date: Thu, 03 May 2007 07:35:16 +1000 Subject: sd, sd, who's got the sd - rel notes info for upgraders - needs review In-Reply-To: <4637B953.1050200@iinet.net.au> References: <4634C3B7.5050102@redhat.com> <4635E0FB.20700@iinet.net.au> <4635E33D.80501@gmail.com> <4635E51A.5000907@iinet.net.au> <4635E5D4.5040609@fedoraproject.org> <4635E805.9050708@iinet.net.au> <4635EA69.508@fedoraproject.org> <4635FB01.5020009@iinet.net.au> <4635FF4D.4010700@fedoraproject.org> <46360A70.6010707@iinet.net.au> <46360E59.70908@fedoraproject.org> <4637B953.1050200@iinet.net.au> Message-ID: <46390414.4000002@iinet.net.au> David Timms wrote: > Rahul Sundaram wrote: >> David Timms wrote: >>> Rahul Sundaram wrote: >> >>> I couldn't find the T4 version of the release notes to see if stuff >>> is already mentioned - only links to fc6 etc. >>> >>> Can you point them out ? >> >> T4 is http://fedoraproject.org/wiki/F7Test4/ReleaseNotes but what you >> really need is the current and much more updated version at >> http://fedoraproject.org/wiki/Docs/Beats > Thanks Rahul, based on the info people have provided in this thread, I > probably have enough info to make a relnotes page. I'll post back once I > have an initial version to proofread / test. OK, I did an initial version of what I understand existing Fedora users will need to do to be able to upgrade to F7: http://fedoraproject.org/wiki/Docs/Beats/Installer under "Disk partitions must be labeled" Please feel free to test the process to ensure it works for different types of filesystems etc, and update as appropriate. It's deficient: - doesn't mention lvm labelling - since my machines are not happy with trying to mount lvm volumes, it might be too early to be writing up about the limitations. I assume work is ongoing on this: - would it be better to move the content to: ? http://fedoraproject.org/wiki/DistributionUpgrades That would keep the rel notes tidy, but also exclude it :-| DaveT. From dtimms at iinet.net.au Wed May 2 22:38:45 2007 From: dtimms at iinet.net.au (David Timms) Date: Thu, 03 May 2007 08:38:45 +1000 Subject: Laptop not booting under the 2.6.20-1.3036 kernel In-Reply-To: <1175428947.3215.42.camel@T7.Linux> References: <1175428947.3215.42.camel@T7.Linux> Message-ID: <463912F5.3020102@iinet.net.au> Paul wrote: > Hi, > > I've installed and updated my son's laptop using the F7T3 dvd and it > refuses to boot. It gets past grub, starts to load vmlinuz and then > restarts. > > I've tried nopci and noprobe as command line options but it continually > reboots. > > It's an old laptop - Compaq Presario 1246, but it should be able to > handle things. > > The HD was installed originally on my laptop (x86) and transferred over > - I've done this plenty of times in the past. If I put the drive back in > my laptop, it boots fine. Have you had any success yet ? If not, at the grub prompt, can you adjust the grub boot line to not include rhgb and quiet. You might be able to catch the last message before the reboot. A capture to serial console might be the easiest way to get the messages. DaveT. From tom.horsley at att.net Wed May 2 22:39:52 2007 From: tom.horsley at att.net (Tom Horsley) Date: Wed, 2 May 2007 18:39:52 -0400 Subject: sd, sd, who's got the sd - rel notes info for upgraders - needs review In-Reply-To: <46390414.4000002@iinet.net.au> References: <4634C3B7.5050102@redhat.com> <4635E0FB.20700@iinet.net.au> <4635E33D.80501@gmail.com> <4635E51A.5000907@iinet.net.au> <4635E5D4.5040609@fedoraproject.org> <4635E805.9050708@iinet.net.au> <4635EA69.508@fedoraproject.org> <4635FB01.5020009@iinet.net.au> <4635FF4D.4010700@fedoraproject.org> <46360A70.6010707@iinet.net.au> <46360E59.70908@fedoraproject.org> <4637B953.1050200@iinet.net.au> <46390414.4000002@iinet.net.au> Message-ID: <20070502183952.1c4752a2@zooty> On Thu, 03 May 2007 07:35:16 +1000 David Timms wrote: > OK, I did an initial version of what I understand existing Fedora users > will need to do to be able to upgrade to F7: > http://fedoraproject.org/wiki/Docs/Beats/Installer > under "Disk partitions must be labeled" Couple of additions: The LABEL= syntax is also used in the grub.conf file, so you need to change it as well as the fstab to get all the places that need to know about labels. There are also swap partitions and reiserfs partitions. Anyone know how to change the labels on them? (One suggestion was just to recreate swap from scratch using the -L option, but I still have no idea about reiser). Would sure be nice if there were a general purpose label tool that checked the partition type and knew how to do the right thing for that partition. From stymar at alcatel-lucent.com Wed May 2 23:28:41 2007 From: stymar at alcatel-lucent.com (Styma, Robert E (Robert)) Date: Wed, 2 May 2007 18:28:41 -0500 Subject: sd, sd, who's got the sd In-Reply-To: <1178066987.5191.16.camel@localhost.localdomain> References: <4634C3B7.5050102@redhat.com><6280325c0705010551i6cf0a6e8p85e5a6d2167f9b5d@mail.gmail.com><1178024400.13694.29.camel@aglarond.local><20070501175425.3311ea73@zooty> <1178066987.5191.16.camel@localhost.localdomain> Message-ID: > > Hm, I have dosfslabel (from dosfstools) and ntfslabel (from ntfsprogs) > on this Fedora box. > OK, Let me see if I have this straight. 1. The preferred technique is to have each partition use a label and use the labels in /etc/fstab. 2. You can set the labels on most things during install. For currently unlabled partitions, you can use: e2label [