Re: ASUS A8N-SLI Motherboard: comments?
Pete Klemm wrote: A. E. Lawrence is correct on the disk enumeration issue. I am running 2.6.12-686-smp with udev 0.87-1 and the disk enumeration is quite flaky as some times it boots properly and other times not. udev also has a problem with my Radeon 7000VE in that I did have a few problems with disc enumeration order differing between install and sarge, but this was on a fairly complex system with 4 SATA drives, a couple of genuine scsi drives and a legacy PATA (ie IDE) drive. The grub menu written by the installer tried to boot from the wrong disc (because of said enumeration difference), so I used a grub floppy and edited the entries on the first boot, and then changed them permanently. I should have mentioned in my earlier reply that I think I also had to correct /etc/fstab which was also written incorrectly by the installer. I may also have had to correct other configuration files, but it is a long time ago now. Not difficult once you realize what is going on, but it would be very tough for anyone new to Linux to sort out and you definitely have to think about how to get a bootable system. I think that I needed to mount the target file system with a rescue disc in order to fix /etc/fstab. But as several people have said, there should not be a problem with a single disc. ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ASUS A8N-SLI Motherboard: comments?
Hendrik Tews wrote: Dear all, does anybody have experiences with the ASUS A8N-SLI Motherboard or its Deluxe variant? Does Debian run out of the box on it? I did have a few problems with disc enumeration order differing between install and sarge, but this was on a fairly complex system with 4 SATA drives, a couple of genuine scsi drives and a legacy PATA (ie IDE) drive. The grub menu written by the installer tried to boot from the wrong disc (because of said enumeration difference), so I used a grub floppy and edited the entries on the first boot, and then changed them permanently. Most people with simpler systems have no problems. Unless my memory is failing, Jo is not right in recommending the Via K8T890: it is a Nvidia nforce4 chipset. Maybe Len's 2.6.12 installer might get around the problems that I saw: I expect that the disc enumeration will match. ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE in AMD64 etch
Graham Cobb wrote: don't think using sarge is an option because I don't think it has support for the nVidia components on the ASUS A8N-SLI motherboard I am using (am I wrong?). I run AMD64 sarge on an A8N-SLI with nvidia video, but I roll my own kernels and had to `weave and duck' to get the system installed in the first place. ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nvidia (graphics) driver pain
Lennart Sorensen wrote: On Thu, Nov 03, 2005 at 03:07:13PM +0100, Hans wrote: No, this is only necessary, if you want to use 32-bit programs in 64-bit environment (I use this i.e. for X-Plane (this is a flight simulator)). BTW: In Kernel 2.6.14, the kernel-module can be built, but not loaded, due to an obsolete parameter in the sources ! I recommend to use 2.6.12, this work fine. But use 7174, 7176 and higher will not work (so it is for me). 7174 works with amd64 on 2.6.14 (stock kernel, package from nvidia, not debian packaged). ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 archive move
Joerg Jaspert wrote: There will be multiple mirrors, yes. Already mirroring are bytekeeper.as28747.net and bach.hpc2n.umu.se Could someone post the URI on bach.hpc2n.umu.se: I only seem to be able to see the old mirror. Thankyou. ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing on nforce4 amd...
Lars Schimmer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I got the debian 64bit netinstaller from 10 of april 2005 yesterday and tried to install. I took the sid installer, btw. But it couldn't install lilo or grub on my SATA HD on the asus A8NV nforce4 board. And without a bootloader linux won't start... This is likely to be a disc enumeration problem. Look in the archives for similar reports and a solution. Are you quite sure that you told the installer to write to the right hard disc/partition? The installer and the installed system may disagree about the identity of root. ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing nvidia driver for pci express 6600GT?
Ed Cogburn wrote: Thanks Lawrence, if you have access to that machine could you show us what lspci -vv shows for the video card? Does the output mention a "capability" related to PCIe, or is it like Alexander's output from the earlier post? That is a home machine and I won't be there until the week end. I hope that the problem will be solved by then :-) ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing nvidia driver for pci express 6600GT?
Lennart Sorensen wrote: On Tue, Apr 19, 2005 at 05:41:20PM +0200, Alexander Fieroch wrote: I didn't get the geforce 6600GT to work with xfree86 so I have installed xorg but the nvidia driver is not found too. I suggest going back to xfree86 and following the README in the nvidia-kernel-source package. It seems to work for most people, although it may be that PCIe is a problem (although I have seen people say they have it working on A8N-SLI boards which are PCIe as well). I have already confirmed that a 6600GT PCIe clone works fine with xfree86 and the nvidia driver: that is indeed on an Asus A8N-SLI. ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing nvidia driver for pci express 6600GT?
Jacob Larsen wrote: Alexander Fieroch wrote: So whats the problem with the proprietary nvidia driver? The module can be loaded with modprobe and lsmod shows me that it is loaded, but xorg says "(EE) Failed to load module "nvidia" (module does not exist, 0)"! There are two components: a kernel module which sounds as if it is loaded, and a driver module which is loaded by X which it sounds as if you are not finding. Almost certainly a ModulePath (?) problem. ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installer and installed system differ in disk enumeration
Toshikazu Aiyama, Ph.D. wrote: A.E.Lawrence wrote: I have a similar set up with you: ASUS a8n-sli Deluxe mbrd populated with 5 hard disks: a) 1 scsi MO on adaptec 2940UW b) 1 PATA primary master c) 4 sata on nv_sata, none on sil_SATA In addition, I have 1 DVD-RAM, and 1 CD-RW on PATA secondary. Mine is pretty similar, but my pata drive is on the ide1 channel, and it is not the boot disc. I do not use grub becasue it uses a kind of relative disk assignment: 1st disk is hdd0, and 2nd disk is hdd1, and so on; thus if I change the disk configurations, there is no easy way to boot the system, at least, to grub-ignorant people like me. It just uses Bios enumeration. If you are using an installer, the steps are as follows, I think. After a chosen kernel is installed, we can choose a boot loader: grub or lilo. I believe grub or lilo is a mutually exclusive options; thus since you are talking about grub, you are in the position to follow my suggestions. Of course, you can simply ignore me. The problem is that the installer then wrote the wrong root=drive parameter for the kernel. I could fix that with the grub edit. If I use non-default pre-compiled image, disk on 2940UW is recognized as scsi4 by the installer kernel, and the same disk is recognized as scsi0 by the installed kernel. But if I use non-default image, the SATA2 disk on nv_sata is recognized as scsi0 by both installer kerenel and the installed kernel. Maybe that is another way I could have solved my problem. Anyway, I am up and running now. Thanks for the comments. Let's hope that these entries in the archive will be useful for anyone else who has these sorts of problems. ael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
