coreboot July 2016

coreboot@coreboot.org

47 participants
135 discussions

Re: [coreboot] w83627 uart port is not workable with coreboot in linux
by cheng yichen 25 Jul '16

25 Jul '16

Hi Zoran TTYS1 is also not workable. I also change io resource from 3f8 to 3e8 irq from 4 to 5. but result is the same. Thank you 2016-07-25 13:57 GMT+08:00 Zoran Stojsavljevic < zoran.stojsavljevic(a)gmail.com>: > Hello Chen, > > I see. Also learning, reading and trying to get to the root of the problem. > > > [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) > is a 16550A > > [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = > 115200) is a 16550A > > Please, try to experiment with ttyS1. But I guess, you already know what I > just wrote. Maybe this also can help: > http://forums.debian.net/viewtopic.php?f=7&t=111355 > > Zoran > > On Mon, Jul 25, 2016 at 7:08 AM, cheng yichen <blessyichen(a)gmail.com> > wrote: > >> Hi Zoran >> >> The ttyS0 is superIo uart. Because I add uart asl code in coreboot system >> will show "00:05: ttyS0" >> If I remove asl code system will show "serial8250:ttty" Thank you >> >> 2016-07-25 12:10 GMT+08:00 Zoran Stojsavljevic < >> zoran.stojsavljevic(a)gmail.com>: >> >>> > home# dmesg | grep -i tty >>> > [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >>> root=UUID=b2b7f7fa-b1db-4e97- >>> > 941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet splash >>> vt.handoff=7 >>> > [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >>> root=UUID=b2b7f7fa-b1db- >>> > 4e97-941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet >>> splash vt.handoff=7 >>> > [ 0.000000] console [tty1] enabled >>> > [ 0.000000] console [ttyS0] enabled >>> > [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = >>> 115200) is a 16550A >>> > [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = >>> 115200) is a 16550A >>> > [ 3.412478] fbcon: Remapping primary device, fb1, to tty 1-63 >>> > [ 44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice. >>> > [ 44.380198] systemd[1]: Created slice system-getty.slice. >>> _______ >>> >>> Hello Cheng, >>> >>> Please, try to do the following: lspci -vv (to find your serial on >>> PCIe), then try to remap your IRQs, to see if this will somehow work. >>> >>> Example: >>> setserial /dev/ttyS0 port 0xd800 UART 16550A irq 5 >>> setserial /dev/ttyS0 -av >>> /dev/ttyS0, Line 0, UART: 16550A, Port: 0xd800, IRQ: 5 >>> Baud_base: 115200, close_delay: 5000, divisor: 0 >>> closing_wait: 37856 >>> Flags: spd_normal skip_test >>> >>> Something like described on this web pointer: >>> https://forums.gentoo.org/viewtopic-t-249041-start-0.html >>> >>> Please, report your attempts/results here. >>> >>> Thank you, >>> Zoran >>> >>> On Mon, Jul 25, 2016 at 4:33 AM, cheng yichen <blessyichen(a)gmail.com> >>> wrote: >>> >>>> Hi all >>>> >>>> After i follow kontron/ktqm77 setting. I can't solve the issue. >>>> I try to change iqr(for com1) to 5 or 6. but system can't print linux >>>> message and minicom is not workable. >>>> >>>> >>>> >>>> dump from superiotool >>>> Found Winbond W83627DHG-P/-PT (id=0xb0, rev=0x73) at 0x2e >>>> Register dump: >>>> idx 02 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f >>>> val ff b0 73 ff 00 42 00 00 ff 50 80 00 00 eb 21 00 ff >>>> def 00 b0 NA ff 00 MM 00 MM RR 50 00 00 RR e2 21 00 00 >>>> LDN 0x00 (Floppy) >>>> idx 30 60 61 70 74 f0 f1 f2 f4 f5 >>>> val 01 03 f0 06 02 8e 00 ff 00 00 >>>> def 01 03 f0 06 02 8e 00 ff 00 00 >>>> LDN 0x01 (Parallel port) >>>> idx 30 60 61 70 74 f0 >>>> val 01 03 78 07 04 3f >>>> def 01 03 78 07 04 3f >>>> LDN 0x02 (COM1) >>>> idx 30 60 61 70 f0 >>>> val 01 03 f8 04 40 >>>> def 01 03 f8 04 00 >>>> LDN 0x03 (COM2) >>>> idx 30 60 61 70 f0 f1 >>>> val 01 02 f8 03 40 00 >>>> def 01 02 f8 03 00 00 >>>> LDN 0x05 (Keyboard) >>>> >>>> >>>> dump from dmesg >>>> >>>> home# dmesg | grep -i tty >>>> [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >>>> root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 >>>> console=ttyS0,115200n8 quiet splash vt.handoff=7 >>>> [ 0.000000] Kernel command line: >>>> BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >>>> root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 >>>> console=ttyS0,115200n8 quiet splash vt.handoff=7 >>>> [ 0.000000] console [tty1] enabled >>>> [ 0.000000] console [ttyS0] enabled >>>> [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) >>>> is a 16550A >>>> [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = >>>> 115200) is a 16550A >>>> [ 3.412478] fbcon: Remapping primary device, fb1, to tty 1-63 >>>> [ 44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice. >>>> [ 44.380198] systemd[1]: Created slice system-getty.slice. >>>> >>>> >>>> >>>> >>>> >>>> 2016-07-22 20:24 GMT+08:00 Kyösti Mälkki <kyosti.malkki(a)gmail.com>: >>>> >>>>> On Fri, Jul 22, 2016 at 1:14 PM, cheng yichen <blessyichen(a)gmail.com> >>>>> wrote: >>>>> > Hi all >>>>> > >>>>> > My platform is braswell SOC with W83627dhg superIO. In post stage I >>>>> can get >>>>> > debug message over w83627 uart1(3f8/irq4). but after boot to linux, >>>>> uart >>>>> > port is not woarkable. I test the function by minicom but I can't >>>>> receive >>>>> > and send data. I can get uart information by dmesg command. >>>>> > How to initial it in corebooot? >>>>> >>>>> Does not sound like a coreboot issue to me. >>>>> >>>>> Do you have CTS/RTS hardware handshake disabled in minicom >>>>> configuration? If you directed kernel console to serial port, you >>>>> should not (cannot) use the port for user apps. >>>>> >>>>> HTH, >>>>> Kyösti >>>>> >>>> >>>> >>>> -- >>>> coreboot mailing list: coreboot(a)coreboot.org >>>> https://www.coreboot.org/mailman/listinfo/coreboot >>>> >>> >>> >> >

1 0

Re: [coreboot] w83627 uart port is not workable with coreboot in linux
by Zoran Stojsavljevic 25 Jul '16

25 Jul '16

Hello Chen, I see. Also learning, reading and trying to get to the root of the problem. > [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A > [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A Please, try to experiment with ttyS1. But I guess, you already know what I just wrote. Maybe this also can help: http://forums.debian.net/viewtopic.php?f=7&t=111355 Zoran On Mon, Jul 25, 2016 at 7:08 AM, cheng yichen <blessyichen(a)gmail.com> wrote: > Hi Zoran > > The ttyS0 is superIo uart. Because I add uart asl code in coreboot system > will show "00:05: ttyS0" > If I remove asl code system will show "serial8250:ttty" Thank you > > 2016-07-25 12:10 GMT+08:00 Zoran Stojsavljevic < > zoran.stojsavljevic(a)gmail.com>: > >> > home# dmesg | grep -i tty >> > [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >> root=UUID=b2b7f7fa-b1db-4e97- >> > 941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet splash >> vt.handoff=7 >> > [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >> root=UUID=b2b7f7fa-b1db- >> > 4e97-941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet >> splash vt.handoff=7 >> > [ 0.000000] console [tty1] enabled >> > [ 0.000000] console [ttyS0] enabled >> > [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) >> is a 16550A >> > [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = >> 115200) is a 16550A >> > [ 3.412478] fbcon: Remapping primary device, fb1, to tty 1-63 >> > [ 44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice. >> > [ 44.380198] systemd[1]: Created slice system-getty.slice. >> _______ >> >> Hello Cheng, >> >> Please, try to do the following: lspci -vv (to find your serial on PCIe), >> then try to remap your IRQs, to see if this will somehow work. >> >> Example: >> setserial /dev/ttyS0 port 0xd800 UART 16550A irq 5 >> setserial /dev/ttyS0 -av >> /dev/ttyS0, Line 0, UART: 16550A, Port: 0xd800, IRQ: 5 >> Baud_base: 115200, close_delay: 5000, divisor: 0 >> closing_wait: 37856 >> Flags: spd_normal skip_test >> >> Something like described on this web pointer: >> https://forums.gentoo.org/viewtopic-t-249041-start-0.html >> >> Please, report your attempts/results here. >> >> Thank you, >> Zoran >> >> On Mon, Jul 25, 2016 at 4:33 AM, cheng yichen <blessyichen(a)gmail.com> >> wrote: >> >>> Hi all >>> >>> After i follow kontron/ktqm77 setting. I can't solve the issue. >>> I try to change iqr(for com1) to 5 or 6. but system can't print linux >>> message and minicom is not workable. >>> >>> >>> >>> dump from superiotool >>> Found Winbond W83627DHG-P/-PT (id=0xb0, rev=0x73) at 0x2e >>> Register dump: >>> idx 02 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f >>> val ff b0 73 ff 00 42 00 00 ff 50 80 00 00 eb 21 00 ff >>> def 00 b0 NA ff 00 MM 00 MM RR 50 00 00 RR e2 21 00 00 >>> LDN 0x00 (Floppy) >>> idx 30 60 61 70 74 f0 f1 f2 f4 f5 >>> val 01 03 f0 06 02 8e 00 ff 00 00 >>> def 01 03 f0 06 02 8e 00 ff 00 00 >>> LDN 0x01 (Parallel port) >>> idx 30 60 61 70 74 f0 >>> val 01 03 78 07 04 3f >>> def 01 03 78 07 04 3f >>> LDN 0x02 (COM1) >>> idx 30 60 61 70 f0 >>> val 01 03 f8 04 40 >>> def 01 03 f8 04 00 >>> LDN 0x03 (COM2) >>> idx 30 60 61 70 f0 f1 >>> val 01 02 f8 03 40 00 >>> def 01 02 f8 03 00 00 >>> LDN 0x05 (Keyboard) >>> >>> >>> dump from dmesg >>> >>> home# dmesg | grep -i tty >>> [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >>> root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 >>> console=ttyS0,115200n8 quiet splash vt.handoff=7 >>> [ 0.000000] Kernel command line: >>> BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >>> root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 >>> console=ttyS0,115200n8 quiet splash vt.handoff=7 >>> [ 0.000000] console [tty1] enabled >>> [ 0.000000] console [ttyS0] enabled >>> [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) >>> is a 16550A >>> [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = >>> 115200) is a 16550A >>> [ 3.412478] fbcon: Remapping primary device, fb1, to tty 1-63 >>> [ 44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice. >>> [ 44.380198] systemd[1]: Created slice system-getty.slice. >>> >>> >>> >>> >>> >>> 2016-07-22 20:24 GMT+08:00 Kyösti Mälkki <kyosti.malkki(a)gmail.com>: >>> >>>> On Fri, Jul 22, 2016 at 1:14 PM, cheng yichen <blessyichen(a)gmail.com> >>>> wrote: >>>> > Hi all >>>> > >>>> > My platform is braswell SOC with W83627dhg superIO. In post stage I >>>> can get >>>> > debug message over w83627 uart1(3f8/irq4). but after boot to linux, >>>> uart >>>> > port is not woarkable. I test the function by minicom but I can't >>>> receive >>>> > and send data. I can get uart information by dmesg command. >>>> > How to initial it in corebooot? >>>> >>>> Does not sound like a coreboot issue to me. >>>> >>>> Do you have CTS/RTS hardware handshake disabled in minicom >>>> configuration? If you directed kernel console to serial port, you >>>> should not (cannot) use the port for user apps. >>>> >>>> HTH, >>>> Kyösti >>>> >>> >>> >>> -- >>> coreboot mailing list: coreboot(a)coreboot.org >>> https://www.coreboot.org/mailman/listinfo/coreboot >>> >> >> >

1 0

Re: [coreboot] w83627 uart port is not workable with coreboot in linux
by cheng yichen 25 Jul '16

25 Jul '16

Hi Zoran The ttyS0 is superIo uart. Because I add uart asl code in coreboot system will show "00:05: ttyS0" If I remove asl code system will show "serial8250:ttty" Thank you 2016-07-25 12:10 GMT+08:00 Zoran Stojsavljevic < zoran.stojsavljevic(a)gmail.com>: > > home# dmesg | grep -i tty > > [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic > root=UUID=b2b7f7fa-b1db-4e97- > > 941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet splash > vt.handoff=7 > > [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic > root=UUID=b2b7f7fa-b1db- > > 4e97-941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet > splash vt.handoff=7 > > [ 0.000000] console [tty1] enabled > > [ 0.000000] console [ttyS0] enabled > > [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) > is a 16550A > > [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = > 115200) is a 16550A > > [ 3.412478] fbcon: Remapping primary device, fb1, to tty 1-63 > > [ 44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice. > > [ 44.380198] systemd[1]: Created slice system-getty.slice. > _______ > > Hello Cheng, > > Please, try to do the following: lspci -vv (to find your serial on PCIe), > then try to remap your IRQs, to see if this will somehow work. > > Example: > setserial /dev/ttyS0 port 0xd800 UART 16550A irq 5 > setserial /dev/ttyS0 -av > /dev/ttyS0, Line 0, UART: 16550A, Port: 0xd800, IRQ: 5 > Baud_base: 115200, close_delay: 5000, divisor: 0 > closing_wait: 37856 > Flags: spd_normal skip_test > > Something like described on this web pointer: > https://forums.gentoo.org/viewtopic-t-249041-start-0.html > > Please, report your attempts/results here. > > Thank you, > Zoran > > On Mon, Jul 25, 2016 at 4:33 AM, cheng yichen <blessyichen(a)gmail.com> > wrote: > >> Hi all >> >> After i follow kontron/ktqm77 setting. I can't solve the issue. >> I try to change iqr(for com1) to 5 or 6. but system can't print linux >> message and minicom is not workable. >> >> >> >> dump from superiotool >> Found Winbond W83627DHG-P/-PT (id=0xb0, rev=0x73) at 0x2e >> Register dump: >> idx 02 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f >> val ff b0 73 ff 00 42 00 00 ff 50 80 00 00 eb 21 00 ff >> def 00 b0 NA ff 00 MM 00 MM RR 50 00 00 RR e2 21 00 00 >> LDN 0x00 (Floppy) >> idx 30 60 61 70 74 f0 f1 f2 f4 f5 >> val 01 03 f0 06 02 8e 00 ff 00 00 >> def 01 03 f0 06 02 8e 00 ff 00 00 >> LDN 0x01 (Parallel port) >> idx 30 60 61 70 74 f0 >> val 01 03 78 07 04 3f >> def 01 03 78 07 04 3f >> LDN 0x02 (COM1) >> idx 30 60 61 70 f0 >> val 01 03 f8 04 40 >> def 01 03 f8 04 00 >> LDN 0x03 (COM2) >> idx 30 60 61 70 f0 f1 >> val 01 02 f8 03 40 00 >> def 01 02 f8 03 00 00 >> LDN 0x05 (Keyboard) >> >> >> dump from dmesg >> >> home# dmesg | grep -i tty >> [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >> root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 >> console=ttyS0,115200n8 quiet splash vt.handoff=7 >> [ 0.000000] Kernel command line: >> BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic >> root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 >> console=ttyS0,115200n8 quiet splash vt.handoff=7 >> [ 0.000000] console [tty1] enabled >> [ 0.000000] console [ttyS0] enabled >> [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is >> a 16550A >> [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = >> 115200) is a 16550A >> [ 3.412478] fbcon: Remapping primary device, fb1, to tty 1-63 >> [ 44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice. >> [ 44.380198] systemd[1]: Created slice system-getty.slice. >> >> >> >> >> >> 2016-07-22 20:24 GMT+08:00 Kyösti Mälkki <kyosti.malkki(a)gmail.com>: >> >>> On Fri, Jul 22, 2016 at 1:14 PM, cheng yichen <blessyichen(a)gmail.com> >>> wrote: >>> > Hi all >>> > >>> > My platform is braswell SOC with W83627dhg superIO. In post stage I >>> can get >>> > debug message over w83627 uart1(3f8/irq4). but after boot to linux, >>> uart >>> > port is not woarkable. I test the function by minicom but I can't >>> receive >>> > and send data. I can get uart information by dmesg command. >>> > How to initial it in corebooot? >>> >>> Does not sound like a coreboot issue to me. >>> >>> Do you have CTS/RTS hardware handshake disabled in minicom >>> configuration? If you directed kernel console to serial port, you >>> should not (cannot) use the port for user apps. >>> >>> HTH, >>> Kyösti >>> >> >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> https://www.coreboot.org/mailman/listinfo/coreboot >> > >

1 0

Re: [coreboot] w83627 uart port is not workable with coreboot in linux
by Zoran Stojsavljevic 25 Jul '16

25 Jul '16

> home# dmesg | grep -i tty > [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=b2b7f7fa-b1db-4e97- > 941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet splash vt.handoff=7 > [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=b2b7f7fa-b1db- > 4e97-941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet splash vt.handoff=7 > [ 0.000000] console [tty1] enabled > [ 0.000000] console [ttyS0] enabled > [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A > [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A > [ 3.412478] fbcon: Remapping primary device, fb1, to tty 1-63 > [ 44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice. > [ 44.380198] systemd[1]: Created slice system-getty.slice. _______ Hello Cheng, Please, try to do the following: lspci -vv (to find your serial on PCIe), then try to remap your IRQs, to see if this will somehow work. Example: setserial /dev/ttyS0 port 0xd800 UART 16550A irq 5 setserial /dev/ttyS0 -av /dev/ttyS0, Line 0, UART: 16550A, Port: 0xd800, IRQ: 5 Baud_base: 115200, close_delay: 5000, divisor: 0 closing_wait: 37856 Flags: spd_normal skip_test Something like described on this web pointer: https://forums.gentoo.org/viewtopic-t-249041-start-0.html Please, report your attempts/results here. Thank you, Zoran On Mon, Jul 25, 2016 at 4:33 AM, cheng yichen <blessyichen(a)gmail.com> wrote: > Hi all > > After i follow kontron/ktqm77 setting. I can't solve the issue. > I try to change iqr(for com1) to 5 or 6. but system can't print linux > message and minicom is not workable. > > > > dump from superiotool > Found Winbond W83627DHG-P/-PT (id=0xb0, rev=0x73) at 0x2e > Register dump: > idx 02 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f > val ff b0 73 ff 00 42 00 00 ff 50 80 00 00 eb 21 00 ff > def 00 b0 NA ff 00 MM 00 MM RR 50 00 00 RR e2 21 00 00 > LDN 0x00 (Floppy) > idx 30 60 61 70 74 f0 f1 f2 f4 f5 > val 01 03 f0 06 02 8e 00 ff 00 00 > def 01 03 f0 06 02 8e 00 ff 00 00 > LDN 0x01 (Parallel port) > idx 30 60 61 70 74 f0 > val 01 03 78 07 04 3f > def 01 03 78 07 04 3f > LDN 0x02 (COM1) > idx 30 60 61 70 f0 > val 01 03 f8 04 40 > def 01 03 f8 04 00 > LDN 0x03 (COM2) > idx 30 60 61 70 f0 f1 > val 01 02 f8 03 40 00 > def 01 02 f8 03 00 00 > LDN 0x05 (Keyboard) > > > dump from dmesg > > home# dmesg | grep -i tty > [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic > root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 > console=ttyS0,115200n8 quiet splash vt.handoff=7 > [ 0.000000] Kernel command line: > BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic > root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 > console=ttyS0,115200n8 quiet splash vt.handoff=7 > [ 0.000000] console [tty1] enabled > [ 0.000000] console [ttyS0] enabled > [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is > a 16550A > [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = > 115200) is a 16550A > [ 3.412478] fbcon: Remapping primary device, fb1, to tty 1-63 > [ 44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice. > [ 44.380198] systemd[1]: Created slice system-getty.slice. > > > > > > 2016-07-22 20:24 GMT+08:00 Kyösti Mälkki <kyosti.malkki(a)gmail.com>: > >> On Fri, Jul 22, 2016 at 1:14 PM, cheng yichen <blessyichen(a)gmail.com> >> wrote: >> > Hi all >> > >> > My platform is braswell SOC with W83627dhg superIO. In post stage I can >> get >> > debug message over w83627 uart1(3f8/irq4). but after boot to linux, uart >> > port is not woarkable. I test the function by minicom but I can't >> receive >> > and send data. I can get uart information by dmesg command. >> > How to initial it in corebooot? >> >> Does not sound like a coreboot issue to me. >> >> Do you have CTS/RTS hardware handshake disabled in minicom >> configuration? If you directed kernel console to serial port, you >> should not (cannot) use the port for user apps. >> >> HTH, >> Kyösti >> > > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://www.coreboot.org/mailman/listinfo/coreboot >

1 0

Re: [coreboot] w83627 uart port is not workable with coreboot in linux
by cheng yichen 25 Jul '16

25 Jul '16

Hi all After i follow kontron/ktqm77 setting. I can't solve the issue. I try to change iqr(for com1) to 5 or 6. but system can't print linux message and minicom is not workable. dump from superiotool Found Winbond W83627DHG-P/-PT (id=0xb0, rev=0x73) at 0x2e Register dump: idx 02 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f val ff b0 73 ff 00 42 00 00 ff 50 80 00 00 eb 21 00 ff def 00 b0 NA ff 00 MM 00 MM RR 50 00 00 RR e2 21 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 01 03 f0 06 02 8e 00 ff 00 00 def 01 03 f0 06 02 8e 00 ff 00 00 LDN 0x01 (Parallel port) idx 30 60 61 70 74 f0 val 01 03 78 07 04 3f def 01 03 78 07 04 3f LDN 0x02 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 40 def 01 03 f8 04 00 LDN 0x03 (COM2) idx 30 60 61 70 f0 f1 val 01 02 f8 03 40 00 def 01 02 f8 03 00 00 LDN 0x05 (Keyboard) dump from dmesg home# dmesg | grep -i tty [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet splash vt.handoff=7 [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet splash vt.handoff=7 [ 0.000000] console [tty1] enabled [ 0.000000] console [ttyS0] enabled [ 1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A [ 3.412478] fbcon: Remapping primary device, fb1, to tty 1-63 [ 44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice. [ 44.380198] systemd[1]: Created slice system-getty.slice. 2016-07-22 20:24 GMT+08:00 Kyösti Mälkki <kyosti.malkki(a)gmail.com>: > On Fri, Jul 22, 2016 at 1:14 PM, cheng yichen <blessyichen(a)gmail.com> > wrote: > > Hi all > > > > My platform is braswell SOC with W83627dhg superIO. In post stage I can > get > > debug message over w83627 uart1(3f8/irq4). but after boot to linux, uart > > port is not woarkable. I test the function by minicom but I can't receive > > and send data. I can get uart information by dmesg command. > > How to initial it in corebooot? > > Does not sound like a coreboot issue to me. > > Do you have CTS/RTS hardware handshake disabled in minicom > configuration? If you directed kernel console to serial port, you > should not (cannot) use the port for user apps. > > HTH, > Kyösti >

1 0

New on blogs.coreboot.org: [GSoC] Multiple status registers, block protection and OTP support, week #6, 7, 8 and 9
by WordPress 24 Jul '16

24 Jul '16

1 0

Re: [coreboot] How to use properly the GRUB payload?
by arian 24 Jul '16

24 Jul '16

Hi Ioannis, I ran into a quite similar problem - I think the wikipage needs quite some overhaul. anyway: I also have grub2 as coreboot payload. It seems to have a memdisk, but I don't know how to change this. There is a workaround: a grub.cfg gets into that memdisk, which sources (cbfsdisk)/etc/grub.cfg - find for that in the coreboot tree. the solution then is to add a grub.cfg (and other files, like additional grub modules, background image, ...) to cbfs (in coreboot tree root): ./build/util/cbfstool/cbfstool build/coreboot.rom add -f mygrub.cfg -n etc/grub.cfg -t raw actually it's a good idea _not to_ put etc/grub.cfg at first - if you have errors in that you may end up softbricking your device. put it somewhere else and source it from the grub command line. regards, Arian On 24.07.2016 20:43, Ioannis Koutras wrote: > Hello John, > > And thanks for replying. I have checked https://www.coreboot.org/GRUB2 and it is still not clear to me how to embed grub.cfg. I had added GRUB2 directly via "make menuconfig" (It is available on Payload > Add a payload) , so coreboot checked out GRUB's source code, configured, compiled and embedded it to coreboot.rom. > > Would you recommend me to install it in a more manual way, as described in the wiki? > > > Best regards, > > Ioannis > > On Sun, 17 Jul 2016 at 22:55 John Lewis <jlewis(a)johnlewis.ie <mailto:jlewis@johnlewis.ie>> wrote: > > Hi Ioannis, > > Please see https://www.coreboot.org/GRUB2 in relation to setting it up properly. > > Kind Regards, > > John. > > > On 15/07/16 21:26, Ioannis Koutras wrote: >> Hello, >> >> I have just flashed coreboot (git commit: 89e7b49) on a Lenovo X220 with GRUB2 as payload and when I boot the machine, I am getting GRUB's command line. >> >> I am trying to boot a systemd-boot (previously known as gummiboot?) payload from my disk partition, but I am getting unrecognised payload. Any idea what's the issue there? >> >> Additionally, could anyone help me set it up properly, as in searching for grub.cfg in disks and looking to boot from USB? >> >> >> Many thanks in advance, >> >> Ioannis >> >> > > >

1 0

Re: [coreboot] How to use properly the GRUB payload?
by John Lewis 24 Jul '16

24 Jul '16

Hi Ioannis, Please see https://www.coreboot.org/GRUB2 in relation to setting it up properly. Kind Regards, John. On 15/07/16 21:26, Ioannis Koutras wrote: > Hello, > > I have just flashed coreboot (git commit: 89e7b49) on a Lenovo X220 > with GRUB2 as payload and when I boot the machine, I am getting GRUB's > command line. > > I am trying to boot a systemd-boot (previously known as gummiboot?) > payload from my disk partition, but I am getting unrecognised payload. > Any idea what's the issue there? > > Additionally, could anyone help me set it up properly, as in searching > for grub.cfg in disks and looking to boot from USB? > > > Many thanks in advance, > > Ioannis > >

2 1

Re: [coreboot] Thinkpad x230 video glitches during boot
by Trammell Hudson 24 Jul '16

24 Jul '16

On Sat, Jul 23, 2016 at 08:27:17PM +0000, ron minnich wrote: > I"m assuming this is native graphics? That's sometimes a sign that the > graphics hardware can't get to memory for an image, either due to the page > remapping on the graphics hardware being wrong or maybe BME is not set on > the device. Yes, this was with native graphics. It looks like grub's gfxterm was causing it -- I switched terminal_output to console and there is now a nice text mode boot menu rather than glitching. > [...] > BTW, how big is the Qubes "kernel" itself? Is it possible to put it in > flash? The Qubes kernel is the Xen hypervisor and is only about 800 KB. I'm attempting to add it as the payload, although I think that a minimal Linux in ROM that kexec's Xen from an encrypted and measured disk image will be better suited to my goals. -- Trammell

2 1

New on blogs.coreboot.org: [GSoC] Better RISC-V support, week #6/7/8/9
by WordPress 24 Jul '16

24 Jul '16

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot July 2016