Re: Akmod-nvidia problem
Tim: I wasted ages TRYING to install, before then. Jack: you are referring here to hdinstall, which was thoroughly discussed in these 3 refs: - nov 2008 * F10 HD install - anyone successfully done this? From: Mike Cloaked and response by Tom Horsley Bug 473351 - F10 HD install using the DVD iso file, initiated from grub, fails View this message in context: http://www.nabble.com/F10-HD-install---anyone-successfully-done-this--tp20740373p20741211.html Thanks for that, although that's a different technique than what I was trying to do. That method's more to do with putting your install files onto the drive that you're going to install to, which wasn't possible for me, and probably isn't going to - unless I make a huge boot partition. And that'd still require a lot of effort - putting a laptop drive into an external case (I don't have a spare one), putting the ISO file onto the drive, putting the drive into the laptop... Once you have a system on a drive, i.e. it's not a new one, it's not so hard to prepare a drive so that it has a large spare partition on it to hold install files during installation, that wouldn't get messed with during the installation. The technique I wanted to follow, rather than messing with grub and booting an install image through it, was one I'd used with prior releases: * Download the DVD install ISO file onto an external drive using any available computer. * Attach that drive to the computer to be installed to. * Boot the netinstall disc. * Use the ask method install option. * Tell it where to find my DVD ISO file. * Start installing onto an empty brand new hard drive. I've done that before, and it's far faster than installing from a DVD (with slow seek speeds, spin up / spin down delays, and slower read speed than a hard drive). It was also less messing around, all one had to do was ensure that the CD/DVD drive was the first boot device, to boot the computer from the install disc (no writing of grub menus, no trying to work out which drive was really sda, etc.). Another alternative is to extract all the files from the ISO onto the hard drive, and ask the installer to use the tree of files, rather than the ISO. That seems to work better on some systems, as they seem to die under the load of dealing with a large ISO file. And seems to be the fastest method I've tried (install from the DVD, NFS install, HTTP install, multi-CD-ROM install)... In this instance, the biggest stumbling block seemed to be that the install routine finds the external hard drive inaccessible (SATA drive in a Seagate USB box). It's presence was sort of noticed, to some degree, but that was about it. Since I'm experimenting, I think I'll go through several tests, and prepare this drive with either a large boot partition, or keep a spare install partition to store the ISOs on. I've been avoiding installing updates, as I don't want to waste bandwidth and time, repeatedly installing updates then throwing them away. Incidentally, I tried installing both CentOS 5.3, then tried Fedora 11, onto this laptop. Both had issues with that external drive. As I recall, CentOS asked me to install a driver disc so it could try to access the USB drive, but Fedora didn't. You possibly made a mistake on where you placed the install.img. Or, perhaps, the right install.img? Should I extract one from the netinstall ISO, or the DVD ISO? Are they both the same thing? More likely is the need (starting in F10 and above) for a leading / on the directory holding the iso. Possibly... I had tried with and without leading slash, and likewise with a trailing slash. I really wish Linux would be consistent with that (if it's a directory, end it with a slash, so we can easily tell directory names from file names, and we don't overwrite files when we mean to put a file into a directory). And I really wish the installer would be more helpful, if it needs a leading slash, then prompt for it, and allow us some level of file system browsing instead of requiring us to memorise filepaths. I need to reference that sda1 as sdb1 because w usb anaconda reorders the disks Yes, I thought about that, and I think I did try telling the installer to try both sda1 and sdb1, just in case. It shouldn't happen, in my case, because the boot sequence was first CD ROM, second internal hard drive, no third option. Getting back to the nvidia issue The default install, installed kernel-PAE-2.6.29.4-167.fc11.i686. I managed to miss seeing the PAE bit in there. So I headed off trying to install nvidia for the wrong kernel. Seeing as I only have 1 gig of RAM, I didn't see any need for the PAE kernel. So I did a yum install kernel, and it fetched and installed kernel-2.6.29.6-217.2.7.fc11.i586. According to uname, I have a 686 CPU, and I thought the (something) mistakeningly installs a 586, instead of 686, kernel was an old bug. uname -a Linux
Re: Akmod-nvidia problem
Tim: I wasted ages TRYING to install, before then. Jack: you are referring here to hdinstall, which was thoroughly discussed in these 3 refs: - nov 2008 * F10 HD install - anyone successfully done this? From: Mike Cloaked and response by Tom Horsley .. Thanks for that, although that's a different technique than what I was trying to do. Tim, thanks much for your lengthy reply, especially the detailed steps you use for netinstall. I have zero experience with netinstall, so my prior comments to you probably of little use, if not muddying the waters even more. One thing is really unclear to me: if you cant (or couldn't )access the external usb at all, and that usb is where you have (or had) the dvdiso, it seems to me you can't test whether you have the /images/install.img in the right place or not, and similarly whether your equivalent of my /root/diso has correct leading / or not. OTOH, if you do get access to the usb then you _can_ expect the installer to see the usb first, internal hd second. If instead you move your dvdiso to your internal hd, and keep your usb powered off, then there will be no opportunity for the installer to reorder the disks. Just in case my experience using hdinstall is of use to you, here is specific detaill on location of my /images/install.img [r...@f10 ~]# cd diso [r...@f10 diso]# ls images isolinux [r...@f10 diso]# cd images [r...@f10 images]# ls install.img [r...@f10 images]# pwd /root/diso/images [r...@f10 images]# ls install.img this /root/diso as required, originally was also the location of my f11 dvdiso [I have since moved it out of my f10 system] Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Akmod-nvidia problem
Tim wrote: I wasted ages TRYING to install, before then. ... I seem to recall something about extracting install.img from the ISO, and putting it in the same directory as the main DVD ISO. That didn't work, neither did putting it into a images sub-directory. Tim, you are referring here to hdinstall, which was thoroughly discussed in these 3 refs: - nov 2008 * F10 HD install - anyone successfully done this? From: Mike Cloaked and response by Tom Horsley Bug 473351 - F10 HD install using the DVD iso file, initiated from grub, fails View this message in context: http://www.nabble.com/F10-HD-install---anyone-successfully-done-this--tp20740373p20741211.html --- You possibly made a mistake on where you placed the install.img. More likely is the need (starting in F10 and above) for a leading / on the directory holding the iso. I successfully did an F11 hdinstall following the refs. my hdinstall of f11: where the f11iso is in /root/diso of my f10 on sda1. I need to reference that sda1 as sdb1 because w usb anaconda reorders the disks: title Install Fedora 11 repo=hd:/dev/sdb1:/root/diso reorder root (hdx,y) kernel /boot/f11/vmlinuz noselinux repo=hd:/dev/sdb1:/root/diso initrd /boot/f11/initrd.img #works! used to install f11 to rootusb3 specifically :/root/diso needs that leading / Because i was installing F11 to external usb, it had to be powered on, and then anaconda reordered my disks to place usb first, so /root/diso seen from my f10 on sda1, is seen in anaconda as sdb1 and that has to be specified in my f11 install stanza You don't need to use that repo= form, then instead in the anaconda gui pick /dev/sdb1 and insert /root/diso for the directory HTH Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Akmod-nvidia problem
On Tue, 2009-08-18 at 14:17 +0930, Tim wrote: I just tried akmod-nvidia on Fedora 11 for the first time, the other day. I had to install kernel-devel myself, afterwards, before it could do what it was supposed to. Surely it ought to drag that in as a dependency, then? Installing akmod-nvidia certainly dragged in a pile of other things. When you all say fresh install, does that include all updates (not testing) as well? Is this done before trying to install nvidia or after? 1 - Fresh install and configured (firewall, selinux, networking, etc) to your liking 2 - Updates installed plus programs you like/want added 3 - Make sure your booted into the latest kernel you have installed 4 - Install akmod-nvidia and deps, then reboot. Somewhat of how I do it and don't think I've had any problems installing the akmod or any extra deps as it pulls it all in itself. -- Mike Chambers Madisonville, KY Fedora Project - Bugzapper, Tester, User, etc.. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Akmod-nvidia problem
Tim wrote: I just tried akmod-nvidia on Fedora 11 for the first time, the other day. I had to install kernel-devel myself, afterwards, before it could do what it was supposed to. Surely it ought to drag that in as a dependency, then? Installing akmod-nvidia certainly dragged in a pile of other things. On my x86_64 box, akmod-nvidia does in fact depend on kernel-devel. On i386, it would be kernel-PAE-devel. You could check /var/log/yum.log to see what was installed along with akmod-nvidia. signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Akmod-nvidia problem
On 08/18/2009 02:29 PM, gil...@altern.org wrote: Richard Shaw wrote: On Mon, Aug 17, 2009 at 5:29 PM,gil...@altern.org wrote: Of course, YMMV, but, as far as I'm concerned, I wouldn't advise anybody to use akmod-nvidia. Any way out of this mess? I know I've been guilty of it at times but you have to be careful drawing those types of conclusions from one experience. I've used the akmod-nvidia package for some time without issue and since this is the first posting I've read where someone did have an issue it doesn't look to be that common. As I said, YMMV :) For now, there's a new kernel again and I'll see how it works with kmod-nvidia tomorrow. Whats YMMV My kmod-nvidia doesnt work with the new kernel Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Akmod-nvidia problem
Tim: I just tried akmod-nvidia on Fedora 11 for the first time, the other day. I had to install kernel-devel myself, afterwards, before it could do what it was supposed to. Surely it ought to drag that in as a dependency, then? Installing akmod-nvidia certainly dragged in a pile of other things. Mike Chambers: When you all say fresh install, does that include all updates (not testing) as well? Is this done before trying to install nvidia or after? I booted the DVD, let it install (onto a new, unused, hard drive) with the default options, didn't do any updates, the only things I added to the installation, was first trying kmod-nvidia, but it was missing something, so it wouldn't install, and I noticed I had a pae kernel. Then I installed the ordinary kernel package (yum install kernel), went to install akmod-nvidia (yum install akmod-kernel), it installed but didn't work. Looking at the failure messages during reboot, I thought adding kernel-devel might fix it up. I did a yum install kernel-devel, rebooted, and everything did what it was supposed to. That's it. I forgot about the pae kernel thing, before. The only thing I've done since then was edit the menus, as there was no entry showing to start an email program. Evolution was installed, but the menu entry for it was hidden. Since then, I've pulled the drive. I need to work, and don't have the time to try and get used to a new OS just before doing something I want to rely on the computer for. Experimenting will have to wait a bit. I wasted ages TRYING to install, before then. DVD/CD installs always take an age, and didn't want to use another blank DVD up, so I like to use the smaller net install disc, to boot the machine, and then install from the main image on an external drive. The computer never found my USB hard drive (CentOS 5.3 wouldn't, either). I also tried a NFS install, and that didn't work, either. It'd start, then bog down. I couldn't even ping the machine from another. I seem to recall something about extracting install.img from the ISO, and putting it in the same directory as the main DVD ISO. That didn't work, neither did putting it into a images sub-directory. -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Akmod-nvidia problem
Since Matthew Saltzman was clear about it: I'm surprised the thread has gone on this long without pointing this out: If you install the akmod-nvidia package, it will rebuild the driver automatically when you boot a new kernel. http://www.mail-archive.com/fedora-list@redhat.com/msg49518.html and there certainly was no strong disagreement, after I received the 2.6.29.6-217.2.7.fc11.x86_64 kernel, I installed akmod-nvidia and rebooted. It didn't work. About 2 hours later, the kmod module was available and I knew it had worked well until now. So, I uninstalled akmod and rebooted. It didn't work. I un/reinstalled the kernel. Didn't work. Uninstalled/installed kmod. Didn't work. On the first reboot, I got something like: audit(xxx):auid=xxx ses=xxx subj=system_u:system_r:readahead_t:50 op=remove rulekey=(null) list=2 res=1 audit(xxx):audit_enabled=0 old=1 auid=xxx ses=xxx subj=system_u:system_r:readahead_t:50 res=1 Then, when I reboot, the boot process stops at eth0:link up or Starting atd: [OK]. Then it freezes. Of course, YMMV, but, as far as I'm concerned, I wouldn't advise anybody to use akmod-nvidia. Any way out of this mess? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Akmod-nvidia problem
On Mon, Aug 17, 2009 at 5:29 PM, gil...@altern.org wrote: Since Matthew Saltzman was clear about it: I'm surprised the thread has gone on this long without pointing this out: If you install the akmod-nvidia package, it will rebuild the driver automatically when you boot a new kernel. http://www.mail-archive.com/fedora-list@redhat.com/msg49518.html and there certainly was no strong disagreement, after I received the 2.6.29.6-217.2.7.fc11.x86_64 kernel, I installed akmod-nvidia and rebooted. It didn't work. About 2 hours later, the kmod module was available and I knew it had worked well until now. So, I uninstalled akmod and rebooted. It didn't work. I un/reinstalled the kernel. Didn't work. Uninstalled/installed kmod. Didn't work. On the first reboot, I got something like: audit(xxx):auid=xxx ses=xxx subj=system_u:system_r:readahead_t:50 op=remove rulekey=(null) list=2 res=1 audit(xxx):audit_enabled=0 old=1 auid=xxx ses=xxx subj=system_u:system_r:readahead_t:50 res=1 Then, when I reboot, the boot process stops at eth0:link up or Starting atd: [OK]. Then it freezes. Of course, YMMV, but, as far as I'm concerned, I wouldn't advise anybody to use akmod-nvidia. Any way out of this mess? I know I've been guilty of it at times but you have to be careful drawing those types of conclusions from one experience. I've used the akmod-nvidia package for some time without issue and since this is the first posting I've read where someone did have an issue it doesn't look to be that common. First I have to ask, did you install kernel-headers kernel-devel for the kernel you're booting? I can't remember off hand but at least one if not both of those packages are needed. Second, I would suggest subscribing to the rpmfusion users list since akmod-nvidia is not a fedora provided package. Richard -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Akmod-nvidia problem
Richard Shaw wrote: On Mon, Aug 17, 2009 at 5:29 PM, gil...@altern.org wrote: Of course, YMMV, but, as far as I'm concerned, I wouldn't advise anybody to use akmod-nvidia. Any way out of this mess? I know I've been guilty of it at times but you have to be careful drawing those types of conclusions from one experience. I've used the akmod-nvidia package for some time without issue and since this is the first posting I've read where someone did have an issue it doesn't look to be that common. As I said, YMMV :) For now, there's a new kernel again and I'll see how it works with kmod-nvidia tomorrow. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Akmod-nvidia problem
On Mon, 2009-08-17 at 21:30 -0500, Richard Shaw wrote: First I have to ask, did you install kernel-headers kernel-devel for the kernel you're booting? I can't remember off hand but at least one if not both of those packages are needed. I just tried akmod-nvidia on Fedora 11 for the first time, the other day. I had to install kernel-devel myself, afterwards, before it could do what it was supposed to. Surely it ought to drag that in as a dependency, then? Installing akmod-nvidia certainly dragged in a pile of other things. 1. Fresh install of Fedora 11, from the DVD, with default options. 2. Tried to yum install kmod-nvidia, but there wasn't one prebuilt. 3. So I did yum install akmod-nvidia, rebooted, and watched it fail. 4. Did a yum install kernel-devel, rebooted, and it built the driver and configured itself properly. With the NVidia driver installed, the laptop suspends to RAM and wakes up (I can't recall if I tried suspend to disc). Pulseaudio also works. I'm tempted to say nyah, so I will... -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
