From: robk@robpc4.robk-home.org   
      
   noel  wrote:   
   > On Tue, 03 Aug 2021 11:25:10 -0400, Robert Komar wrote:   
   >   
   >> Ralph Spitzner  wrote:   
   >>> noel wrote on 8/2/21 4:36 PM:   
   >>> [...]   
   >>>> as for not scrolling back, you have that dumbfuck so called genius   
   >>>> torvalds to thank for that. had a boot issue once on a pentium, if I   
   >>>> had scrol back I'd see the obvious error and correct it, but no   
   >>>> scrollback   
   >>>   
   >>> [...]   
   >>> I imagine it's a bit hard to do screen scrolling when the keyboard and   
   >>> video drivers (and all others) are dead/ haltet.   
   >>> would you prefer a windows like:   
   >>> KERNEL PANIC ERROR #DEADBEEF ?   
   >>>   
   >>>     -rasp   
   >>   
   >> I think most of us would prefer the scrolling that was there for almost   
   >> thirty years.  It wasn't perfect, but it was better than nothing.   
   >>   
   >> Back to the original topic, I have slackware-current running in a VM as   
   >> well.  The root filesystem is not ext2, so I can boot without the   
   >> initrd.  In there, I can create an ext2 filesystem in a file, mount   
   >> that, write to it, read from it,...  So, it looks like ext2 works fine   
   >> in that system.  Perhaps my problem on the netbook is really with the   
   >> initrd as I first thought, and the OP has something broken in his   
   >> system.  I can't duplicate his ext2 problems within the VM.   
   >>   
   >> Rob Komar   
   >   
   > current kernels dont like ext2, plain and simple   
   >   
   > I pulled an ol toshiba usb drive out from storage since I knew it was   
   > ext2, nope, stack errors and killed at every first attempt...   
   >   
   > converted it to ext4,   
   >   
   >  tune2fs -O extents,uninit_bg,dir_index,has_journal /dev/sdf1   
   >   
   > and voila! no errors, so its just ext2 theyve rooted up   
   >   
   > way to go linus...   
   >   
   > (im not gonna sift through 10K trolls on LKML to see if its been brought   
   > up there yet.)   
   >   
   > (I didnt see mr spitzers post, I didnt miss anything, my troll filters   
   > seem to be working well)   
      
   Thanks for the tune2fs tip.  It was a bit more work for me, though, so   
   I thought I'd give an update here in case it helps anyone.   
      
   Besides modifying the root filesystem with tune2fs (but with   
   ^has_journal to disable journaling), I modified /etc/fstab to change the   
   root file system type from ext2 to ext4.  I also added the "noatime"   
   option to reduce writing on the SD card.  I had to modify my mkinitrd   
   script to remove the "-f ext2" option I was using.  I also had to modify   
   the /etc/lilo.conf file and add "rootfstype=ext4" to the "append"   
   parameter and re-run lilo.  Without the last change, the root filesystem   
   would only be attempted to be mounted as ext2 and would fail because of   
   unrecognized options.  Perhaps autodetection of the filesystem type is   
   not working properly at that stage, because adding "rootfstype=ext4" to   
   the kernel boot options seems like it shouldn't be necessary.   
      
   The mkinitrd stuff was problematic because it needed the system to be   
   booted to run.  I had to make that change to the script and rebuild the   
   initrd images before starting to make changes to the root filesystem.   
   Fortunately I could re-run lilo on the SD card from my desktop, so I was   
   able to fix that even when the system would not boot.   
      
   Cheers,   
   Rob Komar   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)