01:00:24 <zedmatrix> sup malina: do you mount move devpts?
01:07:10 <zedmatrix> malina: should talk more in here 
01:09:40 <malina> erm no I dont\ move mount?
01:09:43 <malina> what do you mean?
01:09:50 <malina> like what i the issue you are working on?
01:09:56 <zedmatrix> writing an initramfs
01:09:58 <malina> Iin my init in the begiing i remeber it was like
01:10:08 <malina> a bit awakwartd figuyring out the tmpfs systems
01:10:19 <zedmatrix> ive switched to system-v
01:10:20 <malina> i kinda did a bit just , (and i reocmmend this) just go with it
01:10:26 <malina> solve it until you feel it's "ok even if hacky
01:10:32 <zedmatrix> using the grub-mkrescue
01:10:34 <malina> and before yo know it, the system is just booting fooking amazingly
01:10:46 <malina> sure it won't be popular if you spread it (never was my purpose)
01:10:50 <malina> but for your opwn systems
01:10:54 <malina> my systems worked 100%
01:11:01 <malina> and no worry of 'users moaning'
01:11:07 <zedmatrix> how you like my hacky... https://github.com/zedmatrix/Bash_Scripts/tree/main/Initramfs
01:11:13 <malina> but it neevr went wrong.. but ye.. it kinfda is a fight between init and kernel
01:11:25 <zedmatrix> thats old 
01:11:50 <malina> so when you boot you _create the squashfs_?
01:11:53 <zedmatrix> but getting the init is one thing
01:11:53 <malina> from where?
01:12:07 <zedmatrix> the squashfs is already made
01:12:27 <zedmatrix> its mounting the squash to image.squashfs ramdisk
01:12:39 <malina> ye ok 
01:15:35 <zedmatrix> this is the issue.... https://bpa.st/PMDQ
01:19:48 <zedmatrix> malina: this is the newest version > https://github.com/zedmatrix/Bash_Scripts/blob/main/Initramfs/init.sh
01:23:03 <zedmatrix> nsITobin: maybe initramfs/lib/firmware should be populated
01:24:46 <zedmatrix> cause live booting my laptop just stops at drm amdgpu
01:40:21 <malina> aktghough I dont think it was a success, I tried merging drm from libdrm and nvidias?
01:40:23 <malina> or what iut was
01:40:31 <malina> but ye, dont think it was a success
01:42:58 <zedmatrix> i think i need to populate usr/lib/firmware
01:47:30 <nsITobin> zedmatrix: you loading firmware in the squash or in initrd?
01:53:38 <zedmatrix> going to try the squashfs since after it switches root is where its failing
01:54:26 <nsITobin> zedmatrix: is it wise to have overlay and loop as kernel modules then switchroot?
01:57:16 <zedmatrix> no i built overlay and loop into the kernel
01:57:41 <zedmatrix> i just forgot to add hfs,hfsplus 
01:59:56 <zedmatrix> hmm that increased to 1.8G
02:19:02 <zedmatrix> hmm it booted the hp pavilion laptop
02:22:59 <zedmatrix> nsITobin: it adds 1.6G to the squashfs
02:23:19 <nsITobin> does it solve it?
02:24:08 <nsITobin> zedmatrix: how large is your rootfs before sqashing it?
02:26:03 <nsITobin> and do you really need ALL that firmware?
02:27:32 <zedmatrix> see if you can boot... https://ln5.sync.com/4.0/dl/b6e0c5a40#c7jgvs37-9ndcbtm4-y3bm3baf-9dacvx8f
02:27:47 <zedmatrix> one of my laptops had a nvidiafb stop
02:28:48 <zedmatrix> cause of the size i went with the low memory, non ramdisk 
02:29:29 <zedmatrix> but it does boot from usb now.... qemu+hp pav tested
02:30:36 <nsITobin> sucks you had to include udev
02:31:08 <nsITobin> not entirely sure why I need udev
02:32:36 <zedmatrix> makes it easier to populate the filesystem, other than that it gets messy
02:33:26 <zedmatrix> cause then i would haveto manually create all device nodes 
02:34:32 <zedmatrix> but i might try adding a firmware.img
02:35:38 <nsITobin> zedmatrix: just see about compressing each blob
02:37:03 <nsITobin> fedora xz compresses theirs .. the firmware makefile by default gz compresses it for the dist target
02:37:33 <nsITobin> or no..
02:38:00 <nsITobin> install-xz target in makefile
02:38:02 <nsITobin> tthere we go
02:38:12 <nsITobin> no git required
02:38:22 <nsITobin> that should cut down on the space
02:39:31 <nsITobin> so make install-xz with a dest dir should do the trick
02:40:11 <nsITobin> sometimes individual file compression does better than compressing the whole thing
02:40:21 <zedmatrix> i think haveto do a cpio image with /lib/firmware/* so that is available before the init starts
02:40:50 <nsITobin> which init
02:41:02 <nsITobin> sysv?
02:42:29 <zedmatrix> i bet this is a blob> '/boot/gentoo.igz'
02:42:43 <zedmatrix> no the initramfs/init
02:43:52 <nsITobin> honestly i dunno where firmware needs to be
02:45:19 <zedmatrix> i think it should be passed from grub so that the kernel can load it before that init pass over
02:47:40 <nsITobin> ok initrd does contain firmware but typically not all of it
02:48:04 <nsITobin> unless i am wrong
02:48:24 <nsITobin> no i think you prettyy much need firmware in both initrd and the final rootfs
02:49:13 <nsITobin> fedora livecds seem to include it in both
02:49:30 <nsITobin> and yeah a loop likely won't work
02:54:47 <zedmatrix> hmm xz gets it to 539M, i guess if i trim out some blobs
02:58:14 <zedmatrix> whats funny is on the hp laptop the ethernet was eno1
03:02:58 <nsITobin> there is also zstd but zstd pisses me off.. like they are the standard for everything Z.. I am sure you have something to say about it zedmatrix 
03:04:21 <zedmatrix> did you see i changed the timeout to 30 ?
03:04:43 <nsITobin> i haven't tried to boot hardware yet but i will boot vmware.. i was poking the files
03:05:24 <nsITobin> zedmatrix: then i will send it to the you ess bee
03:05:28 <nsITobin> k?
03:06:32 <nsITobin> good in the vmware
03:06:58 <zedmatrix> yea qemu too
03:07:38 <zedmatrix> down to 1693577216 Jun 11 20:06 lfslive.iso
03:07:41 <nsITobin> how much ram you got in your normal com-Puter
03:07:42 <zedmatrix> 1.6G
03:08:15 <zedmatrix> my qemu i use 4G 
03:08:28 <zedmatrix> the Hp has 8G
03:08:41 <nsITobin> still dunno why it maps to hfs+
03:09:00 <nsITobin> is that the file format when you create the loop device?
03:09:06 <nsITobin> filesystem*
03:09:15 <zedmatrix> its how grub-mkrescue/xorriso is creating
03:09:20 <zedmatrix> its how grub-mkrescue/xorriso is creating
03:09:22 <zedmatrix> its how grub-mkrescue/xorriso is creating
03:09:26 <nsITobin> you said that
03:09:28 <nsITobin> sorry i am tired
03:09:43 <zedmatrix> no worry
03:09:44 <nsITobin> i have been up for .. hours
03:09:49 <zedmatrix> me too 
03:09:55 <nsITobin> 0530 it is 2209 now
03:10:10 <zedmatrix> 630 am and 810p
03:10:54 <zedmatrix> ok burning the new image 1.6gb to usb using the firmware.img
03:11:26 <nsITobin> be back
03:11:38 <zedmatrix> i wonder if i am gonna burn out this usb 
03:30:26 <nsITobin> yeah it worked
03:31:57 <nsITobin> and then when i rebooted i found the god damned firmware screwed up my graphics card monitor detection.. my fourth monitor uses a dvi on the monitor side to dp.. changes in firmware fuck it up requiring me to go into Windows and get it to detect again then it is happy.. it is one of those quirks that seems to ONLY happen to me and is why I am so damned particular about my software.. 
03:32:43 <nsITobin> anyway that is what took me so long
03:33:51 <nsITobin> also because of that issue my fourth monitor became 640x480 which means ALL my monitors were 640x480 but because of the stupid framebuffer bs it was only zoomed on the incorrectly detected monitor and tiny corner only on everything else
03:34:02 <nsITobin> which is why for my PERSONAL use i build amdgpu in
03:34:14 <nsITobin> and control it with kernel args
03:34:32 <nsITobin> but again tthat is specific to me
03:34:41 <nsITobin> nothing YOU did was an issue
03:35:03 <nsITobin> just.. the state of things
03:36:31 <zedmatrix> i am having trouble booting in qemu with the firmware blob, ok kernel panic now, it just took time to decompress the blob
03:38:11 <nsITobin> assuming i go to the store tomorrow after that I will see about creating something bootable of my own
03:38:27 <nsITobin> but i think i am several steps behind you still
03:39:01 <zedmatrix> something with that firmware.img blob, maybe i can strip it down to just intel/ amd/ nvidia/ ?
03:39:18 <nsITobin> i don't think it will work
03:42:06 <zedmatrix> ok decompressing blob
03:43:10 <zedmatrix> booted initrd /initrd.img /firmware.img
03:43:45 <zedmatrix> it activated the gtk window
03:50:47 <zedmatrix> still goes to userspace, then 2 nvidiafb crtc0,1
04:08:44 <nsITobin> gonna lay down now good night
04:41:23 <zedmatrix> building a live iso takes alot of tweaking
20:10:12 <nsITobin> you know zedmatrix .. i am gonna just stop spilling my plans out to the world cause every time i do something happens to interfear
20:10:33 <nsITobin> figured go to the store be gone a few hours then back but it was a whole ordeal
20:10:34 <nsITobin> lol
20:10:50 <nsITobin> i can only figure it is because I deemed my intended actions..
20:11:11 <nsITobin> so i figure maybe if I don't say then the universe won't overhear LOL
20:11:57 <nsITobin> Catch the universe off gaurd.. That's the ticket!
20:12:03 <nsITobin> in all seriousness sup
20:24:56 <zedmatrix> nsITobin: rebuilding some linux, using 6.6.93 lts and gonna try trimming the firmware blob too
20:25:31 <zedmatrix> just squashing the new modules
20:27:03 <nsITobin> zedmatrix: god i wish the kernel could loop mount a wim image it would basically complete wimlib-imagex's full equivalance of the windows version.. 
20:27:11 <nsITobin> fuse is too small
20:27:30 <nsITobin> but if i could get a wim support in the kernel.. well that could be fun..
20:27:39 <nsITobin> small.. i mean slow
20:28:07 <zedmatrix> but if you try that iso again add 'nomodeset' to the grub commandline
20:28:27 <nsITobin> yeah I am gonna have to do nomodeset to not have it piss with my gfx card
20:28:40 <zedmatrix> its probably the nvidiafb causing issues
20:28:50 <nsITobin> i use amdgpu
20:29:08 <nsITobin> but every time it changes it makes my shitty dvi to dp cable not detect
20:29:26 <nsITobin> thus fucking up my hardset monitor stuff on kernel cmdline and in x11
20:30:03 <nsITobin> because the entire system is stupid and won't let me at cmdline set the damned monitor resolutions properly .. or just disable some or not
20:31:58 <nsITobin> https://dpaste.org/DU6oH/raw
20:32:10 <nsITobin> this is what I have to do to make my monitors work properly
20:34:21 <nsITobin> because smallest resolution wins
20:34:28 <nsITobin> and it doesn't stretch
20:34:40 <nsITobin> so it double sucks
20:44:10 <zedmatrix> yea thats y linux from scratch is easier :)
21:15:17 <zedmatrix> nsITobin:  if you want to try the new iso ... https://ln5.sync.com/4.0/dl/eaf0754e0#c8rnp7gj-3bkifx8f-dt83yk6h-bj67hhx9
21:19:53 <nsITobin> why 6.6?
21:24:48 <nsITobin> zedmatrix: shutting down falls to system matainace shell
21:24:55 <nsITobin> when doing shutdown now
21:25:23 <nsITobin> stopping system log daemon
21:25:32 <nsITobin> enter root password for system maintanance
21:25:54 <nsITobin> if i ctrl+d it logs back in as root
21:25:59 <nsITobin> but sysvinit is shutdown
23:23:06 <nsITobin> zedmatrix: but i know reboot worked on hardware
23:23:09 <nsITobin> so i dunno
23:23:13 <nsITobin> why the why
23:43:08 <zedmatrix> hmm i just did a quick test in vm it looked ok
23:43:45 <nsITobin> just type shutdown now
23:43:54 <nsITobin> it falls to emerg shell
23:44:17 <nsITobin> i will write it to a flash drive
23:44:22 <nsITobin> after this vidya
23:50:41 <zedmatrix> hmm i never use shutdow
23:51:00 <zedmatrix> its usually, poweroff or reboot :)
23:56:54 <nsITobin> how do i restart linux?
23:56:59 <nsITobin> all i can find is reboot
23:57:03 <nsITobin> but i need to restart it
23:57:25 <nsITobin> a related question.. i need to know if i should logoff or logout first
23:57:27 <nsITobin> zedmatrix: 
23:58:15 <nsITobin> i do know i hate "signin signout/off
23:58:16 <nsITobin> "
23:58:45 <nsITobin> because that implies asking permission.. while logging in or on.. implies I am allowed .. also logged as such.
23:59:18 <nsITobin> language shifts thought and expression and i do NOT like the progression from login to sign in