Re: 2.6.0-test8 PCI (?) troubles

2003-10-29 Thread Kjetil Kjernsmo
Hi!

Just a small follow-up... 

I'm now getting very close to achieving what I set out to do with a 2.4 
kernel with Backstreet Ruby patches (now, I only need to manage the X 
servers intelligently). So, I'm going to put my 2.6 project on ice for 
the time being... :-) However, I will return to 2.6 once I get more 
time, since it would be good to be able to use the framebuffers. So, 
I'll keep your advices with me when that happens. 

On Monday 27 October 2003 20:20, Andre Kalus wrote:
> If something went wrong with framebuffers: do not use it. In general
> if nobody has a better idea (see post of pigeon) I would suggest the
> following:
>
> Try to build a vanilla kernel with only those features you will
> need to boot:
> - Disable framebuffers (from kernel config, no vga parameter on boot
> prompt)
> - Disable ACPI, APM
> - Disable APIC
> - Disabe USB
> - Disable support for "special devices" like TV cards, ISDN cards
> etc. (searching for them might (?) confuse the PCI bus)

OK, obviously a good idea!

> Make sure you backup your old config so you know which options you
> wanted to set.

Yup, always do! 

> > However, I built these two kernels very differently. The test8-ruby
> > I've built with make-kpkg, and starting out with Andreas' config
> > for his kernel. With the test9, I've used make bzImage and friends,
> > and I started out with my own 2.4.22 kernel config.
>
> It should not make a difference but I always use the "make clean
> bzImage" for a new kernel. make-kpkg should not do anything but ...

Yup.


> >> Enabling fast FPU save and restore... done. Enabling unmasked SIMD
> >> FPU exception support... done. Checking 'hlt' instruction... OK.
> >> POSIX conformance testing by UNIFIX
> >> NET: Registered protocol family 16
> >> PCI: PCI BIOS revision 2.10 entry at 0xfdb51, last bus=1
> >
> > OK, so this is where it stops with ACPI and APIC enabled. But I
> > can't see anything suspecious...
>
> OK, might be what Pigeon wrote: your BIOS uses an invalid APIC ->
> disable it.

Yeah, but I couldn't find anything about APIC in my BIOS set-up... Any 
further pointers where I may find it...?

Best,

Kjetil
-- 
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
[EMAIL PROTECTED]  [EMAIL PROTECTED]  [EMAIL PROTECTED]
Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC


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



Re: 2.6.0-test8 PCI (?) troubles

2003-10-27 Thread Andre Kalus
On Sun, 26 Oct 2003 14:34:27 +0100, Kjetil Kjernsmo wrote:
> 
> 
> Yeah, I just tried test9 too. I downloaded a vanilla test8 yesterday,
> patched it with test9 today. That stopped even earlier... It seems
> something was wrong with the framebuffers. It goes down to where the
> Matrox fb stuff is loaded, then I get back the first few lines where the
> kernel is loaded, and then everything halts.

If something went wrong with framebuffers: do not use it. In general if
nobody has a better idea (see post of pigeon) I would suggest the
following:

Try to build a vanilla kernel with only those features you will
need to boot:
- Disable framebuffers (from kernel config, no vga parameter on boot
prompt)
- Disable ACPI, APM
- Disable APIC
- Disabe USB
- Disable support for "special devices" like TV cards, ISDN cards etc.
(searching for them might (?) confuse the PCI bus)

Make sure you backup your old config so you know which options you wanted
to set.

> 
> However, I built these two kernels very differently. The test8-ruby I've
> built with make-kpkg, and starting out with Andreas' config for his
> kernel. With the test9, I've used make bzImage and friends, and I started
> out with my own 2.4.22 kernel config.

It should not make a difference but I always use the "make clean bzImage"
for a new kernel. make-kpkg should not do anything but ...

> 
>> Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU
>> exception support... done. Checking 'hlt' instruction... OK.
>> POSIX conformance testing by UNIFIX
>> NET: Registered protocol family 16
>> PCI: PCI BIOS revision 2.10 entry at 0xfdb51, last bus=1
> 
> OK, so this is where it stops with ACPI and APIC enabled. But I can't see
> anything suspecious...

OK, might be what Pigeon wrote: your BIOS uses an invalid APIC -> disable
it.


>> PCI: Using IRQ router default [1106/3074] at :00:11.0
> 
> Is this an ISA bridge on your system...? 

It is.

> This resembles where I stop with
> ACPI and APIC disabled, but there is a lot less happening between the two
> in my case. I didn't write it down, but I would guess it looks more like
> 
> PCI: PCI BIOS revision 2.10 entry at 0xf0d40, last bus=1 PCI: Using
> configuration type 1
> mtrr: v2.0 (20020519)
> PCI: Probing PCI hardware
> PCI: Probing PCI hardware (bus 00)
> PCI: Using IRQ router VIA [1106/0686] at 00:04.0

This is caused by all those ACPI messages. Here is a boot log with acpi
disabled:

Linux version 2.6.0-test7 ([EMAIL PROTECTED]) (gcc version 3.3.2 20031005 (Debian 
prerelease)) #1 Thu Oct 9 14:17:31 CEST 2003
Video mode to be used for restore is 317
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009fc00 (usable)
 BIOS-e820: 0009fc00 - 000a (reserved)
 BIOS-e820: 000d - 000d4000 (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - 0fff (usable)
 BIOS-e820: 0fff - 0fff8000 (ACPI data)
 BIOS-e820: 0fff8000 - 1000 (ACPI NVS)
 BIOS-e820: fff8 - 0001 (reserved)
user-defined physical RAM map:
 user:  - 0009fc00 (usable)
 user: 0009fc00 - 000a (reserved)
 user: 000d - 000d4000 (reserved)
 user: 000f - 0010 (reserved)
 user: 0010 - 0fff (usable)
 user: 0fff - 0fff8000 (ACPI data)
 user: 0fff8000 - 1000 (ACPI NVS)
 user: fff8 - 0001 (reserved)
255MB LOWMEM available.
On node 0 totalpages: 65520
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 61424 pages, LIFO batch:14
  HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
Building zonelist for node : 0
Kernel command line: root=/dev/hda6 vga=791 acpi=off mem=262080K
No local APIC present or hardware disabled
Initializing CPU#0
PID hash table entries: 1024 (order 10: 8192 bytes)
Detected 1592.834 MHz processor.
Console: colour dummy device 80x25
Memory: 255488k/262080k available (2067k kernel code, 5872k reserved, 843k data, 152k 
init, 0k highmem)
Calibrating delay loop... 3129.34 BogoMIPS
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 3febf9ff   
CPU: After vendor identify, caps: 3febf9ff   
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: After all inits, caps: 3febf9ff   0080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU#0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU#0: Thermal monitoring enabled
CPU: Intel(R) Pentium(R) 4 CPU 1.60GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' inst

Re: 2.6.0-test8 PCI (?) troubles

2003-10-26 Thread Pigeon
On Fri, Oct 24, 2003 at 10:56:57PM +0200, Kjetil Kjernsmo wrote:
> Hi all!
> 
> Lately, I have been desparately trying to get a second head with a 
> separate login on my computer, something that has included quite a few 
> approaches. Finally, I've upgraded to sid, and now I'm onto 
> 2.6.0-test8, and not only that, it's patched with the ruby patches. I 
> got the whole thing from Andreas Schuldei, who has done some great work 
> on this. Presumably, what I'm now seeing are not specifically ruby 
> problems, so I try to avoid bothering him (unless he wants to chime 
> in).
> 
> I've googled through the archives, and done the things recommended 
> there, like enabling VT, creating /sys, etc. I'm not including all the 
> details, since I don't know where to start, I guess for the sake of 
> brevity it is no use posting a lot of possibly irrelevant info.
> 
> Compile (using make-kpkg) seems to go fine, so does install. Re-run of 
> lilo has a couple of warnings, but nothing that has ever meant anything 
> before... :-) 
> 
> When I boot up, I get kernel messages rolling along, but stops with the 
> following line:
> PCI: PCI BIOS revision 2.10 entry at 0xf0d40, last bus=1
> then, the LED on the floppy drive lights up and remain lit, and then it 
> just sits there. Nothing happens, I and have to push the reset button 
> to reboot. It doesn't tell me it's panicked either. 
> 
> I find the same line in my 2.4.22 dmesg. What follows after booting 
> 2.4.22 is this:
> PCI: PCI BIOS revision 2.10 entry at 0xf0d40, last bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Probing PCI hardware (bus 00)
> PCI: Using IRQ router VIA [1106/0686] at 00:04.0
> PCI: Disabling Via external APIC routing
> Linux NET4.0 for Linux 2.4
> 
> Now, it seems like 2.6 does things in a different order, for example, 
> the framebuffer stuff seems to be loaded before the halt happens. 
> OTOH, since it looks as if it is looking through the PCI hardware with 
> 2.4.22 after this message, I'm guessing something goes wrong with PCI 
> with 2.6.0-test8 too... I could be very wrong here, but it is the only 
> clue I have... 
> 
> Any better clues...?

I have the same chipset. With 2.4, I find I have to turn the APIC off
in BIOS Setup, otherwise the boot hangs when it gets to dealing with
the APIC. I don't know if this applies to 2.6 (haven't tried 2.6 yet
because the driver for my scsi card is broken) but it might be worth a
shot.

-- 
Pigeon

Be kind to pigeons
Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F


pgp0.pgp
Description: PGP signature


Re: 2.6.0-test8 PCI (?) troubles

2003-10-26 Thread Kjetil Kjernsmo
Hi and thanks for all the help!

On Sunday 26 October 2003 13:18, Andre Kalus wrote:
> ISA is sometimes needed for PCMCIA support but missing support should
> not stop boot process.

OK.

> > The next thing it says after this in my 2.4.22 dmesg is PCI:
> > Disabling Via external APIC routing I have disabled APIC too, some
> > time ago.
>
> Try to enable apic you can disable it by passing "noapic" on the boot
> line.

OK. Actually, reenabling APIC made it stop on the previous spot I had, 
(... BIOS Revision...)

> Did you try a kernel version different to test8? - sometimes a kernel
> version does not work with everybody's hardware - for me test5 did
> only work without ACPI.

Yeah, I just tried test9 too. I downloaded a vanilla test8 yesterday, 
patched it with test9 today. That stopped even earlier... It seems 
something was wrong with the framebuffers. It goes down to where the 
Matrox fb stuff is loaded, then I get back the first few lines where 
the kernel is loaded, and then everything halts. 

However, I built these two kernels very differently. The test8-ruby I've 
built with make-kpkg, and starting out with Andreas' config for his 
kernel. With the test9, I've used make bzImage and friends, and I 
started out with my own 2.4.22 kernel config. 



> I attached my dmesg output so you can have a look if you can find
> anything strange before your system hangs.

OK, thanks!

> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> NET: Registered protocol family 16
> PCI: PCI BIOS revision 2.10 entry at 0xfdb51, last bus=1

OK, so this is where it stops with ACPI and APIC enabled. But I can't 
see anything suspecious... 

> PCI: Using configuration type 1
> mtrr: v2.0 (20020519)
> ACPI: Subsystem revision 20030918
> ACPI: Interpreter enabled
> ACPI: Using PIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (00:00)
> PCI: Probing PCI hardware (bus 00)
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: Power Resource [URP1] (off)
> ACPI: Embedded Controller [EC0] (gpe 5)
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
> ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
> ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKC] (IRQs 3 10 11)
> ACPI: PCI Interrupt Link [LNKD] (IRQs 5 6 7)
> Linux Plug and Play Support v0.97 (c) Adam Belay
> PnPBIOS: Scanning system for PnP BIOS support...
> PnPBIOS: Found PnP BIOS installation structure at 0xc00f82c0
> PnPBIOS: PnP BIOS version 1.0, entry 0xf:0x729b, dseg 0xf
> PnPBIOS: Unknown tag '0x82', length '25'.
> PnPBIOS: 12 nodes reported by PnP BIOS; 12 recorded by driver
> SCSI subsystem initialized
> Linux Kernel Card Services
>   options:  [pci] [cardbus] [pm]
> PCI: Probing PCI hardware
> PCI: Using IRQ router default [1106/3074] at :00:11.0

Is this an ISA bridge on your system...? This resembles where I stop 
with ACPI and APIC disabled, but there is a lot less happening between 
the two in my case. I didn't write it down, but I would guess it looks 
more like

PCI: PCI BIOS revision 2.10 entry at 0xf0d40, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router VIA [1106/0686] at 00:04.0

I just discovered something interesting with the backstreet ruby 2.4 
kernel I've been struggling with too. I had a problem that e2fsck 
complained about a bad superblock, and now it turns out this was 
connected to that I booted the kernel with mount=devfs (or was it the 
other way around). 

I'm obviously getting real ruby on 2.6 up and running (since I have 
Matrox DH card), so I'm always happy for more help! Meanwhile, I'll 
explore the backstreet-ruby with 2.4 some more to see if I can get that 
running. If I get that running first, I think I'll stick with it. 

Best,

Kjetil
-- 
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
[EMAIL PROTECTED]  [EMAIL PROTECTED]  [EMAIL PROTECTED]
Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC


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



Re: 2.6.0-test8 PCI (?) troubles

2003-10-26 Thread Andre Kalus
On Sun, 26 Oct 2003 11:42:39 +0100, Kjetil Kjernsmo wrote:
> 
> Now, it stops with the message
> PCI: Using IRQ router VIA [1106/0686] at :00:04.0
> 
> I assume this is (from lspci -v on 2.4.22):
> 
> 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
> (rev 40)
> Subsystem: Asustek Computer, Inc. A7M266 Mainboard Flags: bus
> master, stepping, medium devsel, latency 0 Capabilities: [c0]
> Power Management version 2
> 
> I'm baffled, there are no ISA slots on my mobo... But ISA bridge means
> perhaps something entirely different?

That is OK, I have one in my laptop, too. AFAIK, the ISA bridge is
contained in the chipset that is able to support ISA slots. Mainboard
manufacturers normally do not put ISA slots on boards - except for
industry purposes where you still need them sometimes...


> I had disabled ISA completely, but I just enabled it again and compiled
> and booted a kernel, but it didn't make any difference.

ISA is sometimes needed for PCMCIA support but missing support should not
stop boot process.


> The next thing it says after this in my 2.4.22 dmesg is PCI: Disabling
> Via external APIC routing I have disabled APIC too, some time ago.
> 
> 
Try to enable apic you can disable it by passing "noapic" on the boot
line.

Did you try a kernel version different to test8? - sometimes a kernel
version does not work with everybody's hardware - for me test5 did only
work without ACPI.

I attached my dmesg output so you can have a look if you can find anything
strange before your system hangs.

Greetings
Andre

Linux version 2.6.0-test7 ([EMAIL PROTECTED]) (gcc version 3.3.2 20031005 (Debian 
prerelease)) #1 Thu Oct 9 14:17:31 CEST 2003
Video mode to be used for restore is 317
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009fc00 (usable)
 BIOS-e820: 0009fc00 - 000a (reserved)
 BIOS-e820: 000d - 000d4000 (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - 0fff (usable)
 BIOS-e820: 0fff - 0fff8000 (ACPI data)
 BIOS-e820: 0fff8000 - 1000 (ACPI NVS)
 BIOS-e820: fff8 - 0001 (reserved)
user-defined physical RAM map:
 user:  - 0009fc00 (usable)
 user: 0009fc00 - 000a (reserved)
 user: 000d - 000d4000 (reserved)
 user: 000f - 0010 (reserved)
 user: 0010 - 0fff (usable)
 user: 0fff - 0fff8000 (ACPI data)
 user: 0fff8000 - 1000 (ACPI NVS)
 user: fff8 - 0001 (reserved)
255MB LOWMEM available.
On node 0 totalpages: 65520
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 61424 pages, LIFO batch:14
  HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 AMI   ) @ 0x000fb100
ACPI: RSDT (v001 AMIINT VIA_P6   0x0010 MSFT 0x0097) @ 0x0fff
ACPI: FADT (v001 AMIINT VIA_P6   0x0011 MSFT 0x0097) @ 0x0fff0030
ACPI: DSDT (v001VIA   P4X266 0x1000 INTL 0x02002024) @ 0x
Building zonelist for node : 0
Kernel command line: root=/dev/hda6 vga=791 netprofile=Home pci=noacpi mem=262080K
No local APIC present or hardware disabled
Initializing CPU#0
PID hash table entries: 1024 (order 10: 8192 bytes)
Detected 1592.181 MHz processor.
Console: colour dummy device 80x25
Memory: 255488k/262080k available (2067k kernel code, 5872k reserved, 843k data, 152k 
init, 0k highmem)
Calibrating delay loop... 3072.00 BogoMIPS
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 3febf9ff   
CPU: After vendor identify, caps: 3febf9ff   
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: After all inits, caps: 3febf9ff   0080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU#0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU#0: Thermal monitoring enabled
CPU: Intel(R) Pentium(R) 4 CPU 1.60GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfdb51, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20030918
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Power Resource [URP1] (off)
ACPI: Embedded Controller [EC0] (gpe 5)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0

Re: 2.6.0-test8 PCI (?) troubles

2003-10-26 Thread Kjetil Kjernsmo
On Sunday 26 October 2003 11:28, Andre Kalus wrote:
> No, you only have to add one. Try acpi=off first - if your system
> does not boot with this option you can forget about the others.

OK! Anyway, I disabled it in the kernel, built a new one, and it gets a 
bit further. 

Now, it stops with the message
PCI: Using IRQ router VIA [1106/0686] at :00:04.0

I assume this is (from lspci -v on 2.4.22):

00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] 
(rev 40)
Subsystem: Asustek Computer, Inc. A7M266 Mainboard
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2

I'm baffled, there are no ISA slots on my mobo... But ISA bridge means 
perhaps something entirely different?

I had disabled ISA completely, but I just enabled it again and compiled 
and booted a kernel, but it didn't make any difference.  

The next thing it says after this in my 2.4.22 dmesg is
PCI: Disabling Via external APIC routing
I have disabled APIC too, some time ago. 

(BTW, MTRR was loaded shortly before, so I disabled that too in my most 
recent build.)

Best,

Kjetil
-- 
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
[EMAIL PROTECTED]  [EMAIL PROTECTED]  [EMAIL PROTECTED]
Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC


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



Re: 2.6.0-test8 PCI (?) troubles

2003-10-26 Thread Andre Kalus
On Sat, 25 Oct 2003 22:39:55 +0200, Kjetil Kjernsmo wrote:

>>You do not have to compile a
>> new kernel for this, just try to append one of the following options in
>> the boot prompt (edit lilo.conf or menu.list (grub)):
>>
>> pci=noacpi
>> pci=biosirq
>> acpi=off
> 
> I tried adding all three, but it had appreciable effect Was it wrong
> to add all three, or should I conclude this wasn't it...?
> 

No, you only have to add one. Try acpi=off first - if your system does not
boot with this option you can forget about the others.

If it works but you do not want to disable ACPI you can try one of the
others.

Greetings
Andre


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



Re: 2.6.0-test8 PCI (?) troubles

2003-10-25 Thread Kjetil Kjernsmo
Thanks a lot for the reply, Andre!

On Saturday 25 October 2003 12:29, Andre Kalus wrote:

> had some PCI problems with 2.6, too. I were able to solve them by
> disabling ACPI (partially or generally). 

OK!

>You do not have to compile a
> new kernel for this, just try to append one of the following options
> in the boot prompt (edit lilo.conf or menu.list (grub)):
>
> pci=noacpi
> pci=biosirq
> acpi=off

I tried adding all three, but it had appreciable effect Was it wrong 
to add all three, or should I conclude this wasn't it...?

BTW,
> > the LED on the floppy drive lights up and remain lit, 
this, I have found, is something I have seen just once, so it is 
probably irrelevant. 

Best,

Kjetil
-- 
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
[EMAIL PROTECTED]  [EMAIL PROTECTED]  [EMAIL PROTECTED]
Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC


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



Re: 2.6.0-test8 PCI (?) troubles

2003-10-25 Thread Andre Kalus
On Fri, 24 Oct 2003 22:56:57 +0200, Kjetil Kjernsmo wrote:

[...]
> 
> When I boot up, I get kernel messages rolling along, but stops with the
> following line:
> PCI: PCI BIOS revision 2.10 entry at 0xf0d40, last bus=1 then, the LED on
> the floppy drive lights up and remain lit, and then it just sits there.
> Nothing happens, I and have to push the reset button to reboot. It doesn't
> tell me it's panicked either.
> 
> I find the same line in my 2.4.22 dmesg. What follows after booting 2.4.22
> is this:
> PCI: PCI BIOS revision 2.10 entry at 0xf0d40, last bus=1 PCI: Using
> configuration type 1
> PCI: Probing PCI hardware
> PCI: Probing PCI hardware (bus 00)
> PCI: Using IRQ router VIA [1106/0686] at 00:04.0 PCI: Disabling Via
> external APIC routing Linux NET4.0 for Linux 2.4
[...]

Hi,

had some PCI problems with 2.6, too. I were able to solve them by
disabling ACPI (partially or generally). You do not have to compile a new
kernel for this, just try to append one of the following options in the
boot prompt (edit lilo.conf or menu.list (grub)):

pci=noacpi
pci=biosirq
acpi=off

For me, test3 worked without any options, test4 required pci=noacpi and
test5 would not work until I diabled ACPI (acpi=off). Now I have test7 and
it works with pci=noacpi.

Greetings
Andre


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



2.6.0-test8 PCI (?) troubles

2003-10-24 Thread Kjetil Kjernsmo
Hi all!

Lately, I have been desparately trying to get a second head with a 
separate login on my computer, something that has included quite a few 
approaches. Finally, I've upgraded to sid, and now I'm onto 
2.6.0-test8, and not only that, it's patched with the ruby patches. I 
got the whole thing from Andreas Schuldei, who has done some great work 
on this. Presumably, what I'm now seeing are not specifically ruby 
problems, so I try to avoid bothering him (unless he wants to chime 
in).

I've googled through the archives, and done the things recommended 
there, like enabling VT, creating /sys, etc. I'm not including all the 
details, since I don't know where to start, I guess for the sake of 
brevity it is no use posting a lot of possibly irrelevant info.

Compile (using make-kpkg) seems to go fine, so does install. Re-run of 
lilo has a couple of warnings, but nothing that has ever meant anything 
before... :-) 

When I boot up, I get kernel messages rolling along, but stops with the 
following line:
PCI: PCI BIOS revision 2.10 entry at 0xf0d40, last bus=1
then, the LED on the floppy drive lights up and remain lit, and then it 
just sits there. Nothing happens, I and have to push the reset button 
to reboot. It doesn't tell me it's panicked either. 

I find the same line in my 2.4.22 dmesg. What follows after booting 
2.4.22 is this:
PCI: PCI BIOS revision 2.10 entry at 0xf0d40, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router VIA [1106/0686] at 00:04.0
PCI: Disabling Via external APIC routing
Linux NET4.0 for Linux 2.4

Now, it seems like 2.6 does things in a different order, for example, 
the framebuffer stuff seems to be loaded before the halt happens. 
OTOH, since it looks as if it is looking through the PCI hardware with 
2.4.22 after this message, I'm guessing something goes wrong with PCI 
with 2.6.0-test8 too... I could be very wrong here, but it is the only 
clue I have... 

Any better clues...?

Cheers,

Kjetil
-- 
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
[EMAIL PROTECTED]  [EMAIL PROTECTED]  [EMAIL PROTECTED]
Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC


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