#6 No usable path error when using the script on devuan
Ditutup
dibuka 7 tahun lalu oleh newtodevuan
·
31 komentar
Label
Tidak ada Label
Tonggak
Tidak ada tonggak
Penerima
Tidak ada penerima
3 Peserta
Memuat...
Belum ada konten.
I am trying to use your script. I have installed Devuan in an amd64 machine just to run it, but I am getting an error. This are the last messages before returning.
I have this issue #5 , and I have tried saying Y and N. Both produce the same result at the end and no images. Also, I get no config.log.
Hi,
It looks like you need to install m4
# apt install m4
Issue #5 is unrelated step, the config file does not have CONFIG_ARM_ERRATA_CR711784 entry so it prompts. Both paths Y and N will actually produce images (I tried both because I was unsure).
@creoflux thanks, I'll try with m4 installed. Any reason why it is not in the list of packages to install in the README? Also, there is a '/' missing in the apt install line in the README, after u-boot-tools.
As for issue #5, you probably have not had time to look into it, but any suggestion on what option could be better?
After installing m4, now I get a different error:
The error happens independently from the option I chose from issue #5.
I am not sure, I just started using this script... just pure speculation, but I think depending on what version of Devuan you install perhaps this comes with.
The other issue:
This looks like you are missing patch also
# apt install patch
@creoflux I assumed you were the maintainer, I realize now that is not the case. Thanks for the help. I have installed in an spare HD Devuan 1 (Jessie) on x86_64 as recommended in the README.
After installing patch, I got a new error:
I realized I need to run the script as root so it can find parted.
I have finally finished the script without errors, but it has only created the 2GB image file. No 16GB image file as the README seems to indicate. What could be wrong?
EDIT: After burning the 2GB image in a 4GB usb device using dd as indicated in the README, the image will not boot in the C201. Also, GParted says there is some problem with the created partitions and can not recognize them. I will paste the end of the devsus.sh script output later on.
The fact that it didn't produce the 16GB image is indication of an issue, it appears you have all of the proper dependencies now.
Maybe there are other suggestions from someone that has a more fundamental understanding of the script but my naive approach has been to reboot (cleaning up everything) and try running it again with a fresh git in a new directory.
Either skim through the script output to find the error, or attach it here so we can take a look too.
I re-installed Devuan Jessie again in the amd64 machine and that solved the problems but it is still not working. These are the steps I have taken:
Now both images, the 2GB and the 16GB one, are created. I think the problem was that previously missing m4 and patch would stop the installation of something half way and that would not get solved on re-run. In any case, its working now.
The problem now: I dd the 2GB image into the usb stick and boot the c201 with it. I login as root, go to the folder with the 16Gb image and run 'dd if=devuan-jessie-c201-libre-16GB.img of=/dev/mmcblk0 bs=50M'. It completes but when I reboot and try to run from internal media, devuan does not load and appears a text message prompting me to install a recovery usb.
Also, when I run Gparted after I have dd'ed the 2Gb image in the usb device, I get a warning dialog:
I have to select Ignore. If I select fix, the usb device will not be bootable.
Still, Gparted tells me the small 32Mb partition with the label Kernel is unknown and does not recognize it. The big 1.92Gb partition is now recognized as ext4.
So it seems there is still something wrong with the image.
Whether I select 'y' or 'n' in the issue #5 seems to make no difference at all.
I am going to post the final part of the output in the next comment. If someone else is needed please ask.
That's when you're supposed to press CTRL+D.
Also, try to kick the
bs=50Mwhen youddthe 16 GB image to the SSD.@dimkr Pressing CTRL+D does nothing. I have tried with and without the usb inserted.
By "try to kick the bs=50M when you dd the 16 GB image to the SSD", you mean remove the bs=50M part from the command?
That recovery screen you're talking about - does it appear immediately once you start the machine? Have you enabled developer mode or flashed Libreboot?
Regarding that command-line - try to use
dd if=devuan-jessie-c201-libre-16GB.img of=/dev/mmcblk0instead ofdd if=devuan-jessie-c201-libre-16GB.img of=/dev/mmcblk0 bs=50M.Yes, I have flashed libreboot. Also, Kernels signature verification is disabled and External media boot is enabled, all as per this page: https://libreboot.org/docs/install/c201.html .
When I boot I get the libreboot screen with text:
... (more options, 3 second message, warnings about kernel without signature and external media boot)
If I press Ctrl + D for internal media (or do nothing, its the default) after having dd'ed the image into the ssd, I get the screen prompting me to provide a recovery usb. Before I dd'ed the sdd, I got ChromeOS obviously.
I have just dd'ed without the 'bs=50M' and get the same results as before. After pressind Ctrl+D in the libreboot screen, I get a new text screen, like this:
(in the center of the screen)
Pressing ctrl+d here does nothing.
Boot from USB using the 2GB image and run these:
1) Make sure the SSD is exactly 15762194432 bytes 2) Do you see any errors? 3) Try to mount /dev/mmcblk0p2
fdisk -l says the size of the ssd is exactly that.
I get errors. When I run fdisk -l it says:
After some more output another mistake:
When I run cgpt show /dev/mmcblk0, at the end it says:
Should I try that?
Can all this be connected with the GPT problem in the small partition of the usb after flashing the 2GB image?
You're making a mess. Let's do things step-by-step, without retrying things without understanding why they didn't work in first place or running stuff blindly without understanding what they do.
What device do these errors occur on? Is that the flash drive or the SSD?
When I boot from the usb device using the 2GB image,
the output of 'cgpt show /dev/mmcblk0': https://paste.ubuntu.com/25191085/
and the output of 'fdisk -l': https://paste.ubuntu.com/25191103/
That's weird, it seems the beginning of the disk is corrupt. Do you see any errors in the output of
dmesgwhen you rundd?Which one do you want me to look for, when I dd the usb stick or when I dd the internal memory of the c201?
Both
After dd to the c201 internal memory, dmesg shows this:
Which is similar to what fdisk -l said.
Tomorrow I'll do the other one. You might have missed from previous comments, but after I burn the 2Gb image into the usb stick, if I load gparted it brings up a dialog saying this:
I have to select Ignore. If I select fix, the usb device will not be bootable.
Still, Gparted tells me the small 32Mb partition with the label Kernel is unknown and does not recognize it. The big 1.92Gb partition is now recognized as ext4.
Is it possible there is something wrong with the image? Anyway tomorrow when I wake up Ill do the dmesg of dd of the 2Gb in the usb.
Here is the dmesg output that appears after dd the 2Gb image into the usb device: http://paste.ubuntu.com/25195821/
The image could be faulty but I doubt that. It seems more like that the flash drive is. Do you have another flash drive?
Using a different usb and dd the 2Gb image, this is the dmesg output: http://paste.ubuntu.com/25196072/
Also, same as with previous usb memory stick when loading Gparted.
EDIT: I have tested a third usb and same results. All 3 usb's were working fine previously as far as I could see.
If you copy the image, do you see the same errors in
dmesg? Those errors may indicate there is a problem with at least one of your disks.I have copied (not moved, copied) both the 2Gb and the 16Gb images to another folder. Now I have 2 copies of each in the HD. Dmesg output nothing.
@dimkr so in your opinion the most probable explanation is that there is something wrong with the HDD where Devuan amd64 is installed?
The script is working correctly in your computer?
Yes, it works correctly and the last build (which I use right now on my C201) is several days old. I don't know why things don't work on your machine, but those kernel errors are a very bad sign.
Ok, so I have no idea what could be wrong.
I have a HDD where I have Windows installed and I use it when I need to flash something that needs windows and stuff like that. It has been working without a problem. I installed Devuan amd64 on it, update and upgrade, ... When I dd'ed the usb device same warning in dmesg and same results in the c201.
I though that maybe my computer usb and devuan were not playing nice and that was the problem, so I burned the image as a file in a dvd. I booted into Ubuntu and dd'ed the image. Same warning in dmesg and same results in the cc201.
So at this point I am kind of at a lost at what could be happening. I have tried 3 usb devices that seem to work otherwise, 2 HDD, one which was working recently, and even dd'ing from different operating systems.
Any suggestion welcome. But at this point, if anyone could upload the 2Gb image somewhere in the internet so I can compare it to the one I generate I would be very thankful.