Another X server start failure

Having a Raden 240 (sometimes 250) and an older AMDGPU. The older card is deactivated in BIOS but it is been found by the X -configure problem. X server did start one time with -config /root/xorg.conf.new, copied to /etc/X11/ xorg.conf, never got back any "blank black grafic" screen. Rebuilt new

Lockdown adaX numbers to allow booting ?

Hi! We have a system with 10 SATA disks. 2 disks are for the system, 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE - The problem is that if all 10 disks are connected, the system looses

Re: Lockdown adaX numbers to allow booting ?

> On 19. Sep 2019, at 17:57, Kurt Jaeger wrote: > > Hi! > >>> We have a system with 10 SATA disks. 2 disks are for the system, >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: >>> >>> bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE

Re: Lockdown adaX numbers to allow booting ?

On Thu, 19 Sep 2019 18:04:54 +0200 Michael Gmelin wrote: > > On 19. Sep 2019, at 17:57, Kurt Jaeger wrote: > > > > Hi! > > > >>> We have a system with 10 SATA disks. 2 disks are for the system, > >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup > >>> purposes: > >>> >

Re: Lockdown adaX numbers to allow booting ?

On 19/09/19 18:04, Michael Gmelin wrote: > > What about gpart output of the pool drives? > > In general you would create zpools using gptids or gpt labels, not the > devices, so you’re independent of device numbering. The boot loader should > only be installed on drives that contain the boot

Re: Lockdown adaX numbers to allow booting ?

> > I've made a few more details available here: > > https://people.freebsd.org/~pi/host/gpart.txt > What about gpart output of the pool drives? No gpart on the bck pool, raw drives. > In general you would create zpools using gptids or gpt labels, not the > devices, so you???re independent of

Re: Lockdown adaX numbers to allow booting ?

> On 19 Sep 2019, at 17:02, Kurt Jaeger wrote: > > Hi! > > We have a system with 10 SATA disks. 2 disks are for the system, > 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: > > bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE - > > The

Firefox – GtkFileChooserNative – file selection dialogues

Firefox does not use xdg-desktop-portal for file selection dialogs > This patch makes Firefox's GTK3 platform support use > GtkFileChooserNative when available. GtkFileChooserNative > transparently uses the desktop portals interface, which >

Re: Lockdown adaX numbers to allow booting ?

On 19/09/19 18:54, Freddie Cash wrote: > On Thu, Sep 19, 2019 at 9:47 AM Guido Falsi > wrote: > > On 19/09/19 18:04, Michael Gmelin wrote: > > > > What about gpart output of the pool drives? > > > > In general you would create zpools using gptids or

Re: wlan can't discover known networks after relocating

Roaming is done in wpa_supplicant when it's running.That's where the smarts need to be. :( -adrian On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb wrote: > On 19 Sep 2019, at 12:28, Tom Jones wrote: > > Hi, > > freebsd-wireless might be a better list for all this .. > > > > On Tue, Sep 17,

Re: Lockdown adaX numbers to allow booting ?

Hi! > > We have a system with 10 SATA disks. 2 disks are for the system, > > 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: > > > > bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE > > - > > The problem is that if all 10 disks are

Re: Lockdown adaX numbers to allow booting ?

> On 19 Sep 2019, at 18:57, Kurt Jaeger wrote: > > Hi! > >>> We have a system with 10 SATA disks. 2 disks are for the system, >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: >>> >>> bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE

Re: Lockdown adaX numbers to allow booting ?

On Thu, Sep 19, 2019 at 9:47 AM Guido Falsi wrote: > On 19/09/19 18:04, Michael Gmelin wrote: > > > > What about gpart output of the pool drives? > > > > In general you would create zpools using gptids or gpt labels, not the > devices, so you’re independent of device numbering. The boot loader

Re: Lockdown adaX numbers to allow booting ?

> On 19 Sep 2019, at 21:48, Kurt Jaeger wrote: > > Hi! > Also the question is, what you mean with ???system looses track > >>> I interpret the hang during boot as 'it looses track'. So I guess >>> it tries to read the kernel from the wrong drives. > >> no, loader does probe disks

Re: Lockdown adaX numbers to allow booting ?

Hi Kurt! You're probably looking for this: https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html Best regards, Daniel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: Lockdown adaX numbers to allow booting ?

On 19. Sep 2019, at 19:15, Kurt Jaeger wrote: >>> I've made a few more details available here: > >>> https://people.freebsd.org/~pi/host/gpart.txt > >> What about gpart output of the pool drives? > > No gpart on the bck pool, raw drives. > >> In general you would create zpools using gptids

Re: Another X server start failure

Assuming you are running 13.0 Current, and already put the entry in /etc/rc.conf: kld_list="amdgpu" #Yes, no path needed, just "amdgpu" Having done that, try this in /boot/loader.conf hw.syscons.disable=1 # then reboot I'm not the expert here, but the cause is what I might call a

Re: Lockdown adaX numbers to allow booting ?

On Thu, Sep 19, 2019, 20:56 Michael Gmelin wrote: > > > On 19. Sep 2019, at 19:15, Kurt Jaeger wrote: > > >>> I've made a few more details available here: > > > >>> https://people.freebsd.org/~pi/host/gpart.txt > > > >> What about gpart output of the pool drives? > > > > No gpart on the bck

Re: Lockdown adaX numbers to allow booting ?

Hi! > >> Also the question is, what you mean with ???system looses track > > I interpret the hang during boot as 'it looses track'. So I guess > > it tries to read the kernel from the wrong drives. > no, loader does probe disks to see which devices make up the pool and hung > system is not

Re: wlan can't discover known networks after relocating

In message , Johannes Lundberg writes: > --0875960592f275a3 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Tested today with bgscan added. Didn=E2=80=99t connect to home network unti= > l I > manually run ifconfig wlan0 scan. > Again,

Re: wlan can't discover known networks after relocating

On 9/19/19 7:30 PM, Cy Schubert wrote: > In message om> > , Johannes Lundberg writes: >> --0875960592f275a3 >> Content-Type: text/plain; charset="UTF-8" >> Content-Transfer-Encoding: quoted-printable >> >> Tested today with bgscan added. Didn=E2=80=99t connect to home network unti=

Re: wlan can't discover known networks after relocating

On Tue, Sep 17, 2019 at 04:36:28PM +, Poul-Henning Kamp wrote: > > In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.org>, Johannes > Lundber > g writes: > > >For a long time now I have had this problem with iwm and wlan0. Whenever > >I move between work and home it won't

Re: wlan can't discover known networks after relocating

On 19 Sep 2019, at 12:28, Tom Jones wrote: Hi, freebsd-wireless might be a better list for all this .. On Tue, Sep 17, 2019 at 04:36:28PM +, Poul-Henning Kamp wrote: In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.org>, Johannes Lundber g writes: For a long time now

Re: wlan can't discover known networks after relocating

Tested today with bgscan added. Didn’t connect to home network until I manually run ifconfig wlan0 scan. Again, this is with failover lagg. It did however realize I wasn’t at the office anymore and the ssid field was empty in ifconfig output. Sometimes it stays the same long after I leave the

Re: Lockdown adaX numbers to allow booting ?

Hi! > You're probably looking for this: > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html Thanks, that looks like a very useful approach. Will test that when I'm in the housing facility, and report back. -- p...@opsec.eu+49 171 3101372One

Re: wlan can't discover known networks after relocating

So roaming in ifconfig/net80211 is what's set to manual. wpa_supplicant right now does RSSI threshold based roaming. All of the roaming and network preferences when wpa_supplicant is running is done in wpa_supplicant. That's where you have to look. Ideally wpa_supplicant would be triggering

Re: wlan can't discover known networks after relocating

In message <7938e5fa-67da-35fa-10d0-ee3004438...@freebsd.org>, Johannes Lundber g writes: > > On 9/19/19 3:06 PM, Adrian Chadd wrote: > > So roaming in ifconfig/net80211 is what's set to manual. > > > > wpa_supplicant right now does RSSI threshold based roaming. All of the > > roaming and

Re: Lockdown adaX numbers to allow booting ?

On Thu, Sep 19, 2019 at 12:01 PM Andreas Nilsson wrote: > Seems like more of a bios enumeration issue. You should be able to set a > boot order better suited for your setup there. And if that does not work, > just move the sata cables around seems like the most straight forward > solution. > >

Re: wlan can't discover known networks after relocating

On September 19, 2019 8:20:07 AM PDT, Adrian Chadd wrote: >Roaming is done in wpa_supplicant when it's running.That's where the >smarts >need to be. :( > > > >-adrian > > >On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb > >wrote: > >> On 19 Sep 2019, at 12:28, Tom Jones wrote: >> >> Hi, >> >>

Re: wlan can't discover known networks after relocating

On 9/19/19 3:06 PM, Adrian Chadd wrote: > So roaming in ifconfig/net80211 is what's set to manual. > > wpa_supplicant right now does RSSI threshold based roaming. All of the > roaming and network preferences when wpa_supplicant is running is done > in wpa_supplicant. That's where you have to

Re: wlan can't discover known networks after relocating

I've no idea, bgscan is broken with atheros NICs because the driver still doesn't do background scan without dropping frames :( (one of many thing I'd love to fix, but life/time.) please do experiment though! I think wpa_supplicant's roaming logic would benefit from a lot more work. -adrian