Hi,
With kernel 2.6.19 I was able to boot using the pata_via driver
I tried to compile 2.6.20-rc6 and now I get a "unknown device: sda3"
error when I try to boot.
I compiled 2.6.20-rc6 by copying over the .config from the 2.6.19 tree
and running a make oldconfig && make
Am I doing something wrong?
Patrick
On Sun, Jan 28, 2007 at 12:47:18PM +0100, Patrick Ale wrote:
> Hi,
Hi Patrick,
> With kernel 2.6.19 I was able to boot using the pata_via driver
> I tried to compile 2.6.20-rc6 and now I get a "unknown device: sda3"
> error when I try to boot.
>
> I compiled 2.6.20-rc6 by copying over the .config from the 2.6.19 tree
> and running a make oldconfig && make
>
> Am I doing something wrong?
Both kernels are self-compiled or is 2.6.19 a distribution kernel?
It could be that 2.6.20-rc6 has a bug and therefore no longer is able to
use your controller.
It's also possible that the enumeration changed (e.g. sda is now an
external hard disk).
During boot, there should be some messages prefixed with ata: and sda:
describing what your kernel found and how it enumerated them.
What do they print with 2.6.20-rc6?
> Patrick
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
On 1/29/07, Patrick Ale <[email protected]> wrote:
> On 1/29/07, Adrian Bunk <[email protected]> wrote:
> > On Sun, Jan 28, 2007 at 12:47:18PM +0100, Patrick Ale wrote:
>
> >
> > Hi Patrick,
>
Morning!
The 2.6.19 was self-compiled, using the gentoo-sources-rc4 AND using
the vanilla 2.6.19 from kernel.org (I was recommended to use vanilla
sources with my ATI drivers), both worked.
2.6.20 is self compiled to. I will give you the kernel output when I
am at home, I will have to connect a serial cable to my laptop and use
the scrollbuffer since on a kernel panic or system crash my keyboard
leds start to blink, which the kernel sees as a device addressing
hardware directly and giving me a kernel message for every blink :D
Oh, and pata_via is the ONLY driver I have compiled built-in,
regarding libsata. As I mentioned in previous mails I have quite some
controllers and disks, but pata_via (my onboard IDE) has only two
drives attaches, on IDE0 (in 2.6.19 ata0) my boot disk
I also tried to boot with scsi_mod.scan=sync, this didnt work either
More info follows, thanks for your time allready :)
Patrick
Okay so, I unplugged the keyboard the moment I selected a kernel to boot.
The last thing i see on my screen, regarding SCSI is:
scsi 0:0:0:0: Direct-Access ATA WDC WD2000JB-00G 08.0 PQ: 0 ANSI: 5
scsi 1:0:0:0 CD-ROM AOPEN DUW1608/ARR A060 PW: 0 ANSI: 5
then later on:
VFS: Cannot open root device "sda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
On 1/29/07, Patrick Ale <[email protected]> wrote:
> Okay so, I unplugged the keyboard the moment I selected a kernel to boot.
> The last thing i see on my screen, regarding SCSI is:
>
> scsi 0:0:0:0: Direct-Access ATA WDC WD2000JB-00G 08.0 PQ: 0 ANSI: 5
> scsi 1:0:0:0 CD-ROM AOPEN DUW1608/ARR A060 PW: 0 ANSI: 5
Funny, when I look at my dmesg log when I boot the 2.6.19 kernel (which works)
then I seem to miss something in the kernel output when I boot the
2.6.20 kernel.
When I boot 2.6.19 I see:
scsi 0:0:0:0: Direct-Access ATA WDC WD2000JB-00G 08.0 PQ: 0 ANSI: 5
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
Does 2.6.20 see my IDE bus but it doesnt probe for drives?
Patrick
On 1/29/07, Patrick Ale <[email protected]> wrote:
A lot of crap. And i am a fruitcake, nutter, headcase.
*sigh* sorry for wasting your time, I found my problem.
Since I thought libata worked like my old ata drivers and 2.6.19 was
booting well, I reconfigured my kernel source and changed
CONFIG_BLK_DEV=y to CONFIG_BLK_DEV=m, since I genuinely thought I
wouldnt need additional disk drivers since I never needed them for
IDE. I compiled the kernel and all but never copied over the bzImage
over to /boot/
Now, I grabbed the config from 2.6.19 , copied it to 2.6.20, ran a
make oldconfig && make && make_modules and copied the bzImage to
/boot/. Of course, the 2.6.20 image I try to boot DOES contain the
CONFIG_BLK_DEV=m , so it wont find any disks, since the module is not
active (I dont use ramdisks).
I reconfigured 2.6.20 with CONFIG_BLK_DEV=y , and its working now.
idiot I am, what else can I say.
Again, sorry for wasting your time.