Radeon HD 2400 PRO, DRI setup problem
Hi all, I here reproduce the mail I sent to freebsd-x11 for which I received no reply. I hope I have more luck in questions@ I'm having quite a few problems setting DRI up on my system. I'm running 9.0-RELEASE on amd64 using GENERIC kernel. I recompiled the radeon kernel module with WITHOUT_NOUVEAU="YES" just to see if I had more luck. This is some information about my system: pciconf -lv: vgapci0@pci0:4:0:0: class=0x03 card=0x10411462 chip=0x94c31002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'RV610 video device [Radeon HD 2400 PRO]' class = display subclass = VGA Using GENERIC kernel for 9.0-RELEASE on amd64. radeon kernel driver compiled with WITHOUT_NOUVEAU. /usr/ports/graphics/dri properly configured and installed. I followed instructions at http://dri.freedesktop.org/wiki/DriTroubleshooting, but I found that dmesg | grep agp doesn't return anything so I suppose this is a bad sign. I know agp subsystem has been in the default kernel for a while. I can also load the radeon module and I get the /dev/dri/card0 device node. Using the radeon driver for Xorg results in a system hang after a blank screen and the monitor going to sleep. Only if I set DRI to false and I _do not_ load the radeon driver I can get my X server running though it is quite slow. The output of glxinfo | grep OpenGL is: OpenGL vendor string: Mesa Project OpenGL renderer string: Software Rasterizer OpenGL version string: 2.1 Mesa 7.6.1 OpenGL shading language version string: 1.20 OpenGL extensions: So basically I don't know how to get the card working. It works in Linux with the Xorg's radeon driver so I suppose I have some misconfiguration around but I can not figure it out. Any help would be appreciated. Thanks in advance. PS: Please, CC me as I'm not subscribed to the list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Thu, 20 Dec 2012 05:13:39 +0100, Ralf Mardorf wrote: > Thank you Erich :) > > ok, so "FreeBSD release" is the version of the kernel and not a > labelling for the collection of all the software. No. The version specification refers to the version of the kernel _and_ the operating system (which form a unit maintained by the FreeBSD team). Those typically have to be in sync. Depending on what branch you follow, this can be: a) a static release number, e. g. 8.2-RELEASE b) a release, enriched by security updates, e. g. 8.2-RELEASE-p2 c) a stable version, e. g. 8-STABLE of a specific date (this is "work in progress" that has been considered working) d) a development version, e. g. 10-CURRENT (this may or _may not_ even compile, it's experimental) Depending on what branch you follow, updating techniques may differ: freebsd-update (the binary way) can be used for a) and b); for c) and d) you update from source. > For Linux major distros there usually is a labelling for the collection > of the software, independent of the kernel version. Linux doesn't know the differentiation between "the operating system" (consisting of the OS kernel and the OS programs, the "world" in FreeBSD terminology) and "everything else" (third party contributed applications, in FreeBSD provided by the ports collection). > On Linux I usually install binaries for the base system and desktop > environment, but for important software, in my case it's audio, > compiling from source is very important. The ports collection allows both binary installation and by source. There are tools that help managing them. Note that unlike Linux, FreeBSD draws a line between "the OS" and "installed applications" - you need to install and update them separately. This is a big benefit as a failed program installation can never harm your OS. > The author of the snd_hdspe driver for FreeBSD seems to need testers. It > seems to be that nobody ever tested if ADAT is working and I'll test it. > OTOH I suspect bug fixes for the driver have to be added by recompiling > the kernel or at least the driver for the kernel, so I still could use > binaries for the applications. Of course. The separation I've mentioned explicitely allows this method to function. What you need to do is to update your sources in /usr/src and then recompile the kernel and, if required, the world, as explained in /usr/src/Makefile's comment header. > Since audio on FreeBSD seems to be a niche, I wonder if it's more > promising, to go the source or to go the binary rout. I'd say: Use the source Luke. :-) Experimental changes and "bleeding edge updates" are typically a domain of source installations. With svn you can track smallest changes very quickly, apply them to your system and have a test run. Doesn't work? Undo the change, or wait for a new version. > I suspect if it's impossible or at least less good to mix binaries and > from source build software for FreeBSD, I should chose to build from > source. Basically there is no problem. One thing you have to pay attention to is dependency versions, but that's what port management tools like portmaster can do for you. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Thank you Erich :) ok, so "FreeBSD release" is the version of the kernel and not a labelling for the collection of all the software. For Linux major distros there usually is a labelling for the collection of the software, independent of the kernel version. On Linux I usually install binaries for the base system and desktop environment, but for important software, in my case it's audio, compiling from source is very important. The author of the snd_hdspe driver for FreeBSD seems to need testers. It seems to be that nobody ever tested if ADAT is working and I'll test it. OTOH I suspect bug fixes for the driver have to be added by recompiling the kernel or at least the driver for the kernel, so I still could use binaries for the applications. Since audio on FreeBSD seems to be a niche, I wonder if it's more promising, to go the source or to go the binary rout. I suspect if it's impossible or at least less good to mix binaries and from source build software for FreeBSD, I should chose to build from source. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Hi, On Wed, 19 Dec 2012 18:09:16 +0100 Ralf Mardorf wrote: > On Wed, 2012-12-19 at 10:14 -0600, Antonio Olivares wrote: > > You may also use at your discretion the portmaster tool? It works > > very well and a nice example is given by W. Block: > > > > http://www.wonkity.com/~wblock/docs/html/portupgrade.html > > Thank you Antonio :) > > because I can't install FreeBSD by the 9.0 DVD, for what reason ever > this doesn't work, I installed it by the 8.3 DVD and will now make a > release upgrade. IIUC a release upgrade will rebuild everything, hence one way was already shown to you. The other route would lead you via the sources. I prefer the sources over the binary upgrade. If the new kernel will not boot, you can boot the old kernel which will then be under kernel.old. > there should be no dependency issues. My FreeBSD 8.3 is a fresh Dependencies come in when it comes to ports. I would like to suggest the you first make a decision whether you want the ports as binaries or via source. Both routes work. Only the sources allow you to specify options. I would also recommend to download first the sources or the binaries and start the upgrade only after all files are downloaded. As you already know, portupgrade is the tool of choice here. If you have problems with 9.1, you might consider a move to 10. I have done this too for the same reason when I got a new machine which has had problems with 9.0. 10.0 is not recommended for production. Me and many other still do this. You might will run occassionally into problems. So, think twice before doing this. > install, I only set up PPPoE, anything else is default. > IIUC I need to take care about it to keep dependencies up to date, > when I don't upgrade the complete release, but just upgrade some > software. > > So, can I upgrade from 8.3 to 9.0, without taking care about > dependencies and take care about the link, when 9.0 is installed, > instead of doing it right now? > FreeBSD and the ports have 'nothing' to do with each other. You have to upgrade FreeBSD first and then upgrade the ports. Most likely, all applications will continue to work without upgrade. If I remember right, even after an upgrade from 8.3 to 10.0 on one of my machines, all applications continued to work. I still upgraded them as fast as possible. > My apologize for the terrible English, I'm in a hurry, but wanted to > rely immediately and this makes broken English not better ;). Do not worry about this here. I think, while you have been pretty clear on the rest, the last line does not make real sense to me. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Atheros, AirPort Extreme, WPA issues
On Dec 19, 2012, at 7:39 PM, Christopher Sean Hilton wrote: > I'm having issues using an ath(4) AR5212 card to connect FreeBSD 8.2 to the > Internet via an Apple AirPort Extreme with WPA protection. Basically the > ath/wlan combo associates to the network and can send packets fine but > receiving fails. The is seen when you try to negotiate a DHCP lease. I have > this combo working with a Novatel MiFi and an Airport Express but the extreme > fails. > > If you have this combo working I'd love to exchange an email or so. I can > provide my configs when I get back to my test rig. > Sorry about replying to my own post. Please ignore this thread. I thought that the much more detailed post got lost due to an error from mutt. -- Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Atheros, AirPort Extreme, WPA issues
I'm having issues using an ath(4) AR5212 card to connect FreeBSD 8.2 to the Internet via an Apple AirPort Extreme with WPA protection. Basically the ath/wlan combo associates to the network and can send packets fine but receiving fails. The is seen when you try to negotiate a DHCP lease. I have this combo working with a Novatel MiFi and an Airport Express but the extreme fails. If you have this combo working I'd love to exchange an email or so. I can provide my configs when I get back to my test rig. Thanks Chris Sent from my iPhone ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ath0 + wpa/wpa2 + apple airport extreme = no joy.
I posted on a similar subject last year but in the end it turned out
to be irrelevant. I'm trying to get the combination of:
a Soekris Net4511,
FreeBSD 8-STABLE from Dec 2011,
an Atheros AR5BMB-44 wifi interface (identified as AR5212 in dmesg),
an Apple Airport Extreme (about 2010 vintage) with WPA/WPA2 security,
to all play nicely. To start with I plan to look at the change logs
for the wpa_supplicant suite to see if there were changes from last
December to now. I will probably just upgrade this box to a later
vintage of 8-STABLE. Still, hit me with a cluebat if this problem got
fixed between December, 2011 and now.
Anyhow, no matter what I've done, the result is the same:
The atheros/wlan combo associates to my wireless network;
The dhcp client on the soekris sends a request to the dhcp
server. The dhcp server receives the negotiation and tries to
offer a lease but the soekris never receives a reply;
I've confirmed this by running tcpdump on the dhcp server where I've
seen the requests arrive with the atheros' mac address and I've seen
the replies go back out of the dhcp server but either the atheros
isn't listening or the Airport Extreme isn't forwarding the traffic. I
haven't sniffed the wifi to see if the Airport Extreme just isn't
forwarding the reply or if the atheros isn't receiving it properly.
I can convince this combination of hardware to work if I change the
network security on the airport extreme from WPA/WPA2 to None.
The configuration that I feel should make the atheros work with the
Airport Extreme works just fine with my 2010 vintage Airport
Express. The Express and the Extreme are basically creating the same
network. The Extreme is on 2.4GHz channel 11, the Express on 2.4GHz 1.
The reason I have both so you are always near an access point.
I can get the atheros to work with WPA2 on my Mifi 4082.
As a new data point, the combination of an Intel 2200bg + WPA works
with the Airport Extreme.
I've posted my configs after my signature if you want to look and I
can provide more information if you need it.
My hope in posting this is to try and figure out what's up with the
atheros or the Airport Extreme that it isn't working in this
configuration. If anyone has an atheros card working with WPA/WPA2 and
an Apple Airport Extreme I'd love any assistance you'd be willing to
give me with the configuration.
Thanks for any help you can provide.
--
-- Chris
"There will be an answer, Let it be."
e: chris -at- vindaloo -dot- com
This is the hacked /etc/rc.conf to work with the Intel card:
...
wpa_supplicant_enable="YES"
## wlans_ath0="wlan0"
wlans_iwi0="wlan0"
ifconfig_wlan0="WPA DHCP"
...
Here's my abridged /etc/wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
## Airport Extreme
network={
ssid="FooBarBaz"
bssid=f8:1e:df:xx:xx:xx
psk=""
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
priority=12
}
## Airport Express
network={
ssid="FooBarBaz"
bssid=00:1f:f3:xx:xx:xx
psk=""
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
priority=10
}
## Mifi 4082
network={
ssid="FooBarBaz-Mobile"
psk=""
priority=0
}
Finally, here's the result of ifconfig on wlan0/iwi0 associated and
working with the Airport Extreme:
ryloth chris $ ifconfig iwi0
iwi0: flags=8843 metric 0 mtu 2290
ether 00:15:00:xx:xx:xx
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
status: associated
ryloth chris $ ifconfig wlan0
wlan0: flags=8843 metric 0 mtu 1500
ether 00:15:00:xx:xx:xx
inet 10.59.145.87 netmask 0xfe00 broadcast 10.59.145.255
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
status: associated
ssid FooBarBaz channel 11 (2462 MHz 11g) bssid f8:1e:df:xx:xx:xx
country US authmode WPA2/802.11i privacy ON deftxkey UNDEF
TKIP 3:128-bit txpower 0 bmiss 24 scanvalid 60 protmode CTS wme
roaming MANUAL
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Can't get start_precmd to do *anything*
On 19/12/2012, Paul Schmehl wrote:
> --On December 19, 2012 10:47:56 PM + Chris Rees
> wrote:
>
>> On 19/12/2012, Paul Schmehl wrote:
>>> I'm working on an rc.d init script for a port, and I am clearly in need
>>> of a clue.
>>>
>>> I have a daemon that requires that a FIFO exist before it will start.
>>> The FIFO is defined in the daemon's conf file. I could just point that
>>> out to the user using "warn", but I thought it would be nicer to simply
>>> take care of it programmatically.
>>>
>>> So I created this:
>>>
>>> start_precmd="${name}_ck4fifo()"
>>
>> Is this a copy/paste error, or is your function actually called
>> _ck4fifo or _ch4fifo?
>>
>
> Both, but I fixed it and nothing changed.
>
>>> ${name}_ch4fifo()
>>
>> I'm surprised sh isn't choking on this, you can't use ${name} in a
>> function name. Indirecting it is a waste of processing time, if I'm
>> honest; just use
>>
>> start_precmd=pads_agent_prestart
>>
>> pads_agent_prestart()
>> {
>> do_something
>> }
>>
>
> OK, I've done that. Still no change. {{{sigh}}}
>
> Here's the current invocation:
>
> start_precmd="pads_agent_ck4fifo()"
Lose the parentheses in the above line (this isn't C :) )
Chris
> pads_agent_ck4fifo()
> {
> . ${pads_agent_conf}
> if [ ! -p ${PADS_FIFO} ]; then
> `/usr/bin/mkfifo ${PADS_FIFO}`
> fi
> echo "Checking for ${PADS_FIFO}"
> if [ -p ${PADS_FIFO} ]; then
> echo "${PADS_FIFO} exists."
> return 0
> else
> echo "I tried to create ${PADS_FIFO} and failed."
> echo "You will need to create it manually before starting
> ${name}."
> return 1
> fi
> }
>
> --
> Paul Schmehl, Senior Infosec Analyst
> As if it wasn't already obvious, my opinions
> are my own and not those of my employer.
> ***
> "It is as useless to argue with those who have
> renounced the use of reason as to administer
> medication to the dead." Thomas Jefferson
> "There are some ideas so wrong that only a very
> intelligent person could believe in them." George Orwell
>
>
--
Chris Rees | FreeBSD Developer
cr...@freebsd.org | http://people.freebsd.org/~crees
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Can't get start_precmd to do *anything*
--On December 19, 2012 10:47:56 PM + Chris Rees
wrote:
On 19/12/2012, Paul Schmehl wrote:
I'm working on an rc.d init script for a port, and I am clearly in need
of a clue.
I have a daemon that requires that a FIFO exist before it will start.
The FIFO is defined in the daemon's conf file. I could just point that
out to the user using "warn", but I thought it would be nicer to simply
take care of it programmatically.
So I created this:
start_precmd="${name}_ck4fifo()"
Is this a copy/paste error, or is your function actually called
_ck4fifo or _ch4fifo?
Both, but I fixed it and nothing changed.
${name}_ch4fifo()
I'm surprised sh isn't choking on this, you can't use ${name} in a
function name. Indirecting it is a waste of processing time, if I'm
honest; just use
start_precmd=pads_agent_prestart
pads_agent_prestart()
{
do_something
}
OK, I've done that. Still no change. {{{sigh}}}
Here's the current invocation:
start_precmd="pads_agent_ck4fifo()"
pads_agent_ck4fifo()
{
. ${pads_agent_conf}
if [ ! -p ${PADS_FIFO} ]; then
`/usr/bin/mkfifo ${PADS_FIFO}`
fi
echo "Checking for ${PADS_FIFO}"
if [ -p ${PADS_FIFO} ]; then
echo "${PADS_FIFO} exists."
return 0
else
echo "I tried to create ${PADS_FIFO} and failed."
echo "You will need to create it manually before starting
${name}."
return 1
fi
}
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Can't get start_precmd to do *anything*
On 19/12/2012, Paul Schmehl wrote:
> I'm working on an rc.d init script for a port, and I am clearly in need of
> a clue.
>
> I have a daemon that requires that a FIFO exist before it will start. The
> FIFO is defined in the daemon's conf file. I could just point that out to
> the user using "warn", but I thought it would be nicer to simply take care
> of it programmatically.
>
> So I created this:
>
> start_precmd="${name}_ck4fifo()"
Is this a copy/paste error, or is your function actually called
_ck4fifo or _ch4fifo?
> ${name}_ch4fifo()
I'm surprised sh isn't choking on this, you can't use ${name} in a
function name. Indirecting it is a waste of processing time, if I'm
honest; just use
start_precmd=pads_agent_prestart
pads_agent_prestart()
{
do_something
}
We always have search and replace in case you choose to modify $name :)
Chris
> {
> . ${pads_agent_conf}
> echo "Checking to see if ${PADS_FIFO} exists.."
> if [ ! -p ${PADS_FIFO} ]; then
> echo "${PADS_FIFO} did not exist. Creating it now."
> `/usr/bin/mkfifo ${PADS_FIFO}
> else
> echo "${PADS_FIFO} already exists."
> fi
> }
>
> When I run the init script with rc_debug enabled, it calls the
> start_precmd, but absolutely nothing happens. I don't even get the echos.
>
> # /usr/local/etc/rc.d/pads_agent onestart
> /usr/local/etc/rc.d/pads_agent: DEBUG: checkyesno: pads_agent_enable is set
>
> to YES.
> /usr/local/etc/rc.d/pads_agent: DEBUG: run_rc_command: start_precmd:
> pads_agent_ck4fifo()
> Starting pads_agent.
> /usr/local/etc/rc.d/pads_agent: DEBUG: run_rc_command: doit:
> /usr/local/bin/sguil-sensor/pads_agent.tcl -D -c
> /usr/local/etc/sguil-sensor/pads_agent.conf
> [root@buttercup4 /usr/ports/security/sguil-sensor-update/sguil-sensor]#
> Error: Unable to read
> /var/data/nsm/sguil-sensor/buttercup4.utdallas.edu/pads.fifo
>
> I even tried this but got the same result.
>
> ${name}_ch4fifo()
> {
> warn "You must create PADS_FIFO before starting ${name}."
> warn "Set PADS_FIFO in the ${pads_agent_conf} file."
> }
>
> The warn messages aren't in the messages file either, which is expected
> behavior.
>
> What the heck is going on here? Is something wrong with rc.subr on this
> host? Am I missing something?
>
> --
> Paul Schmehl, Senior Infosec Analyst
> As if it wasn't already obvious, my opinions
> are my own and not those of my employer.
> ***
> "It is as useless to argue with those who have
> renounced the use of reason as to administer
> medication to the dead." Thomas Jefferson
> "There are some ideas so wrong that only a very
> intelligent person could believe in them." George Orwell
>
> ___
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-rc
> To unsubscribe, send any mail to "freebsd-rc-unsubscr...@freebsd.org"
>
>
--
Chris Rees | FreeBSD Developer
cr...@freebsd.org | http://people.freebsd.org/~crees
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Can't get start_precmd to do *anything*
I'm working on an rc.d init script for a port, and I am clearly in need of
a clue.
I have a daemon that requires that a FIFO exist before it will start. The
FIFO is defined in the daemon's conf file. I could just point that out to
the user using "warn", but I thought it would be nicer to simply take care
of it programmatically.
So I created this:
start_precmd="${name}_ck4fifo()"
${name}_ch4fifo()
{
. ${pads_agent_conf}
echo "Checking to see if ${PADS_FIFO} exists.."
if [ ! -p ${PADS_FIFO} ]; then
echo "${PADS_FIFO} did not exist. Creating it now."
`/usr/bin/mkfifo ${PADS_FIFO}
else
echo "${PADS_FIFO} already exists."
fi
}
When I run the init script with rc_debug enabled, it calls the
start_precmd, but absolutely nothing happens. I don't even get the echos.
# /usr/local/etc/rc.d/pads_agent onestart
/usr/local/etc/rc.d/pads_agent: DEBUG: checkyesno: pads_agent_enable is set
to YES.
/usr/local/etc/rc.d/pads_agent: DEBUG: run_rc_command: start_precmd:
pads_agent_ck4fifo()
Starting pads_agent.
/usr/local/etc/rc.d/pads_agent: DEBUG: run_rc_command: doit:
/usr/local/bin/sguil-sensor/pads_agent.tcl -D -c
/usr/local/etc/sguil-sensor/pads_agent.conf
[root@buttercup4 /usr/ports/security/sguil-sensor-update/sguil-sensor]#
Error: Unable to read
/var/data/nsm/sguil-sensor/buttercup4.utdallas.edu/pads.fifo
I even tried this but got the same result.
${name}_ch4fifo()
{
warn "You must create PADS_FIFO before starting ${name}."
warn "Set PADS_FIFO in the ${pads_agent_conf} file."
}
The warn messages aren't in the messages file either, which is expected
behavior.
What the heck is going on here? Is something wrong with rc.subr on this
host? Am I missing something?
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Boot of 9.1 under qemu-kvm 1.3 hangs at pci probing
In article <50ce5805.7010...@cran.org.uk> you write: >I'm trying to install FreeBSD 9.1 in a Proxmox KVM, using qemu-kvm 1.3, >but the boot process is hanging: > >pbib0: matched entry for 0.1 INTA >pbib0: slot 1 INTA hardwired to IRQ 9 >ioapic0: Changing polarity for pin 9 to low >found -> vendor=0x1013, dev=0x00b8, revid=0x00 >domain=0, bus=0, slot=2, func=0 >class=03-00-00, hdrtype=0x00, mfdev=0 >cmdreg=0x0103, statreg=0x, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0ns), maxlat=0x00 (0ns) >[hang] > >Has anyone come across this before and know of any workarounds? Just in case you haven't meanwhile found this yourself (and for the archives), this is caused by an incompatible change in seabios [1] that qemu uses. I hope this will be fixed for qemu 1.3.1, a fixed bios.bin that you can pass to qemu/kvm with -bios has been posted in this thread: https://lists.nongnu.org/archive/html/qemu-devel/2012-12/msg01703.html HTH, :) Juergen [1] http://git.qemu.org/?p=seabios.git;a=commit;h=4540409d19a4baeec5006d925cfca19f8038a96e ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: about unattended installation
On Dec 19, 2012, at 10:52 AM, Amitabh Kant wrote: > Won't be able to help you much, but bsdinstall seems to be using gpart > rather than fdisk. This page has a nice explanation on how to use gpart: > > http://www.wonkity.com/~wblock/docs/html/disksetup.html > > As for sysinstall, it's not being mainitned officially, but > http://druidbsd.sourceforge.net/ is using sysinstall > Cool! I'm the maintainer of FreeBSD Druid (sysinstall-based 9.x installer). When 9.1 is officially announced, I'll start rolling a new 9.1 based installer (right now, still just 8.3 and 9.0 are the latest offerings). I'm also the maintainer of bsdconfig. I'd like to also think I'm that last unofficial maintainer of sysinstall (I've actually patched it in stable/9 in the past 90 days). And, as-of the last DevSummit, I've been nominated the new maintainer of bsdinstall (with nwhitehorn's blessing). So… At some point, you'll see me go rabid on all the PR's in the freebsd-sysinstall pool, but right now I'm still in the coal-mines dredging out the framework to accept all these missing features. -- Devin > On Wed, Dec 19, 2012 at 11:36 PM, Egoitz Aurrekoetxea Aurre < > ego...@ramattack.net> wrote: > >> Good afternoon, >> >> One little question… I'm trying to have ready our new unattended FreeBSD >> installation system. Until now, I have been using Sysinstall scripting file >> but now with 9.1 out I think it's moment to start using BSDInstaller in the >> unattended installation process. I have seen the new installer, works >> basically like an script…. my real question is… before I did in install.cfg >> something like : >> >> >> disk=da0 >> partition=all >> bootManager=standard >> diskPartitionEditor >> >> >> >> da0s1-1=ufs 3072000 / >> da0s1-2=swap 8096000 none >> da0s1-3=ufs 20485760 /var 1 >> da0s1-4=ufs 30720760 /usr 1 >> da0s1-5=ufs 0 /expert 1 >> diskLabelEditor >> >> >> >> Now I assume there's no way of getting this same through any command like… >> 'bsdinstall partedit ___' am I wrong??. So I assume all >> should be done by hand like this example of the Handbook : >> >> # dd if=/dev/zero of=/dev/da1 bs=1k count=1 >> # fdisk -BI da1 #Initialize your new disk >> # bsdlabel -B -w da1s1 auto #Label it. >> # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any >> partitions. >> # mkdir -p /1 >> # newfs /dev/da1s1e # Repeat this for every partition you created. >> # mount /dev/da1s1e /1 # Mount the partition(s) >> # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. >> >> In the auto script…. >> >> am I wrong?. If the answer is yes… could you point me to some >> documentation in order to be able to complete all this doc. Apart from all >> this… is Sysinstall going to be maintained in parallel?. >> >> Thank you very much, >> Best regards! >> >> >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> freebsd-questions-unsubscr...@freebsd.org" >> > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: about unattended installation
On Thu, Dec 20, 2012 at 12:29 AM, Devin Teske wrote: > > On Dec 19, 2012, at 10:06 AM, Egoitz Aurrekoetxea Aurre wrote: > > > Good afternoon, > > > > One little question… I'm trying to have ready our new unattended FreeBSD > installation system. Until now, I have been using Sysinstall scripting file > but now with 9.1 out I think it's moment to start using BSDInstaller in the > unattended installation process. > > Hold on a moment. You might want to wait until 9.2. (read more below) > > > > > I have seen the new installer, works basically like an script…. my real > question is… before I did in install.cfg something like : > > > > > > disk=da0 > > partition=all > > bootManager=standard > > diskPartitionEditor > > > > > > > > da0s1-1=ufs 3072000 / > > da0s1-2=swap 8096000 none > > da0s1-3=ufs 20485760 /var 1 > > da0s1-4=ufs 30720760 /usr 1 > > da0s1-5=ufs 0 /expert 1 > > diskLabelEditor > > > > > > > > Now I assume there's no way of getting this same through any command > like… 'bsdinstall partedit ___' am I wrong??. > > You're correct. In 9.0 and 9.1, it's just not feasible to man-handle the > user interface (partedit) as one could sysinstall. (read below about 9.2) > > > > > So I assume all should be done by hand like this example of the Handbook > : > > > > # dd if=/dev/zero of=/dev/da1 bs=1k count=1 > > # fdisk -BI da1 #Initialize your new disk > > # bsdlabel -B -w da1s1 auto #Label it. > > # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any > partitions. > > # mkdir -p /1 > > # newfs /dev/da1s1e # Repeat this for every partition you created. > > # mount /dev/da1s1e /1 # Mount the partition(s) > > # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. > > > > In the auto script…. > > > > am I wrong?. If the answer is yes… could you point me to some > documentation in order to be able to complete all this doc. > > The answer is (unfortunately) yes… that is until (hopefully) 9.2. > > It's an on-going significant amount of work to make add backward > compatibility (so bsdinstall can load sysinstall "install.cfg" files). I'm > not going to discuss the specifics here or yet, but I'm actively working on > it. > > No docs on how to mangle the auto script to do what you want (that I know > of). > > > > > Apart from all this… is Sysinstall going to be maintained in parallel?. > > > > Sysinstall is dead. The bsdinstall you know can be considered the "first > generation" and accordingly is a bit spartan. I'm working hard on the next > generation. My plan is to have 10.0 with bsdinstall able to run sysinstall > scripts (for backward compatibility; can't yet say what 9.x release will be > MFC'd to, but that could be 9.2). > > I'm planning one helluva BSDCan-2013 presentation. > -- > Devin > > Interesting Devin. I have played around with bsdinstall script files and partedit source files to certain extent. Was able to achieve a bit of success. One of the major stumbling blocks for me still is including custom scripts and packages. Just can't seem to understand where and how to place them, so that it is available to auto script for further processing. Amitabh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: about unattended installation
On Dec 19, 2012, at 10:06 AM, Egoitz Aurrekoetxea Aurre wrote: > Good afternoon, > > One little question… I'm trying to have ready our new unattended FreeBSD > installation system. Until now, I have been using Sysinstall scripting file > but now with 9.1 out I think it's moment to start using BSDInstaller in the > unattended installation process. Hold on a moment. You might want to wait until 9.2. (read more below) > I have seen the new installer, works basically like an script…. my real > question is… before I did in install.cfg something like : > > > disk=da0 > partition=all > bootManager=standard > diskPartitionEditor > > > > da0s1-1=ufs 3072000 / > da0s1-2=swap 8096000 none > da0s1-3=ufs 20485760 /var 1 > da0s1-4=ufs 30720760 /usr 1 > da0s1-5=ufs 0 /expert 1 > diskLabelEditor > > > > Now I assume there's no way of getting this same through any command like… > 'bsdinstall partedit ___' am I wrong??. You're correct. In 9.0 and 9.1, it's just not feasible to man-handle the user interface (partedit) as one could sysinstall. (read below about 9.2) > So I assume all should be done by hand like this example of the Handbook : > > # dd if=/dev/zero of=/dev/da1 bs=1k count=1 > # fdisk -BI da1 #Initialize your new disk > # bsdlabel -B -w da1s1 auto #Label it. > # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any partitions. > # mkdir -p /1 > # newfs /dev/da1s1e # Repeat this for every partition you created. > # mount /dev/da1s1e /1 # Mount the partition(s) > # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. > > In the auto script…. > > am I wrong?. If the answer is yes… could you point me to some documentation > in order to be able to complete all this doc. The answer is (unfortunately) yes… that is until (hopefully) 9.2. It's an on-going significant amount of work to make add backward compatibility (so bsdinstall can load sysinstall "install.cfg" files). I'm not going to discuss the specifics here or yet, but I'm actively working on it. No docs on how to mangle the auto script to do what you want (that I know of). > Apart from all this… is Sysinstall going to be maintained in parallel?. > Sysinstall is dead. The bsdinstall you know can be considered the "first generation" and accordingly is a bit spartan. I'm working hard on the next generation. My plan is to have 10.0 with bsdinstall able to run sysinstall scripts (for backward compatibility; can't yet say what 9.x release will be MFC'd to, but that could be 9.2). I'm planning one helluva BSDCan-2013 presentation. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: about unattended installation
Won't be able to help you much, but bsdinstall seems to be using gpart rather than fdisk. This page has a nice explanation on how to use gpart: http://www.wonkity.com/~wblock/docs/html/disksetup.html As for sysinstall, it's not being mainitned officially, but http://druidbsd.sourceforge.net/ is using sysinstall Amitabh On Wed, Dec 19, 2012 at 11:36 PM, Egoitz Aurrekoetxea Aurre < ego...@ramattack.net> wrote: > Good afternoon, > > One little question… I'm trying to have ready our new unattended FreeBSD > installation system. Until now, I have been using Sysinstall scripting file > but now with 9.1 out I think it's moment to start using BSDInstaller in the > unattended installation process. I have seen the new installer, works > basically like an script…. my real question is… before I did in install.cfg > something like : > > > disk=da0 > partition=all > bootManager=standard > diskPartitionEditor > > > > da0s1-1=ufs 3072000 / > da0s1-2=swap 8096000 none > da0s1-3=ufs 20485760 /var 1 > da0s1-4=ufs 30720760 /usr 1 > da0s1-5=ufs 0 /expert 1 > diskLabelEditor > > > > Now I assume there's no way of getting this same through any command like… > 'bsdinstall partedit ___' am I wrong??. So I assume all > should be done by hand like this example of the Handbook : > > # dd if=/dev/zero of=/dev/da1 bs=1k count=1 > # fdisk -BI da1 #Initialize your new disk > # bsdlabel -B -w da1s1 auto #Label it. > # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any > partitions. > # mkdir -p /1 > # newfs /dev/da1s1e # Repeat this for every partition you created. > # mount /dev/da1s1e /1 # Mount the partition(s) > # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. > > In the auto script…. > > am I wrong?. If the answer is yes… could you point me to some > documentation in order to be able to complete all this doc. Apart from all > this… is Sysinstall going to be maintained in parallel?. > > Thank you very much, > Best regards! > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Ralf, On Wed, Dec 19, 2012 at 11:09 AM, Ralf Mardorf wrote: > On Wed, 2012-12-19 at 10:14 -0600, Antonio Olivares wrote: >> You may also use at your discretion the portmaster tool? It works >> very well and a nice example is given by W. Block: >> >> http://www.wonkity.com/~wblock/docs/html/portupgrade.html > > Thank you Antonio :) > > because I can't install FreeBSD by the 9.0 DVD, for what reason ever > this doesn't work, I installed it by the 8.3 DVD and will now make a > release upgrade. IIUC a release upgrade will rebuild everything, hence > there should be no dependency issues. My FreeBSD 8.3 is a fresh install, > I only set up PPPoE, anything else is default. > IIUC I need to take care about it to keep dependencies up to date, when > I don't upgrade the complete release, but just upgrade some software. > > So, can I upgrade from 8.3 to 9.0, without taking care about > dependencies and take care about the link, when 9.0 is installed, > instead of doing it right now? Yes, you can do it. You can update to 9.0 with freebsd-update tool and then install/reinstall the ports. # freebsd-update -r 9.1-RELEASE or # freebsd-update -r 9.0-RELEASE in case that 9.1 is not there yet*? then run # freebsd-update fetch # freebsd-update install to get security updates as is documented : http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html This should work well to get newer RELEASE, but some ports may be needed to be rebuilt/reinstalled. Hope this helps, Antonio > > My apologize for the terrible English, I'm in a hurry, but wanted to > rely immediately and this makes broken English not better ;). > > Regards, > Ralf > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
about unattended installation
Good afternoon, One little question… I'm trying to have ready our new unattended FreeBSD installation system. Until now, I have been using Sysinstall scripting file but now with 9.1 out I think it's moment to start using BSDInstaller in the unattended installation process. I have seen the new installer, works basically like an script…. my real question is… before I did in install.cfg something like : disk=da0 partition=all bootManager=standard diskPartitionEditor da0s1-1=ufs 3072000 / da0s1-2=swap 8096000 none da0s1-3=ufs 20485760 /var 1 da0s1-4=ufs 30720760 /usr 1 da0s1-5=ufs 0 /expert 1 diskLabelEditor Now I assume there's no way of getting this same through any command like… 'bsdinstall partedit ___' am I wrong??. So I assume all should be done by hand like this example of the Handbook : # dd if=/dev/zero of=/dev/da1 bs=1k count=1 # fdisk -BI da1 #Initialize your new disk # bsdlabel -B -w da1s1 auto #Label it. # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /1 # newfs /dev/da1s1e # Repeat this for every partition you created. # mount /dev/da1s1e /1 # Mount the partition(s) # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. In the auto script…. am I wrong?. If the answer is yes… could you point me to some documentation in order to be able to complete all this doc. Apart from all this… is Sysinstall going to be maintained in parallel?. Thank you very much, Best regards! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Wed, 2012-12-19 at 10:14 -0600, Antonio Olivares wrote: > You may also use at your discretion the portmaster tool? It works > very well and a nice example is given by W. Block: > > http://www.wonkity.com/~wblock/docs/html/portupgrade.html Thank you Antonio :) because I can't install FreeBSD by the 9.0 DVD, for what reason ever this doesn't work, I installed it by the 8.3 DVD and will now make a release upgrade. IIUC a release upgrade will rebuild everything, hence there should be no dependency issues. My FreeBSD 8.3 is a fresh install, I only set up PPPoE, anything else is default. IIUC I need to take care about it to keep dependencies up to date, when I don't upgrade the complete release, but just upgrade some software. So, can I upgrade from 8.3 to 9.0, without taking care about dependencies and take care about the link, when 9.0 is installed, instead of doing it right now? My apologize for the terrible English, I'm in a hurry, but wanted to rely immediately and this makes broken English not better ;). Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Ralf, On Wed, Dec 19, 2012 at 10:04 AM, Ralf Mardorf wrote: > Hi :) > > this isn't a request, just a note about the handbook, from the point of > view a newbie has got. > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > > "We also assume that you have already obtained the sources to a newer > system. If the sources available on the particular system are old too, > see Section 25.6 for detailed help about synchronizing them to a newer > version." > > I know svn from Linux, but I don't know what I should update using > svn ;). Yes, the ports, but to get knowledge were the ports are, I have > to google ;). This howto is more confusing for a newbie and seems to > need more reboots, so I started with > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html > > but it's not described how to do the following: > "Note that setting the BATCH environment variable to yes will answer yes > to any prompts during this process, removing the need for manual > intervention during the build process." > > regarding to google it's "env BATCH=yes", I'll test it next time I'll > reboot into FreeBSD. > > Another issue is, that the portupgrade command isn't found. Check in /usr/ports/ports-mgmt/ directory: Become super user, $ su - passwd: then as super user: # cd /usr/ports/ports-mgmt/portupgrade then from that directory # make install clean and you should have the portugrade command :) You may also use at your discretion the portmaster tool? It works very well and a nice example is given by W. Block: http://www.wonkity.com/~wblock/docs/html/portupgrade.html Best Regards, Antonio > > However, pppoe does work, but using vi never is fun for me :). > > I guess I'll read how to install software, IOW how to install > portupgrade and continue with the portupgrade method ASAP, later today, > or tomorrow. > > Regards, > Ralf > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Hi :) this isn't a request, just a note about the handbook, from the point of view a newbie has got. > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html "We also assume that you have already obtained the sources to a newer system. If the sources available on the particular system are old too, see Section 25.6 for detailed help about synchronizing them to a newer version." I know svn from Linux, but I don't know what I should update using svn ;). Yes, the ports, but to get knowledge were the ports are, I have to google ;). This howto is more confusing for a newbie and seems to need more reboots, so I started with > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html but it's not described how to do the following: "Note that setting the BATCH environment variable to yes will answer yes to any prompts during this process, removing the need for manual intervention during the build process." regarding to google it's "env BATCH=yes", I'll test it next time I'll reboot into FreeBSD. Another issue is, that the portupgrade command isn't found. However, pppoe does work, but using vi never is fun for me :). I guess I'll read how to install software, IOW how to install portupgrade and continue with the portupgrade method ASAP, later today, or tomorrow. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: wifi support?
On 12/19/12 08:59, Thuban wrote: Hello, I would like to try freebsd, but I need to know if my wifi card will be usable. A lspci under debian returns : 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01) Can you tell me where I can find if this card is supported or not? Thank you. RealTek wifi support is nil in 9.x (I have a RealTek wireless and wired in my laptop and only the wired works). You'll have to use ndistulator to get RealTek wifi under FreeBSD (its how its done in Linux afaik). -- Yours in Christ, Joseph A Nagy Jr "Whoever loves instruction loves knowledge, But he who hates correction is stupid." -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: wifi support?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/19/12 9:59 AM, Thuban wrote: > Hello, I would like to try freebsd, but I need to know if my wifi > card will be usable. A lspci under debian returns : 02:00.0 Network > controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n > WiFi Adapter (rev 01) > > Can you tell me where I can find if this card is supported or not? > > Thank you. > Hi there, According to this posting, it doesn't look like that card is supported on FreeBSD yet: http://freebsd.1045724.n5.nabble.com/RTL8188CE-wireless-card-td5628611.html Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDR3UYACgkQ0sRouByUApDHjACgwV3FQZP/FVLvOhjvNvOYU8RV 6ewAoMpMTn3Z76OcmvwY5EkjH3oJMNlG =YeRx -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
wifi support?
Hello, I would like to try freebsd, but I need to know if my wifi card will be usable. A lspci under debian returns : 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01) Can you tell me where I can find if this card is supported or not? Thank you. -- ,--. Xavier Cartron : /` ) M2 MEFPC | `-' Debian user \_ jabber : thu...@jabber.fr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: reboot after removing ipv6 ?
Frank Bonnet esiee.fr> writes: > > Hello > > Do I have to reboot a server after unvalidating IPv6 in /etc/rc.conf ? > > I seems to use "/etc/rc.d/netif restart" is not suffisant Use 'netstat' to see what service(s) listen for ipv6 traffic and restart them. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Curious question about using zfs send -R and receive on FreeBSD
On 2012-12-19 07:01, Christopher J. Ruwe wrote: On Mon, 17 Dec 2012 16:00:06 -0600 dweimer wrote: I recently migrated a machine that was built on a VM to physical hardware using the zfs send -R option against a snapshot of its root zfs setup. I went from smaller drives to larger, both using a mirrored zpool. However the devices were different, the device IDs on the VM were da0 and da1, the device IDs on the physical hardware were ada0 and ada1. I had used labels when creating the gpt layout to plan for this. And all worked great, in fact it was the fastest I have ever converted a virtual machine to a physical machine. After I finished though, I got curious, was it actually necessary for me to mount the new boot zfs partition while running on the live cd and copy the zpool.cache file I had created when creating the zpool or would have the existing cache file that would have been included in the zfs send contained the right information? As the zpool was pointed at the gpt label devices, or was the fact that the size changed enough difference that copying the file was indeed necessary? I fear you might be mixing things up here. You did a zfs-migrate, not a zpool-migrate, you created a new zpool and received the datasets on that new zpool, even if the zpool names were the same. The function of zpool.cache is to tell the OS about available device-zpool combinations. Without, the OS does not know which zpools are available and accordingly cannot mount the root-ZFS passed in the vfs.root.mountfrom directive in loader.conf, which is why you needed to copy the zpool.cache and, if you changed the zpool-names, needed to adapt loader.conf. There are plans to change this behaviour, as it is deemed superfluous at least in the case of disks, but I do not know how much that has progressed so far. http://lists.freebsd.org/pipermail/freebsd-fs/2012-October/015328.html Hope I could shed some light on that issue, although I am by no means an expert on this. Cheers, Yes that did explain it, and I did keep the zpool the same name to avoid having to change the loader.conf. This also does answer other things as well for me. In that this should be able to be done from a mirror to a zraid, or single disk pool. But as you have pointed out the migration is done on the ZFS data layer that is on top of the zpool layer, so it shouldn't matter what the underlying zpool raid level is. And likewise wouldn't matter if the hardware devices behind it changed even if I hadn't used gpt labels to configure the zpool. Good information to know going forward, thanks for the explanation. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing chromium port
19.12.2012 15:34, Jack Mc Lauren: Hi guys When I attempt to install chromium port I face this error : ===> chromium-6.0.472.63 is forbidden: several security vulnerabilities.*** Error code 1 What should I do with this ?? Thanks in advance 6.0.472.63 is very old. Try updating your ports first. -- Sphinx of black quartz, judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Installing chromium port
Hi guys When I attempt to install chromium port I face this error : ===> chromium-6.0.472.63 is forbidden: several security vulnerabilities.*** Error code 1 What should I do with this ?? Thanks in advance ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Curious question about using zfs send -R and receive on FreeBSD
On Mon, 17 Dec 2012 16:00:06 -0600 dweimer wrote: > I recently migrated a machine that was built on a VM to physical > hardware using the zfs send -R option against a snapshot of its root > zfs setup. I went from smaller drives to larger, both using a > mirrored zpool. However the devices were different, the device IDs > on the VM were da0 and da1, the device IDs on the physical hardware > were ada0 and ada1. I had used labels when creating the gpt layout > to plan for this. And all worked great, in fact it was the fastest I > have ever converted a virtual machine to a physical machine. > After I finished though, I got curious, was it actually necessary > for me to mount the new boot zfs partition while running on the live > cd and copy the zpool.cache file I had created when creating the > zpool or would have the existing cache file that would have been > included in the zfs send contained the right information? As the > zpool was pointed at the gpt label devices, or was the fact that the > size changed enough difference that copying the file was indeed > necessary? > I fear you might be mixing things up here. You did a zfs-migrate, not a zpool-migrate, you created a new zpool and received the datasets on that new zpool, even if the zpool names were the same. The function of zpool.cache is to tell the OS about available device-zpool combinations. Without, the OS does not know which zpools are available and accordingly cannot mount the root-ZFS passed in the vfs.root.mountfrom directive in loader.conf, which is why you needed to copy the zpool.cache and, if you changed the zpool-names, needed to adapt loader.conf. There are plans to change this behaviour, as it is deemed superfluous at least in the case of disks, but I do not know how much that has progressed so far. http://lists.freebsd.org/pipermail/freebsd-fs/2012-October/015328.html Hope I could shed some light on that issue, although I am by no means an expert on this. Cheers, -- Christopher TZ: GMT + 2h GnuPG/GPG: 0xE8DE2C14 Punctuation matters: "Let's eat Grandma" or "Let's eat, Grandma" - Punctuation saves lives. "A panda eats shoots and leaves" or "A panda eats, shoots, and leaves" - Punctuation teaches proper biology. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
reboot after removing ipv6 ?
Hello Do I have to reboot a server after unvalidating IPv6 in /etc/rc.conf ? I seems to use "/etc/rc.d/netif restart" is not suffisant Thank you ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
