Re: OSS SBLive driver causes kernel panic with 5.0 current

2003-03-20 Thread Jody Franklin
David Schultz wrote:
Thus spake Andre Guibert de Bruet [EMAIL PROTECTED]:

On Fri, 7 Mar 2003, Jody Franklin wrote:


I'd been keeping up with current (world/kernel) every other week or so,
and until this week I had no real problems. But after the build I did on
March 3rd my soundcard driver (4Front's SBLive/Audigy driver) causes a
kernel panic on load. If I don't load the driver the system boots fine,
and runs with no other problems.
This is the message I get from the debugger when I load the driver:

panic: Invalid major (-1030904368) in make_dev

I've posted this info to their support forums also, their last responce
was to see what they broke.
Please don't cross-post -current and -questions.

Major numbers are now being allocated dynamically. Sounds like the emu10k1
driver doesn't like this. My guess is, it's probably in the process of
being converted over...


His post refers to the commercial driver, which still needs to be
converted.


As of the 12th 4Front's last word was that they are using 
/usr/share/examples/cdev as an example for their code, and that example 
causes the same panic as their driver. Thus asking that the examples be 
updated to match the current kernel so that they can update their driver.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


OSS SBLive driver causes kernel panic with 5.0 current

2003-03-07 Thread Jody Franklin
I'd been keeping up with current (world/kernel) every other week or so,
and until this week I had no real problems. But after the build I did on
March 3rd my soundcard driver (4Front's SBLive/Audigy driver) causes a
kernel panic on load. If I don't load the driver the system boots fine,
and runs with no other problems.
This is the message I get from the debugger when I load the driver:

panic: Invalid major (-1030904368) in make_dev

I've posted this info to their support forums also, their last responce
was to see what they broke.
Jody





To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message