On Mon, 27 Mar 2017, Andrei Borzenkov wrote:
> 27.03.2017 15:41, Colin Watson пишет:
> > I guess that the attached bug happens because grub_install_register_efi
> > is called on non-biosdisk-ish systems but uses
> > grub_util_biosdisk_get_osdev to get an OS device name for
> > efidir_grub_dev->dis
On Mon, Mar 27, 2017 at 11:29:48PM +0530, Gailu Singh wrote:
> Can you please let me know how following three values are calculated in
> your patch. I am trying to understand how do I change it for my board.
>
> port->board.base_baud = 400;
> port->board.port_offset = 0x200;
>
Hi Matthias,
Can you please let me know how following three values are calculated in
your patch. I am trying to understand how do I change it for my board.
port->board.base_baud = 400;
port->board.port_offset = 0x200;
port->board.base_offset = 0x1000;
On Fri, Mar 24, 2017
27.03.2017 17:12, Nando Eva пишет:
> OK, I found the cause if the problem:
> - the ACPI tables specified to the 'acpi' command are loaded to new addresses
> and a new RSDT and XSDT created with pointers to them. This can be confirmed
> by the 'lsacpi' command.
>
> - the RSDP isn't updated to poi
27.03.2017 15:41, Colin Watson пишет:
> I guess that the attached bug happens because grub_install_register_efi
> is called on non-biosdisk-ish systems but uses
> grub_util_biosdisk_get_osdev to get an OS device name for
> efidir_grub_dev->disk, which isn't going to work so well. I'm a bit
> rusty
OK, I found the cause if the problem:
- the ACPI tables specified to the 'acpi' command are loaded to new addresses
and a new RSDT and XSDT created with pointers to them. This can be confirmed by
the 'lsacpi' command.
- the RSDP isn't updated to point to the new RSDT and XSDT.
So when chainloa
On Mon, 27 Mar 2017, Andrei Borzenkov wrote:
> Link to the bug report would be helpful. I assume it contains actual
> invocation with arguments, I do not see them in this mail.
see https://bugs.debian.org/858832
--
| .''`. ** Debian **
Peter Palfrader
Hi
I've had trouble with booting my system recently and have had to edit the
parameters during boot. I have a long boot line (kernel text + 115 chars of
optional params) and getting to the right place (about char 80) is very
tedious. The key repeat seems to be very slow. It also buffers the ke
Link to the bug report would be helpful. I assume it contains actual
invocation with arguments, I do not see them in this mail.
On Mon, Mar 27, 2017 at 3:41 PM, Colin Watson wrote:
> I guess that the attached bug happens because grub_install_register_efi
> is called on non-biosdisk-ish systems bu
I guess that the attached bug happens because grub_install_register_efi
is called on non-biosdisk-ish systems but uses
grub_util_biosdisk_get_osdev to get an OS device name for
efidir_grub_dev->disk, which isn't going to work so well. I'm a bit
rusty here - would anyone care to venture a guess at
10 matches
Mail list logo
