* Re: 43p-140 install issues
From: Ulrich Teichert @ 2005-01-04 15:23 UTC (permalink / raw)
To: mikemartin; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc, Philippe Guyot
In-Reply-To: <855e88d005010405417d49dcfb@mail.gmail.com>
Hi,
>I gave Leigh's 2.4.22 a try. It gave me the same result with the
>debian root disk:
>
>VFS: Insert root floppy and press ENTER
>
>FAT: bogus logical sector size 1981
>FAT: bogus logical sector size 1981
>read_super_block: can't find a reiserfs filesystem on (dev 02:00,
>block 64, size 1024)
>read_super_block: can't find a reiserfs filesystem on (dev 02:00,
>block 8, size 1024)
>Kernel panic: VFS: Unable to mount root fs on 02:00
Could you try to format them before dd'ing on them, like fdformat /dev/fd0h1440?
I am not sure if that will change anything, though.
>Tonight I'll grab a different root floppy and see what happens.
>
>Leigh's 2.4.22 will also boot the system installed on /dev/sdb1,
>however it also stopped responding after awhile. I think it lasted
>longer than with 2.4.19.
I am begining to believe that there is some sort of hardware problem with your
box or it is an upgraded version which was a -140 in it's previous life, but my
-140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
I will leave it running tonight to see what happens,
HTH,
Uli
--
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24 |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Christian @ 2005-01-04 15:08 UTC (permalink / raw)
To: linuxppc-dev; +Cc: Marc Dietrich
In-Reply-To: <200501041423.34061.marc.dietrich@ap.physik.uni-giessen.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marc Dietrich schrieb:
>
> So you are using netboot and it seems that when having a root-fs via nfs _no_
> disk driver is initialized even if it is compiled in (acording to your
> config). Funny, didn't know that.
>
whoops! so, the 2.6.10-rc3 bootlog shows indeed no scsi-initialization -
i'll boot a proper scsi-enabled config then and upload another bootlog ;-)
- --
BOFH excuse #401:
Sales staff sold a product we don't offer.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB2rF+C/PVm5+NVoYRAjkRAKCiSC6zSmw6Rvhy5RAbUtw4yFKvJgCfTMnA
IIfoTniXDIT/YvsORjexf38=
=vX/q
-----END PGP SIGNATURE-----
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Sebastian Heutling @ 2005-01-04 14:42 UTC (permalink / raw)
To: Marc Dietrich; +Cc: linuxppc-dev
In-Reply-To: <200501041504.57588.marvin24@gmx.de>
On Tue, 2005-01-04 at 15:04 +0100, Marc Dietrich wrote:
> Hallo Sebastian,
>
> Am Dienstag, 4. Januar 2005 12:31 schrieben Sie:
> > Hello Marc,
> >
> > Marc Dietrich wrote:
> > >Hi Christian,
> >
> > Erm ... I'm Sebastian ;-)
>
> ah! - sorry Sebastian, to many confusion in the last time...
Hehe :)
>
> > I am using a 2.6.8 (I was too lazy to patch & compile a 2.6.9 and wanted
> > to test 2.6.10 when it's (the sources) in debian/unstable).
> >
> > >Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can
> > >write it to a floppy disk)?
> >
> > I will do that and tell you later where you can download it.
>
> This may no longer be necessary, but see below.
>
> Acording to your log, your scsi drive also fails later, but boots from ide
> (how did you managed to install the ide disks?).
Yep, it fails later but it doesn't boot from IDE. The SCSI disk is
recognized correctly and the system is on the SCSI drive. The IDE disks
only contain data. It fails later that is right but it still works after
failure.
Making IDE work was easy. A friend soldered the connectors and then I
passed "ide0=ide0=0x1f0,0x3f6,14" as kernel parameter to make channel 0
work. Later on after, discovering what was wrong with 2.6 kernels, I
enabled the correct interrupt in the appropriate table in prep_pci.c.
>
> I posted a message to linux-scsi describing this problem. I guess the sym2
> driver never worked on the PReP machines. I tried it also with 2.4 kernels.
>
> So to summerize it: No one has a working Powerstack with 2.6 kernel and
> booting from SCSI. I hope there will be some input from the scsi list.
As said above, it does really work although I have to admit there is a
problem with PCI or IRQ handling in general. You can also see in my log
that one of the ethernet devices has problems every now and then. All in
all it is sort of functional.
You can also try to remove every additional PCI device except the gfx
card and see what happens. I had to remove an additional SCSI host
controller in order to avoid problems with other PCI devices (mostly it
was one of the ethernet devices which lost an interrupt).
But I share your thoughts that there is something wrong with the sym2
driver.
>
> > >How does your boot.log looks like?
> >
> > Attached it.
> > Note that I use a Matrox MilleniumII gfx card and XFree4 runs fine
> > (without any crash) since I got a 2.6 kernel running (although I am not
> > using XFree because I use the Powerstack as a router/server which has no
> > Monitor).
>
> Yeah - I search so many times for a Millenium card on eBay. Now I got one for
> EUR 1.00 but it is in Germany, while I'm in France now for holidays :-(
> I also have a P9100 here, but it is not supported (yet?) under linux...
:(
Sebastian
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Marc Dietrich @ 2005-01-04 14:04 UTC (permalink / raw)
To: Sebastian Heutling; +Cc: linuxppc-dev
In-Reply-To: <41DA7E7A.3070901@gmx.de>
Hallo Sebastian,
Am Dienstag, 4. Januar 2005 12:31 schrieben Sie:
> Hello Marc,
>
> Marc Dietrich wrote:
> >Hi Christian,
>
> Erm ... I'm Sebastian ;-)
ah! - sorry Sebastian, to many confusion in the last time...
> I am using a 2.6.8 (I was too lazy to patch & compile a 2.6.9 and wanted
> to test 2.6.10 when it's (the sources) in debian/unstable).
>
> >Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can
> >write it to a floppy disk)?
>
> I will do that and tell you later where you can download it.
This may no longer be necessary, but see below.
Acording to your log, your scsi drive also fails later, but boots from ide
(how did you managed to install the ide disks?).
I posted a message to linux-scsi describing this problem. I guess the sym2
driver never worked on the PReP machines. I tried it also with 2.4 kernels.
So to summerize it: No one has a working Powerstack with 2.6 kernel and
booting from SCSI. I hope there will be some input from the scsi list.
> >How does your boot.log looks like?
>
> Attached it.
> Note that I use a Matrox MilleniumII gfx card and XFree4 runs fine
> (without any crash) since I got a 2.6 kernel running (although I am not
> using XFree because I use the Powerstack as a router/server which has no
> Monitor).
Yeah - I search so many times for a Millenium card on eBay. Now I got one for
EUR 1.00 but it is in Germany, while I'm in France now for holidays :-(
I also have a P9100 here, but it is not supported (yet?) under linux...
Greetings
Marc
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Marc Dietrich @ 2005-01-04 13:23 UTC (permalink / raw)
To: Christian; +Cc: linuxppc-dev
In-Reply-To: <41D9FB86.1060407@gmx.net>
Hallo Christian,
thanks for your info. I was also a little confused by all these configs and
images ...
So you are using netboot and it seems that when having a root-fs via nfs _no_
disk driver is initialized even if it is compiled in (acording to your
config). Funny, didn't know that.
Sebastian just send me a mail with his bootlog, and later also some zImage url
I hope. He is running a 2.6.8 kernel and his kernel (scsi: sym2 2.1.18j)
seems to detect the hard disk but fails later due to the same scsi timeouts.
Luckily, he managed to install 2 IDE disks...
Greetings
Marc
Am Dienstag, 4. Januar 2005 03:12 schrieben Sie:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > anymore. but i'm building PReP kernel everyday, results and a config-file
> > is here:
> >
> > http://www.nerdbynature.de/bits/sheep/latest-kernel/
>
> sorry, it should read:
>
> http://www.nerdbynature.de/bits/hal/daily/
>
> > yes, i'll upload working zImage.prep + .config here:
> >
> > http://www.nerdbynature.de/bits/sheep/prep/
>
> and: http://www.nerdbynature.de/bits/hal/daily/results/
>
> >>>How does your boot.log looks like?
>
> will show up in http://www.nerdbynature.de/bits/hal/daily/boot/
>
> sorry for the confusion,
> Christian.
> - --
> BOFH excuse #57:
>
> Groundskeepers stole the root password
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFB2fuGC/PVm5+NVoYRAiCxAKC8B1L+FVw/5CoG3y7IpFVxpqzrgACfVSK7
> gXQcGiHCfHg3vEabXHtaZaU=
> =2cwH
> -----END PGP SIGNATURE-----
^ permalink raw reply
* Re: Linux Kernel boot problem
From: Jerry Van Baren @ 2005-01-04 14:06 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <000401c4f261$dca2c1e0$1269cb0a@bgcw301>
Srivatsan wrote (badly quoted):
> * *
> *Well, what are the last readable messages you can find in the buffer?*
> * *
> *The last readable message which I see in the log buffer is *
> * *
>
> *00138BD4: 3C 36 3E 4D 65 6D 6F 72 79 20 42 41 54 20 6D 61 |<6>Memory BAT ma|*
> *00138BE4: 70 70 69 6E 67 3A 20 42 41 54 32 3D 31 36 4D 62 |pping: BAT2=16Mb|*
> *00138BF4: 2C 20 42 41 54 33 3D 30 4D 62 2C 20 72 65 73 69 |, BAT3=0Mb, resi|*
> *00138C04: 64 75 61 6C 3A 20 30 4D 62 0A 00 00 00 00 00 00 |dual: 0Mb.......|*
>
> *Any pointers will surely help me with the problem. *
>
> *I have tried with all serial ports, I find that the porting is done
> fine. I checked with the MPC860 porting document available on the web. *
>
> *Any pointers will surely help me. Thanks Mr.Wolfgang and everyone for
> sparing me time.*
>
> *Best regards,*
> *C.R.*Srivatsan
I don't have a clue, but The Source Knows (TSK). The following is very
generic advice...
The "<6>" is a progress stamp put out by the kernel start up code. Find
where it is printed and/or where the BAT mapping message is printed and
look what the kernel does next. Somewhere between "<6>" and where "<7>"
would be printed if your kernel didn't crash is where the problem lies.
If the crash location isn't obvious, move the "<7>" back in the code
until you see it coming out, which will further narrow down the error area.
My totally uneducated guess (TUG) is that you have problems with your
BAT configuration. Compare your memory map to how your BATs are set up
by the linux kernel. Also, verify that EVERY piece of hardware
(ESPECIALLY the uart hardware) is mapped properly (probably by a BAT) at
this point in time. My TUG is that you are trying to access a piece of
hardware (likely a uart or a blinking LED) that isn't mapped and thus
you are getting a memory map fault. At this point in time, memory map
faults are very silent and very deadly.
gvb
P.S. Sorry for all the bad TLA humor ;-)
^ permalink raw reply
* Re: 43p-140 install issues
From: Mike Martin @ 2005-01-04 13:41 UTC (permalink / raw)
To: Philippe Guyot; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc
In-Reply-To: <855e88d005010403234bd3eeb3@mail.gmail.com>
> I'll give 2.4.22 a try tonight.
>
> Thanks!
> MikeMartin
I gave Leigh's 2.4.22 a try. It gave me the same result with the
debian root disk:
VFS: Insert root floppy and press ENTER
FAT: bogus logical sector size 1981
FAT: bogus logical sector size 1981
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 8, size 1024)
Kernel panic: VFS: Unable to mount root fs on 02:00
Tonight I'll grab a different root floppy and see what happens.
Leigh's 2.4.22 will also boot the system installed on /dev/sdb1,
however it also stopped responding after awhile. I think it lasted
longer than with 2.4.19.
MikeMartin
^ permalink raw reply
* RE: Linux Kernel boot problem
From: Srivatsan @ 2005-01-04 13:32 UTC (permalink / raw)
To: wd; +Cc: linuxppc-embedded
In-Reply-To: <20041228174222.79FC7C14EC@atlas.denx.de>
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
Well, what are the last readable messages you can find in the buffer?
The last readable message which I see in the log buffer is
00138BD4: 3C 36 3E 4D 65 6D 6F 72 79 20 42 41 54 20 6D 61 |<6>Memory
BAT ma|
00138BE4: 70 70 69 6E 67 3A 20 42 41 54 32 3D 31 36 4D 62 |pping:
BAT2=16Mb|
00138BF4: 2C 20 42 41 54 33 3D 30 4D 62 2C 20 72 65 73 69 |, BAT3=0Mb,
resi|
00138C04: 64 75 61 6C 3A 20 30 4D 62 0A 00 00 00 00 00 00 |dual:
0Mb.......|
Any pointers will surely help me with the problem.
I have tried with all serial ports, I find that the porting is done
fine. I checked with the MPC860 porting document available on the web.
Any pointers will surely help me. Thanks Mr.Wolfgang and everyone for
sparing me time.
Best regards,
C.R.Srivatsan
********************************DISCLAIMER**********************************
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege of Deccanet Designs Ltd.
If you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you are strictly prohibited from retaining, using, copying, altering or
disclosing the contents of this message.
****************************************************************************
[-- Attachment #2: Type: text/html, Size: 9099 bytes --]
^ permalink raw reply
* Asymmetric throughput in pq2ads. Help needed
From: Bastos Fernandez Alexandre @ 2005-01-04 13:31 UTC (permalink / raw)
To: 'linuxppc'
Hi to all,
I have been doing some throughput test in the 8272ads board
using it as a router.
Several tests have been done with uboot-1.1.2 (using FCC1 ETHERNET)
and linux kernel 2.6.10-rc3
To support both FCC interfaces on this board, I have enabled
FCC2 in BCSR3:
In platforms/pq2ads.h
#define BCSR3_FETHIEN2 ((uint)0x10000000)
#define BCSR3_FETH2_RST ((uint)0x80000000)
In 8260_io/fcc_enet.c
*(volatile uint *)(BCSR_ADDR + 12) &= ~BCSR3_FETHIEN2;
*(volatile uint *)(BCSR_ADDR + 12) |= BCSR3_FETH2_RST;
No other related changes have been done to linuxppc-2.5 top
bitkeeper version of kernel.
In this context I have set this trivial net:
PC1 -----X-cable------ 8272ADS ------X-cable------ PC2
The ADS is connected to PC1 through FCC1 and to PC2 through FCC2.
Then, throughput from PC1 to PC2 (measured using ttcp) is not the
same than throughput from PC2 to PC1.
UDP ... PC1 --> PC2 90 Mbps aprox
PC2 --> PC1 60 Mbps aprox !!!!!!!!
TCP ... PC1 --> PC2 60 Mbps aprox
PC2 --> PC1 1 Mbps aprox !!!!!!!!!!!!
It seems as if the ADS were loosing packets arriving at FCC2.
At this point I am a bit lost. I don't know what I should try to change or
where I should set any breakpoint with my BDI to find what is going wrong.
Any idea from guys in the list?
Thanks,
Alex Bastos
^ permalink raw reply
* Re: Making a serial multiplexer (new driver)
From: Luís Vitório Cargnini @ 2005-01-04 11:07 UTC (permalink / raw)
To: Geert Uytterhoeven, linuxppc-embedded
In-Reply-To: <Pine.GSO.4.61.0501031717080.27452@waterleaf.sonytel.be>
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
it can't be done in user space
why?
Because the multiplexer has an proprietary pŕotocol 8-(
so i'll encapsulate the communication of 3 channels to communicate with
physical device and my user-level applications like pppd don't need to
know the mux protocol, this will be transparent for the user
applications.
On Mon, 2005-01-03 at 17:17 +0100, Geert Uytterhoeven wrote:
> On Mon, 3 Jan 2005, [ISO-8859-1] Luís Vitório Cargnini wrote:
> > Hi i need to write a driver that must multiplex an serial channel my
> > driver will have 3 interfaces and i must communicate with another
> > interface (midleware) like /dev/ttyS2 for example, how could i write a
> > driver that will communicate with my existing uart ???
> >
> > i have a component that could be multiplexed in 3 logical channels throw
> > my single physical channel that are accessed with a normal serial
> > interface using uart, how could this be possible ?
> > this is necessary to be transparent to software user level.
>
> Do it in userspace using fifos?
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
--
Luís Vitório Cargnini <vitorio@digitel.com.br>
Digitel S/A
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Sebastian Heutling @ 2005-01-04 11:31 UTC (permalink / raw)
To: Marc Dietrich; +Cc: linuxppc-dev
In-Reply-To: <200501031326.34477.marvin24@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 3820 bytes --]
Hello Marc,
Marc Dietrich wrote:
>Hi Christian,
>
>
Erm ... I'm Sebastian ;-)
>Am Sonntag, 2. Januar 2005 01:31 schrieb Sebastian Heutling:
>
>
>>You don't really need to change any IRQ above slot 9 on a 2.6.? kernel
>>because the slot is 2 (while it was on 12 in 2.4 kernels).
>>
>>
>
>ah yes, now I understand. You just copied all numbers from top to down.
>
>
Yep.
>
>
>>>[...]
>>>PCI: Probing PCI hardware
>>>Setting PCI interrupts for a "Utah (Powerstack II Pro4000)"
>>>PCI: Cannot allocate resource region 5 of device 0000:00:01.1
>>>
>>>
>>This is the IDE chip which gets IRQ 0 and therefore results in an error.
>>Try changing the value of Slot 1 from 0 to 4 (which is IRQ 14). I don't
>>really think it changes the SCSI timeouts maybe it helps - no one knows
>>for sure ;).
>>
>>
>
>Ok - did that also.
>
>
>
>>>SCSI subsystem initialized
>>>[...]
>>>PCI: Enabling device 0000:00:02.0 (0000 -> 0003)
>>>sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15
>>>
>>>
>
>so I guess 0000:00:02.0 is right as oposed to 0000:00:0C.0 with 2.4 kernels.
>
>
Yes.
>
>
>>>[...]
>>>new BADLUNTBL [ 256] @c7d9aa00.
>>>sym0: SCSI BUS has been reset.
>>>scsi0 : sym-2.1.18m
>>>elevator: using anticipatory as default io scheduler
>>>sym0:0:0:ccb @c7d9ac00 using tag 256.
>>>sym0: queuepos=2.
>>>sym0:0:0: ABORT operation started.
>>>sym0:0:0: ABORT operation timed-out.
>>>sym0:0:0: DEVICE RESET operation started.
>>>sym0:0:0: DEVICE RESET operation timed-out.
>>>sym0:0:0: BUS RESET operation started.
>>>sym0:0:0: BUS RESET operation timed-out.
>>>sym0:0:0: HOST RESET operation started.
>>>sym0:0:0:ccb @c7d9ac00 freeing tag 256.
>>>sym0: SCSI BUS has been reset.
>>>[ hangs here ]
>>>
>>>
>>Hmmm strange ... is there anything attached on scsi?
>>
>>
>
>Yes - a hard disk and a cdrom. Both are working under 2.4 kernels (see the
>boot.log of the 2.4.24-pre1 kernel). I don't use net boot. My system (debian
>sarge) is installed on sda3. Anyway - also on a netboot system, the kernel
>should hang when trying to initialize the scsi controler.
>
>
>
>>... wait a second ... looking at the lspci output ... you use a USB PCI
>>card? The IRQ-sharing doesn't work well and the USB PCI card is on the
>>same slot as the SCSI controller resulting in both using the same IRQ.
>>Remove the USB card and check wether it changes anything. If it does
>>work now: Did it ever work with USB using another kernel? If so maybe
>>there is something else wrong, if not it's a HW Problem.
>>I also attached a config file from my powerstack (which I use as a
>>router and runs a 2.6 kernel since june last year or so)
>>
>>
>
>I didn't checked if the usb card is working under a 2.4 kernel, but it boots
>without problems. I removed it now, just to eleminate possible trouble.
>
>I setup a kernel using your config file and added vga console and offb and
>removed the nfs drivers to get an image smaller then 1.44 Mb (I'm using
>XFree86-3.3.6 with the cirrus 5664 card). This has the same effect than
>before: scsi not working.
>
>It seems, that this config is not for a 2.6.10 kernel. What kernel version are
>you using? Maybe some bad things happened in newer kernels.
>
>
I am using a 2.6.8 (I was too lazy to patch & compile a 2.6.9 and wanted
to test 2.6.10 when it's (the sources) in debian/unstable).
>Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can
>write it to a floppy disk)?
>
>
I will do that and tell you later where you can download it.
>How does your boot.log looks like?
>
>
Attached it.
Note that I use a Matrox MilleniumII gfx card and XFree4 runs fine
(without any crash) since I got a 2.6 kernel running (although I am not
using XFree because I use the Powerstack as a router/server which has no
Monitor).
Sebastian
[-- Attachment #2: boot.log --]
[-- Type: text/plain, Size: 8383 bytes --]
Total memory = 256MB; using 512kB for hash table (at c0380000)
Linux version 2.6.8 (root@sengor) (gcc version 3.3.5 (Debian 1:3.3.5-2)) #8 Tue Nov 9 15:59:40 CET 2004
PReP architecture
On node 0 totalpages: 65536
DMA zone: 65536 pages, LIFO batch:16
Normal zone: 0 pages, LIFO batch:1
HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: root=/dev/sda2 console=ttyS0
PID hash table entries: 2048 (order 11: 16384 bytes)
time_init: decrementer frequency = 16.657680 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 255232k available (2204k kernel code, 1144k data, 160k init, 0k highmem)
Calibrating delay loop... 299.00 BogoMIPS
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
NET: Registered protocol family 16
PCI: Probing PCI hardware
Setting PCI interrupts for a "Utah (Powerstack II Pro4000)"
PCI: Cannot allocate resource region 5 of device 0000:00:01.1
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
PCI: Enabling device 0000:00:08.0 (0080 -> 0082)
matroxfb: Matrox Millennium (PCI) detected
matroxfb: 640x480x8bpp (virtual: 640x6553)
matroxfb: framebuffer at 0xC1800000, mapped to 0xf1800000, size 4194304
fb0: MATROX frame buffer device
fb0: initializing hardware
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Console: switching to colour frame buffer device 80x30
Macintosh non-volatile memory driver v1.1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
W82C105: IDE controller at PCI slot 0000:00:01.1
PCI: Enabling device 0000:00:01.1 (0000 -> 0001)
W82C105: chipset revision 5
W82C105: 100% native mode on irq 14
W82C105: dma_base is invalid (0x0000)
ide0: W82C105 Bus-Master DMA disabled (BIOS)
W82C105: dma_base is invalid (0x0000)
ide1: W82C105 Bus-Master DMA disabled (BIOS)
Probing IDE interface ide0...
hda: ST380021A, ATA DISK drive
hdb: IBM-DTLA-305040, ATA DISK drive
hda: selected PIO 4 (120ns) (0240)
hdb: selected PIO 4 (120ns) (0240)
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
Probing IDE interface ide2...
ide2: Wait for ready failed before probe !
Probing IDE interface ide3...
ide3: Wait for ready failed before probe !
hda: max request size: 128KiB
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63
hda: hda1
hdb: max request size: 128KiB
hdb: 80418240 sectors (41174 MB) w/380KiB Cache, CHS=65535/16/63
hdb: hdb1
PCI: Enabling device 0000:00:02.0 (0000 -> 0003)
sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15
sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18j
Vendor: IBM Model: DPSS-309170N Rev: S93E
Type: Direct-Access ANSI SCSI revision: 03
sym0:0:0: tagged command queuing enabled, command queue depth 16.
scsi(0:0:0:0): Beginning Domain Validation
sym0:0: wide asynchronous.
sym0:0: FAST-10 WIDE SCSI 20.0 MB/s ST (100.0 ns, offset 8)
scsi(0:0:0:0): Ending Domain Validation
st: Version 20040403, fixed bufsize 32768, s/g segs 256
SCSI device sda: 16777216 512-byte hdwr sectors (8590 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
atkbd.c: keyboard reset failed on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
atkbd.c: keyboard reset failed on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
NET: Registered protocol family 1
NET: Registered protocol family 17
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 160k init 36k pmac 4k chrp 4k openfirmware
Adding 262136k swap on /dev/sda3. Priority:-1 extents:1
EXT3 FS on sda2, internal journal
Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Enabling device 0000:00:04.0 (0000 -> 0003)
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media AUI (#2) described by a 21140 non-MII (0) block.
tulip0: Index #1 - Media MII (#11) described by a 21140 MII PHY (1) block.
tulip0: MII transceiver #8 config 3100 status 786b advertising 01e1.
eth0: Digital DS21140 Tulip rev 34 at 0x1800, 08:00:3E:29:2E:45, IRQ 11.
de2104x PCI Ethernet driver v0.7 (Mar 17, 2004)
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
eth0: Setting full-duplex based on MII#8 link partner capability of 45e1.
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (2048 buckets, 16384 max) - 296 bytes per conntrack
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
PCI: Enabling device 0000:00:06.0 (0000 -> 0003)
eth1: 0000:00:06.0, 00:02:B3:1A:8C:72, IRQ 10.
Board assembly 751767-003, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
Secondary interface chip i82555.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x8e695832).
PPP BSD Compression module registered
PPP Deflate Compression module registered
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
UDP: bad checksum. From 213.97.110.54:5889 to 83.129.181.72:4472 ulen 27
UDP: bad checksum. From 82.90.52.67:12826 to 83.129.248.97:4223 ulen 27
eth1: TX underrun, threshold adjusted.
eth1: TX underrun, threshold adjusted.
sym0:0:0: ABORT operation started.
sym0:0:0: ABORT operation timed-out.
sym0:0:0: ABORT operation started.
sym0:0:0: ABORT operation timed-out.
sym0:0:0: ABORT operation started.
sym0:0:0: ABORT operation timed-out.
sym0:0:0: ABORT operation started.
sym0:0:0: ABORT operation timed-out.
sym0:0:0: DEVICE RESET operation started.
sym0:0:0: DEVICE RESET operation timed-out.
sym0:0:0: BUS RESET operation started.
sym0: SCSI BUS reset detected.
sym0: SCSI BUS has been reset.
sym0:0:0: BUS RESET operation complete.
eth1: TX underrun, threshold adjusted.
UDP: short packet: From 217.126.164.250:5676 33/27 to 83.129.160.15:11124
eth1: TX underrun, threshold adjusted.
UDP: short packet: From 82.254.199.92:1024 132/26 to 83.129.199.46:571
UDP: bad checksum. From 217.126.164.250:5676 to 83.129.174.118:5667 ulen 27
UDP: bad checksum. From 82.50.40.247:7689 to 83.129.1.186:4120 ulen 28
UDP: bad checksum. From 218.90.225.199:3357 to 83.129.16.247:3258 ulen 26
UDP: short packet: From 217.126.164.250:2960 11925/27 to 83.129.63.189:4662
UDP: short packet: From 83.129.64.153:888 0/27 to 83.129.70.178:13054
UDP: bad checksum. From 217.126.164.250:5676 to 83.129.70.178:3454 ulen 33
UDP: bad checksum. From 217.126.164.250:5676 to 83.129.70.178:12855 ulen 80
^ permalink raw reply
* Re: 43p-140 install issues
From: Mike Martin @ 2005-01-04 11:23 UTC (permalink / raw)
To: Philippe Guyot; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc
In-Reply-To: <200501041023.37580.pguyot@cvf.fr>
The firmware is the most recent.
The kernel (boot) is Leigh's 2.4.19 kernel.
The root is from Woody.
Both floppies were written with dd to blank, unforatted disks.
I'll give 2.4.22 a try tonight.
Thanks!
MikeMartin
On Tue, 4 Jan 2005 10:23:37 +0100, Philippe Guyot <pguyot@cvf.fr> wrote:
> On Tuesday 04 January 2005 05:03, Mike Martin wrote:
> > (Re-posting with shorter attachment to please the list gods. Sorry)
> >
> > > If there is such a deadline, why not consider to install first a woody
> > > (many successes exist) then upgrading to sarge after ?
> >
> > Ok... trying again with Leigh Brown's boot image and a woody root
> > floppy and a woody CD.
> >
> > The console capture is below. Leigh's kernel boots up great, asks for
> > a root floppy and then ...
> >
> > VFS: Insert root floppy and press ENTER
> >
> > FAT: bogus logical sector size 1981
> > FAT: bogus logical sector size 1981
> > read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> > block 64, size 1024)
> > read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> > block 8, size 1024)
> > Kernel panic: VFS: Unable to mount root fs on 02:00
> >
> > Reiserfs? Huh? I tried it twice, two different floppies. Both written
> > as follows (as suggested in Debian manual):
> > sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
> > \1440+0 records in
> > 1440+0 records out
> > 1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)
> >
> > I can however boot the installation I made earlier using Leigh's
> > image. I have completed the installation and it runs ... for a short
> > period of time. After about 5 minutes or so it stops responding to the
> > console and to pings.
> >
>
> BTW, what about your firmware? Is it the most recent one ?
>
> > MikeMartin
>
^ permalink raw reply
* Re: 43p-140 install issues
From: Ulrich Teichert @ 2005-01-04 11:19 UTC (permalink / raw)
To: Philippe Guyot
Cc: Ulrich Teichert, linuxppc-dev, mikemartin, debian-powerpc,
Mike Martin
In-Reply-To: <200501041023.37580.pguyot@cvf.fr>
Hi,
[del]
> BTW, what about your firmware? Is it the most recent one ?
Yes, it is. I have asked this before ;-)
CU,
Uli
--
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24 |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
^ permalink raw reply
* Re: MPC5200 PCI byte-swapping
From: Stefan Nickl @ 2005-01-04 9:37 UTC (permalink / raw)
To: Sylvain Munaut; +Cc: linuxppc-embedded
In-Reply-To: <41D97734.3070800@246tNt.com>
On Mon, 2005-01-03 at 17:47 +0100, Sylvain Munaut wrote:
> >Thanks. I had an older manual that didn't spell it out so
> >clearly.
> >
> >I've been trying to interpret the PCI sections for some other
> >82xx family parts, and it appears that they do NOT do this
> >byte lane swapping, so this make the 5200 non-standard in
> >this regard, which is unfortunate. If I'm understanding this
> >right, one would have to have different drivers for a PCI
> >device on a 5200 and an 8270, for instance.
> >
> >
> Mmmm ...
> Still I use the intel eepro driver without problems or modifications.
> As long as the driver uses the proper readl/writel that should do
> it or am I mistaken ?
This reminds me of an issue with the Coral P PCI graphics chip I
encountered a while ago. The driver is from the Denx CVS and was
apparently developed on a 5200.
When I tried it on a mpc8540, the console text looked blueish, but I
could not investigate further. But I know where I'd look at now ...
--
Stefan Nickl
Kontron Modular Computers
^ permalink raw reply
* Re: 43p-140 install issues
From: Philippe Guyot @ 2005-01-04 9:23 UTC (permalink / raw)
To: mikemartin, Mike Martin; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc
In-Reply-To: <855e88d0050103200337efc719@mail.gmail.com>
On Tuesday 04 January 2005 05:03, Mike Martin wrote:
> (Re-posting with shorter attachment to please the list gods. Sorry)
>
> > If there is such a deadline, why not consider to install first a woody
> > (many successes exist) then upgrading to sarge after ?
>
> Ok... trying again with Leigh Brown's boot image and a woody root
> floppy and a woody CD.
>
> The console capture is below. Leigh's kernel boots up great, asks for
> a root floppy and then ...
>
> VFS: Insert root floppy and press ENTER
>
> FAT: bogus logical sector size 1981
> FAT: bogus logical sector size 1981
> read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> block 64, size 1024)
> read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> block 8, size 1024)
> Kernel panic: VFS: Unable to mount root fs on 02:00
>
> Reiserfs? Huh? I tried it twice, two different floppies. Both written
> as follows (as suggested in Debian manual):
> sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
> \1440+0 records in
> 1440+0 records out
> 1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)
>
> I can however boot the installation I made earlier using Leigh's
> image. I have completed the installation and it runs ... for a short
> period of time. After about 5 minutes or so it stops responding to the
> console and to pings.
>
BTW, what about your firmware? Is it the most recent one ?
> MikeMartin
^ permalink raw reply
* Re: 43p-140 install issues
From: Ulrich Teichert @ 2005-01-04 8:20 UTC (permalink / raw)
To: mikemartin; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc, Philippe Guyot
In-Reply-To: <855e88d0050103200337efc719@mail.gmail.com>
Hi,
[del]
>Ok... trying again with Leigh Brown's boot image and a woody root
>floppy and a woody CD.
>
>The console capture is below. Leigh's kernel boots up great, asks for
>a root floppy and then ...
>
>VFS: Insert root floppy and press ENTER
>
>FAT: bogus logical sector size 1981
>FAT: bogus logical sector size 1981
Strange.
[del]
>Reiserfs? Huh? I tried it twice, two different floppies. Both written
>as follows (as suggested in Debian manual):
>sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
>\1440+0 records in
>1440+0 records out
>1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)
How did you format the floppys before?
>I can however boot the installation I made earlier using Leigh's
>image. I have completed the installation and it runs ... for a short
>period of time. After about 5 minutes or so it stops responding to the
>console and to pings.
Ugh. I would recommend to dd Leighs kernel to your disk then. This has been
running reliable for me. The bootup log looks good to me, minus the floppy issue,
it's very much like mine.
HTH,
Uli
--
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24 |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
^ permalink raw reply
* Re: (OT?) Making a serial multiplexer (new driver)
From: David Jander @ 2005-01-04 8:00 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <1104758458.14925.5.camel@vitorio>
Hi,
I am working on something like that (GSM-07.10 mux). Contact me if you are
interested.
Greetings,
--
David Jander
Protonic Holland.
^ permalink raw reply
* Re: 43p-140 install issues
From: Mike Martin @ 2005-01-04 4:03 UTC (permalink / raw)
To: Philippe Guyot; +Cc: Ulrich Teichert, linuxppc-dev, debian-powerpc
In-Reply-To: <200501031530.54487.pguyot@cvf.fr>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
(Re-posting with shorter attachment to please the list gods. Sorry)
> If there is such a deadline, why not consider to install first a woody (many
> successes exist) then upgrading to sarge after ?
Ok... trying again with Leigh Brown's boot image and a woody root
floppy and a woody CD.
The console capture is below. Leigh's kernel boots up great, asks for
a root floppy and then ...
VFS: Insert root floppy and press ENTER
FAT: bogus logical sector size 1981
FAT: bogus logical sector size 1981
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 8, size 1024)
Kernel panic: VFS: Unable to mount root fs on 02:00
Reiserfs? Huh? I tried it twice, two different floppies. Both written
as follows (as suggested in Debian manual):
sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
\1440+0 records in
1440+0 records out
1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)
I can however boot the installation I made earlier using Leigh's
image. I have completed the installation and it runs ... for a short
period of time. After about 5 minutes or so it stops responding to the
console and to pings.
MikeMartin
[-- Attachment #2: 43pflo~1.txt --]
[-- Type: text/plain, Size: 5732 bytes --]
RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000
memory keyboard network scsi speaker ok
0 > boot floppy
loaded at: 00600400 00734EC8
relocated to: 00800100 00934BC8
board data at: 00231370 00237D7C
relocated to: 0092B02C 00931A38
zimage at: 00805B90 0092AA9D
avail ram: 00400000 00800000
Linux/PPC load: console=ttyS0,9600 root=/dev/fd0
Uncompressing Linux...done.
Now booting the kernel
Memory BAT mapping: BAT2=256Mb, BAT3=0Mb, residual: 0Mb
Total memory = 256MB; using 512kB for hash table (at c0300000)
Linux version 2.4.19 (leigh@micro.solinno.co.uk) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81)) #3 Sun Aug 4 08:28:30 BST 2002
PReP architecture
IBM planar ID: 000000d5
PReP boot cpu: 0
MPIC at 0xfddc0000 (0x3ddc0000), length 0x00040000 mapped to 0xeffc0000
On node 0 totalpages: 65536
zone(0): 65536 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0,9600 root=/dev/fd0
OpenPIC Version 1.0 (4 CPUs and 16 IRQ sources) at effc0000
time_init: decrementer frequency = 16.617869 MHz
Console: colour dummy device 80x25
Calibrating delay loop... 331.77 BogoMIPS
Memory: 255552k available (1944k kernel code, 880k data, 160k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Bridge 00:17.0 resource 2 was deactivated by firmware
Setting PCI interrupts for a "IBM 43P-140 (Tiger1)"
PCI: Cannot allocate resource region 0 of PCI bridge 1
PCI: bridge 1 resource 0 moved to 7ff000..7fffff
PCI: Cannot allocate resource region 0 of device 00:0b.0
PCI: Cannot allocate resource region 0 of device 00:0c.0
PCI: Cannot allocate resource region 0 of device 00:10.0
PCI: Cannot allocate resource region 0 of device 00:12.0
PCI: Cannot allocate resource region 0 of device 01:03.0
PCI: moved device 00:0b.0 resource 0 (101) to 1000
PCI: moved device 00:0c.0 resource 0 (101) to 1020
PCI: moved device 00:10.0 resource 0 (101) to 1400
PCI: moved device 00:12.0 resource 0 (101) to 1040
PCI: moved device 01:03.0 resource 0 (101) to 7ff000
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Journalled Block Device driver loaded
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
IBM_E15: initializing
IBM_E15: could not find S3 864 in system
initialize_kbd: Keyboard reset failed, no ACK
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
keyboard: Timeout - AT keyboard not present?(ed)
keyboard: Timeout - AT keyboard not present?(f4)
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 2.88M
FDC 0 is a National Semiconductor PC87306
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
pcnet32.c:v1.27a 10.02.2002 tsbogend@alpha.franken.de
PCI: Enabling device 00:0c.0 (0000 -> 0003)
pcnet32: PCnet/PCI II 79C970A at 0x1020, 00 06 29 ba 40 05 assigned IRQ 22.
eth0: registered as PCnet/PCI II 79C970A
pcnet32: 1 cards_found.
SCSI subsystem driver Revision: 1.00
PCI: Enabling device 00:10.0 (0010 -> 0013)
ncr53c8xx: at PCI bus 0, device 16, function 0
ncr53c8xx: setting PCI_COMMAND_MASTER...(fix-up)
ncr53c8xx: 53c825a detected
ncr53c825a-0: rev 0x13 on pci bus 0 device 16 function 0 irq 23
ncr53c825a-0: ID 7, Fast-10, Parity Checking
scsi0 : ncr53c8xx-3.4.3b-20010512
Vendor: IBM Model: CDRM00203 !K Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 02
ncr53c825a-0-<4,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 8)
Vendor: IBM Model: DCHS09U Rev: 6363
Type: Direct-Access ANSI SCSI revision: 02
ncr53c825a-0-<5,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 8)
Vendor: IBM Model: DPSS-318350N Rev: S96F
Type: Direct-Access ANSI SCSI revision: 03
Attached scsi disk sda at scsi0, channel 0, id 4, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 5, lun 0
SCSI device sda: 17774160 512-byte hdwr sectors (9100 MB)
Partition check:
sda: sda1
sdb: Spinning up disk..............ready
SCSI device sdb: 35548320 512-byte hdwr sectors (18201 MB)
sdb: sdb1 sdb2 < sdb5 >
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
ncr53c825a-0-<3,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 8)
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.12
Macintosh non-volatile memory driver v1.0
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Insert root floppy and press ENTER
FAT: bogus logical sector size 1981
FAT: bogus logical sector size 1981
read_super_block: can't find a reiserfs filesystem on (dev 02:00, block 64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 02:00, block 8, size 1024)
Kernel panic: VFS: Unable to mount root fs on 02:00
<0>Rebooting in 180 seconds..
^ permalink raw reply
* Re: dcbz not used on ppc64?
From: Anton Blanchard @ 2005-01-04 3:16 UTC (permalink / raw)
To: Chris Friesen; +Cc: linuxppc-dev
In-Reply-To: <41D9D6A2.2010705@nortelnetworks.com>
> Hmm. As of 2.6.9 at least, clear_page() is only ever called by
> clear_user_page(), which in turn is only ever called by
> drivers/media/video/video-buf.c. I'm not using that driver, which
> explains why the instruction didn't show up when I disassembled the kernel.
Dont forget mm/memory.c:clear_user_highpage -> clear_user_page.
Anton
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: Christian @ 2005-01-04 2:12 UTC (permalink / raw)
To: linuxppc-dev
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> anymore. but i'm building PReP kernel everyday, results and a config-file
> is here:
>
> http://www.nerdbynature.de/bits/sheep/latest-kernel/
sorry, it should read:
http://www.nerdbynature.de/bits/hal/daily/
> yes, i'll upload working zImage.prep + .config here:
>
> http://www.nerdbynature.de/bits/sheep/prep/
and: http://www.nerdbynature.de/bits/hal/daily/results/
>>>How does your boot.log looks like?
will show up in http://www.nerdbynature.de/bits/hal/daily/boot/
sorry for the confusion,
Christian.
- --
BOFH excuse #57:
Groundskeepers stole the root password
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB2fuGC/PVm5+NVoYRAiCxAKC8B1L+FVw/5CoG3y7IpFVxpqzrgACfVSK7
gXQcGiHCfHg3vEabXHtaZaU=
=2cwH
-----END PGP SIGNATURE-----
^ permalink raw reply
* Re: [FYI] linux 2.6 still not working with PReP (ppc32)
From: evilninja @ 2005-01-04 0:54 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <200501031326.34477.marvin24@gmx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marc Dietrich schrieb:
> Hi Christian,
>
actually, Sebastian is the helping hand here ;)
> Yes - a hard disk and a cdrom. Both are working under 2.4 kernels (see the
> boot.log of the 2.4.24-pre1 kernel). I don't use net boot. My system (debian
> sarge) is installed on sda3. Anyway - also on a netboot system, the kernel
> should hang when trying to initialize the scsi controler.
i can't help you much at the scsi-issue here. as i said, i don't have a
disk attached to the machine any more. the last time i booted with disk
was a 2.4 kernel. and these errors (ABORT operation started / timed-out)
occured upon heavy load on the scsi bus. i think i've never booted a 2.6
kernel with a scsi disk attached. but the errors look familiar :-(
> I setup a kernel using your config file and added vga console and offb and
> removed the nfs drivers to get an image smaller then 1.44 Mb (I'm using
> XFree86-3.3.6 with the cirrus 5664 card). This has the same effect than
> before: scsi not working.
:-(
> It seems, that this config is not for a 2.6.10 kernel. What kernel version are
> you using? Maybe some bad things happened in newer kernels.
ironically, now that i am able to netboot the machine, i'm not *using* it
anymore. but i'm building PReP kernel everyday, results and a config-file
is here:
http://www.nerdbynature.de/bits/sheep/latest-kernel/
> Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can
> write it to a floppy disk)?
yes, i'll upload working zImage.prep + .config here:
http://www.nerdbynature.de/bits/sheep/prep/
> How does your boot.log looks like?
i'll upload a boot.log too.
Christian.
- --
BOFH excuse #78:
Yes, yes, its called a design limitation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB2ekxC/PVm5+NVoYRAs/MAKCGSNylixVnx6W20TIK/h5ALwivxQCfc9pi
IL8BTtzcpDTJ9KNwhixVqXc=
=ggNI
-----END PGP SIGNATURE-----
^ permalink raw reply
* Re: dcbz not used on ppc64?
From: Chris Friesen @ 2005-01-03 23:34 UTC (permalink / raw)
To: Anton Blanchard; +Cc: linuxppc-dev
In-Reply-To: <20050103225822.GC7335@krispykreme.ozlabs.ibm.com>
Anton Blanchard wrote:
>>1) Is it in fact true that ppc64 does not use dcbz in the kernel?
>>2) If so, why not? Presumably it would be a win in some cases,
>>otherwise they wouldn't be using it in ppc32. Is there some other
>>factore in play for ppc64?
>
>
> include/asm-ppc64/page.h:clear_page() uses it:
Hmm. As of 2.6.9 at least, clear_page() is only ever called by
clear_user_page(), which in turn is only ever called by
drivers/media/video/video-buf.c. I'm not using that driver, which
explains why the instruction didn't show up when I disassembled the kernel.
Still, ppc32 also uses it in cacheable_memzero and __copy_tofrom_user.
It's also used in cacheable_memcpy, but that routine doesn't seem to be
used anywhere.
Chris
^ permalink raw reply
* Re: dcbz not used on ppc64?
From: Anton Blanchard @ 2005-01-03 22:58 UTC (permalink / raw)
To: Chris Friesen; +Cc: linuxppc-dev
In-Reply-To: <41D9CD19.50207@nortelnetworks.com>
Hi,
> I ran into some issues with the use of the dcbz instruction in the
> kernel for ppc32. I'm now looking at porting our work to ppc64, and
> when I looked around a bit, I found that the dcbz instruction doesn't
> appear to be used in ppc64.
>
> This leads me to ask:
>
> 1) Is it in fact true that ppc64 does not use dcbz in the kernel?
> 2) If so, why not? Presumably it would be a win in some cases,
> otherwise they wouldn't be using it in ppc32. Is there some other
> factore in play for ppc64?
include/asm-ppc64/page.h:clear_page() uses it:
static __inline__ void clear_page(void *addr)
{
unsigned long lines, line_size;
line_size = systemcfg->dCacheL1LineSize;
lines = naca->dCacheL1LinesPerPage;
__asm__ __volatile__(
"mtctr %1 # clear_page\n\
1: dcbz 0,%0\n\
add %0,%0,%3\n\
bdnz+ 1b"
: "=r" (addr)
: "r" (lines), "0" (addr), "r" (line_size)
: "ctr", "memory");
}
Anton
^ permalink raw reply
* dcbz not used on ppc64?
From: Chris Friesen @ 2005-01-03 22:54 UTC (permalink / raw)
To: linuxppc-dev
I ran into some issues with the use of the dcbz instruction in the
kernel for ppc32. I'm now looking at porting our work to ppc64, and
when I looked around a bit, I found that the dcbz instruction doesn't
appear to be used in ppc64.
This leads me to ask:
1) Is it in fact true that ppc64 does not use dcbz in the kernel?
2) If so, why not? Presumably it would be a win in some cases,
otherwise they wouldn't be using it in ppc32. Is there some other
factore in play for ppc64?
Thanks,
Chris
^ permalink raw reply
* Re: 43p-140 install issues
From: Ulrich Teichert @ 2005-01-03 22:11 UTC (permalink / raw)
To: Leigh Brown; +Cc: Ulrich Teichert, linuxppc-dev, mikemartin, debian-powerpc
In-Reply-To: <33721.82.10.231.190.1104781370.squirrel@82.10.231.190>
Hi,
>Delete the "console=tty0", so you end up with:
>
> Linux/PPC load: console=ttyS0,9600 root=/dev/ram
>
>and try again!
[del]
Right, then the installer knows what to do. I think this should go into
the Debian installation docs, there are a lot of boxes with graphic cards
out which are not supported by Linux.
But the low level SCSI-driver is missing in this image, or any low level
SCSI drivers for that matter. There are only the high level modules there,
like sd_mod.ko and sr_mod.ko:
Nov 30 00:06:32 hw-detect: Using discover version 1.
Nov 30 00:06:35 hw-detect: Detecting hardware...
Nov 30 00:06:36 hw-detect: Missing module 'sym53c8xx'.
Nov 30 00:06:36 hw-detect: Missing module 'usb-storage'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-mod'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-probe-mod'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-detect'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-generic'.
Nov 30 00:06:37 hw-detect: Missing module 'ide-floppy'.
--More-- (57% of 44385 bytes) Nov 30 00:06:37 hw-detect: Missing module 'ide-disk'.
Nov 30 00:06:37 hw-detect: Missing module 'isofs'.
Nov 30 00:06:37 hw-detect: Loading modules...
Nov 30 00:06:37 hw-detect: Detected module 'pcnet32' for 'Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]'
Nov 30 00:06:37 hw-detect: Trying to load module 'pcnet32'
Nov 30 00:06:37 kernel: pcnet32.c:v1.30i 06.28.2004 tsbogend@alpha.franken.de
Nov 30 00:06:37 kernel: PCI: Enabling device 0000:00:0c.0 (0000 -> 0003)
Nov 30 00:06:37 kernel: pcnet32: PCnet/PCI II 79C970A at 0x1020, 00 06 29 2e 98 9d assigned IRQ 22.
Nov 30 00:06:37 kernel: divert: allocating divert_blk for eth0
Nov 30 00:06:37 kernel: eth0: registered as PCnet/PCI II 79C970A
Nov 30 00:06:37 kernel: pcnet32: 1 cards_found.
Nov 30 00:06:38 hw-detect: Detected module 'floppy' for 'Linux Floppy'
Nov 30 00:06:38 hw-detect: Trying to load module 'floppy'
Nov 30 00:06:38 kernel: inserting floppy driver for 2.6.8-powerpc
Nov 30 00:06:38 kernel: Using anticipatory io scheduler
Nov 30 00:06:38 kernel: Floppy drive(s): fd0 is 2.88M
Nov 30 00:06:38 kernel: FDC 0 is a National Semiconductor PC87306
Nov 30 00:06:38 hw-detect: Detected module 'ide-cd' for 'Linux ATAPI CD-ROM'
Nov 30 00:06:38 hw-detect: Trying to load module 'ide-cd'
Nov 30 00:06:39 kernel: Linux Kernel Card Services
Nov 30 00:06:39 kernel: options: [pci] [cardbus] [pm]
Nov 30 00:06:39 hw-detect: Starting PCMCIA services: using yenta_socket instead of i82365
Nov 30 00:06:39 hw-detect: cardmgr[1070]: no sockets found!
Nov 30 00:06:39 cardmgr[1070]: no sockets found!
Nov 30 00:06:39 hw-detect: done.
Nov 30 00:06:39 hw-detect: Detected discover version 1, installing discover1.
Nov 30 00:06:39 hw-detect: Detected hotplug support, installing hotplug.
Nov 30 00:06:40 hw-detect: Missing modules 'sym53c8xx (Symbios Logic Inc. / NCR 53c825), usb-storage (USB storage), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-generic (Linux IDE support), ide-floppy (Linux IDE floppy), ide-disk (Linux ATA DISK), isofs (Linux ISO 9660 filesystem)
/lib/modules/2.6.8-powerpc/kernel/drivers/scsi # ls
scsi_mod.ko sd_mod.ko sr_mod.ko
So, either this is the wrong image (I've taken the same as Daniel mentioned
in one of his mails: http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd),
or it's missing some vital modules.
HTH,
Uli
--
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24 |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox