Firefox will not browse after 2.6.13 kernel compilation

mimithebrain · 11-03-2005, 07:02 PM

nice

I have yet still to learn what modules and drivers can't be enabled at the same time

That caused me to recompile my kernel quite a few times...

sweetnsourbkr · 11-04-2005, 09:32 AM

Took me 3 weeks to get a working kernel and fine tune it. Keep at it.

mimithebrain · 11-04-2005, 09:35 AM

lol! I didn't know that you had to work this hard as well in slackware...

dkpw · 11-04-2005, 10:18 AM

Have you checked your DNS settings?

mimithebrain · 11-04-2005, 11:19 AM

How would DNS be changed by changing kernels? isn't both kernels suppose to use the same configurations?

it's so crazy... it just might work

sweetnsourbkr · 11-04-2005, 03:39 PM

Quote:

Originally posted by mimithebrain
lol! I didn't know that you had to work this hard as well in slackware...

Maybe it's just me.

mimithebrain · 11-04-2005, 03:50 PM

I said the same thing when I installed gentoo, after the 8th or 10th after finally installing KDE and having my ATI card working...

Isn't a odd revision number a bit unstable kernel?

MustangCSA · 11-04-2005, 04:54 PM

Anyone have any suggestions?

mimithebrain · 11-04-2005, 05:04 PM

I have a couple, sorry it's not more elaborated then that.

1 Check the module for your card is loaded
2 Check DNS settings
3 Check lynx has a true connection to the internet, and not just cache
4 use old kernel
5 update to newer kernel

gninnib · 12-06-2005, 01:23 PM

I believe you are having the same problem I had which I resolved by setting this in firefox.

In the address field type: about:config
change 'network.dns.disableIPv6' from false to true.

It appears the new v2.6 of the kernel enables this. You may want to disable the IP6 stuff completely.

gninnib

mimithebrain · 12-06-2005, 05:11 PM

I never used IPv6, so I never enabled it....

I wonder when the "world" is actually going to switch to IPv6?

MustangCSA · 12-06-2005, 09:07 PM

I have to thank you gninnib so much. I have to say that the original problem is no more because I got a new harddrive and installed debian etch and slackware 10.2. But I have just been using the stock 2.4 kernel that comes with slack, so everything is working fine. But I was having the exact same problem in debian etch using a 2.6.12 kernel and it was driving me crazy. Then I saw your reply, tried it and everything works fine now. I'm pretty sure it would have solved the original problem too. Thank you very much.