Open dilyn-corner opened 3 years ago
Well, the thing is that i can't test the UEFI on real hardware and in qemu
you need some tricky bios files due to boot into UEFI, i do the UEFI things copying what other distros do.
So thanks to report, that UEFI doesn't work at all. I'm blind in that sense.
But this isn't the first experience with kiss grub
and images that don't boot. I tried the kiss-bootstrap script, and if you run inside a KISSLINUX machine the image result don't boots also.
With bios boots "well", under qemu
and real hardware.
I will see what to do with the file
issue, but I assume that is installed because is a util-linux
depends, and that is a syslinux
depends also. I will work on that.
I will add the tarball option, i might think how (well i need to do a kiss-export <pkg>
inside only).
But I want to ask you a question, have you booted well the kiss-kde-live? I mean, mine boots, i see kde splash after login, the wallpaper + cursor, aaaaand that's all, I can't move the cursor, keyboard don't respond, I didn't know if it's freezed or it's working without input devices.
I don't have qemu setup and I'm not terribly interested in learning how to do so but I'd be more than happy to try!
The best way to troublshoot input issues would probably involve launching top
when X starts to see what processes are running and if it's frozen or your input is broken. It could be anything from input devices not being setup by xorg or an issue with plasmashell (I have similar bugs when updating qt5; it seems that qt5 only sometimes links to dbus when an update is made? I'm unsure, and it's a problem I'm exploring. Unfortunately rebuilding qt5 until it works isn't a good solution haha).
file
wouldn't seem to be a util-linux
dep (as I have one installed and not the other).
I'll explore the UEFI requirements further and see what I can find!
So I mounted the iso to a loopback device and... It's empty? There's nothing there. But it's 252MB in size, so there's something in it...
I'm dumb, file
isn't a dep of util-linux
.
I tried to launch some apps when I start X, like konsole
or dolphin
but nothing happens on my laptop, only wallpaper + cursor.
The iso file is empty? No 'boot' or 'pkgs' dir inside? That's weird.
Unsure what bizarre mistakes were made on my end but after fixing up my kernel and rebooting, the ISO looks like it contains most of the right stuff (comparing to Arch's ISO)... ~I'll have to continue looking at why I can't boot it.~ Was attempting another method of making a UEFI-bootable USB live device and wouldn't you know it, cfdisk
tells me the stick has a DOS label. Who gave them the right to manipulate my parition tables like that smh.
As for your issues, there could be a few reasons... Most of them lost to the sands of time (I haven't had a full freeze like that since the first time I tried to launch KDE).
I will work on getting qemu setup on my machine today and test there to see what's up.
Launched qemu through the run-qemu
script; encountered a black screen with an x in the center. My best guess, plasma-shell is crashing.
I have to manually load linux because the linux.mod is in /boot/grub/linux.mod Not /boot/grub/x86_64-efi/linux.mod
I have a uefi PC, can test and probably fix stuff
@ucodelukas that screenshot is from the kde
branch?
that is the iso you provide in Releases
That issue is opened about the 'kde branch'. Thanks for the report, but this isn't related to this issue.
is firmware and a properly configured kernel there? if not, we are working on one
can someone post the recent kde iso? i will try to find out why
also, efi works, some tests go on tho
@dilyn-corner I made some changes, and now the livecd it's EFI-bootable (tested on real hardware), and made some changes to work with your tarball. I guess that would be sufficient. I'm testing now.
Sorry I've been AWOL, other projects caught my eye and I've been tearing my hair out solving the problems that arose. I'll give your new work a test this week and report back. Y'all are great <3
Testing the kde branch šš»
Command executed was
sudo ./kiss-live -d -k
. Seemed to run successfully, I have a built ISO image (and the sha1sum matches). Looking over everything that goes into the creation of this ISO, I should be able to use it on a UEFI system, yes? The usual ways I would go about making a UEFI bootable usb (cat kiss-live-2020.9-2.iso /dev/sda
ordd
) do not render a bootable USB device; my list of options is blank (this method works fine with an Arch ISO, for comparison). Have you had success usingkiss-live
with a UEFI system? I have no experience creating ISOs, so I'm not sure where to check on this problem.Another issue (here) was resolved by installing
file
on the host. I'd add a check for this when you also check for the other required packages (or find a different way to set $kernver; could justcat repo/linux/version
if you don't need all the information given byfile
).Outside of that, there isn't a whole lot else I see as being wrong with the kde work you've incorporated here. A few recommendations would be to use the
kiss-kde
tarball I provide so users don't have to build the entire kde_pkgs list every time they want an ISO; I might have missed the option (you could probably do this through build.cfg?) but using a local tarball instead of starting from scratch would be great in case of failures or incremental updates to the image.