Re: [gentoo-user] Suspend questions
James Colby wrote: I have trying to set up Suspend on my Dell Latitude D620 laptop. The laptop is currently running a 2.6.19-gentoo-r5 kernel. I emerged the suspend2 sources, copied the .config from the 2.6.19 directory and ran make oldconfig. I then configured the suspend options in the kernel via the docs in the wiki. When I try to boot the suspend kernel, the system fails to boot because it can't find any of the filesystems located in my /etc/fstab. The reason for that is because the suspend kernel is configuring my hard disk as /dev/hda and my standard kernel is configuring it as /dev/sda. Does anyone know how I can get the suspend kernel to assign my hard disk as /dev/sda? I had this problem when I upgraded my kernel a month ago or so. I believe it occurred because the standard ATA driver grew support for my SATA hardware. It was unfortunately probing before the SATA driver and grabbing the device. The best solution I found was to add the following to the boot line in grub: hda=noprobe hda=none Hope that helps. James - Ben -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Suspend questions
Steve Dommett wrote: On Wednesday 03 October 2007, James Colby wrote: The reason for that is because the suspend kernel is configuring my hard disk as /dev/hda and my standard kernel is configuring it as /dev/sda. Does anyone know how I can get the suspend kernel to assign my hard disk as /dev/sda? I think eventually you would have run into this problem even if you hadn't switched to using suspend2-sources. Recent changes in the kernel (at 2.6.21 unless my memory fails me) removed the need for most SATA drivers to use the SCSI layer of the kernel. The result being that many hard drives that were previously addressed as /dev/sda will now be available at /dev/hda. You'll need to change at least /boot/grub/grub.conf and /etc/fstab to reflect this . Yes, it's a pest because it complicates booting into older kernels. You may not know that GRUB supports editing the boot parameters with the 'E' key, which goes a long way towards easing the pains. I think its preferable to get the SATA driver to handle the device if you can. I know on my machine disk performance dropped quite a bit when it was probed as hda by the ATA driver. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Why can't kernel-2.6.19-gentoo-r5 see my root partition?
Michael Sullivan wrote:
I upgraded my kernel to 2.6.19-gentoo-r6 this morning. I used
genkernel. I followed these steps:
Deleted the /usr/src/linux symlink and recreated it point
to /usr/src/2.6.19-gentoo-r5
zcat /proc/config.gz /usr/share/genkernel/x86/kernel-config-2.6
genkernel all
After it successfully built, I opened up my /boot/grub/grub.conf file in
vim and copied the entry lines for the old kernel I was using
(2.6.18-gentoo-r6 - also created with genkernel) and changed the numbers
to reflect the new kernel on the title, kernel, and initrd lines.
However when I attempt to boot up with the new kernel, it goes through
its usual device checks, and then right when it should say Booting
initramfs-{}, it says /dev/sda6 is not a suitable root
device. (or something like that) and offers me either a chance to enter
the root device, or a shell. I asked for the shell. I did ls and saw a
directory structure seemingly similar to my / on my root partition, but
when I did ls /dev I didn't see any sda devices (or an other s* devices
for that matter). What's gone wrong, and what do I do to fix it? Below
is my /boot/grub/grub.conf:
I ran into a similar problem when upgrading. It looked to me like the
SATA device configuration variables had been changed or renamed. This
caused me to lose all my SATA modules when I rebuilt. After I went in
and explicitly added the new SATA drivers into the config the machine
could boot again.
Hope that helps.
- Ben
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] GTK fonts uglified after update
On Wednesday 29 November 2006 12:13 am, Shaw Vrana wrote: I just performed an emerge -Du world and found that the fonts in the few gtk apps that I use (gaim and wireshark) have now become quite ugly. I followed the wiki at http://gentoo-wiki.com/HOWTO_Xorg_and_Fonts to beautify a while back and the changes I made there have remained intact through the update. Are you running KDE with the gtk-qt theme engine? If so, I had a similar problem with fonts no longer being anti-aliased in gaim. I found the solution on this page: http://www.kde-look.org/content/show.php?content=9714 Basically you need to change your General font setting in the control center. Once you make a change (any change) you can change it back to how you had it originally. Once you restart your gtk applications the fonts should be aliased again. There is no explanation for why this works, but it resolved the issue for me. Hope that helps. Thanks, Shaw - Ben -- gentoo-user@gentoo.org mailing list
