[gentoo-user] [gentoo-amd64] Help! New install and New User to linux - Gentoo!
sorry if you are geting this twice as I have also posted to the amd64 list Hello All, I figure I will also give this information to this list as I was asked some questions from the amd list. Frist part is this is not a live cd, it is booting off of the hard drive. Next thing is all of the stuff here loaded right when usings a livecd, I got the list by doing a lsmod and then writeing them into the file that coldplug uses to automatic load them as this is the stuff that the live cd loaded / detected. The hard drives that are being used is SATA (in the bios I have it as IDE as I don't care to use raid or arrays, the motherboard is a Asus K8V Delux SE (its the one with talking boot up and also the one that has a wireless card slot init) If there is any more questions I could answer to help with figureing out these issue please ask! Sincerely, Christopher On 4/20/06, Mark Haney [EMAIL PROTECTED] wrote: Christopher E wrote: hello All, I have been for the last couple of days (4) days trying to get this system up and running and I am having a number of probs and below is a list of them I get all these errors when booting up: !! The root block device is unspecified or not detected at the prompte I can type in /dev/sda6 and it will boot then the following comes after this mkdir: Cannot creat directory '/newroot/tmp/.initrd': Looks to me like the install disk can't find a hard drive. What kind of hard drive/system is this? The other failures I think are pretty common on most boot/install/live media as it tries to load many different modules to get a basic system up for you to continue the install. Failed to load pcspkr [!!] Failed to load skge Failed to load ati_remote Failed to load dm_mirror Failed to load dm_mod Failed to load pdc_adma Failed to load sata_mv Failed to load ahci Failed to load sata_qstor Failed to load sata_uli Failed to load sata_sil24 Failed to load lidata Failed to load sl811_hcd Failed to load usbcore Sincerely, christopher PS: this help is NOT for personal or commaul gain its for a non-profit org project -- Interdum feror cupidine partium magnarum Europae vincendarum Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 -- gentoo-amd64@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] [gentoo-amd64] Help! New install and New User to linux - Gentoo!
Christopher E [EMAIL PROTECTED] wrote: the motherboard is a Asus K8V Delux SE I had a similar problem with Asus A8V, sata disk not recognised. Later I found out that southbridge (VT8251) was not supported... On your mobo there is VIA VT8237 southbridge, check if this is supported by kernel (kernel-sources). If not, you have to patch kernel first to get your sata-drive recognised... Anyway, for installation I had to use p-ata disk (this was detected by livecd-kernel), install linux on it, patch kernel, then sata-disk was recognised, and finally install on sata disk... BTW, try to switch your sata to ahci. Sometimes helps. But in my case it was definitely not supported southbridge... Jarry -- Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] [gentoo-amd64] Help! New install and New User to linux - Gentoo!
Hello Jarry, I am able to get into the system with the current setup that is the strange thing, I am NOT using the liveCD any more, I am booting using GRUB, it loads the kernel and then it prompts me for a root block device and then I enter /dev/sda6 --- this is my sata drive and when I do this it mounts the root (sda6 is my root partition) my boot is /dev/sda1 Does this change any thing seeing I am able to do the above? if so what should I do? Sincerely, christopher On 4/20/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Christopher E [EMAIL PROTECTED] wrote: the motherboard is a Asus K8V Delux SE I had a similar problem with Asus A8V, sata disk not recognised. Later I found out that southbridge (VT8251) was not supported... On your mobo there is VIA VT8237 southbridge, check if this is supported by kernel (kernel-sources). If not, you have to patch kernel first to get your sata-drive recognised... Anyway, for installation I had to use p-ata disk (this was detected by livecd-kernel), install linux on it, patch kernel, then sata-disk was recognised, and finally install on sata disk... BTW, try to switch your sata to ahci. Sometimes helps. But in my case it was definitely not supported southbridge... Jarry -- Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] [gentoo-amd64] Help! New install and New User to linux - Gentoo!
On 4/20/06, Christopher E [EMAIL PROTECTED] wrote: I am able to get into the system with the current setup that is the strange thing, I am NOT using the liveCD any more, I am booting using GRUB, it loads the kernel and then it prompts me for a root block device and then I enter /dev/sda6 --- this is my sata drive and when I do this it mounts the root (sda6 is my root partition) my boot is /dev/sda1 What does /boot/grub/grub.conf contain? -Richard PS. Please don't top post on this list. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] [gentoo-amd64] Help! New install and New User to linux - Gentoo!
Christopher E [EMAIL PROTECTED] wrote: I am able to get into the system with the current setup that is the strange thing, I am NOT using the liveCD any more, I am booting using GRUB, it loads the kernel and then it prompts me for a root block Well, I'm not using GRUB, but I think that the way GRUB reads disks has very little (if anything) common with linux. Not only it gives different names to disk-partitions, grub is like mini-OS, which uses its own routines. It can be that GRUB sees disks/partitions differently, than linux... lilo has been designed as LInux LOader. If lilo can see some disks/partitions, linux kernel can find them too (and vice-versa). But this is sometimes not true for GRUB... Jarry -- Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] [gentoo-amd64] Help! New install and New User to linux - Gentoo!
On 4/20/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well, I'm not using GRUB, but I think that the way GRUB reads disks has very little (if anything) common with linux. Not only it gives different names to disk-partitions, grub is like mini-OS, which uses its own routines. It can be that GRUB sees disks/partitions differently, than linux... lilo has been designed as LInux LOader. If lilo can see some disks/partitions, linux kernel can find them too (and vice-versa). But this is sometimes not true for GRUB... No. both grub and lilo work through the system BIOS. Neither can 'see' things not provided through the system BIOS. But grub and lilo do work very differently in their 'normal' configurations. Lilo records absolute disk blocks where the kernel is located, and loads the kernel directly from those blocks. This is why you have to re-run lilo every time you update your kernel. Grub however has some knowledge of filesystems, so can actually read the filesystem that contains the kernel to determine what blocks to load. So it is possible (not so much today, but in years past) to use a filesystem that linux understands but grub does not. -Richard Jarry -- Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] [gentoo-amd64] Help! New install and New User to linux - Gentoo!
Richard Fish wrote: No. both grub and lilo work through the system BIOS. Neither can 'see' things not provided through the system BIOS. Are you absolutely sure about lilo? lilo used bios for disk sector read, but I think is not using anymore (quite a long time). Thanks to that you can have /boot (more exactly, kernel) wherever you want. int13h is called with following registers: AH: 02h (read sectors from drive) CH + 2low bits from CL: cylinder number (0-1023) rest 6bits from CL: sector number (1-63) DH: head (1-255) That's the famous 8-GB limit (and there are some more, equally famous), where you had to install kernel with old lilo to be able to boot it. But at least a couple of years there is no such a limit with lilo. I think I have read somewhere that lilo is not using bios for disk-access anymore. I'll try to dig it out... Jarry -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] [gentoo-amd64] Help! New install and New User to linux - Gentoo!
On 4/20/06, Jarry [EMAIL PROTECTED] wrote: Richard Fish wrote: No. both grub and lilo work through the system BIOS. Neither can 'see' things not provided through the system BIOS. Are you absolutely sure about lilo? Checking the source and the README in the source of 22.7.1 makes it pretty clear that lilo is still using the BIOS for booting. lilo used bios for disk sector read, but I think is not using anymore (quite a long time). Thanks to that you can have /boot (more exactly, kernel) wherever you want. int13h is called with following registers: AH: 02h (read sectors from drive) CH + 2low bits from CL: cylinder number (0-1023) rest 6bits from CL: sector number (1-63) DH: head (1-255) That's the famous 8-GB limit You are correct about old systems having a 1024-cylinder limit, but the solution for this was that the system bios was extended to allow access to sectors = 1024. The typical term for this is the 13h extensions. In lilo documentation, this is the EDD packets. famous), where you had to install kernel with old lilo to be able to boot it. But at least a couple of years there is no such a limit with lilo. I think I have read somewhere that lilo is not using bios for disk-access anymore. I'll try to dig it out... This might be true on itanium or other non-x86 platforms (I know nothing about these). But on x86, the BIOS controls booting, and the OS cannot access the disks any other way than through the BIOS until it's own device drivers are loaded. So unless lilo has been adding device drivers for the plethora of SCSI, FC, IDE, SATA, IEEE1284, and USB disk controllers out there, and making them all fit in the impossibly small space of the MBR (~460 bytes?), it is using the BIOS for at least some actions. -Richard -- gentoo-user@gentoo.org mailing list
