Hello Felix, Thank you for your informative response to my issue.
My comments in-line below: On Sun, 30 Apr 2017 21:34:14 -0400, Felix Miata <mrma...@earthlink.net> wrote: >Larry Dighera composed on 2017-04-30 16:40 (UTC-0700): >[...] >Previously, in OP https://lists.debian.org/debian-user/2017/04/msg00534.html : >http://www.udoo.org/ >*** > Without anything there indicating date of release, that URI strongly > suggests >to me nevertheless that his hardware is newer than Jessie can be expected to >support. > Yes. It's a new single-board computer platform that began shipping ~April 14, 2017. I can personally confirm that Tails Linux X11 runs fine on this platform, and the manufacturer (Udoo) claims to have successfully installed Debian. Specs are here: http://www.udoo.org/new-resources-udoo-x86/ Intel® Celeron® N3160, Quad Core @1.6GHz (Turbo Boost 2.24GHz), 2MB Cache, 6W TDP. Integrated Intel® HD Graphics controller Three independent display support HW decoding of HEVC(H.265), H.264, MPEG2, MVC, VC-1, VP8, WMV9, JPEG/MJPEG formats HW encoding of H.264, MVC and JPEG/MPEG formats Video Interfaces HDMI connector 2 x miniDP++ connectors Video Resolution Up to 3840 x 2160 24bpp @ 30Hz, 2560 x 1600 24bpp @60Hz CIR (Consumer InfraRed) Sensor Arduino 101 compatible shield Integrated 6-axis combo sensor with accelerometer and gyroscope ------------ Here is data from Debian Jessie on the Udoo X86 platform: --------------- System Information---------------- Kernel name: Linux Network node Hostname: UdooX86Debian Kernel release: 3.16.0-4-amd64 Kernel version: #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux Machine hardware name: Operating system: ------------------- OS Release ------------------- PRETTY_NAME="Debian GNU/Linux 8 (jessie)" NAME="Debian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=debian HOME_URL="http://www.debian.org/"; SUPPORT_URL="http://www.debian.org/support"; BUG_REPORT_URL="https://bugs.debian.org/"; ---------------- CPU Information ----------------- Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 76 Model name: Intel(R) Celeron(R) CPU N3160 @ 1.60GHz Stepping: 4 CPU MHz: 499.800 CPU max MHz: 2332.3999 CPU min MHz: 499.8000 BogoMIPS: 3199.86 Virtualization: VT-x L1d cache: 24K L1i cache: 32K L2 cache: 1024K NUMA node0 CPU(s): 0-3 processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 76 model name : Intel(R) Celeron(R) CPU N3160 @ 1.60GHz stepping : 4 microcode : 0x40a cpu MHz : 499.800 cache size : 1024 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 3199.86 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 76 model name : Intel(R) Celeron(R) CPU N3160 @ 1.60GHz stepping : 4 microcode : 0x40a cpu MHz : 499.800 cache size : 1024 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 3199.86 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 76 model name : Intel(R) Celeron(R) CPU N3160 @ 1.60GHz stepping : 4 microcode : 0x40a cpu MHz : 500.060 cache size : 1024 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 4 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 3199.86 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 76 model name : Intel(R) Celeron(R) CPU N3160 @ 1.60GHz stepping : 4 microcode : 0x40a cpu MHz : 499.800 cache size : 1024 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 4 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 3199.86 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: --------- > >GiaThnYgeia later wrote: >$ inxi -c10 -v3 >Will list basic system info and hardware >*** > I found nothing in the archive or on original reading of the thread > responding >to this, but then later I did see OP wrote: > >Intel quad-core Celeron N3160 >2.24 GHz & Intel® Quark SE core 32 MHz plus 32-bit ARC core 32 MHz, Intel HD >Graphics 400 Up to 640 MHz 12 execution units, 4 GB DDR3L Dual Channel RAM >and 32GB eMMC Storage >*** > This supports my suspicion. Later, OP provided logs, which contained: > >Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 >root=UUID=f0748180-a596-4f02-85d8-34b09b57cb42 ro quiet >(EE) open /dev/dri/card0: No such file or directory >(EE) open /dev/dri/card0: No such file or directory >(EE) open /dev/fb0: No such file or directory >(EE) open /dev/fb0: No such file or directory >(EE) Screen 0 deleted because of no matching config section. >(EE) Screen 0 deleted because of no matching config section. >*** > These support my suspicion, and explain why his ttys are stuck in 80x25 > mode, >unresponsive to later instruction from David Wright. Lack of /dev/fb0 is a not >unusual pre-KMS result from a kernel cmdline (from the selected Grub stanza, as >modified, if modified) that lacks anything telling the kernel not to enable >framebuffer, resulting in use of 80x25 text mode on the ttys. Since Jessie's >3.16 kernel does support KMS, his 1920x1080 Samsung SyncMaster display's native >mode should be picked up by KMS, but that depends on the kernel supporting his >Intel HD Graphics 400 device. > I'm very impressed with your insight into this issue, and deep understanding of Debian Jessie, not to mention grateful you have chosen to share your knowledge. I don't know when Intel HD Graphics 400 was released, but Tails Linux runs X11 on the Udoo X86, so apparently there is a Linux driver available. >Possibly Grub could be reconfigured to make a >lesser mode like 1440x900 or less explicit. > I'm willing to edit grub, if you're willing to provide specific instructions. Unfortunately, my Unix experience predates grub (AT&T Unix SVR3 ~1994). > >Lack of /dev/dri/card0 explains why >X doesn't work, the kernel found no supported gfx device. > It sounds like you've discovered the root cause of the issue. I failed to find /dev/dri let alone card0. I have no idea what this means. > >When I boot an Intel video Jessie PC with no video parameters on cmdline, >root=LABEL=deb8jessie plymouth.enable=0 noresume > ??? > >I see kernel messages begin in 80x25 mode, after which the kernel figures out >the display's native mode and switches to it, resulting in ttys producing 210 >columns by 65 rows. > Now we're talking... > ># inxi -c0 -G >Graphics: Card: Intel 82945G/GZ Integrated Graphics Controller > Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa) > tty size: 210x65 Advanced Data: N/A for root out of X > >When I reboot same PC with framebuffer disabled to emulate OP's boot condition >thus, >root=LABEL=deb8jessie plymouth.enable=0 noresume nomodeset ># ls -l /dev/fb* >ls: cannot access /dev/fb*: No such file or directory >the ttys stay in 80x25 mode: ># inxi -c0 -G >Graphics: Card: Intel 82945G/GZ Integrated Graphics Controller > Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa) > tty size: 80x25 Advanced Data: N/A for root out of X > >I've seen nothing in thread explicitly explaining why he has no /dev/fb0, but >unless and until /dev/fb0 exists, ttys are stuck in 80x25. Maybe that is >something installing a working Plymouth can fix. I don't know, as I never use >Plymouth, and suspect it would also be victim of unsupported hardware. > I did install Plymouth: apt-get install Plymouth. It didn't seem to make any noticeable change. (There are some Plymouth entries in daemon.log and syslog.) Subsequently running lightdm still yields a black display screen. > >Even if OP can get the ttys working to his liking, I still think it's very >likely a lost cause trying to use Jessie on his hardware. Stretch is very near >ready to release, and probably OP's better next move. > In this message thread: http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/ others have also suggested Stretch. I looked at the existing bugs: https://bugs.debian.org/release-critical/other/testing.html https://bugs.debian.org/release-critical/ Release-critical bugs status Tue May 2 17:00:00 UTC 2017 Total number of release-critical bugs: 1649 Number that have a patch: 271 Number that have a fix prepared and waiting to upload: 38 Number that are being ignored: 78 Number concerning the current stable release: 699 Number concerning the next release: 149 ---- The reason for installing Debian was because I have been impressed with its stability and few update issues compared to other Linux flavors I've used, so I was/am reluctant to overwrite Jessie with Stretch. Given the Udoo team claims to have installed Debian on their hardware, and Tails Linux runs on it, I'd prefer to sort out the issues, and see if I (we?) can effect a useable system. Thank you again for sharing your knowledge, and the time you've spent in investigating this issue. Best regards, Larry
