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

Bug#399120: marked as done (JMicron controller support)



Your message dated Sun, 26 Nov 2006 17:28:25 -0700
with message-id <[🔎] 20061127002825.GF24420@colo>
and subject line Bug#399120: RC1 bugreport
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

Boot method: <How did you boot the installer? CD? floppy? network?>
Image version: <Full URL to image you downloaded is best>
Date: <Date and time of the install>

Machine: <Description of machine (eg, IBM Thinkpad R32)>
Processor:
Memory:
Partitions: <df -Tl will do; the raw partition table is preferred>

Output of lspci -nn and lspci -vnn:

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [?]
Configure network:      [?]
Detect CD:              [E]
Load installer modules: [ ]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems:

RC1 and still no support for the Asus P5B (series) motherboard. Or any other mobo with a JMicron controller. This is no news to you, I'm sure, but I thought I'd report it anyway.

- and no hard feelings. Thanks for a wonderful free OS :)




--- End Message ---
--- Begin Message ---
Version: 2.6.18-1

On Sun, Nov 26, 2006 at 08:17:20PM +0100, Johan Spee wrote:
> My message from last week apparently never made it to this log, so here it is again:
> 
> > Are you telling it is fixed in the _Debian_ kernel, version 2.6.18?
> 
> Yes it is. And my initial bug report really is just a plea to make sure this kernel is used for the final release.
> From what I gather the module was already added to kernel 2.6.16, but did not work due to a bug. Unfortunately kernel 2.6.17 was identical in this 
> respect. Apparently the bug was fixed in versions 2.6.18 RC4 and above.
> 
> I currently use Debian kernel 2.6.18-3-686 on an ASUS P5B and everything works fine (including the onboard NIC, which isn't supported by the current 
> kernel 2.6.17 either).
> 
> As for the other questions: obviously there is no reason to dig up the details of this bug. That work has already been done some time ago.

Marking as closed in 2.6.18.
2.6.18 will be the kernel in etch. Thanks!

-- 
dann frazier


--- End Message ---

Reply to: