Re: CD install on new Dell Dimension E521
Does the same thing. On Oct 22, 2006, at 10:14 AM, Lowell Gilbert wrote: Paul Root [EMAIL PROTECTED] writes: I just got a Dimension e521 that I'm going to install FreeBSD on. I'm having some trouble. I've tried the 6.1-RELEASE i386 DVD, I've downloaded the 6.1-Release CD iso for AMD64 I've downloaded the 6.2-Beta2 CD (today 10/20) for AMD64. All give the same error: panic: ohci_add_done: addr 0x3bef1ba0 not found This is a AMD Athlon 64 x2, 3800, 1 gig, 160gb, no PS/2 keyboard only USB. 6 usb ports. The screen blanks before I can write down everything. Since I can't stop it by hitting the keyboard. The keyboard has the following as part of it's dag: atkbdc0: (keyboard controller i8042) on port 0x60 0x64 Something like that. Any words of wisdom? Tried booting in safe mode? Paul Root [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CD install on new Dell Dimension E521
I just got a Dimension e521 that I'm going to install FreeBSD on. I'm having some trouble. I've tried the 6.1-RELEASE i386 DVD, I've downloaded the 6.1-Release CD iso for AMD64 I've downloaded the 6.2-Beta2 CD (today 10/20) for AMD64. All give the same error: panic: ohci_add_done: addr 0x3bef1ba0 not found This is a AMD Athlon 64 x2, 3800, 1 gig, 160gb, no PS/2 keyboard only USB. 6 usb ports. The screen blanks before I can write down everything. Since I can't stop it by hitting the keyboard. The keyboard has the following as part of it's dag: atkbdc0: (keyboard controller i8042) on port 0x60 0x64 Something like that. Any words of wisdom? Thanks, Paul. Paul Root [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to mount secondary hard disks now
I just noticed, this isn't going to the group. Always, keep the thread with the group. I don't know everything. In fact, I haven't done usb disks on FreeBSD. Anyway, there's a couple of disturbing things here. 1. You need to find out which drive is which. Because, what we do could be distructive to the disk. Especially if it's not the disk you think it is. Run dmesg and look for the da device references, maybe that will give you an idea as to which disk is which. Ok, let's assume for a minute that da2 became da1. That would explain why the disklabel is wrong. Since it was configured as da2c not da2s1c. try disklabel da1 disklabel da2 disklabel da1s1 disklabel da2s1 mount let's see what's what. 2. That disklabel is wrong. That's why you can't access the partition. Back in the old days, it was frowned upon to use 'C' as a live filesystem. It was always the whole disk. I generally will make an 'a' or 'e' or something that is also the whole disk There are 2 problems with this disklabel, if it is the right disk. 1. The file type is unused. It should be 4.2BSD 2. The C partition extends past the end of the unit. That's probably because it starts at 63 instead of 0. Which actually leads me to believe that this is the old da2. Run the dmesg, disklabels and mount for us (the whole list, I can easily miss things). And see if we can't figure out what drive is what. Paul. Shea Frederick wrote: FileServer# disklabel /dev/da1s1c # /dev/da1s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 156296322 63unused0 0 # raw part, don't edit partition c: partition extends past end of unit disklabel: partition c doesn't start at 0! disklabel: An incorrect partition c may cause problems for standard system utilities but something else interesting came up while i was poking around.I went to write some files to my da2 drive, and noticed that the access light on drive da1 was blinking. So somehow after re-booting, my da1 and da2 drives switched places (i sware i didnt switch the cables) -Shea On Apr 6, 2005 2:28 PM, Paul T. Root [EMAIL PROTECTED] wrote: Ok, so that was a bad guess. The disk may have gotten wiped. You can try running fsck with the next superblock. fsck -b 32 /dev/da1s1c What does disklabel give you? disklabel da1s1 Shea Frederick wrote: The first drive (da0) was setup using the instructions here... http://www.freebsd.org/doc/en_US.ISO8859-1/articles/formatting-media/article.html The 2nd drive (da1) was setup using sysinstall come to think of it, thats the only difference, so maybee thats part of the problem. I have no da1s4c FileServer# ll /dev/da* crw-r- 1 root operator4, 19 Apr 6 22:59 /dev/da0 crw-r- 1 root operator4, 23 Apr 6 17:01 /dev/da0c crw-r- 1 root operator4, 20 Apr 6 22:59 /dev/da1 crw-r- 1 root operator4, 65 Apr 6 22:59 /dev/da1a crw-r- 1 root operator4, 66 Apr 6 22:59 /dev/da1c crw-r- 1 root operator4, 34 Apr 6 22:59 /dev/da1s1 crw-r- 1 root operator4, 55 Apr 6 22:59 /dev/da1s1c crw-r- 1 root operator4, 21 Apr 7 04:38 /dev/da2 crw-r- 1 root operator4, 69 Apr 7 04:39 /dev/da2c I forgot to mention that drive 3 (setup just like da0) also works fine -Shea On Apr 6, 2005 1:42 PM, Paul T. Root [EMAIL PROTECTED] wrote: I'm not entirely sure, but it sure looks like da1s4c to me. Why is one drive da0c and the other da1s1c? How did you set them up? Shea Frederick wrote: Im running FreeBSD 5.3, its an almost fresh install. Its been running for about 7 days now. I have an internal IDE drive that the OS runs from, then I have two external firewire drives (da0, da1) that are only used as Samba shares. This morning i found that one of the firewire drives are no longer mounted (da1), this might have happened when I uninstalled Samba 2.x and installed 3.x yesterday, then rebooted. but im not sure, because i didnt check to see if the drive was still mounted after the reboot. So i figured i would just mount it again (even though da1 in the fstab) FileServer# mount /dev/da1s1c /mnt/jabba mount: /dev/da1s1c on /mnt/jabba: incorrect super block So now im not realy sure what to do, this drive was working perfectly before the reboot. someone told me to run fsck on the drive, but that gives me the following error. FileServer# fsck /dev/da1s1c ** /dev/da1s1c Cannot find file system superblock /dev/da1s1c: NOT LABELED AS A BSD FILE SYSTEM (unused) here is what fdisk returns... FileServer# fdisk /dev/da1s1c *** Working on device /dev/da1s1c *** parameters extracted from in-core disklabel are: cylinders=9728 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=9728 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information
Re: booting using NT boot loader
bootpart worked. Thanks! Paul. Marco Radzinschi wrote: On Thu, 5 Dec 2002, Paul Root wrote: Hi, I used to have this working then I reimaged my Windows 2000. Anyway, I have Windows 2000 on the C: (first partition) and FreeBSD on the second. VMWare is installed on Win2000. FreeBSD is 4.7-Stable of not that long ago. If switch the active partion to be the FreeBSD partition it boots fine. However, I get a failure if I go thru the NT boot loader. I copied boot1 from /boot to C:\ and called it bootsect.bsd I do a sum on FreeBSD and on Win 2000 (cygwin what a lifesaver) and They come up the same: proot@PTROOT /cygdrive/c $ sum bootsect.bsd 30147 1 proot@PTROOT /cygdrive/c $ cat boot.ini [boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT=Microsoft Windows 2000 Professional /fastdetect C:\bootsect.bsd=FreeBSD C:\=Microsoft Windows What am I doing wrong here? I tried copying the file to a peerless drive when just booted in FreeBSD and then moving it over with Explorer, then I copied it in FreeBSD, gzipped it, copied it over, gunziped it in cygwin and used mv in cygwin to rename. Sorry, I'm not currently on the list, don't have time to read. Any help would be appreciated. Thanks, Paul. -- Paul T. RootE/Mail: [EMAIL PROTECTED] 600 Stinson Blvd, Fl 1S PAG: +1 (877) 693-7155 Minneapolis, MN 55413 WRK: +1 (612) 664-3385 NIC:PTR FAX: +1 (612) 664-4779 Just use bootpart, and run it under windows. Tell it which partition is your FreeBSD one, and it will create the appropriate bootsector file (and entry). http://www.winimage.com/bootpart.htm Marco Radzinschi E-Mail: [EMAIL PROTECTED] Thu Dec 5 20:17:38 EST 2002 -- Paul T. RootE/Mail: [EMAIL PROTECTED] 600 Stinson Blvd, Fl 1S PAG: +1 (877) 693-7155 Minneapolis, MN 55413 WRK: +1 (612) 664-3385 NIC:PTR FAX: +1 (612) 664-4779 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
booting using NT boot loader
Hi, I used to have this working then I reimaged my Windows 2000. Anyway, I have Windows 2000 on the C: (first partition) and FreeBSD on the second. VMWare is installed on Win2000. FreeBSD is 4.7-Stable of not that long ago. If switch the active partion to be the FreeBSD partition it boots fine. However, I get a failure if I go thru the NT boot loader. I copied boot1 from /boot to C:\ and called it bootsect.bsd I do a sum on FreeBSD and on Win 2000 (cygwin what a lifesaver) and They come up the same: proot@PTROOT /cygdrive/c $ sum bootsect.bsd 30147 1 proot@PTROOT /cygdrive/c $ cat boot.ini [boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT=Microsoft Windows 2000 Professional /fastdetect C:\bootsect.bsd=FreeBSD C:\=Microsoft Windows What am I doing wrong here? I tried copying the file to a peerless drive when just booted in FreeBSD and then moving it over with Explorer, then I copied it in FreeBSD, gzipped it, copied it over, gunziped it in cygwin and used mv in cygwin to rename. Sorry, I'm not currently on the list, don't have time to read. Any help would be appreciated. Thanks, Paul. -- Paul T. RootE/Mail: [EMAIL PROTECTED] 600 Stinson Blvd, Fl 1S PAG: +1 (877) 693-7155 Minneapolis, MN 55413 WRK: +1 (612) 664-3385 NIC:PTR FAX: +1 (612) 664-4779 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
