Gentoo 2006.1 livecd with JMicron-Support (JMB363/361/36x)

[kernelOfTruth]

Not sure if its the vga mode or something on the disk tho, as from looking in vmware the screen goes blank when the resoultion changes on normal boot. I might give the vga param a go on norm boot mode

equilibrium, in the meantime I could reproduce your error: it seems to be related to a wrong configuration concerning fbsplash / bootsplash, vesafb ...

it should be fixed with the amd64-r3 release ...

[VampyreUK]

Hi Kernel,

Maybe this isn't your problem but I've hit one ... I got as far as downloading a stage 3 tarball (I believe that's what you guys call them) and then it says look in /mnt/cdrom/snapshots and there isn't one on the CD. So now I'm not sure what to do next ... any ideas and can you tell I'm a n00b?

Kyu

[kernelOfTruth]

So now I'm not sure what to do next ... any ideas and can you tell I'm a n00b?

nope you aren't

if you've dealth with other distros like slackware, debian ...
gentoo compared to them is somewhat more advanced at the beginning stage (using it now for over 2 years)

gentoo mirrors

use one of them:

United Kingdom
Blueyonder ISP (UK/http)
Blueyonder ISP (UK/ftp)
The UK Mirror Service (UK/http)
The UK Mirror Service (UK/ftp)

here you go:

ftp://mirrors.blueyonder.co.uk/mirrors/ ... ent/stages

just download the stage3 tarball and follow the gentoo handbook (in the beginning I've also had a lot of minor problems but you'll be able to solve them in no time, the learn-curve is pretty steep)

don't forget to enable swap-file, especially with reiser4 if you haven't got much ram ...

[VampyreUK]

here you go:

ftp://mirrors.blueyonder.co.uk/mirrors/ ... ent/stages

just download the stage3 tarball and follow the gentoo handbook (in the beginning I've also had a lot of minor problems but you'll be able to solve them in no time, the learn-curve is pretty steep)

don't forget to enable swap-file, especially with reiser4 if you haven't got much ram ...

Hi Kernel,

Thanks for that ... maybe I didn't explain myself well but it's the snapshots I'm after (I downloaded a stage 3 tarball)

Are they a part of the tarball once it's extracted?

Kyu

[VampyreUK]

Thanks for that ... maybe I didn't explain myself well but it's the snapshots I'm after (I downloaded a stage 3 tarball)

Are they a part of the tarball once it's extracted?

Hi,

Any idea on this because I'm kinda stuck?

Kyu

[kernelOfTruth]

hm ...

use this version of gentoo handbook

just follow it step by step:

5.b. Default: Using a Stage from the Internet

=> that's stage3, go for that (you should already have done that)

5.c. Alternative: Using a Stage from the Installation CD

=> is optional and since my livecd is based on the minimal livecd / it should stay "small" (as it's name) it has no stage-tarball

5.d. Installing Portage

portage is gentoo's "package"-management-system
=> you once have to install it manually, then later you can update it via

Code: Select all

emerge --sync 

or

Code: Select all

emerge --sync --quiet

so that you get the latest versions of the apps
it should be similar to:

Code: Select all

yum --update

(is this the command on fedora ?) and

Code: Select all

apt-get update

(debian)

just follow the handbook step by step, if something's not included on the livecd (such as the stage3/stage..-tarball) just download it from the gentoo mirrors

hope that's clear

[VampyreUK]

Installing Gentoo on Intel RAID
System Spec
• Intel D865PERL Motherboard
• 2.8GHz Intel P4 Prescott 1Mb
• 1Gb DDR400 RAM
• 32Mb Matrox G550 Dual Head AGP
• 160Gb SATA RAID 0 (2 x 80GB)
• 1 x DVDRW Dual
• 1 x DVD/CDRW Combo
Assumes
• LAN based connection to net
• DHCP server
Instructions
1. Boot using KOT small-gentoo CD. Type "gentoo-irqpoll dodmraid"
2. Configure RAID (cfdisk /dev/mapper/<RAIDNAME>) with:
• _RAID1: 1024Mb bootable (type 82)
• _RAID2: 2048Mb Swap (type 83)
• _RAID3: As much of disk as required (I chose 102400Mb, Type 82)
3. Write disk configuration and restart.
4. Boot using KOT small-gentoo CD. Type "gentoo-irqpoll dodmraid"
5. Initialise onboard networking for DHCP ("modprobe e100")
6. Format boot & main partitions
• BOOT (as ext2): "mke2fs /dev/mapper/_RAID1"
• MAIN (as reiserfs): "mkreiserfs /dev/mapper/_RAID3"
7. Format & initialise SWAP:
• msswap /dev/mapper/_RAID2
• swapon /dev/mapper/_RAID2
8. Mount partitions & create required folders:
• mount /dev/mapper/_RAID3 /mnt/gentoo
• mkdir /mnt/gentoo/boot
• mount /dev/mapper/_RAID1 /mnt/gentoo/boot
9. cd /mnt/gentoo
10. Download stage3 tarball and latest snapshot using links2
11. Extract stage3 tarball ("tar xvjpf stage3-*.tar.bz2")
12. Extract snapshot ("tar xvjf /mnt/gentoo/portage-latest.tar.bz2 -C /mnt/gentoo/usr"
13. Edit the make.conf file as appropriate (look around but no need to edit), "nano /mnt/gentoo/etc/make.conf"
14. Add your local mirror to make.conf, "mirrorselect -i -o >> /mnt/gentoo/etc/make.conf" (check make conf as in 13 afterwards)
15. Copy the DNS settings over, "cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf"
16. Mount the /proc and /dev file systems:
• mount -t proc none /mnt/gentoo/proc
• mount -o bind /dev /mnt/gentoo/dev
17. Enter the new environment:
• chroot /mnt/gentoo /bin/bash
• env-update (you'll get a message, "Regenerating /etc/ld.so.cache...")
• source /etc/profile
• export PS1="(chroot) $PS1"
18. Configure Portage:
• emerge --sync
19. Add 'USE="qt3 qt4 kde dvd alsa cdr"' to make.conf
20. Copy relevant timezone info over ("cp /usr/share/zoneinfo/GMT /etc/localtime")
21. Install the kernel sources ("USE="-doc symlink" emerge gentoo-sources")
22. Emerge genkernel ("emerge genkernel")
23. Copy the installation CD kernel config ("zcat /proc/config.gz > /usr/share/genkernel/x86/kernel-config-2.6"
24. Compile the kernel ("genkernel all")
25. Make a note of the kernel & initrd ("ls /boot/kernel* /boot/initramfs*)
• initramfs-genkernel-x86-2.6.17-gentoo-r8
• kernel-genkernel-x86-2.6.17-gentoo-r8
26. Add additional autodetection to the system:
• emerge coldplug
• rc-update add coldplug boot
27. Find any modules you need to add to your new kernel and add them to the modules.autoload file:
28. find /lib/modules/2.6.17-r5/ -type f -iname '*.o' -or -iname '*.ko' (found "e100.ko")
29. nano -w /etc/modules.autoload.d/kernel-2.6 (add line "e100")
30. Edit your fstab file appropriately ("nano -w /etc/fstab") and add the following:

/dev/mapper/isw_cbhfacbicf_RAID1 /boot ext2 defaults,noatime 1 2
/dev/mapper/isw_cbhfacbicf_RAID2 none swap sw 0 0
/dev/mapper/isw_cbhfacbicf_RAID3 / reiserfs noatime 0 1

none /proc proc defaults 0 0
none /dev/shm tmpfs nodev,nosuid,noexec 0 0

/dev/cdrom /mnt/cdrom auto noauto,user 0 0

31. Set the HOSTNAME variable ("nano -w /etc/conf.d/hostname")
• 'HOSTNAME="ar-einstein-lx"
32. Configure DHCP ("nano -w /etc/conf.d/net")
• config_eth0=( "dhcp" )
• dhcp_eth0="nodns nontp nonis"
33. Automatically start networking on boot ("rc-update add net.eth0 default")
34. Set the root password ("passwd")
35. Change keyboard settings to UK ("nano -w /etc/conf.d/keymaps")
• KEYMAP="uk"
36. Change clock ("# nano -w /etc/conf.d/clock")
• CLOCK="local"
37. Install a system logger
• emerge syslog-ng
• rc-update add syslog-ng default
38. Install a cron daemon
• emerge vixie-cron
• rc-update add vixie-cron default
39. Install file indexing using slocate ("emerge slocate")
40. Install file system tools ("emerge reiserfsprogs")
41. Install the DHCP client ("emerge dhcpcd")

OK ... all's fine up to this point then I try to use GRUB or lilo!

Emerging them is fine (as is editing the files ... see below) but they cannot, no matter what I do, seem to find the boot sector of my RAID array.

default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz

title=Gentoo Linux 2.6.17-r8
root (hd0,0)
kernel /boot/ kernel-genkernel-x86-2.6.17-gentoo-r8 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev
initrd /boot/ initramfs-genkernel-x86-2.6.17-gentoo-r8

image=/boot/kernel-genkernel-x86-2.6.17-gentoo-r8
label=gentoo
read-only
root=/dev/ram0
append="init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev"
initrd=/boot/initramfs-genkernel-x86-2.6.17-gentoo-r8
append="vga=0x318 video=vesafb:mtrr:3,ywrap"

Help?

Kyu

[kernelOfTruth]

Hi Kyu,

google loves me

and told me the following (I have near no experience with software-raid):

Installing GRUB Onto Drives that have /boot Raid Partitions

Type grub from prompt and will put you in grub's shell:
#grub
grub>

grub>find /grub/stage1
This will give you where all the grub setup files are located. On my raid1
mirror system listed:
(hd0,0)
(hd1,0)

Redhat specifically mounts your /boot partition as the root partition for
grub and is redhat specific. What this is listing are the locations of root
for grub which in fact is grub syntax for where the /boot partition is
located.
Sda=hd0 sdb=hd1 for scsi and hda=hd0 and hdb=hd1 for ide and the second
number specifies the partition number and 0 is the starting number so this
is specifying that it found grub setup files on sda1 and sdb1 scsi or hda1
and hdb1 ide.

Now you want to make sure that grub gets installed into the master boot
record of your additional raid drives so that if id0 is gone then the next
drive has a mbr loaded with grub ready to go. Systems will automatically go
in drive order for both ide and scsi and use the first mbr and active
partitions it finds so you can have multiple drives that have mbr's as well
as active partitions and it won't affect your system booting at all.

So using what was shown with the find above and already knowing that hd0
already has grub in mbr, we then run:

Grub>device (hd0) /dev/sdb (/dev/hdb for ide)
Grub>root (hd0,0) and then:
Grub>setup (hd0)

Grub will then spit out all the commands it runs in the background of setup
and will end with a successful embed command and then install command and
end with .. succeeded on both of these commands and then Done returning to
the grub> prompt.

Notice that we made the second drive device 0. Why is that you ask?
Because device 0 is going to be the one with mbr on the drive so passing
these commands to grub temporarily puts the 2nd mirror drive as 0 and will
put a bootable mbr on the drive and when you quit grub you still have the
original mbr on sda and will still boot to it till it is missing from the
system.

You have then just succeeded in installing grub to the mbr of your other
mirrored drive and marked the boot partition on it active as well. This
will insure that if id0 fails that you can still boot to the os with id0
pulled and not have to have an emergency boot floppy.

taken from Software Raid and Grub HOWTO (dell)

hope this helps ...

[VampyreUK]

grub>find /grub/stage1

I type that and get Error 15: File not found

Oh well ... Google here I come!

EDIT: There's some stuff here Gentoo Grub Error Collection ... now I just need to figure out what the hell it means!!!!!

Kyu

[VampyreUK]

grub>find /grub/stage1

I type that and get Error 15: File not found

Oh well ... Google here I come!

EDIT: There's some stuff here Gentoo Grub Error Collection ... now I just need to figure out what the hell it means!!!!!

Kyu

I'm not able to solve this ... as it was some 36 hours after I started the installation I gave up last night. I still have my quicknotes so I can probably get back to the stage I was at in somewhat fewer hours should anyone come up with any solutions.

Kyu

[kernelOfTruth]

sorry, Kyu, that I couldn't help you on that stage,

but hey! don't give up that fast (I didn't either) I found something:

# grub benötigt folgende Dateien um das Device korrekt anzusprechen
cp /lib/grub/<your-cpu-arch>-pc/stage1 /boot/grub/
cp /lib/grub/<your-cpu-arch>-pc/stage2 /boot/grub/

grub
# wir befinden uns nun in der grub-shell

device (hd0) /dev/mapper/nvidia...
# damit teilen wir grub das aktuelle mapping mit

geometry (hd0) <zylinder> 255 63
# zusätzlich muss grub die aktuelle Geometrie des RAID-Devices mitgeilt werden.
# Die aktuelle Anzahl der Zylinder findet man mit folgendem Kommando heraus:
# (fdisk -l /dev/mapper/nvidia_...)

root (hd0,2)
# Auswählen der root-Partition. Es müsste nun so etwas wie "...reiserfs..." o.Ä. zurückgemeldet werden.

setup (hd0)
# Finales installieren von grub

quit
# grub setup verlassen

update-grub
# Anlegen der /boot/grub/menu.lst und hinzufügen des aktuellen Kernels

and here the translation:

# grub needs the following files for correctly communicating with the device
cp /lib/grub/<your-cpu-arch>-pc/stage1 /boot/grub/
cp /lib/grub/<your-cpu-arch>-pc/stage2 /boot/grub/

grub
# we're now in the grub shell

device (hd0) /dev/mapper/nvidia...
# with this we tell grub the actual mapping

geometry (hd0) <zylinder> 255 63
# in addition to that you have to tell grub the actual geometry of the RAID-Devices
# The momentary number of cylinders can be displayed by issueing the following command:
# (fdisk -l /dev/mapper/nvidia_...)

root (hd0,2)
# selecting the root partition.

setup (hd0)
# final installation of grub

quit
# exit grub setup

#update-grub
# ubuntu/debian-specific

hope that helps

some other resources (if you haven't already tried them out):

gentoo install on software raid
gentoo install on bios-raid
gentoo install with nvraid

[VampyreUK]

sorry, Kyu, that I couldn't help you on that stage,

... you've been really helpful and I appreciate it

but hey! don't give up that fast (I didn't either) I found something:

I haven't given up, I just couldn't leave the system on all week trying to find a solution ... anyway, it gives me a chance to follow my notes through and see if I got it right.

hope that helps

I work form home on Wednesdays so might try then, failing that I'll give it a go at the weekend

Thanks for the support and I'll let you know how I get on

Kyu

[Strukt]

Still have some problems.

I managed to get gentoo installed, but when trying to boot it complains that it cant find the harddrive. Or boot from it. When i installed grub it found the drive and everything seems fine. And it also boots fine from grub in the start.

Domehow the harddrive configuration have changed from when i installed, its now on (hd1), instead of (hd0)

It asks me to specify boot device after the boot process has gone for a while. Until i added no-generic-ide it changes to hdc / instead of sdb. So i typed /dev/hdc3 and it started with the message "Mounting root..." and it just hangs there.. ?

I have compiled in the neccesary drivers in the kernel, not as modules but directly. Any ideas?

Im at work now so i dont have access to the box, but i can give much more info when i get home.

[kernelOfTruth]

You are permitted to use the Gentoo name in computer-related content, provided that:

1. You acknowledge that the name "Gentoo" is a trademark of Gentoo Foundation, Inc., and
2. you do not entitle any software project or computer-related product "Gentoo" or have "Gentoo" appear within its name, and
3. the fully-qualified domain name for your software project or computer-related products does not contain "Gentoo", and
4. you clearly state that the content, project, site, product or any other type of item with which the "Gentoo" name is associated is not part of the Gentoo project and is not directed or managed by Gentoo Foundation, Inc.

I just realized that I can't call the liveCD "small gentoo", can I ?

name-logo

[daddldido]

Hi folks

first of all: Thank You for this work You did Kernel!

I am using an Asus P5B Deluxe and try to install gentoo. I did every step of the gentoo handbook, but there is a small Problem. When I try to start Gentoo with Grub as bootloader i get the error that the hd0,0 is not available. Also i didn´t get the choice to add the jmicron modul to my kernel. The other modules are available.... I tried to find something in google and here in the forum, but this is the only thread regarding to issues with the jmicron chipset. Maybe You have an idea for my problem...



Thanks a lot

daddldido

[kernelOfTruth]

Hi daddldido,

welcome to gentoo

Also i didn´t get the choice to add the jmicron modul to my kernel.

you mean for gentoo-sources ?

you could either try out vipernicus' emission-sources (2.6.18-emission1)


or patching gentoo-sources

for this you need the non-libata driver for jmicron devices (in vipernicus' broken-out directory of 2.6.18-emission1)

patch -p1 < 09-non-libata-driver-for-jmicron-devices.patch

(09-non-libata-driver-for-jmicron-devices.patch must reside in the kernel-directory)


another option would be:

trying out mm-sources:
2.6.18-mm1 - 2.6.18-mm3 (2.6.18-mm1 seems to me, 2.6.18-mm2 to -mm3 have problems with Marvell-network-cards)

you have to look for the jmicron-driver in:

1.) non-libata (this applies to patched gentoo-sources & emission-sources)
Device Drivers ---> <*> ATA/ATAPI/MFM/RLL support ---> [*] PCI IDE chipset support ---> [*] Generic PCI bus-master DMA support --->
<*> JMicron JMB36x support (NEW)

2.) libata (works better & works with ahci & native-mode) (this applies to emission-sources & newer mm-sources [>=2.6.18-mm1])
Serial ATA (prod) and Parallel ATA (experimental) drivers ---> <*> ATA device support --->
<*> AHCI SATA support
<*> Intel PIIX/ICH SATA support
<*> Generic ATA support
<*> JMicron PATA support

please compile the drivers into the kernel! otherwise it won't work / boot properly

depending on your hardware you might need to compile in even more drivers ...

the most relevant network-drivers for those boards are:

Device Drivers ---> Network device support ---> Ethernet (1000 Mbit) --->
<*> Realtek 8169 gigabit ethernet support
<*> SysKonnect Yukon2 support (EXPERIMENTAL)
<*> New SysKonnect GigaEthernet support

you have to look under < HELP > which driver applies to you

hope that helps ...
this driver is known

[daddldido]

Ok thanks!

I will try it later when i am back home....

[VampyreUK]

... and failed again I'm afraid. Much the same kind of errors, grub wouldn't install, Error 15 again. Tried the device/geometry thing but no luck (also Error 15).

On the plus side the notes I took and turned into instructions made it easier so I failed quicker

Kyu

[kernelOfTruth]

hm, I really hope NeddySeagoon reads this:

Neddy, you give pretty competent advices & surely know a lot, could you let us have part in your knowledge in this case?

I don't know of any other advice for this problem ...

Thanks in advance

[daddldido]

Hi daddldido,

2.) libata (works better & works with ahci & native-mode) (this applies to emission-sources & newer mm-sources [>=2.6.18-mm1])
Serial ATA (prod) and Parallel ATA (experimental) drivers ---> <*> ATA device support --->
<*> AHCI SATA support
<*> Intel PIIX/ICH SATA support
<*> Generic ATA support
<*> JMicron PATA support

please compile the drivers into the kernel! otherwise it won't work / boot properly

depending on your hardware you might need to compile in even more drivers ...

the most relevant network-drivers for those boards are:

Device Drivers ---> Network device support ---> Ethernet (1000 Mbit) --->
<*> Realtek 8169 gigabit ethernet support
<*> SysKonnect Yukon2 support (EXPERIMENTAL)
<*> New SysKonnect GigaEthernet support

you have to look under < HELP > which driver applies to you

hope that helps ...
this driver is known

That helps I tried the first option but it was not working for me. The second option was really easy but i forgot to compile the usb HID drivers into the kernel.... so i have to do some work tonight again. Thanks for Your help!!

[blitz667]

why there's no pppoatm.so on the livecd? Oh, and the ppp_generic module is not working either i think.

Is there a valid reason for this?

Thanks for any replies.

[kernelOfTruth]

@blitz667:
Welcome to Gentoo

Is there a valid reason for this?

yes there is

since I had to remove some folders from the livecd on its building process the possibility exists that some libraries are missing /
that means some apps may not work which should work

it can also be that some apps are broken due to bugs ... (bugs.gentoo.org)

could you please tell me which application needs this lib?
then I'll have a look at it ...

[Jjeje007]

Hi,

kernelOfTruth can you give me your kernel config for the sata from the Ez-backup (enable Sata Silicon Image ??)
Even if i try emission-sources and no-sources kernel with an reiser4 partition for "/" ... no way to boot the kernel :
Complaining about VFS: unable to find /dev/sda3 (my root partition) or somethink like that

I've just reformat my hard drive and used reiser 3.6 ... I will see (then i will i have again an headache with the buggy sky2 :s)

Just to remenber you : motherboard : ASUS P5W DH Deluxe, two sata hard drive in raid0 throught Ez-backup connectors

[kernelOfTruth]

@VampyreUK:

Kyu, try to pm NeddySeagoon, perhaps he can help you with your problem ...

@Jjeje007:

didn't I already have that covered in this post ?

Code: Select all

Serial ATA (prod) and Parallel ATA (experimental) drivers ---> <*> ATA device support --->
<*> AHCI SATA support
<*> Intel PIIX/ICH SATA support
<*> Generic ATA support
<*> JMicron PATA support 

and here the excerpt of my config:

<*> ATA device support │ │
│ │ <*> AHCI SATA support │ │
│ │ < > ServerWorks Frodo / Apple K2 SATA support │ │
│ │ <*> Intel PIIX/ICH SATA support │ │
│ │ < > Marvell SATA support (HIGHLY EXPERIMENTAL) │ │
│ │ < > NVIDIA SATA support │ │
│ │ < > Pacific Digital ADMA support │ │
│ │ < > Pacific Digital SATA QStor support │ │
│ │ < > Promise SATA TX2/TX4 support │ │
│ │ < > Promise SATA SX4 support │ │
│ │ <*> Silicon Image SATA support │ │
│ │ <*> Silicon Image 3124/3132 SATA support │ │
│ │ < > SiS 964/180 SATA support │ │
│ │ < > ULi Electronics SATA support │ │
│ │ < > VIA SATA support │ │
│ │ < > VITESSE VSC-7174 / INTEL 31244 SATA support │ │
│ │ < > ALi PATA support (Experimental) │ │
│ │ < > AMD/NVidia PATA support (Experimental) │ │
│ │ < > ARTOP 6210/6260 PATA support (Experimental) │ │
│ │ < > ATI PATA support (Experimental) │ │
│ │ < > CMD64x PATA support (Very Experimental) │ │
│ │ < > CS5510/5520 PATA support │ │
│ │ < > CS5530 PATA support (Experimental) │ │
│ │ < > CS5535 PATA support (Experimental) │ │
│ │ < > Cypress CY82C693 PATA support (Very Experimental) │ │
│ │ < > EFAR SLC90E66 support │ │
│ │ <*> Generic ATA support │ │
│ │ < > HPT 366/368 PATA support (Very Experimental) │ │
│ │ < > HPT 370/370A/371/372/374/302 PATA support (Very Experimental) │ │
│ │ < > HPT 372N/302N PATA support (Very Experimental) │ │
│ │ < > HPT 343/363 PATA support (Experimental) │ │
│ │ < > IT821x PATA support (Experimental) │ │
│ │ <*> JMicron PATA support

I've just reformat my hard drive and used reiser 3.6 ... I will see (then i will i have again an headache with the buggy sky2 :s)

please don't reformat (and loose all of your gentoo-system), instead first boot from a livecd and create a stage4 (I think there's a howto in the gentoo-wiki.com)

for the sky2-part use 2.6.18-mm1, emission-sources or >=2.6.19-rc4-mm1 (in >= 2.6.19-rc4-mm1 frequency-switching seems to be broken)

[Jjeje007]

Hi,

Thx for your help

I format already 3 times
And then when playing with the ide setting in the bios i find out why i was getting an kernel panic at boot
Right now i just finish to compil the kernel from emission-sources ... hope it will be ok for the sky2 module