-   Linux - General (
-   -   Console res problems and a thank you... (

redkazan 01-10-2004 10:55 PM

Console res problems and a thank you...
Hey All:

I just wanted to say thank you for the support given by all those who have responded to my [many] threads in the past few days. A person can only handle so much googling before they turn to these forums. It's a blessing that Linux users have forums like these to turn to, and that the regulars here are so patient.

Anyway, I've finally succesfully compiled my first *good* kernel (boot time into X is under 30 seconds on my Slack 9.1/kernel 2.6.1 laptop!). There are, however, a few remaining issues I need to sort out. One I can't, for the life of me, figure out, the others are just kind of annoyances.

My biggest concern is that after I upgraded from 2.6.0 to 2.6.1, the resolution of my console has dropped to 640x480. In both 2.4.22 and 2.6.0, the console accepted lilo's call to set it to 791 (1024x768x64k). However, now it seems to ignore lilo and set itself to 640x480. I have enabled all of the relevant framebuffer stuff in the kernel, as well as the fonts and logos and stuff, just for good measure. I have tried compiling the kernel both with Radeon drivers enabled under FB support, and with regular VESA drivers enabled -- neither makes a difference. What the devil is going on? I can still obtain a res of 1400x1050 when I boot into X.

The other annoyances just deal with helping me clean up my boot. I get the following error messages at miscellaneous points during the boot process:

[Directly after ALSA loads]
request_module: failed /sbin/modprobe -- snd-card-0. error = -16

Oh, I have sound, by the way, so it's not as though ALSA isn't working properly. I just get that strange error message. ALSA support is built into the kernel; it isn't a module.

[Directly after net card driver is loaded]
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
" " snd-card-1. error = 256
" " char-major-10-134. error = 256.

And then further down the boot process; this is listed twice:
atkbd.c: unknown key released (translated set 2, code 0x7a on isa 0060/serio0)

Finally, I get some "FATAL" errors when OSS emulation is being started by ALSA. I believe it is failing to load components of OSS. Anybody else getting this?

Tech specs:

Slack 9.1
Kernel: 2.6.1
Gateway 450XL



Edit: I was playing with my lilo.conf, and set vga=normal to see if perhaps the kernel would autodetect, using the installed radeonfb drivers, and instead ended up with a garbled display. So I changed the lilo.conf BACK to 791, updated lilo, rebooted, and my screen was still garbled. What's going on? It's as though the kernel is selectively obeying lilo's vga commands.

redkazan 01-11-2004 01:26 PM


If I set vga=ask in lilo, the system ignores it, and boots with 640x480. Likewise, the system ignores it if I set vga=773 instead of 791. Also, another ridiculous problem has reared its head: the system randomly hangs during boot after loading:

ACPI: IRQ 9 was Edge Triggered, setting to Level Triggerd



Edit: Nope, after booting okay the first few times, the system hangs at that ACPI line every time now. What is going on? Also, the old 2.4.22 kernel recognizes vga=ask.

All times are GMT -5. The time now is 07:49 PM.