From: Michael Lundkvist <ml@epact.se>
To: linuxppc-dev@lists.linuxppc.org
Cc: aeb@veritas.com
Subject: Going from 2.2.12 to 2.2.17pre10
Date: 06 Jul 2000 15:27:51 +0200 [thread overview]
Message-ID: <qphfa3ie20.fsf@erbium.epact.se> (raw)
Hi!
I'm trying to go from 2.2.12 to 2.2.17pre10 on an MVME 2400.
A few problems:
The Motorola SROM bug-patch lacks one row in de4x5.c:
--- de4x5.c~ Thu Jul 6 16:01:32 2000
+++ de4x5.c Thu Jul 6 16:14:18 2000
@@ -4829,6 +4829,7 @@
} else if ((lp->media == INIT) && (lp->timeout < 0)) {
lp->ibn = 3;
lp->active = *p;
+ if (MOTO_SROM_BUG) lp->active = 0;
lp->infoblock_csr6 = OMR_MII_100;
lp->useMII = TRUE;
lp->infoblock_media = ANS;
This one was easy. Now for the hard one. :)
I'm using a PMC-harddisk based on the CMD-646 chipset (Ramix 233).
I installed my system under 2.2.12 with Debian.
When I come to the partition check in 2.2.17pre10 it fails with
"hda: unknown partition table"
I added a printout in drivers/block/genhd.c in msdos_partition()
--- genhd.c~ Thu Jul 6 16:01:31 2000
+++ genhd.c Thu Jul 6 16:48:02 2000
@@ -522,7 +522,8 @@
#endif
if (*(unsigned short *) (0x1fe + data) != cpu_to_le16(MSDOS_LABEL_MAGIC)) {
brelse(bh);
- return 0;
+ printk("Data: %x LABEL:%x\n",(*(unsigned short *) (0x1fe + data)), cpu_to_le16(MSDOS_LABEL_MAGIC) );
+ return 0;
}
p = (struct partition *) (0x1be + data);
With this I get the following printout:
hda:Data: aa55 LABEL:55aa
So it seems like the byte order is wrong. Does anyone know why this
happens?
Please don't tell me my 2.2.12 partitioned disk is wrong. :)
Where do I go for the best LinuxPPC 2.4 kernel for MVME-boards? Is it
fsmlabs Bitkeeper repository?
/Micke
--
ml@epact.se
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-06 13:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 13:27 Michael Lundkvist [this message]
2000-07-06 13:54 ` Going from 2.2.12 to 2.2.17pre10 Hollis Blanchard
2000-07-06 17:17 ` Gabriel Paubert
2000-07-06 17:32 ` Michael Lundkvist
2000-07-06 17:55 ` Gabriel Paubert
2000-07-06 22:23 ` Michael Lundkvist
2000-07-07 8:22 ` Gabriel Paubert
2000-07-07 8:55 ` Michael Lundkvist
2000-07-07 9:21 ` Gabriel Paubert
2000-07-07 9:47 ` Michael Lundkvist
2000-07-07 10:19 ` Gabriel Paubert
2000-07-08 0:08 ` Problem with de4x5 on an MVME-2400 Michael Lundkvist
2000-07-10 11:58 ` Gabriel Paubert
2000-07-12 13:01 ` Michael Lundkvist
2000-07-08 23:29 ` Going from 2.2.12 to 2.2.17pre10 Matt Porter
2000-07-09 6:12 ` Michael Lundkvist
2000-07-10 5:29 ` Matt Porter
2000-07-10 12:25 ` Gabriel Paubert
2000-07-11 5:57 ` Matt Porter
2000-07-11 9:37 ` Adrian Cox
2000-07-11 10:17 ` Benjamin Herrenschmidt
2000-07-11 12:57 ` Adrian Cox
2000-07-11 14:10 ` Claus
2000-07-11 19:15 ` Geert Uytterhoeven
2000-07-12 13:31 ` Benjamin Herrenschmidt
2000-07-13 11:17 ` Geert Uytterhoeven
2000-07-12 9:11 ` Timothy A. Seufert
2000-07-12 14:16 ` Matt Porter
2000-07-13 11:43 ` Gabriel Paubert
2000-07-13 14:12 ` Matt Porter
2000-07-12 12:52 ` Michael Lundkvist
2000-07-12 14:17 ` Matt Porter
2000-07-10 12:12 ` Gabriel Paubert
2000-07-11 6:12 ` Matt Porter
2000-07-11 10:48 ` Gabriel Paubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=qphfa3ie20.fsf@erbium.epact.se \
--to=ml@epact.se \
--cc=aeb@veritas.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.