element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Ultrazed Hardware Design Ultrazed-EV bootconsole [cdns0] disabled
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 19 replies
  • Answers 3 answers
  • Subscribers 341 subscribers
  • Views 4547 views
  • Users 0 members are here
Related

Ultrazed-EV bootconsole [cdns0] disabled

khabnl
khabnl over 6 years ago

Hello,

 

I am testing the Ultrazed-EV board and I found bootconsole [cdns0] disabled message and stopped.

 

I added booting parameters in system-user.dtsi.

 

bootargs = "console=ttyPS0,115200 earlycon clk_ignore_unused cpuidle.off=1 root=/dev/mmcblk0p2 rw  rootfstype=ext4 rootwait";

 

 

U-Boot 2019.01 (Jul 19 2019 - 14:29:54 +0000)

 

Board: Xilinx ZynqMP

DRAM:  4 GiB

usb dr_mode not found

EL Level:       EL2

Chip ID:        zu7ev

MMC:   mmc@ff160000: 0, mmc@ff170000: 1

Loading Environment from SPI Flash... SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB

*** Warning - bad CRC, using default environment

 

In:    serial@ff000000

Out:   serial@ff000000

Err:   serial@ff000000

Board: Xilinx ZynqMP

Bootmode: SD_MODE1

Reset reason:   EXTERNAL

Net:   ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id

eth0: ethernet@ff0e0000

U-BOOT for uzev_plinux

 

ethernet@ff0e0000 Waiting for PHY auto negotiation to complete...... done

BOOTP broadcast 1

BOOTP broadcast 2

BOOTP broadcast 3

DHCP client bound to address 192.168.0.101 (1016 ms)

Hit any key to stop autoboot:  0

Device: mmc@ff160000

Manufacturer ID: 13

OEM: 14e

Name: Q2J55

Bus Speed: 52000000

Mode : MMC High Speed (52MHz)

Rd Block Len: 512

MMC version 5.0

High Capacity: Yes

Capacity: 7.1 GiB

Bus Width: 4-bit

Erase Group Size: 512 KiB

HC WP Group Size: 8 MiB

User Capacity: 7.1 GiB WRREL

Boot Capacity: 16 MiB ENH

RPMB Capacity: 4 MiB ENH

23676020 bytes read in 1770 ms (12.8 MiB/s)

## Loading kernel from FIT Image at 10000000 ...

   Using 'conf@1' configuration

   Trying 'kernel@0' kernel subimage

     Description:  Linux Kernel

     Type:         Kernel Image

     Compression:  uncompressed

     Data Start:   0x100000d8

     Data Size:    13574656 Bytes = 12.9 MiB

     Architecture: AArch64

     OS:           Linux

     Load Address: 0x00080000

     Entry Point:  0x00080000

     Hash algo:    sha1

     Hash value:   6430bf9020db9fe81f94415ab58478ebe4154d35

   Verifying Hash Integrity ... sha1+ OK

## Loading ramdisk from FIT Image at 10000000 ...

   Using 'conf@1' configuration

   Trying 'ramdisk@0' ramdisk subimage

     Description:  ramdisk

     Type:         RAMDisk Image

     Compression:  uncompressed

     Data Start:   0x10cfa620

     Data Size:    10066525 Bytes = 9.6 MiB

     Architecture: AArch64

     OS:           Linux

     Load Address: unavailable

     Entry Point:  unavailable

     Hash algo:    sha1

     Hash value:   21d9aa2b62261cf1213a1643c76d418b626775cb

   Verifying Hash Integrity ... sha1+ OK

## Loading fdt from FIT Image at 10000000 ...

   Using 'conf@1' configuration

   Trying 'fdt@0' fdt subimage

     Description:  Flattened Device Tree blob

     Type:         Flat Device Tree

     Compression:  uncompressed

     Data Start:   0x10cf23d0

     Data Size:    33180 Bytes = 32.4 KiB

     Architecture: AArch64

     Hash algo:    sha1

     Hash value:   b128e977b259dd6ff89fe8d29afee83b6c64ac7b

   Verifying Hash Integrity ... sha1+ OK

   Booting using the fdt blob at 0x10cf23d0

   Loading Kernel Image ... OK

   Loading Ramdisk to 07666000, end 07fffa5d ... OK

   Loading Device Tree to 000000000765a000, end 000000000766519b ... OK

 

Starting kernel ...

 

[    0.000000] Booting Linux on physical CPU 0x0

[    0.000000] Linux version 4.9.0-xilinx-v2017.3 (avnet@ubuv1604) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Tue Feb 6 17:51:04 EST 2018

[    0.000000] Boot CPU: AArch64 Processor [410fd034]

[    0.000000] earlycon: cdns0 at MMIO 0x00000000ff000000 (options '115200n8')

[    0.000000] bootconsole [cdns0] enabled

[    0.000000] efi: Getting EFI parameters from FDT:

[    0.000000] efi: UEFI not found.

[    0.000000] cma: Reserved 256 MiB at 0x000000006fc00000

[    0.000000] psci: probing for conduit method from DT.

[    0.000000] psci: PSCIv1.1 detected in firmware.

[    0.000000] psci: Using standard PSCI v0.2 function IDs

[    0.000000] psci: MIGRATE_INFO_TYPE not supported.

[    0.000000] percpu: Embedded 21 pages/cpu @ffffffc87ff78000 s48152 r8192 d29672 u86016

[    0.000000] Detected VIPT I-cache on CPU0

[    0.000000] CPU features: enabling workaround for ARM erratum 845719

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 1033987

[    0.000000] Kernel command line: earlycon clk_ignore_unused

[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)

[    0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)

[    0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)

[    0.000000] software IO TLB [mem 0x6bc00000-0x6fc00000] (64MB) mapped at [ffffffc06bc00000-ffffffc06fbfffff]

[    0.000000] Memory: 3777580K/4193280K available (9212K kernel code, 584K rwdata, 2884K rodata, 512K init, 397K bss, 153556K reserved, 262144K cma-reserved)

[    0.000000] Virtual kernel memory layout:

[    0.000000]     modules : 0xffffff8000000000 - 0xffffff8008000000   (   128 MB)

[    0.000000]     vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000   (   250 GB)

[    0.000000]       .text : 0xffffff8008080000 - 0xffffff8008980000   (  9216 KB)

[    0.000000]     .rodata : 0xffffff8008980000 - 0xffffff8008c60000   (  2944 KB)

[    0.000000]       .init : 0xffffff8008c60000 - 0xffffff8008ce0000   (   512 KB)

[    0.000000]       .data : 0xffffff8008ce0000 - 0xffffff8008d72200   (   585 KB)

[    0.000000]        .bss : 0xffffff8008d72200 - 0xffffff8008dd5634   (   398 KB)

[    0.000000]     fixed   : 0xffffffbefe7fd000 - 0xffffffbefec00000   (  4108 KB)

[    0.000000]     PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000   (    16 MB)

[    0.000000]     vmemmap : 0xffffffbf00000000 - 0xffffffc000000000   (     4 GB maximum)

[    0.000000]               0xffffffbf00000000 - 0xffffffbf1dc00000   (   476 MB actual)

[    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc880000000   ( 34816 MB)

[    0.000000] Hierarchical RCU implementation.

[    0.000000]  Build-time adjustment of leaf fanout to 64.

[    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.

[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4

[    0.000000] NR_IRQS:64 nr_irqs:64 0

[    0.000000] GIC: Adjusting CPU interface base to 0x00000000f902f000

[    0.000000] GIC: Using split EOI/Deactivate mode

[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 99.99MHz (phys).

[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171015c90f, max_idle_ns: 440795203080 ns

[    0.000003] sched_clock: 56 bits at 99MHz, resolution 10ns, wraps every 4398046511101ns

[    0.008221] Console: colour dummy device 80x25

[    0.012480] console [tty0] enabled

[    0.015846] bootconsole [cdns0] disabled

  • Sign in to reply
  • Cancel
Parents
  • narrucmot
    0 narrucmot over 6 years ago

    Hi Kiman,

     

    The last boot message you see here ("bootconsole [cdns0] disabled") usually has nothing to do with the bootconsole being disabled.  This message just happens to be the spot where the kernel boot got hung up.  Because of the way STDIO messages are buffered to the UART during boot, this is the last message that is seen by the user.  The problem is somewhere else.  The u-boot messages indicate this is a kernel that expects a RAMdisk rootfs (“## Loading ramdisk from FIT Image at 10000000 ...”), but the bootargs in the system-user.dtsi file indicate a rootfs on the SD card (“root=/dev/mmcblk0p2 rw  rootfstype=ext4 rootwait”).  These settings re inconsistent.  I would expect the bootargs for a kernel mounting a RAMdisk to look much simpler (“bootargs = "earlycon clk_ignore_unused"”).  If there truly is a rootfs on the mmcblk0p2 partition then PetaLinux also needs to be configured (and thus u-boot) for that.  I believe Xilinx UG1144 describes this (https://www.xilinx.com/support/documentation/sw_manuals/xilinx2019_1/ug1144-petalinux-tools-reference-guide.pdf ).

     

    --Tom

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • khabnl
    0 khabnl over 6 years ago in reply to narrucmot

    Hi Tom,

     

    Thank you for your response.

     

    Actually I tried to simple way but I got the same result.

    bootargs = "console=ttyPS0,115200 earlycon clk_ignore_unused";

    stdout-path = "serial0:115200n8";

     

    I need the SD card /dev/mmcblk0p2 partition for the Debian rootfs.

     

    Thanks,

    Kiman

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • khabnl
    0 khabnl over 6 years ago in reply to khabnl

    I create image.ub using petalinux version 2019.1

    But the kernel image log file shows "Linux version 4.9.0-xilinx-v2017.3 (avnet@ubuv1604) (gcc version 6.2.1 20161016"

     

    I think this is something wrong, image.ub booting from existing avnet image instead of the SD card?

    Starting kernel ...

     

     

    [    0.000000]
    Linux version 4.9.0-xilinx-v2017.3 (avnet@ubuv1604) (gcc version 6.2.1 20161016
    (Linaro GCC 6.2-2016.11) ) #1 SMP Tue Feb 6 17:51:04
    EST 2018

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • drozwood90
    0 drozwood90 over 6 years ago in reply to khabnl

    Hi there,

     

    It sounds like you might be booting from the onboard EEPROM or other memory.  Check your boot switch configuration to ensure that you are targeting booting from the SDCARD.

     

    --Dan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Reply
  • drozwood90
    0 drozwood90 over 6 years ago in reply to khabnl

    Hi there,

     

    It sounds like you might be booting from the onboard EEPROM or other memory.  Check your boot switch configuration to ensure that you are targeting booting from the SDCARD.

     

    --Dan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Children
  • khabnl
    0 khabnl over 6 years ago in reply to drozwood90

    Hi Dan,

     

    Yes, I configured booting from the SD card, and  I confirmed several times.

    Avnet default is QSPI (OFF,ON,ON,ON).

    The SD card booting is (OFF, ON, OFF, ON).

    If remove SDCARD there is no serial console message.

     

    If you see U-Boot message it indicate on Jul 19 2019, but Kernel is not 2019.1

     

     

    U-Boot 2019.01 (Jul 19 2019 - 14:29:54 +0000)

     

    Board: Xilinx ZynqMP

    DRAM:  4 GiB

    usb dr_mode not found

    EL Level:       EL2

    Chip ID:        zu7ev

    MMC:   mmc@ff160000: 0, mmc@ff170000: 1

    Loading Environment from SPI Flash... SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB

    *** Warning - bad CRC, using default environment

     

     

    Thanks,

    Kiman

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • khabnl
    0 khabnl over 6 years ago in reply to khabnl

    Hello,

     

    I revisited my ultrazed EV SD card booting project.

    I create a new Vivado 2018.2 project based on uz7ev_evcc_sd_oob_2018_2,bsp.

    And now I can booting-up fro SD card.

     

     

    #ultrazed_ev SD card booting
    # boot   : FAT32
    # footfs : Ext4 partition, Debian 10

     

    # Create a new project preate from uz7ev_evcc_sd_oob_2018_2,bsp

    $petalinux-create -t project -s uz7ev_evcc_sd_oob_2018_2.bsp -n uz7ev_evcc_sd_oob_2018_2_mytest

     

    $cd uz7ev_evcc_sd_oob_2018_2_mytest

     

    # uz_petalinux.sdk is my new Vivado project 2018.2, new project based on bsp UZ7EV_EVCC
    $petalinux-config --get-hw-description=/home/bpmlab2/xilinx/kiman/ultrazed_ev/2018.2/uz_petalinux.sdk

     

    $petalinux-build

     

    #Create BOOT.bin
    $petalinux-package --boot --format BIN --fsbl images/linux/zynqmp_fsbl.elf --u-boot images/linux/u-boot.elf --pmufw images/linux/pmufw.elf --fpga images/linux/system.bit --force

     

     

     

    Thank for your support.

     

    Release 2018.2   Aug 15 2019  -  21:20:32
    NOTICE:  ATF running on XCZU7EV/silicon v4/RTL5.1 at 0xfffea000
    NOTICE:  BL31: Secure code at 0x0
    NOTICE:  BL31: Non secure code at 0x8000000
    NOTICE:  BL31: v1.4(release):xilinx-v2018.1-4-g93a69a5a
    NOTICE:  BL31: Built : 01:18:22, Aug 16 2019
    PMUFW:  v1.0

    U-Boot 2018.01 (Aug 15 2019 - 21:18:06 -0400) Xilinx ZynqMP ZCU102 rev1.0

    I2C:   ready
    DRAM:  4 GiB
    EL Level:       EL2
    Chip ID:        zu7ev
    MMC:   sdhci@ff160000: 0 (eMMC), sdhci@ff170000: 1 (SD)
    SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB
    In:    serial@ff000000
    Out:   serial@ff000000
    Err:   serial@ff000000
    Board: Xilinx ZynqMP
    Net:   ZYNQ GEM: ff0e0000, phyaddr 0, interface rgmii-id
    eth0: ethernet@ff0e0000
    Hit any key to stop autoboot:  0
    Device: sdhci@ff160000
    Manufacturer ID: 13
    OEM: 14e
    Name: Q2J55
    Tran Speed: 200000000

     

    [    3.817126] EXT4-fs (mmcblk1p2): couldn't mount as ext3 due to feature incompatibilities
    [    3.979175] EXT4-fs (mmcblk1p2): recovery complete
    [    3.985284] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
    [    3.993315] VFS: Mounted root (ext4 filesystem) on device 179:2.
    [    4.002864] devtmpfs: mounted
    [    4.005876] Freeing unused kernel memory: 512K
    [    4.738733] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
    [    4.760315] systemd[1]: Detected architecture arm64.

    Welcome to Debian GNU/Linux 10 (buster)!

    [    4.782154] systemd[1]: Set hostname to <debian10-zcu102>.
    [    5.084836] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
    [    5.101838] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
    [    5.337221] systemd[1]: Listening on Journal Audit Socket.
    [  OK  ] Listening on Journal Audit Socket.
    [    5.357344] systemd[1]: Listening on Journal Socket.
    [  OK  ] Listening on Journal Socket.
    [    5.374570] systemd[1]: Mounting POSIX Message Queue File System...
             Mounting POSIX Message Queue File System...
    [    5.397326] systemd[1]: Listening on initctl Compatibility Named Pipe.
    [  OK  ] Listening on initctl Compatibility Named Pipe.
    [    5.422311] systemd[1]: Starting Remount Root and Kernel File Systems...
             Starting Remount Root and Kernel File Systems...
    [  OK  ] Listening on udev Kernel Socket.
    [  OK  ] Reached target Swap.
    [  OK  ] Created slice system-getty.slice.
             Mounting Huge Pages File System...
    [  OK  ] Listening on Syslog Socket.
    [  OK  ] Listening on udev Control Socket.
             Starting Load Kernel Modules...
    [  OK  ] Started Forward Password R…uests to Wall Directory Watch.
             Starting udev Coldplug all Devices...
    [  OK  ] Started Dispatch Password …ts to Console Directory Watch.
    [  OK  ] Reached target Local Encrypted Volumes.
    [  OK  ] Reached target Paths.
             Mounting Kernel Debug File System...
    [  OK  ] Listening on Journal Socket (/dev/log).
    [  OK  ] Reached target Sockets.
    [  OK  ] Reached target Slices.
    [  OK  ] Created slice system-serial\x2dgetty.slice.
             Starting Journal Service...
    [  OK  ] Reached target Remote File Systems.
    [  OK  ] Mounted POSIX Message Queue File System.
    [  OK  ] Started Remount Root and Kernel File Systems.
    [  OK  ] Mounted Huge Pages File System.
    [  OK  ] Started Journal Service.
    [  OK  ] Started Load Kernel Modules.
    [  OK  ] Mounted Kernel Debug File System.
             Mounting Kernel Configuration File System...
             Starting Apply Kernel Variables...
             Starting Flush Journal to Persistent Storage...
             Starting Create System Users...
             Starting Load/Save Random Seed...
    [  OK  ] Mounted Kernel Configuration File System.
    [  OK  ] Started Apply Kernel Variables.
    [  OK  ] Started Load/Save Random Seed.
    [  OK  ] Started Create System Users.
             Starting Create Static Device Nodes in /dev...
    [    5.961644] systemd-journald[2183]: Received request to flush runtime journal from PID 1
    [  OK  ] Started Flush Journal to Persistent Storage.
    [  OK  ] Started Create Static Device Nodes in /dev.
    [  OK  ] Reached target Local File Systems (Pre).
    [  OK  ] Reached target Local File Systems.
             Starting udev Kernel Device Manager...
             Starting Create Volatile Files and Directories...
    [  OK  ] Started udev Coldplug all Devices.
             Starting Helper to synchronize boot up for ifupdown...
    [  OK  ] Started Create Volatile Files and Directories.
             Starting Update UTMP about System Boot/Shutdown...
             Starting Network Time Synchronization...
    [  OK  ] Started udev Kernel Device Manager.
    [  OK  ] Started Update UTMP about System Boot/Shutdown.
    [  OK  ] Found device /dev/ttyPS0.
    [  OK  ] Started Network Time Synchronization.
    [  OK  ] Started Helper to synchronize boot up for ifupdown.
             Starting Raise network interfaces...
    [  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
    [  OK  ] Reached target System Time Synchronized.
    [  OK  ] Reached target System Initialization.
    [  OK  ] Started Daily Cleanup of Temporary Directories.
    [    8.405605] pps pps0: new PPS source ptp0
    [    8.409568] macb ff0e0000.ethernet: gem-ptp-timer ptp clock registered.
    [    8.416253] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [  OK  ] Started Daily man-db regeneration.
    [  OK  ] Started Daily apt download activities.
    [  OK  ] Started Daily apt upgrade and clean activities.
    [  OK  ] Reached target Basic System.
             Starting getty on tty2-tty…nd logind are not available...
             Starting System Logging Service...
    [  OK  ] Started Regular background program processing daemon.
    [  OK  ] Started Daily rotation of log files.
    [  OK  ] Reached target Timers.
    [  OK  ] Reached target Sound Card.
    [  OK  ] Started Raise network interfaces.
    [  OK  ] Reached target Network.
             Starting Permit User Sessions...
             Starting OpenBSD Secure Shell server...
    [  OK  ] Started Permit User Sessions.
    [  OK  ] Started System Logging Service.
    [  OK  ] Started Getty on tty2.
    [  OK  ] Started Serial Getty on ttyPS0.
    [  OK  ] Started Getty on tty1.
    [  OK  ] Started Getty on tty3.
    [  OK  ] Started Getty on tty4.
    [  OK  ] Started Getty on tty5.
    [  OK  ] Started Getty on tty6.
    [  OK  ] Started getty on tty2-tty6… and logind are not available.
    [  OK  ] Reached target Login Prompts.
    [  OK  ] Started OpenBSD Secure Shell server.
    [  OK  ] Reached target Multi-User System.
    [  OK  ] Reached target Graphical Interface.
             Starting Update UTMP about System Runlevel Changes...
    [  OK  ] Started Update UTMP about System Runlevel Changes.

    Debian GNU/Linux 10 debian10 ttyPS0

    debian10 login:

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube