[gentoo-user] Bootsplash problem
I've emerge'ed bootsplash but I don't get what I expected. I use the following lines in my grub.conf: > title=Gentoo Linux > root (hd0,4) > kernel (hd0,4)/boot/bzImage root=/dev/hda7 video=vesa:mtrr vga=0x31a splash=silent hdc=ide-scsi hdd=ide-scsi > initrd=/initrd-1280x1024 I expected to boot up in silent mode whitout the usual boot messages, but it seems like im starting in verbose mode. I get the background jpeg and the boot messages on top. After a little investigation I discovered an error after initialization of the vesa framebuffer: > vesafb: framebuffer at 0xf600, mapped to 0xe080a000, size 2560k > vesafb: mode is 1280x1024x16, linelength=2560, pages=5 > vesafb: protected mode interface info at c000:03af > vesafb: scrolling: redraw > vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0 > Looking for splash picture silenjpeg size 20209 bytes, does not fit into framebuffer. > found (1280x1024, 26385 bytes, v3). I've checked the jpegs using GIMP and they should be the right size 1280x1024. Does anyone know what's wrong? Jesper -- [EMAIL PROTECTED] mailing list
[gentoo-user] Trrouble with ALSA
I have a ASUS A7V8X-X motherboard with onboard sound through the VIA VT8235 southbridge so I've tried using the snd-via82xx ALSA driver to get sound. I've followed the guide on the gentoo homepage and everything seemed to go smoothly. At boot time I get a message that says that ALSA is starting with the right driver and no error messages and Gnome also starts without the "can't find /dev/sound/mixer" error. I'm able to play CD's and such so everything is fine untill I look at dmesg. I get this near the end: > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] > ALSA ../alsa-kernel/pci/via82xx.c:499: codec_valid: codec 0 is not valid [0x87e5370] The line is repeated that many times. Does anybody know what the problem is? Jesper -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] boot time font sizes
Mark Knecht wrote: 2) How could I change the boot time font to be smaller and have more lines on the screen so that these messages didn't scroll off? If you compile "Video mode selection support" into the kernel Console drivers --> Video selection support [*] and pass vga=ask to the kernel at boot time you will be presented with some choices regarding the number of columns and rows in the console. You can also look at framebuffer support. Jesper -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Problems compiling modules
Thank you for your suggestions, but it seems like I've thrown myself into to deep waters on this one. I have lerned though that rookies like mee should stay away from the development sources :-) Jesper -- [EMAIL PROTECTED] mailing list
[gentoo-user] Problems compiling modules
I'm trying to switch to the development-sources (2.5.70) to get a better support for my hardware. The kernel compiles nicely. But I have SCSI Emulation, SCSI device support, SCSI CD-ROM support, and SCSI generic support set to compile as modules, and when I execute > make modules modules_install I get the following feedback: > Building modules, stage 2. > MODPOST > INSTALL drivers/scsi/ide-scsi.ko > INSTALL drivers/scsi/scsi_mod.ko > INSTALL drivers/scsi/sg.ko > INSTALL drivers/scsi/sr_mod.ko > if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.5.70; fi > depmod: *** Unresolved symbols in /lib/modules/2.5.70/kernel/drivers/scsi/ide-scsi.ko > depmod: scsi_register > depmod: scsi_add_host > depmod: scsi_adjust_queue_depth > depmod: scsi_unregister > depmod: scsi_sleep > depmod: scsi_remove_host > depmod: *** Unresolved symbols in /lib/modules/2.5.70/kernel/drivers/scsi/sg.ko > depmod: scsi_ioctl_send_command > depmod: scsi_device_get > depmod: scsi_block_when_processing_errors > depmod: scsi_release_request > depmod: scsi_unregister_device > depmod: scsi_do_req > depmod: scsi_reset_provider > depmod: scsi_allocate_request > depmod: proc_scsi > depmod: print_req_sense > depmod: scsi_register_device > depmod: scsi_device_put > depmod: scsi_ioctl > depmod: scsi_sleep > depmod: *** Unresolved symbols in /lib/modules/2.5.70/kernel/drivers/scsi/sr_mod.ko > depmod: scsi_io_completion > depmod: scsi_wait_req > depmod: scsi_set_medium_removal > depmod: scsi_device_get > depmod: scsi_block_when_processing_errors > depmod: scsi_release_request > depmod: scsi_unregister_device < depmod: scsi_allocate_request > depmod: print_req_sense > depmod: scsi_register_device > depmod: print_command > depmod: scsi_device_put > depmod: scsi_ioctl > depmod: scsi_sleep When I use the kernel (whit out loading the SCSI modules) I get errors during "Calculating module dependencies". I get > Failed to calculate dependencies > > modprobe: QM_MODULES: Function not implemented What am I missing in the setup ? Jesper -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] IRQ routing conflict ?
Spider wrote: For my part I didn't get rid of those messages until I updated to the new apic implementation in kernel 2.5.72 (latest at the moment of install) at which point they dissapear. The message conflict is between the via Rhine (onboard network card) and the USB interface. I've tried enabling ACPI in the kernel, wich did help on things. But I still get some warnings, so I think I'll try the development-sources. Jesper -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] refresh rate in the console
But...as many of us have learned the hard way, the riva framebuffer device tends to conflict with the closed-source, accelerated NVidia XFree drivers. Some get away with it, and some don't. If your computer locks in X, or trying to start it up or even close it down, try using something else besides the riva framebuffer device. - richard I think I'll stick with the vesa driver for now, and accept the 60Hz refresh rate. I usually use X anyway. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] IRQ routing conflict ?
I have the A7V8X motherboard (with all the extras). Are you using the extended 'APIC' interrupt controller? (I'd guess not from the messages I'm seeing, or more accurately not seeing, in the cut section you gave.) The Via controller on the A7V8X supports APIC, so you may want to turn on 'Local APIC support on uniprocessors' and 'IO-APIC support on uniprocessors' in the kernel configuration. This effectively gives you several more interrupts that you can use, and could allow you to avoid this problem. I have actually both. Do I need to do any setup to use it? The output of dmesg is below. It may be more complicated if you dual-boot a lot; I'm unfortunately no expert in how much of this information is kept in the BIOS. If you mean several operating systems by dual-boot, I do use dual-boot. I have Window XP on the first primary partition and Gentoo on some logical partitions. But how can this cause these effects? The following is the output of dmesg > Linux version 2.4.20-gentoo-r5 ([EMAIL PROTECTED]) (gcc version 3.2.2) #15 Sun Jun 22 16:59:00 CEST 2003 > BIOS-provided physical RAM map: > BIOS-e820: - 0009fc00 (usable) > BIOS-e820: 0009fc00 - 000a (reserved) > BIOS-e820: 000f - 0010 (reserved) > BIOS-e820: 0010 - 1fffc000 (usable) > BIOS-e820: 1fffc000 - 1000 (ACPI data) > BIOS-e820: 1000 - 2000 (ACPI NVS) > BIOS-e820: fec0 - fec01000 (reserved) > BIOS-e820: fee0 - fee01000 (reserved) > BIOS-e820: - 0001 (reserved) > 511MB LOWMEM available. > On node 0 totalpages: 131068 > zone(0): 4096 pages. > zone(1): 126972 pages. > zone(2): 0 pages. > Kernel command line: root=/dev/hda7 video=mtrr,vesa:1280x1024 vga=0x31a splash=silent hdc=ide-scsi hdd=ide-scsi > bootsplash: silent mode. > ide_setup: hdc=ide-scsi > ide_setup: hdd=ide-scsi > Found and enabled local APIC! > Initializing CPU#0 > Detected 1833.323 MHz processor. > Console: colour dummy device 80x25 > Calibrating delay loop... 3643.80 BogoMIPS > Memory: 512244k/524272k available (1684k kernel code, 9464k reserved, -2032k data, 120k init, 0k highmem) > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) > Inode cache hash table entries: 32768 (order: 6, 262144 bytes) > Mount-cache hash table entries: 8192 (order: 4, 65536 bytes) > Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) > Page-cache hash table entries: 131072 (order: 7, 524288 bytes) > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > CPU: L2 Cache: 512K (64 bytes/line) > Intel machine check architecture supported. > Intel machine check reporting enabled on CPU#0. > CPU: After generic, caps: 0383fbff c1c3fbff > CPU: Common caps: 0383fbff c1c3fbff > CPU: AMD Athlon(TM) XP 2500+ stepping 00 > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Checking 'hlt' instruction... OK. > POSIX conformance testing by UNIFIX > enabled ExtINT on CPU#0 > ESR value before enabling vector: > ESR value after enabling vector: > Using local APIC timer interrupts. > calibrating APIC timer ... > . CPU clock speed is 1833.0815 MHz. > . host bus clock speed is 333.1512 MHz. > cpu: 0, clocks: 1666512, slice: 833256 > CPU0 > mtrr: v1.40 (20010327) Richard Gooch ([EMAIL PROTECTED]) > mtrr: detected mtrr type: Intel > PCI: PCI BIOS revision 2.10 entry at 0xf1990, last bus=1 > PCI: Using configuration type 1 > PCI: Probing PCI hardware > PCI: Probing PCI hardware (bus 00) > PCI: Using IRQ router VIA [1106/3177] at 00:11.0 > Linux NET4.0 for Linux 2.4 > Based upon Swansea University Computer Society NET3.039 > Initializing RT netlink socket > apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16) > Starting kswapd > devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) > devfs: boot_options: 0x1 > Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). > NTFS driver 2.1.4a [Flags: R/O]. > vesafb: framebuffer at 0xf600, mapped to 0xe080, size 2560k > vesafb: mode is 1280x1024x16, linelength=2560, pages=5 > vesafb: protected mode interface info at c000:03af > vesafb: scrolling: redraw > vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0 > Looking for splash picture silenjpeg size 75071 bytes, does not fit into framebuffer. > found (1280x1024, 26385 bytes, v3). > Console: switching to colour frame buffer device 153x54 > fb0: VESA VGA frame buffer device > pty: 256 Unix98 ptys configured > Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled > ttyS00 at 0x03f8 (irq = 4) is a 16550A > Uniform Multi-Platform E-IDE driver Revision: 6.31 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > VP_IDE: IDE controller on PCI bus 00 dev 89 > PCI: No IRQ known for interrupt
[gentoo-user] Unresolved symbol when starting X
After having compiled and installed the nVidia GLX- and kernel module for my Diamond Viper 770 Riva TNT2 Ultra graphics card I get a strange message when i run startx: > Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! > Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! X starts and I can use it without getting any errors or unexpected lock ups, but they still bather me . Does anybody know what is wrong? I've followed the Desktop configuration guide on www.gentoo.org. Jesper -- [EMAIL PROTECTED] mailing list
[gentoo-user] IRQ routing conflict ?
I get the following messeges during boot > usb.c: registered new driver hub > PCI: Found IRQ 3 for device 00:10.3 > IRQ routing conflict for 00:10.0, have irq 10, want irq 3 > IRQ routing conflict for 00:10.1, have irq 10, want irq 3 > IRQ routing conflict for 00:10.2, have irq 10, want irq 3 > IRQ routing conflict for 00:10.3, have irq 10, want irq 3 > hcd.c: ehci-hcd @ 00:10.3, VIA Technologies, Inc. USB 2.0 > hcd.c: irq 10, pci mem e0aa1000 > usb.c: new USB bus registered, assigned bus number 1 > hcd/ehci-hcd.c: USB 2.0 support enabled, EHCI rev 1. 0 > hub.c: USB hub found > hub.c: 6 ports detected > uhci.c: USB Universal Host Controller Interface driver v1.1 > PCI: Found IRQ 3 for device 00:10.0 > IRQ routing conflict for 00:10.0, have irq 10, want irq 3 > IRQ routing conflict for 00:10.1, have irq 10, want irq 3 > IRQ routing conflict for 00:10.2, have irq 10, want irq 3 > IRQ routing conflict for 00:10.3, have irq 10, want irq 3 > uhci.c: USB UHCI at I/O 0xd800, IRQ 10 > usb.c: new USB bus registered, assigned bus number 2 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Found IRQ 3 for device 00:10.1 > IRQ routing conflict for 00:10.0, have irq 10, want irq 3 > IRQ routing conflict for 00:10.1, have irq 10, want irq 3 > IRQ routing conflict for 00:10.2, have irq 10, want irq 3 > IRQ routing conflict for 00:10.3, have irq 10, want irq 3 > uhci.c: USB UHCI at I/O 0xd400, IRQ 10 > usb.c: new USB bus registered, assigned bus number 3 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Found IRQ 3 for device 00:10.2 > IRQ routing conflict for 00:10.0, have irq 10, want irq 3 > IRQ routing conflict for 00:10.1, have irq 10, want irq 3 > IRQ routing conflict for 00:10.2, have irq 10, want irq 3 > IRQ routing conflict for 00:10.3, have irq 10, want irq 3 > uhci.c: USB UHCI at I/O 0xd000, IRQ 10 > usb.c: new USB bus registered, assigned bus number 4 > hub.c: USB hub found > hub.c: 2 ports detected > usb.c: registered new driver usblp > printer.c: v0.11: USB Printer Device Class driver I have a ASUS A7V8X-X motherboard with 6 USB 2.0 ports, but it seems like somthing goes wrong during boot. Do I need to set anything special in the kernel config? Jesper -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] refresh rate in the console
MAL wrote: The vesa framebuffer driver doesn't support setting refresh rates IIRC. Again, IIRC, some of the card specific drivers do. MAL I have a Diamond Viper 770 RIVA TNT2 Ultra graphics card. I've tried compiling with Console drivers --> Frame-buffer support --> nVidia Riva support [*] instead of the VESA driver, but I can't get it to work. The kernel compiles nicely but when I boot the resolution is 640x400 and I only get the TUX logo instead of the nice bootsplash :-(. Does the grub.conf need any thing special when I use the nVidia driver (I used the same as previously posted)? I've also tried appending @85 to 1280x1024 but it doesn't seem to make a difference. (only tried this with the VESA driver) Jesper -- [EMAIL PROTECTED] mailing list
[gentoo-user] refresh rate in the console
I've just emerge'ed the bootsplash ebuild and every seems to work after I compiled the kernel and did the nessesary configuration. The refresh rate is only 60Hz though and I would like to increase it to 85Hz if it's possible. I've used the example from the /usr/share/bootsplash/grub.conf to configure grub: # title=Gentoo Linux (1280x1024) # root (hd0,4) # kernel /boot/bzImage.001 root=/dev/hda7 video=mtrr,vesa:1280x1024 vga=0x31a splash=silent # initrd=/initrd-1280x1024 I run X in [EMAIL PROTECTED] without any problems, and I would like that in the consoles as well. Jesper -- [EMAIL PROTECTED] mailing list
