hm, that's the odd thing, then - because i *am* modprobing the sound
driver at boot time, and i haven't unloaded it before these problems
start! which makes it seem like i have 2.2 behaviour with a 2.0 module,
only the dmabuf commandline option isn't available. ;)
hm, might the awedrv patch have something to do with it? or perhaps i
should try just doing away with the module altogether and compile sound
support directly into the kernel? could that make a difference somehow?
i apologise if this thread has gone on long enough. i'd like to move up
to 2.2 anyway, but as i said before have had some problems. perhaps i'll
outline these in another post in hopes that some kind soul will take pity
on me and guide me towards some solutions... (first i'll try the latest ac
patch though)
-damon
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/