Hello!
I made my own build of Ubuntu 16.04 x64 using this manual (https://help.ubuntu.com/community/LiveCDCustomization).
Almost everything is alright, but I found that USB mouse doesn't work with the build. There is no cursor and reaction to clicking (neither in install wizard nor in LiveCD mode), but the mouse lights and indicates its moving. PS/2 mouse and keyboard work with the build normally.
Both mice (USB and PS/2) work normally with the official image of Ubuntu 16.04 x64.
How can I make a build with saving ability to use USB mouse, like in the official image? It really upsets me.

Hello and welcome to LQ.

lsusb might shed some light on the issue but the real problem for us is what did you do?

The two basic parts of a mouse might be mouse support and usb support. I don't see how you could have damaged that normally. I get the feeling some build problem or only slightly a permission problem.


What exactly did you do to customize the build?

Thanks for greeting :-) OK, I'll try to make this problem easier for understanding.
Just for the record, I'm not so good in Linux and I understand not all commands that I executed :-)
First, I made my own build (added my own packages, theme etc) and I saw that my USB mouse doesn't work (as I already described).
Then I tried to find a reason and made the build without whatever modifications, using only commands from the manual (figuratively speaking, to disassemble the official image and build its accurate copy).
When making this build, I executed all commands from parts:

"Obtain the base system"
"Extract the CD .iso contents"
"Extract the Desktop system"
"Prepare and chroot"
"Customizations"->"Apt"->"Prerequisites"
"Cleanup"
"Producing the CD image"->"Assembling the file system"

and I got image without modifications.
When testing it, I found that mistake remained and USB mouse doesn't work again.
I think, when I made these builds by executing the commands, I somehow broke USB support or something like this. I don't know how to fix it, and I'll be grateful for any help.

Sam_Rosewood,

Welcome to LQ.

I am sure that you have very good reasons for adopting the custom-build route.

On the other hand, it could take you some time to solve this problem.

You may need to consider the more conventional route and have a functioning mouse.

I generally adopt the KISS principle in such matters.

I hope you find a speedy solution.

beachboy2, thank you for positive mood, but maybe I didn't understand what do you mean about "conventional route".
I see reason to analyze not my goals for creating custom build, but real problem that appeared when creating this build.
About "a functioning mouse": my USB mouse is working and fully functioning on all of the systems (Windows, Ubuntu etc), but not on my custom build. However, my other PS/2 mouse works on this build (in install wizard and LiveCD mode) normally.
Yes, it's not so hard for me to install this build to my old desktop with PS/2 port, but I can't use it on my new notebook, that has only USB ports.
In spite of my lack of knowledge about Linux, I'll always be glad to hear concrete proposition and thinking about this problem.

"
"Obtain the base system"
"Extract the CD .iso contents"
"Extract the Desktop system"
"Prepare and chroot"
"Customizations"->"Apt"->"Prerequisites"
"Cleanup"
"Producing the CD image"->"Assembling the file system"
"

I don't see how those commands should have broken your mouse. Did you try lsusb command in terminal to get more information?

I assume that the usb mouse did work in the normal build correctly and you can go back to that to see what it reports.

The second part of that is the actual mouse support. I'd have to search for that but I suspect it is a kernel module.

It is possible that some permissions were changed too.

It is possible that the build failed for some reason. Ram errors or such.

Lastly could be an oddity of the computer. Try full power down, remove ac, press power button a few times then power up. Then plug in mouse to see if action works.

Any apt settings changed that come close to mouse? Usb?

Sam_Rosewood,

The conventional route would be to install the "ready-made" Ubuntu 16.04.

Hopefully you will find somebody on these forums who can solve your problem with a concrete proposition.

beachboy2, if "ready-made" means "official", then it doesn't suit me. I just want to create custom build with all packages that are necessary for me. And yet, thank you for trying to help me.
jefro,
1. "lsusb" command
Yes, it was the answer from ubuntuforums.org. Trying to find a reason, I made an experiment: I wrote the official image of Ubuntu 16.04 x64 and my custom build on 2 flash drives, loaded LiveCD mode and made the screenshots of "lsusb" log n terminal.
1) Official Ubuntu: LiveCD mode loaded normally, USB mouse work normally and shows in "lsusb" log.
2) Custom build: LiveCD mode loaded normally, USB mouse doesn't work. There is no cursor and reaction, but it lights when moving and displayed in "lsusb" log too! I had to execute terminal by USB keyboard (it works, by the way).
I made screenshots of logs. As you can see, they're identical (apart from flash drive information, of course).
2. Build could not fail. I tried to make the build on my old desktop and even on new notebook, same result: USB mouse doesn't work.
I thought that problem is in the computer, in flash drive, in official image, anywhere... but after all the experiments, I think that something happened with usb when I created the build. If somebody tried to reproduce it and solve, it would be awesome.

By the way, this is one more problem: when I made screenshot on custom build, I saw that there is no sound when making it. On official Ubuntu, sound works normally. I think I spoiled sound on custom build too.

Attached Thumbnails

   

Hi Sam. This is perhaps X-server related. What is reported by the following command?
More verbose output can be generated using
This might be useful too

Some more ideas here under mouse for tests. http://www.linux-usb.org/USB-guide/x194.html

At this point I assume that lsusb is good enough to say that a mouse was found on a usb port. That is only part of the works.

Sounds like you are missing pkg's and other dependent libraries that make up the systems functionality for recognition, sound and etc...

There are thousands of pkg's and it could be close to impossible to tell what's missing.
The sound module may not be installed and if it is it might not be loading.

Run those commands for ferrari and post the output when you can.

Agreed.

Maybe the mouse isn't working because the driver/module is installed or not and or it's not loading.
<OR> maybe there isn't support in that particular kernel for that brand of mouse?
Driver can be fun to say the least.

1 members found this post helpful.

ferrari, hi. I did "lsusb" on the custom build and the official image (LiveCD mode). They are different. Screenshots are enclosed.
jefro, I went through this page (I try to look at this later) and I didn't found files /usr/X11R6/lib/X11/XF86Config or /etc/X11/XF86Config (the official image, LiveCD mode). Maybe there is another file that is used for it?
Ztcoracat, about sound: I removed no packages for excluding the possibility to break something, but sound and USB mouse has been broken in my custom build. I didn't modificated by myself, I've only executed commands from manual. Please, read again all my previous posts and the manual. I don't want to explain it again the second time.
About USB mouse and drivers: Maybe there is something happened with driver/module, as you said, but not with the support or kernel, the USB mouse worked with the official Ubuntu image correctly. I already said about it in my previous post.

Attached Thumbnails

         

Okay, I see from your screen shots that the custom build shows the mouse is not reported, whereas the 'standard' build shows 'A4Tech USB mouse'. Connecting the mouse, and observing 'dmesg' output would be helpful here. It is likely missing the required kernel support.

I've found at least one reference that refers to the 'hid-a4tech' module as being required for this mouse hardware. As a temporary measure try loading the module manually
If that module is not found, then that may well be your problem (with the kernel build) here.

ferrari, here is the logs from dmesg and screenshots from modprobe.

Attached Thumbnails

   

Attached Files

	dmesg-custom-build.txt (56.7 KB, 10 views)
	dmesg-ubuntu-1604-x64.txt (59.7 KB, 11 views)