kata has quit [Read error: Connection reset by peer]
op_4 has quit [Remote host closed the connection]
op_4 has joined #kisslinux
fturco has joined #kisslinux
fturco has quit [Ping timeout: 248 seconds]
_whitelogger has joined #kisslinux
zlg has quit [Ping timeout: 252 seconds]
fultilt has quit [Quit: Leaving]
_whitelogger has joined #kisslinux
worf1337 has quit [Ping timeout: 244 seconds]
worf1338 has joined #kisslinux
drmcstsr has joined #kisslinux
<drmcstsr>
Hello everyone! I've finally got some time to proceed with installing kiss and currently i'm stuck on choosing firmware. Is there's script or a well-written list that can help me with this task? I do know what hardware is inside my pc but failing to include some of the needed hardware and then having to rebuild the kernel looks a little bit too time-consuming to me.
<riteo>
drmcstsr: I think that `dmesg` should complain about each firmware file
<riteo>
also check out the gentoo wiki
drmcstsr has quit [Remote host closed the connection]
phinxy has quit [Quit: WeeChat 4.5.1]
phinxy has joined #kisslinux
<sad_plan>
riteo: correct. you can actually run it in init script aswell, and redirect it to some file
<sad_plan>
this way, you can even debug if screen is black
fultilt has joined #kisslinux
drmcstsr has joined #kisslinux
drmcstsr has quit [Remote host closed the connection]
drmcstsr has joined #kisslinux
drmcstsr has quit [Remote host closed the connection]
chungstoin has joined #kisslinux
<chungstoin>
I can't for the life of me get kiss linux to boot properly
<chungstoin>
it just shows a blank but on screen
<chungstoin>
following the comfy guide perfectly
<chungstoin>
I fixed it before on a previous install by getting it to use tty1, rootwait, etc, but multiple other things displayed errors and so forth, it didn't feel like a complete fix and I couldn't get startx to work as user
<chungstoin>
though any of these issues could have been for different reasons
<chungstoin>
trying to use an efistub btw but I used grub first