Bug#926980: installation-reports: No problem on Intel H110 Skylake with SATA SSD, HDMI-LCD.
Package: installation-reports Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: tester To: Debian Bug Tracking System Subject: installation-reports: No problem on Intel H110 Skylake with SATA SSD, HDMI-LCD. Bcc: tester Package: installation-reports Severity: minor Dear Maintainer, This machine, I tested something standard GNOME. Simple Filesystem, no LVM, no LUKS. As always, this mail is submitted from my other main machine. -- Package-specific info: Boot method: netinst.iso Image version: Debian official Buster Date: 2019-04-11 Machine: DIY, ASRock H110 + Pentium G4400, SATA SSD. Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on udev devtmpfs 3915004 0 3915004 0% /dev tmpfs tmpfs 7859929268776724 2% /run /dev/sdb2 ext4 28705700 4569208 22655276 17% / tmpfs tmpfs 3929948 116 3929832 1% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 3929948 0 3929948 0% /sys/fs/cgroup tmpfs tmpfs 3929948 228 3929720 1% /tmp /dev/sdb4 ext4 78069428 189216 73871408 1% /home tmpfs tmpfs 785988 0785988 0% /run/user/0 tmpfs tmpfs 7859884888781100 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Installation are 2019-04-11 and confirmation is 2019-04-13, after upgrades. * tty resolutions are fine. * byobu works; but on GNOME terminal and byobu window size changes, GNU nano display corrupts. * lm-sensors reads almost perfect, except PCH temps. * s2ram works and it's quick. * GNOME, Firefox, Thunderbird and logcheck summary mails are GO. Youtube FullHD video, full screen, quality and sound are good. * fstrim works. NOTE I use same LCD, using HDMI splitter, shared with #926920, Kaby Lake + GeForce 1030 (HDMI) machine. #926920 machine is still does not play sounds. This machine does. I guess something around GeForce is wrong, or simply GeForce HDMI output does not contain sound, or filesystem could be the cause. That machine has separated, strict (many nosuid noexec, etc.) LVM-over-LUKS filesystem. I'm sorry I have no idea about it. Anyway, I will write about it at #926920. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="10 (buster) - installer build 20190408-00:02:21" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux buster 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:190f] (rev 07) lspci -knn: Subsystem: ASRock Incorporation Device [1849:190f] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 510 [8086:1902] (rev 06) lspci -knn: Subsystem: ASRock Incorporation Device [1849:1902] lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) lspci -knn: Subsystem: ASRock Incorporation Device [1849:a12f] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: Kernel modules: xhci_pci lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31) lspci -knn: Subsystem: ASRock Incorporation Device [1849:a131] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) lspci -knn: Subsystem: ASRock Incorporation Device [1849:a13a] lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31) lspci -knn: Subsystem: ASRock Incorporation Device [1849:a102] lspci -knn: Kernel driver in use: ahci lspci -knn: Kernel module
Bug#926980: syslog around the screen blank touble
Dear maintainers, I forgot to append syslog. I am sorry for multiple submits. By the way, It seems something EDID and/or i2c NAK related. (also it could be a HDMI splitter related, I guess.) I did not switch the HDMI input during this. However, the splitter is a cheap one, no EDID emulation. Another same HDMI splitter is used on my main Stretch machine, attached to another LCD. Apr 13 17:20:19 buster systemd[1]: Started Locale Service. Apr 13 17:20:49 buster systemd[1]: systemd-localed.service: Succeeded. Apr 13 17:23:55 buster PackageKit[2071]: daemon quit Apr 13 17:23:55 buster systemd[1]: packagekit.service: Main process exited, code=killed, status=15/TERM Apr 13 17:23:55 buster systemd[1]: packagekit.service: Succeeded. Apr 13 17:28:55 buster systemd[1]: Starting Cleanup of Temporary Directories... Apr 13 17:28:55 buster systemd[1]: systemd-tmpfiles-clean.service: Succeeded. Apr 13 17:28:55 buster systemd[1]: Started Cleanup of Temporary Directories. Apr 13 17:30:54 buster gnome-shell[2324]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 553]: reference to undefined property 0 Apr 13 17:46:52 buster gnome-shell[2324]: JS WARNING: [resource:///org/gnome/shell/ui/notificationDaemon.js 81]: reference to undefined property "image-path" Apr 13 17:52:28 buster gnome-shell[2324]: Failed to read EDID blob from HDMI-1: No such file or directory Apr 13 17:52:28 buster gnome-shell[2324]: Failed to apply DRM plane transform 0: Permission denied Apr 13 17:52:28 buster systemd[1]: Started Getty on tty5. Apr 13 17:52:29 buster gsd-color[2480]: failed to get edid: EDID length is too small Apr 13 17:52:29 buster gsd-color[2480]: failed to create device: failed to obtain org.freedesktop.color-manager.create-device auth Apr 13 17:52:29 buster gsd-color[2480]: could not find device: property match 'XRANDR_name'='HDMI-1' does not exist Apr 13 17:52:29 buster systemd[1]: Started Getty on tty3. Apr 13 17:52:30 buster kernel: i2c i2c-1: sendbytes: NAK bailout. Apr 13 17:52:31 buster gsd-color[2480]: could not find device: property match 'XRANDR_name'='HDMI-1' does not exist Apr 13 17:52:31 buster gnome-shell[2324]: 0x2e (gnome-shel): frame_complete callback never occurred for frame 5747 Apr 13 17:54:36 buster gdm-password][8567]: pam_unix(gdm-password:auth): conversation failed Apr 13 17:54:36 buster gdm-password][8567]: pam_unix(gdm-password:auth): auth could not identify password for [tester] Apr 13 17:58:19 buster gsd-color[2480]: failed to find device: property match 'XRANDR_name'='HDMI-1' does not exist Apr 13 17:58:30 buster gnome-shell[2324]: Failed to apply DRM plane transform 0: Permission denied Apr 13 17:58:31 buster gsd-color[2480]: failed to create device: failed to obtain org.freedesktop.color-manager.create-device auth Apr 13 17:58:31 buster gsd-color[2480]: could not find device: property match 'XRANDR_name'='HDMI-1' does not exist Apr 13 17:58:39 buster gsd-color[2480]: could not find device: property match 'XRANDR_name'='HDMI-1' does not exist Apr 13 17:58:46 buster gdm-password][15807]: gkr-pam: the password for the login keyring was invalid. Apr 13 17:59:20 buster login[3714]: pam_unix(login:session): session opened for user root by LOGIN(uid=0) Apr 13 17:59:20 buster systemd[1]: Created slice User Slice of UID 0. Apr 13 17:59:20 buster systemd[1]: Starting User Runtime Directory /run/user/0... Apr 13 17:59:20 buster systemd-logind[432]: New session 9 of user root. Apr 13 17:59:20 buster systemd[1]: Started User Runtime Directory /run/user/0. Apr 13 17:59:20 buster systemd[1]: Starting User Manager for UID 0...
Bug#926934: flash-kernel: /sbin/installkernel fails when flash-kernel is installed
On 12/04/2019 20:19, Vagrant Cascadian wrote:
> There may in fact be some bug in the interaction between flash-kernel
> and installkernel
There is.
I'll quote my original bug report:
> There is a conflict: installkernel assumes the /etc/kernel/postinst.d
> hook scripts can be run outside of a kernel package installation but
> flash-kernel's /etc/initramfs/post-update.d hook script assumes that
> it will only be run during a kernel package installation.
These assumptions are Debian's assumptions and they aren't changed in
PureOS. For evidence of these assumptions, please see the following:
https://salsa.debian.org/debian/debianutils/blob/82a4e5c5fe640504a5054317588406953083/installkernel#L85
https://salsa.debian.org/installer-team/flash-kernel/blob/3dc64fa3bd1e73fddbc0f3aee867a151c553fdc0/initramfs-hook/flash-kernel#L14
https://salsa.debian.org/installer-team/flash-kernel/blob/3dc64fa3bd1e73fddbc0f3aee867a151c553fdc0/functions#L695
--
Bob Ham
for (;;) { ++pancakes; }
signature.asc
Description: OpenPGP digital signature
Bug#926980: Additional reports.
Dear maintainers, I wrote my H110 Skylake box works fine with this weeks Buster image, I encountered a minor trouble. GNOME blank screen, itself is okay, but when I leave the box for a while without suspend option, HDMI wake up, and then blank again. After that, keyboard and mouse cannot simply turn the blank display on. Changing other tty, it recovers. Regards.
Bug#926920: HDMI-sound: solved
Dear maintainers, I re-checked from BIOS settings and finally found that I had ignored GNOME sound setting source even when I checked sound tests. It was set onboard S/PDIF, instead of dGPU HDMI. Changed it to the GP108's HDMI, it's okay; clear sound from GeForce 1030 HDMI output. It was clearly my fault. I am sorry again. However, the initial value should be HDMI-output, when video output is only HDMI, I think. if (video_output == HDMI-only) initial_sound_source = HDMI-sound; something like that. Of course on board HD audio S/PDIF would be better and many people might prefer that, use that. I am not familiar with S/PDIF. SUMMARY === * Kaby Lake (Z270) + GeForce 1030 with nouveau works. * GDM, GNOME, Firefox, playing on Youtube, are OK. * lm-sensors asus-isa-000 reads wrong. It just reports cpu_fan only, and the value is 0. On BIOS and visual, It is rotating. * I enabled ALPM on BIOS, since the kernel now support that; there are no-data-loss by now. * byobu, after all, seems works both on CLI and GUI. I cannot find specific log and reproduction method. * LibreOffice, Google Mozc, and Japanese inputs are OK. * AppArmor working. * Thunderbird reads local delivered logcheck summary mails. I will re-install the next week Buster image, and install Stretch and dist-upgrade, when I have time. Thank you for reading messy reports. Thank you, Debian team! Regards.
Bug#926975: Additional report
Dear maintainers, This old TOSHIBA laptop, upgraded from Stretch, started some strange behaviors. * GNOME itself is fine, but sometimes sound volume setup lost; it drops into 0%. * THIS IS MY OPINION: GNOME setting, Removal media, Software, should be "Ask what to do" by initial setting. * freshclam, daemon mode, consumes CPU significantly. Though it does stop wasting, after 10 minutes. /var/log/clam/freshclam.log : Notify Error I stopped the daemon, removed cvd files under /var/lib, "dpkg-reconfigure clamav-freshclam" to disable notification, then restarted the daemon. log seems fine now. CPU wasting stopped. Perhaps it might be better to remove cvd files and disable notification on dist-upgrade. clamscan works. Regards.
Bug#927037: Message didn't fully fit inside its window
Package: debian-installer
Severity: minor
I recall when the graphical installer got to this message,
Name: partman-crypto/progress/plain_erase_text
Type: text
Description: The installer is now overwriting ${DEVICE} with zeroes to delete
its previous contents. This step may be skipped by cancelling this action.
it didn't fully fit in its window, so people couldn't see the last part
of the sentence.
Bug#927045: ^C doesn't work when booting into recovery mode
Package: installation-reports Severity: minor Just want to let you know after a fresh install, when booting into "(recovery mode)" from the grub menu, and typing the root passwd, # cat ^C doesn't interrupt cat, etc. One needs ^Z, then "kill %" to stop it. Yes, these just reported the same as on a normal fully working terminal: # stty -a speed 38400 baud; rows 48; columns 128; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0; -parenb -parodd -cmspar cs8 hupcl -cstopb cread -clocal -crtscts -ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany imaxbel iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke -flusho -extproc # stty -g 6502:5:4bf:8a3b:3:1c:7f:15:4:0:1:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0 So I don't know what the problem is. Note I had only installed the packages contained on Debian GNU/Linux 9.8.0 _Stretch_ - Official amd64 NETINST 20190216-11:59"; with no internet connection. Sure, after adding more packages and rebooting, the problem went away. So do try it with the bare bones install from just http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/ with no network connection to download extra packages. The only other odd thing I did was add nomodeset to linux /boot/vmlinuz-4.9.0-8-amd64 ... in grub.
