- CRUX-ARM - lists.crux-arm.nu

USB 3 thumb drive not registering on OdroidXU4
by Alex Matviychuk 28 Apr '17

28 Apr '17

I installed crux 3.3 on an OdroidXU4. Everything works fine except when I plug in a thumb drive into either front USB 3 port, nothing shows up in dmesg and no /dev/sd* devices are created. Any idea on what I might be missing? Thanks, Alexander Matviychuk

2 2

Re: [crux-arm] Keyboard is not working
by Victor Martinez 29 Mar '17

29 Mar '17

* Matt Savin (matt(a)tegers.com) wrote: > Hello Victor, > Hey Matt, > OK, keyboard is working. I had to reset USB hub through gpio. > > Thank you for your help, > Great!, not much help really, but glad to know you got it working. Regards, --- Victor Martinez Learning bit by bit | http://vjml.es

1 0

Re: [crux-arm] Keyboard is not working
by Victor Martinez 28 Mar '17

28 Mar '17

* Matt Savin (matt(a)tegers.com) wrote: > Hello Victor, > Hey, > Yes and yes - I do use the debian kernel for both rootfs' and I did copy > /lib/modules from debian to crux-arm. > It shouldn't be related but did you copy /lib/firmware too? Are you using the same kernel boot options? (if there are) It's really strange, not sure why it's happening and how can I help in this case (no hardware to debug or test). May be unpplugin and plugging again when booted? Test with another keyboard? Check if there are specific udev/eudev rules in debian? I've tested the generic release on the odroid-xu4 with separated usb mouse and keyboard, and another test with a smart tv keyboard with a pad without problems. > Thank you very much for your reply, > Matt > You are welcome. Regards, --- Victor Martinez Learning bit by bit | http://vjml.es

1 0

Keyboard is not working
by Matt Savin 28 Mar '17

28 Mar '17

Hello, I have a proprietary device with i.MX 6Quad 32-bit processor (ARMv7 Cortex-A9 core) which is running Debian 8 (jessie). I created a separate Crux root partition, downloaded http://resources.crux-arm.nu/releases/3.3/crux-arm-rootfs-3.3.tar.xz, extracted its contents in to the new partition, modified rc.conf, shadow and sshd_config files and booted into the Crux. Keyboard and mouse on the console are not working, but I can ssh to the system and work on it remotely. On Crux "dmesg | grep -i usb" returns: *usbcore: registered new interface driver usbfsusbcore: registered new interface driver hubusbcore: registered new device driver usbusbcore: registered new interface driver udlusbcore: registered new interface driver dln2ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driverusbcore: registered new interface driver usb-storage2184200.usb supply vbus not found, using dummy regulatorci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00usb usb1: New USB device found, idVendor=1d6b, idProduct=0002usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1usb usb1: Product: EHCI Host Controllerusb usb1: Manufacturer: Linux 4.0.0+ ehci_hcdusb usb1: SerialNumber: ci_hdrc.1hub 1-0:1.0: USB hub foundusb0: HOST MAC 22:76:48:b0:7b:c3usb0: MAC 86:81:e4:b2:91:5cusbcore: registered new interface driver usbhidusbhid: USB HID core driverusb_otg_vbus: disabling* On Debian "dmesg | grep -i usb" returns (lines in bold are identical for Crux and Debian, the rest on Debian is loaded by systemd): *usbcore: registered new interface driver usbfsusbcore: registered new interface driver hubusbcore: registered new device driver usbusbcore: registered new interface driver udlusbcore: registered new interface driver dln2ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driverusbcore: registered new interface driver usb-storage2184200.usb supply vbus not found, using dummy regulatorci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00usb usb1: New USB device found, idVendor=1d6b, idProduct=0002usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1usb usb1: Product: EHCI Host Controllerusb usb1: Manufacturer: Linux 4.0.0+ ehci_hcdusb usb1: SerialNumber: ci_hdrc.1hub 1-0:1.0: USB hub foundusb0: HOST MAC 56:8d:e9:dc:85:d7usb0: MAC 6e:fa:25:5b:03:8eusbcore: registered new interface driver usbhidusbhid: USB HID core driverusb_otg_vbus: disabling* usb 1-1: New USB device found, idVendor=0424, idProduct=2514 usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usb 1-1.1: new high-speed USB device number 3 using ci_hdrc usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514 usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 hub 1-1.1:1.0: USB hub found hub 1-1.1:1.0: 2 ports detected usb 1-1.2: new low-speed USB device number 4 using ci_hdrc usb 1-1.2: New USB device found, idVendor=0461, idProduct=4d64 usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.2: Product: USB Optical Mouse input: USB Optical Mouse as /devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.2/1-1.2:1.0/0003:0461:4D64.0001/input/input1 hid-generic 0003:0461:4D64.0001: input,hidraw0: USB HID v1.11 Mouse [USB Optical Mouse] on usb-ci_hdrc.1-1.2/input0 usb 1-1.1.1: new full-speed USB device number 5 using ci_hdrc usb 1-1.1.1: New USB device found, idVendor=156a, idProduct=0008 usb 1-1.1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.1.1: Product: Logical ImposterK input: Logical ImposterK as /devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.1/1-1.1.1/1-1.1.1:1.0/0003:156A:0008.0002/input/input2 usb 1-1.3: new low-speed USB device number 6 using ci_hdrc hid-generic 0003:156A:0008.0002: input,hidraw1: USB HID v1.10 Keyboard [Logical ImposterK] on usb-ci_hdrc.1-1.1.1/input0 input: Logical ImposterK as /devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.1/1-1.1.1/1-1.1.1:1.1/0003:156A:0008.0003/input/input3 usb 1-1.3: New USB device found, idVendor=046d, idProduct=c31d usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.3: Product: USB Keyboard usb 1-1.3: Manufacturer: Logitech hid-generic 0003:156A:0008.0003: input,hidraw2: USB HID v1.10 Device [Logical ImposterK] on usb-ci_hdrc.1-1.1.1/input1 input: Logitech USB Keyboard as /devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.3/1-1.3:1.0/0003:046D:C31D.0004/input/input4 usb 1-1.1.2: new full-speed USB device number 7 using ci_hdrc hid-generic 0003:046D:C31D.0004: input,hidraw3: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-ci_hdrc.1-1.3/input0 input: Logitech USB Keyboard as /devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.3/1-1.3:1.1/0003:046D:C31D.0005/input/input5 m25p80 spi4.0: s25fl064k (8192 Kbytes) hid-generic 0003:046D:C31D.0005: input,hidraw4: USB HID v1.10 Device [Logitech USB Keyboard] on usb-ci_hdrc.1-1.3/input1 usb 1-1.1.2: New USB device found, idVendor=156a, idProduct=0009 usb 1-1.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.1.2: Product: Logical ImposterM input: Logical ImposterM as /devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/0003:156A:0009.0006/input/input6 hid-generic 0003:156A:0009.0006: input,hidraw5: USB HID v1.10 Mouse [Logical ImposterM] on usb-ci_hdrc.1-1.1.2/input0 lsmod on Crux retrurns: Module Size Used by cfg80211 485728 0 m25p80 7879 0 spi_nor 22158 1 m25p80 lsmod on Debian returns: Module Size Used by joydev 9812 0 sg 31856 0 m25p80 7879 0 spi_nor 22158 1 m25p80 Would appreciate if you can point me in the right direction on how to make keyboard and mouse recognized. Thank you, Matt

2 1

pkgutils-cross 3.3 sources are not available
by Matt Zhabin 23 Mar '17

23 Mar '17

Hello, First of all, thank you very much for the great distribution! I tried to follow instructions on https://crux-arm.nu/Documentation/PkgutilsCross: 2. Build pkgutils-cross $ cd /devel/crux-arm $ git clone git://crux-arm.nu/crux-arm/pkgutils-cross.git $ cd pkgutils-cross $ git branch 3.3 origin/3.3 $ git checkout 3.3 $ make [matt@tegers devel]# git clone git://crux-arm.nu/crux-arm/pkgutils-cross.git Cloning into 'pkgutils-cross'... remote: Counting objects: 587, done. remote: Compressing objects: 100% (379/379), done. remote: Total 587 (delta 381), reused 294 (delta 203) Receiving objects: 100% (587/587), 244.67 KiB | 347.00 KiB/s, done. Resolving deltas: 100% (381/381), done. Checking connectivity... done. [matt@tegers devel]# cd pkgutils-cross/ [matt@tegers pkgutils-cross]# git branch 3.3 origin/3.3 fatal: Not a valid object name: 'origin/3.3'. [matt@tegers pkgutils-cross]# git branch 3.2 origin/3.2 Branch 3.2 set up to track remote branch 3.2 from origin. [matt@tegers pkgutils-cross]# git checkout 3.2 Switched to branch '3.2' Your branch is up-to-date with 'origin/3.2'. According to the above, either I'm not able to follow above instructions properly, or 3.3 branch is still not available for pkgutils-arm. Thank you, Matt

2 1

[ANN] CRUX-ARM 3.3 Released
by CRUX-ARM System Team 11 Mar '17

11 Mar '17

Hello there, we are pleased to announce CRUX-ARM 3.3 release: Release notes: http://crux-arm.nu/Documentation/ReleaseNotes3-3 Changelog: http://crux-arm.nu/Documentation/Changelog#3-3 Download: http://crux-arm.nu/Main/Download Best regards, -- CRUX-ARM System Team | http://crux-arm.nu

1 0

Re: [crux-arm] crux-arm 3.3?
by Victor Martinez 26 Feb '17

26 Feb '17

* Guido Caliandro (guido.caliandro(a)gmail.com) wrote: > Hi Victor, > Hey Guido! > first of all thank you very much for the great job that you and all staff > are doing. > No problem :) > if it could be of any interest, I can test it on raspberry pi 1b, b+, PI2 > and PI3, and also on some olinuxino arm with A10 and A20 soc. > I hope in the next weeks I can put hands on optimizations for some devices, A10 and A20. My Rpi 1b is far and I'm not sure if I'll be able to start with it in at least 3 weeks. If you want to deploy the generic release and look for errors, improvements or anything, it could be greati, also to debug and probably to start optimizations in some of your devices like Rpi2/Rpi3. If you need any point to start doing these optimizations like we do, just tell me and I'll try to guide you in the proccess. There is some information here: https://crux-arm.nu/Documentation/HowToContribute > ciao > Guido > Regards, --- Victor Martinez Learning bit by bit | http://vjml.es

1 0

crux-arm 3.3?
by Guido Caliandro 25 Feb '17

25 Feb '17

Hi all, Is there any news about that? ;-) thank you bye Guido

2 2

Re: [crux-arm] crux-arm setup firefox error - segmentation fault
by Víctor Martínez 07 Feb '17

07 Feb '17

El 03/02/17 a las 07:47, Milan Buška escribió: > Hi Victor Hey Milan, > nspr => enable-64bit on disable-64bit > firefox => delete line ac_add_options --with-pthreads I've make an overlay for nspr to avoid the enable-64bit option. Thank you for this catch. About firefox, I was deeping in the problem this last weekend with the segfault and removing pthread support isn't a good way to solve the problem, since it wasn't really related to firefox, and doing this is like avoiding the problem. The problem was the nss update to 3.28.1 which I made it wrong. I don't know how I checked upstream commit because I didn't see all the changes made by Fredrick... and this broke firefox. I've updated the port and only a rebuild of nss is needed. I recommend you to check it and let firefox with pthreads support because it will work right now. > I deleted a line ac_add_options --with-pthreads > maybe it should just be pthread - I do not know > But after adjustments and subsequent compilation Firefox starts without errors. Thank you very much for your report and help provided. > Have a nice day > Milan > Have a nice web surfing with firefox! Regards, -- Victor Martinez Learning bit by bit | http://vjml.es

3 2

Re: [crux-arm] crux-arm setup firefox error - segmentation fault
by matti christensen 07 Feb '17

07 Feb '17

Hello i've been following your discussion because i used to have serious issues w ff and arm boards while ago. after version 48.n.n building has gone smoothly on rpi which i use for writing this. as Victor may remember i'm really aschetic w my systems = i only install bare minimum binary using the only system suitable for that ( CRUX ARM ), then i remove stuff i don't need ( there are many + binary package manager ) and start building stuff like X etc.. attached you find my .mozconfig for 48.0.2 ( please note that most lines are just because of my minimal needs ); /mc Quoting Victor Martinez <pitillo(a)crux-arm.nu>: > * Milan Bu??ka (milan.buska(a)gmail.com) wrote: >> Hi Victor >> >> 2017-02-02 15:17 GMT+01:00 Victor Martinez <pitillo(a)crux-arm.nu>: >>> * Milan Bu??ka (milan.buska(a)gmail.com) wrote: >>>> Hi Victor >>>> >> > Hey! > >>> Hello again Milan, >>> >>>> Compile with options O0 gives the same error. >>> I can confirm the same. I've built firefox without optimizations >>> and it's still segfaulting. >>> >>>> My suggestion is to move the package from nspr opt to opt-arm >>>> and adjust Pkgfile for detailed specification of the ARM 32-bit >>>> architecture. >>> Good catch I'll review nspr and give a try with a rebuild. >>> >>>> I suspect that this error depends on compilations since nspr. >>>> I'll try to compile firefox with modified nspr and nss packages. >>>> >>>> Have a nice day >>> Same there. I'll update with results. >>> >>>> Milan >>>> >> >> nspr => enable-64bit on disable-64bit >> firefox => delete line ac_add_options --with-pthreads >> >> I deleted a line ac_add_options --with-pthreads >> maybe it should just be pthread - I do not know >> But after adjustments and subsequent compilation Firefox starts >> without errors. >> > Very good catch Milan. I've modified nspr, rebuilt nss and firefox > and the problem persists. I'll update firefox port with your > suggestions and I'll check tomorrow, if it works right, I'll push > changes for nspr and firefox at saturday night. > > I was near to revert nss and firefox ports because I wasn't abke to > deep in to the problem more than removing optimizations. > > Thank you very much for your research and fixes provided. You have > Flyspray and IRC too to contact us, but ML is fine (just as a > reminder). > >> Have a nice day >> Milan >> > Best Regards, > > --- > Victor Martinez > Learning bit by bit | http://vjml.es > _______________________________________________ > crux-arm mailing list > crux-arm(a)crux-arm.nu > https://crux-arm.nu/mailman/listinfo/crux-arm

2 1