device registering at boot
 

Can anyone explain why there is a difference in how a device is registered at boot on the same machine between 2.6.17.13 from slack-11 and 2.6.21.5 from rc-1?

Note 2nd and 3rd to last closing lines from the two dmesg snippits below:

dmesg slack-11 2.6.17.13
<snip>
agpgart: Detected VIA KM400/KM400A chipset
agpgart: AGP aperture is 128M @ 0xd0000000
Linux video capture interface: v1.00
cx2388x dvb driver version 0.0.5 loaded
CORE cx88[0]: subsystem: 107d:665f, board: WinFast DTV1000-T [card=35,autodetected]
TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:0b.2[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
cx88[0]/2: found at 0000:00:0b.2, rev: 5, irq: 11, latency: 32, mmio: 0xe3000000
cx88[0]/2: cx2388x based dvb card
DVB: registering new adapter (cx88[0]).
DVB: registering frontend 0 (Conexant CX22702 DVB-T)...
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
<snip>

dmesg Current rc1 2.6.21.5:
<snip>
agpgart: Detected VIA KM400/KM400A chipset
agpgart: AGP aperture is 128M @ 0xd0000000
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
CORE cx88[0]: subsystem: 107d:665f, board: WinFast DTV1000-T [card=35,autodetected]
TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe
cx88[0]/2: cx2388x 8802 Driver Manager
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:0b.2[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
cx88[0]/2: found at 0000:00:0b.2, rev: 5, irq: 10, latency: 32, mmio: 0xe3000000
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
cx88[0]/0: found at 0000:00:0b.0, rev: 5, irq: 10, latency: 32, mmio: 0xe2000000
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
<snip>

Booting 2.6.17.13 the device is registered as a DVB device with adapter and frontend

Booting 2.6.21.5 the device is registered as video0 (v4l2) and vbi0

Is this a difference in kernel config/compile or something else?

I believe it has a bearing on whether udev will create the dvb devices required for viewing dvb.

TIA

yep its udev alright, if you have setup udev then there will be no change but if you left it to the defaults then the way hardware is detected and auto assigned has changed lots of times.
My CDROM and DVD change places every 6-8 months when I reboot for a new kernel, I can not be bothered to setup udev :(

Udev is supposed to create /dev/dvb/adapter0 and devices therein when a dvb device is detected.

In slack-10.1 I had to make up a udev rule and script to get dvb devices created by udev. No problem, it worked.

It worked off the shelf with slack-11 on three different boxes with pci dvb-t cards.

On those boxes the dmesg showed the device registered at boot as a dvb device.

With rc-1, on one of those same boxes, the the same dvb-t device is not being registered as dvb at boot.

I believe that is why udev is not working and I think the problem is the device not being registered as a dvb device.

Problem is I do not know why and googling so far has not given me the answer I need or a way to fix it