ianw1974

OK, I've found something else that may help: First off, go back into HardDrake, and we'll set to choose DHCP instead of the Manual Configuration we've gone with so far. Afterwards, check /etc/sysconfig/network-scripts/ifcfg-eth0 to make sure the settings are: DEVICE=eth0 BOOTPROTO=dhcp onBOOT=yes METRIC= IPADDR= SUBNET= GATEWAY= HWADDR= DHCP_HOSTNAME= NEEDHOSTNAME= Then check /etc/resolv.conf and make sure this is clear of DNS server settings. Just edit, and place a # in front of any DNS servers listed. Do the same for /etc/dhclient.conf Also, just do a lspci (LSPCI), to make sure your card is recognised fully by the system. Then reboot, and see if that resolves the problem. If not, do a dhclient eth0 and post back the results, along with ifconfig as well.

OK, been doing a bit of googling, and see if any of this will help for you. We've currently allocated an IP address to the card. In this example, I will assume you set 192.168.1.2. You can try this: ifconfig eth0 192.168.1.2 up Then type route, and see if you have any routes configured. You may need to: route add default gw 192.168.1.1 (assuming this is the IP of the router) If it was DHCP assigned, then you could type: dhclient eth0 so you could try this, if the above doesn't work, but you'd need to reset the card to DHCP, through the config we did in HardDrake before. Also can try "lspci" or "cat /proc/pci" and look for Ethernet Controller, to make sure we have drivers installed and running OK. And one last thing, type: "dmesg | grep -i eth0" and report back what it says.

The "echo $LANG" command, just gives back what's set for the keyboard. If the rpmnew's have now replaced the files as before, you still can't log in through KDE? What happens? To get rid of X, type "init 3" when on as su, which should stop it, then try startx after that to get it back up.

What does your /var/log/boot.log show? Does it show errors on bootup for the network?

That's OK, I think that's only usually enabled for laptop configurations. I have it enabled on mine, but then I'm using a laptop :P I'm stumped, as I'm not sure what else to suggest. I can't figure out why the card won't start. I'll keep thinking about it, and I'll do a bit of googling to see if I can find something in the meantime that may help resolve it, or perhaps, some members here might have an idea on something else that can be tried. I'll get back to you, if I find something useful to try!

OK, and when you do the network config, is network hotplugging enabled along with start at boot. Also, when you go through the run config again, does it remember the settings we entered before?

I presume, if you stop and start it, that it still doesn't show an IP address?

Reboot after you've made the changes. Type "reboot", that should let you start with the new files.

I think I might have posted in between your reply. Did the Network Service show as running or stopped?

Looking back, I've just checked this same thing on mine for comparison: Comparing, the first two lines are missing for you, and the "UP" is missing from the broadcast line. For some reason, your network card isn't up, and I can't understand why. Can you check this for me: 1. System/Configuration/Configure Your Computer. 2. System then Services. 3. Network service (can you report it's current status?)

That's OK, my network reports the same on my module. At least we know it's there, we just need to figure out sorting the network config now. Just need to gather my thoughts, and I'll see if there is anything else I can suggest shortly.

OK, back in the network card screen, after you've clicked it, but before clicking run config, there is a screen to the right with a load of info in. Under misc, there is Module, and it will give a name for it. At the prompt, su and root, and type lsmod (LSMOD), and have a look to see if that module is running. If not, type modprobe and the module name you noted earlier. Then run lsmod again, to see if it's there?

OK, you need to do this: Switch to each of the directories, and replace each .conf file with the .rpmnew. To do: cd /etc/kde/kdm cp kdmrc.rpmnew kdmrc.conf repeat for each of the others. Take copies of the original .conf files first, in case there are any other adverse effects, but you should be OK.

Did it fix the mdkkdm issue? I did the urpme and urpmi, and got it working to an extent, but what I experienced was this. When I choose reboot or shutdown from within KDE, it would return to the mdkkdm screen. Then I had to click halt or shutdown for it to actually do what I wanted it to. I don't really like xdm or gdm, so haven't bothered to install KDE 3.4 until this issue was resolved. Also, kdesysguard didn't work either, which I like to use, and another reason I didn't run it. Currently staying with 10.1, because I couldn't get LE2005 to configure my graphics card with 3D/OpenGL. I think it might have been because of urpmi upgrade, but not sure. I've not got a CD/DVD image to try it, since my connection is only 128kbps, and would take me a week to download!

Have you tried adding to modprobe.preload?

Also, do you have link lights on the network card? Have you checked the cable, to make sure it's all OK?

What ethernet card do you have?

Or this link: http://www.student.lu.se/~mat02mni/misc/setup_flgrx_ati.html

OK, this'll be the prob. Right, what we can do is this. If you're in KDE, this will be the easiest way. 1. Click System/Configuration/Hardware/HardDrake 2. Supply root password when prompted. 3. Select the network card on the left hand side. 4. Click Run Config Tool. 5. Select LAN Connection. 6. Select eth0. 7. Select Manual Configuration. 8. Set IP address which is the same range as your router, and make sure the subnet is also. 9. Set hostname to whatever you want it to be (all one word). 10. Set your DNS servers (ISP supplied), and set the default gateway which is your router. 11. Ignore zeroconf and leave blank. 12. Choose Yes to restart network. Then try ifconfig and see what it reports back?

Have you just done the modprobe ircomm, without actually doing the makedev first? Make sure /dev is clear of ircomm (which it seems to do after reboot). Then type modprobe ircomm (need to be root for this - su and root password). Then type lsmod | grep ircomm and see if it lists the device. If so, then add ircomm to modprobe.preload, or if you say this didn't work before, add to modprobe.conf instead.

Have you ran an ifconfig at the prompt to see if it shows the IP bound to eth0? First, su and supply root password, then ifconfig.

OK, you can try this too. If you're doing a fresh install, don't install the ATI drivers, and see what performance you get? Reason I say this is I'm using a Radeon 9250 card, with LE2005, and I didn't install the ATI drivers. It works, at around 1000fps. To get it to work, you'll have to install mesa, and then edit the xorg.conf and add the Section DRI I mentioned before. Then apply MandrivaUpdates (I normally apply all normal, security and bugfixes). Obviously, rebooting the system after, as you'll need to restart X before the new settings take effect. If you've currently got the system with the ATI drivers on, then you could always try removing the ATI drivers using urpme or the Remove Software option (file begins with fglrx). Then reconfigure the card, and check the xorg.conf for the section information etc, and make sure you've checked the MandrivaUpdates to see if there are updates for mesa, etc. Rebooting afterwards, to pick up the new settings. I'm not on my LE2005 system at the minute, but I will get on it in about an hour, as it's tied up with my missus playing Frozen Bubble!!!!

And the following section is in xorg.conf? Section "DRI" Mode 0666 EndSection Also, check for a line, normally near the beginning which says load dri? Also, what version of xorg is running? I think if you're running LE2005, it'll be 6.8.0.

OK, I'm assuming your in KDE. If so, click System/Configuration/Packages/Install Software Choose the option for viewing all files, and scroll through the list to find dhcp-client and dhcp-common, or just type dhcp and search (make sure All apps/files is selected first). If they aren't on the list, then they'll probably already be installed. One thing you could do, is configure the network card for a static IP address, then you'd be able to ensure that networking is fine. You can do this, by clicking System/Configuration/Hardware/HardDrake. In this screen, go to the network card, and choose the configure option. You can then set an IP, subnet mask, default gateway, and DNS servers to access the network/internet. Make sure you have a hostname, but don't worry about search domain and zeroconf hostname, these aren't really needed. This will then rule out the network card as being a problem, and that you're not getting dhcp for one reason or another.

Normally, mesa is required, but because of the lack of dri, you get "Mesa Indirect" instead, which is really bad. When direct rendering is working, because of the DRI section in xorg.conf, everything is OK, but you still need the mesa libraries for OpenGL anyway. It's the direct rendering that's the main problem.