F21 TC4 Live Workstation install issues

2014-11-26 Thread Zoltan Kota
Hi,

Yesterday I installed F21 TC4 Workstation Live i686 on my relatively old PC.

Booting from the Live DVD was OK, after getting the graphical screen I
chose the install to harddrive option. The installation went quite smooth,
but after rebooting to F21 the booting process stucked resulting in a
dracut prompt.

In the machine there are two hard drives, one ATA and one SATA disk (with
installed F17 and windows on regular partitions). Maybe Anaconda confused
the disks a bit? Booting with an old installation (F17) from an other
partition, I checked grub staff in /boot of F21. In the devices.map both
hard disks were labelled the same (sda or sdb). Changing one of the device
name in this file I could boot F21.
However logging in as a user at the graphical login screen a grey screen
appeared telling that there are problems, try to logout ... This is the
case even if I choose 'Gnome classic'.
My video card is a Radeon 9200SE. Is there any solution for this? Or should
I install eg. LXDE instead of Gnome?

Zoltan
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fwd: F21 nm-openvpn and md5

2014-11-05 Thread Zoltan Kota
I've tried to add the environment variable as you described below, but it
still does not work.

In a virtual machine with F20 I updated the F20 openssl-1.0.1e-40.fc20 to
openssl-1.0.1e-40.fc21. After the update I get the error as expected. But
after adding "Environment="OPENSSL_ENABLE_MD5_VERIFY=1" to
/usr/lib/systemd/system/NetworkManager.service the openvpn connection
started to work.

The same change under F21 does not help, I still get the error.

Zoltan


On Wed, Nov 5, 2014 at 7:53 AM, poma  wrote:

> On 04.11.2014 22:57, Zoltan Kota wrote:
> > Hi,
> >
> > With F21 on, openssl has been patched to disallow verification of
> > certificates that are signed with MD5 algorithm. Until I get our
> sysadmins
> > generate new keys I should use the workaround described as: "a temporary
> > measure the OPENSSL_ENABLE_MD5_VERIFY environment variable can be set to
> > allow verification of certificates signed with MD5 algorithm."
> >
> > On my pre-F21 (test)machine I use gnome with Networkmanager(-openvpn).
> How
> > can I add the above environment variable for Networkmanager?
> >
>
> [openssl] disable verification of certificate, CRL, and OCSP signatures
> using MD5
>
> https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-2013/1144043.html
>
> ⁠Chapter 28. Networking
>
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.0_Release_Notes/Known-Issues-Networking.html
>
> openssl component, BZ#1062656
> It is not possible to connect to any Wi-Fi Protected Access (WPA)
> Enterprise Access Point (AP) that requires MD5-signed certificates. To work
> around this problem, copy the wpa_supplicant.service file from the
> /usr/lib/systemd/system/ directory to the /etc/systemd/system/ directory
> and add the following line to the Service section of the file:
>
> Environment="OPENSSL_ENABLE_MD5_VERIFY"
>
> Then run the systemctl daemon-reload command as root to reload the
> service file.
>
> Important
> Note that MD5 certificates are highly insecure and Red Hat does not
> recommend using them.
>
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Fwd: F21 nm-openvpn and md5

2014-11-04 Thread Zoltan Kota
Hi,

With F21 on, openssl has been patched to disallow verification of
certificates that are signed with MD5 algorithm. Until I get our sysadmins
generate new keys I should use the workaround described as: "a temporary
measure the OPENSSL_ENABLE_MD5_VERIFY environment variable can be set to
allow verification of certificates signed with MD5 algorithm."

On my pre-F21 (test)machine I use gnome with Networkmanager(-openvpn). How
can I add the above environment variable for Networkmanager?

Zoltan
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F17 installation on an Apple Macbook Pro

2012-09-24 Thread Zoltan Kota
On Mon, Sep 24, 2012 at 9:02 AM, Zoltan Kota  wrote:
> Hi,
>
> I've tried to follow the discussions related to Fedora and Apple
> hardware in these lists. Some days ago I decided to try to install F17
> on my Macbook Pro. Maybe it is useful to share my experiences.
>
> The initial state was:
> Apple Macbook Pro 3.1, a Triple-boot system with Mac OSX, WindowsXP,
> Fedora 14, booting through ReFit
> For Fedora I had a separate 'root', 'swap' and 'home' partitiion.
> My plan was to do a fresh installation on the existing root partition
> keeping the home partition as is.
> The istallation media was F17 i386 DVD.
>
> 1. The system booted from DVD correctly, graphical setup was OK.
> 2. At selecting partitions I choose custom setup, and selected my
> existing /, swap, and /home partitions for installation.
> At this point I had to stop, because setup needed a bios boot
> partition that I didn'h have.
> 3. As I didn't want to mess up my partitions completely / to have more
> control, I manipulated my partition table out of the graphical setup.
> I used gdisk in command line from the DVD. I removed my linux root
> partition and created a 1MB Bios boot partition and a new root
> partition. The other partitions were not touched. With gdisk I could
> set the hybrid MBR as well.
> 4. Starting setup again, selecting custom disk layout with grub
> installed on the boot partition, the installation was OK.
> 5. However the hybrid MBR of the disk was cleared. So I had to setup
> again the hybrid MBR with gdisk. After that I could boot all the 3
> systems with ReFit. (ReFit now shows an extra starting icon however,
> that seems to start windows or fedora depending on which one was
> booted last time. I don't know where comes this from.)
> But finally I have bootable Fedora 17 system, hurrah. And my existing
> other OS-es survived. :-)
>
> I think

Soory, accidentally I sent it before I could finish my email.
So, I think would be nice to try F17_x86_64 as well? I have never
tried EFI installation of fedora before. Is it possible to install
grub efi in the root/boot partition during setup? ReFit should find it
as I know.

Zoltan
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

F17 installation on an Apple Macbook Pro

2012-09-24 Thread Zoltan Kota
Hi,

I've tried to follow the discussions related to Fedora and Apple
hardware in these lists. Some days ago I decided to try to install F17
on my Macbook Pro. Maybe it is useful to share my experiences.

The initial state was:
Apple Macbook Pro 3.1, a Triple-boot system with Mac OSX, WindowsXP,
Fedora 14, booting through ReFit
For Fedora I had a separate 'root', 'swap' and 'home' partitiion.
My plan was to do a fresh installation on the existing root partition
keeping the home partition as is.
The istallation media was F17 i386 DVD.

1. The system booted from DVD correctly, graphical setup was OK.
2. At selecting partitions I choose custom setup, and selected my
existing /, swap, and /home partitions for installation.
At this point I had to stop, because setup needed a bios boot
partition that I didn'h have.
3. As I didn't want to mess up my partitions completely / to have more
control, I manipulated my partition table out of the graphical setup.
I used gdisk in command line from the DVD. I removed my linux root
partition and created a 1MB Bios boot partition and a new root
partition. The other partitions were not touched. With gdisk I could
set the hybrid MBR as well.
4. Starting setup again, selecting custom disk layout with grub
installed on the boot partition, the installation was OK.
5. However the hybrid MBR of the disk was cleared. So I had to setup
again the hybrid MBR with gdisk. After that I could boot all the 3
systems with ReFit. (ReFit now shows an extra starting icon however,
that seems to start windows or fedora depending on which one was
booted last time. I don't know where comes this from.)
But finally I have bootable Fedora 17 system, hurrah. And my existing
other OS-es survived. :-)

I think
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora On MacBook Pro

2010-09-07 Thread Zoltan Kota
On Tue, Sep 7, 2010 at 1:01 AM, Jon Hermansen  wrote:
> On Mon, Sep 6, 2010 at 3:47 PM, Bob Cochran  wrote:
>>
>> I don't even know if the MacBook Pro will show a BIOS screen.
>
> Apple provides BIOS emulation, but I'm not sure if it shows the POST output
> you're probably used to. This is how they made their EFI-based systems
> compatible with Windows XP 32-bit (which requires a BIOS).
>
> Linux can boot via native EFI _or_ BIOS emulation.
>
>>
>> Or if it will boot from USB or DVD.
>
>
> It will definitely (at least) boot from CD/DVD. Hold down the Option key
> immediately after you power on your Mac.


You may also find useful infos in search results for 'Macbook Pro
triple boot', for example. :-)

http://darkliquid.co.uk/2009/05/23/macbook-triple-boot-with-osx-leopard-windows-7-and-ubuntu-904/

http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/triple-boot-fedora-on-macbook-pro-787458/

http://blog.christophersmart.com/2009/12/02/how-to-triple-boot-mac-pro-with-os-x-fedora-windows/

Zoltan
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test


Re: Fedora On MacBook Pro

2010-09-06 Thread Zoltan Kota
On Mon, Sep 6, 2010 at 2:37 AM, Bob Cochran  wrote:
>  Is it possible to install Fedora on an Apple MacBook Pro?

Yes, it should be. I have an F13 parallel with MacOSX on my Macbook
Pro (2 years old).
First of all, you can check if you can boot your machine with a Fedora Live CD.

Zoltan
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test


Re: F14 Alpha blank screen during install

2010-08-26 Thread Zoltan Kota
On Fri, Aug 27, 2010 at 12:46 AM, Adam Williamson  wrote:
> On Fri, 2010-08-27 at 00:42 +0200, Zoltan Kota wrote:
>> On Thu, Aug 26, 2010 at 8:14 PM, Adam Williamson  wrote:
>> > On Thu, 2010-08-26 at 09:11 -0400, Clyde E. Kunkel wrote:
>> >> On 08/26/2010 09:00 AM, Zoltan Kota wrote:
>> >> > Hi,
>> >> >
>> >> > I still was not able to install F14 Alpha with netinst.iso. Blank
>> >> > screen after anaconda starts, as described in the F14 Common Bugs wiki
>> >> > page. I have Ati Radeon 9200. As I remember it didn't work with basic
>> >> > video drive either. I will try it again.
>> >> > Is that problem still exist? A new bug was opened in bugzilla yesterday:
>> >> > https://bugzilla.redhat.com/show_bug.cgi?id=627133
>> >> >
>> >> > Can I somehow (help to) resolve the problem?
>> >> >
>> >> > Zoltan
>> >>
>> >> Specify nomodeset in the kernel cmd line.  Known problem and in bz.
>> >
>> > Zoltan's bug doesn't look like the widely-encountered one, I think his
>> > Radeon is a bit too early to hit that. Zoltan, does booting the live CD
>> > work?
>>
>> OK, I could install Alpha in graphic mode after adding the nomodeset
>> parameter at the boot screen.
>> I also tested the live CD, it does boot.
>
> Hmm, so that does sound like the known bug then. But using basic video
> driver didn't work?

No. I have tried again just now. Blank screen with basic video driver.

Zoltan
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test


Re: F14 Alpha blank screen during install

2010-08-26 Thread Zoltan Kota
On Thu, Aug 26, 2010 at 8:14 PM, Adam Williamson  wrote:
> On Thu, 2010-08-26 at 09:11 -0400, Clyde E. Kunkel wrote:
>> On 08/26/2010 09:00 AM, Zoltan Kota wrote:
>> > Hi,
>> >
>> > I still was not able to install F14 Alpha with netinst.iso. Blank
>> > screen after anaconda starts, as described in the F14 Common Bugs wiki
>> > page. I have Ati Radeon 9200. As I remember it didn't work with basic
>> > video drive either. I will try it again.
>> > Is that problem still exist? A new bug was opened in bugzilla yesterday:
>> > https://bugzilla.redhat.com/show_bug.cgi?id=627133
>> >
>> > Can I somehow (help to) resolve the problem?
>> >
>> > Zoltan
>>
>> Specify nomodeset in the kernel cmd line.  Known problem and in bz.
>
> Zoltan's bug doesn't look like the widely-encountered one, I think his
> Radeon is a bit too early to hit that. Zoltan, does booting the live CD
> work?

OK, I could install Alpha in graphic mode after adding the nomodeset
parameter at the boot screen.
I also tested the live CD, it does boot.

Zoltan
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test


F14 Alpha blank screen during install

2010-08-26 Thread Zoltan Kota
Hi,

I still was not able to install F14 Alpha with netinst.iso. Blank
screen after anaconda starts, as described in the F14 Common Bugs wiki
page. I have Ati Radeon 9200. As I remember it didn't work with basic
video drive either. I will try it again.
Is that problem still exist? A new bug was opened in bugzilla yesterday:
https://bugzilla.redhat.com/show_bug.cgi?id=627133

Can I somehow (help to) resolve the problem?

Zoltan
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test


F13 to F14 branched upgrade?

2010-08-17 Thread Zoltan Kota
Hi,

Is there a recommended way  to upgrade my F13 system to F14
(branched/alpha)? I couldn't manage to install F14 alpha RC4 directly
(install failed).

Zoltan
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test