MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
it never succeeds in interfacing when the computer starts up. and then i have to reset the connection in drak control when i get into X. does anyone please know how to sort this problem out? thanks
I have a similar problem. The only solution I have found thus far is to start up using the old version. I would appreciate any suggestions as well. This seems to be the only major problem that I am facing with the beta version of Mandrakelinux 10.0
What is the name and specs of the networking devices you are trying to get to start at boot?
Post the output of lsmod (this must be done as root)
Post the contents of /etc/modules.conf
Post the contents of /etc/modprobe.preload
This should be enough to get us started. The reason why I ask this is because I had a similar problem that stemmed from the fact that the modules needed to load my network card loaded after the card was attempted to be brought up (and this ultimately stemmed from the fact that modules.conf is the kernel 2.4.x file for loading modules at boot and modprobe.preload is the file used to load modules in the kernel 2.6.x)
probeall scsi_hostadapter
probeall usb-interface usb-uhci ehci-hcd
alias sound-slot-0 snd-via82xx
above snd-via82xx snd-pcm-oss
alias agpgart via-agp
alias eth0 3c59x
alias eth1 via-rhine
# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules
If you are able to determine the module name for the device that you are trying to start, search the output of lsmod to see if it there. If it is not try adding the name of the module to the bottom of your modprobe.preload file (its in your /etc directory). Keep in mind in order to edit that file you will need to be root.
Try rebooting after that and see if it starts.
If this does in fact work remember to post back with any other info that helped you solve your problem so others can benefit from your experience.
u can try editing this file to add/alter boot processes
/etc/rc.d/rc.local
mermxx makes a good point, just keep in mind that the rc.local file is the last script to be run after all other init scripts. So in the case of loading proper modules in order to start a network device at boot (given that your network device will be attempted to be brought up before rc.local is run) it may not be the best way to do it. That file is however a very useful way to append things to your boot process and start-up.
The reason why I ask this is because I had a similar problem that stemmed from the fact that the modules needed to load my network card loaded after the card was attempted to be brought up (and this ultimately stemmed from the fact that modules.conf is the kernel 2.4.x file for loading modules at boot and modprobe.preload is the file used to load modules in the kernel 2.6.x)
I know you're waiting for a response from the original poster, but would you mind summarising how you resolved this? I suspect I'm having the same problem in this thread:
Problems after installing ATI radeon drivers in Mandrake 10
(I'd post the url, but you can't when you have fewer than 5 posts). It's not far down the page.
In it I forgot to mention that in the process of rebuilding the kernel, I went from 2.4.x to 2.6.x
If I can just get the infernal internet working again, I'll be all set
The module that you are looking for in that list is
3c59x 29680 1 (autoclean)
It is already present, so that cannot be the problem. Let me repeat what I said earlier, when I start up with 9.2, eth0 loads fine. When I start up with 10.0, eth0 fails.
Knowing that the device works at least with one configuration (under 9.2 you said it works) is useful so at least we know its not a hardware problem, but its not enough info to solve the problem.
A couple of things to try:
As root issue the command
service network restart
Does eth0 still fail when you do this?
Also try booting into 9.2 and 10.0 and comparing the text file /etc/sysconfig/network-scripts/ifcfg-eth0 between the two (its the configuration file for the network device).
If you post the contents of this file for both 9.2 and 10 that may be useful for narrowing down the problem.
eth0 still fails upon the command service network restart
For 9.2 where eth0 functions
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
MII_NOT_SUPPORTED=no
NEEDHOSTNAME=yes
Try editing ifcfg-eth0 and change
MII_NOT_SUPPORTED to yes
and try again it could be because of ifplugd which is by default used for eth0.
another way is maybe to assign a static ip address
a typical /etc/sysconfig/network-scripts/ifcfg-eth0 would be some thing along these lines bearing in mind the ip addys i have used here are typical lan addys, you could change dns to =yes and add dns servers to /etc/resolv.conf
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.0.2
NETMASK=255.255.255.0
USERCTL=no
PEERDNS=no
GATEWAY=192.168.0.1
TYPE=Ethernet
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules
scsi_hostadapter
sis-agp
thanks a lot, i am sorry for taking so long to reply.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
