[nycbug-talk] Help getting FreeBSD current to boot (5.2.1 releasedoes work)
G. Rosamond
george
Sun Jun 13 14:24:30 EDT 2004
>-----Original Message-----
>From: talk-bounces at lists.nycbug.org
>[mailto:talk-bounces at lists.nycbug.org] On Behalf Of Jonathan
>Sent: Sunday, June 13, 2004 2:21 PM
>To: pete wright
>Cc: talk at lists.nycbug.org
>Subject: Re: [nycbug-talk] Help getting FreeBSD current to
>boot (5.2.1 releasedoes work)
>
>pete wright wrote:
>
>>
>> On Jun 13, 2004, at 11:44 AM, Jonathan wrote:
>>
>>> Dan Langille wrote:
>>>
>>>> On 13 Jun 2004 at 11:08, Jonathan wrote:
>>>>
>>>>> Wold anyone be willing to help me get a -current kernel
>to boot on
>>>>> my computer? As the subject says 5.2.1-release boots
>fine but any
>>>>> recent (within a month +) -current fails to boot successfully. I
>>>>> can test any patches etc. the machine is just sitting right now
>>>>> while I try to get it to work. I don't have a null modem
>cable and
>>>>> really don't want to pay Radioshack prices for one but I
>will if I
>>>>> need to. I'm located on FT Drum if anyone is willing to help in
>>>>> person and lives nearby or knows someone nearby who may
>help. I'd
>>>>> really like to get FreeBSD -current running because I
>want to stick
>>>>> with 5.x and 5.2.1 release has several known security issues. I
>>>>> will probably switch to -stable when it becomes 5-stable.
>>
>>
>> i'm game to help you out but i think the folks on the list
>would need a
>> bit more info your setup, like hardware specs etc. also if
>you could
>> post the output of a "dmesg." also, are you trying to boot
>off GENERIC
>> or is this a custom kernel? If custom, try booting off GENERIC.
>> finally, i would post the "uname" of the release that boots fine.
>>
>> -p
>>
>
>Booting GENERIC 5.2.1 and trying GENERIC -current
>
>The computer is a Pentium I 233MHz with 128MB RAM (My desktop has
>problems too but the 233 computer will be dedicated to FreeBSD
>so I want
>to get it working first). I have a site I can post anything
>on to avoid
>large on-list messages as well if that would be better for
>this list. I
>will post a transcription of the error messages and a boot -v
>later but
>I'm in the middle of a 12 hour buildworld/buildkernel (trying -current
>dated 5 May 2004 to see if that works).
<snip>
I actually think this list doesn't get *enough* long dmesgs.
g
More information about the talk
mailing list