| 1 |
On Tue, Apr 6, 2010 at 10:54 AM, Joerg Schilling |
| 2 |
<Joerg.Schilling@××××××××××××××××.de> wrote: |
| 3 |
> Paul Hartman <paul.hartman+gentoo@×××××.com> wrote: |
| 4 |
> |
| 5 |
>> >> Would a HAL preprobe FDI like this prevent it from interfering with burning? |
| 6 |
>> > |
| 7 |
>> > Could you explain what this means? |
| 8 |
>> |
| 9 |
>> I was just thinking if HAL is instructed to ignore the device maybe it |
| 10 |
>> won't bother it any more (if that's even the cause of Dale's problem). |
| 11 |
>> Not a fix but a workaround. Maybe not even a workaround. :) |
| 12 |
> |
| 13 |
> I have been told that this could work but I have no idea on how to do this. |
| 14 |
|
| 15 |
Create a file in /etc/hal/fdi/preprobe/ containing these contents: |
| 16 |
|
| 17 |
<?xml version="1.0" encoding="UTF-8"?> |
| 18 |
<deviceinfo version="0.2"> |
| 19 |
<device> |
| 20 |
<match key="storage.drive_type" string="cdrom"> |
| 21 |
<merge key="info.ignore" type="bool">true</merge> |
| 22 |
</match> |
| 23 |
</device> |
| 24 |
</deviceinfo> |
| 25 |
|
| 26 |
Then reboot (or maybe restart HAL is enough). It should hopefully make |
| 27 |
HAL completely ignore the cdrom device. (maybe edit to match your |
| 28 |
specific device) |
Archives