You are not logged in.
Thank you, very much for generating a easy and understandable explanation from my unsorted clutter.
As to the problem itself, that is addressed in this debian bugs:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1038930
https://bugs.debian.org/cgi-bin/bugrepo … ug=1055771
First one has a working patch, second has not.
Both aren't fixed yet.
I have a bit of a struggle to address a Bug I found and might have annoyed some (at least one) software developers.
As I understand it, Devuan is using mostly Debian packages.
So any package coming from Debian to Devuan is called "downstream"?
Any Bug reported with Devuan, which has its root in the debian package is to be reported by the devuan maintainer "upstrem" to Debian?
Is that the right understanding?
EDIT:
perfectly explained here:
https://dev1galaxy.org/viewtopic.php?pid=48821#p48821
Summary: there are only devuan packages when debian packages need to be "de-systemd-ed", which are very few.
(for completion: the mentioned package in the other thread does not fall into that category)
So with the first answer in my bug #1412 do actually have no idea where the right place is to post this..
So do I open a Devuan bug for this and if necessary the maintainers will bush it upstream, if necessary? (devuan -> debian -> radicale).
OK, that seems the wrong way to do it. I searched bugs.devuan.org for radicale:
"There is no maintainer for radicale. This means that this package no longer exists (or never existed). Please do not report new bugs against this package."
Meanwhile on my installation:
# apt-cache search radicale
python3-radicale - simple calendar and addressbook server - python3 module
radicale - simple calendar and addressbook server - daemon
Same result for my chimeara (server) and daedalus(desktop) installation.
So, first upgrad my server to deadalus and then if the problem still exists a bug repost to debian (since there is no devuan maintainer) ?
Yeah, I have been to most of it, but it seems the sysV is now left to the package maintainers.
I did open an bug here
https://github.com/Kozea/Radicale/issues/1412
the bug I posted earlier is marked closed:
https://github.com/Kozea/Radicale/issues/1188
But didn't fixed my problem. I could try to use the default storage location, but that would be in /var/lib which feels somewhat wrong for me.
Sadly the patch didn't work. I do have an idea where the problem lies, but don't know how to fix it.
The startscript defines this variable:
CALDIR=/var/lib/$NAME
That's the default path for storing the calendar-files,
which later on is used in the script as location for the calendar file, which is odd, since you can define that in
/etc/radicale/config.
Where I did this:
[storage]
# Folder for storing local collections, created if not present
filesystem_folder = /data/ordnung/radicale/collections
I do find that a bit off. Why define the storage path i the init-script, if there is config file for that?
also the init-sscript has this comment:
# Description: Start/Stop the Radicale CalDAV and CardDAV
# server, configurable via /etc/default/radicale.
and /etc/default/radicale looks like this:
# Defaults for radicale calendar server (sourced from /etc/init.d/radicale)
# If you want radicale to be started as a system service,
# enable it using the command 'update-rc.d radicale enable'
# Options for radicale on startup
# Note that most options can be specified in /etc/radicale/config
RADICALE_OPTS="--daemon"
# Make initscript verbose, override system default
# (Note: This is ONLY about the initscript!)
VERBOSE=yes
If that seems a bit confused, you are right, I am...
Found the right hint, I guess.
https://github.com/Kozea/Radicale/issues/1188
Hadn't time to test it jet. I'll be back.
I just installed radicale (calDAV server) on my home-server. (via apt)
Starting manually works with the config file:
radicale -D -C config
I can the reach the server and generate a calendar, which is accessible from Thunderbird
However the init-script fails me:
root@homeserver# /etc/init.d/radicale start
Starting Radicale CalDAV server : radicale.
root@homeserver# /etc/init.d/radicale status
radicale is not running ... failed
I did enable the service before with:
update-rc.d radicale enable
unfortunately the log-dir stays empty:
/var/log/radicale
I just wonder:
Is there any reason to install Kicad from backports? It's fully present in the standard Devuan Deadalus repos.... and has long been.
The thing with kicad often is, that the very helpfull libraries form external sources often require a newer version, IIRC.
And as is stands backports is kicad 7.x while daedalus is 6.x.
It's not that I necessarily want it, but to knew the path when I get there. (I "think" it was a much bigger gap in debian).
I get, that is the "package by package" way to do it. But kicad has also several other packages like kicad-library, kicad-foodprints and some.
The thought was to have those covered, too without to remember the "-t daedalus-backports" option every time.
Another question I'm not entirely sure of. If there are updates in the backport package, will that be covered by?:
apt update && apt upgrade
I want to install kicad on my daedalus system from backports.
As I'm not used to include backports, I'd like some verification, that this is the/a correct way to do so.
sources list, add backports:
deb http://deb.devuan.org/merged daedalus-backports main non-free contrib
Then generate a preferences file for apt (/etc/apt/preferences):
Package: *
Pin: release a=daedalus
Pin-Priority: 900
Package: *
Pin: release a=daedalus-backports
Pin-Priority: 500
And for have it tidy generate one for kicad:
/etc/apt/preferences.d/kicad
containing:
Package: kicad*
Pin: release a=daedalus-backports
Pin-Priority: 1000
And then the usual
apt-get update
apt-get install kicad<whatever>
As I understand it, the other way would be, to put the kicad part directly into the preferences file.
So is that about right? Do I miss something?
I just updated from chimaera to daedalus.
First annoyance: The new design of Thunderbird (102 vs. 115).
Is there a way to get the look and feel of Thunderbird 102 for 115? I looked into themes, but all howtos seem to be written for older Thunderbird versions..
There is a Theme called "Classic TB2", but that isn't usable beyond version 60, if I understand it correctly.
(This constant change with every new Version of Thunderbird/Firefox is so fckng annoying and I mean that in the annoying way MS windows is annoying. And I really grieve for the times the absence of that annoyance was a major advantage of Linux over MS..)
I just learned that blender has LTS versions.
is there a way to use apt to install a blender LTS version and keep that one updated?
My cubox is now running with fluxbox. Fluxbox with 1 bash window is using 170MB RAM of 2GB. That is quite nice, here are some things I haven't managed to fix so far.
- boot messages are still on the serial console only (so I have unlock the encrypted disc there)
-- how do I get the boot messages on the HDMI and serial?
- the windowmanager has a bit of a lag with mouse movements (IIRC I had an installation of armbian a few years back which was running more smoothly)
-- some packages I need to install for the graphic? (drivers/xorg package?)
- keyboard layout is still at US (the installer seems not to give the choice here or it is somehow eaten by the bit strange resolution of the serial connect via screen).
-- is that something to be fixed with dpkg-reconfigure somehow?
So the overall test for that arm build works quite nice
Which is why real server motherboards come with a serial console that works right from POST and/or IPMI as standard.
Which still don't solve the problem, which is me forgetting to look at that console....
(remotely over ssh means next room n this case)
Three man in a boat had 4 cigarettes but no matches.
How do they manage to smoke?
The threw away one cigarette, making the boat a cigarette lighter.
Sorry, I don't get the point. I didn't change anything after the install. Shouldn't the sources.list work after installation?
Those must be the ones used during install after all.
EDIT: Or do I simply ignore that the release file is not valid? (Yeah me stupid, it is working. I was just confused about the errors).
Starting installs now.
EDIT2: ok, works fine so far. rsync install for testing.
I'm now cloning the sd-card so I can always start over with the minimal install.
So I just found my old cubox and decided to give it a try.
I got images from
https://pkgmaster.devuan.org/devuan/dists/<release>/main/installer-armhf/current/images/netboot/SD-card-images/
And put it together and on an sd-card:
zcat firmware.MX6_Cubox-i.img.gz partition.img.gz > complete_daedalus_cubox.img
cat complete_daedalus_cubox.img > /dev/<sd-card-device>
Then I connected to the micro USB port of the cubox (which delivers output as serial device) and connected to that with screen:
screen /dev/ttyUSB0 115200
With sd-card in the cubox and also connected:
-HDMI
-USB (keyboard, mouse
-Ethernet (RJ45)
Did the complete install on the serial console (incl. full disc encryption)
The reboot to finish installation doesn't work (because arm doesn't seem to have an power of mode.
1st boot (whichis just power up the device) didn't went well, I got stuck at:
"hit any key to abort autostart: 0
=>
on the HDMI screen.
So I did a 2nd boot with the serial console attached like in the install setup, which gave me the passphrase question on the serial console.
It is running at the moment with 2 drawbacks:
No output at HDMI
Updating fails (logged in via ssh):
root@cubox:~# apt-get update
Ign:1 http://deb.devuan.org/merged daedalus InRelease
Hit:2 http://deb.devuan.org/merged daedalus-security InRelease
Get:3 http://deb.devuan.org/merged daedalus-updates InRelease [32.5 kB]
Hit:1 http://deb.devuan.org/merged daedalus InRelease
Reading package lists... Done
E: Release file for http://deb.devuan.org/merged/dists/daedalus-security/InRelease is not valid yet (invalid for another 19698d 11h 36min 13s). Updates for this repository will not be applied.
E: Release file for http://deb.devuan.org/merged/dists/daedalus-updates/InRelease is not valid yet (invalid for another 19699d 14h 36min 36s). Updates for this repository will not be applied.
E: Release file for http://deb.devuan.org/merged/dists/daedalus/InRelease is not valid yet (invalid for another 19694d 3h 11min 36s). Updates for this repository will not be applied.
So nice to have the base install done, but how do I proceed from here?
EDIT: I guess I need to user other repos?
well. slightly related but not in technical sense.
I just updated my little homeserver (remotely) to the last versions of chimaera. After the full-upgrade I did a reboot to have it run with the new kernel and opened a ping to the server to see when it is back online.
Well. It didn't. I have (learned years ago) a monitor and keyboard attached to it. So I got there.
Guess what? Remind yourself that, if full disc encryption in place, you "might" have to type your passphrase to get the system running.... (yeah had 2 very long days before that at work).
Sorry for the delay. Since it is working in the current setup, it is not really urgent.
I wasn't aware that HID device do need more power than a thumb drive. and I get the idea of the powered USB hub to check if it's a low power problem. The ports are of this design:
https://www.performance-pcs.com/media/c … -b-usb.jpg
Which I assumed (maybe wrongly) to be powered from the same line.
I'm quite unsure about investing the time to get hands on a powered USB hub (I might have an old 1.1USB hub lying around which has the option of external power (not sure about the powersupply, though), let alone one for USB3.
As for the BIOS, I guess that wouldn't apply with a chromebox flashed with coreboot. But maybe coreboot uses the same defaults, which I have to look up in the coreboot menu.
comments from me, followed by the dmesg that results from action in comment
## mouse disconnected from front port, reconnect top back port
[Nov14 17:05] usb 1-3: USB disconnect, device number 2
[ +8.930261] hub_port_connect: 5 callbacks suppressed
[ +0.000011] usb usb1-port5: connect-debounce failed
## mouse back front front port
[Nov14 17:07] usb 1-3: new low-speed USB device number 4 using xhci_hc
[ +0.153630] usb 1-3: New USB device found, idVendor=046d, idProduct=c03e, bcdDevice=20.00
[ +0.000015] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ +0.000006] usb 1-3: Product: USB-PS/2 Optical Mouse
[ +0.000004] usb 1-3: Manufacturer: Logitech
[ +0.004152] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C03E.0004/input/input12
[ +0.000106] hid-generic 0003:046D:C03E.0004: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:14.0-3/input0
## keyboard from back buttom port to back top port and back
[Nov14 17:09] usb 1-6: USB disconnect, device number 3
[ +3.305752] usb 1-5: new full-speed USB device number 5 using xhci_hcd
[ +0.128088] usb 1-5: device descriptor read/64, error -71
[ +0.235964] usb 1-5: device descriptor read/64, error -71
[ +0.236013] usb 1-5: new full-speed USB device number 6 using xhci_hcd
[ +0.127984] usb 1-5: device descriptor read/64, error -71
[ +0.236036] usb 1-5: device descriptor read/64, error -71
[ +0.108093] usb usb1-port5: attempt power cycle
[ +0.411887] usb 1-5: new full-speed USB device number 7 using xhci_hcd
[ +0.000189] usb 1-5: Device not responding to setup address.
[ +0.207987] usb 1-5: Device not responding to setup address.
[ +0.207819] usb 1-5: device not accepting address 7, error -71
[ +0.128005] usb 1-5: new full-speed USB device number 8 using xhci_hcd
[ +0.000195] usb 1-5: Device not responding to setup address.
[ +0.207977] usb 1-5: Device not responding to setup address.
[ +0.207820] usb 1-5: device not accepting address 8, error -71
[ +0.000126] usb usb1-port5: unable to enumerate USB device
[ +9.783881] usb 1-6: new low-speed USB device number 9 using xhci_hcd
[ +0.157427] usb 1-6: New USB device found, idVendor=04f2, idProduct=3f41, bcdDevice= 9.21
[ +0.000015] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ +0.000005] usb 1-6: Product: HP Wired Desktop 320K Keyboard
[ +0.000005] usb 1-6: Manufacturer: Chicony
[ +0.005052] input: Chicony HP Wired Desktop 320K Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/0003:04F2:3F41.0005/input/input13
[ +0.057922] hid-generic 0003:04F2:3F41.0005: input,hidraw1: USB HID v1.11 Keyboard [Chicony HP Wired Desktop 320K Keyboard] on usb-0000:00:14.0-6/input0
[ +0.003539] input: Chicony HP Wired Desktop 320K Keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.1/0003:04F2:3F41.0006/input/input14
[ +0.060312] input: Chicony HP Wired Desktop 320K Keyboard System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.1/0003:04F2:3F41.0006/input/input15
[ +0.000346] hid-generic 0003:04F2:3F41.0006: input,hidraw2: USB HID v1.11 Device [Chicony HP Wired Desktop 320K Keyboard] on usb-0000:00:14.0-6/input1
### USB Devuan install stick on upper back port and disconnect again
[Nov14 17:12] usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd
[ +0.255226] usb 2-3: New USB device found, idVendor=1f75, idProduct=0917, bcdDevice= 0.01
[ +0.000014] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ +0.000007] usb 2-3: Product: PenDrive
[ +0.000004] usb 2-3: Manufacturer: Innostor
[ +0.000004] usb 2-3: SerialNumber: 000000000000000014
[ +0.015427] usb-storage 2-3:1.0: USB Mass Storage device detected
[ +0.000316] scsi host4: usb-storage 2-3:1.0
[ +0.000088] usbcore: registered new interface driver usb-storage
[ +0.002718] usbcore: registered new interface driver uas
[ +1.026909] scsi 4:0:0:0: Direct-Access Innostor Innostor 1.00 PQ: 0 ANSI: 6
[ +0.000564] sd 4:0:0:0: Attached scsi generic sg1 type 0
[ +0.000237] sd 4:0:0:0: [sdb] 7864320 512-byte logical blocks: (4.03 GB/3.75 GiB)
[ +0.000131] sd 4:0:0:0: [sdb] Write Protect is off
[ +0.000003] sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ +0.000146] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[ +0.001836] sdb: sdb1 sdb2
[ +0.000276] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ +10.883659] usb 2-3: USB disconnect, device number 2
TL;DR
It is working with one port still not usable for mouse/keyboard. Installing "firmware-linux"
Asus Chromebook CN&" with intel i7 CPU and flashed with coreboot (MrChromebox)
Details:
Installation setup was: Mouse/keyboard at an USB switch on the lower USB port, Installation from USB Stick.
I use the expert install with a minimal system and add my needed software from there.
While choosing the kernel to use I picked the pre-selected. After that there is the option to install all drivers or only those specific for the device. I picked the later. Perhaps this is why the upper port now accepts USB memory sticks fine, but just not any USB HID device. I have it working with the keyboard at the lower port in the back and the mouse at one of the front USB ports.
While this blocks one front port everything else works fine (so far).
Gladly would like to learn how this last bit is fixable.
Thanks a lot. That seems to solve the problem. I haven't tested all setups, so I'll wait until I did that tomorrow.
My first chromebox install isn't going well as it seems.
I did install in the following setup:
2nd Monitor input and an USB switch for keyboard/mouse
-I did choose "only drivers specific for this hardware" (don't know the exact words used)
Which leaves me with working keyboard/mouse only when using the USB devices over the USB switch.
Plus I need to choose the boot option with the "6.1.0-10-amd" kernel (the one running during installation, I guess), with the (default) "6.1.0-13-amd" I won't even get a working keyboard even through the USBswitch.
one hint might be that during package install I get several lines of:
W: Possible missing firmware /lib/firmware/i915/..
EDIT: conclusion in post #5
Well, next fail on my side. If no x is installed a log out an log in won't read the new config. After a reboot keyboard-layout is fine
Well, THAT was a nice fuckup in my list... I had c&p 2 commands, which resulted in a "install" inside the list. sorry for bothering.