Pali Rohár | 14 Apr 16:51 2014
Picon

Fn keys on Dell Latitude E6440

Hello,

on my notebook dell-wmi kernel driver generates some scan codes 
when I press some of Fn key combinations. Now all these scan 
codes are mapped to key "prog3". I would like to add some actions 
for these Fn key combinations, so what do you think? Which key 
codes should be assigned for these scan codes? Note that these 
combinations are not special (and labeled) as other (like Fn+F11 
= play/pause) and seems like windows does not recognize them.

Matthew, you are author of dell-wmi driver, do you know if there 
are some other secrets key combinations? And why first 10 Fn key 
combinations generate scan codes? 

Output of commands:

$ lsinput

/dev/input/event7
   bustype : BUS_HOST
   vendor  : 0x0
   product : 0x0
   version : 0
   name    : "Dell WMI hotkeys"
   phys    : "wmi/input0"
   bits ev : EV_SYN EV_KEY EV_MSC

$ /lib/udev/keymap -i /dev/input/event7

scan code: 0x10   key code: prog3   --> Fn+Q
(Continue reading)

Valentina Manea | 14 Feb 18:35 2014
Picon

/dev entry of USB device not disappearing after detach

Hello,

I am working on a driver for a virtual USB host controller. When I attach a USB
device, everything is fine - sysfs files are created, /dev entry is
created, device is usable.
However, when I detach it, the /dev entry still remains. The sysfs
files are removed, as expected. Obviously, the /dev entry is no longer
usable, e.g. it can't be used for mounting.

The output from udevmon is here [1]. vhci_hcd is the device representing the
USB hub and 2-1 is the bus ID of the attached device.

As far as I can tell, udevd receives the remove event but, for some
reason, the /dev entry still remains.

Any help is greatly appreciated.

Thanks,
Valentina

[1] http://pastebin.com/0M2pSGw1
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

David Avery | 7 Feb 03:44 2014

question on udev device naming before root is mounted

Can the device names for hard drives be forced before root is mounted
in so much so that udev rules can force via a device serial number to
be a specific /dev/sdX device name.

Looking at my pci and bios boot order I shouldn't even need to do this
but I think the defaults of udev or the sysfs?? are to move USB
devices to latter drive letters.

I am booting from a USB 16GB flash drive and would prefer the device
be sda but even if I could force it to be sdz, and force my sata
drives to be specific drive letters based on their serial numbers so
that I can create a hotswap raid array and be confident that once my
drives are installed they won't move around to different device names.
I think this information would be useful to a lot of people who have
simply given up in the past, and after weeks I was at the point of
giving up but Greg's email bot has given me one more ounce of juice to
keep trying. I really would prefer to not bother him directly but I
have a sneaking suspicion what I'm trying to accomplish isn't
possible.

I have this thread: http://ubuntuforums.org/showthread.php?t=2202219
on Ubuntuforums.org where I'm trying to find out if this is possible:

I really appreciate any help, and please forgive my demeanor in my
thread on the ubuntuforums page I have a personality that takes an
acquired taste.

If there is any information needed that I haven't provided in the post
at the link above please let me know and I would be happy to provide
it.
(Continue reading)

Arkadiusz Bubała | 3 Feb 13:44 2014

Re: Reordered network interface names

Hello,

thank you for your response.

On 03.02.2014 13:02, Tom Gundersen wrote:
> > Rarely after reboot interfaces are reordered and one of them is named
>
> > eth1_rename (about 20 reboots is needed to reproduce this issue). I
> > tried to update udev but this didn't resolve this issue. I also tried
> > running udev with debug-trace but it caused that only eth0 didn't have
> > "_rename" suffix.
>
> This is a known problem, when trying to rename interfaces in the 
> kernel namespace (ethX). It is fixed in recent versions of udev (what 
> versions did you try?) by udev automatically renaming all the 
> interfaces in a deterministic way (google for predictable interface 
> names).
>
I understand. I tried the latest udev which compile on this system 
(udev-137 downloaded from pkgs.fedoraproject.org). But now I know that 
it's fixed in version 197. I'll try to resolve this issue manually. 
Thank you for your help.
>
> I suggest you either use the most recent udev, or call your interfaces 
> something else, lanX, say.
>
> HTH,
>
> Tom
>
(Continue reading)

Arkadiusz Bubała | 3 Feb 10:47 2014

Reordered network interface names

Hello,
I have server with S5520UR motherboard running Debian Etch (with the
latest mainline kernel 3.4). This motherboard has two integrated ports:
01:00.0 Ethernet controller [0200]: Intel Corporation 82575EB Gigabit
Network Connection [8086:10a7] (rev 02)
01:00.1 Ethernet controller [0200]: Intel Corporation 82575EB Gigabit
Network Connection [8086:10a7] (rev 02)

There also additional network adapters attached:

03:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection [8086:10fb] (rev 01)
03:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection [8086:10fb] (rev 01)
07:00.0 Ethernet controller [0200]: Intel Corporation 82576 Gigabit
Network Connection [8086:10c9] (rev 01)
07:00.1 Ethernet controller [0200]: Intel Corporation 82576 Gigabit
Network Connection [8086:10c9] (rev 01)
0a:00.0 Ethernet controller [0200]: Intel Corporation 82576 Gigabit
Network Connection [8086:10c9] (rev 01)
0a:00.1 Ethernet controller [0200]: Intel Corporation 82576 Gigabit
Network Connection [8086:10c9] (rev 01)

Rarely after reboot interfaces are reordered and one of them is named
eth1_rename (about 20 reboots is needed to reproduce this issue). I
tried to update udev but this didn't resolve this issue. I also tried
running udev with debug-trace but it caused that only eth0 didn't have
"_rename" suffix.

I attached udev rules file, udevinfo output. I also have full logs from 
(Continue reading)

Martin Pitt | 27 Jan 09:08 2014

Re: udev: Please add keymap for HP Chromebook 14 (Falco)

Hey Stefan,

Stefan Nagy [2014-01-25  2:24 +0100]:
> as most (all?) Chromebooks the HP Chromebook 14 has no standard
> function keys. Almost all top row keys are multimedia keys: in the
> leftmost position there's the ESC-key, in the rightmost position
> there's a power-button (-key) – in between those two keys there are
> 10 multimedia keys. For now all these multimedia keys act as
> standard function keys (F1–F10). Aside from that, instead of the
> caps lock key there's also a multimedia key.

Thanks for your keymap! I translated it to the current hwdb format
that systemd uses these days, and committed:

  http://cgit.freedesktop.org/systemd/systemd/commit/?id=82cd413782

> Two entries in the key mapping are commented out:
> 
> 1. 0x3D refresh (?)
> -> In this case I'm not sure this is the correct KEY_XXXXX constant
> since it won't work as expected in Iceweasel (I'm running Debian
> Jessie), though in nautilus it works as expected…

I commented that back in. On all screenshots of the keyboard that I
found it does look like a "refresh/reload" key (circular arrow), and
that seems to be the best match. Of course it's entirely possible that
some applications don't support that key, but hopefully some do.

> 2. 0x3E fullscreen (?)
> -> In this case I couldn't find a KEY_XXXXX constant which provides
(Continue reading)

Thomas H.P. Andersen | 20 Jan 21:11 2014
Picon

[PATCH] README: typo fixes

From: Thomas Hindoe Paaboel Andersen <phomes <at> gmail.com>

---
For libabc

 README | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/README b/README
index bb06cad..f1a505d 100644
--- a/README
+++ b/README
 <at>  <at>  -36,17 +36,17  <at>  <at>  Why bother?
     nice, and give them what they are used to. It makes their life a
     lot easier.

-use autotools
+Use autotools
   - Every custom config/makefile/build system is worse for everybody
     than autotools is.
   - We are all used to autotools, it works, nobody cares.
   - It's only two simple files to edit and include in git, which are
     well understood by many many people, not just you.
-  - Ignore all crap autotools create in the source tree. never check
+  - Ignore all crap autotools create in the source tree. Never check
     the created files into git.
   - Never, ever, install config.h. That's internal to your sources
     and is nothing to install.
-  - And really, anything but autotools is realy an option. Just get
+  - And really, nothing but autotools is really an option. Just get
(Continue reading)

Jiang Liu | 20 Jan 03:31 2014
Picon

[Patch v1] ACPI, x86: fix bug in associating hot-added CPUs with corresponding NUMA node

Current ACPI cpu hotplug driver fails to associate hot-added CPUs with
corresponding NUMA node when doing socket online. The code path to
associate CPU with NUMA node is as below:
acpi_processor_add()
    ->acpi_processor_get_info()
	->acpi_processor_hotadd_init()
	    ->acpi_map_lsapic()
		->_acpi_map_lsapic()
		    ->acpi_map_cpu2node()
cpu_subsys_online()
    ->try_online_node()
	->node_set_online()

When doing socket online, a new NUMA node is introduced in addition to
hot-added CPU and memory device. And the new NUMA node is marked as
online when onlining hot-added CPUs through sysfs interface
/sys/devices/system/cpu/cpuxx/online.

On the other hand, acpi_map_cpu2node() will only build the CPU to node
map if corresponding NUMA node is already online, so it always fails
to associate hot-added CPUs with corresponding NUMA node because the
NUMA node is still in offline state.

For the fix, we could safely remove the "node_online(node)" check in
function acpi_map_cpu2node() because it's only called for hot-added CPUs
by acpi_processor_hotadd_init().

Signed-off-by: Jiang Liu <jiang.liu <at> linux.intel.com>
---
 arch/x86/kernel/acpi/boot.c |    8 ++++----
(Continue reading)

Greg KH | 15 Jan 16:11 2014

Re: udev: attributes rules to identical devices

On Wed, Jan 15, 2014 at 03:46:15PM +0100, Teo Wolf wrote:
> Thank you for your prompt reply. 
> I have already /dev/ttyUSB0, /dev/ttyUSB1, they are enumerated progressively
> following a chronological plug in order.

And what is showing up in /dev/serial/ ?

> Fortunately I can use permanent USB port names, but I was wondering if
> permanent names were possible even without an ATTRS{serial}.

How would that be possible if there is no way to tell the devices apart?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Theo | 15 Jan 15:15 2014
Picon

udev: attributes rules to identical devices

Hello everybody, 

I am working with Kubuntu 13.10. 
I need to assign permanent names to some modems that I am working with. 
This would be possible by creating a rule in /etc/udev/rules.d/ and defining 
a symlink, something like this:

KERNEL=="ttyUSB[0-9]*", ATTRS{serial}=="0000:00:1d.0", SYMLINK="Modem0"

The problem is that all these modems have the same serial, so I cannot 
distinguish them and cannot assign a different symlink to each one. 

If it can help, the output of lsusb with two modems connected is this:

Bus 006 Device 002: ID 0403:6001 Future Technology Devices International, Ltd 
FT232 USB-Serial (UART) IC
Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd 
FT232 USB-Serial (UART) IC

Is there a way to do this? 
Thanks.

Theo

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

(Continue reading)

Sami Kerola | 5 Jan 13:15 2014
Picon
Picon

[PATCH] prefer vertical lists rather than horizontal

Hi Kay, et.al.,

This change is for libabc, and should not conflict when applied on top of
commit 3e633f4ad80eb6f222c7aa021a6f75762a31b405.

--->8----
From: Sami Kerola <kerolasa <at> iki.fi>
Date: Sun, 5 Jan 2014 12:05:45 +0000
Subject: [PATCH] prefer vertical lists rather than horizontal

Vertical lists, e.g., one string per line, can be version controlled
individually.  This commit also removes -Wpointer-arith duplicate from
my_CFLAGS variable.
---
 configure.ac | 42 +++++++++++++++++++++++++++++++++---------
 1 file changed, 33 insertions(+), 9 deletions(-)

diff --git a/configure.ac b/configure.ac
index 1926d18..e883619 100644
--- a/configure.ac
+++ b/configure.ac
 <at>  <at>  -6,13 +6,27  <at>  <at>  AC_INIT([abc],
         [http://www.example.com/abc/])
 AC_CONFIG_SRCDIR([src/libabc.c])
 AC_CONFIG_AUX_DIR([build-aux])
-AM_INIT_AUTOMAKE([check-news foreign 1.11 -Wall -Wno-portability silent-rules tar-pax
no-dist-gzip dist-xz subdir-objects])
+AM_INIT_AUTOMAKE([
+	check-news
+	foreign
(Continue reading)


Gmane