Tom St Denis wrote:
This won't be fixed as part of 2.6.18.x?
Probably not.
So why is it detected and
working there but not in 2.6.18?
It wasn't detected under 2.6.17. Either your kernel is modified, or you
were using the vendor sk98lin driver or something like that. If you have
2.6.17 still bootable you could boot it and check the dmesg output to
make sense of things.
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]