F13 Alpha RC1

[Jim Haynes]

I had the same problem others have reported with non-working mouse and
keybaord when X starts up.

Then I tried to go ahead and install using the basic video system.
I don't know if the following is a bug or if I just don't understand
what I'm doing.  I have on the first disk a working F12 system, an
old F11 system that I can blow away, a swap partition, and a bunch of
free space.

I told it to do a fresh install and use the free space and it said
it couldn't find any free space.  Then I told it to do a fresh
install and use existing space, and I did not see it give me any
choices about the partitioning that was going to be done or even tell
me what it was going to do when it got to where it said it was going
to write new partition data to the disk, so I backed out.  If I had 
been given a choice I would have told it to install in the partition
that currently contains the old F11 system and not touch the working
F12 system. Then I tried telling it to update the F11 system, not what I 
really had in mind to do, and in any case anaconda crashed with that 
selection.

It's been quite a long time since I used the basic video kind of install,
and I don't remember that far back, but seems like it should give me a
lot more control over partitioning, like the X-install does.  Am I
missing some switches that would get me into more detailed control over
partitioning in the basic video system?



jhhaynes at earthlink dot net

[He Rui]

On Sun, 2010-02-21 at 21:36 -0600, Jim Haynes wrote:
>  I had the same problem others have reported with non-working mouse
> and
>  keybaord when X starts up.
>  
>  Then I tried to go ahead and install using the basic video system.
>  I don't know if the following is a bug or if I just don't understand
>  what I'm doing.  I have on the first disk a working F12 system, an
>  old F11 system that I can blow away, a swap partition, and a bunch of
>  free space.
>  
>  I told it to do a fresh install and use the free space and it said
>  it couldn't find any free space.  Then I told it to do a fresh
>  install and use existing space, and I did not see it give me any
>  choices about the partitioning that was going to be done or even tell
>  me what it was going to do when it got to where it said it was going
>  to write new partition data to the disk, so I backed out.  If I had 
>  been given a choice I would have told it to install in the partition
>  that currently contains the old F11 system and not touch the working
>  F12 system. Then I tried telling it to update the F11 system, not what I 
>  really had in mind to do, and in any case anaconda crashed with that 
>  selection.
>  
>  It's been quite a long time since I used the basic video kind of install,
>  and I don't remember that far back, but seems like it should give me a
>  lot more control over partitioning, like the X-install does.  Am I
>  missing some switches that would get me into more detailed control over
>  partitioning in the basic video system?
>  
>  
>  
>  jhhaynes at earthlink dot net
>   
Hi Jim, 

If you do a graphical install, checking 'Review and modify partitioning
layout' at very below of the partitioning page can get you into more
detailed partitioning info. But you cannot review it if using a text
install.

Thanks,
He Rui

-- 
Contacts

FAS Name: Rhe 
Location: Beijing/UTC+8
TEL: [phone]
IRC nick: rhe #fedora-qa #fedora-zh

[Adam Williamson]

On Mon, 2010-02-22 at 14:00 +0800, He Rui wrote:

>  > It's been quite a long time since I used the basic video
> kind of install,
>  > and I don't remember that far back, but seems like it should give me a
>  > lot more control over partitioning, like the X-install does.  Am I
>  > missing some switches that would get me into more detailed control over
>  > partitioning in the basic video system? 
>  Hi Jim, 
>  
>  If you do a graphical install, checking 'Review and modify partitioning
>  layout' at very below of the partitioning page can get you into more
>  detailed partitioning info. But you cannot review it if using a text
>  install. 
Just to expand on that, you (Jim) seem to be confusing 'basic video' and
'text' install. The basic video install is just the graphical installer,
using the 'vesa' driver rather than the native driver for the system's
graphics adapter. Except for the choice of graphics driver, it's exactly
the same as a 'regular' install.

The text mode installer is an entirely different path in anaconda which
was heavily simplified a couple of releases ago, hence the lack of
control you noticed.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

[Jim Haynes]

On Mon, 22 Feb 2010, Adam Williamson wrote:

>  Just to expand on that, you (Jim) seem to be confusing 'basic
> video' and
>  'text' install. The basic video install is just the graphical installer,
>  using the 'vesa' driver rather than the native driver for the system's
>  graphics adapter. Except for the choice of graphics driver, it's exactly
>  the same as a 'regular' install.
>  
Well what actually happens is, if I select Install new system or upgrade
then I run into the already-known bug where the keyboard and mouse are
inoperative.

So I selected Install system with basic video driver and that worked
for a while and then said
X startup failed, falling back to text mode

So I guess that's why basic video and text mode seemed to be the same
thing.

Proceeding in text mode I selected to upgrade an existing system
(F11)  That leads to
     anaconda 13.28 exception report
Traceback (last used call first):
File "/usr/lib/anaconda/text.py"
    line 597, in run
     (file, classNames) =
    stepToClasses [step]
File "/usr/bin/anaconda", line 1191,
    in <module>
   anaconda.intf.run (anaconda)
KeyError: 'cleardiskssel'

I selected debug
since I don't know what to say to the debugger I said quit

It said Install exited abnormally [1/1]
The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete

and that is untrue for Ctrl-C, but does reboot on Ctrl-Alt-Delete

So I guess I might as well sit out RC1 and try again when the X problem
is fixed.

[Adam Williamson]

On Mon, 2010-02-22 at 20:38 -0600, Jim Haynes wrote:

>  So I guess I might as well sit out RC1 and try again when the X
> problem
>  is fixed. 
yeah, that's the best plan all around. We're generally working on the
basis that RC1 is FUBAR, and waiting for RC2 (which will at least need
to fix the anaconda X issue and the selinux issue).
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

[Kevin Kofler]

Adam Williamson wrote:
>  yeah, that's the best plan all around. We're generally
> working on the
>  basis that RC1 is FUBAR, and waiting for RC2 (which will at least need
>  to fix the anaconda X issue and the selinux issue). 
Sadly RC2 still has broken Akonadi:
https://bugzilla.redhat.com/show_bug.cgi?id=566547
(the fix just went to testing). :-(

This makes a big mess out of kdepim.

IMHO this is a blocker, should I add it to the tracker?

        Kevin Kofler

[Jesse Keating]

On Tue, 2010-02-23 at 10:58 +0100, Kevin Kofler wrote:
>  Adam Williamson wrote:
>  > yeah, that's the best plan all around. We're generally working on the
>  > basis that RC1 is FUBAR, and waiting for RC2 (which will at least need
>  > to fix the anaconda X issue and the selinux issue).
>  
>  Sadly RC2 still has broken Akonadi:
>  https://bugzilla.redhat.com/show_bug.cgi?id=566547
>  (the fix just went to testing). :-(
>  
>  This makes a big mess out of kdepim.
>  
>  IMHO this is a blocker, should I add it to the tracker?
>  
>          Kevin Kofler
>   
Yes.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating