DSD: No Tour for Device

Hi Experts
I am working on DSD
All backend configurations have been done. Data is coming in the connector tables.
We are facing 2 problems for the data which is coming on the middleware(MI Server) from the connector tables
1. Data in all Sync Bou2019s except in DSD_REGION is in waiting status(I-Waiting)
2. Data being sent to DSD_REGION shows
u201CSYNCRONIZER_CONTROL_DISABLEDu201D
As data is not coming properly on the MI Server we are getting the following message on the MI AWT Client
u201CNo tour for deviceu201D
Whereas, on the DSD Administrator console all the data(Tour id, driver, vehicle) is coming for the device.
What can be the problem for the data which is coming in waiting state? Any other reason for the message showing u201CNo tour for deviceu201D?
Regards,
Ashima Sharma
Edited by: Ashima Sharma on Jun 13, 2008 10:49 AM

Hi,
1. When I look at the transaction /DSD/ME_CPT and try to select the device I'm having some trouble to determine exactly the device I want to associate. For example:
Firstly copy your device id from your AWT client and go to transaction Merep_pd
Select TAb Mobile ID
Press F4 at Mobile ID
paste ur device id at Device GUID and press enter and select mobile id with MDS component and r/3 user assigned to it.
this is the correct mobile id u need to assign at connector cockpit.
Download MDSD monitoring guide from SMP....it will help u a lot
Regards,
Akhil

Similar Messages

MDSD: No tour for device

Hi Folks,
We are facing some trouble when synchronizing, in this case, downloading the tour information to the device.
I believe we have everything configured correctly. We also have installed DSD Administration Console. Our test is that we have created a business scenario, with sales order, delivery, shipment, and finally we have checked out.
With the check out executed, we saw that an IDOC was generated for the message type: /DSD/HH_CONTROL
After that, at the DSD Administration Console, Sync. Status Overview, we can see the following information:
Device Tour No. Driver Vehicle ID Status
GLI V0000000056 CPB1000500 TRUCK02 P - Info: Device notified of tour readiness
Download Status we have:
Tour data ready: S - Info: Successfully processed for download
Pricing data readiness: S - Info: Successfully processed for download
The device is correctly registered. We can see the device at the device maintenance, and we have configured /DSD/ME_CPT for the user GLI and selected the corresponding device plus assigned the driver and vehicle to it. When we synchronize we are getting on the device that, no tour was found for the device. But we can see that the tour is available for the device, but somehow the device can't get it.
I have several questions about this:
1. When I look at the transaction /DSD/ME_CPT and try to select the device I'm having some trouble to determine exactly the device I want to associate. For example:
When I hit the matchcode I get Mobile ID's, User, MSD_NAME, but at the Device Maintenance From the MI, there is no Mobile ID, instead there are Device Name, Device ID and USER. But USER wouldn't be enough if I have several devices associated to a user. Under this scenario the way I'm identifying the device is just selecting random mobile ID associated with user and MDS_Name and after this, compare device ID to assure that I'm selecting the correct one.
Is there an easier way, or am I missing something about device assignments?
2. What does the synchronization checks to determine what should be sent to what device? The device ID? I ask this because there also a field called Channel ID.
I would really appreciate any help you can give me to guide me through the synchronization problem.
Regards,
Gilberto Li
Edited by: Gilberto Li on Mar 3, 2010 9:41 PM

Hi,
1. When I look at the transaction /DSD/ME_CPT and try to select the device I'm having some trouble to determine exactly the device I want to associate. For example:
Firstly copy your device id from your AWT client and go to transaction Merep_pd
Select TAb Mobile ID
Press F4 at Mobile ID
paste ur device id at Device GUID and press enter and select mobile id with MDS component and r/3 user assigned to it.
this is the correct mobile id u need to assign at connector cockpit.
Download MDSD monitoring guide from SMP....it will help u a lot
Regards,
Akhil

Data not coming from DOE to Mobile After defining Rule for device attribute

Hi All,
I have created a DO and rule for it.In case of Bulk Rule for all definition when i triggere extract from Portal then all the data comes to outbound queue but when i define rule for Device attribute then no data comes to my Outboun queue.Here is the scenario what i am doing :
1. I have order header in my backend which has a field named "Work_Center" and this will be criteria field.
2. In CDS table i have all the records for all the work center.
3. Now in RMM under customized , i have added an attribute named "Work_center".
4. Now i defined a rule with Device attribute mapping and activated the rule.
5. Now on Portal i assigned this data object and in the device attribute tab i assigned the value(this value exist in CDS table for few orders) of a Work center to the attribute "Work_Center" .
6. Then i triggrere extract but its Outbound queue is empty, what could be the reason.
Is my approach is correct
Regards,
Abhishek

Hi Abhishek,
You can check one ore thing, after you have performed all the steps till step 5, i.e. just before triggering
extract. Check if the AT table for ur DO has entries based on the criteria specified by you...
1. In the workbench click on the Data Object, and then right click and select "View Metadata".
2. Select Distribution Model tab.
3. Now select your DO's Association table.
4. For the input field DEVICE ID specify your corresponing device id,and also for status field specify it
as "I" and execute
If there are any entries now in the AT table, and on triggering extract if they are not coming to the
outbound Q there is some EXTRACT Q blocked. And is there were no entries in the AT then the rule
specified is not the satifying.
Thanks,
Swarna
Now if you have entries w

HT201401 My bluetooth is no longer working in the car - it keeps 'searching' for devices

My bluetooth is no longer working in the car - it keeps 'searching' for devices. Anyone ever had this issue?
Thanks

Can you connect from your phone to another BT device, not the car? If you haven't ,I'd try a reset of the phone by holding the home and power button down. Next step would be to talk to your dealership and see if they have any ideas. Sometimes software can either get updated on iOS or on the vehicle and it can cause problems. Every dealership seems to have a go-to person that handles issues like this. Getting to know him or her well and getting their direct phone number will pay big dividends. A device restore might be necessary, but if it were me I'd talk to the dealership first.

Hp LaserJet 1200 Generic Class: Waiting for device

I have 2 computers that I want to print to my hp Laserjet 1200 printer. We are using an iogear 4-port usb 2.0 sharing switch. One computer prints fine but the other always displays a message "Generic Class: Waiting for device." Help!

Both computers have the printer driver installed. The usb device does not have a driver to install. You just plug in the usb cords to each computer and the printer. You only install a driver if using a pc operating system.

HP LaserJet 5200 - Yet another "GenericClass: waiting for device" problem

I have an HP LaserJet 5200 that worked until today. I have changed nothing and replaced nothing and now I'm getting the ol' "GenericClass: waiting for device." It worked when I first went to 10.5.4, so that's not the issue. The connection obviously works because the computer recognizes the printer. I've deleted and reinstalled everything under the sun related to printing to no avail.
Any ideas? I'm hoping I don't have a $2000 paper weight.
Thanks in advance
Message was edited by: Wesley Johnson

Several Leopard users are reporting that HP printers no longer work with USB-parallel adapter cables. I don't know why.
The best solution is to put the printer on the network, either by buying the jetdirect card that fits that model (on eBay), or by buying a used parallel port print server.

Devices not detected - where is the drop down menu for device?

the latest 11.0.1 update doesn't have the dropdown menu for devices and if i click on FILE > DEVICES, nothing happens plus all the selections are greyed out!
can anyone explain?
thanks

Thanks, but the issue was that i had to restart my computer! iTunes has detected my devices now, but thanks!

I put ios7.1 to my ipad it was working not it is asking for activite for developer and allready registered to my developer for devices but now it does not actived

I put ios7.1 to my ipad it was working not it is asking for activite for developer and allready registered to my developer for devices but now it does not actived

If you are an authorized member of Apple's developer program, you have forums and resources through which you can address issues with seed versions of Apple's software. Posting here or in any public forum is a violation of your NDA with Apple. The developer forums can be found here:
https://developer.apple.com/devforums/
If you are not an authorized developer, then you have an illegal copy of the software.
Either way, we cannot help you with questions about unreleased Apple software in these forums.
Regards.

[SOLVED] dmraid "Timed out waiting for device" at boot

Created a bug report with solution proposal: https://bugs.archlinux.org/task/33166
I created a virtual machine to demonstrate the problem
https://docs.google.com/open?id=0B40Hp1 … WZUQ21xZk0
The root and the other mount points are all on one raid disk. Although the root mounts quickly, other mount points cause timeouts at boot time.
dmraid prints that all /dev/mapper/isw_* devices are created.
I think /dev/disk/by-uuid/* links are created too, but for some reason systemd doesn't see them.
After boot I can execute "mount -a" without errors.
here's my fstab:
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=e89249d8-49a5-415b-8f9b-97de5cfbe82d / ext3 defaults
UUID=c37f8bdd-3d6c-495f-bf8a-5ef059e55254 swap swap defaults 0 0
UUID=91988343-dd89-43b9-8975-babb0b9510a2 /media/ARCHLINUXNEW ext4 nofail 0 1
UUID=62C813E9C813B9ED /media/distrpart ntfs-3g rw,nofail
UUID=E0A1-D623 /media/realboot vfat rw,codepage=866,iocharset=utf8,umask=002,noatime,nofail
# journalctl -b
Dec 15 00:25:24 localhost kernel: firewire_core 0000:05:03.0: created device fw0: GUID 0011d800017a5dd7, S400
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-E0A1\x2dD623.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/realboot.
Dec 15 00:26:50 localhost systemd[1]: Job media-realboot.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-62C813E9C813B9ED.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/distrpart.
Dec 15 00:26:50 localhost systemd[1]: Job media-distrpart.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/ARCHLINUXNEW.
Dec 15 00:26:50 localhost systemd[1]: Job media-ARCHLINUXNEW.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/91988343-dd89-43b9-8975-babb0b9510a2.
Dec 15 00:26:50 localhost systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.service/start failed with result 'dependency
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /dev/disk/by-uuid/c37f8bdd-3d6c-495f-bf8a-5ef059e55254.
Dec 15 00:26:50 localhost systemd[1]: Reached target Swap.
Note the 1.5 minute pause
# mount | grep /dev/mapper
/dev/mapper/isw_ebaifefjbf_Volume0p9 on / type ext3 (rw,relatime,stripe=64,data=ordered)
/dev/mapper/isw_ebaifefjbf_Volume0p1 on /media/realboot type vfat (rw,noatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp866,iocharset=utf8,shortname=mixed,errors=remount-ro)
/dev/mapper/isw_ebaifefjbf_Volume0p8 on /media/ARCHLINUXNEW type ext4 (rw,relatime,stripe=64,data=ordered)
/dev/mapper/isw_ebaifefjbf_Volume0p5 on /media/distrpart type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
Last edited by leniviy (2012-12-22 16:06:25)

I've ran into exactly same problem lately, but finally solved it.
Setup: Intel Fake RAID, mirror, partitioned as:
/dev/mapper/isw_dfjeffgfaj_rootvol1 /boot
/dev/mapper/isw_dfjeffgfaj_rootvol2 /
/dev/mapper/isw_dfjeffgfaj_rootvol3 /home (dm-crypted)
In /etc/fstab i had following mountpoints:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
/dev/mapper/isw_dfjeffgfaj_rootvolp1 /boot ext4 rw,relatime,data=ordered 0 2
and boot hung on waiting for /dev/mapper/isw_dfjeffgfaj_rootvolp1. Solution involves changing dev path to UUID:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
UUID=44809529-11d9-4f53-9652-7b97ed077225 /boot ext4 rw,relatime,data=ordered 0 2
For some reason symlinks /dev/mapper/isw* are not present during systemd mount.

Inappropriate ioctl for device

Hello,
I have some zones set up in solaris 10. When i try to scp a file to any of the zones, i get the following error:
"shell-init: error retrieving current directory: getcwd: cannot access parent directories: Inappropriate ioctl for device"
1. /export/home is mounted using lofs in to the zone from the parent.
2. This does not happen when i scp something to the parent
3. This does not happen on an account which is local to the zone, whose default shell is bash
3. This does not happen on an NIS account whose default shell is ksh
4. This does happen on all NIS accounts who have a default shell of bash, even if there is nothing in their home directory (ie, no .bashrc).
5. There is no mention of tty in /etc/profile or /etc/.login
6. I have tried changing the default TERM to vt100 from xterm, it still happens
7. The error does not present itself upon a normal ssh login
8. the error [n]does[n] show up when i do something like `ssh myzone "id"` from another box or zone.
If i don't mount /export/home from the parent in to the zone, i do not get this error. There must be some problem with how i set this up maybe? Here's the zonecfg info:
zonepath: /export/zones/vwsuserz
autoboot: true
pool:
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
fs:
dir: /export/home
special: /export/home
raw not specified
type: lofs
options: [rw,nodevices]
net:
address: 10.222.136.162
physical: bge0
I've been googling for a long time and no one seems to have found a resolution. Does anyone have insight in to this problem?
Message was edited by:
keegang
Message was edited by:
keegang

The problem maybe a permissions on your parent directory, I had a similar error:
root@elliot:~ # ls -ald ../
drwx-----x 9 root root 512 Feb 15 14:33 ../
jemurray@freiwald:~ $ scp hat.txt elliot.nts.wustl.edu:
shell-init: error retrieving current directory: getcwd: cannot access parent directories: Permission denied
hat.txt 100% |**********************************************************************************| 1428 00:00
root@elliot:~ # chmod 755 ../
root@elliot:~ # ls -ald ../
drwxr-xr-x 9 root root 512 Feb 15 14:33 ../
jemurray@freiwald:~ $ scp hat.txt elliot.nts.wustl.edu:
hat.txt 100% |**********************************************************************************| 1428 00:00
We used to try and have our main /export/home directory 701 permissions, but we received this error. Permissions 755 make the problem go away. Not the best answer, but for the users we have on our systems, it is not a big deal.

Stuck on waiting for device to become ready...

I did a slide show on iDVD now I'm trying to burn it on a Phillips dvd but it reads waiting for device to become ready. this continues & it does not burn the dvd. I tried the save as disk image but the same thing happens. the utility was no help on getting it started

Hi Don't:
Just assuming here (which is always dangerous)...
Is there any audio associated with your slideshow?
Sue
PS Verbatim DVD-R (you are using DVD-R, right?) is about the best there is....

WES 7 OSD standalone (works) vs bootable (fails) - Failed to find suitable device driver for device (help)

Hi everyone,
I'm trying to deploy a Windows Embedded Standard 7 (trial key at the moment) image in SCCM 2012 SP1 with a very simple task sequence.
I have a 'build and capture' and an OSD TS. I'm testing these on Hyper-V PCs and both work fine when i create stand alone media. The problem arrises when I try to deploy (or build & capture) with a bootable media;
The TS starts, formats the disk, applies the OS, Windows and network settings, Apply Device Drivers etc., but when it reboots into Windows
(or WES7 to be exact) it cant boot. The Windows Boot Manager reports a 0xc0000359 for storvsc.sys
And I can't figure out what's wrong. I will post the SMSTS log further down below. The SAME TS works fine when it's a stand alone media.
I have tried to:
- Apply the WIM manually (nothing wrong - boots fine)
- Create and apply driver package for the Hyper-V machines (from the MSI's Windows5.x-HyperVIntegrationServices-x86 and Windows5.x-HyperVIntegrationServices-x64)
- No dice
- Create a new boot image with the hyper-v drivers in it. No dice
- Google everything related I can think of.
I suspect it has something to do with the lines where it says:
"Failed to find a suitable device driver for device xxx”
It also has a couple of 401 errors when trying to get the packages, but it seems like it DOES end up getting the content.
Please help! What could it be?
I have 2 Hyper-V machines; one w. legacy network adapter - one not. Both have same issue.
I have 2 Hyper-V machines; one w. legacy network adapter - one not. Both have same issue.
SMSTS log key points are (the log is too long to post here):
401 - Authentication failure on request with anonymous access, retrying with context credentials.
OSDDriverClient
5/6/2014 4:03:41 PM     612 (0x0264)
401 - Authentication failure on request with context credentials, retrying with supplied credentials.
OSDDriverClient
5/6/2014 4:03:41 PM     612 (0x0264)
Downloaded file from http://<CUSTOMER DP REMOVED>:80/SMS_DP_SMSPKG$/56D13589-D906-4697-8A1E-1CC3211902AA/sccm?/s3cap.inf to C:\_SMSTaskSequence\ContentCache\56D13589-D906-4697-8A1E-1CC3211902AA\s3cap.inf
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Downloaded file from http://<CUSTOMER DP REMOVED>:80/SMS_DP_SMSPKG$/56D13589-D906-4697-8A1E-1CC3211902AA/sccm?/vmbusvideo.cat to C:\_SMSTaskSequence\ContentCache\56D13589-D906-4697-8A1E-1CC3211902AA\vmbusvideo.cat
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Downloaded file from http://<CUSTOMER DP REMOVED>:80/SMS_DP_SMSPKG$/56D13589-D906-4697-8A1E-1CC3211902AA/sccm?/vms3cap.sys to C:\_SMSTaskSequence\ContentCache\56D13589-D906-4697-8A1E-1CC3211902AA\vms3cap.sys
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Download done setting progress bar to 100
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) VerifyContentHash: Hash algorithm is 32780
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Installing driver "Microsoft Emulated S3 Device Cap"
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Adding "C:\_SMSTaskSequence\ContentCache\56D13589-D906-4697-8A1E-1CC3211902AA" to Windows driver store.
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Setting %SystemRoot% to "C:\WINDOWS"
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "amd64"
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Added list item with key value '1'
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Writing configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Successfully saved configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Setting temporary directory to 'C:\_SMSTaskSequence\PkgMgrTemp'.
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Calling Package manager to add drivers to the offline driver store.
OSDDriverClient
5/6/2014 4:03:41 PM    612 (0x0264)
Command line for extension .exe is "%1" %*
OSDDriverClient
5/6/2014 4:03:41 PM
612 (0x0264) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"
OSDDriverClient
5/6/2014 4:03:41 PM    612 (0x0264)
Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"
OSDDriverClient
5/6/2014 4:03:41 PM    612 (0x0264)
Process completed with exit code 0
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Dism successfully added drivers to the offline driver store.
OSDDriverClient
5/6/2014 4:03:45 PM    612 (0x0264)
Successfully added "C:\_SMSTaskSequence\ContentCache\56D13589-D906-4697-8A1E-1CC3211902AA" to the Windows driver store.
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Successfully installed driver "Microsoft Emulated S3 Device Cap".
OSDDriverClient
5/6/2014 4:03:45 PM    612 (0x0264)
Entering ReleaseSource() for C:\_SMSTaskSequence\ContentCache\56D13589-D906-4697-8A1E-1CC3211902AA
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) reference count 1 for the source C:\_SMSTaskSequence\ContentCache\56D13589-D906-4697-8A1E-1CC3211902AA before releasing
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Released the resolved source C:\_SMSTaskSequence\ContentCache\56D13589-D906-4697-8A1E-1CC3211902AA
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Ranking compatible drivers for VMBUS\{57164F39-9115-4E78-AB55-382F3BD5422D}\{FD149E91-82E0-4A7D-AFA6-2A4166CBD7C0}
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) SCOPEID_4AA3EF76-E8E6-4FC3-8E79-00F39F7D1CB5/DRIVER_C01B80DA1C014302CC793357FF0F1C0486554D11_0E4046FEF6FF1BC7776A060DF1B19003E0B5640936488E08E61C41D47A8B26C2 (SMS Driver Rank = 0x0000)
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) SCOPEID_4AA3EF76-E8E6-4FC3-8E79-00F39F7D1CB5/DRIVER_C01B80DA1C014302CC793357FF0F1C0486554D11_8E607B402D9A9C9A0FBC0881F11231BDA52B4C8851F1BA00F7E8B3D932FC4871 (SMS Driver Rank = 0x0000)
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) SCOPEID_4AA3EF76-E8E6-4FC3-8E79-00F39F7D1CB5/DRIVER_C01B80DA1C014302CC793357FF0F1C0486554D11_54E81CFA62FCB88FCA9D60C01594AA5FCEE40F9D5B28F47DE2A7B70C91268F17 (SMS Driver Rank = 0x0000)
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Driver "Hyper-V Heartbeat" has already been installed.
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Failed to find a suitable device driver for device 'Intel 82443BX Pentium(R) II Processor to PCI Bridge'.
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Failed to find a suitable device driver for device 'Generic Monitor'.
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Ranking compatible drivers for VMBUS\{A9A0F4E7-5A45-4D96-B827-8A841E8C03E6}\{242FF919-07DB-4180-9C2E-B86CB68C8C55}
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) SCOPEID_4AA3EF76-E8E6-4FC3-8E79-00F39F7D1CB5/DRIVER_C01B80DA1C014302CC793357FF0F1C0486554D11_0E4046FEF6FF1BC7776A060DF1B19003E0B5640936488E08E61C41D47A8B26C2 (SMS Driver Rank = 0x0001)
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) SCOPEID_4AA3EF76-E8E6-4FC3-8E79-00F39F7D1CB5/DRIVER_C01B80DA1C014302CC793357FF0F1C0486554D11_8E607B402D9A9C9A0FBC0881F11231BDA52B4C8851F1BA00F7E8B3D932FC4871 (SMS Driver Rank = 0x0001)
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) SCOPEID_4AA3EF76-E8E6-4FC3-8E79-00F39F7D1CB5/DRIVER_C01B80DA1C014302CC793357FF0F1C0486554D11_54E81CFA62FCB88FCA9D60C01594AA5FCEE40F9D5B28F47DE2A7B70C91268F17 (SMS Driver Rank = 0x0001)
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Driver "Hyper-V Heartbeat" has already been installed.
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Failed to find a suitable device driver for device 'Numeric data processor'.
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Ranking compatible drivers for VMBUS\{35FA2E29-EA23-4236-96AE-3A6EBACBA440}\{2450EE40-33BF-4FBD-892E-9FB06E9214CF}
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) SCOPEID_4AA3EF76-E8E6-4FC3-8E79-00F39F7D1CB5/DRIVER_C01B80DA1C014302CC793357FF0F1C0486554D11_8E607B402D9A9C9A0FBC0881F11231BDA52B4C8851F1BA00F7E8B3D932FC4871 (SMS Driver Rank = 0x0001)
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) SCOPEID_4AA3EF76-E8E6-4FC3-8E79-00F39F7D1CB5/DRIVER_C01B80DA1C014302CC793357FF0F1C0486554D11_54E81CFA62FCB88FCA9D60C01594AA5FCEE40F9D5B28F47DE2A7B70C91268F17 (SMS Driver Rank = 0x0001)
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) SCOPEID_4AA3EF76-E8E6-4FC3-8E79-00F39F7D1CB5/DRIVER_C01B80DA1C014302CC793357FF0F1C0486554D11_0E4046FEF6FF1BC7776A060DF1B19003E0B5640936488E08E61C41D47A8B26C2 (SMS Driver Rank = 0x0001)
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Driver "Hyper-V Heartbeat" has already been installed.
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Failed to find a suitable device driver for device 'Microsoft System Management BIOS Driver'.
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264) Failed to find a suitable device driver for device 'CD-ROM Drive'.
OSDDriverClient
5/6/2014 4:03:45 PM 612 (0x0264)
Exiting with return code 0x00000000
OSDDriverClient
5/6/2014 4:03:45 PM
612 (0x0264)
In advance: Sorry...

Hi,
0xc0000359 for storvsc.sys
Looks like Hyper-v Storage Controller driver issue.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

In ITunes I don't have a listing in the column for "Devices" so I can check to see if I have sync all ringtones. I have one downloaded but can't get it synced to my Iphone.

In Itunes I don't have a listing in the column for "Devices" so I can check to see if my Iphone can sync all my new ringtones. I have one ready to go but cannot get it downloaded to my Iphone. Where is my "Devices" heading in the column on the left side of my Itunes page?

Connect your device to computer. In iTunes left Pane, select your iPhone under 'Devices'. Then on th right Pane, select Tones tab.

[SOLVED] Waiting 10 seconds for device...

I'm getting a "waiting 10 seconds for device..." on boot, and then it waits 10 seconds and boots me to a recoverely shell.
I do realise a lot of people have had this problem, but the solutions all imply the Fallback. When I boot to fallback, I get the exact same error, so I can't use those solutions.
It seems that I have to run "mkinitcpio -p linux", can I do that from a livecd. If yes, how?
Any ideas? Thank you.
Last edited by ephan (2012-11-09 17:02:52)

I'm glad you fixed it. But you don't have to reinstall packages, just run mkinitcpio -p linux and you'll be fine (reinstallation also works because mkinitcpio -p linux is invoked during the process).

[Solved] Boot messages waiting 10 secodns for device...

Hello.
When i'm boot my arch i got message waiting 10 secdonds for device /dev/sda1 (arch partition).
I have in mkinitcpio this modules:
ahci ext4 scsi_mod sd_mod libata.
That's all what can i do run arch wihout waiting 10 secodns?
Last edited by SpeedVin (2009-06-26 13:56:57)

paranoos wrote:
after a little digging, i realized this is caused by mkinitcpio. it defaults to 10 seconds, but most drives don't need to wait at all. this delay is available for people booting off usb devices which take a few seconds to initialize. the default should be no waiting, with an option for those who need it (by setting the kernel rootdelay manually).
afaict this is a bug, here is the fix
edit /lib/initcpio/init; where it says
# If rootdelay is empty or not a non-negative integer, set it to 10
if [ -z "${rootdelay}" -o ! "${rootdelay}" -ge 0 ]; then
export rootdelay=10
fi
change it to export rootdelay=0 -- this way, the default is not to wait
also edit /lib/initcpio/init_functions; where it says
if [ "$2" -gt 0 ]; then
seconds="$2"
change -gt 0 to -ge 0 -- this way, it will accept a setting of 0 and not ignore it.
Great that's working thamk you

DSD: No Tour for Device

Similar Messages

Maybe you are looking for