Re: [gentoo-user] Boot hangs after install, no error
On Sunday 27 June 2010 10:50:55 Peter Humphrey wrote: On Saturday 26 June 2010 18:31:05 James Wall wrote: You could also check out Pappy's Kernel Seeds at http://www.kernel-seeds.org.org/ I will - thanks. Turned out it was much simpler than kernel config - it was BOINC. Now all I have to do is to find more suitable parameters for it on a 4-core box. -- Rgds Peter. Linux Counter 5290, 1994-04-23.
Re: [gentoo-user] Boot hangs after install, no error
On Saturday 26 June 2010 18:31:05 James Wall wrote: You could also check out Pappy's Kernel Seeds at http://www.kernel-seeds.org.org/ I will - thanks. -- Rgds Peter. Linux Counter 5290, 1994-04-23.
Re: [gentoo-user] Boot hangs after install, no error
On 6/23/2010 4:36 AM, Peter Humphrey wrote: On Wednesday 23 June 2010 03:29:16 Dale wrote: By all means, use genkernel. I will, RSN. This nearly new, shiny, quad-core box is as sluggish as hell, and I want to find out why. So I'll use genkernel to install everything under the sun and see if I can work it out. You could also check out Pappy's Kernel Seeds at http://www.kernel-seeds.org.org/
Re: [gentoo-user] Boot hangs after install, no error
On Wednesday 23 June 2010 03:29:16 Dale wrote: By all means, use genkernel. I will, RSN. This nearly new, shiny, quad-core box is as sluggish as hell, and I want to find out why. So I'll use genkernel to install everything under the sun and see if I can work it out. -- Rgds Peter. Linux Counter 5290, 1994-04-23.
Re: [gentoo-user] Boot hangs after install, no error
On 06/21/2010 03:37 PM, Dale wrote: I'm not saying you can't use it just that it doesn't always work. Thing is, when someone uses genkernel to make the kernel, when someone asks 'did you include some driver', the usual answer is 'I don't know, I used genkernel' and then nobody knows whether it is there or not. If a person builds their own kernel, they usually know if it is there and better yet how to check and make sure it is there. Also, I don't use initrd and not sure why most people need one. I don't use modules either, hence the reason I don't need initrd. Just build in the drivers and such that are needed to boot until the modules are loaded and that's it. It's not rocket science. Driver controller, file system that root uses and that's about it. And all I'm trying to point out is that you're making a leap of incorrect logic by ascribing to genkernel characteristics that it doesn't have. The root cause is that they've misconfigured something, so the red herring of I blah blah blah genkernel blah blah blah shouldn't set off alarms. I've been using it for years and it's always worked for me. Very few times I have seen it crash while trying to build, but never have I seen it do anything untoward or unexpected. Maybe part of the issue is that users might rely on it without supplying enough arguments to it. I had to write my script because I was getting carpal tunnel from typing out the stupid command so many times. That said, I *always* use the --kerneldir argument, so that might explain some things. By default, it just uses /usr/src/linux, even if you're in some other directory, and if you're not aware of that, yeah, I can see how you could bite off your own toes pretty easily and not even notice.
Re: [gentoo-user] Boot hangs after install, no error
Bill Longman wrote: On 06/21/2010 03:37 PM, Dale wrote: I'm not saying you can't use it just that it doesn't always work. Thing is, when someone uses genkernel to make the kernel, when someone asks 'did you include some driver', the usual answer is 'I don't know, I used genkernel' and then nobody knows whether it is there or not. If a person builds their own kernel, they usually know if it is there and better yet how to check and make sure it is there. Also, I don't use initrd and not sure why most people need one. I don't use modules either, hence the reason I don't need initrd. Just build in the drivers and such that are needed to boot until the modules are loaded and that's it. It's not rocket science. Driver controller, file system that root uses and that's about it. And all I'm trying to point out is that you're making a leap of incorrect logic by ascribing to genkernel characteristics that it doesn't have. The root cause is that they've misconfigured something, so the red herring of I blah blah blah genkernel blah blah blah shouldn't set off alarms. I've been using it for years and it's always worked for me. Very few times I have seen it crash while trying to build, but never have I seen it do anything untoward or unexpected. Maybe part of the issue is that users might rely on it without supplying enough arguments to it. I had to write my script because I was getting carpal tunnel from typing out the stupid command so many times. That said, I *always* use the --kerneldir argument, so that might explain some things. By default, it just uses /usr/src/linux, even if you're in some other directory, and if you're not aware of that, yeah, I can see how you could bite off your own toes pretty easily and not even notice. Things is, I have seen genkernel fail for lots of people. I have never had my way to fail. I may forget a option or have to add a option when adding hardware but I have never had make make modules_install fail. The copy process always works too. It's not a leap from my point of view. Maybe you are just lucky so far. Some people use genkernel and it works but a lot have problems with it too. Funny thing is, when a person comes for help and genkernel is being used, not much help is offered. The other thread I mentioned earlier is getting help but not with genkernel. We are helping him with building his own tho and figuring out the options. This sort of reminds me of cdrkit and cdrtools. You can use cdrkit of you want. Thing is, you won't get much help with it because it is buggy and just doesn't work with some hardware. You can use it tho. It's still your choice. By all means, use genkernel. Dale :-) :-)
Re: [gentoo-user] Boot hangs after install, no error
snip This is funny. I have NEVER got a genkernel to work on my system. Actually, on any system. I'm not sure the OP would know that kernel is any better then the one he makes. Dale, If you've never gotten genkernel to work, you should try this little script that I've used for the past few years. I put it in /usr/src/gk and I change into whatever /usr/src/kernel directory I'm going to compile. Then, I just call ../gk all and off it goes. Of course, if you use lilo, it's a different story because I jumped out of the lilo life raft years ago and managed to swim to shore. Here's gk. Tweak to your environment: CFLAGS=-O2 -march=barcelona -pipe \ genkernel --lvm --menuconfig --save-config --oldconfig \ --bootloader=grub --install --symlink --kerneldir=$PWD \ --makeopts=-s -j4 $@ -- Bill
Re: [gentoo-user] Boot hangs after install, no error
Bill Longman wrote: snip This is funny. I have NEVER got a genkernel to work on my system. Actually, on any system. I'm not sure the OP would know that kernel is any better then the one he makes. Dale, If you've never gotten genkernel to work, you should try this little script that I've used for the past few years. I put it in /usr/src/gk and I change into whatever /usr/src/kernel directory I'm going to compile. Then, I just call ../gk all and off it goes. Of course, if you use lilo, it's a different story because I jumped out of the lilo life raft years ago and managed to swim to shore. Here's gk. Tweak to your environment: CFLAGS=-O2 -march=barcelona -pipe \ genkernel --lvm --menuconfig --save-config --oldconfig \ --bootloader=grub --install --symlink --kerneldir=$PWD \ --makeopts=-s -j4 $@ -- Bill I don't use genkernel anymore. I just roll my own. That way, I know what is in there and what is not. Then if something doesn't work, I know if it is the kernel or something else. With genkernel, you won't have a clue what it is since you don't know much if anything about the kernel and how it is configured. I'll pass. As I have seen with others, genkernel doesn't work consistently enough. Dale :-) :-)
Re: [gentoo-user] Boot hangs after install, no error
Dale writes: I don't use genkernel anymore. I just roll my own. That way, I know what is in there and what is not. Then if something doesn't work, I know if it is the kernel or something else. With genkernel, you won't have a clue what it is since you don't know much if anything about the kernel and how it is configured. That's not necessarily true. When I create a new kernel, I copy /usr/src/linux/.config into the new kernel directory, make oldconfig and menuconfig just as I like my kernel to be, and recreate the linux symlink to the new kernel directory. Then I do a genkernel --install --lvm --luks all emerge -a @module-rebuild, and am done. I never noticed genkernel changing anything in my configuration, .config, /proc/config.gz and the stuff in /etc/kernels/ are identical. Until not long ago, I did not even know that genkernel was intended to create a working kernel from scratch. Wonko
Re: [gentoo-user] Boot hangs after install, no error
Alex Schuster wrote: Dale writes: I don't use genkernel anymore. I just roll my own. That way, I know what is in there and what is not. Then if something doesn't work, I know if it is the kernel or something else. With genkernel, you won't have a clue what it is since you don't know much if anything about the kernel and how it is configured. That's not necessarily true. When I create a new kernel, I copy /usr/src/linux/.config into the new kernel directory, make oldconfig and menuconfig just as I like my kernel to be, and recreate the linux symlink to the new kernel directory. Then I do a genkernel --install --lvm --luks all emerge -a @module-rebuild, and am done. I never noticed genkernel changing anything in my configuration, .config, /proc/config.gz and the stuff in /etc/kernels/ are identical. Until not long ago, I did not even know that genkernel was intended to create a working kernel from scratch. Wonko I always do mine this way. I copy the .config from the old kernel to the new kernel, run make oldconfig then afterwards make all make modules_install and then copy the kernel to /boot with my own numbering system. That way I know which version and series the kernel is. After that, edit grub with the new kernel and I'm done. I have only had that fail once in the past six years or so and the kernel made some serious changes and I had to start from scratch that one time. They moved things around and oldconfig couldn't reorganize things on the new kernel. Point being, genkernal causes issues for people and they don't know how to fix it because they expect genkernel to do everything. Problem with that is that usually when someone has a kernel problem, they use genkernel. If they do their own, it just works. Now someone new to building a kernel may need some help but apparently genkernel needs some help anyway. May as well learn how to roll your own. This is Gentoo after all. Dale :-) :-)
Re: [gentoo-user] Boot hangs after install, no error
On 06/21/2010 12:01 PM, Dale wrote: Alex Schuster wrote: Dale writes: I don't use genkernel anymore. I just roll my own. That way, I know what is in there and what is not. Then if something doesn't work, I know if it is the kernel or something else. With genkernel, you won't have a clue what it is since you don't know much if anything about the kernel and how it is configured. That's not necessarily true. When I create a new kernel, I copy /usr/src/linux/.config into the new kernel directory, make oldconfig and menuconfig just as I like my kernel to be, and recreate the linux symlink to the new kernel directory. Then I do a genkernel --install --lvm --luks all emerge -a @module-rebuild, and am done. I never noticed genkernel changing anything in my configuration, .config, /proc/config.gz and the stuff in /etc/kernels/ are identical. Until not long ago, I did not even know that genkernel was intended to create a working kernel from scratch. Wonko I always do mine this way. I copy the .config from the old kernel to the new kernel, run make oldconfig then afterwards make all make modules_install and then copy the kernel to /boot with my own numbering system. That way I know which version and series the kernel is. After that, edit grub with the new kernel and I'm done. I have only had that fail once in the past six years or so and the kernel made some serious changes and I had to start from scratch that one time. They moved things around and oldconfig couldn't reorganize things on the new kernel. Point being, genkernal causes issues for people and they don't know how to fix it because they expect genkernel to do everything. Problem with that is that usually when someone has a kernel problem, they use genkernel. If they do their own, it just works. Now someone new to building a kernel may need some help but apparently genkernel needs some help anyway. May as well learn how to roll your own. This is Gentoo after all. The only thing that genkernel would add is your initrd. The kernel is exactly the same, whether you compile it with make or through genkernel. Do a test and you'll see. (I'm assuming we're both talking about gentoo-sources, not vanilla-sources. Either way, they'd be the same.) Some might be confused about what happens in the steps if they haven't been down the kernel compilation trail more than once or twice, but for folks who just want to compile their kernel and plop it into place, along with a hands-off initrd, it's rather handy.
Re: [gentoo-user] Boot hangs after install, no error
Bill Longman wrote: On 06/21/2010 12:01 PM, Dale wrote: Alex Schuster wrote: Dale writes: I don't use genkernel anymore. I just roll my own. That way, I know what is in there and what is not. Then if something doesn't work, I know if it is the kernel or something else. With genkernel, you won't have a clue what it is since you don't know much if anything about the kernel and how it is configured. That's not necessarily true. When I create a new kernel, I copy /usr/src/linux/.config into the new kernel directory, make oldconfig and menuconfig just as I like my kernel to be, and recreate the linux symlink to the new kernel directory. Then I do a genkernel --install --lvm --luks all emerge -a @module-rebuild, and am done. I never noticed genkernel changing anything in my configuration, .config, /proc/config.gz and the stuff in /etc/kernels/ are identical. Until not long ago, I did not even know that genkernel was intended to create a working kernel from scratch. Wonko I always do mine this way. I copy the .config from the old kernel to the new kernel, run make oldconfig then afterwards make all make modules_install and then copy the kernel to /boot with my own numbering system. That way I know which version and series the kernel is. After that, edit grub with the new kernel and I'm done. I have only had that fail once in the past six years or so and the kernel made some serious changes and I had to start from scratch that one time. They moved things around and oldconfig couldn't reorganize things on the new kernel. Point being, genkernal causes issues for people and they don't know how to fix it because they expect genkernel to do everything. Problem with that is that usually when someone has a kernel problem, they use genkernel. If they do their own, it just works. Now someone new to building a kernel may need some help but apparently genkernel needs some help anyway. May as well learn how to roll your own. This is Gentoo after all. The only thing that genkernel would add is your initrd. The kernel is exactly the same, whether you compile it with make or through genkernel. Do a test and you'll see. (I'm assuming we're both talking about gentoo-sources, not vanilla-sources. Either way, they'd be the same.) Some might be confused about what happens in the steps if they haven't been down the kernel compilation trail more than once or twice, but for folks who just want to compile their kernel and plop it into place, along with a hands-off initrd, it's rather handy. But only if it works. When I compile my kernel, I KNOW for sure what is in there. When genkernel does one, especially on a new install, I have no idea what is in it or what is not. If something goes wrong, I don't know where to start. Is it a kernel problem or is it something else? Who knows. Then you have to go back and start from the bottom, usually the kernel, and work your way back up to find out what is broken. Genkernel may work for you but that doesn't mean it does for everyone else. Should I mention hal here? When someone comes for help, your looking for the failure not the successes. If it was sucessful, they wouldn't need help. Dale :-) :-)
Re: [gentoo-user] Boot hangs after install, no error
On 06/21/2010 01:23 PM, Dale wrote: The only thing that genkernel would add is your initrd. The kernel is exactly the same, whether you compile it with make or through genkernel. Do a test and you'll see. (I'm assuming we're both talking about gentoo-sources, not vanilla-sources. Either way, they'd be the same.) Some might be confused about what happens in the steps if they haven't been down the kernel compilation trail more than once or twice, but for folks who just want to compile their kernel and plop it into place, along with a hands-off initrd, it's rather handy. But only if it works. When I compile my kernel, I KNOW for sure what is in there. When genkernel does one, especially on a new install, I have no idea what is in it or what is not. If something goes wrong, I don't know where to start. Is it a kernel problem or is it something else? Who knows. Then you have to go back and start from the bottom, usually the kernel, and work your way back up to find out what is broken. By But only if it works, I assume the antecedent it refers to is a kernel that we're attempting to boot correctly. (In other words, you're not talking about genkernel failing to create a kernel for you. Is that correct?) If someone has trouble on an initial install, then that just means they didn't configure the kernel correctly, is what I interpret that to mean. The result of make and the result of genkernel kernel are exactly the same. If your make menuconfig creates an invalid .config file for you, no sort of magic is going to make its resultant kernel valid. Do you mean to say that you just grab a kernel, jump into the directory and say make without an mrproper and some sort of config? You do realize that genkernel has --menuconfig, --xconfig and --gconfig exactly for this purpose, don't you? What sort of things do you believe genkernel is adding to your kernel? If you use genkernel --menuconfig --no-install kernel, you can look and see what it did. It's no different than running make menuconfig followed by a make; make modules. Just look in /usr/share/genkernel at the gen_compile.sh and you'll see that it does a make. Genkernel may work for you but that doesn't mean it does for everyone else. Should I mention hal here? When someone comes for help, your looking for the failure not the successes. If it was sucessful, they wouldn't need help. Which is why I mentioned genkernel in the first place. Most times a hang after boot is due to components that were missed in the kernel build -- from where? -- from a missing or incorrectly created initrd if the required modules weren't compiled into the kernel. The easiest way that I've seen is to use genkernel and get back to work. Then later on you can find out what an initrd is and why it's needed with modules but at least you'd have a running system. No, I don't think you should mention hal because it's probably OT for a thread about a hung boot. But you should apply to yourself a similar logic you ask of me: if others can use genkernel successfully, why can't I? Bill
Re: [gentoo-user] Boot hangs after install, no error
Bill Longman wrote: On 06/21/2010 01:23 PM, Dale wrote: The only thing that genkernel would add is your initrd. The kernel is exactly the same, whether you compile it with make or through genkernel. Do a test and you'll see. (I'm assuming we're both talking about gentoo-sources, not vanilla-sources. Either way, they'd be the same.) Some might be confused about what happens in the steps if they haven't been down the kernel compilation trail more than once or twice, but for folks who just want to compile their kernel and plop it into place, along with a hands-off initrd, it's rather handy. But only if it works. When I compile my kernel, I KNOW for sure what is in there. When genkernel does one, especially on a new install, I have no idea what is in it or what is not. If something goes wrong, I don't know where to start. Is it a kernel problem or is it something else? Who knows. Then you have to go back and start from the bottom, usually the kernel, and work your way back up to find out what is broken. By But only if it works, I assume the antecedent it refers to is a kernel that we're attempting to boot correctly. (In other words, you're not talking about genkernel failing to create a kernel for you. Is that correct?) If someone has trouble on an initial install, then that just means they didn't configure the kernel correctly, is what I interpret that to mean. The result of make and the result of genkernel kernel are exactly the same. If your make menuconfig creates an invalid .config file for you, no sort of magic is going to make its resultant kernel valid. Do you mean to say that you just grab a kernel, jump into the directory and say make without an mrproper and some sort of config? You do realize that genkernel has --menuconfig, --xconfig and --gconfig exactly for this purpose, don't you? What sort of things do you believe genkernel is adding to your kernel? If you use genkernel --menuconfig --no-install kernel, you can look and see what it did. It's no different than running make menuconfig followed by a make; make modules. Just look in /usr/share/genkernel at the gen_compile.sh and you'll see that it does a make. Genkernel may work for you but that doesn't mean it does for everyone else. Should I mention hal here? When someone comes for help, your looking for the failure not the successes. If it was sucessful, they wouldn't need help. Which is why I mentioned genkernel in the first place. Most times a hang after boot is due to components that were missed in the kernel build -- from where? -- from a missing or incorrectly created initrd if the required modules weren't compiled into the kernel. The easiest way that I've seen is to use genkernel and get back to work. Then later on you can find out what an initrd is and why it's needed with modules but at least you'd have a running system. No, I don't think you should mention hal because it's probably OT for a thread about a hung boot. But you should apply to yourself a similar logic you ask of me: if others can use genkernel successfully, why can't I? Bill I'm not saying you can't use it just that it doesn't always work. Thing is, when someone uses genkernel to make the kernel, when someone asks 'did you include some driver', the usual answer is 'I don't know, I used genkernel' and then nobody knows whether it is there or not. If a person builds their own kernel, they usually know if it is there and better yet how to check and make sure it is there. Also, I don't use initrd and not sure why most people need one. I don't use modules either, hence the reason I don't need initrd. Just build in the drivers and such that are needed to boot until the modules are loaded and that's it. It's not rocket science. Driver controller, file system that root uses and that's about it. I haven't used genkernel in a while. I have just seen where people have used it and it not work. Same as hal. It works for most but when it doesn't, no one can figure out why because few people know how the thing works and even fewer can figure out the config file. That's not quite as off topic as it appears. If you want to use genkernel, go for it. I just know this, when someone asks for help that may be kernel related and they use genkernel, there is very very little help I can provide. Some people here use genkernel but there are a lot that don't. There is another thread posted a day or so ago where they used genkernel, no one has been able to help them yet. Not one reply that I have seen. I want to help but with genkernel, I have no idea where to start. I'm sure it is a kernel issue but that's about it. It appears that on one else can help either. It's not like this is a small mailing list with few people on it. It's your choice. Use whatever makes you happy and gets you where you want to go. Dale :-) :-)
Re: [gentoo-user] Boot hangs after install, no error
On Fri, 2010-06-18 at 14:26 +1000, Jake Moe wrote: No, I was tempted to try genkernel, but again, OCD got the best of me; I like Gentoo because I tell it what I want and need, and it does that and nothing else. Genkernel, in my understand, does everything (and apparently does it pretty well), but it means that it's bigger than it needs to be. Plus, I hadn't gotten a reply back in a while, and I'm limited on time with this laptop, so I went back to that which I know better. And I thought the Live CD used genkernel; I thought that was where genkernel came from in the first place? Is it different? I have no idea; I don't use genkernel. All I'm saying is if you can try booting on a kernel you know at least *should* work (such as the live cd or genkernel) and that works then at least you can deduce it down to kernel config. -a
Re: [gentoo-user] Boot hangs after install, no error
Albert Hopkins wrote: On Fri, 2010-06-18 at 14:26 +1000, Jake Moe wrote: No, I was tempted to try genkernel, but again, OCD got the best of me; I like Gentoo because I tell it what I want and need, and it does that and nothing else. Genkernel, in my understand, does everything (and apparently does it pretty well), but it means that it's bigger than it needs to be. Plus, I hadn't gotten a reply back in a while, and I'm limited on time with this laptop, so I went back to that which I know better. And I thought the Live CD used genkernel; I thought that was where genkernel came from in the first place? Is it different? I have no idea; I don't use genkernel. All I'm saying is if you can try booting on a kernel you know at least *should* work (such as the live cd or genkernel) and that works then at least you can deduce it down to kernel config. -a This is funny. I have NEVER got a genkernel to work on my system. Actually, on any system. I'm not sure the OP would know that kernel is any better then the one he makes. Dale :-) :-)
Re: [gentoo-user] Boot hangs after install, no error
Jake, Jake Moe jakesaddr...@gmail.com writes: I've just completed a fresh Gentoo installation on a new laptop, and strangely, after I choose the entry from the Grub screen, all I get is: Booting `Gentoo Linux 2.6.32-r7` root (hd0,1) Filesystem type is ext2fs, partition type 0x83 kernel /kernel-2.6.32-gentoo-r7 root=/dev/sda4 [Linux-bzImage, setup=0x3000, size=0x1ab020] It then sits there. No error, no other messages. The hard drive light stops, and the Num Lock and Caps Lock keys don't respond. If I press the power button, it immediately turns off. The laptop is a HP 8440p and I've installed amd64. I've followed the install guide, and the hard drive has Windows, EXT2 /boot, swap, EXT3 / on it. I've compiled EXT2, EXT3 and SATA AHCI into the kernel. Does anyone have any idea what I've forgotten or missed? If you need more info, let me know. Thanks for any help you can give. I had a similar problem about 6 weeks or so ago. It turned out that the hardware (a Dell Optiplex 320) and Grub were incompatible in some way. I installed Lilo instead, and everything now works fine. So, try searching on your specific hardware to see if this is a known problem. Roger
Re: [gentoo-user] Boot hangs after install, no error
On 17/06/10 20:38, Roger Mason wrote: Jake, Jake Moe jakesaddr...@gmail.com writes: I've just completed a fresh Gentoo installation on a new laptop, and strangely, after I choose the entry from the Grub screen, all I get is: Booting `Gentoo Linux 2.6.32-r7` root (hd0,1) Filesystem type is ext2fs, partition type 0x83 kernel /kernel-2.6.32-gentoo-r7 root=/dev/sda4 [Linux-bzImage, setup=0x3000, size=0x1ab020] It then sits there. No error, no other messages. The hard drive light stops, and the Num Lock and Caps Lock keys don't respond. If I press the power button, it immediately turns off. The laptop is a HP 8440p and I've installed amd64. I've followed the install guide, and the hard drive has Windows, EXT2 /boot, swap, EXT3 / on it. I've compiled EXT2, EXT3 and SATA AHCI into the kernel. Does anyone have any idea what I've forgotten or missed? If you need more info, let me know. Thanks for any help you can give. I had a similar problem about 6 weeks or so ago. It turned out that the hardware (a Dell Optiplex 320) and Grub were incompatible in some way. I installed Lilo instead, and everything now works fine. So, try searching on your specific hardware to see if this is a known problem. Roger I had tried to see if there was anything special about the hardware, but couldn't find anything. I'm still of the opinion that it's something to do with the kernel, but I've given up on amd64 (I'm not sure if I've had an amd64 Gentoo PC before) and switched back to x86, and other than forgetting SCSI disk support in the kernel for my SATA disk (which I *always* do, why can't they make SCSI disk support a requirement for SATA AHCI support?), the install went smoothly. The only other thing of note is that I seem to need to use the unstable ndivia-drivers (195.36.24), as the latest stable one (190.42-r3) produced flickering garbage on my screen when I went into X. Thanks for trying to those that did. Jake Moe
Re: [gentoo-user] Boot hangs after install, no error
On Fri, 2010-06-18 at 13:54 +1000, Jake Moe wrote: I had tried to see if there was anything special about the hardware, but couldn't find anything. I'm still of the opinion that it's something to do with the kernel, but I've given up on amd64 (I'm not sure if I've had an amd64 Gentoo PC before) and switched back to x86, and other than forgetting SCSI disk support in the kernel for my SATA disk (which I *always* do, why can't they make SCSI disk support a requirement for SATA AHCI support?), the install went smoothly. The only other thing of note is that I seem to need to use the unstable ndivia-drivers (195.36.24), as the latest stable one (190.42-r3) produced flickering garbage on my screen when I went into X. Thanks for trying to those that did. Jake Moe Did you compile your own kernel or use genkernel? Did you try using the same kernel config as the live cd (assuming that the livecd boots fine)? -a
Re: [gentoo-user] Boot hangs after install, no error
On 18/06/10 14:05, Albert Hopkins wrote: On Fri, 2010-06-18 at 13:54 +1000, Jake Moe wrote: I had tried to see if there was anything special about the hardware, but couldn't find anything. I'm still of the opinion that it's something to do with the kernel, but I've given up on amd64 (I'm not sure if I've had an amd64 Gentoo PC before) and switched back to x86, and other than forgetting SCSI disk support in the kernel for my SATA disk (which I *always* do, why can't they make SCSI disk support a requirement for SATA AHCI support?), the install went smoothly. The only other thing of note is that I seem to need to use the unstable ndivia-drivers (195.36.24), as the latest stable one (190.42-r3) produced flickering garbage on my screen when I went into X. Thanks for trying to those that did. Jake Moe Did you compile your own kernel or use genkernel? Did you try using the same kernel config as the live cd (assuming that the livecd boots fine)? -a No, I was tempted to try genkernel, but again, OCD got the best of me; I like Gentoo because I tell it what I want and need, and it does that and nothing else. Genkernel, in my understand, does everything (and apparently does it pretty well), but it means that it's bigger than it needs to be. Plus, I hadn't gotten a reply back in a while, and I'm limited on time with this laptop, so I went back to that which I know better. And I thought the Live CD used genkernel; I thought that was where genkernel came from in the first place? Is it different? Jake Moe
[gentoo-user] Boot hangs after install, no error
I've just completed a fresh Gentoo installation on a new laptop, and strangely, after I choose the entry from the Grub screen, all I get is: Booting `Gentoo Linux 2.6.32-r7` root (hd0,1) Filesystem type is ext2fs, partition type 0x83 kernel /kernel-2.6.32-gentoo-r7 root=/dev/sda4 [Linux-bzImage, setup=0x3000, size=0x1ab020] It then sits there. No error, no other messages. The hard drive light stops, and the Num Lock and Caps Lock keys don't respond. If I press the power button, it immediately turns off. The laptop is a HP 8440p and I've installed amd64. I've followed the install guide, and the hard drive has Windows, EXT2 /boot, swap, EXT3 / on it. I've compiled EXT2, EXT3 and SATA AHCI into the kernel. Does anyone have any idea what I've forgotten or missed? If you need more info, let me know. Thanks for any help you can give. Jake Moe
