Re: ldd failing on fglrx-installer

[Goswin von Brederlow]

Mark Kennedy <[EMAIL PROTECTED]> writes:

> Hi there,
>
> I just started installing the debian-pure64-3.4 port
> on my machine, and ran into a couple of problems
> building & installing an ATI driver according to
> .

Try just gcc-3.4 but it is experimental.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

aMule 2.0.0RC7 Font Size

[thierry]

Font size is really small, something like size 6, or even less, for the 
all amule window, except the title bar, where it's ok. I am runnign 
amule on a amd64 machine, with gnome. Is any one having this problem, or 
any one to help me out with that matter?
Thank you
Thierry

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: Kernel panic with latest iso's

[SpikeyGG]

Yeah, I installed my system about a week ago using 
the mini.iso off the netinst directory and it worked like a charm.  MSI K8N 
Neo2 Platinum installing on 2 SATA drives in a mirrored array.  I just 
wanted to set it up and decide if the AMD64 port works well enough to 
use as a HTPC.  I've decided that it's more stable that I expected and that 
there are more 64bit packages than I know what to do with.  
 
  So I wanted to wipe it clean and 
redistribute my array to account for some swap space and make it more 
redundant.  I tried to use the CD that I used before and when it 
got to the "downloading stuff" portion of the install it complained that 
there weren't and kernel images matching the one I was using.  
Something about "it probably won't work if you continue without kernel 
sources".  Since I didn't want it not to work, I figured better get 
the latest image.
 
  I went and downloaded mini.iso dated from 
TODAY, Feb-6th and burned it to a CD (I've learned to start using RW discs 
instead of coastering a 4.4MB CDR, only did it once - thank you) and tried 
to boot off of it.  Same thing as you, I get the kernel panic: can't mount 
root fs.  I was worried that the installer didn't know what to do 
with my raid array so I tried unplugging the drives so that they aren't even 
there to see and it still panic-ed.  Must be an issue with the 
installer.
 
We'll just have to wait to install it till they fix 
the panic, it's worth the wait.  I just wish I knew who needs to know so I 
could tell them!
 
-Greg

Re: Re: Framebuffer and Kernel issues

[SpikeyGG]

Sven,
 
Thanks for the response... I did exactly the same 
thing just now with another "test" kernel and it still gives me a blank 
screen.  I did a similar command "grep FB .config" in my linux 
directory and it responded with exactly the results that you have.  I set 
up my kernel line with a vga=ask so that it'll ask me on boot (and I have tried 
hardcoding it too).  I've tried all sorts of combonations.  0x301, 
0x312, 0x318, 0x305... none of them work.  What's really weird is that the 
stock kernel with frame buffers works, I just can't compile one to work! 
:(  Any other ideas?
 
Thanks,
 
-Greg

Re: Re: Framebuffer and Kernel issues

[SpikeyGG]

Sven,
 
Thanks for the response... I did exactly the same 
thing just now with another "test" kernel and it still gives me a blank 
screen.  I did a similar command "grep FB .config" in my linux 
directory and it responded with exactly the results that you have.  I set 
up my kernel line with a vga=ask so that it'll ask me on boot (and I have tried 
hardcoding it too).  I've tried all sorts of combonations.  0x301, 
0x312, 0x318, 0x305... none of them work.  What's really weird is that the 
stock kernel with frame buffers works, I just can't compile one to work! 
:(  Any other ideas?
 
Thanks,
 
-Greg

ldd failing on fglrx-installer

[Mark Kennedy]

Hi there,

I just started installing the debian-pure64-3.4 port
on my machine, and ran into a couple of problems
building & installing an ATI driver according to
.

The first problem that I ran into was a package
(libqt3-mt-dev) not installing because of a package
conflict
(libc6-dev_2.3.2.ds1-20.0.0.1.gcc4_amd64.deb).  I
found an email saying that the problem could be fixed
using dpkg --force-overwrite on the package, which
seemed to work.

When building the ATI driver, however, I got this
error:

dh_shlibdeps
/usr/bin/ldd: line 145: /lib/ld-linux.so.2: No such
file or directory
ldd: /lib/ld-linux.so.2 exited with unknown exit code
(127)
dpkg-shlibdeps: failure: ldd on
`debian/fglrx-drivers/usr/X11R6/bin/fgl_glxgears' gave
error exit status 1
dh_shlibdeps: command returned error code 256
make: *** [binary] Error 1

If I type in 'ldd /bin/ls', it works.  If I try 'ldd
/usr/bin/ldd', I get the same ld-linux.so.2 error as
above.

ldd is part of the libc6 package, which should be
fully 64 bit.  If so, why is it looking for
ld-linux.so.2, a 32 bit library?  And why would the
command work if it needed this library?

If this is a bug, I'll enter it in the appropriate
place.

Thanks,

Mark K.

=
Mark Kennedy
[EMAIL PROTECTED]


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Help with initial setup

[Sebastian Kügler]

On Sunday 06 February 2005 19:07, Dustin N.Jenkins wrote:
>  I've just put together my Gigabyte K8NS Ultra-939 board with AMD64
> 3000+ CPU.  I've used Debian for years and really, really like it.  I
> MUCH prefer doing a clean install rather than installing from, say,
> Knoppix so as to keep it as clean as possible.  Having said that, this
> is my first 64-bit machine, and it's currently running the latest
> Debian 3.1 (Unstable) and seems fine.  I've gone through the pure64
> documentation, but I can't really piece together whether I need to
> reinstall using the pure64 distro, or if I can just add the suggested
> entries into my sources.list and be done with it.  Can anyone advise
> me?

AFAIK, if you're switching arch's, you have to do a clean install. (I read it 
somewhere some time ago, could probably dig it up from the archives, but 
maybe it's enough for you to just trust me saving me or someone else some 
work ;-)

> Dustin

Cheers!

sebas
-- 
http://vizZzion.org
==
To know that one knows what one knows, and to know that one doesn't know what 
one doesn't know, there lies true wisdom. - Confucius


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Sata and Ati Xpress 200

[Karel Schneider]

Dear debian users,

I am having some trouble to install debian on a system with an athlon
64 on a msi board with the relatively new ati xpress 200 chipset.  The
cdrom on the ide channel works, but my harddisk connected to the
on-board sata thing is not.  RAID is not used.

I have tried both sarge and sid from alioth, as well as some other
distributions (but I have only little experience in actually
installing linux) without success. I tried to read all the relevant
messages on the list, but sometimes I was not sure, how to do the
things suggested.

I loaded "debian from scratch" and tried lspci.  It seems that debian
identifies the sata controller but does not know what to do with it. 
Any ideas how I can get it working easily?

I tried to connect the harddisk to different connectors on the
mainboard as has been suggested in some other post. To disable the
IDE-Bus does not seem to be a useful aproach.  Btw. I did a quick
install of Windows XP, everything seems to work, but I need a unix
system for my application :(

Thanks for any help or suggestions...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Help with initial setup

[Dustin N . Jenkins]

Hello all,
	I've just put together my Gigabyte K8NS Ultra-939 board with AMD64 
3000+ CPU.  I've used Debian for years and really, really like it.  I 
MUCH prefer doing a clean install rather than installing from, say, 
Knoppix so as to keep it as clean as possible.  Having said that, this 
is my first 64-bit machine, and it's currently running the latest 
Debian 3.1 (Unstable) and seems fine.  I've gone through the pure64 
documentation, but I can't really piece together whether I need to 
reinstall using the pure64 distro, or if I can just add the suggested 
entries into my sources.list and be done with it.  Can anyone advise 
me?

Many thanks,
Dustin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Supported Mainboards List Addition

[Johannes Klug]

Hello,
is this [1] list still the most recent list?
If so, could the one in charge add a new column, which contains the 
modules needed for "sensors" to work?

Thanks,
Johannes
[1] http://alioth.debian.org/docman/?group_id=30192
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Discover doesn't discover anything

[Adam Skutt]

Nicolas Fournier wrote:
Does anyone has any idea ? (except loading modules manually ;-) )
Remove discover completly and just use hotplug?
Sorry, I'm not a discover fan and I don't see it's puprose at all 
especially when it seems hotplug works better for me and is the apparent 
way of the future.  discover just complicates things generally (e.g., 
who loaded OSS sound modules this time)  and IMO, isn't worth it.

Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Realtime kernel patch for pure64 audio users

[Daniel James]

Hello all,

Looks like the 2.6.x preemption patch bug which caused kernel builds 
to fail on pure64 may have been fixed now:

http://lwn.net/Articles/121630/

Latest patch against 2.6.11-rc3 is at:

http://people.redhat.com/mingo/realtime-preempt/

Cheers

Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: libxf86config.a can't be used by shared libraries

[Sebastian Kügler]

On Sunday 06 February 2005 04:40, Goswin von Brederlow wrote:
> Sebastian Kügler <[EMAIL PROTECTED]> writes:
> > ... also identical. How do I proceed? I'm not quite experienced with
> > that, so ... I.e. is there a bugzilla for the - I think still unofficial
> > - pure64? Since I'm not encountering said problems on i386, I'm not sure
> > it's a valid bug for bugs.debian.org.

> Amd64 bugs (and this isn't even one since i386 has it too) are in the
> normal BTS too. Just for amd64 specific things the severity should be
> more moderate. Amd64 won't be in sarge so its bugs can't be RC.
>
> So just run "reportbug -f /usr/X11R6/lib/libxf86config.a".

I've just filed bug #293881 about that.

Thanks for your assistance!

Cheers,

sebas
-- 
http://vizZzion.org
==
God may be subtle, but he isn't plain mean. - Albert Einstein

kernel 2.6.10-9-amd64-k8

[Andree Zeulner]

Hi,

since kernel 2.6.10-9 I get an error while booting:

pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Evaluate _OSC Set fails. Status = 0x0005
pciehp: add_host_bridge: status 5
pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5
pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
pciehp: acpi_pciehprm:   Slot sun(1) at s:b:d:f=0x00:00:08:
pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5
pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
pciehp: acpi_pciehprm:   Slot sun(2) at s:b:d:f=0x00:00:09:
pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5
pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
pciehp: acpi_pciehprm:   Slot sun(3) at s:b:d:f=0x00:00:0a:
pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5
pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
pciehp: acpi_pciehprm:   Slot sun(4) at s:b:d:f=0x00:00:0c:
pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5
pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
pciehp: acpi_pciehprm:   Slot sun(5) at s:b:d:f=0x00:00:12:
pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5
pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
pciehp: acpi_pciehprm:   Slot sun(6) at s:b:d:f=0x00:00:13:
pciehp: Fails to gain control of native hot-plug
shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
shpchp: acpi_shpchprm:   Slot sun(1) at s:b:d:f=0x00:00:08:
shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
shpchp: acpi_shpchprm:   Slot sun(2) at s:b:d:f=0x00:00:09:
shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
shpchp: acpi_shpchprm:   Slot sun(3) at s:b:d:f=0x00:00:0a:
shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
shpchp: acpi_shpchprm:   Slot sun(4) at s:b:d:f=0x00:00:0c:
shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
shpchp: acpi_shpchprm:   Slot sun(5) at s:b:d:f=0x00:00:12:
shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5
shpchp: acpi_shpchprm:   Slot sun(6) at s:b:d:f=0x00:00:13:
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4

FATAL: Error inserting pciehp 
(/lib/modules/2.6.10-9-amd64-k8/kernel/drivers/pci/hotplug/pciehp.ko): No 
such device

modinfo pciehp
filename:   
/lib/modules/2.6.10-9-amd64-k8/kernel/drivers/pci/hotplug/pciehp.ko
license:GPL
description:PCI Express Hot Plug Controller Driver
author: Dan Zink <[EMAIL PROTECTED]>, Greg Kroah-Hartman 
<[EMAIL PROTECTED]>, Dely Sy <[EMAIL PROTECTED]>
srcversion: 5EC532C0153B2015B7CB083
alias:  pci:v*d*sv*sd*bc06sc04i00*
depends:pci_hotplug
vermagic:   2.6.10-9-amd64-k8 gcc-3.4
parm:   pciehp_debug:Debugging mode enabled or not
parm:   pciehp_poll_mode:Using polling mechanism for hot-plug events 
or not
parm:   pciehp_poll_time:Polling mechanism frequency, in seconds

what further info is needed to solve this problem?

regards

Andree


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Install report

[v0n0]

I have managed to install pure64 on my Asus L5846DFUH, and it was very 
easy (no problem during installation)!!! :-)  Thanks to the 'port' 
team!!! I only have to fix some things.
Output of my lspci:
:00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4)
   Subsystem: Asustek Computer, Inc.: Unknown device 80c5
   Flags: bus master, 66MHz, fast devsel, latency 0
   Memory at e800 (32-bit, prefetchable) [size=128M]
   Capabilities: [44] #08 [0180]
   Capabilities: [c0] AGP version 3.0

:00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev f6)
   Subsystem: Asustek Computer, Inc.: Unknown device 80c5
   Flags: bus master, 66MHz, fast devsel, latency 0
:00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4)
   Subsystem: Asustek Computer, Inc.: Unknown device 80c5
   Flags: 66MHz, fast devsel, IRQ 11
   I/O ports at 5000 [size=64]
   I/O ports at 5040 [size=64]
   Capabilities: [44] Power Management version 2
:00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5) 
(prog-if 10 [OHCI])
   Subsystem: Asustek Computer, Inc.: Unknown device 1858
   Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 11
   Memory at febfb000 (32-bit, non-prefetchable) [size=4K]
   Capabilities: [44] Power Management version 2

:00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5) 
(prog-if 10 [OHCI])
   Subsystem: Asustek Computer, Inc.: Unknown device 1858
   Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 5
   Memory at febfc000 (32-bit, non-prefetchable) [size=4K]
   Capabilities: [44] Power Management version 2

:00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2) 
(prog-if 20 [EHCI])
   Subsystem: Asustek Computer, Inc.: Unknown device 1859
   Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
   Memory at febfdc00 (32-bit, non-prefetchable) [size=256]
   Capabilities: [44] #0a [2080]
   Capabilities: [80] Power Management version 2

:00:06.0 Multimedia audio controller: nVidia Corporation nForce3 
Audio (rev a2)
   Subsystem: Asustek Computer, Inc.: Unknown device 1853
   Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 5
   I/O ports at e400 [size=256]
   I/O ports at e080 [size=128]
   Memory at febfe000 (32-bit, non-prefetchable) [size=4K]
   Capabilities: [44] Power Management version 2

:00:06.1 Modem: nVidia Corporation: Unknown device 00d9 (rev a2) 
(prog-if 00 [Generic])
   Subsystem: Asustek Computer, Inc.: Unknown device 1856
   Flags: 66MHz, fast devsel, IRQ 10
   I/O ports at e800 [size=256]
   I/O ports at ec00 [size=128]
   Memory at febff000 (32-bit, non-prefetchable) [size=4K]
   Capabilities: [44] Power Management version 2

:00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5) 
(prog-if 8a [MasterSecP PriP])
   Subsystem: Asustek Computer, Inc.: Unknown device 185a
   Flags: bus master, 66MHz, fast devsel, latency 0
   I/O ports at ffa0 [size=16]
   Capabilities: [44] Power Management version 2

:00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2) 
(prog-if 00 [Normal decode])
   Flags: bus master, 66MHz, fast devsel, latency 0
   Bus: primary=00, secondary=02, subordinate=04, sec-latency=128
   I/O behind bridge: b000-dfff
   Memory behind bridge: f8a0-feaf

:00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4) 
(prog-if 00 [Normal decode])
   Flags: bus master, 66MHz, medium devsel, latency 64
   Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
   Memory behind bridge: f690-f89f
   Prefetchable memory behind bridge: c680-e67f

:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
   Flags: fast devsel
   Capabilities: [80] #08 [2101]
:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
   Flags: fast devsel
:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
   Flags: fast devsel
:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
   Flags: fast devsel
:01:00.0 VGA compatible controller: nVidia Corporation: Unknown 
device 031b (rev a1) (prog-if 00 [VGA])
   Subsystem: Asustek Computer, Inc.: Unknown device 1852
   Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
   Memory at f700 (32-bit, non-prefetchable) [size=16M]
   Memory at d000 (32-bit, prefetchable) [size=256M]
   Expansion ROM at f89e [disabled] [size=128K]
   Capabilities: [60] Power Management version 2
   Capabilities: [44] AGP version 3.0

:02:00.0 Ethernet controller: Marvell Technology Group Ltd. Yukon 
Gigabit Ethernet 10/100/1000Base-T Adapter (rev 13)
   Subsystem: Asustek Computer, Inc.: Unknown device 173c
   Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
   

Discover doesn't discover anything

[Nicolas Fournier]

Hi,

I've updated discover this morning (from discover1 to discover package) but 
unfortunatly it doesn't find any of my hardware anymore. I tried to run the 
"discover" command and it seems to work but the init script doesn't load the 
corresponding modules :

# discover
unknown unknown 
unknown unknown 
ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) 
ATI Technologies Inc RV350 AP [Radeon 9600] 
Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 
Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 
Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 
Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology 
Configuration 
VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller 
VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800 South] 
VIA Technologies, Inc. USB 2.0 
VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller 
VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller 
VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller 
VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller 
VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE 
VIA Technologies, Inc. VIA VT6420 SATA RAID Controller 
Marvell Technology Group Ltd. Gigabit Ethernet Controller 
Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) 
VIA Technologies, Inc. IEEE 1394 Host Controller 
VIA Technologies, Inc. VT8237 PCI bridge [K8T800 South] 
VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge 
unknown unknown 
unknown unknown 
unknown unknown 
unknown unknown 
unknown unknown 

and

# /etc/init.d/discover start
Discovering hardware: 


Does anyone has any idea ? (except loading modules manually ;-) )

Thanks,
Nicolas Fournier


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Framebuffer and Kernel issues

[Sven Krahn]

On Fri, 4 Feb 2005 22:26:40 -0700, SpikeyGG <[EMAIL PROTECTED]> wrote:

(...) 

> One of my problems is that I can't recompile a kernel and get the frame
> buffer working (using vga=0x318 with the boot options).  I find that using
> linux in a 1024x768 frame buffer is much more efficient than the 80x25
> default.  I've learned how to use grub (it's nice) and I learned how to use
> mkinitrd so that my system will load required modules before the kernel gets
> loaded to avoid panics; but I cannot seem to get the frame buffer to work. 
> When I set vga=ask in the grub option and reboot to that entry, It asks like
> it should.  When I try 318 and the screen just goes black (system still
> boots, can hear disk access, and log in then reboot blindly).  I can choose
> 0 (80x25) and it'll work fine.  I tried compiling the VESA FB into the
> kernel (Y instead of M) and also with Console FB support and it still didn't
> work.  Now here's the kicker: when I use the precompiled kernel that came
> with the pure64 release and add vga=0x318 it works like a charm.  What's up
> with that? 

I had this issue recently as well and could resolve it using these FB
options in the kernel config:

sk:~# grep FB /boot/config-2.6.10-050131-1
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
CONFIG_FB_VIRTUAL=m

My corresponding GRUBentry is as follows:

title Debian Linux AMD64 - 2.6.10-050131-1
root (hd0,8)
kernel (hd0,9)/vmlinuz-2.6.10-050131-1 ro root=/dev/hda9 vga=0x318

-- 
Best regards / Mit den besten Grüssen
Sven Krahn

Re: compiling custom kernel with gcc-3.4

[Jean-Luc Coulon (f5ibh)]

Le 06.02.2005 02:49:38, David Liontooth a écrit :
On Sat, 5 Feb 2005, Jonathan Marchand wrote:
Hi,
I'am running an amd64 laptop and I would like to build a kernel with
gcc-.34 like the kernel images avaible on the internet. Therefore, it
seems I can only build kernel with gcc-3.3. I did change some
variables in the kernel-source's Makefile and the environment
variables, but the resulting kernel is always compiled with gcc-3.3.
I
compile the kernel the Debian way with make-kpkg. Is there any
options
to add with make-kpkg to use gcc-3.4? Why the kernel-source package
isn't configured to be build by defauly with gcc-3.4, it seems the
more natural, or it is on purpose?
I'm sorry I'm pretty unknowledgeable with compiling kernels and the
different versions of gcc but any informations will be greatly
appreciated.
Thanks
Jonathan
Hi Jonathan,
Here's what I do: before compiling, change the /usr/bin/gcc symlink
from
/usr/bin/gcc-3.3 to /usr/bin/gcc-3.4. Afterwards, change it back.
Goswin's solution is more worthy of a true geek of course ;-)
I use the following:
MAKEFLAGS="CC=gcc-3.4" \
make-kpkg --revision  \
--append-to-version - \
--initrd \
--rootcmd fakeroot kernel_image
I use something like 20050205 (the date) for 
And -k8-1  for my version, you can increase the number as you create  
more versions  ;-)

Dave
Jean-Luc


pgpzKipX3ZHbD.pgp
Description: PGP signature