From: Patrick Bottelberger <patrick.bottelberger@sigon.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org
Subject: Re: Linux on Amiga A600, a success story (in progress, with possible patch)
Date: Wed, 25 Jan 2012 20:11:05 +0100 [thread overview]
Message-ID: <4F2053C9.3090201@sigon.net> (raw)
In-Reply-To: <CAMuHMdWbQau3kS2-svDS705_PS4-0adCCvLvT=Af6VKKZfr+gA@mail.gmail.com>
Hi Geert,
Geert Uytterhoeven schrieb:
>> Without supplying the '-p' parameter amiboot didn't output anything at
>> all, it just froze the amiga directly after entering the command.
>>
>
> Even with '-d'?
>
Yes, even with "-d", no output is printed, after entering the command
("amiboot -d root=/dev/hda5" for example) and pressing "enter" the
system freezes immediately.
> I can't reproduce it on ARAnyM with 3.1.4.
>
>
>> Call Trace: [<0000ffff>] mm_release+0xa1/0xa4
>> [<002b84fa>] topology_sysfs_init+0x0/0x1e
>>
>> Seems to prove that, do you think
>>
>
> But this indeed looks like the same problem. Are you using a Debianized 3.1.4
> source tree?
>
I just checked again, yes, you're right, i totally forgot i patched my
source tree with the Debian patches, sorry :-(
>> http://www.spinics.net/lists/linux-m68k/msg04709.html would solve the issue?
>>
>
> Yes, that should fix this problem.
>
It really did! Thank you for pointing me in the right direction, now i
got sysfs and udev again.
> You cannot rely on that message. It just assumes A2000/A500/A600 etc.
> have an A2000-style clock chip. But on all but A2000 the RTC is optional.
> BTW, I also asked Jens Schönfeld.
>
After activating CONFIG_RTC_CLASS and CONFIG_RTC_DRV_MSM6242 in the
kernel and finally being able to get the device nodes created
automatically by udev, the RTC now works... somewhat. 8 out of 10 reads
from the RTC (via hctosys inside the kernel at startup, hwclock from
userspace or cat one of the special files inside /sys/class/rtc) return
successfully, but the other 2 return an ioctl()-error. I forgot which
exactly, i'll go upstairs to the Amiga later and write it down.
The PCMCIA-network still doesn't work, i'll recompile the kernel with
CONFIG_APNE=y (instead of m), maybe that will work.
Regards,
Patrick
next prev parent reply other threads:[~2012-01-25 19:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 18:37 Linux on Amiga A600, a success story (in progress, with possible patch) Patrick Bottelberger
2012-01-23 20:42 ` Geert Uytterhoeven
2012-01-23 23:04 ` Michael Schmitz
2012-01-24 8:41 ` Geert Uytterhoeven
2012-01-24 17:56 ` Patrick Bottelberger
2012-01-24 21:19 ` Geert Uytterhoeven
2012-01-27 17:44 ` Thorsten Glaser
2012-01-28 20:24 ` Michael Schmitz
2012-01-28 20:43 ` Thorsten Glaser
2012-01-28 20:49 ` Geert Uytterhoeven
2012-01-28 21:01 ` Thorsten Glaser
2012-01-24 17:35 ` Patrick Bottelberger
2012-01-24 21:17 ` Geert Uytterhoeven
2012-01-24 21:49 ` Geert Uytterhoeven
2012-01-25 19:11 ` Patrick Bottelberger [this message]
2012-01-26 17:05 ` Patrick Bottelberger
2012-02-07 19:55 ` Patrick Bottelberger
2012-02-07 22:13 ` Thorsten Glaser
2012-02-20 21:38 ` Patrick Bottelberger
2012-02-20 22:09 ` Andreas Schwab
2012-02-20 22:47 ` Patrick Bottelberger
2012-02-20 23:02 ` Andreas Schwab
2012-02-21 10:55 ` Patrick Bottelberger
2012-01-29 21:59 ` Geert Uytterhoeven
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=4F2053C9.3090201@sigon.net \
--to=patrick.bottelberger@sigon.net \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.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.