Re: [gentoo-user] Re: Not able to install ksh93

2016-09-11 Thread Neil Bothwick 
On Sat, 10 Sep 2016 18:23:01 -0400, Harry Putnam wrote:

> Currently waiting out an update of world with ksh removed from world
> file.

You don't need to mess with @world if a failing package is preventing an
update. If --keep-going doesn't deal with it, --exclude ksh will.


-- 
Neil Bothwick

Velilind's Laws of Experimentation:
1. If reproducibility may be a problem, conduct the test only once.
2. If a straight line fit is required, obtain only two data points.


pgpooSGlgU5Vd.pgp
Description: OpenPGP digital signature

[gentoo-user] X-rite color calibrator not working

2016-09-11 Thread Devrin Talen 
I'm trying to use an X-rite i1 Display 3 to calibrate my laptop screen
in gnome 3 and running into some trouble.  The color calibration
settings screen opens up as soon as I plug in the calibrator, and the
first error I see is after I've gone through all the options and
clicked the start button to actually begin calibrating.

At that point the error message is:

An internal error occurred that could not be recovered.
You can remove the calibration device.

This error occurs immediately after clicking the button.

So I googled around and I found a few links to folks having similar issues:

[1]: https://github.com/hughsie/colord/pull/29
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1297167
[3]: https://bugzilla.redhat.com/show_bug.cgi?id=1000910

Out of those, the third seems to be the closest to the issue I'm
having.  From what I can see, the USB device is enumerated properly by
the kernel:

% dmesg # snipped the relevant stuff:
[ 2406.995020] usb 1-1.2: new full-speed USB device number 8 using ehci-pci
[ 2407.083266] usb 1-1.2: New USB device found, idVendor=0765, idProduct=5021
[ 2407.083275] usb 1-1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 2407.083279] usb 1-1.2: Product: i1Display3 Bootloader
[ 2407.083283] usb 1-1.2: Manufacturer: X-Rite Inc.
[ 2407.086060] hid-generic 0003:0765:5021.0004: hiddev0,hidraw0: USB
HID v1.11 Device [X-Rite Inc. i1Display3 Bootloader] on
usb-:00:1a.0-1.2/input0
[ 2407.842362] usb 1-1.2: USB disconnect, device number 8
[ 2408.019082] usb 1-1.2: new full-speed USB device number 9 using ehci-pci
[ 2408.107524] usb 1-1.2: New USB device found, idVendor=0765, idProduct=5020
[ 2408.107531] usb 1-1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 2408.107535] usb 1-1.2: Product: i1Display3
[ 2408.107538] usb 1-1.2: Manufacturer: X-Rite, Inc.
[ 2408.109804] hid-generic 0003:0765:5020.0005: hiddev0,hidraw0: USB
HID v1.11 Device [X-Rite, Inc. i1Display3] on
usb-:00:1a.0-1.2/input0

And udev seems to be happy about it:

% udevadm monitor --environment --udev # plugging in the device:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV  [3659.893310] add  /class/usbmisc (class)
ACTION=add
DEVPATH=/class/usbmisc
SEQNUM=3434
SUBSYSTEM=class
USEC_INITIALIZED=3659893139

UDEV  [3659.894709] add
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 (usb)
ACTION=add
BUSNUM=001
DEVNAME=/dev/bus/usb/001/012
DEVNUM=012
DEVPATH=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2
DEVTYPE=usb_device
DRIVER=usb
ID_BUS=usb
ID_MODEL=i1Display3_Bootloader
ID_MODEL_ENC=i1Display3\x20Bootloader
ID_MODEL_ID=5021
ID_REVISION=0001
ID_SERIAL=X-Rite_Inc._i1Display3_Bootloader
ID_USB_INTERFACES=:03:
ID_VENDOR=X-Rite_Inc.
ID_VENDOR_ENC=X-Rite\x20Inc.
ID_VENDOR_FROM_DATABASE=X-Rite, Inc.
ID_VENDOR_ID=0765
MAJOR=189
MINOR=11
PRODUCT=765/5021/1
SEQNUM=3431
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=3659894455
...

But the calibration isn't working.  Here's the bit of the journal
showing gnome complaining when I hit the start button:

% journalctl -xb # here's the relevant part:
Aug 30 22:36:23 luigi colord[1036]: (colord:1036): Cd-WARNING **: the
child exited with return code 1
Aug 30 22:36:23 luigi gnome-session[1374]:
(gnome-control-center:1829): color-cc-panel-WARNING **: calibration
failed with code 1: argyll-spotread exited unexpectedly
Aug 30 22:36:24 luigi colord[1036]: (colord:1036): Cd-WARNING **: no
child pid to kill!
Aug 30 22:36:24 luigi gnome-session[1374]:
(gnome-control-center:1829): color-cc-panel-WARNING **: failed to
start calibrate: failed to calibrate

So when I saw that I started running argyll-spotread on its own to see
if that would still fail:

% argyll-spotread -v -D4
usb_check_and_add: found instrument vid 0x0765, pid 0x5020
new_inst: called with path '/dev/bus/usb/001/013 (X-Rite i1
DisplayPro, ColorMunki Display)'
Connecting to the instrument ..
i1d3_init_coms: called
i1d3_init_coms: About to init USB
usb_open_port: open port '/dev/bus/usb/001/013' succeeded
i1d3_command: Sending cmd 'GetStatus' args '00 01 00 00 00 00 00 00'
coms_usb_transaction: Submitting urb to fd 3 failed with -1
i1d3_command: response read failed with ICOM err 0x2
coms_usb_transaction: Submitting urb to fd 3 failed with -1
i1d3_init_coms: failed with rv = 0x70062
Failed to initialise communications with instrument
or wrong instrument or bad configuration!
('Communications failure' + 'Communications failure')
urb_reaper: cleared requests

And when that happens I see this out in dmesg (the USB IDs may not
line up since I plugged and unplugged this many times):

% dmesg
[  232.711891] usb 1-1.2: usbfs: usb_submit_urb returned -28
[  232.711910] usb 1-1.2: usbfs: usb_submit_urb returned -28
[  232.784675] usb 1-1.2: reset full-speed USB device number 7 using ehci-pci

My questions are:

1. Has anyone successfully used this model of calibrator to
successfully calibrate their display with the gnome tools?

2. Am I

Re: [gentoo-user] Re: Not able to install ksh93

2016-09-11 Thread David W Noon 
> David W Noon  writes:
[snip]
>> The a look at  and see
>> if it is the same as the symptoms you are seeing.
> 
> I don't see a segmentation fault but I don't know how to recognize
> that in the massive output.  However, it appears, like one of the
> fellows on the bug report discussion says; the process fails to
> install nmake. (Which seems like that should curtail the install but
> doesn't).  The process tries to carry on without nmake and finally
> many lines later fails because of not being able to find nmake.
> 
> So sound very similar but I'm not sure about a seg-fault.

Run a grep on the ebuild log searching for "program as", since the
segfault occurs in the assembler.
-- 
Regards,

Dave  [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwn...@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Re: [gentoo-user] About "make install all" when kernel building

2016-09-11 Thread Alan McKinnon 
On 11/09/2016 01:11, Harry Putnam wrote:
> I have a newish install I've been running for a while.
> 
> Today I added a setting to the kernel and rebuilt.
> 
> The final move I made on the kernel move was
> 
>   "make install all"
> 
> No looking at the /boot/grub/grub.conf all I find is the example file
> that comes with install.
> 
> If there was old version before calling "make install all" , it has
> been removed I guess.
> 
> I've created a version from a very old one I had in some very old
> backup and wondering if all the options on the kernel line are still
> valid. (I do have the VESA ahd vesafb (frame buffer) and mtrr stuff
> checked in the kernel config). And "root" is at /dev/hda4
> 
> ,
> | default 0
> | timeout 10
> | splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> | 
> | title Gentoo Linux 4.1.6
> | root (hd0,0) 
> | kernel /boot/vmlinuz-4.1.6-gentoo root=/dev/hda4 vga=0x31A 
> video=vesafb:mtrr,ywrap
> `
> 
> I'm pretty confident of everything but the kernel line.
> 
> Before I reboot, find it fails to boot,  and have lots of huffing and
> puffing starting up with grub commands or having to go back to an
> install .ISO to get insdide, I hoped someone here could tell me if my
> grub.conf is likely to work


That config looks fine. However, you only have one kernel stanza. To be
really safe, copy the old one to a second entry and clearly label it as
the old one. Then you can select it if the new one does fail to boot.

It's easier that way than trying to edit it in grub's editor


-- 
Alan McKinnon
alan.mckin...@gmail.com

[gentoo-user] Re: About "make install all" when kernel building

2016-09-11 Thread Harry Putnam 
Alan McKinnon  writes:

> That config looks fine. However, you only have one kernel stanza. To be
> really safe, copy the old one to a second entry and clearly label it as
> the old one. Then you can select it if the new one does fail to boot.
>
> It's easier that way than trying to edit it in grub's editor

Many thanks... I remember there being those old kernel lines now that
you mention it I probably would have proceeded though without your
comment.

[gentoo-user] [SOLVED] New install, a few problems (or not?)

2016-09-11 Thread waltdnes 
On Fri, Sep 09, 2016 at 12:50:09AM -0400, waltd...@waltdnes.org wrote

> 2) "uname -a" gives the following output...
> 
> [i3][root][~] uname -a
> Linux i3 4.4.6-gentoo #4 SMP Wed Sep 7 17:12:27 Local time zone must be 
> set--see zic m x86_64 Intel(R) Pentium(R) CPU N3700 @ 1.60GHz GenuineIntel 
> GNU/Linux
> 
> 
> ...but I've already run...
> 
> [i3][root][~] emerge --config sys-libs/timezone-data
> 
> Configuring pkg...
> 
>  * Updating /etc/localtime with /usr/share/zoneinfo/Canada/Eastern

  Solved; I had to do the above *AND THEN REBUILD MY KERNEL* which
results in...

Linux i3 4.4.6-gentoo #5 SMP Sat Sep 10 00:48:23 UTC 2016 x86_64 Intel(R) 
Pentium(R) CPU N3700 @ 1.60GHz GenuineIntel GNU/Linux

> 3) The new machine is not co-operating with my hardware KVM switch.  If
> I select the machine while it's booting up, it works fine.  But if I
> switch away and come back, the VGA video does not work.  I've confirmed
> that the keyboard part of KVM still works...
> * boot up with new machine selected
> * log in as root in text console mode
> * switch away
> * switch back, and there's no video
> * but if I blindly type "poweroff", it shuts down, so keyboard works

  This is going to sound like "One weird little tip", but it works...
* boot up with new machine selected
* start up X
* run "xrandr" *WITHOUT ANY PARAMETERS*.  I put it in my ~/.xinitrc so
  that it runs automatically with each invocation of X.  Here it is...

#!/bin/bash
xset fp+ /usr/share/fonts/misc && xset fp rehash
/usr/bin/xterm -e xrandr -s 1920x1080 && xrandr --dpi 96 && sleep 10 && xrandr &
[[ -f ~/.Xresources ]] && xrdb -merge ~/.Xresources
/usr/bin/xterm -bg black -fg cyan -geometry 50x9+0+0 -fn 
lucidasanstypewriter-12 &
/usr/bin/xterm -bg black -fg cyan -geometry +0+0 -fn lucidasanstypewriter-12 &
exec /usr/bin/icewm > ~/.icewm.log 2>&1
xset dpms 240 256 260
xsetleds +num -caps -scroll


  After this I can switch back, and I get back to the X session on the
new machine.  Notes...
* "xrandr" only has to be run once.  After this, I can switch back and
  forth multiple times at will
* the ability to switch properly via my hardware KVM survives through
  dpms kicking in screensaver mode
* it does *NOT* survive reboots or stopping and re-starting X

  I assume that plain "xrandr" without any parameters does some
port-probing that sets up the video card.  It's the only explanation I
can think of.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications