* IDE CD-ROM no more recognized as CD-ROM after 63480d01
From: Andrey Borzenkov @ 2010-05-09 18:09 UTC (permalink / raw)
To: linux-hotplug
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
Is it intentional change (meaning - should I complaint/patch it in
distribution)? This commit removed hdX from list of valid CD-ROM names
meaning now IDE CD-ROM no more recognized as such.
There are still valid cases for IDE. Some chipsets - notably ALi M5229 -
still do have DMA issues with ATAPI and PATA drivers.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* Re: System hangs when using USB 3.0 HD with on Ubuntu
From: Alan Stern @ 2010-05-07 15:03 UTC (permalink / raw)
To: Jonas Schwertfeger
Cc: Sarah Sharp, Mark Lord, Dinh.Nguyen-KZfg59tc24xl57MIdRCFDg,
Sergei Shtylyov, James Bottomley, Kay Sievers, David Zeuthen,
linux-hotplug-u79uwXL29TY76Z2rM5mHXA,
linux-usb-u79uwXL29TY76Z2rM5mHXA, USB Storage List, Matthew Dharm,
linux-scsi-u79uwXL29TY76Z2rM5mHXA, Lennart Poettering,
Douglas Gilbert
In-Reply-To: <4BE3EE87.6020505-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Fri, 7 May 2010, Jonas Schwertfeger wrote:
> On 04/29/2010 05:45 PM, Alan Stern wrote:
> > I would still like to see a usbmon trace of hdparm under USB-2.
>
> hdparm through USB-2:
>
> /dev/sdb:
> outgoing cdb: 85 08 2e 00 00 00 01 00 00 00 00 00 00 40 ec 00
> data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
> SG_IO: bad response (not CHECK_CONDITION)
> Trying legacy HDIO_DRIVE_CMD
> outgoing cdb: 85 08 2e 00 00 00 01 00 00 00 00 00 00 40 a1 00
> data: 40 00 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00
> SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
> SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 00 04 00 01 00 00 00 00 00
> 00 40 51 00 00 00 00 00 00 00 00 00 00
> SG_IO: desc[]: 09 0c 00 04 00 01 00 00 00 00 00 00
> ATA_16 statQ err\x04 nsect\x01 lbal\0 lbam\0 lbah\0 dev@
> I/O error, ata_op=0xa1 ata_status=0x51 ata_error=0x04
> HDIO_DRIVE_CMD(identify) failed: Input/output error
> readonly = 0 (off)
> readahead = 256 (on)
> geometry = 121601/255/63, sectors = 1953525168, start = 0
>
> ffff8801f8199540 602153163 S Bo:1:003:2 -115 31 = 55534243 d4000000
> 00020000 80001085 082e0000 00010000 00000000 40ec00
> ffff8801f8199540 602153314 C Bo:1:003:2 0 31 >
> ffff8801f8184d80 602153376 S Bi:1:003:1 -115 512 <
> ffff8801f8184d80 602159046 C Bi:1:003:1 0 512 = 00000000 00000000
> 00000000 00000000 00000000 00000000 00000000 00000000
> ffff8801f8199540 602159103 S Bi:1:003:1 -115 13 <
> ffff8801f8199540 602159156 C Bi:1:003:1 0 13 = 55534253 d4000000 00000000 00
> ffff8801f8199540 602159382 S Bo:1:003:2 -115 31 = 55534243 d5000000
> 00020000 80001085 082e0000 00010000 00000000 40a100
> ffff8801f8199540 602159536 C Bo:1:003:2 0 31 >
> ffff8801f8184d80 602159594 S Bi:1:003:1 -115 512 <
> ffff8801f8184d80 602159791 C Bi:1:003:1 -32 0
> ffff8801f8199540 602159846 S Co:1:003:0 s 02 01 0000 0081 0000 0
> ffff8801f8199540 602159900 C Co:1:003:0 0 0
> ffff8801f8199540 602159951 S Bi:1:003:1 -115 13 <
> ffff8801f8199540 602160029 C Bi:1:003:1 0 13 = 55534253 d5000000 00020000 01
> ffff8801f8199540 602160100 S Bo:1:003:2 -115 31 = 55534243 d6000000
> 60000000 80000603 00000060 00000000 00000000 000000
> ffff8801f8199540 602160159 C Bo:1:003:2 0 31 >
> ffff8801f8184d80 602160201 S Bi:1:003:1 -115 96 <
> ffff8801f8184d80 602160276 C Bi:1:003:1 0 96 = 00000000 00000000
> 00000000 00000000 00000000 00000000 00000000 00000000
> ffff8801f8199540 602160334 S Bi:1:003:1 -115 13 <
> ffff8801f8199540 602160418 C Bi:1:003:1 0 13 = 55534253 d6000000 00000000 00
> ffff8801f8199540 602161915 S Bo:1:003:2 -115 31 = 55534243 d7000000
> 00100000 80000a28 00000000 00000008 00000000 000000
> ffff8801f8199540 602162023 C Bo:1:003:2 0 31 >
> ffff8801f8184d80 602162080 S Bi:1:003:1 -115 4096 <
> ffff8801f8184d80 602162284 C Bi:1:003:1 0 4096 = 00000000 00000000
> 00000000 00000000 00000000 00000000 00000000 00000000
> ffff8801f8199540 602162344 S Bi:1:003:1 -115 13 <
> ffff8801f8199540 602162405 C Bi:1:003:1 0 13 = 55534253 d7000000 00000000 00
Hmm. I'm not sure I believe this data. For a while (starting with
2.6.33) the usbmon implementation didn't work right with EHCI -- it
looked in the transfer buffer before the DMA-unmapping was done, so on
a system with >= 4 GB of memory it wouldn't always see the data. The
fix for this was merged only within the last week or so.
Can you repeat the USB-2.0 test but this time doing "rmmod ehci-hcd"
beforehand?
Alan Stern
^ permalink raw reply
* Re: System hangs when using USB 3.0 HD with on Ubuntu
From: Jonas Schwertfeger @ 2010-05-07 10:42 UTC (permalink / raw)
To: Alan Stern
Cc: Sarah Sharp, Mark Lord, Dinh.Nguyen, Sergei Shtylyov,
James Bottomley, Kay Sievers, David Zeuthen, linux-hotplug,
linux-usb, USB Storage List, Matthew Dharm, linux-scsi,
Lennart Poettering, Douglas Gilbert
In-Reply-To: <Pine.LNX.4.44L0.1004291144480.1697-100000@iolanthe.rowland.org>
On 04/29/2010 05:45 PM, Alan Stern wrote:
> I would still like to see a usbmon trace of hdparm under USB-2.
hdparm through USB-2:
/dev/sdb:
outgoing cdb: 85 08 2e 00 00 00 01 00 00 00 00 00 00 40 ec 00
data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
SG_IO: bad response (not CHECK_CONDITION)
Trying legacy HDIO_DRIVE_CMD
outgoing cdb: 85 08 2e 00 00 00 01 00 00 00 00 00 00 40 a1 00
data: 40 00 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 00 04 00 01 00 00 00 00 00
00 40 51 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 04 00 01 00 00 00 00 00 00
ATA_16 statQ err\x04 nsect\x01 lbal\0 lbam\0 lbah\0 dev@
I/O error, ata_op=0xa1 ata_status=0x51 ata_error=0x04
HDIO_DRIVE_CMD(identify) failed: Input/output error
readonly = 0 (off)
readahead = 256 (on)
geometry = 121601/255/63, sectors = 1953525168, start = 0
ffff8801f8199540 602153163 S Bo:1:003:2 -115 31 = 55534243 d4000000
00020000 80001085 082e0000 00010000 00000000 40ec00
ffff8801f8199540 602153314 C Bo:1:003:2 0 31 >
ffff8801f8184d80 602153376 S Bi:1:003:1 -115 512 <
ffff8801f8184d80 602159046 C Bi:1:003:1 0 512 = 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000
ffff8801f8199540 602159103 S Bi:1:003:1 -115 13 <
ffff8801f8199540 602159156 C Bi:1:003:1 0 13 = 55534253 d4000000 00000000 00
ffff8801f8199540 602159382 S Bo:1:003:2 -115 31 = 55534243 d5000000
00020000 80001085 082e0000 00010000 00000000 40a100
ffff8801f8199540 602159536 C Bo:1:003:2 0 31 >
ffff8801f8184d80 602159594 S Bi:1:003:1 -115 512 <
ffff8801f8184d80 602159791 C Bi:1:003:1 -32 0
ffff8801f8199540 602159846 S Co:1:003:0 s 02 01 0000 0081 0000 0
ffff8801f8199540 602159900 C Co:1:003:0 0 0
ffff8801f8199540 602159951 S Bi:1:003:1 -115 13 <
ffff8801f8199540 602160029 C Bi:1:003:1 0 13 = 55534253 d5000000 00020000 01
ffff8801f8199540 602160100 S Bo:1:003:2 -115 31 = 55534243 d6000000
60000000 80000603 00000060 00000000 00000000 000000
ffff8801f8199540 602160159 C Bo:1:003:2 0 31 >
ffff8801f8184d80 602160201 S Bi:1:003:1 -115 96 <
ffff8801f8184d80 602160276 C Bi:1:003:1 0 96 = 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000
ffff8801f8199540 602160334 S Bi:1:003:1 -115 13 <
ffff8801f8199540 602160418 C Bi:1:003:1 0 13 = 55534253 d6000000 00000000 00
ffff8801f8199540 602161915 S Bo:1:003:2 -115 31 = 55534243 d7000000
00100000 80000a28 00000000 00000008 00000000 000000
ffff8801f8199540 602162023 C Bo:1:003:2 0 31 >
ffff8801f8184d80 602162080 S Bi:1:003:1 -115 4096 <
ffff8801f8184d80 602162284 C Bi:1:003:1 0 4096 = 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000
ffff8801f8199540 602162344 S Bi:1:003:1 -115 13 <
ffff8801f8199540 602162405 C Bi:1:003:1 0 13 = 55534253 d7000000 00000000 00
and hdparm through UBS-3:
/dev/sdb:
outgoing cdb: 85 08 2e 00 00 00 01 00 00 00 00 00 00 40 ec 00
data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
SG_IO: bad response (not CHECK_CONDITION)
Trying legacy HDIO_DRIVE_CMD
outgoing cdb: 85 08 2e 00 00 00 01 00 00 00 00 00 00 40 a1 00
data: 40 00 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 00 04 00 01 00 00 00 00 00
00 40 51 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 04 00 01 00 00 00 00 00 00
ATA_16 statQ err\x04 nsect\x01 lbal\0 lbam\0 lbah\0 dev@
I/O error, ata_op=0xa1 ata_status=0x51 ata_error=0x04
HDIO_DRIVE_CMD(identify) failed: Input/output error
readonly = 0 (off)
readahead = 256 (on)
geometry = 121601/255/63, sectors = 1953525168, start = 0
ffff8801f810c6c0 734453214 S Bo:10:002:2 -115 31 = 55534243 c4000000
00020000 80001085 082e0000 00010000 00000000 40ec00
ffff8801f810c6c0 734453421 C Bo:10:002:2 0 31 >
ffff8801f810c9c0 734453512 S Bi:10:002:1 -115 512 <
ffff8801f810c9c0 734459225 C Bi:10:002:1 0 512 Z
ffff8801f810c6c0 734459316 S Bi:10:002:1 -115 13 <
ffff8801f810c6c0 734459485 C Bi:10:002:1 0 13 = 55534253 c4000000
00000000 00
ffff8801f810c6c0 734459861 S Bo:10:002:2 -115 31 = 55534243 c5000000
00020000 80001085 082e0000 00010000 00000000 40a100
ffff8801f810c6c0 734460033 C Bo:10:002:2 0 31 >
ffff8801f810c9c0 734460121 S Bi:10:002:1 -115 512 <
ffff8801f810c9c0 734460395 C Bi:10:002:1 -32 0
ffff8801f810c6c0 734460482 S Co:10:002:0 s 02 01 0000 0081 0000 0
ffff8801f810c6c0 734460885 C Co:10:002:0 0 0
ffff8801f810c6c0 734461026 S Bi:10:002:1 -115 13 <
ffff8801f810c6c0 734461270 C Bi:10:002:1 0 13 = 55534253 c5000000
00020000 01
ffff8801f810c6c0 734461371 S Bo:10:002:2 -115 31 = 55534243 c6000000
60000000 80000603 00000060 00000000 00000000 000000
ffff8801f810c6c0 734461560 C Bo:10:002:2 0 31 >
ffff8801f810c9c0 734461649 S Bi:10:002:1 -115 96 <
ffff8801f810c9c0 734461814 C Bi:10:002:1 0 96 Z
ffff8801f810c6c0 734461904 S Bi:10:002:1 -115 13 <
ffff8801f810c6c0 734462066 C Bi:10:002:1 0 13 = 55534253 c6000000
00000000 00
ffff8801f810c6c0 734463922 S Bo:10:002:2 -115 31 = 55534243 c7000000
00100000 80000a28 00000000 00000008 00000000 000000
ffff8801f810c6c0 734464100 C Bo:10:002:2 0 31 >
ffff8801f810c9c0 734464187 S Bi:10:002:1 -115 4096 <
ffff8801f810c9c0 734476632 C Bi:10:002:1 0 4096 Z
ffff8801f810c6c0 734476724 S Bi:10:002:1 -115 13 <
ffff8801f810c6c0 734476913 C Bi:10:002:1 0 13 = 55534253 c7000000
00000000 00
Hope this helps,
-Jonas
^ permalink raw reply
* [PATCH] keymap: Add keymap quirk of WebCam key for MSI netbooks
From: Yin Kangkai @ 2010-05-07 8:34 UTC (permalink / raw)
To: linux-hotplug
Hi,
Patch below add support for Fn+F6 (WebCam) key event in some MSI
netbooks. I've verified that this patch works on MSI U100, N014, U135
http://bugs.meego.com/show_bug.cgi?id\x1741
From b70a4ad8cf7e39bdcff8f328239291c7309622de Mon Sep 17 00:00:00 2001
From: Yin Kangkai <kangkai.yin@intel.com>
Date: Fri, 7 May 2010 15:05:21 +0800
Subject: [PATCH] keymap: Add keymap quirk of WebCam key for MSI netbooks.
I've verified that this patch fixes MSI U100, N014, U135
http://bugs.meego.com/show_bug.cgi?id\x1741
Signed-off-by: Yin Kangkai <kangkai.yin@intel.com>
---
| 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
--git a/extras/keymap/keymaps/micro-star b/extras/keymap/keymaps/micro-star
index 0469434..0de5ae6 100644
--- a/extras/keymap/keymaps/micro-star
+++ b/extras/keymap/keymaps/micro-star
@@ -6,6 +6,7 @@
0xE2 bluetooth # satellite dish2
0xE4 f22 # Fn-F3 Touchpad disable
0xEC email # envelope button
+0xEE camera # Fn-F6 camera disable
0xF6 wlan # satellite dish1
0xF7 brightnessdown # Fn-F4
0xF8 brightnessup # Fn-F5
--
1.6.5
^ permalink raw reply related
* RE: How to use blkid for getting USB partition name???
From: chinnathambi @ 2010-05-07 4:36 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <20100506093216.D2E411F105E@zimbra.jasmin-infotech.com>
Hai Stephane,
I am not able to get any verbose output. Pls carify..
root:/> cat /proc/partitions
major minor #blocks name
31 0 256 mtdblock0
31 1 384 mtdblock1
31 2 7552 mtdblock2
31 3 7680 mtdblock3
31 4 512 mtdblock4
8 0 244198584 sda
8 1 1 sda1
8 5 33551721 sda5
8 6 33551721 sda6
8 7 33551721 sda7
8 8 33551721 sda8
8 9 33551721 sda9
8 10 33551721 sda10
8 11 33551721 sda11
8 12 9325701 sda12
root:/> blkid -p -o udev /dev/sda5
root:/> BLKID_DEBUG=0xffff blkid -p -o udev /dev/sda5
root:/>
root:/>
I need to extract the USB name. But I cant get it. I don
know whether I am doing anything wrong in the basic level. So please clarify
in this regard.
Regards,
Chinnathambi M
-----Original Message-----
From: linux-hotplug-owner@vger.kernel.org
[mailto:linux-hotplug-owner@vger.kernel.org] On Behalf Of Karel Zak
Sent: Thursday, May 06, 2010 7:09 PM
To: chinnathambi
Cc: 'stephane ancelot'; linux-hotplug@vger.kernel.org
Subject: Re: How to use blkid for getting USB partition name???
On Thu, May 06, 2010 at 03:03:23PM +0530, chinnathambi wrote:
> Hai,
> I have enable hotplug for detecting USB. I am having muti partition
> in my USB hard disc. I am trying to recover the parttion name by using
parttion name... Do you mean filesystem LABEL?
> blkid. But I cant get any response. I want to know whether I have to
enable
> anything in my kernel. Or after executing blkid command where to check for
> the output ?
>
> Shown below is how I used blkid.
>
> root:/> hotplug: usb inserted
> hotplug: usb inserted
> hotplug: usb inserted
> hotplug: usb inserted
> hotplug: usb inserted
>
> root:/> cat /proc/partitions
> major minor #blocks name
>
> 31 0 256 mtdblock0
> 31 1 384 mtdblock1
> 31 2 7552 mtdblock2
> 31 3 7680 mtdblock3
> 31 4 512 mtdblock4
> 8 0 244198584 sda
> 8 1 1 sda1
> 8 5 33551721 sda5
> 8 6 33551721 sda6
> 8 7 33551721 sda7
> 8 8 33551721 sda8
> 8 9 33551721 sda9
> 8 10 33551721 sda10
> 8 11 33551721 sda11
> 8 12 9325701 sda12
> root:/> blkid /dev/sda5
> root:/> blkid -c -o /dev/sda5
blkid -p -o udev /dev/sda5
or
BLKID_DEBUG=0xffff blkid -p -o udev /dev/sda5
to get more verbose output.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply
* Re: [PATCH] keymap: Add keymap and force-release quirk for Samsung
From: Martin Pitt @ 2010-05-06 14:01 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <20100506023313.GK6648@kai-debian>
Hello Yin,
Yin Kangkai [2010-05-06 10:33 +0800]:
> I failed to find the support for Samsung N128 in
> 95-keyboard-force-release.rules and 95-keymap.rules, So I'm trying to
> send a patch for this, please consider accept it. Thanks.
Thanks! Applied to git master.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
^ permalink raw reply
* Re: How to use blkid for getting USB partition name???
From: Karel Zak @ 2010-05-06 13:39 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <20100506093216.D2E411F105E@zimbra.jasmin-infotech.com>
On Thu, May 06, 2010 at 03:03:23PM +0530, chinnathambi wrote:
> Hai,
> I have enable hotplug for detecting USB. I am having muti partition
> in my USB hard disc. I am trying to recover the parttion name by using
parttion name... Do you mean filesystem LABEL?
> blkid. But I cant get any response. I want to know whether I have to enable
> anything in my kernel. Or after executing blkid command where to check for
> the output ?
>
> Shown below is how I used blkid.
>
> root:/> hotplug: usb inserted
> hotplug: usb inserted
> hotplug: usb inserted
> hotplug: usb inserted
> hotplug: usb inserted
>
> root:/> cat /proc/partitions
> major minor #blocks name
>
> 31 0 256 mtdblock0
> 31 1 384 mtdblock1
> 31 2 7552 mtdblock2
> 31 3 7680 mtdblock3
> 31 4 512 mtdblock4
> 8 0 244198584 sda
> 8 1 1 sda1
> 8 5 33551721 sda5
> 8 6 33551721 sda6
> 8 7 33551721 sda7
> 8 8 33551721 sda8
> 8 9 33551721 sda9
> 8 10 33551721 sda10
> 8 11 33551721 sda11
> 8 12 9325701 sda12
> root:/> blkid /dev/sda5
> root:/> blkid -c -o /dev/sda5
blkid -p -o udev /dev/sda5
or
BLKID_DEBUG=0xffff blkid -p -o udev /dev/sda5
to get more verbose output.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
^ permalink raw reply
* How to use blkid for getting USB partition name???
From: chinnathambi @ 2010-05-06 9:45 UTC (permalink / raw)
To: linux-hotplug
Hai,
I have enable hotplug for detecting USB. I am having muti partition
in my USB hard disc. I am trying to recover the parttion name by using
blkid. But I cant get any response. I want to know whether I have to enable
anything in my kernel. Or after executing blkid command where to check for
the output ?
Shown below is how I used blkid.
root:/> hotplug: usb inserted
hotplug: usb inserted
hotplug: usb inserted
hotplug: usb inserted
hotplug: usb inserted
root:/> cat /proc/partitions
major minor #blocks name
31 0 256 mtdblock0
31 1 384 mtdblock1
31 2 7552 mtdblock2
31 3 7680 mtdblock3
31 4 512 mtdblock4
8 0 244198584 sda
8 1 1 sda1
8 5 33551721 sda5
8 6 33551721 sda6
8 7 33551721 sda7
8 8 33551721 sda8
8 9 33551721 sda9
8 10 33551721 sda10
8 11 33551721 sda11
8 12 9325701 sda12
root:/> blkid /dev/sda5
root:/> blkid -c -o /dev/sda5
root:/>
Please clarify me how to use this command blkid?
Regards,
Chinnathambi M
^ permalink raw reply
* [PATCH] keymap: Add keymap and force-release quirk for Samsung N128
From: Yin Kangkai @ 2010-05-06 2:33 UTC (permalink / raw)
To: linux-hotplug
Hi list,
I failed to find the support for Samsung N128 in
95-keyboard-force-release.rules and 95-keymap.rules, So I'm trying to
send a patch for this, please consider accept it. Thanks.
From 3a0507af389b560942a37fd5b8078f3975c34f0d Mon Sep 17 00:00:00 2001
From: Yin Kangkai <kangkai.yin@intel.com>
Date: Thu, 6 May 2010 10:06:43 +0800
Subject: [PATCH] keymap: Add keymap and force-release quirk for Samsung N128
http://bugs.meego.com/show_bug.cgi?id\x1530
Signed-off-by: Yin Kangkai <kangkai.yin@intel.com>
---
| 2 +-
| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--git a/extras/keymap/95-keyboard-force-release.rules b/extras/keymap/95-keyboard-force-release.rules
index 011b2e3..7c334ce 100644
--- a/extras/keymap/95-keyboard-force-release.rules
+++ b/extras/keymap/95-keyboard-force-release.rules
@@ -19,7 +19,7 @@ DRIVER!="atkbd", GOTO="force_release_end"
ENV{DMI_VENDOR}="$attr{[dmi/id]sys_vendor}"
-ENV{DMI_VENDOR}="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}="*N130*|*N140*|*SR70S/SR71S*|*Q210/P210*", RUN+="keyboard-force-release.sh $devpath samsung-other"
+ENV{DMI_VENDOR}="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}="*N128*|*N130*|*N140*|*SR70S/SR71S*|*Q210/P210*", RUN+="keyboard-force-release.sh $devpath samsung-other"
ENV{DMI_VENDOR}="Dell Inc.", ATTR{[dmi/id]product_name}="Studio 1557|Studio 1558", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
--git a/extras/keymap/95-keymap.rules b/extras/keymap/95-keymap.rules
index a27bc6d..8c00ba1 100644
--- a/extras/keymap/95-keymap.rules
+++ b/extras/keymap/95-keymap.rules
@@ -110,7 +110,7 @@ ENV{DMI_VENDOR}="INVENTEC", ATTR{[dmi/id]product_name}="SYMPHONY 6.0/7.0", RUN
ENV{DMI_VENDOR}="MAXDATA", ATTR{[dmi/id]product_name}="Pro 7000*", RUN+="keymap $name maxdata-pro_7000"
-ENV{DMI_VENDOR}="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}="*NC10*|*NC20*|*N130*|*SP55S*|*SQ45S70S*|*SX60P*|*SX22S*|*SX30S*|*R59P/R60P/R61P*|*SR70S/SR71S*|*Q210*|*Q310*|*X05*|*P560*|*R560*", RUN+="keymap $name samsung-other"
+ENV{DMI_VENDOR}="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}="*NC10*|*NC20*|*N128*|*N130*|*SP55S*|*SQ45S70S*|*SX60P*|*SX22S*|*SX30S*|*R59P/R60P/R61P*|*SR70S/SR71S*|*Q210*|*Q310*|*X05*|*P560*|*R560*", RUN+="keymap $name samsung-other"
ENV{DMI_VENDOR}="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}="*SX20S*", RUN+="keymap $name samsung-sx20s"
ENV{DMI_VENDOR}="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}="SQ1US", RUN+="keymap $name samsung-sq1us"
--
1.6.5
^ permalink raw reply related
* Re: 2 nics are the same, but not drivers ...
From: Kay Sievers @ 2010-05-05 15:24 UTC (permalink / raw)
To: linux-hotplug
On Wed, May 5, 2010 at 16:54, stephane ancelot <sancelot@free.fr> wrote:
> I have problem with 2 r8169 nic boards, I want one of them use a classic
> kernel driver and the other one using another
> specific realtime driver .
You can only unbind the one and bind the other driver manually through sysfs.
Kay
^ permalink raw reply
* 2 nics are the same, but not drivers ...
From: stephane ancelot @ 2010-05-05 14:54 UTC (permalink / raw)
To: linux-hotplug
Hi,
I have problem with 2 r8169 nic boards, I want one of them use a classic
kernel driver and the other one using another
specific realtime driver .
how to do this ????
Best Regards
steph
^ permalink raw reply
* Re: Seek help on rule
From: Kay Sievers @ 2010-05-05 6:28 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <851760.15837.qm@web56001.mail.re3.yahoo.com>
On Wed, May 5, 2010 at 07:23, Yan Zhang <yanzhang012@yahoo.com> wrote:
> Dear Madam/Sir.
>
> I am writing to seek help from you over a rule. This is my rule
>
> IMPORT{program}="/bin/echo iii=0"
>
> KERNEL="sdb", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u -x -a -s %p -d $tempnode", ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232", NAME="sdz$ENV{iii}", ENV{iii}="1"
> KERNEL="sdc", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u -x -a -s %p -d $tempnode", ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232", NAME="sdz$ENV{iii}", ENV{iii}="2"
> KERNEL="sdd", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u -x -a -s %p -d $tempnode", ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232", NAME="sdz$ENV{iii}", ENV{iii}="3"
> KERNEL="sde", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u -x -a -s %p -d $tempnode", ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232", NAME="sdz$ENV{iii}", ENV{iii}="4"
>
> It is working and I can get /dev/sdz0, /dev/sdz1, /dev/sdz2, and /dev/sdz3. But, could you tell me how to let rule increasing ENV{iii} automatically? Here I have to set ENV{iii}="1", ENV{iii}="2", ENV{iii}="3", and ENV{iii}="4" manually.
>
> By any change, could you tell me a single line rule, just like the following format, to realize my rule's function?
>
> KERNEL="sd*", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u
> -x -a -s %p -d $tempnode",
> ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232",
> NAME="sdz <automatically increase number by 1>"
You can't to any simple enumeration in udev. Udev does not provide
this for the simple reason, that it is unpredictable and can never
work as expected. Events run in parallel without any defined order,
there can be no counter to increase. There is no global environment
where these variables would be visible from multiple events, all
events run independent, if you set something in one event the others
will not see it.
All this should be already solved with the standard symlinks in
/dev/disk. Please just use the by-id/ links there, they are reliably
created and contain unique strings to identify devices.
Also don't call scsi_id again, udev already did that as part of the
standard device identification.
And the primary node names must never be changed, the names will no
longer match the kernel log, sysfs, /proc/partitions, ...
Future udev versions will not even allow you to rename kernel-supplied
primary device nodes with NAME=, so please don't do this.
Thanks,
Kay
^ permalink raw reply
* Seek help on rule
From: Yan Zhang @ 2010-05-05 5:23 UTC (permalink / raw)
To: linux-hotplug
Dear Madam/Sir.
I am writing to seek help from you over a rule. This is my rule
IMPORT{program}="/bin/echo iii=0"
KERNEL="sdb", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u -x -a -s %p -d $tempnode", ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232", NAME="sdz$ENV{iii}", ENV{iii}="1"
KERNEL="sdc", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u -x -a -s %p -d $tempnode", ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232", NAME="sdz$ENV{iii}", ENV{iii}="2"
KERNEL="sdd", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u -x -a -s %p -d $tempnode", ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232", NAME="sdz$ENV{iii}", ENV{iii}="3"
KERNEL="sde", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u -x -a -s %p -d $tempnode", ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232", NAME="sdz$ENV{iii}", ENV{iii}="4"
It is working and I can get /dev/sdz0, /dev/sdz1, /dev/sdz2, and /dev/sdz3. But, could you tell me how to let rule increasing ENV{iii} automatically? Here I have to set ENV{iii}="1", ENV{iii}="2", ENV{iii}="3", and ENV{iii}="4" manually.
By any change, could you tell me a single line rule, just like the following format, to realize my rule's function?
KERNEL="sd*", SUBSYSTEM="block", IMPORT{program}="/sbin/scsi_id -g -u
-x -a -s %p -d $tempnode",
ENV{ID_SERIAL}="360a980006e424539576f57487a4b6232",
NAME="sdz <automatically increase number by 1>"
Thanks for your help in advance.
Best regards,
Yan Zhang
^ permalink raw reply
* Re: udevd hang
From: Greg KH @ 2010-05-04 23:41 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <n2q9a158e2e1005041442l384fb987x1420d25a01131d38@mail.gmail.com>
On Tue, May 04, 2010 at 04:14:03PM -0700, Kyle Hubert wrote:
> On Tue, May 4, 2010 at 3:41 PM, Greg KH <greg@kroah.com> wrote:
> > On Tue, May 04, 2010 at 02:42:27PM -0700, Kyle Hubert wrote:
> >> I'm cross posting this:
> >>
> >> http://lkml.org/lkml/2010/5/4/8
> >>
> >> Can anyone help me? At the very least is there a way to stall the init
> >> script until udevd is fully up?
> >
> > Use devtmpfs?
>
> Well... cough cough, it's an older kernel. 2.6.32 was when devtmpfs
> was merged, right? Upgrading the kernel isn't a solution right now,
> for various reasons. Or, if devtmpfs is only 300 lines of code, truly,
> then is it easy to backport?
>
> Is there any way to have a barrier for when udev has walked /sys and
> is fully up? I just don't like beating the race by inserting 'sleep
> 1'...
Yes, read the man page for 'udevadm'
good luck,
greg k-h
^ permalink raw reply
* Re: udevd hang
From: Kyle Hubert @ 2010-05-04 23:14 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <n2q9a158e2e1005041442l384fb987x1420d25a01131d38@mail.gmail.com>
On Tue, May 4, 2010 at 3:41 PM, Greg KH <greg@kroah.com> wrote:
> On Tue, May 04, 2010 at 02:42:27PM -0700, Kyle Hubert wrote:
>> I'm cross posting this:
>>
>> http://lkml.org/lkml/2010/5/4/8
>>
>> Can anyone help me? At the very least is there a way to stall the init
>> script until udevd is fully up?
>
> Use devtmpfs?
Well... cough cough, it's an older kernel. 2.6.32 was when devtmpfs
was merged, right? Upgrading the kernel isn't a solution right now,
for various reasons. Or, if devtmpfs is only 300 lines of code, truly,
then is it easy to backport?
Is there any way to have a barrier for when udev has walked /sys and
is fully up? I just don't like beating the race by inserting 'sleep
1'...
Thank you very much for your response.
-Kyle Hubert
^ permalink raw reply
* Re: udevd hang
From: Greg KH @ 2010-05-04 22:41 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <n2q9a158e2e1005041442l384fb987x1420d25a01131d38@mail.gmail.com>
On Tue, May 04, 2010 at 02:42:27PM -0700, Kyle Hubert wrote:
> I'm cross posting this:
>
> http://lkml.org/lkml/2010/5/4/8
>
> Can anyone help me? At the very least is there a way to stall the init
> script until udevd is fully up?
Use devtmpfs?
^ permalink raw reply
* udevd hang
From: Kyle Hubert @ 2010-05-04 21:42 UTC (permalink / raw)
To: linux-hotplug
I'm cross posting this:
http://lkml.org/lkml/2010/5/4/8
Can anyone help me? At the very least is there a way to stall the init
script until udevd is fully up?
Thank you,
-Kyle Hubert
^ permalink raw reply
* Re: [PATCH 2/2] cdrom_id: only mark sr[0-9]* as ID_CDROM
From: Martin Pitt @ 2010-05-04 7:09 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <1272363960-22836-2-git-send-email-harald@redhat.com>
Hello Harald,
harald@redhat.com [2010-04-27 12:26 +0200]:
> From: Harald Hoyer <harald@redhat.com>
>
> we cannot be sure for xvd*
Thanks! Applied.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
^ permalink raw reply
* Re: Problems with i2c-tiny-usb
From: Matthew Dharm @ 2010-05-03 15:03 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <1272890814.2494.25.camel@moi-laptop>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On Mon, May 03, 2010 at 02:46:54PM +0200, Martin Schröder wrote:
> Hello,
>
> As written in the subject: I have problems with i2c-tiny-usb on my
> Packard Bell Notebook TR-85 running Ubuntu 9.10 (karmic).
> When I plug in the device, it says the following:
>
> May 3 14:43:06 moi-laptop kernel: [20405.713393] usb 5-1: new low speed
> USB device using uhci_hcd and address 2
> May 3 14:43:06 moi-laptop kernel: [20405.928366] usb 5-1: configuration
> #1 chosen from 1 choice
> May 3 14:43:08 moi-laptop kernel: [20407.564316] i2c-tiny-usb 5-1:1.0:
> version 1.05 found at bus 005 address 002
> May 3 14:43:08 moi-laptop kernel: [20407.567307] i2c-adapter i2c-6:
> connected i2c-tiny-usb device
> May 3 14:43:08 moi-laptop kernel: [20407.567325] usbcore: registered
> new interface driver i2c-tiny-usb
>
> That looks like everything went well and I would expect some i2c-stuff
> showing up in /dev/, but it doesn't.
>
> What could be the problem?
Did you load i2c-dev ?
Matt
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
G: Baaap booop BAHHHP.
Mir: 9600 Baud?
Mik: No, no! 9600 goes baap booop, not booop bahhhp!
-- Greg, Miranda and Mike
User Friendly, 12/31/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Problems with i2c-tiny-usb
From: Martin Schröder @ 2010-05-03 12:46 UTC (permalink / raw)
To: linux-hotplug
Hello,
As written in the subject: I have problems with i2c-tiny-usb on my
Packard Bell Notebook TR-85 running Ubuntu 9.10 (karmic).
When I plug in the device, it says the following:
May 3 14:43:06 moi-laptop kernel: [20405.713393] usb 5-1: new low speed
USB device using uhci_hcd and address 2
May 3 14:43:06 moi-laptop kernel: [20405.928366] usb 5-1: configuration
#1 chosen from 1 choice
May 3 14:43:08 moi-laptop kernel: [20407.564316] i2c-tiny-usb 5-1:1.0:
version 1.05 found at bus 005 address 002
May 3 14:43:08 moi-laptop kernel: [20407.567307] i2c-adapter i2c-6:
connected i2c-tiny-usb device
May 3 14:43:08 moi-laptop kernel: [20407.567325] usbcore: registered
new interface driver i2c-tiny-usb
That looks like everything went well and I would expect some i2c-stuff
showing up in /dev/, but it doesn't.
What could be the problem?
Greetings,
Martin Schröder
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply
* Re: [PATCH udev-git-20100430] Fix device node deletion
From: Kay Sievers @ 2010-05-01 15:32 UTC (permalink / raw)
To: linux-hotplug
On Fri, Apr 30, 2010 at 00:53, Michael Thayer <Michael.Thayer@sun.com> wrote:
> udev-152 and -153 do not remove device nodes again when a USB device is
> unplugged, instead printing the log message 'static device entry found
> -- not deleting'. Â I believe that the patch below against current udev
> git will fix this issue.
Applied.
Thanks,
Kay
^ permalink raw reply
* [PATCH udev-git-20100430] Fix device node deletion
From: Michael Thayer @ 2010-04-29 22:53 UTC (permalink / raw)
To: linux-hotplug
udev-152 and -153 do not remove device nodes again when a USB device is
unplugged, instead printing the log message 'static device entry found
-- not deleting'. I believe that the patch below against current udev
git will fix this issue.
Signed-off-by: Michael Thayer <michael.thayer@sun.com>
---
--- a/udev/udev-node.c 2010-04-30 00:36:12.571596487 +0200
+++ b/udev/udev-node.c 2010-04-30 00:36:53.871702361 +0200
@@ -428,7 +428,7 @@
}
util_strscpyl(filename, sizeof(filename), LIBEXECDIR "/devices", &devnode[strlen(udev_get_dev_path(udev))], NULL);
- if (stat(filename, &stats) = 0 || stats.st_rdev = udev_device_get_devnum(dev)) {
+ if (stat(filename, &stats) = 0 && stats.st_rdev = udev_device_get_devnum(dev)) {
info(udev, "static device entry found '%s', skip removal\n", devnode);
goto out;
}
--
Sun Microsystems GmbH Michael Thayer
Werkstrasse 24 VirtualBox engineer
71384 Weinstadt, Germany mailto:michael.thayer@sun.com
Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Jürgen Kunz
^ permalink raw reply
* Re: System hangs when using USB 3.0 HD with on Ubuntu
From: Alan Stern @ 2010-04-29 15:45 UTC (permalink / raw)
To: Jonas Schwertfeger
Cc: Sarah Sharp, Mark Lord, Dinh.Nguyen, Sergei Shtylyov,
James Bottomley, Kay Sievers, David Zeuthen, linux-hotplug,
linux-usb, USB Storage List, Matthew Dharm, linux-scsi,
Lennart Poettering, Douglas Gilbert
In-Reply-To: <4BD946E3.9030303@gmail.com>
On Thu, 29 Apr 2010, Jonas Schwertfeger wrote:
> Sorry for the delay. Attached are both a USB3 and a USB2 dmesg log of
> running the latest version of hpdarm.
I would still like to see a usbmon trace of hdparm under USB-2.
Alan Stern
^ permalink raw reply
* Re: [PATCH 2/2] cdrom_id: only mark sr[0-9]* as ID_CDROM
From: Kay Sievers @ 2010-04-29 13:48 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <1272363960-22836-2-git-send-email-harald@redhat.com>
On Tue, Apr 27, 2010 at 19:05, Martin Pitt <martin.pitt@ubuntu.com> wrote:
> harald@redhat.com [2010-04-27 12:26 +0200]:
>> diff --git a/extras/cdrom_id/60-cdrom_id.rules b/extras/cdrom_id/60-cdrom_id.rules
>> index 16b3af9..b3109f1 100644
>> --- a/extras/cdrom_id/60-cdrom_id.rules
>> +++ b/extras/cdrom_id/60-cdrom_id.rules
>> @@ -5,7 +5,7 @@ SUBSYSTEM!="block", GOTO="cdrom_end"
>> KERNEL!="sr[0-9]*|xvd*", GOTO="cdrom_end"
>> ENV{DEVTYPE}!="disk", GOTO="cdrom_end"
>>
>> -ENV{ID_CDROM}="1"
>> +KERNEL="sr[0-9]*", ENV{ID_CDROM}="1"
>
> This would require the distros/platforms (such as some powerpc) which
> still use the IDE CD driver to adapt this as well (which shouldn't be
> a big deal.
Yeah, and they need to patch moer than this rule. All the persistent
namning stuff does no longer match hd* too.
> I wonder why we need this at all. cdrom_id already sets ID_CDROM once
> it figured out that it is a drive. Was this added for cases where
> cdrom_id failed (we recently fixed a ton of bugs in it)? Or for the
> case where you build without extras?
We do O_ECXL now, which means we could validly fail to open the device
while handling an event, and would never set ID_CDROM, even when we
can be sure we have one.
The result is that we remove all /dev/cdrom, ... links with the same
event, which isn't what we want, and therefore just set it when the
kernel device matches and we know we can expect one.
Kay
^ permalink raw reply
* Re: System hangs when using USB 3.0 HD with on Ubuntu
From: Mark Lord @ 2010-04-29 12:56 UTC (permalink / raw)
To: Jonas Schwertfeger
Cc: Sarah Sharp, Alan Stern, Dinh.Nguyen, Sergei Shtylyov,
James Bottomley, Kay Sievers, David Zeuthen, linux-hotplug,
linux-usb, USB Storage List, Matthew Dharm, linux-scsi,
Lennart Poettering, Douglas Gilbert
In-Reply-To: <4BD946E3.9030303@gmail.com>
On 29/04/10 04:44 AM, Jonas Schwertfeger wrote:
> Sorry for the delay. Attached are both a USB3 and a USB2 dmesg log of
> running the latest version of hpdarm.
..
I'm not entirely sure _what_ you were tracing here,
but it appears that the ATA IDENTIFY DEVICE command (0xec)
succeeded in both instances, USB2 and USB3.
--
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox