|
ubuntu 12.04 internet
|
|
Member
|
6. March 2012 @ 10:48 |
Link to this message
|
|
so iv been testing ubuntu 12.04 on my netbook, and everything seems to be going great. all except one thing. the Internet seems to work fine when on battery power, however if I plug the cable in to charge, the Internet does not work at all. is this a bug, or is this just some small configuration issues I can solve?
|
|
Advertisement
|
 |
|
|
Member
|
17. March 2012 @ 06:35 |
Link to this message
|
|
hi, i dont think you understand what i mean. i am already using ubuntu, however the most recent one that will be coming out is in april and i am having issues using the internet, whilst having the charger plugged in.
|
Member
|
26. March 2012 @ 08:00 |
Link to this message
|
|
im using 11.04 at the moment, i have no issues with the internet, i have the power cable plugged in and the internet is fine, however if i use 12.04, the internet will only work with the power cable out. maybe configuration?
|
|
ps355528
Senior Member
|
29. March 2012 @ 19:28 |
Link to this message
|
|
I think you might have a fruitful time looking through the network-manager and battery monitor configs, and how the applets are assigned to the system tray o wherever. What desktop are you running.. and have you tried others like lxde/xfce etc to see if the problem is common to all?
|
Member
|
1. April 2012 @ 06:00 |
Link to this message
|
i had the same problem with 11.10 and yes i did use other desktops and the outcome was the same, however i will try with the configurations and hopefully that will sort things out
|
Member
|
3. April 2012 @ 20:41 |
Link to this message
|
|
i tried using dconf but i have no idea what i am looking at. iv looked through the power configurations, but nothing relevant there. could you possibly tell me where to look? thanks for the help :)
|
|
ps355528
Senior Member
|
6. April 2012 @ 16:14 |
Link to this message
|
|
As I'm running Arch I don't think my system is anywhere near enough to yours to have much of an idea what may be wrong even if I saw it... including the fact that I don't have this problem and so can't duplicate it. It's not just dconf.. it's rc.d and rcS.d and any desktop.conf files.. look for things being loaded twice I would guess. There are a few threads on the network-manager applet being a bit touchy.
Try ask ubuntu or the ubuntu forums, somebody must know..
p.s .. browsers suddenly crashing?.. flashplugin-nonfree update is really broken.. replace with a 10.xxx from adobe archive manually ;)
|
Member
|
6. April 2012 @ 22:02 |
Link to this message
|
|
nothing is crashing, no browsers, no plugins nothing, just no internet :( i guess il have to check ask ubuntu. by the way, what is arch like? any benefits of using it over a debian based distro?
|
|
ps355528
Senior Member
|
7. April 2012 @ 10:19 |
Link to this message
|
|
Arch is pretty hardcore, but because it's bloat free it's blazing fast on old hardware.... but... you really do need to know what you are doing in case things don't work.
I still think your main problem is caused by running upstream testing version. Chances are a clean install (apt-get remove --purge network-manager battery-monitor) would do the trick, reinstalling them again afterwards. I managd to get 2 network monitor applets to load and had to take the one out of rc.d as network manager #comment it out to see# is handled by desktop startup ;) .. maybe??
Wonder if Mick has any thoughts on this one.
This message has been edited since posting. Last time this message was edited on 7. April 2012 @ 10:21
|
|
Schmick
Junior Member
|
8. April 2012 @ 05:21 |
Link to this message
|
|
Maybe acpid is doing something screwy with the on/off battery events?
|
|
Schmick
Junior Member
|
8. April 2012 @ 05:39 |
Link to this message
|
|
It is probably also worth adding that since you're playing with a beta version of Ubuntu, you should be reporting the errors to the Ubuntu devs so that they can fix it for the release version.
I personally find Arch fun, I actually enjoy having to put all the pieces together myself and getting myself out of trouble when something goes wrong (happening quite a bit now that I've got an ATI graphics card...). It is a steep learning curve, if you do want to have a go at it, I'd recommend trying it on a computer you don't need to rely on and can spend a week or two experimenting - you'll almost certainly find yourself formatting and reinstalling! But you WILL learn a lot about what actually makes up the operating system as a whole.
^ PEBKAC ^
|
|
ps355528
Senior Member
|
8. April 2012 @ 07:54 |
Link to this message
|
My arch lappy has an old lump of ati hardware.. it refuses to work with either of the "proper" drivers, but it's sweet with the vesa chunk so I'm happy.. except AGAIN with flash which latest update caused instant browser exits stage left (running even) .. at least with arch it's so very easy to try different versions until one works.. WHY have we internet users allowed adobe to have sole control of a damn player?.. proprietary crap has no place on OUR internet!!!
My big production pile runs Sabayon 7 - 64 these days, debian betrayed us by going gnome3 abortion by default with FAR too many mono dependencies for my liking.. when you need something solid trust Sabayon ;) Spot the linux user?.. Arch, ubuntu (yuck) Anubis (pretty cool but out of date) Sabayon and Slackware (server) messed with pretty much every day.. Just need a fedora box for the full house of package managers :) .. antique lappy runs BeOS5-PE (exotic enough for ya?)
I tested out the ubuntu 3.0.0 kernel (trying to solve the current bastard adobe shenannagins) and have to report that it's broken the wireless on this otherwise working lappy.. If it wasn't an experimental patched kernel trying to fix what turns out to be an unrelated flashplayer fatal error then I would be all over the ubuntu forums calling people unpleasant names (like crass amateurs who test nothing before release to main repos deserve!!) like a rash I promise..
This message has been edited since posting. Last time this message was edited on 8. April 2012 @ 08:07
|
Member
|
11. April 2012 @ 13:35 |
Link to this message
|
|
well i did a clean install of the ubuntu 12.04 daily build instead, of course nothing has changed, i will try and remove the battery-monitor and network-manager and see if anything works. and what would i do about acpid?
|
|
Schmick
Junior Member
|
12. April 2012 @ 01:22 |
Link to this message
|
Have a look in /etc/acpid/events/ to see if there is anything related to battery or ac_adapter event handlers. http://packages.ubuntu.com/precise/acpid would suggest that there isn't anything to blame there though. So probably not the cause in this case.
Have you tried a different desktop manager and/or network manager? Maybe try to see if the problem still exists if you use XFCE, or use Wicd instead of NetworkManager. Could be Gnome3 trying to be too smart for it's own good.
^ PEBKAC ^
|
Member
|
12. April 2012 @ 13:31 |
Link to this message
|
|
i have tried using xubuntu, and the same thing applies. therfore it is not an issue of which desktop environment i am using. i checked acpid and i dont think anything is wrong there, but then again i dont know what i am looking at. i reckon it is the kernel version. if i use any distro that uses the kernel 3.0 or later, i have a problem with the internet. such as ubuntu 11.10 and 12.04.
|
|
Schmick
Junior Member
|
12. April 2012 @ 22:12 |
Link to this message
|
|
What make and model netbook are you using? There might be someone out in the interwebs who has identified and documented what the problem is.
^ PEBKAC ^
|
Member
|
14. April 2012 @ 07:29 |
Link to this message
|
the netbook is a Packard bell dot se-710uk. all the drivers work out of the box, and everything is running fine. it connects to the network okay and i made sure nothing has gone wrong. so it is definitely a software issue.
|
|
ps355528
Senior Member
|
14. April 2012 @ 20:13 |
Link to this message
|
are you sure?.. could easily be a module conflict. I tried the 3.0.0 kernel on ubuntu and it broke the wireless connectivity which works just fine on the last 2.6 kernels. I think there is a wider problem here than ubuntu are admitting.. Everybody is reporting wireless and networking broken with the 3.0.x kernels, BUT.. you can always backport an older one with no real problems.. This lappy is rather "development and debug" setup.. as you can tell..
title Ubuntu 10.04.4 LTS, kernel 3.0.0-18-generic
root (hd0,0)
kernel /boot/vmlinuz-3.0.0-18-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-3.0.0-18-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 3.0.0-18-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-3.0.0-18-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-3.0.0-18-generic
title Ubuntu 10.04.4 LTS, kernel 2.6.32-40-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-40-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-2.6.32-40-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 2.6.32-40-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-40-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-2.6.32-40-generic
title Ubuntu 10.04.4 LTS, kernel 2.6.32-39-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-39-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-2.6.32-39-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 2.6.32-39-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-39-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-2.6.32-39-generic
title Ubuntu 10.04.4 LTS, kernel 2.6.32-38-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-38-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-2.6.32-38-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 2.6.32-38-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-38-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-2.6.32-38-generic
title Ubuntu 10.04.4 LTS, kernel 2.6.32-37-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-37-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-2.6.32-37-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 2.6.32-37-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-37-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-2.6.32-37-generic
title Ubuntu 10.04.4 LTS, kernel 2.6.32-36-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-36-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-2.6.32-36-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 2.6.32-36-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-36-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-2.6.32-36-generic
title Ubuntu 10.04.4 LTS, kernel 2.6.32-35-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-35-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-2.6.32-35-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 2.6.32-35-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-35-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-2.6.32-35-generic
title Ubuntu 10.04.4 LTS, kernel 2.6.32-34-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-34-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-2.6.32-34-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 2.6.32-34-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-34-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-2.6.32-34-generic
title Ubuntu 10.04.4 LTS, kernel 2.6.32-33-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-33-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-2.6.32-33-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 2.6.32-33-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-33-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-2.6.32-33-generic
title Ubuntu 10.04.4 LTS, kernel 2.6.24-29-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-29-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro quiet splash
initrd /boot/initrd.img-2.6.24-29-generic
quiet
title Ubuntu 10.04.4 LTS, kernel 2.6.24-29-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-29-generic root=UUID=f5a94f83-b526-4199-999c-846b4de50d4e ro single
initrd /boot/initrd.img-2.6.24-29-generic
title Ubuntu 10.04.4 LTS, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet
This message has been edited since posting. Last time this message was edited on 14. April 2012 @ 20:17
|
Member
|
15. April 2012 @ 08:30 |
Link to this message
|
|
it could be the ubuntu kernel, i used fedora 17 alpha and it seems to work okay.
|
|
ps355528
Senior Member
|
19. April 2012 @ 10:35 |
Link to this message
|
It is.. lots of problems with the ubuntu implementation of the 3.x kernels.. Heres a thought if you like a challenge. My Sabayon 7 (3.2 kernel) runs flawlessly so how about dragging in the sources from the Sabayon repos and compiling it up against the ubuntu libs and headers and seeing what happens?
I have had to revert to a 2.6 kernel on this to get any sort of sanity from both browsers and wireless.. it feels like a cumulative little fault has been growing. Afterdawn has been causing random browser crashes on ubuntu for a while, the later the kernel and flashplayer combination the worse it gets....... Take heart.. we are not alone..
https://www.google.co.uk/#hl=en&safe=of...iw=1006&bih=638
I only got interested in the kernel problems due to a fatal browser problem which seems to be caused by that stupid flashplayer blob. Not quite solved yet with ubuntu, but I did fix it on my Arch lappy where things are a lot more standalone.
|
Member
|
19. April 2012 @ 14:24 |
Link to this message
|
|
i think your right, but i have been using distros such as mageia 2 and fedora 17, which both use kernel 3.3, with 3.3 both the computers i run dont have any problems. i will try ubuntu 12.04 but using the kernel ppa or manually upgrading the kernel to 3.3 see if anything else happens
|
Member
|
22. April 2012 @ 05:23 |
Link to this message
|
|
tried ubuntu 12.04 with kernel 3.3, no luck so switching to fedora 17 when released.
|
|
ps355528
Senior Member
|
24. April 2012 @ 08:03 |
Link to this message
|
|
I found something interesting.. it looks like they have been buggering about in lots of different places.. wpa_supplicant which used to run from /var/run/blahblahblah now just runs from /run/ .. etc
It's a really strange problem because in actual fact it's breaking all networking.. wired included though it continues to work mostly.. With a dongle there is obviously something else going on.. I found I could set the link to "up" and while it demanded it was "down" I could scan the local networks and see them all.. but on trying to connect there was a "no carrier" timeout.
Hres a thought.. no networks will be initialised when running wicd or another network manager unless it's called by an applet.. rc.conf is interesting (debian variants use symlinks to rc.d) as when loading the "network" daemon wired is fine, but that then messes up the "networkmanager" daemon.. the fault seems to be in networkmanager (and friends) rather than the applet, but that would explain the applet not loading.. circular dependency problem?
I have reverted my Arch lappy right back to 3.0.1 and the problem remains (25/6 it began with some unfathomable change to networkmanager and wpa_supplicant which were both woring fine)
I think somewhere some arses need a good swift kick.. I'm getting pretty sick and tired of this new "change for the sake of it" mentality from the kernel devs, not to mention the obvious complete lack of any upstream testing .. because surely breaking wifi connectivity is a pretty BIG ISSUE not to notice before pushing something out into "core".. What happened to "if it works leave it be" .. they haven't messed about with cups in years (yeah yeah.. we bloody hate that antiquated printer management system, but it works and we are used to it.. maybe being owned by the unix people stops the cavalier buggering about on a whim we have seen recently across most distros.. ) I wonder why fedora isn't broken.. oh yes.. it's "free" redhat.. and who employs 90% of the kernel devs.. oh aye.. redhat!!.. Something smells.. but I'm not quite sure what..
|
Member
|
24. April 2012 @ 09:59 |
Link to this message
|
|
you have a good point there, but iv completely given up now. fedora 16/17 work fine and so i will stick with fedora in the future as well. seems more stable to me anyway. thanks for everyones help.
|
|
Advertisement
|
|
|
|
ps355528
Senior Member
|
30. June 2012 @ 21:17 |
Link to this message
|
would you believe it's STILL broken? .. this is getting beyond a joke. I'm running puppy on my netbooks and sabayon on my big iron.. I had to give up with arch as I rely on that little old dell as my travel machine.. and it kept breaking too often, usually the wireless!! but occasionally the desktop too.
|
