Kernel panics

Just finished downloading and trying trisquel mini. Cannot find option to disable mouse clicks with touchpad. After disabling automount, was getting error pop ups on the desktop for every media change but /media/trisquel stayed clean after umounting those universal id's initially placed there on startup. Memory usage seems unchanged between mini and standard edition where I can do screenshots and document stuff with gedit. After resuming from suspend I was getting i/o errors for system commands including man and sudo fdisk -l. Other commands such as lsblk continued to work and showed that /dev/sdb's had, again migrated to /dev/sdc's. This never ever happened on another pc running trisquel live for an uptime already exceeding one year with trisquel 6.0 live! I suspect "Strong ROM" intialization has been corrupted on this Nvidia drive controller that somehow is tightly knit with BIOS. Gateway seems tightlipped about this annoyance. Subsequent attempts to start trisquel lite from usb repeatedly end up with a black screen now with a flashing cursor in the upper left hand corner. Replugging trisquel 6.0 live got me here to follow this up. Also, option to test memory is blocked from the live boot menu.

/dev/sdX (where X is a letter) is not a mount point (that must be a directory). It is a device. It should contain some partition(s) /dev/sdXY (where Y is a number). Such a partition can be mounted wherever you want. For instance, to mount the partition 1 of the disk b on /mnt:
$ sudo mount /dev/sdb1 /mnt

That said, suspension should not create such problems. Are we talking about partitions mounted at init? If so, how are they identified in the first column of /etc/fstab (by UUID, by label or the device node)?

Memtest86+ is not on Trisquel ISOs. That means you cannot test your memory with the Trisquel live system (well, actually, you can by installing "memtester" that does not require a reboot). You can install the "memtest86+" package on Trisquel though.

One thing you could try to mitigate that is edit the suspend scripts to unmount and the resume scripts to mount the devices.

I remember seeing that error message once and editing some text file on the usb stick changing isolinux to syslinux in the path. I believe this might be related to what tool you used to make the usb.

Thank-you again for your valuable time helping me:

Indeed I have a hardware issue: I would like to bypass zram0 [SWAP] which makes up 184.1M of total Swap memory of 983M; where the Disk utility 'sees' only the /dev/sdb6 [SWAP] |-sdb6 of 799M which was wiped using DoD 5220.28-STD (7 passes) and reformatted as a Linux swap.

The vast majority of Kernel panics would occur when I allocated the BIOS default of 64M frame buffer for Nvidia. What I suspect is that the unallocated portion is used as swap space.

To veriy this, I went back from the maximum allowable 128M to 64M frame buffer allocation in the BIOS and saved settings and exited and surely enough Kernel panics would occur with both usb bootable devices, with no drives in any slots, the Minitool partitioning tool alone or Trisquel alone respectively. Cutting the power and trying once again got me into the partitioning tool, and then I plugged the removable drive with the 799M swap partition, refreshed the device list and proceeded to wipe it.

With the Trisuel usb, I got kernel panic after selecting try Trisquel. Cutting power and trying that once again got me into Trisquel - momentarily a high resolution black screen appeared with one line message: ATA failed - invalid argument, and I was back here!

Now zram0 has 215.8M capacity and total swap space, adding the 799MB, indeed is 1014MB. Is there any way using the "Disk utility" to disable and test the drive which is embedded in the video controller? I have about 4MB memory available after booting into the Desktop when the swapper is still vacant. I would like to try reassigning swap space to the sdb6 799MB device only. How?