[HELP] [BUG] Unable to install deepin 20 beta from bootable usb
Tofloor
poster avatar
amaan75
deepin
2020-04-27 07:44
Author
Edited by amaan75 at 2020-5-4 13:33

Unable to install deepin 20 on my pc
PC config: core -7 9700K Not overclocked yet
TRIDENTZ ROYAL-16GB ddr4 3200mhz
rtx2070 super inno 3d
gigabyte z390 aorus pro wifi rev 1.1
2 m.2 ssds
OSes: WINDOWS, UBUNTU and now wanna switch to deepin and stop ubuntu, if this v20 works out
error update:
  1. 1739869 nouvcau 0000:01:00.0: DRM: failed to create kernel channel, -22
  2. 9670328 ITCO_udt 1 TO_date: can't request region for resource (mem Ox00c5fffc-0x00c5ffff] [ A start job is running for Journal Service (in 24 in 25s)
  3. 984227511 pcieport 0000:00:1b.0: AER:
  4. 984227271 pcieport 0000:00:1b.0: AER: PCle Bus Error: severity=Corrected, type=Physical Layer, Receiver ID) device (8086:a3401 error status/nask=18000601_00082008 JA start job is running for Journal Service (1 min 35 / Min 35s) FAILED) Failed to start Journal Service.
  5. See 'systenctl status systemd-journald.service for details.
  6. DEPEND) Dependency failed for Flush Journal to Persistent Storage.
  7. 9 1 Stopped Journal Service.
  8. Starting Journal Service...1739869 nouvcau 0000:01:00.0: DRM: failed to create kernel channel, -22
  9. 9670328 ITCO_udt 1 TO_date: can't request region for resource (mem Ox00c5fffc-0x00c5ffff] [ A start job is running for Journal Service (in 24 in 25s)
  10. 984227511 pcieport 0000:00:1b.0: AER:
  11. 984227271 pcieport 0000:00:1b.0: AER: PCle Bus Error: severity=Corrected, type=Physical Layer, Receiver ID) device (8086:a3401 error status/nask=18000601_00082008 JA start job is running for Journal Service (1 min 35 / Min 35s) FAILED) Failed to start Journal Service.
  12. See 'systenctl status systemd-journald.service for details.
  13. DEPEND) Dependency failed for Flush Journal to Persistent Storage.
  14. 9 1 Stopped Journal Service.
  15. Starting Journal Service...
Copy the Code




Reply Favorite View the author
All Replies
187******12
deepin
2020-04-27 07:52
#1
did you check md5sum of your iso?
Reply View the author
amaan75
deepin
2020-04-27 09:32
#2
https://bbs.deepin.org/post/193038
did you check md5sum of your iso?

yes sir it was valid
Reply View the author
amaan75
deepin
2020-04-27 09:34
#3
Edited by amaan75 at 2020-4-27 01:46

MD5 WAS A PASS, HERES ANOTHER CLEAR PIC OF THE PROBLEM I THINK ;-;
https://slack-files.com/T1JDD1QH4-F012C4LKAKG-df726ba074
Reply View the author
ghostry
deepin
2020-04-27 14:49
#4
I guess it is because of rtx2070
Reply View the author
amaan75
deepin
2020-04-27 20:25
#5
https://bbs.deepin.org/post/193038
I guess it is because of rtx2070

what do i do to get it to work?
Reply View the author
187******12
deepin
2020-05-03 05:33
#6
did you try to boot without the graphical card?
Reply View the author
amaan75
deepin
2020-05-03 06:14
#7
https://bbs.deepin.org/post/193038
did you try to boot without the graphical card?

i dont want to go through the trouble of taking out the graphics card, then boot, i can already run ubuntu with the card, i was just really bored of the ubuntu UI and wanted to switch to deepin.
Besides, i dual boot windows for gaming, so taking out the gfx card is not a solution, i dont mind  if the drivers on deepin are old or if i can't get the full performance out of my card on deepin but i can't just run the system without it.
Reply View the author
amaan75
deepin
2020-05-03 06:24
#8
it will be great, if somebody could guide me on how to get logs  on what went wrong during the bootphase, the way things stand right now, i can barely read anything on that screen
is there a location on the usb drive where deepin stores logs in case the boot fails or something?
Reply View the author
wtz
deepin
2020-05-03 17:40
#9
Which ISO did you use to boot?

deepin-20Beta-desktop-amd64.iso
deepin-live-system-2.0-amd64.iso

The first one is for installation only (although you can tweak GRUB param to make it LIVE), and the second one is a real LIVE system for rescue, etc.
Reply View the author
amaan75
deepin
2020-05-03 22:11
#10
https://bbs.deepin.org/post/193038
Which ISO did you use to boot?

deepin-20Beta-desktop-amd64.iso

stupid me, i didn't know, there were 2 different things here and live usb meant something else entirely.
Let me re-iterate over what i was trying to do and what i did in wanting to achieve it. I downloaded  Deepin boot maker and deepin beta 20 ISO, the one used for installing it.
post which, i created a bootable usb(which i thought was called a live usb also(super sorry for giving everyone the wrong idea).)
I then tried to boot from the usb and then install it.
After that i waited for quite some time and but the PC was still stuck at the deepin boot logo, i figured something was amiss and pressed some keys (ctrl+alt+del) or (cntrl+alt+f2,f3) or something. i saw the pc going crazy and printing logs about journal service and what not  and some plymounte something( none of these made sense to me) so i took a photo of it and posted it here.
Also note that with the same usb i was able to install deepin on my super old laptop, which has a 3rg gen core i7 a GT650M(2Gb) and 8gbs ddr3(1333MHz) ram.
Reply View the author
wtz
deepin
2020-05-04 03:40
#11
https://bbs.deepin.org/post/193038
stupid me, i didn't know, there were 2 different things here and live usb meant something else enti ...

It seems the kernel lacks some drivers (or they did not work properly).

Try to boot with basic hardware support by modifying GRUB parameters:
1. At system boot screen, press E;
2. Move the cursor to the line beginning with "linux";
3. Append the following parameters to that line:
  1. noapic noapm nodma nomce nolapic nomodeset nosmp nosplash
Copy the Code

4. Press Ctrl-X to boot.

These parameters used to appear in the older version of Deepin Live ISO (Deepin Failsafe), but got removed in v20 Beta.
Reply View the author
amaan75
deepin
2020-05-04 09:20
#12
https://bbs.deepin.org/post/193038
It seems the kernel lacks some drivers (or they did not work properly).

Try to boot with basic ha ...

hey wtz
https://photos.app.goo.gl/35AMd3gJdFs5X1Sg7
(screenshots here^)
i tried what you said
added the params at the end and this is what happened
Reply View the author
wtz
deepin
2020-05-04 16:07
#13
https://bbs.deepin.org/post/193038
hey wtz
https://photos.app.goo.gl/35AMd3gJdFs5X1Sg7
(screenshots here^)

Thanks for the update, but I have no access to Google Photos. Would you please describe briefly what was shown on the screen? Were those messages the same as before (i.e. without additional params)?
Alternatively, you may try to plug the USB disk into different USB slots and boot again, as some USB 3.0 slots do not work well while booting (this is a quite old issue; I'm not sure if it still exists in v20, but I would suggest to verify it).
Reply View the author
amaan75
deepin
2020-05-04 21:31
#14
https://bbs.deepin.org/post/193038
Thanks for the update, but I have no access to Google Photos. Would you please describe briefly wh ...
  1. 1739869 nouvcau 0000:01:00.0: DRM: failed to create kernel channel, -22
  2. 9670328 ITCO_udt 1 TO_date: can't request region for resource (mem Ox00c5fffc-0x00c5ffff] [ A start job is running for Journal Service (in 24 in 25s)
  3. 984227511 pcieport 0000:00:1b.0: AER:
  4. 984227271 pcieport 0000:00:1b.0: AER: PCle Bus Error: severity=Corrected, type=Physical Layer, Receiver ID) device (8086:a3401 error status/nask=18000601_00082008 JA start job is running for Journal Service (1 min 35 / Min 35s) FAILED) Failed to start Journal Service.
  5. See 'systenctl status systemd-journald.service for details.
  6. DEPEND) Dependency failed for Flush Journal to Persistent Storage.
  7. 9 1 Stopped Journal Service.
  8. Starting Journal Service...1739869 nouvcau 0000:01:00.0: DRM: failed to create kernel channel, -22
  9. 9670328 ITCO_udt 1 TO_date: can't request region for resource (mem Ox00c5fffc-0x00c5ffff] [ A start job is running for Journal Service (in 24 in 25s)
  10. 984227511 pcieport 0000:00:1b.0: AER:
  11. 984227271 pcieport 0000:00:1b.0: AER: PCle Bus Error: severity=Corrected, type=Physical Layer, Receiver ID) device (8086:a3401 error status/nask=18000601_00082008 JA start job is running for Journal Service (1 min 35 / Min 35s) FAILED) Failed to start Journal Service.
  12. See 'systenctl status systemd-journald.service for details.
  13. DEPEND) Dependency failed for Flush Journal to Persistent Storage.
  14. 9 1 Stopped Journal Service.
  15. Starting Journal Service...
Copy the Code


i ran the photo through google lens and took out the text(WOW! this thing is like magic) but anywho this is exactly what showed up and this time it didn't go crazy although the messages were probably similar and i do think this probably has something to do with the gfx card
Reply View the author
wtz
deepin
2020-05-04 22:19
#15
https://bbs.deepin.org/post/193038
i ran the photo through google lens and took out the text(WOW! this thing is like magic) but any ...

I think you are right. The kernel used for Ubuntu installation was tweaked for a better support of hardware.
As a workaround, you may try to boot Deepin with kernels from Ubuntu (a little bit complicated though):
1. Boot from Deepin installation disk;
2. At system selection menu, press C, a command line will show up;
3. Try to locate the boot directory of Ubuntu. For example, you may type:
ls (hd0,1)/boot/
this will possibly show the files under the "boot" directory of the first partition on your disk. If this does not work, replace "hd0,1" with other numbers, saying "hd0,2", "hd1,3", etc. and try again.
4. Once found, you will see a list of available kernels, named "vmlinuz-XXX". Choose one and remember its name;
5. Choose the ramdisk file (named "initrd.XXX") corresponding to the kernel that you choose, and remember its name. For example, if you choose "vmlinuz-4.16.0-1-amd64" in the previous step, you should also choose "initrd.img-4.16.0-1-amd64" here;
6. Press Esc, back to the system selection menu;
7. Press E, enter the menu editor.
8. Replace "/live/vmlinuz.efi" by the path of the kernel that you choose, and "/live/initrd.lz" by the path of the ramdisk file.
Note: their path should be a complete path, i.e. something like "(hd0,1)/boot/vmlinuz-4.16.0-1-amd64", where "(hd0,1)" is the partition of Ubuntu that you've just found.
9. Press Ctrl+X to boot.
Reply View the author
amaan75
deepin
2020-05-07 22:32
#16
https://bbs.deepin.org/post/193038
I think you are right. The kernel used for Ubuntu installation was tweaked for a better support of ...

sounds like too much trouble , i settled down for ubuntu dde
Thanks anyway much appreciated
Reply View the author
o***[email protected]
deepin
2020-05-08 02:37
#17
please,
try to customize your patition and make it logic not primary.
Reply View the author
mahuan
deepin
2020-05-08 06:03
#18
问题貌似相同,看楼主怎么解决的!我的显卡2060.主板也是技嘉z390ultra
Reply View the author
amaan75
deepin
2020-05-09 21:48
#19
https://bbs.deepin.org/post/193038
问题貌似相同,看楼主怎么解决的!我的显卡2060.主板也是技嘉z390ultra

how did you solve it?
Reply View the author
mahuan
deepin
2020-05-09 21:58
#20
我的可以进去桌面。只是开机和关机都显示这个代码!其他好像都正常的!难不成是技嘉主板的问题?我的bios版本是f10b!装的闭源440.82驱动
Reply View the author