Hi ,
During the installation of RHEL-7.X the driver pack drivers or OEMDRV is NOT getting detected on time, due to which the latest drivers will not get installed from OEMDRV.
The problem is due to slow usb.
Upon introducing the delay for slow usb (OEMDRV) during the insertion of modules after "udevadm trigger" everything works fine.
Here is the patch.
--- anaconda-19.31.79/dracut/driver-updates.sh 2015-04-20 23:03:45.160081886 +0530 +++ anaconda-19.31.79_new/dracut/driver-updates.sh 2015-04-20 23:07:38.719101243 +0530 @@ -4,6 +4,7 @@
# load all modules udevadm trigger +sleep 2 udevadm settle
# Look for devices with the OEMDRV label
Regards Balaji Singh
On Tue, 2015-04-28 at 09:57 +0530, B_B_Singh@DELL.com wrote:
Hi ,
During the installation of RHEL-7.X the driver pack drivers or OEMDRV is NOT getting detected on time, due to which the latest drivers will not get installed from OEMDRV.
The problem is due to slow usb.
Upon introducing the delay for slow usb (OEMDRV) during the insertion of modules after "udevadm trigger" everything works fine.
Here is the patch.
--- anaconda-19.31.79/dracut/driver-updates.sh 2015-04-20 23:03:45.160081886 +0530 +++ anaconda-19.31.79_new/dracut/driver-updates.sh 2015-04-20 23:07:38.719101243 +0530 @@ -4,6 +4,7 @@
# load all modules udevadm trigger +sleep 2 udevadm settle
Looks good to me, but I'm far from being expert in this area.
--- anaconda-19.31.79/dracut/driver-updates.sh 2015-04-20 23:03:45.160081886 +0530 +++ anaconda-19.31.79_new/dracut/driver-updates.sh 2015-04-20 23:07:38.719101243 +0530 @@ -4,6 +4,7 @@
# load all modules udevadm trigger +sleep 2 udevadm settle
# Look for devices with the OEMDRV label
Why isn't this udev's problem?
- Chris
-----Original Message----- From: anaconda-patches-bounces@lists.fedorahosted.org [mailto:anaconda- patches-bounces@lists.fedorahosted.org] On Behalf Of Chris Lumens Sent: Wednesday, April 29, 2015 7:31 PM To: anaconda-patches@lists.fedorahosted.org Subject: Re: [Patch for Review] Introduce delay for slow USB devices to detect OEMDRV on time.
--- anaconda-19.31.79/dracut/driver-updates.sh 2015-04-20
23:03:45.160081886 +0530
+++ anaconda-19.31.79_new/dracut/driver-updates.sh 2015-04-20
23:07:38.719101243 +0530
@@ -4,6 +4,7 @@
# load all modules udevadm trigger +sleep 2 udevadm settle
# Look for devices with the OEMDRV label
Why isn't this udev's problem?
- Chris
anaconda-patches mailing list anaconda-patches@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/anaconda-patches
Hi Chris,
No, this can't be done in udev because of below reasons.
If it is implemented in udev,
1. This would result in delay for all usb devices, which is NOT preferred since it impacts the boot time. 2. For each udevadm trigger in anaconda there will be a delay, to avoid this we can have delay for OEMDRV only in driver-updatesh.sh.
Please let me know your comments on this.
Regards Balaji Singh
- This would result in delay for all usb devices, which is NOT preferred since it impacts the boot time.
- For each udevadm trigger in anaconda there will be a delay, to avoid this we can have delay for OEMDRV only in driver-updatesh.sh.
I'm not asking for udev to just have an unqualified "sleep 2". I'm asking why the combination of udevadm trigger and then udevadm settle isn't enough. Why do we have to sleep? Why doesn't udev figure this out for us?
- Chris
-----Original Message----- From: Chris Lumens [mailto:clumens@redhat.com] Sent: Wednesday, May 06, 2015 7:45 PM To: Singh, B B Cc: anaconda-patches@lists.fedorahosted.org Subject: Re: [Patch for Review] Introduce delay for slow USB devices to detect OEMDRV on time.
- This would result in delay for all usb devices, which is NOT preferred
since it impacts the boot time.
- For each udevadm trigger in anaconda there will be a delay, to avoid this
we can have delay for OEMDRV only in driver-updatesh.sh.
I'm not asking for udev to just have an unqualified "sleep 2". I'm asking why the combination of udevadm trigger and then udevadm settle isn't enough. Why do we have to sleep? Why doesn't udev figure this out for us?
- Chris
Hi Chris,
What I observed is the uevents from kernel is NOT reaching to udevd on time & due to this the settle also fails to wait because there are no uevents to process in queue. I have even tried with "udevadm settle ---timeout=120/240/360 "option but this could not help, because it is returning immediately without any wait as queue is empty.
Regards Balaji Singh
anaconda-patches@lists.fedorahosted.org