Thread: Redhat 8 and Soundblaster Live!

  1. #16
    Registered User
    Join Date
    Jul 2002
    Posts
    913
    make sure your boot partition is mounted(if in doubt, just run 'mount /boot').

    now you copy your kernel over, so 'cp /usr/src/linux/arch/i386/boot/bzImage /boot'. now the kernel is in there but it wont boot, nothing is telling it too.

    so now you have to update your bootloader(either lilo or grub. i only know lilo). so you open up the config file(like /etc/lilo.conf or grub.conf), and add a new section folling the format. basicly the exact same thing with a different title and image(same root too).

    or just cheat and run 'make install' then you can test out your new kernel on next restart.

    <edit>
    more typos than usual.

  2. #17
    Pursuing knowledge confuted's Avatar
    Join Date
    Jun 2002
    Posts
    1,916
    Alright, I've copied bzImage to /boot, and now I'm logged in as root. This is what /etc/lilo.conf.anaconda contains
    Code:
    prompt
    timeout=50
    default=DOS
    boot=/dev/hda
    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    linear
    
    image=/boot/vmlinuz-2.4.18-14
    	label=linux
    	initrd=/boot/initrd-2.4.18-14.img
    	read-only
    	append="hdd=ide-scsi root=LABEL=/"
    
    other=/dev/hda1
    	optional
    	label=DOS
    I think I need to change the image line, but I don't know whta to change it to. The directory that I copied bzImage from was /usr/src/linux-2.4.20-18.8/i386/boot (I think you need that?)

    I really hope that I get the sound working when I'm done with this
    Away.

  3. #18
    Pursuing knowledge confuted's Avatar
    Join Date
    Jun 2002
    Posts
    1,916
    I looked a little closer, and I thought that this would work, so I changed it to this:
    Code:
    prompt
    timeout=50
    default=DOS
    boot=/dev/hda
    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    linear
    
    image=/boot/vmlinuz-2.4.20-18.8
    	label=linux
    	initrd=/boot/initrd-2.4.20-18.8.img
    	read-only
    	append="hdd=ide-scsi root=LABEL=/"
    
    other=/dev/hda1
    	optional
    	label=DOS
    If that doesn't work, I'll edit this post and say what happened.

    edit: It worked, but I got the following error message several times while everything was loading
    Warning: modutils is reading from /etc/modules.conf and ignoring /etc/conf.modules. The use of /etc/conf.modules is deprecated, please remove /etc/conf.modules as soon as possible. Command rm /etc/conf.modules
    Can I just type rm /etc/conf.modules, or will something break? Also, what do I do now to get the sound card to work? I'm going to try the OSS thing again.
    Last edited by confuted; 07-16-2003 at 02:06 PM.
    Away.

  4. #19
    Registered User
    Join Date
    Jul 2002
    Posts
    913
    you want lilo.conf, i have no idea what your file is. probally the installers copy or something.


    Code:
    image=/boot/vmlinuz-2.4.18-14
    	label=linux
    	initrd=/boot/initrd-2.4.18-14.img
    	read-only
    	append="hdd=ide-scsi root=LABEL=/"
    this is a normal 'block'. so you can copy and past it and just adjust,

    so image = will have to change to the bzImage you just copied(you might want to rename what you cp, but you dont have to).

    the "append" doesnt always work, the "LABEL" needs some dorky kernel option, so you should change your new kernel "block" to 'append="hdd=ide-scsi root=/"'

    so yours will look something like
    Code:
    prompt
    timeout=50
    default=DOS
    boot=/dev/hda
    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    linear
    
    image=/boot/vmlinuz-2.4.18-14
    	label=linux
    	initrd=/boot/initrd-2.4.18-14.img
    	read-only
    	append="hdd=ide-scsi root=LABEL=/"
    image=/boot/bzImage
    	label=linux-new
    	initrd=/boot/initrd-2.4.18-14.img
    	read-only
    	append="hdd=ide-scsi root=/"
    other=/dev/hda1
    	optional
    	label=DOS
    when your done with that you have to save the settings. instead of closing the file you need to rerun lilo, '/sbin/lilo'. that will update the bootsector/mbr.





    I really hope that I get the sound working when I'm done with this
    lol! nothing works the first time! but learning how to recompile a kernel is important.

    sound should just be a matter of playing with the oss install guide. i only gotten oss to work with my value under redhat, but people say you can get alsa to work with it. but they dont have value cards .

    its kind of annoying, im using gentoo with no sound i might go back to redhat just for xmms(linux winamp).
    Last edited by mart_man00; 07-16-2003 at 02:07 PM.

  5. #20
    Pursuing knowledge confuted's Avatar
    Join Date
    Jun 2002
    Posts
    1,916
    #1) See the edit on my last post.

    #2) I don't have a lilo.conf. Maybe what I did didn't work. Hmmm... here's grub.conf. How do I tell which file I need to modify?

    Code:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd1,1)
    #          kernel /vmlinuz-version ro root=/dev/hdb3
    #          initrd /initrd-version.img
    #boot=/dev/hda
    default=2
    timeout=10
    splashimage=(hd1,1)/grub/splash.xpm.gz
    title Red Hat Linux (2.4.20-18.8)
    	root (hd1,1)
    	kernel /vmlinuz-2.4.20-18.8 ro root=LABEL=/ hdd=ide-scsi
    	initrd /initrd-2.4.20-18.8.img
    title Red Hat Linux (2.4.18-14)
    	root (hd1,1)
    	kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ hdd=ide-scsi
    	initrd /initrd-2.4.18-14.img
    title DOS
    	rootnoverify (hd0,0)
    	chainloader +1
    Away.

  6. #21
    Registered User
    Join Date
    Jul 2002
    Posts
    913
    its basicly the same thing as with lilo

    looks like you did run make install, did you? if you did you can restart and give it a shot(grun doesnt need to be updated).

  7. #22
    Pursuing knowledge confuted's Avatar
    Join Date
    Jun 2002
    Posts
    1,916
    I did run make install, but I don't think that it worked. It had an error message. I think that the reason there are two entries for Linux there is because I downloaded the new kernel through the redhat network, which automatically updates everything. Should I try this?

    Code:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd1,1)
    #          kernel /vmlinuz-version ro root=/dev/hdb3
    #          initrd /initrd-version.img
    #boot=/dev/hda
    default=2
    timeout=10
    splashimage=(hd1,1)/grub/splash.xpm.gz
    title Red Hat Linux (recompiled)
    	root (hd1,1)
    	kernel /bzImage ro root=LABEL=/ hdd=ide-scsi
    	initrd /initrd-2.4.20-18.8.img
    title Red Hat Linux (2.4.20-18.8)
    	root (hd1,1)
    	kernel /vmlinuz-2.4.20-18.8 ro root=LABEL=/ hdd=ide-scsi
    	initrd /initrd-2.4.20-18.8.img
    title Red Hat Linux (2.4.18-14)
    	root (hd1,1)
    	kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ hdd=ide-scsi
    	initrd /initrd-2.4.18-14.img
    title DOS
    	rootnoverify (hd0,0)
    	chainloader +1
    That's basically a guess...

    Edit: Do I need to change the default= line to default=3 to have DOS be the default?
    Away.

  8. #23
    Registered User
    Join Date
    Jul 2002
    Posts
    913
    Edit: Do I need to change the default= line to default=3 to have DOS be the default?
    yes

    id try change the "root=LABEL=/ "s to "root=/ " and then give it a shot.

    they changed it alittle from what i used todo(like with the name "Red Hat Linux (recompiled)").

  9. #24
    Pursuing knowledge confuted's Avatar
    Join Date
    Jun 2002
    Posts
    1,916
    I did the title...

    Alright, I made the changes, time to try a reboot.
    Wish me luck

    edit: didn't work. I booted up to the older one again. This is what I have in grub.conf ATM
    Code:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd1,1)
    #          kernel /vmlinuz-version ro root=/dev/hdb3
    #          initrd /initrd-version.img
    #boot=/dev/hda
    default=3
    timeout=10
    splashimage=(hd1,1)/grub/splash.xpm.gz
    title Red Hat Linux (recompiled)
    	root (hd1,1)
    	kernel /bzImage ro root=/ hdd=ide-scsi
    	initrd /initrd-2.4.20-18.8.img
    title Red Hat Linux (2.4.20-18.8)
    	root (hd1,1)
    	kernel /vmlinuz-2.4.20-18.8 ro root=LABEL=/ hdd=ide-scsi
    	initrd /initrd-2.4.20-18.8.img
    title Red Hat Linux (2.4.18-14)
    	root (hd1,1)
    	kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ hdd=ide-scsi
    	initrd /initrd-2.4.18-14.img
    title DOS
    	rootnoverify (hd0,0)
    	chainloader +1
    Also, I'm still getting that error message that I mentioned earlier... can I type rm /etc/conf.modules or will it break something?
    Last edited by confuted; 07-16-2003 at 02:36 PM.
    Away.

  10. #25
    Registered User
    Join Date
    Jul 2002
    Posts
    913
    you have modules support in your kernel right? basicly everything in that category.

  11. #26
    Pursuing knowledge confuted's Avatar
    Join Date
    Jun 2002
    Posts
    1,916
    rm /etc/conf.modules worked okay and got rid of the warning messages, but I still didn't get the sound card to work. I tried the OSS installation some more, but it wouldn't work on the updated kernel from Redhat (2.4.20-18.8) and I haven't been able to boot to the one that I made. The installation worked on 2.4.18-14, and I configured everything... but the sound still didn't work.

    I want to kill it.

    Is there another distro of Linux/unix that I can get for free that will recognize this sound card and work *without* me hacking the crap out of the thing?
    Away.

  12. #27
    Registered User
    Join Date
    Jul 2002
    Posts
    913
    why cant you boot the new one? i though you did the kernel and the rm worked(id like to know how, maybe thats the old one..).

    if you want to compeletly chicken out madrake is the only thing easier, but its just redhat.

  13. #28
    Pursuing knowledge confuted's Avatar
    Join Date
    Jun 2002
    Posts
    1,916
    I can't boot the new one because I haven't figured out quite what to put in grub.conf for it. The last thing I posted about that didn't work - it hung after doing some bare initialization that I'm guessing doesn't depend on the kernel at all. I must need to change one or more of these lines
    Code:
    title Red Hat Linux (recompiled)
    	root (hd1,1)
    	kernel /bzImage ro root=/ hdd=ide-scsi
    	initrd /initrd-2.4.20-18.8.img
    Any ideas on that?

    From the error message
    Warning: modutils is reading from /etc/modules.conf and ignoring /etc/conf.modules. The use of /etc/conf.modules is deprecated, please remove /etc/conf.modules as soon as possible. Command rm /etc/conf.modules
    I would assume that what I rm-ed was old. rm said something about it being an empty file.
    Away.

  14. #29
    Registered User
    Join Date
    Jul 2002
    Posts
    913
    when you run make install it copies the bzImage into boot under a different name(like normal).

    so
    cd /boot
    ls

    and change the grun file to the new image(should be easy to find).

  15. #30
    Registered User
    Join Date
    Jul 2002
    Posts
    913
    News -- February 12, 2003

    The Dell CT0200 -- The new Live 5.1 card from Dell (CT0200) is not based on the EMU10K1 chip, so the EMU10K1 driver available at SourceForge won't work with it. Fortunately, 4Front Technologies (www.opensound.com) has developed a driver.
    --http://opensource.creative.com/

    i have a vaule card, but it is from dell. this could be a problem...

Popular pages Recent additions subscribe to a feed