Świeża instalacja i problem z udev

[Fryderyk Dziarmagowski]

On Mon, 14 Sep 2009 11:07:35 +0200
Paweł Muszynski <pmuch w zamek.szczecin.pl> wrote:

> Instaluję właśnie nowe PLD (TH+ready) x86_64.
> W komputerze jest karta sieciowa na tg3, udev-146-1.x86_64 (konfiguracja 
> z paczki).
> 
> Ale po restarcie karta się nie podnosi, zaś po ręcznym dodaniu modułu 
> tg3 - bez problemu wstaje.
> udevadm test /sys/class/net/eth0 daje następujący wynik (po 
> doinstalowaniu hwdata - może to powinno być suggeseted przez udev ?)

udev nie potrzebuje hwdata. potrzebne są pciutils/usbutils.

> run_command: calling: test
> udevadm_test: version 146
> This program is for debugging only, it does not run any program,
> specified by a RUN key. It may show incorrect results, because
> some values may be different, or not available at a simulation run.
> 
> parse_file: reading '/etc/udev/rules.d/40-alsa-restore.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/40-alsa.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/40-pilot-links.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/40-zaptel.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/50-firmware.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/50-udev-default.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/60-cdrom_id.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/60-persistent-alsa.rules' as 
> rules file
> parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as 
> rules file
> parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as 
> rules file
> parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules' 
> as rules file
> parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as 
> rules file
> parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules 
> file
> parse_file: reading '/lib/udev/rules.d/61-mobile-action.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/61-option-modem-modeswitch.rules' 
> as rules file
> parse_file: reading '/lib/udev/rules.d/61-persistent-storage-edd.rules' 
> as rules file
> parse_file: reading '/etc/udev/rules.d/64-device-mapper.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/70-acl.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/70-hid2hci.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/70-udev-pld.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as 
> rules file
> parse_file: reading '/lib/udev/rules.d/75-net-description.rules' as 
> rules file
> parse_file: reading '/lib/udev/rules.d/75-tty-description.rules' as 
> rules file
> parse_file: reading '/lib/udev/rules.d/78-sound-card.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/79-fstab_import.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/80-drivers.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/95-keymap.rules' as rules file
> parse_file: reading '/lib/udev/rules.d/95-udev-late.rules' as rules file
> udev_rules_new: rules use 21012 bytes tokens (1751 * 12 bytes), 11837 
> bytes buffer
> udev_rules_new: temporary index used 13160 bytes (658 * 20 bytes)
> udev_device_new_from_syspath: device 0x62fb10 has devpath 
> '/devices/pci0000:00/0000:00:1c.5/0000:0e:00.0/net/eth0'
> udev_device_new_from_syspath: device 0x6379a0 has devpath 
> '/devices/pci0000:00/0000:00:1c.5/0000:0e:00.0'
> udev_device_new_from_syspath: device 0x637d00 has devpath 
> '/devices/pci0000:00/0000:00:1c.5'
> udev_device_new_from_syspath: device 0x625120 has devpath 
> '/devices/pci0000:00'
> udev_rules_apply_to_event: IMPORT 'pci-db 
> /devices/pci0000:00/0000:00:1c.5/0000:0e:00.0/net/eth0' 
> /lib/udev/rules.d/75-net-description.rules:11
> util_run_program: 'pci-db 
> /devices/pci0000:00/0000:00:1c.5/0000:0e:00.0/net/eth0' started
> util_run_program: '/lib/udev/pci-db' (stderr) 'libudev: 
> udev_device_new_from_syspath: device 0x6092c0 has devpath 
> '//devices/pci0000:00/0000:00:1c.5/0000:0e:00.0/net/eth0''
> util_run_program: '/lib/udev/pci-db' (stderr) 'libudev: 
> udev_device_new_from_syspath: device 0x609630 has devpath 
> '//devices/pci0000:00/0000:00:1c.5/0000:0e:00.0/net''
> util_run_program: '/lib/udev/pci-db' (stderr) 'libudev: 
> udev_device_new_from_syspath: device 0x6098a0 has devpath 
> '//devices/pci0000:00/0000:00:1c.5/0000:0e:00.0''
> util_run_program: 'pci-db 
> /devices/pci0000:00/0000:00:1c.5/0000:0e:00.0/net/eth0' returned with 
> exitcode 0
> udevadm_test: UDEV_LOG=6
> udevadm_test: DEVPATH=/devices/pci0000:00/0000:00:1c.5/0000:0e:00.0/net/eth0
> udevadm_test: INTERFACE=eth0
> udevadm_test: IFINDEX=2
> udevadm_test: ACTION=add
> udevadm_test: SUBSYSTEM=net
> udevadm_test: ID_BUS=pci
> udevadm_test: ID_VENDOR_ID=0x14e4
> udevadm_test: ID_MODEL_ID=0x165a

tu żadnych pożytecznych informacji nie ma. potrzebny jest log w
momencie jak udevadm trigger błądzi po /sys

> 
> No i nie mam pomysłu, co z tym zrobić.

na początek możesz spróbować:
udevadm trigger --verbose --type=failed

-- 
freetz