Subject: Re: Problems installing on 6500/225; kernel modules
From: Trevor Marshall (trevor@risk2risk.com)
Date: Thu Aug 16 2001 - 16:20:30 MDT
Rich Frueh wrote:
>
> >Subject: Re: Problems installing on 6500/225; more info
> >From: Brian Watson (bcwatso1@uiuc.edu)
> >Date: Wed Aug 08 2001 - 18:14:45 MDT
>
> >I'm on a 6500/300 and I had the same problem with the network
> >configuration installer. So, I switched to the text installer. The
> >system out hang when I went to set the settings manually. However, I
> >seletected DHCP, and that worked fine. After the installation was
> >complete, I went back and changed my settings manually. However,
> >the blue background of netconfig stays even after I update the
> >settings, so I have to press return, logout, and log back in. I
> >haven't noticed any performance problems, as I matter of fact I'm
> >running my web server off of it now:
>
> Brian,
>
> Thanks for your information. Unfortunately, I'm still stuck. I cannot ever
> get my ethernet card to activate. If I look at my router, it never gets a
> link from the card.
>
> Here's what I have done:
>
> First, I went to Farallon's web page to find out if they knew how to get the
> card working under Linux. Of course, they don't support it, but they do say
> it uses the DEC 21143 chipset, and that the TULIP driver under OSX will
> work. Tried to fidn where to tell YellowDog to use a TULIP driver. No
> dice.
>
> Erased the HD< installed LinuxPPC. This actually did fire up the ethernet
> card during install, and it took an address. Rebooted, no link light, no
> network. Fine, go in and try to figure out what I need to do to get my
> machine to see its ethernet card.
>
> Still no dice.
>
> Reformatted again, decided to give YDL a try again, now that I know which
> driver it is, and have done some reading on kernel arguments in Intel Linux
> (RedHat). Give the kernel an "ether=tulip" argument. Nothing. Say "ah,
> the hell with it" and skip the network stuff etnirely, and install the rest
> of YDL again, then try and play. Unfortunately, I can't find a guide beyond
> the base installation guide, so I'm wondering if a RedHat book would help.
> Look through the KDE menus and find 'kernelcfg'. Aha. Run that. Put in
> eth0 as a tulip device. Now what? Do I need to relink the kernel? Do
> something else entirely?
Rich -
Can you ping 127.0.0.1? if so you are on the wrong track. could it be
the network cable? Probably not though if you get module errors..
I would definitely recommend online redhat or linux doc project (LDP)
docs; books can be waste of money for more complicated issues. it
doesn't matter at all in this case if you are running yellowdog.
do google searches on the errors you see
have you checked your logs in /var/log? these are your best friend.
try man page for insmod
the tulip module should be there; try "insmod
/lib/modules/2.x.xx/net/tulip.o"
check the LDP for a modules or network card howto; something will be
there.
if that fails i'd try reconfiguring and recompiling the kernel. it's
fun. here are some steps but you should have the kernel howto from the
LDP handy. to do this _backup_ the source directory in /usr/src (cp -R
/usr/src/linux-xx /usr/src/linux-xx.bak) then cd to it and type as root:
make menuconfig
- this will bring up the current kernel config. don't touch what you
don't understand. there is help for most options. just go to the network
interface list to the 10/100 ethernet and put a star beside the decchip
tulip, instead of an M. this will put it right into the kernel so no
more module worries.
save and exit
make dep
make bzImage
make modules
make modules_install
then copy /usr/src/linux/arch/i386/boot/bzImage to /boot/somename and
relink vmlinux to it (ln -s somename vmlinux). you would normally keep
the old kernel available so you can still boot if the new kernel's
effed; this means updating the bootloader but I'm a lilo guy so i can't
help you there. no biggie if you can still reinstall.
reboot with fingers crossed. if nothing then boot off rescue cd and
relink vmlinux to the old kernel and reboot, or just choose the old one
if you configured the bootloader properly like you should.
no guaranties of course but this is what i'd do in redhat. i've only
used yellowdog for 2 days, but i love my mac again.
any problems email ...
cheers,
-TRevor
>
> I do really want to use Linux on this box, and to do that it ahs to have
> networking. Any help?
>
> Also, do the instructions for enabling sound for 1.2 apply for 2.0? Because
> I can't get sound to work, and every time it boots I get an error about a
> dependency module not being found.
>
> Thanks,
>
> Rich Frueh
> Frustrated Linux Wannabeauser
>
> _______________________________________________________
> Send a cool gift with your E-Card
> http://www.bluemountain.com/giftcenter/
This archive was generated by hypermail 2a24 : Thu Aug 16 2001 - 15:27:55 MDT