Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: amd64 -current has been borked on my ASUS laptop for at least a few weeks. Suggestions wanted.



On 01.12.2010 00:18, Michael Litchard wrote:
> Hi. I installed 5.1 just to find that their was no driver for my
> Atheros 9285 network device. After a little digging I found some work
> being done in -current for this. However, I haven't been able to get
> past the first line one sees upon booting the iso for the amd64
> -current build (trying several from the last few weeks) This is what I
> see
>
> integer+integer+integer ....
> spinning cursor.
>
> Eventually the cursor stops spinning, and locks. What I would like to
> know is what would I need to do in order to get useful information to
> submit? Or is this being worked on, and all I have to do is wait?
>
> My Asus is a K72D. If I need to provide more detailed information
> please let me know.

I encountered a similar "freeze" during twiddle step, early on boot, for
amd64, on a recentish amd64 machine.

Suggestion: try booting the ISO by passing "modules off" to the
bootloader command line, and see if it goes further. Another test is to
rebuild an ISO (release + iso-image) with this patch:


Index: sys/arch/i386/stand/lib/exec.c
===================================================================
RCS file: /cvsroot/src/sys/arch/i386/stand/lib/exec.c,v
retrieving revision 1.45
diff -u -p -u -p -r1.45 exec.c
--- sys/arch/i386/stand/lib/exec.c      30 Oct 2010 08:12:43 -0000      1.45
+++ sys/arch/i386/stand/lib/exec.c      2 Dec 2010 01:03:14 -0000
@@ -297,6 +297,7 @@ exec_netbsd(const char *file, physaddr_t
        boot_argv[5] = basemem;

        /* pull in any modules if necessary */
+       boot_modules_enabled = false; /* XXX XXX XXX */
        if (boot_modules_enabled) {
                module_init(file);
                if (btinfo_modulelist) {


If it works, you are in the same situation as mine. The lock happens
before execution is passed to kernel. It is bootloader related, during
module load. I did not investigate why (lack of time).

In case it's not: bad luck :/

-- 
Jean-Yves Migeon
jeanyves.migeon%free.fr@localhost


Home | Main Index | Thread Index | Old Index