Re: USB3 on QNAP TS-221 running Debian 11
Ciao Luca, I see from your log a kernel crash in the usb driver. Have you tried if with Linux v4.19 it's better? regards federico Il giorno gio 3 mar 2022 alle ore 15:12 Luca Paolini ha scritto: > I've got a *QNAP TS-221* running *Debian 11*, thanks to the modified > partition table suggested by Arnaud Mouiche ( > https://github.com/amouiche/qnap_mtd_resize_for_bullseye). > > Everything works like a charm, except for the *USB3* ports on the rear. > Looking at the logs I see no problems but they don't detect any device I > connect to them. > > Any ideas? > > Many thanks in advance, > Luca Paolini > > -- > > *# uname -a* > Linux nas 5.10.0-11-marvell #1 Debian 5.10.92-1 (2022-01-18) armv5tel > GNU/Linux > > *# lsusb* > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > *# dmesg | grep -i usb* > [ 16.350546] usbcore: registered new interface driver usbfs > [ 16.420379] usbcore: registered new interface driver hub > [ 16.471191] usbcore: registered new device driver usb > [ 16.511954] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > [ 16.701714] orion-ehci f105.ehci: new USB bus registered, assigned > bus number 1 > [ 16.741020] xhci_hcd :02:00.0: new USB bus registered, assigned bus > number 2 > [ 16.877256] Modules linked in: xhci_pci(+) xhci_hcd ehci_orion(+) sg > ehci_hcd marvell mvmdio mv643xx_eth marvell_cesa orion_wdt libdes watchdog > libaes ahci usbcore libahci usb_common nls_base kirkwood_thermal spi_orion > evdev gpio_keys fuse configfs nfsd auth_rpcgss nfs_acl lockd grace sunrpc > ip_tables x_tables hmac ipv6 autofs4 ext4 crc16 mbcache jbd2 raid10 raid456 > libcrc32c crc32c_generic async_raid6_recov async_memcpy async_pq async_xor > xor async_tx raid6_pq raid0 multipath linear dm_mod raid1 md_mod sd_mod > t10_pi crc_t10dif crct10dif_generic crct10dif_common sata_mv libata > scsi_mod rtc_s35390a > [ 17.006890] [] (xhci_run [xhci_hcd]) from [] > (usb_add_hcd+0x43c/0x720 [usbcore]) > [ 17.016186] [] (usb_add_hcd [usbcore]) from [] > (usb_hcd_pci_probe+0x32c/0x39c [usbcore]) > [ 17.026134] [] (usb_hcd_pci_probe [usbcore]) from > [] (xhci_pci_probe+0x18/0xf4 [xhci_pci]) > [ 17.172206] Modules linked in: xhci_pci(+) xhci_hcd ehci_orion(+) sg > ehci_hcd marvell mvmdio mv643xx_eth marvell_cesa orion_wdt libdes watchdog > libaes ahci usbcore libahci usb_common nls_base kirkwood_thermal spi_orion > evdev gpio_keys fuse configfs nfsd auth_rpcgss nfs_acl lockd grace sunrpc > ip_tables x_tables hmac ipv6 autofs4 ext4 crc16 mbcache jbd2 raid10 raid456 > libcrc32c crc32c_generic async_raid6_recov async_memcpy async_pq async_xor > xor async_tx raid6_pq raid0 multipath linear dm_mod raid1 md_mod sd_mod > t10_pi crc_t10dif crct10dif_generic crct10dif_common sata_mv libata > scsi_mod rtc_s35390a > [ 17.301734] [] (xhci_run [xhci_hcd]) from [] > (usb_add_hcd+0x43c/0x720 [usbcore]) > [ 17.311017] [] (usb_add_hcd [usbcore]) from [] > (usb_hcd_pci_probe+0x32c/0x39c [usbcore]) > [ 17.320961] [] (usb_hcd_pci_probe [usbcore]) from > [] (xhci_pci_probe+0x18/0xf4 [xhci_pci]) > [ 17.479078] orion-ehci f105.ehci: USB 2.0 started, EHCI 1.00 > [ 17.531108] usb usb1: New USB device found, idVendor=1d6b, > idProduct=0002, bcdDevice= 5.10 > [ 17.539503] usb usb1: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ 17.546815] usb usb1: Product: EHCI Host Controller > [ 17.551733] usb usb1: Manufacturer: Linux 5.10.0-11-marvell ehci_hcd > [ 17.558137] usb usb1: SerialNumber: f105.ehci > [ 17.607623] hub 1-0:1.0: USB hub found > [ 22.275120] usb usb2: New USB device found, idVendor=1d6b, > idProduct=0002, bcdDevice= 5.10 > [ 22.283587] usb usb2: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ 22.290930] usb usb2: Product: xHCI Host Controller > [ 22.295841] usb usb2: Manufacturer: Linux 5.10.0-11-marvell xhci-hcd > [ 22.302247] usb usb2: SerialNumber: :02:00.0 > [ 22.333205] hub 2-0:1.0: USB hub found > [ 22.373361] xhci_hcd :02:00.0: new USB bus registered, assigned bus > number 3 > [ 22.391488] xhci_hcd :02:00.0: Host supports USB 3.0 SuperSpeed > [ 22.406888] usb usb3: We don't know the algorithms for LPM for this > host, disabling LPM. > [ 22.426755] usb usb3: New USB device found, idVendor=1d6b, > idProduct=0003, bcdDevice= 5.10 > [ 22.435228] usb usb3: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ 22.442498] usb usb3: Product: xHCI Host Controller > [ 22.447409] usb usb3: Manufacturer: Linux 5.10.0-11-marvell xhci-hcd > [ 22.453799] usb usb3: SerialNumber: :02:00.0 > [ 22.505590] hub 3-0:1.0: USB hub found >
Re: armel/marvell kernel size
Hello guys, I believe the problem we are facing on Kirkwood with stretch is the same I had with iop32 and other folks with ixp4xx. As the support for iop32 on Wheezy is under EOL, do we have any hopes to solve the kernel size issue common for all this architectures or it's time to replace our nas? best regards federico 2018-03-28 11:22 GMT+02:00 Rick Thomas: > > On Mar 27, 2018, at 2:08 PM, Rogério Brito wrote: > > > On 2018-03-27 17:29, Rick Thomas wrote: > >> On Mar 27, 2018, at 1:04 PM, Rogério Brito wrote: > >>> As a related subject, I could compile a more stripped down version of > >>> the armel kernel, put it for people to download and ask people to > >>> comment if it works for them, so that we can gauge what people actually > >>> need from such a kernel... > >> > >> Please do! I have an OpenRD box and a SheevaPlug that I’ll be happy to > test on. > > > > You're welcome. I don't know much about the OpenRD nor about the > > SheevaPlug, but are they able to run the -marvell kernels? What was the > > last version of the kernel that worked for you? > > > > What filesystems do you use? Do you use any (para)virtualization? What > > about addon hardware that you have? Any USB dongles? Anything that you > > can think of? Sound? > > > > Do you use NFS? (I do) What kind of compressed ramdisk do you use? The > > loaded modules that you have with lsmod would be nice to know. > > A lot of questions… I’ll do my best to answer them as best I can sometime > this weekend (There are an equally large lot of things on my to-do list > this week! /-: ) > > In the mean time here’s a start: > > OpenRD Client > > rbthomas@client:~$ uname -a > > Linux client 4.9.0-6-marvell #1 Debian 4.9.82-1+deb9u3 (2018-03-02) > armv5tel GNU/Linux > > SheevaPlug > > rbthomas@sheeva:~$ uname -a > > Linux sheeva 4.9.0-6-marvell #1 Debian 4.9.82-1+deb9u3 (2018-03-02) > armv5tel GNU/Linux > > Both are running the latest Stretch. > > Rick >
Re: Supporting armel/armhf in wheezy-lts
Hi folks, 2016-04-25 9:43 GMT+02:00 Santiago Ruano Rincón: > From the other side, what about armel/armhf LTS support? No objecting > voices? > I enjoy my debian wheezy on my iop32x, which wheezy is the last supported release for my arch, so +1 for consider LTS support on my n2100. thanks, regards happy hacking federico
Re: NFS kernel oops with Thecus DMA patch
Hi folks! I need your help for my Thecus.. I'm setting up a fresh debian on it, I'm more oriented to squeeze as my feeling is that with wheezy I could get less performance on iop32x.. Steve, was your kernel built with net_dma? it's the same problem as this above? https://bugzilla.kernel.org/show_bug.cgi?id=13432 I mean, it's your patch fine for have a stable squeeze kernel, if net_dma is left disable? Anyone have a more recent kernel to suggest me for have full dma kernel for Thecus? Thanks for help! Federico 2009-09-25 23:41 GMT+02:00 Martin Michlmayr: > * Steve Langasek [2009-09-25 13:50]: > > Sorry, it turns out this didn't fix the problem after all. :/ > > Putting NFS load on the system caused the panic to reappear again, > > and even downgrading to the 2.6.26 dma kernel doesn't fix it; so it > > seems it was just coincidence that it first appeared after I > > upgraded, and this patch is a wash. > > Ah, damn. > -- > Martin Michlmayr > http://www.cyrius.com/ > > > -- > To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > https://lists.debian.org/debian-arm/2009/09/msg00079.html >
Re: Debian on thecus N2100
2013/4/11 Brian Platt brianpl...@hotmail.com Date: Wed, 10 Apr 2013 22:20:18 +0400 From: alexander.a.dani...@gmail.com To: debian-arm@lists.debian.org Subject: Re: Debian on thecus N2100 On 10.04.2013 16:41, Brian Platt wrote: I'm tring to install debian on the Thecus N2100 using the instructions from http://www.cyrius.com/debian/iop/n2100/ however when formatting the partitions the bar goes up to 33% Try another hdd model. Tried that maybe your RAM is damaged, try another one or to perform a memtest. ciao federico
Re: Mele doing A1000 (Quad Core A31) and A200 (Dual Core A20) devices for developers
Hi Luke 2013/4/13 luke.leighton luke.leigh...@gmail.com On Sat, Apr 13, 2013 at 11:56 AM, Peter Bauer peter.ba...@inode.at wrote: Can you please ask if the offer different cases ? i've passed on the request to them. How can I contact the Mele company, could you please post there email address and web page ? what about second question? thanks federico
Re: Reboot failed -- System halted
Hello did you upgrade recently? try to chroot from debian installer federico 2012/7/30 kqt4a...@gmail.com: I am running Wheezy with kernel 3.4.4 on Zyxel NSA320, Marvel Kirkwood 88F6281_A1. The reboot, shutdown -r, fails and requires a power cycle. Is the a patch for this. Richard -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.DEB.2.00.1207300904500.6302@tehzcl2.tehzcl-arg -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CA+KKcbk4B=KM4OOz40Qj7o0g8LX_f_n7L784iGtFGNgfPZrY=w...@mail.gmail.com
Re: single device to replace ADSL router, WiFi/Ethernet router, SIP router?
Hi list! what about speedport (a branded tcom of Fritz!Box, is almost the same hardware as fritz but cheep). About customize the firmware to make it function like a Fritz!Box, as there is freetz for FritzBox on speedport there is speed2fritz. My favorite product are: speedport w501v (like 7141 without USB, work only in Annex B, no way to use it with Annex A and VOIP) speedport w701v (like 7140 without USB, working perfectly) speedport w900v (like 7270 with 802.11g, working perfectly) speedport w920v (like 7270 with 802.11gN, working perfectly) Happy new year! federico -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CA+KKcbk5sRnrO9=um9bv50zogrn31g4_wnbcynys9q7f3xt...@mail.gmail.com
Re: Bricked N2100
2010/11/25 John Winters j...@sinodun.org.uk: On Thu, 25 Nov 2010 12:27:51 +, John Ashby n2...@hotmail.co.uk wrote: Following a bad edit to /etc/network/interfaces, my Thecus N2100 has zero network connectivity. The way I've solved this in the past is to take the HDD out of my N2100 and edit the file on another machine. A little USB=SATA cradle comes in useful here. + 1 I would do the same Your RAID1 configuration obviously makes it slightly more complicated, but it should still be possible. yes it is! But if your root (/etc) partition is also under raid1 you have a bit more trouble, you have to set one hdd as faulty drive and then recreate the mirror from the hdd with the correct /etc/network/interfaces. Take a look at http://www.howtoforge.com/replacing_hard_disks_in_a_raid1_array -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimt1vfvytrgefddssccx3fj2b83l-szurmt5...@mail.gmail.com