F12 Beta installation FAIL
by the.masch
I've installed F12 and updated to the latest version and I think that I have
an issue with the Xorg-server. In random time, I got black screen, no mouse
and no keyword works, but the OS works because I can connect from another
machine using SSH. I tried using GNOME and KDE and it freezes in both cases.
I have an Nvidia card and I've tried with nomodeset and without it.
Does anybody have the same problem? Should I report to bugzilla?
Thanks.
Salu2...
masch...
14 years, 8 months
anaconda asknetwork parameter
by Tom Horsley
https://bugzilla.redhat.com/show_bug.cgi?id=530470
This is my first f12 beta bug so far, and I worked around it
by simply removing the asknetwork parameter.
I remembered why I always use asknetwork later when trying to
get my static network up after the install :-).
I started as always by disabling NetworkManager and enabling
network. Then I copied my ifcfg-eth0 and ifcfg-br0 scripts
from fedora 11 partition to fedora 12 and rebooted.
Still no network.
I decided maybe bridges aren't working, so I deleted the br0
file and edited the eth0 file to have the whole static network
def, rebooted again, and still no network.
So I ran System > Administration > Network and defined the
eth0 from scratch, which produced a file as close to identical
to the one I made by hand as I could see, rebooted again,
and this time the network is up.
Why is this so hard? I guess I should try building the bridge
again next, but it is time to watch baseball now :-).
14 years, 8 months
F12 beta live installs
by Birger Monsen
I have tested a few installs on my idle test PC.
Overall, a nice new release with exciting news and a few blockers.
Beautiful theme (as always).
Fedora 12 x86_64 live CD
Comes up nicely with 1920x1200 resolution using nouveau driver.
I must have pressed enter to wake up the display, as I found myself logged
in without selecting keyboard layout. The default was USA layout. Easy
enough to correct.
Installed to hard drive
Installed on entire drives
Selected Review and modify
Deleted all lvm stuff, built a raid1 device for /home and rebuilt the lvm vg
for swap and /
Creating filesystems took a long time. I would prefer to answer all
questions first so I could leave the PC.
The reboot button on the last screen didn't reboot. Just terminated the
installer.
Rebooted and left.
When I came back the CD tray was ejected and the screen black. Nothing
would wake the screen, so I removed the CD and forcefully rebooted. See the
i686 install below for more info.
Booted nicely, went through firstboot, setting up my local NTP servers, etc.
Set up a local user.
Logged in, and the default keyboard was still USA...
Logged out and selected correct keyboard at login.
Still USA layout after login!
Went to system->preferences->Keyboard. USA was the only layout listed.
Added Norwegian and removed USA.
Logged out and selected my user. The keyboard selector at the login screen
still says USA. Ignored it and entered my password.
Got correct keyboard layout.
Login screen keyboard layout selector seems to not work at all. Keyboard
selection at install doesn't have any effect on the default after install.
No 'desktop effects'. Hope nouveau gets there soon...
Did a yum update and rebooted. Got the superblock in the future error. Yes,
I am east of Greenwich. A lot of us are. Make it part of your testing of
all packages, please. The evolution-mapi connector is full of such time
zone errors as well. I didn't work around this issue, as I was ready to
reinstall.
Fedora 12 i686 live CD
This time I selected Norwegian layout while logging into the live session.
This actually worked.
Installed just like the x86_64 install above. This time I was present while
the system supposedly rebooted. After I typed reboot, the screen went
black, the tray ejected, and then nothing. The system never rebooted. I
assume this was the same with the x86_64 install.
Everything proceeded just like the x86_64 install. They seemed completely
bug-compatible, including the keyboard layout selector at login not doing
much good.
upgraded and rebooted to verify that the file system got updated in the
future. It didn't! The system actually rebooted, but NetworkManager failed
during login. Couldn't find some required resource. The network is up and
running, but no icon.
If this kind of report is interesting, I was planning to do a basic install
tomorrow from the x86_64 DVD, and then a network install. Just testing the
basic installation. I have not been asked to submit smolt profiles during
these installs from the live cd's. I'll do so tomorrow.
--
birger
14 years, 8 months
long standing aggravation
by Gene Czarcinski
I have had a long standing aggravation dealing with anaconda's boot disk order
and how grub is set. When I get things "right", the install and reboot work
fine. Often as not, I don't get it right. But, with a lot of experience with
this problem, the fix is "easy" ... after the install, boot up in rescue mode
and change /boot/grub/grub.conf so that (hdN,i) is set correctly [e.g., change
(hd2,7) to be (hd0,7)] ... then, after chroot'ing to the system run grub-
install /dev/xxxx [such as grub-install /dev/sda8]. The "cost" is that I get
an selinux relabel during the first bootup.
This problem has been BZ'ed a number of times such as --
https://bugzilla.redhat.com/show_bug.cgi?id=431638
https://bugzilla.redhat.com/show_bug.cgi?id=431644
https://bugzilla.redhat.com/show_bug.cgi?id=435878
These reports are generally closed with "live with it, there is not much we
can do" ... just set the boot selection and bios order options to the
"correct" values.
Putting in yet another BZ report does not seem to be very promising.
Therefore, I thought that maybe some discussion on this list (or maybe this
should be on the devel list) might prove more beneficial.
Most of my recent experience has been on my test system where I have installed
Fedora 10, Fedora 11, and Fedora 12-rawhide a number of times.
My hardware:
- ASUS M4A78 PRO mobo
- AMD 940 Phenom processor with 8GB ram.
- one 1.5TB disk (call this scsi0)
- two 1.0TB disks (call them scsi1 and scsi2)
- one DVD drive (call this scsi4).
- plus two NICs and the usual set of other stuff.
BTW, try buying small disks these days .. cost and performance where the
deciding factors ... not storage capacity.
This system is not just dual-boot but is multi-boot ... a single small Fedora
installation on scsi0 with grub installed in scsi0's MBR ... this small system
is used for "emergencies", as a boot selector, and to pre-partition my disks
with LVM.
Besides the "small Fedora", scsi0 has four /boot partitions with the rest of
the disk as physical LVM. This physical LVM has a single volume group with
root1, root2, root3, and root4 logical volumes allocated plus a /home logical
volume. This gives me the ability to have up to four separate installations I
can select to run [I always fresh install, never upgrade]. All installs are
"custom layouts" for disks and edit rather than allocate partitions of logical
volumes.
The other two disks (scsi1 and scsi2) are a single LVM volume group that I use
for data storage such as my collection of iso images and my storage for qemu-
kvm disk images. I could possibly fit everything onto a single drive but
experience with performance says that root and /home need to be separate from
data such as qemu-kvm image files.
When I boot up the BIOS lists the disks as scsi0, scsi1, and scsi2 (not by
those names but in that order ... or at least the 1.5TB is always first and
that is the MBR that is booted.
After booting the F12-Beta DVD in either rescue mode or installation mode, if
I go to VT-2 and do "cat /proc/scsi/scsi", this list is always in the "proper"
order of scsi0, scsi1, and scsi2. But anaconda shows the order as scsi1,
scsi2, and scsi0 (third place).
Note: the physical order that the disk cables are plug into the mobo's SATA
interfaces is scsi0, scsi1, and scsi2.
On at least one occasion installing Fedora (10, 11, or 12 ... I forget which),
the boot partition after installation was "sdc" and it worked!
Naturally, since /etc/fstab has disks referenced by UUID or LVM name, stuff can
shuffle around with no problems. But grub is something else.
While anaconda seems to be pretty much consistent, what is it using to
determine boot order since the list in ./proc/scsi/scsi is the correct order?
If I guess right during the install, everything works. If I guess wrong then
I have to go back and fix things which, like I said, I have lots of experience
doing.
Guessing right is not always as easy as I described above. One system I had
(which I no longer have) had a 120GB PATA disk and a 120GB SATA disk ... the
PATA disk was booted by the BIOS. And then there is the situation where you
have two identical disks.
I am not really python literate so figuring out what anaconda is doing is not
simple for me.
Can someone explain how anaconda figures out boot/disk order and is there some
guarantee that the algorithm will not change between Fedora releases?
Question: should I cross post to the devel list or is the test list sufficient?
Gene
14 years, 8 months
wireless always switched on on boot
by Hassan Ibraheem
Hi,
Fedora (both 11 and rawhide) doesn't remember my wireless connection
state, and *always* turns it on at boot, even if it was turned off
when I booted/rebooted.
I'm using KDE, I don't if it's relevant though.
Ethernet controller: Atheros Communications Inc. AR242x 802.11abg
Wireless PCI Express Adapter (rev 01)
Is this a bug? or something configurable?
--
Hassan Ibraheem
14 years, 8 months
Fedora Test Day Summary - Confined Users
by Eduard Benes
Greetings!
This Tuesday was the "Confined Users" Test Day / Fit&Finish [1] (TD/F&F).
Though we expected higher attendance, the results are really valuable.
The most valuable outcome of a test day could be a fact that we should
bring more attention/people to using/testing SELinux policy and related
tools.
Thanks to all who participated and helped with the organization,
especially to Dan Walsh who promptly started to resolve reported bugs
and already fixed some important issues.
Following bugs were reported during the TD/F&F by the participants:
ID Summary
529873 Openswan/pluto - AVC denials when starting the ipsec service
529870 SELinux is preventing /usr/bin/python "getattr" access on /home/jlaska/.gvfs.
529871 SELinux is preventing /usr/bin/python "connectto" access on /var/run/nscd/socket.
529758 SELinux is preventing /usr/sbin/sendmail.sendmail "module_request" access.
529803 Your system may be seriously compromised! /usr/sbin/nscd attempted to mmap low kernel memory.
529606 SELinux is preventing /usr/sbin/modem-manager "read write" access to device noz0.
529738 SELinux is preventing /lib64/dbus-1/dbus-daemon-launch-helper "execute" access on /usr/sbin/abrtd.
529827 guest_u user not able to run ps
529830 SELinux failed to limit the authority of execute of user_u
529903 SELinux is preventing bash "create" access.
529911 SELinux is preventing nautilus "read write" access on sr0.
529916 AVCs with confined "mailuser" sending e-mail
529933 SELinux is preventing /usr/sbin/abrtd "setattr" access on .abrt.
529934 SELinux is preventing /usr/sbin/abrtd "write" access on /root.
529951 SELinux is preventing the /bin/loadkeys from using potentially mislabeled files (Documents).
529953 hp cups selinux denial
529961 SELinux is preventing /usr/sbin/abrtd "read" access on Bugzilla.conf.
Have a nice day,
/Eduard
[1] - https://fedoraproject.org/wiki/Test_Day:2009-10-20
[2] - http://docs.fedoraproject.org/selinux-user-guide/f10/en-US/sect-Security-...
[3] - http://magazine.redhat.com/2008/07/02/writing-policy-for-confined-selinux...
14 years, 8 months
F12 Beta issues
by Joachim Backes
1. Trying to install F12 Beta from an external USB drive stops (did not
find an install image). On the other hand, installing from an internal
IDE DVD device proceeds.
2. Anaconda crashes after having installed some (or all?) packages.
A traceback is generated: (Remark: I tried to re-install after the first
installation had crashed, so the packages were already installed, but
the error message was the same when installing for the first time).
anaconda 12.37 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/users.py", line 201, in setRootPassword
self.admin.setpassUser(rootUser, cryptPassword(password,
algo=algo), True)
File "/usr/lib/anaconda/instdata.py", line 171, in write
algo=self.getPassAlgo())
File "/usr/lib/anaconda/backend.py", line 305, in writeConfiguration
anaconda.id.write()
File "/usr/lib/anaconda/dispatch.py", line 200, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 123, in gotoNext
self.moveStep()
File "/usr/lib/anaconda/gui.py", line 1195, in nextClicked
self.anaconda.dispatch.gotoNext()
File "/usr/lib/anaconda/iw/progress_gui.py", line 79, in renderCallback
self.intf.icw.nextClicked()
File "/usr/lib/anaconda/gui.py", line 1216, in handleRenderCallback
self.currentWindow.renderCallback()
TypeError: argument 1 must be Entity, not None
The whole traceback has been attached. Somebody has similar problems?
Regards
--
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
http://www.rhrk.uni-kl.de/~backes
14 years, 8 months
first experience with f12 beta
by Riku Seppälä
Hello,
Just installed f12 beta on my infamous HP dv9237eu laptop. I read that
suspend will now work even when you have nvidia graphics adapter.
I try suspend to disk on kde, screen goes black but the cpu fan keeps
rolling. System seems frozen so I have to use power button to shutdown.
Now when I boot I see:
*** An error occured during the file system check.
*** ...
*** ...
*** ...
Give root password for maintenance
(or type Control-D to continue):
Indent looks weird but who cares. Now if I press ANY key I get:
Login incorrect.
Give root password for maintenance
(or type Control-D to continue):
Control-D does not work and I can't type root password. How can I boot
normally?
Riku
14 years, 8 months
checksum/disk theories?
by Tom Horsley
I have the f12 Beta dvd images run through "split -b 1G" on
a vfat usb stick. For both the i36 and the x86_64 images
when I do something like this:
cat Fedora-12-Beta-x86_64-DVD.isoa* > ~/Fedora-12-Beta-x86_64-DVD.iso
The sha256sum -c fails on the resulting file :-(. (The checksums
checked OK on the original files I downloaded).
Then I do this:
cat Fedora-12-Beta-x86_64-DVD.isoaa > ~/Fedora-12-Beta-x86_64-DVD.iso
cat Fedora-12-Beta-x86_64-DVD.isoab >> ~/Fedora-12-Beta-x86_64-DVD.iso
cat Fedora-12-Beta-x86_64-DVD.isoac >> ~/Fedora-12-Beta-x86_64-DVD.iso
cat Fedora-12-Beta-x86_64-DVD.isoad >> ~/Fedora-12-Beta-x86_64-DVD.iso
The resulting file is the same size as the one I got the 1st time,
but this file passes the sha256sum -c.
Has bash started randomly ordering wildcard expansion or something?
Has my usb stick flaked out and only works right when I read the
same set of files twice in a row?
I got the exact same results getting the i386 images off the usb stick
as well.
What is going on?
14 years, 8 months