June 2015 - luv-main - example.com

Re: [luv-beginners] linux noob - install problems, installfests?
by Trent W. Buck 09 Jun '15

09 Jun '15

Wen Lin wrote: > One key point: *BIOS and UEFI: set it to AHCI* Unless you're dual-booting, *always* set your SATA controllers to AHCI. The options "legacy", "hybrid" and "PATA" are worse choices for Linux. Erratum: current hardware seems to add NVMe, which appears to be better? https://en.wikipedia.org/wiki/NVMe_vs_AHCI > using the parameter 'noatime'. The default should be relatime (check /proc/mounts), which should be near enough. Changing it to noatime will break a handful of programs, but you probably don't use them anyway.

1 0

Cups and printer conundrums
by Mark Trickett 08 Jun '15

08 Jun '15

Hello All, I have an Canon LPB-5050N, old stock obviously as it is discontinued. I have the Canon CAPT software, version 2.30 which includes both RPM's and DEB's. The only problem is that the RPM's are both 32 and 64 bit, but the DEB is only 32 bit and I want to install on a 64 bit Debian system. Add to that the machine is (mostly) airgapped, and my 'net access is dialup. There are instructions in the archive, and I can consider using "alien" on the 64 bit RPM, but I would prefer to do it in a cleaner fashion. I would appreciate any comments. The appropriate two pieces of software have the source in the package, but I am not certain that computer has all the necessary development packages, yet. It is also that the deb scripts will put the appropriate files in the right places, and do a lot of the registering and configuring, which is why I am using Debian for the administration tools. Regards, Mark Trickett

4 5

xrdp and elevated privileges
by Tim Hamilton 07 Jun '15

07 Jun '15

I use xrdp to remote desktop into one of my machines (Ubuntu Mate 14.04) when I need to use a gui. This works reasonably well, though xrdp does not allow tasks that require elevated privileges to run as it doesn't seem to properly call the graphical password prompt. Calling the program from the command line with gksudo works fine, but is suboptimal as you need to know the name of the binary you're calling. This post [1] describes one way to solve this little problem, and it works well except for it to work it requires the xrdp service to be restarted (or manually started if it's not started at boot) via ssh after a reboot. I've tried having the xrdp service start late in the boot process in case it depends upon another service, but that doesn't seem to help. I've also tried adding a script to /etc/rc.local to restart xrdp on boot. This appears to work fine but the service is not available after boot. Attempting to restart (or stop / start) it via ssh gives an error that it's already running. Any suggestions on how I can get xrdp to start properly on boot? [1] http://forums.linuxmint.com/viewtopic.php?f=47&t=61971 -- Vote NO in referenda.

1 0

strange SATA errors
by Russell Coker 03 Jun '15

03 Jun '15

[ 477.971022] ata1.00: exception Emask 0x50 SAct 0xc00 SErr 0x290b02 action 0xe frozen [ 477.971107] ata1.00: irq_stat 0x01400000, PHY RDY changed [ 477.971166] ata1: SError: { RecovComm UnrecovData Persist HostInt PHYRdyChg 10B8B BadCRC } [ 477.971243] ata1.00: failed command: READ FPDMA QUEUED [ 477.971305] ata1.00: cmd 60/a8:50:00:13:ed/00:00:05:00:00/40 tag 10 ncq 86016 in [ 477.971308] res 40/00:58:a8:13:ed/00:00:05:00:00/40 Emask 0x50 (ATA bus error) [ 477.971449] ata1.00: status: { DRDY } [ 477.971501] ata1.00: failed command: READ FPDMA QUEUED I was using dd to copy /dev/sda3 to /dev/sdb3 on a system that is usually running Windows but doesn't appear to have hardware problems. Then I saw the above message about a READ error on ata1.00 in the kernel log followed immediately by the below message about a WRITE error on ata2.00. Any ideas about what might be happening here? I've attached the entire kernel message log. [ 477.971763] ata1: hard resetting link [ 477.971796] ata2.00: exception Emask 0x50 SAct 0x3fffe000 SErr 0x480800 action 0x6 frozen [ 477.971877] ata2.00: irq_stat 0x08000000, interface fatal error [ 477.971937] ata2: SError: { HostInt 10B8B Handshk } [ 477.971994] ata2.00: failed command: WRITE FPDMA QUEUED [ 477.972082] ata2.00: cmd 61/00:68:00:2c:e7/04:00:05:00:00/40 tag 13 ncq 524288 out [ 477.972087] res 40/00:68:00:2c:e7/00:00:05:00:00/40 Emask 0x50 (ATA bus error) [ 477.972233] ata2.00: status: { DRDY } [ 477.972287] ata2.00: failed command: WRITE FPDMA QUEUED -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/

3 4