When you start the machine, hit TAB when the menu comes up and you'll be able to add whichever ones you want to the cmdline. You could also add them to the /boot/syslinux/porteus.cfg file on the APPEND line.....but I find it easier to just do it boot time.
Installing Porteus onto a flashdrive from Arch results with /dev/media [SOLVED]
-
- Full of knowledge
- Posts: 400
- Joined: 02 Jan 2011, 18:41
- Distribution: Porteus 5.0-RC1
- Location: In a hayfield
Installing Porteus onto a flashdrive from Arch results with /dev/media [SOLVED]
- eggbladder
- Black ninja
- Posts: 36
- Joined: 20 Nov 2023, 22:50
- Distribution: Arch Linux
- Location: Tonga
Installing Porteus onto a flashdrive from Arch results with /dev/media [SOLVED]
Ah, those, okay. Do i try them all at once, or individually?
-
- Full of knowledge
- Posts: 400
- Joined: 02 Jan 2011, 18:41
- Distribution: Porteus 5.0-RC1
- Location: In a hayfield
Installing Porteus onto a flashdrive from Arch results with /dev/media [SOLVED]
@eggbladder,
No, not all at the same time, there would be conflicts. I would try one at a time and see if they make a difference. Check all the logs in /var/log/.
No, not all at the same time, there would be conflicts. I would try one at a time and see if they make a difference. Check all the logs in /var/log/.
- eggbladder
- Black ninja
- Posts: 36
- Joined: 20 Nov 2023, 22:50
- Distribution: Arch Linux
- Location: Tonga
Installing Porteus onto a flashdrive from Arch results with /dev/media [SOLVED]
I will do (up to) 3 tests for each command. I will see how much they help, if at all.
test with amdgpu.modeset=1 - failed (booted up but screen ended up freezing and no longer working)
test with amdgpu.dpm=1 - failed (same as above)
test with amdgpu.dc=1 - failed (same as above)
test with amdgpu.dc=0 - failed (same as above)
test with amdgpu.cik_support=1 - failed (same as above)
test with amdgpu.si_support=1 - passed (never crashed + showed symptoms of not going to crash any time soon)
test 2 with amdgpu.si_support=1 - failed (same as above)
test with radeon.cik_support=0 - failed (same as above)
test with radeon.si_support=0 - failed (same as above)
an indicator on whether or not porteus will crash is usually when booting to ram. if, before it starts up, Xorg changes the terminal display accordingly, it wont crash (the resolution gets larger)
it will always crash when the resolution does not get smaller and stays really big.
I have an idea of getting my Debian live USB and seeing what GRUB boot settings it has, and seeing if they work on Porteus.
test with amdgpu.modeset=1 - failed (booted up but screen ended up freezing and no longer working)
test with amdgpu.dpm=1 - failed (same as above)
test with amdgpu.dc=1 - failed (same as above)
test with amdgpu.dc=0 - failed (same as above)
test with amdgpu.cik_support=1 - failed (same as above)
test with amdgpu.si_support=1 - passed (never crashed + showed symptoms of not going to crash any time soon)
test 2 with amdgpu.si_support=1 - failed (same as above)
test with radeon.cik_support=0 - failed (same as above)
test with radeon.si_support=0 - failed (same as above)
an indicator on whether or not porteus will crash is usually when booting to ram. if, before it starts up, Xorg changes the terminal display accordingly, it wont crash (the resolution gets larger)
it will always crash when the resolution does not get smaller and stays really big.
I have an idea of getting my Debian live USB and seeing what GRUB boot settings it has, and seeing if they work on Porteus.
- eggbladder
- Black ninja
- Posts: 36
- Joined: 20 Nov 2023, 22:50
- Distribution: Arch Linux
- Location: Tonga
Installing Porteus onto a flashdrive from Arch results with /dev/media [SOLVED]
searching through debian didnt do much.
do you think i should make a new forum post? this one is 34 posts long and doesnt even display my issue haha
do you think i should make a new forum post? this one is 34 posts long and doesnt even display my issue haha
-
- Full of knowledge
- Posts: 400
- Joined: 02 Jan 2011, 18:41
- Distribution: Porteus 5.0-RC1
- Location: In a hayfield
Installing Porteus onto a flashdrive from Arch results with /dev/media [SOLVED]
It's probably a good idea to start a new thread, especially as this one is marked as solved. But make the focus on lxdm as the login manager as slim is really not supported in Porteus.eggbladder wrote: ↑28 Nov 2023, 01:31searching through debian didnt do much.
do you think i should make a new forum post? this one is 34 posts long and doesnt even display my issue haha
I had the same screen freeze using the amdgpu.modeset=1 parameter, it finally brought up the desktop after 80 seconds. The logs however, showed lxdm doing only 1 retry. That makes me think the problem is possibly with amdgpu and the kernel. It might be worthwhile to try one of the past kernels posted in the Kernel Builder thread.
- eggbladder
- Black ninja
- Posts: 36
- Joined: 20 Nov 2023, 22:50
- Distribution: Arch Linux
- Location: Tonga
Installing Porteus onto a flashdrive from Arch results with /dev/media [SOLVED]
Ill make a new thread soon. I'll try to get porteus amd drivers first, see if that does anything. I went to linux.org and asked there and they said id need drivers for it.