Operating Systems > Linux and UNIX

How do i sort out my kernel/system?

<< < (3/5) > >>

flap:
did it work before? did you do something to break it?

Calum:
i installed the driver for my SiS7018 sound card that i got from www.sis.com (which now i look has gone offline...) reason being that SiS hardware is full of bugs and i cannot use Slab until i 'get a better driver for my sound card'. So i dutifully went to the manufacturer's site and got the newest driver for linux and hey presto, not only does Slab still not work, but this happens.

voidmain:
I remember the old SIS days. They *do* have crap drivers. I had a hell of a time with an SIS based motherboard under Windows and drivers from the SIS web site. I quit buying anything that says "SIS Inside".

Is that boot log from a new kernel that you have compiled? If you recompiled the same version that the system came with and installed the modules they could have been installed in the same directory under /lib/modules/[kernelversion]/* as the old kernel. If there are modules in there from the previous kernel then you would likely get modules loading problems. Another thing that I always run after booting up a new kernel is a "depmod -a".

LorKorub:
Calum, it always seems that you and I are floating in the same boat.  I just recompiled my kernel tonight, and found this page to be really helpful:

http://dudle.linuxroot.org/docs/debian-install/debian-install-4.html

I had to do it twice, and here's why.

Forget about section 4.2. I did what he suggested, and make could no longer find /bin/sh.  Totally fucked me. So, I whipped out the trusty boot-floppy (always make one of these....those guys weren't lying during the install when they say it is IMPERATIVE that you make a boot floppy), and got back into 2.2.2. I had to run taskel again to load up X, wait for a (re)install, and then I was good to go.  

To tell you the truth, I don't know what happened.  I would just skip 4.2 and follow the rest of the instructions. I have sound now, so I am happy (I apparently didn't include sound modules when I loaded the 2.2.2 kernel when I installed Debian.)

Hope it works out for you....

Calum:

quote:Originally posted by void main:
I remember the old SIS days. They *do* have crap drivers. I had a hell of a time with an SIS based motherboard under Windows and drivers from the SIS web site. I quit buying anything that says "SIS Inside".
--- End quote ---
i have seen more problems on bulletin boards for SiS stuff than anybody else, but it's in my machine now so tough nuts to me.

 
quote:Is that boot log from a new kernel that you have compiled? If you recompiled the same version that the system came with and installed the modules they could have been installed in the same directory under /lib/modules/[kernelversion]/* as the old kernel. If there are modules in there from the previous kernel then you would likely get modules loading problems. Another thing that I always run after booting up a new kernel is a "depmod -a".
--- End quote ---
No it's not as far as i know. The installation process for the SiS audio driver requires a reboot after you install it, which is something i haven't had to do since... well since i installed the SiS7018 driver for DOS! there was no message about why it was to be rebooted, you just run the install script and then a minute later it tells you 'please reboot your computer to complete installation'. Dodgy.

LorKorub, thanks as well, i will look into that, but the sound card worked fine before in everything but SLab. It is a recording suite and it won't apparently record further than 8 frames if you have a buggy sound driver, according to the developer, but i have tried the mandrake driver for this card and the SiS driver too, and neither work for that application. I suspect it is the card's fault. The kernel recompilation is now my main concern.

Navigation

[0] Message Index

[#] Next page

[*] Previous page