MX-14.1.1 "Symbiosis" bugfix/enhancements release

[KBD]

Just did a full install and it looks very good :-)

[james c]

Non-pae MX-14.1.1 Similar results with a bit less ram usage.Every little bit helps on these ram-challenged boxes.

Code: Select all

demo@mx1:~
$ inxi -F
System:    Host: mx1 Kernel: 3.12-0.bpo.1-486 i686 (32 bit) 
           Desktop: Xfce 4.10.2 Distro: MX-14.1.1 Symbiosis 18 June 2014 
Machine:   System: Compaq Presario 061 product: DK214A-ABA S4020WM NA210 v: 0n31411RE101SALSA10
           Mobo: N/A model: KM266-8235
           Bios: Phoenix v: AM37312 date: 03/17/2003
CPU:       Single core AMD Athlon XP 2400+ (-UP-) cache: 256 KB
           clocked at 1998 MHz
Graphics:  Card: NVIDIA NV18 [GeForce4 MX 440 AGP 8x]
           Display Server: X.Org 1.12.4 drivers: nouveau (unloaded: fbdev,vesa)
           Resolution: 1024x768@85.0hz
           GLX Renderer: Mesa DRI nv18 x86/MMX+/3DNow!+/SSE
           GLX Version: 1.2 Mesa 8.0.5
Audio:     Card VIA VT8233/A/8235/8237 AC97 Audio Controller 
           driver: snd_via82xx 
           Sound: Advanced Linux Sound Architecture v: k3.12-0.bpo.1-486
Network:   Card: Realtek RTL-8139/8139C/8139C+ driver: 8139too
           IF: eth0 state: unknown speed: 100 Mbps duplex: full 
           mac: 00:40:ca:5a:1c:14
Drives:    HDD Total Size: 80.0GB (1.5% used)
           ID-1: /dev/sda model: ST380215A size: 80.0GB
Partition: ID-1: / size: 794M used: 34M (5%) fs: rootfs dev: N/A 
           ID-2: swap-1 size: 1.26GB used: 0.00GB (0%) fs: swap dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 40.0C mobo: N/A 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 99 Uptime: 7 min Memory: 176.7/1008.7MB 
           Client: Shell (bash) inxi: 2.1.28 

Code: Select all

$ free
             total       used       free     shared    buffers     cached
Mem:       1032932     743132     289800          0      95460     466992
-/+ buffers/cache:     180680     852252
Swap:      1228936          0    1228936

[Gordon Cooper]

I just pick Windows on /dev/sda1 and that throws me to the Puppy/Windows boot screen to pick from there.

Comment: After regularly runnng into Grub/Boot problems on my old multiboot (invariably my fault) I keep a copy
of Puppy on a 60 cent CD. Boot from the disk, run Puppy's Grub4Dos utility, and Grub is restored in good working
order. I'll be doing that again after installing 14.1.1 to replace an older distro, Puppy's Grub display is uncluttered
and in larger type.

[tascoast]

I got this warning about disc errors after selecting my existing MX-14 partitions (root/home) for a fresh install of the latest *.iso (MX-14.1.1-pae.iso).

It might be a spurious alert as I've not experienced disc errors before. I hunted for a means of scanning but am unfamiliar with Linux utilities for this.

Given the warning I cancelled the above install pending consideration of disc health and clarification.

kindly

Mick

[dyfi]

Have played around with the liveCD, booted it to RAM, wireless connected - everything appears to work satisfactorily. Nice release, thanks.

[chrispop99]

I got this warning about disc errors after selecting my existing MX-14 partitions (root/home) for a fresh install of the latest *.iso (MX-14.1.1-pae.iso).

It might be a spurious alert as I've not experienced disc errors before. I hunted for a means of scanning but am unfamiliar with Linux utilities for this.

Given the warning I cancelled the above install pending consideration of disc health and clarification.

kindly

Mick

It would be inadvisable to use that machine if you have data on it that you care about.

First step should be to secure any data. Best way to do so is to boot the new MX-14.1.1.1 CD, and then copy off anything you need from the hard disk. How you do that will depend on the size of any data, and what means you have to store it. Optical media, USB thumb drive, external HDD, over a network to another machine - use what suits you.

To get more detailed information about your disk, whilst still running live open a terminal and become Root. (Type su, press enter, type root as the password.) Enter the following:

Code: Select all

smartctl -a /dev/sda | less

You can then scroll down a list of information.

If you are not comfortable using a terminal, whilst still running live install gsmartcontrol via Synaptic. After install, it will appear in the 'System' menu. Run it and explore the tabbed information. The error log will be the most useful.

If errors are shown ( I will eat my hat if there are none!), go to the 'Perform Tests' tab and select 'Extended Self-test' from the drop-down.

Ailing drives are a complete nightmare; total failure is not necessarily the worst problem they cause. (You do have backups, I hope!) If in any doubt about your drive, it will be advisable to replace it. Don't be tempted to keep the old one just for data - dump it!

Chris

[chrispop99]

Just a heads-up - we have been bitten by the Mozilla 'take over your files' problem!

As default, clicking jpg and png graphics files will cause Iceweasel to open to display them, instead of Mirage. Bmp works as expected.

Simple fix is to right-click any jpg, select Properties, and then use the 'Open With' drop-down to select Mirage. You only need to do this once; the setting will be remembered, but will need to be done also for any png files.

Chris

[fu-sen]

A Japanese user gave up use of MX-14,
but was able to use MX-14.1.1.
I had communication from the user. I can support it and am happy.

[Richard]

Put it on a USB with dd. Boots fine, runs great,
but can not connect to Broadcom wireless, OOTB:

Code: Select all

richard@mx14:/WIN/Dropbox
$ inxi -n
Network:   Card-1: Atheros AR8132 Fast Ethernet driver: atl1c
           IF: eth0 state: down mac: 00:26:22:2b:f4:05
           Card-2: Broadcom BCM4312 802.11b/g LP-PHY driver: wl
           IF: wlan0 state: up mac: 0c:60:76:54:98:82
richard@mx14:/WIN/Dropbox

[Jerry3904]

Put it on a USB with dd. Boots fine, runs great,
but can not connect to Broadcom wireless, OOTB:

Code: Select all

richard@mx14:/WIN/Dropbox
$ inxi -n
Network:   Card-1: Atheros AR8132 Fast Ethernet driver: atl1c
           IF: eth0 state: down mac: 00:26:22:2b:f4:05
           Card-2: Broadcom BCM4312 802.11b/g LP-PHY driver: wl
           IF: wlan0 state: up mac: 0c:60:76:54:98:82
richard@mx14:/WIN/Dropbox

Hmmm: driver is associated but no AP is recognized. Please paste back the output of

Code: Select all

iwconfig wlan0

Can you manually associate it with AP using as root?:

Code: Select all

iwconfig wlan0 essid [name of your AP]