Auto bridge for qemu network [was: kqemu support: not compiled]

2008-05-15 Thread bazzoola

Thanks for updating the port!

I have few suggestions:

#cat /etc/rc.conf
[...]
#KQEMU for qemu
kqemu_enable=YES

#Bridge for qemu
cloned_interfaces=bridge0
ifconfig_bridge0=up addm sk0
autobridge_interfaces=bridge0
autobridge_bridge0=tap*

This should take care of the network connection between qemu virtual  
host and the host instead of doing it manually. Assuming that qemu is  
using tap and the default if on the host is sk0.


Also, is it possible to update this page, it has some outdated info:
http://people.freebsd.org/~maho/qemu/qemu.html
*It is the 1st answer from google when asked freebsd qemu

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


kqemu support: not compiled

2008-05-12 Thread bazzoola

Greetings,

I just cant get kqemu to work on my AMD64 SMP!

I setenv WITH_KQEMU
I compiled the port with make -DWITH_KQEMU
I edited src.conf and added WITH_KQEMU=yes
I make config and checked KQEMU ALPHA support

I am running
#uname -a
FreeBSD Aa.bsd 7.0-STABLE FreeBSD 7.0-STABLE #3: Mon Apr 21 05:56:16  
CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  amd64


#pkg_info | grep qemu
kqemu-kmod-1.3.0.p11_6
qemu-devel-0.9.1s.20080302_6

latest as you as see ^^^

any ideas?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: kqemu support: not compiled

2008-05-12 Thread bazzoola


On May 12, 2008, at 10:20 PM, Bakul Shah wrote:


I just cant get kqemu to work on my AMD64 SMP!


echo kqemu_enable=YES  /etc/rc.conf
/usr/local/etc/rc.d/kqemu start


Is this documented anywhere?

Also, I volunteered to update the wiki and the author was grateful for  
that but I didn't get access. If anyone cares. I can just send the  
updates here via email.


Thanks!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: kqemu support: not compiled

2008-05-12 Thread bazzoola


On May 12, 2008, at 10:20 PM, Bakul Shah wrote:


I just cant get kqemu to work on my AMD64 SMP!


echo kqemu_enable=YES  /etc/rc.conf
/usr/local/etc/rc.d/kqemu start


I looked at the rc script and all it does is kldload aio and kqemu. I  
already have them loaded by default.

This still does not help me with my problem.

I press Ctrl + Alt + 2
then I type info kqemu
I get kqemu support: not compiled


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: kqemu support: not compiled

2008-05-12 Thread bazzoola


On May 13, 2008, at 12:24 AM, Brandon S. Allbery KF8NH wrote:



On 2008 May 13, at 0:18, bazzoola wrote:


I press Ctrl + Alt + 2
then I type info kqemu
I get kqemu support: not compiled



Without looking, I'd guess this means the qemu binary was built  
without kqemu support enabled.


as I stated before (which u omitted) I DID enabled kqemu everywhere  
and then built qemu but still I get that error not compiled.


setenv WITH_KQEMU
edited src.conf and added WITH_KQEMU=yes
did make config and checked KQEMU ALPHA support
compiled the port with make -DWITH_KQEMU

how do you compile qemu binary with kqemu? other than the 4 things  
above?



--
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED]
system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED]
electrical and computer engineering, carnegie mellon university 
KF8NH





___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: kqemu support: not compiled

2008-05-12 Thread bazzoola

Thanks for your quick reply I appreciate that! Please see below:

On May 13, 2008, at 12:51 AM, Bakul Shah wrote:


On Tue, 13 May 2008 00:18:32 EDT bazzoola [EMAIL PROTECTED]  wrote:


On May 12, 2008, at 10:20 PM, Bakul Shah wrote:


I just cant get kqemu to work on my AMD64 SMP!


echo kqemu_enable=YES  /etc/rc.conf
/usr/local/etc/rc.d/kqemu start


This should probably be described in pkg-message.

It is not there.




I looked at the rc script and all it does is kldload aio and kqemu. I
already have them loaded by default.


You didn't provide information so I had to guess.

My problem lies in qemu not being compiled with kqemu




This still does not help me with my problem.

I press Ctrl + Alt + 2
then I type info kqemu
I get kqemu support: not compiled


Are you running qemu? It is an i386 emulator and won't use
kqemu on amd64.  You need to run qemu-system-x86_64.  I know,
this is a bit confusing.

I thought qemu on x64 runs that directly. My bad..

Note I had to run qemu-system-x86_64 -kernel-kqemu
to get kernel mode virtz to work otherwise it will just load it in  
user mode.


Thanks again for your help!




If you are still having problems provide the *exact sequence*
of commands you used to build and run qemu.  BTW, to build
you don't need to muck with environ. var. or -DWITH_KQEMU.
Just do

make config  make


___
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

2008-02-28 Thread bazzoola

Terrific job!
Thanks for anyone contributed to this fine release :)

On Feb 27, 2008, at 5:32 PM, Ken Smith wrote:



Just in case some interested parties are not subscribed to the
freebsd-announce mailing list...  FreeBSD 7.0-RELEASE has been  
formally
released.  If you would like to see the release announcement it's  
here:


 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.

--
   Ken Smith
- From there to here, from here to  |   [EMAIL PROTECTED]
 there, funny things are everywhere.   |
 - Theodore Geisel |


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


ral0: device timeout in RELENG_7

2007-10-28 Thread bazzoola

Greetings,

ral0 does not function correctly under RELENG_7 as an access point.  
The same configuration used to work just fine on RELENG_6 (please see  
attached)


ral0: device timeout
I do not receive this message if I am using ral0 as a client (not an  
access point)
I do not receive this message if ral0 does not have an IP address  
associated with it (even if hostapd is running and running as an AP).  
So, to trigger this problem I run: ifconfig ral0 inet 192.168.2.11  
netmask 255.255.255.0
Also, immediately after that I get so many interrupts on IRQ5 and the  
LED on the card keeps blinking.


Here is my configuration:
#pciconf
[EMAIL PROTECTED]:0:13:0:   class=0x028000 card=0x00321737
chip=0x02011814 rev=0x01 hdr=0x00
 vendor = 'Ralink Technology, Corp'
 device = '0x03011814 Zonet ZEW1601 (Ralink Chipset) 802.11b/
g WLAN Card'
 class  = network
 cap 01[40] = powerspec 2  supports D0 D3  current D0

#cat /root/kernels/GENERIC2
# GENERIC2 -- Generic kernel configuration file for FreeBSD/i386

cpu I486_CPU
cpu I586_CPU
cpu I686_CPU
ident   GENERIC2

options SCHED_ULE   # ULE scheduler
options PREEMPTION  # Enable kernel thread
preemption
options INET# InterNETworking
options INET6   # IPv6 communications protocols
options SCTP# Stream Control Transmission
Protocol
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates
support
options UFS_ACL # Support for access control
lists
options UFS_DIRHASH # Improve performance on big
directories
options UFS_GJOURNAL# Enable gjournal-based UFS
journaling
options MD_ROOT # MD is a potential root device
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem
(requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_PART_GPT   # GUID Partition Tables.
options GEOM_LABEL  # Provides labelization
options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP
THIS!]
options SCSI_DELAY=5000 # Delay (in ms) before
probing SCSI
options KTRACE  # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-
time extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options ADAPTIVE_GIANT  # Giant mutex is adaptive.
options STOP_NMI# Stop CPUS using NMI instead
of IPI
options AUDIT   # Security event auditing

device  apic# I/O APIC

device  pci

device  fdc

device  ata
device  atadisk # ATA disk drives
device  ataraid # ATA RAID drives
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives
device  atapist # ATAPI tape drives
options ATA_STATIC_ID   # Static device numbering

device  atkbdc  # AT keyboard controller
device  atkbd   # AT keyboard
device  psm # PS/2 mouse

device  kbdmux  # keyboard multiplexer

device  vga # VGA video card driver

device  agp # support several AGP chipsets

device  pmtimer

device  sio # 8250, 16[45]50 based serial ports
device  uart# Generic UART driver

device  sk  # SysKonnect SK-984x  SK-982x
gigabit Ethernet

device  wlan# 802.11 support
device  wlan_wep# 802.11 WEP support
device  wlan_ccmp   # 802.11 CCMP support
device  wlan_tkip   # 802.11 TKIP support
device  wlan_amrr   # AMRR transmit rate control algorithm
device  wlan_scan_ap# 802.11 AP mode scanning
device  wlan_scan_sta   # 802.11 STA mode scanning
device  ral # Ralink Technology RT2500 wireless
NICs.

device  loop# Network loopback
device  random  # Entropy device
device  ether   # Ethernet support
device  sl  # Kernel SLIP
device  ppp # Kernel PPP
device  tun # Packet tunnel.
device  pty # Pseudo-ttys (telnet etc)
device  md  # Memory disks
device  gif 

ral0: device timeout in RELENG_7

2007-10-28 Thread bazzoola

Greetings,

ral0 does not function correctly under RELENG_7 as an access point.  
The same configuration used to work just fine on RELENG_6 (please see  
attached)


ral0: device timeout
I do not receive this message if I am using ral0 as a client (not an  
access point)
I do not receive this message if ral0 does not have an IP address  
associated with it (even if hostapd is running and running as an AP).  
So, to trigger this problem I run: ifconfig ral0 inet 192.168.2.11  
netmask 255.255.255.0
Also, immediately after that I get so many interrupts on IRQ5 and the  
LED on the card keeps blinking.


Here is my configuration:
#pciconf
[EMAIL PROTECTED]:0:13:0:   class=0x028000 card=0x00321737
chip=0x02011814 rev=0x01 hdr=0x00
vendor = 'Ralink Technology, Corp'
device = '0x03011814 Zonet ZEW1601 (Ralink Chipset) 802.11b/
g WLAN Card'
class  = network
cap 01[40] = powerspec 2  supports D0 D3  current D0

#cat /root/kernels/GENERIC2
# GENERIC2 -- Generic kernel configuration file for FreeBSD/i386

cpu I486_CPU
cpu I586_CPU
cpu I686_CPU
ident   GENERIC2

options SCHED_ULE   # ULE scheduler
options PREEMPTION  # Enable kernel thread
preemption
options INET# InterNETworking
options INET6   # IPv6 communications protocols
options SCTP# Stream Control Transmission
Protocol
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates
support
options UFS_ACL # Support for access control
lists
options UFS_DIRHASH # Improve performance on big
directories
options UFS_GJOURNAL# Enable gjournal-based UFS
journaling
options MD_ROOT # MD is a potential root device
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem
(requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_PART_GPT   # GUID Partition Tables.
options GEOM_LABEL  # Provides labelization
options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP
THIS!]
options SCSI_DELAY=5000 # Delay (in ms) before
probing SCSI
options KTRACE  # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-
time extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options ADAPTIVE_GIANT  # Giant mutex is adaptive.
options STOP_NMI# Stop CPUS using NMI instead
of IPI
options AUDIT   # Security event auditing

device  apic# I/O APIC

device  pci

device  fdc

device  ata
device  atadisk # ATA disk drives
device  ataraid # ATA RAID drives
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives
device  atapist # ATAPI tape drives
options ATA_STATIC_ID   # Static device numbering

device  atkbdc  # AT keyboard controller
device  atkbd   # AT keyboard
device  psm # PS/2 mouse

device  kbdmux  # keyboard multiplexer

device  vga # VGA video card driver

device  agp # support several AGP chipsets

device  pmtimer

device  sio # 8250, 16[45]50 based serial ports
device  uart# Generic UART driver

device  sk  # SysKonnect SK-984x  SK-982x
gigabit Ethernet

device  wlan# 802.11 support
device  wlan_wep# 802.11 WEP support
device  wlan_ccmp   # 802.11 CCMP support
device  wlan_tkip   # 802.11 TKIP support
device  wlan_amrr   # AMRR transmit rate control algorithm
device  wlan_scan_ap# 802.11 AP mode scanning
device  wlan_scan_sta   # 802.11 STA mode scanning
device  ral # Ralink Technology RT2500 wireless
NICs.

device  loop# Network loopback
device  random  # Entropy device
device  ether   # Ethernet support
device  sl  # Kernel SLIP
device  ppp # Kernel PPP
device  tun # Packet tunnel.
device  pty # Pseudo-ttys (telnet etc)
device  md  # Memory disks
device  gif # 

ral timeout in RELENG_7

2007-10-25 Thread bazzoola

Greetings,

csup'd today:

I am using ral0 to setup a wireless access point.
Whenever my laptop searches for my AP I get ral0: device timeout I  
read in the man pages that this should not happen. However, I have  
been running an AP since RELENG_6 was formed and I have never had any  
issues with it.


#pciconf
[EMAIL PROTECTED]:0:13:0:   class=0x028000 card=0x00321737  
chip=0x02011814 rev=0x01 hdr=0x00

vendor = 'Ralink Technology, Corp'
device = '0x03011814 Zonet ZEW1601 (Ralink Chipset) 802.11b/ 
g WLAN Card'

class  = network
cap 01[40] = powerspec 2  supports D0 D3  current D0


#cat /root/kernels/GENERIC2
# GENERIC2 -- Generic kernel configuration file for FreeBSD/i386

cpu I486_CPU
cpu I586_CPU
cpu I686_CPU
ident   GENERIC2

options SCHED_ULE   # ULE scheduler
options PREEMPTION  # Enable kernel thread  
preemption

options INET# InterNETworking
options INET6   # IPv6 communications protocols
options SCTP# Stream Control Transmission  
Protocol

options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates  
support
options UFS_ACL # Support for access control  
lists
options UFS_DIRHASH # Improve performance on big  
directories
options UFS_GJOURNAL# Enable gjournal-based UFS  
journaling

options MD_ROOT # MD is a potential root device
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem  
(requires PSEUDOFS)

options PSEUDOFS# Pseudo-filesystem framework
options GEOM_PART_GPT   # GUID Partition Tables.
options GEOM_LABEL  # Provides labelization
options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP  
THIS!]
options SCSI_DELAY=5000 # Delay (in ms) before  
probing SCSI

options KTRACE  # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real- 
time extensions

options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options ADAPTIVE_GIANT  # Giant mutex is adaptive.
options STOP_NMI# Stop CPUS using NMI instead  
of IPI

options AUDIT   # Security event auditing

device  apic# I/O APIC

device  pci

device  fdc

device  ata
device  atadisk # ATA disk drives
device  ataraid # ATA RAID drives
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives
device  atapist # ATAPI tape drives
options ATA_STATIC_ID   # Static device numbering

device  atkbdc  # AT keyboard controller
device  atkbd   # AT keyboard
device  psm # PS/2 mouse

device  kbdmux  # keyboard multiplexer

device  vga # VGA video card driver

device  agp # support several AGP chipsets

device  pmtimer

device  sio # 8250, 16[45]50 based serial ports
device  uart# Generic UART driver

device  sk  # SysKonnect SK-984x  SK-982x  
gigabit Ethernet


device  wlan# 802.11 support
device  wlan_wep# 802.11 WEP support
device  wlan_ccmp   # 802.11 CCMP support
device  wlan_tkip   # 802.11 TKIP support
device  wlan_amrr   # AMRR transmit rate control algorithm
device  wlan_scan_ap# 802.11 AP mode scanning
device  wlan_scan_sta   # 802.11 STA mode scanning
device  ral # Ralink Technology RT2500 wireless  
NICs.


device  loop# Network loopback
device  random  # Entropy device
device  ether   # Ethernet support
device  sl  # Kernel SLIP
device  ppp # Kernel PPP
device  tun # Packet tunnel.
device  pty # Pseudo-ttys (telnet etc)
device  md  # Memory disks
device  gif # IPv6 and IPv4 tunneling
device  faith   # IPv6-to-IPv4 relaying (translation)
device  firmware# firmware assist module

device  bpf # Berkeley packet filter





#dmesg
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 

freebsd-snapshot [fsync: giving up on dirty]

2007-03-01 Thread bazzoola

After installing freebsd-snapshot

I am getting this error:

fsync: giving up on dirty
0xc23c7880: tag devfs, type VCHR
usecount 1, writecount 0, refcount 185 mountedhere 0xc2352300
flags ()
v_object 0xc1050420 ref 0 pages 15362
 lock type devfs: EXCL (count 1) by thread 0xc25ef480 (pid 15164)
dev ad0s1f


then I get this email from cron:
Subject: Cron root/usr/local/sbin/periodic-snapshot hourly
X-Cron-Env: SHELL=/bin/sh
X-Cron-Env: PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin
X-Cron-Env: HOME=/root
X-Cron-Env: LOGNAME=root
X-Cron-Env: USER=root

mount: /usr/.snap/hourly.0: Resource temporarily unavailable

P.S CC me I am not on the list
Thanks
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


acpi: bad read from port 0x021 (8) acpi: bad write to port 0x021 (8), val 0xfb

2006-06-13 Thread bazzoola

Greetings,

I sync'd my src tree for 6.1-stable recently then I updated my system.
Now I keep getting:

acpi: bad read from port 0x021 (8)
acpi: bad write to port 0x021 (8), val 0xfb

I searched the mailing list I found one useful entry however, he had  
the same problem and no one replied to him.
Attached is my dmesg. I am not sure if my ACPI is faulty. Or is this  
a normal behavior?
I have beening following the stable branch for years this is the  
first time I get it.

If more info is needed I am more than happy to send it.

Thanks!



dmesg.today
Description: Binary data
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

wireless ral with bridging crashes

2006-03-19 Thread bazzoola

Greetings,

*CC Me in not on the list*

I upgraded my sources yesterday because I was having trouble with WPA 
and ral0. That problem is fixed now. However, now I am getting different 
crashes and core dumps.


I wanted to run a wireless access point on freebsd and I got that 
working by itself.

On my wired network I have openVPN which uses bridging.
Using three interfaces on a bridge 
(net.link.ether.bridge.config=rl0,ral0,tap0) I am able to crash FreeBSD 
6.1-PRERELEASE with an ifconfig command only.

I'm running the default GENERIC kernel.

To reproduce this crash, all i need is to type is ifconfig ral0 
mediaopt hostap

I have vmcore and other useful info if requested.

Procedure:
1- load bridge and wlan_* to loader.conf
2- setup bridging between three interfaces in sysctl.conf
3- run ifconfig ral0 mediaopt hostap
4- note that i didnt try to run hostapd before running ifconfig

Settings that I think are useful to debug this:
in loader.conf I have
console=comconsole
bridge_load=YES
wlan_wep_load=YES
wlan_tkip_load=YES
wlan_ccmp_load=YES
wlan_xauth_load=YES
wlan_acl_load=YES

in sysctl.conf I have:
net.inet.tcp.blackhole=2
net.inet.udp.blackhole=1
net.inet.ip.fw.verbose=1
net.inet.ip.fw.verbose_limit=5
net.inet.ip.forwarding=1
net.inet.ip.fastforwarding=1

# OpenVPN
net.link.ether.bridge.enable=1
net.link.ether.bridge.ipfw=1

# OpenVPN
# net.link.ether.bridge_cfg=rl0,tap0
# net.link.ether.bridge.config=rl0,tap0

# Wireless AP
# net.link.ether.bridge.config=ral0,rl0

# Wireless and OpenVPN
net.link.ether.bridge.config=rl0,ral0,tap0

in dmesg I have:
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
   The Regents of the University of California. All rights reserved.
FreeBSD 6.1-PRERELEASE #3: Sun Mar 19 15:32:41 EST 2006
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD-K6(tm) 3D processor (501.14-MHz 586-class CPU)
 Origin = AuthenticAMD  Id = 0x58c  Stepping = 12
 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
 AMD Features=0x8800SYSCALL,3DNow
real memory  = 266272768 (253 MB)
avail memory = 251170816 (239 MB)
wlan: mac acl policy registered
K6-family MTRR support enabled (2 registers)
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: GBT AWRDACPI on motherboard
acpi0: Power Button (fixed)
cpu0: ACPI CPU on acpi0
acpi_throttle0: ACPI CPU Throttling on cpu0
acpi_button0: Power Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0x480-0x48f,0x5000-0x5041 
on acpi0

pci0: ACPI PCI bus on pcib0
pcib0: no PRT entry for 0.0.INTA
agp0: SiS 530 host to AGP bridge mem 0xe000-0xe3ff at device 
0.0 on pci0
atapci0: SiS 530 UDMA66 controller port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x4000-0x400f irq 14 at device 0.1 
on pci0

ata0: ATA channel 0 on atapci0
ata1: ATA channel 1 on atapci0
isab0: PCI-ISA bridge at device 1.0 on pci0
isa0: ISA bus on isab0
pci0: unknown at device 1.1 (no driver attached)
ohci0: SiS 5571 USB controller mem 0xe4904000-0xe4904fff irq 9 at 
device 1.2 on pci0

ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: SiS 5571 USB controller on ohci0
usb0: USB revision 1.0
uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pcib1: PCI-PCI bridge at device 2.0 on pci0
pci1: PCI bus on pcib1
pci1: display, VGA at device 0.0 (no driver attached)
rl0: D-Link DFE-530TX+ 10/100BaseTX port 0xd000-0xd0ff mem 
0xe4902000-0xe49020ff irq 11 at device 9.0 on pci0

miibus0: MII bus on rl0
rlphy0: RealTek internal media interface on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: xx:xx:xx:xx:xx:xx
rl1: D-Link DFE-530TX+ 10/100BaseTX port 0xd400-0xd4ff mem 
0xe4903000-0xe49030ff irq 10 at device 11.0 on pci0

miibus1: MII bus on rl1
rlphy1: RealTek internal media interface on miibus1
rlphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl1: Ethernet address: xx:xx:xx:xx:xx:xx
ral0: Ralink Technology RT2500 mem 0xe490-0xe4901fff irq 12 at 
device 13.0 on pci0

ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525
ral0: Ethernet address: xx:xx:xx:xx:xx:xx
pci0: multimedia, audio at device 15.0 (no driver attached)
fdc0: floppy drive controller port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: 1440-KB 3.5 drive on fdc0 drive 0
sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on 
acpi0

sio0: type 16550A, console
sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0: Standard parallel printer port port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: Parallel port bus on ppc0
plip0: PLIP network interface on ppbus0
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0

sysinstall new disc layout in 5.4 RELEASE

2005-05-10 Thread bazzoola
First, thanks for all the people who took the time and effort to make
this happen :)

I just finished downloading the images thru torrents. I burned both
i386 disc one and two then installed 5.4. Everything worked fine as
usual.

After that I decided to install new packages. I inserted disc2 then
typed sysinstall. then I went to post config and selected some pre
compiled packages to install. (like expat, apache, portsnap,
freebsd-update, etc.)
The installer started installing the packages from disc2 then it came
across expat the xml parser package and requested disc1. I inserted
disc1 and it installed expat after that it showed an error msg that it
cannot install apache because it was not found on the media. I thought
It should have asked for disc2 but it didnt.

Should this be considered a bug in sysinstall?

if this is the wrong mailing list please tell me where to forward.

Thanks again,
bazzoola
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: sysinstall new disc layout in 5.4 RELEASE

2005-05-10 Thread bazzoola
Jose M Rodriguez wrote:
El Martes, 10 de Mayo de 2005 18:15, Freddie Cash escribió:
 

On May 10, 2005 02:35 am, bazzoola wrote:
   

First, thanks for all the people who took the time and effort to
make this happen :)
I just finished downloading the images thru torrents. I burned both
i386 disc one and two then installed 5.4. Everything worked fine as
usual.
 

CD1 is the installation CD.  This includes about 400 MB of
pre-compiled packages that can be installed.
CD2 is a LiveCD mainly meant for rescue situations via sysinstall's
Fixit feature.
   

Not Any more.  Now Install/LiveCD/Rescue is done by disc1, which include 
also the packages needed by sysinstall.

disc2 is a collection of aditional packages that, at last in the i386 
case, include the full gnome/kde ports (Not lite).

--
 josemi
 

I know I do not have any problems with the new disc layout. All I am 
saying was:
1- I installed the FreeBSD 5.4 i386 on the system without any problems.
2- After I finished installing. I decided to install other packages so I 
ran sysinstall
3- when I ran sysinstall disc2 was inserted (it was just there)
4- I chose the new packages to install like expat, apache, portupgrade, 
portsnap, etc.
5- sysinstall installed the packages from disc2 then showed a msg that 
expat is located on disc1 and requested disc1
6- I inserted disc1 to fulfill the request and it installed the packages.
7- an error msg showed up saying that apache cannot be found on the 
media and it failed to install.

I know that apache is on disc2. All I was saying that sysinstall should 
have asked for disc2 to be inserted like it did for disc1.
All I did to fix this (obviously) I ran sysinstall again with disc2 
inserted and it installed it.
So, should this be considered a bug in sysinstall because it didnt ask 
for the disc even tho it should have known that it is located on disc2.

bazzoola
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]