Re: What's the status of the USB stack port?
On Mon, Sep 3, 2012 at 11:56 AM, Markus Pfeiffer markus.pfeif...@morphism.de wrote: Hello, On Sat, Sep 01, 2012 at 07:44:47PM +1000, elekktrett...@exemail.com.au wrote: Hi all, Last time I heard there was someone working on the port. I'd be willing to test (my dragonfly installation is long not used because my USB peripherals - keyboard etc are not working with the existing USB stack) Thanks for your offer! I am currently caught up in getting my PhD submitted. Once that is done and I have settled in at my new work space I will finish the port pretty quickly I guess. I also thank Sascha for putting the effort in to get USB into master. I guess by the end of September you will be able to use the USB stack as a replacement for the old one. Out of interest, does the new USB stack support xHCI?
Re: DragonFly GUI desktop at work - not bad at all
On Fri, Jul 20, 2012 at 9:07 PM, John Marino dragonfly...@marino.st wrote: On 7/20/2012 20:53, Carsten Mattner wrote: On Fri, Jul 20, 2012 at 8:33 PM, Stéphane Russell Complaining is important, but contributing platform support patches (if you have the skills) would possibly be a better choice, wouldn't it? Besides that statement also applying to yourself, the answer is no. The BSD community simply will not accept the substandard replacements of BSD functionality that Linux is adding to gnome. I don't use any of the DEs. So, I don't really have an itch, sorry. In other words, the functionality is already on BSD, Linux people are reinventing the wheel, and coming up with a worse product. The BSD folks I'm new to BSDs again after a hiatus of approximately 12 years. Therefore excuse my knowledge gap. What functionality are you referring to? Is it something that also already exists in the Linux world but is reinvented? will just stick with what they have as it's better. That's one of the issues and no amount of patch skills is going to fix that. It's a philosophical difference. Lennart Poettering: BSD isn't relevant anymore http://bsd.slashdot.org/story/11/07/16/0020243/Lennart-Poettering-BSD-Isnt-Relevant-Anymore Slashdot sensationalism, but basically gnome doesn't care if it's BSD-friendly or not and it's diverging to the point of no compatibility. While that's true, from what I read they do welcome patches to support the new stack on other platforms. It's true though that their focus has changed with more work going into adding layers of plumbing.
Re: DragonFly GUI desktop at work - not bad at all
On Fri, Jul 20, 2012 at 8:33 PM, Stéphane Russell sruss...@prodigeinfo.qc.ca wrote: John Marino a écrit : On 7/20/2012 17:12, Stéphane Russell wrote: Wojciech Puchar a écrit : despite of an error message at startup is working fine, as long as I'm not trying to configure it, since GConf is not working. just use windows manager like cwm or fvwm2+your own configuration. I for example use my 9 year old .fvwm2rc which results in cwm-alike environment. it's really easier to just run program you need (like openoffice writer, mail client, gimp etc.) instead of running bells and whistles like Gnome. I assume you need workstation (==computer to do actual work). Gnome nor XFCE nor KDE doesn't help in doing actual work. I always try to use Gnome whenever possible, and fall back to XFCE when it's not. It might be time to rethink that approach. The gnome library version numbers are all mismatched. Some are 2.24, others 2.26, others 2.32. Effectively they can't all be brought to the current level of glib2 due to the increasing amount of linux-only functionality there. The days of Gnome on non-Linux might be numbered, at least modern Gnome... On the flipside, KDE has been compiling completely and all the modules have matching versions numbers. Currently KDE 3.5 just lost regressed a module or two, but before that we had fully building KDE 3.5 and 4.8.x. XFCE has been building as well, but it's still on 4.6 John I think your right about this. Even the Illumos community complains about this. Complaining is important, but contributing platform support patches (if you have the skills) would possibly be a better choice, wouldn't it?
Re: questions from FreeBSD user
On Mon, Jul 16, 2012 at 8:08 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: For now i am FreeBSD user, but when i read what are proposed by developers(!) for FreeBSD i clearly understand i will need something else. Which FreeBSD plans do you find worrisome?
Re: questions from FreeBSD user
On Mon, Jul 16, 2012 at 12:18 PM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: For now i am FreeBSD user, but when i read what are proposed by developers(!) for FreeBSD i clearly understand i will need something else. Which FreeBSD plans do you find worrisome? more and more user friendly features that are proposed as well as confirmed by developers. Read FreeBSD-hackers mailing lists since 2 months. Found training wheels and replacing rc(8) threads. Anything else?
Re: machine won't start
On Wed, Jul 4, 2012 at 2:58 AM, Edward M martinezedward...@gmail.com wrote: On 07/03/2012 02:15 PM, Carsten Mattner wrote: At that point I hit hard (cold) reset and since that time the machine won't leave the BIOS startup phase (POST?). Took out the CMOS battery for a minute to no avail. Anything else I should try? Is it possible that the ROM or CPU has been damaged by the installer? I can't even get into the BIOS via DEL. I'll take out the CMOS battery overnight and try tomorrow. Thanks for any help. . Sounds like identical problem i was having with my old intel based laptop. After the first reboot, following an install, it would get stuck on the BIOS screen. i had to do. turn off the system, remove the hd, connect it on an another system and install another os, erasing dragonfly. reconnect the hd back to the laptop then the laptop would boot fine. unfortunately, i never found the solution, the hd pins were beginning to bend from removing the hd alot trying to find a workaround. The most important questions are - will the installer always corrupt the hdd in this machine? - is there a plan to fix this?
Re: machine won't start
On Tue, Jul 3, 2012 at 11:30 PM, Sascha Wildner s...@online.de wrote: On Tue, 03 Jul 2012 23:15:47 +0200, Carsten Mattner carstenmatt...@gmail.com wrote: Hi, I tried to install dfly 3.0.2 on an old amd64 box. When setup was in the configuration phase it didn't allow setting passwords with : or other characters. At that point I hit hard (cold) reset and since that time the machine won't leave the BIOS startup phase (POST?). Took out the CMOS battery for a minute to no avail. Anything else I should try? Is it possible that the ROM or CPU has been damaged by the installer? I can't even get into the BIOS via DEL. I'll take out the CMOS battery overnight and try tomorrow. Thanks for any help. It sounds like http://bugs.dragonflybsd.org/issues/989 Sascha, is it be safe to assume that once I've made the disk functional NetBSD, FreeBSD, or OpenBSD would not have the problem? I'm not sure after reading the bug report.
Re: machine won't start
On Wed, Jul 4, 2012 at 7:31 PM, Matthew Dillon dil...@apollo.backplane.com wrote: Normally this issue can be fixed by setting the BIOS to access the disk in LBA or LARGE mode. The problem is due to a bug in the BIOS's attempt to interpret the slice table in CHS mode instead of logical block mode. It's a BIOS bug. These old BIOS's make a lot of assumptions w/regards to the contents of the slice table, including making explicit checks for particular OS types in the table. I've only ever seen the problem on old machines, and I've always been able to solve it by setting the BIOS access mode. I've never, ever found a slice table format that works properly across all BIOSs. At this juncture we are using only newer (newer being 'only' 25+ years old) slice table formats (aka LBA layouts and using proper capped values for hard drives that are larger than the 32-bit LBA layout can handle). Ultimately we will want to start formatting things w/GPT, but that opens up a whole new can of worms... old BIOSes can explode even more easily when presented with a GPT's compat slice format, at least as defined by GPT. Numerous vendors such as Apple modified their GPT to try to work around the even larger number of BIOS bugs related to GPT formatting than were present for the older LBA formatting. I consider it almost a lost cause. -Matt Thanks Matt for the explanation and tip. It did of course hang when I tried to DEL into the BIOS. What worked is pulling out the sata connector, entering the BIOS putting it back and then detecting the disk. Interesting the auto detection then worked. I've explicitly set it to LARGE and now I can boot a rescue cd. How many bytes should I zero out for the disk to be normal again? 512bytes? 4megs?
Re: machine won't start
On Wed, Jul 4, 2012 at 8:07 PM, Matthew Dillon dil...@apollo.backplane.com wrote: :Thanks Matt for the explanation and tip. : :It did of course hang when I tried to DEL into the BIOS. :What worked is pulling out the sata connector, entering :the BIOS putting it back and then detecting the disk. :Interesting the auto detection then worked. I've explicitly :set it to LARGE and now I can boot a rescue cd. : :How many bytes should I zero out for the disk to be :normal again? 512bytes? 4megs? The BIOS is basically just accessing the slice table in the first 512 bytes of the disk. If I want to completely wipe a non-GPT formatted disk I usually zero-out (with dd) the first ~32MB or so to catch both the slice table and the stage-2 boot and the disklabel and the likely filesystem header. Destroying a GPT disk requires (to be safe) zero'ing out both the first AND the last X bytes of the physical media to also ensure that the backup GPT table is also scrapped. Again, to be safe I zero-out around 32MB at the beginning and 32MB at the end w/dd (if it's GPT). How do I tell dd to delete x bytes at the end of device? Negative values? This will effectively destroy everything on the disk from the point of view of probing, so please note that these instructions are NOT going to leave multi-OS installations intact.
Re: machine won't start
On Wed, Jul 4, 2012 at 8:11 PM, Carsten Mattner carstenmatt...@gmail.com wrote: On Wed, Jul 4, 2012 at 8:07 PM, Matthew Dillon dil...@apollo.backplane.com wrote: :Thanks Matt for the explanation and tip. : :It did of course hang when I tried to DEL into the BIOS. :What worked is pulling out the sata connector, entering :the BIOS putting it back and then detecting the disk. :Interesting the auto detection then worked. I've explicitly :set it to LARGE and now I can boot a rescue cd. : :How many bytes should I zero out for the disk to be :normal again? 512bytes? 4megs? The BIOS is basically just accessing the slice table in the first 512 bytes of the disk. If I want to completely wipe a non-GPT formatted disk I usually zero-out (with dd) the first ~32MB or so to catch both the slice table and the stage-2 boot and the disklabel and the likely filesystem header. Destroying a GPT disk requires (to be safe) zero'ing out both the first AND the last X bytes of the physical media to also ensure that the backup GPT table is also scrapped. Again, to be safe I zero-out around 32MB at the beginning and 32MB at the end w/dd (if it's GPT). How do I tell dd to delete x bytes at the end of device? Negative values? Will try seek=nG
Re: machine won't start
On Wed, Jul 4, 2012 at 8:16 PM, Carsten Mattner carstenmatt...@gmail.com wrote: On Wed, Jul 4, 2012 at 8:11 PM, Carsten Mattner carstenmatt...@gmail.com wrote: On Wed, Jul 4, 2012 at 8:07 PM, Matthew Dillon dil...@apollo.backplane.com wrote: :Thanks Matt for the explanation and tip. : :It did of course hang when I tried to DEL into the BIOS. :What worked is pulling out the sata connector, entering :the BIOS putting it back and then detecting the disk. :Interesting the auto detection then worked. I've explicitly :set it to LARGE and now I can boot a rescue cd. : :How many bytes should I zero out for the disk to be :normal again? 512bytes? 4megs? The BIOS is basically just accessing the slice table in the first 512 bytes of the disk. If I want to completely wipe a non-GPT formatted disk I usually zero-out (with dd) the first ~32MB or so to catch both the slice table and the stage-2 boot and the disklabel and the likely filesystem header. Destroying a GPT disk requires (to be safe) zero'ing out both the first AND the last X bytes of the physical media to also ensure that the backup GPT table is also scrapped. Again, to be safe I zero-out around 32MB at the beginning and 32MB at the end w/dd (if it's GPT). How do I tell dd to delete x bytes at the end of device? Negative values? Will try seek=nG dd's seek= operates on blocks so have to supply multiple of bs=. Thanks again Matt and everybody.
Re: machine won't start
On Tue, Jul 3, 2012 at 11:30 PM, Sascha Wildner s...@online.de wrote: On Tue, 03 Jul 2012 23:15:47 +0200, Carsten Mattner carstenmatt...@gmail.com wrote: Hi, I tried to install dfly 3.0.2 on an old amd64 box. When setup was in the configuration phase it didn't allow setting passwords with : or other characters. At that point I hit hard (cold) reset and since that time the machine won't leave the BIOS startup phase (POST?). Took out the CMOS battery for a minute to no avail. Anything else I should try? Is it possible that the ROM or CPU has been damaged by the installer? I can't even get into the BIOS via DEL. I'll take out the CMOS battery overnight and try tomorrow. Thanks for any help. It sounds like http://bugs.dragonflybsd.org/issues/989 Pulled out the hdd, put the battery back, started. First the 4 POST LEDs looked like this GREEN RED GREEN GREEN After loading default settings in the BIOS and doing some changes and saving all of it and restarting all LEDs went green. Thanks Sascha. Now I only need to find a way get the HDD content repaired. Suggestions? Can I use the same machine? I suppose I'll have to buy or find a USB adapter to connext the 3.5 SATA disk? This is the first time I saw a BIOS hang caused by harddisk content.
Re: machine won't start
On Tue, Jul 3, 2012 at 11:55 PM, Carsten Mattner carstenmatt...@gmail.com wrote: On Tue, Jul 3, 2012 at 11:30 PM, Sascha Wildner s...@online.de wrote: On Tue, 03 Jul 2012 23:15:47 +0200, Carsten Mattner carstenmatt...@gmail.com wrote: Hi, I tried to install dfly 3.0.2 on an old amd64 box. When setup was in the configuration phase it didn't allow setting passwords with : or other characters. At that point I hit hard (cold) reset and since that time the machine won't leave the BIOS startup phase (POST?). Took out the CMOS battery for a minute to no avail. Anything else I should try? Is it possible that the ROM or CPU has been damaged by the installer? I can't even get into the BIOS via DEL. I'll take out the CMOS battery overnight and try tomorrow. Thanks for any help. It sounds like http://bugs.dragonflybsd.org/issues/989 Pulled out the hdd, put the battery back, started. First the 4 POST LEDs looked like this GREEN RED GREEN GREEN After loading default settings in the BIOS and doing some changes and saving all of it and restarting all LEDs went green. Thanks Sascha. Now I only need to find a way get the HDD content repaired. Suggestions? Can I use the same machine? I suppose I'll have to buy or find a USB adapter to connext the 3.5 SATA disk? This is the first time I saw a BIOS hang caused by harddisk content. The important question is if the disk would have been incompatible in content even if I hadn't hard-resetted the machine while in the installer. ?
Re: machine won't start
On Tue, Jul 3, 2012 at 11:42 PM, Raimundo Santos rait...@gmail.com wrote: Well... you are very lucky! :) Always have identical spare mainboard just in case? Try to boot without the HDD and see what happens. That worked see the other reply.
Re: Single boot EFI Mac install
On Fri, Mar 23, 2012 at 12:05 AM, peeter (must) karu.pr...@gmail.com wrote: Thanks again, partial success so far: could get refit working but apparently refit does not boot dfly, or at least not yet. I made two partitions for dfly as described in the README on the live cd, a ufs partition for /boot and hammer partition for the rest. refit recognizes the boot partition as a FreeBSD one and when I choose to boot it in the refit many then I get a blank screen and then No bootable device -- insert boot disk and press any key. Then the computer hangs. 2 GPT partitions or 2 slices in the dragonfly partition? I thought it might be since refit isn't familiar with 64bit disklablel but using disklabel32 gives the same result. I tried to gptsync the partition tables but refit refuses; refit sees dfly partitions as Unknown and refuses to do anything with them. I thought there might be a way to force gptsync but refit shell hasn't got gptsync. Did you use a GPT aware partitioning tool? (g)parted or cgdisk on Linux livecds (sysresccd etc.) or Apple's Disk Util. 2 GPT partitions as described in Boot setup http://leaf.dragonflybsd.org/cgi/web-man?command=gptsection=8 However, this might be outdated. As far as I understand, gpt was ported from freebsd; freebsd has moved on to gpart now. refit gptsync complained about gpt partitions. When I installed freebsd and used gpart, then refit was satsified. I tried installing freebsd on an external usb stick. And succeeded: so this is the first time I've succeeded in getting a BSD running on this 13 MBPro! Booting sequence is then: MacEFI -- refit -- fbsd It turns out fbsd has two exclusive types of partioning schemes. The old one, bsd slices; and gpt. They are exclusive: you can't disklabel gpt slices. And you should created one gpt slice for each partition you want, so eg /dev/ada0p1 /boot /dev/ada0p2 swap /dev/ada0p3 / and so on, as many as you like. dfly man 8 gpt is not quite consistent with this. dfly disklabels a gpt slice. Fbsd gpt booting scheme involves a small 64k partition that consists of a loader, /boot/gptboot, see http://www.freebsd.org/cgi/man.cgi?query=gpartapropos=0sektion=0manpath=FreeBSD+9.0-RELEASEarch=defaultformat=html However, success did not last long; at the next boot I got Missing operating system -- a different error message from the last time. I did not touch any freebsd partitions, and have no clue what happened. I never regained booting to that system. Installed fbsd on the harddisk and could gptsync and everything. But refit boot leads to Missing operating system. That usually happens if something changed in the partition table and it was not synced for BIOS mode boot to work. Maybe try with a 1MB BIOS BOOT partition prior to the DragonFly partitions? I haven't needed it, but I know that Fedora Linux insist on adding it if GPT is in use (or always? not sure). I wonder if there's a way to make refit recognize how to boot from the I've never booted a BSD via rEFIt. Is it possible you need to have a 1MB BIOS BOOT partition as the 3rd partition? dfly ufs partition? I was browsing around to find if grub2 might work but haven't found the right .efi image yet. The following is what should work, but I didn't try it out for BSDs. You could of course install a grub.efi image inside the HFS+ partition and then provide a grub.cfg with the chainloader config or kernel loader config based on one of the myriads of grub2 plugins for booting dragonfly. Creating a grub2.efi image file is not hard. Get a livecd with grub2-efi-32 and then use usegrub-mkimage to create an efi image file by selection all plugins/modules you want and the output filename. Once you have that, write or generate a grub.cfg and put it in the same directory. Next bless the grub efi image instead of refit.efi in the OSX installer's terminal. If you have an Nvidia or ATI video adapter you might have to load one of the video bios grub plugins or just boot with rEFIt to avoid such issues. I will try grub32 next. Another thought: if dfly could port /boot/gptboot from fbsd and set up similar booting scheme, then efi booting might be solved? Sorry I can't help you with that.
Re: Single boot EFI Mac install
On Thu, Mar 22, 2012 at 12:28 AM, peeter (must) karu.pr...@gmail.com wrote: Thanks again, partial success so far: could get refit working but apparently refit does not boot dfly, or at least not yet. I made two partitions for dfly as described in the README on the live cd, a ufs partition for /boot and hammer partition for the rest. refit recognizes the boot partition as a FreeBSD one and when I choose to boot it in the refit many then I get a blank screen and then No bootable device -- insert boot disk and press any key. Then the computer hangs. 2 GPT partitions or 2 slices in the dragonfly partition? I thought it might be since refit isn't familiar with 64bit disklablel but using disklabel32 gives the same result. I tried to gptsync the partition tables but refit refuses; refit sees dfly partitions as Unknown and refuses to do anything with them. I thought there might be a way to force gptsync but refit shell hasn't got gptsync. Did you use a GPT aware partitioning tool? (g)parted or cgdisk on Linux livecds (sysresccd etc.) or Apple's Disk Util. I wonder if there's a way to make refit recognize how to boot from the I've never booted a BSD via rEFIt. Is it possible you need to have a 1MB BIOS BOOT partition as the 3rd partition? dfly ufs partition? I was browsing around to find if grub2 might work but haven't found the right .efi image yet. The following is what should work, but I didn't try it out for BSDs. You could of course install a grub.efi image inside the HFS+ partition and then provide a grub.cfg with the chainloader config or kernel loader config based on one of the myriads of grub2 plugins for booting dragonfly. Creating a grub2.efi image file is not hard. Get a livecd with grub2-efi-32 and then use usegrub-mkimage to create an efi image file by selection all plugins/modules you want and the output filename. Once you have that, write or generate a grub.cfg and put it in the same directory. Next bless the grub efi image instead of refit.efi in the OSX installer's terminal. If you have an Nvidia or ATI video adapter you might have to load one of the video bios grub plugins or just boot with rEFIt to avoid such issues.
Re: Single boot EFI Mac install
On Tue, Mar 20, 2012 at 2:09 PM, peeter (must) karu.pr...@gmail.com wrote: On Mon, Mar 19, 2012 at 9:08 PM, Carsten Mattner carstenmatt...@googlemail.com wrote: On Mon, Mar 19, 2012 at 7:41 PM, peeter (must) karu.pr...@gmail.com wrote: On Wed, Mar 7, 2012 at 1:32 PM, Carsten Mattner carstenmatt...@googlemail.com wrote: Has anyone successfully installed DragonFly as a single boot system on an EFI Mac? I'd be interested in this too. I failed: got the boot prompt and then the boot process hung. I also tried a gpt setup described on 'man gpt' but got the same result. I would be interested in setting up a dual boot but can't risk losing the main system, currently macosx. On a positive note, rEFIt recognized the DFBSD slice and gave the boot prompt, so something goes wrong after that. What I've learned for Mac 32-bit EFI and how to use it without OS X but with rEFIt to allow booting all kinds of systems: - boot the OS X installer - start Disk Util - create a 200MB (it will actually force it to 1GB) HFS+ partition - now you will have a 200MB unused FAT EFI protected partition and a 1GB HFS+ partition - boot a livecd which has a partitioning tool that can resize the HFS+ partition - resize parition #2 (HFS+ 1GB) to 200MB, that should be enough - reboot into the OS X installer again - put rEFIt on the HFS+ partition - bless --folder ... etc. (see the shell script in rEFIt for the command) to bless refit.efi - if the resizing tool is non-destructive you could avoid booting twice into the OS X installer and instead extract and configure rEFIt on the 1GB partition - reboot - rEFIt should show up - if BSD or Linux doesn't properly boot, make sure the hybdrid partition table is synced (gptsync). rEFIt's partition tool menu item should suggest to sync if needed - if the installed rEFIt doesn't have the partition tool menu item boot rEFIt ISO - depending on what OS and bootloader you use you might want to add a 3rd partition of 1MB size and type BIOS BOOT before BSD or Linux. PS: I'm not subscribed to u...@crater.dragonflybsd.org anymore. If this is filtered, someone has to moderate it onto the list. Thanks a lot for this! Will try as soon as I get a moment. When I said you should create a HF+ partition I forgot that you should - assuming you want to have a single-boot system - Repartition the disk as GPT with a single HFS+ partition of 1GB size and then resize that to 200MB. Now you will have a GPT partition with a 200MB EFI FAT and 1GB HFS+ partition.
Re: Single boot EFI Mac install
On Mon, Mar 19, 2012 at 7:41 PM, peeter (must) karu.pr...@gmail.com wrote: On Wed, Mar 7, 2012 at 1:32 PM, Carsten Mattner carstenmatt...@googlemail.com wrote: Has anyone successfully installed DragonFly as a single boot system on an EFI Mac? I'd be interested in this too. I failed: got the boot prompt and then the boot process hung. I also tried a gpt setup described on 'man gpt' but got the same result. I would be interested in setting up a dual boot but can't risk losing the main system, currently macosx. On a positive note, rEFIt recognized the DFBSD slice and gave the boot prompt, so something goes wrong after that. What I've learned for Mac 32-bit EFI and how to use it without OS X but with rEFIt to allow booting all kinds of systems: - boot the OS X installer - start Disk Util - create a 200MB (it will actually force it to 1GB) HFS+ partition - now you will have a 200MB unused FAT EFI protected partition and a 1GB HFS+ partition - boot a livecd which has a partitioning tool that can resize the HFS+ partition - resize parition #2 (HFS+ 1GB) to 200MB, that should be enough - reboot into the OS X installer again - put rEFIt on the HFS+ partition - bless --folder ... etc. (see the shell script in rEFIt for the command) to bless refit.efi - if the resizing tool is non-destructive you could avoid booting twice into the OS X installer and instead extract and configure rEFIt on the 1GB partition - reboot - rEFIt should show up - if BSD or Linux doesn't properly boot, make sure the hybdrid partition table is synced (gptsync). rEFIt's partition tool menu item should suggest to sync if needed - if the installed rEFIt doesn't have the partition tool menu item boot rEFIt ISO - depending on what OS and bootloader you use you might want to add a 3rd partition of 1MB size and type BIOS BOOT before BSD or Linux. PS: I'm not subscribed to u...@crater.dragonflybsd.org anymore. If this is filtered, someone has to moderate it onto the list.
Single boot EFI Mac install
Has anyone successfully installed DragonFly as a single boot system on an EFI Mac?
