nvidia/nouveau problems
I got a new Sandy Bridge i7 laptop with nvidia/optimus graphics. I managed to install the new KDE beta, after a few problems. However, there seems to be some issues with nouvaeu trying to start up: One issue is errors messages and slowness starting up: First I get this console message: mkdir: cannot create directory `/run': File exists Then I get these errors from nouveau: Pointer to BIT loadval table invalid i2c wr fail: -6 PGRAPH: unsupported chipset, please reported Then it hangs for a long time (many minutes), before I finally bet a KDE login screen. After KDE starts up, things mostly work, but some fan is going continuously, even when the system is idle. Perhaps the GPU fan? My preference would be to just use integrated graphics, and completely disable the nvidia graphics. Unfortunately, there doesn't seem to be a way to do that from the BIOS, at least not the visible BIOS control settings. Googling hasn't found any good suggests so far. I've tried blacklist nouveau in both blacklist.conf and in blacklist-nouvaeu.conf. I also added rdblacklist=nouveau to the kernel line in grub.conf. One suggestion I've seen is to prm -e the nouveau driver. -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
some issues with 15 Beta RC2 Live Desktop CD
Adam Williamson awilliam at redhat.com writes: Did you (fileabug, I mean)? I've seen a couple other people report this, it looks like an issue we should definitely track: if you filedabug, can you give the URL? Thanks. Sorry, just noticed this message. Just filed it since I saw the same issue with the latest GNOME3 test day image and didn't see an existing bug. https://bugzilla.redhat.com/show_bug.cgi?id=698184 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
Per Bothner wrote: I got a new Sandy Bridge i7 laptop with nvidia/optimus graphics. I managed to install the new KDE beta, after a few problems. However, there seems to be some issues with nouvaeu trying to start up: One issue is errors messages and slowness starting up: [snip] My preference would be to just use integrated graphics, and completely disable the nvidia graphics. Unfortunately, there doesn't seem to be a way to do that from the BIOS, at least not the visible BIOS control settings. There is not an option in the BIOS because laptop manufacturers think you're going to use the operating system that was pre-installed. Optimus is not supported in any shape or form by nouvaeu or the NVIDIA proprietary driver. In other words, you're screwed until someone reverse engineers it or NVIDIA supports it. Search for linux optimus to find dozens of other frustrated users. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
On Wed, Apr 20, 2011 at 11:14, Per Bothner p...@bothner.com wrote: I did try hard to get a laptop with just integrated graphics, but they're very hard to find, especially once you get to mid/upper-end with i7 quad-core Sandy Bridge. Most of them have nvidia/optimus. A few have ATI, which would of course be my strong preference, but there are very few choices, especially if you want to avoid a glossy screen. All of the ThinkPad line can meet these requirements and work out-of-the box with no proprietary bits. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
I followed the instructions here: http://linux-hybrid-graphics.blogspot.com/2010/07/using-acpicall-module-to-switch-onoff.html And they seemed to have worked - the laptop get now blessedly quiet, and the indicator light switched to indicate the integrated graphics. (The fan noise did come back after a bit, though.) The main issue now is the slow/flakey bootup, hanging for multiple minutes. Plus it hangs trying to shutdown. Hopefully that can be fixed. -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
On 04/20/2011 10:00 AM, Jason D. Clinton wrote: On Wed, Apr 20, 2011 at 11:14, Per Bothner p...@bothner.com mailto:p...@bothner.com wrote: I did try hard to get a laptop with just integrated graphics, but they're very hard to find, especially once you get to mid/upper-end with i7 quad-core Sandy Bridge. Most of them have nvidia/optimus. A few have ATI, which would of course be my strong preference, but there are very few choices, especially if you want to avoid a glossy screen. All of the ThinkPad line can meet these requirements and work out-of-the box with no proprietary bits. Yes, if you limit yourself to i7-2620M. If you want Lenovo T420 or T520 with i7-2720QM (or even just a i7-2630QM) you have to get nvidia/optimus, unless there is some option I haven't found. The W520 appears to be only available with nvidia. And so it goes. Trust me, I've done a lot of research and agonizing. -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
On Wed, Apr 20, 2011 at 12:00:19PM -0500, Jason D. Clinton wrote: On Wed, Apr 20, 2011 at 11:14, Per Bothner p...@bothner.com wrote: I did try hard to get a laptop with just integrated graphics, but they're very hard to find, especially once you get to mid/upper-end with i7 quad-core Sandy Bridge. Most of them have nvidia/optimus. A few have ATI, which would of course be my strong preference, but there are very few choices, especially if you want to avoid a glossy screen. All of the ThinkPad line can meet these requirements and work out-of-the box with no proprietary bits. A word of caution about the Thinkpad x120e with AMD E-350 Fusion processor and integrated ATI graphics; I managed to get F15 running on it this week, after missing some of the previous test days because I couldn't boot into the provided LiveCDs (needed to use a minimal boot image from 2011-04-13 to partition the hard drive), but suspend / resume results in flaky graphics (need to log out and log back in again after resuming to give X a kick) and the Realtek wifi card reports a strong connection, even though it seems to be unable to transmit most of the time (the logs show no connection drops). I plan to file bug reports, just have precious little time at the moment to pull the formal info together and I haven't found any smoking guns in the logs to date. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Public Service Announcement re 'Oh no! Something has gone wrong' screen in GNOME 3
Hey, all. If you're running F15 with updates and after a recent update you find that you keep getting the Shell's 'Oh no! Something has gone wrong' screen (informally known as the fail whale), check if you have the packages gnome-shell-3.0.0.2-2.fc15 and gnome-menus-3.0.0-1.fc15 installed. This combination is bad and results in the above behaviour. To fix it, update to gnome-menus-3.0.0-2.fc15 (it's in updates-testing, or you can grab it from Koji). Somehow, even though gnome-shell-3.0.0.2-2.fc15 and gnome-menus-3.0.0-2.fc15 are part of the same update, gnome-shell got into the F15 'stable' repo ahead of gnome-menus, so if you have the updates-testing repo disabled you may have run into this. The releng team is working to fix the bug that caused this to happen so it won't hit future updates. They've now tagged the gnome-menus package into stable, so once repos sync up, it won't be possible (or at least likely) to hit this any more. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
On Wed, 2011-04-20 at 01:12 -0700, Per Bothner wrote: I got a new Sandy Bridge i7 laptop with nvidia/optimus graphics. I managed to install the new KDE beta, after a few problems. However, there seems to be some issues with nouvaeu trying to start up: One issue is errors messages and slowness starting up: First I get this console message: mkdir: cannot create directory `/run': File exists This is known, and harmless (currently systemd tries to create /run when it starts in case it doesn't exist in the filesystem, but F15's filesystem package does include /run, hence the error.) Then I get these errors from nouveau: Pointer to BIT loadval table invalid i2c wr fail: -6 PGRAPH: unsupported chipset, please reported Do what it says on the tin :) Then it hangs for a long time (many minutes), before I finally bet a KDE login screen. After KDE starts up, things mostly work, but some fan is going continuously, even when the system is idle. Perhaps the GPU fan? If CPU usage shows as low, then that sounds likely. My preference would be to just use integrated graphics, and completely disable the nvidia graphics. Unfortunately, there doesn't seem to be a way to do that from the BIOS, at least not the visible BIOS control settings. Google around using your laptop's model number. There are hacks for the BIOSes for some systems to expose the option to isolate the Intel chipset (this is the case for my laptop). Googling hasn't found any good suggests so far. I've tried blacklist nouveau in both blacklist.conf and in blacklist-nouvaeu.conf. I also added rdblacklist=nouveau to the kernel line in grub.conf. One suggestion I've seen is to prm -e the nouveau driver. Nothing you can do at the OS level is going to force the BIOS to present the Intel adapter rather than the NVIDIA one, I don't think. What does lspci show - both the NVIDIA and the Intel adapter, or just the Intel one? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Public Service Announcement re 'Oh no! Something has gone wrong' screen in GNOME 3
On 04/20/2011 11:00 PM, Adam Williamson wrote: Hey, all. If you're running F15 with updates and after a recent update you find that you keep getting the Shell's 'Oh no! Something has gone wrong' screen (informally known as the fail whale), This type of error can apparently happen for any number of other reasons and GNOME Shell doesn't give you any more information other than a log out button. Not very helpful if you want to report a bug or find out what the heck went wrong. This seems a weak point that needs to be rectified quickly Rahul -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Public Service Announcement re 'Oh no! Something has gone wrong' screen in GNOME 3
On Wed, 2011-04-20 at 23:14 +0530, Rahul Sundaram wrote: On 04/20/2011 11:00 PM, Adam Williamson wrote: Hey, all. If you're running F15 with updates and after a recent update you find that you keep getting the Shell's 'Oh no! Something has gone wrong' screen (informally known as the fail whale), This type of error can apparently happen for any number of other reasons and GNOME Shell doesn't give you any more information other than a log out button. Not very helpful if you want to report a bug or find out what the heck went wrong. This seems a weak point that needs to be rectified quickly I'm told that the conditions for the fail whale to hit are that anything controlled by gnome-session crashes more than once within a short time after session start. Generally, debugging starts by looking at ~/.xsession-errors to see what's crashing. (Someone else noted you can actually close the fail whale screen with alt-f4, to get a look behind it. Presumably this only works if mutter is still up.) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
On 04/20/2011 01:33 PM, Adam Williamson wrote: First I get this console message: mkdir: cannot create directory `/run': File exists This is known, and harmless (currently systemd tries to create /run when it starts in case it doesn't exist in the filesystem, but F15's filesystem package does include /run, hence the error.) If this is a scripty thing perhaps it can be changed to mkdir -p If its c-code, then perhaps ignoring EEXIST from mkdir() call. gene/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
On Wed, Apr 20, 2011 at 12:21, Per Bothner p...@bothner.com wrote: On 04/20/2011 10:00 AM, Jason D. Clinton wrote: On Wed, Apr 20, 2011 at 11:14, Per Bothner p...@bothner.com mailto:p...@bothner.com wrote: I did try hard to get a laptop with just integrated graphics, but they're very hard to find, especially once you get to mid/upper-end with i7 quad-core Sandy Bridge. Most of them have nvidia/optimus. A few have ATI, which would of course be my strong preference, but there are very few choices, especially if you want to avoid a glossy screen. All of the ThinkPad line can meet these requirements and work out-of-the box with no proprietary bits. Yes, if you limit yourself to i7-2620M. Chips higher than the 2620M do not have Intel graphics (Ironlake) and so they must have discreet video from either NVidia or ATI. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-15 boot issues
1) Yesterday an unattended reboot to F-15 went past the passphrase prompt for my LUKS /home partition and ended in gdm with /home not being mounted. Normal behaviour would have been for me to type in the passphrase, because that's how it is set up in /etc/crypttab for this install. The issue is not reproducible, and I boot into F-15 at least twice a day. What could I look at if I ran into it again? 2) Partitions mounted twice: $ mount|sort|uniq -d /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered) /dev/mapper/vg_faldor-Home on /home/misc15/mnt/sharedhome type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) 3) Occasionally, a booted F-15 shows a gdm screen where existing user accounts are not displayed. Only 'Other' is available. I can use it to log in, and using Cancel refreshes gdm to display the previously missing users. Looks like there's a race condition somewhere. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
On 04/20/2011 10:33 AM, Adam Williamson wrote: Nothing you can do at the OS level is going to force the BIOS to present the Intel adapter rather than the NVIDIA one, I don't think. What does lspci show - both the NVIDIA and the Intel adapter, or just the Intel one? lspic show: 01:00.0 VGA compatible controller: nVidia Corporation Device 0df4 (rev a1) It is shown - both before and after I do the test_off as described in: http://linux-hybrid-graphics.blogspot.com/2010/07/using-acpicall-module-to-switch-onoff.html On 04/20/2011 10:00 AM, Jason D. Clinton wrote: Chips higher than the 2620M do not have Intel graphics (Ironlake) and so they must have discreet video from either NVidia or ATI. Are you sure? I thought the whole point of Optimus was to be able to switch between integrated and discrete graphics - so there must be some Intel graphics. The card that came with my laptop calls this Intel Integrated GPU. -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problems
On Wed, Apr 20, 2011 at 13:12, Jason D. Clinton m...@jasonclinton.com wrote: On Wed, Apr 20, 2011 at 12:21, Per Bothner p...@bothner.com wrote: On 04/20/2011 10:00 AM, Jason D. Clinton wrote: On Wed, Apr 20, 2011 at 11:14, Per Bothner p...@bothner.com mailto:p...@bothner.com wrote: I did try hard to get a laptop with just integrated graphics, but they're very hard to find, especially once you get to mid/upper-end with i7 quad-core Sandy Bridge. Most of them have nvidia/optimus. A few have ATI, which would of course be my strong preference, but there are very few choices, especially if you want to avoid a glossy screen. All of the ThinkPad line can meet these requirements and work out-of-the box with no proprietary bits. Yes, if you limit yourself to i7-2620M. Chips higher than the 2620M do not have Intel graphics (Ironlake) and so they must have discreet video from either NVidia or ATI. Actually, that's not right. In Sandy Bridge generation, it might be a thermal problem. 2620M is the highest part that stays inside the 35W envelope which has been as high as Intel mobile parts have gone, historically. It sure seems that companies are only shipping these 45W chips with laptops that also have cooling assemblies for discreet graphics. Also, in the T520 series, the motherboard is slightly different. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-15 boot issues
On Wed, 2011-04-20 at 20:26 +0200, Michael Schwendt wrote: 1) Yesterday an unattended reboot to F-15 went past the passphrase prompt for my LUKS /home partition and ended in gdm with /home not being mounted. Normal behaviour would have been for me to type in the passphrase, because that's how it is set up in /etc/crypttab for this install. The issue is not reproducible, and I boot into F-15 at least twice a day. What could I look at if I ran into it again? This sounds like: https://bugzilla.redhat.com/show_bug.cgi?id=695407 AIUI there's a timeout for encrypted partition mounting; if you don't type a passphrase within the timeout it'll try and continue boot. I'm not sure if there's a filter for 'essential' partitions; if there is, it doesn't include /home. It'd be good if Lennart would provide some detail on the intentions here in the bug report. 2) Partitions mounted twice: $ mount|sort|uniq -d /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered) /dev/mapper/vg_faldor-Home on /home/misc15/mnt/sharedhome type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) What's in /etc/fstab ? 3) Occasionally, a booted F-15 shows a gdm screen where existing user accounts are not displayed. Only 'Other' is available. I can use it to log in, and using Cancel refreshes gdm to display the previously missing users. Looks like there's a race condition somewhere. This is https://bugzilla.redhat.com/show_bug.cgi?id=678236 . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-15 boot issues
On Wed, 2011-04-20 at 20:26 +0200, Michael Schwendt wrote: 1) Yesterday an unattended reboot to F-15 went past the passphrase prompt for my LUKS /home partition and ended in gdm with /home not being mounted. Normal behaviour would have been for me to type in the passphrase, because that's how it is set up in /etc/crypttab for this install. The issue is not reproducible, and I boot into F-15 at least twice a day. What could I look at if I ran into it again? Oddly enough, I _think_ this is the intended behavior. I had a similar issue during Alpha, and it seems admins asked for a passphrase timeout when activating any non-essential system partitions during boot. The timeout is in the minutes range, I forget if it's 1 or 3 minutes. I'm trying to re-familiarize myself with this issue, so don't quote me on this yet! :) Are you not encrypting your rootfs, or is the passphrase for the rootfs and /home different such that you are always prompted for the /home passphrase on boot? 2) Partitions mounted twice: $ mount|sort|uniq -d /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered) /dev/mapper/vg_faldor-Home on /home/misc15/mnt/sharedhome type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) Selinux sandbox (policycoreutils-sandbox) is responsible for making it look like partitions are mounted twice. Iirc, they are bind mounts. 3) Occasionally, a booted F-15 shows a gdm screen where existing user accounts are not displayed. Only 'Other' is available. I can use it to log in, and using Cancel refreshes gdm to display the previously missing users. Looks like there's a race condition somewhere. Still trying to pinpoint this issue in https://bugzilla.redhat.com/show_bug.cgi?id=678236 Thanks, James signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-15 boot issues
On Wed, 20 Apr 2011 11:59:12 -0700, AW wrote: 2) Partitions mounted twice: $ mount|sort|uniq -d /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered) /dev/mapper/vg_faldor-Home on /home/misc15/mnt/sharedhome type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) What's in /etc/fstab ? $ cat /etc/fstab # # /etc/fstab # Created by anaconda on Mon Apr 4 22:26:43 2011 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=c7bc3679-139b-441a-a234-13889dfa6a87 / ext4 defaults1 1 /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 /home ext4defaults1 2 /dev/mapper/vg_faldor-Storage /mnt/storageext3defaults1 2 UUID=9abb2e74-0237-4c28-aa25-aed5d24de2d3 swapswap defaults0 0 tmpfs /dev/shmtmpfs defaults0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults0 0 proc/proc procdefaults0 0 /mnt/storage/yum-cache/f15/var/cache/yum auto bind 0 0 /dev/mapper/vg_faldor-Home /home/misc15/mnt/sharedhomeext3 defaults 1 2 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 14 updates-testing report
The following Fedora 14 Security updates need testing: https://admin.fedoraproject.org/updates/tomcat6-6.0.26-20.fc14 https://admin.fedoraproject.org/updates/wireshark-1.4.6-1.fc14 https://admin.fedoraproject.org/updates/couchdb-1.0.2-1.fc14 https://admin.fedoraproject.org/updates/tor-0.2.1.29-1400.fc14 https://admin.fedoraproject.org/updates/fail2ban-0.8.4-27.fc14 https://admin.fedoraproject.org/updates/openldap-2.4.23-10.fc14 https://admin.fedoraproject.org/updates/perl-Mojolicious-0.29-2.fc14 https://admin.fedoraproject.org/updates/feh-1.10.1-1.fc14 https://admin.fedoraproject.org/updates/avahi-0.6.27-6.fc14 https://admin.fedoraproject.org/updates/mediawiki-1.16.4-57.fc14 https://admin.fedoraproject.org/updates/polkit-0.98-5.fc14 https://admin.fedoraproject.org/updates/python-feedparser-5.0.1-1.fc14 https://admin.fedoraproject.org/updates/ikiwiki-3.20110328-1.fc14 https://admin.fedoraproject.org/updates/krb5-1.8.2-10.fc14 The following Fedora 14 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/polkit-0.98-5.fc14 https://admin.fedoraproject.org/updates/NetworkManager-0.8.3.999-2.git20110414.fc14 https://admin.fedoraproject.org/updates/pygtk2-2.17.0-9.fc14 https://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-14.20101010git8c8f15c.fc14 https://admin.fedoraproject.org/updates/dosfstools-3.0.9-6.fc14 https://admin.fedoraproject.org/updates/libimobiledevice-1.0.6-1.fc14 https://admin.fedoraproject.org/updates/libconcord-0.23-5.fc14,udev-161-9.fc14,concordance-0.23-2.fc14 https://admin.fedoraproject.org/updates/usbmuxd-1.0.7-1.fc14 https://admin.fedoraproject.org/updates/openldap-2.4.23-10.fc14 https://admin.fedoraproject.org/updates/avahi-0.6.27-6.fc14 https://admin.fedoraproject.org/updates/xorg-x11-drv-geode-2.11.11-4.fc14 The following builds have been pushed to Fedora 14 updates-testing Zim-0.51-1.fc14 bluetile-0.5.3-5.fc14 cmusphinx3-0.8-7.fc14 cobbler-2.0.11-1.fc14 collectd-4.9.5-2.fc14 darktable-0.8-8.fc14 gappa-0.14.1-1.fc14 ghc-regex-tdfa-1.1.8-1.fc14 gnucash-2.4.5-1.fc14 latexmk-4.23a-1.fc14 mozc-1.1.690.102-0.2.20110419svn.fc14 nfs-utils-1.2.3-6.fc14 openscap-0.7.2-1.fc14 openvas-manager-2.0.3-1.fc14 perl-Eval-Closure-0.04-1.fc14 perl-Ouch-0.0300-1.fc14 pocketsphinx-0.7-1.fc14 polkit-0.98-5.fc14 psfex-3.9.1-3.fc14 python-cloudfiles-1.7.9.1-1.fc14 python-dns-1.9.4-1.fc14 python-twisted-conch-10.1.0-2.fc14 sphinxbase-0.7-1.fc14 spice-protocol-0.8.0-1.fc14 spice-vdagent-0.8.0-1.fc14 Details about builds: Zim-0.51-1.fc14 (FEDORA-2011-5681) Desktop wiki notekeeper Update Information: New upstream release ChangeLog: * Wed Apr 20 2011 Robin Lee cheese...@fedoraproject.org - 0.51-1 - Update to 0.51 (#683469) References: [ 1 ] Bug #683469 - [abrt] Zim-0.50-1.fc14: widgets.py:1762:lambda:AttributeError: 'CustomToolManagerDialog' object has no attribute 'show_help' https://bugzilla.redhat.com/show_bug.cgi?id=683469 bluetile-0.5.3-5.fc14 (FEDORA-2011-5661) Tiling window manager for GNOME ChangeLog: * Wed Apr 20 2011 Jens Petersen peter...@redhat.com - 0.5.3-5 - gnome-session uses gconf to find window-manager: - remove gnome-bluetile-session, since WINDOW_MANAGER doesn't work by default - add a readme file explaining the gconf and other ways of setting up cmusphinx3-0.8-7.fc14 (FEDORA-2011-5659) Large vocabulary speech recognition in C Update Information: This update represents a major upgrade in functionality. See http://cmusphinx.sourceforge.net/2011/04/cmusphinx-0-7-is-released/ for more information. ChangeLog: * Tue Apr 19 2011 Jerry James loganje...@gmail.com - 0.8-7 - Rebuild for sphinxbase 0.7 * Mon Nov 29 2010 Jerry James loganje...@gmail.com - 0.8-5 - Move COPYING and other doc files to -libs package.
Fedora 13 updates-testing report
The following Fedora 13 Security updates need testing: https://admin.fedoraproject.org/updates/tor-0.2.1.29-1300.fc13 https://admin.fedoraproject.org/updates/mediawiki-1.16.4-57.fc13 https://admin.fedoraproject.org/updates/libmodplug-0.8.7-3.fc13 https://admin.fedoraproject.org/updates/feh-1.10.1-1.fc13 https://admin.fedoraproject.org/updates/perl-Mojolicious-0.25-3.fc13 https://admin.fedoraproject.org/updates/perl-5.10.1-123.fc13 https://admin.fedoraproject.org/updates/openldap-2.4.21-12.fc13 https://admin.fedoraproject.org/updates/wireshark-1.2.16-1.fc13 https://admin.fedoraproject.org/updates/libcgroup-0.35.1-5.fc13 https://admin.fedoraproject.org/updates/libtiff-3.9.5-1.fc13 https://admin.fedoraproject.org/updates/polkit-0.96-2.fc13 https://admin.fedoraproject.org/updates/python-feedparser-5.0.1-1.fc13 https://admin.fedoraproject.org/updates/xorg-x11-server-utils-7.4-17.fc13 https://admin.fedoraproject.org/updates/krb5-1.7.1-19.fc13 https://admin.fedoraproject.org/updates/ikiwiki-3.20100815.7-1.fc13 https://admin.fedoraproject.org/updates/fail2ban-0.8.4-27.fc13 The following Fedora 13 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/polkit-0.96-2.fc13 https://admin.fedoraproject.org/updates/xorg-x11-drv-penmount-1.4.1-2.fc13 https://admin.fedoraproject.org/updates/NetworkManager-0.8.3.999-2.git20110414.fc13 https://admin.fedoraproject.org/updates/python-ethtool-0.7-2.fc13 https://admin.fedoraproject.org/updates/libtiff-3.9.5-1.fc13 https://admin.fedoraproject.org/updates/pygtk2-2.17.0-9.fc13 https://admin.fedoraproject.org/updates/dosfstools-3.0.9-5.fc13 https://admin.fedoraproject.org/updates/tzdata-2011d-3.fc13 https://admin.fedoraproject.org/updates/policycoreutils-2.0.83-33.8.fc13 https://admin.fedoraproject.org/updates/libimobiledevice-1.0.6-1.fc13 https://admin.fedoraproject.org/updates/usbmuxd-1.0.7-1.fc13 https://admin.fedoraproject.org/updates/fuse-2.8.5-5.fc13 https://admin.fedoraproject.org/updates/libcgroup-0.35.1-5.fc13 https://admin.fedoraproject.org/updates/openldap-2.4.21-12.fc13 https://admin.fedoraproject.org/updates/livecd-tools-13.2-1.fc13 https://admin.fedoraproject.org/updates/lua-5.1.4-7.fc13 https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.904-7.fc13 https://admin.fedoraproject.org/updates/lldpad-0.9.26-2.fc13 The following builds have been pushed to Fedora 13 updates-testing cobbler-2.0.11-1.fc13 ghc-regex-tdfa-1.1.8-1.fc13 latexmk-4.23a-1.fc13 mozc-1.1.690.102-0.2.20110419svn.fc13 perl-Eval-Closure-0.04-1.fc13 polkit-0.96-2.fc13 python-dns-1.9.4-1.fc13 Details about builds: cobbler-2.0.11-1.fc13 (FEDORA-2011-5657) Boot server configurator Update Information: New stable upstream release. See CHANGELOG for full description of updates. New upstream release, see CHANGELOG for complete description of changes. Upstream bug fix release. New upstream release, see CHANGELOG for full details Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release New upstream release, see CHANGELOG for full details Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release New upstream release, see CHANGELOG for full list of updates. Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release New upstream release, see CHANGELOG for full details Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release New upstream release, see CHANGELOG for complete description of changes. Upstream bug fix release. New upstream release, see CHANGELOG for full details Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release New upstream release, see CHANGELOG for full details Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release New upstream release, see CHANGELOG for full list of updates. Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release New upstream release, see CHANGELOG for full details Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler 2.0.4 release Cobbler
Re: Fedora 14 updates-testing report
upda...@fedoraproject.org wrote: cobbler-2.0.11-1.fc14 (FEDORA-2011-5680) Boot server configurator Update Information: New stable upstream release. See CHANGELOG for full description of updates. New upstream release, see CHANGELOG for complete description of changes. Upstream bug fix release. New upstream release, see CHANGELOG for full details Cobbler 2.0.4 release [snip huge, wasteful changelog] Can someone edit this so it isn't garbage? It also looks like the RPM spec[1] changelog was not properly edited. [1] http://pkgs.fedoraproject.org/gitweb/?p=cobbler.git;a=blobdiff;f=cobbler.spec;h=5fe3df22820a730465a976412011c2d3f8098219;hp=4eecb881280e5bd7c36ad5d454d14e2498b423f8;hb=4da91ec80994fd71e0fe7c40232417f71c9cd3af;hpb=f984a209680b749ad38c93bfeaa049e7bbc8ec2e -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 14 updates-testing report
On Wed, 2011-04-20 at 14:35 -0500, Michael Cronenworth wrote: upda...@fedoraproject.org wrote: cobbler-2.0.11-1.fc14 (FEDORA-2011-5680) Boot server configurator Update Information: New stable upstream release. See CHANGELOG for full description of updates. New upstream release, see CHANGELOG for complete description of changes. Upstream bug fix release. New upstream release, see CHANGELOG for full details Cobbler 2.0.4 release [snip huge, wasteful changelog] Can someone edit this so it isn't garbage? It also looks like the RPM spec[1] changelog was not properly edited. [1] http://pkgs.fedoraproject.org/gitweb/?p=cobbler.git;a=blobdiff;f=cobbler.spec;h=5fe3df22820a730465a976412011c2d3f8098219;hp=4eecb881280e5bd7c36ad5d454d14e2498b423f8;hb=4da91ec80994fd71e0fe7c40232417f71c9cd3af;hpb=f984a209680b749ad38c93bfeaa049e7bbc8ec2e wasteful to what? -sv -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 14 updates-testing report
seth vidal wrote: wasteful to what? When I create updates in the future should I make them hundreds of lines long like I'm in detention at school, too? I don't like resulting to sarcasm, but I don't see how you see this as not wasteful. Meaning: Scroll down the updates e-mail and look at the cobbler changelog. It makes up about 25% of the length of the updates e-mail. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 14 updates-testing report
On Wed, 2011-04-20 at 14:43 -0500, Michael Cronenworth wrote: seth vidal wrote: wasteful to what? When I create updates in the future should I make them hundreds of lines long like I'm in detention at school, too? I don't like resulting to sarcasm, but I don't see how you see this as not wasteful. I mean - it's not waste unless there is a limit to the number of bits. you don't NEED to download the updateinfo to get the updates. -sv -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-15 boot issues
On Wed, 2011-04-20 at 21:09 +0200, Michael Schwendt wrote: $ mount|sort|uniq -d /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered) /dev/mapper/vg_faldor-Home on /home/misc15/mnt/sharedhome type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) What's in /etc/fstab ? $ cat /etc/fstab ... /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 /home ext4defaults1 2 /dev/mapper/vg_faldor-Home /home/misc15/mnt/sharedhomeext3 defaults 1 2 ... well, there you go, those mountpoints are both in there. I guess the question is how they got there... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-15 boot issues
On Wed, 2011-04-20 at 12:51 -0700, Adam Williamson wrote: On Wed, 2011-04-20 at 21:09 +0200, Michael Schwendt wrote: $ mount|sort|uniq -d /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered) /dev/mapper/vg_faldor-Home on /home/misc15/mnt/sharedhome type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) What's in /etc/fstab ? $ cat /etc/fstab ... /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 /home ext4defaults1 2 /dev/mapper/vg_faldor-Home /home/misc15/mnt/sharedhomeext3 defaults 1 2 ... well, there you go, those mountpoints are both in there. I guess the question is how they got there... I suspect sandbox ... http://lists.fedoraproject.org/pipermail/test/2011-April/098960.html Thanks, James signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 14 updates-testing report
On 04/20/2011 03:43 PM, Michael Cronenworth wrote: seth vidal wrote: wasteful to what? When I create updates in the future should I make them hundreds of lines long like I'm in detention at school, too? I don't like resulting to sarcasm, but I don't see how you see this as not wasteful. Meaning: Scroll down the updates e-mail and look at the cobbler changelog. It makes up about 25% of the length of the updates e-mail. Concur: [Cobbler 2.0.4 release\n\n] ^ n; n-large number Plus [New upstream release, see CHANGELOG for full details]^m ; with m n/4 is wasteful and not useful :-) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-15 boot issues
On Wed, 20 Apr 2011 12:51:41 -0700, AW wrote: On Wed, 2011-04-20 at 21:09 +0200, Michael Schwendt wrote: $ mount|sort|uniq -d /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered) /dev/mapper/vg_faldor-Home on /home/misc15/mnt/sharedhome type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) What's in /etc/fstab ? $ cat /etc/fstab ... /dev/mapper/luks-15465009-86ee-4a3c-a291-5a105ca148c4 /home ext4defaults1 2 /dev/mapper/vg_faldor-Home /home/misc15/mnt/sharedhomeext3 defaults 1 2 ... well, there you go, those mountpoints are both in there. I guess the question is how they got there... No, the entries are needed of course and are normal. Without them, /home would not be mounted at all. ;) Same for the other LV. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 14 updates-testing report
seth vidal wrote: I mean - it's not waste unless there is a limit to the number of bits. you don't NEED to download the updateinfo to get the updates. Again, let me clarify. I'm not talking about bytes. With compression these lines make up no significance of the updates metadata. Is it useful to anyone wanting to test cobbler to see a 100+ line changelog that has no meaning? What kind of impression are we giving Fedora users who read the bodhi update notes? We don't care about recording changes and just allow any kind of garbage into the update notes? Will it take posting spam links in bodhi notes to see someone take action? Is my point clear now? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] 2011-04-21 @ 17:00 UTC - F-15 blocker bug review #2
# F15 Blocker Review meeting #2 # Date: 2011-04-21 # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST) # Location: #fedora-bugzappers on irc.freenode.net Due to upcoming holidays, the second F15 Final blocker review meeting will be this Thursday at 17:00 UTC in #fedora-bugzappers. We'll review proposed and accepted F-15 blocker bugs. As usual, an updated list of blocker bugs is available at https://fedoraproject.org/wiki/Current_Release_Blockers. The list of bugs is also attached to this mail. We'll be reviewing the bugs to determine ... 1. whether they meet the Final release criteria [2] and should stay on the list 2. are getting the attention they need For guidance on Blocker and Nice-to-have (NTH) bugs, checkout ... https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_nth_bug_process == Suggested Meeting Preparation == Maintainers ... * If your bug is *not* MODIFIED ... this issue is at risk of slipping the F15 Beta release date * If your bug is in MODIFIED ... please make sure a build with the fix exists, and is available as a bodhi update. Testers ... * If you REPORT a bug ... please be responsive to any requests for additional information. * If a bug is in ON_QA ... please take a moment to apply the update, and post karma feedback [1] https://fedoraproject.org/wiki/Infrastructure/UTCHowto [2] https://fedoraproject.org/wiki/Fedora_15_Final_Release_Criteria Thanks, James == Approved Blockers == The following list of bugs are approved blockers that must be resolved. There are 4 bugs affecting 4 components. === anaconda === * https://bugzilla.redhat.com/695389 (MODIFIED) - Traceback when writing a kickstart for an unused lvm-on-raid (TypeError: 'NoneType' object is not subscriptable) === desktop-backgrounds === * https://bugzilla.redhat.com/696832 (ON_QA) - Default Install of F15-desktop does not contain fedora desktop as default === nautilus === * https://bugzilla.redhat.com/689260 (NEW) - [abrt] nautilus-2.91.91-1.fc15: gtk_action_group_add_action: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) === system-config-services === * https://bugzilla.redhat.com/682001 (ASSIGNED) - s-c-services - all read and disabled == Proposed Blockers == The following list of bugs are not yet approved to block the release. There are 14 bugs affecting 12 components. For guidance on reviewing the following bugs, refer to [[QA:SOP_blocker_bug_process]]. === NetworkManager === * https://bugzilla.redhat.com/696278 (NEW) - The system network services are not compatible with this version. === NetworkManager-openconnect === * https://bugzilla.redhat.com/696107 (ON_QA) - NetworkManager Openconnect fails in FC15 Alpha === gdm === * https://bugzilla.redhat.com/678236 (NEW) - User list sometimes not visible on greeter === gnome-menus === * https://bugzilla.redhat.com/697834 (NEW) - Other menu appears in default installation === gnome-session === * https://bugzilla.redhat.com/698184 (NEW) - Enabling session saving with Gnome shell makes GUI login unusable === gnome-themes-standard === * https://bugzilla.redhat.com/674799 (ON_QA) - Isn't dragged in for upgrades === gstreamer === * https://bugzilla.redhat.com/695730 (NEW) - PackageKit doesn't find codecs === ibus === * https://bugzilla.redhat.com/696510 (MODIFIED) - need a dependency in ibus-gtk3 for imsettings-gnome === imsettings === * https://bugzilla.redhat.com/693809 (ASSIGNED) - Error message about missing input methods should be removed === kernel === * https://bugzilla.redhat.com/693442 (NEW) - NETDEV WATCHDOG: em1 (sky2): transmit queue 0 timed out === ntfs-3g === * https://bugzilla.redhat.com/697008 (NEW) - Include the latest ntfs-3g package in the final F-15 compose === systemd === * https://bugzilla.redhat.com/678555 (NEW) - systemd should not purge application created cgroups, even if they contain no processes * https://bugzilla.redhat.com/692230 (NEW) - Non-root iSCSI volumes are not mounted on boot * https://bugzilla.redhat.com/696320 (NEW) - After text-mode iSCSI install and boot, firstboot-text and getty are both running - unable to login on console == Approved NICE-TO-HAVE == The following list of of bugs are approved nice-to-have. Fixes for nice-to-have bugs will be accepted during the freeze. There are 3 bugs affecting 3 components. === gdm === * https://bugzilla.redhat.com/678236 (NEW) - User list sometimes not visible on greeter === lockdev === * https://bugzilla.redhat.com/681898 (ON_QA) - DON'T make /var/lock/lockdev world writeable (security issue) === report === * https://bugzilla.redhat.com/696240 (ON_DEV) - report is filing Fedora 15 installer bugs against rawhide (not Fedora 15) == Proposed NICE-TO-HAVE == The following list of bugs are not yet approved nice-to-have issues. Only fixes for approved nice-to-have bugs will be accepted during the freeze. There are
Re: nvidia/nouveau problem
I have been following this thread about the nvidia and nouveau problem. I had the problem in my installation too until I installed using the install with basic video drive the second choice down on the installation choices page and I am having good success with my installation. I installed the Beta release on a Dell 9400 Inspirion, FX2500 video card, 4g Hyperx memory, T7700 processor. -- Lawrence E Graves lgra...@risingstarmbc.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-15 Branched report: 20110420 changes
Compose started at Wed Apr 20 13:15:55 UTC 2011 Broken deps for x86_64 -- collectd-mysql-4.10.2-2.fc15.x86_64 requires libmysqlclient.so.16()(64bit) collectd-mysql-4.10.2-2.fc15.x86_64 requires libmysqlclient.so.16(libmysqlclient_16)(64bit) cpm-0.23-0.3.beta.fc12.x86_64 requires libdotconf-1.0.so.0()(64bit) db4o-7.4-2.fc13.x86_64 requires mono(Mono.GetOptions) = 0:2.0.0.0 dbmail-3.0.0-0.3.rc1.fc15.x86_64 requires libevent-1.4.so.2()(64bit) dbmail-auth-ldap-3.0.0-0.3.rc1.fc15.x86_64 requires libevent-1.4.so.2()(64bit) dh-make-0.55-3.fc15.noarch requires debhelper eog-plugins-2.91.90-1.fc15.x86_64 requires libchamplain-gtk-0.10.so.0()(64bit) eog-plugins-2.91.90-1.fc15.x86_64 requires libchamplain-0.10.so.0()(64bit) 1:fife-0.3.2-1.fc15.i686 requires libboost_regex.so.1.44.0 1:fife-0.3.2-1.fc15.i686 requires libboost_system.so.1.44.0 1:fife-0.3.2-1.fc15.i686 requires libboost_filesystem.so.1.44.0 1:fife-0.3.2-1.fc15.x86_64 requires libboost_regex.so.1.44.0()(64bit) 1:fife-0.3.2-1.fc15.x86_64 requires libboost_system.so.1.44.0()(64bit) 1:fife-0.3.2-1.fc15.x86_64 requires libboost_filesystem.so.1.44.0()(64bit) file-browser-applet-0.6.6-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::ScrolledWindow) gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::Dialog) gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::Toolbar) gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::TreeView) gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::MenuBar) gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::VBox) gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::Window) gcstar-1.6.1-3.fc15.noarch requires perl(Gtk2::MessageDialog) glom-1.16.1-2.fc15.x86_64 requires libgdamm-4.0.so.12()(64bit) glom-libs-1.16.1-2.fc15.i686 requires libgdamm-4.0.so.12 glom-libs-1.16.1-2.fc15.x86_64 requires libgdamm-4.0.so.12()(64bit) glunarclock-0.34.1-1.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-bubblemon-2.0.15-1.fc13.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-cpufire-1.6-3.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-globalmenu-0.7.9-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-grandr-0.4.1-2.fc12.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-music-2.5.1-5.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-sensors-2.2.7-4.fc15.i686 requires libpanel-applet-2.so.0 gnome-applet-sensors-2.2.7-4.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-sshmenu-3.18-3.fc15.noarch requires ruby(panelapplet2) gnome-applet-window-picker-0.5.8-2.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) 1:gnome-applets-2.32.0-3.fc15.x86_64 requires libpanel-applet-3.so.0()(64bit) 1:gnome-applets-2.32.0-3.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) 1:gnome-applets-2.32.0-3.fc15.x86_64 requires libgweather.so.1()(64bit) gnome-netstatus-2.28.2-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotd.so.5()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotdcm.so.4()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotdconduit.so.3()(64bit) gnome-python2-applet-2.32.0-1.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-python2-brasero-2.32.0-1.fc14.x86_64 requires libbrasero-media.so.1()(64bit) gnome-python2-brasero-2.32.0-1.fc14.x86_64 requires libbrasero-burn.so.1()(64bit) gnome-python2-evince-2.32.0-1.fc14.x86_64 requires libevview.so.3()(64bit) gnome-python2-evince-2.32.0-1.fc14.x86_64 requires libevdocument.so.3()(64bit) gnome-python2-evolution-2.32.0-1.fc14.x86_64 requires libcamel-1.2.so.19()(64bit) gnome-python2-gdl-2.25.3-22.fc15.x86_64 requires libgdl-1.so.3()(64bit) gnome-python2-totem-2.32.0-1.fc14.x86_64 requires libgnome-media-profiles.so.0()(64bit) gnome-rdp-0.2.3-6.fc12.x86_64 requires mono(Mono.Data.SqliteClient) = 0:2.0.0.0 gnome-themes-2.32.0-5.fc15.noarch requires gtk-theme-engine-clearlooks gnomeradio-1.8-9.fc15.x86_64 requires libgtk-3.0.so.0()(64bit) gnomeradio-1.8-9.fc15.x86_64 requires libgdk-3.0.so.0()(64bit) gnotime-2.3.0-8.fc15.x86_64 requires libgtkhtml-3.15.so.19()(64bit) gnubiff-2.2.13-4.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnustep-back-0.18.0-4.fc14.x86_64 requires libobjc.so.2()(64bit) gnustep-back-0.18.0-4.fc14.x86_64 requires libgnustep-base.so.1.20()(64bit) gnustep-examples-1.3.0-4.fc15.x86_64
Hard disk install from DVD image?
OK, I've been doing installs from the dvd image on hard disk forever because they are faster and don't require fiddling with actual media. I just downloaded the x86_64 f15 beta DVD iso, and there is no install.img file anymore that I used to have to copy to an images subdir. What is the new technique for doing a hard disk install? Have anaconda options for pointing to the disk image changed as well? Or do I no longer need the install.img file and can go back to just pointing to the iso image itself like I used to do before things changed a while back? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problem
On 04/20/2011 01:58 PM, Lawrence E Graves wrote: I have been following this thread about the nvidia and nouveau problem. I had the problem in my installation too until I installed using the install with basic video drive the second choice down on the installation choices page and I am having good success with my installation. I installed the Beta release on a Dell 9400 Inspirion, FX2500 video card, 4g Hyperx memory, T7700 processor. This may the same effect as specifying nomodeset on the grub kernel line. That seems to work - it boots fairly cleanly, with no long pause. However, the downside is pretty bad: Maximum resolution of 1280x014, and it doesn't detect an external display. -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problem
On Wed, 2011-04-20 at 17:54 -0700, Per Bothner wrote: On 04/20/2011 01:58 PM, Lawrence E Graves wrote: I have been following this thread about the nvidia and nouveau problem. I had the problem in my installation too until I installed using the install with basic video drive the second choice down on the installation choices page and I am having good success with my installation. I installed the Beta release on a Dell 9400 Inspirion, FX2500 video card, 4g Hyperx memory, T7700 processor. This may the same effect as specifying nomodeset on the grub kernel line. That seems to work - it boots fairly cleanly, with no long pause. However, the downside is pretty bad: Maximum resolution of 1280x014, and it doesn't detect an external display. -- --Per Bothner p...@bothner.com http://per.bothner.com/ This may be true but it's Beta and it works for the time being. I am just trying to learn some of the new features and that's all I am ask for right now. Before it is all said and done everything will be alright. Do you agree? -- Lawrence E Graves lgra...@risingstarmbc.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Multiple F15Beta bugs in under an hour
Ok, downloaded the F15Beta live cd today. Booted it on a Thinkpad X200s docked with external display, keyboard and mouse + internal panel. Guess I'll run the bugs by roughly in the order discovered. Grub is the first one. The external keyboard didn't work. It does on F12 which is the primary OS on the machine. Lauching the file browser (nautilus?) and mousing over the available mount points got a crash from gvfs. Next bug is no debuginfo packages for key bits like glibc means no automatic bug report from abrt was possible. Guys, no debug packages means no good reports, which is the whole point of a beta, right? Cups is present and browsing is enabled but no printers show. Lots of printers are expected to show. Nothing interesting in the logs. My large display is to the left of the laptop. This is correctable via the GUI. Making it the primary display isn't, xrandr is required to set the primary display with 'xrandr --output HDMI2 --primary' If the user needs the terminal for something that basic, more baking needs doin'. Invoking the sound config locks if you click on a default sound. Quiet repeating grunts are audible until it finally crashes for good and again, abrt can't make a report. Not sure yet if that is a kernel problem, the eternal horror of pulseaudio or something new. When I get time I will poke around more and report. Please don't be a kernel bug! I have had to pass over F13 and F14 because of kernel bugs in undocking if I have to skip F15 for sound I'm boned. Pulseaudio I can remove. Launch firefox and display the About popup. Notice anything missing? Yup, the only way to be rid of it is to stop FF and kill off xulrunner-bin. Or perhaps xkill? Is this a window manager (mutter?) bug? And finally, good thing I read the mailing lists... otherwise I'd have never guessed holding ALT down was the only way to shutdown or reboot. What genius of user interface design thought that was a good idea? REALLY? Seriously, this is introducing a whole new idiom to user interfaces that people have zero expectation of. The choices presented in a menu should not vary based on buckybits. It violates decades of user expectations. signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Hard disk install from DVD image?
On Wed, 20 Apr 2011 20:29:32 -0400 Tom Horsley wrote: Or do I no longer need the install.img file and can go back to just pointing to the iso image itself like I used to do before things changed a while back? Bingo! I just tried the experiment and it worked fine just pointing to the iso image directory even with no images subdir. (I'm glad I don't need to copy out images any more, but I bet I won't be the last confused by this). The install worked, though I haven't tried actually booting it yet. A couple of impressions from the install: Congratulations! You either finally disabled the screen blanking during anaconda, or the install runs so fast that the screen never got around to blanking itself. Anaconda resizing itself to fill a 46 inch 1920x1080 HD TV screen is a bit disconcerting. I think I liked the old version where it just drew a small window in the middle of the giant screen. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora-15-Nightly-20110420.17-i686-Live-soas.iso testing results
link: http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#Fedora-15-Nightly-20110420.17-i686-Live-soas.iso also visit this page for older tests tested with live cd on external usb dvd/CD -ACER ASPIRE ONE N450 10 netbook ===Fedora-15-Nightly-20110420.17-i686-Live-soas.iso=== *http://alt.fedoraproject.org/pub/alt/nightly-composes/current.html :Boots to NAME___;Color == *Does not connect to Wireless AP in f1 neighborhood :no connect dialog to enter AP Key ;Wired connection only connects to jabber after Control Panel about me color change and restart. ::sees 3 Wireless AP and 3 ad-hoc network points *Central Avitar disappears then chat icon missing on f1 *Restart ejects CD (it us usually goes back to login gdm screen like Control Panel restart does.) *Activities (all selected as favorites) # '''etoys 116''' error after startup '''write 72'''clip, bullet indent and table no submenus '''terminal 116''' '''memorize 36''' '''calculate 35''' no submenus '''physics 8''' '''record 66''' Photo Video OK no sound '''speak 20''' voice ok 2 right submenus bad # '''turtle art 105'''(did not start) see update below '''irc 9''' works but no channel tabs; have to /join '''pippy 40''' '''chat 70''' joined by another user not visible on F1 Dbus Exception: org.freedesktop.Telepathy, error invalid handle '''log 24''' '''abacus 19''' submenus OK # '''browse 120''' (did not start) *Software Update turtle art 105-107 Works no submenus speak 20-24 voice ok 2 right submenus bad record 66-89 very faint sounds calculate 35-36 no submenus Thanks. it is nice to have a working SoaS again. Tom Gilliard satellit on #sugar freenode IRC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Multiple F15Beta bugs in under an hour
Next bug is no debuginfo packages for key bits like glibc means no automatic bug report from abrt was possible. Guys, no debug packages means no good reports, which is the whole point of a beta, right? Are you saying that ABRT didn't download debuginfo packages? For a while now (not just F15) debuginfo isn't installed at install time. It just automatically gets downloaded when ABRT tries to generate the backtrace and it caches them in /var rather than installing them as full RPMs on the system. If ABRT didn't actually download the debugs that's actually a bug and you probably should report it. Launch firefox and display the About popup. Notice anything missing? Yup, the only way to be rid of it is to stop FF and kill off xulrunner-bin. Or perhaps xkill? Is this a window manager (mutter?) bug? Not that I specifically agree with it but popup windows like the about window are dismissed with the Esc key rather than a close button. Gnome-shell has some minimalistic design decisions in it which will take some getting used to like the lack of a minimize button and the alt button press for a shutdown. That last one seems fine for desktops which I run 24x7 but not necessarily laptops which I tend to shutdown and pack away. -- John Watzke -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Multiple F15Beta bugs in under an hour
On 04/20/2011 06:39 PM, John Watzke wrote: [snip] Launch firefox and display the About popup. Notice anything missing? Yup, the only way to be rid of it is to stop FF and kill off xulrunner-bin. Or perhaps xkill? Is this a window manager (mutter?) bug? Not that I specifically agree with it but popup windows like the about window are dismissed with the Esc key rather than a close button. Gnome-shell has some minimalistic design decisions in it which will take some getting used to like the lack of a minimize button and the alt button press for a shutdown. That last one seems fine for desktops which I run 24x7 but not necessarily laptops which I tend to shutdown and pack away. I think the OP has a good bead on this. It is rather silly to change the paradigm (no close button on popups) and expect people to use the ESC key instead. Use the ALT button to shut down? What kind of lunacy is this? I can't believe it takes THAT much more code/CPU to implement a close button and leave the shutdown mechanism alone regardless of how minimalistic they want to be. rant This sounds like change for change's sake and makes no sense whatsoever. The more I see of Gnome's silly decision making process, the less confidence I have in them. Surely Red Hat has some pull with these people. How about using a bit of it to quash these stupid plans? Red Hat can't realistically expect a RHEL release based on F15 and this sort of idiocy to fly with their customer base, do they? Seriously? /rant -- Rick Stevens -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Multiple F15Beta bugs in under an hour
On Wed, 2011-04-20 at 20:39 -0500, John Watzke wrote: Are you saying that ABRT didn't download debuginfo packages? For a while now (not just F15) debuginfo isn't installed at install time. It just automatically gets downloaded when ABRT tries to generate the backtrace and it caches them in /var rather than installing them as full RPMs on the system. If ABRT didn't actually download the debugs that's actually a bug and you probably should report it. It tried to download and failed. The failure dialog suggested running 'debuginfo-install gvfs'. That also failed. Apparently yum can't find glibc-debuginfo and a couple others. Launch firefox and display the About popup. Notice anything missing? Yup, the only way to be rid of it is to stop FF and kill off xulrunner-bin. Or perhaps xkill? Is this a window manager (mutter?) bug? Not that I specifically agree with it but popup windows like the about window are dismissed with the Esc key rather than a close button. Gnome-shell has some minimalistic design decisions in it which will take some getting used to like the lack of a minimize button and the alt button press for a shutdown. That last one seems fine for desktops which I run 24x7 but not necessarily laptops which I tend to shutdown and pack away. Personally I consider GNOME3 a regression. After trying F15Alpha I went ahead and switched my desktop to XFCE since I have zero desire to relearn everything. But I wanted to test the main release in the interest of giving the best feedback. signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Multiple F15Beta bugs in under an hour
On Wed, 2011-04-20 at 19:24 -0700, Rick Stevens wrote: I think the OP has a good bead on this. It is rather silly to change the paradigm (no close button on popups) and expect people to use the ESC key instead. Use the ALT button to shut down? What kind of lunacy is this? I can't believe it takes THAT much more code/CPU to implement a close button and leave the shutdown mechanism alone regardless of how minimalistic they want to be. Especially confusing since the window is still decorated with a thick bar at the top implying that SOMETHING should be there. Since they took away all the buttons and the title they should go ahead and suppress the bar. rant This sounds like change for change's sake and makes no sense whatsoever. The more I see of Gnome's silly decision making process, the less confidence I have in them. Surely Red Hat has some pull with these people. How about using a bit of it to quash these stupid plans? Red Hat can't realistically expect a RHEL release based on F15 and this sort of idiocy to fly with their customer base, do they? Seriously? /rant GNOME3 is more like an experimental university project 'to explore what we could do if we toss everything we know about existing user interfaces and start from scratch!' and it is now poised to ship as the default UI on one of the major Linux distros. I have a very bad feeling about this, suspect it will end badly. -- signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Multiple F15Beta bugs in under an hour
On Wed, 2011-04-20 at 20:07 -0500, John Morris wrote: Ok, downloaded the F15Beta live cd today. Booted it on a Thinkpad X200s docked with external display, keyboard and mouse + internal panel. Guess I'll run the bugs by roughly in the order discovered. Grub is the first one. The external keyboard didn't work. It does on F12 which is the primary OS on the machine. Fileabug. Lauching the file browser (nautilus?) and mousing over the available mount points got a crash from gvfs. Fileanother! Next bug is no debuginfo packages for key bits like glibc means no automatic bug report from abrt was possible. Guys, no debug packages means no good reports, which is the whole point of a beta, right? debuginfo packages are always generated in builds, they don't go 'missing'. We'd need much more detail on what you actually saw to figure out what problem you had here. Cups is present and browsing is enabled but no printers show. Lots of printers are expected to show. Nothing interesting in the logs. Did you set the firewall appropriately? My large display is to the left of the laptop. This is correctable via the GUI. Making it the primary display isn't, xrandr is required to set the primary display with 'xrandr --output HDMI2 --primary' If the user needs the terminal for something that basic, more baking needs doin'. It's not actually basic, because there's no way to reliably detect which display should be the primary in any given configuration. But the Display applet could probably stand having a button to do it, yeah. Invoking the sound config locks if you click on a default sound. Quiet repeating grunts are audible until it finally crashes for good and again, abrt can't make a report. Not sure yet if that is a kernel problem, the eternal horror of pulseaudio or something new. When I get time I will poke around more and report. Please don't be a kernel bug! I have had to pass over F13 and F14 because of kernel bugs in undocking if I have to skip F15 for sound I'm boned. Pulseaudio I can remove. That sounds like a hardware-specific kernel bug to me (PulseAudio generally can't crash anything _that_ hard). Launch firefox and display the About popup. Notice anything missing? Yup, the only way to be rid of it is to stop FF and kill off xulrunner-bin. Or perhaps xkill? Is this a window manager (mutter?) bug? Or...the Esc key. This one's been reported already. And finally, good thing I read the mailing lists... otherwise I'd have never guessed holding ALT down was the only way to shutdown or reboot. What genius of user interface design thought that was a good idea? REALLY? Seriously, this is introducing a whole new idiom to user interfaces that people have zero expectation of. The choices presented in a menu should not vary based on buckybits. It violates decades of user expectations. The alternative was not having the Shut Down option at all, so be careful what you wish for...=) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Multiple F15Beta bugs in under an hour
On Wed, 2011-04-20 at 19:24 -0700, Rick Stevens wrote: Not that I specifically agree with it but popup windows like the about window are dismissed with the Esc key rather than a close button. Gnome-shell has some minimalistic design decisions in it which will take some getting used to like the lack of a minimize button and the alt button press for a shutdown. That last one seems fine for desktops which I run 24x7 but not necessarily laptops which I tend to shutdown and pack away. I think the OP has a good bead on this. It is rather silly to change the paradigm (no close button on popups) and expect people to use the ESC key instead. The expectation isn't that people should use Esc, it's that the dialog should have a Close button. Check the About dialog for any GNOME app. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problem
On Wed, 2011-04-20 at 17:54 -0700, Per Bothner wrote: On 04/20/2011 01:58 PM, Lawrence E Graves wrote: I have been following this thread about the nvidia and nouveau problem. I had the problem in my installation too until I installed using the install with basic video drive the second choice down on the installation choices page and I am having good success with my installation. I installed the Beta release on a Dell 9400 Inspirion, FX2500 video card, 4g Hyperx memory, T7700 processor. This may the same effect as specifying nomodeset on the grub kernel line. That seems to work - it boots fairly cleanly, with no long pause. However, the downside is pretty bad: Maximum resolution of 1280x014, and it doesn't detect an external display. Both of these result in use of the generic VESA driver. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problem
On Wed, 2011-04-20 at 19:04 -0600, Lawrence E Graves wrote: This may be true but it's Beta and it works for the time being. I am just trying to learn some of the new features and that's all I am ask for right now. Before it is all said and done everything will be alright. Do you agree? It doesn't really work that way, bugs don't get fixed magically; they get fixed when you experience them, investigate them, and file useful reports, and Fedora's developers read the reports and go and fix the code :) (and sometimes, yes, even that doesn't happen). the Beta status isn't _terribly_ relevant here, there's no guarantee this will be fixed in Final; the more detailed info you're able to provide in a good bug report, the more likely our nouveau developers can fix it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Multiple F15Beta bugs in under an hour
On Wed, 2011-04-20 at 20:59 -0700, Adam Williamson wrote: The expectation isn't that people should use Esc, it's that the dialog should have a Close button. Check the About dialog for any GNOME app. If the expectation is that 100% of applications will conform to Gnome UI standards, there is only one word that comes to mind. Delusion. Firefox being one of the better examples. It is a port, Moz doesn't really give a darned what Linux users need. Almost all of their users and most of the developers are on Windows. It will be almost as hard for Gnome to impose their UI notions on KDE app developers. signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 LiveCD Autologin Bug Status Query
On 04/15/2011 12:27 PM, Tim Flink wrote: During the blocker meeting today, a greeter bug came up [1] but we weren't sure if this is affecting the live images. Using a recent live image, has anyone been dumped to gdm with an empty user list? Tim [1] https://bugzilla.redhat.com/show_bug.cgi?id=678236 Bumping in the hopes of getting feedback before we revisit this bug as a blocker tomorrow. If we don't have any cases of users being dumped to an empty gdm after failed autologin on a live image, it is likely to stay NTH. Tim signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problem
I think I have a simple work-around: Just remove nouvaeu.ko from /lib/modules/ Seems to work great: No weird errors or slowness booting. I can use the full laptop resolution *and* attach an external monitor over HDMI. Suspend/resume works fine. I'm not sure yet how robust it is. (Besides having to remove nouvaeu.ko each time the kernel is updated.) Some subsequence reboots hang, but that may be unrelated - I haven't figured out the pattern yet. -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F15 LiveCD Autologin Bug Status Query
Tim Flink tflink at redhat.com writes: During the blocker meeting today, a greeter bug came up [1] but we weren't sure if this is affecting the live images. Using a recent live image, has anyone been dumped to gdm with an empty user list? Tim [1] https://bugzilla.redhat.com/show_bug.cgi?id=678236 Booting from the latest GNOME3 test day i686 live image yesterday, this happened to me once. I haven't been able to reproduce it after several reboots on the same machine, though. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nvidia/nouveau problem
On Wed, Apr 20, 2011 at 10:23:27PM -0700, Per Bothner wrote: I think I have a simple work-around: Just remove nouvaeu.ko from /lib/modules/ Seems to work great: No weird errors or slowness booting. Quite possibly you may achieve the same effect by addind a file /etc/modprobe.d/nouvaeu.conf with blacklist nouvaeu in it (unless this module is loaded behind a modprobe back). Possibly you need to rebuild initramfs after such change. I'm not sure yet how robust it is. (Besides having to remove nouvaeu.ko each time the kernel is updated.) If it works then you do not have to remove/rename anything. Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
