Re: zabbix-server-mysql

2017-05-31 Thread Gareth de Vaux 
On Mon 2017-05-29 (18:23), Gareth de Vaux wrote:
> Hi all, I'm trying to install zabbix-server-mysql on Stretch but when I
> get to the configuration over the web stage there's no database type
> option for MySQL, only PostgreSQL. I assume this's because zabbix-server-mysql
> pulls in MariaDB rather than MySQL. How do I get zabbix to use 'MySQL'?

Ok I was missing php-mysql module.

zabbix-server-mysql

2017-05-29 Thread Gareth de Vaux 
Hi all, I'm trying to install zabbix-server-mysql on Stretch but when I
get to the configuration over the web stage there's no database type
option for MySQL, only PostgreSQL. I assume this's because zabbix-server-mysql
pulls in MariaDB rather than MySQL. How do I get zabbix to use 'MySQL'?

Re: X dies after upgrade

2016-08-07 Thread Gareth de Vaux 
On Sun 2016-08-07 (14:32), Felix Miata wrote:
> version, while your "2nd Generation Core" is newer. If I'm right about the 
> identification, you needn't be trying to use the Intel driver, but instead 
> should be able to use the server's integral modesetting driver.

You're right the internal driver works - the problem ended up being my window
manager being removed during the upgrade and me not spotting it, thanks for
the help everyone.

X dies after upgrade

2016-08-07 Thread Gareth de Vaux 
Hi all, I can't find any similar issues on this list - I upgraded my system
tracking debian testing yesterday but it's been awhile given by the Xorg
changelog at http://lordcow.org/Xorg.changelog.txt and now X doesn't start.

I installed xserver-xorg-legacy and added needs_root_rights=yes to
/etc/X11/Xwrapper.config just incase it was that. I tried creating an
xorg.conf and setting the driver to intel for older hardware as suggested
but this doesn't help. X seems to flash up for a split second but then
terminates. The unhelpful log is at http://lordcow.org/Xorg.0.log .

I'm getting nowhere trying different drivers and configs, does anyone
have an idea? Some specs:

from lspci -v:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA 
controller])
Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor 
Family Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at fb80 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at ff00 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

$ dpkg -l | grep Intel
ii  i965-va-driver:amd64  1.7.1-1   
amd64VAAPI driver for Intel G45 & HD Graphics family
ii  libcilkrts5:amd64 6.1.1-10  
amd64Intel Cilk Plus language extensions (runtime)
ii  libmpx0:amd64 5.4.0-6   
amd64Intel memory protection extensions (runtime)
ii  xserver-xorg-video-intel  2:2.99.917+git20160706-1  
amd64X.Org X server -- Intel i8xx, i9xx display driver

$ lsmod | grep i915
i915 1245184  1
video  40960  1 i915
drm_kms_helper147456  1 i915
drm   360448  3 i915,drm_kms_helper
i2c_algo_bit   16384  1 i915
button 16384  1 i915

$ cat /etc/issue
Debian GNU/Linux stretch/sid \n \l

$ uname -a
Linux fire 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 GNU/Linux

Re: Logitech unified wireless

2013-10-17 Thread Gareth de Vaux 
On Wed 2013-10-16 (13:04), Dan Ritter wrote:
  Ran into this today too (with the logitech mk520 keyboard/mouse),
  seems like you need to unpair/pair the devices on each reboot?
 
 No, once programmed the pairing ought to continue until
 reprogrammed. Keyboards paired this way should be usable at BIOS
 boot time, assuming your BIOS can cope with USB HID (almost
 all can).

I could use the keyboard/mouse in the BIOS from the start fine.
I do need to redo the pairing on each boot in the OS though.

If anyone's interested:

# uname -a
Linux cow 3.10-3-amd64 #1 SMP Debian 3.10.11-1 (2013-09-10) x86_64 GNU/Linux

# lsmod | grep logitech
hid_logitech_dj13238  0 
hid81894  5 hid_generic,usbhid,hid_logitech_dj

re-pairing:

Oct 16 14:39:26 cow kernel: [2.006318] usb 3-5: Manufacturer: Logitech
Oct 16 14:39:26 cow kernel: [6.846603] logitech-djreceiver 
0003:046D:C52B.0004: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB 
Receiver] on usb-:00:14.0-5/input2
Oct 16 14:40:02 cow kernel: [   54.497184] logitech-djreceiver 
0003:046D:C52B.0004: logi_dj_recv_destroy_djhid_device: can't destroy a NULL 
device
Oct 16 14:40:10 cow kernel: [   62.040497] logitech-djreceiver 
0003:046D:C52B.0004: logi_dj_recv_destroy_djhid_device: can't destroy a NULL 
device
Oct 16 14:40:20 cow kernel: [   72.159565] input: Logitech Unifying Device. 
Wireless PID:2011 as 
/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.2/0003:046D:C52B.0004/input/input13
Oct 16 14:40:20 cow kernel: [   72.159926] logitech-djdevice 
0003:046D:C52B.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech Unifying 
Device. Wireless PID:2011] on usb-:00:14.0-5:1
Oct 16 14:40:28 cow kernel: [   80.174418] input: Logitech Unifying Device. 
Wireless PID:1024 as 
/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.2/0003:046D:C52B.0004/input/input14
Oct 16 14:40:28 cow kernel: [   80.174985] logitech-djdevice 
0003:046D:C52B.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech Unifying 
Device. Wireless PID:1024] on usb-:00:14.0-5:2

# solaar-cli show
Unifying Receiver [/dev/hidraw1:A3E79BAD] with 2 devices
1: K520 [K520:5086F8BB] 
2: M310 [M310:2A2AC894] 


lsusb -v:

Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x046d Logitech, Inc.
  idProduct  0xc52b Unifying Receiver
  bcdDevice   12.01
  iManufacturer   1 Logitech
  iProduct2 USB Receiver
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   84
bNumInterfaces  3
bConfigurationValue 1
iConfiguration  4 RQR12.01_B0019
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower   98mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  1 Boot Interface Subclass
  bInterfaceProtocol  1 Keyboard
  iInterface  0 
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.11
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength  59
 Report Descriptors: 
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval   8
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  1 Boot Interface Subclass
  bInterfaceProtocol  2 Mouse
  iInterface  0 
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.11
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength 148
 Report Descriptors: 
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7

Re: Logitech unified wireless

2013-10-15 Thread Gareth de Vaux 
On Mon 2013-10-14 (07:18), Dan Ritter wrote:
 There's a utility called solaar which can reprogram Logitech
 mice and keyboards to use a plugged-in receiver; it's at
 http://pwr.github.io/Solaar/index.html

Ran into this today too (with the logitech mk520 keyboard/mouse),
seems like you need to unpair/pair the devices on each reboot?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131015151838.ga57...@lordcow.org

Re: Realtek RTL8111/8168B death

2012-08-28 Thread Gareth de Vaux 
On Mon 2012-08-27 (13:28), Camale?n wrote:
 As you seem to be running Wheezy stock kernel I would open bug report in 
 Debian BTS for this (if there's still none already opened).

Thanx, wasn't sure which current ones were related, but will do.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120828095349.ga36...@lordcow.org

Realtek RTL8111/8168B death

2012-08-26 Thread Gareth de Vaux 
Hi all, after about 3 weeks into a new machine the network card started dying
pretty regularly with these oopses:

Aug 21 23:03:49 fire kernel: [ 2656.192450] [ cut here ]
Aug 21 23:03:49 fire kernel: [ 2656.192457] WARNING: at 
/build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/net/sched/sch_generic.c:255
 dev_watchdog+0xe9/0x148()
Aug 21 23:03:49 fire kernel: [ 2656.192459] Hardware name: H61M-DS2
Aug 21 23:03:49 fire kernel: [ 2656.192460] NETDEV WATCHDOG: eth0 (r8169): 
transmit queue 0 timed out
Aug 21 23:03:49 fire kernel: [ 2656.192461] Modules linked in: ipt_MASQUERADE 
xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp 
iptable_filter ip_tables x_tables nf_conntrack_ftp nf_conntrack binfmt_misc 
nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop snd_hda_intel 
snd_hda_codec snd_hwdep snd_pcm snd_page_alloc i915 snd_seq snd_seq_device 
coretemp snd_timer crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 snd 
acpi_cpufreq video aes_generic drm_kms_helper soundcore parport_pc drm 
i2c_algo_bit serio_raw mperf parport cryptd evdev joydev pcspkr iTCO_wdt 
i2c_i801 i2c_core iTCO_vendor_support processor button thermal_sys ext4 crc16 
jbd2 mbcache dm_mod raid1 md_mod sd_mod sr_mod cdrom crc_t10dif usbhid hid ahci 
libahci atl1c libata r8169 scsi_mod mii ehci_hcd usbcore usb_common [last 
unloaded: scsi_wait_scan]
Aug 21 23:03:49 fire kernel: [ 2656.192503] Pid: 0, comm: swapper/0 Not tainted 
3.2.0-3-amd64 #1
Aug 21 23:03:49 fire kernel: [ 2656.192505] Call Trace:
Aug 21 23:03:49 fire kernel: [ 2656.192506]  IRQ  [81046901] ? 
warn_slowpath_common+0x78/0x8c
Aug 21 23:03:49 fire kernel: [ 2656.192512]  [810469ad] ? 
warn_slowpath_fmt+0x45/0x4a
Aug 21 23:03:49 fire kernel: [ 2656.192514]  [812a3559] ? 
netif_tx_lock+0x40/0x72
Aug 21 23:03:49 fire kernel: [ 2656.192518]  [812a36ba] ? 
dev_watchdog+0xe9/0x148
Aug 21 23:03:49 fire kernel: [ 2656.192520]  [81051f74] ? 
run_timer_softirq+0x19a/0x261
Aug 21 23:03:49 fire kernel: [ 2656.192522]  [812a35d1] ? 
netif_tx_unlock+0x46/0x46
Aug 21 23:03:49 fire kernel: [ 2656.192526]  [81065ad7] ? 
timekeeping_get_ns+0xd/0x2a
Aug 21 23:03:49 fire kernel: [ 2656.192528]  [8104bee8] ? 
__do_softirq+0xb9/0x177
Aug 21 23:03:49 fire kernel: [ 2656.192532]  [81351eec] ? 
call_softirq+0x1c/0x30
Aug 21 23:03:49 fire kernel: [ 2656.192535]  [8100f8e5] ? 
do_softirq+0x3c/0x7b
Aug 21 23:03:49 fire kernel: [ 2656.192537]  [8104c150] ? 
irq_exit+0x3c/0x9a
Aug 21 23:03:49 fire kernel: [ 2656.192541]  [81024208] ? 
smp_apic_timer_interrupt+0x74/0x82
Aug 21 23:03:49 fire kernel: [ 2656.192543]  [8135075e] ? 
apic_timer_interrupt+0x6e/0x80
Aug 21 23:03:49 fire kernel: [ 2656.192544]  EOI  [81023ed0] ? 
lapic_next_event+0xe/0x13
Aug 21 23:03:49 fire kernel: [ 2656.192549]  [811ec633] ? 
intel_idle+0xea/0x118
Aug 21 23:03:49 fire kernel: [ 2656.192551]  [811ec612] ? 
intel_idle+0xc9/0x118
Aug 21 23:03:49 fire kernel: [ 2656.192555]  [8126cbff] ? 
cpuidle_idle_call+0xec/0x179
Aug 21 23:03:49 fire kernel: [ 2656.192557]  [8100d248] ? 
cpu_idle+0xa5/0xf2
Aug 21 23:03:49 fire kernel: [ 2656.192560]  [816aab33] ? 
start_kernel+0x3b3/0x3be
Aug 21 23:03:49 fire kernel: [ 2656.192562]  [816aa140] ? 
early_idt_handlers+0x140/0x140
Aug 21 23:03:49 fire kernel: [ 2656.192564]  [816aa3c4] ? 
x86_64_start_kernel+0x104/0x111
Aug 21 23:03:49 fire kernel: [ 2656.192565] ---[ end trace 52c65d93a2f98318 ]---

$ lspci -knn | grep -B2 r8169
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. TEG-ECTX Gigabit PCI-E 
Adapter [Trendnet] [10ec:8168]
Kernel driver in use: r8169

$ cat /etc/issue
Debian GNU/Linux wheezy/sid \n \l

$ uname -a
Linux fire 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux


It doesn't seem to be related to the amount of traffic through it beforehand.

I've noticed people posting similar reports over a few years so I'm not sure
if this is a new bug to report? Could it be hardware or should I be using
Realtek's own drivers?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120826173223.ga97...@lordcow.org

Re: Realtek RTL8111/8168B death

2012-08-26 Thread Gareth de Vaux 
On Sun 2012-08-26 (19:34), Lisi wrote:
 On Sunday 26 August 2012 18:32:23 Gareth de Vaux wrote:
  $ cat /etc/issue
  Debian GNU/Linux wheezy/sid \n \l
 
 What do the \n and  \l mean?  I have googled, but got nowhere.  Well, nowhere 
 useful. :-(

See under ISSUE ESCAPES in the agetty manpage.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120826184834.ga1...@lordcow.org

Re: usb failure

2011-09-12 Thread Gareth de Vaux 
On Sun 2011-09-11 (08:26), Simon Brandmair wrote:
 Maybe related to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634023

I don't think so? Nothing happens when I plug a stick in - the subsystem
is 'dead'.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110912174056.ga63...@lordcow.org

usb failure

2011-09-10 Thread Gareth de Vaux 
Hi guys, I've been having usb issues on and off for about 2 years with
my SUN W1100z workstation. The keyboard, mouse, flash stick etc. are all
currently unresponsive. (The machine only has usb ports, all of which I've
tried).

I'm guessing the current state is due to the latest upgrade which included:

[UPGRADE] libusb-0.1-4 2:0.1.12-18 - 2:0.1.12-19
[UPGRADE] libusb-1.0-0 2:1.0.8-4 - 2:1.0.8-5
[UPGRADE] linux-image-3.0.0-1-amd64 3.0.0-1 - 3.0.0-3
[UPGRADE] usbutils 1:003-1 - 1:004-2

and typically an upgrade down the line will resolve the issue, but a further
upgrade will make it reappear. Does anyone have any idea what's going on?


Some info after a reboot:

$ cat /etc/issue
Debian GNU/Linux wheezy/sid \n \l

$ uname -a
Linux fire 3.0.0-1-amd64 #1 SMP Sat Aug 27 16:21:11 UTC 2011 x86_64 GNU/Linux

$ grep -i usb /var/log/kern.log | grep Sep 10
Sep 10 15:39:55 fire kernel: [0.925358] usbcore: registered new interface 
driver usbfs
Sep 10 15:39:55 fire kernel: [0.925394] usbcore: registered new interface 
driver hub
Sep 10 15:39:55 fire kernel: [0.942267] usbcore: registered new device 
driver usb
Sep 10 15:39:55 fire kernel: [0.943043] ehci_hcd: USB 2.0 'Enhanced' Host 
Controller (EHCI) Driver
Sep 10 15:39:55 fire kernel: [0.943516] ohci_hcd: USB 1.1 'Open' Host 
Controller (OHCI) Driver
Sep 10 15:39:55 fire kernel: [0.963136] ohci_hcd :01:00.0: new USB bus 
registered, assigned bus number 1
Sep 10 15:39:55 fire kernel: [1.031744] usb usb1: New USB device found, 
idVendor=1d6b, idProduct=0001
Sep 10 15:39:55 fire kernel: [1.031750] usb usb1: New USB device strings: 
Mfr=3, Product=2, SerialNumber=1
Sep 10 15:39:55 fire kernel: [1.031753] usb usb1: Product: OHCI Host 
Controller
Sep 10 15:39:55 fire kernel: [1.031756] usb usb1: Manufacturer: Linux 
3.0.0-1-amd64 ohci_hcd
Sep 10 15:39:55 fire kernel: [1.031759] usb usb1: SerialNumber: :01:00.0
Sep 10 15:39:55 fire kernel: [1.031912] hub 1-0:1.0: USB hub found
Sep 10 15:39:55 fire kernel: [1.147657] ohci_hcd :01:00.1: new USB bus 
registered, assigned bus number 2
Sep 10 15:39:55 fire kernel: [1.202050] usb usb2: New USB device found, 
idVendor=1d6b, idProduct=0001
Sep 10 15:39:55 fire kernel: [1.202054] usb usb2: New USB device strings: 
Mfr=3, Product=2, SerialNumber=1
Sep 10 15:39:55 fire kernel: [1.202057] usb usb2: Product: OHCI Host 
Controller
Sep 10 15:39:55 fire kernel: [1.202060] usb usb2: Manufacturer: Linux 
3.0.0-1-amd64 ohci_hcd
Sep 10 15:39:55 fire kernel: [1.202063] usb usb2: SerialNumber: :01:00.1
Sep 10 15:39:55 fire kernel: [1.202282] hub 2-0:1.0: USB hub found

$ lsmod | egrep hcd|evdev
evdev  17558  4 
ohci_hcd   26576  0 
ehci_hcd   40090  0 
usbcore   128338  3 ohci_hcd,ehci_hcd

$ lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

$ ls -l /dev/input
total 0
drwxr-xr-x 2 root root 60 Sep 10 15:39 by-path
crw--- 1 root root 13, 64 Sep 10 15:39 event0
crw--- 1 root root 13, 65 Sep 10 15:39 event1
crw--- 1 root root 13, 66 Sep 10 15:39 event2
crw--- 1 root root 13, 63 Sep 10 15:39 mice



Corresponding kern.log output from when it was last working:

Aug 29 20:07:17 fire kernel: [1.431907] usbcore: registered new interface 
driver usbfs
Aug 29 20:07:17 fire kernel: [1.431946] usbcore: registered new interface 
driver hub  
Aug 29 20:07:17 fire kernel: [1.475085] usbcore: registered new device 
driver usb 
Aug 29 20:07:17 fire kernel: [1.475851] ehci_hcd: USB 2.0 'Enhanced' Host 
Controller (EHCI) Driver
Aug 29 20:07:17 fire kernel: [1.608606] ehci_hcd :01:03.2: new USB bus 
registered, assigned bus number 1
Aug 29 20:07:17 fire kernel: [1.644171] ehci_hcd :01:03.2: USB 2.0 
started, EHCI 1.00
Aug 29 20:07:17 fire kernel: [1.644205] usb usb1: New USB device found, 
idVendor=1d6b, idProduct=0002
Aug 29 20:07:17 fire kernel: [1.644210] usb usb1: New USB device strings: 
Mfr=3, Product=2, SerialNumber=1
Aug 29 20:07:17 fire kernel: [1.644213] usb usb1: Product: EHCI Host 
Controller
Aug 29 20:07:17 fire kernel: [1.644216] usb usb1: Manufacturer: Linux 
3.0.0-1-amd64 ehci_hcd
Aug 29 20:07:17 fire kernel: [1.644219] usb usb1: SerialNumber: :01:03.2
Aug 29 20:07:17 fire kernel: [1.644372] hub 1-0:1.0: USB hub found
Aug 29 20:07:17 fire kernel: [1.703189] ohci_hcd: USB 1.1 'Open' Host 
Controller (OHCI) Driver
Aug 29 20:07:17 fire kernel: [1.703861] ohci_hcd :01:00.0: new USB bus 
registered, assigned bus number 2
Aug 29 20:07:17 fire kernel: [1.758039] usb usb2: New USB device found, 
idVendor=1d6b, idProduct=0001
Aug 29 20:07:17 fire kernel: [1.758044] usb usb2: New USB device strings: 
Mfr=3, Product=2, SerialNumber=1
Aug 29 20:07:17 fire kernel: [1.758047] usb usb2: Product: OHCI Host 
Controller
Aug 29 20:07:17