On Mon, May 9, 2011 at 4:49 PM, Matthias Rampke
wrote:
> Re: IO APIC
>
> Disabling IO APIC didn't help with the SMP kernel, it complains about lapic
> initialization before dropping to the debugger (is there a LAPIC loader
> tunable? I can't find any documentation on this or hw.apic_io_enable).
I agree on the random video RAM contents thing - that would have been
my first guess.
The wireless connection Matt and I both had trouble with, with ath(4),
was using WPA2, though I don't know the device. If you want to try
different setups and see what works and what doesn't, that would make
a u
On Montag, 9. Mai 2011 at 09:47, Ivan Uemlianin wrote:
> One thing that happened both times: on startx, the laptop screen filled
> with semi-random-looking blocks of colour for a split second before
> going into the wm. I think I've seen this before on some linux
> installs. Presumably X is con
ave completely ballsed up your installation!" I
shan't reinstall (unless advised otherwise).
Although installing DragonFly on a virtual machine (e.g., VirtualBox) is
a good idea, many of my symptoms seem to be to do with the particular
hardware of the laptop. so I'll continue wit
This is a new bug, then, cause I think the original ath(4) problem is
fixed. I don't have the right laptop and wireless combo to test. In any
case, you may want to file a report including the network encryption type.
On May 7, 2011 4:16 AM, "Matthias Rampke" wrote:
> On Fri, 6 May 2011, Justin
On Fri, 6 May 2011, Justin Sherrill wrote:
sysctl net.wlan.force_swcrypto=1 may help.
http://leaf.dragonflybsd.org/mailarchive/commits/2010-11/msg00169.html
Works for me. Thank you!
-matthiasr
On Fri, May 6, 2011 at 10:03 AM, Matthias Rampke
wrote:
> Is this on the WLAN? Which card? I'm having massive trouble getting ath(4) to
> work with most WLAN routers, e.g. I don't receive the DHCPOFFERs from my home
> WLAN. My phone's WiFi hotspot (Motorola Milestone / CyanogenMod 6) works
> p
On Freitag, 6. Mai 2011 at 16:03, Matthias Rampke wrote:
>From what I gather SMP Kernels with IO APIC enabled don't work. I just settled
>on using UP since I only have one core anyway. You may try setting
>hw.apic_io_enable=0 in /boot/loader.conf
Sorry, that wasn't worded well. I meant to say tha
That's a good idea (and I have vbox to hand). Many of the problems
relate to the particular hardware (e.g., configuring the network), but I
could at least iron out the other problems. Thanks
Ivan
On 06/05/2011 15:54, Krzysztof Langer wrote:
Maybe you should try no-gui DFBSD image, perhaps
Maybe you should try no-gui DFBSD image, perhaps in VirtualBox (?) - it works
fine on Mac OS X.
That way, you can install & configure all your needed stuff from the ground up
(xorg, window manager, pkgsrc etc.) and copy most config files on your real DF
system.
Klanger
Dnia 6-05-2011 o godz.
Dear Tomas and Matthias
Thanks for these leads. I'll investigate and report back.
Best wishes
Ivan
--
Ivan A. Uemlianin
Speech Technology Research and Development
i...@llaisdy.com
www.llais
On Freitag, 6. Mai 2011 at 15:30, Ivan Uemlianin wrote:
Dear All
>
> I am installing DragonFly BSD onto a Thinkpad X60.
I recently installed on a X40, so let's see. There is also a page on the
Website about the T42[1] and the X61s[2], especially most of the latter should
apply to y
At least output of dmesg, pciconf and probably pictures of those
debugger output will be fine.
On Fri, May 6, 2011 at 3:30 PM, Ivan Uemlianin wrote:
> Dear All
>
> I am installing DragonFly BSD onto a Thinkpad X60. Actually, I have
> installed it, but perhaps not correctly.
Dear All
I am installing DragonFly BSD onto a Thinkpad X60. Actually, I have
installed it, but perhaps not correctly. Below are my symptoms. Please
can anybody help with any of them?
Some background: I am fairly familiar with Unix-like operating systems
(long time fan of Debian GNU
On Sun, Nov 8, 2009 at 4:26 PM, Karthik Subramanian
wrote:
> On Sun, Nov 8, 2009 at 4:05 PM, Sascha Wildner wrote:
>> Karthik Subramanian schrieb:
>>>
>>> Hi Folks,
>>>
>>> I'm trying to install DragonFly under qemu, using an ISO (this one's
>>> yesterday's snapshot, I think).
>>>
>>> It boots fi
On Sun, Nov 8, 2009 at 4:05 PM, Sascha Wildner wrote:
> Karthik Subramanian schrieb:
>>
>> Hi Folks,
>>
>> I'm trying to install DragonFly under qemu, using an ISO (this one's
>> yesterday's snapshot, I think).
>>
>> It boots fine, I'm able to login as root and everything seems to work OK.
>>
>> W
Karthik Subramanian schrieb:
Hi Folks,
I'm trying to install DragonFly under qemu, using an ISO (this one's
yesterday's snapshot, I think).
It boots fine, I'm able to login as root and everything seems to work OK.
When I try to login as installer, however, I get the following error message:
=
Hi Folks,
I'm trying to install DragonFly under qemu, using an ISO (this one's
yesterday's snapshot, I think).
It boots fine, I'm able to login as root and everything seems to work OK.
When I try to login as installer, however, I get the following error message:
=
Starting installer
Anyway, I ignored the possibility that it wasn't working, and
proceeded with the instructions.
And when I tried re-booting, from the disk drive, it worked!
At least, it almost worked. I have a dragonfly system, but it's not
quire right. (I think I edited /etc/fstab in the wrong place - I
forgot t
If I add an extra initial line:
4 partitions:
Then I no longer get the error message.
But it does say sector size 0, and just typing:
disklabel ad0s1
shows the same information as before.
2009/4/20 Colin Adams :
> I also tried saving the output from disklabel ad0s1 and just using the
> last pa
I also tried saving the output from disklabel ad0s1 and just using the
last part of that.
But I get the same error messages. It looks like a bug in disklabel to me.
2009/4/20 Colin Adams :
> Thanks.
>
> I am having problems with the disklabel.
>
> I get:
>
> line 2: partition name out of range a-`
On Sat, 18 Apr 2009 09:00:21 +0100
Colin Adams wrote:
> 2009/4/18 Jordan Gordeev :
> > Colin Adams wrote:
> >>
> >> I don't know if it is the same problem (it certainly sounds
> >> similar).
> >>
> >> This is not a laptop though. Nor is it an old machine (less than 3
> >> years old).
> >>
> >> An
2009/4/18 Jordan Gordeev :
> Colin Adams wrote:
>>
>> I don't know if it is the same problem (it certainly sounds similar).
>>
>> This is not a laptop though. Nor is it an old machine (less than 3 years
>> old).
>>
>> Anyway, I have booted DragonFly from the live CD and logged in as root.
>>
>> But
Colin Adams wrote:
I don't know if it is the same problem (it certainly sounds similar).
This is not a laptop though. Nor is it an old machine (less than 3 years old).
Anyway, I have booted DragonFly from the live CD and logged in as root.
But what device name do I use (I only have one disk)?
I don't know if it is the same problem (it certainly sounds similar).
This is not a laptop though. Nor is it an old machine (less than 3 years old).
Anyway, I have booted DragonFly from the live CD and logged in as root.
But what device name do I use (I only have one disk)? Everything I
guessed
Colin Adams wrote:
> I was able to install DragonFly on the disk all-right, but the
> machine still won't boot if the drive is powered-on at boot time.
I remember that I had a similar problem about 2 years ago with my Bullman
laptop.
http://leaf.dragonflybsd.org/mailarchive/users/2007-02/msg0
So linux fdisk says the following things about the disk:
/dev/sda1 Bootable Start 1 End 19382 Blocks 156290872+ Id a5 System FreeBSD
(I selected UFS rather than HAMMER when I installed DragonFly on it).
So everything looks fine, except I can't have it powered on at
Computer boot-time.
Perhaps I
I was able to install DragonFly on the disk all-right, but the
machine still won't boot if the drive is powered-on at boot time.
I'll have to try the linux live-cd fdisk :-(
2009/4/17 Colin Adams :
> Now I'm back home, i've tried out everyone's suggestions.
>
> Bill's idea to remove the hard-dis
Now I'm back home, i've tried out everyone's suggestions.
Bill's idea to remove the hard-disk from the boot-sequence made no
difference (I'm surprised - I thought that was just something obvious
that I had forgotten in my approaching senility).
The suggestion to only plug the hard-disk in after b
Colin Adams wrote:
I couldn't use Windows anything - that is banned from my house.
Good news, that. Should reduce your long-term rosk of stroke or hear attack.
;-)
Equally, I can't use a Linux fdisk (for instance), because I can't
boot the computer at all if the disk is plugged in.
If I rem
You can try booting a linux live cd, then plugging in the hdd after the bios
screen, but before the linux kernel starts running.
cheers
simon
Colin Adams wrote:
I couldn't use Windows anything - that is banned from my house.
Equally, I can't use a Linux fdisk (for instance), because I can't
I couldn't use Windows anything - that is banned from my house.
Equally, I can't use a Linux fdisk (for instance), because I can't
boot the computer at all if the disk is plugged in.
If I remove uncable the disk, then I can boot from the DragonFly live
DVD (or any other live CD/DVD presumably). Bu
I bet this is the "set all bits to one on CHS overflow" thing in fdisk. I'd
really like to know how we are supposed to handle this (better).
Colin, sorry for trashing your computer. I think we are well aware of this
issue, but we simply don't know exactly how to deal with it. Could you maybe
What appears to have happened is that in some way it has trashed my
disk-drive - I can still get the machine to boot from the live CD, but
only if I physically disconnect the hard-disk first.
2009/4/8 Hasso Tepper :
> Colin Adams wrote:
>> Well, if that is the case the ISO should not be available
:
:Colin Adams wrote:
:> Well, if that is the case the ISO should not be available for download
:> - there should be a fixed version.
:
:Well. It shouldn't be any way fatal, but in general I agree - we should
:release 2.2.1 ASAP, really.
:
:
:--
:Hasso Tepper
I'd love to but I'm so busy I h
Sascha Wildner wrote:
> Colin Adams schrieb:
>> I'm trying to install from the DVD.
>>
>> When i get to the login prompt, I type installer.
>>
>> Now every screen I come to, I get, in addition to the formatted screens,
>> I get:
>>
>> Login incorrect
>> login:
>>
>> Password:/i386 (dfly-live)
Colin Adams wrote:
> Well, if that is the case the ISO should not be available for download
> - there should be a fixed version.
Well. It shouldn't be any way fatal, but in general I agree - we should
release 2.2.1 ASAP, really.
--
Hasso Tepper
Well, if that is the case the ISO should not be available for download
- there should be a fixed version.
Meanwhile my PC appears to have been broken - I'm not sure if it was
caused by DragonFly or a coincidence.
I get stuck at an initial display after power-up with an intel logo,
And a message:
Colin Adams schrieb:
I'm trying to install from the DVD.
When i get to the login prompt, I type installer.
Now every screen I come to, I get, in addition to the formatted screens, I get:
Login incorrect
login:
Password:/i386 (dfly-live) (ttyv1)
login:
It appears I need some kind of passwor
I'm trying to install from the DVD.
When i get to the login prompt, I type installer.
Now every screen I come to, I get, in addition to the formatted screens, I get:
Login incorrect
login:
Password:/i386 (dfly-live) (ttyv1)
login:
It appears I need some kind of password to login as installer
:Hi,
:
:* [EMAIL PROTECTED] wrote:
:> The script doesn't seem to work. Firstly I had to change ad6 to ad4, and
:> remove a line saying "exit 1" after the 10 second warning. The partitions
:> get created but it seems that most of the important stuff doesn't get
:> cpduped over as for example the /b
Hi,
* [EMAIL PROTECTED] wrote:
> The script doesn't seem to work. Firstly I had to change ad6 to ad4, and
> remove a line saying "exit 1" after the 10 second warning. The partitions
> get created but it seems that most of the important stuff doesn't get
> cpduped over as for example the /boot part
The script doesn't seem to work. Firstly I had to change ad6 to ad4, and
remove a line saying "exit 1" after the 10 second warning. The partitions
get created but it seems that most of the important stuff doesn't get
cpduped over as for example the /boot partition ONLY has 1 file in it
(loader.conf
Petr Janda schrieb:
Is it yet possible or is it coming? 1) Does the installer support selection of
file system. I need to install a DragonFly OS and i definately need at
least /home and /usr on Hammer, but I want to do it during the install, not
complicatedly after the install. Can someone show
Hi,
* Petr Janda wrote:
> Is it yet possible or is it coming? 1) Does the installer support selection
> of
> file system. I need to install a DragonFly OS and i definately need at
> least /home and /usr on Hammer, but I want to do it during the install, not
> complicatedly after the install. C
Is it yet possible or is it coming? 1) Does the installer support selection of
file system. I need to install a DragonFly OS and i definately need at
least /home and /usr on Hammer, but I want to do it during the install, not
complicatedly after the install. Can someone show me how?
2) is /boot
Okay Sascha thanks! I'm going to re-install my desktop once that build
is available. Just let me know.
On 7/22/08, Sascha Wildner <[EMAIL PROTECTED]> wrote:
> Sascha Wildner schrieb:
>> I don't think adding packages from the installer works (it probably
>> still assumes that we're using FreeBSD po
Sascha Wildner schrieb:
I don't think adding packages from the installer works (it probably
still assumes that we're using FreeBSD ports).
I take that back.
The path for the package tools was wrong. I've changed it in HEAD and
the 2.0 branch. Although I'm not sure if there aren't other issues
Archimedes Gaviola schrieb:
First of all, congratulations for this new release of DragonFly! I've
tried installing on my desktop PC but I encountered some errors while
adding software packages (checked all) but suddenly it prompts for
"Packages were successfully installed!". Below are the errors
Hi,
First of all, congratulations for this new release of DragonFly! I've
tried installing on my desktop PC but I encountered some errors while
adding software packages (checked all) but suddenly it prompts for
"Packages were successfully installed!". Below are the errors I've
encountered.
--
Can anybody confirm that this still works? When I try to upgrade a
FreeBSD 4.9 system to DragonFly 1.2 following the procedure outlined
in this document, make buildworld fails in /usr/src/usr.bin/mklocale.
What error do you get?
===> usr.bin/mklocale (bootstrap-tools)
/usr/obj/usr/src/btool
On Sat, February 16, 2008 2:27 pm, Sascha Wildner wrote:
> Andre LeClaire wrote:
>> I would like to go this route to migrate some production servers that
>> are currently running FBSD 4.11 to DragonFly, if possible.
>
> Yeah, some kind of more or less convenient upgrade path for FreeBSD 4
> users
:Where is the big difference between doing a buildworld, buildkernel,=20
:installkernel, installworld or doing a binary update? Maybe we should=20
:encourage people to do this instead? I even thought the installer had an=
:=20
:option. If not, "just" copying over /kernel /modules /usr /bin/sbin
Sascha Wildner wrote:
I would like to go this route to migrate some production servers that
are currently running FBSD 4.11 to DragonFly, if possible.
Yeah, some kind of more or less convenient upgrade path for FreeBSD 4
users would be nice to have.
Where is the big difference between doing a
Andre LeClaire wrote:
Can anybody confirm that this still works? When I try to upgrade a
FreeBSD 4.9 system to DragonFly 1.2 following the procedure outlined in
this document, make buildworld fails in /usr/src/usr.bin/mklocale.
What error do you get?
I would like to go this route to migrate
:Hmm, but he's trying FreeBSD 4 -> DragonFly 1.2, something which seems
:to have been working at some point.
:
:Strange..
:
:Sascha
:
:--
:http://yoyodyne.ath.cx
It's possible that the CVS surgery we've done over the years has messed
up 1.2 with regards to building from FreeBSD. Even m
Matthew Dillon wrote:
I really doubt that you can build the dragonfly kernel from inside
FreeBSD any more, short of booting a DragonFly CD in a virtual machine
and building it there.
Hmm, but he's trying FreeBSD 4 -> DragonFly 1.2, something which seems
to have been working at some
:Can anybody confirm that this still works? When I try to upgrade a
:FreeBSD 4.9 system to DragonFly 1.2 following the procedure outlined in
:this document, make buildworld fails in /usr/src/usr.bin/mklocale.
:I would like to go this route to migrate some production servers that
:are currently
though it seems to be supported to build (some releases) of DragonFly on
(some releases) of FreeBSD and cross-install them, I can't get it to
work.
I tried building 1.0, 1.2, 1.4, 1.6 and 1.10 on 4.11, 5.5, 6.0 and 8.0.
They all quickly die in buildworld during bootstrap-tools phase. Even
plaster
On Thu, 14.02.2008 at 22:16:38 +0100, Simon 'corecode' Schubert wrote:
> Ulrich Spoerlein wrote:
> > /modules/acpi.ko text=0x477c0 data=0x2034+0xc98 syms=[0x4+0x6e60+0x4+0x8bfc]
> > -
> >
> > And then it's dead
>
> Are you sure (sure sure) it is dead? I had the situation that it would
> simply
Ulrich Spoerlein wrote:
/modules/acpi.ko text=0x477c0 data=0x2034+0xc98 syms=[0x4+0x6e60+0x4+0x8bfc]
-
And then it's dead
Are you sure (sure sure) it is dead? I had the situation that it would
simply not use the console, and at some point the Login: prompt would show
up (maybe won't happen
On Thu, February 14, 2008 3:08 pm, Ulrich Spoerlein wrote:
> Hi there,
>
> though it seems to be supported to build (some releases) of DragonFly on
> (some releases) of FreeBSD and cross-install them, I can't get it to
> work.
>
> I tried building 1.0, 1.2, 1.4, 1.6 and 1.10 on 4.11, 5.5, 6.0 and 8
Hi there,
though it seems to be supported to build (some releases) of DragonFly on
(some releases) of FreeBSD and cross-install them, I can't get it to
work.
I tried building 1.0, 1.2, 1.4, 1.6 and 1.10 on 4.11, 5.5, 6.0 and 8.0.
They all quickly die in buildworld during bootstrap-tools phase. Ev
Simon 'corecode' Schubert wrote:
Michael Neumann wrote:
I don't know about the issues involved with different disk geometries,
but as this is the only difference I see between DragonFly 1.4 and
1.8, maybe this might be a problem?
Possibly not. Try using fdisk with -C. Your BIOS might stumbl
Michael Neumann wrote:
I don't know about the issues involved with different disk geometries,
but as this is the only difference I see between DragonFly 1.4 and 1.8,
maybe this might be a problem?
Possibly not. Try using fdisk with -C. Your BIOS might stumble upon these
values.
cheers
sim
Rauf Kuliyev wrote:
Hi,
I bet it is IBM ThinkPad. You can find additional information here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#BOOT-ON-THINKPAD
No it isn't a ThinkPad, it's a Bullman (noname), similar to an Acer.
FreeBSD runs without change to the bootblock.
Ne
Hi,
I bet it is IBM ThinkPad. You can find additional information here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#BOOT-ON-THINKPAD
Regards,
Rauf
On 2/19/07, Michael Neumann <[EMAIL PROTECTED]> wrote:
Hi,
Just a few minutes ago, I installed Dragonfly 1.8 onto my laptop.
Michael Neumann wrote:
Hi,
Just a few minutes ago, I installed Dragonfly 1.8 onto my laptop.
Then I rebooted, and the BIOS hung up completely after showing that it
detected the harddisk and cdrom. I powered down and tried again, but
that didn't worked either. I couldn't even boot a CD or anyth
Hi,
Just a few minutes ago, I installed Dragonfly 1.8 onto my laptop.
Then I rebooted, and the BIOS hung up completely after showing that it
detected the harddisk and cdrom. I powered down and tried again, but
that didn't worked either. I couldn't even boot a CD or anything else or
couldn't ev
On Fri, 26 Aug 2005 10:10:14 +0300
Eugene <[EMAIL PROTECTED]> wrote:
> Chris Pressey wrote:
>
> >Because DragonFly and FreeBSD have the same partition id (165,)
> >FreeBSD's installer will see the DragonFly partition as a FreeBSD
> >slice. And, *even if you don't set up any BSD partitions on the
Chris Pressey wrote:
Because DragonFly and FreeBSD have the same partition id (165,)
FreeBSD's installer will see the DragonFly partition as a FreeBSD slice.
And, *even if you don't set up any BSD partitions on the DragonFly
partition*, the installer will erase the DragonFly partition's
disklabe
[25-Aug-2005 20:58.39 (BST) / Freddie Cash]
> GRUB 0.9.5 and above supports UFS1 and UFS2. And you don't need to use
> chainloader to load the BSD loader. You just set the kernel option in
> GRUB to /boot/loader.
This is where my knowledge of grub booting FreeBSD & DragonFly natively
break
fcash-ml wrote @ Thu, 25 Aug 2005 12:58:39 -0700:
> On August 25, 2005 12:45 pm, Rob Andrews wrote:
> > [25-Aug-2005 17:59.00 (BST) / Chris Pressey]
> > Be warned, grub may not support the ufs filesystem you choose to
> > install it upon. If grub can't read the stage2 files from your
> > filesyste
On August 25, 2005 12:45 pm, Rob Andrews wrote:
> [25-Aug-2005 17:59.00 (BST) / Chris Pressey]
> > I haven't tested any workarounds yet, but I suspect that marking
> > the DragonFly partition with some other partition id (like MS-DOS)
> > before installing, and marking it back after installing,
[25-Aug-2005 17:59.00 (BST) / Chris Pressey]
> I haven't tested any workarounds yet, but I suspect that marking the
> DragonFly partition with some other partition id (like MS-DOS) before
> installing, and marking it back after installing, would be enough to
> trick FreeBSD's installer into ign
Here's something I found out the hard way last night:
If you already have DragonFly on a disk (say partition 1) and you want
to install FreeBSD on that disk (say partition 2), you have to be very
careful.
Because DragonFly and FreeBSD have the same partition id (165,)
FreeBSD's installer will see
76 matches
Mail list logo