Am Tue, 23 Sep 2014 17:14:46 +0200
Dimitry Andric d...@freebsd.org schrieb:
On 23 Sep 2014, at 17:00, Nathan Whitehorn nwhiteh...@freebsd.org wrote:
On 09/23/14 07:28, Harald Schmalzbauer wrote:
Bezüglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime):
…
The problem I reported
Bezüglich O. Hartmann's Nachricht vom 04.10.2014 08:47 (localtime):
…
Sorry, forget the suggestion, it doesn't work since it leads to CFLAG
-march= and the same problem occurs.
For my case this works:
--- sys/boot/efi/Makefile.inc.orig 2014-09-23 16:22:46.0 +0200
+++
Am Tue, 23 Sep 2014 16:51:08 +0200
Harald Schmalzbauer h.schmalzba...@omnilan.de schrieb:
Bezüglich Harald Schmalzbauer's Nachricht vom 23.09.2014 16:28
(localtime):
Bezüglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime):
…
The problem I reported about in the first place is
On Tue, 23 Sep, at 08:00:31AM, Nathan Whitehorn wrote:
Could you try adding -mno-avx2 to /sys/boot/amd64/Makefile.inc line 9?
Do you pull the -mno-redzone flag anywhere? I'm looking through the
loader sources now, and I see that switch in sys/conf/kern.mk, but it
doesn't look like that's being
Bezüglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime):
…
The problem I reported about in the first place is triggered by a faulty
loader.efi that
arises, when optimisation level is -O3. -O2 works fine.
I can confirm that this problem also shows up when using
Bezüglich Harald Schmalzbauer's Nachricht vom 23.09.2014 16:28
(localtime):
Bezüglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime):
…
The problem I reported about in the first place is triggered by a faulty
loader.efi that
arises, when optimisation level is -O3. -O2 works fine.
Could you try adding -mno-avx2 to /sys/boot/amd64/Makefile.inc line 9?
-Nathan
On 09/23/14 07:28, Harald Schmalzbauer wrote:
Bezüglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime):
…
The problem I reported about in the first place is triggered by a faulty
loader.efi that
arises,
On 23 Sep 2014, at 17:00, Nathan Whitehorn nwhiteh...@freebsd.org wrote:
On 09/23/14 07:28, Harald Schmalzbauer wrote:
Bezüglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime):
…
The problem I reported about in the first place is triggered by a faulty
loader.efi that
arises, when
Bezüglich Nathan Whitehorn's Nachricht vom 23.09.2014 17:00 (localtime):
Could you try adding -mno-avx2 to /sys/boot/amd64/Makefile.inc line 9?
Done so, but it doesn't fix the problem with halting loader.efi when
compiled with CPUTYPE=core-avx2.
The whole -mno-xyz isn't applied to
Am Wed, 17 Sep 2014 01:25:07 +0300
Andriy Gapon a...@freebsd.org schrieb:
On 17/09/2014 00:32, Ed Maste wrote:
On 16 September 2014 17:03, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
In that case, is it still /boot/boot1.efifat or is it /boot/boot1.efi?
What is the
difference? Is
On 09/17/2014 00:54, Nathan Whitehorn wrote:
Try xf86-video-scfb instead?
I also had the same problem (mentioned in another thread called
Problems starting X on Mac using vesa, radeon or intel drivers when
running FreeBSD-CURRENT in EFI), and following your suggestion to
install the
Am Tue, 16 Sep 2014 02:05:41 +0200
O. Hartmann ohart...@zedat.fu-berlin.de schrieb:
Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for
UEFI fine.
After I updated the sources to r271649, recompiled world and kernel (as well
as
installed), now I get stuck with
Am Tue, 16 Sep 2014 15:54:31 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/16/14 14:50, O. Hartmann wrote:
Am Tue, 16 Sep 2014 00:09:01 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/15/14 22:51, O. Hartmann wrote:
Am Mon, 15 Sep 2014 17:39:26 -0700
On 16 September 2014 17:50, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
...
hw.vga.textmode=1
hw.vty=sc
(tried also hw.vty=vt).
...
One clarification for the archives: there's no tunable hw.vty, it's
kern.vty. From vt(4):
kern.vty
When both vt and sc(4) have been
On 09/15/14 22:51, O. Hartmann wrote:
Am Mon, 15 Sep 2014 17:39:26 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/15/14 17:36, Allan Jude wrote:
On 2014-09-15 20:05, O. Hartmann wrote:
Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for
UEFI
fine.
On 16 Sep 2014, at 00:05 , O. Hartmann ohart...@zedat.fu-berlin.de wrote:
Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for
UEFI fine.
After I updated the sources to r271649, recompiled world and kernel (as well
as
installed), now I get stuck with the screen
Am Tue, 16 Sep 2014 00:09:01 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/15/14 22:51, O. Hartmann wrote:
Am Mon, 15 Sep 2014 17:39:26 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/15/14 17:36, Allan Jude wrote:
On 2014-09-15 20:05, O. Hartmann wrote:
Am Mon, 15 Sep 2014 20:36:23 -0400
Allan Jude allanj...@freebsd.org schrieb:
On 2014-09-15 20:05, O. Hartmann wrote:
Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works
for UEFI
fine. After I updated the sources to r271649, recompiled world and kernel
(as well
On 16 September 2014 17:03, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
In that case, is it still /boot/boot1.efifat or is it /boot/boot1.efi? What
is the
difference? Is the efi partition FAT?
An EFI system partition (ESP) is a FAT-formatted partition with a
specific GPT or MBR identifier
Am Tue, 16 Sep 2014 00:09:01 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/15/14 22:51, O. Hartmann wrote:
Am Mon, 15 Sep 2014 17:39:26 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/15/14 17:36, Allan Jude wrote:
On 2014-09-15 20:05, O. Hartmann wrote:
Am Tue, 16 Sep 2014 17:32:12 -0400
Ed Maste ema...@freebsd.org schrieb:
On 16 September 2014 17:03, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
In that case, is it still /boot/boot1.efifat or is it /boot/boot1.efi? What
is the
difference? Is the efi partition FAT?
An EFI system
On 17/09/2014 00:32, Ed Maste wrote:
On 16 September 2014 17:03, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
In that case, is it still /boot/boot1.efifat or is it /boot/boot1.efi? What
is the
difference? Is the efi partition FAT?
An EFI system partition (ESP) is a FAT-formatted
Am Wed, 17 Sep 2014 01:25:07 +0300
Andriy Gapon a...@freebsd.org schrieb:
On 17/09/2014 00:32, Ed Maste wrote:
On 16 September 2014 17:03, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
In that case, is it still /boot/boot1.efifat or is it /boot/boot1.efi?
What is the
difference? Is
On 09/16/14 14:50, O. Hartmann wrote:
Am Tue, 16 Sep 2014 00:09:01 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/15/14 22:51, O. Hartmann wrote:
Am Mon, 15 Sep 2014 17:39:26 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/15/14 17:36, Allan Jude wrote:
On
On 16 September 2014 18:25, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
Besides, checking both boot1.efi and loader.efi with file() shows something
like
loader.efi: PE32+ executable (EFI application) x86-64 (stripped to external
PDB), for MS
Windows. So both are PECOFF format files?
On 16 September 2014 18:54, Nathan Whitehorn nwhiteh...@freebsd.org wrote:
On 09/16/14 14:50, O. Hartmann wrote:
When the system boots, I do not see a loader! Where is the loader I'm used
to see when I
have the chance to switch to single user mode, console or switch off ACPI?
There is no
On 2014-09-15 20:05, O. Hartmann wrote:
Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for
UEFI fine.
After I updated the sources to r271649, recompiled world and kernel (as well
as
installed), now I get stuck with the screen message:
FreeBSD EFI boot block
On 09/15/14 17:36, Allan Jude wrote:
On 2014-09-15 20:05, O. Hartmann wrote:
Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for
UEFI fine.
After I updated the sources to r271649, recompiled world and kernel (as well as
installed), now I get stuck with the screen
Am Mon, 15 Sep 2014 17:39:26 -0700
Nathan Whitehorn nwhiteh...@freebsd.org schrieb:
On 09/15/14 17:36, Allan Jude wrote:
On 2014-09-15 20:05, O. Hartmann wrote:
Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works
for UEFI
fine. After I updated the sources to
29 matches
Mail list logo
