- luv-main - luv.asn.au

Iceweasel or ABC has sand in the gears?
by Erik Christiansen 10 Jun '15

10 Jun '15

While youtube clips show (watchable, but not entirely smooth) motion in iceweasel on my new debian 7.8.0 install, ABC clips bearing the simple two-circle Venn diagram symbol in the TLH corner show only a static video image, and even the audio feed is interrupted. Is there some way to diagnose where the pipe is most constricted? (The 10 MB file at http://mirror.internode.on.net/pub/test/ took 20 seconds.) Does anyone else have trouble with the ABC's new video clip dingus? Erik

3 4

Re: CUPS and "broken pipe" and Canon LBP-5050N
by Mark Trickett 10 Jun '15

10 Jun '15

Hello All, Still chasing, but a slightly different tack. When I set it up, it sets to "socket://192.168.0.215" which research shows as the HP JetDirect protocol. There are comments in the CUPS documentation that the vendors implement the IPP (Internet Printing Protocol) with deficiencies that mean it is better to use other protocols. Does anyone here have any information to contribute? I do not want to run Windows, but will set up a Windows box if necessary and sniff the packets to see what is going on. That will take undue time and effort at the moment, but would provide real answers. If anyone can find answers where someone has done any of that, I would very much appreciate information. I would still appreciate a bit of a network primer about the netmask and the like. I also need to "discover" the ip address of the switch I have, it does not respond at what I have found on the net as the default ip address. Regards, Mark Trickett

1 0

CUPS and "broken pipe"
by Mark Trickett 10 Jun '15

10 Jun '15

Hello All, Have continued looking hither and yon and cannot find what specifies invocation of filters and the like, cannot see where there might be a broken pipe. Is it piping between filters and programs, or perhaps the networking. Still not certain. Regards, Mark Trickett

2 2

Re: [luv-beginners] linux noob - install problems, installfests?
by Russell Coker 09 Jun '15

09 Jun '15

On Mon, 8 Jun 2015 09:01:26 AM Wen Lin wrote: > Another key point: A Solid State Drive is worn down relatively quickly by > write actions. So this site introduced steps/commands on how to minimise > the action of writing to SSD by turning off the updating whenever a file is > read (last accessed time) - using the parameter 'noatime'. It has already been pointed out that relatime is default now. It would be interesting to compare the amount of data written for that vs for other operations. Modern SSDs are designed for significant volumes of disk writes. When you use an SSD as a ZIL for a ZFS filesystem it will get a copy of all data that is written to the entire RAID array. We aren't seeing reports of SSDs failing when used for a ZIL. Some previous analysis of potential SSD lifetimes on this list suggested that they should be good for at least 5 years. If that was the case then they would often outlast hard drives. If your data is important then you will have multiple drives used in some form of RAID array or really good backups (in the case of systems that can't do RAID such as typical laptops). So you shouldn't be particularly worried about the life of SSDs. As with hard drives you can expect them to last long enough that you want bigger ones before they wear out. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/

1 0

Re: [luv-beginners] linux noob - install problems, installfests?
by Chris Samuel 09 Jun '15

09 Jun '15

Hi Wen, Justin, On Mon, 8 Jun 2015 09:01:26 AM Wen Lin wrote: > Another key point: A Solid State Drive is worn down relatively quickly by > write actions. So this site introduced steps/commands on how to minimise > the action of writing to SSD by turning off the updating whenever a file is > read (last accessed time) - using the parameter 'noatime'. That's out of date - the kernel already defaults to "relatime" (since 2.6.30, released 6 years ago pretty much today), Red Hat describe it thus: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/ht… # Relatime maintains atime data, but not for each time that a file # is accessed. With this option enabled, atime data is written to # the disk only if the file has been modified since the atime data # was last updated (mtime), or if the file was last accessed more # than a certain length of time ago (by default, one day). So in other words for files that aren't being written you'll get an atime update at most once a day on reading it. commit 0a1c01c9477602ee8b44548a9405b2c1d587b5a2 Author: Matthew Garrett <mjg(a)redhat.com> Date: Thu Mar 26 17:53:14 2009 +0000 Make relatime default Change the default behaviour of the kernel to use relatime for all filesystems. This can be overridden with the "strictatime" mount option. Signed-off-by: Matthew Garrett <mjg(a)redhat.com> Signed-off-by: Linus Torvalds <torvalds(a)linux-foundation.org> Best of luck! Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC

3 2

Clean install of OpenSuse 13.2 - What partitioning set up should I use?
by Andrew Greig 09 Jun '15

09 Jun '15

Years ago I was very comfortable with a multi partition setup. But on starting an upgrade to OpenSuse 31.2 I have discovered that the machine needed a serious cleanout. So I tried to repartition into SWAP, / and /home. OpenSuse recommended btrfs for / and XFS for /home. I have used XFS for years so no problems. I allocated 20Gb for SWAP and 50Gb for / and the balance to /home. The install has failed because it could not format the BTRFS partition. I expect that in the process the new partition table has been created, so maybe the historical mess is gone. Can someone recommend a "standard" btrfs set up to save me some time, please? Andrew Greig

8 11

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