xeno74 wrote:
Many thanks for testing! Could you please try the kernel 3.19? Download:
vmlinux-3.19.0-KVM-PR-AMIGA_one_X1000.tar.bz2
For the kernel 3.19 you need Upstart and the
rw boot argument.
Code: Select all
sudo apt-get install upstart-sysv
Code: Select all
setenv bootargs "root=/dev/sdb7 quiet ro splash rw"
Epsilon wrote:
FYI I note that an extra dialog box appears on my install that was not mentioned in the instructions - a prompt saying the kernel wasn't detected or something (?) and that the partition would not boot without it, ok to proceed?
Yes, ok to proceed is correct. Could you tell me when does the extra dialog box appears?
I tried booting into ubuntu mate with 4.2 as it works to a shell at least, so I can install the package you mentioned. When I run the command apt-get as above I got unable to resolve the ports.ubuntu.... thinking about it a bit I remembered that in the installation it asked which network device I wanted to use for the installation. Since AmigaOS 4.1 can't use the onboard NIC I instantly told it to use the PCI realtek one, which is connected to the network. The onboard is not connected because it doesn't work in OS4.1. The initial OS installation worked fine this way.
I then thought about it and assumed that the issue was Ubuntu was automatically choosing the onboard card when running from the hd after the installation, and ignoring what I said during the installation. So I swapped the cable to the other card and the download worked. That is a gotcha for os4.1 people since they never use that NIC onboard!
Anyway, after the package installed, I got some weird warning messages like these:
"dpkg: systemd-sysv: dependency problems, but removing anyway as you requested"
Since it didn't ask me anything and just did it all automatically I didn't have any choice....
My photos are not being accepted to be uploaded to this server so I have uploaded them to flickr instead. Links are here for the messages mentioned here:
IMG_8690 by
Epsilon2012, on Flickr
I change the boot args as you mentioned in CFE, copied the vmlinux-3.19 kernel to the CF card and when selected Linux booted straight (with an odd message about hard disk mounting which I saw previously too) to a terminal login - no X and no CTRL-ALT-F1 needed. I logged in and got a weird message I also never seen before "systemd-logind[2900]: failed to start user service: Unknown unit:
[email protected]"
IMG_8692 by
Epsilon2012, on Flickr
IMG_8691 by
Epsilon2012, on Flickr
I tried running X -configure again, but same result - no devices found.
As a comparison this is what the boot did before when using kernel 4.2 - a lot more information appeared on the screen:
IMG_8678 by
Epsilon2012, on Flickr
No idea. Seems worse now than before - looks broken.
Catcha,
Epsilon