Jump to content

pmpatrick

Members
  • Posts

    1861
  • Joined

  • Last visited

Everything posted by pmpatrick

  1. To determnine your gateway, just run: # route Eg. Here's my output which is pretty vanilla for a router/ethernet system using a broadband modem: # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 Your network configuration is in /etc/sysconfig/network-scripts. You will see config files for each network interface. The one for eth0 is ifcfg-eth0. A generic one for dhcp setup would look like this: DEVICE=eth0 BOOTPROTO=dhcp NETMASK=255.255.255.0 ONBOOT=yes METRIC=10 DNS is configured through /etc/resolv.conf. And the module/driver for your network card is loaded through /etc/modprobe.conf. For reasons unknown to me, DSL seems to have more issues with DNS. If you can ping outside numeric ips but can't resolve urls, it's probably a DNS issue. The ip for mandrivausers.org is 83.245.15.165. Try pinging that number and see what you get.
  2. No, jpackage is an open source implemetation of java. That's probably what's screwing things up. You probably didn't install java from an rpm so it's not in the rpm database. Just my best guess.
  3. Limewire is a java application. You have to have java installed for it to work.
  4. Open a console, su to root and see if the card is listed when you run: # lspci also, check the output of: # lsmod See if the ohci1394 module is loaded. If not, it may be setup to autoload only when a firewire device is connected to the card. Try doing that.
  5. In 2006, ndiswrapper is broken on the smp kernels. You have to install a non-smp kernel for it to work properly. I can't find the errata page on mandriva's new website, but I definitely remember seeing it there. You could also use your LE2005 smp kernel in 2006 as a workaround if smp support is important. I really haven't noticed a huge performance hit with my P4 HT cpu.
  6. I got it fixed. The problem appears to be with the dkms package. dkms is suppose to automatically compile and install nonstandard kernel modules like the nvidia driver. I uninstalled dkms and redid a manual install of the nvidia driver and all was well.
  7. No NTFS here but I got it fixed somehow. I installed another kernel on it for win4lin and was trying to get the nvidia driver working on it. Nvidia wouldn't compile properly with the new kernel because the kernel was compiled with gcc-3.3 and mdv2006 has only gcc-4.0.1. Actually, the module compiled but refused to load complaining of the version mismatch. I rebooted into my old kernel and no more shutdown problems at all. The above leads me to believe it's a problem with mandriva's nvida installation which was corrected by my failed attempt to install the nvidia driver on another kernel. You might try dowloading the most recent nvidia driver and reinstalling. Edit: OK. I spoke too soon. Had a little more time to look at things and it seems that Opengl(i.e. 3d acceleration) is no longer working; I'm sure it was working before. The nvidia screen comes up and the driver loads but I just get error messages when I try to run glxgears. I also have the suspicion that if I get 3d back, my shutdown problems will return. All this definitely points to a problem with the nvidia driver, xorg and manadriva's implementation of the same. Will try to experiment a little more this weekend.
  8. I have shut down issues with 2006 as well. When I try to logout, reboot or shutdown, the system hangs at a blue screen. Glad to see I'm not the only one. I haven't figured out why, but the workaround is to hit Ctrl-Alt-F1. That will take you to a terminal, command line login. Login with your username and password and then run: $ halt or $ reboot Alternatively, don't even try to shutdown with the kde menu entry; just open a console and run the above commands.
  9. I don't mount any network shares at boot so that's not an issue for me. However, in kde, if I right click a folder in my home directory and try to set file sharing and then tick the "Configure file sharing" button all I get is an unitelligible grey window from mcc popping up instead of the usuall file sharing window. I could probably set the whole thing up manually as this appears to be an mcc bug but I haven't had time do so. I've seen others complain about the file sharing as well. I haven't heard any other complaints like my shutdown issue; I haven't even checked my logs yet which would be the first thing to do. It could be xorg or the nvidia driver which was autoinstalled. It's just an FX 5900 graphics card; nothing new or exotic. I guess I'm planning on waiting things out a bit and see if any big bug fixes come out in the updates before digging into 2006.
  10. On balance, 2006 is OK. The two major bugs I've seen are network file sharing(it's seriously broke on my box) and shutdown issues. Mine hangs on shutdown, reboot or logout at the blue screen. I have to go to a terminal and issue a reboot command. That's not nearly as bad as some stuff we've seen in the past but annoying nonetheless. I'm sure they will get it sorted out in the next month or so. In the mean time I'm sticking with LE2005 until the bugs are fixed.
  11. AVG is well known by windows users as they provide the most commonly used free antivirus program for that platform. Their stuff is OK - it's free, it's decent and it's not a resource hog, unlike norton. A lot of windows users ask about antivirus software when they try linux; they just can't believe it's not necessary. This will give them something familiar to use even though it's totally unecessary.
  12. 1. Probably. 2. Yes, try a recent 2.4 kernel; if you have problems try an earlier kernel. 3. Yes. It's commonly done. 4. Don't know.
  13. aRTee, check out my post here: https://mandrivausers.org/index.php?showtop...22&hl=konqueror That kded thing was a widely reported bug in mdk10.1 as well. My post in the above thread deals with a workaround:
  14. There's already a fairly extensive errata for 2006: http://qa.mandriva.com/twiki/bin/view/Main...Linux2006Errata Some of those look pretty serious. The new xorg in particular is causing a lot of problems. I'm getting a lot of freeze ups and crashes. I beginning to think arctic has the right idea; sit back, wait a month or two, let the bugs get fixed by updates and then install.
  15. Scarecrow, what shortcomings are you refering to? They're not obvious to me. I think pclos is a pretty nice project. Texstar, the main developer, has a long history with mdk and has a well deserved rep for being an excellent package builder. His themes were always top notch as well; something mandriva still hasn't managed to achieve. Tex knows how to put together a very nice looking and nice acting distro. When tex went off on his own to make his own distro as a fork from mandrake he stopped building rpms for mandrake/mandriva. A lot of people around here really miss tex and the excellent rpms he would build for us. Give the guy a break he's done a lot of good work and hasn't asked a whole lot in return. His distro generally gets very good reviews and is especially well liked by noobs. I have pclos installed on one of my partitions and I think it's excellent. He's using apt for rpm with synaptic for package management and the distro is definitely upgradable through apt with a ton less fewer problems upgrading than mandriva or debian based distros for that matter. The packages available through tex's repos are excellent and wide ranging, including most, if not all, of the plf stuff. Pclos is pretty nice IMHO and the live cd is much better than mandriva's. I wouldn't have a problem recommending pclos to anyone.
  16. Maybe it was a lame library. Compare your output with mine: $ rpm -qa | grep lame gstreamer-lame-0.8.8-1plf liblame0-3.96.1-1plf lame-3.96.1-1plf I'm pretty sure the mp3 ioslave needs the liblame package. It wasn't clear from your prior post whether you had liblame. Gstreamer is for gnome stuff and shouldn't effect kde.
  17. It's definitely a kde package but I don't remember which one. It might be one of the kdemultimedia packages. Here's one I have installed that looks promising, kdebase-servicemenu: At least it mentions something about lame. IIRC I was trying to get mp3 in the koqueror audio Cd browser and just kept adding stuff and it started working. It must have been something in kdemultimedia or the kdebase-servicemenu package.
  18. I know exactly what you are talking about and run LE2005. In konqueror, I'm getting cda, flac, mp3 and ogg vorbis. They all work perfectly.
  19. For any mandriva club members, the 2006 torrents where just posted on mandriva club.
  20. I haven't seen the torrents released for 2006 on mandrake club yet. Hopefully, they will be out sometime today. To answer your original question, you just have to go into the media/sources section in mcc/software management and edit the dvd source to reflect the mountpoint for your dvd drive.
  21. You generally don't have to reinstall; windows overwrites the linux bootloader,lilo, when you reinstall windows. You just have to reinstall your lilo bootloader. That can be easily done. Boot off your mdk10.1 install cd-1. As soon as you see the first screen, hit F1 which will take you to a command prompt. At the prompt, type "rescue" w/o quotes and hit Enter. That will take you to the rescue selection menu. Choose the option to reinstall lilo. That should do it; reboot and your old lilo boot selection screen should be back.
  22. Disk overlays are a terrible hack IMHO. They cause problems in both windows and linux; I avoid them like the plague. The only stable solution is to invest in a pci ide controller as that won't be bound by your bios hard drive size limitations or to get a bios update if one is available. I assume you've looked into the bios update and none is available. At any rate, these drive overlay programs are not necessary in linux. Once the linux kernel is loaded, linux kisses the bios hard drive size limits good bye. Windows is much more bound to the bios size limits and drive overlay programs are a hack around that limitation. You only have to make sure you install linux on a partition within the bios size limits so the kernel can load. That would not be a problem at all in your situation since you have linux installed on another drive. I assume mandrake sees the entire 100GB. All that being said, do NOT attempt any partitioning operations on the drive with hardrake; you will undoubtedly lose all your data if you do so. Before fooling around with anything on the drive, backup your data to cd-r or dvd-r. That's probably a good idea anyway as I've lost data on drives with an overlay even within a pure windows environment. Bottom line, that drive overlay is probably not compatible with linux and is necessary for the the drive to be used in windows, at least to full capacity. You really need a hardware solution, i.e. a bios update or a new pci ide controller card. That will allow you to get rid of the overlay program for once and for all.
  23. If you have your swap partition on hdc and not hda, I would suspect swap activity to account for the hdc disk activity. You could try experimenting by commenting out your hdc swap partition in fstab and creating a swap partition on hda and adding an entry for it fstab. i.e. isolate swap on hda. When running a heavy DE like kde or gnome, I think you will get swapping with 250MB of ram.
  24. A.I., I agree with your observations. Also, I'm not accusing anyone of cheating. I think there is clearly a campaign to elevate the ubuntu score but I assume that these types of campaigns are within the rules of distrowatch. As to whether we should launch a similar campaign, assuming the rules permit it, I agree with everyone here that it would not be advisable to do so. IMHO launching that type of campaign is a tacit admission that your distro couldn't receive a decent score without such extraordinary efforts.
×
×
  • Create New...