On 07/03/18 18:13, Rodney W. Grimes wrote:
Do you get the same failure condition if you use the
wpa_supplicant from the base system?
Same failure with the base wpa_supplicant.
Creating wlan0 by hand helps, but this should happen automatically.
restarting devd service also helps.
I think w
Hi,
I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64 12.0
disk1 ISO (20180628) using UEFI on a Dell PowerEdge R430 by getting this error:
https://imgur.com/a/Idljfhm
The bootonly ISOs seems to show the same error message.
Changing the server to boot via BIOS loads the
Can you post lsdev -v output?
Also, could you try ls command? Like, ls cd0:
Rgds,
Toomas
Sent from my iPhone
> On 4 Jul 2018, at 12:28, Linus Sundqvist wrote:
>
> Hi,
>
> I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64
> 12.0 disk1 ISO (20180628) using UEFI on
Hi,
Sure, while using the 12.0 ISO here is lsdev -v and ls cd0:
https://imgur.com/RmYpg7u
and here is ls cd1:
https://imgur.com/FPsixOw
Med vänlig hälsning/Best Regards
Linus Sundqvist
System Engineer, Loopia AB
On 04/07/18 15:08, Toomas Soome wrote:
> Can you post lsdev -v output?
>
> Also, c
[ Charset UTF-8 unsupported, converting... ]
> On 07/03/18 18:13, Rodney W. Grimes wrote:
> > Do you get the same failure condition if you use the
> > wpa_supplicant from the base system?
>
>
> Same failure with the base wpa_supplicant.
>
> Creating wlan0 by hand helps, but this should happen au
> Hi,
>
> I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64
> 12.0 disk1 ISO (20180628) using UEFI on a Dell PowerEdge R430 by getting this
> error:
> https://imgur.com/a/Idljfhm
>
> The bootonly ISOs seems to show the same error message.
Are you booting from a USB thu
set currdev=cd1:
include /boot/loader.rc
This should give menu/boot.
Rgds,
Toomas
Sent from my iPhone
> On 4 Jul 2018, at 16:25, Linus Sundqvist wrote:
>
> Hi,
>
> Sure, while using the 12.0 ISO here is lsdev -v and ls cd0:
> https://imgur.com/RmYpg7u
>
> and here is ls cd1:
> https://imgur
borg.lerctr.org dumped core - see /var/crash/vmcore.0
Wed Jul 4 11:37:29 CDT 2018
FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #46 r335957: Wed Jul
4 11:08:13 CDT 2018
r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/VT-LER amd64
panic: page fault
GNU gdb (GDB) 8.1 [G
On 07/04/18 18:51, Larry Rosenman wrote:
borg.lerctr.org dumped core - see /var/crash/vmcore.0
Ideas?
https://svnweb.freebsd.org/changeset/base/335958
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-
On Wed, Jul 04, 2018 at 06:57:19PM +0200, Hans Petter Selasky wrote:
> On 07/04/18 18:51, Larry Rosenman wrote:
> > borg.lerctr.org dumped core - see /var/crash/vmcore.0
>
> >
> > Ideas?
> >
> https://svnweb.freebsd.org/changeset/base/335958
Thanks! That fixes it for me.
--
Larry Rosenman
On 07/04/18 07:27, Rodney W. Grimes wrote:
Devd/devmatch is one of the largest changes recently,
it could be something in that code path.
Do you get the if_run.ko module loaded? What does kldstat show
immediately after boot and before you try to "fix" anything with
ifconfig.
It definitely di
> On 07/04/18 07:27, Rodney W. Grimes wrote:
> > Devd/devmatch is one of the largest changes recently,
> > it could be something in that code path.
> >
> > Do you get the if_run.ko module loaded? What does kldstat show
> > immediately after boot and before you try to "fix" anything with
> > ifconf
On 07/04/18 12:00, Rodney W. Grimes wrote:
Just for fun to see if this can clear up your issue add
if_run_load="YES"
to /boot/loader.conf
This doesn't help. In the presence of preloaded if_run.ko wpa_supplicant
still can't initialize wlan0.
Yuri
__
On Wed, Jul 4, 2018 at 11:49 AM, Yuri wrote:
> On 07/04/18 07:27, Rodney W. Grimes wrote:
>
>> Devd/devmatch is one of the largest changes recently,
>> it could be something in that code path.
>>
>> Do you get the if_run.ko module loaded? What does kldstat show
>> immediately after boot and befo
On Wed, Jul 4, 2018, 2:13 PM Kevin Oberman wrote:
> On Wed, Jul 4, 2018 at 11:49 AM, Yuri wrote:
>
> > On 07/04/18 07:27, Rodney W. Grimes wrote:
> >
> >> Devd/devmatch is one of the largest changes recently,
> >> it could be something in that code path.
> >>
> >> Do you get the if_run.ko module
On Wed, Jul 4, 2018 at 12:06 PM, Yuri wrote:
> On 07/04/18 12:00, Rodney W. Grimes wrote:
>
>> Just for fun to see if this can clear up your issue add
>> if_run_load="YES"
>> to /boot/loader.conf
>>
>
>
> This doesn't help. In the presence of preloaded if_run.ko wpa_supplicant
> still can
On Wed, Jul 4, 2018 at 12:17 PM, Warner Losh wrote:
>
>
> On Wed, Jul 4, 2018, 2:13 PM Kevin Oberman wrote:
>
>> On Wed, Jul 4, 2018 at 11:49 AM, Yuri wrote:
>>
>> > On 07/04/18 07:27, Rodney W. Grimes wrote:
>> >
>> >> Devd/devmatch is one of the largest changes recently,
>> >> it could be som
kvm_swap.ksw_devname is defined in as 32 characters. It's easy to
exceed this (e.g. /dev/diskid/DISK-4C441001130129435304p2)
I suppose setting an automatic glabel would be the solution, but how much
hassle would bumping this field cause? I notice that swap with such long
names still actually work
In message <20180703170223.266db...@thor.intern.walstatt.dynvpn.de>,
"O. Hartma
nn" writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Tue, 3 Jul 2018 10:19:57 -0400
> Michael Butler schrieb:
>
> > It seems recent changes (SVN r335873?) may have broken drm-next-kmod ..
> >
> > --
Running these commands makes the boot menu show up, and then takes me to the
BSD installer!
Med vänlig hälsning/Best Regards
Linus Sundqvist
System Engineer, Loopia AB
On 04/07/18 16:50, Toomas Soome wrote:
> set currdev=cd1:
> include /boot/loader.rc
>
> This should give menu/boot.
>
> Rgds,
20 matches
Mail list logo
