Arch Linux

morgoth

Member

Registered: 2005-04-07

Posts: 21

Problems with udev

I have three things I have problems with. All which I can trace back to udev.

1. cdburning. K3b which I use works great with  udev-058-4
with the last udev-062-1 it give me the following and halts.

k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, plain-atapi, hacked-atapi
k3b: (K3bExternalBinManager) 2 1 -1  seems to be cdrecord version >= 1.11a02, using burnfree instead of burnproof
k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support for Just Link via burnfree driveroption
k3b: (K3bDevice::HalConnection) initializing HAL >= 0.5
k3b: (K3bDevice::HalConnection) unable to connect to DBUS.
k3b: /dev/hdd resolved to /dev/hdd
k3b: /dev/hdd is block device (64)
k3b: /dev/hdd seems to be cdrom
k3b: (K3bDevice::Device) /dev/hdd: init()
k3b: (K3bDevice::Device) /dev/hdd feature: CD Mastering
k3b: (K3bDevice::Device) /dev/hdd feature: CD Track At Once
k3b: (K3bDevice::Device) /dev/hdd feature: CD-RW Media Write Support
k3b: (K3bDevice::Device) /dev/hdd feature: DVD Read
k3b: (K3bDevice::Device) /dev/hdd feature: DVD+R
k3b: (K3bDevice::Device) /dev/hdd feature: DVD+RW
k3b: (K3bDevice::Device) /dev/hdd feature: DVD+R Double Layer
k3b: (K3bDevice::Device) /dev/hdd feature: DVD-R/-RW Write
k3b: (K3bDevice::Device) /dev/hdd feature: Rigid Restricted Overwrite
k3b: (K3bDevice::Device) /dev/hdd: dataLen: 60
k3b: (K3bDevice::Device) /dev/hdd: checking for TAO
k3b: (K3bDevice::Device) /dev/hdd: checking for SAO
k3b: (K3bDevice::Device) /dev/hdd: checking for SAO_R96P
k3b: (K3bDevice::Device) /dev/hdd: checking for SAO_R96R
k3b: (K3bDevice::Device) /dev/hdd: checking for RAW_R16
k3b: (K3bDevice::Device) /dev/hdd: checking for RAW_R96P
k3b: (K3bDevice::Device) /dev/hdd: checking for RAW_R96R
k3b: (K3bDevice::Device) /dev/hdd:  Number of supported write speeds via GET PERFORMANCE: 2
k3b: (K3bDevice::Device) /dev/hdd : 5540 KB/s
k3b: (K3bDevice::Device) /dev/hdd : 2770 KB/s
k3b: (K3bDevice::DeviceManager) setting current write speed of device /dev/hdd to 5540
k3b: /dev/hdc resolved to /dev/hdc

You may think why don't he just use that version then. Not so easy. Cause I also will play WoW, which don't work with udev-058-4, ognly create a dead prosess. But cedega works with udev-062-1.

Now I also have some flash based cards which I want to mount. The problem if I get any of the above to work I cant mount the usb/flash unit..

/etc/fstab

#<file system>  <mount point>                      <type>      <options>                   <dump>  <pass>
none            /dev/pts                           devpts      defaults                               0     0
proc            /proc                              proc        defaults                       0     0
none            /dev/shm                           tmpfs       defaults                               0     0
tmpfs           /tmp                               tmpfs       defaults                               0     0
usbfs           /proc/bus/usb                      usbfs       defaults                               0     0

/boot/grub/menu.lst

# (0) Arch Linux
title  Arch Linux  [/boot/vmlinuz26]
root   (hd1,1)
kernel /vmlinuz26 root=/dev/discs/disc3/part3 devfs=nomount ro vga=773

morgoth

Member

Registered: 2005-04-07

Posts: 21

Re: Problems with udev

Ok now for an update. I have found out that I kan both use cedega and K3b with the last udev release. I just have to  choose which I program I want to use, and I can only use it one time. After that I only get dead prosesses and have to reboot if I want to use it again.

 7192 ?        D      0:01 k3b

11402 pts/4    D      0:00 /home/someuser/.point2play/.winex_ver/winex-4.3.2/winex/bin/wine -- setValue -force

scarecrow

Member

From: Greece

Registered: 2004-11-18

Posts: 715

Re: Problems with udev

Latest k3b basically uses hal for assigning optical drives. Having hal running it works fine here:

k3b: (K3bDevice::HalConnection) initializing HAL >= 0.5

Actually I get some nonsensical errors like:

k3b: (K3bDevice::DeviceManager) scanning fstab: tmpfs
k3b: Could not resolve tmpfs
k3b: (K3bDevice::Device) Error: could not open device tmpfsfor reading
k3b: could not open device tmpfs (No such file or directory)
k3b: Could not resolve tmpfs
k3b: tmpfs resolved to tmpfs

... but after all that it does work fine.
Hope it helped.

---

Microshaft delenda est

morgoth

Member

Registered: 2005-04-07

Posts: 21

Re: Problems with udev

Worked fine at first, but then I got this:

k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, plain-atapi, hacked-atapi
k3b: (K3bExternalBinManager) 2 1 -1  seems to be cdrecord version >= 1.11a02, using burnfree instead of burnproof
k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support for Just Link via burnfree driveroption
k3b: (K3bDevice::HalConnection) initializing HAL >= 0.5
k3b: /dev/hdc resolved to /dev/hdc

and my dreaded

7856 pts/2    D      0:01 k3b

scarecrow

Member

From: Greece

Registered: 2004-11-18

Posts: 715

Re: Problems with udev

Maybe its something hardware related: Is you burner (/dev/hdd) slave to another IDE/Atapi device?
Burners actually like being masters, either in Linux or Windblows...

---

Microshaft delenda est

morgoth

Member

Registered: 2005-04-07

Posts: 21

Re: Problems with udev

Its slave to an dvd-rom. But I will change and try. The thing is that it hasn't been a problem before..

scarecrow

Member

From: Greece

Registered: 2004-11-18

Posts: 715

Re: Problems with udev

You'd better swap the drives, and use old, good 40-wire IDE ribbon and not 80-wire UDMA stuff.

---

Microshaft delenda est

elasticdog

Member

From: Washington, USA

Registered: 2005-05-02

Posts: 995

Website

Re: Problems with udev

You'd better swap the drives, and use old, good 40-wire IDE ribbon and not 80-wire UDMA stuff.

I disagree...there's absolutely no reason to use one of the old 40-wire IDE cables.  The 80-wire (40-pin) cable is the exact same thing connectivity wise, only with extra ground wires placed in between the signal wires to provide some protection against cross-talk, thus allowing more accurate data transmission.

ozar

Member

From: USA

Registered: 2005-02-18

Posts: 1,686

Re: Problems with udev

udev 064 was released yesterday, so upgrading to it might solve some issues... not sure when it might hit the Arch repo, though.

---

oz

scarecrow

Member

From: Greece

Registered: 2004-11-18

Posts: 715

Re: Problems with udev

The 80-wire (40-pin) cable is the exact same thing connectivity wise...

Then how come the 80-wire ones being directional and the master/slave plugs being explicit, while none of the above applies for 40-wire ribbons?

---

Microshaft delenda est

Offline

elasticdog

Member

From: Washington, USA

Registered: 2005-05-02

Posts: 995

Website

Re: Problems with udev

scarecrow...take a look here: Ultra DMA (80-Conductor) IDE/ATA Cables

p.s. Sorry for threadjacking...

morgoth

Member

Registered: 2005-04-07

Posts: 21

Re: Problems with udev

udev 064 was released yesterday, so upgrading to it might solve some issues... not sure when it might hit the Arch repo, though.

I've moved back to devfs, and what do you know everything works
I will have to try again with udev when it has aged a bit..

Snowman

Developer/Forum Fellow

From: Montreal, Canada

Registered: 2004-08-20

Posts: 5,212

Re: Problems with udev

You might not be aware, but this month, devfs support will be removed from the kernel.  You'll need to stick with the older kernel unless you can figure out how to make udev work. :?

morgoth

Member

Registered: 2005-04-07

Posts: 21

Re: Problems with udev

bastards