Bug#1020276: Fwd: Bug#1020276: linux-image-5.19.0-1-amd64: NFC device not detected

2022-09-21 Thread Oliver Sander

Thanks Mark,

I worked my way through these build instruction and got successfully to Step 15:
There, I don't know to do.  What is my target platform?  Is it "custom"?
If so, what are the correct values to set?

I also wonder whether that part is optional.  In 8./9. I make and install
the software.  Then I modify the code (in 15.) and make/install again (16./17.)
That's a bit confusing.

Running the demo after the first make/install also doesn't work:

~/linux_libnfc-nci(master)> sudo nfcDemoApp
nfcDemoApp: error while loading shared libraries: libnfc_nci_linux-1.so.0: 
cannot open shared object file: No such file or directory
~/linux_libnfc-nci(master)> echo $LD_LIBRARY_PATH
/usr/local/lib/
~/linux_libnfc-nci(master)> ls $LD_LIBRARY_PATH
libnfc_nci_linux-1.so.0  libnfc_nci_linux.la  pkgconfig  python3.10  
python3.9
libnfc_nci_linux-1.so.0.0.0  libnfc_nci_linux.so  python2.7  python3.8

That may be me doing something stupid, though.



smime.p7s
Description: S/MIME Cryptographic Signature


Bug#1020276: linux-image-5.19.0-1-amd64: NFC device not detected

2022-09-19 Thread Oliver Sander

Package: src:linux
Version: 5.19.6-1
Severity: normal

I have a ThinkPad X1 Yoga (4th gen).  It has an NFC device built in.
The NFC device appears in the BIOS, and it is enabled there.
However, I cannot see it from Debian at all.  Neither lsusb nor
lspci show anything ressembling an NFC device.  I would gladly help
to debug this, but I don't know what to do in such a situation.



-- Package-specific info:
** Version:
Linux version 5.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP 
PREEMPT_DYNAMIC Debian 5.19.6-1 (2022-09-01)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.19.0-1-amd64 
root=UUID=1a64cfce-790c-4909-943a-4b0eae472280 ro quiet

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
[50279.964287] usb 1-2.3.3.2: SerialNumber: 
[50280.044948] input: Lenovo ThinkPad USB-C Dock Gen2 USB Audio as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3.3/1-2.3.3.2/1-2.3.3.2:1.3/0003:17EF:A396.0008/input/input35
[50280.103999] hid-generic 0003:17EF:A396.0008: input,hidraw5: USB HID v1.11 
Device [Lenovo ThinkPad USB-C Dock Gen2 USB Audio] on 
usb-:00:14.0-2.3.3.2/input3
[50280.183667] usb 1-2.3.3.4: new full-speed USB device number 22 using xhci_hcd
[50280.290956] usb 1-2.3.3.4: New USB device found, idVendor=0b0e, 
idProduct=0422, bcdDevice= 2.31
[50280.290962] usb 1-2.3.3.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
[50280.290964] usb 1-2.3.3.4: Product: Jabra SPEAK 510 USB
[50280.290965] usb 1-2.3.3.4: SerialNumber: 3050752CC7E7021F00
[50280.576445] input: Jabra SPEAK 510 USB as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3.3/1-2.3.3.4/1-2.3.3.4:1.3/0003:0B0E:0422.0009/input/input36
[50280.634984] usb 1-2.3.3.4: 1:1: cannot set freq 48000 to ep 0x3
[50280.635890] jabra 0003:0B0E:0422.0009: input,hiddev1,hidraw6: USB HID v1.11 
Device [Jabra SPEAK 510 USB] on usb-:00:14.0-2.3.3.4/input3
[50280.669158] usbcore: registered new interface driver snd-usb-audio
[50280.842220] wlp0s20f3: authenticate with f4:4e:05:b5:37:dd
[50280.843533] wlp0s20f3: send auth to f4:4e:05:b5:37:dd (try 1/3)
[50280.939101] wlp0s20f3: authenticated
[50280.943667] wlp0s20f3: associate with f4:4e:05:b5:37:dd (try 1/3)
[50280.945310] wlp0s20f3: RX AssocResp from f4:4e:05:b5:37:dd (capab=0x111 
status=0 aid=11)
[50280.946668] wlp0s20f3: associated
[50281.051857] wlp0s20f3: Limiting TX power to 17 dBm as advertised by 
f4:4e:05:b5:37:dd
[50281.051931] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
[50281.085188] input: Lenovo ThinkPad USB-C Dock Gen2 USB Audio as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3.3/1-2.3.3.2/1-2.3.3.2:1.3/0003:17EF:A396.000A/input/input37
[50281.147813] hid-generic 0003:17EF:A396.000A: input,hidraw5: USB HID v1.11 
Device [Lenovo ThinkPad USB-C Dock Gen2 USB Audio] on 
usb-:00:14.0-2.3.3.2/input3
[50281.162696] usbhid 1-2.3.3.1:1.1: can't add hid device: -32
[50281.162704] usbhid: probe of 1-2.3.3.1:1.1 failed with error -32
[50281.360066] usb 1-2.3.3.1: USB disconnect, device number 20
[50281.623686] usb 1-2.3.3.1: new full-speed USB device number 23 using xhci_hcd
[50281.731344] usb 1-2.3.3.1: New USB device found, idVendor=04b4, 
idProduct=521a, bcdDevice= 0.00
[50281.731347] usb 1-2.3.3.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[50281.731348] usb 1-2.3.3.1: Product: USB-I2C Bridge
[50281.731349] usb 1-2.3.3.1: Manufacturer: Cypress Semiconductor
[50284.799365] IPv6: ADDRCONF(NETDEV_CHANGE): enx482ae3771609: link becomes 
ready
[50284.799711] r8152 4-1.1:1.0 enx482ae3771609: carrier on
[50312.180563] wlp0s20f3: disconnect from AP f4:4e:05:b5:37:dd for new auth to 
f4:4e:05:ae:21:ed
[50312.247452] wlp0s20f3: authenticate with f4:4e:05:ae:21:ed
[50312.257584] wlp0s20f3: send auth to f4:4e:05:ae:21:ed (try 1/3)
[50312.296792] wlp0s20f3: authenticated
[50312.299718] wlp0s20f3: associate with f4:4e:05:ae:21:ed (try 1/3)
[50312.301711] wlp0s20f3: RX ReassocResp from f4:4e:05:ae:21:ed (capab=0x111 
status=0 aid=2)
[50312.305238] wlp0s20f3: associated
[50312.337849] wlp0s20f3: Limiting TX power to 17 dBm as advertised by 
f4:4e:05:ae:21:ed
[50631.655067] wlp0s20f3: disconnect from AP f4:4e:05:ae:21:ed for new auth to 
f4:4e:05:b5:37:dd
[50631.702978] wlp0s20f3: authenticate with f4:4e:05:b5:37:dd
[50631.712151] wlp0s20f3: send auth to f4:4e:05:b5:37:dd (try 1/3)
[50631.751766] wlp0s20f3: authenticated
[50631.754022] wlp0s20f3: associate with f4:4e:05:b5:37:dd (try 1/3)
[50631.755982] wlp0s20f3: RX ReassocResp from f4:4e:05:b5:37:dd (capab=0x111 
status=0 aid=12)
[50631.759006] wlp0s20f3: associated
[50631.798424] wlp0s20f3: Limiting TX power to 17 dBm as advertised by 
f4:4e:05:b5:37:dd
[50631.799678] wlp0s20f3: disconnect from AP f4:4e:05:b5:37:dd for new auth to 
f4:4e:05:ae:21:ed
[50631.849425] wlp0s20f3: authenticate with f4:4e:05:ae:21:ed
[50631.857225] wlp0s20f3: send auth to f4:4e:05:ae:21:ed (try 1/3)

Bug#981704: Attempting to use Wacom stylus freezes system

2021-02-03 Thread Oliver Sander


I saw this, too.  The latest kernel from unstable fixed it.



smime.p7s
Description: S/MIME Cryptographic Signature


Bug#707635: ThinkPad X230: right touchpad button functions as left button when touchpad is touched

2013-05-09 Thread Oliver Sander

Package: src:linux
Version: 3.8.11-1
Severity: minor

Dear Maintainer,
I have a Lenovo ThinkPad X230, running Wheezy and the 3.8.11 kernel from 
today's unstable.
The touchpad works okay, in particular the two buttons do what they are 
supposed to do.
Unless, that is, I have a finger resting on the touchpad.  Then the right 
button triggers
the same actions as the left button, until I remove my finger from the touchpad 
again.
This can be reproduced all the time.  It has behaved that way for all kernels I 
tried
between 3.2 and the current one.

-- Package-specific info:
** Version:
Linux version 3.8-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.2 
(Debian 4.7.2-5) ) #1 SMP Debian 3.8.11-1

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.8-1-amd64 
root=UUID=64517d02-ab77-4577-9b35-cf21c25cb293 ro quiet

** Not tainted

** Kernel log:
[ 7214.785370] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 7214.799730] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) 
done.
[ 7214.815693] PM: Entering mem sleep
[ 7214.815737] Suspending console(s) (use no_console_suspend to debug)
[ 7214.944815] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 7214.947356] sd 0:0:0:0: [sda] Stopping disk
[ 7215.220319] e1000e :00:19.0: System wakeup enabled by ACPI
[ 7215.461905] ACPI: Cannot transition to non-D0 state from D3
[ 7215.529859] PM: suspend of devices complete after 715.862 msecs
[ 7215.529959] PM: late suspend of devices complete after 0.098 msecs
[ 7215.545793] ehci-pci :00:1d.0: System wakeup enabled by ACPI
[ 7215.561626] ehci-pci :00:1d.0: power state changed by ACPI to D3hot
[ 7215.561711] ehci-pci :00:1a.0: System wakeup enabled by ACPI
[ 7215.577582] ehci-pci :00:1a.0: power state changed by ACPI to D3hot
[ 7215.593603] xhci_hcd :00:14.0: System wakeup enabled by ACPI
[ 7215.609500] xhci_hcd :00:14.0: power state changed by ACPI to D3hot
[ 7215.609562] PM: noirq suspend of devices complete after 79.804 msecs
[ 7215.610158] ACPI: Preparing to enter system sleep state S3
[ 7215.781100] PM: Saving platform NVS memory
[ 7215.782526] Disabling non-boot CPUs ...
[ 7215.884811] smpboot: CPU 1 is now offline
[ 7215.886311] smpboot: CPU 2 is now offline
[ 7215.887712] smpboot: CPU 3 is now offline
[ 7215.888010] Extended CMOS year: 2000
[ 7215.888997] ACPI: Low-level resume complete
[ 7215.889035] PM: Restoring platform NVS memory
[ 7215.889413] Extended CMOS year: 2000
[ 7215.890003] microcode: CPU0 updated to revision 0x17, date = 2013-01-09
[ 7215.890019] Enabling non-boot CPUs ...
[ 7215.890107] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 7215.903962] microcode: CPU1 updated to revision 0x17, date = 2013-01-09
[ 7215.982038] CPU1 is up
[ 7215.982137] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 7215.995984] microcode: CPU2 updated to revision 0x17, date = 2013-01-09
[ 7216.073797] CPU2 is up
[ 7216.073896] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 7216.087758] microcode: CPU3 updated to revision 0x17, date = 2013-01-09
[ 7216.165568] CPU3 is up
[ 7216.168716] ACPI: Waking up from system sleep state S3
[ 7216.357034] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1: docking
[ 7216.384952] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1: Unable to dock!
[ 7216.516670] i915 :00:02.0: power state changed by ACPI to D0
[ 7216.532568] xhci_hcd :00:14.0: power state changed by ACPI to D0
[ 7216.548586] xhci_hcd :00:14.0: System wakeup disabled by ACPI
[ 7216.596417] ehci-pci :00:1a.0: power state changed by ACPI to D0
[ 7216.612383] ehci-pci :00:1a.0: System wakeup disabled by ACPI
[ 7216.628570] ehci-pci :00:1d.0: power state changed by ACPI to D0
[ 7216.644305] ehci-pci :00:1d.0: System wakeup disabled by ACPI
[ 7216.676489] sdhci-pci :02:00.0: MMC controller base frequency changed to 
50Mhz.
[ 7216.692687] PM: noirq resume of devices complete after 176.536 msecs
[ 7216.692776] PM: early resume of devices complete after 0.065 msecs
[ 7216.692802] i915 :00:02.0: setting latency timer to 64
[ 7216.692805] xhci_hcd :00:14.0: setting latency timer to 64
[ 7216.692849] mei :00:16.0: irq 41 for MSI/MSI-X
[ 7216.692862] e1000e :00:19.0: System wakeup disabled by ACPI
[ 7216.692885] ehci-pci :00:1a.0: setting latency timer to 64
[ 7216.692912] ehci-pci :00:1d.0: setting latency timer to 64
[ 7216.692954] ahci :00:1f.2: setting latency timer to 64
[ 7216.692971] snd_hda_intel :00:1b.0: irq 43 for MSI/MSI-X
[ 7216.693124] e1000e :00:19.0: irq 46 for MSI/MSI-X
[ 7216.748103] tpm_tis 00:09: TPM is disabled/deactivated (0x6)
[ 7216.748562] Extended CMOS year: 2000
[ 7216.923718] usb 3-1.6: reset high-speed USB device number 5 using ehci-pci
[ 7217.035297] ata2: SATA link down (SStatus 0 SControl 300)
[ 7217.035349] ata5: SATA link down (SStatus 0 SControl 300)
[ 7217.043306] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 7217.043986] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 7217.043991] 

Bug#592943: Feel free to close

2012-12-13 Thread Oliver Sander

I have gotten rid of this hardware.  Feel free to close the bug.


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50ca47a1.9020...@mi.fu-berlin.de



Re: Bug#648207: Please add support for newest Dell touchpad

2012-01-10 Thread Oliver Sander

I have been using Seth Forshee's patches together with the testing kernels
for several month now.  They appear to work flawlessly.


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f0c08bf.5050...@mi.fu-berlin.de



Re: Re: Bug#648207: Please add support for newest Dell touchpad

2012-01-10 Thread Oliver Sander

... on a Dell Latitude E6510, that is.


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f0c1607.9050...@mi.fu-berlin.de



Bug#592943: still no network with 2.6.38 from squeeze-backports

2011-05-24 Thread Oliver Sander

Hi!
I just tried the 2.6.38 kernel in squeeze-backports, to no avail.

From http://wireless.kernel.org/en/users/Drivers/orinoco I learned that
this is a known issue, and that I should set the wpa_supplicant 
parameter ap_scan to 2.
However I can only do that if I stop using networkmanager, because 
networkmanager

ignores the wpa_supplicant conf files.

So I guess I could start trying out alternatives to networkmanager, but I
don't really like the idea.  First, nm is the default and I would expect
it to just work.  Secondly the machine in question is not mine, and I'd
rather not fool around with it too much.  I am stuck:  is this a kernel bug?
A nm bug?  Will someone with more skills than me fix this properly sometime
in the future?  Can I help?

Thanks for your time,
Oliver



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ddba304.3060...@mi.fu-berlin.de



Bug#618422: linux-image-2.6.32-5-amd64: HP DM1-2160la with ALPS toucpad wasn't detect very well

2011-03-18 Thread Oliver Sander

I had the same symptoms with an ALPS touchpad in a Dell Latitude E6510.
I found a patch in the following list: 
https://bugzilla.redhat.com/show_bug.cgi?id=590880,
which I attach for your convenience.  The patch applies cleanly to the 
current stable
kernel.  It enabled vertical scrolling for me.  Also, by a trivial tweak 
of the patch
(look at the code, it really is trivial) I was able to disable 
click-on-tap, which was

way to sensitive on my machine.

I'm not quite sure how Dell-specific the patch is, but it may be worth a 
try.
diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
index a9f461e..27ec20e 100644
--- a/drivers/input/mouse/alps.c
+++ b/drivers/input/mouse/alps.c
@@ -29,15 +29,17 @@
 #define dbg(format, arg...) do {} while (0)
 #endif
 
-#define ALPS_DUALPOINT	0x01
-#define ALPS_WHEEL	0x02
-#define ALPS_FW_BK_1	0x04
-#define ALPS_4BTN	0x08
-#define ALPS_OLDPROTO	0x10
-#define ALPS_PASS	0x20
-#define ALPS_FW_BK_2	0x40
-#define ALPS_PS2_INTERLEAVED	0x80	/* 3-byte PS/2 packet interleaved with
+#define ALPS_DUALPOINT	0x001
+#define ALPS_WHEEL	0x002
+#define ALPS_FW_BK_1	0x004
+#define ALPS_4BTN	0x008
+#define ALPS_OLDPROTO	0x010
+#define ALPS_PASS	0x020
+#define ALPS_FW_BK_2	0x040
+#define ALPS_PS2_INTERLEAVED	0x080	/* 3-byte PS/2 packet interleaved with
 	   6-byte ALPS packet */
+#define ALPS_EC_PROTO	0x100		/* EC memory access protocol */
+#define ALPS_IMPS	0x200		/* IMPS emulation */
 
 static const struct alps_model_info alps_model_data[] = {
 	{ { 0x32, 0x02, 0x14 },	0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT }, /* Toshiba Salellite Pro M10 */
@@ -64,6 +66,7 @@ static const struct alps_model_info alps_model_data[] = {
 	{ { 0x73, 0x02, 0x50 }, 0xcf, 0xcf, ALPS_FW_BK_1 },		  /* Dell Vostro 1400 */
 	{ { 0x52, 0x01, 0x14 }, 0xff, 0xff,
 		ALPS_PASS | ALPS_DUALPOINT | ALPS_PS2_INTERLEAVED },	  /* Toshiba Tecra A11-11L */
+	{ { 0x73, 0x02, 0x64 }, 0x00, 0x00, ALPS_EC_PROTO | ALPS_IMPS },  /* Dell E2 series */
 };
 
 /*
@@ -516,6 +519,89 @@ static int alps_absolute_mode(struct psmouse *psmouse)
 	return ps2_command(psmouse-ps2dev, NULL, PSMOUSE_CMD_SETPOLL);
 }
 
+static int alps_ec_mode(struct psmouse *psmouse, bool enable)
+{
+	struct ps2dev *ps2dev = psmouse-ps2dev;
+	unsigned char param[4];
+
+	if (ps2_command(ps2dev, NULL, PSMOUSE_CMD_SETSTREAM))
+		return -1;
+	if (enable) {
+		/* EC EC EC E9 */
+		if (ps2_command(ps2dev, NULL, PSMOUSE_CMD_RESET_WRAP) ||
+		ps2_command(ps2dev, NULL, PSMOUSE_CMD_RESET_WRAP) ||
+		ps2_command(ps2dev, NULL, PSMOUSE_CMD_RESET_WRAP))
+			return -1;
+		param[0] = param[1] = param[2] = 0xff;
+		if (ps2_command(ps2dev, param, PSMOUSE_CMD_GETINFO))
+			return -1;
+
+		dbg(EC report: %2.2x %2.2x %2.2x, param[0], param[1], param[2]);
+
+		if (param[0] != 0x88 || param[1] != 0x07 || (param[2] != 0x9b  param[2] != 0x9d))
+			return -1;
+	}
+
+	return 0;
+}
+
+static int alps_ec_nibble(struct psmouse *psmouse, uint8_t nibble)
+{
+	struct ps2dev *ps2dev = psmouse-ps2dev;
+	unsigned char param;
+	static const int cmds[] = {
+		PSMOUSE_CMD_SETPOLL,
+		PSMOUSE_CMD_RESET_DIS,
+		PSMOUSE_CMD_SETSCALE21,
+		PSMOUSE_CMD_SETRATE,
+		PSMOUSE_CMD_SETRATE,
+		PSMOUSE_CMD_SETRATE,
+		PSMOUSE_CMD_SETRATE,
+		PSMOUSE_CMD_SETRATE,
+		PSMOUSE_CMD_SETRATE,
+		PSMOUSE_CMD_SETRATE,
+		PSMOUSE_CMD_GETINFO,
+		PSMOUSE_CMD_SETRES,
+		PSMOUSE_CMD_SETRES,
+		PSMOUSE_CMD_SETRES,
+		PSMOUSE_CMD_SETRES,
+		PSMOUSE_CMD_SETSCALE11 };
+	static const unsigned char params[] = {
+		0xff, 0xff, 0xff, 10, 20, 40, 60, 80, 100, 200, 0xff, 0, 1, 2, 3, 0xff };
+
+	nibble = 0xf;
+	param = params[nibble];
+	if (ps2_command(ps2dev, param, cmds[nibble]))
+		return -1;
+
+	return 0;
+}
+
+static int alps_ec_write(struct psmouse *psmouse, uint16_t addr, uint8_t value)
+{
+	struct ps2dev *ps2dev = psmouse-ps2dev;
+
+	/* Select new address: EC addr3 addr2 addr1 addr0 */
+	if (ps2_command(ps2dev, NULL, PSMOUSE_CMD_RESET_WRAP) ||
+	alps_ec_nibble(psmouse, addr  12) ||
+	alps_ec_nibble(psmouse, addr  8) ||
+	alps_ec_nibble(psmouse, addr  4) ||
+	alps_ec_nibble(psmouse, addr))
+		return -1;
+
+	/*
+	 * PSMOUSE_CMD_GETINFO can be used to read from the current address,
+	 * returning { addr_high, addr_low, value }  Useful when working with bit fields.
+	 */
+
+	/* Write byte: value1 value0 */
+	if (alps_ec_nibble(psmouse, value  4) ||
+	alps_ec_nibble(psmouse, value))
+		return -1;
+
+	return 0;
+}
+
 static int alps_get_status(struct psmouse *psmouse, char *param)
 {
 	struct ps2dev *ps2dev = psmouse-ps2dev;
@@ -602,30 +688,65 @@ static int alps_hw_init(struct psmouse *psmouse, int *version)
 	if (!priv-i)
 		return -1;
 
-	if ((priv-i-flags  ALPS_PASS) 
-	alps_passthrough_mode(psmouse, true)) {
+	if (!priv-dev2  !(priv-i-flags  ALPS_IMPS)) {
+		/* Because we never initialized dev2 */
+		printk(KERN_ERR alps.c: Failed to reconnect to IMPS emulation mode\n);
 		return -1;
 	}
 
-	if (alps_tap_mode(psmouse, true)) {
-		printk(KERN_WARNING alps.c: Failed to enable hardware 

Bug#592943: Confirmed in linux-image-2.6.37-rc7

2011-01-09 Thread Oliver Sander

I just tried linux-image-2.6.37-rc7 from experimental.  The problem is still 
there.




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d29d11b.5020...@mi.fu-berlin.de



Bug#593507: This seems to be Bug #593432

2010-08-19 Thread Oliver Sander

Hi!  This really does seem to be the same as 593432.  I have also
seen the backlight behavior you describe, and even the problem
with 'nomodeset'.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c6d2694.8010...@mi.fu-berlin.de



Bug#593432: Black screen with kms and i915

2010-08-18 Thread Oliver Sander

Strange.  Last night's update must have changed the default
behavior.  All of a sudden the content of /etc/modprobe.d/i915-kms.conf
doesn't seem to matter anymore: kms is always off.  The only way
to trigger the problem is to add modeset=1 to the boot options.
I guess this makes the problem less grave, because the default
behavior works now.

For your questions: I installed the machine from scratch using
a netinstall cd in late July.  From the date, the kernel must have
been 2.6.32-15.  The bug was there.  Before, I had been using
Lenny, and that worked fine.  However, that's pre-kms anyways,
so I don't know whether that really counts as a regression.

Here's the dmesg output with kms:

[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-20) 
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Thu 
Aug 12 13:38:27 UTC 2010

[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   NSC Geode by NSC
[0.00]   Cyrix CyrixInstead
[0.00]   Centaur CentaurHauls
[0.00]   Transmeta GenuineTMx86
[0.00]   Transmeta TransmetaCPU
[0.00]   UMC UMC UMC UMC
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009e800 (usable)
[0.00]  BIOS-e820: 0009e800 - 000a (reserved)
[0.00]  BIOS-e820: 000c - 000d4000 (reserved)
[0.00]  BIOS-e820: 000e - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 176b7000 (usable)
[0.00]  BIOS-e820: 176b7000 - 176e (ACPI NVS)
[0.00]  BIOS-e820: 176e - 176f (ACPI data)
[0.00]  BIOS-e820: 176f - 1770 (ACPI NVS)
[0.00]  BIOS-e820: 1770 - 1778 (usable)
[0.00]  BIOS-e820: 1778 - 1800 (reserved)
[0.00]  BIOS-e820: ff80 - ffc0 (reserved)
[0.00]  BIOS-e820: fff0 - 0001 (reserved)
[0.00] DMI 2.3 present.
[0.00] Phoenix BIOS detected: BIOS may corrupt low RAM, working 
around it.
[0.00] e820 update range:  - 0001 
(usable) == (reserved)

[0.00] last_pfn = 0x17780 max_arch_pfn = 0x10
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-C7FFF write-protect
[0.00]   C8000-E uncachable
[0.00]   F-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 0 mask FF000 write-back
[0.00]   1 base 01000 mask FF800 write-back
[0.00]   2 base 017F8 mask 8 uncachable
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] PAT not supported by CPU.
[0.00] initial memory mapped : 0 - 0180
[0.00] init_memory_mapping: -1778
[0.00]  00 - 40 page 4k
[0.00]  40 - 001740 page 2M
[0.00]  001740 - 001778 page 4k
[0.00] kernel direct mapping tables up to 1778 @ 1-16000
[0.00] RAMDISK: 1113f000 - 1194891c
[0.00] ACPI: RSDP 000f6300 00014 (v00 PTLTD )
[0.00] ACPI: RSDT 176ea420 00034 (v01 PTLTDRSDT   0604  
LTP )
[0.00] ACPI: FACP 176efdf3 00074 (v01 DELL   X200 0604 
PTL  004B)
[0.00] ACPI: DSDT 176ea454 0599F (v01 DELLX2000604 
MSFT 010D)

[0.00] ACPI: FACS 176fcfc0 00040
[0.00] ACPI: SSDT 176efe67 000BC (v01 PTLTD  ACPICST1 0604  
LTP 0001)
[0.00] ACPI: SSDT 176eff23 000B5 (v01 PTLTD  ACPIPST1 0604  
LTP 0001)
[0.00] ACPI: BOOT 176effd8 00028 (v01 PTLTD  $SBFTBL$ 0604  
LTP 0001)

[0.00] 0MB HIGHMEM available.
[0.00] 375MB LOWMEM available.
[0.00]   mapped low ram: 0 - 1778
[0.00]   low ram: 0 - 1778
[0.00]   node 0 low ram:  - 1778
[0.00]   node 0 bootmap 00012000 - 00014ef0
[0.00] (9 early reservations) == bootmem [00 - 001778]
[0.00]   #0 [00 - 001000]   BIOS data page == 
[00 - 001000]
[0.00]   #1 [001000 - 002000]EX TRAMPOLINE == 
[001000 - 002000]
[0.00]   #2 [006000 - 007000]   TRAMPOLINE == 
[006000 - 007000]
[0.00]   #3 [000100 - 00014c6b94]TEXT DATA BSS == 
[000100 - 00014c6b94]
[0.00]   #4 [001113f000 - 001194891c]  RAMDISK == 
[001113f000 - 001194891c]
[

Bug#593432: Info received (Bug#593432: Black screen with kms and i915)

2010-08-18 Thread Oliver Sander

Forget what I said about the default behavior having changed.
This machine is a can full of Heisenbugs!  After the fifth reboot,
kms came back with a vengeance.  Currently not even the
conf file won't stop it.  The only way I have to use
the machine is the kernel from Ubuntu 10.4 that I hand-copied
onto it.  Apparently they have kms disabled for the i915 by
some brute force method.  The dmesg output contains the
line

/i915/ disabling kernel modesetting for known /bad device/.


Bug#592943: Can't connect to WEP network: eth1: Lucent/Agere firmware doesn't support manual roaming

2010-08-14 Thread Oliver Sander

Package: linux-2.6
Version: 2.6.32-18
Severity: normal

I cannot connect to a WEP network.  The kde network manager
keeps asking me for the password.  This is after a complete
reinstall of Debian Squeeze.  Connecting to the very same
network worked when the machine was still running Lenny.

One other way to connect is to use the kernel shipped with
Ubuntu 10.4.  The firmware-linux-nonfree package needs to
be removed for this---I guess they ship their own firmware.

In case you wonder about the linux-base package from
experimenal: it was pulled in when I installed the 2.6.35
kernel from experimental.  That did not appear to change
anything, but I am too scared to downgrade again.


-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-18) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Sat Jul 24 02:27:10 UTC 2010


** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 
root=UUID=2b4fbfbd-8cd8-4da5-b90c-7b281a41435b ro quiet


** Not tainted

** Kernel log:
[7.901738] intel_rng: FWH not detected
[7.925838] dcdbas dcdbas: Dell Systems Management Base Driver 
(version 5.6.0-3.2)
[8.036778] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input7
[8.037020] ACPI: Video Device [GRFX] (multi-head: yes  rom: yes  
post: no)

[8.100735] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[8.889669] [drm] Initialized drm 1.1.0 20060810
[8.970529] i801_smbus :00:1f.3: PCI INT B - Link[LNKB] - GSI 
10 (level, low) - IRQ 10
[9.125816] pci :00:02.0: PCI INT A - Link[LNKA] - GSI 10 
(level, low) - IRQ 10

[9.125833] pci :00:02.0: setting latency timer to 64
[9.138369] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on 
minor 0

[9.412976] yenta_cardbus :02:03.0: CardBus bridge found [1028:0122]
[9.541048] yenta_cardbus :02:03.0: ISA IRQ mask 0x00b8, PCI irq 10
[9.541061] yenta_cardbus :02:03.0: Socket status: 3006
[9.541081] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge I/O 
window: 0xa000 - 0xafff
[9.541093] pcmcia_socket pcmcia_socket0: cs: IO port probe 
0xa000-0xafff: clean.
[9.542535] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge 
Memory window: 0xe020 - 0xe02f
[9.542547] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge 
Memory window: 0x1800 - 0x21ff

[9.543151] yenta_cardbus :02:07.0: CardBus bridge found [12a3:ab01]
[9.543175] yenta_cardbus :02:07.0: Enabling burst memory read 
transactions
[9.543186] yenta_cardbus :02:07.0: Using CSCINT to route CSC 
interrupts to PCI

[9.543194] yenta_cardbus :02:07.0: Routing CardBus interrupts to PCI
[9.543204] yenta_cardbus :02:07.0: TI: mfunc 0x0102, devctl 0x60
[9.773048] yenta_cardbus :02:07.0: ISA IRQ mask 0x, PCI irq 10
[9.773061] yenta_cardbus :02:07.0: Socket status: 3010
[9.773072] pci_bus :02: Raising subordinate bus# of parent bus 
(#02) from #04 to #07
[9.773097] yenta_cardbus :02:07.0: pcmcia: parent PCI bridge I/O 
window: 0xa000 - 0xafff
[9.773110] pcmcia_socket pcmcia_socket1: cs: IO port probe 
0xa000-0xafff: clean.
[9.774549] yenta_cardbus :02:07.0: pcmcia: parent PCI bridge 
Memory window: 0xe020 - 0xe02f
[9.774560] yenta_cardbus :02:07.0: pcmcia: parent PCI bridge 
Memory window: 0x1800 - 0x21ff
[   10.234342] pcmcia_socket pcmcia_socket0: cs: IO port probe 
0x100-0x3af: clean.
[   10.235355] pcmcia_socket pcmcia_socket0: cs: IO port probe 
0x3e0-0x4ff: excluding 0x4d0-0x4d7
[   10.235854] pcmcia_socket pcmcia_socket0: cs: IO port probe 
0x820-0x8ff: clean.
[   10.236399] pcmcia_socket pcmcia_socket0: cs: IO port probe 
0xc00-0xcf7: clean.
[   10.237180] pcmcia_socket pcmcia_socket0: cs: IO port probe 
0xa00-0xaff: clean.
[   10.412083] pcmcia_socket pcmcia_socket1: pccard: PCMCIA card 
inserted into slot 1
[   10.528166] Intel ICH :00:1f.5: PCI INT B - Link[LNKB] - GSI 10 
(level, low) - IRQ 10

[   10.528206] Intel ICH :00:1f.5: setting latency timer to 64
[   10.576068] pcmcia_socket pcmcia_socket1: cs: memory probe 
0xe020-0xe02f: excluding 0xe020-0xe020

[   10.585810] pcmcia 1.0: pcmcia: registering new device pcmcia1.0
[   10.594737] pcmcia_socket pcmcia_socket1: cs: IO port probe 
0x100-0x3af: clean.
[   10.595748] pcmcia_socket pcmcia_socket1: cs: IO port probe 
0x3e0-0x4ff: excluding 0x4d0-0x4d7
[   10.596585] pcmcia_socket pcmcia_socket1: cs: IO port probe 
0x820-0x8ff: clean.
[   10.597015] pcmcia_socket pcmcia_socket1: cs: IO port probe 
0xc00-0xcf7: clean.
[   10.597793] pcmcia_socket pcmcia_socket1: cs: IO port probe 
0xa00-0xaff: clean.

[   10.903008] cfg80211: Using static regulatory domain info
[   10.903016] cfg80211: Regulatory domain: US
[   10.903023]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, 
max_eirp)

[   10.903032]  (2402000 KHz - 2472000 KHz @