View previous topic :: View next topic |
Author |
Message |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
|
Back to top |
|
 |
xPAGANx Tux's lil' helper


Joined: 08 Oct 2003 Posts: 93 Location: Warren, Michigan
|
Posted: Fri Oct 17, 2003 4:30 pm Post subject: |
|
|
Try this:
emerge fam-oss
emerge libart-lgpl
env-update && source /etc/profile
Lemme know if it works out
xPAGANx |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Fri Oct 17, 2003 7:24 pm Post subject: |
|
|
i'm sorry, but i think the problem with my NIC has to be solved first...
the error here was that Gentoo detected it during install, but after installation, t failed to load on startup
see config files above for more information |
|
Back to top |
|
 |
xPAGANx Tux's lil' helper


Joined: 08 Oct 2003 Posts: 93 Location: Warren, Michigan
|
Posted: Fri Oct 17, 2003 7:50 pm Post subject: |
|
|
make sure you module is loaded in
/etc/modules.autoload.d/kernel-2.x
or you could try rebuilding your kernel with the driver built in instead of the module.
does the system fail to see the NIC or is it not configured right?
xPAGANx |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Sat Oct 18, 2003 9:31 am Post subject: |
|
|
i checked my configuration and i've already set a * by the two chips of my network card ("Ethernet(10 or 100Mbit)" -> "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support" and "RealTek RTL-8139 PCI Fast Ethernet Adapter support")
here's my /etc/modules.autoload.d/kernel-2.5 file
i've set the two options in it (8139 and 8139+ [i'm not sure if they're right, but i seem to remember something about it during install] ) but after reboot Gentoo still "failes to load" when "bringing op eth0"
do i have to do something special or so [n00bish question]? |
|
Back to top |
|
 |
xPAGANx Tux's lil' helper


Joined: 08 Oct 2003 Posts: 93 Location: Warren, Michigan
|
Posted: Sat Oct 18, 2003 4:48 pm Post subject: |
|
|
Ok if you set the * by the NIC in your kernel when you first configured it then it should be built into the kernel. You shouldn't need to load any modules at startup.
If it is built into your kernel as you say try typing: "dhcpd eth0" at the bash prompt and then try "ping www.google.com" and hit control-c after a few seconds...
see iff that lets you connect to the internet.
The above assumes you are using dhcp.. If your not your gonna have to mod a configuration file.. Let me know what you need and I can try to help ya.
xPAGANx |
|
Back to top |
|
 |
Decibels Veteran


Joined: 16 Aug 2002 Posts: 1631 Location: U.S.A.
|
Posted: Sun Oct 19, 2003 1:08 am Post subject: |
|
|
I don't see you mentioning that you are using masqurade or a router so why is your /etc/conf.d/net file set for dhcp on eth0 and you give it a static ip for a lan. Looks like you have a conflict.
Code: | iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
#iface_eth1="207.170.82.202 broadcast 207.0.255.255 netmask 255.255.0.0"
# For DHCP set iface_eth? to "dhcp"
# For passing options to dhcpcd use dhcpcd_eth?
#
iface_eth0="dhcp"
#dhcpcd_eth0="..." |
if that is the case and eth0 is connected to the ISP then try:
Code: | #iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
#iface_eth1="207.170.82.202 broadcast 207.0.255.255 netmask 255.255.0.0"
# For DHCP set iface_eth? to "dhcp"
# For passing options to dhcpcd use dhcpcd_eth?
#
iface_eth0="dhcp"
#dhcpcd_eth0="..." |
_________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Sun Oct 19, 2003 5:40 pm Post subject: |
|
|
You're right: it is contradict;
i'm on a network with a router so my settings are, just like in Windows, dhcp.
I've updated my /etc/conf.d/net file but the error still exists.
Precise description:
Bringing up interface eth0...
Failed to bring eth0 up [!!]
ERROR: Problem starting needed services.
"netmount" was not started.
Last edited by k:arel on Sun Oct 19, 2003 6:47 pm; edited 1 time in total |
|
Back to top |
|
 |
Decibels Veteran


Joined: 16 Aug 2002 Posts: 1631 Location: U.S.A.
|
Posted: Sun Oct 19, 2003 5:51 pm Post subject: |
|
|
Add netmount to your default initscript:
rc-update add netmount default _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Sun Oct 19, 2003 6:46 pm Post subject: |
|
|
but isn't because my NIC is not found, netmount is unable to start?
anyway, i tried rc-update add netmount default and it said it was already my default, so skipping...
NB: notice the red line i've added in my previous post, i had forgotten that... |
|
Back to top |
|
 |
Decibels Veteran


Joined: 16 Aug 2002 Posts: 1631 Location: U.S.A.
|
Posted: Sun Oct 19, 2003 7:42 pm Post subject: |
|
|
Okay, I don't have the 2.5 kernel to see if the name was changed. But in the
2.4 kernel and in the 2.6 kernel.
The two 8139 drivers are called: 8139cp and 8139too
Code: |
In your /etc/modules.autoload.d/kernel-2.5 file
# For example:
# 3c59x
8139cp
8139+ |
Plus, if as suggested you have it compiled in your kernel (*) instead of as a module (M) then you will not have to have the modules listed in modules.autoload.d... because there is no module to load, it is in the kernel.
I would suggest you recompile your kernel (at least to test) with them as modules and not in the kernel (some drivers work better as modules). Then change the above "8139+" to "8139too" (without the quotes ).
Unless for some odd reason they renamed it for 2.5 kernel only.
Then when and if you have it working. Use the command "lsmod" as root to see which one you are really using for your NIC.
Then finally, if everything is working and you really want it in the kernel. Recompile the NIC driver you are using in the kernel, but you will get an error that it didn't load if you leave the module name in the place you have it now, because again, there is no module to load.
Does this make sense? Then like you said, you can work on why kde doesn't start.
*Also note: Kernel 2.5 is a testing (unstable, not ready for prime time) kernel. Unless you are wanting to play with something new, that may not be correct and stable, you should use Even numbered kernels. I would go back to 2.4 or try 2.6.  _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Mon Oct 20, 2003 5:24 pm Post subject: |
|
|
okay, after recompilation with the the two modules with an "M" it still aint working
i'm going to find out how to change my kernel to 2.4 or 2.6 and try it
stupid remarq removed |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Tue Oct 21, 2003 9:17 am Post subject: |
|
|
Ok, after recompling my kernel with the right card(s) as module (M) i've found this on another topic:
Code: | insmod 8139too
modprobe 8139too |
and yes, my NIC works!
Never felt pinging Google so good!
But still, there's the initial problem: kdeinit failes to load
And i was able to fix that too with the code xPAGANx gave me:
xPAGANx wrote: |
emerge fam-oss
emerge libart-lgpl
env-update && source /etc/profile
|
and with a little adjustment it will be:
(mention the underscore)
But i still have to do, every time after reboot,
Code: | insmod 8139too
modprobe 8139too |
isn't it possible to make this autoload?
i've set this in /etc/modules.autoload.d/kernel-2.5 and kernel-2.4:
8139too
but doesn't seem to work |
|
Back to top |
|
 |
xPAGANx Tux's lil' helper


Joined: 08 Oct 2003 Posts: 93 Location: Warren, Michigan
|
Posted: Tue Oct 21, 2003 4:56 pm Post subject: |
|
|
Well I am pleased to hear you have come as far as you have..
you said you compiled kernel 2.6 and it worked...
you also said you put the modules in /etc/modules.auto.d/kernel-2.5,2.4
what about the 2.6? or isnt there one? or was this a typo?
xPAGANx |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Tue Oct 21, 2003 5:26 pm Post subject: |
|
|
there's is no 2.6 kernel
i didn't actually know how to manage that
i've now a working 2.5 (?) and it looks fine
the networkmodules (and also my soundcard) are now loaded even after reboot so thats also fine
but i've also compiled with NTFS and MSDOS etc support, but that still aint working (have followed the FAQ thow...)
after recompling with those options, i can't even mount my windows floppy's because gentoo says that's also not supported  |
|
Back to top |
|
 |
xPAGANx Tux's lil' helper


Joined: 08 Oct 2003 Posts: 93 Location: Warren, Michigan
|
Posted: Tue Oct 21, 2003 6:59 pm Post subject: |
|
|
did you add the filesystems as modules or did you build them into the kernel? |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Tue Oct 21, 2003 8:03 pm Post subject: |
|
|
xPAGANx wrote: | did you add the filesystems as modules or did you build them into the kernel? |
i build them in |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Wed Oct 22, 2003 6:27 pm Post subject: |
|
|
nobody any idea? |
|
Back to top |
|
 |
k:arel Tux's lil' helper


Joined: 14 Oct 2003 Posts: 91 Location: Belgium
|
Posted: Mon Oct 27, 2003 9:11 pm Post subject: |
|
|
they key was recompiling with NTFS en vFAT support as module, not build into the kernel
my fstabfile:
Code: | /dev/hda7 /boot ext3 noauto,noatime 1 1
/dev/hda10 / reiserfs noatime 0 0
/dev/hda8 none swap sw 0 0
/dev/hda9 home reiserfs noatime 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
#WINDOWS MOUNTS
/dev/hda1 /mnt/C ntfs defaults,gid=0,umask=727 0 0
/dev/hda2 /mnt/D ntfs defaults,gid=0,umask=727 0 0
/dev/hda5 /mnt/werk ntfs defaults,gid=0,umask=727 0 0
/dev/hda6 /mnt/software ntfs defaults,gid=0,umask=727 0 0
#/dev/hdb4 /mnt/G vfat defaults,gid=0,umask=707 0 0
/dev/hdb5 /mnt/linuxShare vfat defaults,gid=0,umask=707 0 0 |
my /etc/modules.autoload.d/kernel-2.4 file:
Code: | 8139too
emu10k1
ntfs
vfat |
this topic is solved |
|
Back to top |
|
 |
Decibels Veteran


Joined: 16 Aug 2002 Posts: 1631 Location: U.S.A.
|
Posted: Tue Oct 28, 2003 3:43 pm Post subject: |
|
|
Maybe it was the NTFS filesystem. I have ext3, dos fat, msdos, vfat all compiled in the kernel. I don't have NTFS though. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
 |
|