fc7t4: still eating babies?
by Benjamin De Kosnik
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.
Thanks,
benjamin
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.
16 years, 12 months
rawhide users' actions because of core and extra merge?
by Gianluca Cecchi
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
16 years, 12 months
F7T4 -- I tried the Nouveau driver from the LiveCD and hit major problems
by Miles Lane
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
16 years, 12 months
F7t4 KDE live CD test report
by Doncho N. Gunchev
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
16 years, 12 months
problem after updating to libvirt-0.2.2-2.fc7
by Amit Rana
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?
16 years, 12 months
Re: problem with iwlwifi
by Amit Rana
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.
16 years, 12 months
Wireless ACX on T4
by Roger Grosswiler
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?
Thanks,
Roger
16 years, 12 months
FC7T4 xen 3ware96502LP SE7520BD2 can't boot
by p v
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
16 years, 12 months
Fedora 7 Test 4 GNOME based i386 Live CD report
by Rahul Sundaram
Hi
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
http://smolt.fedoraproject.org/show?UUID=492900d9-5ee0-441c-9792-fc2ecc86...
* 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
default
* 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
separate.
* 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
as expected.
* 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.
Rest later,
Rahul
16 years, 12 months