Re: [gentoo-user] firefox crash when playing flash
Are you using compiz-fusion? There are reported problems with firefox and flash contents with compiz-fusion...
Re: [gentoo-user] iwl4965 performance
Hi, Have you tried using the driver from the 2.6.24* series kernel? I've been using iwl3945 from tuxonice-sources 2.6.24-r3 without any performance or stability problems whatsoever. Good luck. Regards, José Pedro On Mon, Mar 24, 2008 at 4:28 PM, Thomas Kahle [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am using the iwl4965 driver which is included in the kernel 2.6.25-rc6. Everything works fine (Networkmanager, WPA2, etc.) The only thing I experience is a very bad performance. I cannot get more than around 30 kb/s. Also the responses are rather slow. If I open some new tabs in firefox it takes up to 5 seconds before there is enough data to render something. When using wired network its much faster. The router is also not the source of the problem, with my old airo card i could get up to 200 kb/s, the macbook running gentoo gets to around 500kb/s. Any ideas where to start investigation ? Thanks Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH59amrpEWPKIUt7MRAqdhAJ9+QC796Ru3Gy3QxnEbpuSopk2FEgCfXCDA wYRlsepf7rwt+5FgzlaUw2M= =k17g -END PGP SIGNATURE- -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] weird xorg/nvidia-drivers 169.09-r1 behaviour
On Thu, Mar 20, 2008 at 5:02 AM, 李刚 [EMAIL PROTECTED] wrote: in your xorg.conf In the module section, try adding the following line load dbe Then try to run conky from your terminal-emulator, does it say something that double framebuffer enabled? Yup, i have dbe enabled and I'm running conky with double buffer support. I have no problems whatsoever with older versions of nvidia-drivers Also,i found the conky in ~x86 portage a little of weird, conky 1.4.9-r1* *is marked as stable for x86 1. it displays my uptime very strange, a very very very very long digit, something like 343434, oh, my computer never run so much time without powering down 2. mpd is not working with conky, maybe this is a problem with mpd, but i am not sure I use audacious with conky and works like a charm for me hope this would help On 3/20/08, José Pedro Saraiva [EMAIL PROTECTED] wrote: Been using nvidia-drivers-100.14.19 without problems but I wish to upgrade to latest stable version, in a hope to reduce random suspend crashes I've been having with latest tuxonice-sources. The thing is... once I'm up and running with nvidia-drivers 169.09-r1xorg and conky have this strange behaviour with conky window overlapping each time it refreshes. First screenshot is my desktop in it's normal state, 2nd one is the behaviour I'm talking about... The only window that always overlaps is the network section, and the conkyrc options are the same as for other conky instances. Anyone have a clue what may be causing this? Best regards! -- Easy things should be easy, hard things should at least be possilbe. Powered by Gentoo Linux
Re: [gentoo-user] No kernel boot after inserting more ram
On Jan 20, 2008 10:43 PM, Thomas Kahle [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I guess your kernel is configured to support only 1GB of RAM. In the kernel configuration look for Processor Type and Features There you find the Option. High Memory Support. Probably it is set to off. Set it to 4GB then recompile the kernel. That should do it. That was already suggested in a previous reply :) I do have High Memory Support enabled with 4GB, still, it refuses to boot! have fun Tom José Pedro Saraiva wrote: Well, after all kinds of tests and trying different types of memory configurations, I can only conclude that my kernel boots normally with 1 GB of RAM installed but hangs when I have 2 GB of RAM installed. I can't find a logical reason for this to happen. Any pointers or suggestions are welcome, Regards On Jan 19, 2008 11:31 PM, José Pedro Saraiva [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Following your replies I've done the following, in an attempt to isolate the problem: (memory #1 - old memory, memory #2 - new memory) - Runned memtest on both memories with 0 errors - Booted with both memories... kernel hang - Booted with memory #1 on slot #1 successfully - Booted with memory #1 on slot #2 successfully - Booted with memory #2 on slot #1 successfully - Booted with memory #2 on slot #2 successfully - Booted with both memories on windows successfully For some reason, my kernel hangs if I have 2 GB of RAM installed. And I do have High memory support (4GB), although that doesn't seem relevant. Ideas? :X Thank you all for the quick replies. Cheers On Jan 19, 2008 2:29 PM, Hal Martin [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: An alternative to running memtest (which is quite easy to do, I might add) would be to remove the original RAM and see if the computer boots with the new RAM only. Alternatively, you could just run memtest, as it is included with many BIOSs now. It doesn't take long to identify problems, if there are any. I find that test #5 is the best test for finding problems, however it tends to keep you in the dark until it's finished the test. -Hal Neil Bothwick wrote: On Fri, 18 Jan 2008 22:58:59 +, José Pedro Saraiva wrote: I'm sure there's nothing wrong with the RAM, How? Have you run memtest? -- gentoo-user@lists.gentoo.org mailto:gentoo-user@lists.gentoo.org mailing list -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHk86lrpEWPKIUt7MRAtm6AJ9EbOJfcrxM7UoceMz3B2gdpKLn1gCfdMMh +04EiTXdzcE5JOp6ON5IQOQ= =SdgG -END PGP SIGNATURE- -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] No kernel boot after inserting more ram
Well, after all kinds of tests and trying different types of memory configurations, I can only conclude that my kernel boots normally with 1 GB of RAM installed but hangs when I have 2 GB of RAM installed. I can't find a logical reason for this to happen. Any pointers or suggestions are welcome, Regards On Jan 19, 2008 11:31 PM, José Pedro Saraiva [EMAIL PROTECTED] wrote: Following your replies I've done the following, in an attempt to isolate the problem: (memory #1 - old memory, memory #2 - new memory) - Runned memtest on both memories with 0 errors - Booted with both memories... kernel hang - Booted with memory #1 on slot #1 successfully - Booted with memory #1 on slot #2 successfully - Booted with memory #2 on slot #1 successfully - Booted with memory #2 on slot #2 successfully - Booted with both memories on windows successfully For some reason, my kernel hangs if I have 2 GB of RAM installed. And I do have High memory support (4GB), although that doesn't seem relevant. Ideas? :X Thank you all for the quick replies. Cheers On Jan 19, 2008 2:29 PM, Hal Martin [EMAIL PROTECTED] wrote: An alternative to running memtest (which is quite easy to do, I might add) would be to remove the original RAM and see if the computer boots with the new RAM only. Alternatively, you could just run memtest, as it is included with many BIOSs now. It doesn't take long to identify problems, if there are any. I find that test #5 is the best test for finding problems, however it tends to keep you in the dark until it's finished the test. -Hal Neil Bothwick wrote: On Fri, 18 Jan 2008 22:58:59 +, José Pedro Saraiva wrote: I'm sure there's nothing wrong with the RAM, How? Have you run memtest? -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] No kernel boot after inserting more ram
Following your replies I've done the following, in an attempt to isolate the problem: (memory #1 - old memory, memory #2 - new memory) - Runned memtest on both memories with 0 errors - Booted with both memories... kernel hang - Booted with memory #1 on slot #1 successfully - Booted with memory #1 on slot #2 successfully - Booted with memory #2 on slot #1 successfully - Booted with memory #2 on slot #2 successfully - Booted with both memories on windows successfully For some reason, my kernel hangs if I have 2 GB of RAM installed. And I do have High memory support (4GB), although that doesn't seem relevant. Ideas? :X Thank you all for the quick replies. Cheers On Jan 19, 2008 2:29 PM, Hal Martin [EMAIL PROTECTED] wrote: An alternative to running memtest (which is quite easy to do, I might add) would be to remove the original RAM and see if the computer boots with the new RAM only. Alternatively, you could just run memtest, as it is included with many BIOSs now. It doesn't take long to identify problems, if there are any. I find that test #5 is the best test for finding problems, however it tends to keep you in the dark until it's finished the test. -Hal Neil Bothwick wrote: On Fri, 18 Jan 2008 22:58:59 +, José Pedro Saraiva wrote: I'm sure there's nothing wrong with the RAM, How? Have you run memtest? -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] No kernel boot after inserting more ram
Hi all, wise gentoo users! I've recently bought an extra GB of RAM for my laptop. After inserting it, kernel refuses to boot, it hangs at Booting the kernel I'm sure there's nothing wrong with the RAM, so it must be some other issue, perhaps related with my boot options? Any help or ideas are welcome :) Here's an extract of my grub.conf: title Gentoo 2.6.22-r8 root (hd0,1) kernel /boot/kernel-2.6.22-r8 root=/dev/sda5 splash=verbose,fadein,theme:emergence fbcon=scrollback:128K console=/dev/tty1 combined_mode=libata initrd /boot/fbsplash-emergence-1024x768 Best regards, José Pedro
[gentoo-user] ipw3945 and wpa_supplicant issues
Hi all!
I own a Toshiba laptop P100-400 with a Intel PRO/Wireless 3945ABG wireless
adapter.
I've managed to get it working with normal WEP authentication, but no
success with wpa_supplicant (and I really need it for WPA auth).
# /etc/init.d/net.eth1 restart
* Stopping eth1
* Bringing down eth1
* Stopping dhcpcd on eth1
...
[ ok ]
* Shutting down eth1
...
[ ok ]
* Stopping wpa_cli on eth1
...
[ ok ]
* Stopping wpa_supplicant on eth1
...
[ ok ]
* Starting eth1
* Starting wpa_supplicant on eth1 ...
ioctl[SIOCSIWMODE]: Resource temporarily unavailable
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Resource temporarily unavailable
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Resource temporarily
unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily
unavailable
[ ok ]th param 5 value 0x1 -
* Starting wpa_cli on eth1
...
[ ok ]
* Failed to configure eth1 in the background
Ugly, uh? :/
dmesg output:
ipw3945: Error sending LEDS_CMD: time out after 500ms.
ipw3945: Error sending LEDS_CMD: time out after 500ms.
ipw3945: Error sending LEDS_CMD: time out after 500ms.
ipw3945: request scan called when driver not ready.
ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
ipw3945: Error sending LEDS_CMD: time out after 500ms.
ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
Some extra info:
I'm using the internal ieee8021x stack with gentoo-sources-2.6.19-r5
* net-wireless/ipw3945
Latest version available: 1.2.0
Latest version installed: 1.2.0
* net-wireless/ipw3945-ucode
Latest version available: 1.14.2
Latest version installed: 1.14.2
* net-wireless/ipw3945d
Latest version available: 1.7.22-r4
Latest version installed: 1.7.22-r4
* net-wireless/wpa_supplicant
Latest version available: 0.5.7
Latest version installed: 0.5.7
# lspci | grep Wireless
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Connection (rev 02)
# pcitweak -l 21 | grep 03.00.0:
PCI: 03:00:0: chip 8086,4222 card 8086,1041 rev 02 class 02,80,00 hdr 00
# iwconfig eth1
eth1 unassociated ESSID:off/any
Mode:Managed Frequency= 2.462 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:179 Missed beacon:0
/etc/conf.d/net extract:
modules_eth1=( !plug wpa_supplicant )
wpa_supplicant_eth1=-Dwext
associate_timeout_eth1=60
/etc/wpa_supplicant/wpa_supplicant.conf extract (the problem isn't here
though, it fails with all types of configurations):
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=0
eapol_version=1
ap_scan=0
fast_reauth=1
network={
ssid=XX
priority=1
key_mgmt=NONE
auth_alg=SHARED
wep_key0=XXX
wep_tx_keyidx=0
}
Sorry for the length.
Any help would be greatly appreciated.
Best regards,
José Pedro
[gentoo-user] ipw3945 and wpa_supplicant issues
Hi all!
I own a Toshiba laptop P100-400 with a Intel PRO/Wireless 3945ABG wireless
adapter.
I've managed to get it working with normal WEP authentication, but no
success with wpa_supplicant (and I really need it for WPA auth).
# /etc/init.d/net.eth1 restart
* Stopping eth1
* Bringing down eth1
* Stopping dhcpcd on eth1
...
[ ok ]
* Shutting down eth1
...
[ ok ]
* Stopping wpa_cli on eth1
...
[ ok ]
* Stopping wpa_supplicant on eth1
...
[ ok ]
* Starting eth1
* Starting wpa_supplicant on eth1 ...
ioctl[SIOCSIWMODE]: Resource temporarily unavailable
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Resource temporarily unavailable
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Resource temporarily
unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily
unavailable
[ ok ]th param 5 value 0x1 -
* Starting wpa_cli on eth1
...
[ ok ]
* Failed to configure eth1 in the background
Ugly, uh? :/
dmesg output:
ipw3945: Error sending LEDS_CMD: time out after 500ms.
ipw3945: Error sending LEDS_CMD: time out after 500ms.
ipw3945: Error sending LEDS_CMD: time out after 500ms.
ipw3945: request scan called when driver not ready.
ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
ipw3945: Error sending LEDS_CMD: time out after 500ms.
ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
Some extra info:
I'm using the internal ieee8021x stack with gentoo-sources-2.6.19-r5
* net-wireless/ipw3945
Latest version available: 1.2.0
Latest version installed: 1.2.0
* net-wireless/ipw3945-ucode
Latest version available: 1.14.2
Latest version installed: 1.14.2
* net-wireless/ipw3945d
Latest version available: 1.7.22-r4
Latest version installed: 1.7.22-r4
* net-wireless/wpa_supplicant
Latest version available: 0.5.7
Latest version installed: 0.5.7
# lspci | grep Wireless
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Connection (rev 02)
# pcitweak -l 21 | grep 03.00.0:
PCI: 03:00:0: chip 8086,4222 card 8086,1041 rev 02 class 02,80,00 hdr 00
# iwconfig eth1
eth1 unassociated ESSID:off/any
Mode:Managed Frequency=2.462 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:179 Missed beacon:0
/etc/conf.d/net extract:
modules_eth1=( !plug wpa_supplicant )
wpa_supplicant_eth1=-Dwext
associate_timeout_eth1=60
/etc/wpa_supplicant/wpa_supplicant.conf extract (the problem isn't here
though, it fails with all types of configurations):
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=0
eapol_version=1
ap_scan=0
fast_reauth=1
network={
ssid=XX
priority=1
key_mgmt=NONE
auth_alg=SHARED
wep_key0=XXX
wep_tx_keyidx=0
}
Sorry for the length.
Any help would be greatly appreciated
.
Best regards,
José Pedro
[gentoo-user] irc bouncer(s) problem(s)
Greetings all!I've had a working version of psybnc running for mounths with no problems. But recently I needed to recompile it and I am unable to get it working, maybe due to glibc version update, as I've read on some foruns. Even though it was a masked package (~x86) I builded it anyway, but it crashes. The funny thing is that it only crashes when trying to connect to any IRC server. So I decided to look for more options, builded miau and muh.Although miau is a fork of muh, I can get muh to work with no problems but miau gives the following weird startup error:Sep 02 10:17:47 + Configuration read. Sep 02 10:17:47 - Unable to create socket! (Address family not supported by protocol)muh on the other hand runs smooth:[Sat 02 Sep 10:59:17] + parsing configuration file...[Sat 02 Sep 10:59:17] + listening on port 31330. [Sat 02 Sep 10:59:17] + muh's nick is 'nocive'.[Sat 02 Sep 10:59:17] + alrite, muh's forked. (pid 13213)This is puzzling me 'cause the config files for both programs are quite smiliar and the core is, presumably, the same. Now, what bothers me is that miau has some features that I really need (such as on connect commands) that muh doesn't.So any help on getting miau or psybnc running would be appreciated.Many thanks, José Pedro Saraiva
Re: [gentoo-user] irc bouncer(s) problem(s)
Many thanks Stuart!That was what was causing the socket error, which is kind of stupid since I don't have ipv6 support enabled, so miau should have been compiled without ipv6 support by default.Thanks again On 9/2/06, Stuart Howard [EMAIL PROTECTED] wrote: HiThis may be unrelated here but when I used to run miau it would onlywork when I compiled it with the USE flag -ipv6hope it helpsstuOn 02/09/06, José Pedro Saraiva [EMAIL PROTECTED] wrote: Greetings all! I've had a working version of psybnc running for mounths with no problems. But recently I needed to recompile it and I am unable to get it working, maybe due to glibc version update, as I've read on some foruns. Even though it was a masked package (~x86) I builded it anyway, but it crashes. The funny thing is that it only crashes when trying to connect to any IRC server. So I decided to look for more options, builded miau and muh. Although miau is a fork of muh, I can get muh to work with no problems but miau gives the following weird startup error: Sep 02 10:17:47 + Configuration read. Sep 02 10:17:47 - Unable to create socket! (Address family not supported by protocol) muh on the other hand runs smooth: [Sat 02 Sep 10:59:17] + parsing configuration file... [Sat 02 Sep 10:59:17] + listening on port 31330. [Sat 02 Sep 10:59:17] + muh's nick is 'nocive'. [Sat 02 Sep 10:59:17] + alrite, muh's forked. (pid 13213) This is puzzling me 'cause the config files for both programs are quite smiliar and the core is, presumably, the same. Now, what bothers me is that miau has some features that I really need (such as on connect commands) that muh doesn't. So any help on getting miau or psybnc running would be appreciated. Many thanks, José Pedro Saraiva--There are 10 types of people in this world: those who understandbinary, those who don't--Unknown --gentoo-user@gentoo.org mailing list
Re: [gentoo-user] P4P800 - Intel ICH5R - data recovery?
On 7/20/05, Patrick Rutkowski [EMAIL PROTECTED] wrote: On Tuesday 19 July 2005 19:37, José Pedro Saraiva wrote: Thanks for the reply Colin =) If you remember your stripe size, then you should be able to plug your drives into any ICH5R-based motherboard and get your data back. Theoretically, you could plug your drives into any RAID whose BIOS does not write to the disks when creating an array and then recreate the array in the BIOS with the same stripe size. I don't know if software RAID can rebuild your array, but that seems like your best bet, lest you have a friend with a lot of SATA RAID controllers (s) he's willing to lend out. I already ordered another ICH5R motherboard (similar to my P4P800 but a new model, since my old one is not available anymore) to try that out. I'm almost sure that my stripe size is 64KB (default). If so, plugging my hard drives into the new board and creating a new array with the same stripe size will give me access to my data? Or is there the risk of loosing it all? Do you know if the ICH5R writes to the disks when creating the array? If all else fails and your data is priceless, grab a couple grand and look into professional data recovery, because unless you can find a super-geek, that will probably be your best bet. Unfortunately I cannot afford such a service, even though my data is crucial to me, they're just too expensive for my pocket. :-( José Pedro My one BIG FAT WARNING to you would be to think for 30 seconds or more before pushing any buttons when redoing your disks. Its very easy to accidentally format things when you don't know exactly what your doing... at least for me it is; I've done it :-p Wishing the best of luck, Patrick Rutkowski It turns out everything is easier than we thought! I contacted Intel for some support and here's what they told me: - Thank you for contacting Intel(R) Technical Support. You should be able to just connect both drives to a motherboard with either the Intel(R) 82801ER I/O controller hub (ICH5R), the Intel(R) 82801FR I/O controller hub (ICH6R) or the Intel(R) 82801GR I/O controller hub (ICH7R) and everything should work fine. Now, you just need to connect the drives. Do not create the RAID 0 volume again because this will cause the drives to be overwritten. Before plugging in the drives, make sure that the onboard RAID controller is enabled in the BIOS, or that Serial ATA features are set to RAID. Either one of the above RAID controllers, once enabled at BIOS level, should be able to detect the RAID structure on the drives. - Neat, huh? :D Now I can blame Intel if anything goes wrong! : Regards, José Pedro -- gentoo-user@gentoo.org mailing list
[gentoo-user] P4P800 - Intel ICH5R - data recovery?
Hi, I know this isn't a gentoo related question so forgive me, but I trust on the gentoo mailing list to give me a hand... I have a Asus P4P800 motherboard that recently became useless (plain broken, don't know why, no boot, no BIOS, nothing). I had 2x120 GB SATA hard drives connected with RAID 0 using the intel ICH5R chipset included in the board. Is my data completely lost, now that the motherboard is broken? Is there a way to recover it? If I install another motherboard with the same RAID chipset will my data be recoverable or is it a lost cause? Thanks in advance, José Pedro -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] P4P800 - Intel ICH5R - data recovery?
Thanks for the reply Colin =) If you remember your stripe size, then you should be able to plug your drives into any ICH5R-based motherboard and get your data back. Theoretically, you could plug your drives into any RAID whose BIOS does not write to the disks when creating an array and then recreate the array in the BIOS with the same stripe size. I don't know if software RAID can rebuild your array, but that seems like your best bet, lest you have a friend with a lot of SATA RAID controllers (s) he's willing to lend out. I already ordered another ICH5R motherboard (similar to my P4P800 but a new model, since my old one is not available anymore) to try that out. I'm almost sure that my stripe size is 64KB (default). If so, plugging my hard drives into the new board and creating a new array with the same stripe size will give me access to my data? Or is there the risk of loosing it all? Do you know if the ICH5R writes to the disks when creating the array? If all else fails and your data is priceless, grab a couple grand and look into professional data recovery, because unless you can find a super-geek, that will probably be your best bet. Unfortunately I cannot afford such a service, even though my data is crucial to me, they're just too expensive for my pocket. :-( José Pedro -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Packet loss unknown issue - SOLVED :)
On 7/13/05, Petr Kocmid [EMAIL PROTECTED] wrote: Your modem/router which is 192.168.1.254 on eth0 fits the netmask of the eth1 network. Weird thing is that this configuration as always been working for me, with no problems whatsoever... until now. Anyways, thank you! Problem solved! -- gentoo-user@gentoo.org mailing list
[gentoo-user] heavy packet loss problem (ifconfig?)
Hello, I'm quite desperate and have tried just about anything. I'll try to explain it... I connect to the net through eth0 and have a masquerading through eth1 to my other computers, using shorewall. My server never had any problems of this kind and all was fine until a couple of days ago. I'm experiencing some heavy packet loss when pinging different hosts. I have isolated the problem (at least I think I did) and got to the conclusion that issuing a simple 'ifconfig eth1 down' and leaving eth0 up, the packet loss vanishes. Tests were made with all services down (shorewall, sshd, apache2, mysqld, proftpd, sendmail, ...) and with the network cable unplugged from eth1 (so no traffic is being generated through eth1 that could cause packet loss) Here are the statistics: - eth1 up - # ping -c 200 google.com --- google.com ping statistics --- 200 packets transmitted, 104 received, 48% packet loss, time 208227ms rtt min/avg/max/mdev = 152.388/229.520/2016.847/279.805 ms, pipe 3 - eth1 down - # ping -c 200 google.com --- google.com ping statistics --- 200 packets transmitted, 200 received, 0% packet loss, time 199175ms rtt min/avg/max/mdev = 147.197/169.978/193.949/8.384 ms Both network cards are using the same chipset (RLT8139) loaded as a module in the kernel (2.6.11-hardened-r13). I have tried to replace the network card (with one also using RLT8139) and changing it from IRQ but with no effect. Please help, I've runned out of ideas... Thanks in advance! José Pedro -- gentoo-user@gentoo.org mailing list
[gentoo-user] Packet loss unknown issue
Hello, I'm quite desperate and have tried just about anything to understand my issue. I'll try to explain it... I connect to the net through eth0 and have a masquerading through eth1 to my other computers, using shorewall. My server never had any problems of this kind and all was fine until a couple of days ago. I'm experiencing some heavy packet loss when pinging different hosts. I have isolated the problem (at least I think I did) and got to the conclusion that issuing a simple 'ifconfig eth1 down' and leaving eth0 up, the packet loss vanishes. Tests were made with all services down (shorewall, sshd, apache2, mysqld, proftpd, sendmail, ...) Here are the statistics: - eth1 up - # ping -c 200 google.com --- google.com ping statistics --- 200 packets transmitted, 104 received, 48% packet loss, time 208227ms rtt min/avg/max/mdev = 152.388/229.520/2016.847/279.805 ms, pipe 3 - eth1 down - ping -c 200 google.com --- google.com ping statistics --- 200 packets transmitted, 200 received, 0% packet loss, time 199175ms rtt min/avg/max/mdev = 147.197/169.978/193.949/8.384 ms Both network cards are using the same chipset (RLT8139) loaded as a module in the kernel (2.6.11-hardened-r13). I have tried to replace the network card (with one also using RLT8139) and changing it from IRQ but with no effect. Please help me, I've runned out of ideas... Thanks in advance! José Pedro -- gentoo-user@gentoo.org mailing list
