> The past few days I've been trying to install Debian (any release) on an IBM
> x3850 M2 server, and I encounter more or less the same issues you describe
> in bug #526525
> With amd64 releases kernels boot (various Debian flavors) but the onboard
> Broadcom Nic (BCM5709) is not detected at all an
>> Possibly fixed by a BIOS upgrade. See report on the PE mailing list at
>> http://lists.us.dell.com/pipermail/linux-poweredge/2009-May/039328.html
> Yup - works for me. New BIOS for all 11G Dell servers which closes this
> bug.
Yes, upgrade Dell PowerEdge T610 BIOS to 1.1.4 worked for me too.
[Andrew]
> This bug doesn't just affect disk and network and it doesn't just affect
> the T610.
>
> I'm seeing problems detecting the disk and network controllers and usb
> media (you also reported this earlier in the ticket) on a Dell R610. These
> also have the same components as the R710 and I s
retitle 526525 disk and network fail on Dell T610 under 64-bit kernel only
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
retitle 526525: disk and network fail on Dell T610 under 64-bit kernel only
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Fri, May 22, 2009 at 3:43 AM, Andrew Robert Nicols
wrote:
> On Wed, May 20, 2009 at 09:04:38AM -0700, Tony Godshall wrote:
>> Reboot with USB stick plugged in: now I get a long pause immediately
>> after "md: raid1 personality registered for level 1"
>>
>&
On Wed, May 20, 2009 at 8:48 AM, Tony Godshall wrote:
> [me]
> ...
>>> Perhaps if I could figure out how to grab the dmesg output from
>>> initramfs environment, I could then compare the amd64 kernel
>>> output to the 686-bigmem kernel output... :-/
>
> [m
[me]
...
>> Perhaps if I could figure out how to grab the dmesg output from
>> initramfs environment, I could then compare the amd64 kernel
>> output to the 686-bigmem kernel output... :-/
[martin f krafft]
> Append 'break=bottom debug' to the kernel line and at the shell do
> something like
>
>
On Tue, May 12, 2009 at 9:11 AM, martin f krafft wrote:
> also sprach Tony Godshall [2009.05.11.2058 +0200]:
>> They are *not*. That would seem to be the nub of the problem. No
>> base partitions, thus no RAID. Good, thanks, that's progress. Might
>> be good fo
...
> Sorry. We got off on a bad start. I'll review your stuff tomorrow
> and then let's start afresh.
OK
> By the time you get dumped into the busybox prompt during initramfs
> time, are /dev/sd[abcd] present?
They are *not*. That would seem to be the nub of the problem. No
base partitions, t
On Mon, May 11, 2009 at 9:55 AM, martin f krafft wrote:
> also sprach Tony Godshall [2009.05.11.1843 +0200]:
>> I filed the report because I want to see Debian work great on all
>> configurations, with all CPUs, with all RAID configurations, off the
>> bat, without tweakin
at de7fc000 (32-bit, non-prefetchable) [size=16K]
Memory at de80 (32-bit, non-prefetchable) [size=8M]
[virtual] Expansion ROM at de00 [disabled] [size=64K]
Capabilities: [dc] Power Management version 1
On Mon, May 11, 2009 at 9:25 AM, martin f krafft wrote:
&g
On Sat, May 9, 2009 at 12:35 AM, martin f krafft wrote:
> retitle 526525 amd64 kernel cannot find bnx2 PCI device base address
Um. BNX2 is the network card? WTF does it have to do with being able
to mount and boot off RAID in 64-bit mode only?
> also sprach Tony Godshall [2009.05.0
On Fri, May 8, 2009 at 12:45 AM, martin f krafft wrote:
> also sprach Tony Godshall [2009.05.08.0055 +0200]:
>> bnx2 :01:00.1: Cannot find PCI device base address, aborting.
>> mptbase: ioc0: ERROR - : ERROR - Unable to map adapter memory!
>> mptbase: ioc1: ERROR - :
seem to be the issue here. But I did
determine that there's no /dev/md0. Oddly, there *is* a /dev/md/
directory. cat /proc/modules shows raid1 and md_mod loaded.
Best Regards.
Tony
On Sat, May 2, 2009 at 12:06 PM, maximilian attems wrote:
> On Fri, May 01, 2009 at 11:22:47AM -07
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-15
Severity: important
Kernel from linux-image-2.6.26-2-amd64 does not see
root RAID device /dev/md0 so boot sequence drops
busybox shell. 2.6.26-2-686-bigmem and 2.6.26-2-686
work properly.
This is after an install with no issues from the st
when a hard-drive-based debian was upgraded to kernel 2.6.16
Hang point is just past report of serial port detected.
Tony Godshall (g)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi.
Looks like building the initrd required an upgraded
Depends: directly or indirectly to e2fsprogs.
Not sure the minimum version required, but I had
1.35-6 when installing linux-image-2.6.12-1-686 failed
and 1.38-1.1 when installing linux-image-2.6.12-1-686
succeeded.
Best Regards,
Tony
Package: linux-image-2.6.12-1-686
Version: 2.6.12-5
Severity: important
sena:~# apt-get -V install linux-image-2.6.12-1-686
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
lilo (22.6.1-6.2)
The following NEW packages will be installed:
linux-image-2.6.12-1
19 matches
Mail list logo
