i just installed fedora linux on my dell 3100 chromebook and the mouse pad worked the first time it booted after installation but when i turned it off and then back on it doesnt work anymore
also for some reason only 3.6GB of 30GB are available to use after a fresh install of fedora
how do i fix this
What did you use to install, and did you reclaim space during installation? Also if you have a usb mouse try using that.
i used a live usb and i just figured out that when i installed there was 2 unallocated space partions so when it installed it only used one. is there any way to “add” that space to my main partition?
Unless you have already added programs or something, I would recommend just reinstalling fedora from your live USB, But they’re likely is a way to add space to your existing partition. I simply don’t know how to If there is (I’m relatively new to linux). I have put fedora on a Dell 3100 and Lenovo 200 E Chromebook Though so far and have not run into the same issue as you, so I would recommend reinstalling Fedora and this time, making sure you reclaim all the space on your hard drive. Even then that only gives you (if I recall correctly) 16 GB of space so I would recommend using an SD card and Selecting both your hard drive, and the SD card during installation. P.S. The hard drive will be labeled as SD card reader, I don’t really know why.
Also, it may just be giving you 3.6 GB because fedora takes up about 15 GB of space.
So the touchpad worked on the live installer but not on the normal install?
That is strange, as on the regular install environments you cannot add packages yourself afaik.
There will be a driver missing that you need to install.
https://packages.fedoraproject.org/search?query=Input
Also for partition issues, please open Disks and share a picture, or in the terminal use lslbk
I think I might have similar issues with the Fedora installer not wiping eMMC storage by default. Feel free to join discussion.fedoraproject.org to get more Fedora-specific help. Also, the missing touchpad driver could be reporter in the workstation bug tracker so you get a faster answer.
Add the relevant data there