Re: [gentoo-amd64] Drivers For USB HDD
On Sun, 6 May 2012 14:29:20 -0400 Frank Peters wrote: ... snip ... Using a Gentoo Live DVD to boot Linux, the drive was recognized without any read errors. In this case fdisk could recognize the drive. I then attempted to reformat the drive with an ext2 file system but the format failed. ... snip ... With the LiveCD running, try the following commands lsusb -v to list information on the usb devices found by Gentoo lsmod to list the modules loaded. HTH, David
Re: [gentoo-amd64] Updating masked packages
On Fri, 22 Jan 2010 16:06:27 +0100 Marko Obrovac wrote: CrÃstian Viana wrote: shouldn't you add xlibs instead of qtlibs? Ahhh, I got confused with the long package names! Thanks for the tip (usually the most obvious solution is the one we don't see) As it turns out, I have to keyword both of them! Thnx again Marko The autounmask utility can be used to unmask all the dependant packages ...
Re: [gentoo-amd64] emerge -eav system failed with ati-drivers
On Sun, 21 Jun 2009 13:55:10 -0400 Drake Donahue wrote: snip I'm guessing you did an emerge --depclean sometime after compiling the 2.6.22-r2 kernel and after emerging a new gentoo-sources that erased your make files, This is something depclean loves to do while leaving 99% of the older kernel source files intact. I think depclean leaves your .config file in place. Been a few weeks since I burned myself last with this one. If you were following directions back in 2007 you should have a stored 2.6.22-r2 config in the /boot directory. Try emerge =sys-kernel/gentoo-sources-2.6.22-r2 to re-emerge the old package and regain the make files. What the osmp is about beats me. or Emerge a new gentoo-sources, eselect it, configure, compile, install a new (current) kernel. My understanding is that ati-drivers expects /usr/src/linux to contain the source of the currently running kernel. I'm running a 2.6.28 kernel. I have downloaded 2.6.30 and built that but have not yet rebooted. emerge ati-drivers failed with 2.6.30 in /usr/src/linux. Changing directory names allowed ati-drivers to build happily. HTH, David
Re: [gentoo-amd64] emerge -eav system failed with ati-drivers
On Sun, 21 Jun 2009 14:54:36 -0400 John P. Burkett wrote: David Relson wrote: On Sun, 21 Jun 2009 13:55:10 -0400 Drake Donahue wrote: snip I'm guessing you did an emerge --depclean sometime after compiling the 2.6.22-r2 kernel and after emerging a new gentoo-sources that erased your make files, This is something depclean loves to do while leaving 99% of the older kernel source files intact. I think depclean leaves your .config file in place. Been a few weeks since I burned myself last with this one. If you were following directions back in 2007 you should have a stored 2.6.22-r2 config in the /boot directory. Try emerge =sys-kernel/gentoo-sources-2.6.22-r2 to re-emerge the old package and regain the make files. What the osmp is about beats me. or Emerge a new gentoo-sources, eselect it, configure, compile, install a new (current) kernel. My understanding is that ati-drivers expects /usr/src/linux to contain the source of the currently running kernel. I'm running a 2.6.28 kernel. I have downloaded 2.6.30 and built that but have not yet rebooted. emerge ati-drivers failed with 2.6.30 in /usr/src/linux. Changing directory names allowed ati-drivers to build happily. David, thank you for sharing your experience. On my system, doing uname -r gets the response 2.6.22-gentoo-r2-osmp. In my /usr/src/linux directory I currently have a .config file starting with the lines # Automatically generated make config: don't edit # Linux kernel version: 2.6.22-gentoo-r2 # Mon Sep 3 21:48:37 2007 Can you suggest how to change directory names to allow the ati-drivers to build? Best regards, John John, /usr/src/linux is what I'd want to see. Do you have just a few files (like .config) or the full kernel source? It's my understanding that ati-drivers need the full kernel source. Likely they use (or check) some of the kernel's internal header files to match up the driver with the kernel it's running against. If you've got the full kernel source, then all I can suggest is getting source for the newest kernel, building it (using your old .config as the starting point), rebooting, and (finally) emerging ati-drivers. The steps up to and including rebooting should provide a consistent kernel version and source tree and make ati-drivers happy. HTH, David
Re: [gentoo-amd64] ASUS M2A-VM and kernel 2.6.27
On Tue, 16 Dec 2008 08:26:51 +0100 Raffaele BELARDI wrote: David Relson wrote: If you've got an M2A-VM running, perhaps you could share your .config with me??? In attach, for 2.6.28-rc6. raf Thanks, Raf. I'll give it a try as soon as the replacement mobo arrives. Regards, David
Re: [gentoo-amd64] ASUS M2A-VM and kernel 2.6.27
On Mon, 15 Dec 2008 11:20:31 +0100 Volker Armin Hemmann wrote: On Montag 15 Dezember 2008, David Relson wrote: The 2.6.25 kernel ran fine for several months before these started appearing, so I suspect a hardware issue. However, when running 2.6.27's make xconfig I noticed there's an AMD_IOMMU option. I'd very much like to see if it relates to the messages above. it is very, very unlikely. The desktop amd 'iommu' is the agpgart - and that is unrelated to that option Ah, well. It sounded relevant ... Info appreciated :- David
Re: [gentoo-amd64] ASUS M2A-VM and kernel 2.6.27
On Mon, 15 Dec 2008 11:55:15 +0100 Raffaele BELARDI wrote: David Relson wrote: Hi, Anybody using an ASUS M2A-VM mobo with a 2.6.27 kernel? When I attempt to boot a 2.6.27 kernel, I see the Loading modules message (and messages for loaded modules) and then the boot process hangs. With a 2.6.25 kernel, after all the module messages boot displays Activating mdev. I've never seen this message with the 2.6.27 kernel. For that matter, I tried 2.6.26 a while back and had the same problem. Anybody know about this problem or what might cause it? On a related note, a few weeks back I started seeing kernel messages like: PCI-DMA: Out of IOMMU space for 8192 bytes at device :00:14.1 PCI-DMA: Out of IOMMU space for 1536 bytes at device :02:00.0 The 2.6.25 kernel ran fine for several months before these started appearing, so I suspect a hardware issue. However, when running 2.6.27's make xconfig I noticed there's an AMD_IOMMU option. I'd very much like to see if it relates to the messages above. If you've got an M2A-VM running, perhaps you could share your .config with me??? I have used on a M2A-VM without problems the 2.6.27-rc6 from the kernel.org, now I am using the 2.6.28-rc6 (well, almost without problems, see http://bugzilla.kernel.org/show_bug.cgi?id=11599, and I have yet another USB-related problem with this mobo). I'm on a different box now, I'll send you my .config tomorrow if you still need it. But I always have all the modules I need built in the kernel and module loading disabled, so I might not be affected by your issue. I've not seen yet the IOMMU message. I did update the BIOS before installing Gentoo, there is one upgrade specifically released to support Linux on the Asus support site. raf Hi Raf, A copy of the .config would be appreciated. It'll be a few days before I can test it because the board is boxed up ready to cross-ship to ASUS for a replacement. FWIW, I've had the board for a year or so. I learned when I got it that the USB support for the SB600 is bad (based on discussions with the kernel USB mailing list). I worked around that problem with a PCI USB card. Regards, David
Re: [gentoo-amd64] ASUS M2A-VM and kernel 2.6.27
On Mon, 15 Dec 2008 08:11:22 +0100 Martin Herrman wrote: On Mon, Dec 15, 2008 at 1:37 AM, David Relson da...@osagesoftware.com wrote: H'lo Branko, No nvidia. The M2A-VM mobo has builtin ATI Radeon X1200 capability so I have no need for a separate video card. As to the IOMMU, I've already changed the BIOS to allow the maximum memory usage (256MB) for the purpose. The change hasn't stopped the IOMMU out of space messages. I'm truly looking for someone running 64 bit gentoo on the M2A-VM mobo and using a new kernel with the CONFIG_AMD_IOMMU capability. Regards, David there are lot's of bios updates for this board that fix memory/compatibility issues. You might want to try latest BIOS, which currently is version 2201 that was released 10th of November. Martin Hi Martin, The board was RMA'd about 2 weeks ago. ASUS reflashed the BIOS and sent it back. It still has problems, so it'll be cross shipped to ASUS this week and I'll have a different board. As the board is now outside my computer (waiting to be shipped), I can't verify the BIOS revision. I'll check that info when the new board arrives. Regards, David
Re: [gentoo-amd64] Re: ASUS M2A-VM and kernel 2.6.27
On Mon, 15 Dec 2008 23:50:13 + (UTC) Duncan wrote: David Relson da...@osagesoftware.com posted 20081215074756.33119...@fit-pc, excerpted below, on Mon, 15 Dec 2008 07:47:56 -0500: FWIW, I've had the board for a year or so. I learned when I got it that the USB support for the SB600 is bad (based on discussions with the kernel USB mailing list). I worked around that problem with a PCI USB card. 2.6.28 I believe has the fix for that. If not, .29 will. There's definitely a patch ready, I know that, as I've been following a bug based on someone here having that issue. Hi Duncan, That's nice to know. I've been waiting patiently for the 16 months or so I've had the SB600 mobo. Regards, David
[gentoo-amd64] ASUS M2A-VM and kernel 2.6.27
Hi, Anybody using an ASUS M2A-VM mobo with a 2.6.27 kernel? When I attempt to boot a 2.6.27 kernel, I see the Loading modules message (and messages for loaded modules) and then the boot process hangs. With a 2.6.25 kernel, after all the module messages boot displays Activating mdev. I've never seen this message with the 2.6.27 kernel. For that matter, I tried 2.6.26 a while back and had the same problem. Anybody know about this problem or what might cause it? On a related note, a few weeks back I started seeing kernel messages like: PCI-DMA: Out of IOMMU space for 8192 bytes at device :00:14.1 PCI-DMA: Out of IOMMU space for 1536 bytes at device :02:00.0 The 2.6.25 kernel ran fine for several months before these started appearing, so I suspect a hardware issue. However, when running 2.6.27's make xconfig I noticed there's an AMD_IOMMU option. I'd very much like to see if it relates to the messages above. If you've got an M2A-VM running, perhaps you could share your .config with me??? Regards, David
Re: [gentoo-amd64] ASUS M2A-VM and kernel 2.6.27
On Mon, 15 Dec 2008 01:37:28 +0100 Branko Badrljica bran...@avtomatika.com wrote: David Relson wrote: Hi, Anybody using an ASUS M2A-VM mobo with a 2.6.27 kernel? SNIP I have had somewhat similar problems on Phenom. Do you have nvidia card on the machine ? If so, there is some parameter for the module that limits its use of IOMMU space. Also, I thint the problem was rectified in later revisions of the driver. Regards, Branko H'lo Branko, No nvidia. The M2A-VM mobo has builtin ATI Radeon X1200 capability so I have no need for a separate video card. As to the IOMMU, I've already changed the BIOS to allow the maximum memory usage (256MB) for the purpose. The change hasn't stopped the IOMMU out of space messages. I'm truly looking for someone running 64 bit gentoo on the M2A-VM mobo and using a new kernel with the CONFIG_AMD_IOMMU capability. Regards, David
[gentoo-amd64] genkernel [ was: boottime ]
On Wed, 12 Nov 2008 15:43:35 -0500 Mark Haney wrote: [EMAIL PROTECTED] wrote: I allready took everything out of my kernel but is there a big difference with modules or buildin's ? And X allready starts at boot. And why shouldn't I use genkernel? I don't know about moving X, but this is a thread I thought about starting yesterday so this is very timely. I'll look at X to see how things are affected. As for genkernel, that's pretty much like any other distro kernel with lots of added modules and built in drivers that take up more resources and take longer to load. It may not be much on a system, but every second counts. genkernel allows you to configure your kernel (with menuconfig, if I recall). Given a .config file in /usr/src/linux, genkernel will just use it. I've been using genkernel for 2 years with configured kernels and it's been working fine for me. David
Re: [gentoo-amd64] traceroute
On Mon, 30 Jun 2008 00:16:49 +0300 Daniel Iliev wrote: Hi, I have a broken net-analyzer/traceroute-2.0.9-r1. === localhost ~ # traceroute gentoo.org gentoo.org: Bad value for ai_flags Cannot handle host cmdline arg `gentoo.org' on position 1 (argc 1) localhost ~ # === I'd file a bug report for amd64 only if there's someone else here having this problem, because on my x86 systems traceroute works just fine. -- Best regards, Daniel traceroute-2.0.9-r1 is working fine here (Michigan, USA)... -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Kernel 2.6.25
On Tue, 24 Jun 2008 16:27:33 +0200 Christoph Mende wrote: On Tue, 24 Jun 2008 09:50:51 -0400 Mark Haney [EMAIL PROTECTED] wrote: Just out of curiosity, what's taking so long with releasing the .25 kernel to stable? I don't recall any kernel before taking this long to be released. https://bugs.gentoo.org/show_bug.cgi?id=218127 FWIW, while using 2.6.25 I encountered a problem that was resolved by switching to 2.6.24. With a 2.6.25 kernel and linux-headers-2.6.25, vmware-server wasn't happy. More precisely, attempts to load vmnet.ko (for example using 'modprobe vmnet.ko') would log the following: vmnet: disagrees about version of symbol struct_module in /var/log/messages. This occurred even with rebuilds of the kernel and the module. Since switching to 2.6.24 (with 2.6.25's .config file as the basis of the 2.6.24 .config file), all has been fine. Regards, David -- gentoo-amd64@lists.gentoo.org mailing list
