Discussion thread for linux-rpi testing kernel

Development on core packages and the distribution goes on in here.

Re: Discussion thread for linux-rpi testing kernel

Postby andiling » Sat Oct 14, 2023 12:34 am

No issue regarding that on my RPi4.
max_usb_current is not specifically configured in config.txt.
Last edited by andiling on Sat Oct 14, 2023 6:33 pm, edited 2 times in total.
andiling
 
Posts: 69
Joined: Sun Mar 06, 2016 8:34 pm

Re: Discussion thread for linux-rpi testing kernel

Postby darksky » Sat Oct 14, 2023 11:24 am

This issue was reported a couple of weeks ago.
make_clickable_callback(MAGIC_URL_FULL, '
', 'https://github.com/raspberrypi/linux/issues/5623', '', ' class="postlink"')

max_usb_current=1 in config.txt fixes it for now.
darksky
 
Posts: 35
Joined: Thu Oct 15, 2020 5:57 pm

Re: Discussion thread for linux-rpi testing kernel

Postby nicheosala » Fri Oct 20, 2023 2:28 pm

I have the following problem:

[code]
pi ➜ ~ uname -a
Linux pi 6.5.7-1-rpi-ARCH #1 SMP PREEMPT Thu Oct 19 19:57:34 EDT 2023 aarch64 GNU/Linux
pi ➜ ~ pacman -Qe linux-rpi
linux-rpi 6.5.8-1
[/code]

Of course, I've rebooted the PC after the update. Also, I've tried to manually run [code]mkinitcpio -P[/code], but I still get 6.5.7.
nicheosala
 
Posts: 4
Joined: Tue May 23, 2023 7:22 pm

Re: Discussion thread for linux-rpi testing kernel

Postby graysky » Fri Oct 20, 2023 6:04 pm

That is to be expected. I thought upstream rebased against 5.6.8 but I was mistaken so I can either add an epoch=1 which I do not want to do, or we can wait until the 6.5 code base actually catches up.
graysky
Developer
 
Posts: 1733
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Re: Discussion thread for linux-rpi testing kernel

Postby anarki » Thu Oct 26, 2023 12:14 pm

Hi all. Just switched to grayskys linux-rpi on my headless rpi4. I have a question regarding cmdline, though.

My /boot/cmdline.txt consists of:
[code]root=/dev/mmcblk0p2 rw rootwait console=serial0,115200 console=tty1 fsck.repair=yes[/code]

Although, /proc/cmdline reads:
[code]coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:12:82:CD vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 root=/dev/mmcblk0p2 rw rootwait console=ttyS0,115200 console=tty1 fsck.repair=yes[/code]

Not only I wonder how and when actual cmdline is assembled, I also wonder why snd_bcm2835_enable_headphones is present twice. Meanwhile, my /boot/config.txt reads:
[code]initramfs initramfs-linux.img followkernel

arm_boost=0
display_auto_detect=0
camera_auto_detect=0

dtparam=krnbt=on,hdmi=off,audio=on[/code]

Can someone shed some light into generation of cmdline? - Thank you
anarki
 
Posts: 4
Joined: Fri Dec 21, 2018 9:56 am

Re: Discussion thread for linux-rpi testing kernel

Postby graysky » Thu Oct 26, 2023 6:44 pm

I am shipping this:make_clickable_callback(MAGIC_URL_FULL, ' ', 'https://github.com/graysky2/PKGBUILDs/blob/rpi-6.5.y/core/linux-rpi/cmdline.txt', '', ' class="postlink"')

Not sure why /proc/cmdline differs. Mine also has extra lines.
graysky
Developer
 
Posts: 1733
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Previous

Return to Arch Linux ARM

Who is online

Users browsing this forum: No registered users and 1 guest