Re: udev problem ?

[Brad Rogers]

On Tue, 10 Dec 2013 21:36:46 +0100
Erwan David  wrote:

Hello Erwan,

>Le 10/12/2013 20:25, Brad Rogers a écrit :
>> echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs  
>Thanks it works.

YW, but like I said, it's not my work.  I'm just the messenger.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
The stakes were high but the danger low
Charade - Skids


signature.asc
Description: PGP signature

Re: udev problem ?

[Erwan David]

Le 10/12/2013 20:25, Brad Rogers a écrit :
> echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs

Thanks it works.





signature.asc
Description: OpenPGP digital signature

Re: udev problem ?

[Brad Rogers]

On Tue, 10 Dec 2013 19:25:27 +0100
Erwan David  wrote:

Hello Erwan,

Your problem has been discussed on this list recently.  Search for "CD
drive not showing up anymore", if you want to read it.  Credit for the
following info is due to them, not me.

>So where could be the problem ?

It seems to be in udev, and bug reports are filed.  There is a fix, but
you have to do it after every reboot.  The command should be executed
during a normal boot process but for some reason, it's not being in
Jessie ATM, so as root, do;

echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs

and your device notifier will work.  Currently, it's what I do whilst
waiting for a fix from upstream.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Walking through town is quite scary
I Predict A Riot - Kaiser Chiefs


signature.asc
Description: PGP signature

Re: udev problem ?

[Erwan David]

Le 10/12/2013 19:25, Erwan David a écrit :
> I am use jessie with KDE.
>
> When I plug my phone I see in /var/log/syslog 2 drives appearing (sdc
> and sdd one for the phone, one for the flashcard inside).
> They appear as soon as I plug, before I activate the USB storage on the
> phone.
>
> When I activate the USB mass storage, nothing happens, /dev/sdc1 and
> /dev/sdd1 do not appear.
>
> However if I fdisk /dev/sdc, the partition appears and the device
> notifier shows me the device.
>
> So where could be the problem ?
>
> PS: I also tried in MTP mode, but depending on the jessie instance
> mtp-probe detects a mtp device, or not...
>  

For the MTP problem I see a difference wether I plug the phone on a
USB-3 (works) or USB-2 port (don't work)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52a76294.7020...@rail.eu.org

udev problem ?

[Erwan David]

I am use jessie with KDE.

When I plug my phone I see in /var/log/syslog 2 drives appearing (sdc
and sdd one for the phone, one for the flashcard inside).
They appear as soon as I plug, before I activate the USB storage on the
phone.

When I activate the USB mass storage, nothing happens, /dev/sdc1 and
/dev/sdd1 do not appear.

However if I fdisk /dev/sdc, the partition appears and the device
notifier shows me the device.

So where could be the problem ?

PS: I also tried in MTP mode, but depending on the jessie instance
mtp-probe detects a mtp device, or not...
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52a75c97.8020...@rail.eu.org

udev problem

[Richard]

Hi there looks like there has been a change in the way udev handles its rules.
I'm using piklab which I've use consistently for a few years.
I can now only use it as root, as it wont allow the connection to the usb 
programer.
The things which normally work are the add to groups, piklab and usbuser and 
add myself to them.
also to add rules in /etc/udev/rules.d
026-piklab.rules
#PICKit 1
ATTR{idVendor}=="04d8", ATTR{idProduct}=="0032", OWNER:="root", 
GROUP:="microchip",MODE:="0660"
#PICKit 2
ATTR{idVendor}=="04d8", ATTR{idProduct}=="0033", OWNER:="root", 
GROUP:="microchip",MODE:="0660"
#ICD2
ATTR{idVendor}=="04d8", ATTR{idProduct}=="8001", OWNER:="root", 
GROUP:="microchip",MODE:="0660"
#ICD21
ATTR{idVendor}=="04d8", ATTR{idProduct}=="8001", OWNER:="root", 
GROUP:="microchip",MODE:="0660"
#PICDEM FS USB Bootloader
ATTR{idVendor}=="04d8", ATTR{idProduct}=="000b", OWNER:="root", 
GROUP:="microchip",MODE:="0660"

11-usbuser.rules
ACTION=="add", BUS=="usb", GROUP:="usbuser", MODE:="0666"

That normally works, but not now.

As a user I get 
USB Port: Could not find USB device (vendor=0x04D8 product=0x8001). 

lsusb shows
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 04b8:0007 Seiko Epson Corp. Printer
Bus 004 Device 002: ID 046d:c05f Logitech, Inc. 
Bus 006 Device 002: ID 04d8:8001 Microchip Technology, Inc. ICD2 in-circuit 
debugger

It is there and is usable by root :(

I'm also a member of the group microchip


For a long while as you boot up there has been a message the udev is changing 
from action to attributes

I'm also getting similar problems with another app which uses /dev/ttyS0.

Whats changed ??

TIA

-- 
Best wishes / 73
Richard Bown

e-mail: rich...@g8jvm.com   or   richard.b...@blueyonder.co.uk

nil carborundum a illegitemis
##
Ham Call G8JVM . OS Debian Wheezy/Sid amd64 on a Dual core AMD Athlon 5200, 4 
GB RAM
Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W ( degs mins )
QRV HF + VHF Microwave 23 cms:140W,13 cms:100W,6 cms:10W & 3 cms:5W
##
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111201180044.2e9de...@g8jvm.com

Re: libnss-ldap udev problem

[Marc Franquesa]

Finally I found  that udev needs (in some cases) to resolve its own
hostname (I haven't set the hostname on /etc/hosts).

Putting the hostname in /etc/hosts with this nsswitch.conf configuration
works for the other two hosts. (Despite one of them can boot without
this setup).

10 de 10 de 2010 a les 23:59 +0200, Marc Franquesa wrote:

> I have the same problem described in the Bug 375077, despite this bug
> appears as fixed in 251-4 version, my hosts running Debian Lenny show
> the same behavior reported in it. Four hosts with Lenny installed (and
> different architectures: i386, arm and mips) have this exact same issue:
> udev hangs indefinitely when using libnss-ldap. No timeouts, no error
> messages, ... nothing, I can press Ctrl+C and the boot process continue.
> If I configure nsswitch to use only local files, udev boots correctly.
> 
> I am using libnss-ldap, and my /etc/nsswitch.conf is this:
> 
> passwd: files ldap [UNAVAIL=return]
> group:  files ldap [UNAVAIL=return]
> shadow: files ldap [UNAVAIL=return]
> hosts:  files dns ldap [UNAVAIL=return]
> networks:   files ldap [UNAVAIL=return]
> protocols:  db files ldap [UNAVAIL=return]
> services:   db files ldap [UNAVAIL=return]
> ethers: db files
> rpc:db files ldap [UNAVAIL=return]
> automount:  files ldap [UNAVAIL=return]
> 
> And libnss-ldap is configured with bind_policy soft.
> 
> I have detected that some udev-rules search for groups not
> in /etc/groups (like nvram or fuse) I added them to local files, but reading 
> the bug report (IMHO),
> bind_policy soft would be enough to exit immediately if network nor LDAP
> is available and udev would boot normaly. Currently all of my Debian
> Lenny hosts show this same problem during boot, udev hangs without any error 
> message.
> 
> The most strange is that I've create the nvram group in all 4 hosts and in 
> one of them udev boots
> normally now, but other three shows the same problem: udev hangs if nsswitch 
> is configured to seek libnss-ldap.
> 
> I don't like to reopen again the old bug before comenting it in the list and
> probably this is a misconfiguration or libnss-ldap installation problem.
> Can someone provide some clues? 
> 
> Thank you
> 
> 
> 
> -- 
> --
> Marc Franquesa
> Lady 3Jane http://www.l3jane.net/
> Warbaby
> 
> 
> 
> 
> 

-- 
--
Marc Franquesa
Lady 3Jane http://www.l3jane.net/
Nexus




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1287122045.2415.2.ca...@nexus.l3jane.net

libnss-ldap udev problem

[Marc Franquesa]

I have the same problem described in the Bug 375077, despite this bug
appears as fixed in 251-4 version, my hosts running Debian Lenny show
the same behavior reported in it. Four hosts with Lenny installed (and
different architectures: i386, arm and mips) have this exact same issue:
udev hangs indefinitely when using libnss-ldap. No timeouts, no error
messages, ... nothing, I can press Ctrl+C and the boot process continue.
If I configure nsswitch to use only local files, udev boots correctly.

I am using libnss-ldap, and my /etc/nsswitch.conf is this:

passwd: files ldap [UNAVAIL=return]
group:  files ldap [UNAVAIL=return]
shadow: files ldap [UNAVAIL=return]
hosts:  files dns ldap [UNAVAIL=return]
networks:   files ldap [UNAVAIL=return]
protocols:  db files ldap [UNAVAIL=return]
services:   db files ldap [UNAVAIL=return]
ethers: db files
rpc:db files ldap [UNAVAIL=return]
automount:  files ldap [UNAVAIL=return]

And libnss-ldap is configured with bind_policy soft.

I have detected that some udev-rules search for groups not
in /etc/groups (like nvram or fuse) I added them to local files, but reading 
the bug report (IMHO),
bind_policy soft would be enough to exit immediately if network nor LDAP
is available and udev would boot normaly. Currently all of my Debian
Lenny hosts show this same problem during boot, udev hangs without any error 
message.

The most strange is that I've create the nvram group in all 4 hosts and in one 
of them udev boots
normally now, but other three shows the same problem: udev hangs if nsswitch is 
configured to seek libnss-ldap.

I don't like to reopen again the old bug before comenting it in the list and
probably this is a misconfiguration or libnss-ldap installation problem.
Can someone provide some clues? 

Thank you



-- 
--
Marc Franquesa
Lady 3Jane http://www.l3jane.net/
Warbaby





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1286747988.1632.24.ca...@warbaby.l3jane.net

udev problem? Testing system does not detect USB drive.

[Carl Fink]

My audio player (Coby MC941) acts as a USB-mounted hard drive.  Under Etch,
udev detected the drive when I plugged it in and identified it as /dev/sde.

Under testing, nothing.  Plug it in, no message in /var/log/messages.

I can still mount /dev/sde1 manually, bu of course that device is not
guaranteed to work in the future.  I thought udev was FIXED, not broken, but
everything since the original hotplug seems to gradually work worse.

Kernel 2.6.18-4-k7, udev 0.105-4.
-- 
Carl Fink   [EMAIL PROTECTED] 

Read my blog at nitpickingblog.blogspot.com.  Reviews!  Observations!
Stupid mistakes you can correct!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev problem

[L . V . Gandhi]

Thanks Florian, EackoJacko and Andrew for response
On 5/17/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
On Wed, May 17, 2006 at 07:23:20AM -0700, L.V.Gandhi wrote:> I am running sid> I have a rule in localrule as below.
> lvgdell600m:~# cat /etc/udev/rules.d/local.rules> BUS="scsi", SYSFS{model}="Cruzer Micro", KERNEL="sd?1", NAME="%k",> SYMLINK="flash"> Previoulsy it used to work to do automounting with autofs. it used to create
> /dev/flash. Now it fails to create. Further during boot also I get msg rule> is not correct. I get msg in syslog as below.I think there is a recent change to udev where it is a stickler about"=" (assignment) versus "==" (comparator). youmight check that out.
A-BEGIN PGP SIGNATURE-Version: GnuPG v1.4.3 (GNU/Linux)iD8DBQFEa4ytaIeIEqwil4YRAt7kAKCpYEFyqZGlBsHh36GwLqfAZaFByQCg5Hk8PU7gDXT01aNzEAXeVhXT4os==0bwK-END PGP SIGNATURE-
-- L.V.Gandhihttp://lvgandhi.tripod.com/linux user No.205042 

Re: udev problem

[Andrew Sackville-West]

On Wed, May 17, 2006 at 07:23:20AM -0700, L.V.Gandhi wrote:
> I am running sid
> I have a rule in localrule as below.
> lvgdell600m:~# cat /etc/udev/rules.d/local.rules
> BUS="scsi", SYSFS{model}="Cruzer Micro", KERNEL="sd?1", NAME="%k",
> SYMLINK="flash"
> Previoulsy it used to work to do automounting with autofs. it used to create
> /dev/flash. Now it fails to create. Further during boot also I get msg rule
> is not correct. I get msg in syslog as below.

I think there is a recent change to udev where it is a stickler about
"=" (assignment) versus "==" (comparator). youmight check that out.

A


signature.asc
Description: Digital signature

Re: udev problem

[Wackojacko]

L.V.Gandhi wrote:

I am running sid
I have a rule in localrule as below.
lvgdell600m:~# cat /etc/udev/rules.d/local.rules
BUS="scsi", SYSFS{model}="Cruzer Micro", KERNEL="sd?1", NAME="%k", 
SYMLINK="flash"


The new version of udev requires you to use '==' instead of '=' when 
looking at comparisons.  You will probably see errors on boot such as 
'invalid BUS command' relating to this rule.


HTH

Wackojacko


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev problem

[Florian Kulzer]

On Wed, May 17, 2006 at 07:23:20 -0700, L.V.Gandhi wrote:
> I am running sid
> I have a rule in localrule as below.
> lvgdell600m:~# cat /etc/udev/rules.d/local.rules
> BUS="scsi", SYSFS{model}="Cruzer Micro", KERNEL="sd?1", NAME="%k",
> SYMLINK="flash"
> Previoulsy it used to work to do automounting with autofs. it used to create
> /dev/flash. Now it fails to create. Further during boot also I get msg rule
> is not correct. I get msg in syslog as below.
> lvgdell600m:~# tail -n 30 /var/log/syslog

[ syslog messages relating to /dev/sda look OK ]

> May  7 18:04:00 localhost automount[6462]: >> mount: special device
> /dev/flash does not exist
> May  7 18:04:00 localhost automount[6462]: mount(generic): failed to mount
> /dev/flash (type vfat) on /var/autofs/removable/flash
> Is there any change to creating rules?
> What should be the rule for creating /dev/flash?

I think your rule should be

BUS=="scsi", SYSFS{model}=="Cruzer Micro", KERNEL=="sd?1", NAME=="%k", 
SYMLINK="flash"

The newest udev versions insist on a proper distinction between a
comparison ("==" operator) and an assignment ("="). 

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

udev problem

[L . V . Gandhi]

I am running sidI have a rule in localrule as below.lvgdell600m:~# cat /etc/udev/rules.d/local.rulesBUS="scsi", SYSFS{model}="Cruzer Micro", KERNEL="sd?1", NAME="%k", SYMLINK="flash"
Previoulsy it used to work to do automounting with
autofs. it used to create /dev/flash. Now it fails to create. Further
during boot also I get msg rule is not correct. I get msg in syslog as
below. lvgdell600m:~# tail -n 30 /var/log/syslog
May  7 18:03:35 localhost kernel: usb 4-1: new high speed USB device using ehci_hcd and address 4May  7 18:03:38 localhost kernel: SCSI subsystem initializedMay  7 18:03:38 localhost kernel: Initializing USB Mass Storage driver...
May  7 18:03:38 localhost kernel: scsi0 : SCSI emulation for USB Mass Storage devicesMay  7 18:03:38 localhost kernel: usbcore: registered new driver usb-storageMay  7 18:03:38 localhost kernel: USB Mass Storage support registered.
May  7 18:03:38 localhost kernel: usb-storage: device found at 4May  7 18:03:38 localhost kernel: usb-storage: waiting for device to settle before scanningMay  7 18:03:43 localhost kernel:   Vendor: SanDisk   Model: Cruzer Micro  Rev: 
0.2May  7 18:03:43 localhost kernel:   Type:   Direct-Access  ANSI SCSI revision: 02May  7 18:03:43 localhost kernel: usb-storage: device scan completeMay  7 18:03:44 localhost kernel: SCSI device sda: 1000944 512-byte hdwr sectors (512 MB)
May  7 18:03:44 localhost kernel: sda: Write Protect is offMay  7 18:03:44 localhost kernel: sda: Mode Sense: 03 00 00 00May  7 18:03:44 localhost kernel: sda: assuming drive cache: write throughMay  7 18:03:44 localhost kernel: SCSI device sda: 1000944 512-byte hdwr sectors (512 MB)
May  7 18:03:44 localhost kernel: sda: Write Protect is offMay  7 18:03:44 localhost kernel: sda: Mode Sense: 03 00 00 00May  7 18:03:44 localhost kernel: sda: assuming drive cache: write throughMay  7 18:03:44 localhost kernel:  sda: sda1
May  7 18:03:44 localhost kernel: sd 0:0:0:0: Attached scsi removable disk sdaMay  7 18:04:00 localhost automount[6462]: >> mount: special device /dev/flash does not existMay  7 18:04:00 localhost automount[6462]: mount(generic): failed to mount /dev/flash (type vfat) on /var/autofs/removable/flash
Is there any change to creating rules?What should be the rule for creating /dev/flash?-- L.V.Gandhihttp://lvgandhi.tripod.com/linux user No.205042

Re: Udev problem when rebooting....no filesystem found

[seeker5528]

On Thu, 27 Apr 2006 09:14:04 +0200
"miguel velasco" <[EMAIL PROTECTED]> wrote:

> Hi all! yesterday night I installed my Debian Etch widh KDE 3.5 at
> home and everything could be ok untill I rebooted my computer. At this
> moment in the boot process watched:
> 
> Waiting for root file system.. (hay se queda unos minutos)
> Aler! /dev/hda3 does not exist. Dropping to a shell !
> 
> Now I have limited console with no all commands and the next file
> system in my PC:
> $ df -h
> filesystemSize  UsedAvailableUse % Monted on
> udev379.0M  28.0K   378.9M  0%/dev

I don't know if it's the same thing happening to you, but I did
experience something similar to this.

In my case I was dropped in to a busybox shell and after some moments of
poking around and not figuring out anything else to do I exited the
shell and my system continued to boot and it never happened again after
that.

Later, Seeker


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Udev problem when rebooting....no filesystem found

[Jochen Schulz]

miguel velasco:
> 
> During the installation of th KDE 3.5 one packet named Udev was kept
> back and it didn?t upgradeI thought it was no important and now I
> suppose it was.

Sure it was. :) udev creates your device files under /dev, that is
probably why your root device wasn't found.

I guess you have to resort to some sort of rescue CD (Knoppix, etch
installer, grml...) and chroot into your installation to fix udev.

J.
-- 
In an ideal world I would cure poverty and go to the gym at least three
days a week.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: Udev problem

[Adam Hardy]

Frank Hart on 26/04/06 14:24, wrote:

On Thu, Apr 20, 2006 at 11:59:09AM +0100, Adam Hardy wrote:
I had a similar problem and solved it by doing a "apt-get --purge 
remove" followed by moving the old /etc/udev/ out of the way to 
/etc/udev.old/


Then I reinstalled the udev I needed and the problem sorted itself out.


Seems to me that you lost the udev rules other packages provide by 
removing /etc/udev and reinstalling.  This looks like a bug in alsa and 
libgphoto.  Recent udev force you to write correct rules (look in the 
changelog for "=" and "==").


Absolutely correct and with my configuration of packages, I had problems 
with sound and with the hardware sensors. I should have included that 
caveat.





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Udev problem when rebooting....no filesystem found

[miguel velasco]

Hi all! yesterday night I installed my Debian Etch widh KDE 3.5 at
home and everything could be ok untill I rebooted my computer. At this
moment in the boot process watched:

Waiting for root file system.. (hay se queda unos minutos)
Aler! /dev/hda3 does not exist. Dropping to a shell !

Now I have limited console with no all commands and the next file
system in my PC:
$ df -h
filesystemSize  UsedAvailableUse % Monted on
udev379.0M  28.0K   378.9M  0%/dev

During the installation of th KDE 3.5 one packet named Udev was kept
back and it didn´t upgradeI thought it was no important and now I
suppose it was.
The questions are: what is udev?  why my file system is /dev?  where
is /dev/hda3?

Thanks very much for ur time.
--
MIGUEL

Re: Udev problem

[Frank Hart]

On Thu, Apr 20, 2006 at 11:59:09AM +0100, Adam Hardy wrote:
> I had a similar problem and solved it by doing a "apt-get --purge 
> remove" followed by moving the old /etc/udev/ out of the way to 
> /etc/udev.old/
> 
> Then I reinstalled the udev I needed and the problem sorted itself out.

Seems to me that you lost the udev rules other packages provide by 
removing /etc/udev and reinstalling.  This looks like a bug in alsa and 
libgphoto.  Recent udev force you to write correct rules (look in the 
changelog for "=" and "==").

-- 
Frank Hart
gpg:FBB8E53A
jabber: [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Udev problem

[Wulfy]

Ross Boylan wrote:

On Wed, Apr 19, 2006 at 07:39:09PM +0100, Wulfy wrote:
  

I was updating my Sarge system using the backports.org repository.
Foolishly, I updated Udev...  which promptly told me it needed a later
kernel.  I downgraded back to the one I had before.

Now I'm getting problems from a couple of packages I installed at the
same time: libgphoto2 and alsa-utils (which sorta broke at the same time).

I'm getting the following lines in the log:

Apr 19 18:10:12 localhost udev[7046]: parse error 
/etc/udev/rules.d/025_libgphoto2.rules, line 3:13, rule skipped
Apr 19 18:10:12 localhost udev[7046]: parse error 
/etc/udev/rules.d/025_libgphoto2.rules, line 4:39, rule skipped
Apr 19 18:10:12 localhost udev[7046]: parse error 
/etc/udev/rules.d/025_libgphoto2.rules, line 933:28, rule skipped
Apr 19 18:10:12 localhost udev[7046]: parse error 
/etc/udev/rules.d/z60_alsa-utils.rules, line 1:38, rule skipped



I've attached the rules files.  As udev rules might as well be written 
in Klingon as far as I'm concerned, I'm hoping someone who understands 
this can help...



I've been struggling with udev too.  I think you've been caught by
its rapid changes.  More recent udevs depend on more recent
(post-stock Sarge) kernels and apparently implement features that the
older udev didn't.  I assume that the errors come from an older udev
trying to parse a file intended only for a newer udev.

Changing a package doesn't necessarily change the config files, which
are what are giving you problems.  If you can do a purge, not just
remove, of the affected packages and then reinstall them you'll
probably fix your problem.

Alternatively, you could plunge ahead into the exciting world of
testing, aka etch.  But if your goal is stability, reversion is
probably safer.

Others on the list may be able to contribute more elegant solutions.

Ross

Aye.  Thanks, Ross.

I'll wait a little to see if someone can come up with something, then if 
not, I'll purge alsa-utils and libgphoto2-2 and reinstall them at the 
lower version.


--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Udev problem

[Adam Hardy]

Ross Boylan on 20/04/06 05:35, wrote:
I've attached the rules files.  As udev rules might as well be written 
in Klingon as far as I'm concerned, I'm hoping someone who understands 
this can help...


I've been struggling with udev too.  I think you've been caught by
its rapid changes.  More recent udevs depend on more recent
(post-stock Sarge) kernels and apparently implement features that the
older udev didn't.  I assume that the errors come from an older udev
trying to parse a file intended only for a newer udev.

Changing a package doesn't necessarily change the config files, which
are what are giving you problems.  If you can do a purge, not just
remove, of the affected packages and then reinstall them you'll
probably fix your problem.


I had a similar problem and solved it by doing a "apt-get --purge 
remove" followed by moving the old /etc/udev/ out of the way to 
/etc/udev.old/


Then I reinstalled the udev I needed and the problem sorted itself out.


hth
Adam


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Udev problem

[Ross Boylan]

On Wed, Apr 19, 2006 at 07:39:09PM +0100, Wulfy wrote:
> I was updating my Sarge system using the backports.org repository.
> Foolishly, I updated Udev...  which promptly told me it needed a later
> kernel.  I downgraded back to the one I had before.
> 
> Now I'm getting problems from a couple of packages I installed at the
> same time: libgphoto2 and alsa-utils (which sorta broke at the same time).
> 
> I'm getting the following lines in the log:
> 
> Apr 19 18:10:12 localhost udev[7046]: parse error 
> /etc/udev/rules.d/025_libgphoto2.rules, line 3:13, rule skipped
> Apr 19 18:10:12 localhost udev[7046]: parse error 
> /etc/udev/rules.d/025_libgphoto2.rules, line 4:39, rule skipped
> Apr 19 18:10:12 localhost udev[7046]: parse error 
> /etc/udev/rules.d/025_libgphoto2.rules, line 933:28, rule skipped
> Apr 19 18:10:12 localhost udev[7046]: parse error 
> /etc/udev/rules.d/z60_alsa-utils.rules, line 1:38, rule skipped
> 
> 
> I've attached the rules files.  As udev rules might as well be written 
> in Klingon as far as I'm concerned, I'm hoping someone who understands 
> this can help...

I've been struggling with udev too.  I think you've been caught by
its rapid changes.  More recent udevs depend on more recent
(post-stock Sarge) kernels and apparently implement features that the
older udev didn't.  I assume that the errors come from an older udev
trying to parse a file intended only for a newer udev.

Changing a package doesn't necessarily change the config files, which
are what are giving you problems.  If you can do a purge, not just
remove, of the affected packages and then reinstall them you'll
probably fix your problem.

Alternatively, you could plunge ahead into the exciting world of
testing, aka etch.  But if your goal is stability, reversion is
probably safer.

Others on the list may be able to contribute more elegant solutions.

Ross


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev problem

[seeker5528]

On Sat, 18 Feb 2006 11:33:58 -0500
Jonathan Dill <[EMAIL PROTECTED]> wrote:

> On a second box, I thought I would get "smart" 
> and install yaird and remove initramfs before I switched from 2.4 to 2.6 
> kernel, but that didn't work somehow.

Typing 'man mkinitrd.yaird' shows:

To  let yaird build the initial boot image when a Debian kernel package
   is installed, rather than the default mkinitrd, put the
following  line in /etc/kernel-img.conf:

  ramdisk = /usr/sbin/mkinitrd.yaird

   Support  for  the ramdisk variable is built into the kernel
package; it is available in Debian kernels packaged since june 2005.

: worked for me. I had troubles getting the initrd image updated though
and finally ended up doing an 'apt-get install --reinstall' of my
kernel to get the job done.

Later, Seeker


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev problem

[Jonathan Dill]

Magnus Therning wrote:

Haven't found any cons. I removed the initramfs package to trigger
kernel upgrades to use yaird.

IME yaird produces MUCH smaller ramdisks.
  
The sequence in which you install / remove the packages seems 
significant, however.  On a second box, I thought I would get "smart" 
and install yaird and remove initramfs before I switched from 2.4 to 2.6 
kernel, but that didn't work somehow.  There were some dependent 
packages that didn't get installed, or some command that was missing.  
However, I rebooted to the new kernel with all the udev errors, then 
tried yaird again, and that fixed it.  If I try it on a third box, I'll 
report what the problem was exactly :)


Jonathan


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev problem

[Magnus Therning]

On Fri, Feb 17, 2006 at 06:01:03PM -0800, L.V.Gandhi wrote:
>On 2/17/06, John Schmidt <[EMAIL PROTECTED]> wrote:
>> On Thursday 16 February 2006 23:37, Deephay wrote:
>> > Hi all,
>> >
>> >   I have a problem with udev here: every time when I
>> > was booting the computer, the udev always show some lines
>> > like this on the console:
>> > "udevd_even: run program /.../.../ failed" (these lines
>> > goes a little bit fast and I cannot remember the exact
>> > format but it is more or less like this)
>> > but when I didn't find anything like this in the syslog,
>> > and seems it doesn't affect anything, so I only want to
>> > eliminate this, how can I do that? thx!
>> >
>> > Deephay
>>
>> There are a couple of options:
>>
>> 1.  install yaird and purge initramfs-tools and then do a:
>> dpkg-reconfigure linux-image-2.6.X
>>
>> 2.  Update to the latest udev (unstable) and do an update-intramfs -u -t
>> (don't do option 1) and reboot.
>
>What are the pros and cons using yaird in place of initramfs?

Haven't found any cons. I removed the initramfs package to trigger
kernel upgrades to use yaird.

IME yaird produces MUCH smaller ramdisks.

/M

-- 
Magnus Therning(OpenPGP: 0xAB4DFBA4)
[EMAIL PROTECTED]
http://therning.org/magnus

Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.

In order to understand recursion you must first understand recursion.


pgpcfdCyCmp3g.pgp
Description: PGP signature

Re: udev problem

[Ing. Vladimir M. Kerka]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

John Schmidt wrote:
> On Thursday 16 February 2006 23:37, Deephay wrote:
> 
>>Hi all,
>>
>>  I have a problem with udev here: every time when I
>>was booting the computer, the udev always show some lines
>>like this on the console:
>>"udevd_even: run program /.../.../ failed" (these lines
>>goes a little bit fast and I cannot remember the exact
>>format but it is more or less like this)
>>but when I didn't find anything like this in the syslog,
>>and seems it doesn't affect anything, so I only want to
>>eliminate this, how can I do that? thx!
>>
>>Deephay
> 
> 
> There are a couple of options:
> 
> 1.  install yaird and purge initramfs-tools and then do a:
>   dpkg-reconfigure linux-image-2.6.X
> 
> 2.  Update to the latest udev (unstable) and do an update-intramfs -u -t 
> (don't do option 1) and reboot.
> 
> John
Hi, John
many thanks for your help. I followed option 1 and everything now is OK.
HAND
Vlada
- --
Ing. Vladimir M. Kerka
Klukovicka 1530
155 00 Praha 5 - Stodulky
Czech Republic
e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
web:www.dinmont.cz

NOTE: rm -rf /bin/ladin
Nedostavam a nerozesilam viry, protoze nepouzivam M$ Windows

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD9vMEizaXOOTBYxcRAhEEAJoD4K/UKvyGgZ3RI/q76rQflKRAeQCgrfD2
u+kji3chozMzFL/9ylD1Oyo=
=hRZq
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev problem

[L . V . Gandhi]

On 2/17/06, John Schmidt <[EMAIL PROTECTED]> wrote:
> On Thursday 16 February 2006 23:37, Deephay wrote:
> > Hi all,
> >
> >   I have a problem with udev here: every time when I
> > was booting the computer, the udev always show some lines
> > like this on the console:
> > "udevd_even: run program /.../.../ failed" (these lines
> > goes a little bit fast and I cannot remember the exact
> > format but it is more or less like this)
> > but when I didn't find anything like this in the syslog,
> > and seems it doesn't affect anything, so I only want to
> > eliminate this, how can I do that? thx!
> >
> > Deephay
>
> There are a couple of options:
>
> 1.  install yaird and purge initramfs-tools and then do a:
> dpkg-reconfigure linux-image-2.6.X
>
> 2.  Update to the latest udev (unstable) and do an update-intramfs -u -t
> (don't do option 1) and reboot.

What are the pros and cons using yaird in place of initramfs?
--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042

Re: udev problem

[John Schmidt]

On Thursday 16 February 2006 23:37, Deephay wrote:
> Hi all,
>
>   I have a problem with udev here: every time when I
> was booting the computer, the udev always show some lines
> like this on the console:
> "udevd_even: run program /.../.../ failed" (these lines
> goes a little bit fast and I cannot remember the exact
> format but it is more or less like this)
> but when I didn't find anything like this in the syslog,
> and seems it doesn't affect anything, so I only want to
> eliminate this, how can I do that? thx!
>
> Deephay

There are a couple of options:

1.  install yaird and purge initramfs-tools and then do a:
dpkg-reconfigure linux-image-2.6.X

2.  Update to the latest udev (unstable) and do an update-intramfs -u -t 
(don't do option 1) and reboot.

John
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev problem

[L.V.Gandhi]

On 2/17/06, Deephay <[EMAIL PROTECTED]> wrote:
> Hi all,
>
>   I have a problem with udev here: every time when I
> was booting the computer, the udev always show some lines
> like this on the console:
> "udevd_even: run program /.../.../ failed" (these lines
> goes a little bit fast and I cannot remember the exact
> format but it is more or less like this)
> but when I didn't find anything like this in the syslog,
> and seems it doesn't affect anything, so I only want to
> eliminate this, how can I do that? thx!
I think you are using sid. You might have compiled kernel this week. I
think there was some problem. Compile now. It should not show. I also
experienced the same now. I don't have that problem now.

--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042

Re: udev problem

[Deephay]

thx :)

- Original Message - 
From: "Lubos Vrbka" <[EMAIL PROTECTED]>
To: "Deephay" <[EMAIL PROTECTED]>
Cc: "debian_user" 
Sent: Friday, February 17, 2006 3:14 PM
Subject: Re: udev problem


>>   I have a problem with udev here: every time when I
>> was booting the computer, the udev always show some lines
>> like this on the console:
>> "udevd_even: run program /.../.../ failed" (these lines 
>> goes a little bit fast and I cannot remember the exact 
>> format but it is more or less like this)
>> but when I didn't find anything like this in the syslog,
>> and seems it doesn't affect anything, so I only want to
>> eliminate this, how can I do that? thx!
> hi, this has been covered several days ago. search archives for 'udev 
> strangeness in sid'.
> regards,
> 
> -- 
> Lubos
> [EMAIL PROTECTED]"
> 
>

Re: udev problem

[Lubos Vrbka]

  I have a problem with udev here: every time when I
was booting the computer, the udev always show some lines
like this on the console:
"udevd_even: run program /.../.../ failed" (these lines 
goes a little bit fast and I cannot remember the exact 
format but it is more or less like this)

but when I didn't find anything like this in the syslog,
and seems it doesn't affect anything, so I only want to
eliminate this, how can I do that? thx!
hi, this has been covered several days ago. search archives for 'udev 
strangeness in sid'.

regards,

--
Lubos
[EMAIL PROTECTED]"


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

udev problem

[Deephay]

Hi all,

  I have a problem with udev here: every time when I
was booting the computer, the udev always show some lines
like this on the console:
"udevd_even: run program /.../.../ failed" (these lines 
goes a little bit fast and I cannot remember the exact 
format but it is more or less like this)
but when I didn't find anything like this in the syslog,
and seems it doesn't affect anything, so I only want to
eliminate this, how can I do that? thx!

Deephay

Re: udev(?) problem

[Henrik Christian Grove]

Hi 

I have a pcmcia GPRS-modem (Sony Ericsson GC75e).

On my old laptop which runs Debian Sarge with a homemade 2.6.13.3 kernel
and static /dev, it works fine (appears as /dev/ttyS2).

On my new laptop which also runs Debian Sarge, but with the standard
2.6.8-2-686 kernel and udev (I just did `apt-get install udev` - haven't
had the time to play with it yet), the status is:
- the card is detected (`cardctl ident` shows the same info as on my old
  laptop)
-  according to /var/log/syslog, /etc/pcmcia/serial is run with "start
  /dev/ttyS0" as parameters 
- /dev/ttyS0 is not a tty
  Here is (a simplified version of) the C-code I use:
fd=open("/dev/ttyS0", O_RDWR|O_NONBLOCK);
if ( ! isatty(fd) ) {
  printf("/dev/ttyS0 is not a tty\n");
  exit(2);
}

What have I done wrong (possibly not done at all)?

I'll prefer to stay close as close to Sarge as possible, except that
I'll probably end up compiling my own kernel anyway, and I know that
there are some issue with newer (Debian?) kernels and the version of
udev from Sarge, so I'll probably have to upgrade a few things.

.Henrik (who really needs a new english .signature - I graduaed almost 3
years ago)

-- 
Henrik Christian Grove
[EMAIL PROTECTED]
Student of Mathematics at the University of Copenhagen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

udev(?) problem

[Henrik Christian Grove]

Hi 

I have a pcmcia GPRS-modem (Sony Ericsson GC75e).

On my old laptop which runs Debian Sarge with a homemade 2.6.13.3 kernel
and static /dev, it works fine (appears as /dev/ttyS2).

On my new laptop which also runs Debian Sarge, but with the standard
2.6.8-2-686 kernel and udev (I just did `apt-get install udev` - haven't
had the time to play with it yet), the status is:
- the card is detected (`cardctl ident` shows the same info as on my old
  laptop)
-  according to /var/log/syslog, /etc/pcmcia/serial is run with "start
  /dev/ttyS0" as parameters 
- /dev/ttyS0 is not a tty
  Here is (a simplified version of) the C-code I use:
fd=open("/dev/ttyS0", O_RDWR|O_NONBLOCK);
if ( ! isatty(fd) ) {
  printf("/dev/ttyS0 is not a tty\n");
  exit(2);
}

What have I done wrong (possibly not done at all)?

I'll prefer to stay close as close to Sarge as possible, except that
I'll probably end up compiling my own kernel anyway, and I know that
there are some issue with newer (Debian?) kernels and the version of
udev from Sarge, so I'll probably have to upgrade a few things.

.Henrik (who really needs a new english .signature - I graduaed almost 3
years ago)

-- 
Henrik Christian Grove
[EMAIL PROTECTED]
Student of Mathematics at the University of Copenhagen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

/dev/hdc lost, udev problem?

[S guo]

I apologize, if I disturb anybody by repeating message.

I just found out that my problem might have something to do with udev, 
because I found the real device /dev/.static/dev/hdc. However, I can't 
understand why udev doesn't recognise my DVD/RW drive so that it would 
create the device, /dev/hdc, for me.


I would appreciate any hints and help!


From: "S guo" <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: RE: /dev/hdc lost
Date: Tue, 22 Nov 2005 11:15:04 +0100

Sorry, I forgot to mention, I'm using Debian sarge.
Could anyone help me?


From: "S guo" <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: /dev/hdc lost
Date: Mon, 21 Nov 2005 12:00:22 +0100

Hello, all,

I couldn't mount my DVD-drive today and found its device, /dev/hdc, 
simply disappeared. The computer has been running for a while and 
hadn't such problem before.


The computer has two SCSI harddisk, one holds SuSe OS, the other 
one holds Debian.

It has also one SCSI CD-ROM and one IDE DVD-rewriter.

From the file /var/log/messages, I could see that the DVE-rewriter 
was

recognised and assigned as hdc.

I can mount my DVD after I manually created a node for it using 
"mknod". However, the node I manually created disappears again 
after the reboot.


Has anyone idea to solve this problem permantly?

Thanks in advance!

Maron

_
与联机的朋友进行交流，请使用 MSN Messenger: 
http://messenger.msn.com/cn



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with 
a subject of "unsubscribe". Trouble? Contact 
[EMAIL PROTECTED]




_
享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a 
subject of "unsubscribe". Trouble? Contact 
[EMAIL PROTECTED]




_
与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn 



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian sid and udev problem.[SOLVED]

[Jon Jahren]

On Thursday 10 November 2005 11:49 pm, Justin Guerin wrote:
>
> ../hotplug.rules isn't a directory, it's a file that's supposed to be
> installed by udev.  It seems that udev version 0.056-3 doesn't contain that
> file, and 0.074-2 expects it to be there.  It may have been introduced by
> an intermediate version of udev, but the package doesn't account for you
> upgrading from a version where that file didn't exist.
>
> You should probably file a bug against the udev package.  Use the reportbug
> package; it will make things easy.
>
> For what it's worth, I just upgraded udev from 0.070 to 0.074-2, and I did
> not get that error.
>
> Hope that helps,
> Justin Guerin

I don't think I need to, I misiniterpreted the error messege, and it was the 
rules.d directory that was missing, which I had moved from a previous errror 
message to /root for testing. Moved the rules.d directory back, and 
everything worked fine. Sorry about that, it was entirely my mistake.

Jon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian sid and udev problem.

[mikepolniak]

On 20:24 Thu 10 Nov , Jon Jahren wrote:

>snip
> Preparing to replace udev 0.056-3 
> (using .../archives/udev_0.074-2_i386.deb) ...
> ln: creating symbolic link `/etc/udev/rules.d/z55_hotplug.rules' to 
> `../hotplug.rules': No such file or directory
> dpkg: error processing /var/cache/apt/archives/udev_0.074-2_i386.deb 
> (--unpack):
>  subprocess pre-installation script returned error exit status 1
> Errors were encountered while processing:
>  /var/cache/apt/archives/udev_0.074-2_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> 
> 
> As far as I can tell, it's failing at making a symlink to ../hotplug.rules in 
> the /etc/udev/rules directory, so I tried manually making the hotplug.rules 
> directory, which didn't work.

I just installed udev-0.74-2 and the link to hotplug.rules file is
created.

There is now a new file /etc/udev/hotplug.rules in addition to the
original /etc/udev/hotplugd.rules file.

I would d/l the udev_0.074-2_i386.deb again and try again. My udev*.deb is for
amd64 so maybe the i386.deb was corrupted.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian sid and udev problem.

[Justin Guerin]

On Thursday 10 November 2005 12:24, Jon Jahren wrote:
> Hello, I'm not sure where to ask this question, but this seemed as the
> more appropriate mailling list. 
You're in the right place.  Welcome.

> I have installed debian, and upgraded to 
> debian sid, and then I get this error with udev:
> debian:/home/jon# apt-get -f install
> Reading package lists... Done
> Building dependency tree... Done
> Correcting dependencies... Done
> The following extra packages will be installed:
>   udev
> The following packages will be upgraded:
>   udev
> 1 upgraded, 0 newly installed, 0 to remove and 178 not upgraded.
> Need to get 0B/300kB of archives.
> After unpacking 303kB of additional disk space will be used.
> Do you want to continue [Y/n]? y
> WARNING: The following packages cannot be authenticated!
>   udev
> Install these packages without verification [y/N]? y
> (Reading database ... 112823 files and directories currently installed.)
> Preparing to replace udev 0.056-3
> (using .../archives/udev_0.074-2_i386.deb) ...
> ln: creating symbolic link `/etc/udev/rules.d/z55_hotplug.rules' to
> `../hotplug.rules': No such file or directory
> dpkg: error processing /var/cache/apt/archives/udev_0.074-2_i386.deb
> (--unpack):
>  subprocess pre-installation script returned error exit status 1
> Errors were encountered while processing:
>  /var/cache/apt/archives/udev_0.074-2_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
>
> As far as I can tell, it's failing at making a symlink to
> ../hotplug.rules in the /etc/udev/rules directory, so I tried manually
> making the hotplug.rules directory, which didn't work.
> So, help please? I'm running kernel 2.6.14-1-686-smp and as you can see,
> I'm trying to install udev 0.074. If this is the wrong mailinglist I
> apologise and would like to know the appropriate mailinglist.
> Thanks in advance
> Jon

../hotplug.rules isn't a directory, it's a file that's supposed to be 
installed by udev.  It seems that udev version 0.056-3 doesn't contain that 
file, and 0.074-2 expects it to be there.  It may have been introduced by 
an intermediate version of udev, but the package doesn't account for you 
upgrading from a version where that file didn't exist.

You should probably file a bug against the udev package.  Use the reportbug 
package; it will make things easy.

For what it's worth, I just upgraded udev from 0.070 to 0.074-2, and I did 
not get that error.

Hope that helps,
Justin Guerin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Debian sid and udev problem.

[Jon Jahren]

Hello, I'm not sure where to ask this question, but this seemed as the more 
appropriate mailling list. I have installed debian, and upgraded to debian 
sid, and then I get this error with udev:
debian:/home/jon# apt-get -f install
Reading package lists... Done
Building dependency tree... Done
Correcting dependencies... Done
The following extra packages will be installed:
  udev
The following packages will be upgraded:
  udev
1 upgraded, 0 newly installed, 0 to remove and 178 not upgraded.
Need to get 0B/300kB of archives.
After unpacking 303kB of additional disk space will be used.
Do you want to continue [Y/n]? y
WARNING: The following packages cannot be authenticated!
  udev
Install these packages without verification [y/N]? y
(Reading database ... 112823 files and directories currently installed.)
Preparing to replace udev 0.056-3 
(using .../archives/udev_0.074-2_i386.deb) ...
ln: creating symbolic link `/etc/udev/rules.d/z55_hotplug.rules' to 
`../hotplug.rules': No such file or directory
dpkg: error processing /var/cache/apt/archives/udev_0.074-2_i386.deb 
(--unpack):
 subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/udev_0.074-2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



As far as I can tell, it's failing at making a symlink to ../hotplug.rules in 
the /etc/udev/rules directory, so I tried manually making the hotplug.rules 
directory, which didn't work.
So, help please? I'm running kernel 2.6.14-1-686-smp and as you can see, I'm 
trying to install udev 0.074. If this is the wrong mailinglist I apologise 
and would like to know the appropriate mailinglist.
Thanks in advance
Jon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]