Re: [coreboot] kexec --reset-vga from an inteldrmfb frame buffer

[Zoran Stojsavljevic]

Are you using KMS in this setup (KMS - Kernel Mode Setting)?

Excellent material to read:
https://wiki.archlinux.org/index.php/kernel_mode_setting

Zoran

On Tue, Jul 18, 2017 at 5:53 PM, Trammell Hudson  wrote:

> When I have my coreboot payload Linux kernel setup a console framebuffer
> and then kexec into Xen + another kernel, the video glitches out quite
> a bit before falling back to text mode.  The kexec --reset-vga option
> doesn't seem to have any effect.
>
> I read in the docs that kexec and framebuffers don't get along and
> it seems that the patch from 2006 only works with VESA:
>
> https://lkml.org/lkml/2006/7/17/58
>
> My system is using i915 graphics, and there is no option ROM, so I don't
> think it even shows up with any VESA compatible modes.  Is there any
> way to reset the card or to transfer the mode info to the next kernel?
>
> --
> Trammell
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] (depthcharge, vboot) Difficulties booting on Chromebook

[Linus Heckemann]

On 18/07/17 09:13, Paul Kocialkowski wrote:
>> Do you know of any "known-to-work" instructions for setting up a
>> non-chrome OS boot medium that I could compare my setup to or try
>> using
>> instead? Or a way to get more helpful information than a beep from
>> depthcharge?
> 
> I have a cros-medium-setup script that does that:
> https://git.code.paulk.fr/gitweb/?p=libettereboot.git;a=blob;f=projects/cros-scripts/install/cros-medium-setup;h=1865ae36de14aafc610a5e8a81e45e8fed0ee343;hb=HEAD
> 
> You could try to run the paritions action and then cat a known good
> kernel image to the first partition. 

By the looks of it that's pretty much what I've done and I don't see any
differences that could cause it to fail. I'm guessing that leaves the
kernel…

> Alternatively, you can use my whole
> build system:
> http://git.code.paulk.fr/gitweb/?p=libettereboot.git;a=summary
> to build a cros kernel and install it to the storage:
> ./libreboot download linux-cros
> ./libreboot cook linux-cros veyron
> ./libreboot cook cros-scripts
> cd install/cros-scripts/
> ./cros-kernel-prepare pack ../linux-cros-veyron usb
> ./cros-medium-setup partitions /dev/sdfoo
> ./cros-medium-setup kernel /dev/sdfoo ../linux-cros-veyron usb
> 
> That will however take a while to complete. I'm not providing binary
> releases at this point (or any official documentation, really).
> 
> Maybe reading these scripts can help you figure out what is going wrong
> with your setup.

I'll have a look at that, thanks for the pointer. Side note: the git
repo URLs shown by your gitweb are wrong — they contain two slashes
after the domain, and aren't clonable (but taking out the extra slash
fixes it).

Thanks again
Linus

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] kexec --reset-vga from an inteldrmfb frame buffer

[ron minnich]

I had a patch at some point for the kernel which boiled down to "it's
working! keep your hands off it!" and it's fairly simple. But it did
require a change.

On Tue, Jul 18, 2017 at 8:55 AM Trammell Hudson  wrote:

> When I have my coreboot payload Linux kernel setup a console framebuffer
> and then kexec into Xen + another kernel, the video glitches out quite
> a bit before falling back to text mode.  The kexec --reset-vga option
> doesn't seem to have any effect.
>
> I read in the docs that kexec and framebuffers don't get along and
> it seems that the patch from 2006 only works with VESA:
>
> https://lkml.org/lkml/2006/7/17/58
>
> My system is using i915 graphics, and there is no option ROM, so I don't
> think it even shows up with any VESA compatible modes.  Is there any
> way to reset the card or to transfer the mode info to the next kernel?
>
> --
> Trammell
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] kexec --reset-vga from an inteldrmfb frame buffer

[Trammell Hudson]

When I have my coreboot payload Linux kernel setup a console framebuffer
and then kexec into Xen + another kernel, the video glitches out quite
a bit before falling back to text mode.  The kexec --reset-vga option
doesn't seem to have any effect.

I read in the docs that kexec and framebuffers don't get along and
it seems that the patch from 2006 only works with VESA:

https://lkml.org/lkml/2006/7/17/58

My system is using i915 graphics, and there is no option ROM, so I don't
think it even shows up with any VESA compatible modes.  Is there any
way to reset the card or to transfer the mode info to the next kernel?

-- 
Trammell

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Any intro available for adding cbmem support to an old platform?

[Keith Hui]

Hi Paul,

For some reason your replies ended up in junk mail. :-\ I've pulled
them out and can now reply properly. :)

It boots, all the way into Slackware and able to get an SSH
conversation going (for board_status).

On Sat, Jul 15, 2017 at 10:21 AM, Paul Menzel
 wrote:
>
> Thank you for uploading the log files to the board status repository.
> Unfortunately the build is marked as *dirty*, which means, you probably
> had uncommitted changes in the tree, that might or might not have been
> needed to boot the machine. So it’s hard for somebody else rebuilding
> the same image, and it’s less likely that it’ll boot.
>
> `git status` and `git diff`, maybe with the switch `--cached`, could be
> used to find out, what is uncommitted. If you run `make gitconfig`, you
>  will also have the alias `git sup`, which checks out the correct
> commits of the submodules, which are often a reason
>
> If you need help to get rid of the *dirty* state, please don’t hesitate
> to ask.
>
It probably caught the changes I made for what I set out to do (which
are not yet even staged for submission), but the binary I compiled
when I ran board_status is without any of those. The binary now in the
flash chip carries those changes and I can test. I am also staging
them for submission into gerrit (took hours and quite a few tries to
get git right), so it should not be dirty for long.

Cheers
Keith

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] question on libgfxinit DP port number

[Iru Cai]

Thanks, Nico


On 2017年07月18日 16:20, Nico Huber wrote:
> Hi Iru,
>
> On 18.07.2017 09:28, Iru Cai wrote:
>> Hi,
>>
>> I found the mainboard DP port doesn't have output before kernel starts in
>> hp/2570p (https://review.coreboot.org/c/20489/). After I added DP3 and
>> HDMI3 in port list, the DP port had output, and cbmem log said it's DP3.
>> However, xrandr says this port is DP2. What is the problem?
> libgfxinit only knows about physical ports (i.e. how they are ordered*
> in the datasheet). Linux ignores ports that aren't strapped to be active
> (or are disabled by VBT) and renumbers the ports to fill the holes.
>
> Nico
>
> * The numbering is not perfect. As historically VGA was the first port
>   (port A in datasheets), digital ports are counted from B, so DP1 is
>   port B, DP2 is port C, etc.

Now I found /sys/class/drm_dp_aux_dev/drm_dp_aux{0,1} (Linux 4.4) and
`cat /sys/class/drm_dp_aux_dev/*/name` gives me:
  DPDDC-B
  DPDDC-D

So should the ports be DP1 and DP3?

Iru

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] question on libgfxinit DP port number

[Nico Huber]

Hi Iru,

On 18.07.2017 09:28, Iru Cai wrote:
> Hi,
> 
> I found the mainboard DP port doesn't have output before kernel starts in
> hp/2570p (https://review.coreboot.org/c/20489/). After I added DP3 and
> HDMI3 in port list, the DP port had output, and cbmem log said it's DP3.
> However, xrandr says this port is DP2. What is the problem?

libgfxinit only knows about physical ports (i.e. how they are ordered*
in the datasheet). Linux ignores ports that aren't strapped to be active
(or are disabled by VBT) and renumbers the ports to fill the holes.

Nico

* The numbering is not perfect. As historically VGA was the first port
  (port A in datasheets), digital ports are counted from B, so DP1 is
  port B, DP2 is port C, etc.

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] (depthcharge, vboot) Difficulties booting on Chromebook

[Paul Kocialkowski]

On Tue, 2017-07-18 at 08:49 +0100, Linus Heckemann wrote:
> Hi Paul, thanks for your reply.
> 
> On 18/07/17 08:28, Paul Kocialkowski wrote:
> > Hi,
> > 
> > On Tue, 2017-07-18 at 07:24 +0100, Linus Heckemann wrote:
> > > I've been following the instructions for getting Debian running on
> > > an
> > > Asus C201 Chromebook[1]. This has been going well, mostly, except
> > > that
> > > when I try to actually boot it (power on and press Ctrl-U) I am
> > > greeted
> > > by a loud and low-pitched beep and not much else. Any ideas as to
> > > what
> > > I
> > > may be missing?
> > 
> > That probably means that your boot medium was not setup correctly.
> > Perhaps the Debian instructions are either incorrect or incomplete.
> 
> Do you know of any "known-to-work" instructions for setting up a
> non-chrome OS boot medium that I could compare my setup to or try
> using
> instead? Or a way to get more helpful information than a beep from
> depthcharge?

I have a cros-medium-setup script that does that:
https://git.code.paulk.fr/gitweb/?p=libettereboot.git;a=blob;f=projects/cros-scripts/install/cros-medium-setup;h=1865ae36de14aafc610a5e8a81e45e8fed0ee343;hb=HEAD

You could try to run the paritions action and then cat a known good
kernel image to the first partition. Alternatively, you can use my whole
build system:
http://git.code.paulk.fr/gitweb/?p=libettereboot.git;a=summary
to build a cros kernel and install it to the storage:
./libreboot download linux-cros
./libreboot cook linux-cros veyron
./libreboot cook cros-scripts
cd install/cros-scripts/
./cros-kernel-prepare pack ../linux-cros-veyron usb
./cros-medium-setup partitions /dev/sdfoo
./cros-medium-setup kernel /dev/sdfoo ../linux-cros-veyron usb

That will however take a while to complete. I'm not providing binary
releases at this point (or any official documentation, really).

Maybe reading these scripts can help you figure out what is going wrong
with your setup.

> > > Relevant stuff:
> > > 
> > > # crossystem | grep dev_boot
> > > dev_boot_usb   = 1   # Enable developer mode boot from
> > > USB/SD
> > > (writable)
> > > dev_boot_legacy= 0   # Enable developer mode boot Legacy
> > > OSes
> > > (writable)
> > > dev_boot_signed_only   = 0   # Enable developer mode boot only
> > > from
> > > official kernels (writable)
> > > 
> > > I've uploaded an image of the SD card resulting from the
> > > instructions
> > > (208M, 2G uncompressed) at [2].
> > > 
> > > Best regards
> > > Linus
> > > 
> > > 
> > > [1]: https://wiki.debian.org/InstallingDebianOn/Asus/C201
> > > [2]: https://sphalerite.org/chromebook-debian-boot-sd.img.gz
> 
> 
-- 
Paul Kocialkowski,

developer of free digital technology and hardware support

Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] (depthcharge, vboot) Difficulties booting on Chromebook

[Linus Heckemann]

Hi Paul, thanks for your reply.

On 18/07/17 08:28, Paul Kocialkowski wrote:
> Hi,
> 
> On Tue, 2017-07-18 at 07:24 +0100, Linus Heckemann wrote:
>> I've been following the instructions for getting Debian running on an
>> Asus C201 Chromebook[1]. This has been going well, mostly, except that
>> when I try to actually boot it (power on and press Ctrl-U) I am
>> greeted
>> by a loud and low-pitched beep and not much else. Any ideas as to what
>> I
>> may be missing?
> 
> That probably means that your boot medium was not setup correctly.
> Perhaps the Debian instructions are either incorrect or incomplete.

Do you know of any "known-to-work" instructions for setting up a
non-chrome OS boot medium that I could compare my setup to or try using
instead? Or a way to get more helpful information than a beep from
depthcharge?

>> Relevant stuff:
>>
>> # crossystem | grep dev_boot
>> dev_boot_usb   = 1   # Enable developer mode boot from USB/SD
>> (writable)
>> dev_boot_legacy= 0   # Enable developer mode boot Legacy OSes
>> (writable)
>> dev_boot_signed_only   = 0   # Enable developer mode boot only from
>> official kernels (writable)
>>
>> I've uploaded an image of the SD card resulting from the instructions
>> (208M, 2G uncompressed) at [2].
>>
>> Best regards
>> Linus
>>
>>
>> [1]: https://wiki.debian.org/InstallingDebianOn/Asus/C201
>> [2]: https://sphalerite.org/chromebook-debian-boot-sd.img.gz
> 


-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] (depthcharge, vboot) Difficulties booting on Chromebook

[Paul Kocialkowski]

Hi,

On Tue, 2017-07-18 at 07:24 +0100, Linus Heckemann wrote:
> I've been following the instructions for getting Debian running on an
> Asus C201 Chromebook[1]. This has been going well, mostly, except that
> when I try to actually boot it (power on and press Ctrl-U) I am
> greeted
> by a loud and low-pitched beep and not much else. Any ideas as to what
> I
> may be missing?

That probably means that your boot medium was not setup correctly.
Perhaps the Debian instructions are either incorrect or incomplete.

> Relevant stuff:
> 
> # crossystem | grep dev_boot
> dev_boot_usb   = 1   # Enable developer mode boot from USB/SD
> (writable)
> dev_boot_legacy= 0   # Enable developer mode boot Legacy OSes
> (writable)
> dev_boot_signed_only   = 0   # Enable developer mode boot only from
> official kernels (writable)
> 
> I've uploaded an image of the SD card resulting from the instructions
> (208M, 2G uncompressed) at [2].
> 
> Best regards
> Linus
> 
> 
> [1]: https://wiki.debian.org/InstallingDebianOn/Asus/C201
> [2]: https://sphalerite.org/chromebook-debian-boot-sd.img.gz

-- 
Paul Kocialkowski,

developer of free digital technology and hardware support

Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] question on libgfxinit DP port number

[Iru Cai]

Hi,

I found the mainboard DP port doesn't have output before kernel starts in
hp/2570p (https://review.coreboot.org/c/20489/). After I added DP3 and
HDMI3 in port list, the DP port had output, and cbmem log said it's DP3.
However, xrandr says this port is DP2. What is the problem?

I also checked lenovo/x230, but the port named DP2 in xrandr or
/sys/class/drm/card0-DP-2 is also shown as DP2 in cbmem log.

Thanks,
Iru

-- 
Please do not send me Microsoft Office/Apple iWork documents. Send
OpenDocument instead! http://fsf.org/campaigns/opendocument/
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Wiki page for Lenovo Thinkpad W520

[Iru Cai]

Hi Charlotte,

On Tue, Jul 18, 2017 at 1:37 PM, Charlotte Plusplus <
pluspluscharlo...@gmail.com> wrote:

> Hello
>
> I would be very happy to help with pictures, source, binaries, info etc.
> But since Denver, I have been just a bit behind. Too many side projects :-)
>
> Anyway, I will get back in touch soon. If you use my previously released
> binary, you should be fine.
>
> The port to the current coreboot I did in Denver has new ram issues that I
> am investigating. It may need again some dirty workarounds, like adding +1
> or +2 to some SPD settings to get memtest work without any failure.
> Optimus is still not working yet.
>

Maybe you need to rebase your code on master coreboot, which has some
improvements on Sandy/Ivy Bridge RAM init. There's also some changes in the
codebase.

Iru


> Thanks
> Charlotte
>
>
> On Sun, Jul 16, 2017 at 8:49 AM, Nico Rikken  wrote:
>
>> I created a wiki page for the Lenovo W520 based on information shared
>> on this mailinglist:
>>
>> https://www.coreboot.org/Board:lenovo/w520
>>
>> I hope others can contribute more details, so I can benefit when taking
>> on the challenge of flashing a W520 myself.
>>
>> Kind regards,
>> Nico Rikken (NL)
>>
>
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
>



-- 
Please do not send me Microsoft Office/Apple iWork documents. Send
OpenDocument instead! http://fsf.org/campaigns/opendocument/
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] (depthcharge, vboot) Difficulties booting on Chromebook

[Linus Heckemann]

Hi all,

I've been following the instructions for getting Debian running on an
Asus C201 Chromebook[1]. This has been going well, mostly, except that
when I try to actually boot it (power on and press Ctrl-U) I am greeted
by a loud and low-pitched beep and not much else. Any ideas as to what I
may be missing?

Relevant stuff:

# crossystem | grep dev_boot
dev_boot_usb   = 1   # Enable developer mode boot from USB/SD
(writable)
dev_boot_legacy= 0   # Enable developer mode boot Legacy OSes
(writable)
dev_boot_signed_only   = 0   # Enable developer mode boot only from
official kernels (writable)

I've uploaded an image of the SD card resulting from the instructions
(208M, 2G uncompressed) at [2].

Best regards
Linus


[1]: https://wiki.debian.org/InstallingDebianOn/Asus/C201
[2]: https://sphalerite.org/chromebook-debian-boot-sd.img.gz

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot