Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I downloaded the first SuSE 10 installation CD, burned it, and rebooted my PC so I could set up dual-boot with XP Home. On first boot the scren blanks. I added the acpi=off noapic nolapic commands to boot up and it worked just dandy. I went all through install as usual and rebooted at the end. Now when I get to Grub and try to boot SuSE, I just get the same blank screen. If I boot in failsafe it seems to be hanging when it looks for PCI cards. I'll have to get the exact error message and repost after I'm done with homework. Adding the options above doesn't help at all with this problem.
And I also have an external cardbus wifi adapter that I use because I'm fairly sure the crappy Broadcom one won't work on 64 bit (it didn't with the Ubuntu or SuSE live CD). It's an Orinoco silver 802.11b card.
Nice Laptop! My Compaq V2000 is nearly identical--Ram and everything, and my gentoo install cd gave me the same issue. Anyway, I haven't used SuSE in nearly two years so I do not quite remember the exact way to configure grub...but what you need to do is append the acpi=off noapic and nolapic paramaters to the kernel line in the /boot/grub/menu.1st file (or re-install and add them to the additional kernel paramaters or whatever line.) This probably will not be ideal since acpi will be disabled but it should get you up and running. Once you are running, I would suggest downloading the kernel source and configuring and compiling your kernel manually. I am using 2.6.17 at the moment and I do not need any of those options to be able to boot.
As for the broadcom card, there are currently two ways to get it working on amd64. The oldest and most supported way is to install ndiswrapper and get some 64-bit windows drivers for the card (hint: look on the acer-euro ftp site for the acer fararri drivers). The second way is by using the broadcom drivers that are now integrated into the kernel (2.6.17 and later). I have not had much luck with these (kernel panics), but then again I didn't try too hard since wifi works fine with ndiswrapper for me.
Ok, I got it running with the acpi=force nolapic noirq parameters. I'm using my cardbus wifi for now and it's working ok. I've never recompiled a kernel before, so I suppose it's about time I learned. Got any recommended reading on where to get started and how to not screw it up too bad?
I tried Ndiswrapper on this card before under the Ubuntu live CD and it didn't work at all. I followed the instructions to a T and got nothing. How do you have it configured?
These instructions are copied and pasted from the gentoo handbook, but they will apply to any
distro. Use YAST to install the kernel sources. They probably will not be the latest (won't have the bcm43xx drivers etc...) but they will have the SuSE patches (like bootsplash etc...).
Manually configuring a kernel is often seen as the most difficult procedure a Linux user ever has to
perform. Nothing is less true -- after configuring a couple of kernels you don't even remember that it was difficult ;)
However, one thing is true: you must know your system when you start configuring a kernel manually.
Most information can be gathered by emerging pciutils (emerge pciutils) which contains lspci. You
will now be able to use lspci within the chrooted environment. You may safely ignore any pcilib
warnings (like pcilib: cannot open /sys/bus/pci/devices) that lspci throws out. Alternatively, you
can run lspci from a non-chrooted environment. The results are the same. You can also run lsmod to
see what kernel modules the Installation CD uses (it might provide you with a nice hint on what to
Now go to your kernel source directory and execute make menuconfig. This will fire up an
ncurses-based configuration menu.
Code Listing 4: Invoking menuconfig
# cd /usr/src/linux
# make menuconfig
You will be greeted with several configuration sections. We'll first list some options you must
activate (otherwise Gentoo will not function, or not function properly without additional tweaks).
Activating Required Options
First of all, activate the use of development and experimental code/drivers. You need this,
otherwise some very important code/drivers won't show up:
Code Listing 5: Selecting experimental code/drivers
Code maturity level options --->[*] Prompt for development and/or incomplete code/drivers
Now, go to General Setup and since 2.6 is the default and only kernel supported on AMD64, we will
enable support for hot-pluggable devices for use with udev.
Code Listing 6: General Support
General setup --->[*] Support for hot-pluggable devices
We shall then select the exact processor type. The x86_64 kernel maintainer strongly recommends
users enable MCE features so that they are able to be notified of any hardware problems. On x86_64,
these errors are not printed to dmesg like on other architectures, but to /dev/mcelog. This requires
the app-admin/mcelog package.
Code Listing 7: Selecting processor type and features
Processor type and features --->
[ ] Intel MCE Features
[ ] AMD MCE Features
Processor family (AMD-Opteron/Athlon64) --->
( ) AMD-Opteron/Athlon64
( ) Intel EM64T
( ) Generic-x86-64"
Now go to File Systems and select support for the filesystems you use. Don't compile them as
modules, otherwise your Gentoo system will not be able to mount your partitions. Also select Virtual
memory and /proc file system.
Code Listing 8: Selecting necessary file systems
File systems --->
Pseudo Filesystems --->[*] /proc file system support[*] Virtual memory file system support (former shm fs)
(Select one or more of the following options as needed by your system)
<*> Reiserfs support
<*> Ext3 journalling file system support
<*> JFS filesystem support
<*> Second extended fs support
<*> XFS filesystem support
If you are using PPPoE to connect to the Internet or you are using a dial-up modem, you will need
the following options in the kernel:
Code Listing 9: Selecting PPPoE necessary drivers
Device Drivers --->
Networking Support --->
<*> PPP (point-to-point protocol) support
<*> PPP support for async serial ports
<*> PPP support for sync tty ports
The two compression options won't harm but are not definitely needed, neither does the PPP over
Ethernet option, that might only be used by rp-pppoe when configured to do kernel mode PPPoE.
If you require it, don't forget to include support in the kernel for your ethernet card.
If you have a multi-CPU Opteron or a multi-core (e.g. AMD64 X2) system, you should activate
"Symmetric multi-processing support":
Code Listing 10: Activating SMP support
Processor type and features --->[*] Symmetric multi-processing support
If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable those as well:
Code Listing 11: Activating USB Support for Input Devices
Device Drivers --->
USB Support --->
<*> USB Human Interface Device (full HID) support[*] HID input layer support
When you've finished configuring the kernel, continue with Compiling and Installing.
Compiling and Installing
Now that your kernel is configured, it is time to compile and install it. Exit the configuration and
start the compilation process:
Code Listing 12: Compiling the kernel
# make && make modules_install
When the kernel has finished compiling, copy the kernel image to /boot. Use whatever name you feel
is appropriate for your kernel choice and remember it as you will need it later on when you
configure your bootloader. Remember to replace <kernel-version> with the name and version of your
Code Listing 13: Installing the kernel
# cp arch/x86_64/boot/bzImage /boot/<kernel-version>
Now continue with Configuring Kernel Modules.
Configuring the Modules
You should list the modules you want automatically loaded in /etc/modules.autoload.d/kernel-2.6. You can add extra options to the modules too if you want.
To view all available modules, run the following find command. Don't forget to substitute "<kernel version>" with the version of the kernel you just compiled:
Code Listing 18: Viewing all available modules
# find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'
For instance, to automatically load the 3c59x.o module, edit the kernel-2.6 file and enter the module name in it.
Code Listing 19: Editing /etc/modules.autoload.d/kernel-2.6
# nano -w /etc/modules.autoload.d/kernel-2.6
Code Listing 20: /etc/modules.autoload.d/kernel-2.6
The modules part may be unnessicary as hotplug will probably take care of it. Good luck. Off to take a java test.
EDIT: Some things I forgot to mention: I would reccomend looking through all of the options and deselecting anything you know you do not need/selecting anything you may find useful. You will also need to edit your grub menu.1st file again to add/change to the new kernel (I would add another entry in grub for your new kernel until you are sure it boots and works as expected before deleting the old entry)