linuxcbon linuxcbon | 5 May 23:27 2015
Picon

how to do ? minimal udev script for my rc.sysinit ?

Hi,

my kernel boots ok and gives the hand to init which runs rc.sysinit.
I am writing a minimal rc.sysinit.
It creates /dev with devtmpfs and now all works except udev.
I need 1 or 2 or 3 lines with udev commands to make it work
and detect and modprobe needed modules.
I don't know the minimal and shortest commands to do this ?
Can you please help me ?

Thanks in advance.
Linuxcbon
--
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

Daniel Norris | 20 Apr 17:07 2015
Picon

PCI Hotplug Hardware Support

Hi there,

Can anyone recommend a modern server/workstation (prefer tower form
factor) that supports PCI hotplug? I've checked with HP and Dell; both
of them have dropped support for hotplug, although it's supported by
the intel chipsets they use...

My customers use PCI FPGA cards for development. Each time they load a
device model onto their PCI cards, the card appears as whatever type
of device they loaded on the PCI bus for the the OS (linux) to
interact with.  So, I'm not necessarily looking for
electrical/physical support, but software support as devices
appear/disappear from the bus.

Right now, we have to reboot the server each time their cards are
reconfigured, but I'd like to remove that need.

Thanks,
--Dan
--
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

zkubinski@gmail.com | 18 Apr 10:21 2015
Picon

how to install zxdsl 852 v2

Hello,
How to install a modem zxdsl 852 v2 on kernel 3.19.3 or 4.0 ?

Best redgards, Zbyszek
--
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

Christoph Pleger | 26 Mar 11:04 2015
Picon

create /etc/udev/rules.d/70-persistent-net.rules

Hello,

I hope that this is a right place fur udev questions.

My problem is that I need to create a file
/etc/udev/rules.d/70-persistent-net.rules on a PXE-Booted computer with an
NFS-Rootfilesystem. Unfortunately, that file ist not created automatically
at boot time, also "echo add > /sys/class/net/*/uevent" did not work,
though it did an another, disk-booted computer where I had deleted the
file before.

So, how can I create /etc/udev/rules.d/70-persistent-net.rules on a
netbooted computer, if possible without using tools like ifconfig, sed and
awk?

Regards
  Christoph

--
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

Mr. Ibrahim | 25 Jan 10:19 2015
Picon

Re. Important.

Dear Donated Beneficiary,

You have been carefully selected as the sole beneficiary of the sum of 3,200.000.00 (USD)donated to you by
Mr. Ibrahim who Won the Euro Million Lottery 13th October 2014.

Kindly contact me for claims. Email: ibrahim <at> donation-claimsoffice.com

Regards,
Mr. Ibrahim.
--
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

hi | 3 Dec 19:49 2014
Picon

hi


iphone 6,  380euro,
nous avons aussi samsung s5, seulement  260euro, ...
Si Te: assroooo. com
Rajib Karmakar | 2 Dec 14:46 2014
Picon

udev not renaming interface if driver is built-in

Hello,

My ethernet driver was built as a module and once it was probed, I can
see that udev renames the interface. but when I try to have the
ethernet driver as built-in. the driver is probed but udev no longer
renames the interface.

Can you please help me in this?

Thanks in advance.

Regards,
Rajib
--
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

Angelo Dureghello | 13 Oct 15:19 2014
Picon

Re: udev error, ENOEXEC

On 13/10/2014 15:10, Andrei Borzenkov wrote:
> On Mon, Oct 13, 2014 at 5:06 PM, Angelo Dureghello <angelo70 <at> gmail.com> wrote:
>> Dear all,
>>
>> i am running kernel 3.19.0,
> Are you sure?
Sry, 3.17.0.

I solved.

This kernel needs:

CONFIG_BINFMT_SCRIPT

Regards,
angelo

--
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

Angelo Dureghello | 13 Oct 15:06 2014
Picon

udev error, ENOEXEC

Dear all,

i am running kernel 3.19.0, Init 2.88 and udev 182

At boot i get this automount error:

VFS: Mounted root (ubifs filesystem) on device 0:14.
devtmpfs: mounted
Freeing unused kernel memory: 152K (c05de000 - c0604000)
INIT: version 2.88 booting
Please wait: booting...
Populating /dev using udev: udevd[1070]: starting version 182
davinci_wdt: disagrees about version of symbol module_layout
done
Starting System Watchdog service: random: nonblocking pool is initialized
done
udevd[1088]: failed to execute '/lib/udev/automount' 'automount add 
mmcsd /dev/mmcblk0p1': Exec format error

Mounting configuration partition...
Checking that all configuration is in place...
Done
Inserting all the extra modules...
....

Tried hardly to find informations over the day, but still can't get out.
After login, if i execute the same "automount" command not launched from 
udev but from command prompt), mount works.
Same rootfs image with old kernel 3.5.1 was also working.

(Continue reading)

Jiang Liu | 19 Sep 07:18 2014
Picon

[Patch Part3 V6 0/8] Enable support of Intel DMAR device hotplug

When hot plugging a descrete IOH or a physical processor with embedded
IIO, we need to handle DMAR(or IOMMU) unit in the PCIe host bridge if
DMAR is in use. This patch set tries to enhance current DMAR/IOMMU/IR
drivers to support hotplug and is based on latest Linus master branch.

All prerequisite patches to support DMAR device hotplug have been merged
into the mainstream kernel, and this is the last patch set to enable
DMAR device hotplug.

You may access the patch set at:
https://github.com/jiangliu/linux.git iommu/hotplug_v6

This patch set has been tested on Intel development machine.
Appreciate any comments and tests.

V5->V6:
1) Fix a race condition found during review
2) Refine dmar_walk_resources() to dmar_walk_remapping_entries()

Patch 1-4 enhances DMAR framework to support hotplug
Patch 5 enhances Intel interrupt remapping driver to support hotplug
Patch 6 enhances error handling in Intel IR driver
Patch 7 enhance Intel IOMMU to support hotplug
Patch 8 enhance ACPI pci_root driver to handle DMAR units

Jiang Liu (8):
  iommu/vt-d: Introduce helper function dmar_walk_resources()
  iommu/vt-d: Dynamically allocate and free seq_id for DMAR units
  iommu/vt-d: Implement DMAR unit hotplug framework
  iommu/vt-d: Search for ACPI _DSM method for DMAR hotplug
(Continue reading)

Brandon R Schwartz | 11 Sep 04:34 2014
Picon

Improper Naming in /dev/disk/by-id and Drives Offline

Hi,

I'm working on a particular issue (possibly two separate issues) where
our HDDs are (1) getting mislabeled in /dev/disk/by-id and (2)
dropping offline even though drive and controller logs show that the
drive is communicating and working as expected.  I don't have much
knowledge on the udev side of things so it would be great if someone
could offer some insight into the way udev assigns device names and if
there are thoughts as to why the OS cannot see the drive in certain
cases (timing issue?).

The first issue, the mislabeling problem, is that on reboots or power
cycles we occasionally see our drives become mislabeled in
/dev/disk/by-id.  We expect to see something like:

ata-ST3000DM001-1CH166_W1F26HKK
ata-ST3000DM001-1CH166_Z1F2FBBY

But instead we see:

ata-ST3000DM001-1CH166_W1F26HKK
scsi-35000c500668a9bdb

The "scsi" drive is assigned a drive letter and the OS can communicate
with the drive.  Drives logs and controller logs show the drive is
working properly, but for some reason it's getting labeled incorrectly
in /dev/disk/by-id.  We have looked through dmesg and enabled logging
in udev (udevadm control --log-priority=debug), but we have not seen
where these labels are coming from.

(Continue reading)


Gmane