I thought the big feature of the new "intel" driver was its
ability to hot-swap displays. It doesn't seem to work for me, though I
realize this is beta code, and perhaps it isn't expected to work yet.
(If it is expected to work, I can file bugzilla report and provide
I have a Dell Inspiron R1405 with a 945GM chipsset and a 1440x900
screen. If I boot with my external monitor (ViewSonic, 1600x1200)
plugged in, then the external monitor is recognized, and 1600x1200
is used. The laptop mirrors the external monitor. It would be nice
to be able to show separate screens (with nvidia calls "twinview"),
but I haven't figured out how to do that, and it's not that important
What would be nice is being able to plug in an external monitor *after*
X has started, and have it be recognized, and used at full 1600x1200
resolution. When if I unplug the external monitor, I should be back
to the laptop, at 1440x900 resolution.
As I said, if this expected to work, I'll collect more data and
submit a bugzilla entry
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
I've tried nopci and noprobe as command line options but it continually
It's an old laptop - Compaq Presario 1246, but it should be able to
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.
Sie können mich aufreizen und wirklich heiß machen!
However, I found some bugs. In particular:
1) two drives in systems, installing onto one, not doing anything to
the second, but try to mount the second on say
/mnt/drive/montsouris so that one can read files from it. Kills anaconda dead.
2) same as one, but without the mount. Reboot: it looks like grub
written to the wrong drive (ie, installing on to drive one, grub info
written to drive two). UGH!!!!
Minor panic as I contemplate a day of moaning and non-paris rando velo
riding, but then I reboot into the fc7t4 disk and mount drive two
manuall: data still intact, apparently boot info fried. Ie, there is a
directory "/boot" but nothing is in it.
Any pointers on how to get drive two bootable again? Drive two is an
up-to-date FC6 install, or used to be.
ps. Usually I physically unplug the second drive to avoid this kind of
thing. Ever the optimist....
pps. please cc my gmail account on replies as my mail is now screwed.
Just installed the F7 T4 GNOME based i386 live cd and here are some of
my observations after playing with it for a day.
* You do not need to accept the EULA anymore. It just has a pointer to
the wiki link instead of including the text.
* Smolt integration UI is good and works well. Noticed that it said it
would update the profile automatically on a monthly basis. My test
system profile is
* Look and feel is good. Flying high theme with Mist based icon set.
* Firefox and Evolution are the default panel applications but seem to
be using the old Blue Curve icons.
* Network manager (nm-applet) is enabled by default
* Blog, stock ticker, bittorrent and gparted applications installed by
* fast user switcher applet is on the panel by default and shows up on
the lock screen. too.
* Multiple locales and input methods available by default
* Abiword does not crash on startup anymore. gnumeric is also available
but we are missing a small presentation program to complete this sort of
mini office suite.
* Beagle is installed by default and replaces gnome-search-tool on the
UI like the previous release. Might be better to keep these entries
* gThumb and GIMP are available by default but not f-spot.
* Pigdin has replaced Gaim. Has new icons and a better interface.
* Wodim has replaced cdrecord. cdrecord is a symlink to wodim and works
* New application, system-config-selinux is available under
administration. Looks pretty comprehensive. SELinux boolean
configuration has been removed from system-config-securitylevel and is
now available in this tool. Title says "system-config-selinux.py"
instead of just "system-config-selinux" which is a minor wart in the UI.
* Places and /home/<user> is filled by default folders for documents,
video etc. Might look less cluttered if those default folder were under
a common parent. /home/<user>/personal/<default folders> for example.
* Preferences menu is organized into multiple categories now. The
central control panel that GNOME includes is disabled by default
(upstream inherited) but can be enabled using alacarte. Menu editor is a
entry now in the preferences menu.
* Yum is faster. Pirut and Pup UI does not appear to hang anymore.
* About Fedora menu entry uses old wordings and says Fedora people
instead of Planet Fedora as we have agreed upon now for consistency.
* nautilus-open-terminal extension was not installed by default unlike
previous live cd releases.
* SCIM input icon doesnt show up on the system tray unlike the previous
test release. Default is showing on demand but setting it to show always
does not make it show up on the system tray.
* nautilus has crashed more than once during login including the
previous test releases with some vague bonobo error which I did not note
down. Anyone else seeing this?
* Turning on desktop effects immediately makes it crash Xorg
* shutdown entry showed up twice as first and last entries in the system
menu just once.
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.
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 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)
"Sex is like air, it's not important unless your not getting any!"
I am writing this report here since I can not reproduce anymore the result.
I used the dvd version to update my laptop from an existing FC-6. While
updating (760/850 total packages) the update stop and anaconda complained
that the it was not possible to update because of a possible corrupted media.
I asked for reboot and anaconda never returned the output. I changed to vt2
where I saw (using top) that some of the programs that usually run in the
post install stage were running. After waiting for more than an hour only
anaconda was running so I decided that it was time to force a reboot.
What is strange about this is that the package that anaconda complained about
was installed (redhat-lsb), the media check to the dvd returned an OK, and
according to the last report left in the installation log there was a problem
running a postinstall script.
I have used yum to update the system and everything seems to work as it
should. The only problem of the interrupted update was that no xorg server
was installed. After installing xorg-x11-server-Xorg everything works as
Is the iwlwifi package going to work in F7?
The current signs aren't great, as my Thinkpad T60p with a ipw3945
wireless still has the oft-reported problems in F7t4.
I'm willing to put some testing time in, but things are a bit
discouraging so far, I mean F7t4 is supposed to be a beta release. (Or
maybe there is some simple thing that needs to be done to get everything
to work, but what is it?)
Peter F. Patel-Schneider
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
<?xml version="1.0" encoding="UTF-8"?>
failed during request deserialization:
not well-formed (invalid token) at line 23, column 0, byte 1637 at