User

Bump! :) tried as suggested LoadModule php4_module /usr/lib64/libphp4_common.so.4 Syntax Error on line 248 of /etc/httpd/conf/httpd.conf: Cannot load /usr/lib64/libphp4_common.so.4 into server: /usr/lib64/libphp4_common.so.4: undefined symbol: php_startup_internal_extensions Has anyone got those files around? Only way it sems (per on the net) it will be created for me is if I decide to install Apache2 and PHP from source (if it is really suppose to be libphp4.so or libphp5.so - seems to be the _common.so for 64 bt - I could be wrong). That should not have to be the case if Mandriva is to be a user friendly OS and has all the rpms for installs. Any help would be appreciated.

Maybe I need to clear something up. This is 64 bit Mandrake installed. I found out that the install does not create the 64 bit libphp4.so or the libphp5.so on some AMD systems. Anyone got a link to download these files? Any help would be appreciated. Thanks in advance. :)

Yes to all being installed as stated in the 3rd line in my oriinal post. :) my rpm -qa apache-mod_php returns: apache-mod_php-2.0.54_5.0.4-4mdk so pretty sure all is installed okay. Just the php files will not run properly. They work fine on another server running LE2005. Even gave it execute permission just for the hell of it. :) No go. Any other suggestions. Could it be I need to unassociate it to open with a text editor on the local machine (never needed to tdo that before). Will try that later when I am on that system. Could it be I may be missing some specific <IfModule> directive perhaps in the httpd.conf file? Thanks again in advance.

I had a hard drive crash on me... For the life of me I can't remember what I needed to do to get php to run on a local notebook with apache. I had it fine on 10.1 but on LE2006 I'm forgetting to add or edit something. All modules apache, php and MySQL are installed. I've edited my httpd.conf to the proper document root and proper <Directory "/home/my web"> added LoadModule php4_module extramodules/mod_php4.so - (also tried php5) tried with and without AddType application/x-httpd-php .php - (and also the extra extensions like .php4, phtml, etc - and even tried AddHandlers) Even tried the remove 2 php applications/x in the 70_mod_php.conf (and php4) suggestion (know I never did that in 10.1 ) edited the php.ini file to include the proper doc_root= "/home/my web" copied php.ini in just about every php dir to cover almost every path I could think of (I may be missing something here - am running x64 version of Mandriva) wrote a basic test.php file and put it into /home/my web everytime I run firefox locally (http://192.168.1.10/test.php) it keeps asking what to do with the file (save to disk, etc options) instead of just parsing/running it properly and displaying it as a web page in the browser. Also added in host file 192.168.1.10 MyNotebookName to properly resolve it Made sure httpd service is running and can access/run html fine (no errors). Does anyoneknow/can help with what I'm missing? Thanks in advance! [moved from Installing Mandriva by spinynorman]

Thanks! :D

Anyone got a default or close to default copy of the etc/group file for Mandriva 2006 that they can post up in this thread? I edited some permissions and accidently edited/deleted one or 2. I just need to see th default to verify that I at least got spcific defaults correct. Thanks in advance. [moved from Software by spinynorman]

Try the above in my previous post. It is specifically for the Broadcom wireless adapter (the aspire has the 94306 chip in it.) You will need the 2 files BCM... Uninstall the ndiswrapper (if you used a newer one and retry installation of the one that is on the linux CD). You can also use Linuxants driver install, and those 2 BCM* files.

I going to try and keep this short and I'm not going to waste hopefully time (and BB space, and those quotes on quotes, etc. :) ) correcting some errors in your last post. The X popping up on the screen with a blue background, and then nothing (notice the nothing???) is a video crash and "also" happens when the video fails and it tries to or drops back to the basic VGA install screen to allow a different configuration attempt. A script failed to get the pallette image? Please try something better than that. It's just accessing a file. If you put in a different card, it most likely wouldn't be affected by the script and in all likelihood would get it with the same script you claimed that failed. Not a script issue. Video cards cannot burn out? Of course they can. 1) Overdriving a monitor can cause monitor to draw current and current surges from video cards to blow them out. Can also cause shorts/sparks/discharge on the connector and fry out the card. 2) Using an improper clock frequency on a video cards chip (especially overclocking over a safe value - usually no more than 5%-10% is a safe normal allowable range) will ruin that card. Wrong drivers and settings can send commands/signals that can fry them out too, even if/when the driver is for a different card. Both points above can also cause the Motherbaord to also burn out/ blow, fry, etc. from a frying/blowing/burning video card. Warnings from card manufacturers are there (NVidia, ATI, Matrox, etc) of possible damage to both monitors and the video cards. Hmmm, now if the card can never blow, why manufacturers bother with the those specific warnings? (Rhetorical question) Quick example of a bad issue. My Pine OEM G2 MX200 gets identified as a G4 MX440 on Mandrake 10.0. Fortunately I caught the error and set the proper card manually. And fortunately the chip in my Pine Card has the same clock frequency rating. But if it had been an older version of the card with the older chip it could have been fried if the driver drove the chip at the MX440 card's default setting. Hopefully, karigar at least will get back to us on if the older version worked for him. It should, as I never had and issue with 10.0 on my Acer notebook (AMD64, ATI mobility 9600) and installed straight from CD to bootup, but did not in 10.1 (originally doing a 10.1 upgrade, and then even doing full wipe and a 10.1 clean install). The things I needed to do according to Xorg were preposterous to have to do to get it finally working, when it did work fine on 10.0. Yes it is up and running on 10.1 and is working good now. But it never should had been so much work to correct the video issue if it worked great on 10.0.

See if I word this right (appologies if I don't). arTee... Absolutely not, it fails on the setting after that basic resolution setting that comes after the X, which is no longer the simple VGA install resolution. And if the new setting/resolution/driver cannot install, then it is useless as a basic installable simple GUI desktop OS. And if the test fails, you go back and drop back to the X, then that is a failsafe dropback not at the requested, supported (if correct) resolution. Bad move, as a wrong setting can actually damage a video card or display. And bypassing the test then also leads to not knowing for sure if the resolution or the actual hardware even supports it. Then upon bootup failure, who's to say it is a video problem or not afterwards. Or you can just blow up something. How? By blowing the video card/monitor out as a possible very bad scenario. That testing is there to do, else why bother put it in period. You may want to take chances, but most people will not. And I don't think the Mandrake (and others) wants things like that to happen either (see issues about ruining CD-ROMS too). See your own comments below (486 etc. - you're in more trouble than this board can fix?). If they did in fact have a 486 processor, then Mandrake 10.1 wouldn't install, period. It only comes with the 586 Kernel. Older systems/cards/CPU's are no longer supported by newer OSes. Only choice will then be to go back to an older version. But a video failure/issue should never be the cause to do that, but for Linux it is more likely than not to be. (See later down this post). And in many instances older version worked fine on the same supported hardware, and did not with the newer version. That means something got broke or is no longer supported, but it never should have. Especially when a basic absolutely needed hardware, at it's most basic setting, should work always. Of course they do. Just look at this board's posted problems, and many unsolved ones. That goes for all OSes, and will continue to be so. Mdk may be for 586 or newer, but 586 has nothing to do with video, nor should ever have anything to do with it. A ISA/PCI/AGP/PCI-e/etc. video card should always work regardless of the processor. Programming for the standard VGA capabilites basic display properties is not processor dependent. Are some repairable. Yes. But also many have still not been solved. And seeing as the install actually starts for this person and proceeds and only fails upon video testing, means that this person is not on a 486 cause Mandrake 10.1 is only for 586 and up. Bad point/comment to make on your part. And this board is here to fix issues, for all Linux versions, new and old, hardware/software, etc.. Go read the commentorial/editorial/description. Things get better on newer equipment/hardware only. And that is mostly due to it being programmed/designed for newer equipment/hardware. And the hardware itself is so much faster and better. If Linux is to be a GUI OS then the simplest VGA mode needs to always be accessible upon every video failure. MS does it very well, Linux does not. Windows has not gotten faster too? Of course it has. So has Unix, Mac OS, etc. But that is also easily due to faster processors and other hardware. Sloppier coding will run faster on the newer hardware, just by the fact that it's faster hardware. Try recompiling the latest "current" 386 kernel on a 386 system, and an older one with all of the same options. If you bench them, the newer one runs slower. (That is something you can try yourself for actual proof). Why? They (and most) just want to do a basic install of Linux and at least get it to boot to a standard simple working VGA Mode on a 586+ processor (as suppose to be supported). If anyone who just starts out with a newer Linux OS has to revert to a text mode Linux, then that is absolutely no enticement to get them to switch from Windows, or even DOS 3.x for that matter. And if they got to do tons of editing (especially in text mode), etc. (and many people are clueless to do that) then that is not a good point. Bad point! Most Linux distros no longer install a 386 or even come with the 386 kernel, so it no longer installs to the basic 386 processor kernel. Which they should as the newer x86 (486,586/686 and higher) processors still have/include all the same physical structures/instructions. They have all been designed mostly to install to the extra 586 processor instruction set, just like windows OS (no more 386 kerenls, just 586+ kernels). Linux should be better than that. That is intentionally by design from the programmers/designers of the Linux kernel (and all the other Oses) and distro programmers/creators. So to make a point that current linux installs and runs on a 386 is wrong. Yes, many can actually write/rewrite all the coding to do so, but if I (or anyone) want a Mandrake 10.1, Fedora 2/3, etc., to install on a 386 machine from the downloadable ISO's, that will never happen. So no idea where you get that idea from. Perhaps you can point us all to that wonderful current, new and decent distro that does and without needing to completely learn the whole Linux OS/kerenl and a manual recompiling/tweaking. I would love to install it! (on a 386 or 486 ). A (any) failure in the video in Windows automatically drops to the 640x480, 16 colors (if needed for info purposes 4-bit) GUI mode (including longhorn) and not into an OS safe mode. Linux (whether Xorg, Xfree or if there is anything else) keeps erroring out, crashes and/or in most instances keeps retrying to restart the X display, or miserably crashes as oppose to just dropping to a minimal standard GUI. Noone should need to edit or text trouble shoot files anymore for video. Worst scenario should be a 16 color GUI desktop, ugly (colorless) as it is. Get to the desktop, and then install/test video drivers. VGA is the very basic of video programming and it is a basic standard that all video cards work on. MS windows, all versions, always respect that and so (almost) always boot up to a poor looking GUI. Windows upon installation of a new video card, upon failure of a new driver, upon accidental deletion, etc. does that (usually), period. Linux still hasn't taken a good page (one of the very few good pages ;) ) from their book.

Depends how far back you go. I got one system that the best I could put on it without needing to do tons of tweaking or modifications with an SiS 1MB PCI video card was Red Hat 7.0. It makes for a good multinetworking router/firewall by dropping it down to text mode only. Anything newer basically just failed miserably. Another system, the best I could do was Red Hat 9.0 and that was with a 1MB Matrox Millineum video card, which isn't that bad, in graphics mode ( the OS actually still had the specific driver for it in there - but your card may need to go as far back as above). So perhaps try Mandrake 9.0 or less. I believe the kernel match for RedHat 9.0 is Mandrake 8.0 (could be wrong there - trying to go off of memory on kernel matches at the time). That is another thing about Linux, that it does not take MS's lead into making sure to always work in a simplified GUI at Standard VGA mode 640x480 at 16 colors as a failsafe, so it doesn't matter what card you have in there if it fails. All Oses should do a no need for anything but basic VGA mode desktop upon video display failure.

Try only the VGA or SVGA "generic" card at 8 bit, 640x480, maybe 800x600 tops. Else you will need to throw away the 1 MB video card, at minimum. Addendum: You can try to install in text mode and try options there.

inet6 is IPV6 and that is the IPv6 address, assigned for your eth0. Currently the net is IPV4. You can disable the service in Services to not start on boot. Try that.

Try this and see if it works route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1 dev eth0 then try to get to sites. If it does then go into System|Configuration|Configure Your Computer and recheck/redo the network adapter settings for eth0.

What worked in 98SE? The CD rom drive? Windows 98SE is a 650MB bootable CD rom disc and as I mentioned above, it (Windows 98SE) may be bootable (and possibly only read the older CD's) because your actual CD Rom Drive may only support booting/reading from that old 650MB CD standard. As it may be an older standard CD drive (depends which option you got) the older CD drives were never designed to do the newer CD Rom discs cause they can not (or were not - depends what one you got) be manufactured to support a standard that was not out (or by choice of your system) till years later. And hence may not boot (or even read) the newer standard of the larger CD disks (700MB or 800MB). Of course your CD Drive may be gone too. Put in the 98SE CD disc in. If it boots then most likely you got a old drive that will not boot anything on a 700MB or higher CD. Boot from a Linux floppy (use your Dell to create a boot floppy from Linux CD - instructions are on the CD ) and boot it up and install. It's as simple as that. If it then has problems reading your 700MB Linux CD upon installation, then you need to get a different CD drive (see if you can get the DVD optional drive for it, even used - no guarantees that the DVD supports the 700MB standard, but in all likelihood it should). If you can't or do not want to get a newer drive for it, then you could just be out of luck for most versions of Linux (and even XP if it came on a 700MB disc - or if you got a burned copy of XP, get it burned on a 650MB disc not a 700MB disc) as most of them have gone to 700MB CD images/ISO's. Go here also to make sure you got latest of whatever is needed in regards to BIOS. etc., also. http://www-307.ibm.com/pc/support/site.wss...cid=DSHY-3TLQ2L

If neither OS (XP and Mandrake) will boot, then perhaps you have a CD (DVD) Drive that does not boot (or even read) from 700MB (or 800MB if that is what you used to burn) size CD's for your old IBM Model. You'll need to create a boot floppy in that case. If you have 98SE installed on the laptop, does it even read the created 700MB (800MB) CD correctly? If not then that is definitely a read problem and even with a boot floppy will fail to install. If it does read, it may still not be a drive designed to boot 700MB ( 800MB) CD's so use the boot floppy. Hopefully you won't have installation issues if it can't fully access the full 700MB (800MB) CD's areas while it's installing. That is one problem Mandrake and all Linux houses should address. Create all ISO's to only max out their size to be able at minimum to fit the regular standard 650MB CD standards only.

I've had this same problem, on even earlier versions of the Mandrake, REdHat, Fedora, TurboLinux, and the Windows Oses too. Some of the issues, and things mentioned below have still not been done, but am repeating. It's been mentioned on numerous times above, to actually validate the MD5 checksum on the actual Burnt CD's, and not just the Downloaded ISO. So if your file is on your hard drive and you md5'd it and it was okay then that was step 1. Then you burn it to CD. Then you MD5 it on the actaul CD. So if (we'll use DOS for this) your CD-ROM drive is E: then put the burnt CD into that drive and then MD5 E:\ and make sure it matches also. If not you got burn problems. If all is well then, you can still have issues, and they could be intermitent issues. First one can be a intermittent/or permanent bad CD drive (been mentioned somewhere in the postings above that it has worked on another machine - and if not on another machine maybe that machine may have a problem below also). The CD may read correctly when doing MD5 check, but when installing a read error could be generated when installing. Whether due a faulty buffer memory in the CD's memory that is not being used at time of install done differnetly by doing a MD5 check. Or to a peice of hair/dust/dirt/etc. upon the sequencing of the way the head moves during install as opposed to a linear movement on an MD5 check that causes the faulty read(s). And a whole slew of other issues. Easiest thing to do (not so easy for notebooks unless you got a portable CD to try) is put in a new CD drive. Also just blowing inside the drive door cold help (do not use too poerful of compressed air if you do use it), and make sure not to spit. ;) Next one, your CD has issues following the strict guidelines to CD Standards. Meaning that it is one of the many drives that either do not fully support or had actually issues handling the total size standards on reading the full 700MB size standards. Go to a hardware testing/review Website. Anandtech is one I know offhand that does fairly good analysis and may have older listied drives still listed. Easiest fix for that is once again, try another CD drive. The CD error can also be attributed to the drive controller or MB (whether intermittent or permanent) that has finally creeped up also. Then you got a differnet issue. And yes it could be a specific way the data is accessed that hits the controllers faulty area (or it could b a compatibility or bug issue that causes it to retrieve data incorrectly). This issue is not a quick fix as it could rquire a new MB. And also remeber the drive controller also controls Hard drive and floppy/etc. so then the issues also ends up showing up there , so even a Hard Drive install may fail in the same way. Now another issue could be the memory corruption upon installation. Meaning a bit or many bits in your actual PC memory that is now currently being accessed by 10.1 install is bad. Try another memory chip(s). Another issue is actual video related (which also can be tied into a memory or CD drive issue) . I'm not getting into great detail here on all the ways it affects the install, but if you got another video card (even a different brand) try that. Easier yet, just type "text"(without quotation marks) at the beginning of the boot prompt at the initial install bootup screen and try a text install. It eliminates video issues, hopefully bad memory accessed areas , and also a lesser issue on CD ROM accessing. It could also be a newer driver issue. Meaning that 10.1 may have a newer driver that it uses to install and so either it is faulty running now with the current machine, or the older driver was faulty and it's failure was handled in a way that allowed the older installation to continue (this is one of the few instances a bad driver is a good thing - but in reality is not cause it then seems that the actual Device is good but is in fact not). A fix to this is not so easy but try the text install, or try the 3rd party driver install option (I would try the CD driver first, try the rest after) or the driver on the previous version. Or replace the device with something else (like the CD, memory issues above). Or it could be that your hardware now is no longer supported or even tested with the newer version. This means even the manufacturer or Mandrake may have altered drivers enough not to fully include all of the slight variations in the design of your model anymore (meaning they didn't test/include all older hardware revisions bioses, firmwares etc) and may not work anymore. Check any hardware compatibility list. If it is not listed as being verified, then it's a hit or miss attempt to get it all working. Just a few suggestions to try out above.

Change back the permissions. And if you installed and re-installed make sure that during the installs/re-installs you made it reformat all partition(s).

Oops, forgot that you need to also choose Gnome Desktop as an added X server when installing, to use gdm. Therefore type kdm at the prompt and see if you can get in after interactive booting. If you can then after logging in, reboot again. I personally install multiple X servers for instances where there are video, desktop/Xserver issues. Or better yet if kdm fails, install Gnome Desktop manager from the CD at a command prompt using rpm. Then reboot, get to the Interactive command prompt and then gdm to the desktop. Also look at your video screen when either using the command kdm or gdm at the very bottom and see if there is a thin strip that seems to be a bit lighter (it is partially backlit on a clear black screen) if it hangs after the command. Then it's definitely a video/Xserver issue. You most likely got a radeon mobility chip in your notebook and so there are a few issues using the standard radeon fglx driver. I went through all the Xorg stuff, editing the XF86Config*/xconfig/etc and got almost all the same errors. And at one point there was even a point that needed a recompiling of the kernel ( at least for mysellf), which is just too much work to do to bypass a basic video issue and a problem with first init boot process on certain laptops, which yours may also fall under. Since you lost your dual boot, if you re-install Mandrake make sure to let the install (re)format the partition(s) as there are certain files that do not get properly overwritten to clean up the XServer config files. Good Luck!

This is off of my little BB, and should possibly work with other .INF drivers (case sensitive when naming your driver to install) that might help some. I bought myself, quite a while back, an Acer Aspire 1500 notebook. Under Linux, trying to get the wireless adapter to work, was a pain, especially using the ndiswrapper or Linuxant driver. So I'm posting this doc to show how I got it working quite well. It should also work on other notebooks with a similar adapter (and possibly even different adapers). Hope it helps someone. ******************************************************************************** ******************************************************************************** * ******** Installing Wireless Broadcom driver on the Acer Aspire 1501 Mandrake 10.1 This set up is for a static IP (use an address outside of your wireless routers DHCP range - set up your router according to it's specs) ******************************************************************************** ******************************************************************************** * ******** 1. If not already installed, install ndiswrapper-0.9-1mdk rpm package from the Mandrake CD. (You can try newer versions, but ndiswrapper 0.12 had some issues for myself so, I went back to the original. It works fine.) 2. Get the BCMWL5.inf file and the BCMWL5.sys files from a windows distribution. Copy them both into the same directory. For our purpose it will be /install. 3. Run... ndiswrapper -i /install/BCMWL5.inf. (The files and commands are case sensitive so see how it was copied in with a ls of the /install directory- use your own path here to wherever you copied the file to.) 4. Run... modprobe ndiswrapper 5. Run... iwconfig wlan0 essid ESSID - ESSID = your wireless routers id name here . - eg. DLink 6. Run... iwconfig wlan0 key restriced XXXXXXXXXX - use this if you use WEP - eg. 2E456A874C - if need be for your routeer add more iwconfig lines in this section 7. Run... ifconfig wlan0 XXX.XXX.XXX.XXX up - use your IP here 8. Run... ndiswrapper -m 9. Edit your /etc/rc.d/rc.local and add all of these lines to the end of the file modprobe ndiswrapper iwconfig wlan0 essid ESSID - ESSID = yourroutersidnamehere iwconfig wlan0 key restriced XXXXXXXXXX - use this if you use WEP ifconfig wlan0 XXX.XXX.XXX.XXX up - use your IP here route add -net YYY.YYY.YYY.YYY netmask 255.255.255.0 gw ZZZ.ZZZ.ZZZ.ZZZ dev wlan0 route add -net 0.0.0.0 netmask 0.0.0.0 gw ZZZ.ZZZ.ZZZ.ZZZ dev wlan0 route del -net 0.0.0.0 netmask 0.0.0.0 dev eth0 XXX.XXX.XXX.XXX = your IP you want to assign - eg. 192.168.1.5 YYY.YYY.YYY.YYY = your routers network - last number is always 0 - eg. 192.168.1.0 ZZZ.ZZZ.ZZZ.ZZZ = your routers LAN IP number - used for the gateway - eg. 192.168.1.1 ******************************************************************************** ******************************************************************************** * ******** That's it. Reboot. Should be able to connect to the internet. DHCP was not used for the wireless adapter cause it failed. If you need to connect with the actaul built in ethernet card, you will need to either use a script or manually delete/comment/uncomment the last route command in the rc.local file. Of course make sure you actually configured it. You may then need to also uncomment the route add line above too. It'll slow down requests having the 2 gateway routes. Of course you can just write a shell script or even at a terminal prompt type out the route add/del commands as needed without reboots. Trying to add the card in as an actual loadable module, etc, would intermittently cause a whole bunch of non-working issues, so the adding it to the rc.local file seemed to be the fastest and easiest with the least amount of problems. This should also work on other distros as all of the files needed, used or edited are all the same. That's it. Enjoy!

Had a similar problem on an Acer and a Toshiba, so this may help. Like yourself, dual booting Win 2000 Pro and Mandrake 10.1. It all installed correctly, but would freeze at the Blue Mandrake logo screen. 2 things you may try to verify/do. When booting, hit Shift "I" to do interactive and allow just about everything except perhaps for apmd and acpi (press N for those - can try Y too, may work for you). When you get to dm, press N(o) so you do not go into the graphical display manager. This will drop you to a command prompt. Login as root. Then type gdm, and if this gets you into the Graphical Menu's then go in and login (if setup to not autologin, and let everything generate). Then quit and reboot. Should hopefully work for you then. If the above fails, then when installing (or you can just do an upgrade - recommend re-install as it "should" not affect the dual boot) if your monitor is detected as flat panel, set it to a regular screen (and as it is a notebook be careful here) and set it to 1024x768 @ 60hz (your desktop display can be set to display at a higher setting later in the config screen). Then redo the above steps, if when you changed the monitor setting and did the first boot, it hung.