Re: FreeBSD 13/stable and zpool upgrade
On 20/02/2021 00:08, Pete French wrote: I suspect there are many variants on this out there! :-) Well, guess what: * http://popeye.lapinbilly.eu/git/?p=zfsinstaller.git;a=blob;f=zfsinstall.sh;h=c63dfa803e1973006a752bd322e083217e97c67a;hb=HEAD by the fact, this one has to be updated for 13-branches. -- David Marec https://reuz.lapinbilly.eu/#/room/#FreeBSD:matrix.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 13/stable and zpool upgrade
Hi, On 19/02/2021 19:24, Kurt Jaeger wrote: > I suspect that your 'zpool upgrade' enabled things that weren't enabled > before. This caused the old boot blocks to no longer work. Correct. That' s definitely the source of the booting issue. > We should be better about upgrading boot blocks, but EFI is kinda new and > kinda different EFI is able to boot any FreeBSD box for a while. The main issue is that the legacy way to upgrade these /bootcode and partcode/ not only does not work, but do bad things. # gpart bootcode -p /boot/gptzfsboot -i 1 ada0s1 will install an old and inappropriate /partcode/. IMO, 'gptzfsboot' should be sweep off along with 'boot1.efifat' ( by calling 'make delete-old') or be built with the right 'BOOTx64.EFI', which actually is`/boot/loader.efi` . -- David Marec http://wiki.fug-fr.org/doku.php?id=start https://diaspora.lapinbilly.eu/ ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 13/stable and zpool upgrade
On 19/02/2021 22:00, Warner Losh wrote: We can't do that. gptzfsboot is for something else that we can't get rid of: BIOS/CMS booting. My bad. I mean 'gptboot.efifat'. root@machine:~ # mdconfig -u 0 -f /boot/gptboot.efifat root@machine:~ # mount -t msdosfs /dev/md0 /mnt root@machine:~ # diff /boot/loader.efi /mnt/efi/boot/BOOTx64.efi Binary files /boot/loader.efi and /mnt/efi/boot/BOOTx64.efi differ -- David Marec http://wiki.fug-fr.org/doku.php?id=start ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 13/stable and zpool upgrade
I have just upgrade one machine from 12-stable to 13-stable. Everything runs fine until the main ZFS pool was upgraded. Then the box stopped booting. Thanks to a FreeBSD-13 Beta2 usb stick, I was able to fix the issue by copying `BOOTx64.efi` from the stick to the hard-drive. Looking to `/boot` to check out for a new EFI boot-loader available, I noticed that `boot1.efifat` was removed, but `gptboot.efifat` is still there. Unfortunately it contains an old version of the boot loader: root@machine:/boot # mdconfig -f gptboot.efifat -u 0 root@machine:/boot # mount -t msdosfs /dev/md0 /mnt root@machine:/boot # ll /mnt/efi/boot/ total 385 -rwxr-xr-x 1 root wheel 393216 Apr 16 2018 BOOTx64.efi* -rwxr-xr-x 1 root wheel 12 Apr 16 2018 startup.nsh* The boot firmware I got from the 13-Beta2 installer is different: -rwxr-xr-x 1 root wheel 894464 Feb 18 21:07 BOOTx64.efi* What did I missed ? -- David Marec http://wiki.fug-fr.org/doku.php?id=start ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
vt(4) driver configuration mismatch ?
The vt (4) man page brings out some inconsistency in its configuration. "sys/dev/vt/vt.h" header file requires the definition of a prepocessor macro called "VT_FB_MAX_WIDTH" while a kernel option defines "VT_FB_DEFAULT_WIDTH" which will be be setup in the file "opt_syscons.h". This last file will be included into `vt` headers. As a result, if one defines 'VT_FB_DEFAULT_WIDTH' as an option in its own kernel configuration file, it will not be actually used by the driver as this one looks up for the "VT_FB_MAX_WIDTH" preprocessor macro. And the man page mentions ... both. Regards, -- David Marec https://diablotins.lapinbilly.eu/doku.php?id=start ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: What was the intention about "jail -e" in the first place ?
Le 16/04/2020 à 16:22, Eugene Grosbein a écrit : >> But,how was "jail -e" intending to be used, actually ? > > "jail -e" mode is used by periodic/weekly/340.noid script to differentiate parts of mounted file trees > belonging to the host and to the configured full-blown jails, no matter started or not. > > This is documentation ambiguity as "jail -e" was not intended to take jail name as additional argument. Oh, I had a deeper look at the "-e" section of the man page where this statement is clear enough.Thanks. > Do you have any real use case this addition? No, not a case in the real world. I was just playing around with jails on a server and tried to get the ip4 field of a specific one to make sure it was set to 'inherit'. P.-S.: However, I had time to write a short patch (attached to the email) to make it work with a jail list as arguments. ( and that do not change the header file anymore ) This one also add a dedicated line for the "-e" command and fix few typos in the usage() output. // To improve the lookup in the nested loop, I first called "TAILQ REMOVE" on jailnames when found but this would produce errors if the user add more than once the same name in the list .// Regards, -- David Marec https://diablotins.lapinbilly.eu/doku.php?id=jails:zfs ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
What was the intention about "jail -e" in the first place ?
The manpage and usage output doesn't match.
The manpage tells us that this option should be used alone on the
command line, as any other command will be discarded.
The usage ouput does not mention the "-r" flag but "cmr" (with a typo).
Both suggest that the user can request information about one single
jail, or all the jails using a wildcard or no other argument.
Well, looking at the code, it sounds that the only way to make it work
is to use it alone on the command line, and their is no way get
information about a single jail.
Attached is a short patch to get information about one single jail or
all jails (wildcards or empty).
But,how was "jail -e" intending to be used, actually ?
--
David Marec
https://lapinbilly.eu/
Index: jail.c
===
--- jail.c (revision 359745)
+++ jail.c (working copy)
@@ -282,16 +282,12 @@
? NULL : "false");
}
}
- } else if (op == JF_STOP || op == JF_SHOW) {
- /* Just print list of all configured non-wildcard jails */
- if (op == JF_SHOW) {
- load_config();
- show_jails();
- exit(0);
- }
+ } else if (op == JF_STOP ) {
+
/* Jail remove, perhaps using the config file */
if (!docf || argc == 0)
usage();
+
if (!Rflag)
for (i = 0; i < argc; i++)
if (strchr(argv[i], '='))
@@ -300,6 +296,17 @@
(!strcmp(cfname, "-") || stat(cfname, ) == 0)))
load_config();
note_remove = docf || argc > 1 || wild_jail_name(argv[0]);
+ } else if(op == JF_SHOW) {
+ /* Just print list of all configured non-wildcard jails */
+ if (op == JF_SHOW && (argc==0|| wild_jail_name(argv[0]))) {
+ load_config();
+ show_jails();
+ exit(0);
+ }
+
+ if(argc>1)
+ usage();
+ load_config();
} else if (argc > 1 || (argc == 1 && strchr(argv[0], '='))) {
/* Single jail specified on the command line */
if (Rflag)
@@ -474,6 +481,9 @@
dep_done(j, 0);
break;
+ case JF_SHOW:
+ print_jail(stdout, j, 0, 0);
+ break;
case JF_STOP:
case JF_RESTART:
if (j->comparam == NULL) {
@@ -1040,8 +1050,8 @@
(void)fprintf(stderr,
"usage: jail [-dhilqv] [-J jid_file] [-u username] [-U username]\n"
"-[cmr] param=value ... [command=command ...]\n"
- " jail [-dqv] [-f file] [-e separator] -[cmr] [jail]\n"
- " jail [-qv] [-f file] -[rR] ['*' | jail ...]\n"
+ " jail [-dqv] [-f file] [-e separator] [-cmr] [jail]\n"
+ " jail [-qv] [-f file] [-rR] ['*' | jail ...]\n"
" jail [-dhilqv] [-J jid_file] [-u username] [-U username]\n"
"[-n jailname] [-s securelevel]\n"
"path hostname [ip[,...]] command ...\n");
Index: jailp.h
===
--- jailp.h (revision 359745)
+++ jailp.h (working copy)
@@ -69,7 +69,7 @@
#define JF_FROM_RUNQ 0x0800 /* Has already been on the run queue */
#define JF_SHOW 0x1000 /* -e Exhibit list of configured jails */
-#define JF_OP_MASK (JF_START | JF_SET | JF_STOP)
+#define JF_OP_MASK (JF_START | JF_SET | JF_STOP | JF_SHOW)
#define JF_RESTART (JF_START | JF_STOP)
#define JF_START_SET (JF_START | JF_SET)
#define JF_SET_RESTART (JF_SET | JF_STOP)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: stable/11 r329462 - Meltdown/Spectre MFC questions
On 18.02.2018 17:50, Shawn Webb wrote: Strange thing is that tweaking `hw.ibrs_disable` has no effect on `hw.ibrs_active` on my side. Did you install the latest Intel microcode update? Hum, I thought I did, but I don't know actually if the following is the latest revision of the microcode: #cpucontrol -u -v /dev/cpuctl0 cpucontrol: skipping /usr/local/share/cpucontrol/m32306c3_0022.fw of rev 0x22: up to date -- David Marec https://lapinbilly.eu/ ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: stable/11 r329462 - Meltdown/Spectre MFC questions
On 17.02.2018 20:47, Jeremy Chadwick wrote: hw.ibrs_disable - Description: Disable Indirect Branch Restricted Speculation - Loader tunable and sysctl tunable (read-write) - Integer - Default value: unsure. Variable declaration has 1 but SYSCTL_PROC() macro has 0. Strange thing is that tweaking `hw.ibrs_disable` has no effect on `hw.ibrs_active` on my side. -- David Marec https://lapinbilly.eu/ ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 11.1-BETA3 Now Available
Le 24.06.2017 à 18:21, Glen Barber a écrit : > > A list of changes since 11.1-RELEASE are available in the stable/11 > release notes: > > https://www.freebsd.org/relnotes/11-STABLE/relnotes/article.html > > Please note, the release notes page is not yet complete, and will be > updated on an ongoing basis as the 11.1-RELEASE cycle progresses. > There is a mismatch between the description and the related commit, General Network Changes topic: > The TCP stack has been changed to use the estimated RTT instead of > timestamps for receive buffer auto resizing. > [r317386] r317386 fixed an outbound issue within 'lib/libutil/humanize_number.c' and does not sounds related to the TCP Stack. -- David Marec ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic in nvidia module
On Mon, Mar 27, 2017 at 11:39:28AM -0700, Larry Rosenman wrote: > On 3/27/17, 11:34 AM, "Jonathan Chen" <owner-freebsd-sta...@freebsd.org on > behalf of j...@chen.org.nz> wrote: Thanks Larry & Jonathan, rebuidling the nvidia driver against the new kernel solved the issue. -- David Marec https://lapinbilly.eu ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Panic in nvidia module
greeting,
Tracking 11-Stable,
- now : 316014, -
kernel panics on 'page fault' within nvidia module.
The system boots and works well ( 'vt' in graphic mode) until xorg starts.
-
I had to rollback to a r315900 kernel to make xorg run again.
Here is a dump:
=== kgdb kernel.debug /var/crash/vmcore.last ==
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x4
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x82c76964
stack pointer = 0x28:0xfe0235b8e4b0
frame pointer = 0x28:0xfe0235b8e4b0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 3
current process = 876 (Xorg)
trap number = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0x80a8c397 at kdb_backtrace+0x67
#1 0x80a496c6 at vpanic+0x186
#2 0x80a49533 at panic+0x43
#3 0x80eadf52 at trap_fatal+0x322
#4 0x80eae11c at trap_pfault+0x1bc
#5 0x80ead7d0 at trap+0x280
#6 0x80e92681 at calltrap+0x8
#7 0x82c434ef at _nv017563rm+0x1f
Uptime: 1h3m54s
Dumping 489 out of 8082 MB:..4%..14%..23%..33%..43%..53%..63%..72%..82%..92%
Reading symbols from /boot/kernel/zfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/zfs.ko.debug...done.
done.
Loaded symbols for /boot/kernel/zfs.ko
Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from
/usr/lib/debug//boot/kernel/opensolaris.ko.debug...done.
done.
Loaded symbols for /boot/kernel/opensolaris.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linux.ko.debug...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/linux_common.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linux_common.ko.debug...done.
done.
Loaded symbols for /boot/kernel/linux_common.ko
Reading symbols from /boot/kernel/linux64.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linux64.ko.debug...done.
done.
Loaded symbols for /boot/kernel/linux64.ko
Reading symbols from /boot/modules/nvidia-modeset.ko...done.
Loaded symbols for /boot/modules/nvidia-modeset.ko
Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
#0 doadump (textdump=) at pcpu.h:222
222 __asm("movq %%gs:%1,%0" : "=r" (td)
(kgdb) backtrace
#0 doadump (textdump=) at pcpu.h:222
#1 0x80a49256 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:366
#2 0x80a49700 in vpanic (fmt=, ap=optimized out>) at /usr/src/sys/kern/kern_shutdown.c:759
#3 0x80a49533 in panic (fmt=) at
/usr/src/sys/kern/kern_shutdown.c:690
#4 0x80eadf52 in trap_fatal (frame=0xfe0235b8e3f0, eva=4)
at /usr/src/sys/amd64/amd64/trap.c:801
#5 0x80eae11c in trap_pfault (frame=0xfe0235b8e3f0,
usermode=0) at /usr/src/sys/amd64/amd64/trap.c:658
#6 0x80ead7d0 in trap (frame=0xfe0235b8e3f0) at
/usr/src/sys/amd64/amd64/trap.c:421
#7 0x80e92681 in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:236
#8 0x82c76964 in os_get_euid () from /boot/modules/nvidia.ko
#9 0x82c434ef in _nv017563rm () from /boot/modules/nvidia.ko
#10 0xf80021881400 in ?? ()
#11 0x82ba3330 in _nv004904rm () from /boot/modules/nvidia.ko
#12 0x in ?? ()
Current language: auto; currently minimal
=== kgdb kernel.debug /var/crash/vmcore.last ==
Thanks
--
David Marec
https://lapinbilly.eu/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [ZFS] files in a weird situtation
On 18.12.2016 01:38, Adam Vande More wrote:
I am unable to understand what your intent is here. If you wish to
delete it, you can do:
find . -inum 10552574 -exec rm {} \;
It fails on «No such file or directory».
This file missing, not much works.
I have installed a copy into `/usr/lib` to make the system run again.
So, I can't install a new world: `install -C` fails in the same way.
--
David Marec
https://lapinbilly.eu
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [ZFS] files in a weird situtation
On 17.12.2016 22:15, Brandon Allbery wrote: You have a directory entry pointing at a freed inode (or zfs equivalent). ZFS may have mapped this inode that points to nowhere. That makes sense. In this case, what should be the best solution to clean this up ? As I said, as far scrubbing the pool didn't show any error, it didn't solve the issue. -- David Marec https:lapinbilly.eu ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[ZFS] files in a weird situtation
[I had first posted onto the Forum about this issue]
Two months ago,
- next to a call to |`||delete-old-libs`| or `install world`, I don't
really know -
my box that is following FreeBSD-11 Stable ran into a weird situation.
A set of files, especially `/lib/libjail.so.1` are in both states
`existing` and `not existing`:
I means:
david:~>cp ~david/libjail.so.1 /lib
cp: /lib/libjail.so.1: File exists
But:
david:~>ls /lib/libjail.so.1
ls: /lib/libjail.so.1: No such file or directory
david:~>find /lib -name "libjail.so.1" -print
/lib/libjail.so.1
david:~>find /lib -name "libjail.so.1" -ls
find: /lib/libjail.so.1: No such file or directory
With deeper investigation, the file is in fact mapped to an `inode`:
root@dmarec:~ # ls -di /lib
13 /lib
root@dmarec:~ # zdb - zroot/ 13 | grep libjail.so.1
libjail.so.1 = 10552574 (type: Regular File)
Which fails with `zdb` on:
root@dmarec:~ # zdb - zroot/ 10552574
Dataset zroot [ZPL], ID 21, cr_txg 1, 114G, 2570002 objects,
rootbp
DVA[0]=<0:b97d6ea00:200> DVA[1]=<0:1c212b0400:200> [L0 DMU objset]
fletcher4 lz4 LE contiguous unique double size=800L/200P
birth=3852240L/3852240P fill=2570002
cksum=17b78fb7e4:7c87a526a07:16251edfaae60:2ce0c5734ccf2f
Object lvl iblk dblk dsize lsize %full type
zdb: dmu_bonus_hold(10552574) failed, errno 2
`stat (2)` returns ENOENT when checking for the file:
david:~>truss stat -L /lib/libjail.so.1
...
stat("/lib/libjail.so.1",0x7fffe7e8) ERR#2 'No such
file or
directory'david:~>truss stat -L /lib/libjail.so.1
A pass with `zfs scrub` didn't help.
Any clue is welcome. What's that `dmu_bonus_hold` stands for ?
--
David Marec
https://lapinbilly.eu
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Cleaning temporary build tree failed
Hi guys. Since the release of FreeBSD 8.2, building world fails on the following error: -- david:/home/david#cd /usr/src david:/usr/src#make -j4 buildworld make kernel -- World build started on Sat Apr 9 09:16:50 CEST 2011 -- -- Rebuilding the temporary build tree -- rm -rf /usr/obj/usr/src/tmp rm -rf /usr/obj/usr/src/lib32 rm: /usr/obj/usr/src/lib32/usr/lib32/libc.so.7: Operation not permitted rm: /usr/obj/usr/src/lib32/usr/lib32/libcrypt.so.5: Operation not permitted rm: /usr/obj/usr/src/lib32/usr/lib32/libthr.so.3: Operation not permitted rm: /usr/obj/usr/src/lib32/usr/lib32/librt.so.1: Operation not permitted rm: /usr/obj/usr/src/lib32/usr/lib32: Directory not empty rm: /usr/obj/usr/src/lib32/usr: Directory not empty rm: /usr/obj/usr/src/lib32: Directory not empty *** Error code 1 1 error *** Error code 2 1 error david:/usr/src#ls -lo /usr/obj/usr/src/lib32/usr/lib32/ total 1262 -r--r--r-- 1 root wheel schg 1143468 22 mar 21:19 libc.so.7 -r--r--r-- 1 root wheel schg 32060 22 mar 21:19 libcrypt.so.5 -r--r--r-- 1 root wheel schg 16412 22 mar 21:22 librt.so.1 -r--r--r-- 1 root wheel schg 76412 22 mar 21:20 libthr.so.3 -- Im a running FreeBSD 8.2-Stable for amd64. So, before building world, i have to change the flags for the files above. There was no need to do this before. Any idea to get rid of this issue ? -- Cordialement, -- David Marec: http://user.lamaiziere.net/david/Site/ http://www.freebsd.org/fr/ http://www.diablotins.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Cleaning temporary build tree failed
Damien Fleuriot a écrit : I experience no such problems on *many* boxes running 8.2 at work here. You will want to: chflags -R noschg /usr/obj/ cd /usr/src make -j4 buildworld make buildkernel You are right, that 's what i have to do *each time* i want to proceed to a rebuild world. Therefore, the issue is why; moreover, why since the 8.2 release ? Is there any clue to avoid to change these flags, previously to a 'rebuild world' -- Cordialement, -- David Marec: http://user.lamaiziere.net/david/Site/ http://www.freebsd.org/fr/ http://www.diablotins.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: EEEPC and FreeBSD 7.2
Le Monday 11 May 2009 12:35:13 Henri-Pierre Charles, vous avez écrit : Hello, On Fri, May 8, 2009 at 11:47 AM, David Marec david.ma...@davenulle.org wrote: I am trying to use an EEEPC 701 as a diskless station, running FreeBSD 7. Great mini machine ! I agree. This one is owned by my wife, who does not want to change the system that was shipped with it ( Xandros). The EEPC station boots well with PXE then runs the kernel, but the only network card that is recognized is the wireless one (ath0). I read that the wired NIC ( ae? ) has been committed to HEAD; is there any way to make it work on 7-STABLE ? It works out of the box with 7.2 You hust have to add if_ae_load=YES in your /boot/loader.conf I built a kernel that included this driver and the EEEPC is now working quite well as a diskless station. But i have to launch Xorg locally. It doesn't start on XDMCP mode and i didn't found yet what is wrong with this. /I think i will start another thread on a Xorg dedicated list about this point and the touchpad configuration./ -- http://david.marec.free.fr/ http://www.freebsd.org/fr/ http://www.diablotins.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
EEEPC and FreeBSD 7.2
hi! I am trying to use an EEEPC 701 as a diskless station, running FreeBSD 7.2. The EEPC station boots well with PXE then runs the kernel, but the only network card that is recognized is the wireless one (ath0). I read that the wired NIC ( ae? ) has been committed to HEAD; is there any way to make it work on 7-STABLE ? -- http://david.marec.free.fr/ http://www.freebsd.org/fr/ http://www.diablotins.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE Available
Le Thursday 28 February 2008 13:18:30 Kris Kennaway, vous avez écrit : freebsd update requires a known state to upgrade from, i.e. so it can apply the right set of diffs to bring your system from one known state to another. This basically means previously installed from the release media and only updated using freebsd update. I have installed FreeBSD from a «release media» a long time ago ( RELENG_5 ), and, of course, updated it from the sources. so, now, there is no way to use this script to update my box ? If you previously did an update using cvsup to go from 6.3-RELEASE to some unknown point in 6.3-STABLE then you can just do another cvsup to go to 7.0 :) i did; i am running 7.0-STABLE now. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE Available
Le Wednesday 27 February 2008 23:32:55 Ken Smith, vous avez écrit : http://www.freebsd.org/releases/7.0R/announce.html On behalf of the FreeBSD Project thanks for your interest in FreeBSD. We hope you enjoy the new release. I am trying to use the freebsd-update script for the first time. And this script fails on: --- david# sh ./freebsd-update.sh -f freebsd-update.conf -r 7.0-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching public key from update1.FreeBSD.org... failed. No mirrors remaining, giving up. --- How to override this step ? Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RELEASE Available
Le Thursday 28 February 2008 12:32:28 David Marec, vous avez écrit : I am trying to use the freebsd-update script for the first time. sh -x freebsd-update.sh -f freebsd-update.conf -r 7.0-RELEASE upgrade -- + fetch -q http://update1.FreeBSD.org/6.3-STABLE/i386/pub.ssl + true + [ -r pub.ssl ] -- «6.3-STABLE» folder does not exist on the update server !? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Display freezes since the last update
hello, Since i updated my FreeBSD 6.3 box yesterday, the display hangs up while KDE is runnning, screen and keyboard are off, i stop the system by the poweroff push-button. I guess this occured when the screensaver or power management was launched. Nov 1 08:39:53 david kernel: pid 1126 (rarian-sk-get-cl), uid 1001: exited on signal 11 (core dumped) I can't disable the KDE's screensaver because it s buggy. regards, -- David Marec www.diablotins.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
