Hello,
I followed your discussion. I still have a problem. The workaround of Alan
works fine from a technical point of view using mkinitramfs. Now the hardware
is assigned to the right devices. But I have some commercial software that
(somehow) determines the "setup" of the computer. After the
Dear Alan, dear kernel & dvb hackers,
Am Sonntag, 20. Januar 2008 schrieb Alan Cox:
> > Well, it's a major pain in the a**. I've no idea, what reversed the
> > order of PCI devices, but I had to disable the automatic dvb driver
> > loading in order
>
> It depends on the order you load the modules
> Well, it's a major pain in the a**. I've no idea, what reversed the order of
> PCI devices, but I had to disable the automatic dvb driver loading in order
It depends on the order you load the modules
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body o
Am Samstag, 19. Januar 2008 schrieben Sie:
> I have a question concerning the ordering of devices during the boot
> process and I hope that the kernel mailing list is the right place for
> this question. In my computer are two raid controllers with one raid
> array connected to each of them (/dev/s
On Jan 19 2008 20:14, Oliver Pinter (Pintér Olivér) wrote:
>
>I don't know, what the proble, but the fstab workaround functioniert:
>form:
>/dev/sda3 / xfs defaults0 1
>to:
>UUID=7c167a53-30ff-4d47-a206-ce8caf2397ba / xfs
> defaults
I don't know, what the proble, but the fstab workaround functioniert:
form:
/dev/sda3 / xfs defaults0 1
to:
UUID=7c167a53-30ff-4d47-a206-ce8caf2397ba / xfs
defaults0 1
in this fix switched form device name to UUID based fsta
6 matches
Mail list logo
