Re: [qubes-users] 404 from qubes-dom0-update for https://yum.qubes.org/r25-5/current/dom0/fc25/repodata/......
Hi > Sorry, that was not a question, but musing on my part. > I havent seen this bug in some time - can you try updating with > qubes-dom0-update passing in the --releasever=4.0 option? sudo qubes-dom0-update --releasever=4.0 runs without errors and does update a number of packages. Upon reboot, sudo qubes-dom0-update without the releasever parameter, now runs without errors, but of course has no updates pending this time around, so not a full test. Kristian -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5f67dc70b7996b02be2ef39f917f0636b7b36e4e.camel%40elof.dk. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 404 from qubes-dom0-update for https://yum.qubes.org/r25-5/current/dom0/fc25/repodata/......
> Where is that r25-5 coming from? > Have you edited your repo definitions in > /etc/yum.repos.d/qubes-dom0.repo ? It appears to originate form the "metalink" field in /etc/yum.repos.d/qubes-dom0.repo And no, I haven't (knowledgedly) tinkered with the configuration. [username@dom0 ~]$ cat /etc/yum.repos.d/qubes-dom0.repo [qubes-dom0-current] name = Qubes Dom0 Repository (updates) #baseurl = https://yum.qubes-os.org/r$releasever/current/dom0/fc25 #baseurl = http://yum.sik5nlgfc5qylnnsr57qrbm64zbdx6t4lreyhpon3ychmxmiem7tioad.onion/r$releasever/current/dom0/fc25 metalink = https://yum.qubes-os.org/r$releasever/current/dom0/fc25/repodata/repomd.xml.metalink enabled = 1 . -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4ffdc51dac3ff7b64ea6e3cf7c65bb5ee25a0132.camel%40elof.dk. For more options, visit https://groups.google.com/d/optout.
[qubes-users] 404 from qubes-dom0-update for https://yum.qubes.org/r25-5/current/dom0/fc25/repodata/......
Hi Qubes 4 in dom0: sudo qubes-dom0-update -v repo: downloading from remote: qubes-dom0-current Qubes Dom0 Repositor [=== ] --- B/s | 0 B --:-- ETA Qubes Dom0 Repositor [=== ] --- B/s | 0 B --:-- ETA error: Status code: 404 for https://yum.qubes-os.org/r25-5/current/dom0/fc25/repodata/repomd.xml.metalink (https://yum.qubes-os.org/r25-5/current/dom0/fc25/repodata/repomd.xml.metalink). repo: downloading from remote: qubes-templates-itl Qubes Templates repo [ === ] --- B/s | 0 B --:-- ETA Qubes Templates repo [ === ] --- B/s | 0 B --:-- ETA error: Status code: 404 for https://yum.qubes-os.org/r25-5/templates-itl/repodata/repomd.xml.metalink (https://yum.qubes-os.org/r25-5/templates-itl/repodata/repomd.xml.metalink). Looking at yum.qubes-os.org with Firefox the folder /r25-5 does not exist However /r4.0/current/dom0/fc25/repodata/ seems to contain the files qubes-dom0-update is looking for How to proceed from here? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6c39f4699b191415e3570fd666f56525883415e0.camel%40elof.dk. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Ethernet port in an USB-C dock - failure to attach to sys-net
> what does lsusb in sys-usb show? What's the listed device class? [user@sys-usb ~]$ lsusb -s 003:013 -v Bus 003 Device 013: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x0b95 ASIX Electronics Corp. idProduct 0x1790 AX88179 Gigabit Ethernet bcdDevice1.00 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 57 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol 0 iInterface 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 11 bMaxBurst 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1513542636.996.7.camel%40elof.dk. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Ethernet port in an USB-C dock - failure to attach to sys-net
> You shouldn't have to do that, sys-usb is a NetVM by default. > Interesting. the sys-usb is indeed listes as "Type: NetVM" However the ethernet device does not show up when running ifconfig or the "Network Connections" gui program. When plugging in the USB-C dock, I see this: [user@sys-usb ~]$ sudo dmesg -w ... [22271.385720] usb 3-1.2.4: new SuperSpeed USB device number 9 using xhci_hcd [22271.404341] usb 3-1.2.4: New USB device found, idVendor=0b95, idProduct=1790 [22271.404371] usb 3-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [22271.404389] usb 3-1.2.4: Product: AX88179 [22271.404401] usb 3-1.2.4: Manufacturer: ASIX Elec. Corp. [22271.404412] usb 3-1.2.4: SerialNumber: 01 [22271.739817] ax88179_178a 3-1.2.4:1.0 eth0: register 'ax88179_178a' at usb-:00:00.0-1.2.4, ASIX AX88179 USB 3.0 Gigabit Ethernet, 60:45:cb:bd:16:c8 [22271.803545] ax88179_178a 3-1.2.4:1.0 enp0s0f0u1u2u4: renamed from eth0 [user@sys-usb ~]$ /sbin/ifconfig lo: flags=73mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1 (Local Loopback) RX packets 36 bytes 2016 (1.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 36 bytes 2016 (1.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 No other network device than "lo" is listed? I would have expected either eth0 or enp0s0f0u1u2u4 ? Kristian -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1513541309.996.6.camel%40elof.dk. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Request for feedback: 4.9 Kernel
On Sat, 2017-05-20 at 13:42 -0600, Reg Tiangha wrote: > People may not have noticed, but there is now a 4.9 kernel in > current-testing (4.9.28 to be specific). Running kernel 4.9.35-19 now > 1) Hardware that used to work with 4.4 or 4.8 no longer works with > 4.9. None observed > 2) Hardware that didn't work with 4.4 or 4.8 still doesn't work. Same as with the 4.8.12-12 That means quite a lot of hardware does not work or are not recognised by the kernel. This is on a very recent i5-7200U based ASUS B9440U laptop with its accompaining USB-C dock. Powermanagemet in general is sorely missing on laptop with Qubes. (batterylife is 3-4 hours instead of approx. 10, the monitor backlight never turns off despite the screensaver turning the screen black, the keyboard backlight does not work and the fan runs nearly all the time. > 4) General feedback on the 4.9 kernel. > Well I look forward to kernel 4.10 and 4.11 and hope to see them soon on Qubes. Othervise I will have to end my Qubes experiment on this laptop and install something else, in order to get actual work done. Kristian -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1501298915.1076.17.camel%40elof.dk. For more options, visit https://groups.google.com/d/optout.
[qubes-users] USB-C docking & ethernet fun with the Asus SimPro and MiniDocks
Hello Using an Asus B9440U laptop connected via USB-C to an Asus SimPro dock and an Asus MiniDock, I see some ports work, some not and some weird behavior. Qubes R3.2 kernel 4.4.14-11 xen 4.6.1 Having followed https://www.qubes-os.org/doc/usb/ the following works: + USB stick + SD card + USB keyboard + mouse + VGA + HDMI - Gigabit Ethernet ? Audio + Displayport - untested so far Both docks show up as devices in dom0 qvm-usb output: [@dom0 ~]$ qvm-usb sys-usb:2-1.3 1fc9:500d NXP_SIMPRODOCK_PD_2.100_098e0695 sys-usb:2-8 8087:0a2b 8087_0a2b sys-usb:2-2.2 2109:0101 VIA_Technologies_Inc._USB_2.0_BILLBOARD_0001 NXP being the SimPro Dock and VIA the MiniDock. The third device is the internal USb device in the laptop. When I plugin an USB stick or SD card or keyboard or mouse, they do show up as individual devices in the dom0 qvm-usb output when plugged into the MiniDock, but not when plugged into the Simpro Dock. In both cases they do show up in the sys-usb lsusb output In both cases they work fine. The gigabit ethernet device do show up in the sys-usb lsusb output, but since it does not show up in the dom0 qvm-usb output I cannot attach it to a vm. [@sys-usb ~]$ lsusb Bus 003 Device 033: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet ... Any idea how usb devices can work fine while not showing up in the dom0 qvm-usb output? How do I get the gigabit ethernet device in the SimPro Dock to work? Not knowing its device ID I cannot attach it to a VM. https://www.asus.com/Docks/ASUS-SimPro-Dock/ https://www.asus.com/Docks/Mini-Dock/ https://www.asus.com/us/Commercial-Laptops/ASUSPRO-B9440UA/specificatio ns/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1497568775.2928.53.camel%40elof.dk. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - ASUSPRO B9440U
Hello Having played with Qubes 3.2 on my new laptop for a couple weeks, it is time to share my findings. The HCL file is attached to this email. ASUSTeK COMPUTER INC B9440UA Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz Intel Corporation Wireless 8260 (rev 3a) qubes: R3.2 xen: 4.6.5 kernel: 4.8.12-12 In general things started to work out ok once I upgraded the kernel to 4.8.12, there was all sorts of weird problems before that upgrade, which I will spare you. Status with kernel 4.8.12-12: Wifi, keyboard, touchpad & screen works. Batterystatus indicator seems to be honest. Daily use in general works fine. I have created an usb-vm, a windows10 vm as well as several others and used the machine for daily work (java development, databases, email etc) for a while. Performance and responsiveness when running 4-5 vms and quite a few memory hungry applications is surprisingly good. Keyboard backlight cannot be turned on. Battery life is only half as good as advertised by ASUS. Powermanagement will blank the screen but hibernation and suspend to disk does not work. There is an error message along these lines "powersave verb not supported" when the machine was supposed to go into hibernation or suspend to disk. High res video eg. youtube is awfully slow & jerky in the fedora vms (haven't tried in windows ot debian vms yet). I suppose software rendered rather than GPU pass-through. I have not yet looked into if this might be configurable or some other drives might be available etc. Audio does not work. When I add the "Audio device" to a VM using the "VM manager" I get a "You've enabled dynamic memore balancing, some devices might not work!" message. When I press on and try to start the vm, it fails to start with the message: "Internal error: unable to reset PCI device, no FLR, PM reset or bus reset available". The Asus MiniDock that came with the laptop works like a charm (It is a tiny USB-C 3.1 -> HDMI, USB-3.0 and USB-C 3.1 device). I have tested it with a 2560x1440 monitor, a VGA projector and a USB stick. No problems observed. The Asus SimPro Dick 1A works partly. USB-3.0 and the powerbutton works. Ethernet does not work. No ethernet device shows up when plugged in. External monitors, does show a picture during boot. Erratic behavior after login, sometimes it works fine, sometimes one or both external monitors goes blank complaining of "no signal". Picture quality seem ok when there is a picture. Not yet tested: Audio, USB-C and SD-card reader -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1496875111.973.29.camel%40elof.dk. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-ASUSTeK_COMPUTER_INC_-B9440UA-20170608-000530.yml Description: application/yaml