ocilent1

SOLVED OK guys I have solved my problem, it was the 2.6.8.1 kernel that was the issue. After I finally got around to looking at the syslog, I noticed that the kernel was complaining about compression errors and dropping packets from ppp all the time, so I just simply installed the 2.4.27pre2 kernel that came on the cd and then my modem connection worked again! Crappy 2.6.8.1 kernel, I will have to file a bug report! Thanks for all your help guys!!

OK, I done some more investigation and the problem does not seem to be a gateway issue. here is my ifconfig and route -n output when my connection is up: [root@localhost ocilent1]# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:62 errors:0 dropped:0 overruns:0 frame:0 TX packets:62 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3914 (3.8 Kb) TX bytes:3914 (3.8 Kb) ppp0 Link encap:Point-to-Point Protocol inet addr:203.219.187.5 P-t-P:202.7.190.201 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:11 errors:1 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:186 (186.0 B) TX bytes:192 (192.0 B) [root@localhost ocilent1]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 202.7.190.201 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 202.7.190.201 0.0.0.0 UG 0 0 0 ppp0 This is my resolve.conf file and everything seems OK (the DNS servers are correct) domain tpg.com.au #kppp temp entry # nameserver 203.12.160.35 #entry disabled by kppp # nameserver 203.12.160.36 #entry disabled by kppp # nameserver 203.12.160.35 # ppp temp entry #entry disabled by kppp # nameserver 203.12.160.36 # ppp temp entry #entry disabled by kppp nameserver 203.12.160.35 #kppp temp entry nameserver 203.12.160.36 #kppp temp entry Any more ideas anybody?? Before you ask, no I have not got a firewall running as I can't even get internet access, so a firewall is pretty much usless at the moment!! Cheers! OC

Thanks for your quick response and suggestions DragonMage! :D I will try out your suggestions when I get home tonight! And let you know how I go! BTW, has anybody around here noticed that MDK 10.1 CE iso's are starting to appear on mirrors? eg. http://mirror.pacific.net.au/linux/Mandrak.../iso/10.1/i586/ Cheers! OC

OK here's my problem. I am using MDK 10.1 CE and have a external dial up modem. Now when using KPPP, the modem establishes a connection to my isp normally. However, if I then try to browse the web, check e-mail etc nothing can be found. I can't ping my ISP or anybody else in the world! So I thought there was a problem in my resolve.conf file, but nope, both the DNS addresses for my ISP are in there upon connection to the net. So whats up?? Is there something I am missing? What else should I check? I have never encountered this isssue before using mandrake over the last 4 years! Cheers! OC

I did a fresh install of MDK 10 community on a spare partition I had and booted with the 2.4 kernel. No probs!!! So it would seem that when upgrading by syncing with the current community tree, something bad has happened. I will give you a dmesg and an lspci as soon as I reboot!! :-)

I have been running MDK 10 community (fully updated) for a few months using the 2.6 kernel and have been mostly happy. The main problem I have with MDK 10, is that I don't think the 2.6 kernel is playing nicely with my external modem. (I have never had any issues with this modem in linux before, I have used linux for about 5 years, and this modem has always worked well) So, I wanted to try the 2.4 kernel that is shipped with MDK 10, to see if my modem would work normally again (as the modem works perfectly fine under PCLinuxOS). However, when I installed the lastest 2.4 kernel from Mandrake onto the system, the boot process stops at: Starting system logger: It never gets past this point. I then rebooted into 2.6 disabled the syslog service, then rebooted again with the 2.4 kernel. The boot process then stops at starting alsa: To cut a long story short, I had to disable hardrake,syslog,alsa,cups and stop X from starting to even get the system to a login prompt. Any ideas whats wrong?? I have tried the original 2.4 kernel that came with community, the latest updated 2.4 kernel and the latest 2.4tmb kernel, and they all exhibit the same behaviour!! Cheers!! ocilent1

Hey thanks for all your input here aRTee. I never knew that you could recover your previously partition tables!!! You learn something new everyday, just wish I knew that before I re-installed everything. Now, off to find that disk....... B) I must say though,overall I am very impressed with Mandy 10.0 (yes even with this nasty partition table bug). I am certainly not going to let a bug like that drive me away from linux, it would take alot more!!! And to all the guys complaining about this bug, you should remember that this is not the final Mandrake 10.0 version, so you should be expecting some bugs, although I must admit, maybe not quite as nasty as this one. If you want a rock solid, stable and bugless version, wait to the 'Mandrake 10.0 Official' version comes out. Cheers!!!

Yes I also got stung with this bug and yes it's a really bad one!! I can't believe there is not more fuss made over this bug!! Going into my bios and setting it to 'LBA' DID NOT fix the problem for me as it was already set on 'LBA'. It seems to have worked for some others though. You are correct in saying that it is the MDK 10 partitioning tool that ruins the partition table. *****WHATEVER YOU DO, DON'T WRITE TO THE PARTITION TABLE WITH MDK 10.0. or it will corrupt it!! For me, once the table was corrupted I had to wipe the table to get windows to install/boot again, and take note, wiping the partition table meant that I lost everything on that hard drive. Just re-installing windows did not make the problem dissappear. All I kept getting was a linking cursor! Many people have this same issue see below for links: http://www.mandrakeusers.org/index.php?sho...topic=12218&hl= http://www.linuxquestions.org/questions/sh...15&pagenumber=1 The only way I could get windwos working was the use the NASTY command: dd if=/dev/zero of=/dev/hda bs=1000 count=1000 This enabled me to re-install everything again, this time I use MDK 9.2 to do all my partition first, then installed WinXP, then MDK 10.0 and everything was OK this time!! ***UPDATE*** Check out this bug report, it may help solve the problem for your as it is now apparantly resolved. https://qa.mandrakesoft.com/show_bug.cgi?id=7959

Just thought I might tell you guys that LG has updated their firmware and released instructions on how to bring your CDROM 'drive back from the dead' once Mandrake 9.2 has had it's way with it. Get eveything you require at the Lg Service website. 1) Firstly, click on Product Support 2) Then click on Device Driver 3) Finally, click on CD-ROM Then follwow the instuctions according to the model of your drive.