Thanks for the explanation there.
I could be wrong, but it doesn't really say which is libata and which isn't, right?_________________Mac Pro single quad 2.8GHz, 6GB RAM, 8800GT. MacBook. Plus way too many SUN/Cobatl/SGI and a lonely Alpha.

Any drivers under Serial ATA (prod)Parallel ATA (experimental) drivers is the new libata drivers.

It doesn't explicitly say that it is the new libata but it is known. You can read more on some kernel websites, like kerneltrap etc. There are bound to be 2 drivers for the same chipset in IDE and libata since its still migrating, such as the jmicron. You can't enable both the drivers or things will go horribly wrong. Just use either one._________________E6300 Gigabyte GA-965P-DS3 2GB Corsair 320GB Seagate 7200.10 XFX 7600GT Gentoo
Dell M1330 T7500 2GB 160GB 13.3" WXGA Gentoo
Sharp Zaurus SL-C760 Cacko ROM 1.21b / pdaXrom 1.10rc5 512MB CF + 512MB SD
Sun Ultra5 Gentoo

Ah, thanks for clearing that up.
I don't work much with Linux, and when I do it's mostly for my home servers.
And those are SUN machines with SCSI._________________Mac Pro single quad 2.8GHz, 6GB RAM, 8800GT. MacBook. Plus way too many SUN/Cobatl/SGI and a lonely Alpha.

@lenk, don't think 2.6.19-r1 was in portage when I setup my sysytem, hence i used mm-sources. However, I haven't seen any errors in dmesg so far as you show.
You could try to compile in the Generic PCI IDE chipset support, which gives /dev/hd*. Maybe it helps, maybe not.

starting with 2.6.16. 2.6.17 worked too, and 2.6.18 and at the moment I am using 2.6.19

But what sources? mm-sources, no-sources, gentoo-sources?

vanilla kernel org.

I would have added -mm, -gentoo or something else, if I would not use vanilla kernel org Linus-tree kernels._________________Study finds stunning lack of racial, gender, and economic diversity among middle-class white males

Ok.. i actually went and tried out the 2.6.19 kernel from kernel.org.. the jmicron controller and such works perfectly and the Intel ICH7R SATA work fine.. just Intel ICH7R PATA doesnt work at all _________________Intel Core 2 Duo E6600 2.4Ghz
Asus P5W DH Deluxe
Lite-On 16x DVDRW
Western Digital 120GB IDE
Western Digital 120GB SATA
Western Digital 200GB IDE x 2

using this on another distro i cant patch the kernel using that patch ive tried "patch -p0 > 2.6.18-rc4-mm2" and "patch -p1 > 2.6.18-rc4-mm2" both with no output or errors.. i have to ctrl+c the process to stop it from doing nothing _________________Intel Core 2 Duo E6600 2.4Ghz
Asus P5W DH Deluxe
Lite-On 16x DVDRW
Western Digital 120GB IDE
Western Digital 120GB SATA
Western Digital 200GB IDE x 2

thats the thing.. that doesnt work it just sits there for ages... no disk activity no patching being done.. nothing.. it never ends.
___________

I just tried doing that in gentoo (patch -p1 etc) and it doesnt even work in gentoo... so what the heck does the ebuild do that using normal patch doesnt? something is majorly borked._________________Intel Core 2 Duo E6600 2.4Ghz
Asus P5W DH Deluxe
Lite-On 16x DVDRW
Western Digital 120GB IDE
Western Digital 120GB SATA
Western Digital 200GB IDE x 2

i used gentoo to make the 2.6.18-rc4-no2 tar'd the source up.. uploaded to my local server.. got into ubuntu.. downloaded the tar. compiled installed.. but i get odd errors about my first hd drive (hda = my dvdrw drive) "hda: drive not ready for command" and it just goes spaz.. i cant stop it..

well, then I'm going to upload it (the finished patched kernel), hope cheater doesn't has any objections against it

Update:
oops, sorry for giving that misinformation:

Quote:

2.6.18-rc4-no2 "To be..." | ...My attempt at more stability
this is a testing release
If you have a problem please report it, otherwise I can not help you with it

Release
- A very solid release coming up into the mix, Based off of 2.6.18-rc4-mm1 but including
several important and not so important fixes, some being from -mm2. Nothing real experimental
was pushed into this release, just a ton of fixes and the new version of -mm. I'm really
opt about the stability of this release in comparison to 2.6.18-rc4-no1, I went out of my
way to assure it as stable as possible this release. (marked unstable due to -rc release only)

I've noticed the latest gcc you can get via emerge is 4.11, apparently in 4.2 you can use "core2" as an arch flag, where could i get my hands on gcc 4.2?_________________Intel Core 2 Duo E6600 2.4Ghz
Asus P5W DH Deluxe
Lite-On 16x DVDRW
Western Digital 120GB IDE
Western Digital 120GB SATA
Western Digital 200GB IDE x 2

every week new snapshots are being released, for this you have to edit / hack the existing gcc 4.2 alpha-ebuild,
gcc 4.2 currently is in stage3, which means many bugfixes are being made & it's still not ready for the public

it still doesn't compile every app & it's not supported by gentoo-devs / gentoo

so you probably want to try gcc-4.3, but because it's still in stage1 (not feature-complete) you'll likely be running into trouble when using it as system-compiler, and as always, it isn't supported by gentoo & gentoo-devs in any way, you need to file bugs & create patches for the broken apps on your own

browse in the directory for your corresponding kernel (here 2.6.19-rc4), then selected the needed release (in this example there are two:
2.6.19-rc4-mm1 & 2.6.19-rc4-mm2, but you'll change to 2.6.19-rc4-mm2)

ifconfig eth0 right after bootup confirms: the interface doesn't get an ipv4 address. this issue of course might be a configuration problem and not related to the kernel or the hardware.

I don't know if this is related, but the kernel is having trouble detecting the Realtek gigabit ethernet controller on my P5B lately. It worked fine for several months, and suddenly this started happening (with no configuration changes on my part). On these occasions, ifconfig immediately after booting confirms that the interface isn't detected (only lo is shown). I have a PCI ethernet card installed that is detected as eth0, so if I must I can use that, but so far rebooting (sometimes more than once) has temporarily cured the problem. I have no idea what is going on with that.

My kernel version is 2.6.18-mm3, with the R8169 driver compiled into the kernel (CONFIG_R8169=y). I might try compiling it as a module to see what effect unloading and reloading it has.

Last edited by pillsnotbills on Mon Dec 25, 2006 11:47 pm; edited 1 time in total