[gentoo-user] Nvidia drivers and KDE problem
Howdy, I been letting portage upgrade nvidia drivers as usual. Thing is, the last two or three drivers seems to cause a issue. First, versions that cause the issue: =x11-drivers/nvidia-drivers-319.12 =x11-drivers/nvidia-drivers-319.17 =x11-drivers/nvidia-drivers-319.23 I'm currently using this one which works fine: x11-drivers/nvidia-drivers-313.30 This is KDE info: [IP-] [ ] kde-base/kdelibs-4.10.3-r2 Video card info: 01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT 220] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device 069a Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at fb00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at de00 (64-bit, prefetchable) [size=32M] I/O ports at ef00 [size=128] [virtual] Expansion ROM at d000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nvidia Kernel modules: nvidia The problem. After I am logged into KDE for a good while, like several hours to maybe a day or so, the kicker thingy at the bottom locks up tight. I can't switch desktops, clock stops working, can't click the K menu thingy either. Everything in the kicker thingy is dead as a door nail. I can switch desktops with the keyboard and everything else works in KDE just fine. I can also switch to a console too. Killing X and restarting it fixes it, xdm restart in my case. I don't have to reload drivers or restart the system. I do go back and downgrade the drivers after testing it. So, is this a nvidia bug, KDE bug or is it something else? Since it works when I go back a version of nvidia, it looks like nvidia. Think is, it only affects KDE and nothing else. Is it possible that my card is not supposed to use the 319.* series of drivers? The versions that don't work are all 319.* series. Thoughts? Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Re: [gentoo-user] Nvidia drivers and KDE problem
On 26/05/2013 11:12, Dale wrote: Howdy, I been letting portage upgrade nvidia drivers as usual. Thing is, the last two or three drivers seems to cause a issue. First, versions that cause the issue: =x11-drivers/nvidia-drivers-319.12 =x11-drivers/nvidia-drivers-319.17 =x11-drivers/nvidia-drivers-319.23 I'm currently using this one which works fine: x11-drivers/nvidia-drivers-313.30 This is KDE info: [IP-] [ ] kde-base/kdelibs-4.10.3-r2 Video card info: 01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT 220] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device 069a Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at fb00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at de00 (64-bit, prefetchable) [size=32M] I/O ports at ef00 [size=128] [virtual] Expansion ROM at d000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nvidia Kernel modules: nvidia The problem. After I am logged into KDE for a good while, like several hours to maybe a day or so, the kicker thingy at the bottom locks up tight. I can't switch desktops, clock stops working, can't click the K menu thingy either. Everything in the kicker thingy is dead as a door nail. I can switch desktops with the keyboard and everything else works in KDE just fine. I can also switch to a console too. Killing X and restarting it fixes it, xdm restart in my case. I don't have to reload drivers or restart the system. I do go back and downgrade the drivers after testing it. So, is this a nvidia bug, KDE bug or is it something else? Since it works when I go back a version of nvidia, it looks like nvidia. Think is, it only affects KDE and nothing else. Is it possible that my card is not supposed to use the 319.* series of drivers? The versions that don't work are all 319.* series. I get a similar issue, my video card is an ATI and I use the radeon drivers. Same symptom as you - plasma stops updating it's widgets like clocks and stops responding to the mouse. Keyboard works. In my case, it's usually linked to nfs and smb mounts that went away (eg, if I forget to umount my NFS media server at home and go to work) which indicates a blocking issue somehow. I've read many reports on the internet that krunner is somehow involved, so that might be a good starting point for investigation. krunner is the thing you get in KDE when typing Alt-F2 -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Nvidia drivers and KDE problem
Alan McKinnon wrote: I get a similar issue, my video card is an ATI and I use the radeon drivers. Same symptom as you - plasma stops updating it's widgets like clocks and stops responding to the mouse. Keyboard works. In my case, it's usually linked to nfs and smb mounts that went away (eg, if I forget to umount my NFS media server at home and go to work) which indicates a blocking issue somehow. I've read many reports on the internet that krunner is somehow involved, so that might be a good starting point for investigation. krunner is the thing you get in KDE when typing Alt-F2 So this may not be a nvidia issue at all since you get the same with a ATI card. Right? What package provides the kicker thingy? I think in KDE3 it was called kicker but it appears to have changed to something else. Is that krunner that has it now? Thanks. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Re: [gentoo-user] Nvidia drivers and KDE problem
On 26/05/2013 11:51, Dale wrote: Alan McKinnon wrote: I get a similar issue, my video card is an ATI and I use the radeon drivers. Same symptom as you - plasma stops updating it's widgets like clocks and stops responding to the mouse. Keyboard works. In my case, it's usually linked to nfs and smb mounts that went away (eg, if I forget to umount my NFS media server at home and go to work) which indicates a blocking issue somehow. I've read many reports on the internet that krunner is somehow involved, so that might be a good starting point for investigation. krunner is the thing you get in KDE when typing Alt-F2 So this may not be a nvidia issue at all since you get the same with a ATI card. Right? yes What package provides the kicker thingy? I think in KDE3 it was called kicker but it appears to have changed to something else. Is that krunner that has it now? Maybe it's time you used the thingy suffix a little less and the real names of things a little more :-) What thing are you asking about? The panel that is usually at the bottom and holds the plasma widgets? Or the thin popup you get with Alt-F2? The panel is called plasma-desktop and comes from kde-base/plasma-workspace The popup is krunner and comes from kde-base/krunner I doubt very much it's a real bug as such in either KDE app (although the fix might go in there). It looks much more to me like a side-effect of IO blocking - two or more apps are trying to get something done and unexpectedly are not getting answers, so they hang around waiting in the doorway and get get in the way of everything else. And just for fun, video drivers are also trying to get in on the act as they have to deal with mouse pointer repaints... Debugging this one is going to be fun (for peculiar definitions of fun) -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Nvidia drivers and KDE problem
Alan McKinnon wrote: On 26/05/2013 11:51, Dale wrote: What package provides the kicker thingy? I think in KDE3 it was called kicker but it appears to have changed to something else. Is that krunner that has it now? Maybe it's time you used the thingy suffix a little less and the real names of things a little more :-) What thing are you asking about? The panel that is usually at the bottom and holds the plasma widgets? Or the thin popup you get with Alt-F2? The panel is called plasma-desktop and comes from kde-base/plasma-workspace The popup is krunner and comes from kde-base/krunner I doubt very much it's a real bug as such in either KDE app (although the fix might go in there). It looks much more to me like a side-effect of IO blocking - two or more apps are trying to get something done and unexpectedly are not getting answers, so they hang around waiting in the doorway and get get in the way of everything else. And just for fun, video drivers are also trying to get in on the act as they have to deal with mouse pointer repaints... Debugging this one is going to be fun (for peculiar definitions of fun) The thingy is the thing at the bottom where I can switch desktops, click the K menu and where my clock is. I think it was called Kicker in KDE3. KDE4 seems to have changed it but not sure what the new name is. I hope they fix this thing soon. If they remove the driver from the tree, I'm in a bit of a pickle. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Re: [gentoo-user] Nvidia drivers and KDE problem
On 26/05/2013 13:03, Dale wrote: Alan McKinnon wrote: On 26/05/2013 11:51, Dale wrote: What package provides the kicker thingy? I think in KDE3 it was called kicker but it appears to have changed to something else. Is that krunner that has it now? Maybe it's time you used the thingy suffix a little less and the real names of things a little more :-) What thing are you asking about? The panel that is usually at the bottom and holds the plasma widgets? Or the thin popup you get with Alt-F2? The panel is called plasma-desktop and comes from kde-base/plasma-workspace The popup is krunner and comes from kde-base/krunner I doubt very much it's a real bug as such in either KDE app (although the fix might go in there). It looks much more to me like a side-effect of IO blocking - two or more apps are trying to get something done and unexpectedly are not getting answers, so they hang around waiting in the doorway and get get in the way of everything else. And just for fun, video drivers are also trying to get in on the act as they have to deal with mouse pointer repaints... Debugging this one is going to be fun (for peculiar definitions of fun) The thingy is the thing at the bottom where I can switch desktops, click the K menu and where my clock is. I think it was called Kicker in KDE3. KDE4 seems to have changed it but not sure what the new name is. It's a plasma widget called a panel, the only useful thing it does is to be a container for other widgets that do useful stuff. The panel is started by plasma-desktop as one of the standard widgets it manages. The idea is to give you stuff on the screen that looks more or less like a familiar desktop. Plasma can do other things and give you completely different layouts; like for instance not giving you a panel at all. This would be useful on a phone with small screen The whole thing is heavily event based and has to react to a bucket load of system events being generated such as what the mouse is doing. There's a fantastic number of ways this could go wrong, some might be plasma's fault, some might be faults that happen to plasma I hope they fix this thing soon. If they remove the driver from the tree, I'm in a bit of a pickle. No, you won't be. You have the ebuild right now, copy it to your overlay and remove becomes something that will not happen -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Re: Nvidia drivers and KDE problem
On 26/05/13 12:12, Dale wrote: [...] The problem. After I am logged into KDE for a good while, like several hours to maybe a day or so, the kicker thingy at the bottom locks up tight. I can't switch desktops, clock stops working, can't click the K menu thingy either. Everything in the kicker thingy is dead as a door nail. I can switch desktops with the keyboard and everything else works in KDE just fine. I can also switch to a console too. Killing X and restarting it fixes it, xdm restart in my case. I don't have to reload drivers or restart the system. Hmm, something similar happens here sometimes. But not as severe. It usually happens when I close many windows rapidly in succession, but it's not permanent. The panel becomes responsive again after 10 seconds or so. I'm also on latest nvidia-drivers, but it was happening with older versions too. I happened very rarely though, so it didn't bother me enough to go investigating. Here's something to try out: when it happens, hit the shortcut on your keyboard that temporarily suspends desktop effects. I don't remember what the default shortcut for it is, as I've changed it, but it's shown and configured in the General tab of Desktop Effects in System Settings. See if hitting the shortcut twice to disable and then re-enable desktop effects fixes it.
Re: [gentoo-user] Nvidia drivers and KDE problem
Alan McKinnon wrote: On 26/05/2013 13:03, Dale wrote: Alan McKinnon wrote: On 26/05/2013 11:51, Dale wrote: What package provides the kicker thingy? I think in KDE3 it was called kicker but it appears to have changed to something else. Is that krunner that has it now? Maybe it's time you used the thingy suffix a little less and the real names of things a little more :-) What thing are you asking about? The panel that is usually at the bottom and holds the plasma widgets? Or the thin popup you get with Alt-F2? The panel is called plasma-desktop and comes from kde-base/plasma-workspace The popup is krunner and comes from kde-base/krunner I doubt very much it's a real bug as such in either KDE app (although the fix might go in there). It looks much more to me like a side-effect of IO blocking - two or more apps are trying to get something done and unexpectedly are not getting answers, so they hang around waiting in the doorway and get get in the way of everything else. And just for fun, video drivers are also trying to get in on the act as they have to deal with mouse pointer repaints... Debugging this one is going to be fun (for peculiar definitions of fun) The thingy is the thing at the bottom where I can switch desktops, click the K menu and where my clock is. I think it was called Kicker in KDE3. KDE4 seems to have changed it but not sure what the new name is. It's a plasma widget called a panel, the only useful thing it does is to be a container for other widgets that do useful stuff. The panel is started by plasma-desktop as one of the standard widgets it manages. The idea is to give you stuff on the screen that looks more or less like a familiar desktop. Plasma can do other things and give you completely different layouts; like for instance not giving you a panel at all. This would be useful on a phone with small screen The whole thing is heavily event based and has to react to a bucket load of system events being generated such as what the mouse is doing. There's a fantastic number of ways this could go wrong, some might be plasma's fault, some might be faults that happen to plasma I'll try to remember to call it a panel thingy then. ROFL I hope they fix this thing soon. If they remove the driver from the tree, I'm in a bit of a pickle. No, you won't be. You have the ebuild right now, copy it to your overlay and remove becomes something that will not happen Last time I did that, it didn't work out well. Actually, it just plain didn't work. May as well tell it like it is. ;-) I'll save a copy just in case. Cross that bridge when I get there I guess. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Re: [gentoo-user] Re: Nvidia drivers and KDE problem
Nikos Chantziaras wrote: On 26/05/13 12:12, Dale wrote: [...] The problem. After I am logged into KDE for a good while, like several hours to maybe a day or so, the kicker thingy at the bottom locks up tight. I can't switch desktops, clock stops working, can't click the K menu thingy either. Everything in the kicker thingy is dead as a door nail. I can switch desktops with the keyboard and everything else works in KDE just fine. I can also switch to a console too. Killing X and restarting it fixes it, xdm restart in my case. I don't have to reload drivers or restart the system. Hmm, something similar happens here sometimes. But not as severe. It usually happens when I close many windows rapidly in succession, but it's not permanent. The panel becomes responsive again after 10 seconds or so. I'm also on latest nvidia-drivers, but it was happening with older versions too. I happened very rarely though, so it didn't bother me enough to go investigating. Here's something to try out: when it happens, hit the shortcut on your keyboard that temporarily suspends desktop effects. I don't remember what the default shortcut for it is, as I've changed it, but it's shown and configured in the General tab of Desktop Effects in System Settings. See if hitting the shortcut twice to disable and then re-enable desktop effects fixes it. Mine wasn't set at all. I set it to ctrl alt F12. Now to remember that and try it. Also, I'm using the good nvidia version right now so it won't happen right now. Maybe on the next upgrade. :/ At least I know it is not just me. So far, two people have had this issue to some degree. Thanks. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
[gentoo-user] Re: Nvidia drivers and KDE problem
On 26/05/13 15:14, Dale wrote: Nikos Chantziaras wrote: On 26/05/13 12:12, Dale wrote: [...] The problem. After I am logged into KDE for a good while, like several hours to maybe a day or so, the kicker thingy at the bottom locks up tight. I can't switch desktops, clock stops working, can't click the K menu thingy either. Everything in the kicker thingy is dead as a door nail. I can switch desktops with the keyboard and everything else works in KDE just fine. I can also switch to a console too. Killing X and restarting it fixes it, xdm restart in my case. I don't have to reload drivers or restart the system. Hmm, something similar happens here sometimes. But not as severe. It usually happens when I close many windows rapidly in succession, but it's not permanent. The panel becomes responsive again after 10 seconds or so. I'm also on latest nvidia-drivers, but it was happening with older versions too. I happened very rarely though, so it didn't bother me enough to go investigating. Here's something to try out: when it happens, hit the shortcut on your keyboard that temporarily suspends desktop effects. I don't remember what the default shortcut for it is, as I've changed it, but it's shown and configured in the General tab of Desktop Effects in System Settings. See if hitting the shortcut twice to disable and then re-enable desktop effects fixes it. Mine wasn't set at all. I set it to ctrl alt F12. Now to remember that and try it. Also, I'm using the good nvidia version right now so it won't happen right now. Maybe on the next upgrade. :/ Ctrl+Alt+F12 will probably be intercepted by the X server and switch to virtual console 12. Try something like Ctrl+Shift+F12 instead (I've set mine to the My Computer button on the keyboard though, since that one's useless otherwise.)
[gentoo-user] Re: IP Load Sharing - Per Packet Load Balancing (Linux router)
Any different if the links are VDSL? I have little experience in working with DSL based connections, and was wondering what was possible in terms or bridging/bonding etc.. if anything. N. On 5/25/13, Nick Khamis sym...@gmail.com wrote: I missed out some crusial info in my last email. As mentioned this would be two separate DSL services, connected using separate bridges. I think I am describing more of a link aggregation or bonding Also assuming that the service providers support bonding of the links N. On 5/25/13, Nick Khamis sym...@gmail.com wrote: Hello everyone, I am looking to put together a linux router for small business, and was wondering if there was anything the suite (using quagga etc..) that would allow for load balancing of regular dsl links. Kind of like cisco with fast ethernet 0,1 and ip sef. If outgoing and incoming traffic could be balanced, it would be great! Kind Regards, Nick.
Re: [gentoo-user] IP Load Sharing - Per Packet Load Balancing (Linux router)
On 25 May 2013, at 22:26, Nick Khamis wrote: ... As mentioned this would be two separate DSL services, connected using separate bridges. I think I am describing more of a link aggregation or bonding Also assuming that the service providers support bonding of the links…. Here in the UK this is a somewhat common thing - there are a number of ISPs which offer bonded xDSL services. It's certainly possible to use a Linux router to manage such a connection, although I don't know the details. http://www22.brinkster.com/findall/bondedcd.html http://www.automatedhome.co.uk/reviews/adsl-bonding-how-to-and-review.html Stroller.
Re: [gentoo-user] Nvidia drivers and KDE problem
Am 26.05.2013 11:12, schrieb Dale: Howdy, I been letting portage upgrade nvidia drivers as usual. Thing is, the last two or three drivers seems to cause a issue. First, versions that cause the issue: =x11-drivers/nvidia-drivers-319.12 =x11-drivers/nvidia-drivers-319.17 =x11-drivers/nvidia-drivers-319.23 I'm currently using this one which works fine: x11-drivers/nvidia-drivers-313.30 This is KDE info: [IP-] [ ] kde-base/kdelibs-4.10.3-r2 Video card info: 01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT 220] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device 069a Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at fb00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at de00 (64-bit, prefetchable) [size=32M] I/O ports at ef00 [size=128] [virtual] Expansion ROM at d000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nvidia Kernel modules: nvidia The problem. After I am logged into KDE for a good while, like several hours to maybe a day or so, the kicker thingy at the bottom locks up tight. I can't switch desktops, clock stops working, can't click the K menu thingy either. Everything in the kicker thingy is dead as a door nail. I can switch desktops with the keyboard and everything else works in KDE just fine. I can also switch to a console too. Killing X and restarting it fixes it, xdm restart in my case. I don't have to reload drivers or restart the system. I do go back and downgrade the drivers after testing it. So, is this a nvidia bug, KDE bug or is it something else? Since it works when I go back a version of nvidia, it looks like nvidia. Think is, it only affects KDE and nothing else. Is it possible that my card is not supposed to use the 319.* series of drivers? The versions that don't work are all 319.* series. Thoughts? Dale :-) :-) next time as root do: killall -9 krunner killall -9 plasma-desktop
Re: [gentoo-user] IP Load Sharing - Per Packet Load Balancing (Linux router)
On 25 May 2013, at 22:26, Nick Khamis wrote: ... As mentioned this would be two separate DSL services, connected using separate bridges. I think I am describing more of a link aggregation or bonding Also assuming that the service providers support bonding of the links . Here in the UK this is a somewhat common thing - there are a number of ISPs which offer bonded xDSL services. It's certainly possible to use a Linux router to manage such a connection, although I don't know the details. http://www22.brinkster.com/findall/bondedcd.html http://www.automatedhome.co.uk/reviews/adsl-bonding-how-to-and-revie w.html Bonding network devices together is quite simple, but it needs to be configured on both ends. In other words, to merge 2 DSL-connections together using bonding, you need to get both from the same ISP and the ISP would need to support it on their end. If bonding can't be done on the ISP-side, you can use seperate load-balancing/failover using other techniques. -- Joost
Re: [gentoo-user] IP Load Sharing - Per Packet Load Balancing (Linux router)
On Sunday 26 May 2013 22:35:14 J. Roeleveld wrote: On 25 May 2013, at 22:26, Nick Khamis wrote: ... As mentioned this would be two separate DSL services, connected using separate bridges. I think I am describing more of a link aggregation or bonding Also assuming that the service providers support bonding of the links . Here in the UK this is a somewhat common thing - there are a number of ISPs which offer bonded xDSL services. It's certainly possible to use a Linux router to manage such a connection, although I don't know the details. http://www22.brinkster.com/findall/bondedcd.html http://www.automatedhome.co.uk/reviews/adsl-bonding-how-to-and-revie w.html Bonding network devices together is quite simple, but it needs to be configured on both ends. In other words, to merge 2 DSL-connections together using bonding, you need to get both from the same ISP and the ISP would need to support it on their end. If bonding can't be done on the ISP-side, you can use seperate load-balancing/failover using other techniques. There's different ways of going about it, without or without MLPPP, depending on what your ISP offers: http://wiki.aa.org.uk/index.php/Linux_upload_bonding_using_multipath_routing http://wiki.aa.org.uk/index.php/Linux_upload_bonding_using_policy_routing It used to be the case that Cisco 1800/2800 routers were used at customers' premises for MLPPP with certain UK ISPs, but since BT started implementing 21CN (ADSL2+) they are using ERX core routers (Juniper) and no longer support MLPPP. I understand that MPLS is used instead these days, but have no experience in its implementation. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] kernel panick after time while compiling....
Hi people! When I merge large or big packages like firefox, thunderbird or chromium. The system hangsup with kernel panick and displays on the screen reboot after 30 seconds. What could it be?! For any help or advises, I would kindly thank you. Tamer
Re: [gentoo-user] kernel panick after time while compiling....
Tamer Higazi wrote: Hi people! When I merge large or big packages like firefox, thunderbird or chromium. The system hangsup with kernel panick and displays on the screen reboot after 30 seconds. What could it be?! For any help or advises, I would kindly thank you. Tamer Could be lots of things but have you checked your ram? Power supply getting hot? CPU getting hot? Those are things I can thing of right off the top of my head. I'm sure others will have additional ideas. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
[gentoo-user] Re: kernel panick after time while compiling....
On 27/05/13 02:15, Tamer Higazi wrote: Hi people! When I merge large or big packages like firefox, thunderbird or chromium. The system hangsup with kernel panick and displays on the screen reboot after 30 seconds. What could it be?! Install sys-apps/memtest86+ make a bootloader entry for it and boot it. Sounds like a RAM problem and memtest will help you find out whether that's the case.
Re: [gentoo-user] IP Load Sharing - Per Packet Load Balancing (Linux router)
Remaining independent from corporate bureaucracy or lack of support (ISP saying no to MLPP), and proprietary technology (our friends in blue, purple and green ;). What would be the best way to integrate it to my linux router to laod balance packets both up and down. And if not at the packet level, maybe the session would suffice (i.e, per network session)? Although per packet would be preferred. Kind Regards, Nick. On 5/26/13, Mick michaelkintz...@gmail.com wrote: On Sunday 26 May 2013 22:35:14 J. Roeleveld wrote: On 25 May 2013, at 22:26, Nick Khamis wrote: ... As mentioned this would be two separate DSL services, connected using separate bridges. I think I am describing more of a link aggregation or bonding Also assuming that the service providers support bonding of the links…. Here in the UK this is a somewhat common thing - there are a number of ISPs which offer bonded xDSL services. It's certainly possible to use a Linux router to manage such a connection, although I don't know the details. http://www22.brinkster.com/findall/bondedcd.html http://www.automatedhome.co.uk/reviews/adsl-bonding-how-to-and-revie w.html Bonding network devices together is quite simple, but it needs to be configured on both ends. In other words, to merge 2 DSL-connections together using bonding, you need to get both from the same ISP and the ISP would need to support it on their end. If bonding can't be done on the ISP-side, you can use seperate load-balancing/failover using other techniques. There's different ways of going about it, without or without MLPPP, depending on what your ISP offers: http://wiki.aa.org.uk/index.php/Linux_upload_bonding_using_multipath_routing http://wiki.aa.org.uk/index.php/Linux_upload_bonding_using_policy_routing It used to be the case that Cisco 1800/2800 routers were used at customers' premises for MLPPP with certain UK ISPs, but since BT started implementing 21CN (ADSL2+) they are using ERX core routers (Juniper) and no longer support MLPPP. I understand that MPLS is used instead these days, but have no experience in its implementation. -- Regards, Mick
Re: [gentoo-user] IP Load Sharing - Per Packet Load Balancing (Linux router)
Sorry for the top post. N.
RE: [gentoo-user] Re: kernel panick after time while compiling....
Hey dude, some hints that should help you to discover why your system are freezing. First take a look in temperature of your system while compiling with watch -n 1 sensors. Some programs like atop and htop show me to be very useful too. Take a look inside make.conf and see how much you are overpowering your computer in MAKEOPTS option. Maybe you need raise down it. Another observation, in case that you are using notebook it's about the flow of the cold/hot air. Good luck. -Original Message- From: Nikos Chantziaras [mailto:rea...@gmail.com] Sent: domingo, 26 de maio de 2013 20:39 To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: kernel panick after time while compiling On 27/05/13 02:15, Tamer Higazi wrote: Hi people! When I merge large or big packages like firefox, thunderbird or chromium. The system hangsup with kernel panick and displays on the screen reboot after 30 seconds. What could it be?! Install sys-apps/memtest86+ make a bootloader entry for it and boot it. Sounds like a RAM problem and memtest will help you find out whether that's the case.
Re: [gentoo-user] IP Load Sharing - Per Packet Load Balancing (Linux router)
By downstream, I mean within our own network. Obviously downstream LB from the ISP's DSLAM would be impossible without MLPP, BGP support... N
[gentoo-user] OT: RST vs RST/ACK
I am familiar with an RST response to a SYN hitting a closed port, however, I am also now seeing RST/ACKs. Is there any particular difference or it is merely dependent on how the OS vendor decided to code their TCP/IP stack? Google hits mention Windows 2008 a lot...
[gentoo-user] What does xgetdefault use flag do
Am I correct that the xgetdefault use flag is needed for an application if I want it to read Xresources and Xdefaults? Does it enable anything else? I tried searching the forum and the web but there is too many false positive hits to sort through. Most references to it are very old so is it a deprecated feature? The definition for the use flag is a little cryptic or maybe I'm a little too dumb. OT: This is my first post to this list and just want to say hi. I've been stalking the list for several months now and this is by far the most interesting and useful list I've ever subscribed to. -- B G
[gentoo-user] [OT] A free VPN server
This company: https://proxpn.com sponsors my all-time-favorite podcast, which I heartily commend to you: http://twit.tv/show/security-now (the audio podcast is what I suggest, as the video adds very little) Anyway, you can get a free account from proxpn.com by giving them a working email address (no credit card or any other personal info). Here is what I used to get it working on gentoo: net-misc/networkmanager net-misc/networkmanager-pptp and I had to add these to my kernel config: CONFIG_PPP CONFIG_PPP_MPPE CONFIG_PPP_ASYNC The name of the server to give networkmanager is pptp.proxpn.com I confess I have no idea how to do all of this without networkmanager, but I'd like to hear from you networking nerds out there who know more about this stuff than I do.
