Linux Mint 19 “Tara” Xfce – BETA Release
Forum rules
Section reserved for the team. You can reply to announcements here but not post new topics. Do not add support questions to threads here, use the appropriate support forum instead.
Section reserved for the team. You can reply to announcements here but not post new topics. Do not add support questions to threads here, use the appropriate support forum instead.
Re: Linux Mint 19 “Tara” Xfce – BETA Release
Has anyone else noticed that in Thunar open as root doesn't work? I did post this in the blog, was just wondering if any others were seeing this.
Last edited by HaveaMint on Mon Jun 11, 2018 8:53 am, edited 1 time in total.
"Tune for maximum Smoke and then read the Instructions".
Re: Linux Mint 19 “Tara” Xfce – BETA Release
PLEASE post bug reports Here not in the forums:
https://blog.linuxmint.com/?p=3583 for XFCE
https://blog.linuxmint.com/?p=3582 for MATE
https://blog.linuxmint.com/?p=3581 for CINNAMON
this will be a great help to the Devs as they try to fix bugs for Final release and will help all of us.
Thank You.
https://blog.linuxmint.com/?p=3583 for XFCE
https://blog.linuxmint.com/?p=3582 for MATE
https://blog.linuxmint.com/?p=3581 for CINNAMON
this will be a great help to the Devs as they try to fix bugs for Final release and will help all of us.
Thank You.
Easy tips : https://easylinuxtipsproject.blogspot.com/ Pjotr's Great Linux projects page.
Linux Mint Installation Guide: http://linuxmint-installation-guide.rea ... en/latest/
Registered Linux User #462608
Linux Mint Installation Guide: http://linuxmint-installation-guide.rea ... en/latest/
Registered Linux User #462608
Re: Linux Mint 19 “Tara” Xfce – BETA Release
Well I put the Main PC back to 18.3, too many bugs in 19 for now. I should have listened to @Moem on being a user not an explorer. Or however she said it.
"Tune for maximum Smoke and then read the Instructions".
Re: Linux Mint 19 “Tara” Xfce – BETA Release
Running with the following configuration:
The system appears to function mostly nominally with the following issues:
1) Install from Live USB fails just after the "Configuring Hardware" step. Alert dialog says "GRUB installation failed." After powering off the system, was able to boot by manually entering the "linux" and "initrd" commands to boot the installed image by using the USB stick grub menu. Once booted, I used apt install Grub-efi-ia32 to allow boot directly from the device's efi.
2) Boot from the device's efi requires "nomodeset" or "acpi_osi=" and then often requires mutiple attempts before the boot completes. Otherwise, the screen goes black and the boot hangs approximately at the point where the kernel attempts to switch from the BIOS video driver to the kernel's embedded inteldrmfb code during the boot sequence. /var/log/kern.log indicates:
3) Touchscreen works, but both X and Y axes are inverted. Touching lower-right positions the cursor at upper-left. Moving down-right drags the cursor up-left. Setting xorg.conf.d/10-evdev.conf "Option "InvertX" "true" worked in Mint 18.3-xfce but does not work in Mint-19-beta. kern.log indicates:
4) No sound. kern.log indicates:
5) Camera not recognized.
6) Accelerometer not recognized.
7) Driver Manager loads its cache, then displays a completely blank (white) window with no menus or buttons of any kind.
Code: Select all
charlie@WINBOOK:~$ inxi -Fxz
System: Host: WINBOOK Kernel: 4.15.0-23-generic x86_64 bits: 64 gcc: 7.3.0
Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: Linux Mint 19 Tara
Machine: Device: portable System: WinBook product: TW700 v: 0.1 serial: N/A
Mobo: WinBook. model: TW700 v: FAB1 serial: N/A
UEFI: Phoenix v: 1.00 IA32 date: 11/04/2014
CPU: Quad core Intel Atom Z3735G (-MCP-)
arch: Silvermont rev.8 cache: 1024 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10662
clock speeds: max: 1832 MHz 1: 955 MHz 2: 823 MHz 3: 499 MHz 4: 499 MHz
Graphics: Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
bus-ID: 00:02.0
Display Server: x11 (X.Org 1.19.6 )
drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 800x1280@60.00hz
OpenGL: renderer: Mesa DRI Intel Bay Trail
version: 4.2 Mesa 18.0.0-rc5 Direct Render: Yes
Audio: Card-1 Intel HDMI/DP LPE Audio driver: HdmiLpeAudio
Card-2 bytcr-rt5640 driver: bytcr-rt5640
Sound: Advanced Linux Sound Architecture v: k4.15.0-23-generic
Network: Card: Ralink RT5370 Wireless Adapter
driver: rt2800usb v: 2.3.0 usb-ID: 001-003
IF: wlxc83a35cca8b7 state: up mac: <filter>
Drives: HDD Total Size: NA (-)
ID-1: /dev/mmcblk1 model: N/A size: 15.6GB
ID-2: /dev/mmcblk2 model: N/A size: 62.7GB
Partition: ID-1: / size: 13G used: 6.0G (49%) fs: ext4 dev: /dev/mmcblk1p2
ID-2: swap-1 size: 1.01GB used: 0.06GB (6%)
fs: swap dev: /dev/mmcblk1p3
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 44.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 190 Uptime: 2:15 Memory: 372.9/922.1MB
Init: systemd runlevel: 5 Gcc sys: 7.3.0
Client: Shell (bash 4.4.191) inxi: 2.3.56
1) Install from Live USB fails just after the "Configuring Hardware" step. Alert dialog says "GRUB installation failed." After powering off the system, was able to boot by manually entering the "linux" and "initrd" commands to boot the installed image by using the USB stick grub menu. Once booted, I used apt install Grub-efi-ia32 to allow boot directly from the device's efi.
2) Boot from the device's efi requires "nomodeset" or "acpi_osi=" and then often requires mutiple attempts before the boot completes. Otherwise, the screen goes black and the boot hangs approximately at the point where the kernel attempts to switch from the BIOS video driver to the kernel's embedded inteldrmfb code during the boot sequence. /var/log/kern.log indicates:
Code: Select all
fb: switching to inteldrmfb from EFI VGA
...
[drm:pwm_setup_backlight [i915]] *ERROR* Failed to own the pwm chip
Code: Select all
Goodix-TS i2c-GDIX1001:00: ID 911, version: 1050
input: Goodix Capacitive TouchScreen as /devices/platform/80860F41:03/i2c-3/i2c-GDIX1001:00/input/input4
Code: Select all
Baytrail Audio Port: AsoC: no backend DAIs enabled for Baytrail Audio Port
6) Accelerometer not recognized.
7) Driver Manager loads its cache, then displays a completely blank (white) window with no menus or buttons of any kind.