Page 1 of 1
Interesting, but nasty, new problem
Posted: Sat Apr 04, 2015 11:58 pm
by kilaueabart
I'm not sure this isn't specific to X1000, or X1000 Linux Only, but I don't think it should be.
badscreen.jpg
Apparently as a result of "fixing" a reinstallation of Ubuntu 12.04 LTS on my X1000 yesterday, this is how OS4.1FE boots now (SGrab didn't get the whole screen, but enough). If I click "OK" on the one alert and "Retry" on the other, it reverts to the proper resolution with some dockies out of position, and the system seems entirely functional, but I wish I knew how to fix it to come up right in the first place. What"Volume" is it talking about, I wonder.
The fix consisted only of reformatting a CF card as FAT16 and copying a bunch of kernels back into it, using the DVD Ubuntu. I got anxious to see whether that had worked and hit the reset button instead of shutting down from the screen menu as one is supposed to do. I was able to boot linux from disk just fine thereafter, and spent a couple hours playing with it. Then I needed to do something with AmigaOS, with the above result.
Re: Interesting, but nasty, new problem
Posted: Sun Apr 05, 2015 12:45 am
by nbache
Judging from your description of what you have "messed with", it's most likely the CF card no longer being recognized by the cfide.device in AmigaOS. If so, I can't tell you the reason (I would think it should still recognize it, if you really did only what you described).
But to check whether this is indeed the problem, try commenting out the line for cfide.device.kmod in your Kicklayout and reboot (cold). If the problem is gone, that was it.
Best regards,
Niels
Re: Interesting, but nasty, new problem
Posted: Sun Apr 05, 2015 1:28 am
by kilaueabart
I may try that kickstart trick in a while, although I can't imagine what my CF card has to do with Amiga OS, but I was going to report that there is another alert/message that flashes on screen and every time but the first has been covered up by the other two following. The most I can read before it disappears is "Can't find [something]." When I move the other two out of the way, it is gone. I looked in T: but nothing of the sort there.
And I experimented booting my backup OS4.1u6: No problem, the screen comes up as it should! So it's a matter of FE's partition, I guess.
(A few hours later) I tried hiding cfide.device.kmod with the scary result that the red progress line moved about 80% across the page then stopped! How was I going to fix that, if I couldn't get back to Workbench? To my rather astonished relief, I was able to get to FE's Kickstart files from u6 and undid the commenting out.
I am still very puzzled. I used my Amiga for many years before adding Linux and then a CF card. Why does FE now need to find that card? And why doesn't u6? In any event there seems to be nothing wrong with the card, as Linux gets kernel 4.0 from it and boots me right up.
Re: Interesting, but nasty, new problem
Posted: Sun Apr 05, 2015 11:57 am
by tonyw
Stop changing things before you screw it up even more. Stop and think about it first.
FinalEdition has a built-in device driver for the CF card (this device driver was not released previously). Like any device driver, when it starts, it tries to identify the medium (card) inserted in the card holder.
Cfide.device is only a device driver, nothing more. it does not know or care what sort of formatting the card has. On the other hand, diskboot.kmod is the utility that tries to mount all the devices as they are scanned at boot time. Either it (diskboot) or CrossDOSFileSystem has failed to recognise and mount your FAT16 filesystem.
[edited to correct FS name]
You can fix this problem by (as Niels suggested) taking cfide.device out of the Kicklayout (not out of Kickstart). Simply edit the Kicklayout script with Notepad and put a semi-colon (;) in front of the line that says:
"MODULE Kickstart/cfide.device.kmod"
If you do that, the driver won't be loaded or run and you won't be able to access the CF card from the Amiga side. Of course, you will have to boot another Amiga system disk (CD?) to get to that step.
(Off topic)
Why did you use FAT16? Does it have some advantage over FAT32 or is it to be backward-compatible with some other machine?
Re: Interesting, but nasty, new problem
Posted: Mon Apr 06, 2015 4:09 am
by kilaueabart
Aha! I commented out the wrong thing! Thank you. Even at only 79½ I seem to be in severe cognitive decline.
As for why I reformatted to FAT16, I got around to re-reading the install instructions that came with Ubuntu 12.04 LTS. On page 8 one reads,
"GParted will display the current partition on your CF card. Your card will most likely have a
"FAT32 partition by default. You will need to delete this partition and replace it with a
"FAT16 or EXT2 partition. FAT16 is recommended."
I probably should have just been happy with the fact that FAT32 had seemed to work fine for over a year, but maybe it would work even better if I did it right?
I don't think not being able to access the card from OS4 will be a problem, as long as NTSF keeps working.
Re: Interesting, but nasty, new problem
Posted: Mon Apr 06, 2015 6:28 am
by tonyw
Well, I don't grok Linux and at 70½ I'm not going to learn
But leaving cfide.device.kmod commented out should fix your problem in OS4, and you don't have a problem in Linux, right?
Re: Interesting, but nasty, new problem
Posted: Tue Apr 07, 2015 4:22 am
by kilaueabart
tonyw wrote:Well, I don't grok Linux and at 70½ I'm not going to learn
But leaving cfide.device.kmod commented out should fix your problem in OS4, and you don't have a problem in Linux, right?
Yes, I'm all set thanks to you clarifying what Niels meant.
I don't suppose you can fix my Odyssey password problems now?
