Grant wrote:
...
If my main rig starts using swap a lot, I'm going to be very curious. I
even used 8Gbs to put portages work directory on tmpfs. I still didn't use
any swap. By the way, that doesn't seem to make the compiles any faster.
o_O
CPU bottleneck?
- Grant
I
Mark Shields wrote:
On Sat, Jul 23, 2011 at 10:26 AM, Dale rdalek1...@gmail.com
mailto:rdalek1...@gmail.com wrote:
OK. New theory here. This came about in another thread about the
shiney new kernel, that isn't new by the way. Anyway, look at
this crap:
SNIP
Why are
On 23 July 2011, at 19:30, Albert Hopkins wrote:
I haven't filed a bug because at the moment we have not been able to
figure out exactly what is causing it.
Well, if you knew what was causing it, then you wouldn't need to report
a bug as you could just fix it yourself :P
Quite the
On Sunday, July 24 at 15:11 (+0100), Stroller said:
Well, if you knew what was causing it, then you wouldn't need to
report
a bug as you could just fix it yourself :P
Quite the opposite!
Yeah, I was half joking. The point was that not filing a bug because
you don't know what the
On Sat, 23 Jul 2011 13:51:55 -0500, Dale wrote:
It is a good point. I would like to be able to give some more details
other than when I try to download a file in Firefox or Seamonkey, I get
a kernel panic. That's not really a lot of info to give them and I'm
not sure what they could do
On Sat, 23 Jul 2011 14:46:25 -0400, Mike Edenfield wrote:
What would you have done if the hard drive had failed?
I always image the windows disk and then wipe it, but I'm aware that
this is not completely reliable. some failures make restoration
impossible.
If the hard drive failed
If my main rig starts using swap a lot, I'm going to be very curious. I
even used 8Gbs to put portages work directory on tmpfs. I still didn't
use
any swap. By the way, that doesn't seem to make the compiles any faster.
o_O
CPU bottleneck?
- Grant
I sort of doubt it. I have a AMD 4
Hi there,
im having problems in getting my wifi card working with kernel 2.6.38 r6.
I built the kernel with userspace firmware loading support, and with iwl3945
as a module.
I can successfully load the module, but when i try to bring wlan0 up, kernel
messages says firmware file req failed: -2,
Device Drivers ---
[*] Network device support ---
[*] Wireless LAN ---
[*] Wireless LAN (IEEE 802.11)
M Intel Wireless Wifi
[*] Enable LED support in iwlagn and iwl3945 drivers
[*] Enable Spectrum Measurement in iwlagn driver
- iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
This error indicate a firmware version/filename mismatch. Just rename the
file to whatever iwlwifi displays in this case: iwlwifi-4965-1.ucode If this
fails, try an alternate version, perhaps
Neil Bothwick wrote:
On Sat, 23 Jul 2011 13:51:55 -0500, Dale wrote:
It is a good point. I would like to be able to give some more details
other than when I try to download a file in Firefox or Seamonkey, I get
a kernel panic. That's not really a lot of info to give them and I'm
not sure
Hey thanks for the answer.
No luck with changing the name of the microcode.
--
sent from my mighty Nexusone
On Jul 24, 2011 6:57 p.m., Srdjan Rakic srk...@gmail.com wrote:
- iwl4965: iwlwifi-4965-1.ucode firmware file req failed: Reason -2
This error
On Sat, Jul 23, 2011 at 11:01:43AM +0700, Pandu Poluan wrote:
AFAIK, there are files that *must* still exist for this strategy to
succeed. However, this post from f.g.o [2] said that those files
aren't necessary. So, I should do the following sequence in /etc/fstab
:
1. Mount /dev/xvda3 as
On 07/23/2011 04:49 PM, Adam Carter wrote:
Summary;
Copied / from sda3 to sdb3
Updated the fstab in the new disk (/dev/sdb3 /
btrfs noatime,compress=lzo0 0)
Updated the kernel line's root=/dev/sda3 to /dev/sdb3 in grub.conf,
but left the root (hd0,0) as it is. So, kernel
On Sun, Jul 24, 2011 at 09:49:21AM +1000, Adam Carter wrote:
Summary;
Copied / from sda3 to sdb3
Updated the fstab in the new disk (/dev/sdb3 /
btrfs noatime,compress=lzo0 0)
Updated the kernel line's root=/dev/sda3 to /dev/sdb3 in grub.conf,
but left the root (hd0,0) as
It must be one of the most annoying things in Gentoo when OOo fails at the
very last minute!
It may be this was caused by me forgetting to set MAKEOPTS=-j1 but just in
case something else is amiss, does this look familiar?
===
=
Building
On Sunday 24 July 2011 22:27:34 Mick wrote:
It must be one of the most annoying things in Gentoo when OOo fails at the
very last minute!
It may be this was caused by me forgetting to set MAKEOPTS=-j1 but just
in case something else is amiss, does this look familiar?
Mick wrote:
It must be one of the most annoying things in Gentoo when OOo fails at the
very last minute!
It may be this was caused by me forgetting to set MAKEOPTS=-j1 but just in
case something else is amiss, does this look familiar?
SNIP
Before I start again, shall I switch to
On 07/24/2011 01:27 PM, Mick wrote:
It must be one of the most annoying things in Gentoo when OOo fails at the
very last minute!
It may be this was caused by me forgetting to set MAKEOPTS=-j1
If that's the cause (and I have no idea) then you should be able to complete
the build this way,
On Sunday 24 Jul 2011 22:11:47 walt wrote:
On 07/24/2011 01:27 PM, Mick wrote:
It must be one of the most annoying things in Gentoo when OOo fails at
the very last minute!
It may be this was caused by me forgetting to set MAKEOPTS=-j1
If that's the cause (and I have no idea) then you
On Sunday 24 July 2011 19:13:27 Dale wrote:
I'm not sure it is the nic tho. It downloads just fine when emerge is
fetching files. I'm not saying it isn't tho. I really don't know what
it is. I'm also keeping in mind that the nic is built onto my mobo. I
have never had good luck with a
Unix rights on files? How did you copy the system?
Yep, identical to the original. I used tar to copy the files and
maintain permissions. Checksums match too.
Peter Humphrey wrote:
On Sunday 24 July 2011 19:13:27 Dale wrote:
I'm not sure it is the nic tho. It downloads just fine when emerge is
fetching files. I'm not saying it isn't tho. I really don't know what
it is. I'm also keeping in mind that the nic is built onto my mobo. I
have
Hi,
I just got around to trying my Virtualbox VMs under the new 3.0.0
kernel and they aren't working. It says vboxdrv is not set up. I drop
back to 2.6.39 and they run fine. Please note I really mean only the
VMs won't start. The Vbox GUI runs fine but then cannot start the VMs.
I used make
On Sun, 24 Jul 2011 17:09:13 -0700
Mark Knecht markkne...@gmail.com wrote:
Hi,
I just got around to trying my Virtualbox VMs under the new 3.0.0
kernel and they aren't working. It says vboxdrv is not set up. I drop
back to 2.6.39 and they run fine. Please note I really mean only the
VMs
On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagener st...@gmx.net wrote:
On Sun, 24 Jul 2011 17:09:13 -0700
Mark Knecht markkne...@gmail.com wrote:
Hi,
I just got around to trying my Virtualbox VMs under the new 3.0.0
kernel and they aren't working. It says vboxdrv is not set up. I drop
back
On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagener st...@gmx.net wrote:
On Sun, 24 Jul 2011 17:09:13 -0700
Mark Knecht markkne...@gmail.com wrote:
Hi,
I just got around to trying my Virtualbox VMs under the new 3.0.0
kernel and they aren't working. It says vboxdrv is not set up. I drop
back
Mark Knecht wrote:
On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagenerst...@gmx.net wrote:
On Sun, 24 Jul 2011 17:09:13 -0700
Mark Knechtmarkkne...@gmail.com wrote:
Hi,
I just got around to trying my Virtualbox VMs under the new 3.0.0
kernel and they aren't working. It says
On 07/24/11 22:02, Mark Knecht wrote:
On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagenerst...@gmx.net wrote:
On Sun, 24 Jul 2011 17:09:13 -0700
Mark Knechtmarkkne...@gmail.com wrote:
Hi,
I just got around to trying my Virtualbox VMs under the new 3.0.0
kernel and they aren't working. It
On Sun, Jul 24, 2011 at 7:22 PM, Matthew Finkel
matthew.fin...@gmail.com wrote:
On 07/24/11 22:02, Mark Knecht wrote:
On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagenerst...@gmx.net wrote:
On Sun, 24 Jul 2011 17:09:13 -0700
Mark Knechtmarkkne...@gmail.com wrote:
Hi,
I just got around to
30 matches
Mail list logo
