SliTaz Forum

Usb keyboard and login after install fail

(12 posts) (2 voices)

• Started 3 months ago by CalY
• Latest reply from CalY
• This topic is resolved

Tags:

• boot
• keyboard
• login

1. 

   CalY
   

   offline

   Member

   Downloaded slitaz-current-core64.iso dated June 16/24, ran it as liveCD, hardware functioned using PS2 mouse and usb keyboard. Installed to hard drive from cd, no issues. AFter install reboot to hard drive.
   Graphical login page appears, like white snow with black spider, had user name in login. Usb keyboard had no connection, not even CapsLock or NumLock lights. Powered off, attached PS2 keyboard. System booted, no graphical login, now have terminal full screen with Hostname prompt. Can input user/pw but no method to get to graphical desktop. How to get to desktop, and would like usb keyboard to function as did for livecd!

   Posted 3 months ago #
2. 

   shann
   

   offline

   Administrator

   Hi CalY,

   Strange that all work as expected on live, but issue after install on disk.
   Can you please poste dmesg file (/var/log/dmesg) when you run on livecd.
   Same when you boot on disk and also /var/log/Xorg.*.log files.

   If you have login you can try to start slim (normally autostart).

   As root user su - to become.

   /etc/init.d/slim start

   I do quick test on my EeePC that running current core64, no problem for usb keyboard, see when plug-and-play or if already plug at boot, both case i have desktop.

   Posted 3 months ago #
3. 

   CalY
   

   offline

   Member

   Have files you requested, though found a more significant issue. At install boot partition is primary /dev/sda1 and /home is at logical /sda5. Below is what the installer created for fstab:

   # /etc/fstab: Information about static filesystems.
   #
   proc /proc proc defaults 0 0
   sysfs /sys sysfs defaults 0 0
   devpts /dev/pts devpts rw,gid=5,mode=0620 0 0
   tmpfs /dev/shm tmpfs defaults 0 0
   tmpfs /var/lock tmpfs noexec,nosuid 0 0
   /dev/cdrom /media/cdrom iso9660 user,ro,noauto 0 0
   #/dev/sda3 /home ext3 defaults 0 2
   #/dev/hdb1 /mnt/data btrfs defaults 0 2
   #datasvr:/nfs/home /home nfs tcp,nolock 0 0
   UUID=15feda11-593d-4f74-9fb5-00d30a74991d /home jfs defaults 0 2
   --
   Where is the boot partition or perhaps is more accurate to say root partition? There is none. Added entries to new fstab as below:

   # /etc/fstab: Information about static filesystems.
   #
   proc /proc proc defaults 0 0
   sysfs /sys sysfs defaults 0 0
   devpts /dev/pts devpts rw,gid=5,mode=0620 0 0
   tmpfs /dev/shm tmpfs defaults 0 0
   tmpfs /var/lock tmpfs noexec,nosuid 0 0
   /dev/cdrom /media/cdrom iso9660 user,ro,noauto 0 0
   /dev/sda1 /media/sda1 jfs noauto,noatime,users,umask=0,rw 0 0
   /dev/sda5 /home jfs noauto,noatime,users,umask=0,rw 0 2
   #/dev/sda3 /home ext3 defaults 0 2
   #/dev/hdb1 /mnt/data btrfs defaults 0 2
   #datasvr:/nfs/home /home nfs tcp,nolock 0
   # UUID=15feda11-593d-4f74-9fb5-00d30a74991d /home jfs defaults 0 2
   --

   At install had created a new user. With new fstab at boot Slitaz reaches the graphical user login with my created user name listed. During the boot process, at the start keyboard NumLock light is on, then toward the end of the process, light is off and keyboard has no response. Something in boot process disables keyboard probably cannot find /home. Also during boot there is a message: can't find or locate /home/username. Perhaps I should use the UUID line at end for /home? Something still wrong in fstab.

   Also what are the 0 0 or 0 2 numbers at end of each line for?

   Posted 3 months ago #
4. 

   shann
   

   offline

   Administrator

   Hi CalY,

   hmm infact, if /home not mounted could be an issue.
   For keyboard strange has been detected at boot and unavailable after in desktop.

   Can you post your file (/var/log/dmesg and /var/log/Xorg.*).
   Have files you requested, not sure to understand, files i have see on my EeePC not same as our, in case related to my device :)

   strange that UUID not work but /dev/sdx work for /etc/fstab.

   concerning 0 0 / 0 2 on fstab. If i understand man (https://man7.org/linux/man-pages/man5/fstab.5.html)
   column five indicate if filesystem need dump, most of case dump not installed, default 0
   column six indicate order for fsck, always 1 for root, 2 or other for another partitions (0 is for nocheck)

   Posted 3 months ago #
5. 

   CalY
   

   offline

   Member

   attached is dmesg.log from live cd session

   Attachments

   1. livecd-dmesg.log (26.6 KB, 26 downloads) 3 months old

   Posted 3 months ago #
6. 

   CalY
   

   offline

   Member

   dmesg.log from from hard drive with orignal fstab

   Xorg.0.log from same

   Attachments

   1. Xorg.0.log (58 KB, 20 downloads) 3 months old
   2. installed-dmesg.log (29.5 KB, 27 downloads) 3 months old

   Posted 3 months ago #
7. 

   shann
   

   offline

   Administrator

   Hi CalY,

   Thanks for file.
   Hmm if understand, you don't use SliTaz kernel but 6.6.33 (4MLinux).

   On livecd-dmesg
   Kernel command line: BOOT_IMAGE=/boot/bzImage initrd=/boot/rootfs.gz root=/dev/null video=-32 autologin lang=en_US kmap=us tz=America/New_York

   on installed-dmesg
   Kernel command line: auto BOOT_IMAGE=4MLinux ro root=801 pci=nomsi,noaer

   Could be explain issue you see.

   Posted 3 months ago #
8. 

   CalY
   

   offline

   Member

   This is a test machine with several OS installed one at a time until I find one to be permanent. Had deleted all partitions before installing Slitaz. First time using Gparted, just deleting partitions is not enough, have to use "Create new tables" to empty the MBR.

   Since the first Slitaz cd had issues, acquired the July 28 rolling version. Replaced hard drive with another blanked completely by Gparted, installed again to sda1 as boot and sda5 as home. Grub was installed. Boot after install, Grub displays, let it boot by itself, get this message:

   kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(8,1)

   Computer: Athlon64 X2, 4gb ram, sda1 and 5 are JFS. Kernel module and utils were installed to liveCD before hard drive process.

   Posted 3 months ago #
9. 

   shann
   

   offline

   Administrator

   Hi CalY,

   hmm concercing kernel panic you see, think why :(

   You said use JFS filesystem, but JFS is not in kernel, is 'on module'.
   only ext4 has built-in (with support to ext2/ext3)

   Posted 3 months ago #
10. 

    CalY
    

    offline

    Member

    I realized that. Slitaz will install to a certain FS, but does not copy the FS modules to hard drive. So cannot boot. Tried manually copying all the FS files, something still missing. There are Linux distros that boot to JFS, so the setup procedure varies. Every version of Linux seems different.

    Suggestion: When adding Bootloader during Install, it should ask for the location to install to, as in MBR or boot partition. IF someone has ever used AirBoot manager, you would never want any linux bootloader in MBR. Lilo would be a nice option to install to /boot, so one could use their own boot manager.

    I did try install with Ext2 for boot and home partitions and it booted normal

    Posted 3 months ago #
11. 

    shann
    

    offline

    Administrator

    Hi CalY,

    Support inside kernel depend of distribution, choice has been do.
    In our case for SliTaz, we try to keep kernel small as possible but flexible, that's why for example filesystem has split as module :

    tux@slitaz:~$ tazpkg search fs |grep linux64
    linux64-aufs 20220912_5.10.221 système de base
    linux64-hfsplus 5.10.221 système de base
    linux64-overlayfs 5.10.221 système de base
    linux64-aufs 20220912_5.10.221 système de base
    linux64-autofs 5.10.221 système de base
    linux64-cifs 5.10.221 système de base
    linux64-configfs 5.10.221 système de base
    linux64-cramfs 5.10.221 système de base
    linux64-ecryptfs 5.10.221 système de base
    linux64-exofs 5.10.221 système de base
    linux64-gfs2 5.10.221 système de base
    linux64-hfs 5.10.221 système de base
    linux64-hfsplus 5.10.221 système de base
    linux64-jfs 5.10.221 système de base
    linux64-logfs 5.10.221 système de base
    linux64-ncpfs 5.10.221 système de base
    linux64-nfsd 5.10.221 système de base
    linux64-ocfs2 5.10.221 système de base
    linux64-overlayfs 5.10.221 système de base
    linux64-reiserfs 5.10.221 système de base
    linux64-romfs 5.10.221 système de base
    linux64-squashfs 5.10.221 système de base

    Usually, ext4 is used for root.

    For bootloader, we have feature to install or not, your suggestion is interesting, infact we could purpose install to MBR or partition.

    Posted 3 months ago #
12. 

    CalY
    

    offline

    Member

    Began fresh, did 1 partition and bootloader, the rest of hard drive can be done later. Boots normal. Thank you for assistance, especially explanation on boot install parameters. Each Linux distro can be quite different, some do not tell user how the hard drive is setup, until after one sees the partitions. Consider this thread closed.

    Posted 3 months ago #

RSS feed for this topic

Reply

You must log in to post.