| |
| |
| |
|
Page: 1 2 3 4
Comments:
<0> < > OSS PCM (digital audio) API ? ?
<0> ? ? [ ] OSS Sequencer API ? ?
<0> ? ? <M> RTC Timer support
<1> yup extraversion is great for seperating same version kernels with differing options
<2> (patches)
<0> it already had M in it
<0> do i mark the oss
<0> but i use alsa
<1> up too you, I only use oss because I know it works
<1> varies from chipset too chipset whether you use alsa or oss
<0> gb>for sound card support i have option in menuconfig to M or Y feature
<0> they both work
<0> <*> Sound card support
<0> or <M> Sound card support
<1> no should all be m
<0> ok
<1> unless it breaks as modules in which case try building it into the kernel
<1> only build things into kernel that is essential for mounting /
<1> that way you optimise your memory usage
<0> isa devices------->
<0> im in now
<1> you dont want things as modules that will remain loaded the whole time init runs
<0> ok
<1> otherwise you have driver + module framework sitting in swap/ram when it needn't have the framework there at all
<0> ok
<1> things like sound will get unloaded when not in use freeing memory/swap
<0> thats kool
<1> unless you use something crappy like artsd :)
<1> but if sound is still broken after this build try selecting it with a y
<1> I find building half as modules/other half in kernel will often break it though
<1> which is what you seem too have done this build
<0> compiling now man
<0> root@FisHsTiX:/usr/src/linux-2.6.15.1# make dep;make bzImage;make modules;make modules_install
<0> *** Warning: make dep is unnecessary now.
<0> CHK include/linux/version.h
<0> SPLIT include/linux/autoconf.h -> include/config/*
<0> CHK include/linux/compile.h
<0> CHK usr/initramfs_list
<0> LD sound/core/seq/oss/built-in.o
<0> Kernel: arch/i386/boot/bzImage is ready (#1)
<0> CHK include/linux/version.h
<0> looks ok
<0> brb
<0> gb>got same /dev/dsp error
<0> so im compiling it again, with fewothe roptions :)
<0> few other*
<0> bbs
<0> :) all workin g now sound
<1> hehe
<1> having funI hope :)
<0> yeah, nice as
<0> this kernel seems quicker than my 2.4.31
<0> u think?
<1> dont kill my init now I sneaked in :)
<1> I'm running it as root onmost people systems :)
<1> ps auxw|grep init
<0> ok
<1> should have started when you rebooted
<1> you cant kill it though
<1> or I'll crash your computer :)
<0> so your connected to my pc
<0> lol
<1> nonot connected just infectedx :)
<0> how u do that
<1> hehehe
<1> if I told you I'd have too shoot you
<0> whats it like ivebeen rooted
<0> should i run a rootkit
<1> sure download a viruscannuh frommcafee
<0> heh, im onlinux
<0> run rkhunter
<0> or something
<1> brtjohns: you think linux is more secure then messydos in the hands of a newbie?
<0> no
<0> be worse
<1> not really
<3> sup _RADIOhead
<4> morning
<3> sup
<4> how to send basic stamp program to basic stamp chips?
<4> the Tokenizer don't recognize my basic stamp
<1> uhuh
<5> oooooooooo neil_m
<5> gb dude
<3> sup dude
<5> neil_m, was out
<5> installing some LAN cables damn :(
<5> going again out , i need food
<3> haha
<3> yeh me too :D
<6> I compiled a new kernel (in fact, the first one in my life) with bootsplash support, but when I try to boot it, it stops with the message: "kernel panic: not syncing: VFS: unable to mount root fs on unknown-block(0,0)".. kernel 2.6.15.1
<6> what does this mean and how can I fix it?
<4> ronove: u forget some modules
<7> hi there
<4> filesystem and meaby chips modules
<7> would somebody be kind enough to explain why misc_register et al might return -EBUSY? I can't make sense of it from the source
<4> the file system module must be build to the kernel
<6> paistis: how do I get it in there?
<4> compiled again
<6> yeah, but where do I find that module in menuconfig?
<4> filesystem -> and device -> ata/atapi
<6> I'm using sata disks, anything special I have to do to get them working?
<4> u need put the sata drivers
<4> i don't remember where those are
<7> i thought that was a long shot... oh well
<8> hi all
<6> paistis: "Support for SATA (deprecated; conflicts with libata SATA driver) " so probably I have to find those drivers
<6> but I don't find them..
<6> would it be safe to just check the 'SATA support'?
<8> it's in the scsi section!
<4> yes
<6> meh, they're "checked"
<4> on build mod?
<6> on build mod??
<4> not M
<4> *
<6> ow, they're all M
<4> thos must be *
<6> so I have to press Y on all of them? =/
<6> can't I just do sth like 'make modules' ?
<4> no
<4> configure
<4> and run make && make modules_install
<6> but I can't get them to be [*] instead of <M> =/
<6> This feature depends on another which has been configured as a module. As a result, this feature will be built as a module.
<4> 3 choice
<4> look outs those others modules and put them to buid
<4> or make initri image
<4> or put thoste y on .config file
<6> last one = simplest to do?
<4> no
<4> make initri
<4> but i'm not sure if thats conna help
<6> how would I do that?
<4> mkinitrd /boot/img-2.6.15.1 2.6.15.1
<4> mkinitrd -o /boot/img-2.6.15.1 2.6.15.1
<6> I did the same, but using yaird, since I couldn't find mkinitrd on debian
<4> u mis some package if there is no mkinitrd
<6> ah.. hm.. this starts pissing me off..
<4> :/
<4> just put thoes y on .config file
<4> and recompiled it
<4> it could help
<9> re
<10> hey guys... what would be the easiest way to write user-space (virtual) block device driver?
<11> If I make a program that uses tcsetattr and other stuff that manipulates the /dev/ttyS*, am I likely to encounter problems if I run the binary on different versions of the 2.4 kernel? e.g. 2.4.1 and 2.4.32
<12> where is the code which locks the cdrom on mount?
<13> qknight
<13> i would like to know also
Return to
#kernel
or
Go to some related
logs:
#kde
ipw3945 kernel panic
ubuntu kmud
#css
solaris10 malloc segv
yum install mplayer Metadata file does not match checksum
#bash
how to change a file system from ntfs to ext3 in ubuntu
muine importerror gstreamer
Error inserting scsi_transport_spi
|
|