antiX-17-b3-full, base, net, core-libre for testing - Page 2

BitJam · posted: 2017-08-20 22:43

@eugen-b re: openchrome. I think you're saying that the openchrome video driver worked with kernel 4.9.6-antix-sid.1-486-smp in antiX-17.a3 but fails with the newer kernel found in antiX-17.b3 (32-bit? 64-bit?). It wasn't clear to me if the vesa driver worked or not. It sounds like this is a regression in the beta openchrome video driver (see bug list
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://bugs.freedesktop.org/buglist.cgi?component=Driver%2Fopenchrome&product=xorg&resolution=---"
linktext was:"here"
====================================
). I don't think there is anything the antiX devs can do about this except make the older kernels available to you and try to make it easy to get X working at all OOTB on the live system. Video drivers can be difficult to write, especially if you have to reverse-engineer proprietary hardware. I've also noticed that legacy hardware tends to get short shrift.

In antiX-17.b3_x64-full version 0.5.0 of openchrome is used. According to the bug list a 0.6 version is available. If you want to muck about with the latest versions you could trying installing them using the direction here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.freedesktop.org/wiki/Openchrome/Installation/"
linktext was:"Openchrome installation"
====================================
.

eugen-b · posted: 2017-08-20 23:17

@BitJam, thanks for the infos! It is already kind of good news that people are working on a new version of the openchrome driver at all. I have a 32bit system, vesa driver works. I looked and on antiX-17-b3 openchrome 0.5.0-3 is installed. I could install 0.6 from experimental
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/experimental/xserver-xorg-video-openchrome"
linktext was:"https://packages.debian.org/experimenta ... openchrome"
====================================

However, I will check first on my working antiX-17-a2 install on the VIA machine which kernel (or Xorg) version starts to fail.

Remaster on the live USB doesn't work, not enough space. Will try some time later.

eugen-b · posted: 2017-08-20 23:56

BitJam wrote:Thanks d_o!
1) After running one of the versions that fails, what is the output of this command:
Code: Select all
sudo wipefs -n /dev/sdb2

Code: Select all

=> makefs-uefi
Error: Could not mount /dev/sdd2 at /run/live-usb-maker.v12/uefi

live-usb-maker.v12 took 29 seconds.
eugen@antx:~/Downloads/live-usb-maker-v12-v13
$ sudo wipefs -n /dev/sdd2
offset               type
----------------------------------------------------------------
0x31ff006            nilfs2   [filesystem]
                     LABEL: neju
                     UUID:  37edf735-1929-4657-8135-f5c21615930e

0x36                 vfat   [filesystem]
                     LABEL: antiX-uefi
                     UUID:  FFA2-E78A

2) Also after a failure, please take a look at the output of"dmesg" command or upload it so I can take a look. Here is how I like to view the output:
Code: Select all
dmesg --color=always | less -R
You can also get to this via the antiX-cli-cc command -->"System Information" -->"dmesg". You can save the output to a file (with colored text) using:
Code: Select all
dmesg --color=always > dmesg.out
This is a longshot but it might provide a hint as to why most people aren't running into this problem.

See dmesg output attached.

3) Finally, please try version 14 that I've attached and see if that works. In it I call wipefs after manually clearing each file system.

In a moment. Edit: No it fails again.

Code: Select all

=> partition-clear                                                                      
=> partition-make
Using msdos partitioning
=> makefs-bios
=> makefs-uefi
Error: Could not mount /dev/sdd2 at /run/live-usb-maker.v14/uefi

live-usb-maker.v14 took 27 seconds.
eugen@antx:~/Downloads/live-usb-maker-v14
$ sudo wipefs -n /dev/sdd2
offset               type
----------------------------------------------------------------
0x31ff006            nilfs2   [filesystem]
                     LABEL: neju
                     UUID:  37edf735-1929-4657-8135-f5c21615930e

0x36                 vfat   [filesystem]
                     LABEL: antiX-uefi
                     UUID:  2272-42DA

I'm attaching the corresponding dmesg output.

BitJam · posted: 2017-08-21 01:00

Thanks eugen-b!
The dmesg output says gtkam is reporting a segfault in libglib right after several read errors on the usb device. I'm not certain the segfault is related to the usb problems but I think the usb problems reported by dmesg are why no one else sees the error you are getting in live-usb-maker. It's possible the segfault is triggered by the hardware problem. Do you use gtkam. Was it running? If you do have gtkam running then you could try turning it off and see if the problem goes away. My guess is a hardware problem is triggering both the live-usb-maker error and the gtkam segfault so turning off gtkam won't help.

The output of wipefs shows that it is indeed seeing two file systems. The nilfs file system is reported to have an offset of exactly 50 Meg which is the exact size of the fat32 partition. This means it is in an area of the usb-stick that is past the end of the fat32 partition. That area should not be accessible via the /dev/sdd2 partition.

My preliminary conclusion is that this problem was caused by a combination of a hardware bug and a software bug. We can work around it by specifying the file system type when we mount. There is no need to increase the size of the area we clear because it appears we would have to clear past the end of the partition to fix this. Also, IMO wipefs is buggy and shouldn't be used since we don't want to clear out a file system that is in the area of the next partition on the disk although it might be aided and abetted by a hardware problem.

Have you been using the nilfs file system? Can you think of any reason why it would have existed on the last 1 Meg of your usb-sticks? It is possible there is a wacky hardware error that by some miracle is reporting the signature of the nilfs file system in that last 1 Meg regardless of what is actually on the stick. But I have no idea why that area of the usb-stick can even by accessed via the /dev/sdd2 device.

Please try adjusting the size of the area used by live-usb-maker which you can do by choosing"Make a customized live-usb (includes encryption option)" at the first menu. This was one of my first suggestions to try to rule out a hardware problem. Swapping sticks won't rule out a hardware problem in the controller. I hope this will be the final test I ask you to do. I greatly appreciate all of your help. Thank you!

eugen-b · posted: 2017-08-21 01:08

BitJam wrote:Thanks eugen-b!
The dmesg output says gtkam is reporting a segfault in libglib right after several read errors on the usb device. I'm not certain the segfault is related to the usb problems but I think the usb problems reported by dmesg are why no one else sees the error you are getting in live-usb-maker. It's possible the segfault is triggered by the hardware problem. Do you use gtkam. Was it running? If you do have gtkam running then you could try turning it off and see if the problem goes away. My guess is a hardware problem is triggering both the live-usb-maker error and the gtkam segfault so turning off gtkam won't help.

I used gtkam to upload the photo of the broken X. It took a bit to figure out how it works. But the error occured before and after the usage of gtkam.

Have you been using the nilfs file system? Can you think of any reason why it would have existed on the last 1 Meg of your usb-sticks? It is possible there is a wacky hardware error that by some miracle is reporting the signature of the nilfs file system in that last 1 Meg regardless of what is actually on the stick. But I have no idea why that area of the usb-stick can even by accessed via the /dev/sdd2 device.

I used to format the USB sticks sometimes nilfs or f2fs before writing an ISO to them. But It would be a coincidence if both USB sticks had nilfs on them before and failed for that reason.

Please try adjusting the size of the area used by live-usb-maker which you can do by choosing"Make a customized live-usb (includes encryption option)" at the first menu. This was one of my first suggestions to try to rule out a hardware problem. Swapping sticks won't rule out a hardware problem in the controller. I hope this will be the final test I ask you to do. I greatly appreciate all of your help. Thank you!

Ok, will try.
Update: It worked!

Code: Select all

eugen@antx:~/Downloads/live-usb-maker-v14
$ sudo ./live-usb-maker.v14
[sudo] password for eugen: 
===============================================================================
Starting live-usb-maker.v14
===============================================================================
Only one target usb device was found sdd  3.8G Generic Flash Disk
Will use target device sdd
                                                                                        
Please select what action to perform                                                    
> Make a full-featured live-usb                                                         
> Make an encrypted full-featured live-usb                                              
= Make a customized live-usb (includes encryption option)                               
> Update UUIDs on an existing live-usb                                                  
> Update boot parameters on an existing live-usb                                        
> Reinstall legacy bootloader on an existing live-usb                                   
Press <Enter> to select the highlighted entry                                           
Use 'r' to redraw, 'q' to quit                                                          
                                                                                        
Create an encrypted live-usb?                                                           
> yes                                                                                   
= no                                                                                    
Press <Enter> to select the highlighted entry                                           
Use 'r' to redraw, 'q' to quit                                                          
                                                                                        
Please select the source for the new live-usb                                           
= Copy from an ISO file                                                                 
Press <Enter> to select the highlighted entry                                           
Use 'r' to redraw, 'q' to quit                                                          
Please enter the filename                                                               
(tab completion is enabled)
/media/ISO/antiX-17.b3_386-base.iso
You entered: /media/ISO/antiX-17.b3_386-base.iso                                                                                                                                  
Is this correct?                                                                        
= yes                                                                                   
> no                                                                                    
Press <Enter> to select the highlighted entry                                           
Use 'r' to redraw, 'q' to quit                                                          
Will use source file /media/ISO/antiX-17.b3_386-base.iso                                
Distro: antiX-17.b3_386-base Heather Heyer 18 August 2017
                                                                                        
Customize language and timezone?                                                        
> yes                                                                                   
= no                                                                                    
Press <Enter> to select the highlighted entry                                           
Use 'r' to redraw, 'q' to quit                                                          
                                                                                        
                 Total   Used  Extra
   entire drive  3,900  3,899      1  MiB
 main partition  3,849    618  3,231  MiB
 uefi partition     50     11     39  MiB
                                                                                        
Do you want to change how much of the device is used?                                   
= yes                                                                                   
> no                                                                                    
Press <Enter> to select the highlighted entry                                           
Use 'r' to redraw, 'q' to quit                                                          
                                                                                        
Please select how much space to use for the live-usb partitions                         
>  100% 3,900 MiB                                                                       
=   95% 3,705 MiB                                                                       
>   90% 3,510 MiB                                                                       
>   85% 3,315 MiB                                                                       
>   80% 3,120 MiB                                                                       
>   75% 2,925 MiB                                                                       
>   70% 2,730 MiB                                                                       
>   65% 2,535 MiB                                                                       
>   60% 2,340 MiB                                                                       
>   55% 2,145 MiB                                                                       
>   50% 1,950 MiB                                                                       
>   45% 1,755 MiB                                                                       
>   40% 1,560 MiB                                                                       
>   35% 1,365 MiB                                                                       
>   30% 1,170 MiB                                                                       
>   25%   975 MiB                                                                       
>   20%   780 MiB                                                                       
>   18%   702 MiB                                                                       
Press <Enter> to select the highlighted entry                                           
Use 'r' to redraw, 'q' to quit                                                          
Have set size to 95% (3,704 MiB)                                                        

                 Total   Used  Extra
   entire drive  3,900  3,704    196  MiB
 main partition  3,654    617  3,037  MiB
 uefi partition     50     11     39  MiB

-------------------------------------------------------------------------------
Ready to make live-usb on device sdd
... by copying file /media/ISO/antiX-17.b3_386-base.iso
-------------------------------------------------------------------------------
                                                                                        
Shall we begin?                                                                         
= yes                                                                                   
> no                                                                                    
> pretend mode                                                                          
Press <Enter> to select the highlighted entry                                           
Use 'r' to redraw, 'q' to quit                                                          
=> partition-clear                                                                      
=> partition-make
Using msdos partitioning
=> makefs-bios
=> makefs-uefi

Filesystem     Type  Size  Used Avail Use% Mounted on
/dev/sdd1      ext4  3.6G  7.2M  3.6G   1% main
/dev/sdd2      vfat   50M     0   50M   0% uefi

=> copy-uefi
copy from iso to uefi partition
files: [Ee][Ff][Ii] boot/{grub,uefi-mt} version
Fix uefi memtestbug
=> copy-main
copy from iso to main partition
files: *
|===================================================================================>100%
=> uuids
=> install
extlinux version 6.03

Filesystem     Type  Size  Used Avail Use% Mounted on
/dev/sdd1      ext4  3.6G  618M  3.0G  18% main
/dev/sdd2      vfat   50M   12M   39M  24% uefi

=> done

live-usb-maker.v14 took 2 minutes and 46 seconds.

eugen-b · posted: 2017-08-21 01:20

Ok, I got the VIA machine booting with the latest kernel installed on antiX-17-a2

Code: Select all

eugen@antix ~> inxi -Fxxxz
System:    Host: antix Kernel: 4.10.5-antix.1-486-smp i686 (32 bit gcc: 6.3.0)
           Desktop: LXDE (Openbox 3.6.1) info: lxpanel dm: lightdm
           Distro: antiX-17.a2_386-net keerfa 9 February 2017
Machine:   Device: desktop Mobo: VIA model: VX800 v: 1.0
           BIOS: Phoenix v: 6.00 PG date: 09/15/2010
CPU:       Single core VIA Eden (-UP-) cache: 128 KB
           flags: (nx pae sse sse2 sse3) bmips: 1994 speed/min/max: 1000/400/1000 MHz
Graphics:  Card: VIA VX800/VX820 Chrome 9 HC3 Integrated Graphics
           bus-ID: 00:01.0 chip-ID: 1106:1122
           Display Server: X.Org 1.19.2 driver: openchrome
           Resolution: 1366x768@59.79hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.9, 128 bits)
           GLX Version: 3.0 Mesa 13.0.6 Direct Rendering: Yes
Audio:     Card VIA VT8237A/VT8251 HDA Controller
           driver: snd_hda_intel bus-ID: 00:14.0 chip-ID: 1106:3288
           Sound: ALSA v: k4.10.5-antix.1-486-smp
Network:   Card-1: Ralink RT2790 Wireless 802.11n 1T/2R PCIe
           driver: rt2800pci v: 2.3.0 bus-ID: 02:00.0 chip-ID: 1814:0781
           IF: wlan0 state: down mac: <filter>
           Card-2: Realtek RTL-8110SC/8169SC Gigabit Ethernet
           driver: r8169 v: 2.3LK-NAPI port: bc00
           bus-ID: 04:06.0 chip-ID: 10ec:8167
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 4.0GB (66.8% used)
           ID-1: /dev/sda model: SanDisk_SDCFH size: 4.0GB
           serial: DBZ120210112144
Partition: ID-1: / size: 3.8G used: 2.5G (98%) fs: btrfs dev: /dev/sda1
Sensors:   System Temperatures: cpu: 45.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 122 Uptime: 2 min Memory: 158.8/2776.4MB
           Init: SysVinit v: N/A runlevel: 5 default: 5 Gcc sys: N/A
           Client: Shell (fish running in terminator) inxi: 2.3.5

Then I suppose it must be the /etc/X11/xorg.conf which makes the difference

Code: Select all

eugen@antix ~> cat /etc/X11/xorg.conf
##
## Generated by mhwd - Manjaro Hardware Detection
##
Section"Screen"
    Identifier"Screen0"
    Device      "Card0"
EndSection
Section"Device"
    Identifier "Device0"
    Driver     "openchrome"
    Option     "DRI3"  "0"
    Option     "DRI"   "2"
EndSection

 
Section"DRI"
        Group "video"
        Mode   0666
EndSection

 
Section"Extensions"
    Option"Composite""Enable"
    Option"RENDER"   "Enable"
EndSection

 
Section"InputClass"
    Identifier         "Keyboard Defaults"
    MatchIsKeyboard       "yes"
    Option             "XkbLayout""de,ru"
    Option             "XkbModel""pc104"
    Option             "XkbVariant"",phonetic"
    Option             "XkbOptions""grp:alt_shift_toggle"
EndSection

BitJam · posted: 2017-08-21 03:00

eugen-b wrote:Ok, I got the VIA machine booting with the latest kernel installed on antiX-17-a2
[...]
Then I suppose it must be the /etc/X11/xorg.conf which makes the difference

I agree. Where did that xorg.conf come from? Did you copy it from another system? Did you run mhwd? I was assuming you were using a stock antiX system. I am almost forced to make that assumption unless you tell me you've made changes such as adding this xorg.conf file. Did you edit the file or was all of it generated by mhwd? I've found mhwd code that generates most of what is in it but the two DRI lines in the"Device" section look customized.

It is not clear to me if we should bother detecting your hardware and then autogenerate the parts of that xorg.conf that are needed to get openchrome working on your system. If the settings were needed on all openchrome hardware then I'd imagine they would be the defaults and thus not needed.

We should be able to add the composite section fairly easily if one of the xorg=... arguments is"composite". I don't know how many people would find this useful.

For automatic detection of your hardware I would need to see the output of"lspci -nn" but I'm not sure if I am going to follow through and add it. It is usually a bit of a puzzle connecting PCI bus ids with what xorg.conf options are needed. Sometimes it depends on the kernel version. We've tried to handle all the wacky Intel problems. If I had solid information linking PCI bus ids with xorg.conf options then I would probably automate it but in the past with Intel I had to figure out the connections myself (with help from d_o and others) and sometimes guess.

BitJam · posted: 2017-08-21 03:44

dolphin_oracle wrote:*edit* update - clone mode in VB only works for me on a 64 bit VB session.

Clone mode with antiX-17.b3_386-full worked here. Whether you are cloning or copying from an iso file the mount error can still be an issue (perhaps sporadic). The wait_for_file() fix should work. Do you have any other issues with live-usb-maker? I really appreciate your feedback.

BitJam · posted: 2017-08-21 04:07

eugen-b wrote:I used gtkam to upload the photo of the broken X. It took a bit to figure out how it works. But the error occured before and after the usage of gtkam.

Okay. It is probably an unrelated bug, perhaps triggered by the same hardware problem.

I used to format the USB sticks sometimes nilfs or f2fs before writing an ISO to them. But It would be a coincidence if both USB sticks had nilfs on them before and failed for that reason.

I think the failure is a hardware problem of some sort. It makes more sense to me that nilfs was found by wipefs if it might have existed on one or both sticks. The problem seems much less miraculous now. You did nothing wrong. I think I have an easy way to make this rare problem even less likely to happen. Is it possible that an nilfs partition existed on the usb stick right before you ran live-usb-maker? I can clear out all of the existing file systems before I clear out the partition table. If the hardware is working correctly then this is probably not needed but it is easy to do so why not?

BJ: Please try adjusting the size of the area used by live-usb-maker [...]
e-b: It worked!

Great! This confirms (in my mind) that it is a wacky hardware issue. I still plan to implement the fix of specifying the file system types because that makes the code more robust. I'm glad we went through this and got an improvement to the code. When the hardware is flaky then all bets are off but if we can get the code to work anyway, that's a good thing.

thriftee · posted: 2017-08-21 06:08

I installed the 64 bit version to my Dell I7 - 7559 laptop which has EFI and Grub wouldn't install to EFP, same as with antiX-17-b2-full

the error again...

minstall

Sorry, installing GRUB failed. This may be due to a change in the disk formatting. You can uncheck GRUB and finish installing antiX Linux then reboot to the CD and repair the installation with the reinstall GRUB function.

This time the machine won't boot to the antiX on the EFI boot list, so I can't use the Debian Wiki instructions to rescue it.

BitJam · posted: 2017-08-21 09:21

@thriftee, I don't mean to ignore you but I'm not working on the installer so I can't help. Sorry. I realize that breakage in the installer is serious.

@d_o, @eugen-b, I've pushed the fixes to my live-usb-maker and cli-shell-utils github repos. It was cleaner to move some of the Virtual Box fix into the library. Unfortunately, this means that I cannot just send you a copy of live-usb-maker for testing. If you are really itching to test then I suggest cloning those two repos and running from there. I can provide instructions. Otherwise you will need to wait for new packages. I will test the Virtual Box fix here and I'm pretty confident the fix for eugen-b's machine is working. It didn't require any changes to the lib.

Edit: @eugen-b, if you get a chance, I'd like to see the output of"lspci -nn" from your VIA machine. I'd also like to know if you edited that xorg.conf file that fixed your problems with openchrome (if you remember).

gelosoil · posted: 2017-08-21 17:34

I got the full ,managed finally to create a bootable 16GB scandisk usb ,using the Universal USB creator,(all other tries failed miserably) and i love it!!
Only complaint from me is missing the old (antix 16)wireless connection program(dont recall the name now),but ceni did its job fine.
Also i wonder why dont you instead of firefox use slimjet.I find it really enough for all my needs and it is light.
In all,i cant waitfor the final.. __{{emoticon}}__
Best regards
GS

Architecture: i686
CPU op-mode(s): 32-bit
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 13
Model name: Intel(R) Pentium(R) M processor 1.60GHz
Stepping: 6
CPU MHz: 1600.000
CPU max MHz: 1600.0000
CPU min MHz: 600.0000
BogoMIPS: 3200.10
Flags: fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts est tm2

eugen-b · posted: 2017-08-21 19:11

BitJam wrote: Edit: @eugen-b, if you get a chance, I'd like to see the output of"lspci -nn" from your VIA machine. I'd also like to know if you edited that xorg.conf file that fixed your problems with openchrome (if you remember).

Yeah, I edited xorg.conf on my installed system. I tried to edit it on the live system persistently, but it looks like it gets recreated on every boot. Here is the output you wanted

Code: Select all

eugen@antix ~> lspci -nn
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VX800 Host Bridge [1106:0353] (rev 14)
00:00.1 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Error Reporting [1106:1353]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Host Bus Control [1106:2353]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. VX800 PCI to PCI Bridge [1106:3353]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Power Management Control [1106:4353]
00:00.5 PIC [0800]: VIA Technologies, Inc. VX800/VX820 APIC and Central Traffic Control [1106:5353]
00:00.6 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Scratch Registers [1106:6353]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 North-South Module Interface Control [1106:7353]
00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. VX800/VX820 Chrome 9 HC3 Integrated Graphics [1106:1122] (rev 11)
00:02.0 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:c353]
00:03.0 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:e353]
00:03.1 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:f353]
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VX800 Serial ATA and EIDE Controller [1106:5324]
00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.2 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.4 USB controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 90)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VX800/VX820 Bus Control and Power Management [1106:8353]
00:11.7 Host bridge [0600]: VIA Technologies, Inc. VX8xx South-North Module Interface Control [1106:a353]
00:13.0 PCI bridge [0604]: VIA Technologies, Inc. VX855/VX875/VX900 PCI to PCI Bridge [1106:b353]
00:14.0 Audio device [0403]: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller [1106:3288] (rev 20)
02:00.0 Network controller [0280]: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe [1814:0781]
04:06.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet [10ec:8167] (rev 10)

skidoo · posted: 2017-08-21 19:53

Testing live 64-bit b3 full. It seems solid. Following my usual testing regimen, I've found zero functional bugs.

One cosmetic issue I screencapped ~~ odd wordwrap due to a too-small dialogbox:

FWIW, I still haven't been able to reproduce the"icewm conky blur"

dolphin_oracle · posted: 2017-08-21 19:55

skidoo wrote:Testing live 64-bit b3 full. It seems solid. Following my usual testing regimen, I've found zero functional bugs.

One cosmetic issue I screencapped ~~ odd wordwrap due to a too-small dialogbox:

FWIW, I still haven't been able to reproduce the"icewm conky blur"

I'll echo skiddoo's comments on the conky blur. I haven't seen it in a while either. And I've been changing a lot of themes and desktops.