1 |
Dale wrote: |
2 |
> Howdy, |
3 |
> |
4 |
> I was doing a update a while back and noticed a ewarn, enotice or |
5 |
> something going by. I used the elogviewer to go back and dig it out. |
6 |
> This is what it says: |
7 |
> |
8 |
> Found sources for kernel version: |
9 |
> 3.5.0-gentoo |
10 |
> Checking for suitable kernel configuration options... |
11 |
> ERROR (setup) |
12 |
> |
13 |
> CONFIG_USB_SUSPEND: is not set when it should be. |
14 |
> WARN (setup) |
15 |
udisks will work without that, but if you try to safely unplug a USB |
16 |
stick or other USB storage device, an error will occur because udisks is |
17 |
unable to power off the device before unplugging. |
18 |
The option is not required for its essential functionality, but it's |
19 |
definitely useful and does not add any big overhead to the kernel, so I |
20 |
always enable it and would recommend enabling it unless you have a |
21 |
strong reason not to set it. |
22 |
> |
23 |
> Please check to make sure these options are set correctly. |
24 |
> Failure to do so may cause unexpected problems. |
25 |
> |
26 |
> So, I go into the kernel's menuconfig and find this: |
27 |
> |
28 |
> │ CONFIG_USB_SUSPEND: │ |
29 |
> │ │ |
30 |
> │ If you say Y here, you can use driver calls or the sysfs │ |
31 |
> │ "power/control" file to enable or disable autosuspend for │ |
32 |
> │ individual USB peripherals (see │ |
33 |
> │ Documentation/usb/power-management.txt for more details). │ |
34 |
> │ │ |
35 |
> │ Also, USB "remote wakeup" signaling is supported, whereby some │ |
36 |
> │ USB devices (like keyboards and network adapters) can wake up │ |
37 |
> │ their parent hub. That wakeup cascades up the USB tree, and │ |
38 |
> │ could wake the system from states like suspend-to-RAM. │ |
39 |
> │ │ |
40 |
> │ If you are unsure about this, say N here. │ |
41 |
This message is on a lot of important stuff, it just means you will be |
42 |
able to use USB (at least on *some* machines) without enabling it. |
43 |
As soon as you have any reason to set it or know what it does, this |
44 |
recommendation is superfluous. Only take care if the help message says |
45 |
something like: |
46 |
* This is usually not needed, so if unsure, say no |
47 |
* This is highly experimental, ... |
48 |
* only set this as module ... |
49 |
* Do not enable unless ... |
50 |
In such cases, you should be sure what you are doing and usually no |
51 |
ebuild would require options like that. |
52 |
> │ │ |
53 |
> │ Symbol: USB_SUSPEND [=n] │ |
54 |
> │ Type : boolean │ |
55 |
> │ Prompt: USB runtime power management (autosuspend) and wakeup │ |
56 |
> │ Defined at drivers/usb/core/Kconfig:41 │ |
57 |
> │ Depends on: USB_SUPPORT [=y] && USB [=y] && PM_RUNTIME [=y] │ |
58 |
> │ Location: │ |
59 |
> │ -> Device Drivers │ |
60 |
> │ -> USB support (USB_SUPPORT [=y]) │ |
61 |
> │ -> Support for Host-side USB (USB [=y]) |
62 |
> |
63 |
> The important part is about 'if you are unsure about this, say N here'. |
64 |
> Well, I don't think I need USB remote wakeup or anything so I don't |
65 |
> think I need this but at the same time, udisk is giving me notice that |
66 |
> it should be there. |
67 |
> |
68 |
> This is a desktop system not a laptop. Do I need to listen to me not |
69 |
> needing it or udisk that says I do? |
70 |
This option is only USB relevant and can be used on any laptop / desktop |
71 |
system / whatever with USB support. |
72 |
> Opinions? |
73 |
> |
74 |
> Dale |
75 |
> |
76 |
> :-) :-) |
77 |
> |
78 |
> P. S. The only things I have USB right now is my printer and a camera. I |
79 |
> may have a UPS added to that when I get around to rebooting again. I'm |
80 |
> not sure on how I will end up connecting it yet. |
81 |
In case you have no USB sticks and never want to use any USB storage |
82 |
device, you won't need udisks at all, try disabling the "udisks" USE |
83 |
flags on your desktop packages (esp. gvfs). |
84 |
|
85 |
Regards, |
86 |
Felix |