On Sun, May 14, 2017 at 07:31:09PM +0900, YASUOKA Masahiko wrote:
> On Fri, 12 May 2017 16:15:52 +0200
>
> It seems the problem which had been fixed previous is happening again.
> Does efidev.c have following $OpenBSD$?
>
> /* $OpenBSD: efidev.c,v 1.25 2017/05/11 01:37:24 yasuoka Exp $
On Fri, 12 May 2017 16:15:52 +0200
Michele Curti wrote:
> On Fri, May 12, 2017 at 06:01:35PM +0900, YASUOKA Masahiko wrote:
>> > And something like this?
>>
>> Yes. What we need to do is comparing the device path node before
>> MEDIA_DEVICE_PATH type. So I rewrote it like
>>
>> media_idx = d
On Fri, May 12, 2017 at 06:01:35PM +0900, YASUOKA Masahiko wrote:
>
> > And something like this?
>
> Yes. What we need to do is comparing the device path node before
> MEDIA_DEVICE_PATH type. So I rewrote it like
>
> media_idx = device_path_index(rootdp, MEDIA_DEVICE_PATH);
> for (...)
>
On Fri, 12 May 2017 09:33:04 +0200
Michele Curti wrote:
> On Fri, May 12, 2017 at 07:27:45AM +0200, Michele Curti wrote:
>>
>> The efi_device_path_cmp() compares only a path node.
>> I tried the following diff just to see if I undestood something,
>> hd0 is now set corrctly to the 29GB disk.
>>
On Fri, May 12, 2017 at 07:27:45AM +0200, Michele Curti wrote:
>
> The efi_device_path_cmp() compares only a path node.
> I tried the following diff just to see if I undestood something,
> hd0 is now set corrctly to the 29GB disk.
>
>
> Index: efiboot/efiboot.c
> ===
On Fri, May 12, 2017 at 11:05:13AM +0900, YASUOKA Masahiko wrote:
> On Thu, 11 May 2017 23:45:17 +0200
> Michele Curti wrote:
>
> All disks are identical in HARDWARE_DEVICE_PATH and ACPI_DEVICE_PATH
> and they all don't have MESSAGING_DEVICE_PATH. So the boot loader
> mistakenly treats all of th
On Thu, 11 May 2017 23:45:17 +0200
Michele Curti wrote:
> On Wed, May 10, 2017 at 08:35:28PM +0200, Patrick Wildt wrote:
>>
>> I don't think this is the correct fix. It might solve your issue, but I
>> don't think it's completely right. So EFI has those so called device
>> paths. A path is bas
On Wed, May 10, 2017 at 08:35:28PM +0200, Patrick Wildt wrote:
>
> I don't think this is the correct fix. It might solve your issue, but I
> don't think it's completely right. So EFI has those so called device
> paths. A path is basically a list of nodes. To compare two paths you
> need to com
On Thu, May 11, 2017 at 05:48:34PM +0900, YASUOKA Masahiko wrote:
> Hi,
>
> Thank you for your tests,
>
> On Thu, 11 May 2017 07:40:42 +0200
>
...
> > So I can use the stock bootloader without changes but I must do a
> >
> > boot> set device hd2a
>
> I'm not clear whether we still have a prob
Hi,
Thank you for your tests,
On Thu, 11 May 2017 07:40:42 +0200
Michele Curti wrote:
> On Wed, May 10, 2017 at 08:35:28PM +0200, Patrick Wildt wrote:
>> On Wed, May 10, 2017 at 03:14:30PM +0200, Stefan Sperling wrote:
>> > On Tue, May 09, 2017 at 09:47:14PM +0200, Michele Curti wrote:
>> > > On
On Wed, May 10, 2017 at 08:35:28PM +0200, Patrick Wildt wrote:
> On Wed, May 10, 2017 at 03:14:30PM +0200, Stefan Sperling wrote:
> > On Tue, May 09, 2017 at 09:47:14PM +0200, Michele Curti wrote:
> > > On Tue, May 09, 2017 at 09:36:02PM +0200, Michele Curti wrote:
> > > > On Tue, May 09, 2017 at 1
On Thu, May 11, 2017 at 10:42:04AM +0900, YASUOKA Masahiko wrote:
> Hi,
>
> On Tue, 9 May 2017 10:20:03 +0200
> Michele Curti wrote:
> > I also tried a fresh install, but things do not change.
> > Boot fails and when I do a "machine diskinfo" I got a lot of "?"
> > symbols (a video here https://
Hi,
On Tue, 9 May 2017 10:20:03 +0200
Michele Curti wrote:
> I also tried a fresh install, but things do not change.
> Boot fails and when I do a "machine diskinfo" I got a lot of "?"
> symbols (a video here https://www.youtube.com/watch?v=fsomNX-oFTQ )
Hanging on "machine diskinfo" seems to be
On Wed, May 10, 2017 at 08:35:28PM +0200, Patrick Wildt wrote:
> On Wed, May 10, 2017 at 03:14:30PM +0200, Stefan Sperling wrote:
> > On Tue, May 09, 2017 at 09:47:14PM +0200, Michele Curti wrote:
> > > bios_bootdev = 0x80;
> > > - efi_bootdp = dp0;
On Wed, May 10, 2017 at 03:14:30PM +0200, Stefan Sperling wrote:
> On Tue, May 09, 2017 at 09:47:14PM +0200, Michele Curti wrote:
> > On Tue, May 09, 2017 at 09:36:02PM +0200, Michele Curti wrote:
> > > On Tue, May 09, 2017 at 10:20:03AM +0200, Michele Curti wrote:
> > > > Hi all, I tried to upgrad
On Tue, May 09, 2017 at 09:47:14PM +0200, Michele Curti wrote:
> On Tue, May 09, 2017 at 09:36:02PM +0200, Michele Curti wrote:
> > On Tue, May 09, 2017 at 10:20:03AM +0200, Michele Curti wrote:
> > > Hi all, I tried to upgrade to OpenBSD 6.1 on an Asus X205TA (bay
> > > trail, 32 bit efi, 64 bit o
On Tue, May 09, 2017 at 09:36:02PM +0200, Michele Curti wrote:
> On Tue, May 09, 2017 at 10:20:03AM +0200, Michele Curti wrote:
> > Hi all, I tried to upgrade to OpenBSD 6.1 on an Asus X205TA (bay
> > trail, 32 bit efi, 64 bit os) but the bootloader do not correctly
> > detect the internal disk.
>
On Tue, May 09, 2017 at 10:20:03AM +0200, Michele Curti wrote:
> Hi all,
> I tried to upgrade to OpenBSD 6.1 on an Asus X205TA (bay trail, 32 bit
> efi, 64 bit os) but the bootloader do not correctly detect the internal
> disk.
>
> I also tried a fresh install, but things do not change.
> Boot fai
Hi all,
I tried to upgrade to OpenBSD 6.1 on an Asus X205TA (bay trail, 32 bit
efi, 64 bit os) but the bootloader do not correctly detect the internal
disk.
I also tried a fresh install, but things do not change.
Boot fails and when I do a "machine diskinfo" I got a lot of "?"
symbols (a video he
19 matches
Mail list logo
